Comments (8)
Just for searchability: The screenshot says
info Error: (server_error)
from devpod-provider-hetzner.
Aaaah, now I understand the request - apologies.
It looks like it's a Hetzner error code.
I think there is an improvement that can be made, which is to put the Hetzner error into a nicer format - instead of just <err.code>
, something like <err.code>: <err.message> - <err.details>
. It might get a bit big, but I think I can do something better than what it is now.
Thanks for the clarification.
from devpod-provider-hetzner.
Thanks for the clarification.
Pleased to clarify ;) I had it mixed-up a bit first, due to multiple problems at once (my mistake of changing the region while not thinking about the volume, Hetzner's hickup today + the inconsistent state of the workspace/leftover SSH key).
from devpod-provider-hetzner.
A second thing I notice: The error was logged as info
, should probably be at level error
, if that's possible.
from devpod-provider-hetzner.
Unless I'm reading it wrong, the error is already printed out (the SSH key uniqueness error).
The usage error is Cobra's standard setting of outputting the usage after all errors - I think it's here in the docs.
I'm not against changing it, but it does seem like a lot of faff for not much benefit
from devpod-provider-hetzner.
Yes but this was a second error! After removing the SSH key manually via Hetzner's Web interface (probably some inconsistent state after the Hetzner problems today), I get the original error:
Any ideas on that?
from devpod-provider-hetzner.
Ah, I had a volume from the wrong region left - after deleting that, creating the workspace worked again. And then I got confused by Hetzner's service issues.
I'm not sure if devpod-provider-hetzner can give better error messages than (server_error)
in this case. Please decide if you want to keep the issue open.
from devpod-provider-hetzner.
I think there is an improvement that can be made, which is to put the Hetzner error into a nicer format - instead of just
<err.code>
, something like<err.code>: <err.message> - <err.details>
. It might get a bit big, but I think I can do something better than what it is now.
That does sound like it would be an improvement, at least I would expect that Hetzner API would tell me what is wrong.
The actual problem might be easily reproducible by 1. changing the Hetzner region used in the provider and 2. rebuilding the workspace. I think this provider should then try to re-use the volume - and fail because of the region change. (I use DevPod and devpod-provider-hetzner since yesterday and might not understand the details properly.)
from devpod-provider-hetzner.
Related Issues (7)
- Use ssh keys to connect to machine HOT 5
- Use Hetzner Docker Image HOT 6
- Support new Hetzner machines
- thanks HOT 1
- Snapshots HOT 3
- Optional volumes HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from devpod-provider-hetzner.