-
Notifications
You must be signed in to change notification settings - Fork 159
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
Nitrogen unusable :/ #143
Comments
Is this a new project generated from the most recent master?
…On Wed, Nov 15, 2023, 7:51 PM JiffB ***@***.***> wrote:
Hi Jesse,
Everything is in the title - this falls at a very bad moment, as I have an
app to finish ASAP and I did not kept the former version of nitrogen. I'm
completely stuck.
As usual, I tried to load a page I know works, but I ended with a crash of
the page + one of the crash_handler, he is the console log :
=INFO REPORT==== 16-Nov-2023::02:43:57.530593 ===
Crash Handler Crashed:
{throw,
{handler_not_found_in_context,crash_handler,
[{handler_context,config_handler,default_config_handler,undefined,[]},
{handler_context,log_handler,default_log_handler,undefined,[]},
{handler_context,process_registry_handler,nprocreg_registry_handler,
undefined,[]}]},
[{wf_handler,get_handler,1,[{file,"src/lib/wf_handler.erl"},{line,96}]},
{wf_handler,call_readonly,3,[{file,"src/lib/wf_handler.erl"},{line,61}]},
{wf_core,run_crashed_first_request,3,
[{file,"src/wf_core.erl"},{line,237}]},
{wf_core,run_crash,4,[{file,"src/wf_core.erl"},{line,44}]},
{cowboy_simple_bridge_anchor,init,2,
[{file,"src/cowboy_bridge_modules/cowboy_simple_bridge_anchor.erl"},
{line,36}]},
{cowboy_handler,execute,2,[{file,"src/cowboy_handler.erl"},{line,41}]},
{cowboy_stream_h,execute,3,[{file,"src/cowboy_stream_h.erl"},{line,320}]},
{cowboy_stream_h,request_process,3,
[{file,"src/cowboy_stream_h.erl"},{line,302}]}]}
Original Crash:
{exit,{noproc,{gen_server,call,[nitro_cache_expirer,{new,nitrogen}]}},
[{gen_server,call,2,[{file,"gen_server.erl"},{line,370}]},
{nitro_cache,init,1,[{file,"src/nitro_cache.erl"},{line,48}]},
{default_cache_handler,add_cache,2,
[{file,"src/handlers/cache/default_cache_handler.erl"},
{line,42}]},
{default_cache_handler,init,2,
[{file,"src/handlers/cache/default_cache_handler.erl"},
{line,23}]},
{wf_handler,init,1,[{file,"src/lib/wf_handler.erl"},{line,17}]},
{wf_core,'-call_init_on_handlers/0-lc$^0/1-0-',1,
[{file,"src/wf_core.erl"},{line,211}]},
{wf_core,call_init_on_handlers,0,[{file,"src/wf_core.erl"},{line,211}]},
{wf_core,run_catched,0,[{file,"src/wf_core.erl"},{line,86}]}]}
Could you please fix this ASAP ?
I also have a question : do you have a *normal* page with a working
wizard ? ( I have difficulties to translate from the wizard demo which is
very different from what I use.)
Thanks in advance & regards,
Jean-Yves
—
Reply to this email directly, view it on GitHub
<#143>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABNRHH2KCAIGXVPLLUUCRTYEVWQVAVCNFSM6AAAAAA7NMS6HOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TKOBYGQ4DSOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Btw, this error is primarily indicating that nitro_cache is not started.
If this is starting from a brand new project, I just tested with both
master and the 2.x branch, and both worked as expected.
If this is a previously generated project, but you just pulled a
nitro_cache, try using application:ensure_all_started(nitro_cache), instead
of just application:start(nitro_cache).
Maybe that will help.
…-Jesse
On Wed, Nov 15, 2023, 7:51 PM JiffB ***@***.***> wrote:
Hi Jesse,
Everything is in the title - this falls at a very bad moment, as I have an
app to finish ASAP and I did not kept the former version of nitrogen. I'm
completely stuck.
As usual, I tried to load a page I know works, but I ended with a crash of
the page + one of the crash_handler, he is the console log :
=INFO REPORT==== 16-Nov-2023::02:43:57.530593 ===
Crash Handler Crashed:
{throw,
{handler_not_found_in_context,crash_handler,
[{handler_context,config_handler,default_config_handler,undefined,[]},
{handler_context,log_handler,default_log_handler,undefined,[]},
{handler_context,process_registry_handler,nprocreg_registry_handler,
undefined,[]}]},
[{wf_handler,get_handler,1,[{file,"src/lib/wf_handler.erl"},{line,96}]},
{wf_handler,call_readonly,3,[{file,"src/lib/wf_handler.erl"},{line,61}]},
{wf_core,run_crashed_first_request,3,
[{file,"src/wf_core.erl"},{line,237}]},
{wf_core,run_crash,4,[{file,"src/wf_core.erl"},{line,44}]},
{cowboy_simple_bridge_anchor,init,2,
[{file,"src/cowboy_bridge_modules/cowboy_simple_bridge_anchor.erl"},
{line,36}]},
{cowboy_handler,execute,2,[{file,"src/cowboy_handler.erl"},{line,41}]},
{cowboy_stream_h,execute,3,[{file,"src/cowboy_stream_h.erl"},{line,320}]},
{cowboy_stream_h,request_process,3,
[{file,"src/cowboy_stream_h.erl"},{line,302}]}]}
Original Crash:
{exit,{noproc,{gen_server,call,[nitro_cache_expirer,{new,nitrogen}]}},
[{gen_server,call,2,[{file,"gen_server.erl"},{line,370}]},
{nitro_cache,init,1,[{file,"src/nitro_cache.erl"},{line,48}]},
{default_cache_handler,add_cache,2,
[{file,"src/handlers/cache/default_cache_handler.erl"},
{line,42}]},
{default_cache_handler,init,2,
[{file,"src/handlers/cache/default_cache_handler.erl"},
{line,23}]},
{wf_handler,init,1,[{file,"src/lib/wf_handler.erl"},{line,17}]},
{wf_core,'-call_init_on_handlers/0-lc$^0/1-0-',1,
[{file,"src/wf_core.erl"},{line,211}]},
{wf_core,call_init_on_handlers,0,[{file,"src/wf_core.erl"},{line,211}]},
{wf_core,run_catched,0,[{file,"src/wf_core.erl"},{line,86}]}]}
Could you please fix this ASAP ?
I also have a question : do you have a *normal* page with a working
wizard ? ( I have difficulties to translate from the wizard demo which is
very different from what I use.)
Thanks in advance & regards,
Jean-Yves
—
Reply to this email directly, view it on GitHub
<#143>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABNRHH2KCAIGXVPLLUUCRTYEVWQVAVCNFSM6AAAAAA7NMS6HOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TKOBYGQ4DSOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Last question - what is the mechanism by which Nitrogen here is being launched? Also, if you wouldn't mind sharing the whole compilation and startup sequence, that would be helpful |
Hi Jesse, sorry for the delay, a small e-mail server problem. It was both, a former one upgraded with make and a brand new one to test if its was the same. If this has a meaning, I use Erlang 25.3.2.6 compiled from their tarball. Jean-Yves |
There is some progress on the new install (no time to test the old one at this moment), however if the original index.erl page displays in the browser, it crashes in the console immediately after, here is the log :
|
This next error is indicating that From the root of the nitrogen repo, what is the latest commit?
That should be able to tell me how some of the processes are being started? |
It is launched from its root by a sh scripts :
Ok, I erased *.beam w/ this script:
and re-compiled :
and the very first start up, just after make (launched with the above script) :
|
O_o, Whiney Houston, we have a problem - i got out of the first start up and typed that, but it did not like it :/
May be it just comes from the scripts I copied at the root, as I did not commit anything since the creation of this test project. |
I mean from the root of |
Regardless, there's a disconnect between versions (pulling from the So there are a few options here to get this squared away: Option 1: Update your For your already-existing project, I'd recommend doing option 1, for a new project, I recommend option 2. Alternatively, you can automate some of the steps to upgrade to Nitrogen 3 and rebar3 with this: https://github.com/nitrogen/nitrogen#upgrading-from-nitrogen-2-to-nitrogen-3 Make sure you follow the instructions on-screen closely. There is a post-script step that requires some manual steps before running one more script. |
Arf, here it is :
|
Ah, ok, I was beginning to think about that.
I'll take this one until the net stable tag appears.
What I did was to restore nitrogen files from a former backup, but I'm locking it right now to the '2.x' branch instead of the master one to make sure there's no possibility to goof.
Talking about that, I have some fix/modifications to the 2.x branch, such as 'fix-slim-release' fixed (used: git:// instead of https://), the 'after' in element_checkbox that now works, adding the 'loading' parm into element_image and element_iframe and a modification to wf_convert (encoding/decoding the keyboard hyphen to the typographic one, that isn't recognized by databases) shall I send you directly (PM) the modified files ? |
Ideally, I'd prefer these updates as pull requests rather than as PMs.
Thanks,
…On Thu, Nov 16, 2023, 3:02 PM JiffB ***@***.***> wrote:
Regardless, there's a disconnect between versions (pulling from the master
branch of nitrogen_core won't work with the current version of the
nitrogen repo on your machine).
Ah, ok, I was beginning to think about that.
So there are a few options here to get this squared away:
Option 1: Update your rebar.config to point nitrogen_core at the 2.x
branch (instead of the master branch), then delete dependencies and rerun
make
I'll take this one until the net stable tag appears.
Option 2: Pull the latest version of nitrogen with git clone
https://github.com/nitrogen/nitrogen and run the usual make scripts from
that
For your already-existing project, I'd recommend doing option 1, for a new
project, I recommend option 2.
What I did was to restore nitrogen files from a former backup, but I'm
locking it right now to the '2.x' branch instead of the master one to make
sure there's no possibility to goof.
Alternatively, you can automate some of the steps to upgrade to Nitrogen 3
and rebar3 with this:
https://github.com/nitrogen/nitrogen#upgrading-from-nitrogen-2-to-nitrogen-3
Make sure you follow the instructions on-screen closely. There is a
post-script step that requires some manual steps before running one more
script.
Talking about that, I have some fix/modifications to the 2.x branch, such
as 'fix-slim-release' fixed (used: git:// instead of https://), the
'after' in element_checkbox that now works, adding the 'loading' parm into
element_image and element_iframe and a modification to wf_convert
(encoding/decoding the keyboard hyphen to the typographic one, that isn't
recognized by databases) shall I send you directly (PM) the modified files ?
—
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABNRHAMT64NS4HZC4MLCULYEZ5PFAVCNFSM6AAAAAA7NMS6HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJVGMYTAMJRGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi Jesse,
Everything is in the title - this falls at a very bad moment, as I have an app to finish ASAP and I did not kept the former version of nitrogen. I'm completely stuck.
As usual, I tried to load a page I know works, but I ended with a crash of the page + one of the crash_handler, he is the console log :
I just re-tested with a fresh install just in case, but it also crashed as soon as I tried : http://locahost:8000
Could you please fix this ASAP ?
Thanks in advance & regards,
Jean-Yves
The text was updated successfully, but these errors were encountered: