You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.
closes: #16819
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.
closes: #16819
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.
closes: #16819
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Expected behavior:
YAML file with the bucket exported
Actual behavior:
Error retrieved:
As a side note, trying to retrieve a label, a bucket or a variable results in same error.
Environment info:
Machine where I ran the client is Ubuntu 18.04 Linux, run as a VM.
I have tried creating a brand new bucket as wlel
The
influx
CLI from 2.0.0 beta 2 was used.Metadata about the bucket I have tried to retrieve:
The text was updated successfully, but these errors were encountered: