-
Parsing durations with significant millisecond accuracy (which do not appear to strictly follow the ISO8601 spec) returns incorrect results
E.g:-
Parse 'PT52M59.989…
-
*Not sure if that's the right place to report this issue, please advise.*
# Description
I'm provisioning a ServiceBus queue with an ARM template. Here is the snippet:
``` json
{
"apiVer…
-
**Describe the bug**
I've been facing some really inconsistent bugs with redis-parser lately on our application. The worst part is they seem to be happening at random, with no clear path to get it to…
-
➜ ~ kbcli version
Kubernetes: v1.25.7-gke.1000
KubeBlocks: 0.5.0-alpha.9
kbcli: 0.5.0-alpha.9
```
➜ ~ k get pod
NAME READY STATUS …
-
General comments:
1. The entire context from response seems to be copied from request including timestamp. This is incorrect.
2. Catalog (on_search) response should be exactly compliant with [this](…
-
```
nesh> const { parse } = require('iso8601-duration')
undefined
nesh> parse('P1111111111')
{ weeks: 0,
years: 0,
months: 0,
days: 0,
hours: 0,
minutes: 0,
seconds: 0 }
```
-
Please answer these questions before submitting your issue. Thanks!
1. What version of Python are you using?
Python 3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:48:03) [MSC v.1928 64 bit (AMD…
-
1. on_search shows items.location_id of "el" which doesn't match locations.id - what is this location then?
2. what does fulfillment_id of "Grocery" mean?
3. Catalog item.price should also have maxi…
-
## Steps To Reproduce
`parse('abc');`
## The current behavior
Throws error
```
TypeError: Cannot read property 'slice' of null
at parse (node_modules/iso8601-duration/lib/index.js:35:10)
`…
-
### Checklist
- [X] I'm reporting a bug unrelated to a specific site
- [X] I've verified that I'm running yt-dlp version **2022.07.18** ([update instructions](https://github.com/yt-dlp/yt-dlp#upda…