[Bug][config-ui] After upgrade the config UI is stuck

[michelengelen]

Search before asking

• [x] I had searched in the issues and found no similar issues.

What happened

I have just recently updated the devlake version from 1.0.2 to 1.0.3-beta7 to include the nginx upgrade due to a security vulnerability in nginx 1.27 and now the config ui is stuck (see screenshot)

What do you expect to happen

The config ui should be working

How to reproduce

Anything else

No response

Version

v1.0.3-beta7

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[dosubot[bot]]

The 502 Bad Gateway error after upgrading to v1.0.3-beta7 and nginx 1.29 likely means the backend service is unreachable or misconfigured. There are no documented upgrade or migration steps for nginx or DevLake that specifically address this issue, but recent changes may impact backend availability.

A recent pull request upgraded nginx in the config-ui Dockerfile to 1.29 for security reasons, but did not change nginx configuration itself PR #8481. Another change disabled CORS middleware in the backend API server, which could affect how nginx proxies requests to the backend and may cause errors if the frontend expects CORS headers PR #8549.

There is also a known backend crash after upgrading to v1.0.3-beta7 due to a database migration issue (NULL to int conversion in the 'priority' column), which can prevent the backend from starting and result in 502 errors PR #8622.

Troubleshooting steps:

• Check that the backend service is running and healthy (not crashing due to migration errors).
• Review backend logs for database migration errors or startup failures.
• Make sure nginx is correctly proxying requests to the backend service and the backend port is reachable.
• If you see migration errors, you may need to manually resolve database issues or confirm migrations are complete.
• If you rely on CORS for frontend-backend communication, consider re-enabling CORS middleware or adjusting nginx proxy headers.

If you need more targeted help, sharing backend logs or nginx config could help pinpoint the issue.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[petkostas]

Can you provide the logs from the devlake instance? This is most likely related to https://github.com/apache/incubator-devlake/issues/8621

[michelengelen]

All right ... seems like the instance keeps trying to restart due to a faulty SELECT:

[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
 - using env:   export GIN_MODE=release
 - using code:  gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /ping                     --> github.com/apache/incubator-devlake/server/api/ping.Get (3 handlers)
[GIN-debug] GET    /ready                    --> github.com/apache/incubator-devlake/server/api/ping.Ready (3 handlers)
[GIN-debug] GET    /health                   --> github.com/apache/incubator-devlake/server/api/ping.Health (3 handlers)
[GIN-debug] GET    /version                  --> github.com/apache/incubator-devlake/server/api/version.Get (3 handlers)
time="2025-10-24 08:22:09" level=info msg=" [pipeline service] get lock and wait next pipeline"
time="2025-10-24 08:22:09" level=info msg="\x1b[31;1m/app/impls/dalgorm/dalgorm.go:227 \x1b[35;1msql: Scan error on column index 0, name \"priority\": converting NULL to int is unsupported\n\x1b[0m\x1b[33m[0.973ms] \x1b[34;1m[rows:1]\x1b[0m SELECT `priority` FROM `_devlake_pipelines` WHERE status IN ('TASK_CREATED','TASK_RERUN','TASK_RESUME') ORDER BY priority DESC LIMIT 1"
panic: attached stack trace
  -- stack trace:
  | github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).convertGormError
  |     /app/impls/dalgorm/dalgorm.go:547
  | github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).Pluck
  |     /app/impls/dalgorm/dalgorm.go:227
  | github.com/apache/incubator-devlake/server/services.dequeuePipeline
  |     /app/server/services/pipeline.go:268
  | github.com/apache/incubator-devlake/server/services.RunPipelineInQueue
  |     /app/server/services/pipeline.go:335
  | runtime.goexit
  |     /usr/local/go/src/runtime/asm_amd64.s:1598
Wraps: (2) sql: Scan error on column index 0, name "priority": converting NULL to int is unsupported (500)
Wraps: (3) sql: Scan error on column index 0, name "priority"
Wraps: (4) converting NULL to int is unsupported
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *fmt.wrapError (4) *errors.errorString

Scan error on column index 0, name \"priority\": converting NULL to int is unsupported seems to be the problem here.

cc @klesh @petkostas

[michelengelen]

Seems the problem already got fixed here #8622 .. when will this be released?

[klesh]

@d4x1 Let's release a new beta on Friday

[petkostas]

@d4x1 is the a chance we get a release this week? as currently we had to disable Apache Devlake due to the specific issue.

[randidwinandra]

Hey @d4x1 , we’re seeing the same issue too. Any update on when it might be released? Thanks a lot!

[d4x1]

https://github.com/apache/incubator-devlake/releases/tag/v1.0.3-beta8

@randidwinandra @petkostas