Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Robert Prehn
@prehnra@mastodon.social  ·  activity timestamp last week

Just solved a bug in my client's application that was supposedly "caused by the switch to #elixir." After much debugging, I figured out the cause:

There was a race between their front end JS code and their backend code. If the backend code finished preparing some data before the UI was fully initialized, the frontend would barf, breaking the UI. This never happens in the pre-Elixir version of the code, because the old API never returned answer quickly enough. Task failed successfully, I guess?

  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1-alpha.8 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login