github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-07 02:16:06 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

[GH-ISSUE #680] WebUI unresponsive after Resource Sync #8619

New Issue
Closed
opened 2026-05-03 04:44:47 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-05-03 04:44:47 -05:00
Owner
Copy Link

Originally created by @rsocko on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/680

I have noticed for the past several weeks a strange behavior: after I sync a pending Resource-Sync to my GitHub repo, the UI becomes unresponsive.

I am using Edge on a Windows PC with tons of RAM and plenty of power. This seems to consistently repro each time:

  1. Go to Resource-Syncs
  2. If there is a pending change - commit the change
  3. UX refreshes (such as alert in the top right no longer shows there is a pending sync) - however the UX becomes completely unresponsive. If I try to click on anything I get an alert from Edge that the page is not responding. This does not seem to resolve and I end up closing the tab completely.
Originally created by @rsocko on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/680 I have noticed for the past several weeks a strange behavior: after I sync a pending Resource-Sync to my GitHub repo, the UI becomes unresponsive. I am using Edge on a Windows PC with tons of RAM and plenty of power. This seems to consistently repro each time: 1. Go to Resource-Syncs 2. If there is a pending change - commit the change 3. UX refreshes (such as alert in the top right no longer shows there is a pending sync) - however the UX becomes completely unresponsive. If I try to click on anything I get an alert from Edge that the page is not responding. This does not seem to resolve and I end up closing the tab completely.
GiteaMirror added the bug label 2026-05-03 04:44:47 -05:00
GiteaMirror commented 2026-05-03 04:44:51 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Jul 24, 2025):

I think I need to remove the fancy syntax highlighting for the TOML. In edge case it causes this UI freeze.

<!-- gh-comment-id:3111938583 --> @mbecker20 commented on GitHub (Jul 24, 2025): I think I need to remove the fancy syntax highlighting for the TOML. In edge case it causes this UI freeze.
GiteaMirror commented 2026-05-03 04:44:52 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Jul 24, 2025):

It is sad because this syntax highlighting is nice. But the way you make syntax highlighting with monaco editor is incredibly confusing and I have no idea how to debug this issue. The code is here: https://github.com/moghtech/komodo/blob/main/frontend/src/monaco/toml.ts

<!-- gh-comment-id:3111940495 --> @mbecker20 commented on GitHub (Jul 24, 2025): It is sad because this syntax highlighting is nice. But the way you make syntax highlighting with monaco editor is incredibly confusing and I have no idea how to debug this issue. The code is here: https://github.com/moghtech/komodo/blob/main/frontend/src/monaco/toml.ts
GiteaMirror commented 2026-05-03 04:44:53 -05:00
Author
Owner
Copy Link

@rsocko commented on GitHub (Jul 25, 2025):

Are you using the same syntax highlighting on the Stack Info page (and perhaps elsewhere?) Or are you using a different type/feature (like a diff view perhaps?)

<!-- gh-comment-id:3117951551 --> @rsocko commented on GitHub (Jul 25, 2025): Are you using the same syntax highlighting on the Stack Info page (and perhaps elsewhere?) Or are you using a different type/feature (like a diff view perhaps?)
GiteaMirror commented 2026-05-03 04:44:55 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Jul 25, 2025):

The syntax highlighting depends on the language, stack info uses standard Monaco yaml highlighting. On toml / sync syntax highlighting has this issue.

<!-- gh-comment-id:3120403907 --> @mbecker20 commented on GitHub (Jul 25, 2025): The syntax highlighting depends on the language, stack info uses standard Monaco yaml highlighting. On toml / sync syntax highlighting has this issue.
GiteaMirror commented 2026-05-03 04:44:55 -05:00
Author
Owner
Copy Link

@oblivioncth commented on GitHub (Aug 5, 2025):

It does seem to be that, as for my at the moment the page will freeze if I have the Info tab selected, which of course has the highlighting.

The highlighting is really cool too :(

<!-- gh-comment-id:3155856931 --> @oblivioncth commented on GitHub (Aug 5, 2025): It does seem to be that, as for my at the moment the page will freeze if I have the `Info` tab selected, which of course has the highlighting. The highlighting is really cool too :(
GiteaMirror commented 2026-05-03 04:44:57 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Aug 30, 2025):

Starting in 1.19.0, the fancy TOML highlighting is disabled by default to avoid this issue. If your setup works with it, you can enable it again with KOMODO_ENABLE_FANCY_TOML=true

<!-- gh-comment-id:3238964971 --> @mbecker20 commented on GitHub (Aug 30, 2025): Starting in 1.19.0, the fancy TOML highlighting is disabled by default to avoid this issue. If your setup works with it, you can enable it again with `KOMODO_ENABLE_FANCY_TOML=true`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#8619
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?