The better build tool. Finds dependencies automatically for any language.
Runs your actix-web app as a lambda app that will respond to Application Load Balancer requests
Generator for "fail days calendar" for Beeminer
Makes Kindle books from a blog
Befunge interpreter in Clojure(script)
A copy of cgkit that's buildable under debian
Clojure DXF library, based off Stani's Python DXF library
A cd command that learns - easily navigate directories from the command line
A python egg to simplify AMEE API access
Rust-translated version of https://github.com/joshkunz/ashuffle
push eventpalfrey/fenestra
commit sha 29329e22bba27a2a0921a91f5d6fa413d5c94ca3
Add flake8 and fix bad imports
commit sha 68db7084b643f6ec7aed730b1c582e451ae69343
Add "on_change" event
commit sha 7829aa903508a6a194b3d1e9c3add7858b286da9
Refactor plugins into common code
push time in 2 days
push eventpalfrey/serial_test
commit sha 4997bc3d56d150ceb7f48294e5ea9b25901a265a
Include LICENSE file in all sub-crates LICENSE files should be included in all sub-crates to allow tools used to package the crates to figure out the license.
commit sha a1d4c2790835158890b70e1214df52a734685c20
Merge pull request #26 from martinezjavier/license-sub-crates Include LICENSE file in all sub-crates
push time in 6 days
PR merged palfrey/serial_test
LICENSE files should be included in all sub-crates to allow tools used to package the crates to figure out the license.
pr closed time in 6 days
push eventpalfrey/re-frame-10x
commit sha 0b73db55940b39903ff93f8c27e236d10f32232a
Strings in github actions need single quotes
push time in 8 days
push eventpalfrey/re-frame-10x
commit sha 546615fed57862b26a8fd61c985f50f4dd1f7eb7
pull_request not pull-request
push time in 8 days
PR opened day8/re-frame-10x
Fixes https://github.com/day8/re-frame-10x/issues/233
pr created time in 8 days
fork palfrey/re-frame-10x
A debugging dashboard for re-frame. X-ray vision as tooling.
fork in 8 days
push eventpalfrey/maiden
commit sha 343f9ec590d154d53cbb7562e07cd5ceb81a6387
publish: Merge pull request #34 from palfrey/allow-hyphens-as-letters generated from commit 80189999aab6e3d3f3ded9cad2e0f1d88f023bfd
push time in 8 days
push eventpalfrey/maiden
commit sha bf44dfdc770df9245692529f1d1e8afc53f672c2
Allow hyphens as digits
commit sha 80189999aab6e3d3f3ded9cad2e0f1d88f023bfd
Merge pull request #34 from palfrey/allow-hyphens-as-letters Allow hyphens as digits
push time in 8 days
issue closedpalfrey/maiden
Hyphens are not counted as letters
The parser at https://palfrey.github.io/maiden/ skips hyphens in the count of letters in literals.
For example, Belle was a be-our-guest intellectual generates Assignment { target: Variable("Belle"), value: Floating(102.0) }. The literal be-our-guest contains ten letters and two hyphens for a total of twelve, so the value should be 122.0 instead.
https://github.com/RockstarLang/rockstar/blob/master/spec.md says "The hyphen (-) is counted as a letter – so you can use terms like 'all-consuming' (13 letters > 3) and 'power-hungry' (12 letters > 2) instead of having to think of 12- and 13-letter words."
closed time in 8 days
bskendig
push eventpalfrey/maiden
commit sha dcde8d7717a301df4d5719745cd3b30f61c093cc
publish: Use matches macro generated from commit 98106ce407ef933353d8990e688ebe600633eab6
push time in 8 days
push eventpalfrey/maiden
commit sha 98106ce407ef933353d8990e688ebe600633eab6
Use matches macro
push time in 8 days
issue commentpalfrey/maiden
Hyphens are not counted as letters
Agreed. So the upstream change was https://github.com/RockstarLang/rockstar/pull/234 and unfortunately (see #33 for fixing this) our PEG file is manually derived from upstream's one so I'll need to fix that by hand.
comment created time in 8 days
issue openedpalfrey/maiden
Automatically derive PEG format from upstream
Maiden's PEG file is at https://github.com/palfrey/maiden/blob/main/src/rockstar.peg and the upstream one is at https://github.com/RockstarLang/rockstar/blob/master/satriani/rockstar.peg, but because PEG.js and pest disagree on formatting, they're not directly compatible. It should however be possible to automatically convert from one to the other. So far, they were converted by hand and have since been manually updated.
created time in 8 days
push eventpalfrey/fenestra
commit sha b1862a4258a5aea922a6cc40d754760893a9325e
Cope with DISPLAY not being available yet
commit sha b96fdba033802fe0829a1ec25c6dd8397c79d358
Remember to start supervisor if not already started
push time in 9 days
issue openedflz/iaqualink-py
Failure to cleanup session if the login fails
Because of the definition of the with statement (https://docs.python.org/3/reference/compound_stmts.html#the-with-statement) if the login throws an AqualinkLoginException then the __aexit__ routine never gets called and so the session never gets cleaned up.
created time in 9 days
delete branch palfrey/core
delete branch : exception-handler-without-exception
delete time in 10 days
push eventpalfrey/xboxone-home-assistant
commit sha ab657f75a83f2e481c4fe45de31a5931651ff8c2
Update README.md
commit sha 3c288f40bb56a844806f1166742ccc6670e0d91a
Format
commit sha c8a7861be71af60428fcca8bdbc2ecc1816ccf5e
Merge pull request #29 from KTibow/master Format
commit sha 3eeac4d6a38d9bd4d467822a82249b76c9d3801c
Add GitHub Actions
commit sha c765b6b97399133b84646e09c1e723f45a7e6278
Merge pull request #30 from KTibow/patch-1 Add GitHub Actions
commit sha cc078f91250c8bc0897c16297169d4ad09450db1
Reformat media_player.py
commit sha b8a2983c1a5fabc813d730e7488a5de0b3c873be
Merge branch 'master' into async
push time in 11 days
push eventpalfrey/core
commit sha ceef65c715bd7e185694edf5a792b94a53c6d691
Ignore unclosed client sessions from iaqualink tests
push time in 11 days
Pull request review commenthome-assistant/core
Don't try and store exceptions when the key is missing
def hass(loop, hass_storage, request): def exc_handle(loop, context): """Handle exceptions by rethrowing them, which will fail the test."""- exceptions.append(context["exception"])+ # Most of these contexts will contain an exception, but not all.+ # The docs note the key as "optional"+ # See https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.call_exception_handler+ if "exception" in context:
The spec says we should always have the message field, so I've added a new Exception with that in instead
comment created time in 11 days
push eventpalfrey/core
commit sha 49d05267854796ec56a74fadd04360ef5018fcc9
Add exception with message if no Exception
push time in 11 days
push eventpalfrey/core
commit sha 40b25e9f63a02e2792e67ec78810f5c5fd28ac5b
Fix linter issues
push time in 12 days
PR opened home-assistant/core
Proposed change
Fixes #41356 by throwing an error on attempts to load secrets from within the secrets file
Type of change
<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
Example entry for configuration.yaml:
<!-- Supplying a configuration snippet, makes it easier for a maintainer to test your PR. Furthermore, for new integrations, it gives an impression of how the configuration would look like. Note: Remove this section if this PR does not have an example entry. -->
configuration.yaml
http:
ssl_key: !secret a
secrets.yaml
a: 1
b: !secret a
Additional information
<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->
- This PR fixes or closes issue: fixes #41356
- This PR is related to issue:
- Link to documentation pull request:
Checklist
<!--
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. Your PR cannot be merged unless tests pass
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (
black --fast homeassistant tests) - [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - [ ] New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - [ ] Untested files have been added to
.coveragerc.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!-- This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet been reviewed.
Thanks for helping out! -->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other open pull requests in this repository.
<!-- Thank you for contributing <3
Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io
pr created time in 12 days
issue commenthome-assistant/core
Does any of https://blog.hqcodeshop.fi/archives/482-OpenSSH-8.3-client-fails-with-load-pubkey-invalid-format.html and https://blog.hqcodeshop.fi/archives/487-OpenSSH-8.3-client-fails-with-load-pubkey-invalid-format-Part-2.html help to explain/fix things?
comment created time in 12 days
push eventpalfrey/core
commit sha 093e5889c5a127f4c01d5d00fb3b082bd7cd2a4a
Disable linting of the imports outside of toplevel
push time in 13 days
PR opened home-assistant/core
<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->
Proposed change
Periodically (e.g. https://github.com/home-assistant/core/runs/1250003930) we get the following error:
2020-10-13T21:10:58.1834937Z --- Logging error ---
2020-10-13T21:10:58.1835344Z Traceback (most recent call last):
2020-10-13T21:10:58.1837143Z File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1744, in call_exception_handler
2020-10-13T21:10:58.1837737Z self._exception_handler(self, context)
2020-10-13T21:10:58.1838530Z File "/__w/core/core/tests/conftest.py", line 112, in exc_handle
2020-10-13T21:10:58.1839059Z exceptions.append(context["exception"])
2020-10-13T21:10:58.1839731Z KeyError: 'exception'
This fixes that, by not trying to store exceptions that don't exist
Type of change
<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
Example entry for configuration.yaml:
<!-- Supplying a configuration snippet, makes it easier for a maintainer to test your PR. Furthermore, for new integrations, it gives an impression of how the configuration would look like. Note: Remove this section if this PR does not have an example entry. -->
# Example configuration.yaml
Additional information
<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
Checklist
<!--
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. Your PR cannot be merged unless tests pass
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (
black --fast homeassistant tests) - [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running:python3 -m script.hassfest. - [ ] New or updated dependencies have been added to
requirements_all.txt.
Updated by runningpython3 -m script.gen_requirements_all. - [ ] Untested files have been added to
.coveragerc.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!-- This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet been reviewed.
Thanks for helping out! -->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other open pull requests in this repository.
<!-- Thank you for contributing <3
Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io
pr created time in 13 days
create barnchpalfrey/core
branch : exception-handler-without-exception
created branch time in 13 days
PR opened home-assistant/core
Proposed change
Correct circular imports of config_validation. Without this fix the following occurs:
>>> from homeassistant.components.http import HomeAssistantView
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/palfrey/src/home-assistant-core/homeassistant/components/http/__init__.py", line 20, in <module>
from homeassistant.helpers import storage
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/storage.py", line 10, in <module>
from homeassistant.helpers.event import async_call_later
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/event.py", line 47, in <module>
from homeassistant.helpers.template import RenderInfo, Template, result_as_boolean
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/template.py", line 35, in <module>
from homeassistant.helpers import config_validation as cv, location as loc_helper
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/config_validation.py", line 519, in <module>
def template(value: Optional[Any]) -> template_helper.Template:
AttributeError: partially initialized module 'homeassistant.helpers.template' has no attribute 'Template' (most likely due to a circular import)
So you fix the config_validation.py error, and then get the following in location.py
>>> from homeassistant.components.http import HomeAssistantView
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/palfrey/src/home-assistant-core/homeassistant/components/http/__init__.py", line 20, in <module>
from homeassistant.helpers import storage
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/storage.py", line 10, in <module>
from homeassistant.helpers.event import async_call_later
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/event.py", line 47, in <module>
from homeassistant.helpers.template import RenderInfo, Template, result_as_boolean
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/template.py", line 35, in <module>
from homeassistant.helpers import location as loc_helper
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/location.py", line 10, in <module>
import homeassistant.helpers.config_validation as cv
File "/home/palfrey/src/home-assistant-core/homeassistant/helpers/config_validation.py", line 519, in <module>
def template(value: Optional[Any]) -> template_helper.Template:
AttributeError: partially initialized module 'homeassistant.helpers.template' has no attribute 'Template' (most likely due to a circular import)
```
After this fix:
```
>>> from homeassistant.components.http import HomeAssistantView
>>>
```
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
pr created time in 13 days
push eventpalfrey/core
commit sha 68433b09383071c53fa5d3ba9321c8f34f4252fb
Fix circular import of config_validation and template
push time in 13 days
fork palfrey/core
:house_with_garden: Open source home automation that puts local control and privacy first
fork in 13 days
issue commenttypeddjango/django-stubs
Projects with no models.py suddenly seem to have missing related fields
I can't provide code directly as it's a private project, but the other errors were all things like mypy complaining that class X didn't have field Y, when field Y exists because class Z has a ForeignKey referencing class X. Even when I imported class Z into the file where the error was, it didn't go away.
comment created time in 13 days
issue openedtypeddjango/django-stubs
Projects with no models.py suddenly seem to have missing related fields
Bug report
What's wrong
I've got a project where we've just moved over from having a models.py to splitting out all of the models and their related views, etc into feature-specific files. The project was getting 0 errors from mypy before this, but then suddenly had issues like a model using the default primary key having errors like has no attribute "id" and others now missing various related fields.
Notably, the project still works absolutely fine and all the fields, etc are present in the running system.
I've managed to hack around this by making a models.py that imports all the submodules, but I was surprised about this.
How is that should be
I shouldn't have needed the hack. Or the Django stubs should have complained about this, as it took me most of a day to work out what the problem was...
System information
- OS:
pythonversion: 3.7.7djangoversion: 3.0.7mypyversion: 0.782django-stubsversion: 1.6.0
created time in 13 days
push eventpalfrey/urlgrab
commit sha e29ca16c05fe68bd52a9c0f0cbf2ad8b6c721348
Change requests type on encodings
push time in 14 days
push eventpalfrey/awesome-rust-actions
commit sha 4dc72076d9bd905a854a436b91cf4c8a8809da50
Increase git checkout depth to stop lint age issues
push time in 15 days
PR opened max/awesome-lint
Previously the README mentioned the author, but didn't link to the actual tool.
pr created time in 15 days
PR opened actions-rs/awesome-rust-actions
pr created time in 15 days
create barnchpalfrey/awesome-rust-actions
branch : disable-awesome-badge-lint
created branch time in 15 days
fork palfrey/awesome-rust-actions
Curated list of awesome Actions for Rust programming language
fork in 15 days
startedactions-rs/awesome-rust-actions
started time in 15 days
push eventpalfrey/fenestra
commit sha df75f073d0e775936cf6c65f518a787f06bddceb
Re-run on wakeup
push time in 16 days
push eventpalfrey/axiom
commit sha 1713a95652c5c4c9d8e86362e34abcb56058285e
Create dependabot.yml
commit sha 2c5460884600e0d0a459caa418c46665cb59df43
Bump actions/setup-python from v1 to v2.1.2 Bumps [actions/setup-python](https://github.com/actions/setup-python) from v1 to v2.1.2. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](https://github.com/actions/setup-python/compare/v1...24156c231c5e9d581bde27d0cdbb72715060ea51) Signed-off-by: dependabot[bot] <[email protected]>
commit sha 3821b846b131c9e255f0d3997aabfa2b8f877a37
Merge pull request #134 from twisted/dependabot/github_actions/actions/setup-python-v2.1.2 Bump actions/setup-python from v1 to v2.1.2
commit sha e90fd39fc193f4e045d4c85c8144bcffa7741cad
Wait for all builds
commit sha e03cbe700347bcc5e399e2bb44cd2a89952a7fd5
Merge branch 'master' into mithrandi-patch-1
commit sha 17417abf9b8d5077cb7caf206a6789d7d2a03549
Merge pull request #135 from twisted/mithrandi-patch-1 Wait for all builds
commit sha a7973732869fc74717bfaab21976b4847cf2c5de
Bump actions/setup-python from v2.1.2 to v2.1.3 Bumps [actions/setup-python](https://github.com/actions/setup-python) from v2.1.2 to v2.1.3. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](https://github.com/actions/setup-python/compare/v2.1.2...c181ffa198a1248f902bc2f7965d2f9a36c2d7f6) Signed-off-by: dependabot[bot] <[email protected]>
commit sha aeb29fb6178930314329d86c277cd6e70696bc5c
Merge pull request #136 from twisted/dependabot/github_actions/actions/setup-python-v2.1.3 Bump actions/setup-python from v2.1.2 to v2.1.3
commit sha e8c205809ea1f05de2a65426d796473c2ca1161e
Merge branch 'master' into python3
commit sha 16bae219288e8a2117be0f873bfcd1d6ea1da92b
More text comparison fixes
push time in 16 days
push eventpalfrey/fenestra
commit sha 80060eed2167b02531f665f5e1286f58a94063c7
Use randrctl 1.9.0 from pypi
push time in 16 days
issue commentrust-unofficial/awesome-rust
* Quality of projects to link to: i am all for quality over quantity. This is a quite subjective and difficult topic. Especially when it comes to inactive but important projects. Not sure whether an objective measure like stars really can reflect this.
My thinking on stars is that they're inaccurate at the high end, but useful at the low end. To give an example: if Project A has 1000 stars and Project B has 2000 stars, all we can really say is that both projects are popular and Project B has more people that have starred it, but would be hard to say definitively which one is more popular. OTOH, vs. Project C with 2 stars, we can say that both A and B are more popular. I think if we said something like 50 stars, or 1000 downloads on crates.io as a initial value and dug through and found the list of our current projects that would be removed and see if there's anything obviously great that wouldn't get there, and then look at those thresholds and see if we either need to tweak them or find extra ones.
* Quality control: i've always felt that a cleanup script is necessary to enforce a common style (to fix ordering, whitespace, dashes etc.).
To be able to do both of these easily mechanically, I'm currently leaning towards the JSON data file plus generation code to make the actual README.
To be honest, i don't plan to invest much time in this project anymore. Maybe it's time to look for maintainers again or leave awesome-rust at it is?
I think we could really badly do with more maintainers if you've got any ways of finding them. The project still has potential, but it needs this sort of level of overhaul to get it to a better place. It would be kinda ok as-is, but I think it could be better. I need some time away for a while, but I think if there's other maintainers around I could come back at some point.
comment created time in 16 days
push eventrust-unofficial/awesome-rust
commit sha b49400cd8b2e2cee106f37749426d7c9ed73341c
Kill all the HTML images in favour of Markdown
push time in 17 days
PR closed rust-unofficial/awesome-rust
Added Arcane Fortune in the games section
pr closed time in 17 days
pull request commentrust-unofficial/awesome-rust
I'm seeing build instructions (with a few issues...), but it's still not exactly a great repo, and I'd still say the licensing issue is thoroughly a problem. I'm closing this for the moment, but feel free to reopen if it improves.
comment created time in 17 days
PR closed rust-unofficial/awesome-rust
As noted in issue #931, minifib would be a nice addition to the GUI section.
pr closed time in 17 days
pull request commentrust-unofficial/awesome-rust
Open for over a week, and still has the issues mentioned. Closing until they're resolved.
comment created time in 17 days
PR closed rust-unofficial/awesome-rust
pr closed time in 17 days
pull request commentrust-unofficial/awesome-rust
Open for over a week, and still has the issues mentioned. Closing until they're resolved.
comment created time in 17 days
issue openedrust-unofficial/awesome-rust
This is to some extent a continuation of #479, but also some other items. I'm interested in particular in @luciusmagn and @kud1ing's thoughts, but others are also welcomed
So, I'm feeling a bit burnout on this project, and as such will be switching off notifications on new PRs and won't be reviewing them for at least a bit. A lot of my issues come down to the following problems:
- Quality of repos: we don't really have any. It's called "Awesome Rust", and TBH our quality control (for which I'm as guilty as any) is not great. This results in a really long list, which is nice in certain ways, but I'm wondering if quality rather than quantity would be a better idea. I'm leaning towards more mechanical options of quality (e.g. Github stars or crates.io downloads), mainly to try and a) provide a consistent process and b) avoid the maintainers here being the judges of such matter, and using existing community metrics instead. If we do that, the thresholds should be clearly and publicly documented. There will always be popular projects that don't fit into any of the metrics, and in those cases we first need to find a new metric.
- Quality of list items: Our formatting is a bit of a mess. There's kinda a style, but it's not enforced, and there's kinda alphabetical ordering, but also not enforced. I think we need to have a fixed style, and enforce it. Main goal here is to reduce maintainer time i.e. make it easy to do the right route, so this should be an automatic thing. Probably a CI check. Maybe fits in with the JSON data concepts that were being floated in #479.
- Time spent on PRs: We need something like the Github pull request templates plus saved replies. The template should have a bunch of common issues to tick off, and there should be an expectation that if you open a PR and you've ignored one or more of those, it's getting closed pretty damn quick. It's somewhat of a jerk move, but from a "maintainer time" perspective, it's a win, and I think needed.
Thoughts anyone?
created time in 17 days
push eventrust-unofficial/awesome-rust
commit sha 6acde2174ce17de471fb453233d4ec3a654f26ee
Add NATS client to the Network Programming section The `nats` crate is the offical [NATS](https://en.wikipedia.org/wiki/Cloud_Native_Computing_Foundation#NATS) client.
commit sha f8431c8f345ffaa966160e9eac94df30a10ca4ee
Add CI badge for the NATS client
commit sha cc639b7273a256f9deab4b44e21974087b115ffe
Update README.md
commit sha 1eeb4901e81e328eda09492b44800d6341034621
Update README.md
commit sha 4a193a3253f0519fc95026a5a395053b99410489
Merge branch 'master' into patch-1
commit sha baf15c3fb5fad753087b06b13406e632d37e2f4a
Update README.md
commit sha 7001e25e03aabbfce7408dd4e062700990c1ccc0
Merge pull request #970 from stjepang/patch-1 Add NATS client to the Network Programming section
push time in 18 days
PR merged rust-unofficial/awesome-rust
The nats crate is the official client for the NATS messaging system.
https://nats.io
pr closed time in 18 days
push eventrust-unofficial/awesome-rust
commit sha c43a44f2f17f44da13b6fcc4c9d8e98ec9c0065c
add sccache, must have it here
commit sha faa4c62b66a5b2d1fe6fe40bf83fc0468358e9ce
Merge pull request #980 from TriplEight/patch-1 add sccache, must have it here
push time in 19 days
push eventpalfrey/fenestra
commit sha a2e2669c5889f094f2c0252a9d503a461ae562ae
Fix broken dropbox setup
commit sha 1819eea6459946767c142357c695c8ed494ddd5b
Expand out udiskie parameters
push time in 20 days
push eventpalfrey/fenestra
commit sha f15dbb88c78a47591b5dbf99bb39987394f1aba7
Cope with gitattributes
commit sha 5b64ffbd868eb8755ecbe495b86ae5b94b4e552d
Don't worry about supervisor output
commit sha 83885f425d57b017534b800a47a09623f679f3ad
Get diff before writing config
commit sha f153851a497fb024b32f573efed032b6a25efd69
Build our own systemd script
push time in 20 days
push eventpalfrey/serial_test
commit sha 7e059dcbcebe8dbe543dac4ca583dc1e6abed2dd
Upgrade all the dependencies
push time in 20 days
push eventpalfrey/serial_test
commit sha a43adf7f85955bc418c25c055daa100a0f94681a
Allow compiling against parking_lot 0.11
commit sha d69226e9e61226e6e790c0de3c9ba935e32559eb
Merge pull request #25 from palfrey/parking-lot-0.11 Allow compiling against parking_lot 0.11
push time in 20 days
issue closedpalfrey/serial_test
I'm trying to minimize duplicate dependencies, and parking_lot 0.10 (serial_test) vs 0.11 (others) is one of them
closed time in 20 days
dvtomas
push eventpalfrey/potboiler
commit sha 6f8a60900ca9c9478da583a3ae64513f7daedc8f
Fix extra import clippy issues
push time in 21 days
push eventpalfrey/fenestra
commit sha 7c85b9a4fe901a352bdc67ed8ad98b54507e7944
Fix attributes
push time in 21 days
push eventpalfrey/fenestra
commit sha 16bbd4d65653720abe1e6d5315e57b828b369abb
Move gitattributes to polybar
push time in 21 days
push eventpalfrey/fenestra
commit sha eed0d14dd33acbc93af3439f3961c48224f2be97
Mark jinja files as ini
push time in 21 days
push eventpalfrey/fenestra
commit sha 747b5e8b8d9b5dd15dd87b3f859673c9c5162cb5
Add README
push time in 21 days
created repositorypalfrey/fenestra
Tooling for setting up various desktop config
created time in 21 days
issue openededio/randrctl
https://pypi.org/project/randrctl/ still has 1.8.2
created time in 21 days
push eventrust-unofficial/awesome-rust
commit sha f2d8416d7e4826f89dd12d159c46fb24f0d0171f
Add Rust GraphQL example repo
commit sha ae60d6b9a8999be80587d045be5c99716dcc579a
Add CI badge
commit sha dce80b44a18c19233afacaae41dabe457d7110a1
Update badge
commit sha 89999b6c52a6f3e58aa933456c16aad1174f3985
Merge branch 'master' into patch-1
commit sha a9f1f767bc08e28863dcf850622d138e06e3c785
Merge pull request #979 from ronanyeah/patch-1 Add Rust GraphQL example repo
push time in 22 days
Pull request review commentrust-unofficial/awesome-rust
See also [A comparison of operating systems written in Rust](https://github.com/ * [svenstaro/miniserve](https://github.com/svenstaro/miniserve) — A small, self-contained cross-platform CLI tool that allows you to just grab the binary and serve some file(s) via HTTP [<img src="https://github.com/svenstaro/miniserve/workflows/CI/badge.svg?branch=master">](https://github.com/svenstaro/miniserve/actions) * [TheWaWaR/simple-http-server](https://github.com/TheWaWaR/simple-http-server) — simple static http server * [wyhaya/see](https://github.com/wyhaya/see) — Static HTTP file server [](https://travis-ci.org/wyhaya/see)+* [ronanyeah/rust-hasura](https://github.com/ronanyeah/rust-hasura) — A demonstration of how a Rust GraphQL server can be used as a remote schema with [Hasura](https://hasura.io/) 
Please add the branch name to the build badge image as per https://github.com/rust-unofficial/awesome-rust/blob/master/CONTRIBUTING.md
comment created time in 22 days
push eventrust-unofficial/awesome-rust
commit sha 52b44c436ca0de4a5d25e36e9f69377fed67201a
Add Druid to Librairies/GUI Druid ( https://linebender.org/druid/ ) is a data-first Rust-native UI toolkit.
commit sha af271db01d5f819c756d9d731ccc2be68c7954fa
Add CI badge to Druid
commit sha be96d4d9f94edfb5c38b3b7d9c96f8793c9c1787
Fix Druid CI badge
commit sha 7dabcea03f3d681807f673661c79d2817bbc210f
Change Druid CI badge URL Point Druid CI badge to the "Actions" section of the repo
commit sha 90e383ec626b0b87f7531e5ab6dc6662c5e5830c
Merge pull request #978 from VJean/patch-1 Add Druid to Librairies/GUI
push time in 22 days
PR merged rust-unofficial/awesome-rust
Druid ( https://linebender.org/druid/ ) is a data-first Rust-native UI toolkit.
pr closed time in 22 days