a year ago
Building…
fatal error: all goroutines are asleep - deadlock!
Killed
goroutine 1 [chan receive]:
github.com/evanw/esbuild/internal/helpers.(*ThreadSafeWaitGroup).Wait(…)
[github.com/evanw/esbuild/internal/helpers/waitgroup.go:36](github.com/evanw/esbuild/internal/helpers/waitgroup.go:36)
main.runService.func2()
[github.com/evanw/esbuild/cmd/esbuild/service.go:114](github.com/evanw/esbuild/cmd/esbuild/service.go:114) +0x59
main.runService(0x1)
[github.com/evanw/esbuild/cmd/esbuild/service.go:160](github.com/evanw/esbuild/cmd/esbuild/service.go:160) +0x4ed
main.main()
[github.com/evanw/esbuild/cmd/esbuild/main.go:240](github.com/evanw/esbuild/cmd/esbuild/main.go:240) +0xa29
goroutine 6 [chan receive]:
main.runService.func1()
[github.com/evanw/esbuild/cmd/esbuild/service.go:98](github.com/evanw/esbuild/cmd/esbuild/service.go:98) +0x4a
created by main.runService
[github.com/evanw/esbuild/cmd/esbuild/service.go:97](github.com/evanw/esbuild/cmd/esbuild/service.go:97) +0x1e5
goroutine 7 [chan receive]:
main.(*serviceType).sendRequest(0xc0001ba060, {0x93c580, 0xc000959a70})
[github.com/evanw/esbuild/cmd/esbuild/service.go:192](github.com/evanw/esbuild/cmd/esbuild/service.go:192) +0xfa
main.runService.func3()
[github.com/evanw/esbuild/cmd/esbuild/service.go:125](github.com/evanw/esbuild/cmd/esbuild/service.go:125) +0x39
created by main.runService
[github.com/evanw/esbuild/cmd/esbuild/service.go:122](github.com/evanw/esbuild/cmd/esbuild/service.go:122) +0x31c
goroutine 13 [semacquire]:
sync.runtime_Semacquire(0xc000010300?)
runtime/sema.go:62 +0x27
sync.(*WaitGroup).Wait(0xc000114240?)
sync/waitgroup.go:116 +0x4b
github.com/evanw/esbuild/internal/bundler.ScanBundle(, {, _, _, _, _, }, {, _}, 0xc000114240, …)
[github.com/evanw/esbuild/internal/bundler/bundler.go:1333](github.com/evanw/esbuild/internal/bundler/bundler.go:1333) +0x948
github.com/evanw/esbuild/pkg/api.rebuildImpl({0xc000114240, {0xc00013c198, 0x1, 0x1}, {0x0, 0x0, 0x0}, {0x0, 0x1, 0x0, …}, …}, …)
[github.com/evanw/esbuild/pkg/api/api_impl.go:1506](github.com/evanw/esbuild/pkg/api/api_impl.go:1506) +0x2e5
github.com/evanw/esbuild/pkg/api.(*internalContext).rebuild(_))
[github.com/evanw/esbuild/pkg/api/api_impl.go:1025](github.com/evanw/esbuild/pkg/api/api_impl.go:1025) +0x2a5
github.com/evanw/esbuild/pkg/api.(*internalContext).Rebuild(0xc00036c000?))
[github.com/evanw/esbuild/pkg/api/api_impl.go:1086](github.com/evanw/esbuild/pkg/api/api_impl.go:1086) +0x58
main.(*serviceType).handleIncomingPacket.func5()
[github.com/evanw/esbuild/cmd/esbuild/service.go:293](github.com/evanw/esbuild/cmd/esbuild/service.go:293) +0xd5
created by main.(*serviceType).handleIncomingPacket
[github.com/evanw/esbuild/cmd/esbuild/service.go:290](github.com/evanw/esbuild/cmd/esbuild/service.go:290) +0x118d
goroutine 51 [chan send]:
github.com/evanw/esbuild/internal/bundler.ScanBundle.func2()
[github.com/evanw/esbuild/internal/bundler/bundler.go:1284](github.com/evanw/esbuild/internal/bundler/bundler.go:1284) +0x2c5
created by github.com/evanw/esbuild/internal/bundler.ScanBundle
my custom start command is npm start
I enclose my repo
https://github.com/kubekthecreator/airbnb-clone-stayhub-front
ⓘ Deployment information is only viewable by project members and Railway employees.
5 Replies
a year ago
You are trying to deploy a development server.
I will make the changes to your repo that are needed to run a production web server.
a year ago
Ok. Thanks!
a year ago
PR submitted, you will need to have your code use environment variables so it knows the correct full backend URL to call, you don't want to be using the proxy middleware.
a year ago
This works fine in my local development environment, but I'm unsure how to configure it for the Railway deployment. Without the proxy, I'm getting the following error:
Error: NG04002: Cannot match any routes. URL Segment: 'oauth2/authorization/okta' at Pl.noMatchError
Is there a way to maintain this proxy configuration in Railway, or perhaps configure it differently using environment variables? I need to ensure that the 'oauth2/authorization/okta' route is properly handled in the production environment.
Any guidance on how to set this up correctly in Railway would be greatly appreciated. Thank you!
a year ago
You don't want to be using a proxy in development or production,it is bad practice as far as i've seen.
Instead of making a request to the relative path `/oauth2/authorization/okta`
you would want to make a request to the full URL https://backend.domain.com/oauth2/authorization/okta
You can specify the domain via environment variables.