Add support for linux/arm64 and darwin/arm64

Signed-off-by: Ismayil Mirzali<EMAIL_ADDRESS>
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

closes #101

@Volatus, I tried to do architecture migration in #102.  It may be more successful to comment there, though you are welcome to see if you can make more headway here.  You need to add several things to the build sections of the builds as in:
https://github.com/conda-forge/airflow-feedstock/pull/102/files#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9aR25-R27
For now, you will also need to skip airflow-with-ldap for the new architectures because dependencies have not yet been built:
https://github.com/conda-forge/airflow-feedstock/pull/102/files#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9aR387-R388

@xylar thanks for the pointers, I'll see what I can do

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@xylar It seems like some issue with yarn but when I tried the yarn install on the Airflow repo everything went fine. Do you think it's possible that the wrapper install script ends up shadowing the real errors underneath? Is there a way I can run the packaging locally to test? (I'm on darwin/arm64)

@Volatus, I also don't understand the yarn issue.  It seems to have emerged very recently and since it's appearing in #104, I don't think it's related to anything you changed here.

I asked about it here:
https://matrix.to/#/!SOyumkgPRWoXfQYIFH:matrix.org/$1678705789214366sdSaV:matrix.org?via=matrix.org&via=gitter.im&via=gnome.org
but no one has responded so far.

@Volatus, I also don't understand the yarn issue. It seems to have emerged very recently and since it's appearing in #104, I don't think it's related to anything you changed here.

Right, and I thought Airflow broke something recently but it did seem like yarn worked fine for me locally on their repo. How would I try running a local build of this feedstock for my host and arch to test some things?

Hmm, I don't think Airflow changed but it does seem like some of the yarn dependencies aren't working anymore.  We probably need to figure out how to patch airflow/www/yarn.lock to fix it but I don't have time or expertise to debug this.

Right, and I thought Airflow broke something recently but it did seem like yarn worked fine for me locally on their repo. How would I try running a local build of this feedstock for my host and arch to test some things?

If you can install docker, you can use:
https://github.com/conda-forge/airflow-feedstock/blob/main/build-locally.py
to build locally.  I can't use docker (it interferes with my ability to connect to my institution's wifi) so I use:
conda mambabuild -m .ci_support/<config>.yaml recipe

That's not foolproof (it can pick up system libraries occasionally) but works pretty well.

You will need to install mamba and boa for this.  boa provides mambabuild.  I believe there are currently some compatibility issues with the latest conda, mamba and boa so it might be safest to go with a version of conda from earlier this year so that you can have a working installation of conda and boa.  (Very inconvenient, so I hope it gets worked out soon!)

@Volatus, it looks like there is a release candidate for 2.5.2:
https://github.com/apache/airflow/issues/30028
That suggests to me that there might be a new release in a week or so.  I think we should just wait for that and try again.  Feel free to debug in the meantime but I won't have time to spend on this until after that release.

@Volatus, if you rebase, you should be able to test again. The fix was to constrain yarn <2.

@xylar Will rebase off of main now.

@xylar So here's the takeaways:

Not sure why the MacOS ARM builds failed, might be something with conda-build.
linux/aarch64 failed on 3.9 and 3.10, but succeeds for 3.8, which makes perfect sense, due to this change introduced in 3.9. It would seem that passlib, a dependency of sqlalchemy ends up creating a bcrypt hash, which Ubuntu's (the current build environment) glibc cannot handle.

@Volatus, okay, we could wait on OSX-ARM for now (and make a separate PR where we ask for help from the experts).
Regarding aarch64, I don't think there's anything we can do about updating glibc (I've had a discussion with core folks about that on some other feedstock).  Anything we can do to patch or bypass this?

Regarding aarch64, I don't think there's anything we can do about updating glibc (I've had a discussion with core folks about that on some other feedstock). Anything we can do to patch or bypass this?

I was wondering how I can change the Docker image for the aarch64 runs. There is an anvil for aarch64 and it would massively speed up our CI builds. Might even fix the issue with crypt, worth a try I think.

It probably makes sense to skip this test when we're cross-compiling:
https://github.com/conda-forge/airflow-feedstock/blob/a1cff27029be376b1a190215c69bcf1c160ad270/recipe/meta.yaml#L114

I don't think we have the ability to change the docker images.  That has to be done consistently across feedstocks by the conda-forge/core folks.

@Volatus, I solved the OSX ARM issue by moving two of the package from host (target architecture) to build (native architecture).  That got merged in #106 and should be available soon (if not now).
I'm working on the Linux architectures in #105 but certainly am open to suggestions you might have.  Feel free to keep working here if you need a testing grounds.


Can't deploy AudioVideoPlaybackBot from Template

Describe the issue
Trying to run the deploy.ps1 script will failed with following error
:08:08 PM - The deployment 'DEPLOYMENTNAME' failed with error(s). Showing 3 out of 4 error(s). Status Message: VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'.
| Error message: "DSC Configuration 'BotServers' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_ServiceResource  failed to execute Set-TargetResource functionality
| with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Service 'AVB (AVB)' cannot be started due to the following
| error: Cannot start service AVB on computer '.'.  The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually."  More information on troubleshooting
| is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot  (Code:VMExtensionProvisioningError)  Status Message: At least one resource deployment operation failed. Please list deployment
| operations for details. Please see https://aka.ms/DeployOperations for usage details. (Code: DeploymentFailed)  - {   "status": "Failed",   "error": {     "code": "ResourceDeploymentFailure",
| "message": "The resource operation completed with terminal provisioning state 'Failed'.",     "details": [       {         "code": "VMExtensionProvisioningError",         "message": "VM has reported a
| failure when processing extension 'Microsoft.Powershell.DSC'. Error message: "DSC Configuration 'BotServers' completed with error(s). Following are the first few: PowerShell DSC resource
| MSFT_ServiceResource  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter
| is set to Stop: Service 'AVB (AVB)' cannot be started due to the following error: Cannot start service AVB on computer '.'.  The SendConfigurationApply function did not succeed. LCM failed to start
| desired state configuration manually."\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "       }     ]   } } (Code:Conflict)   Status
| Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details. (Code: DeploymentFailed)  - {
| "status": "Failed",   "error": {     "code": "ResourceDeploymentFailure",     "message": "The resource operation completed with terminal provisioning state 'Failed'.",     "details": [       {
| "code": "DeploymentFailed",         "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage
| details.",         "details": [           {             "code": "Conflict",             "message": "{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n
| "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n    "details": [\r\n      {\r\n        "code": "VMExtensionProvisioningError",\r\n
| "message": "VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'. Error message: \"DSC Configuration 'BotServers' completed with error(s). Following are the first few:
| PowerShell DSC resource MSFT_ServiceResource  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable
| \"ErrorActionPreference\" or common parameter is set to Stop: Service 'AVB (AVB)' cannot be started due to the following error: Cannot start service AVB on computer '.'.  The
| SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\"\r\n\r\nMore information on troubleshooting is available at
| https://aka.ms/VMExtensionDSCWindowsTroubleshoot "\r\n      }\r\n    ]\r\n  }\r\n}"           }         ]       }     ]   } } (Code:Conflict)   CorrelationId: 1de951ee-10ea-4aec-b93c-42642d1df6a0
Code Snippet
.\deploy.ps1 -OrgName ORGNAME -Location centralus -RunDeployment
Logs
:08:08 PM - The deployment 'ACU1-ORGNAME-AVB-D1-AVB' failed with error(s). Showing 3 out of 4 error(s). Status Message: VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'.
| Error message: "DSC Configuration 'BotServers' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_ServiceResource  failed to execute Set-TargetResource functionality
| with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Service 'AVB (AVB)' cannot be started due to the following
| error: Cannot start service AVB on computer '.'.  The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually."  More information on troubleshooting
| is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot  (Code:VMExtensionProvisioningError)  Status Message: At least one resource deployment operation failed. Please list deployment
| operations for details. Please see https://aka.ms/DeployOperations for usage details. (Code: DeploymentFailed)  - {   "status": "Failed",   "error": {     "code": "ResourceDeploymentFailure",
| "message": "The resource operation completed with terminal provisioning state 'Failed'.",     "details": [       {         "code": "VMExtensionProvisioningError",         "message": "VM has reported a
| failure when processing extension 'Microsoft.Powershell.DSC'. Error message: "DSC Configuration 'BotServers' completed with error(s). Following are the first few: PowerShell DSC resource
| MSFT_ServiceResource  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter
| is set to Stop: Service 'AVB (AVB)' cannot be started due to the following error: Cannot start service AVB on computer '.'.  The SendConfigurationApply function did not succeed. LCM failed to start
| desired state configuration manually."\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "       }     ]   } } (Code:Conflict)   Status
| Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details. (Code: DeploymentFailed)  - {
| "status": "Failed",   "error": {     "code": "ResourceDeploymentFailure",     "message": "The resource operation completed with terminal provisioning state 'Failed'.",     "details": [       {
| "code": "DeploymentFailed",         "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage
| details.",         "details": [           {             "code": "Conflict",             "message": "{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n
| "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n    "details": [\r\n      {\r\n        "code": "VMExtensionProvisioningError",\r\n
| "message": "VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'. Error message: \"DSC Configuration 'BotServers' completed with error(s). Following are the first few:
| PowerShell DSC resource MSFT_ServiceResource  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable
| \"ErrorActionPreference\" or common parameter is set to Stop: Service 'AVB (AVB)' cannot be started due to the following error: Cannot start service AVB on computer '.'.  The
| SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\"\r\n\r\nMore information on troubleshooting is available at
| https://aka.ms/VMExtensionDSCWindowsTroubleshoot "\r\n      }\r\n    ]\r\n  }\r\n}"           }         ]       }     ]   } } (Code:Conflict)   CorrelationId: 1de951ee-10ea-4aec-b93c-42642d1df6a0
Additional context
Add any other context about the problem here.

It seems like your cloud service is not of the correct type, it should be Cloud Service (Classic).

same error when deploying EchoBot. @poiriersimon were you able to solve the issue eventually?

I did do a pull request on the AudioVideoBot, there was some issue with fix
value in the code, if I recall correctly.
On Tue, Mar 21, 2023 at 12:30 PM anastasiya-moodbit <
@.***> wrote:

same error when deploying EchoBot. @poiriersimon
https://github.com/poiriersimon were you able to solve the issue
eventually?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/552#issuecomment-1478176800,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKNXIZAY7RFG32Z2LFYBUTW5HJS5ANCNFSM5XLMQNIQ
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>


Is it possible to improve compile times?

I just created the basic gtk button example from the book and ran cargo build --timings on windows 11, ryzen 2600x (12 threads), 16 GB DDR4.

95 seconds seems really long on a reasonably powerful machine. Especially considering that gtk is dynamically linked.
I was wondering if there's a way to reduce compile times.

I think the only way to improve compile times here is optimizing the compiler. My main guess for the long compile times is the huge amount of extension traits used by gio/gtk4.
Outside compile times, using mold as linker improves linking times for gtk4-rs applications considerably.


A lot of API's do not have the Description field set which results in the search page being unusable sometimes

Link to article:
https://docs.microsoft.com/en-us/rest/api/?term=list resource
Problem:
If you look at this page you'll see a table with name List and no description for many different API's. It's impossible to tell what each one of these API's is for without mousing over and viewing the link for each of them.
Screenshot attached.

@rloutlaw can your team look at this? Is this some indexing issue?

@minhaz1 Thanks for reporting this.
@mairaw  This is a issue w/ the Service Fabric docs not having summary pages that we pull the descriptions from-our API browser doesn't have the content to ingest to put the right descriptions to the links in the report.
I'll work with that team to get those pages in place/ generated by their handauthored process, and then we'll rebuild the index so add the descriptions.


'atomic-reactor build path' tracebacks with FileExistsError

atomic-reactor tracebacks when trying to build an image from a local path. Reproducer:
$ cat ./Dockerfile
FROM fedora:latest
RUN dnf -y install docker-io git python-docker-py python-setuptools koji atomic-reactor && dnf clean all
CMD ["atomic-reactor", "-v", "inside-build", "--input", "path"]
$ docker build -t buildroot-hostdocker .

$ git clone https://github.com/OpenSCAP/openscap-daemon/
$ cd openscap-daemon/ && ./generate-dockerfile.py && cd ../
$ atomic-reactor -v build path --method hostdocker --build-image buildroot-hostdocker --image test/openscap --uri ./openscap-daemon/
2018-03-05 17:17:05,045 - atomic_reactor.outer - INFO - building image 'test/openscap'
2018-03-05 17:17:05,046 - atomic_reactor.core - INFO - building image 'buildroot-hostdocker' in container using docker from host
2018-03-05 17:17:05,046 - atomic_reactor.core - DEBUG - build input: image = 'buildroot-hostdocker', args = '{"image": "test/openscap", "source": {"provider_params": {}, "provider": "path", "uri": "./openscap-daemon/", "dockerfile_path": null}, "postbuild_plugins": [{"name": "tag_and_push", "args": {"registries": {}}}], "prebuild_plugins": [{"name": "pull_base_image", "args": {"parent_registry": null, "parent_registry_insecure": false}}]}'
2018-03-05 17:17:05,046 - atomic_reactor.core - INFO - checking whether image 'buildroot-hostdocker' exists
2018-03-05 17:17:05,046 - atomic_reactor.core - DEBUG - image_id = 'buildroot-hostdocker'
2018-03-05 17:17:05,049 - atomic_reactor.core - DEBUG - image exists: True
2018-03-05 17:17:05,050 - atomic_reactor.source - DEBUG - workdir is '/tmp/tmp_79hipxs'
2018-03-05 17:17:05,050 - atomic_reactor.source - DEBUG - source path is '/tmp/tmp_79hipxs/'
Traceback (most recent call last):
  File "/usr/bin/atomic-reactor", line 11, in <module>
    load_entry_point('atomic-reactor==<IP_ADDRESS>', 'console_scripts', 'atomic-reactor')()
  File "/usr/lib/python3.6/site-packages/atomic_reactor/cli/main.py", line 299, in run
    cli.run()
  File "/usr/lib/python3.6/site-packages/atomic_reactor/cli/main.py", line 282, in run
    args.func(args)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/cli/main.py", line 133, in cli_build_with_source
    cli_build_image(args)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/cli/main.py", line 52, in cli_build_image
    response = build_image_using_hosts_docker(args.build_image, **common_kwargs)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/api.py", line 110, in build_image_using_hosts_docker
    build_response = m.build()
  File "/usr/lib/python3.6/site-packages/atomic_reactor/outer.py", line 139, in build
    partial(BuildContainerFactory.build_image_dockerhost, w))
  File "/usr/lib/python3.6/site-packages/atomic_reactor/outer.py", line 56, in _build
    self.build_container_id = build_method(self.build_image, self.temp_dir)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/core.py", line 137, in build_image_dockerhost
    self._obtain_source_from_path_if_needed(json_args_path, CONTAINER_SHARE_PATH)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/core.py", line 98, in _obtain_source_from_path_if_needed
    source = get_source_instance_for(build_json['source'], tmpdir=local_path)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/source.py", line 138, in get_source_instance_for
    return klass(**args)
  File "/usr/lib/python3.6/site-packages/atomic_reactor/source.py", line 105, in __init__
    os.makedirs(self.source_path)
  File "/usr/lib64/python3.6/os.py", line 220, in makedirs
    mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/tmp/tmp_79hipxs/'

The issue is reproducible on both Fedora 26 and 27:
atomic-reactor-<IP_ADDRESS>-1.fc26.noarch
atomic-reactor-<IP_ADDRESS>-4.fc27.noarch

I can reproduce with version {{<IP_ADDRESS>}}

See #1015.


Mark backgroundTrackingNotificationProvider in the Builder as REQUIRED

When constructing a publisher using Builder omitting backgroundTrackingNotificationProvider parameter leads to
com.ably.tracking.BuilderConfigurationIncompleteException: Some of the required builder parameters are missing.
backgroundTrackingNotificationProvider should be marked as REQUIRED in the Builder doc comments and set in the example snippet in the "USAGE" section of README.md
┆Issue is synchronized with this Jira Task by Unito

+1, I wanted to report the same issue, but not only for the notification. In the subscriber SDK, we get a generic error like this: com.ably.tracking.BuilderConfigurationIncompleteException: Some of the required builder parameters are missing. It would be useful for users to know which parameters are missing.


Correcting invalid URL for Kubernetes

Fixed #123

Thank you fo the contribution. It looks good to me, however, your commit comment needs to be updated to have Signed-off-by: field. Please follow the following URL: https://github.com/containernetworking/cni.dev/pull/124/checks?check_run_id=14314151949, thanks!

Should I close this one and PR new one @s1061123 ?


error when issuing dfx canister call in not top-level project directory

If I run dfx canister call inside the top-level project directory, e.g. /test/src/, I get the following error.
/tmp/test/src$ dfx canister call test_assets retrieve '"sample-asset.txt"'
Cannot find canister id.  Please issue 'dfx canister create test_assets'.

dfx now looks in parent folders


Fix: Android Studio Iguana build issues

This pull request addresses issues that arose following the release of Android Studio Iguana.
Build -> Clean Project problem:

Build -> Rebuild Project problem:

Note: Jetpack Compose tests have been removed due to prolonged lack of maintenance, resulting in compile errors during the build process.

Thanks for the pull request, @volodymyr-chekyrta! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@volodymyr-chekyrta After updating the org.gradle.jvmargs -Xmx2048m -Dfile.encoding=UTF-8 -> -Xmx4608m -Dfile.encoding=UTF-8 in gradle.properties error got fixed, but warnings are still there.

IMO, it's better to consider the warning to be fixed as part of this PR.

@volodymyr-chekyrta After updating the org.gradle.jvmargs -Xmx2048m -Dfile.encoding=UTF-8 -> -Xmx4608m -Dfile.encoding=UTF-8 in gradle.properties error got fixed, but warnings are still there.

IMO, it's better to consider the warning to be fixed as part of this PR.

@farhan-arshad-dev
Yes, I left this issue for future investigation. On my machine that value should be at least -Xmx6144m, so it looks like we'll have to wait for Android Studio to sort it out.

IMO, it's better to consider the warning to be fixed as part of this PR.

@farhan-arshad-dev, this PR concentrates on fixing critical build issues, lets fix warnings in the separate code health PR

@volodymyr-chekyrta 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Network Connectivity API: networkconnectivity.googleapis.com

The API reference only mentions REST...
But here is a public proto: https://github.com/googleapis/googleapis/blob/7bc124cb895a4131f2a6338661db0566e272bd25/google/cloud/networkconnectivity/v1/hub.proto#L54

IAM has the same problem.  I think when gRPC is a documented API it definitely works, but sometimes it works even if undocumented.

The operator should try again.


one question --php_out: protoc-gen-php: Plugin output is unparseable: This is a stub file for IDEs, don't use it directly!

devtools:MacOS, PHP7.3 protoc 3.13
question:
protoc --plugin=protoc-gen-allegrophp=protoc-gen-php.php --allegrophp_out='./' movie.proto
the message : --php_out: protoc-gen-php: Plugin output is unparseable: This is a stub file for IDEs, don't use it directly!
#106 I don't understand what can i do, please tell me more detail thanks.

ProtobufMessage.php is not referenced from php-protobuf source. If you see this error message it means ProtobufMessage.php gets included by your environment when running php process. Make sure this file is not included.


[Bug]: After a disk is offline, you can query disk information through the api

Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched all the existing issues

Priority
low (Default)
Environment
- CubeFS version:v3.3.0
- Deployment mode(docker or standalone or cluster):cluster
- Dependent components:
- OS kernel version(Ubuntu or CentOS): euleros   5.10.0-<IP_ADDRESS>.h592
- CPU/Memory:  16G
- Others:

Current Behavior
When I offline disk /data0， I checked curl -v "http://master2:17320/disks" and found that the disk was still there
Expected Behavior
No response
Steps To Reproduce
No response
CubeFS Log
No response
Anything else? (Additional Context)
No response

It seem that TryDecommissionDisk just offline add data partitions on disk?
I have a solution of this problem:

Add DecommissionDisk pattern to DeleteDataPartitionRequest.
If a disk be decommissioned, we will set its DeleteDataPartitionRequest::DecommissionDisk to true when offline data partitions.
When datanode receive this request, it will mark disk to be decommission, and if disk's data partition count is 0, disk
will be decommissioned and not show in /disks api.
If a datanode receive a CreateDataPartitionRequest to place a partition to decommissioned disk(in datanode'
s view), the datanode will know it's decommission status is not up-to-date and make the disk online.

Please point out any mistakes or misunderstandings on my part.


Add to audit table username

Supa_audit is fantastict!, but, to my total satisfaction, I miss being able to have a field with the username that performs the crud operation
My postgrsql knowledge is poor, sorry if i ask something impossible or trivial.
Would it be possible to add the username that performs the operation (insert, update, delete)?
Thanks

it depends where your user_id is coming from

if you're on the supabase platform, 2 additional columns are enabled by default that track the user's id and the user's role

if user_id is in the table you're auditing
alter table audit.record_version add column user_id bigint default (coalesce(record, old_record) ->> 'user_id');

will add a user_id column and track it in the table

if you mean the SQL current_user you could extend the trigger to track it.

if the concept of a user_id comes from the application thats connecting to the database, netcraft posted an option for adding it here https://news.ycombinator.com/item?id=30615470

Thank you Oliver


bpf: egressgw: support policy entry with egress ifindex

When the EGW policy lookup returns the ifindex of the egress interface, skip the FIB-lookup based selection and redirect straight to the desired interface.
This currently only covers the minimal datapath part. To make full use of this enhancement we'll also need CEGP control plane improvements (and migrate to an EGW policy entry with space to store the ifindex).

/test


bfs.c: Add BFS

Breadth First Search is an algorithm used to search the Tree or Graph. BFS search starts from root node then traversal into next level of graph or tree and continues, if item found it stops other wise it continues.
Closes #35

Thanks for contributing.


Fix wrongly parsed Decimal fields

When special-casing the request parser for Decimal, passing the name of the field as the second argument is incorrect:
            try:
                if self.type is decimal.Decimal:
                    return self.type(str(value)) .   # <--- Incorrect second parameter, can never work in py3
                else:
                    return self.type(value, self.name)
            except TypeError:
                return self.type(value) # <--- Fallback, but without string conversion

The second argument of Decimal is a context. Python 3 checks this is, in fact, a context, whereas Python 2 ignores it if not needed. This means in Python 3 that special-case line is never successful, so it is handled below. However, there is a difference: the first converts to string, the second does not. This results in different values of Decimal being parsed:
>>> import decimal
>>> value = 89.92
>>> decimal.Decimal(str(value))
Decimal('89.92')
>>> decimal.Decimal(value)
Decimal('89.9200000000000017053025658242404460906982421875')
>>>```

This simply stops passing the field name as the second argument and adds a test to check this case.

I don't work on this very actively anymore especially since I don't use flask-restful in any current projects. I don't have a good picture in my head anymore of where this package is at with various bugs and fixes since the last release so generally I would advise you to install the package from a git url at a specific commit instead of from PyPI.


pkg/components/util: only filter release namespace

As part of upstream Helm chart sanitization, we remove all Namespace
objects, as we create them manually before the release is installed,
otherwise Helm will complain. This is the solution from times, where
charts were not updates to not include or conditionally include the
namespace and Helm (v2) was storing all release objects in kube-system
namespace.
This commit changes this behavior to only filter single namespace
object, which is where we will be installing the release. This patch
aims to fix the installation of charts, which spans across multiple
namespaces like for example linkerd.
Right now, many helm charts offers an option to disable namespace
creation already, which we should eventually utilize and disable the
filtering completely, as it is confusing and brings non-obvious results,
especially when comparing 'lokoctl component install' with 'helm
install'. However, this is out of scope for this changeset.
Signed-off-by: Mateusz Gozdek<EMAIL_ADDRESS>

This is the solution from times, where
charts were not updates to not include or conditionally include the
namespace and Helm (v2) was storing all release objects in kube-system
namespace.

Can you fix the wording in the part charts were not updates to not include or conditionally?

aims to fix the installation of charts, which spans across multiple
namespaces like for example linkerd.

Correction, it is istio that needs two namespaces. One for istio operator called istio-operator and another for istio control place called istio-system. Linkerd does everything in same namespace.

Fixed the wording @surajssd


PERF: neon-cluster-operator after a few hours or cluster restart

It looks like neon-cluster-operator does off the deep end after running for a few hours and starts slamming the API server.  This happens quicker after gracefully restarting clusters.
We've been tracking this for a while and I thought that this was related to the neon-acme pod not serving it's OpenAPI spec at the correct URI which is being logged by the API server.  That's still a problem, but I no longer believe that's causing the performance problem.
I tried enabling the Istio Service Mesh to debug, but that's breaking the cluster.  I've also run the operator in the debugger, but I wasn't able to reproduce the problem.  I'm going to have to try adding more logging.

This may be related to: #1852

I finally was able to observe the requests slamming the API server after trying:

Enabling Istio Service Mesh and Kiali (which didn't work due to pod crashes)
Looking into API Server auditing which looks interesting but a bit hard to use (probably a good future feature)
Increase the API Server verbosity to --v=6 by editing it's static pod manifest file (which works great)

After gracefully restarting the cluster I see that the API server is getting hit with watch requests like:
{"ts":1692653060136.0608,"caller":"queueset/queueset.go:724","msg":"QS(workload-low) at t=2023-08-21 21:24:20.135981565 R=600.30029445ss: dispatching request &request.RequestInfo{IsResourceRequest:true, Path:\"/apis/neonkube.io/v1alpha1/neoncontainerregistries\", Verb:\"watch\", APIPrefix:\"apis\", APIGroup:\"neonkube.io\", APIVersion:\"v1alpha1\", Namespace:\"\", Resource:\"neoncontainerregistries\", Subresource:\"\", Name:\"\", Parts:[]string{\"neoncontainerregistries\"}} &user.DefaultInfo{Name:\"system:serviceaccount:neon-system:neon-cluster-operator\", UID:\"3dd0752e-8f37-40d6-812a-9e9d3647f6de\", Groups:[]string{\"system:serviceaccounts\", \"system:serviceaccounts:neon-system\", \"system:authenticated\"}, Extra:map[string][]string{\"authentication.kubernetes.io/pod-name\":[]string{\"neon-cluster-operator-rk2kw\"}, \"authentication.kubernetes.io/pod-uid\":[]string{\"e7cb0678-b611-440b-8e97-69e32812764e\"}}} work {{1 0 0s} 300000 0} from queue 26 with start R<PHONE_NUMBER>5ss, queue will have 0 waiting & 1 requests occupying 1 seats, set will have 1 seats occupied\n","v":6}

log.zip

@marcusbooyah: Can you have a look at this?  There seems to be a lot of API Server activity around: neonclusteroperators in this second log (I increased the log verbosity to 7 for this run).
log.zip

Hmmm, maybe two things are going on here.  I disabled neon-cluster-operator and then gracefully shutdown and restarted a new tiny cluster.  Initially, Hyper-V was reporting that the VM was consuming 4-5% but then after a while that increased to about 22%.  In previous tests with the operator running, I was seeing maybe 28-30%.
With the operator disabled, grafana-agent-node and the apiserver seem too busy:

I tried disabling grafana-agent-node and that didn't really help that much (which seems a bit weird) since it was consuming xxxm CPU before.
I also notice that neon-sso-session-proxy consuming 439m CPU, which seems high (what is is doing?)

So it looks like we need to investigate what's happening when these services:

[ ] neon-cluster-operator
[ ] neon-sso-session-proxy
[ ] grafana-agent-node

neon-cluster-operator
I disabled all of the quartz jobs here and re-enabled them one-by-one and waited a a few hours so see which one might be going rouge.  This took a few days but it looks like the problem is being caused by SendClusterTelemetryJob.  I'm running the test again now to confirm.
I also noticed that neon-cluster-operator cron jobs schedules are all bunched up at 12:00am UTC, which we probably don't want, especially for jobs like send telemetry which means that all NEONKUBE clusters will send telemetry to the headend at the same time :)

...we should also try to spread some of the other schedules out across the 12am hour to reduce the impact on the user's cluster.


Change repo ACL for Harmonia

Repo to change access: https://github.com/hyperledger-labs/harmonia
GitHub ID to add: fowlerrr and ILoomans

Hi there - I'm not exactly sure which permission we need but could you give the two IDs above the ability to write to the Harmonia repo please? That is: we need them to be able to create/push to new branches, etc., from which they can then raise PRs for merging to main.  Many thanks - Richard.

Both added. They need to accept the invite.

Thank you!


Pass kwargs to settings

To enable users to manually specify settings (e.g. pass them in via keyword arguments), cached settings should pass along keyword arguments.
This is an alternative solution to #54.

I'm fine with #54, we can close here


Consolidate Example: dataframe_subquery.rs into dataframe.rs

Is your feature request related to a problem or challenge?

Part of https://github.com/apache/datafusion/issues/11172

The large number of small examples in DataFusion leads to multiple problems:

Makes it harder to find the relevant examples
Unnecessarily large amounts of disk space on a full build (each example binary takes 100+ MB)
Larger cargo t time (each binary must be linked / created)

Thus I think the fewer examples we have the

easier it will be to find the relevant examples
faster our dev experience will be

Describe the solution you'd like

Consolidate the contents of https://github.com/apache/datafusion/blob/main/datafusion-examples/examples/dataframe_subquery.rs
Into https://github.com/apache/datafusion/blob/main/datafusion-examples/examples/dataframe.rs

Then update the readme page:

https://github.com/apache/datafusion/blob/main/datafusion-examples/README.md

Describe alternatives you've considered
No response
Additional context
I think this is a good first issue as the task is straightforward and doesn't require deep understanding of the DataFusion codebase

take.


arch: arm: aarch32: rename z_arm_lib_init() function

We rename the z_arm_lib_init() function to
z_arm_interrupt_init(), aligning to how other
ARCHes name their IRQ initialization function.
There is nothing about 'library' in this
functionality, so we remove the 'lib' in-fix.
The commit does not introduce any behavior changes.
Helper for  #22718
Signed-off-by: Ioannis Glaropoulos<EMAIL_ADDRESS>

It would be helpful to fix the commit message to mention the correct old name for the sake of future reference.
s/z_arm_lib_init/z_arm_int_lib_init/

Will fix, thanks.

Fixed   @stephanosio


Question: Any plans to support new BOSH CLI features like variable interpolation?

Just wondering if there has been any talk of supporting some of the new Golang CLI features like variable interpolation or create-env in this resource.
cc @vito @cppforlife @dpb587-pivotal

Probably not create-env; I think that may be better off as a bosh-env-resource or something, since it has to persist the state file somewhere.
Supporting var interpolation sounds like a great idea. I don't know when we'd get to it, though. :/ I'll mark this as "help wanted".
Something like this?:
put: my-deployment
params:
  var_files:
  - path/to/foo.yml
  - path/to/bar.yml
  vars:
  - name: foo
    value: bar

@vito looks good to me. Although I wonder once the BOSH Config Server is released maybe variable interpolation from the CLI becomes less useful. Not sure what the long-term vision is there.

There'd probably still be a use-case for deploy-time-provided vars even with most of them coming from the config server.

On credhub we've noticed that normal BOSH client erb interpolation doesn't work. The resource tries to read the YAML first, which quite reasonably chokes on erb snippets.
Not sure if this is considered same / related; hence the comment instead of a new issue.

Since cloudfoundry/bosh-deployment-resource exists now, I'm going to say no.
Thanks all for your input!

Will this one be retired in favour of it?

Yep, once we figure out a deprecation strategy. It may just look like
taking it out of the core set and having release notes instruct you to have
it as a custom resource type until you can switch to the cloudfoundry one.
On Wed, Mar 29, 2017, 9:12 AM Jacques Chester<EMAIL_ADDRESS>wrote:

Will this one be retired in favour of it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/concourse/bosh-deployment-resource/issues/35#issuecomment-290085347,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHWKHp-dJNmaCVAUwerIGO0P_6bUkxks5rqljZgaJpZM4K21j7
.


[ENG-9422][eas-cli] Use .nvmrc to set node version

Why
https://exponent-internal.slack.com/archives/C02123T524U/p1689882938014309
How
Read .nvmrc content and set node value in buildProfile.
Test Plan

Create valid .nvmrc file
Build project
Check in build logs if non-default node version is installed.

/change-log feature .nvmrc support for setting node version

/changelog-entry new-feature .nvmrc support for setting node version


Release first version on Clojars

And explain how to use it in the Readme.
What should we do to make it usable from Maven?

Before releasing v0.1.3 we should update the changelog. @davidor did I miss anything?
Then we should add a tag and upload to clojars

Looks good to me.

And it should be done: https://clojars.org/effectivejava
Probably this code is going to be used as a standalone utility and not a library so for now I am not documenting it in the README.


[Question] ConvNeXt layers in MergeHandler

I am trying to implement a graph for convnext, which has a custom module: LayerNorm2d. In there, the input is permuted before sent through LayerNorm. The mergehandler can use handle_layernorm for that right? no need to implement another function if I understand it right. That ties in with the question, if a torch.nn.Permute needs anything else but a "handle_fn" handler

Hi,

Yes the LayerNorm2d handler should already contain everything you need.
For Permute, I believe it should look very similar to the handle_fn logic, except that you will further have to permute the dimensions of the merge/unmerge according to permutation defined in the module.

you mean LayerNorm handler, right? there is no layernorm2d handler.
okay, i shall try that.

Thanks

For 1 - yes sorry. And 2 sounds good. Also, I just replied to your email as well about meeting :) Please let me know if I can help with anything else!


Add checksum insertion and offloading

The stm32 has a built-in module to automatically handle checksums inside IP headers and TCP, UDP, and ICMP payloads, on both the transmit and receive paths. For reference, the stm4 manual covers transmitting on pages 1141 and 1172, and receiving on pages 1145 and 1184.
For transmission, this involves setting two CIC bits in the transmit descriptor so that checksums are calculated and inserted. On the receive side, we set a bit in the maccr register, and the error is grouped into the general error summary flag on the receive descriptor.
In my (very rough) profiling, this change resulted in about a 30% speedup at 75 Mbps Tx over doing the checksums in software inside smoltpc.
Looking through some other manuals, this feature appears to be supported in all MCUs that have a hardware ETH controller. For example:

stmf1 manual, pages 987, 1019, etc.
stmf7 manual, pages 1784, 1816, etc.

Let me know if this would be better done some other way, such as config setting, feature, ...

I think this sounds like a good addition, and it would make sense to enable unconditionally given that it appears that all parts support this feature, and it almost exclusively comes with upsides.
All appropriate bits seem to be set:

cic0 and cic1, and tsf for TX checksum offloading
ipco for RX ipv4 checksum offloading

The CI seems to agree with your observation about it being supported on all parts, so that's very nice too.
@korken89 @thalesfragoso would appreciate another look
Left a small request for a little extra documentation

Correction: I thought we had already enabled enhanced descriptors (edfe in ETHDMABMR), but it seems like I have made a mistake there. On stm32f4xx (and most likely stm32f7xx parts), enhanced descriptors must be enabled for offload support. See page 1186 of the f4 RM.

Interesting! I had missed that part of the manual. I'm on an stm32f429 and, as far as I could tell, packets with malformed headers were still dropped even without enabling enhanced descriptors and correct packet data came through unaltered...
Is it alright to set the descriptor width to 8 words even on the f1 parts, or should there be a config check there as well?

Aha, that's interesting indeed! Wonder how that works...
Hmm, I'm not sure. We're running the descriptors in "chain" mode (aka singly-linked-list mode), so it should be fine since the descriptors will point to the next entry by address. However, I don't have access to an f1 so have no way to test it.
I think it'd be best if we avoid using 8-word wide descriptors on f1 for now. Luckily, it's quite easy:
#[cfg(not(feature = "stm32f107"))]
const DESC_SIZE: usize = 8;

#[cfg(feature = "stm32f107")]
const DESC_SIZE: usize = 4;

#[repr(C)]
pub struct Descriptor {
    desc: Aligned<A8, [u32; DESC_SIZE]>,
}

...
impl Descriptor {
    pub const fn new() -> Self {
        Self {
            desc: Aligned([0; DESC_SIZE]),
        }
    }
...
}

LGTM!


Change Mix.output() method.

I think the mix.setResourceRoot() method should change the output.publicPath option value due to the method comments, but it DOES NOT. So I made a small change :smile:

We actually don't need this, but thanks!


Week 3 Walkthrough Part 2

Just completed the fetch walkthrough for the week 3 project.

Modified the javascript, and html files to use a fetch request instead of hardcoded facts for the fun fact generator.
pom.xml needed the dependency with the servlet, so I added that.

Were you intended to include any js changes?

Yes. I thought I did. I'll include it with my resolved commit.


Add length property to Ranges with signed-number Bound values

Fixes #108. Should I add tests for these? that seems redundant/too granular

also, is it ok that this potentially produces infinity if there's overflow?

for instance:
var a = Int16.min...Int16.max
a.length // error

Codecov Report

Merging #111 into master will decrease coverage by 0.49%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #111     +/-   ##
=========================================
- Coverage   88.71%   88.22%   -0.5%
=========================================
  Files          49       50      +1
  Lines        1436     1444      +8
=========================================
  Hits         1274     1274
- Misses        162      170      +8

Impacted Files
Coverage Δ

ArithmeticTools/RangeTypeExtensions.swift
0% <0%> (ø)

Continue to review full report at Codecov.

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

Looks good to me!


Re-organize landing page

Fix squished option box in decision tree.
Align section title to the left.
Change content in each section.
Add instruction for GPU.
Link discussion to Github issue template.

That's awesome :) thank you so much!


azcore 1.8.0 prevents the usage of the sdk against non-https test endpoint

Bug Report
in azcore 1.8.0, a new Policy was added in azcore to ensure BearerToken are not sent to an http endpoint.
That's a great addition to ensure we don't leak tokens.
However, we are also unable to configure the clients to not set a bearer token on the outgoing request.
that makes us unable to use the SDK in internal integration testing where we use HTTP enpoints to avoid the overhead of certificate setup.
Would you consider adding an option to make this possible?
I don't think we should allow sending a BearerToken to an httpendpoint, but if we could configure the sdk with a NoAuthIdentity type or remove the BearerTokenPolicy from the clients, that would allow us to do this, without the risk of sending a token over insecure channel.
Our current workaround is to wrap the transport, and strip the fake bearer token from the header, but that is really hacky, and has some complexity caused by Poller, and Paging on List calls.

/cc @jim-minter @FumingZhang

remove the BearerTokenPolicy from the clients

https://github.com/Azure/azure-sdk-for-go/blob/5d4f3428475ed9a2fc9a1e5d0694974977c4c446/sdk/azcore/arm/runtime/pipeline.go#L32-L38
I wonder whether something like wrapping the above with if cred != nil might do the trick?  I think that would prevent a BearerTokenPolicy being added to the client if no credential is passed in, which would then avoid the error if an http endpoint is being used in test?
+1 that the gymnastics we're having to pull to workaround this are really awful.

That would work. However, I think what we should settle on is the overall pattern on how unit tests should work WRT credentials across all SDKs.

pass nil which skips adding the authentication policy
provide a TokenCredential type in azcore that does the right thing (e.g. fake.TokenCredential)
have some other opt-out mechanism (not a fan of this)

When you write unit tests, which is easier for you? Passing nil or some fake credential type?

CC @JeffreyRichter

I will add that passing nil to prevent inclusion of the authentication policy means that clients in unit tests now behave slightly different from their production counterparts. Maybe this is ok, but I do think there's value in having unit tests behave as close to production as possible.

Note: it's more of an integration test scenario; it's not a unit test scenario.
It seems logical to me to pass a nil cred if no Authorization header is wanted, but our integration scenario is a rare use case, and if that flow is enabled, it might become a common error case for new SDK users to pass a nil cred and then be confused when they get a 401 back from production ARM?
It's not clear to me that fake.TokenCredential helps much here.  FWIW at the moment we're having to pass something equivalent to fake.TokenCredential (our azcore version isn't yet new enough that fake.TokenCredential is available) because clients can't cope with a nil credential.  But then the BearerTokenPolicy would need a special case not to warn if the credential came from a fake.TokenCredential.
Reducing this to enabling a nil cred effectively solves two problems for us - we no longer need the fake.TokenCredential equivalent, and as no Authorization header is sent we don't need to workaround the BearerToken error.

CC @chlowell for awareness
At present, the BearerTokenPolicy will panic by design if the TokenCredential is nil.  We've used this as an enforcing mechanism to ensure that client constructors that require a TokenCredential provide one (I don't think we've explicitly documented this though). This is true for other credential types (e.g. SharedKeyCredential in the storage SDKs). In addition, per our design guidelines, if a service accepts unauthorized access, then SDKs are to provide a NewClientWithNoCredential constructor variant.
You are correct that if fake.TokenCredential is to become the thing that we'd have to update the BearerTokenPolicy to not reject the fake token it returns. Off-the-cuff it would likely check for the magic token value fake_token and bypass the http check.

Would you mind expanding on how these tests work?  What I'm wondering is if our fakes (which GA in November) will be a better way to solve this issue.

I see, we could manually implement New*ClientWithNoCredential() functions in our SDKs, but if we were to do this it would probably convenient for azcore to have arm.NewClientWithNoCredential() and armruntime.NewPipelineWithNoCredential() analogs.  I think that something like that could potentially work.

This was introduced by https://github.com/Azure/azure-sdk-for-go/pull/21673

The fix (accepting a nil credential value) will go out in November's<EMAIL_ADDRESS>release.

Thank you @jhendrixMSFT ! Appreciate the quick turn around


Inverted extrusion on clockwise polygon

Expected Behavior
When extruding a valid 2D shape, the "direction" of the points should not matter. Note that I'm porting some code from V1 to V2, and this worked in V1.
Actual Behavior
If you define a polygon with counter-clockwise points, then extrudeLinear works fine. If you pass a clockwise polygon, the resulting geometry is inverted, with faces pointing in.

Steps to Reproduce the Problem
const { extrudeLinear } = require('@jscad/modeling').extrusions
const { polygon } = require('@jscad/modeling').primitives

function main() {
  return extrudeLinear(
    {height: 2},
    polygon({points: [[3, 3], [3, 0], [0, 0]]})
  )
}
module.exports = { main }

Specifications

Version: 2.2.0
Platform: Linux 64
Environment: node.js 14.3.0

Notes
It seems like the problem is that the "side" detection in the polygon doesn't look what is inside vs outside. I'd be willing to try and make a PR if you agree that is the right fix.
Alternatively, would be nice to point out in the docs that point direction matters.
Also, the docs incorrectly state that you can create a polygon like polygon([ [0,0],[3,0],[3,3] ]) without an object, but that is no longer true in V2.
Thanks for the hard work, V2 is a huge step forward!

Alternatively, would be nice to point out in the docs that point direction matters.

The API documentation explicitly says... "NOTE: The ordering of points is VERY IMPORTANT."
https://openjscad.xyz/docs/module-modeling_primitives.html#.polygon
Sadly, we lost some of the documentation on orientation in the User Guide.

Ah fair enough. I just updated doc wiki here

Ah fair enough. I just updated doc wiki here

@platypii thanks. I saw the changes to the user guide.
If satisfied then please close this issue.


[$500] [Mobile] Don't immidiately prompt for Camera permission in Scan Receipt flow

Do not automatically prompt users for the camera permission until the user selects the 'Continue' button -- to prevent permission denials

iOS
Android

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Have camera permission disabled
Request Money
Switch to Scan Receipt

Expected Result:

Nothing should happen

Actual Result:

User is prompted for the camera permission before they have even seen the Explainer UI

Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bc79d21437eb7104
Upwork Job ID:<PHONE_NUMBER>290671616
Last Price Increase: 2024-03-05

Proposal
Please re-state the problem that we are trying to solve in this issue.
Don't immediately prompt for Camera permission in Scan Receipt.
What is the root cause of that problem?
refreshCameraPermissionStatus is called in below code directly.
useEffect(() => {
        const refreshCameraPermissionStatus = (shouldAskForPermission = false) => {
            CameraPermission.getCameraPermissionStatus()
                .then((res) => {
                    // In android device app data, the status is not set to blocked until denied twice,
                    // due to that the app will ask for permission twice whenever users opens uses the scan tab
                    setCameraPermissionStatus(res);
                    if (shouldAskForPermission && !askedForPermission.current) {
                        askedForPermission.current = true;
                        askForPermissions(false);
                    }
                })
                .catch(() => setCameraPermissionStatus(RESULTS.UNAVAILABLE));
        };

        // Check initial camera permission status
        refreshCameraPermissionStatus(true);

        // Refresh permission status when app gain focus
        const subscription = AppState.addEventListener('change', (appState) => {
            if (appState !== 'active') {
                return;
            }

            refreshCameraPermissionStatus();
        });

        return () => {
            subscription.remove();
        };
    }, []);

What changes do you think we should make in order to solve the problem?
refreshCameraPermissionStatus should be called when continue button is clicked.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Don't immidiately prompt for Camera permission in Scan Receipt flow
What is the root cause of that problem?
when scan tab amount in useEffect we call  refreshCameraPermissionStatus with parameter shouldAskForPermission  = true
https://github.com/Expensify/App/blob/9411a08168d53df44a957fd8bb86fd9a363b25b4/src/pages/iou/request/step/IOURequestStepScan/index.native.js#L138-L139
What changes do you think we should make in order to solve the problem?
in useEffect don't pass shouldAskForPermission with true to prevent prompt for Camera permission when scan tab amount
 //refreshCameraPermissionStatus(true);
 refreshCameraPermissionStatus();

What alternative solutions did you explore? (Optional)

We should remove the logic to ask permission in refreshCameraPermissionStatus function and use the old logic below or we only apply it for Android device

@dukenv0307 perhaps I missunderstand, but if we only apply it for Android, wouldn't the issue still exist for Android?

@dukenv0307

We should remove the logic to ask permission in refreshCameraPermissionStatus function and use the old logic below

You just threw the term "old" without any context. What old logic? When and why was this logic removed?

or we only apply it for Android device

Again, you mentioned potential Android-specific behavior without any context. Why would we want to be Android-specific? I can see that this was brought in the discussion above; ensure to include the minimal necessary context in the proposal itself.

@dukenv0307
Thank you!
I agree that the crucial part is ensuring to keep https://github.com/Expensify/App/issues/34750 fixed while improving the user experience at the same time. We'll have to double-check this on the implementation phase.

I approve the proposal by @dukenv0307
C+ reviewed 🎀 👀 🎀

❌ There was an error making the offer to @cubuspl42 for the Reviewer role. The BZ member will need to manually hire the contributor.

❌ There was an error making the offer to @dukenv0307 for the Contributor role. The BZ member will need to manually hire the contributor.

FYI @stephanieelliott

PR is actively being reviewed.

@Julesssss
Is there a difference in the expected behavior between mWeb and Native? Don't we want to show the Explainer UI on mWeb and delay the permission prompt, too?

Is there a difference in the expected behavior between mWeb and Native? Don't we want to show the Explainer UI on mWeb and delay the permission prompt, too?

I don't believe we allow users to use the camera on Desktop/Web, so no we shouldn't be showing the prompt.

Looks like all PR changes requests have been addressed, just waiting for internal approval

I don't think we're there yet. I asked for clarification of an important bit. But we're actively working on this.

PR merged and deployed to staging 🚀

The PR that introduced the bug has been identified. Link to the PR:

This bug was a Native/mWeb inconsistency, I don't think any specific PR introduced it

The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

N/A

A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

No need for additional discussion

Determine if we should create a regression test for this bug.

Up to the QA team

If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Android Native / iOS Native / mWeb:

Reset app / web app permissions
Navigate to FAB > Request Money > Scan.
Confirm that the camera request permission prompt does not appear.
Click on the 'Continue' button or the 'Capture' icon.
Verify that the camera request permission prompt now appears.
Accept the permission and ensure that photo capture is possible.

Hey @cubuspl42 @dukenv0307 please accept the Upwork offer when you get a chance https://www.upwork.com/jobs/~011f4474761d208ba4

Done 👍

Thanks @cubuspl42, you've been paid.

ROLE: @dukenv0307 Upwork offer extended, please accept

@dukenv0307 bump on this!

All paid! See summary here: https://github.com/Expensify/App/issues/37737#issuecomment-2045800619


Bug when maximizing and toggling panel

VSCode Version: 1.28.1
OS Version: WSL2

Steps to Reproduce:

Press 'Maximize Panel Size' (workbench.action.toggleMaximizedPanel)
Press "workbench.action.terminal.toggleTerminal" hotkey.
Press "workbench.action.terminal.toggleTerminal" hotkey again.

The panel has now been resized to almost but not quite cover the editor. It needs to be resized back manually with the mouse to see the editor again.
It should either go back to the original size from before it was maximized, or still be maximized when brought back up.
Does this issue occur when all extensions are disabled?: Yes
Not exactly the same as #79891 but if you fix one you could fix the other too.

This is resolved in the latest version


Automate index expiry in the logging cluster

Currently we keep application logs in the logging cluster (logging.wellcomecollection.org) until the disk fills up, and then we go clear out the indexes by hand.
This is inefficient – we should keep logs on a rolling buffer that's automatically pruned (say, last 30 days) rather than cleaning them up by hand.

So apparently this is already configured, but it's not working for some reason:

🤔

Okay, so looking for templates:
GET _cat/templates/firelens*

I found a template called firelens-* which was empty.
GET _template/firelens-*
{ }

I created a new template:
PUT _template/firelens
{
    "order" : 2,
    "index_patterns" : [
      "firelens-*"
    ],
    "settings" : {
      "index" : {
        "lifecycle" : {
          "name" : "expire_after_7_days",
          "rollover_alias" : "firelens"
        }
      }
    },
    "mappings" : { },
    "aliases" : { }
}

It seems to have cleared up the warnings, but just to be on the safe side I'll also delete some indices before I finish today.

Checking today, indexes aren't being deleted and the error is recurring. I'll dig into this more today.

I deleted all the indexes to the beginning of March, which kicks this down the road but will at least stop it alerting for now.

Closing as done.


Constant.is_psd() not working on singular matrix

Describe the bug
Hi everyone, years ago I wrote a piece of code to solve a problem of which the objective function is a quad_form. The code runs smoothly with following output (CVXPY 1.0.21):
----------------------------------------------------------------------------
	SCS v2.1.4 - Splitting Conic Solver
	(c) Brendan O'Donoghue, Stanford University, 2012
----------------------------------------------------------------------------
Lin-sys: sparse-direct, nnz in A = 2813
eps = 1.00e-04, alpha = 1.50, max_iters = 5000, normalize = 1, scale = 1.00
acceleration_lookback = 10, rho_x = 1.00e-03
Variables n = 257, constraints m = 443
Cones:	primal zero / dual free vars: 210
	linear vars: 1
	soc vars: 22, soc blks: 1
	sd vars: 210, sd blks: 1
Setup time: 5.64e-03s
----------------------------------------------------------------------------
 Iter | pri res | dua res | rel gap | pri obj | dua obj | kap/tau | time (s)
----------------------------------------------------------------------------
     0| 4.58e+19  1.17e+20  1.00e+00 -1.90e+21  2.36e+21  5.41e+21  4.80e-03
   100| 1.03e-03  5.47e-04  2.42e-04  1.31e+01  1.31e+01  8.85e-16  2.49e-02
   140| 7.44e-05  4.99e-05  6.20e-05  1.31e+01  1.31e+01  1.29e-15  3.31e-02
----------------------------------------------------------------------------
Status: Solved
Timing: Solve time: 3.32e-02s
	Lin-sys: nnz in L factor: 3838, avg solve time: 7.10e-06s
	Cones: avg projection time: 3.77e-05s
	Acceleration: avg step time: 1.46e-04s
----------------------------------------------------------------------------
Error metrics:
dist(s, K) = 1.9019e-16, dist(y, K*) = 1.8934e-09, s'y/|s||y| = 7.1036e-13
primal res: |Ax + s - b|_2 / (1 + |b|_2) = 7.4450e-05
dual res:   |A'y + c|_2 / (1 + |c|_2) = 4.9888e-05
rel gap:    |c'x + b'y| / (1 + |c'x| + |b'y|) = 6.1957e-05
----------------------------------------------------------------------------
c'x = 13.0637, -b'y = 13.0621
============================================================================

However, after I updated cvxpy to the newest version, I cannot solve the problem anymore, cvxpy tells me that my problem does not follow DCP rules.
===============================================================================
                                     CVXPY
                                    v1.1.15
===============================================================================
(CVXPY) Aug 31 04:25:38 PM: Your problem has 201 variables, 4 constraints, and 0 parameters.
(CVXPY) Aug 31 04:25:38 PM: It is compliant with the following grammars:
(CVXPY) Aug 31 04:25:38 PM: (If you need to solve this problem multiple times, but with different data, consider using parameters.)
(CVXPY) Aug 31 04:25:38 PM: CVXPY will first compile your problem; then, it will invoke a numerical solver to obtain a solution.
  File "C:\Users\Lee\algorithms.py", line 101, in solve
    self.__problem.solve(*args, **kwargs)
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\problems\problem.py", line 462, in solve
    return solve_func(self, *args, **kwargs)
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\problems\problem.py", line 949, in _solve
    data, solving_chain, inverse_data = self.get_problem_data(
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\problems\problem.py", line 570, in get_problem_data
    solving_chain = self._construct_chain(
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\problems\problem.py", line 798, in _construct_chain
    return construct_solving_chain(self, candidate_solvers, gp=gp,
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\reductions\solvers\solving_chain.py", line 155, in construct_solving_chain
    reductions = _reductions_for_problem_class(problem, candidates, gp)
  File "C:\ProgramData\Anaconda3\lib\site-packages\cvxpy\reductions\solvers\solving_chain.py", line 91, in _reductions_for_problem_class
    raise DCPError(
cvxpy.error.DCPError: Problem does not follow DCP rules. Specifically:
The objective is not DCP. Its following subexpressions are not:
QuadForm(var1, [[ 1.11049417e-01 -1.11049417e-01 -2.11200807e-01 ... -2.11200807e-01
  -5.76205228e-04 -1.11049417e-01]
 [-1.11049417e-01  1.00000000e+00 -6.09256990e-01 ... -6.09256990e-01
   1.66803418e-16  1.00000000e+00]
 [-2.11200807e-01 -6.09256990e-01  2.44141970e+00 ...  2.44141970e+00
   6.62623993e-17 -6.09256990e-01]
 ...
 [-2.11200807e-01 -6.09256990e-01  2.44141970e+00 ...  2.44141970e+00
   9.38166736e-17 -6.09256990e-01]
 [-5.76205228e-04  1.66803418e-16  6.62623993e-17 ...  9.38166736e-17
   1.55858030e+00  2.83219693e-16]
 [-1.11049417e-01  1.00000000e+00 -6.09256990e-01 ... -6.09256990e-01
   2.83219693e-16  1.00000000e+00]])

I am very confused because I am not a mathematician. I check the eigen values of the matrix of the quad form, and it is positive semi definite.
Thank you in advance.
Version

OS: Windows 10
CVXPY Version: 1.1.15

On 1.0.21, is_dcp returns True:
In [1]: from scipy.io import loadmat
In [2]: Gamma = loadmat('./gamma.mat')['Gamma']
In [3]: import cvxpy as cp
In [4]: rho = cp.Variable(101)
In [5]: cp.quad_form(rho, Gamma)
Out[5]: Expression(CONVEX, NONNEGATIVE, (1, 1))
In [6]: cp.quad_form(rho, Gamma).is_dcp()
Out[6]: True
But on 1.1.15, it returns False:
In [6]: cp.quad_form(rho, Gamma).is_dcp()
Out[6]: False
gamma.csv
I uploaded the matrix (mat file is not allowed, so I uploaded a csv file. )

I think I found a temporary solution. Just change the EIGVAL_TOL, and everything goes fine.
`
import cvxpy as cp
try:
tol_backup = cp.expressions.constants.constant.EIGVAL_TOL
cp.expressions.constants.constant.EIGVAL_TOL = 1e-6
from scipy.io import loadmat
Gamma = loadmat('c:/lab/gamma.mat')['Gamma']
result = cp.Constant(Gamma).is_psd()
print(result)
rho = cp.Variable(101)
result = cp.quad_form(rho, Gamma).is_dcp()
print(result)
finally:
cp.expressions.constants.constant.EIGVAL_TOL = tol_backup
`

@rileyjmurray could you take a look?

I can confirm the issue. The matrix Gamma is singular, and numerically has negative eigenvalues on the order of -1e-14. Changing EIGVAL_TOL is one way forward here. Another way is to add a small diagonal to Gamma. I added 1e-11 to the diagonal and then result.is_psd() was True.
Unfortunately, I can't look into this in any more detail. I've tried to work on this twice. The fact that this issue persists means that we're looking at some combination of (1) me making mistakes repeatedly, and (2) this problem is actually hard, given only the functions available to us in SciPy. In either case, I don't think I'm the right person to dig deeper.
I'll note that with the csv format, I loaded the matrix into python by
Gamma = np.genfromtxt('gamma.csv', delimiter=',')

Thank you for your reply. I think you suggestion (add a small number to diagonal) is better than modifing EIGVAL_TOL because EIGVAL_TOL is a global setting, and I have to warn my customers not to run the solver in multiple threads if my code changes EIGVAL_TOL temporarily.
Also, may I suggest that for singular matrices, use numpy.linalg.matrix_rank to filter out the eigen values which are close to zero.
In [17]: from numpy.linalg import eig, matrix_rank

In [18]: matrix_rank(Gamma)
Out[18]: 20

In [19]: d, V = eig(Gamma)

In [20]: d[:20]
Out[20]:
array([4.39748082e+01+0.j, 1.87319619e+01+0.j, 1.48068937e+01+0.j,
       1.35283339e+01+0.j, 1.15903829e+01+0.j, 1.13461068e+01+0.j,
       1.69838285e-02+0.j, 1.66473510e+00+0.j, 1.63741938e+00+0.j,
       9.88105826e+00+0.j, 9.71076713e+00+0.j, 7.65039047e+00+0.j,
       8.19658921e+00+0.j, 8.10100965e+00+0.j, 3.29718782e+00+0.j,
       3.25365328e+00+0.j, 6.48367024e+00+0.j, 6.55500046e+00+0.j,
       4.92659954e+00+0.j, 4.86854712e+00+0.j])

Following the suggestion, I add a small number to the diagonal of Gamma, and I designed an equation to determine the value of the small number adaptively:
δ = 10**(2/3*log10(-min_ev))
I test it in several typical cases, and it runs smoothly. I hope that  it will solve all the problems and satisfy my bad tempered customers.
The complete code for generating Gamma using this equation:
(defn matG [M angles magnitude]
    (setv N (len angles) )
    (setv A (matA M angles) )
    (setv P (matP M) )
    (setv G (
        ∑ #_< [a m] ∈ (zip A.T magnitude) #_> (do
            (▦→┇ a)
            (setv t (->> a
                (.conj)
                (kron a)
                (@ P.T)
                (-) ) )
            (setv g #┇[m t])
            (. (outer g g) real) ) ) )
    (/= G N)
    (setv min-ev (-> G (eigvals) (real) (min)))
    (when (< min-ev 0.0)
        (setv
            -min-ev (- min-ev)
            _2/3    (/ 2 3))
        (setv δ (** 10 (* _2/3 (log10 -min-ev))))
        (setv M²+1 (inc (** M 2)))
        (+= G (* δ (eye M²+1))))
    G)

I have several ideas:

Provide an option to bypass the DCP test (because in many cases the user can guarantee that their problem is convex);
Design a different criterion for singular matrices (using matrix_rank to filter out eigvals close to zero);
Provide a method to change EIGVAL_TOL locally without changing the global settings.
I don't know whether they are feasible, but I think these ideas may make cvxpy more friendly, because singular matrices are very common in engineering problems.

@xialulee we don't want to use matrix_rank because that computes the SVD of a matrix. Algorithms for computing SVD produce dense matrices, while the eigenvalue checks we perform use an iterative method that's suitable for sparse matrices. I don't understand the code you provided in your second comment. What language is that? Could you maybe write out the algorithm you're using in pseudo-code?
For your three ideas:

I don't think we can do that easily. However, I do think it would be nice if we had that functionality.
From my comment above -- rank determination is hard because we need the method to work efficiently for sparse matrices.
This could probably be done relatively easily. Python's "with" construction is used for similar purposes in other settings.

Finally, just to explain why modifying the diagonal can produce better results than changing EIGVAL_TOL: the iterative algorithm we use doesn't compute the smallest eigenvalue directly. It computes the eigenvalue(s) of a shifted (and I think also inverted) version of the matrix. Then we perform a check on the smallest eigenvalue which fails if and only if the original matrix had an eigenvalue that falls outside of our tolerance. However, if the iterative method does not accurately compute the relevant eigenvalue of the shifted (and inverted) matrix, then inaccuracies there can (effectively) get magnified when we run our eigenvalue check. These subtleties are explained in comments of the relevant cvxpy source code.

My code is written in Hy, a lisp dialect running on Python runtime. The Python version of my code looks like:
# Calculating G based on some theory I already forgot.
# G cannot pass the psd test
# because it has very small negative eigvals.
# Newly added code to solve the problem:
min_ev = min(eigvals(G))
if min_ev < 0.0:
    # determine the small value:
    delta = 10 ** (2/3 * log10(-min_ev))
    # add the small value to the diagonal of G
    G += delta * eye(delta.shape[0])
return G

I tested it on several realistic scenarios, ALL SUCCESS.
Thank you sir. You saved my weekend. May I close the issue?

I see. If that solution works for you (and it should be fine for n-by-n matrices with n < 500), then that's great. I'll take care of closing the issue. Before I do that, I want to create a new issue that describes the need for a more robust Constant.is_psd(). (Keeping this issue open will help make sure I don't forget to create a new one.)


bundler 1.14.6 -> 1.16.1

Motivation for this change
I was trying to use vagrant plugin install vagrant-aws which was failing with:
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies bundler (= 1.14.6) and bundler (= 1.16.1)
  Activated bundler-1.16.1
  which does not match conflicting dependency (= 1.14.6)

  Conflicting dependency chains:
    bundler (= 1.16.1), 1.16.1 activated

  versus:
    bundler (= 1.14.6)

  Gems matching bundler (= 1.14.6):
    bundler-1.14.6

Things done
I used bundix to create a new gemset.nix and then updated the version of bundler to match what I think ruby expects:
$ git clone git@github.com:hashicorp/vagrant.git
$ cd vagrant
$ bundix -l
$ cp gemset.nix /path/to/nixpkgs/pkgs/development/tools/vagrant

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

duplicate of #30881 , see comments there

Thanks @xeji

For all the pure souls who have to use vagrant, the following workaround for vagrant: #36880 is a short term solution.

I think we can upgrade bundler now, since gitlab was fixed: https://github.com/NixOS/nixpkgs/commit/94f5e5ad14e99700e82576167515ba784dbfe98b

part of https://github.com/NixOS/nixpkgs/pull/39597


TOMEE-2206 - Support for Enum injection in Microprofile JWT

Hi Ivan.
I have reviewed and commit this PR to master.
Thanks for the contribution.


Anyway to support ApplicationRunner or CommandLineRunner?

As title
I have an ApplicationRunner to call some http request, but seems sleuth doesn't generate trace id for me.
Now it's too hard to debug those http request log, because they are all have different trace id in those api service log.

Duplicate of https://github.com/spring-cloud/spring-cloud-sleuth/issues/1903


Node Dashboard

Title of your project
Taiko Node Dashboard
Short (1-2 sentence) description of your project
a user friendly, easy to read, and visually pleasing dashboard for those running a Node/Proposer/Prover
Link to your project
https://github.com/wolfderechter/taiko-node-dashboard-docker/tree/main
Upload a quality logo to your project

Led by Wolfez + Helios

I like the description The Taiko node dashboard is aimed to provide quick and digestible insights into your Taiko node.


tate stremmm

walk through the files
oh no use flag package and NOT os.args
use mime type package instead of playing weird games with ext names
use fyne and FORGET GTK
@npmaile thx nate

no problem, buddy!


Unmarshall array of object in attribute

Hi there.
Thank you for the lib. I want to ask about unmarshaling. We have some atribute that have array of complex object.
For the examples
{
  "id" :10,
  "type" : "myobject",
  "attributes" : {
    "name" : "my name",
    "fields" : [ {"key1" : "value1"}]
 }
}

As far as I know, jsonapi doesn't support to Unmarshall it. But able to Mashall into the json.
It is intended that way, or it was wrong to have array of complex object in atribute.

Sorry I'm not using master.. I pull the master and it is support slice of struct.


GEODE-5212: run windows jobs in serial

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

As we have only dedicated workers and build are non-containerized, so for now run them in serial.


PSMDB-373-update-docs-hashicorp-vault-support updated text and variants

Updated text based on Igor's comments.

Added a commit that clarifies the support for V2 API versioning must be enabled.

Added rotation steps.


Disable username change from profile page in preparation for quota management

This PR is to disable username change from user profile page in preparation for quota management implementation. This decision was made during developer coordination meeting. A username validation rule is also added in user signup page to ensure "+" is not allowed as a valid character in username since "+" is treated as a valid character in username in Django but treated as an invalid username in iRODS and we need to keep username validation rule between Django and iRODS in sync so that each username created in Django can create a corresponding username in iRODS user zone. @pkdash Can you code review this PR?

@pkdash It'd be great if you could give a quick review on this small PR when you get a chance since it'd be better to get it in and deployed sooner rather than later so that users cannot change their username. As it stands now, if a user has created a corresponding iRODS user account, then change their username, iRODS username in user zone will be out of sync with username in Django, which would requires admin operations to get them in sync again. Although this scenario is not too likely to happen, it'd be great to close this possibility to prevent unexpected out-of-sync scenarios from happening.

@dtarb As part of work for locking out username from modification on user profile page, I added the user's username in the profile view mode as shown below:

Specifically, added (username: xxx) between User and since in About section. This way, the user is able to see his or her username. In the screen capture, I have created an associated iRODS account. If the user hasn't done so, the message will show You have not created an associated iRODS account in HydroShare user zone in which case username was not shown anywhere on profile page, so I think it is good to show username somewhere on profile page to inform the user. Let me know if you think where I added username info looks good or not. If not, let me know what you think the preferred way is.
@pkdash I have addressed your review comment and it is ready for your next round of code review.

@hyi +1 from me. You may to wait for feedback from @dtarb.

@dtarb Since @mjstealey is planning for the next release 1.9.5 and has deployed latest develop to beta for pre-RC testing, I hope this PR can make into the next release since the earlier we can get this in, the less we will run into the potential username out-of-sync issue. The feedback I need from you on whether you approve the username addition I added in view mode on profile page is minor, so I am planning to merge this PR by COB today if I don't receive your feedback by then. If you don't approve what I did on the minor username addition in view mode on profile page, I can amend it quickly based on your feedback later.

Sorry I did not get to respond to this earlier.  These changes look good.


Change storage location for volatile files

Fix issue #247.
Since we are going to break backwards compatibility anyway, this PR also changes the location of storage from ~/.local/doom and ~/.cache/doom to ~/.local/doom/etc and ~/.local/doom/cache. This also gives an opportunity to simplify the patches.

Patching seems to be broken for me.
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/yhq1i8praiivm3bw2my24gw7b292nniw-doom-src
source root is doom-src
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
applying patch /nix/store/52q35pvjmfx811z6cjg2vq96zmawj5cc-nix-integration.patch
patching file early-init.el
patching file lisp/doom.el
Hunk #1 FAILED at 229.
Hunk #2 succeeded at 229 (offset -12 lines).
1 out of 2 hunks FAILED -- saving rejects to file lisp/doom.el.rej

Patching seems to be broken for me.
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/yhq1i8praiivm3bw2my24gw7b292nniw-doom-src
source root is doom-src
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
applying patch /nix/store/52q35pvjmfx811z6cjg2vq96zmawj5cc-nix-integration.patch
patching file early-init.el
patching file lisp/doom.el
Hunk #1 FAILED at 229.

Hang on, I think I forgot to update dependent inputs. I'll try to rebuild my config again.

Yep, patch phase succeeded. It's going to take a while to build and recompile everything, though.

Huh. This is actually the second backwards-compat-breaking change[^1] as the first one snuck in somewhat recently and my local testing overriding nix-doom-emacs with my local checkout didn't catch it since I made my projectile project list mostly declarative.
Anyway, now that we're intentionally breaking it again, we could actually implement the relevant XDG spec[^2]:

By default use the current doom-cache-dir "~/.cache/doom" value and a new doom-etc-dir "~/.local/share/doom".
Bonus for migration, could have a little shell script in the Emacs wrapper that tries to deal with all the doom-etc-dirs we've had so far. It wouldn't be perfect, but better than waiting for emoji image rendering or whatever else.

[^1]: I have both ~/.local/doom/* and ~/.local/* files on my machine, but the ~/.local/* ones are newer. A bit ashamed I didn't catch the pollution. Future: Ask upstream to make the constants overridable with envvars.
[^2]: What we definitely shouldn't do is continue to use the unstandardized ~/.local directory instead of one of it's defined subdirectories.

This is way more than I want to do to fix this issue. I can definitively move everything to ~/.local/share/doom instead, that looks ok-ish for me. But everything else seems to be too much.
For the affect folks that care about maintaining their state, I think they can just move this manually. I can probably document this somewhere if this is something you want.

That's very fair. I guess that can stay on my wishlist for whenever I suddenly feel like working on this again.

Set doom-cache-dir as per my HEAD~3 comment, squashed.

@ckiee Updated the flake and rebased again.
Now the patches after upstream are really small, so this should help maintaining it for the long run.

@ckiee Going to merge this one. Any issues?

No issues, and usually I'd complain about the rush but it does make sense here :P


⚠ Samsung has degraded performance

In b224562, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1747 ms

Resolved: Samsung performance has improved in f7e493d.


Default topics not showing up when creating a post

When creating a post in the Building Hylo group, I noticed that the default topics were not showing up when in the topics section. I double checked the group topics settings, and there were default topics set.

Dang, good catch

On Mar 3, 2022, at 1:54 PM, KrishaTerranIO @.***> wrote:
When creating a post in the Building Hylo group, I noticed that the default topics were not showing up when in the topics section. I double checked the group topics settings, and there were default topics set.
https://user-images.githubusercontent.com/92816219/156659075-fa4cf3dd-8abd-4da7-8642-3df2938eae55.png
—
Reply to this email directly, view it on GitHub https://github.com/Hylozoic/hylo-evo/issues/1133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA5HOMOZ7KETVD4B4UCXTU6EYLHANCNFSM5P3W64JA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.


Unify implementations on computing size from shape

jenkins, test this please.

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

Good catch! A lot of same idioms occur at https://github.com/chainer/chainer/blob/master/chainermn/communicators/mpi_communicator_base.py , can you also apply this changes to them?

@kuenishi Yes, I will.

OK, I will merge this PR.

LGTM!


es:your-first-pwapp

What's changed, or what was fixed?

es/fundamentals/codelabs/your-first-pwapp/index.md

CC: @petele

Thanks @JMPerez! I made all changes and something else I found.

Thanks @nucliweb. I applied all changes.
@petele I guess it's ready to merge

:tada: This has been pushed live to https://developers.google.com/web/


sveltekit build step appears to error out on windows

Description
We had a report from a windows user that npm run build does not seem to work for him.
Assigning this to Brendan Colloran  since he has a windows machine.
Couldn't pass beyond "npm run build" · Issue #168 · rilldata/rill-developer

Brendan Colloran
April 25, 2022, 9:37 PM
Had a quick call with Hamadri just now, verified that it should be fine to work on the open source code and be logged into web service accounts owned by Rill from my own hardware. Thanks Himadri Singh ! :slight_smile:
I can verify that the Docker container works on Windows+Linux if that’s the direction we’re heading.
Edit
Delete
:thumbsup:
1
Himadri Singh
April 25, 2022, 9:15 PM
btw, docker should resolve all these multi-os/multi-env issues.
Use docker compose to setup by himadrisingh · Pull Request #166 · rilldata/rill-developer
Edit
Delete
Himadri Singh
April 25, 2022, 9:14 PM
We should be good with any OS policy we stick too. We don’t have any specific policy for this case.
Edit
Delete
Marissa Gorlick
April 25, 2022, 9:12 PM
Himadri Singh , could you provide takes here?
Edit
Delete
Marissa Gorlick
April 25, 2022, 9:12 PM
This project is open source, so we should be able to pull down the repo and examine this bug on any machine.  Concerns around related Rill apps.  Can he be logged into other services on his personal machine?
Edit
Delete

Finally had time to look into this -- building on Windows currently doesn't work because of the bash scripts (and Perl scripts within one of our bash) that we have as build dependencies. This affects both npm install within a cloned repo, but also the new npm install -g @rilldata/rill installation option.
I think the options are:
a) just decide that we don't want to prioritize windows
b) tell windows users they need to install Windows Subsystem for Linux, and the other deps they'll need (this would be an unrealistically bad option I think -- IMO this is a very very high bar, much worse than docker)
c) replace all of the bash scripts with plain node scripts, which hides the cross platform stuff behind a layer of abstraction.
I think option (c) is our best bet. It looks like none of these bash scripts are so involved that replacing them should take too much work.
@hamilton @AdityaHegde  any thoughts?


Ask an Expert and Submit Feedback not working

Post submission of Ask an Expert and Submit Feedback card, the bot is not able to communicate it in the teams channel.
In application insights I am getting the following message:
Error processing message: Operation returned an invalid status code 'Forbidden'
We have also checked a similar issue on stack overflow but it involves a different resource i.e. Key Vault
azure-c-sharp-keyvaulterrorexception-operation-returned-an-invalid-status-code
Enclosure: Call stack message in Application insight
call stack.txt

Hi, I have this same issue. Can we get a resolution on this?

@gsv022, kindly assist with this issue.


Inconsistency in meal price outlier classifier

What is the problem?
In some publications made by Rosie's Twitter, it is noted that the value identified as suspect is within the standard deviation established by the classifier.
As can be verified in the following suspicion:
Suspicions Tweet
Jarbas Documebt
In this case the value is only 34.50 BRL.
How can this be addressed?
I think it is necessary to adjust the classifier rules or improve the training set.

Arguably this example does not shows what you claim it does.
1. Average value for this venue is R$ 13
Using Jarbas's shell_plus we can see they are low in term of total value/price, in average each claim if for R$ 13.22:
In [1]: import statistics

In [2]: values = tuple(r.total_net_value for r in Reimbursement.objects.filter(cnpj_cpf='05467695000130'))

In [3]: sum(values) / len(values)
Out[3]: Decimal('13.22262773722627737226277372')

2. Standard deviation is R$ 6
Also, the standard deviation is around R$ 6.66 (hey devil 😈):
In [4]: statistics.stdev(values)
Out[4]: Decimal('6.655636628195527505758211117')

This R$ 34 happens to be above the threshold
Thus the threshold is R$ R$ 33.19, below the example value of R$ 34,05:
In [5]: (sum(values) / len(values)) + (3 * statistics.stdev(values))
Out[5]: Decimal('33.18953762181285988953740707')

Also we can check the (arguably) low values in Jarbas: https://jarbas.serenata.ai/dashboard/chamber_of_deputies/reimbursement/?q=05467695000130

What I mean is… Rosie has a good accuracy, but 100% is impossible. This example seams more a false-positive than a bug. Sure we can learn with this example and improve the classifier, let's say, to ask it to only consider venues with averages greater than a certain minimum limit ; )


Allow specified UDP cmsg to be saved to QuicReceivedPacket

Commit Message: Allow specified UDP cmsg to be saved to QuicReceivedPacket
Additional Description: This can be accessed via QuicListenerFilter::onFirstPacketReceived.
Risk Level: Low
Testing: Integration test
Docs Changes: N/A
Release Notes: added

/assign @RyanTheOptimist

/assign @danzh2010

/wait

High-level API observation and question: The CMSG seems to be a very low-level detail of an OS-networking capability. If I understand correctly, the idea is to attach the CMSG data into the quic::QuicReceivedPacket data-structure. I'm not sure if adding that ability is core to the QUIC based listener.

This can be used for any UDP listener which share the same socket read code.

Would it make more sense to have the CMSG as an extension (similar to other fields, such as connection_id_generator_config), and then one of the implementations could be the CMSG one? This way there's no coupling on the need CMSG in order to use QUIC.

Unless the whole packet reading logic in IoHandle and listener callback is moved into an extension, I don't see how to define a clean extension API.

/wait

/retest

/retest

/retest


Error font in Vietnamese

VSCode Version: Code 1.17.1 (1e9d36539b0ae51ac09b9d4673ebea4e447e5353, 2017-10-10T14:24:50.851Z)
OS Version: Windows_NT x64 10.0.15063

Steps to Reproduce:

Open a terminal.
Input "Chào buổi sáng Chủ Nhật".
See characters: "ổ", "ủ", "ậ".

Reproduces without extensions: Yes

@torn4dom4n isn't it just the "ổ" that's wrong? The "ủ" and "ậ" look fine to me?

@Tyriar You can zoom in the picture to see. It isn't good.

Duplicate https://github.com/Microsoft/vscode/issues/35901


run clear trackers on render world

Objective

Fixes https://github.com/bevyengine/bevy/issues/6417

Solution

clear_trackers was not being called on the render world. This causes the removed components vecs to continuously grow. This PR adds clear trackers to the end of RenderStage::Cleanup

Migration Guide
The call to clear_trackers in App has been moved from the schedule to App::update for the main world and calls to clear_trackers have been added for sub_apps in the same function. This was due to needing stronger guarantees. If clear_trackers isn't called on a world it can lead to memory leaks in RemovedComponents.

We should probably add some docs to sub apps that they need to add clear_trackers to the sub app too or just call it manually somewhere, but not sure there's a good place for that.

would it be better to call it here: https://github.com/bevyengine/bevy/blob/530be10e72aa2b8191fe680e9ffef5c4576ce961/crates/bevy_app/src/app.rs#L154
and add
            sub_app.app.world.clear_trackers();

That works. Last night I was a little worried what that would mean for pipelined rendering, but I can put it in the sub app run function.
https://github.com/hymm/bevy/blob/d0ea7adf36a15e9adcc78485bb595ebf188c8a16/crates/bevy_app/src/app.rs#L97-L99

Moved the call to clear_trackers.
It does bring up the question of whether I should move the call for the main world into App::update too for consistency

bors r+


Hydra for Dynamo should be Core 2.0 compliant

The Hydra node for Dynamo needs to:

Achieve parity with the Grasshopper component
Achieve greater stability than previous implementations
Capture background preview (finally possible in 2.0 without custom logic)

Early prototype:

@mostaphaRoudsari I am curious what you think about this type of approach?

Hi @alfarok, it looks legit. 💯
Now that you're going this far how hard is it to add it as a menu item? Does Dynamo give access to modify the menu items? It now looks like some of the functionalities of MetaHopper plugin for Grasshopper.

@mostaphaRoudsari Yes we could do something similar using a view extension.  Check out this project, it’s a view extension that instantiates a CEF browser executing three.js.

@mostaphaRoudsari I agree that the experience of using Hydra in a pop-out window could be more powerful and beneficial long term.  Ultimately it would be cool to push/pull directly from Dynamo/Grasshopper without having to use another Git client.  We could even enable internet access in CEF allowing users to browse the Hydra repo from within Dynamo.  This seems like a slightly larger project so I would prefer to initially use a node that establishes parity with the Grasshopper component.  I can avoid the issue of multiple nodes by iterating the current workspace and verifying another Hydra node is not present when the constructor is called.  We should talk more about the extension though because I think it is a great next step.

Addressed in https://github.com/HydraShare/hydra-dynamo/pull/16


Add P2 + B3 element

The bubble enriched Lagrange page has P1 + B3 and P2 + B4, but not P2 + B3

Hi, thanks for the great website and opening this issue. In the meanwhile before this gets updated, do you know where I can find a derivation of the P2+B3 basis functions?


remove TOPPAS

https://greengypsy-staging-openms.readthedocs.io/en/final-touches/docs/tutorials-and-quickstart-guides/guides/user-quickstart-guide.html

[ ] see also only links to utils documentation
[ ] it still refers to TOPPAS. Should we just remove all the TOPPAS things?

Read Existing Documentation
I have checked the following places for the error:

[ ] OpenMS Documentation Troubleshooting
[ ] OpenMS API Developer FAQs

Create OpenMS Bug Report
I have created the bug report in OpenMS for any pipeline errors.

[ ] OpenMS Open Issues

Description of the documentation bug

[ ] I have attached screenshots of the incorrect documentation

Expected behaviour

OpenMS Installation

Version:

Additional context

Yes all TOPPAS references should be removed, except for the message that says that it is deprecated.


tour: [REPLACE WITH SHORT DESCRIPTION]

Context: https://go.dev/tour/list
Change the title above to describe your issue and add your feedback here, including code if necessary

mendoki/holidaY/suha
metin

Please don't open meaningless issues and PRs, thanks.


Questions about the  droplet data of lung and Trachea in figshare

Hello, I downloaded droplet data from figshare. The data of most tissues looks fine, but  two of lung files (/Lung-10X_P8_12,  /Lung-10X_P8_13) and the Trachea tissue (./Trachea-10X_P8_14,        ./Trachea-10X_P8_15) has some problems. They included all the cells instead of filtered cells, so they all have 737280 cells there.
Thanks!
Qi

@liuqivandy did you try using the data here: https://github.com/czbiohub/tabula-muris-vignettes/tree/master/data