-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add Event timers and supporting utilities (+ lint and fmt) #31
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
- New log macro that accepts NGX_LOG_DEBUG bitmask filters - Add logging to events - Updated internal_redirect to call request methods: - ngx_named_location, ngx_internal_redirect which accepts args - Subrequest flags for masking and state - Subrequest accepts query parameters as the arg flag - Quelling lint errors and warnings - Quelling fmt workflow errors
@f5yacobucci Please remove links to not publicly available repositories. |
Can do, can you point me to an example? I'm not seeing one at the moment. Should just be nginx.org dev guide links, but I'll continue to scrub. |
@@ -70,11 +70,9 @@ pub use bindings::*; | |||
/// let data: &str = "example"; // The string to convert | |||
/// let ptr = str_to_uchar(pool, data); | |||
/// ``` | |||
pub fn str_to_uchar(pool: *mut ngx_pool_t, data: &str) -> *mut u_char { | |||
pub unsafe fn str_to_uchar(pool: *mut ngx_pool_t, data: &str) -> *mut u_char { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is that? when unsafe is used in the body of the fn, it is safe
to invoke it, otherwise, the caller must use unsafe
to unsafe { str_to_uchar(...) }
. it is definitely might break many existing codes, let's keep it back.
what's the reason?
Proposed changes