> On Oct 24, 2024, at 2:33 PM, Jarodney Marcus wrote:
>
> No. It comes in handy at the time of need
Cool. I’m glad to hear that, since this has never been expressed, as far as I
know. Can you give an example of when/where it is helpful?
>
> On Thu, Oct 24, 2024, 10:06 AM sebb wrote:
>
>
First time hear of the helpwanted.a.o.
We do not need to develop anything for projects that are on GitHub
Github has long-time standard "good-first-issue" label, that is not only
standard but also they are automatically listed when you go to
github.com/apache/airflow/contribute for example - it's
[
https://issues.apache.org/jira/browse/COMDEV-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-547.
-
Resolution: Fixed
> Reporter appears to be down with 503 Service Unavailable
> --
[
https://issues.apache.org/jira/browse/COMDEV-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892639#comment-17892639
]
Sebb commented on COMDEV-547:
-
Reporter now seems to survive a reboot.
> Reporter appears to
> On Oct 24, 2024, at 3:52 PM, Jarek Potiuk wrote:
>
> First time hear of the helpwanted.a.o.
>
> We do not need to develop anything for projects that are on GitHub
FWIW, the original vision of HelpWanted was pretty specifically not about code.
It was about identifying non-code needs of proj
[
https://issues.apache.org/jira/browse/COMDEV-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892622#comment-17892622
]
Sebb commented on COMDEV-547:
-
The problem was that the gunicorn server for reporter was not
Oh that's an interesting idea that I have not realized so far.
We might actually want to use "good first issue" for other contributions -
the "issues" in GitHub are not necessarily connected with code - they
mostly are of course, and we used them as such, but - especially with the
"projects" featu
No. It comes in handy at the time of need
On Thu, Oct 24, 2024, 10:06 AM sebb wrote:
> The helpwanted.a.o service uses ElasticSearch (ES).
> However, the current version is rather old.
> This was causing issues with Puppet server deployment.
>
> As a temporary measure, the Puppet script not long
To list help wanted issues on our repository, try:
https://github.com/search?q=org:apache+label:%22help+wanted%22&type=issues
https://github.com/search?q=org:apache+label:%22help+wanted%22&type=pullrequests
https://github.com/search?q=org:apache+label:%22help+wanted%22&type=discussions
There are
One may think of iterating all the issues with GitHub REST/GraphQL API
and filter them when label. It MAY be possible for GraphQL but NEVER
for REST API since it have to iterate almost all the (open) issues and
we'd quickly exceed any rate limit (as we have over 2000 repos and
many many issues ...)
Sebb created COMDEV-548:
---
Summary: Reporter does not handle errors well
Key: COMDEV-548
URL: https://issues.apache.org/jira/browse/COMDEV-548
Project: Community Development
Issue Type: Bug
Co
[
https://issues.apache.org/jira/browse/COMDEV-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb reopened COMDEV-547:
-
The system was rebooted, and the problem has recurred.
Looks like there may be an issue contacting kibble?
> Report
> On Oct 24, 2024, at 10:04 AM, sebb wrote:
>
> The helpwanted.a.o service uses ElasticSearch (ES).
> However, the current version is rather old.
> This was causing issues with Puppet server deployment.
>
<…>
> ** So is there any point in keeping the system running, or should it
> be shut down
The helpwanted.a.o service uses ElasticSearch (ES).
However, the current version is rather old.
This was causing issues with Puppet server deployment.
As a temporary measure, the Puppet script not longer tries to set up ES.
This does not affect the service for now, but when(*) it becomes
necessar
[
https://issues.apache.org/jira/browse/COMDEV-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Curcuru closed COMDEV-298.
Resolution: Abandoned
snoot dot io no longer used.
> Accessing Snoot project stats for Samza
> ---
15 matches
Mail list logo
