MSID: 90486 Version: 1 DOI: 2<IP_ADDRESS>7552

"msas": "Cell Biology", "Structural Biology and Molecular Biophysics"
"msid": "90486"
"preprintDoi": "10.1101/2<IP_ADDRESS>7552"
"Reviewed Preprint posted": "2023-09-14"
"Sent for peer review": "2023-06-30"
"Posted to bioRxiv": "2023-07-11" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>7552v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=90486)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/90486/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7552)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/90486/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/90486)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/90486

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/90486

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/90486/v1/90486-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/90486)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

there appears to be a paragraph cut off mid-citation (Rosenthal and Henderson,
this is not present in the pdf, but on biorxiv and eLife preprint

Well spotted @rkcook312!
Do I understand correctly that the issue is one paragraph has been split into two (presumably a typesetting mistake resulting from the page break in the original PDF)?
If this is the only case in this preprint, then I'd be inclined to proceed as is (although could be easily persuaded otherwise). If this is one of many instances, then we should definitely get this fixed and I'll reach out to biorxiv.

Thanks @fred-atherden
Yes correct, one paragraph split into two. This is just the one instance in the preprint so can proceed.

Thanks Rebecca!


perf(raw): resolve id only for allowed extnames

Resolves #2856

🔗 Linked issue
https://github.com/nitrojs/nitro/issues/2856
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

As discussed in linked issue.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Added tests (https://github.com/nitrojs/nitro/commit/03bdd2df3a941911011472b093c644781ef227a2) this does not break #2838, #2836 but only with early return avoiding extra this.resolve call (which is really strange and we should later investigate root cause of this amount of overhead)

Is this connected? It seems that siblings to layer folders slow down Nuxt Nitro, even though they have nothing to do with the app or the layer itself: https://github.com/nuxt/nuxt/issues/30137


Complete branching steps for Rancher 2.9 for Provisioning CAPI

Tasks

[ ] change the rancher-version annotation to catalog.cattle.io/rancher-version: '>= 2.9.0-0 < 2.10.0-0' while adding charts to dev-v2.9 branch. We do this so we can add patches to a  particular Rancher minor version, in this case, it would be the Rancher 2.9 line.
[ ] must have a new chart inside the rancher/charts repository that has a version 104.0.0+upX.Y.Z instead of 103.x.x+upX.Y.Z.
[ ] testing

To be done as part of https://github.com/rancher/rancher/issues/45090 FYI @krunalhinguu @mitulshah-suse @Sahota1225

Branching for CAPI is as expected. Hence, closing the issue.


Release sdk/resourcemanager/confluent/armconfluent v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armconfluent - ci

/check-enforcer override


Webhook-driven scaling not working as expected at enterprise level

Checks

[X] I've already read https://github.com/actions-runner-controller/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.

Controller Version
v0.26.0
Helm Chart Version
0.20.2
CertManager Version
v1.5.4
Deployment Method
Helm
cert-manager installation
yes
Checks

[X] This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
[X] I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
[X] My actions-runner-controller version (v0.x.y) does support the feature
[X] I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue

Resource Definitions
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: re-centos7-deployment
spec:
  template:
    spec:
      enterprise: ***
      labels:
        - re-centos7
      env: []
      group: RELENG-RUNNERS

To Reproduce
to use a webhook-driven scaling
scaler.yaml file

apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name: re-centos7-scaler
spec:
  minReplicas: 1
  maxReplicas: 25
  scaleTargetRef:
    kind: RunnerDeployment
    name: re-centos7-deployment
  scaleUpTriggers:
    - githubEvent:
        workflowJob: {}
      duration: "10m"

added the webhook payload URL and subscribed to workflow_job event

### Describe the bug

webhook-driven scaling worked beautifully at organization level with the github app but when we switched to PAT at the enterprise level scaling is not working as expected.

### Describe the expected behavior

scale up the runners when jobs are in the queue

### Whole Controller Logs

```shell
2022-10-07T07:08:23Z	ERROR	Reconciler error	{"controller": "runnerpod-controller", "controllerGroup": "", "controllerKind": "Pod", "pod": {"name":"re-centos7-deployment-jw7l8-8zqqv","namespace":"re-github-actions-runners"}, "namespace": "re-github-actions-runners", "name": "re-centos7-deployment-jw7l8-8zqqv", "reconcileID": "515d4e9c-0892-4353-8a37-45f6292e7c07", "error": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=32&per_page=100: 500  []"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
2022-10-07T07:08:30Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "num_terminating_busy": 0, "namespace": "re-github-actions-runners", "kind": "runnerdeployment", "name": "re-centos7-deployment", "horizontal_runner_autoscaler": "re-centos7-deployment-scaler", "enterprise": "***", "organization": "", "repository": ""}
2022-10-07T07:08:30Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "suggested": 1, "reserved": 0, "min": 1, "max": 5}
2022-10-07T07:09:21Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "num_terminating_busy": 0, "namespace": "re-github-actions-runners", "kind": "runnerdeployment", "name": "re-centos7-deployment", "horizontal_runner_autoscaler": "re-centos7-deployment-scaler", "enterprise": "***", "organization": "", "repository": ""}
2022-10-07T07:09:21Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "suggested": 1, "reserved": 0, "min": 1, "max": 5}
2022-10-07T07:10:27Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "num_terminating_busy": 0, "namespace": "re-github-actions-runners", "kind": "runnerdeployment", "name": "re-centos7-deployment", "horizontal_runner_autoscaler": "re-centos7-deployment-scaler", "enterprise": "***", "organization": "", "repository": ""}
2022-10-07T07:10:27Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "suggested": 1, "reserved": 0, "min": 1, "max": 5}
2022-10-07T07:11:25Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "num_terminating_busy": 0, "namespace": "re-github-actions-runners", "kind": "runnerdeployment", "name": "re-centos7-deployment", "horizontal_runner_autoscaler": "re-centos7-deployment-scaler", "enterprise": "***", "organization": "", "repository": ""}
2022-10-07T07:11:25Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "suggested": 1, "reserved": 0, "min": 1, "max": 5}
2022-10-07T07:12:26Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "num_terminating_busy": 0, "namespace": "re-github-actions-runners", "kind": "runnerdeployment", "name": "re-centos7-deployment", "horizontal_runner_autoscaler": "re-centos7-deployment-scaler", "enterprise": "***", "organization": "", "repository": ""}
2022-10-07T07:12:26Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "suggested": 1, "reserved": 0, "min": 1, "max": 5}
2022-10-07T07:13:28Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested 2022-10-07T07:08:19Z	DEBUG	events	Normal	{"object": {"kind":"HorizontalRunnerAutoscaler","namespace":"re-github-actions-runners","name":"re-centos7-deployment-scaler","uid":"dcc5d88f-85f7-4abc-9bcc-4028b46e1391","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"2932158187"}, "reason": "RunnerAutoscalingFailure", "message": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=32&per_page=100: 500  []"}
2022-10-07T07:08:19Z	ERROR	Reconciler error	{"controller": "runnerpod-controller", "controllerGroup": "", "controllerKind": "Pod", "pod": {"name":"re-centos7-deployment-jw7l8-8zqqv","namespace":"re-github-actions-runners"}, "namespace": "re-github-actions-runners", "name": "re-centos7-deployment-jw7l8-8zqqv", "reconcileID": "102f37b1-8d01-47d0-824b-6f52b6427dbc", "error": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=33&per_page=100: 500  []"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
2022-10-07T07:08:23Z	ERROR	actions-runner-controller.horizontalrunnerautoscaler	Could not compute replicas	{"horizontalrunnerautoscaler": "re-github-actions-runners/re-centos7-deployment-scaler", "error": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=32&per_page=100: 500  []"}
github.com/actions-runner-controller/actions-runner-controller/controllers.(*HorizontalRunnerAutoscalerReconciler).Reconcile
	/workspace/controllers/horizontalrunnerautoscaler_controller.go:99
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
2022-10-07T07:08:23Z	ERROR	Reconciler error	{"controller": "horizontalrunnerautoscaler-controller", "controllerGroup": "actions.summerwind.dev", "controllerKind": "HorizontalRunnerAutoscaler", "horizontalRunnerAutoscaler": {"name":"re-centos7-deployment-scaler","namespace":"re-github-actions-runners"}, "namespace": "re-github-actions-runners", "name": "re-centos7-deployment-scaler", "reconcileID": "4b14d060-b705-4d67-a557-e4657ba54d7d", "error": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=32&per_page=100: 500  []"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
2022-10-07T07:08:23Z	DEBUG	events	Normal	{"object": {"kind":"HorizontalRunnerAutoscaler","namespace":"re-github-actions-runners","name":"re-centos7-deployment-scaler","uid":"dcc5d88f-85f7-4abc-9bcc-4028b46e1391","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"2932158187"}, "reason": "RunnerAutoscalingFailure", "message": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=32&per_page=100: 500  []"}

Whole Runner Pod Logs
√ Connected to GitHub

Current runner version: '2.285.1'
2022-10-07 10:11:13Z: Listening for Jobs

Additional Context
No response

workflow files have
runs-on: [re-centos7]

I think this unexpected error "error": "failed to list runners: GET https://github.infra.***.com/api/v3/enterprises/***/actions/runners?page=33&per_page=100: 500  []" is coming from your GHES instance and that's breaking ARC. Can you contact your GHES admin or the corresponding GitHub support staff to investigate why its returning 500 errors?

2022-10-10T16:18:31Z	ERROR	actions-runner-controller.runnerpod	Failed to update runner for finalizer removal	{"runnerpod": "re-github-actions-runners/test-deployment-jzddq-jr75q", "error": "Operation cannot be fulfilled on pods \"test-deployment-jzddq-jr75q\": the object has been modified; please apply your changes to the latest version and try again"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
2022-10-10T16:18:31Z	ERROR	Reconciler error	{"controller": "runnerpod-controller", "controllerGroup": "", "controllerKind": "Pod", "pod": {"name":"test-deployment-jzddq-jr75q","namespace":"re-github-actions-runners"}, "namespace": "re-github-actions-runners", "name": "test-deployment-jzddq-jr75q", "reconcileID": "1ab90f19-1ba6-4772-b396-eca089d34b38", "error": "Operation cannot be fulfilled on pods \"test-deployment-jzddq-jr75q\": the object has been modified; please apply your changes to the latest version and try again"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
	```

2022-10-10T16:29:55Z	DEBUG	events	Normal	{"object": {"kind":"Runner","namespace":"re-github-actions-runners","name":"test-deployment-jzddq-x6ml6","uid":"17f07c2e-0b80-4050-81df-4338062bbb37","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"2941441226"}, "reason": "RegistrationTokenUpdated", "message": "Successfully update registration token"}
2022-10-10T16:29:55Z	DEBUG	actions-runner-controller.runnerreplicaset	Skipped reconcilation because owner is not synced yet	{"runnerreplicaset": "re-github-actions-runners/test-deployment-jzddq", "owner": "re-github-actions-runners/test-deployment-jzddq-x6ml6", "pods": null}
2022-10-10T16:29:55Z	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/mutate-runner-set-pod", "UID": "de4d384a-777d-4e18-830c-1fdf204646e9", "kind": "/v1, Kind=Pod", "resource": {"group":"","version":"v1","resource":"pods"}}
2022-10-10T16:29:55Z	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/mutate-runner-set-pod", "code": 200, "reason": "", "UID": "de4d384a-777d-4e18-830c-1fdf204646e9", "allowed": true}
2022-10-10T16:29:55Z	INFO	actions-runner-controller.runner	Created runner pod	{"runner": "re-github-actions-runners/test-deployment-jzddq-x6ml6", "repository": ""}
2022-10-10T16:29:55Z	DEBUG	events	Normal	{"object": {"kind":"Runner","namespace":"re-github-actions-runners","name":"test-deployment-jzddq-x6ml6","uid":"17f07c2e-0b80-4050-81df-4338062bbb37","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"2941441228"}, "reason": "PodCreated", "message": "Created pod 'test-deployment-jzddq-x6ml6'"}
2022-10-10T16:29:55Z	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/mutate-runner-set-pod", "UID": "ecf76436-e76d-44e4-b8b7-4a34277a6d34", "kind": "/v1, Kind=Pod", "resource": {"group":"","version":"v1","resource":"pods"}}
2022-10-10T16:29:55Z	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/mutate-runner-set-pod", "code": 200, "reason": "", "UID": "ecf76436-e76d-44e4-b8b7-4a34277a6d34", "allowed": true}
2022-10-10T16:29:55Z	INFO	actions-runner-controller.runner	Failed to create pod due to AlreadyExists error. Probably this pod has been already created in previous reconcilation but is still not in the informer cache. Will retry on pod created. If it doesn't repeat, there's no problem	{"runner": "re-github-actions-runners/test-deployment-jzddq-x6ml6"}
2022-10-10T16:29:56Z	INFO	actions-runner-controller.runnerpod	Runner pod has been stopped with a successful status.	{"runnerpod": "re-github-actions-runners/test-deployment-jzddq-pk2rb"}
2022-10-10T16:29:59Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "re-github-actions-runners/test-deployment-jzddq-x6ml6", "podCreationTimestamp": "2022-10-10 16:29:55 +0000 UTC"}

Every controller is in general an eventually consistent system. Errors as seen in the last two logs you've pasted are normal.


Fixed tests for armv7 architecture

Fixes #163

[Current coverage][cc-pull] is 65.34%

Merging [#164][cc-pull] into [dev][cc-base-branch] will not change coverage

@@                dev       #164   diff @@
==========================================
  Files            61         61
  Lines          3316       3316
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2167       2167
  Misses         1149       1149
  Partials          0          0

Powered by Codecov. Last updated by [bc4c9d8...8021e97][cc-compare]
[cc-base-branch]: https://codecov.io/gh/badoo/Chatto/branch/dev?src=pr
[cc-compare]: https://codecov.io/gh/badoo/Chatto/compare/bc4c9d8a648c134f16c3168b40ca518fd66416b2...8021e972b9ca8741bd6fa45c7cc476d81bbed37d
[cc-pull]: https://codecov.io/gh/badoo/Chatto/pull/164?src=pr


Update information-technology-quiz.ts

About SPF
Updated: Information technology quiz

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Thank you for your contribution!
Please review the requested changes. Once those changes have been implemented, then we can merge your PR into main. 👍

okay Thanks for the suggestions

Congrats on another contribution to our repository. 🎉 We look forward to future contributions. 👍

Thank you ma'am🥳


Fixes #1030 Update rimraf

The only relevant change was that rimraf now supports promises directly, so I just had to remove the promise wrapper from the code
Also, happy new year by the way!

Thank you as always!


Add dummy deferrer endpoint

Simple dummy endpoint for deferrer.
GET /v1/defer -> "no"
This might seem a bit controversial in the way that "Sure, free to continue with shutdown" response is no, but it felt natural for me to name this in this way and when asking whether or not to defer shutdown, no is the answer to proceed straight away.
Towards https://github.com/giantswarm/giantswarm/issues/2993

"Sure, free to continue with shutdown" response is no

I'm late to the party here, but maybe true/false would look more natural.

I'm late to the party here, but maybe true/false would look more natural.

Works for me. This is in early development so can be changed.


SQLite error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Use 1.8.8
Start the server
https://pastebin.com/ktg1ChAE

Expected behavior
Screenshots
Additional context
Discord contact:

Please switch to paper 1.8.8. They include the SQLite library.


Simplify love.js module lookup

Issue
On Windows the love.js module lookup finds an incorrect folder ( PATH_TO_WORKSPACE\node_modules\love-packager\node_modules\.bin\love.js.cmd vs PATH_TO_WORKSPACE\node_modules\.bin\love.js.cmd).
Solution
I updated the web target to use node's built-in resolution mechanism (require.resolve) and call love.js's main script manually.
I tested this on Windows 11, but don't currently have easy access to test on other systems.

Many thanks for the contribution! ❤


Question: Difference between ServiceEvent, DeviceEvent

I started to develop a SONOS event node for Node-RED, based on your library. Subscribing to and receiving events works fine.
Question: What is the difference between SonosEvents, ServiceEvents?
My understanding is that ONLY the LastChange event is submitted - all others are moderated.

Therefore, the Rendering Control Service event model defines a specialized state variable (LastChange) that is used exclusively for eventing individual state changes. In this model, the LastChange state change is the only variable that is evented using the standard UPnP event mechanism. All other state variables are indirectly evented via the LastChange state variable. (Note:
A_ARG_TYPE_ state variables are not evented, either directly or indirectly.)

Each service emits events https://github.com/svrooij/node-sonos-ts/blob/master/src/services/base-service.ts#L429 They are available at device.ServiceName.Events
The Sonos device subscribes to AvControl and RenderingControl https://github.com/svrooij/node-sonos-ts/blob/master/src/sonos-device.ts#L521 and makes the Sonos device emit the following events. https://github.com/svrooij/node-sonos-ts/blob/master/src/models/sonos-events.ts#L47
Does this answer your question?

Yes. But I am not sure whether I understand it.
Why does the Sonos device only subscribes to AvControl and RenderingControl - there are about 10 services? Just because you picked up the most important?
What happens If I subscribe to volume and mute? Does that results in one or multiple subscription to RenderingControl? What happens if I unsubscribe first to volume and later to mute? After un-subscribing to both the subscription to RenderingControl is un-subscribed?

Not all services provide useful events. The ZoneGroup service doesn’t need to be subscribed to from multiple speakers. The audio in service is only available on speakers that have an audio in port.
I picked the most important services and aggregate the events. Volume events are also used by the notification part for instance. If you subscribe to events on the Sonos device, a subscription for the RenderingControl service and the AvControl service are started. If you also subscribe to those services the events are routed to both handlers but it won’t create an extra subscription on the actual speaker.
Because the events are routed the a speaker/service specific endpoint see here.
It is only possible for each service from each device to have a single subscription. If by accident a service wants to create a new subscription, it will simply be connected to the existing subscription.

Thanks - no it is clear to me.


sdk/reconciler losing type information in log messages.

Expected Behavior
Log messages to display what resources they are working with
Actual Behavior
They are not:
{"level":"info","ts":1547068546.5497584,"logger":"fallback","caller":"sdk/reconciler.go:52","msg":"Reconciling &TypeMeta{Kind:,APIVersion:,} default/laconia-source"}
{"level":"warn","ts":1547068546.687146,"logger":"fallback","caller":"sdk/reconciler.go:74","msg":"Failed to reconcile &TypeMeta{Kind:,APIVersion:,}: services "message-dumper" is forbidden: User "system:serviceaccount:knative-sources:gcppubsub" cannot get services in the namespace "default""}
{"level":"info","ts":1547068567.1675546,"logger":"fallback","caller":"sdk/reconciler.go:52","msg":"Reconciling &TypeMeta{Kind:,APIVersion:,} default/laconia-source"}
Steps to Reproduce the Problem

Run any eventing-source examples, say pubsub
look at the logs and you see that the type information is not properly displayed in the logs.

Additional Info

I think this is cloud events related and obsolete?  Cc @n3wscott

/close
-Scott
On Sat, May 18, 2019 at 10:36 AM Matt Moore<EMAIL_ADDRESS>wrote:

I think this is cloud events related and obsolete? Cc @n3wscott
https://github.com/n3wscott
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/knative/pkg/issues/219?email_source=notifications&email_token=AHWPD4EIVHN6TU5WZQOTXA3PWA5C3A5CNFSM4GPBKCEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWSYTA#issuecomment-493694028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHWPD4GILHSVROG7MJUQEPTPWA5C3ANCNFSM4GPBKCEA
.


podvm-mkosi: build and push images with s390x runner in workflow

Update workflow, to build and push s390x Pod VM image with the s390x runner
Build a image including the s390x Pod VM qcow2 image, and push it to Quay container Registry: quay.io/confidential-containers/podvm-generic-fedora-s390x
Succeed to run the workflow in branch: https://github.com/confidential-containers/cloud-api-adaptor/actions/runs/8643044858/job/23695257457
Verify the qcow2 image:
docker pull quay.io/confidential-containers/podvm-generic-fedora-s390x:latest
docker create --name "fedora-podvm-exporter" "quay.io/confidential-containers/podvm-generic-ubuntu-s390x:latest" /bin/sh
docker cp "fedora-podvm-exporter:/podvm-s390x.qcow2" .
docker rm -f "fedora-podvm-exporter"

Try to create PR from fork repo...


Adjust cpu_cost of some tests to better reflect reality

Should help all C configurations better schedule CPU resources.

LGTM.


BUG: IE10-IE11 Syntax error due to const expression

I'm including iframe-resizer as a dependency in my project without babel transformation and get an exception in IE11-IE10.
Unhandled promise rejection SyntaxError: Syntax error
After debugging, I found out that the problem was in the js/index.js File, namely in using the expression.
const iframeResize = require('./iframeResizer')
...

I want to suggest replacing this expression with the following
var iframeResize = require('./iframeResizer')
...

In addition, a similar expression is used throughout the code.
Pull request will be soon...

Have you tried using V3 of iframe-resizer? That should correctly support IE10

I'll try. Thanks you!

Unfortunately, V3 does not work resize in my case. But there is no error in the IE10.

Is it just IE10 that it does not work in?

I solved the problem this way:
import resizer from 'iframe-resizer/js/iframeResizer';

But I want to create a pull request. Ok?

Is it just IE10 that it does not work in?

No IE10 loaded code without errors. But my resize logic does not work with V3.

Happy to look at a PR, still confused why V3 does not work for you


My website looks different on windows 10

This is what my theme looks like during development on my mac and linux machine.

And this is what my theme looks like on windows 10. My sidebar have no links, share doesn't work and my nav links are somehow italic.

Link to my code:
github

Looks like Internet Explorer might be running in compatibility mode. A dead give away is usually the italics type. This happens because it’s knocking IE down to version 8 which doesn’t support web fonts and other CSS3 properties.

What browser are you using by the way? You don’t have any sort of content/ad blocker plugins enabled do you? Might be blocking third party assets like Google fonts and or Font Awesome which does all the author sidebar social links.

 I'll try disabling it

The problem has been resolved, thank you so much. Adguard and Kaspersky were causing the problem

I have another question, I can't seem to override this transition of nav links.

The nav link underline transition is applied to a :before pseudo class. Relevant CSS is here: https://github.com/mmistakes/minimal-mistakes/blob/master/_sass/minimal-mistakes/_navigation.scss#L233-L252


Paper component cannot display as a circle, example does not work

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Paper components when called with the prop circle={true} should display as a circle.
Current Behavior

The component renders as a square.
Steps to Reproduce (for bugs)

Create a new React app using create-react-app, or create a new, empty React project.
Install material-ui@next.
Copy and paste the Paper example, found here.
Start the application.

An example can be found at this codesandbox I made.
Context

I am simply trying to render the Paper component as a circle, and I can't change anything about it and it's not clear to me why. If I downgrade to 0.20.0 and change nothing else this example works.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.38

React
16.2.0

browser
Chrome, Firefox

@rfaulhaber The circle property wasn't ported to v1-beta. This property was added in https://github.com/mui-org/material-ui/commit/08838a196336b5d3a396b12e503cc9255086a39b. I don't see much value in supporting it. It sounds like a specific and narrow use case. You are free of writing a wrapper with this extra property.
I have added the waiting for users upvotes tag. I'm closing the issue as I'm not sure people are looking for such abstraction. So please upvote this issue if you are. We will prioritize our effort based on the number of upvotes.

Sounds good, thank you!

@leMaik's PR for the RefreshIndicator uses a circular Paper: https://github.com/mui-org/material-ui/pull/9614/files#diff-3c80ade573fa607a2caeccb38e526586R16 so it would be interesting to get his take on whether this is worth having a prop for.


Remove the DeviceLost error

Main reason is: it's not useful. I haven't seen an application that would handle it on all the methods that potentially return this error, and then properly re-create the device and all the resources to continue. I think it's even going to be easier for an application to make sure the graphics is isolated at a task boundary, and then just handle our panic!(), re-create the tasks, and continue.

No consensus here yet, let's move the decision to the next release.


Avoid sharing handles between threads

Fixes #1109 and #2045.

@okuta Could you take a look if this fix is acceptable? I'd like to do the same thing for all handles.

OK, It is acceptable.

@kmaehashi thanks for starting with this issue, don't hesitate to ask me if you need some extra hands to help with it.

Ready for review.

FWIW, I just tested this branch with my multithreaded use cases and it works great. Thanks a lot for this PR, @kmaehashi!

@pentschev Thanks for testing PR! We will proceed to review.

jenkins, test this please.

Jenkins CI test (for commit 520f0b27dd23e5461c4365c6bb5b128c5b9b64e4, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

E   AssertionError: Parameterized test failed.
E
E   Base test method: TestLschol.test_csrmatrix
E   Test parameters:
E     dtype: <type 'numpy.float32'>
E
E   AssertionError:
E   Fail: 10, Success: 0
E
E   The first error message:
E   Traceback (most recent call last):
E     File "cupy/testing/condition.py", line 61, in <lambda>
E       lambda: f(ins, *args[1:], **kwargs),
E     File "/work/cupy/tests/cupyx_tests/linalg_tests/sparse_tests/test_solve.py", line 61, in test_csrmatrix
E       x = cupyx.linalg.sparse.lschol(A, b)
E     File "cupyx/linalg/sparse/solve.py", line 49, in lschol
E       handle = device.get_cusolver_sp_handle()
E     File "cupy/cuda/device.pyx", line 57, in cupy.cuda.device.get_cusolver_sp_handle
E       cpdef get_cusolver_sp_handle():
E     File "cupy/cuda/device.pyx", line 58, in cupy.cuda.device.get_cusolver_sp_handle
E       return _get_device().cusolver_sp_handle
E     File "cupy/cuda/device.pyx", line 213, in cupy.cuda.device.Device.cusolver_sp_handle.__get__
E       'cusolver_sp_handles', cusolver.spCreate, cusolver.spDestroy)
E   AttributeError: 'module' object has no attribute 'spDestroy'```

Looks like this is just a matter of adding a spDestroy function that wraps cusolverSpDestroy. Does that sound right?

Thanks, locally confirmed tests/cupyx_tests/linalg_tests/sparse_tests/test_solve.py pass.
@jakirkham Yes, I added it.

travis ci error.
    cupy/cuda/cusolver.cpp:2370:80: error: ‘cusolverSpDestroy’ was not declared in this scope
             __pyx_v_status = cusolverSpDestroy(((cusolverSpHandle_t)__pyx_v_handle));```

Jenkins CI test (for commit 11dd88e4b527750f1cf13ee637059006d3bd7971, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Test failures are not related to this PR.

Is there anything else needed before integrating this PR? Anything that either of you need help with?

LGTM!

I will backport this PR after #2121 merged.

Thank you! 😊

Thank you all for the effort here, this fix is very much welcome for the work I've been doing! :)


don't reduce CR for low temptargets

With the low_temptarget_lowers_sensitivity option enabled, oref0 doses more aggressively when an "eating soon" target is set.  However, in the current implementation, this becomes much more aggressive with COB, as the adjusted sensitivityRatio is used to adjust CR as well as basal/IOB and ISF.  This results in too-aggressive dosing when a low temptarget is started or left running after carb entry.
This PR adjusts the low_temptarget_lowers_sensitivity behavior so that the modified sensitivityRatio does not affected CR, yielding much more intuitive and predictable behavior before vs. after carb entry, and avoiding most of the risk of a low target causing a postprandial low.

We've been running this branch for 2 months now and have seen far fewer post-meal hypos after setting low targets.

Test is passing for me: re-running.

Ready to merge this if no objections.


Battle of Riften (Imperials)

okay so firstly

hadvar is in the outside part which is good
however the interior

he does side steps

additionally people are going about their day like there isn't a battle going on

Rikke is actually secretly a construction major and is admiring the construction of the wall

Hadvar gets shy and decides not to enter mistviel

and the pre fight dialogue (there is meant to be peace  and some pre changeover dialogue before the fighting starts) is basically non existant
additionally harrold and actually everyone doesn't know when to quit the fight after the Jarl is downed

changeover scene works fine but maven walks in a bit early and causes mayhem
Can't have shit in Riften

Update I saw Hadvar in Mistviel and he seemed to work fine (he was using a bow)

Just wanted to confirm, this is your first time going to Riften right? Mjoll and Sapphire and a few others all have scene quests that play out once you go to Riften. What I need to do is just mark them as completed and they should hopefully go away.
Vanilla Skyrim does this with a few other scene quests like the Execution scene in Solitude or the racism scene (can't think of a better name for it lol) in Windhelm.

Yeah first time

Just wanted to confirm, this is your first time going to Riften right? Mjoll and Sapphire and a few others all have scene quests that play out once you go to Riften. What I need to do is just mark them as completed and they should hopefully go away.
the racism scene (can't think of a better name for it lol) in Windhelm.

Accidentally mistapped on my phone and hit close with comment oopz


KMLDataSource not working with Angular/Webpack in v1.85

Sandcastle example: n/a
Browser: Firefox 92.0
Operating System: MacOS Monterey beta 12.0
After updating to cesium v1.85 there was a problem with webpack/angular where KmlDataSource.load could not load the Datasource anymore. The following error appears in the console after invoking the load method:
ReferenceError: _Users_<username>_<Directory>_<Project_Folder>_node_modules_babel_runtime_helpers_esm_asyncToGenerator__WEBPACK_IMPORTED_MODULE_0__ is not defined

After downgrading to v1.84 everything was working as expected again.

It's possible this is related to https://github.com/CesiumGS/cesium/issues/9790 since KMLDataSource uses zip.js.
CC @ebogo1

@CodeCakePie Could you please share some details about what plugins and versions you are working with? In particular the webpack version would be helpful. Thanks!

I am using Angular 12 which uses Webpack v5.
  "dependencies": {
    "@angular/animations": "^12.0.3",
    "@angular/cdk": "^12.0.5",
    "@angular/common": "^12.0.3",
    "@angular/compiler": "^12.0.3",
    "@angular/core": "^12.0.3",
    "@angular/forms": "^12.0.3",
    "@angular/material": "^12.0.5",
    "@angular/platform-browser": "^12.0.3",
    "@angular/platform-browser-dynamic": "^12.0.3",
    "@angular/router": "^12.0.3",
    "@turf/turf": "6.5.0",
    "cesium": "1.84",
    "file-saver": "^2.0.5",
    "papaparse": "^5.3.1",
    "rxjs": "~6.6.0",
    "tslib": "^2.1.0",
    "zone.js": "~0.11.4"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~12.0.3",
    "@angular/cli": "~12.0.3",
    "@angular/compiler-cli": "~12.0.3",
    "@types/file-saver": "^2.0.2",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^12.11.1",
    "@types/papaparse": "^5.2.5",
    "jasmine-core": "~3.7.0",
    "jasmine-spec-reporter": "~6.0.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "ng-packagr": "^12.0.0",
    "ts-node": "~9.1.1",
    "typescript": "~4.2.3"
  }

These are the working dependencies.
Thank you for looking at this problem!

@CodeCakePie Are you able to test with this branch of CesiumJS? I think this error is related to imports from the third party zip.js worker code and the above branch imports a worker-less version of zip.js. Thanks!
If not, are you able to provide a barebones example to reproduce the error you're seeing?

@CodeCakePie we recently pushed some changes to main to fix and close related issues so I'll close this one since I was unable to reproduce it. Feel free to re-open if you're still having issues, thanks!


Deploy application

New module to allow application to be deployed (ala cf push)
Currently supports public github projects
Feedback provided by log viewer

 (5) Support deploying of an application from a Github URL

 (0.5) Deploy App: Fetch + display available branches. Display chosen branch info


Mermaid support?

Do you plan to support https://mermaid.js.org ? I think it might be great way to generate graphs diagrams in typst.

There's a couple of similar requests which involve supporting some markup language inside of Typst (eg. #184)
I don't think any of these will supported as a primitive in Typst, but rather Typst will allow you to write functions that parse and render your custom Markup language.
As the language and ecosystem evolve, I think we'll move towards a system where users can import libraries which provide such functions, but we are not there yet.


The 'uservoice' link in the issue templates leads to an unused uservoice account

I confirm (by marking "x" in the [ ] below: [x]):

[x] This is not a troubleshooting question. Troubleshooting questions go here: https://docs.mattermost.com/install/troubleshooting.html.
[x] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[x] I have read contributing guidelines.

Summary
Title says it all - when filing a 'feature request' issue here, you are redirected to https://mattermost.uservoice.com/forums/306457-general which is evidently abandoned/unmaintained, as it has spam and links to viruses going back at least half a year.
Environment
Doesn't apply.
Steps to reproduce
Attempt to file an issue in this repository and select "Feature request"
Expected behavior
Following the advice in the template will guide me to a productive way to make a feature request.
Observed behavior
Following the advice in the template will guide me to a list of spam posts with download links for viruses and malware.
Possible fixes
Maintain or shut down (and remove the link to) the Uservoice forum.

@amyblais Should I just make a change to the Issue Template for now to redirect to the above link instead?


Fast streaming hist

PR for CASSANDRA-13444
https://issues.apache.org/jira/browse/CASSANDRA-13444

Jason Brown: committed to trunk as sha 06da35fdda32781e620d5d28c514ee480212a108. Thanks!


api: make health command greater.

Now it prints(using etcd health command):
{"health": "true"}

A better one will be (using etcd health-cluster command):
member 8211f1d0f64f3269 is healthy: got healthy result from http://<IP_ADDRESS>:12379
member 91bc3c398fb3c146 is healthy: got healthy result from http://<IP_ADDRESS>:22379
member fd422379fda50e48 is healthy: got healthy result from http://<IP_ADDRESS>:32379
cluster is healthy

It seems that the pr can be closed.
@disksing

The output of the pd-ctl has been verified. We can close this issue.
@disksing


feat: allow users changing font stretch

Fixes #905.
PR Type
What kind of change does this PR introduce?
Feature
Other information
Added new option in editor settings option to customize font stretch.

@0x7c13 These commits actually solved my issue. Can you merge these?


Compile error for version 0.1.2

Hello! I'm trying to use your crate for retrieving system uptime and received the following errors when trying to compile version 0.1.2 upon running cargo build:
   Compiling systemstat v0.1.2
error[E0432]: unresolved import `self::platform::PlatformImpl`
  --> /Users/natalie/.cargo/registry/src/github.com-1ecc6299db9ec823/systemstat-0.1.2/src/lib.rs:14:9
   |
14 | pub use self::platform::PlatformImpl as System;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `PlatformImpl` in `platform`. Did you mean to use `Platform`?

error[E0412]: cannot find type `PlatformMemory` in this scope
  --> /Users/natalie/.cargo/registry/src/github.com-1ecc6299db9ec823/systemstat-0.1.2/src/data.rs:92:26
   |
92 |     pub platform_memory: PlatformMemory,
   |                          ^^^^^^^^^^^^^^ not found in this scope

error: aborting due to 2 previous errors

error: Could not compile `systemstat`.

If the problem is as simple as switching out Platform for PlatformImpl, I'd be happy to submit a patch!

Hi! This means your OS is not supported.
If it's Windows, it's been added in master (not released) but it doesn't have uptime yet. If it's macOS, there's absolutely zero support for it, sorry. Of course you can contribute support for any OS :)

Okay thanks! That makes sense. I'd like say I'd have the time to do that, but it's probably not very realistic :)

Released 0.1.3, there's not much macOS support, but uptime is one of the few supported things.


Misc. small improvements worth doing

Hi! 🖖
Here are some things I could do for the site, if needs be:

[ ] Wrap the Google Analytics script in a DoNotTrack check. Being nice web neighbours.
[ ] Incorporate the GA Script in the global JS. Doing so reduces the HTML weight, and adds cacheability to the script that invokes GA.
[ ] Add Schema.org metadata where it counts.
[ ] CSS audit - clean up unused CSS, break it up into partials.
[ ] Expose sponsors as independent URLs
[ ] Expose speakers as independent URLs
[ ] Expose the venue as an independent URL

Tick all those you'd like me to tackle :)
-S

Any of those seem worthy but also not urgent - do whatever brings you joy @ndorfin

What do you mean by exposing speakers and sponsors as independent URLs? Like putting a little 🔗 somewhere so people can link to eg http://kiwi.ruby.nz/speakers/#eoin ?
If we're going to do that for speakers and sponsors it's probably worth doing it for side events as well.
As an aside we need to put in something so that # links take into account the height of the nav - ie anchor tags that are a little higher than the elements we're linking to

@mermop
I mean having pages for each speaker / sponsor / side-event, and a sponsors page that lists all sponsors:

For each speaker page, you can list their talks / workshops.
For each sponsor page you can list what talks/workshops that sponsor is supporting.

Ah right. Nah I don't think it's worth doing a separate page for each speaker or even each side event. I'd want to get our design friends involved if we did that and there's other stuff I'd rather they spend their time on. We don't have that much info about each speaker, I think it's fine to have them all on one and link to them with /speakers#their-name - that said we do need to improve the #-linking behaviour as above

Issued #43 to address Google Analytics


Can I use enable multi activityTarget?

I have two block using plaxify, but I just use only one activity target..
How i can use multi activityTarget?

Hi @sweettimes,
Plax wasn't desiged to support multiple activity targets. I've seen people hack a solution together by including the file twice, but there are plenty of reasons why that's a bad idea. Plax hasn't been actively maintained for years, so you're probably better off finding a more current library that can do what you need it to do.


creating managed identity failing in azure china  with az-2.3.7

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az identity create --n identityforwindow -g window
Describe the bug

creating managed identity  is   failed  in azure china  with az-2.3.7,but  with another azure  cli  versions , the reault is fine.
the picture below is  the result   with azure-cli 2.3.7

the picture below is the result  with  azure-cli 2.32

To Reproduce

If  you run the commond  "az identity create --n identityforwindow -g window"  in azure china  with azure-cli 2.3.7
you can reproduce it.
Expected behavior

i want to  create  managed identity in azure china  with azure-cli 2.3.7
Environment summary

CLI version    azure-cli 2.3.7
Additional context

may be this issue is related to api  version.
Could you please  confirm that for manage identity resource provider,  Azure China and Azure global support different sets of API versions?
I see from “Resource Explorer” that they are indeed different, could they be the same any time soon?

identity

@cuijun-1993 It is a known issue, so I close it first. Please refer to issue #22661 for details

@cuijun-1993 you can use 2.37.0 now. The mentioned api version got rollout out to mooncake last week.


feat: bitverseWallet

Changes

Added bitverseWallet

Releated discussion: https://github.com/rainbow-me/rainbowkit/discussions/1867


feat: add UI tests workflow

Description

Created workflows for testing suite of the website .
This would thus automate the entire testing suite as soon as a PR is created on AsyncAPI website .
Checked this branch on my local fork

Related issue(s)
fixes #2083

I wish I could have asked for a review from @derberg 😄 . He is the best person for reviewing github actions and workflows.

/rtm


use http version 9

Summary
Bump to http api version 9
the only change from v8 to v9 were adding thread channels to gateway events
and there's no http api differences between v8 to v9

Checklist

[x] If code changes were made, then they have been tested

[ ] I have updated the documentation to reflect the changes
[ ] I have formatted the code properly by running pre-commit run --all-files

[ ] This PR fixes an issue
[ ] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

We should check if all endpoints work correctly with this http version. If I remember correctly there was a problem with bulk message delete endpoints

Odd, the changelog doesn't specify anything different. https://discord.com/developers/docs/change-log#api-v9


MFMA + LocalSplitU(LSU) support, plus small optimizations

added support for MFMA + LocalSplitU (only 2 or 4 can be used)
extended the range of GlobalSplitU to 4096 (to support larger DepthU with LSU)
extended the range of StaggerUStride to 2048 (to support larger DepthU with LSU)
improved the reject condition of DirectToVgpr + MIWaveGroup to cover LSU case
optimized TailLoop code

set 0 only for A or B instead of setting 0 both

optimized complex data type related code

removed redundant negation code for complex type
removed extra fixed vgpr allocation for alpha calculation. Use temporary vgpr instead.
unified CGEMM and ZGEMM code in MulMIoutAlphaToArch

optimized ShiftVectorComponents code to remove redundant mov for permute in case src and dst are the same vgpr
removed redundant shift code (0 bit shift)
optimized ComputeStoreVgprsMFMA to remove * 1 code when MIWG0=1
optimized cmp_lt + v_cndmask code to use v_min instead
added reject condition for LSU + DirectToLds
added reject condition for LSU + StoreCInUnroll
fixed typo
added test cases for MFMA + LSU in extended folder

This is a big PR, There's a few unrelated changes here that could have been separate PRs (better for reviewing, testing, debugging, error tracking). This will change some aspects of already tuned kernels. Have you tried running rocblas tests with these changes?

I have not tried rocblas yet.
These optimizations (except for MFMA+LSU) are basically removing redundant instructions.
From performance point of view, I do not expect it makes performance worse.
Additional optimizations are not much big. If necessary, I can create a separate PR for additional optimization part.

This is a big PR, There's a few unrelated changes here that could have been separate PRs (better for reviewing, testing, debugging, error tracking). This will change some aspects of already tuned kernels. Have you tried running rocblas tests with these changes?

I have not tried rocblas yet. These optimizations (except for MFMA+LSU) are basically removing redundant instructions. From performance point of view, I do not expect it makes performance worse.
Additional optimizations are not much big. If necessary, I can create a separate PR for additional optimization part.

Updated. I removed extra optimization.

The gfx90a extended failed last time (number 2).
I re-ran it and it passed this time (number 3).
I tried to reproduce the fail on my local node many times, but it all passed.
The fail is not reproducible.


Improvements for layout generation

Changes for layout generation, once the initial code is done:

Factor code as bin_prot_layout, ppx_bin_prot_layout, so the layouts for user types are generated by [@@deriving bin_prot_layout]. Then ppx_version generates layouts for the versioned types by calling code in bin_prot_layout.
Use pointer equality for basic types, i.e. use the Int rule if bin_read_t == bin_read_int, for example. These checks happen at module load time. This change requires that layouts be generated after bin_io code is generated, uncertain whether that can be forced.

Per this earlier discussion: https://discuss.ocaml.org/t/enforcing-order-of-ppx-rewrites/4283, it doesn't seem possible to enforce the order of ppx rewrites.
A solution would be to fork ppx_bin_prot, and add the user-type layout generation there. Then ppx_version would add a layout for the versioned type.


Compiler panics when implementing the NoteInterface

Aim
use dep::aztec::{
    prelude::{AztecAddress, NoteHeader, NoteInterface, PrivateContext},
    protocol_types::{constants::GENERATOR_INDEX__NOTE_NULLIFIER, grumpkin_point::GrumpkinPoint, hash::poseidon2_hash},
    note::utils::compute_note_hash_for_consumption, oracle::unsafe_rand::unsafe_rand,
    keys::getters::get_nsk_app
};

global TOKEN_NOTE_LEN: Field = 3;

#[aztec(note)]
struct TokenNote {
    amount: U128,
    npk_m_hash: Field,
    randomness: Field,
}

impl NoteInterface<TOKEN_NOTE_LEN> for TokenNote {
    fn compute_nullifier(self, context: &mut PrivateContext) -> Field {
        let note_hash_for_nullify = compute_note_hash_for_consumption(self);
        let secret = context.request_nsk_app(self.npk_m_hash);
        poseidon2_hash([
            note_hash_for_nullify,
            secret,
            GENERATOR_INDEX__NOTE_NULLIFIER as Field,
        ])
    }

    fn compute_nullifier_without_context(self) -> Field {
        let note_hash_for_nullify = compute_note_hash_for_consumption(self);
        let secret = get_nsk_app(self.npk_m_hash);
        poseidon2_hash([
            note_hash_for_nullify,
            secret,
            GENERATOR_INDEX__NOTE_NULLIFIER as Field,
        ])
    }

    fn broadcast(self, context: &mut PrivateContext, slot: Field, ivpk_m: GrumpkinPoint) {
      if !(self.amount == U128::from_integer(0)) {
          context.encrypt_and_emit_note(
              (*context).this_address(),
              slot,
              Self::get_note_type_id(),
              ivpk_m,
              self,
          );
      }
    }
}

Expected Behavior
No error, the code should compile.
Bug
The application panicked (crashed).
Message:  called Result::unwrap() on an Err value: ["TOKEN_NOTE_LEN"]
Location: aztec_macros/src/transforms/note_interface.rs:102
This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at https://github.com/noir-lang/noir/issues/.
If there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml
To Reproduce

Start a new Aztec project with aztec-nargo new
Copy the Aim code in main
run aztec-cargo compile

Project Impact
Blocker
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
Binary (noirup default)
Nargo Version
nargo version = 0.30.0 noirc version = 0.30.0+48d9df4ff227c08a6e66f21c0286bc6349151671
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

You are putting this code into main.nr?
You should put your contract into main.nr and import any new types into your contract. You can see the token contract folder for an example.

We should avoid panicking in this case but this code is temporary and will be removed when Noir has proper macro support

You are putting this code into main.nr?
You should put your contract into main.nr and import any new types into your contract. You can see the token contract folder for an example.

I put it in main for example purposes. Putting it in a folder gives the same error.

fyi @Thunkar as this seems to be an issue inside aztec_macros.


Follow-up: increment hf_hub for Sentence Transformers

Hello!
Pull Request overview

Also increment huggingface_hub for Sentence Transformers

Details
Apologies, forgot to increment this one alongside #381.
cc @osanseviero

Tom Aarsen

Let me chase down the test failure

@tomaarsen don't dive too much. If it works locally for you, this one could be just the CI having issues with docker which sometime happens (only if it passes locally)

@Narsil No, I don't have a test pass locally, but that is because the test suite does not work on Windows as far as I can tell. I receive httpx.ConnectError: [WinError 10061] No connection could be made because the target machine actively refused it for Sentence Transformers as well as e.g. SpanMarker.
I've been able to run it with python manage.py start though.

In my experience it's usually to some time-outs/test flakiness we need to fix. Let's merge ahead :)


Autoplay causing auto-restart when src is changed and playing=true

If you change the source while playing=true, and then you pause and play again, you will notice the song restarts every time that you pause and replay.
To fix this simply remove autoplay from initHowler(). It's not actually required because you call toggleHowler() right after which will handle "autoplaying" the track.
  initHowler (props = this.props) {
    this.destroyHowler()
    if (typeof Howl !== 'undefined') { // Check if window is available
      this.howler = new Howl({
        src: props.src,
/* -       autoplay: props.playing,    <-- Remove me!      */
        mute: props.mute,
        loop: props.loop,
        onend: props.onEnd,
        onplay: props.onPlay,
        onpause: props.onPause,
        onload: props.onLoad,
        onloaderror: props.onLoadError
      })
    }
  }

You can see a fork of the repo in which I made the change here: https://github.com/karlfloersch/react-howler -- I didn't submit a PR because I messed with the repo to get npm i --save https://github.com/karlfloersch/react-howler.git to work.

Thanks for pointing this out. I'll make a fix asap as well as install from github so you won't need to mess around with the repo

Is there any solution to keep autoplay?

I think that autoplay actually still works in that if you set playing=true when the file is loading. It's just that it doesn't use the autoplay feature of Howler. Though I could be wrong about this, I'm not completely sure what Howler's autoplay does

Do you think this is a Howler's bug? I dont understand howler codebase either

Honestly not sure. It definitely could be though but would require further investigation.

@karlfloersch, @thangngoc89
I've been playing around with this today and I can definitely reproduce what you're reporting. Through some console debugging, it seems that the seek position gets stuck on the first position that's paused no matter what you do.
Example:

Auto play first file
Switch src to a new file
Pause (Pos === 1.5)
Play (Pos === 1.5 but audio actually restarts)
Pause again in a different position (still Pos === 1.5)

I also tried to reproduce this in Howler with a JSBin and it seems to work there.
I need to retire for the afternoon but wanted to put some findings and my bin on here in case anyone else has ideas what could be causing this.

@Stenerson this looks like a howler bug than our wrapper. Could you file a issue in howler repository?

@thangngoc89 That's what I thought at first too but my JSBin above basically replays exactly what we're doing in pure Howler and it seems to work fine.
That being said, I think I fixed the bug by not setting autoplay and just starting the audio after loading it. This is basically how Howler itself does autoplay so I don't see an issue with it.
  /**
   * Create howler object with given props
   */
  initHowler (props = this.props) {
    this.destroyHowler()
    if (typeof Howl !== 'undefined') { // Check if window is available
      this.howler = new Howl({
        src: props.src,
        mute: props.mute,
        loop: props.loop,
        onend: props.onEnd,
        onplay: props.onPlay,
        onpause: props.onPause,
        onload: props.onLoad,
        onloaderror: props.onLoadError
      })

      // Start playing if props.playing is true
      if (props.playing) {
        this.play()
      }
    }
  }

Before committing I'd like to figure out why this is happening though.

Ah. Thanks for clarify that. I'm fine with the workaround. But if you can find out about the root of the problem that's awesome

I've isolated the issue to be that we're calling play() immediately after invoking autoplay. If I don't call play() right after initializing, everything works great. I was also able to reproduce this in my (JSBin) as well by calling play() after auto starting.
I'm going to open a Howler bug but we can also play a little more nicely with Howler by changing componentWillReceiveProps() to not toggleHowler when the src is changing.
  componentWillReceiveProps (props) {
    if (props.src !== this.props.src) {
      this.initHowler(props)
    } else {
      this.toggleHowler(props) // Moved this into an else rather than always calling it
    }
  }

Awesome !!

FYI - Opened goldfire/howler.js#107


Provide an option to skip loading images

Currently, fastgltf loads external images if you specify the option fastgltf::Options::LoadExternalBuffers. An image is not a buffer. Loading images and loading buffers should be separate options

Fixed with 1f79edc.


ISSUE: The eyeball has an inconsistent hitbox

Touching its feet does not damage you

the collider size has been fixed


Corrected typo

Just a little bit typo

Checklist

Issue number for this PR: #nnn (required)
Docs included?: (yes/no; required for all API/functional changes)
Test units included?: (yes/no; required)
e2e tests included?: (yes/no; required for multi-function/multi-class changes)
In a clean directory, npm install, npm run build, and npm test run successfully? (yes/no; required)

Description

Code sample

@jofftiquez make sure you sign the CLA and then reply back here that you've done it. I don't think the PR can be merged without it.

@markgoho done. thanks! :)


logobserver and dashboard.py can't be stopped using SIGINT, and must be killed

Currently the logobserver and dashboard can't be stopped using Ctrl-C. This should be fixed by terminating any running subprocesses and cleaning up upon receiving SIGINT.

Not urgent for this to be fixed at present, not working on it anymore.


Plugin upgrade path from versions prior to OpenSearch 1.0.0

As part of getting the plugins ready for backwards compatibility the last of the items on https://github.com/opensearch-project/opensearch-plugins/issues/12 are:

[ ] Run in a backwards compatible way on top of OpenSearch 1.0 that has joined an ODFE 1.13.x cluster
[ ] Run in a backwards compatible way on top of OpenSearch 1.0 that has joined an ES 7.10.x cluster

As 1 and 2 are very similar, to break down the problem we'll focus on 1.
We see 2 different upgrade paths:

In place upgrade: A node running ODFE/ES with a plugin is shutdown and OpenSearch with the plugin is started.
Rolling upgrade, Blue/Green: A cluster running ODFE/ES will be joined by OpenSearch node, replicate context and data.

In order to perform and verify this backwards compatibility during upgrades plugins need to have a way to test these scenarios.
Ref: OpenSearch does this today with Bwc tests. Eg: https://github.com/opensearch-project/OpenSearch/blob/main/qa/mixed-cluster/build.gradle

We did mixed cluster test Elasticsearch 7.x and OpenSearch 1.x without any plugins. The OpenSearch node doesn’t join the cluster due to an open issue: https://github.com/opensearch-project/OpenSearch/issues/669

Related issue after this is taken care of is: https://github.com/opensearch-project/opensearch-build/issues/42

I have tested manually using these steps:
Restart Upgrade:

Install ODFE in single node cluster
Make sure this ODFE cluster works (along with plugins)
Index some data and a sample plugin feature
Disable the shards.
Bring down the ODFE cluster
Upgrade to OpenSearch
Make sure this OpenSearch cluster works (along with plugins)
Verify the index data on ODFE is searchable in OpenSearch.

Rolling Upgrade:

Install ODFE in 3 nodes (at the least)
Make sure this ODFE cluster works (along with plugins)

Index random test data
Random search test data w/ assertThat validation
Add cluster setting from one of the plugin (AD)

Disable shard allocation of replicas (set cluster.routing.allocation.enable to primaries)
Ensure nothing is being indexed (stop any test indexing threads)
Flush all indexes / data streams (e.g., POST /_flush)
Bring down one node and Upgrade this node to OpenSearch
Restart the node and wait for it to join the quorum
Make sure the mixed cluster works (along with plugins). Cluster is GREEN
Repeat the activity for other ODFE nodes
Final testing ( after all the nodes are upgraded to OpenSearch ) verify that the search results, cluster settings from the plugin as expected.

I think we should close this, @saratvemulapalli ?

Agreed. I'll open a new one for automated tests.

Reopening this as indexing during rolling upgrades is not supported and potentially will impact Alerting, AD etc

I have tested manually using these steps:
Restart Upgrade:

Install ODFE in single node cluster
Make sure this ODFE cluster works (along with plugins)
Index some data and a sample plugin feature
Disable the shards.
Bring down the ODFE cluster
Upgrade to OpenSearch
Make sure this OpenSearch cluster works (along with plugins)
Verify the index data on ODFE is searchable in OpenSearch.

Rolling Upgrade:

Install ODFE in 3 nodes (at the least)

Make sure this ODFE cluster works (along with plugins)

Index random test data
Random search test data w/ assertThat validation
Add cluster setting from one of the plugin (AD)

Disable shard allocation of replicas (set cluster.routing.allocation.enable to primaries)

Ensure nothing is being indexed (stop any test indexing threads)

Flush all indexes / data streams (e.g., POST /_flush)

Bring down one node and Upgrade this node to OpenSearch

Restart the node and wait for it to join the quorum

Make sure the mixed cluster works (along with plugins). Cluster is GREEN

Repeat the activity for other ODFE nodes

Final testing ( after all the nodes are upgraded to OpenSearch ) verify that the search results, cluster settings from the plugin as expected.

Did the above test is with security enabled?

I have tested manually using these steps:
Restart Upgrade:

Install ODFE in single node cluster
Make sure this ODFE cluster works (along with plugins)
Index some data and a sample plugin feature
Disable the shards.
Bring down the ODFE cluster
Upgrade to OpenSearch
Make sure this OpenSearch cluster works (along with plugins)
Verify the index data on ODFE is searchable in OpenSearch.

Rolling Upgrade:

Install ODFE in 3 nodes (at the least)

Make sure this ODFE cluster works (along with plugins)

Index random test data
Random search test data w/ assertThat validation
Add cluster setting from one of the plugin (AD)

Disable shard allocation of replicas (set cluster.routing.allocation.enable to primaries)

Ensure nothing is being indexed (stop any test indexing threads)

Flush all indexes / data streams (e.g., POST /_flush)

Bring down one node and Upgrade this node to OpenSearch

Restart the node and wait for it to join the quorum

Make sure the mixed cluster works (along with plugins). Cluster is GREEN

Repeat the activity for other ODFE nodes

Final testing ( after all the nodes are upgraded to OpenSearch ) verify that the search results, cluster settings from the plugin as expected.

Did the above test is with security enabled?

No this was without security plugin. Infact all the plugins were purged and installed Job-Scheduler, AD.

Closing this as the fix in security is merged.


Modified the dell and cisco drivers to fix the deployment tests.

Collaborative effort with @zenhack
Fixes #740

I feel like I shouldn't be a reviewer on this, since as @naved001 says we both hacked on this. I'm going to assign some other folks.

@naved001 can you provide more information on what was wrong and how you fixed it?

@zenhack  - since you guys wrote this together, I think it's totally appropriate for you to act as a reviewer, since presumably you were reviewing this as you wrote it.

Both, the dell and cisco, drivers were timing out when running the tests.
In the dell driver, pexepct times out when we try to gather information for an interface because it waits for the "user" to press a key. Because the regex was too strict, it wouldn't find a match and the call would timeout. So what we have done is made the regex pattern to be matched more relxed (Line 165).
The other issue with it was how it was building a dictionary containing the interface information. It was a hodgpe podge because of the timing issues, so changing the pattern here fixes this (Line 173).
In the nexus driver, sometimes the switch can have "custom" interface names and when it doesn't match what we expect it crashes, so we changed it so that continues to run when it encounters such a situation. (Line 159 and 160)
Also, the name of the switch that the port returns is "Ethernet" with a capital 'E', but we were checking for "ethernet" with a small 'e' so we couldn't find a match. (Line 164).

@shwsun could you review this? it's a small PR. Thanks!

Thanks for the explanation to give us the context, could you also update the doc a bit @naved001 ? I will run the test on devhaas and +1 soon.

@shwsun I don't know what to put about this in the documents because we don't really describe the driver code anywhere. The commit message has a detailed explanation of what this change is about, which I think is sufficient.

Checked the code. Ran tests, passing all deployment tests.
+1

merging.


Execute action without closing menu?

Hey, first of all, thanks a lot for putting the effort into creating this project. It is fantastic, and super useful for my workflow ❤
I wanted to ask if it is possible to execute an action without closing MenuHammer.
Here are different examples of use cases:
Volume control menu
E.g., a menu that can be opened with Option + Space -> V, and then:

Allows increasing volume with m
Allows decreasing volume with n

This is important because if not, one would need to open it constantly with Option + Space -> V
Window scaling/moving menus
E.g., some menus that can be opened with Option + Space -> W -> S/M, and then:

Scale/move left with h
Scale/move down with j
Scale/move up with k
Scale/move right with l

These are just some examples but I believe that a feature could be useful. Maybe it is possible already and I'm just not smart enough to figure it out 😅
Anyways, thanks again!

Hi Nick, I'm glad you liked it.  Looks like I didn't document this but you can do this by adding "true" as a 6th argument to the menu action.
E.g. from my personal config:
            {cons.cat.action, '', 'K', "Volume Up 10%", {
                 {cons.act.mediakey, "adjustVolume", 10}},
             true,
            },

Thanks! I've just opened a PR to document it :)


Added code and dependencies for ViT for Image classfication

Fixes issue :
#111
Kindly review and merge the PR.

Thanks for Contributing! 🎉  Please leave a Star on this Repository!


Mention that the fish bug has been fixed

https://github.com/fish-shell/fish-shell/pull/3922

Thanks.


Urbansound8K dataset give an error loading data

RuntimeError: Only 16 and 32 bits are supported for signed PCM.

Hi,
from where you've downloaded the dataset? can you post a link?

I downloaded it from the official website: https://urbansounddataset.weebly.com/urbansound8k.html , after finishing the Download form.

sorry for the late response. i've used the samples from KAGGLE - https://www.kaggle.com/datasets/chrisfilo/urbansound8k
verified that they are readable using soundfile, librosa, and torchaudio
i need to fulfil some application to weebly in order to download it and i expect it will take several days. so for now the fastest solution will be to use the kaggle link
Avi


docs: Label PRs and split them up in the release notes

🙋 Documentation Request

Release notes are not readable
💁 Possible Solution

Label PRs and split the release notes up in sections for Breaking Changes, Features, Fixes, and Other, like seen in MudBlazor

We do that (more or less) on the docs site now since a couple of versions: https://fluentui-blazor.net/WhatsNew.
We figure a lot more people go there instead of going to the GH releases page. We can work on using that same website format here as well. Would that be better?

Closing due to inactivity. As said we will use the What's New format going forward (just list PRs that have been merged, split in docs and demos, components and misc, new components highlighted)


Potential fix for #997

I'll like to wait for at least @emacarron to review this as he introduces that check for a different issue.
I'm not quite comfortable relaying on automapping behaviors to control this.
Another possible fix is how we decide what has setMethods in Reflector.
I don't see why final fields are in there other than for the use case of maybe auto incremented db ids.
But that could be solved by adding an appropriate constructor.
#997

Hi Tim. Just to let you know I have started to have a look at the issue. If I had known it was about automapping and constructors and would't not have told you that I will look at it!! ;)
My first thought is that MyBatis is working OK by default. It creates the Parent object with constructor mappings and next, given that automapping is on, it automaps.
What is probably unexpected is that this works in the opposite way than property mappings. With propperty mappings automappings are done first and explicit mappings second, so undesired values may be overwritten. With constructors this order is not possible and happens the opposite (automappings are overwriting explicit values).
Give me please some more time to think about this.

Hi Tim,
After thinking about this a bit more I think we should not apply the change. I know that the behaviour may be unexpected but it is consistent.
However I think there may be an inconsistence with "nested" result maps and using constructors. This is not related to this issue at all.
A nested resultmap would make MyBatis to build an object tree out of the content of several lines. In this case ChildResultMap is considered nested, but... is that right?
  <resultMap id="ChildResultMap" type="org.apache.ibatis.submitted.constructor_args_997.Child">
    <constructor>
      <idArg column="id" javaType="java.lang.String" jdbcType="VARCHAR"/>
      <arg column="name" javaType="java.lang.String" jdbcType="VARCHAR"/>
      <arg resultMap="ParentResultMap" javaType="org.apache.ibatis.submitted.constructor_args_997.Parent"/>
    </constructor>
  </resultMap>

It has a property with a resultmap indeed so looks nested but when using constructors we can just fill simple relations, not collections. So that object won't get any new objects when processing the rest of the ResultSet rows. There is no point in calculating cache keys for that resultmap because they will never be used.

Thanks for taking the time to look at it @emacarron !

With constructors this order is not possible and happens the opposite (automappings are overwriting explicit values).

This is the problem that I tried to address with this but that isn't obvious to solve. Being able to choose if you want to enable or disable automapping per nestedResultMap (similar to @kazuki43zoo's comment in #997) might be better? Maybe if you could do it inline with the arg declaration and not on the actual resultmap being nested.
For example: @kazuki43zoo offered
<resultMap id="ParentResultMap" type="dto.Parent" autoMapping="false">

I would propose
    <constructor>
      ...
      <arg resultMap="ParentResultMap" javaType="org.apache.ibatis.submitted.constructor_args_997.Parent" autoMapping="false"/>
    </constructor>

What do you think?
One thing I'm confused by:

A nested resultmap would make MyBatis to build an object tree out of the content of several lines. In this case ChildResultMap is considered nested, but... is that right?

In the fix case. ChildResultMap isn't nested. It's the ParentResultMap that is nested. From what you did in shouldApplyAutomaticMappings specifying it as such allows it to skip the automapping. But I do understand that this makes it inconsistent with the above

I'm going to close this and think about it more.
There's an unrelated issue with how shouldApplyAutomaticMappings works that is breaking how I want to get results in even the nonnested, constructor mapping case that is due to the logic in this method.


[Failing Test]: BigtableIOWriteTest::test_bigtable_write is about 50% flaky

What happened?
From  https://github.com/apache/beam/issues/30867#issuecomment-2048454045 and below, it appears that BigTable client initialization sometimes gets stuck and holding GIL indefinitely in:
Traceback for thread 100 (python) [Has the GIL] (most recent call last):
    (Python) File "/usr/local/lib/python3.8/threading.py", line 890, in _bootstrap
        self._bootstrap_inner()
    (Python) File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
        self.run()
    (Python) File "/usr/local/lib/python3.8/threading.py", line 870, in run
        self._target(*self._args, **self._kwargs)
    (Python) File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 80, in _worker
        work_item.run()
    (Python) File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
        result = self.fn(*self.args, **self.kwargs)
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable/batcher.py", line 385, in _flush_rows
        response = self.table.mutate_rows(rows_to_flush)
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable/table.py", line 724, in mutate_rows
        self.name,
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable/table.py", line 160, in name
        table_client = self._instance._client.table_data_client
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable/client.py", line 332, in table_data_client
        transport = self._create_gapic_client_channel(
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable/client.py", line 285, in _create_gapic_client_channel
        channel = grpc_transport.create_channel(
    (Python) File "/usr/local/lib/python3.8/site-packages/google/cloud/bigtable_v2/services/bigtable/transports/grpc.py", line 217, in create_channel
        return grpc_helpers.create_channel(
    (Python) File "/usr/local/lib/python3.8/site-packages/google/api_core/grpc_helpers.py", line 386, in create_channel
        return grpc.secure_channel(
    (Python) File "/usr/local/lib/python3.8/site-packages/grpc/__init__.py", line 2119, in secure_channel
        return _channel.Channel(
    (Python) File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 2046, in __init__
        self._channel = cygrpc.Channel(

Repro:
python -m pytest  -o log_cli=True -o log_level=Info apache_beam/examples/cookbook/bigtableio_it_test.py::BigtableIOWriteTest::test_bigtable_write   --test-pipeline-options='--runner=TestDataflowRunner --project=apache-beam-testing --temp_location=valentyn-testing  --region=us-central1 --wait_until_finish_duration=36000000' --timeout=36000

I wasn't able to repro the error locally outside of Dataflow context.
cc: @mutianf FYI given that BT client is involved. It might be a wider issue, as discussed in https://github.com/apache/beam/issues/30867 and https://github.com/grpc/grpc/issues/36256.
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components

[x] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[x] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

@mutianf Can you check this?

gdb backtrace of the stuck that thread holds up GIL:  https://github.com/grpc/grpc/issues/36256#issuecomment-2052729097

fixed in https://github.com/apache/beam/pull/31044


BUG - All Xero Dbt jobs failing due to missing table

Are you a current Fivetran customer?
Yes. Shubham Sinha, Head of Engineering, Daydream
Describe the bug
dbt run fails since, table credit_note doesn't exist for three separate accounts. There are no config vars that I could use to add a true/false flag to skip this table.
Attaching Bug report from dbt run:
Database Error in model stg_xero__credit_note_tmp (models/tmp/stg_xero__credit_note_tmp.sql)
  relation "trainwithkickoff_39_xero.credit_note" does not exist
  LINE 4:     select * from "cloud_services"."trainwithkickoff_39_xero...
                            ^
  compiled SQL at target/run/xero_source/models/tmp/stg_xero__credit_note_tmp.sql

Steps to reproduce
Hard to reproduce this locally unless you have the same setup (account, tables) but I believe the bug description should have all the details.
Expected behavior
Possible to create some config vars that can be used to skip this table?
Project variables configuration

vars:
  xero_schema: trainwithkickoff_39_xero
  xero_database: cloud_services

models:
  xero:
    +schema: transformations

Package Version
packages:
  - package: fivetran/xero
    version: 0.1.1

Warehouse

[ ] BigQuery
[ ] Redshift
[ ] Snowflake
[X] Postgres
[ ] Databricks
[ ] Other (provide details below)

Additional context

Screenshots
Attaching all the tables synced from Account 1 (Real production users):

Attaching all the tables synced from Account 2 (Real production users):

Please indicate the level of urgency
It's pretty critical for us as it affects several Production users.
Are you interested in contributing to this package?

[ ] Yes, I can do this and open a PR for your review.
[X] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed.
[ ] No, I'd prefer if someone else fixed this.  I don't have the time and/or don't know what the root cause of the problem is.

Hi @elucidateadmin, thanks for opening this Issue!
Our decision to not include a variable to disable the credit_note models was due to >90% of our customers having this. However, we do not want the other 10% to have their dbt runs fails because they do not have this table. Therefore, I just created a new branch and pushed recent commits to add a variable to disable the credit_note models if a users does not have the source table.
I have tested this on my end and it works, but would greatly appreciate if you had time to test the working branch on a customer of yours and let me know if you see the expected results. You can use the below config within your packages.yml in place of the dependency you currently have for fivetran/dbt_xero.
- git: https://github.com/fivetran/dbt_xero.git
    revision: feature/credit-note-var
    warn-unpinned: false

Additionally, you can use the below config in your variables block to disable the credit_note models.
vars:
    xero__using_credit_note: false

Let me know if you have any issues with the working branch or if you have any questions. Thanks!

Hey @fivetran-joemarkiewicz  your fix worked and I tested it against both of our production accounts! Thanks

@elucidateadmin I just merged the branch and cut a new release of the xero package! The new v0.1.2 release should be live by the end of the day on the dbt hub.
Thanks again for opening this issue and let me know if you encounter any other issues or questions!


Fixed build.gradle fixes and removed unused tests

@doneill Can you review?  This fixes existing issues with master.

@zinfin This looks good to merge!


remove ones and zeros from pyro utils

There seems to be a merge conflict with dev.

ready to merge

looks like i got commit #1000 do i win a prize