Skip to content

[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

Closed
josway opened this issue Jun 19, 2024 · 6 comments
Closed

[Bug]: Swagger_UI Error #550

josway opened this issue Jun 19, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@josway
Copy link

josway commented Jun 19, 2024

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

Run the Tunarr server

Commands:
  tunarr version           Print the current version
  tunarr server            Run the Tunarr server                       [default]
  tunarr generate-openapi  Generate OpenAPI schema which in turn is used to
                           generate a well-typed API client
  tunarr legacy-migrate    Migrate from the legacy .dizquetv database
  tunarr db [sub]          Run database commands
  tunarr fixer [sub]       Run a specific fixer task

Options:
      --version          Show version number                           [boolean]
      --log_level                                     [string] [default: "info"]
  -v, --verbose                                                          [count]
  -d, --database         Path to the database directory
                                                   [string] [default: ".tunarr"]
      --force_migration  Forces a migration from a legacy dizquetv database.
                         Useful for development and debugging. NOTE: This WILL
                         override any settings you have!
                                                      [boolean] [default: false]
      --help             Show help                                     [boolean]
  -p, --port             The port to run the Tunarr server on
                                                        [number] [default: 8000]
      --printRoutes                                   [boolean] [default: false]

FastifyError [Error]: Plugin did not start in time: '@fastify/swagger-ui'. You may have forgotten to call 'done' function or to resolve a Promise
    at Timeout._onTimeout (file:///tunarr/server/build/bundle.js:181438:35)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'AVV_ERR_PLUGIN_EXEC_TIMEOUT',
  statusCode: 500,
  fn: <ref *1> [AsyncFunction: fastifySwaggerUi] {
    default: [Circular *1],
    fastifySwaggerUi: [Circular *1],
    [Symbol(skip-override)]: true,
    [Symbol(fastify.display-name)]: '@fastify/swagger-ui',
    [Symbol(plugin-meta)]: {
      fastify: '4.x',
      name: '@fastify/swagger-ui',
      dependencies: [Array]
    }
  }
}
@josway josway added bug Something isn't working triage Attention needed labels Jun 19, 2024
@chrisbenincasa
Copy link
Owner

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.

@chrisbenincasa
Copy link
Owner

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...?

chrisbenincasa added a commit that referenced this issue Jun 19, 2024
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.
chrisbenincasa added a commit that referenced this issue Jun 19, 2024
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.
@chrisbenincasa
Copy link
Owner

I've removed the swagger-ui plugin in #551

@josway
Copy link
Author

josway commented Jun 19, 2024

Attaching the container files list here in case it helps. I'll update now and see if things start up properly.

tunarr-files.txt

@josway
Copy link
Author

josway commented Jun 19, 2024

Back to running normally again.

@chrisbenincasa
Copy link
Owner

chrisbenincasa commented Jun 19, 2024 via email

chrisbenincasa added a commit that referenced this issue Jun 22, 2024
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.
@chrisbenincasa chrisbenincasa removed the triage Attention needed label Jun 23, 2024
markdavella pushed a commit to markdavella/tunarr that referenced this issue Jun 24, 2024
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants