Skip to content
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

[BUG] Unknown failure causes garbo to restart #2057

Open
Alium58 opened this issue Sep 2, 2024 · 4 comments · Fixed by #2062
Open

[BUG] Unknown failure causes garbo to restart #2057

Alium58 opened this issue Sep 2, 2024 · 4 comments · Fixed by #2062

Comments

@Alium58
Copy link
Member

Alium58 commented Sep 2, 2024

Describe the bug
Garbo is looping (silently failing and running again). Somtimes it hangs as well.

I fought mime executives and seems like adventuring at barf is the issue. Attached is session log plus a screenshot of where it sometimes hangs
To Reproduce
Unknown. First time it has happened to me.

Expected behavior
doesn't silently fail or hang

Session Log
alium_20240902.txt

Additional context
Sympotoms originally happened when running candy wrapper full day wrapper script. Also have tried garbo ascend with same behavior so I don't think the wrapper is the cause.

Have tried mafia restart with no help
Have tried computer restart with no help

screenshot of where it sometime hangs for a few mins
image

@Alium58
Copy link
Member Author

Alium58 commented Sep 5, 2024

I've ascended plus got the latest version, so unknown what caused behavior change. However now I'm getting a new error around dieting

image

alium_20240904.txt

@horrible-little-slime
Copy link
Contributor

Happy to reopen the original version of this issue, but for the burnsger thing I'd make sure you're level with main, because #2060 should be resolved

@ianknowles
Copy link

ianknowles commented Sep 6, 2024

should we open another bug or change the title of this one? the searching for sugar cube loop is the main issue I think. It will sit doing that for about 30 mins.

@ianknowles
Copy link

imo close this one and use #2074. Its clearer what the remaining issue is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants