Karthikeyan Singaravelan

Results 222 issues of Karthikeyan Singaravelan

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. ``` find . -iname '*.py' | grep -v example...

The current core.async version causes issues with Clojure 1.9 . This is fixed at https://github.com/clojure/core.async/commit/2f87bc7c7d10cb7b0baafc86e08489d58fa87424 . Consider upgrading to core.async-0.3.442 or the latest core.async to support Clojure 1.9. Thanks.

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. pyupgrade also helps in automatic conversion : https://github.com/asottile/pyupgrade/ ```...

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. pyupgrade also helps in automatic conversion : https://github.com/asottile/pyupgrade/ ```...

Depreaction warning due to invalid escape sequences in Python 3.7 . https://github.com/asottile/pyupgrade/ can be used to resolve the warnings. ``` find . -iname '*py' | grep -Ev 'setup|rdf4|tool' | xargs...

# Description The deprecated aliases were removed in Python 3.11 in python/cpython#28268 . Hence use `assertEquals` . Fixes https://github.com/bsc-wdc/dislib/issues/278 ## Type of change Please delete options that are not relevant....

### Description Task duration chart already has median run and queued duration values as markline using echarts. However dag run duration had issues implementing this since the show landing pages...

kind:feature
needs-triage

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. pyupgrade also helps in automatic conversion : https://github.com/asottile/pyupgrade/ ```...

**Is your feature request related to a problem? Please describe.** Provide function to return metrics **Describe the solution you'd like** `GET \xff\xff/status/json` returns the metrics for the cluster as JSON...

When we pass limit value to `lass-less-than` or `last-less-than-equal` it seems to go to the value and then move forward from there for the given offset. E.g. `bar1` gives `bar`...