Closed marcgemis closed 1 month ago
Thank you for opening this issue!
🔔 @niallpaterson @0w0miki you might want to have a look.
Have the same issue in Slack: https://github.com/raycast/extensions/issues/13067
Have the same issue in Slack: #13067
Hi @LewisLebentz , this is a fairly large issue across extensions: https://github.com/raycast/extensions/issues/10127#issuecomment-2104485073
This issue has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊
This issue has been automatically closed due to inactivity.
Feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss this.
Keep open
Stupid bot kill the community!
Extension
https://www.raycast.com/niallpaterson/jira-time-tracking
Raycast Version
1.76.0
macOS Version
14.4.1
Description
The plugin works fine for a "smaller" project with ca 3000 entries There are problems with a project with ca 23000 entries.
With the development version I got the other day, I get
` Error: Worker terminated due to reaching memory limit: JS heap out of memory
NodeError:errors:406:5
Worker..onexit:worker:229:20
`
In the Raycast window I see that around 11.000 of the 23.000 issues where loaded.
When this happens, one cannot log time for a issues within that project. Even, when the issue is one of the more recent onces and was picked from the dropdown menu offered by the plugin
Steps To Reproduce
Current Behaviour
No response
Expected Behaviour
I wouldn't mind if there was a limit to the number of issues in memory, as long as the most recent issues are loaded.