This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
Fix #207: Reverse log display order #253
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
AWS returns these in lexicographical order. These are named following a pattern of <identifier>/logs/<identifier>.<YYYYMMDDHHMMSS>.log.gz so by default they would be ordered by date.
Codecov Report
@@ Coverage Diff @@
## master #253 +/- ##
=======================================
Coverage 84.46% 84.46%
=======================================
Files 42 42
Lines 1262 1262
Branches 118 118
=======================================
Hits 1066 1066
Misses 178 178
Partials 18 18Continue to review full report at Codecov.
|
jezdez
pushed a commit
that referenced
this pull request
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 /> [](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 pull request
Jan 21, 2019
Bumps [billiard](https://github.com/celery/billiard) from 3.5.0.4 to 3.5.0.5. <details> <summary>Changelog</summary> *Sourced from [billiard's changelog](https://github.com/celery/billiard/blob/master/CHANGES.txt).* > 3.5.0.5 - 2018-12-03 > -------------------- > > - Fix a crash when handling a timeout. > - Improve billiard.einfo.Frame compatibility with Python to avoid crashes when using Django. > - Cleanups. </details> <details> <summary>Commits</summary> - [`d76e621`](celery/billiard@d76e621) Bump version. - [`06faccf`](celery/billiard@06faccf) billiard.einfo.Frame: add `f_back` attribute ([#257](https://github-redirect.dependabot.com/celery/billiard/issues/257)) - [`af85146`](celery/billiard@af85146) Remove test dependency unittest2 ([#254](https://github-redirect.dependabot.com/celery/billiard/issues/254)) - [`3309f96`](celery/billiard@3309f96) fix-billiard-timeout-handler-crash ([#249](https://github-redirect.dependabot.com/celery/billiard/issues/249)) - [`7fe2edd`](celery/billiard@7fe2edd) Prefer https:// links where available ([#253](https://github-redirect.dependabot.com/celery/billiard/issues/253)) - See full diff in [compare view](celery/billiard@v3.5.0.4...v3.5.0.5) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=billiard&package-manager=pip&previous-version=3.5.0.4&new-version=3.5.0.5) 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`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <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.
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.
AWS returns these in lexicographical order. These are named following a
pattern of /logs/..log.gz so by
default they would be ordered by date.