Tool to check PAAS/SAAS status pages (API+CLI)
Simple COVID-19 tracker based on Johns Hopkins CSSE data.
amureki/github-repo-pulls-scoreboard 6
Shows top PR creators and assignees for any GitHub repository
CLI website status checker based on isitup.org
amureki/salesforce_id_converter 4
Convert 15 character Salesforce id into a 18 character id
Make Django App Quickly
amureki/serienplakate_parser 3
Parse new posters to order at http://serienplakate.de/
delete branch amureki/spelling
delete branch : issues/96/find_spec_value_error
delete time in 2 days
pull request commentsphinx-contrib/spelling
Handle `ValueError` raised by `importlib.util.find_spec`
@dhellmann @jdufresne thank you for responding and accepting this so fast!
comment created time in 2 days
PR opened sphinx-contrib/spelling
Reported issue: https://github.com/sphinx-contrib/spelling/issues/96
In 6.0.0, importlib.util.find_spec was introduced as a replacement to imp.find_module.
However, there is a scenario where it can raise ValueError (new behaviour to this codebase):
https://docs.python.org/3/library/importlib.html#importlib.util.find_spec
This PR attempts to handle this scenario.
P.S. I could not find related test to this logic. I'd be happy to write one (and will try now), but I think, I'd need some assistance here. Any pointers?
Best, Rust
pr created time in 2 days
create barnchamureki/spelling
branch : issues/96/find_spec_value_error
created branch time in 2 days
fork amureki/spelling
A spelling checker for Sphinx-based documentation
https://sphinxcontrib-spelling.readthedocs.io/en/latest/
fork in 2 days
issue openedsphinx-contrib/spelling
`importlib.util.find_spec` raises ValueError (it was not a case with `imp.find_module`)
Greetings! Thakns for maintaining this package! ✨
While trying new version 6.0.0, we discovered the next issue:
Exception occurred:
File "/opt/python/3.8.6/lib/python3.8/importlib/util.py", line 114, in find_spec
raise ValueError('{}.__spec__ is None'.format(name))
ValueError: celery.__spec__ is None
I did try to dig a bit and discovered, that new importlib.find_spec raises ValueError in case the spec would be None or is not set.
This behaviour differs from imp.find_module, where it was returning None or raising ImportError.
Seems like we need to update this bit in spelling library to cover new behaviour.
Cheers, Rust
created time in 2 days
push eventamureki/statuscheck
commit sha bef62dfc547d1415f11a99c5c2227f685ce2ff57
Add Python 3.9 support (#230)
push time in 4 days
push eventamureki/statuscheck
commit sha 1f7572f5c67d1e823272432af64854593458d270
Add Python 3.9 support
push time in 4 days
push eventamureki/statuscheck
commit sha e969f642d09cd69965393f0fa10bb4523f518032
Update dependencies (#229) * Update dependencies * Update changelog
push time in 4 days
push eventamureki/statuscheck
commit sha cb46e88c303a9e02650e6d0cf3b51bbd644d879b
Update changelog
push time in 4 days
push eventamureki/statuscheck
commit sha ab0f9b56fe5b36cd945b3d236c876c176c765710
Bump coverage from 5.2.1 to 5.3 (#206) Bumps [coverage](https://github.com/nedbat/coveragepy) from 5.2.1 to 5.3. - [Release notes](https://github.com/nedbat/coveragepy/releases) - [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst) - [Commits](https://github.com/nedbat/coveragepy/compare/coverage-5.2.1...coverage-5.3) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
push time in 4 days
PR merged amureki/statuscheck
Bumps coverage from 5.2.1 to 5.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nedbat/coveragepy/releases">coverage's releases</a>.</em></p> <blockquote> <h2>coverage-5.3</h2> <ul> <li>The <code>source</code> setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new <code>source_pkgs</code> setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes <a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/268">issue 268</a>.</li> <li>If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in <a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/1011">issue 1011</a>. This is now fixed.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst">coverage's changelog</a>.</em></p> <blockquote> <h2>Version 5.3 --- 2020-09-13</h2> <ul> <li> <p>The <code>source</code> setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new <code>source_pkgs</code> setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes <code>issue 268</code>.</p> </li> <li> <p>If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in <code>issue 1011</code>. This is now fixed.</p> </li> </ul> <p>.. _issue 268: <a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/268">nedbat/coveragepy#268</a> .. _issue 1011: <a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/1011">nedbat/coveragepy#1011</a></p> <p>.. _changes_521:</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nedbat/coveragepy/commit/d13594e24f18930e96db55d0b49c3ebdd7275f40"><code>d13594e</code></a> Making a release</li> <li><a href="https://github.com/nedbat/coveragepy/commit/039ef0959c3f21fe0991204c19fb99fab14055f5"><code>039ef09</code></a> If a plugin is disabled, don't try to record its file tracers. <a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/1011">#1011</a></li> <li><a href="https://github.com/nedbat/coveragepy/commit/24eb6fdc8495f969ffeb724f2e96d3941442dd2d"><code>24eb6fd</code></a> Move disable_plugin to Python</li> <li><a href="https://github.com/nedbat/coveragepy/commit/987ceb9300c9326e4932dd69d633e7bd7be04e16"><code>987ceb9</code></a> Fix a missed exception handling for bad plugins</li> <li><a href="https://github.com/nedbat/coveragepy/commit/c907b2ee1184dbcea1a3698588ad198a32fbea71"><code>c907b2e</code></a> ambigious -> ambiguous</li> <li><a href="https://github.com/nedbat/coveragepy/commit/263f3e1da8e5a6a32056a8697286f9adf0f6a55d"><code>263f3e1</code></a> Docs and cleanup for source_pkgs</li> <li><a href="https://github.com/nedbat/coveragepy/commit/ecd6ab19a43a444bc7fc9dfbc08f3ca5274365ca"><code>ecd6ab1</code></a> Create Way to force package even if filepath exists (<a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/1026">#1026</a>)</li> <li><a href="https://github.com/nedbat/coveragepy/commit/39e6d1de90b9574f8eaa266b289a7efc02b2e9e9"><code>39e6d1d</code></a> Thomas Grainger's first commit</li> <li><a href="https://github.com/nedbat/coveragepy/commit/154f5284e124e610d80a0b5c7e3fac9132c891d6"><code>154f528</code></a> replace confusing comment with assertion (<a href="https://github-redirect.dependabot.com/nedbat/coveragepy/issues/1028">#1028</a>)</li> <li><a href="https://github.com/nedbat/coveragepy/commit/c3159081ae67864f75aacc1b86310fe9d8d614cb"><code>c315908</code></a> Explain a mystery</li> <li>Additional commits viewable in <a href="https://github.com/nedbat/coveragepy/compare/coverage-5.2.1...coverage-5.3">compare view</a></li> </ul> </details> <br />
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.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
pr closed time in 4 days
PR closed PostgresApp/PostgresApp
Hey @jakob !
Thank you for maintaining the app, it helps lots of developers! I was wondering if I can get changes from PostgreSQL 12.4 here and was following your example to make this PR.
PostgreSQL 12.4 was released on 2020-08-13. Big migration is not required, everything should work as expected: https://www.postgresql.org/docs/12/release-12-4.html
I am happy to make any further changes if needed, but also can leave it to your hands if you find this appropriate and willing to finish.
Best, Rust
pr closed time in 4 days
pull request commentPostgresApp/PostgresApp
I see you added it in https://github.com/PostgresApp/PostgresApp/commit/5d8335167b14033df9737f3c889922cfdd48eaed therefore I will close this PR. Thanks.
comment created time in 4 days
delete branch amureki/whoisp
delete branch : pyup-update-virtualenv-15.1.0-to-20.0.34
delete time in 6 days
push eventamureki/whoisp
commit sha 3f40550e6894f7b406fc9ec5bc505f2407fc6d6d
Update virtualenv from 15.1.0 to 20.0.35
push time in 6 days
create barnchamureki/whoisp
branch : pyup-update-virtualenv-15.1.0-to-20.0.35
created branch time in 6 days
issue closedThermondo/django-heroku-connect
hc_models.Number.decimal_places attribute not working properly
It seems that the hc_models.Number.decimal_places attribute is ineffective. A few examples:
numberfield = hc_models.Number(sf_field_name='numberfield__c', decimal_places=x, max_digits=x)
if numberfield = 18 and
- decimal_places=0, max_digits=1: numberfield = 20
- decimal_places=0, max_digits=2: numberfield = 18
- decimal_places=0, max_digits=3: numberfield = 18.0
if numberfield = 2.6 and
- decimal_places=0, max_digits=1: numberfield = 3
- decimal_places=0, max_digits=2: numberfield = 2.6
- decimal_places=0, max_digits=3: numberfield = 2.60
closed time in 7 days
Eliagandolfi
issue commentThermondo/django-heroku-connect
hc_models.Number.decimal_places attribute not working properly
Thank you, Johannes, for the clarifications here!
Exactly as you said, Heroku Connect uses double for Number fields:
Number values are stored in Postgres as a double column, which has 15-digit precision. Salesforce values that exceed this limitation will still sync via Heroku Connect, but with reduced precision. This is particularly noticeable with extremely large values.
https://devcenter.heroku.com/articles/heroku-connect-faq#why-does-some-of-my-data-in-postgres-not-match-what-i-wrote-to-salesforce
comment created time in 7 days
push eventThermondo/django-heroku-connect
commit sha 3fefc607534d5da9c1831bd81eecaa7e588a0619
Add TextAreaLong to __all__ along with the other classes (#101) That should fix #89
push time in 7 days
delete branch Thermondo/django-heroku-connect
delete branch : issues/89/textarealong_import
delete time in 7 days
PR merged Thermondo/django-heroku-connect
That should fix #89
pr closed time in 7 days
issue closedThermondo/django-heroku-connect
`hc_models.TextAreaLong` is missing from documentation
We do define TextAreaLong field that is available for use:
https://github.com/Thermondo/django-heroku-connect/blob/3c50924cd839c88112e1cc60530065025ad276fb/heroku_connect/db/models/fields.py#L268
By some reason, it is not documented here: https://django-heroku-connect.readthedocs.io/en/stable/fields.html
closed time in 7 days
amureki
pull request commentThermondo/django-heroku-connect
Add `TextAreaLong` to __all__ along with the other classes
@Ashlett good that you noticed it! I did found a solution to that here: https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154
After applying it disappeared, so we are good now!
comment created time in 7 days
PR opened Thermondo/django-heroku-connect
That should fix #89
pr created time in 8 days
create barnchThermondo/django-heroku-connect
branch : issues/89/textarealong_import
created branch time in 8 days
pull request commentmodel-bakers/model_bakery
[107] Add Instructions and Script To Run `postgis` Tests
Sure, I can also take a look to see how it works on MacOS. And thank you very much @timjklein36 for your contribution!
comment created time in 8 days
push eventmodel-bakers/model_bakery
commit sha de521c7efc01f50c4da03b06f57161d3bfc137ce
Drop retired Python 3.5 (#119) Python 3.5 did reach end-of-life in September 2020: https://www.python.org/downloads/release/python-3510/
push time in 8 days
PR merged model-bakers/model_bakery
Python 3.5 did reach end-of-life in September 2020: https://www.python.org/downloads/release/python-3510/
We can safely remove it from our test environment to reduce test running time.
pr closed time in 8 days
issue closedThermondo/django-heroku-connect
NullBooleanField is deprecated in Django 3.1 for Checkbox field type
I'm getting the following warning from Heroku:
Account.is_deleted: (fields.W903) NullBooleanField is deprecated. Support for it (except in historical migrations) will
be removed in Django 4.0. HINT: Use BooleanField(null=True) instead.
When I looked at the declaration for Checkbox in the source I see:
class Checkbox(HerokuConnectFieldMixin, models.NullBooleanField):
"""Salesforce ``Checkbox`` field."""
pass
Can you folks update the code or do I need to fork it?
closed time in 8 days
monnix
issue commentThermondo/django-heroku-connect
NullBooleanField is deprecated in Django 3.1 for Checkbox field type
Fixed in https://github.com/Thermondo/django-heroku-connect/pull/100 and released as 0.22.0. Thank you for your help @monnix and @codingjoe ! ❤️
comment created time in 8 days
issue closedmodel-bakers/model_bakery
Rename "master" branch to "main"
This topic was a hot one recently and that's great! Given the motivations to our last rename from mommy to bakery, it makes total sense to do the same with the main git branch to not reinforce oppressive language. Links and more information about this:
- Terminology, Power and Oppressive Language;
- Minor HOWTO guide;
- Tweet from Github's CEO endorsing such changes;
Expected behavior
This is just a minor list to make sure everything's right:
- [x] Open PRs should remain open;
- [x] CI should keep on working;
- [x] Read the docs shouldn't break;
closed time in 8 days
berinhard
issue commentmodel-bakers/model_bakery
Rename "master" branch to "main"
Done in https://github.com/model-bakers/model_bakery/pull/114 ❤️
comment created time in 8 days
push eventmodel-bakers/model_bakery
commit sha 6bc62891780cef423aead91ea5a0c1bb290383c6
Replace master branch by main (#114)
commit sha f0f17a70773e2906f0b1a05a40d5023d250bea1e
Model annotation fixes. (#115)
commit sha ed7f807d365d31f6973babd3cc3433aa23ba678e
Drop retired Python 3.5 Python 3.5 did reach end-of-life in September 2020: https://www.python.org/downloads/release/python-3510/
push time in 8 days
PR opened model-bakers/model_bakery
Python 3.5 did reach end-of-life in September 2020: https://www.python.org/downloads/release/python-3510/
pr created time in 8 days
created tagThermondo/django-heroku-connect
Django integration Salesforce using Heroku Connect.
created time in 8 days
push eventThermondo/django-heroku-connect
commit sha 37347e9dcbd586ffbb15f06217822e502d58eb51
Remove models.NullBooleanField as it is deprecated in Django 4.0 (#100) Co-authored-by: Monnix Jelinek <[email protected]>
push time in 8 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.6.3
delete time in 8 days
push eventamureki/whoisp
commit sha 9b4c62bcb21aefa4560d4747b471e786610b2101
Update isort from 4.2.15 to 5.6.4
push time in 8 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.6.4
created branch time in 8 days
delete branch amureki/whoisp
delete branch : pyup-update-virtualenv-15.1.0-to-20.0.33
delete time in 9 days
push eventamureki/whoisp
commit sha e21011b501e85d42c8ae0c1da1e564d476153c2d
Update virtualenv from 15.1.0 to 20.0.34
push time in 9 days
create barnchamureki/whoisp
branch : pyup-update-virtualenv-15.1.0-to-20.0.34
created branch time in 9 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.6.2
delete time in 10 days
push eventamureki/whoisp
commit sha 6690630392019d05a4103b7101ca7e5806e52250
Update isort from 4.2.15 to 5.6.3
push time in 10 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.6.3
created branch time in 10 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.6.1
delete time in 11 days
push eventamureki/whoisp
commit sha dd52044949cc5a4c0ce6b0ca9cf4c4de145ebb1e
Update isort from 4.2.15 to 5.6.2
push time in 11 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.6.2
created branch time in 11 days
push eventamureki/whoisp
commit sha 71e3d0ece40e7ac0c596d4784820c6b6dca64b04
Update tox from 2.7.0 to 3.20.1
push time in 12 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.6.0
delete time in 13 days
push eventamureki/whoisp
commit sha bf603ccbe56f0fffd4c210dcf00586ecabcfdf3e
Update isort from 4.2.15 to 5.6.1
push time in 13 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.6.1
created branch time in 13 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.5.5
delete time in 13 days
push eventamureki/whoisp
commit sha 0e472654b4a060f95766961d13d382a42997940d
Update isort from 4.2.15 to 5.6.0
push time in 13 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.6.0
created branch time in 13 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.5.4
delete time in 13 days
push eventamureki/whoisp
commit sha 328161a1971178eeee90341b8a6e1cdd460b7599
Update isort from 4.2.15 to 5.5.5
push time in 13 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.5.5
created branch time in 13 days
delete branch amureki/whoisp
delete branch : pyup-update-virtualenv-15.1.0-to-20.0.32
delete time in 16 days
push eventamureki/whoisp
commit sha b15c05a4ec4fcb833e3a199f2e7aae9e1d3990f8
Update virtualenv from 15.1.0 to 20.0.33
push time in 16 days
create barnchamureki/whoisp
branch : pyup-update-virtualenv-15.1.0-to-20.0.33
created branch time in 16 days
delete branch amureki/whoisp
delete branch : pyup-update-pytest-3.2.1-to-6.1.0
delete time in 17 days
push eventamureki/whoisp
commit sha 4ddc6eba54f5f543d436513df0562ac025dece22
Update pytest from 3.2.1 to 6.1.1
push time in 17 days
create barnchamureki/whoisp
branch : pyup-update-pytest-3.2.1-to-6.1.1
created branch time in 17 days
delete branch amureki/whoisp
delete branch : pyup-update-flake8-3.4.1-to-3.8.3
delete time in 18 days
push eventamureki/whoisp
commit sha cd6fcc8e8d9ab35eb1e960fe97c41bde1e9db34f
Update flake8 from 3.4.1 to 3.8.4
push time in 18 days
create barnchamureki/whoisp
branch : pyup-update-flake8-3.4.1-to-3.8.4
created branch time in 18 days
push eventamureki/covidapp
commit sha ad9920146e947b0313dd32f34efe91a967068911
Improve naming (#12) Since the chat displays daily new cases instead of increase rates, out should be named accordingly.
push time in 19 days
PR merged amureki/covidapp
Since the chart displays daily new cases instead of increase rates, it should be named accordingly.
pr closed time in 19 days
delete branch amureki/whoisp
delete branch : pyup-update-virtualenv-15.1.0-to-20.0.31
delete time in 19 days
push eventamureki/whoisp
commit sha 8f4bb8b03c4e4d269be508cc8b8ef6a5253575f7
Update virtualenv from 15.1.0 to 20.0.32
push time in 19 days
create barnchamureki/whoisp
branch : pyup-update-virtualenv-15.1.0-to-20.0.32
created branch time in 19 days
delete branch amureki/whoisp
delete branch : pyup-update-isort-4.2.15-to-5.5.3
delete time in 21 days
push eventamureki/whoisp
commit sha 9b41e8c8d6acdbc0a7972d16b43ee65d028f9303
Update isort from 4.2.15 to 5.5.4
push time in 21 days
create barnchamureki/whoisp
branch : pyup-update-isort-4.2.15-to-5.5.4
created branch time in 21 days
delete branch amureki/whoisp
delete branch : pyup-update-pytest-3.2.1-to-6.0.2
delete time in 24 days
push eventamureki/whoisp
commit sha 625427eead7e20768dae1b53fa4d8803ee540474
Update pytest from 3.2.1 to 6.1.0
push time in 24 days
create barnchamureki/whoisp
branch : pyup-update-pytest-3.2.1-to-6.1.0
created branch time in 24 days
delete branch amureki/whoisp
delete branch : pyup-update-cached-property-1.3.0-to-1.5.1
delete time in a month