You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, njs_promise_resolve() might return njs_object_t instead of
njs_promise_t. Later an instance of njs_object_t was put into a
NJS_PROMISE value. Whereas njs_promise_t is always expected to be inside
of a NJS_PROMISE value.
This closesnginx#813 issue on Github.
xeioex
added a commit
to xeioex/njs
that referenced
this issue
Nov 8, 2024
Previously, njs_promise_resolve() might return njs_object_t instead of
njs_promise_t. Later an instance of njs_object_t was put into a
NJS_PROMISE value. Whereas njs_promise_t is always expected to be inside
of a NJS_PROMISE value.
This closesnginx#813 issue on Github.
Describe the bug
A clear and concise description of what the bug is.
Before submitting a bug report, please check the following:
possible to reproduce the issue.
To reproduce
Steps to reproduce the behavior:
Sorry I fuzzed code, but I can not minimize it...
Expected behavior
Don't segmentation fault.
Your environment
352c2e594e57d2bce11f7e2a773dcab417182ef1
Additional context
This is not vuln.
The text was updated successfully, but these errors were encountered: