Closed ArKam closed 1 month ago
Can you provide more details with the whole configuration ?
The API is not that robust, and does do enough check to provide good errors to you and panics instead.
Maybe your missing a parameter or something else. This will be fixed in the future versions.
Sure!
Here is the traefik middleware configuration: https://paste.opendev.org/show/bgl8htLDok7EL7gk0VPE/
Here is the sablier configuration: https://paste.opendev.org/show/bSxzx7d8Cit9VdvXdTm3/
Here is the ingress configuration: https://paste.opendev.org/show/b4R26iLw1CohGPyjfF32/
Tell me if you need further informations.
Do you need anything more regarding this issue? How can I help you tackle it?
I've created a pull request for this, it just adds a nil check on retruned instances.
This mean that it won't crash, but I expect some unexpected feedback from the dynamic ui.
Please share with me as soon as you can if this resolves your issue.
:tada: This issue has been resolved in version 1.8.0-beta.22 :tada:
The release is available on:
v1.8.0-beta.22
Your semantic-release bot :package::rocket:
Alright! I'll test that out! Thanks a lot for the prompt patching!
@acouvreur ok, using sablier:beta is working, it loads the configuration and listen for event!
Thanks a lot!
:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:
v1.8.0
Your semantic-release bot :package::rocket:
Describe the bug When running sablier using image 1.8.0-beta.13 on a raspberry pi 4B 8Gb based kubernetes cluster, the container start correctly and is able to read the configuration file. It however fail at the moment traefik send it a request.
Context
Expected behavior Sablier send the loading page back to traefik and scale up the endpoint.
Additional context Here are the sablier container logs: https://paste.opendev.org/show/bW8eB3f3oFViuUsnY5N3/
TBN: There are no errors on Traefik logs.