Good First Issues in Vue

Describe the bug S3 Integration: Native compatibility with decentralized modern object stores (such as RustFS, Garage, MinIO, or AWS). This project is expected to support Garage. However, the backend aborts with s3 | Failed to set bucket policy: Unimplemented action: PutBucketPolicy when I use Garage as S3 storage. To Reproduce Steps to reproduce the behavior: Create bucket and generate access key / secret key in Garage Set up Alexandrie Start Alexandrie See error Expected behavior The backend server does not fail if the S3 storage is Garage. Screenshots If applicable, add screenshots to help explain your problem. Sep 22 05:01:59 alexandrie docker[46052]: Container alexandrie-mysql Healthy Sep 22 05:01:59 alexandrie docker[46052]: Container alexandrie-backend Starting Sep 22 05:02:00 alexandrie docker[46052]: Container alexandrie-backend Started Sep 22 05:02:00 alexandrie docker[46052]: Container alexandrie-frontend Starting Sep 22 05:02:00 alexandrie docker[46052]: alexandrie-

Is your feature request related to a problem? Please describe. Feature Request: Forward Ticket to Supplier with Private Thread Use Case In many businesses, a Helpdesk Ticket starts with a customer inquiry, but resolving the inquiry requires contacting an external supplier, manufacturer, or service provider. Currently, there is no dedicated workflow in Frappe Helpdesk to communicate with an external party while keeping the entire conversation within the same ticket. Proposed Feature Add a Forward button to the Ticket that allows the agent to forward the ticket to one or more external email addresses. The forwarded conversation should be stored as a Private Thread within the same ticket. Expected Workflow Customer → Ticket → Forward to Supplier → Supplier Reply → Same Ticket The supplier's reply should automatically appear in the same Private Thread, without creating a new ticket. Forward Window When clicking Forward: To field should be empty and editable. Agent can enter

Describe the bug The document overview offers Kanban in the view selector even when no concrete workspace/container is selected. Selecting it in All workspaces displays: DEBUG: View is unrecognized or undefined. Current value: kanban The page then renders the fallback document list rather than a Kanban board. The message is misleading: kanban is a recognized view, but this context has no parent required by the board. To Reproduce Prerequisite: at least one document must be visible in the overview. With an empty document list, the component takes its no-content branch instead. Open the document overview at /dashboard/docs. Select All workspaces so no concrete parent workspace/container is selected. Select Kanban in the view selector. Observe the DEBUG message above the fallback document list. Reload the page. The stored Kanban selection can restore the same unsupported state. Also check navigation from a concrete workspace with Kanban selected back to All workspaces. Expected behavio

Problem When "Create Lead from Incoming Emails" is enabled on an Email Account (crm.utils.create_lead_from_incoming_email, wired via the Communication.after_insert hook), a CRM Lead is created for any incoming email from a sender not already known - with no filtering at all. In practice this means every newsletter, "no-reply@" notification, bounce/delivery-status message, SaaS product notification (we saw Loom/Atlassian reply-notifications, WordPress admin notifications, Google Search Console alerts), and cold sales outreach (Hunter.io-style prospecting) that lands in the connected inbox becomes a Lead, indistinguishable from a real prospect. On a single inbox connected for less than a day, this created 10 junk Leads with senders like [email protected], [email protected], wordpress@..., [email protected], and an outreach email from Hunter.io - none of which are real leads. Relevant code crm/utils/__init__.py::create_lead_from_incoming_email only checks: the communication

Currently categories are displayed as a small tree and with limited context (workspaces and categories). Teams are displayed as simple workspaces without any child. The goal of this issue is to modernize this interface and add a "graph" view. There is no specific target interface; the goal is simply to improve the current experience and make it more usable. For the graphical view, the aim is to avoid using an external library that would bloat the app for the sake of just one page. We should add a view switcher in the top-right corner, similar to the existing ones for map, list, and kanban views.

We should imporve the admin dashboard to add security stats and allow admins to detect and handle problems. Admins should be allowed to change users passwords Admins should be allowed to see and close sessions Admins should be able to suspend / ban accounts

Currelty backups export documents in a big JSON file. We should add an option to allow exports as markdown file Documents should be markdown files Categories should be folders We should keep the tree structure during export

New users currently have to discover most of Alexandrie's features on their own. Add an intuitive onboarding experience on the first login to introduce the main parts of the application. This could be implemented as an interactive guided tour, contextual popups, or another lightweight approach. The tutorial should briefly introduce key features such as: Navigation and the sidebar Creating and organizing documents The Markdown editor Command Center Main application features The goal is to help new users understand the interface without overwhelming them, while allowing them to skip or dismiss the tutorial at any time.

Add support for spanish in dashboard and landing page following the current structure: https://github.com/Smaug6739/Alexandrie/tree/main/frontend/i18n/locales

Description Currently some text fields and elements of the ui, when too long for the current window view (whether on mobile or resized desktop window), are simply cut off. Two examples are the current save folder and folder names / file names in the content tab Describe the solution you'd like Make those fields "scrollable" laterally Describe alternatives you've considered Use line breaks and extend the window's size vertically making it 2 lines Complementary informations Is this feature already implemented in the default WebUI?

Introduce a new markdown feature like {{ figure }} that will be remplaced by 1 , 2 in order of appearance during compilation. We could also allow some customization like {{ titleH1(R) }} for roman numbers, {{ titleH2(l) }} for letters a , b c in lowercase, L for uppercase etc. This would make it easy to reorganize documents without breaking labels.

Allow to share document with or without sub documents / resources Add an option to index public documents by browsers

Is docker rootless mode supported? If I substitute Step 1 here: https://yantr.org/install.html with curl -fsSL https://get.docker.com/rootless | sh Or alternatively podman. Thanks. https://docs.docker.com/engine/security/rootless/

On the Pi 4, the GPIO pins 22 and 23 map to i2c6 (ref). However, on Pi 5: The i2c6 maps to MIPI CAM/DISP0 using sda=38,scl=39. The i2c4 maps to MIPI CAM/DISP1 using sda=40,scl=41. So if someone tries to use a MIPI camera, it will conflict: BlueOS/install/boards/bcm_2712.sh Line 58 in bfbe43a "dtoverlay=i2c-gpio,i2c_gpio_sda=22,i2c_gpio_scl=23,bus=6,i2c_gpio_delay_us=0" \ ..and i2c4 is symlinked to i2c3: BlueOS/core/tools/blueos_startup_update/blueos_startup_update.py Lines 277 to 287 in bfbe43a def update_i2c4_symlink() -> bool: logger.info("Running i2c4 symlink update..") i2c4_symlink = "/dev/i2c-4" i2c4_device = "/dev/i2c-3"

Bug description I would like to report a bug, before 2.33.0, everything was OK, now part of the space to search is cut off, I'm going to leave a screenshot. It happens only in Safari on iOS and on macOS, Firefox is fine. If I revert to prior 2.33.0, everything is fine. The latest 2.34.0 also has the Issue. Expectations space in the search field box Relevant debug informations Nil Steps to reproduce On Safari only How did you install VueTorrent? Downloaded from GitHub releases Environment description OS: macOS, iOS Browser Safari : on iOS and macOS PWA: Yes / No Running inside a container: No qBittorrent version 5.2.1 VueTorrent version 2.33.0 and above Agreements The bug still occurs on the nightly build (demo runs on nightly): link The bug still occurs on the latest version of qBittorrent A similar issue doesn't already exist I checked the DevTools and included any errors that may show up

Information about bug We're trying to use the new email signature, to provide a consistent signature for all our agents. However, we're working on multiple teams, and we'd like to have a different logos etc. per team. Some people are on multiple teams, and so the image should change depending on what "hat" they have on. Version Frappe: v16.18.2 Helpdesk: 1.22.2 Installation method docker Relevant log output / Stack trace / Full Error Message.

Describe the bug It's not possible to remove an audio attachment to a post from the UI, no button visible (see first screen capture of edit UI). When encountering a server error when trying to post (for example: file too big, cannot upload more than one audio attachment), then it is impossible to go back to a working state for the UI, as there is no button to reset the post form altogether as well. Since the draft is persisted, no amount of navigation, logging out and logging in can fix the state, and it's then impossible to post with that account. To Reproduce Steps to reproduce the behavior: Go to Home Click on text area for post Add audio attachment (.mp3, .ogg, .wav for example) click "edit" no button available to remove media, as would be there for visual attachments. Add another audio media click Post Get server error (usually file too big or cannot upload 2 audio attachments with Mastodon) It is now impossible to fix the state. Expected behavior a "remove" button is avail

Discussed in #2403 Originally posted by wiesehahn September 19, 2023 Is there any documentation about possible markdown syntax? For example it seems that bold text is supported, but lists are not rendered.

描述问题 软件的运行比较吃性能，我的这台笔记本比较旧，但还是能用的，平常用VScode，浏览器开着十几个标签页都不卡，结果现在用这个软件，打开一个页面就卡一下，这一点我觉得似乎可以优化一下 在我的设备上，软件的窗口尺寸是定死的，我觉得应该让它能调节大小以便适应多样的使用环境 另外，这个软件的加好友功能是不是有些问题？我搜了官方频道的随机一个人的昵称，显示没有结果，我甚至试了单个字母，依旧没效果，是我用的方法错了吗 描述您想要的解决方案 对软件进行性能优化 加入窗口尺寸调节 考虑的替代方案 在软件中提供选项倒也是个不错的方式，以此可以决定部分非必要的功能的开关，以此提高性能 其他上下文 No response