Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

Create view with jobs histories #271

Closed
vitillo opened this issue Feb 27, 2017 · 3 comments
Closed

Create view with jobs histories #271

vitillo opened this issue Feb 27, 2017 · 3 comments
Assignees
Milestone

Comments

@vitillo
Copy link
Contributor

vitillo commented Feb 27, 2017

There have been several jobs failing silently. Those jobs will soon generate alerts (#201) but it would still be convenient to have a master view in the dashboard that shows the history, and their status, of all scheduled jobs. Furthermore, every user should be able to see the history for their own jobs.

@jezdez
Copy link
Contributor

jezdez commented Mar 6, 2017

@vitillo Yep, another tab on the job detail page makes sense for the list of runs and their status. In fact the work on #201 is providing much of this and I'm far with the implementation so that we should finish that first and then extend that work to implement this feature request.

Would you consider showing the scheduled jobs of all users for admins in the dashboard useful? We have the permission system in place to enable the ability to do that.

@vitillo
Copy link
Contributor Author

vitillo commented Mar 6, 2017

Would you consider showing the scheduled jobs of all users for admins in the dashboard useful? We have the permission system in place to enable the ability to do that.

Yes, in fact this is the view I was referring to in my comment.

@jezdez
Copy link
Contributor

jezdez commented Mar 6, 2017

@vitillo Cool, I've opened #283 to track this separate issue then and leave this open for showing the history on the job detail page.

@robhudson robhudson self-assigned this Mar 13, 2017
@robhudson robhudson removed their assignment Mar 30, 2017
@rafrombrc rafrombrc added this to the m1 milestone Apr 26, 2017
@rafrombrc rafrombrc modified the milestones: m2, m1 May 17, 2017
robhudson added a commit that referenced this issue May 18, 2017
robhudson added a commit that referenced this issue May 22, 2017
robhudson added a commit that referenced this issue May 23, 2017
robhudson added a commit that referenced this issue May 23, 2017
@ghost ghost removed the review label May 23, 2017
jezdez pushed a commit that referenced this issue Nov 12, 2018
Bumps [pycparser](https://github.com/eliben/pycparser) from 2.18 to 2.19.
<details>
<summary>Changelog</summary>

*Sourced from [pycparser's changelog](https://github.com/eliben/pycparser/blob/master/CHANGES).*

> + Version 2.19 (2018.09.19)
> 
>   - PR [#277](https://github-redirect.dependabot.com/eliben/pycparser/issues/277): Fix parsing of floating point literals
>   - PR [#254](https://github-redirect.dependabot.com/eliben/pycparser/issues/254): Add support for parsing empty structs
>   - PR [#240](https://github-redirect.dependabot.com/eliben/pycparser/issues/240): Fix enum formatting in generated C code (also [#216](https://github-redirect.dependabot.com/eliben/pycparser/issues/216))
>   - PR [#222](https://github-redirect.dependabot.com/eliben/pycparser/issues/222): Add support for #pragma in struct declarations
>   - There are reports that this release doesn't work with Python 2.6 ([#281](https://github-redirect.dependabot.com/eliben/pycparser/issues/281)).
>     Please note that the minimal supported version is 2.7; the required versions
>     are listed in the README file. 
> 
> + Version 2.18 (2017.07.04)
> 
>   - PR [#161](https://github-redirect.dependabot.com/eliben/pycparser/issues/161) & [#184](https://github-redirect.dependabot.com/eliben/pycparser/issues/184): Update bundled PLY version to 3.10
>   - PR [#158](https://github-redirect.dependabot.com/eliben/pycparser/issues/158): Add support for the __int128 type.
>   - PR [#169](https://github-redirect.dependabot.com/eliben/pycparser/issues/169): Handle more tricky TYPEID in declarators.
>   - PR [#178](https://github-redirect.dependabot.com/eliben/pycparser/issues/178): Add columns to the coord of each node
> 
> + Version 2.17 (2016.10.29)
> 
>   - Again functionality identical to 2.15 and 2.16; the difference is that the
>     tarball now contains Python files with properly set permissions.
> 
> + Version 2.16 (2016.10.18)
> 
>   - Functionally identical to 2.15, but fixes a packaging problem that caused
>     failed installation (_build_tables wasn't rerun in the pycparser/ dir).
> 
> + Version 2.15 (2016.10.18)
> 
>   - PR [#121](https://github-redirect.dependabot.com/eliben/pycparser/issues/121): Update bundled PLY version to 3.8
>   - Issue [#117](https://github-redirect.dependabot.com/eliben/pycparser/issues/117): Fix parsing of extra semi-colons inside structure declarations.
>   - PR [#109](https://github-redirect.dependabot.com/eliben/pycparser/issues/109): Update c_generator to add {} around nested named initializers.
>   - PR [#101](https://github-redirect.dependabot.com/eliben/pycparser/issues/101): Added support for parsing pragmas into the AST.
>   - Additional fake headers and typedefs, manifest fixes ([#97](https://github-redirect.dependabot.com/eliben/pycparser/issues/97), [#106](https://github-redirect.dependabot.com/eliben/pycparser/issues/106), [#111](https://github-redirect.dependabot.com/eliben/pycparser/issues/111)).
>   - Testing with Python 3.5 instead of 3.3 now (3.4 and 3.5 are the 3.x versions
>     tested).
>   - PR [#145](https://github-redirect.dependabot.com/eliben/pycparser/issues/145): More complete support for offsetof()
>   - Issue [#116](https://github-redirect.dependabot.com/eliben/pycparser/issues/116): Fix line numbers recorded for empty and compound statements.
>   - Minor performance improvement to the invalid string literal regex.
> 
> + Version 2.14 (2015.06.09)
> 
>   - Added CParser parameter to specify output directory for generated parsing
>     tables ([#84](https://github-redirect.dependabot.com/eliben/pycparser/issues/84)).
>   - Removed lcc's cpp and its license from the distribution. Using lcc's cpp
>     is no longer recommended, now that Clang has binary builds available for
>     Windows.
> 
> + Version 2.13 (2015.05.12)
> 
></table> ... (truncated)
</details>
<details>
<summary>Commits</summary>

- [`caa4c11`](eliben/pycparser@caa4c11) Bump versions to 2.19
- [`bcb5f9f`](eliben/pycparser@bcb5f9f) Reformat dates in CHANGES to yyyy.mm.dd format
- [`40f0d91`](eliben/pycparser@40f0d91) Add test for parsing a hex float constant to the right type
- [`a915c3d`](eliben/pycparser@a915c3d) Correct Parsing of Floating Point Literals, issue [#253](https://github-redirect.dependabot.com/eliben/pycparser/issues/253) ([#277](https://github-redirect.dependabot.com/eliben/pycparser/issues/277))
- [`ccd673e`](eliben/pycparser@ccd673e) Merge branch 'master' of github.com:eliben/pycparser
- [`92f65b6`](eliben/pycparser@92f65b6) Add tests for empty struct/union typedecls
- [`8ff8088`](eliben/pycparser@8ff8088) Trim whitespace in test file
- [`a301cbb`](eliben/pycparser@a301cbb) Drop testing for EOL Pythons 3.2 & 3.3 ([#271](https://github-redirect.dependabot.com/eliben/pycparser/issues/271))
- [`0baa8f4`](eliben/pycparser@0baa8f4) Remove unnecessary __future__ import ([#266](https://github-redirect.dependabot.com/eliben/pycparser/issues/266))
- [`1d86699`](eliben/pycparser@1d86699) Use https:// for all project links where available ([#267](https://github-redirect.dependabot.com/eliben/pycparser/issues/267))
- Additional commits viewable in [compare view](eliben/pycparser@release_v2.18...release_v2.19)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=pycparser&package-manager=pip&previous-version=2.18&new-version=2.19)](https://dependabot.com/compatibility-score.html?dependency-name=pycparser&package-manager=pip&previous-version=2.18&new-version=2.19)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

**Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com).

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>
jezdez pushed a commit that referenced this issue Nov 15, 2018
Bumps [mozilla-django-oidc](https://github.com/mozilla/mozilla-django-oidc) from 1.1.1 to 1.1.2.
<details>
<summary>Changelog</summary>

*Sourced from [mozilla-django-oidc's changelog](https://github.com/mozilla/mozilla-django-oidc/blob/master/HISTORY.rst).*

> 1.1.2 (2018-08-24)
> ++++++++++++++++++
> 
> * Fix JWKS handling when OP returns multiple keys
>   Thanks `[**JustinAzoff**](https://github.com/JustinAzoff)`_
</details>
<details>
<summary>Commits</summary>

- [`32578b6`](mozilla/mozilla-django-oidc@32578b6) Bump version: 1.1.1 → 1.1.2
- [`e9f9084`](mozilla/mozilla-django-oidc@e9f9084) Update HISTORY and AUTHORS
- [`d093ba6`](mozilla/mozilla-django-oidc@d093ba6) Merge pull request [#274](https://github-redirect.dependabot.com/mozilla/mozilla-django-oidc/issues/274) from johngian/pr-273
- [`4f12f49`](mozilla/mozilla-django-oidc@4f12f49) Add extra test to distinct mismatching alg/kid.
- [`bc94dd8`](mozilla/mozilla-django-oidc@bc94dd8) problem: retrieve_matching_jwk breaks when multiple keys are returned
- [`32fecfe`](mozilla/mozilla-django-oidc@32fecfe) Merge pull request [#271](https://github-redirect.dependabot.com/mozilla/mozilla-django-oidc/issues/271) from johngian/fix-py37-travis
- [`f92ea7f`](mozilla/mozilla-django-oidc@f92ea7f) Add workaround to enable py37 in travis.
- [`c8bcd91`](mozilla/mozilla-django-oidc@c8bcd91) Add py37 in travis config.
- See full diff in [compare view](mozilla/mozilla-django-oidc@1.1.1...1.1.2)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=mozilla-django-oidc&package-manager=pip&previous-version=1.1.1&new-version=1.1.2)](https://dependabot.com/compatibility-score.html?dependency-name=mozilla-django-oidc&package-manager=pip&previous-version=1.1.1&new-version=1.1.2)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

**Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com).

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants