Sebastian Kreft
Sebastian Kreft
**Describe the bug** The newly added rule `max-control-nesting` added in PR #967, does not correctly handle `else if` blocks. **To Reproduce** Steps to reproduce the behavior: 1. Add the following...
## Expected Behavior I was reviewing the source code of the OpenTelemetry hooks and found two possible bugs related to how the attributes are being handled. The first one is...
## Expected Behavior The OTEL hooks should be compatible with the [latest](dependabot/pip/mypy-1.7.0) OTEL version. ## Current Behavior Instead, the package depends on version 1.16.0, which was released on 2023-05-18.
Currently `tsx` is supposed to be supported via the [`TypescriptLexer`](https://github.com/pygments/pygments/blob/0da640a6bf65654bf28940119bd379d2887e93af/pygments/lexers/javascript.py#L444-L453), however there are several issues when parsing tsx files. I'd suggest removing that support for the `TypescriptLexer`, just like it...
Hi @actgardner, I'm creating this issue to confirm if this project is still being maintained. It has served us well enough, but there are many open issues that are affecting...
It'd be great if the code could be refactored to use `go/analysis` so that `go-namecheck` can be integrated with `golangci-lint`. See https://golangci-lint.run/contributing/new-linters/
Resque-scheduler has the method `remove_delayed_selection` to remove those tasks matching certain arguments. Please add this to resque_spec.
At the moment only the output of the best compressor is checked for validity. The problem with this approach is that if in case the output is invalid, no optimized...
Running all 3 compressors just to see if the file is compressible is a waste of time, as sometimes we are only interested in knowing whether the file is compressible....