🚀 feat: shuffle quotes array on page load

This PR adds a new feature that randomizes the order of quotes every time the page is loaded, making the experience more dynamic and engaging. 🎉
🔍 What was done:

Feature: Shuffling the quotes array on page load using the magic of:const shuffledQuotes = data.quotes.sort(() => Math.random() - 0.5);

Result: Now, every time you refresh the page, you’ll get a fresh new sequence of quotes! 🔄 No more repetitive order, making the experience feel more lively and less predictable.

🛠 Changes:

Introduced a shuffle function using sort() + Math.random() to reorder the quotes dynamically.
Updated DOM rendering logic to use the shuffled quotes array, keeping the same clean and structured layout.
No breaking changes—just a small enhancement for a more delightful user experience. 😎

🧪 Test Plan:
To verify this feature works as intended:

Open the page in a browser.
Verify that the quotes appear in a random order.
Refresh the page. Quotes should shuffle every time the page reloads. ♻
Repeat step 3 a few more times to ensure randomness works consistently. 🔄

✅ Checklist:

[x] Code properly linted and formatted.
[x] Tested manually to ensure randomness and no errors.
[x] Verified that the feature works across multiple page reloads.

Let me know if you need any further adjustments, and happy reviewing! 😃

that was cool. Thanks🫡

Thx 🫶🏻


Automatically change min/max bounds on axis when switching from linear to log scale

Extracted from #109
@3dvkr you're right on with making a threshold -- hypothetically if there's one value at 1E-12 and the rest between 1E-4 and 1E-2, we don't want the map to have the majority of the data squashed to one side and one lone point sitting on its own. Ideally it should be a tunable threshold, what do you think @Luthaf ?
Originally posted by @rosecers in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-788922864

There is already a min/max setting for the axis range, which should deal with this. Or are you referring to something different?

Originally posted by @Luthaf in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-788931488

No, I'm talking with respect to this. When going to log scale, the minimum should automatically change to some epsilon > 0. Agreed?
Originally posted by @rosecers in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-788933414

I think this is a separate issue from this one 😄. My feeling here is that we should not mess with these value automatically in case the user already set them to something meaningful. If the min is negative, we will get a warning once this improvement is implemented (actually, we don't have to check all values for the warning, only the min). If the min is positive but the data distribution is strange, I'd rather leave it to the user to adapt visualization as they want.
Originally posted by @Luthaf in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-788935607

Two notes:

we may also want to check the max (imagine the case where all values are
negative, what's the expected behavior?
if there are negative values we should de facto enforce as a minimum the
smallest positive value.

Originally posted by @ceriottm in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-789025930

we may also want to check the max (imagine the case where all values are negative, what's the expected behavior?)

If everything is negative, nothing will be displayed. If the user want to display negative values in log scale, they can create a dataset with - property as a new property.
The alternative I think you have in mind (correct me if I'm wrong) is to automatically take the negative; and then do a log scale. While convenient, I think this will be confusing (what should the ticks display?) and open the door to more transformations (log(x + 1), 1/x, etc.). I would love to have such data transformation available as a generic feature, but I don't think it is worth doing as a special case for displaying negative values in a log graph.

if there are negative values we should de facto enforce as a minimum the smallest positive value.

This is already the case since negative values will map to NaN, which plotly will remove before adjusting the axes.
BTW, the code we use to get the min/max in the GUI values is broken, I'll open another issue =)

If the min is negative, we will get a warning once this improvement is implemented

So the steps are for the time being to issue a warning if the min is negative and the scale mode is log? Would this also happen in options.ts? And after this warning is in place, we'd want to automatically change the min/max bounds?

So the steps are for the time being to issue a warning if the min is negative and the scale mode is log? Would this also happen in options.ts?

Yes, that's the idea! These changes should not happen in options.ts but in map.ts, I'v written some instructions in https://github.com/cosmo-epfl/chemiscope/issues/109#issuecomment-788889334.

And after this warning is in place, we'd want to automatically change the min/max bounds?

I'm not sure this is something we want to do in practice, this issue is here to discuss if it is worth it or not!

When going to log scale, the minimum should automatically change to some epsilon > 0.

This is the only actionable thing I could pull out of this discussion, and is already implemented. Feel free to open a new issue if you need something else!


ngx-confetti error type.

Details
ngx-confetti is not working in Angular 15 project using npm.
Error: node_modules/ng-particles/lib/ng-particles.component.d.ts:18:89 - error TS2344: Type '{ options: { alias: "options"; required: false; }; url: { alias: "url"; required: false; }; id: { alias: "id"; required: false; }; particlesInit: { alias: "particlesInit"; required: false; }; }' does not satisfy the constraint '{ [key: string]: string; }'. Property '"options"' is incompatible with index signature. Type '{ alias: "options"; required: false; }' is not assignable to type 'string'. 18 static ɵcmp: i0.ɵɵComponentDeclaration<NgParticlesComponent, "ng-particles", never, { "options": { "alias": "options"; "required": false; }; "url": { "alias": "url"; "required": false; }; "id": { "alias": "id"; "required": false; }; "particlesInit": { "alias": "particlesInit"; "required": false; }; }, { "particlesLoaded": "particlesLoaded"; }, never, never, false, never>;

Please describe a bit what is the problem with some code samples, and please don't trigger sweep on your own.

Sorry about sweep, I didn't know that it was optional.
Theres is an error in node_modules folder in ngx-particles component input declaration.
I did some research and it looks like that the library is incompatible with Angular 15, I tried with 17 and works.
A note on readme with required version would be nice.
Thanks

This is something with angular build, something built with newer angular version is not compatible backwards.

Got it, thanks. It would be nice to have a min compatible version note on readme


changing pricing tiers and data retention

Hello
What happens when I change my pricing tier so for example from 100Gb to prepay but I already have data retention for 12 months on all my tables. Will this affect my data retention in any way or can I change tiers?
Thanks

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3bc62483-6dcf-c373-bc5d-fa11983a5126
Version Independent ID: 68bb5add-0557-0799-6a29-f45220482417
Content: Data retention and archive in Azure Monitor Logs - Azure Monitor
Content Source: articles/azure-monitor/logs/data-retention-archive.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@adiBiran please advise.

@kudu-star - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can review and update accordingly.

@kudu-star Thanks for your inquiry! Pricing tier changes have no effect on data retention.
#please-close

Thanks for confirming @guywi-ms


Can I use clone helper as drag n drop?

Please provide explanation, example and screenshot

See I have a button now as I click it and drag into my dropping area I want a dynamic component to be added at mouse drop position...how can I do this can you give a sample code?or should I give a sample code

You can use the 'onPositionChange' event to get the mouse drop position, and rest is up to you..


Adjust to new redlock behaviour

There have been some changes to the behaviour of redis-client and redlock-rb which lead to a different behaviour in this gem.
Before https://github.com/leandromoreira/redlock-rb/pull/110 was merged, redlock would return false if there was an error with the connection, now it raises the error.
Before this behaviour could have been handled by configuring on_conflict. Now the behaviour should be more fine grained.
This adds a on_error option, which can be either nil (leading to a reraise) or a proc leading to the evaluation of said proc.
This allows users to handle connections errors to reduce the amount of jobs that get lost because of said connection errors.

I've been running this PR in production for some days now.
I added some logging around that callback, but it appears to be silent. So this might not be an issue at all. Even though this PR might still be a feature worth adding.
Most of the errors that we encounter come from delete_lock. So I will try and investigate that if I find the time, maybe there is something we can do about that.
redlock's strategy is to simply fire and forget the unlock attempt, rescuing every error that might occur. But I don't know about that, since redlock is more about process based locking. Trying the same might lead to a deadlock situation.

Think we've also been encountering this issue after doing an upgrade with a job with the unique config of; unique :until_executed, lock_ttl: 10.minutes, on_conflict: :log.
Is the gem going to include these changes in the near future?

I think we are experiencing a similar issue related to the redis-client and redlock-rb changes. @nduitz are you still running this branch?
@sharshenov are we able to merge or get an official fix?

I think we are experiencing a similar issue related to the redis-client and redlock-rb changes. @nduitz are you still running this branch?
@sharshenov are we able to merge or get an official fix?

Hey, yes I am still running the branch.
But as I said before, this PR doesn't change anything on the situation. We still have loads of RedisClient::ConnectionError which are in fact triggered by delete_lock.
Since we never experienced any real issues I suspect this arrises through a raise condition and the lock already being deleted but I did not investigate it further

I apologize for the delay. The change is merged now and it will be released with the next gem version


You can't instantiate/use 2 or more scrollbars in the same page

I want to have more scrollbars in one page, but it can't be done because of the id container which should be unique, I've tried also instantiating two object from two different id's but does not seem to work. Is there a way to add more scroll bar in one page?

It is possible, because you can just provide different id or a separate element itself. Here is an example where 2 scrollbars are initialized.
https://github.com/utatti/perfect-scrollbar/blob/master/examples/options-wheelPropagation.html

Working on scrollbar with x axis but not working on y axis

Sorry, it's working now thank you!


Tuya CS3S/BK7231N

This is also sold as LSC Smart Connect moodlight (Dutch shop Action article 3004154)
Light is powered by a USB adapter. I used the Apple iPad charger for it.

How is the model shown in HA device information page?

How is the model shown in HA device information page?

The device needs to be flashed manually with Tuya convert and then added to HA via a yaml MQTT entry. So there is no default name in HA for it.


Fix Python 3.7 for config_paths

Fixes #667

I'm getting this error on skyplane init and cp:
Traceback (most recent call last):
  File "/Users/sarahwooders/repos/skyplane/env/bin/skyplane", line 5, in <module>
    from skyplane.cli.cli import app
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/skyplane/__init__.py", line 3, in <module>
    from skyplane import compute
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/skyplane/compute/__init__.py", line 9, in <module>
    from skyplane.compute.gcp.gcp_cloud_provider import GCPCloudProvider
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/skyplane/compute/gcp/gcp_cloud_provider.py", line 9, in <module>
    from skyplane.compute.gcp.gcp_network import GCPNetwork
  File "<fstring>", line 1
    (body=)
         ^
SyntaxError: invalid syntax

I can't install Python 3.7 on my Mac as it's ARM. I pushed another change to remove the unsupported fstring syntax. Can you try it one more time? I'm not able to test it locally.
There's a lot of small features that are unsupported on Python 3.7 that I added with the API PR.

(whoops, closed the PR by mistake)

@sarahwooders I think this should fix Python 3.7 issues, but please check if so!

Yep was able to run skyplane init!


Check and update session record if one already exists.

Check and update session record if one already exists, instead of deleting and re-inserting new record.

You should use SELECT ... FOR UPDATE instead of SELECT / UPDATE. Much less code and transactionally-safe. Also, if you use SELECT ... FOR UPDATE, you can use ResultSet.moveToInsertRow to insert a record if necessary.

If you use SELECT FOR UPDATE, then you'll also need to start and commit a transaction, with the overhead that entails.  If the record is modified or even deleted between the time the SELECT query and UPDATE, it's of little to no consequence, and no worse than the current delete/insert method.  The worst result would be slightly stale session data being written, which is kind of an issue anyway if you have an application with that many threads all trying to save data for the same session at basically the same time.


Radius measurement values not automatically populating

Environment:
Windows 10. ArcGIS Pro 2.1 build 10224
Using: Military Tools Single add-in installer. Military Tools for ArcGIS 2.0.
Steps to Repro:

With the add-in installed, open the Distance and Direction pane.
Click on the circle tab.
Make sure the From pull down is set to "Diameter".
Click on the Map Point Tool.
Click on a point
Move the mouse outwards, notice the behavior:

The Radius/Diameter box should update as you move the mouse outward.

Repeat the same steps listed above, this time with the From pull down set to "Radius".
Notice the Radius/Diameter box values are not present.
Current behavior for Radius:

Current behavior for Diameter:

#474 is also related to this issue.

@ACueva Is there more information needed on this issue? This issue should have no dependencies. Issue https://github.com/esri/distance-direction-addin-dotnet/issues/474 was verified and is done.


how to start from another distro?

Start wsl-vpnkit from your other WSL 2 distros. Add the command to your .profile or .bashrc to start wsl-vpnkit when you open your WSL terminal.
wsl.exe -d wsl-vpnkit service wsl-vpnkit start

How do you start wsl-vpnkit from other distros?

You should be able to start it by running wsl.exe -d wsl-vpnkit service wsl-vpnkit start from your normal distro unless Windows interop is disabled.

Thank you! I tried it without the extension and it sure then failed.


test: add no_zk flag for circom benchmarking

Description
This PR adds a no_zk flag for circom benchmarking.
With the no_zk flag, you can create proof without zk. By default zk is enabled. You can use this flag in case you want to compare the proof with rapidsnark.

feat(zk/r1cs): add default constructor for groth16 proof Please change scope zk/r1cs to zk
test: add no_zk flag for circom benchmark Please add scope circom.

Could you please add verify flag, too? I believe there's no need to verify every time!


Dry run HPCA SupermarQ tutorial

@richrines1 Notebook check passes now. Looks like a flake. I'll create an issue for it if it happens again.


one gpu

Hello, I only have one 4090 graphics card. How do I need to change the commands for training, evaluation, and rendering

Hi, simply modify the batch size to make it fit into your GPU memeory, and update the number of training iterations accordingly (i.e., keep (the number of GPUs) x (batch size / GPU) x (training iterations) the same).


Include MATLAB for Winter of Code

Feature:
Include MATLAB
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation:
It is a simple and easy programming language that is currently being used during the online conduction of various labs due to Covid-19.
It might be useful for many of us.

@itskrypton Sorry but I don't think this is necessary as of now. We already have C-Sharp, Kotlin and Q-Sharp section which is far behind as compared to other sections so adding this will cause inconsistency since these languages rarely get contributions.

Okay sure, Thanks!


[RFE] Rancher Helm Chart ingress hardcoded to port 80

Rancher Ingress is hardcoded to port 80. Port should be configurable to use the HTTPS port if desired - TLS termination at the load balancer may not be acceptable in all environments.
Fix is straightforward: Parameterize the ingress port in the helm chart. I am happy to make this change.

This is an enhancement to the Helm chart.
Root cause
(copied from the linked PR)
After installing Rancher using the official helm chart behind a reverse proxy (such as ingress-nginx or some other ingress controller/load balancer solution), kubectl exec and related commands (attach, port-forward) fail when using the Rancher-generated kubeconfig.
This is because the ingress created by the Rancher helm chart defaults to use TLS termination (ingress service port is hardcoded to 80), and the SPDY protocol used in kubectl exec requires TLS.
What was fixed, or what changes have occurred
(copied from the linked PR)
Modify the Helm chart to parameterize the ingress service port. The default value remains the same (80), but now users may specify the HTTPS port (443) if they do not want TLS termination to happen at the load balancer.
Areas or cases that should be tested
Using the helm chart to install rancher, the value of servicePort ( in the value.yaml file) should be applied to the Ingress object which is defined in the chart.
What areas could experience regressions?
the default value (80) should still be applied.
Are the repro steps accurate/minimal?
yes

This is available to test in v2.7.0-rc4

Test Environment:
Rancher version: v2.7-head 9f1e043
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: RKE

Testing:
Tested this issue with the following steps:

Create cluster to deploy rancher on using rke
Install Rancher using helm chart and add the flag --set ingress.servicePort=<number>
Wait for Rancher to be deployed
a. kubectl -n cattle-system rollout status deploy/rancher
Verify that servicePort has been successfully updated to the ingress
a. kubectl get ingress rancher -n cattle-system -o yaml

Result - Pass
servicePort has been successfully updated to the rancher ingress using the helm chart


improvement: requeue clusters with pending Pods

Why are these changes needed?
Right now RayClusters that have pending Pods whose .status.phase
isn't Running are considered reconciled and never requeued again.
This results in RayCluster instances with .status like the following.
Notice the absence of .status.state and .status.head.podIP.
status:
  availableWorkerReplicas: 2
  desiredWorkerReplicas: 1
  head:
    serviceIP: <IP_ADDRESS>
  lastUpdateTime: "2023-01-19T17:46:17Z"
  maxWorkerReplicas: 100
  minWorkerReplicas: 1

This change will add .status.state as pending if the RayCluster's Pods
are not all Running yet and requeue the RayCluster to get updates.
When the cluster's Pods are all Running, the controller will update
.status.state to ready and also update .status.head.podIP.
status:
  availableWorkerReplicas: 2
  desiredWorkerReplicas: 1
  head:
    podIP: <IP_ADDRESS>
    serviceIP: <IP_ADDRESS>
  lastUpdateTime: "2023-01-19T17:46:17Z"
  maxWorkerReplicas: 100
  minWorkerReplicas: 1
  state: ready

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

pending if the RayCluster's Pods are not all Running yet

Not sure if all is necessary, I remember we have some logics to check the cluster's readiness, in order to submit the job. it doesn't have all pods running. This definitely needs some clarification and better definition.  I think the idea is to introduce a new state but this should be used for status update without changing the control loop. (for example, job might not be submitted until resources are ready, then this might to too restricted? )

@Jeffwan, thanks for reviewing. I reverted most of my original changes since #850 addresses them. This PR is now much smaller in scope and just about setting a pending .status.state. Lmk what you think.

I am not sure if this is a good idea.
Pods can come and go in a cluster and there might be unexpected consequences to transitioning back and forth between Pending and Running.
I think the best gauge of whether the cluster is Running or Pending could be the phase of the head pod.
On the other hand, the current behavior of the RayJob controller is to wait for all pods to be ready.

makes sense, thanks for the review. Closing for now


When remote stream arrive

A simple question, how do i know when remote Stream arrives?
Even better when remote stream is attached to the DOM if possible

that's not so simple... and there documented http://simplewebrtc.com/notsosimple.html#basic-overlay and http://simplewebrtc.com/notsosimple.html#connstates

lol so it's not that simple but it's really simple, correct? :D


URL and Base64 encoding

Hey @raynjamin, I'm not exactly a C# expert, so feel free to let me know if anything isn't idiomatic here! :)

@paulstraw Sorry this took so long, took a new job and have been traveling.

No problem at all, thanks for merging!


[FEAT] Add Several Content Classifiers

Description

Implement Snake Case Naming for all categories under score datasets (as per @dlmgary's recommendation)
Add 5 new content classifiers and 1 likert scale classifier
Minor updates to scoring documentation

Tests and Documentation

doc/code/scoring.py updated to have labels for easier output recognition in the .ipynb equivalent

Jupytext ran on scoring.py to create scoring.ipynb

TODO: Add references to these classifiers to gpt_classifier.py


Don't steal the focus

Hi,
The defaults of VS Code are set to enable "Focus Window On Break". I find this a highly disturbing default behaviour because sometimes a program needs some time to reach the section you want to debug. In this case there is a high chance, that the user does something else in the meantime and then be forcefully interrupted by VS Code. Even worse, it might occur, that the user is about to type in sensitive information into a terminal or a web form, which then lands within VS Code.
In fact, I'm writing this feature request, while there is a debugging session going on ;-)
Please, do not steal the focus ever, at least not by default. Thanks :slightly_smiling_face:

I assume you have discovered that the setting "debug.focusWindowOnBreak": false exists?
Changing defaults for settings is rarely done because of the negative impact it has on people who are happy with the existing default.

I assume you have discovered that the setting "debug.focusWindowOnBreak": false exists?
Changing defaults for settings is rarely done because of the negative impact it has on people who are happy with the existing default.

Thanks for the reply. Yes, I was able to fix this issue for my installation.
However, focus steal is arguably very bad behaviour and a security issue. If the focus steal happens in the right moment, I'm gonna type my password into VS Code. Since most users are not aware of this default, it happens at least once before the user notices. It happened to me, and made me upset and angry.
So, knowing that changing the defaults will cause a non-negligible fractions of users complain, I find this a highly annoying and unsafe default. Here I wanted to at least raise awareness, so that the current defaults could perhaps be reevaluated.

Thanks for the reply. Yes, I was able to fix this issue for my installation.
However, focus steal is arguably very bad behaviour and a security issue. If the focus steal happens in the right moment, I'm gonna type my password into VS Code. Since most users are not aware of this default, it happens at least once before the user notices. It happened to me, and made me upset and angry.
So, knowing that changing the defaults will cause a non-negligible fractions of users complain, I find this a highly annoying and unsafe default. Here I wanted to at least raise awareness, so that the current defaults could perhaps be reevaluated.

@grisu48 I'm here looking at various open feature requests to see if I can lend a vote to ones that seem important. So I'm interested to learn more, though I haven't encountered this myself. Can you provide more context, such as a screencast that shows the current behavior?

@grisu48 I'm here looking at various open feature requests to see if I can lend a vote to ones that seem important. So I'm interested to learn more, though I haven't encountered this myself. Can you provide more context, such as a screencast that shows the current behavior?

@grisu48 I'm here looking at various open feature requests to see if I can lend a vote to ones that seem important. So I'm interested to learn more, though I haven't encountered this myself. Can you provide more context, such as a screencast that shows the current behavior? This will help "drive by" people who want to weigh in and up-vote.

Sure, I'll have a look tomorrow and see if I can provide a screencast with an example :+1:

@grisu48 I'm here looking at various open feature requests to see if I can lend a vote to ones that seem important. So I'm interested to learn more, though I haven't encountered this myself. Can you provide more context, such as a screencast that shows the current behavior? This will help "drive by" people who want to weigh in and up-vote.

Sure, I'll have a look tomorrow and see if I can provide a screencast with an example :+1:

I could quickly hack a peek session, hope this illustrates why I mean.
Example 1: Text goes to MS Code while Typing
Focus steal while working on some other things

Example 2: Password leak
Focus steal leads to password being typed into MS Code

I could quickly hack a peek session, hope this illustrates why I mean.
Example 1: Text goes to MS Code while Typing
Focus steal while working on some other things

Example 2: Password leak
Focus steal leads to password being typed into MS Code

@grisu48 Well explained! Thanks.
A follow up: are there any benefits to this being the default behavior? (I'm not saying the benefits outweigh the security risks; I'm just asking.)

@grisu48 Well explained! Thanks.
A follow up: are there any benefits to this being the default behavior? (I'm not saying the benefits outweigh the security risks; I'm just asking.)

@grisu48 thanks a lot for your feedback!
However this is the default behavrio for preivous 5+ years and this is the first complaint.
I understand the problem and you have nicely demonstrated that via your gif.
For now I suggest you change the setting, and I would be open to change the default value of the setting in the future. I will like to keep this issue open so we gather more feedback from users. Thanks

@grisu48 thanks a lot for your feedback!
However this is the default behavrio for preivous 5+ years and this is the first complaint.
I understand the problem and you have nicely demonstrated that via your gif.
For now I suggest you change the setting, and I would be open to change the default value of the setting in the future. I will like to keep this issue open so we gather more feedback from users. Thanks

@grisu48 thanks a lot for your feedback!
However this is the default behavrio for preivous 5+ years and this is the first complaint.
I understand the problem and you have nicely demonstrated that via your gif.
For now I suggest you change the setting, and I would be open to change the default value of the setting in the future. I will like to keep this issue open so we gather more feedback from users. Thanks

thanks for the reply @isidorn. I understand the implications and pain of changing the default behaviour and appreciate your open mind towards this issue.
For all the folks who stumbled across this issue, you can change the behaviour as suggested by @gjsjohnmurray by setting debug.focusWindowOnBreak in the Settings dialog of VS Code to false, as shown below:

Cheers :slightly_smiling_face:

@grisu48 thanks a lot for your feedback!
However this is the default behavrio for preivous 5+ years and this is the first complaint.
I understand the problem and you have nicely demonstrated that via your gif.
For now I suggest you change the setting, and I would be open to change the default value of the setting in the future. I will like to keep this issue open so we gather more feedback from users. Thanks

thanks for the reply @isidorn. I understand the implications and pain of changing the default behaviour and appreciate your open mind towards this issue.
For all the folks who stumbled across this issue, you can change the behaviour as suggested by @gjsjohnmurray by setting debug.focusWindowOnBreak in the Settings dialog of VS Code to false, as shown below:

Cheers :slightly_smiling_face:

Errors in vscode also steal focus. That drove me mad. I was trying to copy / paste something from a browser and VsCode wouldn't let me because it kept stealing focus. Whoever came up with the idea of "let's steal focus" in the first place was being obnoxious.

I've used VSCode for years, and the focus stealing has always been something that bothered me, without me realizing - I only now thought to search for it and found the setting and this issue.
Yes, the onus is on me for not searching for my issue - but the thing was I didn't even realize it was something I should search. It's been one of those minor annoyances that's bothersome but since the rest of the program is so quintessential to your workflow, it slips by.
Personally, I think changing the default would be a good move - I don't think most people would notice the change, and the (probably few) who do would be more likely to search for a solution and find the setting.


feat(prisma): enable prisma as open source

:tada: This PR is included in version 3.18.0 :tada:
The release is available on:

v3.18.0
GitHub release

Your semantic-release bot :package::rocket:


fix: fix broken links and 404 errors

Fixes #105
Summary:

Remove nonexisting broken link: Hack Day from Why Hospitalrun blog post
Set post image link to be post.url instead of nonexistent /single.html
fix blog broken links to match the correct links
do slugify in tag page config to fix broken links

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[$125] Web - Onboarding - Onboarding modal's corner become rectangular when hovering over the back button

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

Version Number: 9.0.30-7
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Navigate to staging.new.expensify.com
Sign up with a new account
When the onboarding modal shows up click on something else
Hover over the back button and observe the corner of the modal

Expected Result:
Nothing unusual happens to the corners of the onboarding modal
Actual Result:
Corners of the onboarding modal become rectangular first until the tooltip shows up and reverts back to being curved
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/73604844-7cf9-44ba-94c9-4c2e16f31b29

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

Upwork Job URL: https://www.upwork.com/jobs/~021832074357963924539
Upwork Job ID:<PHONE_NUMBER>963924539
Last Price Increase: 2024-09-13

We think that this bug might be related to #wave-collect - Release 1

@sakluger  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

This seems like a basic styling issue. I'm going to set the price at $125.

Just tried to reproduce on mac-chrome, but I'm not experiencing this issue.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~010522cfcacf6a249a

This issue is caused by a state re-render. When we hover over the back button, the card initially displays the default CSS, which lacks the border-radius property. Once the original CSS loads, the card becomes rounded as intended.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/sandeeppal

Added the retest-weekly label.

I setup local env for the expensify on windows but it not working can  somebody help me.

Please re-state the problem that we are trying to solve in this issue.

Corners of the onboarding modal become rectangular first until the tooltip shows up and reverts back to being curved.
If user slightly touch the border of the back button, and do not go further, the corners stay rectangular.

What is the root cause of that problem?
The BaseOnboardingPersonalDetails component's styling is not proper.
What changes do you think we should make in order to solve the problem?
I will adjust the styling of the BaseOnboardingPersonalDetails component, which will eventually remove the bug.
What alternative solutions did you explore? (Optional)
Overflow hidden on the component or it's parent.
Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: -------

Contributor details
Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: -------

Please re-state the problem that we are trying to solve in this issue.
The corners of the onboarding modal turn rectangular when the tooltip is about to show up and revert back to being curved after the tooltip appears. If the user slightly touches the border of the back button without fully interacting, the corners remain rectangular.
What is the root cause of that problem?
The BaseOnboardingPersonalDetails component’s styling does not properly maintain the curved corners during specific interactions.
What changes do you think we should make in order to solve the problem?
I will adjust the styling of the BaseOnboardingPersonalDetails component to ensure that the modal's corners remain consistently curved, even when the tooltip is displayed or when interacting with the back button.
What alternative solutions did you explore? (Optional)
I explored using overflow: hidden on the component or its parent to keep the corners in place but found it less effective than directly fixing the component's styling.
Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/makhdoomabubakar

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/makhdoomabubakar

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~017304c8ed7eb17c49

Contributor details:
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~017304c8ed7eb17c49

Proposal
Please re-state the problem that we are trying to solve in this issue.
The corners of the onboarding modal initially appear rectangular until the tooltip displays, at which point they return to their curved state. Additionally, if the user lightly touches the edge of the back button without pressing further, the corners remain rectangular.
What is the root cause of that problem?
The issue seems to stem from improper styling in the BaseOnboardingPersonalDetails component. This inconsistency causes the modal’s border-radius to temporarily reset.
What changes do you think we should make in order to solve the problem?
I will adjust the CSS for the BaseOnboardingPersonalDetails component, ensuring the border-radius remains consistent, even when the tooltip appears or when hovering near the back button.
What alternative solutions did you explore? (Optional)
One alternative approach is applying overflow: hidden either to the component itself or to its parent container to control any visual overflow that may be contributing to the issue.

Still looking for proposals that explain the exact root cause with an appropriate fix suggested.

Hmm, we never got a retest by QA.
@AttockOffice85 @Bakhtiar85  @ra-md were you all able to reproduce this issue after Sept 9?

@ra-md Do you have a reference or an explanation for the cited bug? Is there an existing bug report filed with Chromium?

Issue not replicated in Chrome Version 128.0.6613.139 on macOS. The original poster was using Windows; could this be a Chrome bug specific to Windows? Which Chrome version was utilized by the tester?

@ra-md could you please clarify which operating system and version of the app you were using when you reproduced the issue? And could you please answer @akinwale's question here? Thanks!

I can't reproduce this one in Mac Chrome (Version 128.0.6613.138). Given the low impact on users and the difficulty in reproduction, I'm going to close this one for now so we can focus on higher impact bugs.


Migrating Swagger ASPNET.Core from 4.x to latest

I have been given a project to update and I'm gotten a bit stuck in migrating from 4.x to the latest version.
The first issue is the Going from Operation to OpenApiOperation it no longer has Produces and I cannot find anywhere that has a solution for this and I cannot find documentation for the breaking changes. It seems like you're supposed to use labels instead, but I do not know how to get the same functionality.
    public class ApiVersionOperationFilter : IOperationFilter
    {
        public void Apply(OpenApiOperation operation, OperationFilterContext context)
        {
            var actionApiVersionModel = context.ApiDescription.ActionDescriptor?.GetApiVersion();
            if (actionApiVersionModel == null)
            {
                return;
            }

            if (actionApiVersionModel.DeclaredApiVersions.Any())
            {
                operation.Produces = operation.Produces.SelectMany(p => actionApiVersionModel.DeclaredApiVersions.Select(version => $"{p};v={version}")).ToList();
            }
            else
            {
                operation.Produces = operation.Produces.SelectMany(p => actionApiVersionModel.ImplementedApiVersions.OrderByDescending(v => v).Select(version => $"{p};v={version}")).ToList();
            }
        }
    }

The next is concerning the SwaggerDocument.Security which I cannot find anything about whatsoever on the internet.
public void Apply(OpenApiDocument swaggerDoc, DocumentFilterContext context)
{
    swaggerDoc.Security = new List<IDictionary<string, IEnumerable<string>>>()
    {
        new Dictionary<string, IEnumerable<string>>()
        {
            { "Bearer", Array.Empty<string>() }
        }
    };
}

Anyone know how you're supposed to migrate Security from SwaggerDocument 4.x to the latest OpenApiDocument?

Hello
Did you have any more information about your second post or find a workaround ?
I currently dealing with the same situation.
Best regards

Please open a new issue if you're still trying to do this.


Unable to authenticate when using environment variables

I am having trouble authenticating to mongo docker container.
(I have read all related issues but couldn't manage to make authentication work)
My setup

ubuntu 16.04 server edition (hosting the docker that hosts the mongo container)
windows 10 with mongo client (version 4.0.9)

Setting up container on the server
docker pull mongo:4.0.9
docker run -d -p 27017-27019:27017-27019 --name my-mongo -e MONGO_INITDB_ROOT_USERNAME=milen -e MONGO_INITDB_ROOT_PASSWORD=secret mongo:4.0.9
Connecting via mongo client
(I am completely sure about the server IP address)
mongo --username milen --password secret <IP_ADDRESS>
My output
MongoDB shell version v4.0.9
connecting to: mongodb://<IP_ADDRESS>:27017/test?gssapiServiceName=mongodb
2020-03-17T10:59:39.471+0200 E QUERY    [js] Error: Authentication failed. :
connect@src/mongo/shell/mongo.js:343:13
@(connect):2:6
exception: connect failed
Further observation
When I attempt connecting without providing username and password connection is established.
mongo <IP_ADDRESS>
MongoDB shell version v4.0.9
connecting to: mongodb://<IP_ADDRESS>:27017/test?gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("ab83eb76-c5e4-4422-9139-7a9d909a2308") }
MongoDB server version: 4.0.9
However if I further want to authenticated using the mongo shell I get authentication failed again.
> db.auth("milen", "secret")
Error: Authentication failed.
0

Specify --host <IP_ADDRESS> in your command, I'm not sure why but it causes mongo to use test as the auth db whereas specifying --host correctly uses admin
In your docker logs you'll see something like:
ACCESS   [conn5] SASL SCRAM-SHA-1 authentication failed for milen on test from client <IP_ADDRESS>:60538 ; UserNotFound: Could not find user "milen" for db "test"

Then changing it to --host <IP_ADDRESS> or adding --authenticationDatabase admin
ACCESS   [conn6] Successfully authenticated as principal milen on admin from client <IP_ADDRESS>:60596

Thanks a lot, adding the --host option to <IP_ADDRESS> did the trick.
It seem to be problem of the mongo shell itself. Anyway with the option it works.
For others let to this issue here is the connect command that worked at the end
mongo --user milen --password secret --host <IP_ADDRESS>


ph4 crashes after a large number of stars are added to the system

Describe the bug
*** SEE ADDITIONAL CONTEXT BELOW ***
From Aaron Tran (Columbia):
I'm doing low-resolution runs with Josh's bridge code and AMUSE commit c00140052 (i.e., up-to-date ph4).  These runs crash when they try to spawn ~2000-8000 stars at once.  Star particles are sent to ph4:
grav.particles.add_particles(...)

When I try to get or set particle properties from ph4:
# get
print grav.particles
# set
stars_to_grav.copy_attributes(["vx", "vy", "vz"])

The code aborts; a backtrace and valgrind output are copied below.  The crash happens at:
idata.cc:98     if (old_vel) delete [] old_vel;

To Reproduce
This seems to happen during a Torch run.  Unclear yet if a simple example can be found.
Expected behavior
Stars should be added to the internal ph4 arrays and the computation should proceed normally.  The only unusual thing here is that Aaron is adding thousands of stars at a time.
Logs
Some observations:

The code works OK with Hermite instead of ph4 (tested with same FLASH restart + AMUSE random seed).
Crash is not tied to exact # of stars.  E.g., 5000 stars can spawn at once (with first sink), but ~2000 or 3000 will crash.
Crash is not tied to exact # of sinks.  Most crashes are after creating a second sink; however, there's one case where it crashed with only one sink (spawning ~8000 stars).

Backtrace from core dump:
(gdb) bt
#0  0x00002aaaabce61d7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00002aaaabce78c8 in __GI_abort () at abort.c:90
#2  0x00002aaaabd25f07 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x2aaaabe30b48 "*** Error in `%s': %s: 0x%s ***\n")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:196
#3  0x00002aaaabd2d503 in malloc_printerr (ar_ptr=0x0, ptr=<optimized out>, str=0x2aaaabe2e249 "free(): invalid size", action=3) at malloc.c:5013
#4  _int_free (av=0x0, p=<optimized out>, have_lock=0) at malloc.c:3835
#5  0x000000000041cef8 in idata::cleanup (this=0xacbb80) at idata.cc:98
#6  0x000000000041c6a5 in idata::set_ni (this=0xacbb80, n=8448) at idata.cc:37
#7  0x000000000041cc01 in idata::setup (this=0xacbb80) at idata.cc:70
#8  0x0000000000416547 in recommit_particles () at interface.cc:361
#9  0x000000000040d98d in handle_call () at worker_code.cc:673
#10 0x000000000040fe18 in run_mpi (argc=1, argv=0x7fffffffac88) at worker_code.cc:1349
#11 0x0000000000411a13 in main (argc=1, argv=0x7fffffffac88) at worker_code.cc:1833

Output from running AMUSE with "valgrind --error-limit=no":
before stars_to_grav.copy_attributes([...])
==30292== Conditional jump or move depends on uninitialised value(s)
==30292==    at 0x40C016: handle_call() (worker_code.cc:231)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Conditional jump or move depends on uninitialised value(s)
==30292==    at 0x40C01D: handle_call() (worker_code.cc:231)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Conditional jump or move depends on uninitialised value(s)
==30292==    at 0x40C028: handle_call() (worker_code.cc:231)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Invalid write of size 8
==30292==    at 0x423B2E: jdata::predict_all(double, bool) (jdata.cc:705)
==30292==    by 0x416521: recommit_particles (interface.cc:358)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==  Address 0x12d26260 is 0 bytes after a block of size 196,608 alloc'd
==30292==    at 0x4C28D09: operator new[](unsigned long) (vg_replace_malloc.c:433)
==30292==    by 0x422558: jdata::initialize_arrays() (jdata.cc:390)
==30292==    by 0x416416: commit_particles (interface.cc:323)
==30292==    by 0x40C379: handle_call() (worker_code.cc:247)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Invalid write of size 8
==30292==    at 0x423B85: jdata::predict_all(double, bool) (jdata.cc:706)
==30292==    by 0x416521: recommit_particles (interface.cc:358)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==  Address 0x12a14e30 is 0 bytes after a block of size 196,608 alloc'd
==30292==    at 0x4C28D09: operator new[](unsigned long) (vg_replace_malloc.c:433)
==30292==    by 0x42259B: jdata::initialize_arrays() (jdata.cc:391)
==30292==    by 0x416416: commit_particles (interface.cc:323)
==30292==    by 0x40C379: handle_call() (worker_code.cc:247)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Conditional jump or move depends on uninitialised value(s)
==30292==    at 0x41CBCB: idata::setup() (idata.cc:68)
==30292==    by 0x416546: recommit_particles (interface.cc:361)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Use of uninitialised value of size 8
==30292==    at 0x41CBD8: idata::setup() (idata.cc:69)
==30292==    by 0x416546: recommit_particles (interface.cc:361)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== Invalid read of size 8
==30292==    at 0x41CBD8: idata::setup() (idata.cc:69)
==30292==    by 0x416546: recommit_particles (interface.cc:361)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==  Address 0x400d0d0fe3d2bf4f is not stack'd, malloc'd or (recently) free'd
==30292==
[node220:30292] *** Process received signal ***
[node220:30292] Signal: Segmentation fault (11)
[node220:30292] Signal code:  (128)
[node220:30292] Failing at address: (nil)
[node220:30292] [ 0] /lib64/libpthread.so.0(+0xf370)[0x5c0c370]
[node220:30292] [ 1] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x41cbd8]
[node220:30292] [ 2] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x416547]
[node220:30292] [ 3] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x40d98d]
[node220:30292] [ 4] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x40fe18]
[node220:30292] [ 5] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x411a13]
[node220:30292] [ 6] /lib64/libc.so.6(__libc_start_main+0xf5)[0x5e3ab35]
[node220:30292] [ 7] /rigel/astro/users/at3222/code/amuse/src/amuse/community/ph4/ph4_worker[0x40b779]
[node220:30292] *** End of error message ***
==30292==
==30292== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==30292==    at 0x5C0C23B: raise (pt-raise.c:37)
==30292==    by 0x64FF66B: show_stackframe (in /rigel/opt/openmpi-3.1.1/lib/libopen-pal.so.40.10.1)
==30292==    by 0x5C0C36F: ??? (in /usr/lib64/libpthread-2.17.so)
==30292==    by 0x41CBD7: idata::setup() (idata.cc:69)
==30292==    by 0x416546: recommit_particles (interface.cc:361)
==30292==    by 0x40D98C: handle_call() (worker_code.cc:673)
==30292==    by 0x40FE17: run_mpi(int, char**) (worker_code.cc:1349)
==30292==    by 0x411A12: main (worker_code.cc:1833)
==30292==
==30292== HEAP SUMMARY:
==30292==     in use at exit: 38,237,413 bytes in 28,155 blocks
==30292==   total heap usage: 50,342 allocs, 22,187 frees, 45,459,707 bytes allocated
==30292==
==30292== LEAK SUMMARY:
==30292==    definitely lost: 1,713,283 bytes in 39 blocks
==30292==    indirectly lost: 145 bytes in 4 blocks
==30292==      possibly lost: 1,338,865 bytes in 1,780 blocks
==30292==    still reachable: 35,185,120 bytes in 26,332 blocks
==30292==                       of which reachable via heuristic:
==30292==                         newarray           : 524,296 bytes in 1 blocks
==30292==         suppressed: 0 bytes in 0 blocks
==30292== Rerun with --leak-check=full to see details of leaked memory
==30292==
==30292== Use --track-origins=yes to see where uninitialised values come from
==30292== For lists of detected and suppressed errors, rerun with: -s
==30292== ERROR SUMMARY: 337255613 errors from 634 contexts (suppressed: 0 from 0)
Child job 5 terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.

mpiexec noticed that process rank 0 with PID 30292 on node node220 exited on signal 11 (Segmentation fault).
Environment (please complete the following information):
Unknown.  I will find out.
Additional context
I suspect that the call to add_particles() my be leading to this issue.  I wrote the ph4 code for add_particle()  (no s, note).  It assumes that only one particle at a time is being added.  It does dynamic memory allocation in chunks of size JBUF_INC = 8192.  Because the the number of particles can only increase by 1, it is sufficient to increase the current buffer size njbuf by JBUF_INC only when nj >= njbuf on entry.  My problem is that I didn't write add_particles(), and I can't find the code that implements it.  My memory allocation scheme will fail if too many particles are added at once.  I suspect either Aren or Inti wrote this part of the interface.  Pointers to (and an explanation of) the code would be appreciated.

Hmm, I think I’ve experienced this bug as well.
My workaround is to stop ph4 at every timestep and restart it again when needed, this was practical in my case since it reduced the number processes being used at any one time. But it is a workaround and not a solution...
For some reason adding extra particles seems to cause the crashing. Adding particles at the start of a run works fine for me.

Yes, everything should be OK until you get to 8192 particles (the buffer increment).  The function add_particle() in ph4 checks when you add the next one and will increase the buffer by 8192 if needed, and so on.  It doesn’t check that the new buffer size is sufficient because it only expects one star at a time.  But if you have 8000 stars in the buffer and then somehow dump in another 5000 without checking memory, you will crash the code.  My problem is that I can’t figure out exactly what add_particles() is doing.
Steve
Stephen L. W. McMillan
Department Head and Professor of Physics, Drexel University
+1<PHONE_NUMBER>/2723, FAX +1<PHONE_NUMBER><EMAIL_ADDRESS>
On Oct 9, 2019, at 5:03 PM, Steven Rieder<EMAIL_ADDRESS>wrote:
Hmm, I think I’ve experienced this bug as well.
My workaround is to stop ph4 at every timestep and restart it again when needed, this was practical in my case since it reduced the number processes being used at any one time. But it is a workaround and not a solution...
For some reason adding extra particles seems to cause the crashing. Adding particles at the start of a run works fine for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/amusecode/amuse/issues/510?email_source=notifications&email_token=AAPFB3SRT6OSUQQ3TMMS3FTQNZBL5A5CNFSM4I7EV622YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZL5CQ#issuecomment-540196490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPFB3TDXNFGLQ2MKHTRQW3QNZBL5ANCNFSM4I7EV62Q.

I just heard from Aaron that in all (7) cases that crash, the crash occurs when ph4 is asked to store >8192 stars for the first time, which looks consistent with my hypothesis.
Steve
Stephen L. W. McMillan
Department Head and Professor of Physics, Drexel University
+1<PHONE_NUMBER>/2723, FAX +1<PHONE_NUMBER><EMAIL_ADDRESS>
On Oct 9, 2019, at 5:03 PM, Steven Rieder<EMAIL_ADDRESS>wrote:
Hmm, I think I’ve experienced this bug as well.
My workaround is to stop ph4 at every timestep and restart it again when needed, this was practical in my case since it reduced the number processes being used at any one time. But it is a workaround and not a solution...
For some reason adding extra particles seems to cause the crashing. Adding particles at the start of a run works fine for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/amusecode/amuse/issues/510?email_source=notifications&email_token=AAPFB3SRT6OSUQQ3TMMS3FTQNZBL5A5CNFSM4I7EV622YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZL5CQ#issuecomment-540196490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPFB3TDXNFGLQ2MKHTRQW3QNZBL5ANCNFSM4I7EV62Q.

as far as I can see the code adds 1 particle at a time: new_particle in interface.py has:
function.can_handle_array = True This means that the mpi transfer for adding multiple stars in the same call is done in 1 call, but on the code side each particle is added seperately by a seperate call to new_particle. Each new call happens in sequence w/o anything in between..

OK.  I'll look more closely.  Aaron sent me a small script that he says will cause the problem with ust ph4.  I think I should be able to debug this.  I don't know why I couldn't see previously where add_particle() is called...

OK, the bug is fixed.  I can't say it was subtle -- just a piece of untested code.  I'll commit it to my AMUSE repo and make a pull request.

Thanks Steve!

should be fixed by #512


Can't open your homepage!

@vstm now your mirror is dead as well.

@yegortimoschenko You are right, it was down - sorry. I have fixed the problem and the mirror is up again. Thank you!


Resizing smaller makes content bigger than it is prior to resize

I have a very simple content for which I'm using bootstrap.css.  It is used to have responsive design like resizing for smaller size.  When Resizing to a small size, the code starts to resize the content but just before it starts doing it it makes everything bigger then it was originally.  You can see it here in this GIF image
How do I send a repro by the way because I have zipped the little project to test it.  The only thing I can offer in this Issue tracker when writing this is an image.

This media queries seems to work only in Internet Explorer 11 but seems not working in other browsers

Repro Project VS 2013 : https://onedrive.live.com/redir?resid=B1312569CC884E6!3076&authkey=!AOfXSZ27nnjSK-o&ithint=file%2Czip

We require a JSBin or JSFiddle. We do not open zips, tars, other archives or personal projects for security reasons. Please post a JSBin of an isolated example.

Ah sorry, it's my first time,  I'll do a JSBin once at home.  I'll get the trick  :)

On JSBin it's not acting like the project and yet everything is there the same visual, css and reference to bootstrap
http://jsbin.com/dubomujapo/1/edit?html,css,output
When I resize the image is responsive but not the table but it is in my project and it's the same html content any idea ?

@GearTheWorld sounds to me like you may have some CSS which is causing that. Only thing I can think of if you aren't using the .table-responsive class on the table.

Everything you see in JSbin is what I have nothing else.  Now the question is how it uses media-queries on my MVC app and not on JSbin however it has the same things.  HTML, CSS and REFERENCES
I'm lost...

I suggest asking on StackOverflow at this point. It seems to be a problem specific to your use of Bootstrap, rather than with Bootstrap itself. I'd say though: check you don't have any further JS or CSS in your actual project that may be causing this change in styling.


feature help-block

https://github.com/aldeed/meteor-autoform/issues/868

This would be amazing for the project I'm working on. I should have time to test in the next week. Is there anything holding this up right now?

When will this be merged, it would be nice to have this feature in autoform...

@cesarve77 - Is there a possibility of using this somehow even though it's not yet merged? A local branch maybe?

From my forked git
https://github.com/cesarve77/meteor-autoform

@cesarve77  - Thanks! But I'm afraid I do not know how to do that yet :( Any pointers on how to get it working for me? Right now I've included aldeed:auto-form to my meteor project. Is there a different way to include yours?

Sorry for my english:
Just download my repo and put in on a folder named "packages" in the root
of your project
(or clone the repo, in terminal in root of project $ git clone
https://github.com/cesarve77/meteor-autoform.git)
after in your terminal inside your project $ meteor add aldeed:autoform
And meteor will use the local copy of the package.
good luck
2016-07-17 3:20 GMT-04:00 bharathkeshav12<EMAIL_ADDRESS>
@cesarve77 https://github.com/cesarve77 - Thanks! But I'm afraid I do
not know how to do that yet :( Any pointers on how to get it working for
me? Right now I've included aldeed:auto-form to my meteor project. Is there
a different way to include yours?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aldeed/meteor-autoform/pull/1385#issuecomment-233169147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADyXp5pIvQ7LWjSsbSlNKT8Sxzyu_Iowks5qWdeogaJpZM4Hap7m
.

--
César Ramos
Av. Romúlo Gallegos
Centro Gerencial los Andes.
Ofc 6D. Boleita. Caracas
04141400601
02129352802

@cesarve77
Thanks for your help. Here is what i did.

Create a new meteor project using meteor create labrat (for testing, i'm creating a new project named labrat)
cd labrat
mkdir packages
cd packages
git clone https://github.com/cesarve77/meteor-autoform.git
cd ../
meteor add aldeed:autoform

I got the below error:
bharath@bharath-Dell-System-XPS-L502X:~/labrat$ meteor add aldeed:autoform
=> Errors while adding packages:
While building package aldeed:autoform:
error: File not found: templates/bootstrap3/components/afFormGroup/afIconHelp.html
error: File not found: templates/bootstrap3/components/afFormGroup/afIconHelp.js
error: File not found: templates/bootstrap3/components/afFormGroup/afIconHelp.css
What is wrong?

let me check
2016-07-17 4:04 GMT-04:00 bharathkeshav12<EMAIL_ADDRESS>
@cesarve77 https://github.com/cesarve77
Thanks for your help. Here is what i did.

Create a new meteor project using meteor create labrat (for
testing, i'm creating a new project named labrat)
cd labrat
mkdir packages
cd packages
git clone https://github.com/cesarve77/meteor-autoform.git
cd ../
meteor add aldeed:autoform

I got the below error:
bharath@bharath-Dell-System-XPS-L502X:~/labrat$ meteor add aldeed:autoform
=> Errors while adding packages:
While building package aldeed:autoform:
error: File not found:
templates/bootstrap3/components/afFormGroup/afIconHelp.html
error: File not found:
templates/bootstrap3/components/afFormGroup/afIconHelp.js
error: File not found:
templates/bootstrap3/components/afFormGroup/afIconHelp.css
What is wrong?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aldeed/meteor-autoform/pull/1385#issuecomment-233170518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADyXp3cAp9rxn3Jn0hY93YpIa17uN30Kks5qWeIngaJpZM4Hap7m
.

--
César Ramos
Av. Romúlo Gallegos
Centro Gerencial los Andes.
Ofc 6D. Boleita. Caracas
04141400601
02129352802

@bharathkeshav12
Sorry was my fault.
try again

@cesarve77  - Thanks. I tried it now and it's installed without errors. I'd like to understand -

How do I know that what was installed is your local fork and not aldeed's original package.
If I run meteor update in the future, what will happen? Will it update your source or will it update aldeed's source?

@bharathkeshav12
in this page click on changed files as you see below

Now you always be working with the local repo until you delete the folder.
But don't worry  I really hope @aldeed merge this pull request, when this happen you can delete with confidence
Note @aldeed have 7 month without update this repo, sure he is very busy right now, just have to wait

@cesarve77 - Thanks! I'll use your tooltips and help-block until aldeed does something about it! Your help is much appreciated!

@cesarve77  - How exactly can I get the tooltip icon to pull-right and have the text-help appear under the text input instead of next to the label?
Example Schema:
"name":{
        type: String,
        regEx: /^[a-zA-Z0-9][\w@.-]{0,30}$/,
        autoform:{
            placeholder: "Name required",
            afFormGroup:{
                iconHelp: {
                        title: 'Name Info',
                        content: "

Parameter can contain alphanumeric and following special characters('-', '.' '_' and '@').

Should always start with an alphanumeric character.

It should not be an empty string.

Maximum allowed length is 31 characters.

This parameter is case-insensitive.

",
                        type: 'popover',
                        placement: 'right',
                        trigger:'hover'
                    },
                    textHelp: "Name of this instance",
            },
        }
    },

@bharathkeshav12 Now you have all files locally in your machine just go to /Users/cesar/Documents/www/qless/packages/meteor-autoform/templates/bootstrap3/components/afFormGroup
and modify whatever you want

Great work with this!
I have implemented it but I seem to be having a problem with checkboxes. For some reason the iconHelp is not showing up. I should mention that I am using a custom template for the 'afCheckbox_bootstrap3' template and I am thinking that this might be the reason.
It works for regular text fields but not for boolean type fields.
I have tried including {{#if iconHelp}}{{>afIconHelp iconHelp}}{{/if}} and {{textHelp}} in my 'custom_afCheckbox_bootstrap3' template but neither works.
Am I missing something?
Thanks

Couldn't this get merged?

I've proposed a less invasive to add help text. PR #1650 .


Question about filenames and tags

Hey, I tried looking all over for an answer to this but I really couldn't find anything. I'm sorry if you've answered this before but how do I get the image grabber to properly name files like if I downloaded them from danbooru. For example the image downloaded straight from the site would be named
"kiso and tenryuu (kantai collection) drawn by orqz - 20fe79072a1928a0bd22d02cc8501532"
and through the image grabber it's:
"20fe79072a1928a0bd22d02cc8501532"
I tried a separate danbooru downloader and used %originalFilename% but the best I got was this, still not quite right:
"__kiso_and_tenryuu_kantai_collection_drawn_by_orqz__20fe79072a1928a0bd22d02cc8501532"
Any help would be greatly appreciated. I can't quite figure this out and I checked the wiki but couldn't find anything for this specific issue. Thanks for your time man.

use%filename% as seen here https://github.com/Bionus/imgbrd-grabber/wiki/Filename

Hey I can't believe I didn't see that earlier. However what extension should I be using after that? Because when I tried %filename%/%md5%.%ext%  It just did the same thing as before and put it in a named folder while the file remained just a bunch of numbers.

Update: Ok so I was messing around with it and I tried removing the forward slash "/" from "%filename%/%md5%.%ext%"  so it was just "%filename%%md5%.%ext%" and this improved the results but it's still not quite a match. There's no parenthesis "()" or "-" in the filename.

Indeed, that's normal. Note that returning  "__kiso_and_tenryuu_kantai_collection_drawn_by_orqz__20fe79072a1928a0bd22d02cc8501532" would also be correct, it's the actual filename on the server.
For example: https://danbooru.donmai.us/data/__asashimo_kiso_maya_and_tenryuu_kantai_collection_drawn_by_kaga3chi__a068761d1c3a23069b1f2a124e0933be.png
Grabber replaces the underscores by spaces (can be disabled) but the original filename is actually pretty ugly. Danbooru just does some real time renaming when you click the download button (through the download html attribute of the a element and some javascript).
So, from here you have three options:

Re-create the filename using the %character% and other tags
Use the Grabber default version of the filename (without underscores)
Keep the underscores by changing your settings or using %filename:unsafe% (version 4.7.0)

Unless there is a need to update the program and add a new token for this "fake filename"? It's up to debate, I don't think it's necessary, but maybe for people with an already existing collection, it could be a good way to match their already existing files.

Thank you very much for responding, I'm learning a lot about this. I've spent the past few days trying to figure out the intricacies of the booru sites and the image grabbers.
As you said while it doesn't seem like a big deal, for people like me who have been saving pics for a long time and adding to their archive, and where organization is key to locating everything, it would be ideal to keep the file naming consistent with how danbooru renames the files through the download button.
Honestly the whole reason I'm looking into mass image grabbers like this is because saving and renaming files individually is consuming too much time in my life, yet I'm one of those guys who has severe OCD and when they see a beautiful piece of art, or a fine pair of tiddies I can't turn away haha. It's a predicament. The constant fear of missing an amazing picture on my timeline keeps me glued to twitter and takes so much time. I just wanna get the whole archive and complete my collection so I don't have to worry about it anymore lol.
I tried messing around and recreating the naming system with tokens but %character% seems to include the copyright so if you put %copyright% after it you get a double over, but it doesn't include crossover copyrights, and if there is more than one character it has the copyright in parenthesis after each character name, making a really bloated and ugly filenaming system. Like so:
"kiso (kantai collection)+tenryuu (kantai collection) drawn by orqz - 20fe79072a1928a0bd22d02cc8501532"
(or with the copyright)
"tenryuu_(kantai_collection) (kantai_collection yoru_no_yatterman) drawn by torichamaru - 677364b"

So I believe what you're asking for is indeed the "fake" filename danbooru generates when clicking the "download" button?
If so, I'll try to include this in the next update.

Thanks a lot man, it would mean a lot to me. I appreciate you taking the time to consider it and explain all this to me. I hope you have a good one!
Should I click "close and comment" or leave this open for future reference?

Thank you so much man, bless your heart =')

AFAIK, in latest versions, using %filename% on Danbooru returns the correct name as long as you're using the XML or JSON source.

I'm also trying to get that "fake" file name which I get when clicking on "download" on danbooru.
But I'm still getting:
__artemisa_bell_ashcroft_and_ellen_mira_mathers_date_a_live_drawn_by_tsunako__e97987facf4dd88711cbc7b45d901d6d.jpg
instead of:
artemisa bell ashcroft and ellen mira mathers (date a live) drawn by tsunako - e97987facf4dd88711cbc7b45d901d6d.jpg
even when I set the only source as XML or JSON.
Name: %filename%.%ext%
Do I need to do anything more?


desktop shortcut

pls add a tick box to the install wizard to create a desktop shortcut for the client exe

Ok this needs to be set in install4j config

Needs to be done by @micheljung or @Geosearchef  or one of them might need to give me an install4j license. I dont think I can do it without the UI...

https://www.ej-technologies.com/resources/install4j/help/doc/help.pdf page 185

Got the license from downlord so might do it soon TM

Duplicate #356


Issues with mesh order - Pb with mesh Nodes or Elements : 8

Hello,
I have used several times gmsh(version 4.11.0, November 6, 2022) with Safir (version 2022.b.3 and 2019 also) and I have noticed a small bug with the mesh generating order. When I have created my 2D geometry, I always go in Tools--> Options --> Mesh-->General and I put a mesh order of 2. However, when later I generate the mesh (using the command 2D mesh) I always have a mesh where elements have order 1.
Then if I use the command Set order 2, the mesh is finally of order 2, but I cannot generate the .IN file and the error displayed is :_Pb with mesh Nodes or Elements : 8. I have also noticed, that a Refine by Splitting decrease the element order. Can you provide me some helpful explanation for managing this issue ?
Thanks a lot for advance
Best regards

Please provide a sample .geo and .g4s (rename them as .geo.txt and .g4s.txt for correct upload) to reproduce this wrong behavior

thanks a lot ,
here are the two files. I added a screenshot of when I tried to generate the mesh with second order elements.
SousSol_v1.g4s.txt
SousSol_v1.geo.txt


fix: make query params visible in various flows when saved in REST API datasource

Description

Make query params visible when an API datasource is saved. Currently only header info is shown on the page immediately following the save datasource action.
Make query params visible on the right hand section when a REST API action is edited.
TBD: some FE side changes will be added separately.

Fixes #9930
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=44e896a


Did you consider to apply xDiT for parallel inference

Hello Allegro Team,
I hope this message finds you well. I would like to propose the integration of xDiT, a scalable inference engine for Diffusion Transformers (DiTs), into the Allegro ecosystem. xDiT offers several compelling benefits that could significantly enhance the performance and scalability of inference tasks within Allegro.
Key Benefits of xDiT:

Ease of Transformation into Sequence Parallel + USP Version:

xDiT can be easily adapted to support sequence parallelism combined with Unified Scaling Policy (USP), making it highly flexible and efficient for various inference scenarios.

Compatibility with huggingfacee diffusers Ecosystem and ComfyUI:

xDiT is designed to be compatible with the diffuser ecosystem and ComfyUI, ensuring seamless integration and interoperability with existing tools and workflows.

Scalability with PipeFusion and Hybrid Parallelism:

xDiT's support for PipeFusion and hybrid parallelism allows it to scale to very large-scale inference tasks, providing substantial performance improvements.

Additional Highlights:

Efficient Inference for Video Models:

xDiT has demonstrated significant success in reducing inference latency for video models, such as CogVideX-5B and mochi1-10B, achieving notable speedups.

Performance Gains:

The mochi-xdit project has shown a 3.54X reduction in inference latency compared to the official open-source implementation.

References:

GitHub Repository:

xDiT
mochi-xDiT

Medium Articles:

Enhancing Parallelism and Speedup for xDiT in Serving the Mochi-1 Video Generation Model
Leveraging xDiT to Parallelize the Open-Sourced Video Generation Model CogVideoX

Thank you for considering this proposal. I look forward to your thoughts and feedback.

Hi Feifeibear,
Your xDiT looks amazing, and I've starred. However, we're currently really short-handed and do not have enough time for the integration ourselves. If you can help us with the integration, we'd love to make a joint announcement to our developer community! p.s. Allegro will receive an I2V upgrade soon
Best Regards,
Maazel

Hi Feifeibear,
Your xDiT looks amazing, and I've starred. However, we're currently really short-handed and do not have enough time for the integration ourselves. If you can help us with the integration, we'd love to make a joint announcement to our developer community! p.s. Allegro will receive an I2V upgrade soon
Best Regards, Maazel

Thanks! Feel free to contact us if you need parallel inference solutions.


ValueError: Type <class 'sqlalchemy.sql.sqltypes.REAL'> not currently supported by Spectrify. Open an issue?

Spectrify version: latest
Python version: 3.6
Operating System: Mac OS

Description
Copying a table with real column - actually a float4 column
What I Did
spectrify transform

I think it is related to this piece of code
https://github.com/hellonarrativ/spectrify/blob/master/spectrify/utils/schema.py

I wonder if this is related to Redshift seeing FLOAT as FLOAT8, and everything else seeing FLOAT as FLOAT4, which correlates with REAL.

Yes it might be, the only numeric datatypes I have are int4 and float4

Seems like altering float4 columns to float8 would be the quickest fix?

Correct.

Open to PRs for this, if anyone is up for it!

Opened #41 !


Add a cut based on p_timestamp

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

It would be nice to have a cut based on timestamp available though create_cuts and as an actual cut, rather than a hack with lists and whatnot.

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

This has been in master for a while.

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

This is in my branch
https://bitbucket.org/joe_fowler/mass/src/396a83689e7cb6f2b20427bb95457f26cc93889f/mass/core/channel.py?at=galen#cl-1174
We should try merging again sometime soon.


unwrap() hanging execution: markdown report generation

version: 0.2.10
aweil@david-pc18:~/work/ink/test-cases/avoid-autokey-upgradable/avoid-autokey-upgradable-1/vulnerable-example$ cargo scout-audit -v --output-format md
    Updating git repository `https://github.com/CoinFabrik/scout`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-2/reentrancy-2-1/remediated-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/vulnerable-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/remediated-example/exploit`
warning: skipping duplicate package `vault-vulnerable-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example/exploit`
warning: skipping duplicate package `vault-remediated-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example/exploit`
    Updating git repository `https://github.com/CoinFabrik/scout`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-2/reentrancy-2-1/remediated-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/vulnerable-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/remediated-example/exploit`
warning: skipping duplicate package `vault-vulnerable-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example/exploit`
warning: skipping duplicate package `vault-remediated-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example/exploit`
Building detectors
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Finished release [optimized] target(s) in 0.06s
Warning: `--pipe-stderr` is experimental
Warning: `--pipe-stdout` is experimental
Checking with toolchain `nightly-2023-12-16-x86_64-unknown-linux-gnu`
thread 'main' panicked at src/output/report.rs:130:69:
called `Result::unwrap()` on an `Err` value: Error("expected value", line: 1, column: 1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Code is below:
pub fn generate_report(
    scout_output: String,
    info: ProjectInfo,
    detector_info: HashMap<String, LintInfo>,
) -> Report {
    let scout_findings = scout_output
        .lines()
        .map(|line| serde_json::from_str::<serde_json::Value>(line).unwrap())
        .filter(|finding: &Value| {
            finding
                .get("message")
                .and_then(|message| message.get("code"))
                .and_then(|code| code.get("code"))
                .is_some()
        })
        .collect::<Vec<Value>>();

Nevertheless:
aweil@david-pc18:~/work/ink/test-cases/avoid-autokey-upgradable/avoid-autokey-upgradable-1/vulnerable-example$ cargo scout-audit -v --output-format json
    Updating git repository `https://github.com/CoinFabrik/scout`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-2/reentrancy-2-1/remediated-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/vulnerable-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/remediated-example/exploit`
warning: skipping duplicate package `vault-vulnerable-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example/exploit`
warning: skipping duplicate package `vault-remediated-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example/exploit`
    Updating git repository `https://github.com/CoinFabrik/scout`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-2/reentrancy-2-1/remediated-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/vulnerable-example/exploit`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-1/remediated-example/exploit`
warning: skipping duplicate package `vault-vulnerable-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/vulnerable-example/exploit`
warning: skipping duplicate package `vault-remediated-2` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example`
warning: skipping duplicate package `exploit` found at `/home/aweil/.cargo/git/checkouts/scout-7499b4d1fc813b05/6adb623/test-cases/reentrancy-1/reentrancy-1-2/remediated-example/exploit`
Building detectors
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Finished release [optimized] target(s) in 0.06s
Warning: `--pipe-stderr` is experimental
Warning: `--pipe-stdout` is experimental
Checking with toolchain `nightly-2023-12-16-x86_64-unknown-linux-gnu`

aweil@david-pc18:~/work/ink/test-cases/avoid-autokey-upgradable/avoid-autokey-upgradable-1/vulnerable-example$ python
Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
import json
>>> f = open('report.json', 'r')
>>> data = f.read().splitlines()
>>> for idx, l in enumerate(data):
...     print(idx, str(json.loads(l))[:20])
...
0 {'reason': 'compiler
1 {'reason': 'build-sc
2 {'reason': 'compiler
3 {'reason': 'compiler
4 {'reason': 'compiler
5 {'reason': 'compiler
6 {'reason': 'compiler
7 {'reason': 'compiler
8 {'reason': 'compiler
9 {'reason': 'compiler
10 {'reason': 'build-sc
11 {'reason': 'build-sc
12 {'reason': 'build-sc
13 {'reason': 'build-sc
14 {'reason': 'build-sc
15 {'reason': 'compiler
16 {'reason': 'compiler
17 {'reason': 'compiler
18 {'reason': 'compiler
19 {'reason': 'compiler
20 {'reason': 'build-sc
21 {'reason': 'compiler
22 {'reason': 'compiler
23 {'reason': 'compiler
24 {'reason': 'compiler
25 {'reason': 'compiler
26 {'reason': 'compiler
27 {'reason': 'compiler
28 {'reason': 'compiler
29 {'reason': 'compiler
30 {'reason': 'compiler
31 {'reason': 'compiler
32 {'reason': 'compiler
33 {'reason': 'compiler
34 {'reason': 'compiler
35 {'reason': 'compiler
36 {'reason': 'compiler
37 {'reason': 'compiler
38 {'reason': 'compiler
39 {'reason': 'compiler
40 {'reason': 'compiler
41 {'reason': 'compiler
42 {'reason': 'compiler
43 {'reason': 'compiler
44 {'reason': 'compiler
45 {'reason': 'compiler
46 {'reason': 'compiler
47 {'reason': 'compiler
48 {'reason': 'compiler
49 {'reason': 'compiler
50 {'reason': 'compiler
51 {'reason': 'build-sc
52 {'reason': 'compiler
53 {'reason': 'build-sc
54 {'reason': 'compiler
55 {'reason': 'compiler
56 {'reason': 'compiler
57 {'reason': 'compiler
58 {'reason': 'compiler
59 {'reason': 'build-sc
60 {'reason': 'compiler
61 {'reason': 'compiler
62 {'reason': 'compiler
63 {'reason': 'build-sc
64 {'reason': 'compiler
65 {'reason': 'compiler
66 {'reason': 'compiler
67 {'reason': 'compiler
68 {'reason': 'compiler
69 {'reason': 'compiler
70 {'reason': 'compiler
71 {'reason': 'compiler
72 {'reason': 'compiler
73 {'reason': 'compiler
74 {'reason': 'compiler
75 {'reason': 'compiler
76 {'reason': 'compiler
77 {'reason': 'compiler
78 {'reason': 'compiler
79 {'reason': 'compiler
80 {'reason': 'compiler
81 {'reason': 'compiler
82 {'reason': 'compiler
83 {'reason': 'compiler
84 {'reason': 'compiler
85 {'reason': 'build-sc
86 {'reason': 'build-sc
87 {'reason': 'compiler
88 {'reason': 'compiler
89 {'reason': 'compiler
90 {'reason': 'compiler
91 {'reason': 'compiler
92 {'reason': 'compiler
93 {'reason': 'compiler
94 {'reason': 'compiler
95 {'reason': 'compiler
96 {'reason': 'compiler
97 {'reason': 'compiler
98 {'reason': 'compiler
99 {'reason': 'compiler
100 {'reason': 'compiler
101 {'reason': 'compiler
102 {'reason': 'compiler
103 {'reason': 'compiler
104 {'reason': 'compiler
105 {'reason': 'compiler
106 {'reason': 'compiler
107 {'reason': 'compiler
108 {'reason': 'compiler
109 {'reason': 'compiler
110 {'reason': 'compiler
111 {'reason': 'compiler
112 {'reason': 'compiler
113 {'reason': 'compiler
114 {'reason': 'compiler
115 {'reason': 'compiler
116 {'reason': 'compiler
117 {'reason': 'compiler
118 {'reason': 'compiler
119 {'reason': 'compiler
120 {'reason': 'compiler
121 {'reason': 'compiler
122 {'reason': 'build-fi
>>>

I think this was already fixed by Facu.


Reproducible images using a sequence of seeds

This PR makes it possible to reproduce datasets, and individual images from training datasets (without generating all previous images). This should be useful e.g. to generate converge maps, or the list of subhalo masses and positions, for specific images in datasets we are interested in.
Paltas already  allows you to set the numpy random seed via the config. However, it also draws some random numbers from numba, which uses a separate random number generator. Thus, setting the seed in paltas' config does not yet result in predictable images. This also means some of the unit tests are not fully deterministic.
After this PR:

We re-seed the numpy random number generator before generating each image, and seed the separate numba random generator right after that.
The first generated image uses a base seed. The second uses a tuple (base_seed, 1) as a seed (or base_seed + (1,) if base_seed is already a tuple), then (base_seed, 2), etc. Numpy uses SeedSequence internally to turn these low-quality (not very random) seeds into high-quality seeds, see e.g. here.
If the user doesn't specify a base seed to use in the config, ConfigHandler will set the random number generator seed to a random int64. (We could use a larger seed, but this way seeds are still easy to copy-paste from metadata.)

We're not exactly following best practice with random number generators: current wisdom avoids np.seed and instead makes separate random generator instances and passes them around the code. That would be a much bigger change affecting the entire code though.
Two minor changes smuggled in:

When creating the folder with npy images files, allow the folder to already exist. The mkdir can be triggered if the folder already exists, when the catalog's main npy is missing (for some reason).
Do not create a tfrecord during the generate tests, so we can run all the non-analysis tests in environments without tensorflow. The tfrecord was not actually tested anyway (other than implicity requiring it exists by the os.remove cleanup statement). If you'd rather the file is made during testing we could e.g. check if tf imports, and only ask for the tfrecord in the tests if it does.

Looks great!


PDI-5491 Enable setting Rowset prefetch size in the Table input step

Fixes "runaway" query prefetch when rows are wide or contain blob columns.  But required UI changes that are only localized to us_EN.

Build completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands:

ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f ui/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands:
rm -r ~/.ivy2/local || echo no publish local to remove
Changed files:
core/src/org/pentaho/di/core/database/Database.java
engine/src/org/pentaho/di/trans/steps/tableinput/TableInput.java
engine/src/org/pentaho/di/trans/steps/tableinput/TableInputMeta.java
engine/src/org/pentaho/di/trans/steps/tableinput/messages/messages_en_US.properties
ui/src/org/pentaho/di/ui/trans/steps/tableinput/TableInputDialog.java
Unit test coverage change:
org.pentaho.di.core.database.Database:

Instruction Change : -.04%
Line Change : -.04%

org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory:

Branch Change : -7.14%
Complexity Change : -7.69%

org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet:

Branch Change :  + .53%
Complexity Change :  + .56%
Instruction Change :  + .07%

org.pentaho.di.job.entries.sql.JobEntrySQL:

Instruction Change :  + 3.28%
Line Change :  + 3.87%

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL:

Branch Change :  + .67%
Complexity Change :  + .94%
Instruction Change :  + .13%

org.pentaho.di.repository.kdr.KettleDatabaseRepositoryCreationHelper:

Branch Change :  + 1.64%
Complexity Change :  + .69%
Instruction Change :  + 2.43%
Line Change :  + 3.70%

org.pentaho.di.trans.steps.checksum.CheckSumMeta:

Branch Change : -1.32%
Complexity Change : -1.43%
Instruction Change : -.22%
Line Change : -.54%

org.pentaho.di.trans.steps.constant.ConstantMeta:

Instruction Change : -.10%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta:

Instruction Change : -.05%

org.pentaho.di.trans.steps.dbproc.DBProcMeta:

Instruction Change : -.11%

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta:

Branch Change :  + .66%
Complexity Change :  + .41%
Instruction Change :  + .50%
Line Change :  + .24%

org.pentaho.di.trans.steps.groupby.GroupByMeta:

Branch Change : -2.08%
Complexity Change : -2.11%

org.pentaho.di.trans.steps.ifnull.IfNullMeta:

Branch Change : -2.00%
Complexity Change : -1.89%
Instruction Change : -.17%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta:

Instruction Change : -.05%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta:

Branch Change : -1.18%
Complexity Change : -1.35%

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta:

Instruction Change : -.14%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta:

Instruction Change :  + .04%

org.pentaho.di.trans.steps.tableinput.TableInputMeta:

Complexity Change : -1.00%
Instruction Change :  + .68%
Line Change : -.10%
Method Change : -3.55%

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta:

Branch Change :  + .53%

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta:

Instruction Change : -.18%

org.pentaho.di.trans.steps.webservices.WebServiceMeta:

Branch Change : -1.79%
Complexity Change : -1.19%
Instruction Change : -.07%

org.pentaho.di.trans.Trans:

Branch Change :  + .10%
Complexity Change :  + .14%
Instruction Change :  + .09%
Line Change :  + .11%

Integration test coverage change:
org.pentaho.di.trans.step.BaseStep:

Branch Change : -.29%
Complexity Change : -.18%
Instruction Change : -.13%
Line Change : -.23%

License header violations:

Copyright year is not the current year on engine/src/org/pentaho/di/trans/steps/tableinput/TableInput.java. Found 2013. Was expecting 2016
Copyright year is not the current year on engine/src/org/pentaho/di/trans/steps/tableinput/TableInputMeta.java. Found 2013. Was expecting 2016
Copyright year is not the current year on ui/src/org/pentaho/di/ui/trans/steps/tableinput/TableInputDialog.java. Found 2013. Was expecting 2016

Checkstyle violations:
See: https://github.com/pentaho/pentaho-coding-standards
File /home/buildguy/project/core/src/org/pentaho/di/core/database/Database.java

Message: '(' is not followed by whitespace. at Line: 1,655 Column: 44
Message: '(' is not followed by whitespace. at Line: 1,655 Column: 61
Message: ',' is not followed by whitespace. at Line: 1,655 Column: 76
Message: '(' is not followed by whitespace. at Line: 1,655 Column: 77
Message: 'typecast' is not followed by whitespace. at Line: 1,655 Column: 86
Message: ')' is not preceded with whitespace. at Line: 1,655 Column: 102
Message: ')' is not preceded with whitespace. at Line: 1,655 Column: 114
Message: ')' is not preceded with whitespace. at Line: 1,655 Column: 115
Message: 'else' child have incorrect indentation level 10, expected level should be 12. at Line: 1,675
Message: 'member def type' have incorrect indentation level 10, expected level should be 12. at Line: 1,675
Message: File contains tab characters (this is the first instance). at Line: 1,675 Column: 9
Message: ',' is not followed by whitespace. at Line: 1,675 Column: 28
Message: ',' is not followed by whitespace. at Line: 1,700 Column: 28
Message: '(' is not followed by whitespace. at Line: 1,744 Column: 44
Message: '(' is not followed by whitespace. at Line: 1,744 Column: 61
Message: ',' is not followed by whitespace. at Line: 1,744 Column: 76
Message: '(' is not followed by whitespace. at Line: 1,744 Column: 77
Message: 'typecast' is not followed by whitespace. at Line: 1,744 Column: 86
Message: ')' is not preceded with whitespace. at Line: 1,744 Column: 102
Message: ')' is not preceded with whitespace. at Line: 1,744 Column: 114
Message: ')' is not preceded with whitespace. at Line: 1,744 Column: 115

File /home/buildguy/project/engine/src/org/pentaho/di/trans/steps/tableinput/TableInput.java

Message: '(' is not followed by whitespace. at Line: 212 Column: 22
Message: ',' is not followed by whitespace. at Line: 212 Column: 37
Message: ')' is not preceded with whitespace. at Line: 212 Column: 62

File /home/buildguy/project/engine/src/org/pentaho/di/trans/steps/tableinput/TableInputMeta.java

Message: Line has trailing spaces at Line: 83
Message: File contains tab characters (this is the first instance). at Line: 131 Column: 1
Message: Line has trailing spaces at Line: 133
Message: '(' is not followed by whitespace. at Line: 137 Column: 29
Message: ')' is not preceded with whitespace. at Line: 137 Column: 46
Message: '(' is not followed by whitespace. at Line: 177 Column: 43
Message: ')' is not preceded with whitespace. at Line: 177 Column: 65

File /home/buildguy/project/ui/src/org/pentaho/di/ui/trans/steps/tableinput/TableInputDialog.java

Message: Line has trailing spaces at Line: 100
Message: '(' is not followed by whitespace. at Line: 211 Column: 26
Message: Line has trailing spaces at Line: 226
Message: Line has trailing spaces at Line: 227
Message: Line has trailing spaces at Line: 228
Message: 'if' have incorrect indentation level 2, expected level should be 4. at Line: 493
Message: File contains tab characters (this is the first instance). at Line: 493 Column: 1
Message: ')' is not preceded with whitespace. at Line: 493 Column: 43
Message: 'if' child have incorrect indentation level 4, expected level should be 6. at Line: 494
Message: 'method call' child have incorrect indentation level 4, expected level should be 6. at Line: 494
Message: '(' is not followed by whitespace. at Line: 494 Column: 37
Message: 'if rcurly' have incorrect indentation level 2, expected level should be 4. at Line: 495
Message: '(' is not followed by whitespace. at Line: 553 Column: 24
Message: '(' is not followed by whitespace. at Line: 553 Column: 34
Message: ',' is not followed by whitespace. at Line: 553 Column: 56
Message: ')' is not preceded with whitespace. at Line: 553 Column: 60
Message: ')' is not preceded with whitespace. at Line: 553 Column: 61

@malsmith  - any chance you can clean up the checkstyle issues so I can process the pull request? Thanks!

Unfortunately, this isn't the way the PM wants this implemented. Instead of only being implemented at the Table Input step, PM wants it implemented as a database configuration option as well. Please see http://jira.pentaho.com/browse/PDI-2458