You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "udayv2000 (via GitHub)" <gi...@apache.org> on 2025/12/14 05:27:57 UTC
[I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
udayv2000 opened a new issue, #36602:
URL: https://github.com/apache/superset/issues/36602
### Bug description
After upgrading Apache Superset to **6.0.0rc4**, we started observing intermittent routing errors during normal application usage.
The upgrade triggered the standard metadata database migration successfully. However, while using the Superset UI (navigating dashboards, charts, etc.), the application intermittently logs 404 NotFound and 405 MethodNotAllowed exceptions originating from Flask/Werkzeug routing.
These errors did not occur prior to upgrading to the 6.0.0 RC build.
### Screenshots/recordings
**Application logs show intermittent routing exceptions:**
werkzeug.exceptions.NotFound: 404 Not Found
werkzeug.exceptions.MethodNotAllowed: 405 Method Not Allowed
**Exceptions originate from Flask request routing:**
werkzeug/routing/map.py: match()
flask/ctx.py: match_request()
flask/app.py: raise_routing_exception()
**Steps to Reproduce**
Upgrade an existing Superset deployment to 6.0.0rc4
Allow metadata database migration to complete
Use the Superset UI (dashboards, charts, navigation)
Observe intermittent 404/405 routing exceptions in the application logs
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
This behavior was not observed on earlier Superset versions.
Since the database schema has been migrated, downgrading is not straightforward.
Seeking guidance on whether this is a known issue in the 6.0 RC builds.
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "udayv2000 (via GitHub)" <gi...@apache.org>.
udayv2000 commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3654198953
@dosu we found an additional error that seems relevant and may explain the downstream 404/405 routing issues:
Failed to add user to db session: Class 'werkzeug.local.LocalProxy' is not mapped
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3654213503
<!-- Answer -->
That error means Superset tried to add a Flask LocalProxy object (like g.user) to the SQLAlchemy session, but only real ORM model instances are allowed—so SQLAlchemy raised a mapping error. This usually happens as a side effect of session or user context issues, not as a direct cause of 404/405 routing errors, but it can signal underlying problems with session management, authentication, or version mismatches in your environment.
This warning is often triggered by version mismatches (Superset now requires Python 3.10/3.11 and Node.js 20.x), incomplete asset builds, or misconfigured authentication/session context. It can also be caused by Redis/cache misconfiguration or missing reCAPTCHA keys if you use LDAP with AUTH_USER_REGISTRATION enabled. In Helm/cloud setups, double-check your Redis and authentication configs, and make sure all dependencies are on supported versions [reference](https://github.com/apache/superset/issues/35823) [reference](https://github.com/apache/superset/discussions/35997) [reference](https://github.com/apache/superset/discussions/36296).
A fix for this was merged in April 2025 (PR #33025), which unwraps the LocalProxy before adding the user to the session, so if your image is up-to-date, you should not see this error anymore [reference](https://github.com/apache/superset/pull/33025). If you still see it, it’s likely a sign of a session or context mismatch—sometimes triggered by ingress rewrites, missing cookies, or CSRF/session token issues, which can also cause 404s on certain endpoints.
If you can correlate these errors with specific request paths or actions, that will help pinpoint whether a session/auth issue is causing both the LocalProxy warning and the routing errors. Otherwise, focus on verifying your runtime versions, asset builds, and session/auth configs. Let me know if you spot a pattern in the logs or need help digging into a specific path or action.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/edb22955-26a6-4216-83ac-a9a9d5151452?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=That%20error%20means%20Superset%20tried%20to%20add%20a%20Flask%20LocalProxy%20object%20%28like%20g.user%29%20to%20the%20SQLAlchemy%20session%2C%20but%20only%20real%20ORM%20model%20instances%20are%20allowed%E2%80%94so%20SQLAlchemy%20raised%20a%20mapping%20error.%20This%20usually%20happens%20as%20a%20side%20effect%20of%20session%20or%20user%20context%20issues%2C%20not%20as%20a%20direct%20cause%20of%20404/405%20routing%20errors%2C%20but%20it%20can%20signal%20underlying%20problems%20with%20session%20management%2C%20authentication%2C%20or%20version%20mismatches%20in%20your%20environment.%20%0A%0AThis%20warning%20is%20often%20triggered%20by%20version%20mismatches%20%28Superset%20now%20requires%20Python%203.10/3.11%20and%20Node.js%2020.x%29%2C%20incomplet
e%20asset%20builds%2C%20or%20misconfigured%20authentication/session%20context.%20It%20can%20also%20be%20caused%20by%20Redis/cache%20misconfiguration%20or%20missing%20reCAPTCHA%20keys%20if%20you%20use%20LDAP%20with%20AUTH_USER_REGISTRATION%20enabled.%20In%20Helm/cloud%20setups%2C%20double-check%20your%20Redis%20and%20authentication%20configs%2C%20and%20make%20sure%20all%20dependencies%20are%20on%20supported%20versions%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/issues/35823%29%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/discussions/35997%29%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/discussions/36296%29.%0A%0AA%20fix%20for%20this%20was%20merged%20in%20April%202025%20%28PR%20%2333025%29%2C%20which%20unwraps%20the%20LocalProxy%20before%20adding%20the%20user%20to%20the%20session%2C%20so%20if%20your%20image%20is%20up-to-date%2C%20you%20should%20not%20see%20this%20error%20anymore%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/p
ull/33025%29.%20If%20you%20still%20see%20it%2C%20it%E2%80%99s%20likely%20a%20sign%20of%20a%20session%20or%20context%20mismatch%E2%80%94sometimes%20triggered%20by%20ingress%20rewrites%2C%20missing%20cookies%2C%20or%20CSRF/session%20token%20issues%2C%20which%20can%20also%20cause%20404s%20on%20certain%20endpoints.%0A%0AIf%20you%20can%20correlate%20these%20errors%20with%20specific%20request%20paths%20or%20actions%2C%20that%20will%20help%20pinpoint%20whether%20a%20session/auth%20issue%20is%20causing%20both%20the%20LocalProxy%20warning%20and%20the%20routing%20errors.%20Otherwise%2C%20focus%20on%20verifying%20your%20runtime%20versions%2C%20asset%20builds%2C%20and%20session/auth%20configs.%20Let%20me%20know%20if%20you%20spot%20a%20pattern%20in%20the%20logs%20or%20need%20help%20digging%20into%20a%20specific%20path%20or%20action.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36602)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3650250669
<!-- Greeting -->
Hi @udayv2000! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This isn't a widely reported issue, but it's plausible given recent architectural changes in Superset 6.0.0rc4. The introduction of the new AppRootMiddleware means that if your SUPERSET_APP_ROOT, APPLICATION_ROOT, or proxy (Nginx/Apache) settings are misconfigured, requests that don't start with the expected prefix will return 404s or 405s—even intermittently if the proxy or asset build is inconsistent. This is especially common in subpath deployments or when proxy headers like X-Forwarded-Prefix aren't set exactly once and correctly [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py#L41-L107) [[discussion]](https://github.com/apache/superset/discussions/36453).
Your Python (3.9) and Node (16) versions are no longer supported for master/6.0.0rc4—Superset now requires Python 3.10/3.11 and Node 18+/20.x. Running unsupported versions can cause unpredictable routing and asset issues [[issue]](https://github.com/apache/superset/issues/35823).
Troubleshooting steps:
- Make sure SUPERSET_APP_ROOT, APPLICATION_ROOT, and STATIC_ASSETS_PREFIX are set consistently (or unset if not using a subpath).
- If behind a proxy, ensure ProxyPass/ProxyPassReverse only apply to the subpath (not /), and all X-Forwarded-* headers are set exactly once.
- Set ENABLE_PROXY_FIX = True and configure PROXY_FIX_CONFIG appropriately.
- Confirm the frontend asset build is complete and you're accessing the correct port (often 9000, not 8088).
- Clear your browser cache after config or proxy changes.
- If you use multi-domain or CORS, check SUPERSET_WEBSERVER_DOMAINS and CORS_OPTIONS.
If the issue persists after these checks, try upgrading your Python and Node versions, and look for patterns in the failing routes or actions. The new error handling stack will log all routing exceptions centrally, so detailed logs may help pinpoint the root cause [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/error_handling.py#L132-L224).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20isn%27t%20a%20widely%20reported%20issue%2C%20but%20it%27s%20plausible%20given%20recent%20architectural%20changes%20in%20Superset%206.0.0rc4.%20The%20introduction%20of%20the%20new%20AppRootMiddleware%20means%20that%20if%20your%20SUPERSET_APP_ROOT%2C%20APPLICATION_ROOT%2C%20or%20proxy%20%28Nginx/Apache%29%20settings%20are%20misconfigured%2C%20requests%20that%20don%27t%20start%20with%20the%20expected%20prefix%20will%20return%20404s%20or%20405s%E2%80%94even%20intermittently%20if%20the%20proxy%20or%20asset%20build%20is%20inconsistent.%20This%20is%20especially%20common%20in%20subpath%20deployments%20or%20when%20proxy%20headers%20like%20X-Forwarded-Prefix%20aren%27t%20set%20exactly%20once%20and%20correctly%20%5B%5Bsource%5D%5D%28https%3A//github.co
m/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py%23L41-L107%29%20%5B%5Bdiscussion%5D%5D%28https%3A//github.com/apache/superset/discussions/36453%29.%0A%0AYour%20Python%20%283.9%29%20and%20Node%20%2816%29%20versions%20are%20no%20longer%20supported%20for%20master/6.0.0rc4%E2%80%94Superset%20now%20requires%20Python%203.10/3.11%20and%20Node%2018%2B/20.x.%20Running%20unsupported%20versions%20can%20cause%20unpredictable%20routing%20and%20asset%20issues%20%5B%5Bissue%5D%5D%28https%3A//github.com/apache/superset/issues/35823%29.%0A%0ATroubleshooting%20steps%3A%0A-%20Make%20sure%20SUPERSET_APP_ROOT%2C%20APPLICATION_ROOT%2C%20and%20STATIC_ASSETS_PREFIX%20are%20set%20consistently%20%28or%20unset%20if%20not%20using%20a%20subpath%29.%0A-%20If%20behind%20a%20proxy%2C%20ensure%20ProxyPass/ProxyPassReverse%20only%20apply%20to%20the%20subpath%20%28not%20/%29%2C%20and%20all%20X-Forwarded-%2A%20headers%20are%20set%20exactly%20once.%0A-%20Set%20ENABLE_PROXY_FIX%20%3D%20Tr
ue%20and%20configure%20PROXY_FIX_CONFIG%20appropriately.%0A-%20Confirm%20the%20frontend%20asset%20build%20is%20complete%20and%20you%27re%20accessing%20the%20correct%20port%20%28often%209000%2C%20not%208088%29.%0A-%20Clear%20your%20browser%20cache%20after%20config%20or%20proxy%20changes.%0A-%20If%20you%20use%20multi-domain%20or%20CORS%2C%20check%20SUPERSET_WEBSERVER_DOMAINS%20and%20CORS_OPTIONS.%0A%0AIf%20the%20issue%20persists%20after%20these%20checks%2C%20try%20upgrading%20your%20Python%20and%20Node%20versions%2C%20and%20look%20for%20patterns%20in%20the%20failing%20routes%20or%20actions.%20The%20new%20error%20handling%20stack%20will%20log%20all%20routing%20exceptions%20centrally%2C%20so%20detailed%20logs%20may%20help%20pinpoint%20the%20root%20cause%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/error_handling.py%23L132-L224%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36602)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3654136260
<!-- Answer -->
Thanks for clarifying your setup. With the official Helm chart, Python 3.10+, and a root-path deployment, you’ve ruled out the most common causes like asset build issues and subpath/proxy misconfigurations. There aren’t any known bugs or recent changes in Superset 6.0.0rc4 that would cause intermittent 404/405 errors specifically for root-path deployments—the new AppRootMiddleware only affects subpath setups, and isn’t active when running at `/` [citation](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py#L41-L107).
Ingress controllers and health probes are a frequent source of unexpected 404s/405s, especially after upgrades. When you review your ingress and backend logs, look for patterns like liveness/readiness probes, rewritten paths, or annotations that might be sending requests to endpoints that don’t exist in Superset. If you spot any consistent failing paths or actions, share them here—I’m happy to help dig into any subtle routing or middleware edge cases if needed.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Thanks%20for%20clarifying%20your%20setup.%20With%20the%20official%20Helm%20chart%2C%20Python%203.10%2B%2C%20and%20a%20root-path%20deployment%2C%20you%E2%80%99ve%20ruled%20out%20the%20most%20common%20causes%20like%20asset%20build%20issues%20and%20subpath/proxy%20misconfigurations.%20There%20aren%E2%80%99t%20any%20known%20bugs%20or%20recent%20changes%20in%20Superset%206.0.0rc4%20that%20would%20cause%20intermittent%20404/405%20errors%20specifically%20for%20root-path%20deployments%E2%80%94the%20new%20AppRootMiddleware%20only%20affects%20subpath%20setups%2C%20and%20isn%E2%80%99t%20active%20when%20running%20at%20%60/%60%C2%A0%5Bcitation%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py%23L41-L107%29.%
0A%0AIngress%20controllers%20and%20health%20probes%20are%20a%20frequent%20source%20of%20unexpected%20404s/405s%2C%20especially%20after%20upgrades.%20When%20you%20review%20your%20ingress%20and%20backend%20logs%2C%20look%20for%20patterns%20like%20liveness/readiness%20probes%2C%20rewritten%20paths%2C%20or%20annotations%20that%20might%20be%20sending%20requests%20to%20endpoints%20that%20don%E2%80%99t%20exist%20in%20Superset.%20If%20you%20spot%20any%20consistent%20failing%20paths%20or%20actions%2C%20share%20them%20here%E2%80%94I%E2%80%99m%20happy%20to%20help%20dig%20into%20any%20subtle%20routing%20or%20middleware%20edge%20cases%20if%20needed.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36602)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "udayv2000 (via GitHub)" <gi...@apache.org>.
udayv2000 commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3654112108
@dosu thanks for the pointers.
We’re running Superset via the official Apache Helm chart with the standard images (Python 3.10+) and a root-path deployment (no subpath configuration), so runtime compatibility and manual asset builds should be ruled out.
The routing errors we’re seeing originate directly from Werkzeug (map.py 624/629 and send_from_directory), with a high volume of 404s and a small number of 405s starting immediately after upgrading to 6.0.0rc4.
Next step for us is to inspect ingress access logs and correlate them with Superset backend logs to identify the exact request paths triggering these errors (e.g., probes, ingress rewrites, or specific UI actions). Once we have a consistent pattern, we’ll share details back here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "sadpandajoe (via GitHub)" <gi...@apache.org>.
sadpandajoe commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-3715743803
This may potentially fix the issue: https://github.com/apache/superset/pull/36058
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #36602:
URL: https://github.com/apache/superset/issues/36602#issuecomment-4748306499
This was reported against the pre-release 6.0.0rc4 on Python 3.9 / Node 16 (both no longer supported), and the symptoms point to an AppRootMiddleware/proxy subpath configuration issue. A related fix landed in #36058. Could you retest on the released 6.x with a supported runtime? Closing for now, but please comment and we'll reopen if it still reproduces.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4 [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #36602: Intermittent 404 / 405 routing errors after upgrading to Superset 6.0.0rc4
URL: https://github.com/apache/superset/issues/36602
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org