Upload dev wheels to Anaconda.org + revamp wheels publishing workflow

Description
This PR introduces the following changes:

It adds a deploy_anaconda job where the wheels can be uploaded to https://anaconda.org/scientific-python-nightly-wheels/PyWavelets/ using the scientific-python/upload-nightly-action GitHub Action
A workflow_dispatch trigger to push the nightly wheels, and a CRON schedule that matches the one in #710
Replaces the cibuildwheel installation with its upstream GitHub Action, in order to get updates from Dependabot (see #708)
Bumps up versions for the checkout actions and bumps the major version for download-artifact and upload-artifact
Ensures that the necessary job runs or is skipped, based on the other wheel builds that may pass or fail

Footnotes
This PR closes #712.

@rgommers, this is ready for your review whenever you have the time for it. I thought that the changes weren't much!

With these changes, the PyPI job will run on:

Tags

and the Anaconda PyPI index job will run on:

Pushes to master/v1.XX,
On a schedule, same as the WASM upload job (should we alter the CRON statement to have a 5-minute gap in case too many jobs start?)
Manually

Should we allow the PyPI job to be triggered manually as well?

Should we allow the PyPI job to be triggered manually as well?

Yes, that would be useful to do.

I guess we should add another input to the workflow_dispatch: event to gauge where to upload the wheels (there might be a situation where we would want to publish to just Anaconda, or just PyPI, or both).

I guess we should add another input to the workflow_dispatch: event to gauge where to upload the wheels (there might be a situation where we would want to publish to just Anaconda, or just PyPI, or both).

You are right. Actually, on second thought, this is a little dangerous. It should be a little hard to deploy to PyPI. Let's drop that last change. We do like 1-2 releases a year, so in case there's a problem with building from the tag, let's just make sure a maintainer fixes the problem and then moves the tag to do a release.

You are right. Actually, on second thought, this is a little dangerous. It should be a little hard to deploy to PyPI. Let's drop that last change. We do like 1-2 releases a year, so in case there's a problem with building from the tag, let's just make sure a maintainer fixes the problem and then moves the tag to do a release.

Thanks for the clarification! Yes, PyPI is permanent, so we do not want to trigger a broken release (even if the input is false by default). I have reverted the change in https://github.com/PyWavelets/pywt/pull/714/commits/e8e4d86f42aab0fe1a011f8496b9cb53e1a74033.

I tried this on my fork, and the uploading is broken: https://github.com/rgommers/pywt/actions/runs/8252417966. The problem is the name: field of upload-artifact, it is not specific enough. Maybe it used to work and the action got more strict.
On other projects I see that there is one wheel per zip file with the Python interpreter included in the upload name, e.g.: https://github.com/numpy/numpy/actions/runs/8238976297. I'm not sure if that is the optimal solution. Could you investigate, and then test from the master branch of your own fork?

Yes, it used to be more lenient with v3. I checked the workflow and the reason is that we are restricting the Python versions being built using cibw_python in the matrix – this produces parallel jobs per Python version (and therefore the name of the artifact must be different and the matrix variable must be present).
I had not used the CIBW_BUILD enrivonment variable before and therefore did not face this problem (the difference is that it would build Python 3.9–3.12 in serial one, after the other, in the same job).
I have pushed https://github.com/PyWavelets/pywt/pull/714/commits/90ec5e4cbf8d4bbf0aaf8c224df0ef2abe714f3d which should fix this, here's a workflow run I have triggered just now – let's see if it passes: https://github.com/agriyakhetarpal/pywt/actions/runs/8252934295

Looks like it doesn't like the * in the name.

Yes, https://github.com/agriyakhetarpal/pywt/actions/runs/8253018855 works

Now that both cibuildwheel and meson-python correctly set MACOSX_DEPLOYMENT_TARGET, we should look to build arm64 wheels and test them natively before cutting 1.6.0. Do you mind opening a separate issue and PR for that or can I make that change here?

The upload to anaconda.org didn't actually work: https://github.com/PyWavelets/pywt/actions/runs/8253753639/job/22576823450. Could you have a look at that?

Ah never mind, you're already on it!


Refactor object model

do not merge yet
Opening early for visibility and to use a discussion point.
[Note from @elliotcm: please see my comment below for the best way to contribute feedback at this stage]
Depends on: https://github.com/alphagov/gds-api-adapters/tree/publishing-api-refactor
Requires a rebase/merge from master. Some of the pact tests won't work until this is done.
Check https://trello.com/c/qV540aFr/380-refactor-extract-publishstate-from-contentitems for a list of changes still to come.

I've had a chat with @boffbowsh about how much value there is in people reviewing this as is, and we've concluded that the high level questions (like the semver one) are still useful but maybe not in the PR itself.  If you're looking to review this and have those sorts of questions, first check the trello ticket to see if it's something we're going to work on and then drop me and patuzzo an email so we can either address them or include the answers in the docs.

We're running the New Object Model migration at the moment, it's taking a while to run. What's the plan for deployment of this? It feels like the sort of thing that needs doing carefully - as far as I can tell there's no provision to keep the new and old object models updated while the migration is running, and to sync them up afterwards?

@boffbowsh we're going to talk about that soon, probably with a whiteboard.

Cool, mind involving me in that please?

Superseded by https://github.com/alphagov/publishing-api/tree/refactor-object-model-merged-master


Refactor to add relationship member management to Collection

This work is to support adding, replacing, and removing members from a Collection through the relationship endpoints. This is to support incoming work to manage sensor's labels, as well.
Cassettes were updated to support the new requests.

Coverage decreased (-0.5%) to 99.534% when pulling 03c9cc5718449472486da94595d695b93c374c5a on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

I like this refactor! looking forward to seeing how it simplifies the sensor/label relationships. maybe it makes sense to break out relationships into their own object at some point, but I think keeping them under collections for now makes the most sense.

Coverage decreased (-0.6%) to 99.402% when pulling 6500bef50a824ce35f02c6cd0043add1274239ce on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

makes sense to break out relationships into their own object at some point

I agree. Let's see how this shakes out for now[

Coverage decreased (-1.7%) to 98.304% when pulling 23b1db5c7b461e0d5fd3a0b31768173c27f621ba on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

Coverage decreased (-0.4%) to 99.609% when pulling 6a5c39b8d5d8c76e0c7cff9d403ae917c8af2b30 on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

Coverage decreased (-0.4%) to 99.608% when pulling f79c19f7e46f6637c3ffe5667fd8f3cf3991fbd2 on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

Hm, after thinking more about the chaining, I think it makes more sense to do something like:
label.add_sensors(sensor).sensors.each {|sensor| ...}

than
label.add_sensors(sensor).each {|sensor| ... }

That is, add_sensors returns the self of label, rather than the Collection of sensors.
Thoughts?

@lseppala yeah i think it makes sense for label.add_sensors(sensor) to return an instance of Label, so let's go with that for now.

and you were right, there's no caching so it would have worked the other way. I was thinking of a previous implementation where we did more caching

Coverage decreased (-0.4%) to 99.608% when pulling 37f28f0fff69358d9618a5152c15b246560df85d on refactor/collection-relationships into dc25d288c8167bb3f63f71349bd1b3aa90d0d34b on master.

+1 looks good! merging


[API] HDB data types mapping to JavaScript Number Type

Implement the data type conversion as stated by the SAP documentation for hdb types that should be converted to Number type.
Mapping in hdbUtils.js

This issue is closed as the project is no longer maintained


Model name for iPad 2017?

Hello Sebastian,
Do u have any plan to support this new model?
http://www.apple.com/ipad-9.7/
Thanks

I sent in a PR as #65.

Thanks @SlaunchaMan. Merged it to master: f1deb1d6abcdb31dbce0759e5b328eefbe5b3853


maintenance(tracer): apply UA to AWS SDK clients used by Tracer

Description of your changes
applied user agent to tracer

Related issues, RFCs

Issue number: closes #1539
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[x] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my change is effective and works
[x] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

e2e tests ✅ https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/5453643388


crypto/x509: MaxConstraintComparisions typo: "Comparisions" should be "Comparisons"

x509.MaxConstraintComparisions has a typo in "Comparisions". I don't think this can be fixed in the immediate future, but perhaps in Go 2.0?

cc @agl @FiloSottile

Sorry, nothing we can do (exposed in Go 1.10). Maybe if some day we add field aliases we can fix it.


Not able to get the conversation id/replied to tweet using filtered stream

I'm trying to get the tweet to which someone's mentioned my bot, but I'm unable to get the conversation id for it. This is the response I'm getting:

Also referencing the "reply":

Is it possible I might be doing something wrong?

Same here, conversation id is None with get_users_tweets.

I don't know if it's a limitation of the api or something similar, but from what I analyze the lib is making the request and passing the parameters that, but the result is always the same, the id and text, strange.

After re-reading the documentation I noticed that I was using the wrong parameter, instead of tweet_fields I was using media_fields, now it seems to be returning everything correctly.

After re-reading the documentation I noticed that I was using the wrong parameter, instead of tweet_fields I was using media_fields, now it seems to be returning everything correctly.

Hi, can you send me the code snippet for that? Is there something I may be doing wrong. The on_tweet function returns the tweet object so I was using the attributes for that. I also tried fetching the tweet using client.get_tweet but I stil wasn't able to get the conversation ID.

I believe there should be no problems.

Are you requesting the conversation_id Tweet field?
If so, you'll need to provide all of the relevant code for further help.


Side-bar and side-bar-rtl error

Case
When you are in dev mode, in the browser you can get this

But when you export the proyect

Issue
I found this just in this template but I don't know what's the problem, it's not too bad but it change some things on the structure
Info

Operating System: Linux
Node-Version: v11.15.0

Reproduce
And the way to reproduce it is just run
npm run dev and you will see it great(The version is the side-bar and the side-bar-rtl)
when you export it
npm run export
then on the side-bar.pdf you will see that problem

Unfortunately, I can not reproduce the error. Do your skills contain specific characters or a character length?


ql: install: remove un-needed scripts that are isntalled in conda

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR is to remove fasm and qlfasm scripts from the python install dir when packaging the toolchain.
Those scripts and functionalities can be installed using conda, instead of having them copied within the /bin/python/ dir.
Fixes https://github.com/QuickLogic-Corp/symbiflow-arch-defs/issues/96

@acomodi : So "pip install git+https://github.com/QuickLogic-Corp/quicklogic-fasm"
, will install all the qlfasm scripts?

@kkumar23 Indeed and qlfasm can be invoked directly from command line


Can ISE access Azure.Storage Service Endpoint?

Hi,
The documentation says that "Your logic app or integration account can then directly access resources, such as virtual machines (VMs), servers, systems, and services, in your virtual network.".
It is unclear if Service Endpoints, specifically Azure.Storage, can be accessed vi the VNET injection?
Regards,
Balin

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

ID: b5677742-ce89-fe42-6b8e-d9b27a42ec95
Version Independent ID: 7225cb78-956a-ba35-dc04-e84356d96932
Content: Connect to Azure virtual networks with an ISE - Azure Logic Apps
Content Source: articles/logic-apps/connect-virtual-network-vnet-isolated-environment.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hi @balintbako Thanks for reaching out. We will review and update as appropriate.

@balintbako Follow the below considerations :
Access to storage accounts in other regions
Logic apps can't directly access storage accounts that have firewall rules and are in the same region. However, if you permit access for the outbound IP addresses for managed connectors in your region, your logic apps can access storage accounts in a different region except when you use the Azure Table Storage connector or Azure Queue Storage connector.
Access storage accounts through a trusted virtual network
You can put the storage account in an Azure virtual network that you manage, and then add that virtual network to the trusted virtual networks list. To have your logic app access the storage account through a trusted virtual network, you need to deploy that logic app to an integration service environment (ISE), which can connect to resources in a virtual network.
So for now I will proceed with closure of this and If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hi @DixitArora-MSFT,
Thank you for your reply!
I did almost exactly as described in "Access storage accounts through a trusted virtual network", but I added the service endpoint into all 4 subnets used by the ISE vnet injection (and that didn't work).
Could you please give a bit more details how to perform "add that virtual network to the trusted virtual networks list"?
Regards,
Balint


feat: PD-6312 apply roles to all subscriptions in AD

Now if the --subscription-id param is not provided then the script will apply the roles to all the subscriptions in the Active Directory. However if a subscription id is supplied then it will only apply the roles to that subscription.
To do this the apply code was moved to an new function and the main code runner was put inside a main function as per the Google bash style guide

@iaindurham Please resolve the merge conflicts :)


Vickel: Watch spotifymodapkpro.com

Vickel requests the watch of the watch_keyword spotifymodapkpro\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

spotifymodapkpro\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Incompatibility with PlotSquared v6

Server Implementation
Tested against Airplane Purpur branch but also affects all other Paper derivatives.
Server Version
1.16.5
Describe the bug
Going around testing plugins before 1.17's release and forced Java 16 update. Figured I'd let you know of this small incompatibility probably known about before v6's release.
[14:04:52] [Craft Scheduler Thread - 21 - Plot2Dynmap/WARN]: [Plot2Dynmap] Plugin Plot2Dynmap v5.2 generated an exception while executing task 6474
java.lang.NoSuchMethodError: 'boolean com.plotsquared.core.PlotSquared.hasPlotArea(java.lang.String)'
	at com.empcraft.plot2dynmap.Main.run(Main.java:194) ~[?:?]
	at org.bukkit.craftbukkit.v1_16_R3.scheduler.CraftTask.run(CraftTask.java:100) ~[patched_1.16.5.jar:git-Airplane-"1cf4e79"]
	at org.bukkit.craftbukkit.v1_16_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:58) ~[patched_1.16.5.jar:git-Airplane-"1cf4e79"]
	at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.16.5.jar:git-Airplane-"1cf4e79"]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
	at java.lang.Thread.run(Thread.java:831) [?:?]

To Reproduce

Install PlotSquared v6
Install Plot2Dynmap
Incompatibility.

Expected behaviour
Compatibility with v6 P2.
Screenshots / Videos
No response
Error log (if applicable)
No response
Plot Debugpaste
Irrelevant to report.
Plot2Dynmap Version
Plot2Dynmap dev 48
Checklist

[] I have included a Plot debugpaste.
[X] I am using the newest build from https://www.spigotmc.org/resources/1292/ and the issue still persists.

Anything else?
No response

Don't modify the template.


internal/gamepad: Xbox controller's button assignment seems odd on macOS desktop

There is no problem on browsers. Is this GLFW problem?

PS3 controller worked as intended.

https://github.com/libsdl-org/SDL/blob/6dfd7a17e1d9ea94015bb0fda4c570f8b20781bd/src/joystick/darwin/SDL_iokitjoystick.c#L496-L501
HID API is needed.
GameController.framework would work but I'm not sure this works with SDL's gamepad database.

Note that GameController.framework didn't work for an Xbox controller on macOS. That's odd...

Even in the current implementation, a wireless Xbox controller worked. The problem is that the button assignment is wrong. I'll take a look..

The left-upper button is always pressed unexpectedly.


⚠ Bofrost.be has degraded performance

In 0e53497, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1620 ms

Resolved: Bofrost.be performance has improved in 47b00f5.


Cookie jwt

What is this?
This is a POC to show how the JWT can be store in a cookie, rather than local storage and therefor be used on the server for SSR.
How does it work?:
The express app (the server) has a /authSuccess route setup which will setup the client cookie with the auth token. The idea is that the OAuth provider will be given /authSucess as a redirect URL
When the server receives a request, it initialises the AuthContext value to authenticated: true if the client has a valid nexusAuth cookie, or authenticated: false is no valid cookie is present.
The client read its own cookies and then setups up the AuthContext the same way the server does.
Finally, in the Router, the PrivateRoute component checks if the user is authenticated from the AuthContext and redirects to the /login page if not.
So basically, from the app point of view, the flow is:
authData;
if (client) authData = setAuthFromLocalCookie()
if(server) authData = setAuthtFromRequestCookie()

renderAppWithAuthContext(authData)

Please also see https://infosec.mozilla.org/guidelines/web_security.html#cookies and https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet

Security options will be addressed in BlueBrain/nexus#228


Group items together in each column

Is there a way to sort TODO items together for each column, so that there are no gap rows in between items of the same column. Currently, the row a TODO item is given in the kanban table is based on its order in the file or the order of retrieval for multiple file scoping.
For example, I would like to re-sort and group items in the table from the first example below to become the second example:
#+BEGIN: kanban
| TODO   | NEXT   | DONE   |
|--------+--------+--------|
|        |        | Item 1 |
|        |        | Item 2 |
|        | Item 3 |        |
| Item 4 |        |        |
|        |        | Item 5 |
| Item 6 |        |        |
#+END:

#+BEGIN: kanban
| TODO   | NEXT   | DONE   |
|--------+--------+--------|
|        |        | Item 1 |
|        |        | Item 2 |
|        |        | Item 5 |
|        | Item 3 |        |
| Item 4 |        |        |
| Item 6 |        |        |
#+END:

Thats another great idea, I think it should be possible!


Remove the "-target" suffix from the output dist directory

I have the requirement to remove the "dash" from the filename of the dist files. The reason is that the system where the app needs to be deployed does not accept "dashes" (very sad, I know), but there is no way around it unfortunately.
Can this be done? I remember older version of angular did not add the -target to the filename and that's where I'm trying to get to.
In Summary:
Instead of having a dist folder with files in the format: main-es2015.js, etc. I would like to have the files named main.js, etc...
Thank you

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Fix ASN parameter of BGPPeerStatus model.

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Could you follow https://aka.ms/AA6h31t to fix the issue for prettier?

Could you follow https://aka.ms/AA6h31t to fix the issue for prettier?

How to fix the breaking changes listed here?
https://dev.azure.com/azure-sdk/public/_build/results?buildId=366370&view=logs&j=08b5038d-1e84-5877-88da-859df8312b69&t=c1978ecd-fc8a-5291-6d7a-7dd459d8b50f

/azp run automation - sdk

Could you follow https://aka.ms/AA6h31t to fix the issue for prettier?

Done.


Add keyboard interaction model for new basic color picker

Feature Description
The new basic color picker should be easier to use when using a keyboard-only. Ensure full a11y compliance including

Keyboard navigation
Focus styling
Labels

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Verified in QA

Can we close this @barklund ?


Integrate napari layer group into atlas viewer plugin

Currently, we just add each part of the atlas we are interested in as a separate layer to napari. In the future, the napari representation of a BG Atlas should be a layer group containing all the layers of one atlas together.

Depends on https://github.com/napari/napari/pull/5132 being merged


About the pretrained model (Place2)

Hello, @Zhaoyi-Yan, can you provide the pretrained model on Place2 training dataset? I would like to compare with your method. In your paper, you use field scene images from Place2, I want to know which field scene (/f/field/cultivated or /f/field/wild) is employed in your experiment?

Eeee，both I think.   You just train the model yourself.  The model seems to have been lost. I recommand you train the model in pytorch version, which should be faster.  python train.py --batchSize=1 --use_spectral_norm_D=1 --which_model_netG='basic' --mask_type='center', run this line of code. Remember set batchSize=1 and train 30 epochs. Just take the model you train as the model I provide(I don't care...). Hope this can help you.

@Zhaoyi-Yan Thanks for your immediate reply. I want to know which field scene (/f/field/cultivated or /f/field/wild) is employed in your experiment?

Hi, I had a look at my notes written before. It seems that  the figures in the paper are obtained by training /s/synagogue/outdoor, /b/butte and /c/canyon.  Models trained on /f/field/cultivated, /t/tundra, /v/valley seems  a little worse for my case.

@Zhaoyi-Yan Thank you a lot!


IOC R Improvement

To do list :

[ ] Add Complex exercices
[ ] Improve best practices
[x] Construct main pages with link to reference manual and exercices :

[x] Week 1 : variable/function/best practices @bellenger-l
[x] Week 2 : vector/operators/upload @Ning-L (quiz done)
[x] Week 3 : list/ @bellenger-l
[x] Week 4 : df-mat/ @Ning-L (quiz done)
[ ] Week 5 : conditions/apply @bellenger-l
[ ] Week 6 : tidyverse (en 2 semaines ?) @bellenger-l
[x] Week 7 : ggplot2 @Ning-L (quiz done)

[ ] Standardise reference manual

I would suggest not including exo's in the reference manual but rather in the weekly session pages.
What do you think ?
Don't hesitate to review and provide feedback !

[ ] To add a part for Rmarkdown/Quarto for the week 1 presentation, so that the companions can use an Rmd script to render the exercises.

Ready to merge !


Add forcePull option

Closes #33
[...] for pulling the image when the execution environment gets updated.

It would be image version 1.
And that would be a faulty behaviour. Whereby this behaviour is limited.

In the case of a large usage, Nomad will distribute the runners equally among the workers. This would cause all Docker images to be updated by the force_pull option.
Only the case of small usage (/number of idle and used runners) is critical. In this case, some workers have no runner of the updated environment. It depends strongly on the usage how likely it is that a new runner will be requested in the delay time.

One could eliminate this error case by tracking on the Poseidon side whether one is still in the delay time after updating an image, and then setting the force_pull option. Do you think we should do that?

Generally speaking, I am mostly not a big fan of unnamed boolean arguments to methods because their intended use case is not immediately visible

I agree. I am a fan of Goland's way providing this information:

It would be image version 1.
And that would be a faulty behaviour. Whereby this behaviour is limited.

In the case of a large usage, Nomad will distribute the runners equally among the workers. This would cause all Docker images to be updated by the force_pull option.
Only the case of small usage (/number of idle and used runners) is critical. In this case, some workers have no runner of the updated environment. It depends strongly on the usage how likely it is that a new runner will be requested in the delay time.

One could eliminate this error case by tracking on the Poseidon side whether one is still in the delay time after updating an image, and then setting the force_pull option. Do you think we should do that?

Thanks for investigating and providing these insights! It doesn't surprise me but (of course) would have wished that the update is spread across all nodes.
I think we should prevent this error if possible. In my opinion, I see the following three options:

Always use force_pull. This might increase the start time of new containers in any load situation
Remove the image_delay and remove containers immediately. This might increase the start time of new containers in low load situations
Track the delay in Poseidon and use the force_pull option during that time span. This might increase the complexity in Poseidon and (for the duration of the delay time) increase the start time of new containers in any load situation.
Don't reuse image tags. This would allow us to even increase the delay time and would require a version identifier for those images that get updated (frequently).

I tend towards option 2 or 4. Option 2 sounds like an acceptable (but sub-optimal) quick fix while option 4 seems to be more semantically correct.

Yes, I would agree going with option 2 or 4.
For option 2 I verified that the docker image is only removed when no runner uses this image anymore.
I quickly implemented option 2 because the implementation here is trivial and we thus have a fixed reference point. For that option we still need to update the client.hcl in the staging and production environment.

8 Failures. According to my current knowledge of Mathematics 3, this might be a high probability. Why? With the other pull requests, I rarely had to restart the CI...
2 failures are due to the flaky test TestExecuteInteractivelyTestSuite/TestSendsSignalAfterTimeout
6 failures are due to the e2e tests - but not due to flaky test cases but due to the fact that Nomad could not create an environment with 10 runners within 30 seconds. Maybe because it now re-pulls the image? I will observe this during another CI run

8 Failures. According to my current knowledge of Mathematics 3, this might be a high probability. Why? With the other pull requests, I rarely had to restart the CI...
2 failures are due to the flaky test TestExecuteInteractivelyTestSuite/TestSendsSignalAfterTimeout 6 failures are due to the e2e tests - but not due to flaky test cases but due to the fact that Nomad could not create an environment with 10 runners within 30 seconds. Maybe because it now re-pulls the image? I will observe this during another CI run

Thanks for checking and investigating. 30 seconds sounds like a lot even when the image is re-downloaded each time. Didn't you mention that only the digest might get compared. Otherwise, I agree: It's really a high probability of failing tests.

Yes, as far as I know, only the digests are compared.
I was able to reproduce the problem in my environment. The e2e test gets an EOF response. Then I was able to recreate the error in Postman. The simple creation of the test execution environment fails.
When debugging, however, I was able to step through the "createOrUpdate" function without any problems. Just at the moment when the writer sends back the corresponding status message (line 129), Postman displays "Socket hang up". After a few repetitions, I changed the environment ID. From then on, I could no longer reproduce this error, whatever I did...
With this I can be relatively sure that the error is related to this pull request.

That's really interesting. I tried following your explanation but was unsure about the line you referenced. Is it this one? And I don't have any idea why this should be connected to the execution environment ID - that's not obvious, isn't it?
As you mention that this change here is not related to the flaky tests: Shall we move #52 up and tackle the test reliability next? I would expect that more reliable tests make it easier for us to identify real errors and save us from debugging each PR individually.

Is it this one?

Yes

that's not obvious, isn't it?

I agree. Maybe it was just that I introduces any change in the request, or it was just random. After I changed it once I could not reproduce the error by returning to environment 0.

tackle the test reliability next?

Ok, let's do that


Game freezes while loading world

Minecraft Version: 1.16.2
Forge Version: 33.0.10
Mod Version: 1.0.0
Single Player or Server: Single Player
Describe problem (what you were doing; what happened; what should have happened): While trying to create a new world, the game freezes at 47% loaded, and I have to kill the process with Task Manager. This has happened at the same point multiple times, both with other mods and with this as the only mod, and with resource packs loaded and without.
Log file link: https://drive.google.com/file/d/1s1fMj3LZtMsG25J8XPsTjnKYzGtxk5NB/view?usp=sharing
Video/images/gifs (direct upload or link):
If your bug is related to anything causing LAG you need to measure the lag by taking a sample https://minecraft.curseforge.com/projects/sampler

looking into it

fixed in 1.16.3 https://www.curseforge.com/minecraft/mc-mods/custom-game-rules/files/3105223


Fix insert overwrite with Glue

Fixes https://github.com/prestosql/presto/issues/1243

After the change, TestHiveGlueMetastore passes.

thanks @kokosing for your review


Add cli option to order results in output

Details mentioned in https://github.com/rrd108/vue-mess-detector/issues/5#issuecomment-2236180626

I created a PR for this #148

Now asc is the default. Was it intentional? I think desc is more logical to be the default - start with the most problematic.

It was intentional, I thought that was our final decision.
Ok, I still prefer desc order.

Updated in latest commit to main https://github.com/rrd108/vue-mess-detector/commit/5fc8fec084999235a3fbf433259ac3e79c9abd3b


Support "chunked" files stored in SeaweedFS

SeaweedFS reads the entire file into memory when serving it in order to be fast and achieve high concurrency, therefore it isn't very efficient at serving large files. The SeaweedFS wiki recommends splitting large files into smaller chunks and reading each chunk one-by-one.
weed has a CLI command that does this with the upload subcommand, i.e. weed upload -maxMB=64 file. This will read up to 64MB of the file and write to a new file in SeaweedFS and will repeat this until the entire file is in SeaweedFS in parts. Then it will create another file in SeaweedFS with the metadata of the file and file IDs of all of the chunks.
More information about SeaweedFS' implementation can be found at the SeaweedFS wiki.

 cdn-origin chunked file support to improve read/write performance


chore(deps): update gitlab plugin

Description
Update GitLab plugins

Update @immobiliarelabs/backstage-plugin-gitlab from 6.6.0 to 6.6.1

https://github.com/immobiliare/backstage-plugin-gitlab/pull/597

Update @immobiliarelabs/backstage-plugin-gitlab-backend to 6.6.0 to 6.7.0

https://github.com/immobiliare/backstage-plugin-gitlab/pull/607

Which issue(s) does this PR fix
It allow us to disable the GitLab plugin on our team instance.
PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/approve

@Fortune-Ndlovu I've rebased this PR to the yarn 3 update

This was included in #1818


TN-2794 don't insert skipped visits if posted results tie user to older RP

Complicated situation discovered thanks to an assertion in the reporting code.
If a user happens to have posted QNRs that deterministically tie them to the older RP (say they completed ironmisc on v3 versus ironmisc_v5) AND the timing is such that the older protocol (say v3) didn't include a visit (such as month 33), do NOT insert that skipped visit into their timeline, as we can't move back and forth between protocols.

Hello @pbugni! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file portal/models/qbd.py:

Line 81:80: E501 line too long (86 > 79 characters)

In the file portal/models/reporting.py:

Line 234:13: E122 continuation line missing indentation or outdented

Complicated situation discovered thanks to an assertion in the reporting code.
If a user happens to have posted QNRs that deterministically tie them to the older RP (say they completed ironmisc on v3 versus ironmisc_v5) AND the timing is such that the older protocol (say v3) didn't include a visit (such as month 33), do NOT insert that skipped visit into their timeline, as we can't move back and forth between protocols.

@pbugni to clarify an edge case: staff would not be able to add a "paper" (backdated) month 33 in this case, correct? It's not a very realistic use case, and I don't think that's a blocker - just looking for clarity.

Complicated situation discovered thanks to an assertion in the reporting code.
If a user happens to have posted QNRs that deterministically tie them to the older RP (say they completed ironmisc on v3 versus ironmisc_v5) AND the timing is such that the older protocol (say v3) didn't include a visit (such as month 33), do NOT insert that skipped visit into their timeline, as we can't move back and forth between protocols.

@pbugni to clarify an edge case: staff would not be able to add a "paper" (backdated) month 33 in this case, correct? It's not a very realistic use case, and I don't think that's a blocker - just looking for clarity.

Correct - once this is published, you may review the /timeline for the patient.  As they submitted deterministic results on v3 for month 36, they transition to v5 as of month 39.  No month 33 in v3, therefore a paper submission for month 33 would not get an associated QB.

Just noting that I added some of these business rules to https://promowiki.movember.com/display/IR/Questionnaire+Schedule#QuestionnaireSchedule-RelatedBusinessRules


Scaling problems with iframe in Safari

Hi! I have created flowchart with impress.js. I have 1st step as overview of all steps. If I open .html file it is working good, but when I'm including it with iframe on another page - it is not working proper in Safari. But if you will zoom out page (by using Ctrl/Cmd -) it will work. Also if you will click on this white area - it will zoom to other slides.
https://ukrenergo.maketry.xyz/kliyentam/dostup-do-merezh/
Normal view (not zoomed page):

Zoomed out view (zoomed out twice with Cmd -):

I've noticed, that when I'm playing with iframe height (make it smaller) - it works.
E.g. when I set height: 400px; instead of 1750px required to see whole flow.
And if you will click on other invisible (due to this bug) steps it will change iframe height to 400px (I did it with JS) .

The same problem on iOS Safari (white screen).

This I think has been resolved with some updates to Safari, but can you verify please? This might have even been caused by some APIs that were unsupported/broken at that time

How would I verify it? It worked fine for me all the time :-)


Change link from MD to HTML syntax

At https://dwc.tdwg.org/, the link to the Maintenance Group in the first paragraph is currently broken - ie, it displays the raw markdown:
[Darwin Core Maintenance Interest Group](https://www.tdwg.org/standards/dwc/#maintenance%20group)

instead of rendering this as a hyperlink. This may happen because it is embedded within an HTML  element and may be fixable by making it into an <a href=> link.

That worked great. Thank you!


Metamask breaking changes are not supported

As of November 16th metamask has been rolling out breaking changes to their API which deprecate a lot of the methods injected into window.ethereum.
One of those methods is ethereum.enable() which is currently being used here:
https://github.com/Web3Modal/web3modal/blob/master/src/providers/connectors/injected.ts#L6
in order to initialize the injected provider.
It should be replaced with ethereum.request({ method: 'eth_requestAccounts' })

Thanks for tackling this! I've included this fix with v1.9.2 release


Batch update expecting array only getting single value

If I have the following SQL:
if err:= App.Exec(
		`update orders
			set tracking_number = data_table.tracking_number,
			stage_id = (select id from order_stages os where os.id = data_table.stage_id::integer),
			meta = data_table.meta::jsonb
		from
			(select unnest(array[?]) as dcl_order_number, unnest(array[?]) as stage_id, unnest(array[?]) as tracking_number, unnest(array[?]) as meta) as data_table
		where orders.dcl_order_number = data_table.dcl_order_number;	`, []string{"TEST0003", "TEST0002"}, []int{10, 60}, []string{"AKZZ1234-00023", "FOOBA9888"}, []string{`{"serial_numbers": "1232154553,756675665657,sdlsdjlf9328"}`,`{"serial_numbers": "5555,756675665657,sdlsdjlf9328"}`}).Error; err != nil {
		return err
	}
	return nil

I should not need to wrap the parameters to unnest() with array[] if the values being used are of type array or slice as the unnest function is meant to work with that data type. Without the array[] I get an error.

I'm not clear what you're saying here - I need to do batch updates and I was using unnest() along with the update statement. Are you saying that the SQL I was using is not needed to do batch updates? The issue I raised had to do with Gorm not providing the proper data type to the statement (which expects a multi-valued type).
Do you mean to say that the query you showed can be used with an update statement?

Hi @asampal
Grom won't add the array[] for a slice, just like how it works for the IN.

So Gorm treats an array literal (what you used) differently than a slice or array reference? If yes, why does it do that?

GORM don't analyze your SQL, don't know when should we add the array[], what it does is replace the ? with its values.


Scalebar text is not localized

The numbers aren't formatted for the locale
The abbreviations (mi, ft, km) are not translated

The screenshot is taken for the german locale

That was user error. The abbreviations are translated where appropriate.
I also had to set the App Region setting, then the numbers were formatted.


API server certificate not valid for public IP

When following the instructions in the readme and setting up a cluster on openstack, the API server certificate is reported as invalid when trying to use it with the public IP. The certificate is only valid for the private IP.

This is dealt with via the supplementary_addresses_in_ssl_keys value (see documentation). Since this is supposed to be equal to a DNS record that points to the IP address of the load-balancer fronting the masters (or the first master directly), I am unsure this can be easily automated.

This is dealt with via the supplementary_addresses_in_ssl_keys value (see documentation). Since this is supposed to be equal to a DNS record that points to the IP address of the load-balancer fronting the masters (or the first master directly), I am unsure this can be easily automated.

Hmm I was expecting it to be configured through these variables. Anyway, since we know the public IP of all the nodes it shouldn't be a big deal to set these up in the inventory. I think that the dynamic inventories used in some of the contrib/terraform examples already do this, but our static intenctory.ini file does not.

Hmm I was expecting it to be configured through these variables. Anyway, since we know the public IP of all the nodes it shouldn't be a big deal to set these up in the inventory. I think that the dynamic inventories used in some of the contrib/terraform examples already do this, but our static intenctory.ini file does not.

Nice find @lentzi90 ! Let's prioritize this.

Nice find @lentzi90 ! Let's prioritize this.

What statuc inventory.ini are you talking about? If you use the static inventory.ini files generated by either exoscale or gcp this is set.
https://github.com/kubernetes-sigs/kubespray/blob/master/contrib/terraform/exoscale/templates/inventory.tpl#L9
https://github.com/kubernetes-sigs/kubespray/blob/master/contrib/terraform/gcp/generate-inventory.sh#L60

What statuc inventory.ini are you talking about? If you use the static inventory.ini files generated by either exoscale or gcp this is set.
https://github.com/kubernetes-sigs/kubespray/blob/master/contrib/terraform/exoscale/templates/inventory.tpl#L9
https://github.com/kubernetes-sigs/kubespray/blob/master/contrib/terraform/gcp/generate-inventory.sh#L60

I'm talking about this that we generate when running init. Openstack doesn't generate an inventory.ini file to use, but instead it has the dynamic terraform.py. I think we could use that one instead if we just document how. In any case I think it would make sense to add a bit more to our inventory.ini to make it useful in other situations like bare metal. :slightly_smiling_face:

I'm talking about this that we generate when running init. Openstack doesn't generate an inventory.ini file to use, but instead it has the dynamic terraform.py. I think we could use that one instead if we just document how. In any case I think it would make sense to add a bit more to our inventory.ini to make it useful in other situations like bare metal. :slightly_smiling_face:

Right, yea. That inventory.ini file are only there to give you a start if you set up this with bare metal machines. So basically just to give you a start. If you have your own inventory file (One that is created from terraform scrips) you should use that one instead.
Because we cant assume that you can use a dynamic terraform inventory if you have bare metal machines. So I don't think we should have that as default.

Right, yea. That inventory.ini file are only there to give you a start if you set up this with bare metal machines. So basically just to give you a start. If you have your own inventory file (One that is created from terraform scrips) you should use that one instead.
Because we cant assume that you can use a dynamic terraform inventory if you have bare metal machines. So I don't think we should have that as default.

Makes sense! It would probably be enough to reword step 2 in the quick start. That was where I got this from. If it mentioned that you may use dynamic inventories or tweak other settings as well it would be better. Now I understand it as I'm only supposed to edit the IPs and not touch anything else (and I must use that file).

Makes sense! It would probably be enough to reword step 2 in the quick start. That was where I got this from. If it mentioned that you may use dynamic inventories or tweak other settings as well it would be better. Now I understand it as I'm only supposed to edit the IPs and not touch anything else (and I must use that file).

@lentzi90 Would you say that https://github.com/elastisys/compliantkubernetes-kubespray/pull/30 closes this issue?
Or would you like even more documentation on this?

@lentzi90 Would you say that https://github.com/elastisys/compliantkubernetes-kubespray/pull/30 closes this issue?
Or would you like even more documentation on this?

Yes, #30 together with #22 is enough to close this I think. :slightly_smiling_face:  Closing...

Yes, #30 together with #22 is enough to close this I think. :slightly_smiling_face:  Closing...

Err... didn't realize #30 was not merged yet :joy:

Err... didn't realize #30 was not merged yet :joy:

It is now :wink:

It is now :wink:


Improve one UI string

Found during translation: I'm not sure what is meant there but the current string sounded a bit odd

Oh damn ! I should have been "has requested to access".
This means to review all the translations as well

Yes, "has requested" is the simpler change. But if a client is connecting and can still be granted or denied access I prefer the formulation with "is requesting access to". Your choice ;)

Makes sense. Your proposal then ! Thanks for spotting


Added new parameter return_bool to validate dataframe methods (fix linting)

Proposed changes
This PR addresses issue #51 by introducing a return_bool flag to the validate_presence_of_columns, validate_absence_of_columns, and validate_schema methods, enabling them to return boolean values rather than raising errors. This PR is also meant to fix the build error related ruff lint failure in PR #265.
Types of changes
What types of changes does your code introduce to quinn?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

hey @paulooctavio, could you please resolve the merge conflicts? Looks good otherwise!

@paulooctavio thanks for the updates! let me know if there's anything else you would like to change before I try merging again

@jeffbrennan I think is all good now, I tested ruff lint and it passed.

✅


Docker swarm ignores filters on a containers label when getting events

If I run the following (where swarm is running on :4000)
docker -H :4000 events -f label=foo=bar
then
docker -H :4000 run busybox
the events command will output events for this run command, even though the label 'foo=bar' does not exist.
looking at api/events.go and api/handlers.go (if these are the correct places) - it looks like any filtering other than until is not supported? But this doesn't seem to be explicitly documented.
Server Version: swarm/1.2.5

I was able to reproduce it. Docker swarm version 1.2.5 / docker 1.13.0 from master.

Closing this, dupe of https://github.com/docker/swarm/issues/2390.


Can drop attachments, but not actual emails on some PCs

User running Office Home & Business 2013 (x64). He can drag and drop email attachments, but can't drag/drop a full email (.msg).
From a different PC running the same build I can drag an email without issue.
Log attached. Any ideas?
OutlookFileDrag.log

That appears to have fixed it. I'll test on a few other PCs and let you know if it recurs. Thanks!


chore: Release

Codecov Report

Merging #23 (a117a79) into main (52de2ba) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage   92.75%   92.75%
=======================================
  Files          10       10
  Lines         566      566
=======================================
  Hits          525      525
  Misses         41       41


SAA-261 publishing activity creation event and start introduction of localstock for working/testing queues locally.

Codecov Report
Base: 69.05% // Head: 68.84% // Decreases project coverage by -0.21% :warning:

Coverage data is based on head (9266e79) compared to base (180cfd4).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #139      +/-   ##
============================================
- Coverage     69.05%   68.84%   -0.22%
  Complexity      599      599
============================================
  Files           137      137
  Lines          2870     2879       +9
  Branches         87       88       +1
============================================
  Hits           1982     1982
- Misses          828      837       +9
  Partials         60       60

Impacted Files
Coverage Δ

...activitiesmanagementapi/service/EventsPublisher.kt
7.14% <0.00%> (-12.86%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


https/tls and proxy support

Hi David, is running capnpn over tls/https (and through a proxy) something thats feasible to bolt on the this project? I'm contemplating sponsoring the development of something like it as we would like to start to use capnp for message passing between out appliances and servers (I think thats a good use-case :-) )

Hi!
capnp-rpc-rust allows you to construct RPC connections over arbitrary futures-enabled input/output streams.  It should work to have input_stream and output_stream be layered on top of TLS, perhaps through the tokio-tls crate.
I think that getting Cap'n Proto RPC to work over HTTPS would be more difficult, because Cap'n Proto RPC is a complex stateful protocol that seems difficult to map into a request/response pattern.
Alternatively, if you don't have a need for the fancier object-capability features of Cap'n Proto RPC, you could define your own simple RPC protocol that uses just Cap'n Proto serialization in HTTP requests/responses.


Handling redirects "thrown" from endpoint code.

Describe the problem
AFAICT, there's no simple way that one can implement an "authentication gate" (e.g. something that checks for a signed-in user, and if one does not exist, redirects to a sign in page)  without explicitly returning the redirect and it's associated headers "inline." By "inline" I mean like this...
// some route where the user has to be authenticated...
export const get = (event) => {
  const currentUser = myGetTheCurrentUser(event);
  if (!currentUser) {
    return {
      status: StatusCodes.MOVED_TEMPORARILY,
      headers: {
        Location: '/auth',
        // plus some cookies to make the redirect user friendly: flash message, original url,  etc.
      }
    };
  }
  // the user is logged in, so continue...
}

This may not look so bad in one endpoint, but it's not great repeated in every similarly gated endpoint in an app, especially if you want to add some cookies to make the redirect user-friendly.
It'd be way more fun to write it this way...
// some route where the user has to be authenticated...
export const get = (event) => {
  const currentUser = myGateAuthenticated(event);
  // the user is logged in, so continue...
}

... where myGateAuthenticated either returns the user or throws the redirect output (or something that is turned into a redirect output.)
For this to work SvelteKit would have to (slightly?) change the way it deals with the things thrown from endpoints.
Describe the proposed solution
Here's how it'd work...

SvelteKit wraps the endpoint function in a try...catch block. I'm pretty sure this already happens. :)
In the catch, if the thrown thing looks like a "redirect output", i.e. an object that has a 3xx status and a Location header, SvelteKit should deal with it just as if had been returned rather than thrown, rather than displaying __error.svelte.

I believe this "authentication redirect" case is pretty special. Other userland conditions where one might want to throw rather than return (e.g. authorization, not found, etc) can be handled by throwing a regular Error and displaying the message in __error.svelte.
It's also a pretty common pattern, and therefore (barring me having missed something obvious) deserves a specific solution.
Alternatives considered
Some things I've tried:

Throwing a custom error and dealing with it in __error.svelte. This doesn't work -- you can't redirect from ErrorLoad. In any case this solution seems janky.
Wrapping entire endpoints in try...catch blocks that check for this specific case. This works, but it's almost as inconvenient/verbose as the original situation.

Let me know if I've missed something. Thanks.
Importance
would make my life easier
Additional Information
No response

This is one of the cases that would be addressed by layout endpoints (#4274) and inheritable endpoint middleware (which I can't find an issue for right now, but is on the roadmap).


Create Extension for a Mission Summary Field.

Add Summary Text Box Here before Content
Add Extension options here before Order

Summary Field Enable checkbox
Summary Field Label Name (default: Summary)
Summary Field number of lines for initial size (default 5)
Include Summary Field in email checkbox

done

Add a space after the Sumary:
Can Summary come after timeline?

Add summary to views

Change menu name to Mission Posts Summary

Remove Index and check. There isn't a need for an index for this extension.

Update confirmation message to say Configuration was successfully updated instead of Labeled was successfully updated.
Change Summary Label Configuration to Summary Configuration
Change Default Summary Field Size to 5.
Change Update Labels to Update Configuration

done

confirmed issues fixed


Rust-analyzer gets upset when you use #![no_std]

At least on VSCode, if you have rust-analyzer and disable std, rust-analyzer still tries to keep building the test feature, which depends on std.  This leads to naming conflicts with the panic handler, for example.
A quick workaround is to throw in a #![cfg(not(test))] for the crate, which causes rust-analyzer to not build the feature anymore.
This might be a useful blurb to throw in the first setup page.

You can disable testing in Cargo.toml. Eg
[lib]
test = false

for libraries. Alternatively you can disable --all-targets using I think the rust-analyzer.cargo.allTargets config option.

Thanks, that's also very helpful!

Actually, that didn't work for me.

If you'd like to compare my working setup to yours, I made the os_template crate.
It works with rust-analyzer on VSCodium, so I suppose it should work with VSCode as well.

What fixed this for me:
make a file named settings.json in a folder named .vscode in the project's root directory.  For example, if your project directory is blog_os:
blog_os
----.vscode
--------settings.json

in that file, paste the following:
{
    "rust-analyzer.checkOnSave.allTargets": false
}


Django Rest Framework tests + fixes for python 2.7 + drop unsupported Django versions

This pull request is a bit drastic. It  includes #60 as well so you can ignore that one if you agree on this one (or the other way around)
Adding djangorestframework support for older Django versions (<1.11) would be a lot of work:

We need to investigate which version is compatible with which version of Django.
We need to document the specific versions per Django version
We need to do some compatibility checks in the tests to support all versions
We need to make a real complicated test matrix in tox / travis

And this all for Django versions which are not supported anymore, they don't receive any security updates and it's highly recommended not to use them anymore.
So that is why I removed Django versions < 1.11 in travis / tox / setup.py
I also needed to rename rest_framework.py because in python 2.7 it will clash with the rest_framework namespace from django rest framework itself (from rest_framework import exceptions for example).

 It includes #60
https://github.com/jobec/django-auth-adfs/pull/60 as well so you can
ignore that one if you agree on this one (or the other way around)
Adding djangorestframework support for older Django versions (<1.11)
would be a lot of work:

We need to investigate which version is compatible with which
version of Django.
We need to document the specific versions per Django version
We need to do some compatibility checks in the tests to support all
versions
We need to make a real complicated test matrix in tox / travis

And this all for Django versions which are not supported anymore, they
don't receive any security updates and it's highly recommended not to use
them anymore.
So that is why I removed Django versions < 1.11 in travis / tox / setup.py
I also needed to rename rest_framework.py because in python 2.7 it will
clash with the rest_framework namespace from django rest framework itself
(from rest_framework import exceptions for example).
You can view, comment on, or merge this pull request online at:
https://github.com/jobec/django-auth-adfs/pull/61
Commit Summary

Explain the REST Framework integration a bit more
Enable the AdfsAccessTokenBackend for the tests
Install django rest framework with tox
Added tests for the AdfsAccessTokenAuthentication class
restframework -> djangorestframework
Renamed rest_framework.py to prevent nameclashing with python 2.7
Updated docs to use new import path
Drop unsupported django versions
Removed < 1.10 compatibility setting as we dropped all Djangos <1.11

File Changes

M .travis.yml
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-0 (24)
R django_auth_adfs/restframework.py
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-1 (2)
M docs/rest_framework.rst
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-2 (31)
M setup.py
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-3 (3)
M tests/settings.py
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-4 (3)
A tests/test_drf_integration.py
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-5 (73)
M tox.ini
https://github.com/jobec/django-auth-adfs/pull/61/files#diff-6 (6)

Patch Links:

https://github.com/jobec/django-auth-adfs/pull/61.patch
https://github.com/jobec/django-auth-adfs/pull/61.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jobec/django-auth-adfs/pull/61, or mute the thread
https://github.com/notifications/unsubscribe-auth/AjlS_sqITDhCzGUe3lMUyij_Le6_Uy9Cks5uzWQmgaJpZM4Y1030
.

@alejandroleonbauzo You understand that you receive my pull request messages because you starred the repository yourself right? If you don't want to receive them, unstar  the repository on github or disable notifications instead of sending a pretty rude reply (which also appears on github). Thank you.

@maerteijn the issue with the package name is easily fixed with a from __future__ import absolute_import at the top of the test file.
I appreciate the efforts, but please don't just rename things or add arbitrary new lines to files. And certainly don't just go and drop support for django versions. I anticipate this package being used in enterprise environments, where there are sometimes legacy versions that need to be kept alive. I don't endorse such practice, but I know too well that it happens. So as long as tests pass on those old versions, they remain in the supported list.
I'll see how to specify the rest framework version support for the test matrix. Yes it'll vastly expand the number of test combinations. But we'll have to add them somehow anyway.
Also, because your merge request includes a lot of changes not related to one another, I can't merge in the tests and extra docs.

Ok I understand. I’ll add the import statement (didn’t know that!) to fix the namespace issue.
I try to fix the rest framework pinning then as well.
And I didn’t “just go and drop the versions”. I suggested it in this pull request to see if you would agree on that. Now I know you don’t I will change it back, no problem for me.
I’ll clean it up so the pull request includes the tests and docs only.

I kept compatibility with all the Django versions now. Let's explain the reasoning behind the picked DRF versions:

Django 1.8 / 1.9:
Last compatible version is 3.6.x
Django 1.10:
3.9.x dropped 1.10 support so I tested with versions 3.7 and 3.8
Django 1.11 / 2.0 / 2.1:
I picked versions 3.7 / 3.8 / 3.9 as they are the last three major releases and are compatible.

I'd say that supporting three official major releases is enough.
Some explanation for commit c520482cd69b2a3d624f9b119c3b04b311e69c3f: The DRF tests failed with Django versions < 1.11 as there the request parameter does not exist in the authenticate method.
See:

https://docs.djangoproject.com/en/1.11/topics/auth/default/#authenticating-users
Django 1.10 and below: https://github.com/django/django/blob/1.10.8/django/contrib/auth/init.py#L68
Django 1.11 and beyond: https://github.com/django/django/blob/1.11.16/django/contrib/auth/init.py#L93

Making the request parameter optional makes sure it won't end up in **credentials so the backend works with Django<1.11


fix: Remove unnecessary cfg and import

cfg seemed to be a combo of a logical merge conflict and legacy code. Anyway, the whole test is conditionally compiled so adding cfg(test) is basically a nop.
Also there is no testing feature in this crate :P

Import self is only necessary when other imports from the crate are needed.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.54%. Comparing base (09efafe) to head (6d466e3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #424   +/-   ##
=======================================
  Coverage   83.54%   83.54%
=======================================
  Files          37       37
  Lines        1720     1720
  Branches     1720     1720
=======================================
  Hits         1437     1437
  Misses        206      206
  Partials       77       77

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add Remove Brackets Command

Description: deletes highlighted brackets pair in current editor.
fixes https://github.com/Pustelto/Bracketeer/issues/49
fixes https://github.com/Pustelto/Bracketeer/issues/10
fixes https://github.com/Pustelto/Bracketeer/issues/55
Motivation
Bracketeer has hard limitation as extensions can't read language configurations in the web (in case of Bracketeer all some brackets are hardcoded e.g. vscode dynamic < and > bracket matching).
As a benefit of using native bracket model, there is small, but noticeable performance improvement.
I compared it on the contents of this file: https://github.com/microsoft/TypeScript/blob/main/lib/tsserverlibrary.d.ts
Bracketeer: latency 40ms-1s ~150ms for first time in position, then ~40ms
New command: always 2-11ms

//c @hediet

Related: https://github.com/microsoft/vscode/pull/134371
It would be cool if ctrl+delete would delete the bracket before the cursor and it's matching counterpart.

@hediet is this ready to merge, or there is anything else to be done?
I also wonder shouldn't this command be renamed to Delete Brackets instead?


Adding p2pool Saint Petersburg to pools.php

The Garlicoin landing page is the only one consistently maintained with links to all coins/algos.
For some other coins, the signature points to the coin's page. While the operator might set that up for us if reminded, that won't work with us being multi-algo. They've hashed our yescrypt before. So we'd either have two entries with the same full name; or the link from a yescrypt block would land on the argon2d page, or vice-versa. The tag has been truncated to allow whatever change the operator may make.

Although it is undesirable to link to the wrong chain, I suppose we can revisit this if this pool's share of blocks increases.
Thanks!


Widgets ordering lost when editing one widget

Context
Editing a widget "forgets" widget ordering
Steps to Reproduce

You have several widgets, change the order of them.
Enter in one of them and change a setting or the name of it.
Go back.
The widgets are now ordered in the original order

Duplicated with #10302 but leaving this since it cointains better STR

PR for this fix is here: https://github.com/CartoDB/cartodb/pull/11209


Detect overflow should use state rect

Since modifiers can change state, detectOverflow should use state's rect instead of rect returned by getBoundingClientRect

Thanks for the fix!


Enhancement: Flow run timeline interval and subscriptions

Description

Fixes timeline using a subscription interval when the flow is not running
Adds useFlows and useFlowRuns compositions for better devx

Works in the UI


[feature req] allow real json in indexing

The example in the demo is not real json. Serializers like serde will serialize in the format of:
[
  {object1},
  {object2}
]

for a Vec<MyStruct>.

The current format is called LDJSON.
I want to keep tantivy-cli as small as possible and this feature request does not make it possible to do something that was not possible before.
Also JSON for a stream of document has a lot of issue. For instance, on a CPU with many cores it is possible that tantivy's indexing outpaces json parsing. In that case, we want to parse json on more than one thread.
Splitting the payload into documents with this format is very complicated. Without scan, it is actually impossible. (granted we do scan today).


[Bug] Malwarebytes Browser Guard blocks dashdot due to phishing

Description of the bug
When visiting dashdot from Firefox with the Malwarebytes Browser Guard extension enabled, Malwarebytes blocks the website from loading due to phishing. I'm not sure if this is just an error with Malwarebytes or if dashdot is doing something in the background it shouldn't be.

How to reproduce
This seems to be reproducible with any dashdot instance, as it worked with my own instance as well as the https://dash.mauz.dev/ demo instance. Just make sure you have the Browser Guard extension and all its protections enabled.
Relevant log output
No response
Info output of dashdot cli
No response
What browsers are you seeing the problem on?
Firefox
Where is your instance running?
Desktop PC (Linux)
Additional context
No response

Dashdot does not collect any data on any instances, not even the public demo. There is nothing in there that could be phishing for your data. No kind of cookies that it saves or reads. The only thing it does, is saving your settings (light/dark mode) into localStorage. But that is basically it for storage access.
I don't know why this happens with your extension, but I can guarantee you, that Dashdot does not try to steal your data. If you think otherwise, you are of course able to check every line of code in this repository and if you are still skeptical, you can build it yourself.
So I will close this for now, as I am not sure what could be changed in Dashdot to make this notification go away, but I am very sure that I am not trying to gather any data by any means.


Default success policy update: ensure that the successful jobs counted are actually the ones that we expect JobSet to have

See https://github.com/kubernetes-sigs/jobset/pull/119#issuecomment-1536912996 for more context

/assign


The complete callback is still fired more than once when I cancel the file uploading? And I use it with angular?

I just upload one file which is about 20M size, and when it is uploading ,I click the cancel button to stop the upload and then the complete callback is fired ,I wonder why and is it normal?

The cancel() method does not actually block any workflow from finishing, but it does cancel any ongoing file upload. If you click cancel right as the last chunk finishes uploading, the complete() callback will still fire.
If you have some sample code I'd be happy to help you verify / debug.


Chess: Move H1 to D5

Please do not change the title. Just click "Submit new issue".

@tmchuynh done! Successfully played move h1d5 for current game.
Thanks for playing!


Constantly high CPU usage on Intel Mac (hypervisor)

Hey,
first of all thanks a lot for this project, really appreciated.
As I am going to buy a new MacBook Pro with M1 I was switching from Virtualbox to UTM on my current MacBook Pro 2019, 1 TB SSD, 32 GB Ram.
I am not an expert but my vms are x86_64 and I am on an Intel Mac. Is there a way to use UTM as a hypervisor and not an emulator in this setup?
The performance in the Windows 10 vm and the Archlinux vm is very (s)low and uses a way more cpu than Virtualbox. Even if the vm is using not so much cpu in the activity monitor it is constantly draining the battery pretty fast and even when not using the vm at all the fans do not stop spinning. There are no active processes in the vm besides the base system running.
When trying out settings I found out that scaling set to nearest neighbour gives me way better and sharper graphics. I don`t know about other systems, but regarding to quality here it should be the default value.
I am using the following settings:

standard q35 pc
8.196 MB RAM
cpu default
no separately enabled cpu flags
drives as disk image in qcow2 format
full graphics with virtio-vga-gl card
Scaling both nearest neighbour
sound enabled
clipboard sharing, directory sharing and usb3 enabled

Thanks in advance for any feedback and help.

I am not an expert but my vms are x86_64 and I am on an Intel Mac. Is there a way to use UTM as a hypervisor and not an emulator in this setup?

Yes, if your host and guest architecture is the same then UTM will by default use the macOS Hypervisor instead of emulating the CPU completely. This means very fast performance. The same will NOT work if your host is not the same as guest, e. g. Apple Silicon CPU and a x86 VM.
Now, in terms of CPU usage with hypervisor mode, on Intel Mac I have experienced the same (unusually high CPU usage even if the VM is idling). On Apple Silicon this is not the case, so maybe a problem with the Apple Hypervisor or QEMU (UTM backend).

@tiiiecherle can you try again with CPU set to "host"? And please provide Debug Log as per VM Troubleshooting guide.

Thanks for the help and the suggestions. I tried running the vms with CPU set to host and did not get a really noticeable difference except the win 10 vm crashes a lot.
If it helps I can try to get a debug log in the next days.
But the performance/speed is still a lot less than on virtualbox and opening an app on win takes quite a while and if anything else is used it even takes a lot longer.

It seems qemu in UTM is runnning with  -accel hvf -accel tcg,tb-size=2048 when runnning x86_64 guests on x86_64 hosts.
Is "accel=tcg" the right way when running on native CPU?


Add testnets to selector

Closes #55

Can we separate the testnet entries in the list somehow? Maybe add a -------- separator and then list all testnets in the bottom?

I got into a pretty buggy rabbit hole trying to do this, maybe we can extract that UX improvement to a different ticket?

I got into a pretty buggy rabbit hole trying to do this, maybe we can extract that UX improvement to a different ticket?

Sure! One step at a time


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.10.101",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7dbda616fc64298cedfb5b6cd52049f8038234fb"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "7dbda616fc64298cedfb5b6cd52049f8038234fb",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "scsi: target: iscsi: Make sure the np under each tpg is unique\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.101 by commit 7dbda616fc64298cedfb5b6cd52049f8038234fb. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000362


[chip/conn] run additional TCL for loading CS design files outside core files

This PR allows CS to run additional TCL script after the first analyze command, which gives the flexibility to add some additional design files/overwrite existing modules.

There was an unrelated CI issue in Kokoro.
I rebased the branch and pushed it again - let's see whether that fixes the problem.


ix-select not showing the selected value on searching an invalid value clicking enter and then click outside

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
In ix-select component on searching for an invalid value where user has already selected an option previously. pressing enter key is not resetting the selected value. On clicking outside also it not resetting the displayed value to the selected value
Already selected Active in ix-select options

1.Searches for an invalid value

2, Click on enter

3. click outside expecting that it will reset to the selected value

What type of frontend framework are you seeing the problem on?
Angular
Which version of iX do you use?
2.4.0
Code to produce this issue.
<ix-select
          [value]="vlanOptionDefaultValue"
          formControlName="networkRestrictionValue"
          name="ix-select-control"
          [disabled]="isRestrictionDisabled"
          class="restriction-dropdown"
          data-test-id="restrict-nw-access-dropdown"
          tooltipClass="communication-stream-tooltip-style"
          [ngbTooltip]="currentRestrictCommValue"
          (itemSelectionChange)="setRestrictionValue($event)">
          <ix-select-item
            *ngFor="let isEnabled of RestrictionValue"
            label="{{ isEnabled.name | titlecase }}"
            value="{{ isEnabled.value }}"></ix-select-item>
        </ix-select>

Download
link removed
password: changeme
In the installer menu, select "gcc."

If you have further insights regarding this issue please don't attach a zip file directly without any information. If you want to attach source code use a code repository


action: Require PR porting labels

A PR now needs two labels to be applied before it can be merged. One
label must be a backport label from the list below and the other a
forward port label:

backport labels: needs-backport, no-backport-needed.
forward-port labels: needs-forward-port, no-forward-port-needed.

This is to make the maintainer think carefully before merging a PR and
hopefully maximise efficient porting.
Related: https://github.com/kata-containers/kata-containers/issues/634
Fixes: #491.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

/test-ubuntu

Ping @fidencio, @egernst - please tal so we can get this merged today.

/test


Enable large address space (64-bit) support end-to-end.

Tracking the work to get TB-sized models running. A lot of environmental issues come up in those cases that we won't be focusing on (where is that TB of data stored, how the data is efficiently streamed into memory, or how is it divided into SPMD-style sharded programs, etc), but for reasonably sized sharded workloads we should be able to get to a good place.
Known issues by area:
Input:

[x] MHLO is running i64->i32 truncation and that needs to die

Codegen:

[ ] SPIR-V needs to emulate i64 (#8702)

Streams:

[ ] index needs to be split into host/device types in the compiler (#8043)
[x] Dispatch argument marshaling needs to handle these new types for packing
[x] Constant/allocation packing needs to have the right resource constraints to limit allocation size

HAL:

[x] Resource constraints here too for streaming allocations (removed attr in #9127, no longer required)
[x] #9158

VM:

[x] VM imports need to be able to take 64-bit values (#8051)
[x] #9157
[x] #9153

There's some optimizations that can be done (like in #9137 and others related to constants), but this seems to work now. @powderluv offered some larger models and I'll wait to verify those before closing this out.

https://storage.googleapis.com/shark-public/90B.mlir 90Billion params and 650GB file. It was generated a few weeks ago.

That sound is Ben deleting old video games from his computer :)

We'll see if I can compile that without running out of swap :P

I added a 9.7T SSD as swap on my VM 😂

and an 18B parameter model https://storage.googleapis.com/shark-public/18B.mlir

Closing for now as this seems to work. #9275 will make the configuration easier but is going to take some time.


1.19.2 support

Hello, it would be lovely if you added compatibility for 1.19.2.
If I wanted to adjust the stack size to 64, is it correct that the only places I should modify are the numbers in src/main/java/sf/ssf/sfort/suitablystackablestew/mixin/StewItemsMixin.java and nowhere else?
Thank you!

i'm pretty sure 1.1.2 works on 1.19.2. (reopen if i'm wrong)
and ye just change the 16 to 64


Write cluster failover, pool stuck with read-only cluster

I am using amazon aurora RDS in my application, with a cluster with 2 endpoints, read and write.
Using Pools, with the host as the cluster endpoint.
var pool  = mysql.createPool(...);  pool.getConnection( connection => connection.query())
When the primary writer endpoint failsover, the driver seems to be using the available reader endpoint, and insert/update fails (makes sense), but it never switches back to the writer, even when it becomes available.
Is there a way to handle these sittuations?

Hi @francisco4challenge how does the failover work, exactly? I assume you have a DNS name in this module's configuration, is that right? Does RDS update the DNS at some point to change that DNS name to the new writer? Also, does it terminate the connection this module has to the reader when it fails over?


Weird logic when dealing with Z3 options

Recently, we observed that Boogie seems to silently drop Z3 options when they are passed to it using lower-case letters, as in /z3opt:smt.mbqi=true. We tracked this behavior to this interesting piece of logic that deals with Z3 options:
https://github.com/boogie-org/boogie/blob/d93c222b70ebefa01d2f25685b95b2005697c9f3/Source/Provers/SMTLib/Z3.cs#L374
It appears that the options are filtered based on whether the first character is a capital letter or not, which is very strange since Z3 options are case insensitive. For example, if Boogie is invoked with /z3opt:SMT.mbqi=true the option makes its way into the generated query, while if Boogie is invoked with /z3opt:smt.mbqi=true it is unclear what happens in that case, but the behaviors are not identical.
My hunch is that this might be legacy code that should be cleaned up, but I am not totally sure, and so help would be appreciated.

Odd. Yes, this sounds like a good candidate for clean-up.

@zvonimir : I recommend consolidating all cleanup related to Z3 options in one issue and closing all other issues.

Moving discussion to issue #73.


feat: update golang to 1.18.3

Description

Update golang to 1.18.3.
Update grpc-health-probe to 0.4.11.
Update dependencies.

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1417 (680af4a) into main (4bca2c6) will decrease coverage by 0.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1417      +/-   ##
==========================================
- Coverage   45.01%   44.77%   -0.25%
==========================================
  Files         110      110
  Lines       10049    10049
==========================================
- Hits         4524     4499      -25
- Misses       5060     5088      +28
+ Partials      465      462       -3

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
44.77% <ø> (-0.25%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/daemon/peer/peertask_piecetask_poller.go
30.43% <0.00%> (-16.67%)
:arrow_down:

...ent/daemon/peer/peertask_piecetask_synchronizer.go
46.75% <0.00%> (-0.87%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
58.14% <0.00%> (ø)


Add sqlserver to the connector types

 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.

Nice!
Indeed it needs to be added to a type, check the CI logs
Type '"sqlserver"' is not comparable to type 'ConnectorType'.

And we also need to support it in
https://github.com/prisma/prisma/blob/284891a1d04a1d98f358b5cd141c79c0106ed0c3/src/packages/sdk/src/__tests__/convertCredentials.test.ts
https://github.com/prisma/prisma/blob/284891a1d04a1d98f358b5cd141c79c0106ed0c3/src/packages/client/src/__tests__/resolveDatasources.test.ts

That URI will not work with sqlserver, we use JDBC connection strings, which are not a URIs.


hope to collect clients log files by support command

when use curveadm support command, we only collect server service logs now, we may need collect clients logs by given host and mountpoint.

On the other hand, we need a limit option for handle large logs situation.

the client log file path can be specified by user, such as:
curveadm support --client-logs /path/to/logs/dir
the logs dir must be local path on current host.
if the client is running on remote host, the user should collect all/failed clients logs manually to curveadm host.


[Question] Node movement within ItemControl becomes slow

Hello Miroiu. Thank you for sharing with the open source community. I am currently learning how to develop this control. At present, we have encountered a problem where when multiple nodes in the ItemSource overlap, using another node to pass through this stack of overlapping nodes will result in a slow movement speed.
But I can hardly find the reason, and it seems that this phenomenon does not exist in your open-source software. Do you know what the reason is? If you could provide me with an answer, I would greatly appreciate it. Once again, thank you for sharing open source software, which has been very helpful in opening up a new perspective for me.

Hi lyq-lin! This could be caused by rendering complex elements/styles for nodes or connections. I would start removing UI elements from the visual tree one by one until I find the most expensive elements to render.
I noticed that having many overlapping connections can hurt performance. The built-in connections are a bit expensive in terms of rendering, however, you can create a custom connection if you don't need all the features (see #121).
If none of the above works you can also have a look at this issue: #60

thanks for you help. Your answer is simple but useful. I think I know how to continue and learn more performance optimization solutions. Thanks again!

Hello! @miroiu . I'm a person from China. .Net developer and also a content creator. I learned quite a bit about the technology and the interesting things I learned at Notiy. I had an idea if I could make a video of what I had learned about Notify and post it online (in order to share knowledge). I would recommend more people to use Notify, of course, if you don't want to or think it's a bit of a hassle, I'll discontinue the idea.

Hi @lyq-lin, it's awesome to hear you've learned to use Nodify, especially with the steep learning curve. I'm excited to see what applications you create and share in your videos!


Examples other than Kind: Secret please

"This plugin can be used not just for secrets but also for deployments, configMaps or any other Kubernetes resource."
The only way we have been able to get this plugin to work is via Kind:Secrets, per the application examples folder. Any other use, particularly configmap / helm values.yaml would be appreciated.

Other types work the exact same as secrets, you can see an example here https://github.com/argoproj-labs/argocd-vault-plugin/blob/main/fixtures/input/nonempty/full.yaml and doing a quick search through Github can find a lot of different examples.
https://github.com/pavib0403/vault/blob/main/nginx/templates/secret.yaml - ConfigMap
https://github.com/catenax-ng/maintenance-dashboard/blob/main/chart/templates/secrets.yaml - Helm
Hope that helps!


light client may be attack by 1/3+ validators

Summary of Bug
I research the code of ibc 02-client. When ibc  run ‘MsgUpdateClient’ to update client，the CheckHeaderAndUpdateState of 07-tendermint will call light client verify which only verify sign validators is more than 1/3+ trustvalidators( code)
So I think if Chain B validatorset has been change with the number of 1/3+ validators remove or offline, then the 1/3+ validators send counterfeit client of Chain B to Chain A, thus the Chain A  will be  cheated。
It also like this comment https://github.com/cosmos/ibc/issues/421#issuecomment-646912581

Expected Behaviour
This problem is light client problem.
As far as I am concerned, the light client of Chain B will slashing when discovery thus attack。And I think the attack only be discovery by the node of Chain A , but if the attack is happened in Chain B ,it will not be slashing attacker or i'm not search the way of slashing attacker.
Could you pelease help me to solve my question:

the 1/3+ validators whether or not attack to update client？
could ibc have punitive measures to provent this attack？
if ibc have punitive measures ，how can i to use it？

Version

Steps to Reproduce

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Thanks for asking these questions, @BananaLF. And great to read that you've been diving into the ibc-go code!
If 1/3 or more of the voting power belongs to faulty or malicious validators, then at a given height validators could decide on different blocks. If that happens a relayer can submit a message with both conflicting headers (what we call a proof of misbehaviour) and the light client would in that case freeze and not accept new headers any more.
If the chain is taken over by enough voting power of malicious validators that they generate only malicious headers, then the light client will be cheated and accept the malicious headers, but if this happens, then the fact that the chain has become completely malicious is a bigger problem that the light client being cheated.
I hope this helps and if you feel your questions are answered, please feel free to close the issue. We also encourage people to ask general IBC questions on Discord instead of opening an issue in the repo. That's our preferred way to answer questions; I hope that's ok with you!

Hello @BananaLF , this is indeed correct. IBC tendermint client by default runs on the BFT assumption that >1/3 of validator power is honest.
However, this is parameterized. You can choose to adopt a more stringent security model by changing the TrustLevel parameter.
This would require more frequent updates to the client in order to keep it live. Thus there exists a tradeoff between liveness and security when choosing a value for this parameter.
@crodriguezvega is correct. Please direct any followups to the Discord! Thanks!

@AdityaSripal @crodriguezvega Thanks for your reply. I will answer questions on Discord new-devs-support

If Chain B validatorset has been change with the number of 1/3+ validators remove or offline, then Chain B consensus will be work fine. But 1/3+ validator which is removed or offline will send counterfeit client of Chain B to Chain A. In this case, ibc recv msg is wrong msg, Chain B consensus is well, so ibc need send slashing msg to Chain A when recv wrong for punish the perpetrator instead of only submit MsgSubmitMisbehaviour.
As chain developer, when we support ibc,we need do something:

Make app for check this case for each header and submit MsgSubmitMisbehaviour ,send slashing msg to dst chain
Choose carefully 'TrustLevel' 'TrustingPeriod'

Can someone help me with reference values for the above parameters？


508: EM Submission Access Pop Out Module Date Fields and Pickers

Open Module:

Date picker button labels are not unique, change to Toggle Calendar for ""
Date fields look to be mislabeled, the output is the actual date instead of the text label such as 'Open Date)

Extend Module:

Date fields look to be mislabeled, the output is the actual date instead of the text label such as 'Open Date)

Private Zenhub Image

testing complete, date fields and pickers are now appropriately labeled


expose PackageInfo.dir

The dir field of the PackageInfo type might be useful for some applications.

Closed for go/packages package is preferred now.


Server side validation example

Could you provide server side validation, please?
I have backend-based validation according to business rules. Backend returns 442 HTTP response code as error payload with JSON key-value array, where key is the problematic field name and value - the error description.
I've tried to use onMutationError callback in useForm hook, there i can get errors but haven't form ref that's needed for setting errors according antd docs by formRef.setFields()
Also I have tried to use onFinishFailed prop in the Form component, but it isn't called when error.
How can i set server errors to form?

Hey @misterx 👋,
Thank you for contacting us
Have you checked Custom Form Validation example?
https://refine.dev/docs/examples/form/custom-form-validation/

@omeraplak yes, thanks. Example is covering a different flow, it's using pre-submit validation, but i need to display errors during submit process.

I've created some workaround for that, while waiting a better way
import {BaseRecord, FormInstance, useForm} from "@pankod/refine-antd";
import {HttpError} from "@pankod/refine-core";
import {UseFormProps as UseFormPropsRefine} from "@pankod/refine-antd/dist/hooks/form/useForm";

export type UseFormProps<
    TData extends BaseRecord = BaseRecord,
    TError extends HttpError = HttpError,
    TVariables = {}
    > =  UseFormPropsRefine<TData, TError, TVariables> & {
    onMutationError?: (error: TError, variables: TVariables, context: any, formInstance:FormInstance) => void;
};

export const useFormWithInstance:typeof useForm = <
    TData extends BaseRecord = BaseRecord,
    TError extends HttpError = HttpError,
    TVariables = {},
    >(useFormProps: UseFormProps<TData, TError, TVariables>|undefined) => {

    let formInstance:FormInstance;

    const onMutationError = (error:TError,variables:TVariables,context:any)=> {
        if(useFormProps?.onMutationError){
            useFormProps.onMutationError(error,variables,context,formInstance)
        }
    }

    const useFormReturn = useForm({...useFormProps,onMutationError});
    formInstance = useFormReturn.form;
    return useFormReturn;
}

Btw, how i can import UseFormProps from @pankod/refine-antd instead @pankod/refine-antd/dist/hooks/form/useForm ?

Hey @misterx ,
When I tried this way, I succeeded. Is there a point I missed?
const { formProps, saveButtonProps, form } = useForm<IPost>({
        resource: "hede",
        onMutationError: () => {
            form?.setFields([
                {
                    name: "title",
                    errors: ["Any error!"],
                },
            ]);
        },
    });

@omeraplak Thanks, your solution is much better.


[tbb] build failure

Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
`./vcpkg install tbb`

Failure logs
Computing installation plan...
error: while looking for tbb:x64-windows:
error: while loading C:\vcpkg\ports\tbb\vcpkg.json:
$.default-features[0]: mismatched type: expected an identifier

Additional context
This breakage is a side-effect of merging PR #33586.
Replacing the JSON object value of $.default-features[0] with "hwloc" enables vcpkg to build the "tbb" package again.

Do you have latest vcpkg? It also might help.

Do you have latest vcpkg? It also might help.

No, I didn't.
.\vcpkg --version
vcpkg package management program version 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75

See LICENSE.txt for license information.

The "tbb" package builds in its current state after I upgraded vcpkg.exe itself.
.\vcpkg --version
vcpkg package management program version 2023-08-09-9990a4c9026811a312cb2af78bf77f3d9d288416

See LICENSE.txt for license information.


Source control deployment failed

I cloned the source code to our Azure repo, and run the deploy.ps locally. I updated the gitRepoUrl to my devops repo, which caused the issue I think. The Arm template deployment succeeded and the RG created correctly in Azure.
But it failed when doing source control deployment, and open the log file, which is only contains the [].
Anyone can give me some thoughts on this issue? Any suggestions for deploy from devops?

Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses. Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at moment and no response is received, we will close out the issue in 3 business days. You may also always open a new issue or respond here if something does come back up.