Replies: 1 comment 1 reply
-
I too periodically run into these situations. Usually I do not because I'm doing things right, but when I do it's because I'm not and that's most definitely when the nudge would be great. I'm not sure what nudge Mojo could do; after all, if it could nudge, couldn't it handle the scenario better than a slightly less vague log entry? An automatic full stack trace in that scenario, maybe? I find it especially difficult when the action is a callback. Typically when it's a
But also this would be nice:
@guest20 Do you have a one-liner that produces "Could not render a response"? This Just goes straight to a 500 error with a code line at Mojolicious.pm -- that is never where the error is! :D
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The language in this message sounds like rendering couldn't / didn't happen, as if the pre-requsites were not met for rendering, however this
croak
happens after calling$render->render
inMojolicious::Controller->render
‡ and receiving anundef
in returnIt's not clear to me what I'm supposed to do about this, and I understand there's a good chance Mojo can't know either - I guess the renderer is breaking the
->render
contract by returningundef
- but maybe this could somehow be made more specific / actionable / clear? Maybe an entry inMojolicious::Guides::FAQ
⸸ could explain what a dev is supposed to do about itI assume this message is just here to explain why the browser you're testing your app in is timing out when nothing comes out of
->render
, and I'm also sure it's a corner case, but in a case this corner'y I'd like a bit of a nudge in the right direction__
‡.
*cough*
render⸸. possibly next to / as part of
What does "Nothing has been rendered, expecting delayed response" mean?
?Beta Was this translation helpful? Give feedback.
All reactions