tison
@tony-iqlusion but copy the pointer and length of a string (`into_inner(self) -> String`) is still different to copy the whole payload (`self.expose_secret().to_string()`)?
This is related to #334 and there is several discussion about the similar topic.
> Contextual / Hierarchical Logging This seems to be an insatnce of Logforth's [(thread-local) Diagnostic](https://docs.rs/logforth/latest/logforth/diagnostic/struct.ThreadLocalDiagnostic.html) and needs not to be a feature in `log`.
> Fatal Log Level From your description, this can be resolved either: 1. Move recoverable errors to the WARN level. 2. Tag fatal logs with a "fatal" target and specially...
On #334, AFAICS if a major version bump happens, we'd better: * At least add NOTICE and CRITICAL level. * Perhaps align with syslog's level + the TRACE level. People...
> like file/column info As for the column info we don't include in the Record struct, I file https://github.com/rust-lang/log/issues/705 for further discussion.
+1 I have a function: ```rust pub async fn read_ranges( &self, loc: Location, ranges: Vec, ) { ... } ``` .. and a function call: ```rust storage .read_ranges( loc, vec![start...
Is this still relevant? It seems no dropbox CI failures recently.
Further ref - https://bugs.openjdk.org/browse/JDK-8289190
Related code - https://github.com/jni-rs/jni-rs/blob/9278710b5d8a580f24d4b06c02ff7fb86b0821a9/src/wrapper/java_vm/vm.rs#L604-L651 Where we always pass `ptr::null_mut()` for the `JavaVMAttachArgs` position arg.