text:
PLNSRVCE-658: switch from per user ns cfgmap to userconfig crd

this completes the move off of configmap based configuration that @stuartwdouglas and I previously agreed upon
I've done this as a separate PR from https://github.com/redhat-appstudio/jvm-build-service/pull/236, but have included the commits from that PR.  I separated it in case we can merge #236 soon (there is only 1 discussion thread I think that needs resolution before we merge that), but discussion around this change pushes its merge further out.
The new from from that PR are all in the single commit 64305f5cdbefd92e01f635b81139fb2aff62b161
so any review can just focus on the changes in that commit for review.
In addition to porting initialization from one type to the other, I added validation around the presence of the registry secret (there was a TODO comment saying we should do that).
Local testing has looked OK (though I had to do some machinations around dev images tags so as to not interfere with infra team's debug of our kcp issues around creating deployments, and as such, I did not do full end to end testing).

either a maven central hiccup or a need to rebase recent java changes:
[ERROR] Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.18.0:format (default) on project hacbs-repository-parent: Execution default of goal net.revelc.code.formatter:formatter-maven-plugin:2.18.0:format failed: Plugin net.revelc.code.formatter:formatter-maven-plugin:2.18.0 or one of its dependencies could not be resolved: Could not transfer artifact com.github.hazendaz.jsoup:jsoup:jar:1.15.1 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/com/github/hazendaz/jsoup/jsoup/1.15.1/jsoup-1.15.1.jar: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/146.75.36.215] failed: Connection timed out -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
error: build error: error building at STEP "RUN cd java-components && mvn clean package -DskipTests": error while running runtime: exit status 1

will rebase in a bit

/test jvm-build-service-in-repo-e2e

repo: redhat-appstudio/jvm-build-service


text:
Use multiple threads for maven-metadata.xml

Otherwise generating this file can be quite slow the first time it is accessed.
The HTTP connections were also not being closed, which was probably the root cause of the resource leak.

/hold
Failure is related

/test jvm-build-service-in-repo-apicurio-e2e

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Support for custom SSL certificates

Support for custom SSL certificates

LGTM thanks!

repo: redhat-cop/quay-operator


text:
Fix #922 Fuse Tooling appears as 'Selected to download' on conf page

Use 'No download required' for components with size equals undefined
or 0.

Codecov Report

Merging #925 into master will decrease coverage by 0.26%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #925      +/-   ##
==========================================
- Coverage    95.4%   95.13%   -0.27%
==========================================
  Files          39       39
  Lines        3439     3620     +181
  Branches      292      527     +235
==========================================
+ Hits         3281     3444     +163
- Misses        158      165       +7
- Partials        0       11      +11

Impacted Files
Coverage Δ

browser/model/installable-item.js
96.32% <66.66%> (-1.42%)
:arrow_down:

browser/services/credentialManager.js
96.87% <0%> (-3.13%)
:arrow_down:

browser/pages/location/controller.js
92.3% <0%> (-2.86%)
:arrow_down:

browser/pages/install/controller.js
78.84% <0%> (-2.75%)
:arrow_down:

browser/main.js
98.48% <0%> (-1.52%)
:arrow_down:

browser/model/devstudio.js
96.8% <0%> (-0.97%)
:arrow_down:

browser/model/cdk.js
99.21% <0%> (-0.79%)
:arrow_down:

browser/model/helpers/downloader.js
95.27% <0%> (-0.63%)
:arrow_down:

browser/services/data.js
97.06% <0%> (-0.59%)
:arrow_down:

... and 26 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update accac1f...4a1a827. Read the comment docs.

authors: codecov-io dgolovin

license_source: bigquery


text:
adding proposal for dockerfile components

What does this PR do?

Initial draft for improving port detection logic for cases where the dockerfiles are not found in a component.
Which issue(s) does this PR fix

fixes https://github.com/redhat-developer/alizer/issues/244
PR acceptance criteria
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

[x] Unit/Functional tests

[x] Documentation

How to test changes / Special notes to the reviewer

PR moved to https://github.com/devfile/alizer/pull/3

repo: redhat-developer/alizer


text:
No simple way to get kafka url

I have created kafka. Now what I want is just bootstrap URL... but both list and status do not return it. This is the most important data but we cannot get that in simpler way. We need to rethink flow for this somehow

Can we close this? rhoas status returns bootstrap URL, as does describe.

source: gharchive/issue

authors: craicoverflow wtrocki

repo: redhat-developer/app-services-cli


text:
refactor(kafka acl): smarter error handlings

Iterate through all flag options to show every missing flag instead of the immediately missing flag option.

Closes #1229
Verification Steps
Verification needs different flag combinations to be tried out for the commands:

rhoas kafka acl create
rhoas kafka acl delete
rhoas kafka acl grant-access

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[ ] Other (please specify)

Checklist

[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Nothing is broken, maybe this is a refactor or feat?

Nothing is broken, maybe this is a refactor or feat?

Sticking to former.

Left feedback for consideration.

I see you pushed recently so not sure if it is ready for review yet. When it is you can re-request my review and I will look at it again :)

I see you pushed recently so not sure if it is ready for review yet. When it is you can re-request my review and I will look at it again :)

Will be pushing more changes before requesting again :)

I don't think we should use arrow icons as the bullet points personally as they don't give any additional visual usability enhancements, they might even be considered distracting.
I also think that the bulleted listed should have a different indentation to the main message for readability.
Lastly, the Run the command in verbose mode.. message should not be attached to the last bullet point because it is a general message.

$ rhoas kafka acl grant-access
❌ Invalid flag combination:
	 * no operation specified: must provide at least one of "--producer" or "--consumer" flag
	 * principal is missing, provide one of "--user", "--service-account" or "--all-accounts" flags
	 * "--topic" or "--topic-prefix" flag is required for consumer and producer operations
	 * "--group" or "--group-prefix" flag is required for consumer operation.

Run the command in verbose mode using the -v flag to see more information

I think arrow points for bullets look bit better than not using icons. wdyt @craicoverflow ? I tried with other icons, this seems to be the only fit.

I think arrow points for bullets look bit better than not using icons. wdyt @craicoverflow ? I tried with other icons, this seems to be the only fit.

Did you try asterisks? Asterisks are pretty much universally understood as bullet points, unicode icons are not. Icons are great but should be used sparingly to complement main content in my opinion, not to replace it.

While asterisks look okay, do you think numbers might be a better idea?

While asterisks look okay, do you think numbers might be a better idea?

Numbers actually imply that the order matters and 1 must be fixed before 2 etc, and so on (this I was told my the docs team and it makes sense). While i can see that the order listed above is more or less the order that matters, a user should be able to pass --all-accounts first if they wish (for example)

https://www.alt-codes.net/bullet_alt_codes.php
There are special unicode characters for bullet points also.

https://www.alt-codes.net/bullet_alt_codes.php
There are special unicode characters for bullet points also.

Sticking to asterisk.

[Probably should fix this] This is not formatted correctly yet (the sentence should not begin with a random full-stop):

The formatting comes from the rootError. Is it possible to distinguish between single line and multiline error messages?
If no, maybe we should display the verbose hint in a newline always.

The formatting comes from the rootError. Is it possible to distinguish between single line and multiline error messages?

Possible, yes technically but we don't want to go there as it would not be simple.

If no, maybe we should display the verbose hint in a newline always.

Yeah that would work.

Added check for multi lined error by looking up for "\n"


text:
fix: revert service accounts integration

Revert changes introduced in #1716.

@rkpattnaik780 We are looking to release connectors. Service accounts integration should stay on the feature branch as we would need to give more heads up to people as this will introduce some breaking changes.


text:
Add controller to enable metrics/alerts for argocd instances

Adds a new controller to watch for the creation of ArgoCD instances and to add the configuration to enable the built-in metrics stack to scrape metrics from the new ArgoCD.  Also adds an alert rule to report ArgoCD applications that are out of sync.
How to test by running the operator locally
Login to an openshift cluster from the command line
Download the operator-sdk binary from here: https://github.com/operator-framework/operator-sdk/releases/tag/v0.17.2
Check out the argocd-metrics branch from https://github.com/jopit/gitops-operator
cd gitops-operator
go mod vendor
kubectl apply -f deploy/crds
operator-sdk run --local --watch-namespace ""
Create a new argocd application in the openshift-gitops namespace with auto-sync turned off, do not sync the app.  It may take several minutes (I've seen it take over five minutes) but eventually an alert should show up on the overview page in the openshift admin console.

You can also go to the Monitoring>Metrics page in the admin console and enter a PromQL query, for example sum(argocd_app_info{dest_namespace=~"default",health_status!=""}) by (sync_status)
Testing note by Shoubhik
Please validate that deleting up an ArgoCD instance also removes all associated rolebindings/roles and monitoring objects that were created.
Resources to be automatically deleted
Where %s is the name of the namespace the argocd instance was installed into

Kind
Name

Role
%s-read

RoleBinding
%s-prometheus-k8s-read-binding

ServiceMonitor
%s

ServiceMonitor
%s-server

ServiceMonitor
%s-repo-server

PrometheusRule
gitops-operator-argocd-alerts.

@wtam2018 @bigkevmcd Could you also please take a look at this PR?

/ok-to-test
@jopit added to org.

@jopit Can you please provide the steps for how to verify the changes

@jopit I have added unit test target in OpenShift CI via pr https://github.com/redhat-developer/gitops-operator/pull/55. Can you please rebase.

@sbose78 @wtam2018 @amitkrout I believe I've addressed all of the review comments, could you all please take another look at this PR?

@jopit added a testing note for QE / @dewan-ahmed @amitkrout
Could you list the resources created that one should expect to be gone when an ArgoCD is removed ?

/lgtm
/approve

@sbose78 @dewan-ahmed @amitkrout I've added the list of  resources that should be deleted when an argocd instance is deleted to the initial comment of this PR.

Successfully validated following the instructions in the PR. attached screenshot and logs for reference.
cc: @amitkrout

dewanahmed@dahmed-mac gitops-operator % oc get argocd -n openshift-gitops
NAME             AGE
argocd-cluster   13m
dewanahmed@dahmed-mac gitops-operator % oc get clusterrole openshift-gitops-read
Error from server (NotFound): clusterroles.rbac.authorization.k8s.io "openshift-gitops-read" not found
dewanahmed@dahmed-mac gitops-operator % oc get role openshift-gitops-read
Error from server (NotFound): roles.rbac.authorization.k8s.io "openshift-gitops-read" not found
dewanahmed@dahmed-mac gitops-operator % oc get role openshift-gitops-read -n openshift-gitops
NAME                    CREATED AT
openshift-gitops-read   2021-02-23T18:27:38Z
dewanahmed@dahmed-mac gitops-operator % oc get rolebinding openshift-gitops-prometheus-k8s-read-binding -n openshift-gitops
NAME                                           ROLE                         AGE
openshift-gitops-prometheus-k8s-read-binding   Role/openshift-gitops-read   17m
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor openshift-gitops
Error from server (NotFound): servicemonitors.monitoring.coreos.com "openshift-gitops" not found
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor openshift-gitops -n openshift-gitops
Error from server (NotFound): servicemonitors.monitoring.coreos.com "openshift-gitops" not found
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor openshift-gitops-server -n openshift-gitops
Error from server (NotFound): servicemonitors.monitoring.coreos.com "openshift-gitops-server" not found
dewanahmed@dahmed-mac gitops-operator % oc get PrometheusRule gitops-operator-argocd-alerts
Error from server (NotFound): prometheusrules.monitoring.coreos.com "gitops-operator-argocd-alerts" not found
dewanahmed@dahmed-mac gitops-operator % oc get PrometheusRule gitops-operator-argocd-alerts -n openshift-gitops
NAME                            AGE
gitops-operator-argocd-alerts   20m
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor
No resources found in default namespace.
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor -n openshift-gitops
NAME                         AGE
argocd-cluster               22m
argocd-cluster-repo-server   22m
argocd-cluster-server        22m
dewanahmed@dahmed-mac gitops-operator % oc get argocd
No resources found in default namespace.
dewanahmed@dahmed-mac gitops-operator % oc get argocd -n openshift-gitops
NAME             AGE
argocd-cluster   25m
dewanahmed@dahmed-mac gitops-operator % oc delete argocd -n openshift-gitops
error: resource(s) were provided, but no name, label selector, or --all flag specified
dewanahmed@dahmed-mac gitops-operator % oc delete argocd argocd-cluster -n openshift-gitops
argocd.argoproj.io "argocd-cluster" deleted
dewanahmed@dahmed-mac gitops-operator % oc get servicemonitor -n openshift-gitops
No resources found in openshift-gitops namespace.
dewanahmed@dahmed-mac gitops-operator % oc get PrometheusRule gitops-operator-argocd-alerts -n openshift-gitops
Error from server (NotFound): prometheusrules.monitoring.coreos.com "gitops-operator-argocd-alerts" not found
dewanahmed@dahmed-mac gitops-operator % oc get rolebinding openshift-gitops-prometheus-k8s-read-binding -n openshift-gitops
Error from server (NotFound): rolebindings.rbac.authorization.k8s.io "openshift-gitops-prometheus-k8s-read-binding" not found
dewanahmed@dahmed-mac gitops-operator % oc get role openshift-gitops-read -n openshift-gitopsError from server (NotFound): roles.rbac.authorization.k8s.io "openshift-gitops-read" not found

repo: redhat-developer/gitops-operator


text:
check if namespace/project exist

odo push should check that the project or namespace exist and fail with nice error explaining what should user do to fix it (create namespace/project)
▶ odo push
 •  Push devfile component backend  ...
 ✗  Failed to start component with name backend.
Error: Failed to create the component: unable to create or update component: unable to create Deployment backend: namespaces "demo" not found

This is still problem in v3 for both odo dev and odo deploy
/kind bug
/priority medium
/area devfile

/remove-lifecycle rotten
/lifecycle frozen

Closing in favor of https://github.com/redhat-developer/odo/issues/4447

repo: redhat-developer/odo


text:
[Telemetry] Create Charts for the odo dev UI

/kind user-story
/area telemetry
/area Web-UI
User Story
As an odo product manager or product owner or odo developer, I want to be able to view Charts about the odo dev UI, So that I can understand how users interact with this UI, now that it is generally available out of the experimental mode.
This will allow us to make data-driven decisions on how to improve it.
Raw events are being sent already and are available (see https://github.com/redhat-developer/odo/issues/6900).
Acceptance Criteria

[ ] It should create charts under the odo > odo cli space

[ ] TODO Explore what kind of charts can be helpful

Links

Related Epic (mandatory):

/kind user-story

/remove-lifecycle stale
/lifecycle frozen


text:
variable?? cannot be resolved or is not a field of ClassX Java type.qute(UnknownProperty)

Example:
{#formselect value=company.address.country.id?? /}
id?? will get marked in red:
id?? cannot be resolved or is not a field of model.Country Java type.qute(UnknownProperty)

Could you share your project please.

authors: angelozerr geertvanleemputten

repo: redhat-developer/vscode-quarkus


text:
Update image_verifier.py to use APIs in Pyxis GraphQL module

Update image_verifier.py to use APIs in Pyxis GraphQL module, Jira: CWFHEALTH-1255

Hi @ElenaKarolinaSemanova While reviewing your proposal of supporting both LightBlue and Pyxis as the metadata source, I having been thinking on just drop the LightBlue support for the image_verifier module, the reason of supporting both the two metadata source is some handlers are complicated in its implementation and we want to run dev with Pyxis to test it carefully, and make it possible to switch to LightBlue when we see critical bugs on prod with Pyixs. However, I think the image_verifier is much simpler and we can perform the tests easily, so it probably doesn't worth the effort to supporting both the metadata source, what do you think?

@qixiang ptal

@qixiang ptal

Could you test it locally to verify these APIs work as expected? A simple way to test it locally could be something like:
from freshmaker.image_verifier import ImageVerifier
image_verifier = ImageVerifier()
image_verifier.verify_repository("some/repo")
image_verifier.verify_image("some-image-nvr")

And please squash the commits to remove the unnecessary commit which the changes have been dropped.

@qixiang  ptal

@qixiang Please take a look

hi @ElenaKarolinaSemanova I made some changes to the pyxis_gql module in #194, could you rebase this PR and update the push target to pyxis branch once #194 is merged?

@qixiang I resolved your comments; if you agree, we can merge this MR

@ElenaKarolinaSemanova there are some conflicts in freshmaker/pyxis_gql.py, could you rebase it?

@ElenaKarolinaSemanova there are some conflicts in freshmaker/pyxis_gql.py, could you rebase it?

@qixiang Done, we can merge after tests pass

authors: ElenaKarolinaSemanova qixiang

repo: redhat-exd-rebuilds/freshmaker

license: MIT


text:
moved logic for default identities to keycloak service

[ ] Have you created an issue and used it in the commit message?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

Small refactor to move logic for default Identities to service @gastaldi

That was implemented like this previously but I didn't think that was exactly right, because KeycloakService would not perform as it should, and it would influence integration test, but maybe I am being too academic here.
@ALRubinger what do you think?

But on the OTOH, those variables are the main reason to avoid any Keycloak activity so I guess that makes sense

Please reopen this when KeycloakServiceTest passes with the CATAPULT_OPENSHIFT_USERNAME and CATAPULT_OPENSHIFT_PASSWORD env vars set (needed for.integration tests)

authors: edewit gastaldi

repo: redhat-kontinuity/catapult


text:
DNS Container remains in ContainerCreating status

I see the following error and kube-dns containers remain in ContainerCreating. I do see /run/flannel/subnet.env file on master, so not sure why it complains.
Events:
Type     Reason                  Age                From                 Message

Warning  FailedScheduling        6m (x3 over 6m)    default-scheduler    0/1 nodes are available: 1 node(s) were not r
eady.
Warning  FailedScheduling        6m (x3 over 6m)    default-scheduler    0/2 nodes are available: 2 node(s) were not r
eady.
Warning  FailedScheduling        6m (x2 over 6m)    default-scheduler    0/3 nodes are available: 3 node(s) were not r
eady.
Normal   Scheduled               6m                 default-scheduler    Successfully assigned kube-dns-86f4d74b45-b6f
wp to kubemaster
Normal   SuccessfulMountVolume   6m                 kubelet, kubemaster  MountVolume.SetUp succeeded for volume "kube-
dns-config"
Normal   SuccessfulMountVolume   6m                 kubelet, kubemaster  MountVolume.SetUp succeeded for volume "kube-
dns-token-76fvt"
Warning  FailedCreatePodSandBox  5m (x12 over 6m)   kubelet, kubemaster  Failed create pod sandbox: rpc error: code =
Unknown desc = NetworkPlugin cni failed to set up pod "kube-dns-86f4d74b45-b6fwp_kube-system" network: Multus: error in
invoke Delegate add - "flannel": open /run/flannel/subnet.env: no such file or directory
Normal   SandboxChanged          1m (x286 over 6m)  kubelet, kubemaster  Pod sandbox changed, it will be killed and re
-created.

I ran it again and now I see this error message:
Tolerations:     CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason                  Age               From                 Message

Warning  FailedScheduling        3m (x6 over 3m)   default-scheduler    0/1 nodes are available: 1 node(s) were not ready.
Normal   Scheduled               3m                default-scheduler    Successfully assigned kube-dns-86f4d74b45-hljvn to kubemaster
Normal   SuccessfulMountVolume   3m                kubelet, kubemaster  MountVolume.SetUp succeeded for volume "kube-dns-config"
Normal   SuccessfulMountVolume   3m                kubelet, kubemaster  MountVolume.SetUp succeeded for volume "kube-dns-token-zhr8v"
Warning  FailedCreatePodSandBox  2m (x12 over 3m)  kubelet, kubemaster  Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "kube-dns-86f4d74b45-hljvn_kube-system" network: unexpected end of JSON input
Normal   SandboxChanged          2m (x11 over 3m)  kubelet, kubemaster  Pod sandbox changed, it will be killed and re-created.

Hey @verizonold  could you check and see if this is resolved / do you have any notes to add to resolve it? Thanks!

authors: dougbtv verizonold

repo: redhat-nfvpe/kube-ansible


text:
Is there a reason the prometheus operator is limited to Single Namespace and OwnNamespace mode?

Hey All,
Just wondering if there was any history here or if people would be open to  enabling Multi-namespace and AllNamespace capabilities, which makes this operator far more powerful/capable. I've used the underlying operator enough to know that its fully capable of being used in this way, just wondering if there was concern about conflicts with the openshift-monitoring infrastructure, or some other reason this isn't allowed.

Hi @etsauer,
That is something that you will need to check with the maintainers of this operator. The issue here in this repo is regard their distribution on the OCP/OLM catalogue only.
Could you please raise an issue for its maintainers in their repo?

@camilamacedo86 looking at the repo history, the contributor who added the prometheus operator to OH was @J0zi , who does not appear to be a contributor to the operator rep itself. That is why I chose to open the issue here.
https://github.com/prometheus-operator/prometheus-operator/graphs/contributors

@camilamacedo86  I got the same response on the proemtheus-operator so, I need some advice.
I'd love to just submit the change myself, but I'm struggling with this issue: https://github.com/redhat-openshift-ecosystem/community-operators-prod/issues/237

Hi @etsauer,
Could we not close this one? is not it fixed in https://github.com/prometheus-operator/prometheus-operator/issues/4265?
Regards #237 it not supporting podman so far but you can use docker right?


text:
operator gitlab-operator-kubernetes (0.14.1)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible

authors: framework-automation gl-distribution-oc


text:
operator [O] annotationlab (4.4.1)

Signed-off-by: Bikash Bhandari bhnadari@johnsnowlabs.com
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/hold cancel


text:
operator [N] [CI] tempo-operator (0.1.0)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/retest

/merge possible

/retest

/merge possible

/retest

/merge possible

/merge possible

/merge possible


text:
operator bpfd-operator (0.2.0)

Add the bpfd operator to the Openshift operator catalog.  This commit adds the version v0.2.0 manifests.
Please see our website for more information or reach out to #bpfd in K8s slack with any questions.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?
[x] Have you considered whether you want to use semantic versioning order?
[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: astoycos framework-automation


text:
Fix extra variable in Getting Started section

Looks like this was a copy/paste issue from the agnosticd role :) the rhacs-demo.yaml playbook in https://github.com/rh-mobb/rhacs-demo doesn't leverage the ocp4_workload_ prefix, and so results in the following error when run as written:
TASK [ocp4_deploy_acs_demo_apps : Apply/update policies] **************************************************************************************************************
[WARNING]: Module did not set no_log for password
failed: [localhost] (item=/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/cvss_7.json) => {"ansible_loop_var": "item", "changed": false, "connection": "close", "content_length": "190", "content_type": "application/json", "date": "Mon, 27 Jun 2022 15:29:23 GMT", "elapsed": 0, "item": "/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/cvss_7.json", "json": {"code": 16, "details": [], "error": "credentials not found: not authorized: invalid username and/or password", "message": "credentials not found: not authorized: invalid username and/or password"}, "msg": "Status code was 401 and not [200]: HTTP Error 401: Unauthorized", "redirected": false, "status": 401, "url": "https://central-********.apps.cluster-pz84l.pz84l.sandbox1139.opentlc.com/v1/policies/import", "vary": "Accept-Encoding"}
failed: [localhost] (item=/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/process_uid_0.json) => {"ansible_loop_var": "item", "changed": false, "connection": "close", "content_length": "190", "content_type": "application/json", "date": "Mon, 27 Jun 2022 15:29:24 GMT", "elapsed": 0, "item": "/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/process_uid_0.json", "json": {"code": 16, "details": [], "error": "credentials not found: not authorized: invalid username and/or password", "message": "credentials not found: not authorized: invalid username and/or password"}, "msg": "Status code was 401 and not [200]: HTTP Error 401: Unauthorized", "redirected": false, "status": 401, "url": "https://central-********.apps.cluster-pz84l.pz84l.sandbox1139.opentlc.com/v1/policies/import", "vary": "Accept-Encoding"}
failed: [localhost] (item=/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/read_write_root_fs.json) => {"ansible_loop_var": "item", "changed": false, "connection": "close", "content_length": "190", "content_type": "application/json", "date": "Mon, 27 Jun 2022 15:29:24 GMT", "elapsed": 0, "item": "/Users/akrohg/projects/acs-workshop/rhacs-demo/roles/ocp4_deploy_acs_demo_apps/files/policies/read_write_root_fs.json", "json": {"code": 16, "details": [], "error": "credentials not found: not authorized: invalid username and/or password", "message": "credentials not found: not authorized: invalid username and/or password"}, "msg": "Status code was 401 and not [200]: HTTP Error 401: Unauthorized", "redirected": false, "status": 401, "url": "https://central-********.apps.cluster-pz84l.pz84l.sandbox1139.opentlc.com/v1/policies/import", "vary": "Accept-Encoding"}

awesome much appreciated @andykrohg++ !!

authors: andykrohg rcarrata

repo: redhat-scholars/acs-workshop


text:
Add CORS config to S3 bucket

The previous change in f012bdeee2c2b8131a688be6261778a768b2c750 didn't apply a CORS rule to the S3 bucket properly. It appears that the preferred method now is to use aws_s3_bucket_cors_configuration.

Relevant Terraform docs.

repo: redhatcloudx/infrastructure


text:
Failed to cancel tasks scheudled by

Expected behavior
Task is cancelled after executor shutdown
Actual behavior
Task not getting cancelled after executor shutdown
Steps to reproduce or test case
Failed to cancel tasks scheduled by  scheduleWithFixedDelay
here I am creatuing tasks based on value from application.properties file.
private void scheduleHeartBeatTask(String systemId) {
    boolean doSchedule = false;
    try {
        if (!heartBeatMap.containsKey(systemId)) {
            doSchedule = true;
            heartBeatMap.putIfAbsent(systemId, Boolean.TRUE);
        }
        if (doSchedule) {

            RScheduledFuture<?> future = executor.scheduleWithFixedDelay(new HeartbeatTask(systemId), 1, 1, TimeUnit.MINUTES);

        }
    } catch(Exception  e) {
        heartBeatMap.remove(systemId);
        LOG.error("Exception in scheduling task for {}: {}", systemId, e);
    }
}

}
Now I want to cancel tasks based on boolean value from application.properties file
@PostConstruct public void init() throws InterruptedException {
Codec codec = new org.redisson.codec.SerializationCodec();
executor = redisClient.getExecutorService("Heart-BeatExecutor_new", codec);
boolean isShutDown = false;
	 Set<String> tasks = executor.getTaskIds();

    if (!tasks.isEmpty()) {
            for (String s : tasks)) {

                Boolean test = executor.cancelTasks);

                );
            }
        }

	then I shutdown executor and then recreate new executor .

	 executor.shutdown();
        try {
            // Wait a while for existing tasks to terminate
            if (!executor.awaitTermination(60, TimeUnit.SECONDS)) {
                // Cancel currently executing tasks forcefully
                LOG.info("#### pallavi  executor.shutdownNow --1--");
                executor.shutdownNow();
                // Wait a while for tasks to respond to being cancelled
                if (!executor.awaitTermination(60, TimeUnit.SECONDS)) {
                    LOG.info("#### pallavi  executor.shutdownNow --2--");
                }
            }
        } catch (InterruptedException ex) {
            // (Re-)Cancel if current thread also interrupted
            executor.shutdownNow();
            // Preserve interrupt status
            Thread.currentThread().interrupt();
        }

 if (executor.isShutdown()) {
        LOG.info("ExecutorService - Heart_BeatExecutor is shut down, recreate it.");
        isShutDown = true;
        executor.delete();
        executor = redisClient.getExecutorService("Heart-BeatExecutor_new", codec);

		when i create new executor , all previous tasks are still scheduled.
    }

}
Redis version
3.23.5
Redisson version
3.23.5
Redisson configuration
public class RedisConfig {
@Value("${redis.config-file}")
private String redisConfigFile;
@Bean
@Lazy
public RedissonClient createRedissonClient(RedissonConnectionListener redissonConnectionListener) throws RedisConfigurationException {
    RedissonClient client;
    try {
        final var methodName = "createRedissonClient() ";
        LOG.info("{} default redis Config file {}",methodName,redisConfigFile);

        var config = Config.fromYAML(new File(redisConfigFile));
        config.setConnectionListener(redissonConnectionListener);
        client = Redisson.create(config);
    } catch (Exception e) {
        throw new RedisConfigurationException("Unable to create Redis Client %s", e);
    }
    return client;
}

}

any update on this issue ?

Is this issue same as  Can't delete/cancel scheduleWithFixedDelay Job which is running #1869  which was fixed but seems it is resurfacing again ?

ANY UPDATE

repo: redisson/redisson


text:
AnnexBReader在读取最后一个Nalu表现不正确

我在跟着大佬学习h264解码器的过程中尝试使用rust实现相应的功能，在实现Lesson_2_3_ReadAnnexB时C++代码与Rust代码在最后一个Nalu表现不一致，我手动打开了h264原始数据，发现最后一个Nalu的bufLen应该是39，但C++的输出是160。

我认为这可能是一个bug，但也暂时没发现问题出在哪，又或者是我听课时漏了什么。我尝试让C++打印出Nalu中的原始信息，发现C++输出完39字节原始信息后还继续输出了其他不应该存在的字节。希望大佬可以看看是我的问题还是代码存在一些隐秘的bug。

非常感谢你的反馈，因为在过春节，这么晚才回复你。
这是我代码里面的 Bug，现在已经修复了。
问题在于 AnnexBReader::ReadFromFile() 函数中，每次从文件中读取完毕，向 Buffer 中追加数据的时候，每次都追加了固定的 1024 个字节，实际上应该按照实际读取的长度进行追加。
目前这份代码做了一些修改，又之前的每一课一个子目录，变成只有一个目录，而通过 tag 来区分是那节课的内容。
你可以通过 H264_AnnexBReader 标签来获取到这一小节的代码。并且之后的 tag 中的这部分也都进行了修改。
建议你重新 clone 一下代码，因为在修改的过程中，我使用了强制提交，这可能会给你带来一些问题。


text:
Post Tweets using Oauth1 only

The post tweets API uses the RequestHelperV1 only specifically. I need to be able to use OAuth2 Bearer authentication for post tweets. Is there any reason for this specifically? Or can I raise a PR for the changes to use either V1 or V2?

Sorry, didn't realise the endpoint does not support Authenticating with OAuth 2.0 Application-Only.


text:
Setup cluster with TLS using a K8s secret doesn't work

What happened?
My network is internal in my EKS cluster and so I cannot use cert-manager to create a Let's Encrypt certificate. So I have used certbot to create the certificates to my brokers with a DNS challenge which I completed manually.
I then went ahead and inserted the certificate files into a K8s secret just as the documentation asks to do.
I went ahead and fired up a cluster referrencing the secret in the external listeners section
What did you expect to happen?
I expected the cluster to consume the secret content and be able to configure the TLS of the brokers correctly.
but instead, the cluster didn't come up and the logs from the pods said that there is no such file for the ca.crt file
even though I've made a certificate using Let's Encrypt, therefore a public CA not needing to specify a ca.crt file
I also tried to mitigate this by trying to create a generic secret and putting the supplied chain (CA.crt) of Let's encrypt which was provided with the certificate by certbot and tried referncing also that generic secret but again, the cluster won't come up.
Esentially I'm not able to setup a TLS enabled cluster in any other mode other than using a self signed certificate by cert-manager.
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
apiVersion: cluster.redpanda.com/v1alpha2
kind: Redpanda
metadata:
  name: redpanda
spec:
  chartRef:
    chartVersion: 5.9.6
  clusterSpec:
    external:
      enabled: true
      domain: redpanda.example.com
      type: NodePort
    tls:
      enabled: true
      certs:
        external:
          secretRef:
            name: rp-data-tls

    auth:
      sasl:
        enabled: true
        users:
          - name: superuser
            password: secretpassword
    storage:
      persistentVolume:
        enabled: true
        storageClass: gp2 // just an example

Anything else we need to know?
No response
Which are the affected charts?
No response
Chart Version(s)
5.9.6
Cloud provider

AWS - EKS

JIRA Link: K8S-394

Could you share the logs from redpanda when it's refusing to start up and the redacted contents of your secret, really just the keys would be fine?

Just saw now that you replied - of course!
Let's start by the secret , so I'm creating a TLS type secret using the method supplied in the documentation
like so:
kubectl create secret tls rp-data-tls \
  --cert=certs/tls.crt \
  --key=certs/tls.key \
  --namespace redpanda-data

The files are the actual certificate which I've made with certbot - I copied those files and renamed them from the following available files that I got when using certbot.
I renamed the cert.pem to tls.crt and privkey.pem to tls.key and just referenced those files here
The logs of the nodes when they try to come up complain about not having the ca.crt availble (As it red panda is expecting it) even though this certificate was created with a public CA (let's encrypt using certbot cli for macOS)
I'll comment with the actual error in a small bit.

My yaml for creating the cluster is the following:
apiVersion: cluster.redpanda.com/v1alpha2
kind: Redpanda
metadata:
  name: redpanda
spec:
  chartRef:
    chartVersion: 5.9.9
  clusterSpec:
    nodeSelector:
      purpose: "red-panda-cluster"
    external:
      enabled: true
      domain: redpanda-data.k8s.staging.mycompanydomain.com
      type: NodePort
    tls:
      enabled: true
      certs:
        external:
          secretRef:
            name: rp-data-tls

    auth:
      sasl:
        enabled: true
        users:
          - name: superuser
            password: secretpassword
    storage:
      persistentVolume:
        enabled: true
        storageClass: csi-driver-ebs-gp3

INFO  2024-11-10 12:46:40,982 [shard 0:main] cluster - Using index based node ID {2}
INFO  2024-11-10 12:46:40,983 [shard 0:main] main - application.cc:2611 - Starting Redpanda with node_id 2, cluster UUID {nullopt}
INFO  2024-11-10 12:46:40,983 [shard 0:main] raft - coordinated_recovery_throttle.cc:126 - Starting recovery throttle, rate: 104857600
INFO  2024-11-10 12:46:40,983 [shard 0:main] cluster - producer_state_manager.cc:45 - Started producer state manager
INFO  2024-11-10 12:46:40,983 [shard 0:main] main - application.cc:1583 - Partition manager started
INFO  2024-11-10 12:46:40,983 [shard 0:main] security - authorizer.h:273 - Registered superuser account: type {user} name {kubernetes-controller}
INFO  2024-11-10 12:46:40,983 [shard 0:main] security - authorizer.h:273 - Registered superuser account: type {user} name {superuser}
INFO  2024-11-10 12:46:40,983 [shard 0:main] main - application.cc:1671 - Archiver service setup, cloud_storage_enabled: false, legacy_upload_mode_enabled: true
INFO  2024-11-10 12:46:40,983 [shard 0:main] resource_mgmt - storage.cc:182 - Setting new target log data size 11.711GiB. Disk size 19.518GiB reservation percent 25 target percent {80} bytes {nullopt}
INFO  2024-11-10 12:46:40,987 [shard 0:main] rpc - server.cc:284 - vectorized internal rpc protocol - Stopping 1 listeners
INFO  2024-11-10 12:46:40,987 [shard 0:main] rpc - server.cc:296 - vectorized internal rpc protocol - Shutting down 0 connections
INFO  2024-11-10 12:46:40,987 [shard 0:main] resource_mgmt - storage.cc:88 - Stopping disk space manager service
INFO  2024-11-10 12:46:40,987 [shard 0:main] auditing - audit_log_manager.cc:792 - Shutting down audit log manager
INFO  2024-11-10 12:46:40,987 [shard 0:main] auditing - audit_log_manager.cc:563 - stop() invoked on audit_sink
INFO  2024-11-10 12:46:40,987 [shard 0:main] auditing - audit_log_manager.cc:600 - Setting auditing enabled state to: false
INFO  2024-11-10 12:46:40,987 [shard 0:main] auditing - audit_log_manager.cc:654 - Ignored update to audit_enabled(), auditing is already disabled
INFO  2024-11-10 12:46:40,988 [shard 0:main] raft - coordinated_recovery_throttle.cc:134 - Stopping recovery throttle
INFO  2024-11-10 12:46:40,988 [shard 0:main] kvstore - kvstore.cc:125 - Stopping kvstore: dir /var/lib/redpanda/data/redpanda/kvstore/0_0
INFO  2024-11-10 12:46:41,022 [shard 0:main] main - application.cc:461 - Shutdown complete.
ERROR 2024-11-10 12:46:41,022 [shard 0:main] main - application.cc:487 - Failure during startup: std::__nested<std::runtime_error> (Could not read trust file /etc/tls/certs/external/ca.crt): std::__1::__fs::filesystem::filesystem_error (error system:2, filesystem error: open failed: No such file or directory ["/etc/tls/certs/external/ca.crt"])

authors: chrisseto itamararjuan

repo: redpanda-data/helm-charts


text:
Fix redpen-621

Merge branch 'master' into redpen-621

Coverage decreased (-0.03%) to 89.929% when pulling cf62a68ec87f050a1a5a255ca169f366a710f824 on takahi-i:redpen-621 into 3a3f241d46df6ac6f5f29e6794155849b29c2bbd on redpen-cc:master.

Coverage decreased (-0.05%) to 89.909% when pulling 986275dc40348239e1bd42e29552ac2dac00bbeb on takahi-i:redpen-621 into 3a3f241d46df6ac6f5f29e6794155849b29c2bbd on redpen-cc:master.

authors: coveralls takahi-i

repo: redpen-cc/redpen


text:
Song title not showing

If you disable scrolling and align Cleartext onto the right, long titles occasionally dissappear

Hi, with which player is this occurring? What other modifications were done with Cleartext? How do you replicate the issue?

Player is cleartext (not cleartext pure) with spotify. Only modifications made were aligning the player onto the right and disabling scrolling.
I then played a piece of music with this title: Sarasate: Introduction et Tarantelle, Op 43. That made the song title completely dissappear and only show the authors name.

Here are pictures for the bug happening on the right but not on the left.

I'll try to replicate that and see what I can do. :)

Hi, I want to replace Windows Media Player with Groove Music, Or else I want to add Groove Music. Where can I change the code for this?

I'm running into this issue too. Any news?

authors: IsAvaible Lighwan pradeepjts redsaph

repo: redsaph/cleartext


text:
add backers & sponsors

Add backers and sponsors to your readme automatically.
Add badges on top.
more info: https://github.com/opencollective/opencollective/wiki/Github-banner
PS: 2 backer's avatar is already fixed, broken image is cached, should clear eventually.

Thanks for the PR!

authors: Andarist piamancini

repo: redux-saga/redux-saga

license: mit


text:
feat: arrange import section of combineReducers

name: Arrange import section of combineReducers and remove useless repeated import
about: arrange import section
PR Type
Does this PR add a new feature, or fix a bug?

refactoring

Why should this PR be included?

It makes codes more clean!

Checklist

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?
[x] Have the docs been updated to match the changes in the PR?
[ ] Have the tests been updated to match the changes in the PR?
[x] Have you run the tests locally to confirm they pass?

New Features
What new capabilities does this PR add?
What docs changes are needed to explain this?
Bug Fixes
What is the current behavior, and the steps to reproduce the issue?
What is the expected behavior?
How does this PR fix the problem?

Sure, why not. Thanks!

authors: Brew-Brew timdorr

repo: reduxjs/redux


text:
Merge packages

Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature
:memo: Documentation Fix
:book: New/Updated Documentation Content

This is not how you do Open Source.

authors: phryneas plusplushq


text:
Add support for discarding a file in a pull request.

Description
Some files have trivial changes. There is edit and merge already provided by GitHub. Discard could take the old file and put it back as the edit.
Very useful for lightweight cleanup a PR (especially for files which have whitespace changes).
Screenshot

Example URLs
https://github.com/<org>/<repo>/pull/<id>/files

The feature exists already, its called restore-file

@atishay do you have the extension installed?

The example URLs field specifies a REAL URL is required.
The feature also already exists  👍

Thank you. Sorry was looking in the wrong browser.

authors: atishay fregante yakov116

repo: refined-github/refined-github


text:
Direct access to workflow build artifacts

Description
Unless I'm overlooking it, downloading a repo's build artifacts requires a handful of clicks/navigating/filtering:

Clicking a repo's "Actions" tab
Clicking a workflow from the top-left list of workflows
Clicking to filter that workflow's runs by status, e.g. by "Success" (I'm not sure why Github doesn't have a filter for "Has artifacts"
Clicking into workflow run entries to check if each run has artifacts
Scrolling to bottom of a run's page to see if it has artifacts (and if they're unexpired)
And finally, if artifacts exist, if artifacts are unexpired, clicking to download the desired artifacts

It would be phenomenally useful if these could be accessed directly from repos' root pages, whether a hover box from the "Actions" link which shows a list of workflows with most-recent-successful-runs-with-artifacts, or simply direct linking those artifacts themselves).
A variation of this could be an ability to checkbox "favorite" specific workflows, and then have a flashing alert icon on a repo's page to indicate that there is a new build artifact since last visit, or recent X days, etc.
This could additionally be interfaced into the Github inbox/notifications, new workflow artifacts being a notification/alert on its own, with direct links to the artifacts (or at least the particular run).
Granted, there exists an alternative method to this via the "Nightly.link" option, however it's externally hosted and requires manually editing workflow URLs to reach artifact links. Even then, this doesn't always work on all build workflows.
A variation of this feature -- also useful on its own, in addition to above -- would be a function that checks and highlights workflows and workflow-runs that have unexpired, downloadable artifacts, without having to browse into and out of runs, workflow by workflow, run by run.
For example, in the top-left list of Workflows on the "Actions" page, this addon could sort that list by Most-recent-artifact. Similarly, in the list of a workflow's run, individual runs with downloadable/unexpired artifacts could become highlighted/bolded/colored as an indicator, as a sort of visualized filter indicator, pre-applied.
/$0.02
Example URLs
https://github.com/refined-github/refined-github
https://github.com/refined-github/refined-github/actions

This is too involved and niche for Refined GitHub.
I'd advise working with nightly.link to:

add a way to access all workflows at once
fix "this doesn't always work on all build workflows."

As for the notifications, if you control the repo you can configure it to send out notifications either via email or by adding a comment to a specific issue, to which you can subscribe (just an idea).

authors: Coldblackice fregante


text:
Restore forked-to feature and enable it for every user

Fixes #5596
Test URLs
Fork a repo :fork_and_knife:
Screenshot

GitHub really broke the flow here and I expect them to change this once again soon.
The fork button now always points to the new /fork page, even if I have a fork.
Big deal breaker: there is NO link to my existing fork. At least I don't see it.
forked-to just became mandatory for every GitHub user. 😃

Separately perhaps I'd also replace the ?fragment fetch with an API call because that fragment is no longer shown on GitHub and I expect them to drop it soon (unless they restore it)

I suppose this will also close https://github.com/refined-github/refined-github/issues/5435

I suppose this will also close #5435

I don't know, I've never seen this error in the first place

GitHub really broke the flow here and I expect them to change this once again soon.

The repository fork button now displays existing forks.

Called it!

Is this @fregante's work? Impressive 🎉

First requested in https://github.com/refined-github/refined-github/issues/1129 and implemented in https://github.com/refined-github/refined-github/pull/2153

authors: cheap-glitch fregante kidonng


text:
[Feat] strapi v4 with graphql

Describe the bug
I suspect there is a bug, but not sure.
strapi v3 graphql query
query {
  users {
    username
    email
  }
}

strapi v4 graphql query, the field nested under attributes
query {
  documents {
    data {
      id
      attributes {
        title
        categories {
          data {
            id
            attributes {
                name
            }
          }
        }
      }
    }
    meta {
      pagination {
        page
        pageSize
        total
        pageCount
      }
    }
  }
}

In refine, it will query like this:
{
  "query": "query ($where: JSON, $sort: String, $start: Int, $limit: Int) { symptomsConnection (where: $where) { aggregate { count } } symptoms (sort: $sort, where: $where, start: $start, limit: $limit) { name } }",
  "variables": {
    "where": {},
    "sort": "id:asc",
    "start": 0,
    "limit": 10
  }
}

Does the symptoms { name } seems use strapi v3 graphql grammer?
There are also error messages on request :

...
"Cannot query field \"symptomsConnection\" on type \"Query\"."
...
"Unknown argument \"where\" on field \"Query.symptoms\"."
...

Do I missing something? Or @pankod/refine-strapi-graphql is used for strapi V3?
deps
"@pankod/refine-strapi-graphql": "3.25.6",
"@pankod/refine-strapi-v4": "3.25.6",
backend deps
"@strapi/plugin-graphql": "4.2.0",
"@strapi/strapi": "4.2.0",

I'm not sure I have the ability to do that thing. 😂
Can you point out how to do this? Or I can try to step by step, the worst case is that I can't do it, but I leave some information for further develop

Great, I think you're being unfair to yourself on this one. Now I will share some documents and examples that will make your development easier 🚀
How does Refine handle GraphQL queries?
https://refine.dev/docs/guides-and-concepts/data-provider/graphql/
Hasura GraphQL data provider:
https://github.com/pankod/refine/blob/next/packages/hasura/src/index.ts
NHost GraphQL data provider:
https://github.com/pankod/refine/tree/next/packages/nhost
Discord server where you can get support from us whenever you need help: https://discord.gg/refine :)

After some research, except for some technical issues, I find the support to v4 graphql support should be delay.
Lots of complains are found in strapi forum. I guess there would be some changes in the future.
And some technical issues includes:

strapi-v4 's normalizeData function could handle response problems
but query problems(mess data, attributes) are hard to resolve

@omeraplak close this issue or just leave it to wait?

Hey @HaveF,
Thanks a lot for your research. I think we can close the issue. For now, we need some time

Spent 2 hours before realizing I needed version 3 of strapi

Spent 2 hours before realizing I needed version 3 of strapi

Sorry to hear that. We should clearly state this in our documents

yes u should

Spent 2 hours before realizing I needed version 3 of strapi

Sorry to hear that. We should clearly state this in our documents

repo: refinedev/refine


text:
docs(use-one): fix typo

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://refine.dev/docs/guides-concepts/contributing/#commit-convention

Bugs / Features

[ ] Related issue(s) linked
[ ] Tests for the changes have been added
[x] Docs have been added / updated
[ ] Changesets have been added https://refine.dev/docs/guides-concepts/contributing/#creating-a-changeset

What is the current behavior?
What is the new behavior?
fixes (issue)
Notes for reviewers

@BatuhanW Oh, Sorry.
I checked. Thanks 🙏

@BatuhanW Oh, Sorry.
I checked. Thanks 🙏

authors: frontend-jonggil jgjgill


text:
Console spam from Wireless Crafting Grid

I'm not sure how to reproduce this, but this exception has been spamming the console occasionally:
https://gist.github.com/jeremiahwinsley/257c6871e94d2a0badd264cec94e1b2c
Refined Storage version 1.9.13
Refined Storage Addons version 0.7.2
in modpack ATM6 1.7.2

What's your server I wonder lol

I don't think that should happen anymore on newer builds.

authors: jebjordan jeremiahwinsley raoulvdberge

repo: refinedmods/refinedstorageaddons


text:
How to communicate an action to a React component

I asked this question on StackOverflow, but it's not getting much traction. I'm hoping someone here will have an opinion... Sorry in advance for the length.

While my scenario is pretty specific, I think it speaks to a bigger question in Flux. Components should be simple renderings of data from a store, but what if your component renders a third-party component which is stateful? How does one interact with this third-party component while still obeying the rules of Flux?
So, I have a React app that contains a video player (using clappr). A good example is seeking. When I click a location on the progress bar, I want to seek the video player. Here is what I have right now. I've tried to strip down my code to the most relevant parts.
    var PlayerActions = Reflux.createActions([
        'seek'
    ]);

    var PlayerStore = Reflux.createStore({
        listenables: [
            PlayerActions
        ],

        onSeek(seekTo) {
            this.data.seekTo = seekTo;
            this.trigger(this.data);
        }
    });

    var Player = React.createClass({
        mixins: [Reflux.listenTo(PlayerStore, 'onStoreChange')],

        onStoreChange(data) {
            if (data.seekTo !== this.state.seekTo) {
                window.player.seek(data.seekTo);
            }

            // apply state
            this.setState(data);
        }

        componentDidMount() {
            // build a player
            window.player = new Clappr.Player({
                source: this.props.sourcePath,
                chromeless: true,
                useDvrControls: true,
                parentId: '#player',
                width: this.props.width
            });
        },

        componentWillUnmount() {
            window.player.destroy();
            window.player = null;
        },

        shouldComponentUpdate() {
            // if React realized we were manipulating DOM, it'd certainly freak out
            return false;
        },

        render() {
            return
;
        }
    });

The bug I have with this code is when you try to seek to the same place twice. Imagine the video player continuously playing. Click on the progress bar to seek. Don't move the mouse, and wait a few seconds. Click on the progress bar again on the same place as before. The value of data.seekTo did not change, so window.player.seek is not called the second time.
I've considered a few possibilities to solve this, but I'm not sure which is more correct. Input requested...

1: Reset seekTo after it is used
Simply resetting seekTo seems like the simplest solution, though it's certainly no more elegant. Ultimately, this feels more like a band-aid.
This would be as simple as ...
    window.player.on('player_seek', PlayerActions.resetSeek);

2: Create a separate store that acts more like a pass-through
Basically, I would listen to a SeekStore, but in reality, this would act as a pass-through, making it more like an action that a store. This solution feels like a hack of Flux, but I think it would work.
    var PlayerActions = Reflux.createActions([
        'seek'
    ]);

    var SeekStore = Reflux.createStore({
        listenables: [
            PlayerActions
        ],

        onSeek(seekTo) {
            this.trigger(seekTo);
        }
    });

    var Player = React.createClass({
        mixins: [Reflux.listenTo(SeekStore, 'onStoreChange')],

        onStoreChange(seekTo) {
            window.player.seek(seekTo);
        }
    });

3: Interact with window.player within my actions
When I think about it, this feels correct, since calling window.player.seek is in fact an action. The only weird bit is that I don't feel right interacting with window inside the actions. Maybe that's just an irrational thought, though.
    var PlayerActions = Reflux.createActions({
        seek: {asyncResult: true}
    });
    PlayerActions.seek.listen(seekTo => {
        if (window.player) {
            try {
                window.player.seek(seekTo);
                PlayerActions.seek.completed(err);
            } catch (err) {
                PlayerActions.seek.failed(err);
            }
        } else {
            PlayerActions.seek.failed(new Error('player not initialized'));
        }
    });

BTW, there's a whole other elephant in the room that I didn't touch on. In all of my examples, the player is stored as window.player. Clappr did this automatically in older versions, but though it has since been fixed to work with Browserify, we continue to store it on the window (tech debt). Obviously, my third solution is leveraging that fact, which it technically a bad thing to be doing. Anyway, before anyone points that out, understood and noted.

4: Seek via dispatchEvent
I also understand that dispatching a custom event would get the job done, but this feels way wrong considering I have Flux in place. This feels like I'm going outside of my Flux architecture to get the job done. I should be able to do it and stay inside the Flux playground.
    var PlayerActions = Reflux.createActions({
        seek: {asyncResult: true}
    });
    PlayerActions.seek.listen(seekTo => {
        try {
            let event = new window.CustomEvent('seekEvent', {detail: seekTo});
            window.dispatchEvent(event);
            PlayerActions.seek.completed(err);
        } catch (err) {
            PlayerActions.seek.failed(err);
        }
    });

    var Player = React.createClass({
        componentDidMount() {
            window.addEventListener('seekEvent', this.onSeek);
        },
        componentWillUnmount() {
            window.removeEventListener('seekEvent', this.onSeek);
        },
        onSeek(e) {
            window.player.seek(e.detail);
        }
    });

Action => Store => Component that wraps the player, why does that feel like a hack to you?

@ce07c3
Because of actions like seek. It's a one-shot action. I go through the store, because it's what I'm "supposed to do" but the seek value has no use beyond the immediate flow.
I'll try to walk through the workflow:
Seek-To-5-Sec-Button-Component => Action => Store => Player-Component

player is playing.. which means current time updates automatically
user clicks the button
Seek-To-5-Sec-Button-Component calls Action.seek(5)
Store hears action, updates itself, and triggers
handler in Player-Component reacts to the trigger, calling this.player.seek(newStoreData.seekValue)
user clicks the button again
Seek-To-5-Sec-Button-Component calls Action.seek(5)
Store hears action, updates itself

dilemma: The seek value is the same this time. Shouldn't I not trigger? The store has not changed. The value was 5. It still remains 5.
I know that I need to trigger for this to work, so I trigger anyway.

handler in Player-Component reacts to the trigger, calling this.player.seek(newStoreData.seekValue)

Note that I always have to call this.player.seek, because it's plausible for "last value" to equal "next value".

So what do we have here?

A store that always triggers regardless of the value from the action?
A component that always calls this.player.seek(...) whenever the store makes any noise.
What if the store holds additional data, like current time? A change in current time would trigger a seek. Can't have that.

Maybe your answer is to have a SeekStore that only stores this seek value. That way we know every trigger is a legitimate request to seek. Still, it feels like a hack. The only reason we have a store is because we're "supposed to" have a store.
With Player-Component, we're not dealing with a component that simply renders data based on the state of a store. It actually contains another completely separate state machine (this.player), and interacting with that state machine is awkward.

To be clear, I'm not necessarily calling this a bug. There are exceptions to any rule, and I can make this work in a variety of ways. I'm merely looking for recommendations that would as closely as possible align with best practices.

Normally, I would close this question because it doesn't follow our contributing policies... but I think this is something that needs discussion. I'd ask you to take it to the #reactiflux slack, but I'm tired of all the helpful stuff there getting deleted.
I don't really have time to give this the time it deserves at the moment though, but I did want to let you know I have looked at it, and will give it some thought later tonight.
Kneejerk reaction though:  I think sometimes people take the flux pattern and even the reflux pattern a bit too seriously. I tend to keep state that I consider atomic state out of my stores entirely, and just handle them within components.
I define Atomic State as any prop that is temporary in nature, and state can be completely lost, without consequences to the app.

@H3Chief, thanks for giving it thought.
I didn't know about #reactiflux slack, but it looks like they aren't accepting new users right now (according to http://www.reactiflux.com/). I guess a fast-growing community is a good problem to have.

@jfairley I had "similar" issues with resource stores. Whenever I retrieved a list of resources, it would replace any previously fetched lists - very annoying in case a page has multiple lists of the same resource type.
In this case I'd probably say the player does not need to go to the store. It's a stateful view component built without Flux in mind. One use case where a store could make sense: persist the player's seek position in local storage e.g. by video id (I just leave out URL query parameters for now so this example makes sense).
Videos are a great subject for discussion. Usually, the frequent state updates from stores are "flattened" by the virtual DOM -> DOM diffing and patching. For videos, you might have to include a creator in your actions which you propagate to the components, so that you only update when a user seeks (this.trigger(state, creator)).

+1 to @ce07c3's suggestion.

@ce07c3 :+1:
I'd say you don't need to use Flux if the component is stateful and cohesive (i.e. can do by itself and it's children). That way you have a Player component that can be reused. The parent that is using the Player could then just wire in actions through it's props if needed. For example:
// In the parent (ES6)
import Player from "./Player";
// in render
<Player ref="thePlayer" onSeek={(position) => Actions.seek(position, "thePlayer")} />

// In Player.js
const Player = React.createClass({
    propTypes: { onSeek: React.PropTypes.func },
    // this gets called from within the component:
    _onSeek: function(position) {
      if (this.props.onSeek) { this.props.onSeek(position) }
    }
});
export default Player;

Thanks for the suggestions.
Unfortunately, while the player I'm using is a self-contained, stateful, cohesive component, I've disabled the default controls and am reimplementing my own buttons plus some. My controls go way beyond the typical play-pause / volume / full-screen that you typically see, so using Flux actually is helpful for managing button states... the play-pause button icon, various annotations along the seek bar, the having anything show as disabled when appropriate, etc.
Also, since my React DOM is laid out such that the buttons are not children of the Player component, doing the work with callback functions isn't clean either.
Right now, I'm sitting fine with option #1 "reset seekTo after it is used". I see all the drawbacks, but functionally it works, and I can pretty confidently rely on the player seek action completing more quickly than a user intent on seeking to the same place twice.
I'm also toying with the idea of listening to this action directly in the component. I see this as basically the same as using an event architecture rather than flux, so it doesn't bother me a ton the more I think about it.

@H3Chief, your comment about not taking the flux pattern too seriously keeps bubbling up in my head. It think it most fits my problem and less-than-ideal solutions. I'm glad I have flux in my app, and it simplifies 99% of my workflows, but for those 1% of square-peg-in-a-round-hole scenarios, I'm not sweating it too much. Rather I'm more interested in making it work so I can move on to other tasks. This is more an academic discussion for when my mind wanders at night. :wink:

Alternatively you could have two components: Player and PlayerButtons, the latter taking Player as prop from a parent component so it can wire itself up to the player events. Here is an example of using both in the same parent's render method:
render: () => {
  var player = <Player />;
  return (
    <ParentBase>
      <PlayerButtons player={player}></PlayerButtons>
      <something else="lol" />

      { player } /* here be the player */
    </ParentBase>
  );
}

You can use propTypes to validate the player prop in PlayerButtons:
// assuming PlayerButtons is an ES6 Class
PlayerButtons.propTypes = {
  player: React.PropTypes.element // or shape if you want to be more specific with callbacks
};

@spoike Interesting suggestion... I've never thought of doing anything with the react component other than returning it to be rendered. I'll try that out.

This was a rich conversation!  It's been a while since there's been any activity here, so I'm going to close this out.  If the conversation wants to continue on (which I hope it does!), please just open a new issue in our new discussion repo and link back to this issue: https://github.com/reflux/discuss

repo: reflux/refluxjs


text:
Design high-level layout of writing, references, and AI interactions components

For familiarity we need to decide if this should feel like a word processor (WP) or an IDE.

WP: Microsoft Word, Google Docs
IDE: VS Code, RStudio, JetBrains

For the WP, we'd have a persistent left pane with references and right pane with AI interactions.
For the IDE, we'd have collapsible and relocatable windows for writing, references, and AI interactions.

Pulling some comments out of PRs to track:

We can resize components now. How easy is it to collapse them entirely, or re-arrange them?
What is the difference between "Uploads" and "References"? Do we want them to be separate?
Vertical scroll within a component not working yet

What is the difference between "Uploads" and "References"? Do we want them to be separate?

No strong opinion, but I could imagine an "Upload" is the raw document (an unstructured PDF), whereas a Reference is the structured JSON we create from the grobid response
Example citations list from Grobid

[
  {
    "authors": [
      {
        "full_name": "References",
        "surname": "References"
      }
    ],
    "index": 0,
    "id": "b0"
  },
  {
    "authors": [
      {
        "full_name": "O Chapelle",
        "given_name": "O",
        "surname": "Chapelle"
      },
      {
        "full_name": "E Manavoglu",
        "given_name": "E",
        "surname": "Manavoglu"
      },
      {
        "full_name": "R Rosales",
        "given_name": "R",
        "surname": "Rosales"
      }
    ],
    "index": 1,
    "id": "b1",
    "date": "2014",
    "title": "A simple and scalable response prediction for display advertising",
    "journal": "ACM Trans. Intell. Syst. Technol",
    "note": "To appear"
  },
  {
    "authors": [
      {
        "full_name": "K Lee",
        "given_name": "K",
        "surname": "Lee"
      },
      {
        "full_name": "B Orten",
        "given_name": "B",
        "surname": "Orten"
      },
      {
        "full_name": "A Dasdan",
        "given_name": "A",
        "surname": "Dasdan"
      },
      {
        "full_name": "W Li",
        "given_name": "W",
        "surname": "Li"
      }
    ],
    "index": 2,
    "id": "b2",
    "date": "2012",
    "title": "Estimating conversion rate in display advertising from past performance data",
    "book_title": "KDD '12 Proceedings of the 18th ACM SIGKDD international conference on Knowledge discovery and data mining",
    "publisher": "ACM Press"
  },
  {
    "authors": [
      {
        "full_name": "A Dasdan",
        "given_name": "A",
        "surname": "Dasdan"
      },
      {
        "full_name": "A Svirsky",
        "given_name": "A",
        "surname": "Svirsky"
      }
    ],
    "index": 3,
    "id": "b3",
    "date": "2012",
    "title": "Model-based performance goal adjustment in real-time online advertising campaigns",
    "book_title": "KDD '12 Proceedings of the 18th ACM SIGKDD international conference on Knowledge discovery and data mining",
    "publisher": "SIGKDD, ACM Press",
    "pages": "804-812",
    "first_page": "804",
    "last_page": "812"
  },
  {
    "authors": [
      {
        "full_name": "J Friedman",
        "given_name": "J",
        "surname": "Friedman"
      },
      {
        "full_name": "T Hastie",
        "given_name": "T",
        "surname": "Hastie"
      },
      {
        "full_name": "R Tibshirani",
        "given_name": "R",
        "surname": "Tibshirani"
      }
    ],
    "index": 4,
    "id": "b4",
    "title": "glmnet: Lasso and elastic-net regularized generalized linear models",
    "note": "Published: 2013-08-04",
    "url": "cran.r-project.org/web/packages/glmnet/"
  },
  {
    "authors": [
      {
        "full_name": "J Friedman",
        "given_name": "J",
        "surname": "Friedman"
      },
      {
        "full_name": "T Hastie",
        "given_name": "T",
        "surname": "Hastie"
      },
      {
        "full_name": "R Tibshirani",
        "given_name": "R",
        "surname": "Tibshirani"
      }
    ],
    "index": 5,
    "id": "b5",
    "date": "2010",
    "title": "Regularization paths for generalized linear models via coordinate descent",
    "journal": "J. Stat. Softw",
    "volume": "33",
    "issue": "1",
    "pages": "1-22",
    "first_page": "1",
    "last_page": "22"
  },
  {
    "authors": [],
    "index": 6,
    "id": "b6",
    "date": "2013",
    "title": "Making measurement make sense (3ms) initiative",
    "book_title": "Interactive Advertising Bureau",
    "url": "http://www.iab.net/MMMS"
  },
  {
    "authors": [
      {
        "full_name": "C Perlich",
        "given_name": "C",
        "surname": "Perlich"
      },
      {
        "full_name": "B Dalessandro",
        "given_name": "B",
        "surname": "Dalessandro"
      },
      {
        "full_name": "R Hook",
        "given_name": "R",
        "surname": "Hook"
      },
      {
        "full_name": "O Stitelman",
        "given_name": "O",
        "surname": "Stitelman"
      },
      {
        "full_name": "T Raeder",
        "given_name": "T",
        "surname": "Raeder"
      },
      {
        "full_name": "F Provost",
        "given_name": "F",
        "surname": "Provost"
      }
    ],
    "index": 7,
    "id": "b7",
    "date": "2012",
    "title": "Bid optimizing and inventory scoring in targeted online advertising",
    "book_title": "KDD '12 Proceedings of the 18th ACM SIGKDD international conference on Knowledge discovery and data mining",
    "publisher": "SIGKDD, ACM Press",
    "pages": "804-812",
    "first_page": "804",
    "last_page": "812"
  },
  {
    "authors": [
      {
        "full_name": "O Stitelman",
        "given_name": "O",
        "surname": "Stitelman"
      },
      {
        "full_name": "B Dalessandro",
        "given_name": "B",
        "surname": "Dalessandro"
      },
      {
        "full_name": "C Perlich",
        "given_name": "C",
        "surname": "Perlich"
      },
      {
        "full_name": "F Provost",
        "given_name": "F",
        "surname": "Provost"
      }
    ],
    "index": 8,
    "id": "b8",
    "date": "2012",
    "title": "Design principles of massive, robust prediction systems",
    "book_title": "KDD '12 Proceedings of the 18th ACM SIGKDD international conference on Knowledge discovery and data mining",
    "publisher": "SIGKDD, ACM Press",
    "pages": "1357-1365",
    "first_page": "1357",
    "last_page": "1365"
  },
  {
    "authors": [
      {
        "full_name": "R J Tibshirani",
        "given_name": "R",
        "middle_name": "J",
        "surname": "Tibshirani"
      },
      {
        "full_name": "R J Tibshirani",
        "given_name": "R",
        "middle_name": "J",
        "surname": "Tibshirani"
      },
      {
        "full_name": "R Lockhart",
        "given_name": "R",
        "surname": "Lockhart"
      },
      {
        "full_name": "J Taylor",
        "given_name": "J",
        "surname": "Taylor"
      }
    ],
    "index": 9,
    "id": "b9",
    "date": "2014",
    "title": "A significance test for the lasso",
    "journal": "Annals of Statistics",
    "note": "To appear"
  },
  {
    "authors": [
      {
        "full_name": "H Wickham",
        "given_name": "H",
        "surname": "Wickham"
      }
    ],
    "index": 10,
    "id": "b10",
    "date": "2009",
    "title": "ggplot2: Elegant Graphics for Data Analysis",
    "publisher": "Springer"
  }
]

I think the latter could be a gateway into future interactions with the parsed citation list (Ref Studio will go fetch it or some metadata about it for you).

I think we should fairly soon explore a VS Code-like layout where we have a column of icons on the far left that toggle a variety of sidebars such as the file browser and references components, and we reserve the right sidebar for AI interactions. We can then open documents for writing or PDFs for reading in the center in a tabbed configuration with the ability to pull them out to be side-by-side as in an IDE.

authors: gjreda hammer

repo: refstudio/refstudio


text:
Youtube video broken from video

Says the account was deleted

@1-alex98 Thank you for bringing this into my attention. I see that the account has been deleted by Google, maybe it's because gplaydl gets the access to APKs without their permission.

@1-alex98 Thank you for bringing this into my attention. I see that the account has been deleted by Google, maybe it's because gplaydl gets the access to APKs without their permission. I have appealed against this.

wait, so this broke now?

@NTT1906 No. The code hasn't broken. The video violated their TOS and was removed from YouTube.

repo: rehmatworks/gplaydl


text:
🛑 SmartProtection is down

In 0f25825, SmartProtection (https://smartprotection.com) was down:

HTTP code: 404
Response time: 171 ms

Resolved: SmartProtection is back up in 5eb266c after 10 minutes.

repo: reinaldoleon/monitoring


text:
Pretraining networks for PPO

Hello,
Firstly I have to say that you created an amazing Framework, thank you for that!
I am trying to pretrain the policy network for the PPO algorithm, because it converges very slowly for my data. I would like to use a pretrained policy network, for which PPO only does some small optimizations.  What I tried was basically something like this:
fetches = [self.agent.model.optimization, self.agent.model.loss_per_instance]
feed_dict = {self.agent.model.states_input['state'] : batch_x,
                             self.agent.model.actions_input['action'] : batch_y,
                             self.agent.model.reward_input :  np.ones((train_batch_size,), dtype=np.float32)
                             self.agent.model.terminal_input : np.zeros((train_batch_size,), dtype=np.bool_)
                             self.agent.model.deterministic_input : True,
                             self.agent.model.update_input : True}
self.agent.model.session.run(fetches=fetches, feed_dict=feed_dict)

Unfortunately this does only seem to update the baseline network, which is not what I want. I have to say that it is hard for me to get a good overview over the whole tensorflow graph. So maybe someone can help me with some pointers on how I can train the policy network specifically?
Regards,
Mark

Hi,
there is currently no pretraining method for policy gradient algorithms. If you look at the DQFD agentmodel, you see an example of how one can add an API method to pretrain from supervised data (in the pretrain method).
The memory model (which PPO model inherits from) has a method to import experience:
https://github.com/reinforceio/tensorforce/blob/master/tensorforce/models/memory_model.py#L546
So what you would need to do is implement a method in the memory model that  performs an update after importing this data.

Note that you can now do supervised pretraining and load just the relevant layers, see in the FAQ how

I have a large dataset of expert demonstrations and am wondering how to pre-train the PPO agent on this data. As I understand the post above it is not enough to import the experiences directly, I looked at the FAQ for examples but did not find any.
Any directions to further examples would be greatly appreciated.
Regards,
Kris

Two ways:

See faq on just using supervised training externally, load in layers - works
One would need an update function that can be called independently. You can import memories already, but you would then need to be able to call update. It is not that difficult to just add this function (normally an update only happens in conjunction with an observe), so you can try that. I might do this some time soon myself for my research but will not promise anything

Thanks for a super quick response!
Importing experience requires me to import internals, for now, I have left this blank (an empty list) and I assume that is okay? Also, each experience I load should be a single episode, right?

Just follow the example in the dqfd agent test and agent to look at the data layouting/internals

repo: reinforceio/tensorforce


text:
🛑 BINUSMAYA Praktikum (SLC Bluejack) is down

In e4a26d2, BINUSMAYA Praktikum (SLC Bluejack) (https://bluejack.binus.ac.id/binusmayalab/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BINUSMAYA Praktikum (SLC Bluejack) is back up in bbeb730.


text:
🛑 GreatNusa.com is down

In 724afd3, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 129 ms

Resolved: GreatNusa.com is back up in d532536.


text:
🛑 BINUSMAYA (Academic Services) is down

In 71903f8, BINUSMAYA (Academic Services) (https://binusmaya.binus.ac.id/LoginAD.php) was down:

HTTP code: 404
Response time: 1149 ms

Resolved: BINUSMAYA (Academic Services) is back up in 2bed6ca.


text:
upload_to_release flag does not stop releases being made

The problem
Setting the flag 'upload_to_release' to false in the setup.cfg does not stop the release from being made.
Expected behavior
When setting the flag 'upload_to_release' to false, no releases should be made by the workflow.
Additional context
Used to have the flag set to true, but added additional steps after the semantic-release workflow. To prevent overwriting releases I turned it off but nothing changed.
setup.cfg looks like this
[semantic_release]
version_variable = repo_name/__init__.py:__version__
branch = main
upload_to_repository = false
upload_to_release = false

Apparent confusion about what the flag is supposed to do

repo: relekang/python-semantic-release


text:
Check if a model is disposed before fetching its version

We ran into the same issue described in https://github.com/remcohaszing/monaco-marker-data-provider/issues/1 and we are on version 1.2.3 (where the fix is supposed to be). This issue is that model.getVersionId() throws the same error.
Instead this PR switches the check of model.isDisposed() to before model.getVersionId(). If the model is disposed then the condition will short-circuit and model.getVersionId() will never get called.

Makes sense! Thanks!


text:
🛑 Remix Dashboard is down

In 7c08931, Remix Dashboard (https://remix.fairuse.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Remix Dashboard is back up in 99f0c38 after 41 minutes.

repo: remix-bot/status


text:
Typescript is still not working on fresh install

What version of Remix are you using?
2.0.1 (latest)
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
I am using node v20.8.0 + npm v10.1.0.

ran npx create-remix@latest

responded NO to create new repo
responded YES to install via npm

ran npm run typecheck

Expected Behavior
no errors
Actual Behavior

I moved everything to another folder and everything worked after that. Not sure why this was happening.

repo: remix-run/remix


text:
feat: replace node-fetch with @remix-run/web-fetch

This PR replaces the internal usage of node-fetch with @remix-run/web-fetch to be more spec compliant and allow for ReadableStream's to be used as a body in node.
This work is critical to enable a runtime agnostic way to implement streaming in the server-runtime package and provide React 18 support to everyone.
I have also re-worked the file upload handler API to operate on an AsyncIterable for the body content. This allows for better error propagation as well as bringing unstable_parseMultipartFormData to all supported platforms, not just Node.

[x] Docs
[x] Tests

Any obvious reason I'd be getting this after upgrading from 1.4? If not, I'll try to submit a repro or fix.
TypeError: this._readableStream.getReader is not a function
    at ReadableStreamSearch.[Symbol.asyncIterator] ({redacted}/node_modules/@web3-storage/multipart-parser/cjs/src/search.js:149:41)
    at AsyncGenerator.next (<anonymous>)
    at Object.streamMultipart ({redacted}/node_modules/@web3-storage/multipart-parser/cjs/src/index.js:119:29)
    at streamMultipart.next (<anonymous>)
    at parseMultipartFormData ({redacted}/node_modules/@remix-run/server-runtime/formData.js:48:18)

authors: dahlbyk jacob-ebey


text:
feat: create new config package

Signed-off-by: Logan McAnsh logan@mcan.sh

Closes: #

[ ] Docs
[ ] Tests

Testing Strategy:

@mcansh It seems like we have some conflicts to resolve here

authors: MichaelDeBoey mcansh


text:
Make clicking radio boxes and checkboxes on iPads more responsive

Currently clicking these buttons takes about a second for the page to respond. Make it more snappy.
Reported by DTang.

@mrueschman, we should test this on a tablet, a lot of JS was removed in 0.30.0, so hopefully these pages are more responsive.

Tried a survey with 77 questions and branching logic on iPhone, worked fine, closing.

repo: remomueller/slice


text:
🛑 Roubicek.net is down

In d715957, Roubicek.net (https://www.roubicek.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Roubicek.net is back up in d1608d7 after 1 hour, 16 minutes.

repo: renegis/upptime