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.

Sign up for GitHub

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

Jump to bottom

uninitialized constant Rack::RACK_MULTITHREAD #171

Open
benbonnet opened this issue Oct 30, 2023 · 5 comments · May be fixed by #173
Open

uninitialized constant Rack::RACK_MULTITHREAD #171

benbonnet opened this issue Oct 30, 2023 · 5 comments · May be fixed by #173

Comments

@benbonnet
Copy link

benbonnet commented Oct 30, 2023 •
edited

Using rails 7.1.1, rack (3.0.8) and lamby (~> 5.2)
Hard to get why those happen; I created a fresh app following the getting started and deploying via github actions. It does deploy without issues, but invariably getting the following error :

Executing 'config/environment.Lamby.cmd' in function directory '/app'
...
"errorMessage": "uninitialized constant Rack::RACK_MULTITHREAD"
...
2023-10-30T01:36:10.282+01:00 "/app/vendor/bundle/ruby/3.2.0/gems/lamby-5.2.0/lib/lamby/rack_http.rb:45:in `env_base'"
...

Went through the rack code trying to find Rack::RACK_MULTITHREAD; not to be found

Then further below :

Init error when loading handler
--
  | 2023-10-30T01:36:10.282+01:00 | {
  | 2023-10-30T01:36:10.282+01:00 | "errorMessage": "wrong number of arguments (given 4, expected 2..3)",

This one looks related
@hungnv-sr
Copy link

Same issue: rails-lambda/lamby-cookiecutter#41

@hungnv-sr
Copy link

any updates?

@benbonnet
Copy link
Author

benbonnet commented Nov 13, 2023 •
edited

downgrading / forcing down rack to 2.2.6.4 clears the issue; but it surely does not work with latest rack (= default installed for a new rails app seems like 3.0.x)

@arinhouck
Copy link

I experienced the same issue here.

@albertski albertski linked a pull request Jan 26, 2024 that will close this issue
Open
@albertski
Copy link

I experienced this as well. I removed the constants in #173 and it fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove uninitialized constants albertski/lamby
4 participants
@benbonnet @albertski @arinhouck @hungnv-sr