-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Bring in more resolution to hivestats #2
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mistercrunch
force-pushed
the
hive_stats_resolution
branch
from
April 20, 2015 22:52
12b0d6b
to
1954bea
Compare
mistercrunch
added a commit
that referenced
this pull request
Apr 20, 2015
Bring in more resolution to hivestats
asfgit
pushed a commit
that referenced
this pull request
Feb 24, 2017
Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Dear Airflow Maintainers, Please accept this PR that addresses the following issues: AIRFLOW-906 Testing Done: None. Before/After screenshots in AIRFLOW-906 (https://i ssues.apache.org/jira/browse/AIRFLOW-906) Update Code icon from lightning bolt to file Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Merge pull request #1 from djarratt/djarratt- patch-1 Update Code icon from lightning bolt to file AIRFLOW-906 change glyphicon flash to file Merge pull request #2 from djarratt/djarratt- patch-2 AIRFLOW-906 change glyphicon flash to file Closes #2104 from djarratt/master
asfgit
pushed a commit
that referenced
this pull request
Mar 29, 2017
Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Dear Airflow Maintainers, Please accept this PR that addresses the following issues: AIRFLOW-906 Testing Done: None. Before/After screenshots in AIRFLOW-906 (https://i ssues.apache.org/jira/browse/AIRFLOW-906) Update Code icon from lightning bolt to file Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Merge pull request #1 from djarratt/djarratt- patch-1 Update Code icon from lightning bolt to file AIRFLOW-906 change glyphicon flash to file Merge pull request #2 from djarratt/djarratt- patch-2 AIRFLOW-906 change glyphicon flash to file Closes #2104 from djarratt/master (cherry picked from commit bc47200)
alekstorm
pushed a commit
to alekstorm/incubator-airflow
that referenced
this pull request
Jun 1, 2017
Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Dear Airflow Maintainers, Please accept this PR that addresses the following issues: AIRFLOW-906 Testing Done: None. Before/After screenshots in AIRFLOW-906 (https://i ssues.apache.org/jira/browse/AIRFLOW-906) Update Code icon from lightning bolt to file Lightning bolts are not a visual metaphor for code or files. Since Glyphicon doesn't have a code icon (<>, for instance), we should use its file icon. Merge pull request apache#1 from djarratt/djarratt- patch-1 Update Code icon from lightning bolt to file AIRFLOW-906 change glyphicon flash to file Merge pull request apache#2 from djarratt/djarratt- patch-2 AIRFLOW-906 change glyphicon flash to file Closes apache#2104 from djarratt/master
grantnicholas
pushed a commit
to grantnicholas/incubator-airflow
that referenced
this pull request
Aug 31, 2017
…erge Some refactoring and fixed bugs on secrets / volumes in pods
zack3241
pushed a commit
to zack3241/incubator-airflow
that referenced
this pull request
Jan 25, 2018
# This is a combination of 16 commits. # This is the 1st commit message: Add flask_admin_unescape function to airfow.www.utils # This is the commit message apache#2: Add flask_admin_unescape to TaskInstanceModelView for task_id and dag_id # This is the commit message apache#3: Add test_flask_admin_unescape to tests.www.test_utils # This is the commit message apache#4: Add TestTaskInstanceModelView to tests.www.test_views This test for the proper integration between Subdag Tasks and the flask_admin package. Because the flask_admin package uses '.' characters as it's escape character and airflow enforces the dag_id.subdag_id format for the dag_id's for task_id's in subdags, the escaping that flask_admin preforms causes a duplication of the '.' character. When perform the actions that are available for those task_instances via the ui, this causes an error. These tests are here to protect against that integration issue. # This is the commit message apache#5: Update airflow.www.utils to conform to flake8 standards # This is the commit message apache#6: Update tests.www.test_utils to conform to flake8 standards # This is the commit message apache#7: Update TestTaskInstanceModelView to Leverage assertEqual # This is the commit message apache#8: Remove Superfluous SubDAG Task Var TestTaskInstanceModelView # This is the commit message apache#9: Update airflow.www.utils.gizipped.view_func to match with flake8 # This is the commit message apache#11: Update airflow.www._connection_ids to align with flake8 spacing # This is the commit message apache#12: Update tests.www.test_utils.test_flask_admin_unescape with proper spaces # This is the commit message apache#13: Align tests.www.test_views with flake8 standards # This is the commit message apache#14: Remove unnecessary SubDagOperator in tests.www.test_views # This is the commit message apache#15: Change Position on install_aliases call in www.utils for flake8 # This is the commit message apache#16: Separate setting subdag state via flask_admin model tests
boralyl
pushed a commit
to upsight/airflow
that referenced
this pull request
Apr 1, 2019
…-2772 to develop * commit '6242da51d80d49aacbf1b8653b5e38bd9f774c48': DATA-2772: add patch file DATA-2772: re-add markdown pin DATA-2772: alembic dev version and reset markdown DATA-2772: drop jira, pin markdown DATA-2772: drop password DATA-2772: readd rabbitmq DATA-2772: remove sphinx extras DATA-2772: drop eventlet DATA-2772: drop unnecessary dependencies
StewartW
pushed a commit
to StewartW/airflow
that referenced
this pull request
May 27, 2019
tiopi
pushed a commit
to tiopi/airflow
that referenced
this pull request
Jun 14, 2019
# This is the 1st commit message: [AIRFLOW-4750] Log identified zombie task instances (apache#5389) # This is the commit message apache#2: Added Sentry to contrib folder # This is the commit message apache#3: Added Sentry to contrib folder
5 tasks
danielchalef
pushed a commit
to SparkPost/airflow
that referenced
this pull request
Oct 18, 2019
aviemzur
added a commit
to aviemzur/airflow
that referenced
this pull request
Dec 31, 2019
sunkickr
added a commit
to sunkickr/airflow
that referenced
this pull request
Mar 11, 2021
# This is the 1st commit message: adds password field for aws secret # This is the commit message apache#2: adds password field for aws secret
Closed
2 tasks
mobuchowski
pushed a commit
to mobuchowski/airflow
that referenced
this pull request
Jan 4, 2022
BasPH
pushed a commit
that referenced
this pull request
Jul 11, 2022
* # This is a combination of 2 commits. # This is the 1st commit message: Extends resolve_xcom_backend documentation # This is the commit message #2: properly stylize XCom * Extends resolve_xcom_backend documentation properly stylize XCom Final docstring update Extends resolve_xcom_backend documentation properly stylize XCom Final docstring update * Stylistic changes
ephraimbuddy
pushed a commit
that referenced
this pull request
Aug 15, 2022
* # This is a combination of 2 commits. # This is the 1st commit message: Extends resolve_xcom_backend documentation # This is the commit message #2: properly stylize XCom * Extends resolve_xcom_backend documentation properly stylize XCom Final docstring update Extends resolve_xcom_backend documentation properly stylize XCom Final docstring update * Stylistic changes (cherry picked from commit 178af9d)
2 tasks
tatiana
pushed a commit
to tatiana/airflow
that referenced
this pull request
Oct 11, 2023
merge from upstream
akashsriv07
added a commit
to akashsriv07/airflow
that referenced
this pull request
Feb 12, 2024
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.