[LV] Add Latvian binary sensor get state translations

Added sentences and tests for Latvian language binary sensor get state functionality.
The PR and translations are heavily inspired by English language implementation.

Summary by CodeRabbit

New Features

Enhanced the HassGetState intent in Latvian (lv) to include new response variations (one_yesno, any, all, which, how_many) based on query context.
Introduced comprehensive intents for querying states of various binary sensors (battery, carbon monoxide, motion, etc.) in home automation.

Bug Fixes

Corrected and updated binary sensor state values to ensure accurate responses for various conditions (e.g., battery, connectivity, door status).

Tests

Added extensive test cases in Latvian for different binary sensor states to validate HassGetState intents and responses.

@makstech Does this look OK to you?


Document which modes work on touch devices

At the moment it is not clear that certain modes do not work on mobile/touch devices - we should look to document this. I would have to double check which modes do not work out the box, but at least Circle mode is not supported (see #106). I would assume rectangle mode suffers the same fate.

Expanding on this, drawing lines/points/polygons doesn't seem to work in Chrome on touch devices - but do in Firefox

Hey @dob9601 thanks for sharing your experience. Could you potentially share more information about this as it doesn't sound intended! I am able to draw points lines and polygons on terradraw.io on Chrome on Android.
Can you share your exact device, OS and browser version so I can investigate? Also which adapter are you using Terra Draw with?

Hey,
A friend and I came across the behaviour when looking at the demo hosted on the terradraw docs (https://terradraw.io/). On both devices, the behaviour was identical with it working on Firefox (Android) but not Chrome (also Android).
I'm running Chrome 120.0.6099.144 on Android 14 (Pixel 7)

https://github.com/JamesLMilner/terra-draw/assets/24723950/8a54e63e-7dea-4e7f-ad73-69c57dbec99f

@dob9601 this is strange! Thank you for the info and the video, very helpful. I am also running Chrome 120 on Android and not seeing this issue weirdly. Let me do some more digging and get back to you. If you have any additional information you may help to debug please feel free to share in the meantime :)

@dob9601 this is strange! Thank you for the info and the video, very helpful. I am also running Chrome 120 on Android and not seeing this issue weirdly. Let me do some more digging and get back to you. If you have any additional information you may help to debug please feel free to share in the meantime :)

Not a problem! Feel free to reach out if you need any specific debug information

@dob9601 going to move this out a separate dedicated issue :)  #153

I've looked into this and it appears that Great Circle and Freehand are not supported on mobile. Also Rectangle and Circle mode, although working, do not have as nice a UX as when using a mouse. I think supporting Great Circle shouldn't be too complicated, however freehand may require more thought. We could also potentially think about how we improve the UX for Rectangle and Circle mode going forward.


xWebAppPool does not implement the write property autoStart mentioned in the corresponding MOF schema file MSFT_xWebAppPool.schema.mof

I suddenly started seeing below issue in one of our environments. We did couple of deployments and we never had any issues. This is the first time.
we are using xWebAdministration ModuleVersion = '<IP_ADDRESS>'
The command Test-TargetResource of the PS module MSFT_xWebAppPool does not implement the write property autoStart mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules\xWebAdministration\DscResources\MSFT_xWebAppPool\MSFT_xWebAppPool.schema.mof. All write paramenters mentioned in the schema file must be implemented by the command Test-TargetResource.
CategoryInfo :InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
FullyQualifiedErrorId :WriteParameterNotImplemented
---> Microsoft.Management.Infrastructure.CimException: The command Test-TargetResource of the PS module MSFT_xWebAppPool does not implement the write property autoStart mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules\xWebAdministration\DscResources\MSFT_xWebAppPool\MSFT_xWebAppPool.schema.mof. All write paramenters mentioned in the schema file must be implemented by the command Test-TargetResource.
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase1.ProcessNativeCallback(OperationCallbackProcessingContext callbackProcessingContext, T currentItem, Boolean moreResults, MiResult operationResult, String errorMessage, InstanceHandle errorDetailsHandle)    --- End of inner exception stack trace ---    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable)    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute(Action action)    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.DeploymentService.RunPowerShellScripts(DeploymentMachineSpecification deploymentMachine, ScriptSpecification scriptSpecification, ScriptSpecification initializationScriptSpecification, String applicationPath, IPowerShell powerShellSession) ---> (Inner Exception #0) Microsoft.Management.Infrastructure.CimException: The command Test-TargetResource of the PS module MSFT_xWebAppPool does not implement the write property autoStart mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules\xWebAdministration\DscResources\MSFT_xWebAppPool\MSFT_xWebAppPool.schema.mof. All write paramenters mentioned in the schema file must be implemented by the command Test-TargetResource.    at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase1.ProcessNativeCallback(OperationCallbackProcessingContext callbackProcessingContext, T currentItem, Boolean moreResults, MiResult operationResult, String errorMessage, InstanceHandle errorDetailsHandle)

I suddenly started seeing this issue in one of our environments. We did couple of deployments and we never had any issues. This is the first time.

Hello, when I've run into this type of issue before a restart of the node tends to fix the issue, unfortunately I've yet to be able to pinpoint the issue but as the code does work otherwise it tends to be an issue on the machine. Please let us know if you are still seeing the issue.

Are you still experiencing this issue? I haven't heard from you in a while. If we don't hear back from you in 7 days, I'll be resolving this issue.

Closing this as per previous comment.


Add rclone restore helm chart

[!warning]
This is public repository, ensure not to disclose:

[x] personal data beyond what is necessary for interacting with this pull request
[x] business confidential information, such as customer names

What kind of PR is this?
Required: Mark one of the following that is applicable:

[x] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

This adds a helm chart and release called rclone-restore which basically templates rclone-sync in reverse, with a lot of options to be able to patch the config of any providers and the crypt backend.

Fixes #1849
Fixes #1931

Additional information to reviewers
This requires Helmfile v0.162.0 (which I'm currently testing to see if breaks anything but so far so good), and this allows the providers to become templates that we could use for rclone-sync. This includes Azure Blob Storage support OOTB, so with some refactor rclone-sync could get that too.
Screenshots
Checklist

[x] Proper commit message prefix on all commits

Change checks:

[ ] The change is transparent
[ ] The change is disruptive
[ ] The change requires no migration steps
[ ] The change requires migration steps

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packages in the NetworkPolicy Dashboard

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Bug checks:

[ ] The bug fix is covered by regression tests

Question to reviewers:

Do we think it would be easier to have them as cronjobs and you would have to run the job manually?

Currently it is running as jobs so all will be triggered at the same time, which perhaps not the easiest to manage.

I just realised that if we do this we could rework it so that the values template generates the crypt backends and sets appropriate targets, then we could have just one chart.

What do you think would be easiest to manage? One chart per feature or one that does both?

I just realised that if we do this we could rework it so that the values template generates the crypt backends and sets appropriate targets, then we could have just one chart.

What do you think would be easiest to manage? One chart per feature or one that does both?

One for both, the complexity to support the roles will be in the helmfile values templates (auto-generating crypt backends and setting up targets), and the helm chart will basically only know how to run rclone. The template to setup azure/s3/swift backends are already sharable so it just need to include it.
We decided on the standup that we will go the cronjob route anyway so I'll set it up and people can review it.

I'll split this PR since it expanded a bit in scope.


Replace tt_lib in sweeps, integration_tests

Tracking Issue : https://github.com/tenstorrent/tt-metal/issues/11242 , Master Issue : https://github.com/tenstorrent/tt-metal/issues/10532
https://github.com/tenstorrent/tt-metal/pull/11556

https://github.com/tenstorrent/tt-metal/pull/11556 merged


能否接入 DALL·E 2 模型

如题

界面不好放，除非改界面，而且这个接口是信用卡收费的

https://platform.openai.com/docs/guides/images/introduction
根据官方文档 应该不收费
The Images API is in beta. During this time the API and models will evolve based on your feedback. To ensure all users can prototype comfortably, the default rate limit is 50 images per minute. If you would like to increase your rate limit, please review this help center article. We will increase the default rate limit as we learn more about usage and capacity requirements.

不太懂前端。 如果界面不好改， 能不能加一个单独的path 然后去图片的页面呢

有兴趣可以单独开个project，这个专注把聊天做好就好，不然太重了。


MockDisplay panic now prints which row width is incorrect

Hi! Thank you for helping out with Embedded Graphics development! Please:

[ ] Check that you've added passing tests and documentation
[ ] Add a simulator example(s) where applicable
[ ] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, etc) and appropriate crate (embedded-graphics, simulator, tinytga, tinybmp) if your changes affect the public API
[ ] Run rustfmt on the project
[ ] Run ./build.sh (Linux/macOS only) and make sure it passes. If you use Windows, check that CI passes once you've opened the PR.

PR description
I'm not sure if this wording is acceptable, but I find it useful to print which row actually failed the validation.
Also add a dimension to the other panics, just to be overly pedantic.

To be fair, I hit this with 0.6.2 where the error message wasn't at all helpful:
thread 'layout::test::test_view_location_preserved' panicked at 'assertion failed: `(left == right)`
  left: `6`,
 right: `7`', C:\Users\bugad\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib/rustlib/src/rust\src\libcore\macros\mod.rs:16:9

The master version at least hints what this panic is about, but I think we can do better by pointing at the exact row that's incorrect.


modify jenkinsfile and docker file for 90a

Jenkins log contains: Method Code Too Large Error
Here are some potential options to resolve this issue:

Limit the size of the Jenkinsfile code inside of the brackets by moving code out to shared libraries, or external scripts you call with a sh './myscript' command, as per Pipeline Best Practices
Move sections of the Jenkinsfile code out into their own separate methods by doing a groovy method declaration: def $METHOD_NAME(arguments...){}
Use the startup argument org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true as mentioned in JENKINS-56500

Option number 2 is not suitable for us, since we have already made the code into separate methods.
The simplest would be the 3-rd. But the changes will affect all projects on the Jenkins server

@shaojiewang this branch has been squashed and rebased, please delete your local branch, re-pull and start from there :) thanks!

@shaojiewang this branch has been squashed and rebased, please delete your local branch, re-pull and start from there :) thanks!

ok thanks.

@shaojiewang please let the reviewers know when this PR is ready for review. It is currently blocking enabling gfx90a in CI pipeline. Thanks!

@shaojiewang please let the reviewers know when this PR is ready for review. It is currently blocking enabling gfx90a in CI pipeline. Thanks!

OK. working on it now.

I merged develop branch in this PR. It always have a boost error in OpenCL tidy stage. @shurale-nkn could you please help?

Jenkins log contains: Method Code Too Large Error
Here are some potential options to resolve this issue:

Limit the size of the Jenkinsfile code inside of the brackets by moving code out to shared libraries, or external scripts you call with a sh './myscript' command, as per Pipeline Best Practices
Move sections of the Jenkinsfile code out into their own separate methods by doing a groovy method declaration: def $METHOD_NAME(arguments...){}
Use the startup argument org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true as mentioned in JENKINS-56500

Option number 2 is not suitable for us, since we have already made the code into separate methods.
The simplest would be the 3-rd. But the changes will affect all projects on the Jenkins server

Thanks I understand. I removed gfx90a from some non-supported tests.

I got a ci info like below:
There are no nodes with the label ‘rocmtest&&miopen&&gfx90a’

Does it means that we do not have a gfx90a node?

I got a ci info like below:
There are no nodes with the label ‘rocmtest&&miopen&&gfx90a’

Does it means that we do not have a gfx90a node?

Hi @okakarpa, CI pipeline is queued because of the above message. Could you take a look?

I got a ci info like below:
There are no nodes with the label ‘rocmtest&&miopen&&gfx90a’

Does it means that we do not have a gfx90a node?

Hi @okakarpa, CI pipeline is queued because of the above message. Could you take a look?

Since we are in testing phase i named the MI200 node label as rocmtest-trial instead of rocmtest , but i changed the label now the job triggered
http://micimaster.amd.com/job/MLLibs/job/MIOpen/job/jenkins_and_docker_file_for_90a/7/console

Still observing: :(
"[2021-08-12T15:29:43.721Z] gpg: no valid OpenPGP data found."
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jenkins_and_docker_file_for_90a/8/pipeline/56

I made some changes to Docker-file we don't need to enable adding of gpg key if we are setting up rocm through private artifactory
The Docker image is built now and moving forword.
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jenkins_and_docker_file_for_90a/9/pipeline

I think that rocm4-3 is this address:
sh -c 'echo deb [arch=amd64 trusted=yes] http://compute-artifactory.amd.com/artifactory/list/rocm-release-archive-deb/ 4.3 rel-34 > /etc/apt/sources.list.d/rocm.list'

has some issue with boost lib.

seems like http://repo.radeon.com/rocm/apt/.apt_4.3/ xenial main has boost version issue.

@shaojiewang it seems that ROCm 4.3 is required after all, in order to pass unit and future tests. I tried to make build work with ROCm 4.2 but it might not be the right direction :(
Please feel free to revert my changes. Tomorrow I will continue from your work to work on how to make it work with 4.3.
Thanks!

@shaojiewang it seems that ROCm 4.3 is required after all, in order to pass unit and future tests. I tried to make build work with ROCm 4.2 but it might not be the right direction :(

I agree. In this way, we could check whether the other parts of jenkinsfile and dockerfile are right.

Please feel free to revert my changes. Tomorrow I will continue from your work to work on how to make it work with 4.3.

I agree with these changes.
Thanks a lot.

There are no nodes with the label ‘rocmtest-scm-trial&&miopen&&gfx908’

There are no nodes with the label ‘rocmtest-scm-trial&&miopen&&gfx908’

Do you need to test on gfx908 ?

selective (only gfx90a) tests have passed: http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jenkins_and_docker_file_for_90a/55/pipeline
Now starting a full scale test ... if you have local branch of jenkins_and_docker_file_for_90a, please delete and re-pull.

CI-test is re-started and now running.....
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jenkins_and_docker_file_for_90a/59/pipeline/59/


Prefix test title with test location

Fixes #53
Uses figures.pointerSmall to replace / and as a separator between prefix and test title.

@Qix- all good points, I should not submit PRs after 10pm. Will review this again tomorrow, thanks!

Haha no problem; common path stuff.

Added changes to babel.js to detect if generators are supported. If they are supported, babel's gonna use asyncToGenerator transform and blacklist regenerator transform. Before that, tests on 0.10 and 0.12 failed, because they don't support generators.

Lgtm :+1:  @sindresorhus will be the ultimate decider.

The prefixing doesn't seem to work when specifying a direct path:
$ ava test/foo/http.js

  ✔ test title

Expected:
$ ava test/foo/http.js

  ✔ foo › http › test title

@sindresorhus This PR is related to issue #53, which is "Prefix test results with filename when running multiple files". So this output is expected. When running a single test file, I don't think we need prefixes, since direct path is specified.

@vdemedes while I agree that that is sound behavior, I'm with @sindresorhus on it; consistency is important.

Oh right. That makes sense. If only one file, it should not show the path.

Super work @vdemedes. I really like this feature! :)

That gif is life... :baby:


tsp, loadtesting, add visibility=read to FileInfo.fileName

TypeSpec
We've confirmed with TypeSpec dev, that @visibility without any value is not expected and should at least be a warning.
(as, apparently, @visibility without parameter here would not mean this property is not visible)

Service
Mitesh confirmed from service team, that the change of readOnly=true is approparate.

SDK
model TestFileInfo is FileInfo;
model TestRunFileInfo is FileInfo;

TestFileInfo is used in op uploadTestFile as response.
TestFileInfo used in model inputArtifacts?: TestInputArtifacts;, which is a read-only property.
TestRunFileInfo is used in op getTestRunFile is StandardResourceOperations.ResourceRead<TestRunFileInfo>;.
TestRunFileInfo via reference used in testArtifacts?: TestRunArtifacts;, which is a read-only property.
Both model currently only used as output.
(Java code: TestFileInfo, TestRunFileInfo)

There is no impact to SDK, as no model was generated for the previous Swagger based DPG lib.
Data Plane API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Schedule a data plane REST API spec review

Getting help

First, please carefully read through this PR description, from top to bottom.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@weidongxu-microsoft : I saw something interesting, while generating the RLC Javascript Client, it generated the model without this property? Could it be related to the same issue?

@weidongxu-microsoft : I saw something interesting, while generating the RLC Javascript Client, it generated the model without this property? Could it be related to the same issue?

Yes, if you marked a properties as @visibility("read") we will treat it as readOnly and remove it from the input models.

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

Hi Mike,
I would add a BreakingChange-Approved-BugFix label on this PR. I've get feedback from service that this property should be readOnly.
And all of its other properties is already readOnly.
https://github.com/Azure/azure-rest-api-specs/blob/465d3614ef38b4ed3c45bd313035e44a9cad987f/specification/loadtestservice/LoadTestService/models.tsp#L497-L524
And this should be a low impact change, as both TestFileInfo and TestRunFileInfo is not used as input.


dart2js should optimize String.charCodeAt

I think the scanner in dart2js is slow when self-hosting because dart2js doesn't optimize String.charCodeAt.

cps_ir converts String.codeUnitAt to a bounds check and String.charCodeAt.
The bounds check can sometimes be elimiated.
No benchmarks made a statistically significant increase in performance.


Sref 504 deprecate old atlantis and add global to data training account

Adding data-tribe repo on Atlantis orgWhitelist.
Based on request:
https://procoretech.atlassian.net/browse/SREF-504

Wrong remote.


Clean up acceleration Limits

Look holistically at distance minimums and acceleration limits and clean up and centralize.
Need to keep at least some minimum value for r to avoid divide by zero.

For bodies passing close by one another, over acceleration with far less accompanying deceleration can occur because of the size of the steps in the acceleration calculations. When body A and B reach their closest approach they accelerate past one another and then in the next calculation they can be much farther away from each other than they were, resulting in far less deceleration than acceleration, instead of acc and dec being symmetrical.


Running gekko on Node.js server with pm2 process manager

Action taken (what you did)
Tried to start Gekko with this command
pm2 start gekko.js --node-args="--ui"

Expected result (what you hoped would happen)
Gekko process would be running with pm2 and without the need of ssh connection.

Actual result (unexpected outcome)
Gekko did not start and pm2 gives an error
node: bad option: --ui

Without pm2 gekko starts normally and the web UI is useable trough nginx reverse proxy setup.

You can start it like so with pm2:
pm2 start gekko -- --ui

Thanks! This worked :)


Create plan for migrating service: s3

In order for our cloud.gov team to help our users migrate, we need to figure out how each service will get migrated.
Write down:

This is what you have to do to migrate it now without tools

Evaluate:

Can we expect users to do that?

Evaluate:

Do we need to build a tool?

Acceptance criteria:

[ ] We have a tenant-friendly written document somewhere that explains this.
[ ] This document has been vetted by an Atlas team member as usable and workable.
[ ] We've filed next steps as GitHub issues.

This can likely be accomplished via the AWS CLI, or a very simple script around it.

Noting that we'll only do this if a concrete need arises.

From grooming –we're seeing this come up fairly often, so documenting what this would take would be helpful.

No longer necessary.


FEATURE: bosh-cleanup task optionally uses --all

The bosh-cleanup task currently uses --all flag. We would like it if the --all flag was optional.
Our use case is a couple jobs in our pipeline that deploy two different deployments (it tests upgrading from one to the other).  It would be nice if we could run bosh cleanup without the --all option so that the releases for the not-currently-deployed deployment would not get deleted.
Thanks,
Angela & @mcwumbly

Hey @chinangela, this sounds reasonable. Have you verified that removing --all keeps the correct release versions on your BOSH director?

@dsabeti yes, just verified that removing --all keeps the versions we want. In general, it seems to keep the latest 3 releases.

Sounds good. I'll prioritize the story.

@chinangela, take a look at the task now. It supports use of a CLEAN_ALL parameter that you can set to false.

Awesome, thanks a lot!


Modified code to use updated packages from beta.

Updated beta packages. Modified code for updated packages. Fixes to tests.

+1


⚠ Note retirement of this repository

Summary
This PR updates this repository to account for its retirement. The README is updated to say that. This PR deletes the rest of the content, apart from the governance stuff required by CNCF. (Don't worry, it's Git; all the old content is still there in the older commits.)
Related issue(s)

/cc @nirrozenbaum
/cc @waltforme
/cc @ezrasilvera
/cc @pdettori

I suggest also renaming the repo to include suffix - "archived" or something like that.
/lgtm
/approve


Wild Magic Sorcerer "Bend Luck" gives bonuses to opponent's rolls

Unless the little combat stat box is giving out errors, it seems that the Wild Magic Sorcerer's ability "Bend Luck", which should give a bonus to friendly rolls and a penalty to opponent rolls, is giving a bonus to opponent rolls.
I've attached two saved files, one the "Before Bend Luck" save where my cleric is about to hit a big bug with his lightning bolt wand (so before the bug can roll the save for the lightning bolt), and the "After Bend Luck" save where you can see the stat box saying that the Wild Magic Sorcerer gave a BONUS to the bug's save against the lightning bolt.
Before Bend Luck.sav.zip
After Bend Luck.sav.zip

Already fixed in DEV branch, thanks for reporting


Can't install Optimus on Notebook

Describe the bug
I'm using Jupyter notebook and I can not install optimuspyspark using
!pip install optimuspyspark
To Reproduce

I made a new Jupyter notebook ipynb
I ran !pip install optimuspyspark as described in the documentation
I ran into the following error:

ERROR: Could not find a version that satisfies the requirement tensorflow==1.13.1 (from optimuspyspark) (from versions: 2.2.0rc1, 2.2.0rc2, 2.2.0rc3, 2.2.0rc4, 2.2.0, 2.2.1, 2.2.2, 2.3.0rc0, 2.3.0rc1, 2.3.0rc2, 2.3.0, 2.3.1, 2.3.2, 2.4.0rc0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.4.0, 2.4.1, 2.5.0rc0, 2.5.0rc1)
ERROR: No matching distribution found for tensorflow==1.13.1 (from optimuspyspark)

Expected behavior
Succesful install
Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox
Using Anaconda
Notebook version: 6.0.3

Hi @Fluffms,
Thanks for the report.
It seems that tensorflow==1.13.1 is not available anymore.
I am going to bump the TensorFlow version a release a new Optimus version.
I will available at the end of the day.

Thank you for your quick reply! I look forward to the changes


Check for numeric values in factory second parameter

This will allow for things like the passing of a parameter from a console command option to be passed through cleanly to the factory method.
For instance,
protected $signature = 'generate:data {--messages=0};
is currently not usable as
public function handle() {
    $messages = $this->option('messages');
    if ($messages) {
        factory(Message::class, $messages)->create();
    }
}

because $messages gets passed through from the command line as a string "1" for instance.
This will first check if it is usable as a number, and if it is, then it will use that, otherwise fall back to using the old checks.

So in other words - you are "casting" values from the command line?

Not really, just not treating "1" as a string for instance.
The purpose of it handling a string is to handle other class names, but since a class name can never be numeric, this makes sense as a change anyway.

Isn't this a wonderful time to start using a proper types?
$messages = (int)$this->option('messages');
--- or ---
factory(Message::class, (int)$messages)->create();

Wouldn't this be a breaking change? They could be a rare case where someone is expecting it as a string.

@sisve That is what I am currently doing at the moment.
However, PHP is a rather loose language, where "1" == 1 and for "1" to break an application, but 1 to make it work doesn't make sense.
I can cast the value, and currently do. But there is absolutely no reason why it should consider a numeric string to be a class name, which is what it currently does, because PHP classes cannot be numeric.
@Dylan-DPC It is not a breaking change since it throws an exception if you pass through the number as a string as it currently assumes it to be a class name if it is a string.
As I see it, this is a bug fix for factory(), not a new feature for it.

If this does get rejected, and the recommendation is to go with @sisve idea, then the error message should definitely be changed and improved, since it currently says something about class [1] not existing.

No plans to change right now.

@taylorotwell Can i get clarification on how it isn't a bug that it treats a number as a class name?

$factory->defineAs(User::class, 1, function (Faker $faker) {
    dd('here');
});

And in your tests
factory(User::class, "1")->create();


cargo apk run --lib spits out tons of compile error - some std types are missing

I followed the instruction in README and tried to compile the things with cargo apk run --lib, but only to get tons of compile errors like
error[E0531]: cannot find tuple struct or tuple variant `Some` in this scope
    --> C:\Users\switefaster\.cargo\registry\src\mirrors.ustc.edu.cn-61ef6e0cd06fb9b8\once_cell-1.13.0\src\lib.rs:1298:9
     |
1298 |         Some(it) => it,
     |         ^^^^ not found in this scope

It seems that std types such as Option Send Sync are missing. However cargo run works just as intended, what is causing this? Is there any workaround?

Sorry for this, I found I forgot to install the android targets. rustup target add will fix this. Closing,


Add Soundex Cracker

Hey! I have written the necessary scripts to add in the new feature - soundex crcaker
this solves #412

@all-contributors please add @sashreek1 for code

@all-contributors please add @sashreek1 for code

Hey we're changing from MIT to GPLv3 because some of our projects are licensed with that, do you approve? If you do not approve we will be forced to delete your code and rewrite it 😢
By approving of this change, you are agreeing to re-license the code you wrote under GPLv3.

I approve the change, seems all good to me!


create video without using the renderer?

Hi! I'm attempting to use nerfstudio in Google Colab, and I've been running into issues with the renderer (it constantly says "renderer disconnected", no matter what I try). I'd like to render a video from my trained data, but I need the camera path to do so, and the only source for the camera path appears to be the renderer. Is there a way I can generate the camera path and video without having to use the renderer? Thanks!

You can use the blender addon to make camera paths - https://docs.nerf.studio/en/latest/extensions/blender_addon.html
Of you can render a path that interpolates between input cameras - https://docs.nerf.studio/en/latest/reference/cli/ns_render.html#interpolate


[Q] - Why does the "Valid"-method (that new's upp Organisationnummer instance), throw exception instead of i.e. bool?

In an API project I am doing checks if query is valid Organisationsnummer. I wonder why the Valid()-method is throwing exception instead of using a bool for example?
Now in the app, I am naively checking if query is length according to a valid Organisatiosnummer and in that case passes to Valid()-method. This improves performance from around 130ms to 60ms for the api calls.
If this seems to be something that you think could be refactored, I can do a PR.

Hi there!
Not fully sure what you are asking.
The Valid method should return a boolean value.
If you are asking about why we construct a new object in the static valid function instead of running a few checks on it I would say that it's mainly to keep it simple. All rules that would have to be checked for it to be seen as a valid org number is done in the constructor.
Could you show an example on what you are doing so I could get a clearer picture of the issue?

Well I see I missed to provide with some information. Sorry. It returns bool as you say. I meant the Parse method, which throws if invalid. And that decreases performance.

Ah okay, yes, the parse method throws an exception.
Returning a bool would not be possible, as the return value is intended to be a Organisationsnummer instance, it's basically just a factory method for the object. The reason we throw an exception instead of returning something like a null value is cause we can include a lot more information in the exception (why did it fail), although, we have not been too good with that in the package.
The idea is that the exception message should tell the consumer why the parse function failed, much like the int.Parse method.
I could imagine implementing a TryParse function (return bool, out orgnr object), and will take it up with the team and see what they think.
Could you possibly post a snippet of your optimization so I could check what you do to make it faster? Or is it just the try/catch part required for exception handling that actually messes up the speed of the function?

I think it is just the tr/catch part that messes up the speed. ATM I am just making sure that two conditions are valid. The first is that the query length is according to the length of Organisationsnummer, if so it will pass it as param to the Valid() method.
In most cases the user will provide an valid Organisationsnummer when the query is according to the correct length.

I understand!
I will have to do some test cases on the speed of the various checks we do in the parse function. Try/Catch does ofcourse have a penalty, but I would not expect it to be that high, but seeing our first test in the Parse function is a regex match (rather than a simple length check), it could be a bit more heavy than it should be.
I would imagine that checking the length would be a possible first check to do (although, we aught to check the length for short, long and separated short and long to confirm to the specs) it would still likely be faster.
I'll take it up with the team and see what we find being the best way of solving it :)

We have discussed the issue and will recommend each package maintainer to add a length check on the number as a first test. I would imagine that this will speed up execution quite a bit in your case.
Further, I'll add a tryparse function to the c# project, as that is quite standard in the c# world.
Will close this issue when it's done :)


Mock single resource, allow other real resource

Moto version: 1.3.14
Consider the following example. My system is configured such that the boto3 S3 code will execute properly, on its own. However, if I execute the moto code to mock out SQS, the S3 (list_objects) will fail with ClientError: An error occurred (InvalidAccessKeyId) when calling the ListObjects operation: The AWS Access Key Id you provided does not exist in our records.:
import moto
mock_sqs = moto.mock_sqs()
mock_sqs.start()

import boto3
s3 = boto3.client('s3')
resp = s3.list_objects(Bucket='real-bucket-name', Prefix='', Delimiter="/")
print([x['Prefix'] for x in resp['CommonPrefixes']])

I've narrowed the cause of this error to the following: https://github.com/spulec/moto/blob/1299fef8b8217a39cd8446731024614b2191fe04/moto/core/models.py#L51-L56
Based on that code, it look as if I could call mock_sqs.env_variables_mocks.stop() immediately after mock_sqs.start().
I have tried this and it works, which is awesome. I wanted to share this with others in case they encounter the same issue, and also open up a discussion to learn if there's a better way to achieve the same result.
The system I am working in is extremely complex and it is not practical for me to convert all the AWS boto usage over to mocks, thus for now I do need to be able to mock out a single resource.

Thanks for sharing the solution @kylegibson! That is very useful.

Hi @kylegibson , it's been a while, but we've just created a new alpha-release where this behaviour can now be configured: moto==5.0.0alpha2
This release has a new mock_aws-decorator, with a config-parameter where you can specify which services should passthrough to AWS:
@mock_aws(
    config={"core": {
        "mock_credentials": False,
        "passthrough": {
            "services": ["s3"]
    }}}
)

See the release announcement here: https://github.com/getmoto/moto/issues/7198
Are you able to upgrade and verify that this works for you?

Moto V5 has now been released, so I'll close this.
Release: https://pypi.org/project/moto/5.0.0/
Documentation about this feature: http://docs.getmoto.org/en/5.0.0/docs/configuration/index.html


Consents: Use Mailgun's Bulk email send rather than sending individual messages to the user

See this comment for the discussion: https://github.com/carpentries/amy/pull/1872#discussion_r607566498

cc @pbanaszkiewicz I'll circle back around sometime next week and see if I can't get a mailgun sandbox account. If you have access to one for AMY that would be great.

@lauryndbrown I think @fmichonneau has all the accesses.

@pbanaszkiewicz he spoke with me about it. Thanks. I'll take a look at this later this week.


cri: initial implementation of stage1 changes

This PR pulls most of the stage1-based changes from the CRI branch back into
master, leaving out the changes in stage0 (new app subcommands).
Being in the beginning of the next release cycle this gives us the
opportunity to merge the first CRI efforts.
/cc @yifan-gu @lucab @squeed @alban
Relates to #2992

For a reference here is the stat-diff towards the cri branch:
$ git diff crisync..origin/cri
 Documentation/devel/stage1-implementors-guide.md |  34 +++++++++++++++++++++++++++++++
 rkt/app.go                                       |  28 ++++++++++++++++++++++++++
 rkt/app_add.go                                   | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_exec.go                                  |  37 ++++++++++++++++++++++++++++++++++
 rkt/app_list.go                                  |  65 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_rm.go                                    |  82 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_sandbox.go                               | 199 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_start.go                                 |  98 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_status.go                                | 125 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/app_stop.go                                  |  94 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rkt/list.go                                      |   1 -
 11 files changed, 876 insertions(+), 1 deletion(-)

I set the do-not-merge label until I have a green light from CI.

CI looks green enough for needs/review, PTAL :-)


Works Great!

Thanks for the plugin. Any thoughts on supporting more input fields like checkbox for Boolean?
Also any thoughts on supporting relationships between models?

Thank for your opinion.
I have some plans to do these.
Feel free to Pull request and add new features :)


Smarter Polling

We now consult the file size and modification time before re-parsing it.
Same is true for URLs: a HEAD request is made beforehand and we only download the file if the size (Content-Length) or modification time (Last-Modified) has changed since last time we downloaded it.

OK, merging this since time is short.


Create helm chart

Provide a helm chart in kubernetes/stable for httpbin to make deploying this easier in managed k8s environments.

that would be amazing!

how do we get started?

Stable charts live here: https://github.com/helm/charts
Documentation on how to contribute a chart: https://github.com/helm/charts/blob/master/CONTRIBUTING.md
Since you already have an httpbin Docker image on DockerHub, it would be preferable to version that image to prevent accidental updates.
Whomever builds the chart just needs a kubernetes stack for testing it out.
If you like, I'm happy to contribute this with your permission.

@mhamann did you had a chance to create?

Haven't done it yet @declum, but still on the list of things to do unless someone beats me to it ;-)

PR https://github.com/postmanlabs/httpbin/pull/588 :)

I have created a helm chart for httpbin which is available in my helm repository and deploys the golang port of httpbin.
I hope it can help.


feat(api): feature flags

This PR adds a Feature v2 API. This feature API allows enabling and disabling certain features of zitadel. This allows us to separate experimental (Alpha/Beta) features from the rest of zitadel and phased rollouts.
Although the current features can only be disabled or enabled through a boolean flag, this PR adds the possibility of any type of feature "payload" which might be needed for configuration of future features.
Features are set on levels. As system and instance level are easily resolved, those are fully implemented. In the authz middleware each request will receive a cascaded payload of defaults, system and instance feature settings. We currently have no organization and user level features defined, as such there is no request scoped getter implemented yet. This is mostly because we have to figure this out when such features come to exist. For example Organization features might apply to the authenticated user's org or to the organization of the resource being managed during an API call.
Implementation per level

Level
Level enum
Proto definitions
API implementation
Runtime access

SystemDefaults
:heavy_check_mark:
N/A
N/A
:heavy_check_mark:

System
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark:

Instance
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark:

Organization
:heavy_check_mark:
:heavy_check_mark:
:x:
:x:

Project
:heavy_check_mark:
:x:
:x:
:x:

App
:heavy_check_mark:
:x:
:x:
:x:

User
:heavy_check_mark:
:heavy_check_mark:
:x:
:x:

Cascading features
Features must cascade into a final object used by the runtime to know the state of features. It starts with the SystemDeafults from the config yaml and then applies resource specific settings on top of it. Features are evaluated and applied in the following order. The last one that has a specific feature configuration wins.
defaults -> system -> instance -> organization

In the APIs cascading is optional, so that the caller can either determine the state on the level it's managing or the cascaded state as how the zitadel runtime will see the features. The source of each feature is included in the response object.
Closes: #6668
Breaking config  changes
In defaults.yaml there are some changes that need modification if those options were set in a local yaml config file by users.

SystemDefaults.Features is added and affects complete system and all instances, for the features that were not set on instance level. (Either by API or DefaultInstance). The defaults are set to false, so this is not a breaking change by itself.
OIDC.Features is removed -> if it was set it will now be ignored in favor of SystemDefaults.Features. This is a breaking change, but the impact is low. Those options where provided as fallback in case the introspection optimization proved to have bugs. We got no reports.
DefaultInstance.Features is changed from a map to a struct type. If - FeatureLoginDefaultOrg was set it needs to be manually adjust to LoginDefaultOrg or else zitadel will fail to start.

Definition of Ready

[x] I am happy with the code
[x] Short description of the feature/issue is added in the pr description
[x] PR is linked to the corresponding user story
[x] Acceptance criteria are met
[x] All open todos and follow ups are defined in a new ticket and justified
[x] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[x] No debug or dead code
[x] My code has no repetitions
[x] Critical parts are tested automatically
[x] Where possible E2E tests are implemented
[x] Documentation/examples are up-to-date
[x] All non-functional requirements are met
[x] Functionality of the acceptance criteria is checked manually on the dev system.

LGTM, but would be glad if someone else double checked


(#3) Add proper random floating point ranges

Let me know if you think it's weird to have non-primitive constants (ranges in this case)
closes #3

@sdegueldre looks goode to me! Thank you for your contribution!


Allow to restore all fullscreen windows

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
I have two (unsaved) workspaces.
both are in fullscreen , on macos desktops.
when I restart vscode(nightly) for updates, one workspace is restored to full screen while the other one is windowed.
VS Code version: Code - Insiders 1.67.0-insider (3159d61ccf5150764f7742f098d76872e3114dcb, 2022-05-04T00:06:17.219Z)
OS version: Darwin arm64 21.5.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
7, 4, 3

Memory (System)
32.00GB (1.52GB free)

Process Argv
--crash-reporter-id a3a42226-aff1-4ce4-b814-c281836320a1

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

vscode-base64
ada
0.1.0

inline-hasher
ale
1.1.0

git-temporal-vscode
bee
1.0.0

better-toml
bun
0.3.2

githistory
don
0.6.19

hadolint
exi
1.1.1

terraform-preview
has
2022.4.1920

vscode-docker
ms-
1.22.0

vscode-kubernetes-tools
ms-
1.3.7

python
ms-
2022.4.1

git-file-history
pom
1.0.1

vscode-yaml
red
1.7.0

vscode-gitweblinks
red
2.7.0

vscode-kubewatch
san
1.0.9

pip-manager
sli
1.1.1

kubernator-vscode
smp
0.5.1

tfsec
tfs
1.10.0

shellcheck
tim
0.19.2

sort-lines
Tyr
1.9.1

vscode-icons
vsc
11.11.0

jinja
who
0.0.8

json
Zai
2.0.2

(1 theme extensions excluded)

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I believe this is a platform and/or electron limitation. We do remember that the window was fullscreen and set it as such, but only 1 window is opened as fullscreen.
//cc @deepak1556 if this rings any bell, might be related to the issue in Electron that macOS spaces cannot be restored.

Upstream: https://github.com/electron/electron/issues/34367

Also seems to happen on Windows: https://github.com/microsoft/vscode/issues/148698


Unzip.exe not compatible with 64-bit versions of windows

When trying to use the updater on my Windows 10 machine I get the following error
"C:..\tools\unzip.exe" cannot start or run due to incompatibility with 64-bit versions of Windows

Fixed the problem by using node Adm-Zip instead of the zip.exe on my fork
https://github.com/piotrromanowski/node-webkit-updater

I don't understand it's possible there could be an incompatibility with 64-bit Windows. I'm on 64-bit Windows myself too.


rails g delayed_job:upgrade fails under Rails3.2

Summary:
Upgrading from DJ 2.1.4 / Rails 3.0 to DJ 3.0 / Rails 3.2 fails in rails g delayed_job:upgrade with the message Could not find generator delayed_job:upgrade.  I am:

Using delayed_job (3.0.1)
Using delayed_job_active_record (0.2.1)

To replicate:
$ bundle install
Using rake (<IP_ADDRESS>)
Using ZenTest (4.6.2)
Using i18n (0.6.0)
Using multi_json (1.0.4)
Using activesupport (3.2.0)
Using builder (3.0.0)
Using activemodel (3.2.0)
Using erubis (2.7.0)
Using journey (1.0.1)
Using rack (1.4.1)
Using rack-cache (1.1)
Using rack-test (0.6.1)
Using hike (1.2.1)
Using tilt (1.3.3)
Using sprockets (2.1.2)
Using actionpack (3.2.0)
Using mime-types (1.17.2)
Using polyglot (0.3.3)
Using treetop (1.4.10)
Using mail (2.4.1)
Using actionmailer (3.2.0)
Using arel (3.0.0)
Using tzinfo (0.3.31)
Using activerecord (3.2.0)
Using activeresource (3.2.0)
Using addressable (2.2.6)
Using annotate (2.4.0)
Using encryptor (1.1.3)
Using attr_encrypted (1.2.0)
Using autotest (4.4.6)
Using bcrypt-ruby (3.0.1)
Using bluecloth (2.2.0)
Using bundler (1.0.21)
Using cancan (1.6.7)
Using crack (0.3.1)
Using daemons (1.1.6)
Using delayed_job (3.0.1)
Using delayed_job_active_record (0.2.1)
Using orm_adapter (0.0.6)
Using rack-ssl (1.3.2)
Using json (1.6.5)
Using rdoc (3.12)
Using thor (0.14.6)
Using railties (3.2.0)
Using warden (1.1.0)
Using devise (2.0.0)
Using diff-lcs (1.1.3)
Using unf_ext (0.0.4)
Using unf (0.0.4)
Using domain_name (0.5.2)
Using eventmachine (0.12.10)
Using jquery-rails (2.0.0)
Using net-http-digest_auth (1.2)
Using net-http-persistent (2.3.3)
Using nokogiri (1.5.0)
Using ntlm-http (0.1.1)
Using webrobots (0.0.13)
Using mechanize (2.1)
Using pg (0.12.2)
Using rails (3.2.0)
Using rspec-core (2.8.0)
Using rspec-expectations (2.8.0)
Using rspec-mocks (2.8.0)
Using rspec (2.8.0)
Using rspec-rails (2.8.1)
Using ruby-graphviz (1.0.3)
Using ruby-prof (0.10.8)
Using thin (1.3.1)
Using vcr (1.11.3)
Using webmock (1.7.10)
Using webrat (0.7.3)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.

$ rails g delayed_job:upgrade
DEPRECATION WARNING: Calling set_table_name is deprecated. Please use `self.table_name = 'the_name'` instead. (called from <top (required)> at /Users/me/myapp/config/application.rb:7)
Could not find generator delayed_job:upgrade.

(FWIW, I believe the deprecation warning is a rake problem, not a delayed_job problem.)

More info:
When I include:
gem 'delayed_job_active_record'

in my Gemfile, I get the following:
$ bundle install
... lots of messages
$ rake <any command>
DEPRECATION WARNING: Calling set_table_name is deprecated. Please use `self.table_name = 'the_name'` instead. (called from <top (required)> at /Users/me/myapp/config/application.rb:7)

So it appears that the delayed_job_active_record gem is the source of the deprecation message.  I don't know if that's related to the Could not find generator problem.

I believe the deprecation will be fixed in next release. It's harmless anyway.
As far as the generator, it's not present until 0.3.0. I see you are using 0.2.1.

Yah, I just did a 'bundle update' and noticed that I'd be running the older version.  (But in the meantime I looked at the sources and created my own migration to add the :queue field...not difficult.)  Thanks!


New option for create: --google-use-internal-ip

Introduced a new flag for google driver:
--google-use-internal-ip
When invoked while create it will make docker-machine use internal rather than public NATed IPs.
It's very useful if you manage machines from within the same network. It's faster, simpler and make deploying e.g. swarm much easier as one do not have to configure firewall even when swarm is managed from within the same network. The flag is persistent in the sense that a machine created with it retains the feature.

Looks like we would not be able to merge this PR because of merge conflicts. Please rebase, fix conflicts, and force push to your branch.

Hey Mr. @dgageot wdyt? :)

@dmp42 @emsi Seems cool! I'll comment on a few things that could be improved on the code

@emsi can you squash the PR into a single commit?

@emsi would you like to use the feedback to prepare the PR for being shipped with 0.5.0?

Hi
Yes. I've been really busy this week. I'll try to update the PR this weekend. I hope it's not too late  :)
--
Sent from my phone
Mariusz Woloszyn

On 10 paź 2015, at 15:30, David Gageot<EMAIL_ADDRESS>wrote:
@emsi would you like to use the feedback to prepare the PR for being shipped with 0.5.0?
—
Reply to this email directly or view it on GitHub.

@emsi Take your time! I just wanted to be sure you were still involved.

@dgageot: It's squashed now and I have improved the code based on you suggestions. :)

Thanks @emsi! I'll test it tomorrow

@emsi Can you update the documentation in docs/drivers/gce.md?

@emsi You might want to rebase on #1973 for your tests because on master, the google driver is broken

I noticed that yesterday and gave up as it was very late already :) Thanx
for pointing to the right commit.
On Tue, Oct 13, 2015 at 12:04 AM, David Gageot<EMAIL_ADDRESS>wrote:

@emsi https://github.com/emsi You might want to rebase on #1973
https://github.com/docker/machine/pull/1973 for your tests because on
master, the google driver is broken
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/1879#issuecomment-147534192.

--
Emsi

@dgageot: I fixed that garbage code and added the documentation. I also retested it on the GCE to make sure everything works as expected.
You can test it now :)

Thanks @emsi I'll test that tomorrow first thing

@emsi Thank you very much for your PR. I listed a couple of tiny things to fix and I've tested the feature. When the fixes are there, it's good to be merged!

It should be OK now. :)

LGTM
Thank you @emsi
@nathanleclaire @dmp42 can you take a second look?

Please hold on. I found small improvement.

It's perfect now. I removed a bit of unnecessary code.

LGTM

@dmp42 @nathanleclaire wdyt?

Code LGTM.
@nathanleclaire ptal

@emsi can you rebase against latest master? with the recent plugins merge, we need to make sure everything compiles against the latest master.
Sorry for the inconvenience.

I rebased against the latest master but google driver seems to be broken there.
I got Error creating machine: Error in driver during machine creation: unexpected EOF even without my patch.
I tried with v0.5.0-rc1 and got the same error. When I tried to debug that issue it looks like the interactive part with opening URL and pasting the code goes wrong in the background process (it clearly does not show on the tty while it's in the debug).

Ah, right.  Since the code actually makes a call to open a browser window, which naturally won't work inside of an exec-ed process.
Perhaps we need to fix that code to get the token ahead of time like the other drivers, before the release happens.

@nathanleclaire @emsi I created a ticket for this issue #2023

Thanks @dgageot

Hi @emsi, we didn't forget you. The google driver is being fixed with https://github.com/docker/machine/pull/2087. Once it's merged you will have to rebase and fix the conflicts.
Sorry for the delay.

No problem. I'll stay tuned :)
--
Sent from my phone
Mariusz Woloszyn

On 27 paź 2015, at 10:53, David Gageot<EMAIL_ADDRESS>wrote:
Hi @emsi, we didn't forget you. The google driver is being fixed with #2087. Once it's merged you will have to rebase and fix the conflicts.
Sorry for the delay.
—
Reply to this email directly or view it on GitHub.

@emsi You should be able to rebase now that the driver is ok \O/

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "google-use-internal-ip" git@github.com:emsi/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@dgageot It should be OK now :)

LGTM. Scheduling for 0.5.1

LGTM

Hi @emsi, one last rebase and it's merged! Sorry for the inconvenience. A lot of PRs touched the gce driver at the same time.

@dgageot: I take your word for it :)
Should be OK now.

 :)
I got the black belt in rebasing.

:+1:


Update BlockKriging functions to use the n-nearest observations for interpolation

merge_additive_blockkriging and merge_ked_blockkriging has been updated to use the n nearest observations, making them more comparable to IDW interpolation
Removed transformation function from KED high-level class, as n-nearest interpolation ked struggled with back-transforming the data
IDW additive adjustment now uses IDW interpolator from radolan
Updated tests accordingly
added "merge" to src/mergplg__init__.py so that merge functions can be run from a submodule

@eoydvin Sorry for the unnecessarily long delay... 🙈
I had a brief look at the changes in the code and mainly at the notebook, comparing it to the old one before the PR.
I have no capacity to think through the changes in the code in much detail now. But from a more zoomed out perspective everything makes sense. Hence, I am merging this now to allow us to move forward with mergeplg.
I assume we will have time in Jan or Feb 2025 to evaluate the overall structure and direction of the code and the potentially revisit some parts.
Thanks for your contribution 👏 👏 👏


Massive size increases while even serving smaller or lower quality images

Hey,
We're testing image proxy currently at our company, and we see the following on files served through it:

You can see here on the left, the original image is ~176KB. Served through image proxy at its original size and full quality, it is ~631KB.
They only appear to start getting smaller at about q40, at which point the image has pretty bad JPEG artifacts visible all over. When using just size we have to make our images appox at least 1/3rd the original size.
Meaning using this project without lowering size or quality significantly, makes our images up to 4x bigger, which kind of beats the purpose of this.

Can you provide the URL of that test image so I can try to replicate the results?

Are you still seeing this behavior?  As noted above, can you provide the URL of the test image so I can try to reproduce this?

closing old issue with no response.


Interpret any 2xx status code as having sent a broadcast

We were explicitly checking for 200. However the API returns 201 when successful. To be safe this checks if the status code is in the 2xx range.

 Ruby gem should allow all 2xx status code

Looks good to me!


add support for workbooks in deeply nested folders

Updates the template package processing to allow more deeply nested folders.  Several teams have run into this, you should now be able to make more deeply nested folder structures.  I haven't fully verified that the category names work out correctly though because of some other issues (like nobody really using this for real without other strange cases)
For network team, their 3 "missing" templates now show up in the index as workbook templates:

(however, it looks like they have PRs that will flatten out the hierarchy right now so nobody will technically be using it)


Reading large arrays seems to take forever and if endup, results in Segmentation fault

Reproducing the behavior
Running this script with "bend run-c" I can parse a file until with 2**15 elements with the following code, but I get the beginning of the list to print and then a seg fault when I use a 2**16 elements file. I cant see any issue in the implementation itself that could cause that behavior.
Input file example:
Parses a file into a list of integers with the first line being the size of the dataset
Example:
4
41
32
17
23

The script:
# converts a string to an integer
def CharToInt(char):
  return char - 48

def strLen(l):
  match l:
    case String/Nil:
      return 0
    case String/Cons:
      return strLen(l.tail) + 1

def pow(value, power):
  if power == 0:
    return 1
  else:
    return value * pow(value, power - 1)

def StringToInt(str):
  lenght = strLen(str)
  return _StringToInt(str, lenght)

def _StringToInt(str, acc):
  fold str with acc:
    case String/Cons:
      return CharToInt(str.head )*pow(10, acc - 1) + str.tail(acc - 1)
    case String/Nil:
      return 0

def parse_list(txt):
  match txt:
    case String/Cons:
      (head, tail) = txt
      res = List/Cons { head: StringToInt(head), tail: parse_list(tail) }
    case String/Nil:
      res = List/Nil
  return res

def get_dataset():
  with IO:
    fd <- IO/FS/open("../datasets/sequence_random.txt", "r")

    bytes <- IO/FS/read_to_end(fd)

    match res = Bytes/split_once(bytes, '\n'):
      case Result/Ok:
        (firstLine, rest) = res.val
        sizeAndList = (StringToInt(Bytes/decode_utf8(firstLine)), rest)
      case Result/Err:
        sizeAndList = (0, [])

    (sizeBytes, rest) = sizeAndList
    # first line has size of the dataset
    full_size = StringToInt(Bytes/decode_utf8(sizeBytes))
    bend size = full_size, bytes = rest:
      when size > 0:
        match res = Bytes/split_once(bytes, '\n'):
          case Result/Ok:
            (line, rest) = res.val
            value = StringToInt(Bytes/decode_utf8(line))
            list = List/Cons { head: value, tail: fork(size - 1, rest) }
          case Result/Err:
            value = 0
            list = List/Nil
      else:
        list = List/Nil
    return (list)

append = @l @e
  (concat l (List/Cons e List/Nil))

concat = @l1 @l2
  match l1 {
    List/Cons: (List/Cons l1.head (concat l1.tail l2))
    List/Nil: l2
  }

split = @l @i (split.aux [] l i)

split.aux = @acc @l @i
  match l {
    List/Cons:
      switch i {
        0: (acc, l)
        _: (split.aux (append acc l.head) l.tail i-1)
      }
    List/Nil: *
  }

len = @l
  match l {
    List/Nil: 0
    List/Cons: (+ 1 (len l.tail))
  }

def bi_list_to_tuple(l):
  match l:
    case List/Cons:
      match l.tail:
        case List/Cons:
          return (l.head, l.tail.head)
        case List/Nil:
          return (l.head, *)
    case List/Nil:
      return List/Nil

def main:
  with IO:
    fd <- IO/FS/open("../datasets/lines_sorted.txt", "r")

    bytes <- IO/FS/read_to_end(fd)

    match res = Bytes/split_once(bytes, '\n'):
      case Result/Ok:
        (firstLine, rest) = res.val
        sizeAndList = (StringToInt(Bytes/decode_utf8(firstLine)), rest)
      case Result/Err:
        sizeAndList = (0, [])

    (sizeBytes, rest) = sizeAndList
    # first line has size of the dataset
    full_size = StringToInt(Bytes/decode_utf8(sizeBytes))
    bend size = full_size, bytes = rest:
      when size > 0:
        match res = Bytes/split_once(bytes, '\n'):
          case Result/Ok:
            (line, rest) = res.val
            value = StringToInt(Bytes/decode_utf8(line))
            list = List/Cons { head: value, tail: fork(size - 1, rest) }
          case Result/Err:
            value = 0
            list = List/Nil
      else:
        list = List/Nil

    return list

System Settings

HVM: 2.0.21
Bend: 0.2.36
OS: Windows 11 WSL 2 with Ubuntu 22.04.4 LTS
CPU: Intel i5-1235U
RAM: 32 GB -> 26GB to WSL

Additional context
It might be related to this issue: https://github.com/HigherOrderCO/Bend/issues/632

Here a script that generate some files to use as input to reproduce.
import numpy as np

path = "../datasets/"

def generate_uniform_dataset(size, low, high):
    """
    Generate a uniformly distributed dataset.
    """
    return np.random.uniform(low, high, size).astype(int)

def generate_random_dataset(size, low, high):
    """
    Generate a randomly distributed dataset.
    """
    return np.random.randint(low, high, size)

def generate_skewed_dataset(size, low1, high1, low2, high2, skew_ratio=0.8):
    """
    Generate a skewed dataset with the specified ratio.
    """
    size_majority = int(size * skew_ratio)
    size_minority = size - size_majority

    majority_part = np.random.randint(low1, high1, size_majority)
    minority_part = np.random.randint(low2, high2, size_minority)

    return np.concatenate([majority_part, minority_part])

def save_dataset(filename, dataset):
    """
    Save dataset to a file in the format [1, 2, 3, 4].
    """
    with open(filename, 'w') as f:
        f.write(str(len(dataset)) +'\n' + '\n'.join(map(str, dataset)))

if __name__ == "__main__":
    ARRAY_SIZE = 2**16
    # Large random dataset
    large_random_dataset = generate_random_dataset(ARRAY_SIZE , 0, 2**19) # 524288
    save_dataset(path + "lines_random.txt", large_random_dataset)

    # Large skewed dataset
    large_skewed_dataset = generate_skewed_dataset(ARRAY_SIZE, 0, 1000, 1001, 1000000)
    save_dataset(path + "lines_skewed.txt", large_skewed_dataset)

    # Generate and save sorted datasets
    sorted_dataset = np.sort(large_random_dataset)
    save_dataset(path + "lines_sorted.txt", sorted_dataset)

    # Generate and save reverse sorted datasets
    reverse_sorted_dataset = sorted_dataset[::-1]
    save_dataset(path + "lines_reverse.txt", reverse_sorted_dataset)

    print("Datasets generated and saved to files.")

I'll have to test your program later, but some things stand out to me.
First off, IO is indeed very slow right now, but it should be linear with the number of operations (counting each read byte, each argument passed, etc).
The segfault sounds like some problem in the HVM interface with the OS.
I find it surprising that your program works as you expected, because it has some type errors regarding the use of with.
When you do with IO and then you execute a sequential operation with var <- action, the result of that block should be of IO type.
You do this both in main and in the unused get_dataset.

Crash possibly the same as https://github.com/HigherOrderCO/Bend/issues/632


Create, document and publish a manifest schema

Is your feature request related to a problem? Please describe.
Developers get confused what manifest is which. An input build manifest is not the output build manifest.
Describe the solution you'd like

Create sample manifests and link them from a doc/README.
Create a manifest schema that can be used to validate a manifest.
Add a CI that checks that sample and all input manifests conform to schema.

Manifest classes have .SCHEMA which is validated and "published". Closing.


Add issue and feature/suggestion templates

Add an issue/suggestion/feature request template. A simple catch all to allow for easier visualization and documentation of suggestions or bugs made by individuals. Default template modified a little; need more input from team.

Looks good. I think it makes sense to have a separate template for bug reports, for example opendota's approach:
https://raw.githubusercontent.com/odota/web/master/.github/ISSUE_TEMPLATE/Bug_report.md
https://raw.githubusercontent.com/odota/web/master/.github/ISSUE_TEMPLATE/Feature_request.md


Development

I've added the tabs for engine stdout and stderr, which are quite useful when debugging the bot and even the engine. Removed the visualizer output tab, which is not really needed.

I will look at it and merge from the commandline to prevent development to be behind on master.


feature: alert when newer releases of app exist on github

@bilal-fazlani  Another example of adding middleware.  I made this a separate project because of the external dependencies.  When #154 is resolved, we can make this available as another nuget package.

This is cool!


[question] using candle under VPN / firewall

some of my users face an issue with downloading hf models and not sure how to solve this
2024-11-21T19:08:28.461123Z ERROR screenpipe: continuous recording error: request error: https://huggingface.co/openai/whisper-large-v3-turbo/resolve/main/config.json: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer

https://github.com/mediar-ai/screenpipe/issues/730
anything i need to do with HF hub config or any advice would be appreciated

https://github.com/huggingface/hf-hub/blob/ac22200ea0b5af4d8c362f699be0340647b19060/Cargo.toml#L44

最佳 快连VPN 服務
绝对匿名的加密連接
超快的速度且無數位足跡
在美國和全球有数千台安全服务器

官方下载：
https://expvpn.net
https://vpndapps.com
https://letsvpnt.com
https://letskuailian.com


Autoconfiguration ignores user defined graphql.servlet.GraphQLErrorHandler

When you have custom defined GraphQLErrorHandler, it is not picked up by GraphQLWebAutoConfiguration
@Component
class MyErrorHandler extends GraphQLErrorHandler {
    ...
}

This happens because you check explicitly containsBean by name 'GraphQLErrorHandler'
https://github.com/graphql-java-kickstart/graphql-spring-boot/blob/37374516a5cdce8cc83e62a904c6b3861480da41/graphql-spring-boot-autoconfigure/src/main/java/com/oembedler/moon/graphql/boot/GraphQLWebAutoConfiguration.java#L114-L122
I think it's better just check if (errorHandler != null) {, in this way if configuration contains GraphQLErrorHandler bean then it will be auto wired into errorHandler field

I don't see this code in the version 7.0.1. Which version should I use to get this bugfix?


Errors importing Regions into Perspective

Describe the bug
I've set up Perspective in one account and used StackSets to push out the global and regional resources to the other accounts in our Org.
Initially I imported 2 accounts/regions and things looked good.
I then asked Perspective to import the additional 20 or so accounts in our Org, and nothing seemed to happen.  The "Last Scanned" column in the Regions table other than for the 2 original accounts never changed from "N/A".  Further digging, I found the ECS scheduled task seemingly hanging.
To Reproduce
I've seen other issues mention problems bulk importing regions, so I have

Removed the failed Regions.
Stopped the ECS discovery task.
Added 1 additional region at a time.

I've had mixed success with this.  ( I now have 4 regions successfully imported ).   However, I can't get regions to successfully import consistently, and currently the 4 regions I have are not being updated by the scheduled task.
I have updated the ECS task and set LOG_LEVEL to DEBUG and attached the latest log events from the task.
log-events-viewer-result.csv

Unfortunately, due to the way discovery process works when you add a large amount of accounts at once the calls made to AWS Config get throttled and due to retries with exponential back off can end up hanging the whole process. This is mentioned in the documentation here with remediation steps. We have also recently noticed that if single account has ~3k resources in it that the discovery process can hang too but unfortunately the fix to this will require a rewrite of how AWS Perspective uses Config. We are currently in the early stages of this refactor but I can't give a date for when it will be complete just yet.

Hi.  Many thanks for looking into this.
It's been 36 hours or so since I removed regions that I added in bulk and reverted back to just having the original accounts which were successfully imported.  All of those accounts have less than 2000 config resources.  I am still not seeing consistent successful scans though.  The last successful scan was 4 hours ago.  ( I should be seeing successful scan every 15 minutes right? )
The scan ECS task from that time is still running. I've attached the logs.  I can see ThrottlingExceptions in there, but should I still be getting throttled 36 hours later when now all I am doing is updating successfully imported regions?
1637127990974,"{""level"":""debug"",""message"":""Error code for listAggregateDiscoveredResources: ThrottlingException"",""timestamp"":""2021-11-17T05:46:30.974Z""}"

log-events-viewer-result (1).csv

This issue is a scaling limitation with v1.x.x as the discovery process made an API call to AWS Config for every resource it found. For regions with ~2500 resources, this meant Config would start applying rate limiting to these calls and eventually the whole discovery process would hang and not complete. We have addressed this issue in version v2.0.0 and now make far fewer calls to Config when discovering resources. This new version was released today, and the 2500 resource limit no longer applies.


fix: max_streams in ConnectionRefInner is not synced

Fix the bug #401
The value of the  max stream could be updated by Settings frame in the h2 crate.
Pingora needs to get the updated value instead of storing it in its struct

Fixed in a slightly different way https://github.com/cloudflare/pingora/commit/7419b1967e7686b00aefb7bcd2a4dfe59b31e639


Pick an auth library to prototype and test the generated code

Yes. We are using the auth library in this repo.