You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "slice-swayams (via GitHub)" <gi...@apache.org> on 2025/11/17 05:50:34 UTC
[I] Slack API issue - Reports not being generated [superset]
slice-swayams opened a new issue, #36129:
URL: https://github.com/apache/superset/issues/36129
### Bug description
Since the files_upload api is being deprecated by Superset, I have found many reports are not being published properly. So we need to either remove the slack_api code or we need to add an try except to use files_upload_v2 in place of files_upload
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] 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] Slack API issue - Reports not being generated [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #36129:
URL: https://github.com/apache/superset/issues/36129#issuecomment-3540097471
<!-- Greeting -->
Hi @slice-swayams! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Superset already includes a migration path from Slack's deprecated files_upload API to files_upload_v2 for report publishing. The SlackNotification class uses files_upload, but if the v2 API is available (determined by the ALERT_REPORT_SLACK_V2 feature flag and Slack scopes), it raises an exception to trigger an upgrade to files_upload_v2. The report execution logic catches this, updates the recipient to use the v2 API, converts channel names to IDs, and retries the notification with files_upload_v2. If the migration fails (for example, if a channel can't be found), the code reverts to the legacy type and logs an error for manual correction. This migration is handled at runtime, so you don't need to manually add a try/except for files_upload_v2 in the notification code itself. For best results, ensure the ALERT_REPORT_SLACK_V2 feature flag is enabled and your Slack app has the required scopes, especially channels:read, to support the v2 API and avoid deprecation issues in future S
uperset releases.
[Reference: Slack notification migration logic](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py#L130-L626)
<!-- 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/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/23e4e764-e4e3-4184-a5a8-75abb5c1302b?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
b) [](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/36129)
--
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] Slack API issue - Reports not being generated [superset]
Posted by "sakshi-suryawanshi (via GitHub)" <gi...@apache.org>.
sakshi-suryawanshi commented on issue #36129:
URL: https://github.com/apache/superset/issues/36129#issuecomment-3703894898
I’m using Apache Superset version 5. After setting the ALERT_REPORT_SLACK_V2 flag to true, Superset still throws a deprecation warning. I also tried applying a patch to the code, but it didn’t work. I attempted several other approaches as well, but none resolved the issue.
My setup uses TypeScript and Pulumi for Infrastructure as Code (IaC) to deploy Apache Superset (Python) on AWS EKS via Kubernetes/Helm. The stack includes PostgreSQL, Redis, Redshift, and Slack integrations.
--
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] Slack API issue - Reports not being generated [superset]
Posted by "sadpandajoe (via GitHub)" <gi...@apache.org>.
sadpandajoe commented on issue #36129:
URL: https://github.com/apache/superset/issues/36129#issuecomment-3543263923
Do you have reproducible steps or logs? We've had slack v2 for a bit and it has been working so far without any issues.
--
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] Slack API issue - Reports not being generated [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #36129:
URL: https://github.com/apache/superset/issues/36129#issuecomment-4898862635
Closing, as Superset already migrated to files_upload_v2 behind ALERT_REPORT_SLACK_V2. Sadpandajoe stated v2 works and asked for logs/repro in Nov 2025, but none was provided. The only follow-up is a v5 deployment-specific report (EKS/Pulumi) without logs, but we only support 6.x as we work on v7.
--
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] Slack API issue - Reports not being generated [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #36129: Slack API issue - Reports not being generated
URL: https://github.com/apache/superset/issues/36129
--
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