bugs when moving from v2.10.12 to v2.10.13
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
deploy lighthning with v2.10.12 -> ok
deploy lighthning with v2.10.13 -> ko
Last message: {:continue, [use_cache: nil, local_adaptors_repo: false]} 09:37:38.450 [error] GenServer Lightning.AdaptorRegistry terminating ** (CaseClauseError) no case clause matching: {:error, :timeout} (lightning 2.10.13) lib/lightning/adaptor_registry.ex:66: Lightning.AdaptorRegistry.Npm.user_packages/1 (lightning 2.10.13) lib/lightning/adaptor_registry.ex:233: Lightning.AdaptorRegistry.fetch/0 (lightning 2.10.13) lib/lightning/adaptor_registry.ex:113: Lightning.AdaptorRegistry.handle_continue/2 (stdlib 5.2.3) gen_server.erl:1085: :gen_server.try_handle_continue/3 (stdlib 5.2.3) gen_server.erl:995: :gen_server.loop/7 (stdlib 5.2.3) proc_lib.erl:241: :proc_lib.init_p_do_apply/3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the deployment change from v2.10.12 to v2.10.13, then inspect lib/lightning/adaptor_registry.ex at Lightning.AdaptorRegistry.Npm.user_packages/1, fetch/0, and handle_continue/2. Trace how {:error, :timeout} is handled and confirm that the adaptor registry starts successfully when the timeout occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100