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

Non existent atom error #358

Closed
zachdaniel opened this issue Jul 13, 2023 · 1 comment · Fixed by #359
Closed

Non existent atom error #358

zachdaniel opened this issue Jul 13, 2023 · 1 comment · Fixed by #359
Assignees
Labels
bug Something isn't working

Comments

@zachdaniel
Copy link
Collaborator

** (exit) an exception was raised:
    ** (ArgumentError) errors were found at the given arguments:

  * 1st argument: not an already existing atom

        :erlang.binary_to_existing_atom("current_user", :utf8)

Nothing in my application yet refers to :current_user and so therefore we get an error about a non existing atom. I think perhaps we should make these atoms at compile time for each resource.

@zachdaniel zachdaniel added the bug Something isn't working label Jul 13, 2023
@zachdaniel
Copy link
Collaborator Author

Nevermind :) This is apparently what happens when you forget the load_from_session plug? Either way, its me, I, I'm the problem, its me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants