LightQuantum

Oops! It breaks tests. Maybe I messed up something. I'll figure it out when I have time.

(and change L49 to ```var limit = parseInt(requestDef.limit, radix: 10) || 25```)

I guess it's the `unresolved_issue_count` field that determines whether a scan is passing. I'm willing to contribute a pr if this solution is acceptable.

So what's the progress of this PR? The related issue has been locked and there's no review activity on this one.

It looks like a bug of FSEvent API. Many people reported this weird behavior. Sometimes multiple recent events on the same file may get merged into a single event. ref:...

I walked into the exact problem, and when I ported the [deleted snippet in #255](https://github.com/actix/actix-net/pull/255/files#diff-dfc0e8ac07aecaa7a8dcbfbdf5f03ed84162df381e711b408ba0fd1c97a95284L249-L262) to actix 0.12.0 ([here](https://gist.github.com/PhotonQuantum/ffbae4ec04d413f0d498a5f89678dc1b)), it worked. Not sure why `stop_on_panic` is removed. I also tested...

This feature is fantastic! However, I noticed a strange behavior: the hover effect still shows when I move the cursor to the "original" position of traffic lights. The electron implementation...

Shouldn't `PytorchHalfPixel` be the following ```rust if len_out > 1 { (x_out as f32 + 0.5) * scale - 0.5 } else { 0.0 } ``` according to https://github.com/onnx/onnx/blob/master/docs/Changelog.md#Resize-11?

😢 unfortunately, no

I met 'not yet implemented: coordinate_transformation_mode: pytorch_half_pixel', then I found this pr. That said, I'm not hurrying. Correctness matters ;)