Skip to content
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

Updated notify_slack method #5136

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ashiramin
Copy link
Contributor

@ashiramin ashiramin commented Nov 3, 2024

Fixes

Fixes #4884

Description

  • notify_slack method now determines dag_id through context variables

Testing Instructions

Checklist

  • My pull request has a descriptive title (not a vague title likeUpdate index.md).
  • My pull request targets the default branch of the repository (main) or a parent feature branch.
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added or updated tests for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no visible errors.
  • I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
    PRs) or the media properties generator (ov just catalog/generate-docs media-props
    for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@openverse-bot openverse-bot added 🧱 stack: catalog Related to the catalog and Airflow DAGs 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 3, 2024
@krysal krysal added 🟩 priority: low Low priority and doesn't need to be rushed ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 5, 2024
@krysal
Copy link
Member

krysal commented Nov 6, 2024

Hey @ashiramin 👋 Could you fill out the PR template here? It would be helpful to know what you're working on so we can better guide you. I'm guessing you're targeting #4884.

It's failing the linter, you can see the error running the command:

./ov just lint

Add those changes, commit and it should pass.

@krysal
Copy link
Member

krysal commented Nov 14, 2024

@ashiramin, can you continue working on this? Let us know if anything is blocking you.

@ashiramin
Copy link
Contributor Author

@ashiramin, can you continue working on this? Let us know if anything is blocking you.

@krysal I'm sorry I had some local dev issues unrelated to this project. I got it all fixed up so I'll work on it next week.

Thanks for reaching out

@ashiramin ashiramin force-pushed the update-notify_slack branch 3 times, most recently from 3b91f4c to 3dcadc9 Compare December 8, 2024 05:34
@ashiramin ashiramin marked this pull request as ready for review December 19, 2024 05:32
@ashiramin ashiramin requested a review from a team as a code owner December 19, 2024 05:32
@ashiramin ashiramin requested review from krysal and obulat and removed request for a team December 19, 2024 05:32
Copy link
Member

@dhruvkb dhruvkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me! Thanks for your contribution @ashiramin.

) -> None:
send_message(
text,
username=username,
icon_emoji=icon_emoji,
dag_id=dag_id,
dag_id=dag.id,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is supposed to be dag_id and not id.

Suggested change
dag_id=dag.id,
dag_id=dag.dag_id,

This suggests to me that we should have some tests for this because it slipped through our CI + CD workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: catalog Related to the catalog and Airflow DAGs
Projects
Status: 🔁 Changes Requested
Development

Successfully merging this pull request may close these issues.

notify_slack should determine dag_id on its own
4 participants