-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy button on error messages not working #11922
Comments
Refinement notes:
|
Ilya Bogdanov reports a new STANDUP for the provided date (2025-01-17): Progress: Changed z-order of node message, moving output ports to edges layer. It should be finished by 2025-01-20. |
Ilya Bogdanov reports a new STANDUP for yesterday (2025-01-20): Progress: Investigating CI issues on Windows runners, implementing support for output ports on the edges layer. Found issues with visualization preview. It should be finished by 2025-01-21. |
Ilya Bogdanov reports a new STANDUP for yesterday (2025-01-21): Progress: Investigating visualization preview issue, reproduced it on Windows as well, so it is not platform-specific. Little time spent checking how to properly disable sentry API in dev builds from the bazel standpoint. It should be finished by 2025-01-22. |
Ilya Bogdanov reports a new STANDUP for yesterday (2025-01-22): Progress: Still investigating the issue and searching for a workarounds. It should be finished by 2025-01-22. |
Ilya Bogdanov reports a new STANDUP for yesterday (2025-01-23): Progress: Preparing the PR with the final implementation. It should be finished by 2025-01-23. |
The copy button on error messages is not working (presumably because it is under the output port.)
Version 2024.5.1
Build 23cf258
Electron 31.2.0
Chrome 126.0.6478.127
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) enso/2024.5.1 Chrome/126.0.6478.127 Electron/31.2.0 Safari/537.36
The text was updated successfully, but these errors were encountered: