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

Funk is being re-triggered, but isn't on_save #26

Open
toomim opened this issue Mar 2, 2017 · 6 comments
Open

Funk is being re-triggered, but isn't on_save #26

toomim opened this issue Mar 2, 2017 · 6 comments

Comments

@toomim
Copy link
Member

toomim commented Mar 2, 2017

This happens on slideboard:

Uncaught Exception:
AssertionError: Funk is being re-triggered, but isn't on_save. It is: "to_forget", oh and funk: function get_from_master("post/w72p51v3p6x6vg6i529") {..}
    at Console.assert (console.js:94:23)
    at Function.run_handler (/home/considerit/Dropbox/ConsiderIt/prototypes/slideboard/node_modules/statebus/statebus.js:723:21)
    at bus.route (/home/considerit/Dropbox/ConsiderIt/prototypes/slideboard/node_modules/statebus/statebus.js:852:17)
    at Function.bus.route (/home/considerit/Dropbox/ConsiderIt/prototypes/slideboard/node_modules/statebus/server.js:1029:25)
    at Timeout._onTimeout (/home/considerit/Dropbox/ConsiderIt/prototypes/slideboard/node_modules/statebus/statebus.js:391:21)
    at tryOnTimeout (timers.js:224:11)
    at Timer.listOnTimeout (timers.js:198:5)

We don't have a reproducible testcase yet, but haven't tried to make one. It seems pretty frequent.

@tkriplean
Copy link
Member

I have code that is consistently triggering this error. I haven't isolated the offending code. Here's where you can see the code and error:

The code is in Dropbox/Considerit/prototypes/reputation. The offending code is in client/reputation.coffee.

The server is running using supervisor in a screen session on our linode (screen -r reputation).

If you load http://considerit.us:3439, the server will frequently crash with the above error, restart, then crash again.

@toomim
Copy link
Member Author

toomim commented Mar 4, 2017

Thank you! Looks like I'll have to get into this one. Do you happen to know if it is always a "to_forget" on "get_from_master(...)"? If so, I think I see a path for debugging it.

@tkriplean
Copy link
Member

I think it is always "to_forget". I'll keep an eye on that. Let me know if you want me to try to create a smaller test case.

@toomim
Copy link
Member Author

toomim commented Mar 4, 2017

Ok thanks. Don't put further work into it yet.

@toomim
Copy link
Member Author

toomim commented Mar 17, 2017

Is this causing any problems with current stuff? Like, should I try to fix it?

@toomim
Copy link
Member Author

toomim commented Sep 8, 2017

Travis is also getting this now:

Uncaught Exception:
AssertionError: Funk is being re-triggered, but isn't on_save. It is: "to_forget", oh and funk: **function sockjs_pubber({"all":[{"client":"61bfc343-6e) {..}**
    at Console.assert (console.js:94:23)
    at Function.run_handler (/home/considerit/Dropbox/Invisible College/considerit-lab/node_modules/statebus/statebus.js:738:21)
    at bus.route (/home/considerit/Dropbox/Invisible College/considerit-lab/node_modules/statebus/statebus.js:901:17)
    at Function.bus.route (/home/considerit/Dropbox/Invisible College/considerit-lab/node_modules/statebus/server.js:1240:25)
    at Timeout._onTimeout (/home/considerit/Dropbox/Invisible College/considerit-lab/node_modules/statebus/statebus.js:389:21)
    at tryOnTimeout (timers.js:224:11)
    at Timer.listOnTimeout (timers.js:198:5)

I haven't gotten around to investigating it yet.

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

No branches or pull requests

2 participants