-
-
Notifications
You must be signed in to change notification settings - Fork 17
[Bug]: Swagger_UI Error #550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This one is super frustrating since it's outside of our code pretty much completely. I'm inclined to just remove swagger at this point since we're not really using it right now anyway. |
If you get a chance, can you list out the directories and files within the /tunarr directory in the container? I wonder if some of the swagger UI files got messed up somehow...? |
We've seen reports like #550 where swagger-ui prevents the server from starting, permanently. I haven't been able to reproduce this yet. We've opened an issue on the plugin repo to see if they have ideas: fastify/fastify-swagger-ui#156 For now, we're not really in need of this anyway, so just remove it. I've also updated a bunch of deps and shimmed in the "DOM" types in our tsconfig since there are lots of errors when compiling during the lib check phase for things like esbuild, vitest.
We've seen reports like #550 where swagger-ui prevents the server from starting, permanently. I haven't been able to reproduce this yet. We've opened an issue on the plugin repo to see if they have ideas: fastify/fastify-swagger-ui#156 For now, we're not really in need of this anyway, so just remove it. I've also updated a bunch of deps and shimmed in the "DOM" types in our tsconfig since there are lots of errors when compiling during the lib check phase for things like esbuild, vitest.
I've removed the swagger-ui plugin in #551 |
Attaching the container files list here in case it helps. I'll update now and see if things start up properly. |
Back to running normally again. |
Great. Hopefully the maintainers over there can give us some clues as to
what’s going on. I’ll check out the files you attached too
…On Wed, Jun 19, 2024 at 11:13 AM josway ***@***.***> wrote:
Back to running normally again.
—
Reply to this email directly, view it on GitHub
<#550 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMQRX7HDMYYIBUUEBFYL6DZIGNXZAVCNFSM6AAAAABJRG4YLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYHE2DOMBQGQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
We've seen reports like #550 where swagger-ui prevents the server from starting, permanently. I haven't been able to reproduce this yet. We've opened an issue on the plugin repo to see if they have ideas: fastify/fastify-swagger-ui#156 For now, we're not really in need of this anyway, so just remove it. I've also updated a bunch of deps and shimmed in the "DOM" types in our tsconfig since there are lots of errors when compiling during the lib check phase for things like esbuild, vitest.
…asa#551) We've seen reports like chrisbenincasa#550 where swagger-ui prevents the server from starting, permanently. I haven't been able to reproduce this yet. We've opened an issue on the plugin repo to see if they have ideas: fastify/fastify-swagger-ui#156 For now, we're not really in need of this anyway, so just remove it. I've also updated a bunch of deps and shimmed in the "DOM" types in our tsconfig since there are lots of errors when compiling during the lib check phase for things like esbuild, vitest.
Contact Details
No response
What happened?
Got through re-building most of my channels when the swagger_ui error arose again. I am unable to get the container started again. Deleted the last channel-lineup file but that did not help. No additional log info other than the below.
Version
0.1.0
What browser did you experience the the problem on?
No response
What operating system are you using?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: