[Sprint] Update trainer augmentation typing

Description

The typing of some values in augmentation needs to be fixed.

ex) size, brightness, etc..

Checklists

[x] I would create a corresponding branch for this issue from the designated (mostly develop) branch.
[x] This issue only contains a preceding agreement between project owners.

Because omegaconf does not support union input, it cannot handle this issue.
omegaconf.errors.ConfigValueError: Unions of containers are not supported


improve intersect-anchors command

Implement a simple tool that compares two sets of adjacencies (e.g., synteny anchors, but could also be homology clusters).  The comparison should use simple set logic classify for each adjacency set into (identity, superset, subset, incongruency) and produce both stats and a detailed file of differences of the results.
This functionality is in intersect-anchors, but some functionality was lost in a crash.  Time-to-implement is estimated at 1 hour.

closed with commit just now


Added new security questions for issue #1135

Summary of changes
Added new security-related quiz questions to the security-quiz.ts file. The new questions cover topics such as SQL Injection, phishing, CRSF and more based on articles from freeCodeCamp. I ensured that none of the new questions duplicate existing ones in the dataset.
Checklist

[x] I have read and followed the contribution guidelines.
[x] I have read through the Code of Conduct and agree to abide by the rules.
[x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[x] I have provided a summary of my changes.

closes xxxx but worked on #1135
Since this contribution is part of Hacktoberfest, could you please consider adding the hacktoberfest-accepted label if this PR meets the criteria? This would help it count toward Hacktoberfest contributions. Thank you!

It looks like you have a few conflicts.
Please resolve those before we can continue with a review
But also any repo that has the hacktoberfest topic on it will count for hacktoberfest.
So the hacktoberfest accepted label is optional.
You can learn more about that here
https://hacktoberfest.com/participation/#contributors

To resolve a merge conflict, you will need to keep both sets of questions.
You do not want to remove the other contributors questions.

Here is a good article walking your through how to best handle merge conflicts
https://dev.to/opensauced/keeping-your-branch-up-to-date-and-handling-merge-conflicts-while-waiting-for-pr-reviews-3b3h

I am closing this PR due to inactivity.


Convert Legacy Pipelines to One Branch V2

As of now, we will need to convert the following legacy build pipelines to one branch v2, as a part of extensive security effort:
Migration Guides:

Migrate Build Pipeline To OneBranch using ES365 AI tool
S360 KPI - ES Standard: Pipeline Templates.

Pipelines Identified so far that Requires Migration:

CosmosDirect-NET-Publish
CosmosDB-v2-Publish

At the moment, I have assigned this task to myself.

Related PRs:

https://msdata.visualstudio.com/CosmosDB/_git/CosmosDB/pullrequest/1342334
Adds yaml to migrate cosmos Direct Net publish pipeline to OneBranch V2


Rename project to rsm-bsa

Without that change, vcpkg install fails :
find_package(bsa CONFIG) does not work, nor does find_package(rsm-bsa CONFIG)
With that change, we can use find_package(rsm-bsa CONFIG)
If you don't want to make that change, I can instead make it as a vcpkg patch

This is a fix that needs to be implemented in the port script, see rsm-mmio for an example

I guess it is
vcpkg_cmake_config_fixup(
    PACKAGE_NAME "mmio"
    CONFIG_PATH "lib/cmake/mmio"
)

Gonna try that, thanks


update to api 0.4

Summary

Use Cases

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.

All implementation buildpacks already bumped and updated to api v0.4


Return self in set

Hi @Raynos!
set method should return weakmap instance (reference), and it does so in native implementation(s).
Here is a fix for that.
Appreciate your work.
Thanks.

lgtm.

Published v1.1.1


Incompatibility of Bitwise OR Dictionary Merge for Python < 3.9

Line 165 in dbt/adapters/athena/impl.py employs the bitwise OR (|) operator for dictionary merging:
config = LfTagsConfig(**(lf_tags_config | dict(inherited_tags=lf_inherited_tags)))

This syntax is supported in Python 3.9 and above, but leads to a TypeError in Python versions less than 3.9: TypeError: unsupported operand type(s) for |: 'dict' and 'dict'.
Perhaps a version agnostic dictionary merge approach can be taken?
config = LfTagsConfig(**{**lf_tags_config, **{"inherited_tags": lf_inherited_tags}})

@mrkre good catch, as we have to support python 3.8, for now, we might need to do what you suggested.
Any reason why you are still on Python 3.8?

Was running dagster + dbt + dbt-athena, and dagster is on 3.8. However, that can be upgraded so it's a non-issue for me. Just caught me by surprise as my pipelines broke in production.

Thanks for the context @mrkre , feel free to open a PR with your proposed changes.

this issue should be covered by https://github.com/dbt-athena/dbt-athena/pull/487 because @svdimchenko refactored the implementation.
Correct me if I'm wrong.


Could slang works with showTimePicker & showDatePicker?

The reason for this problem is:
because I used only slang, but not inited Localizations in MaterialApp.
In most cases, use only slang is enough for i18n strings.  But showTimePicker() and showDatePicker do not support costomized UI Strings.
Shall there a way to achive this?
Till now i Just want to define custom widgets to replace those buildin funtions.

Please check the documentation (specifically step 4a): https://pub.dev/packages/slang#getting-started
You need to add flutter_localizations dependency and add it to localizationsDelegates.

Closed due to inactivity


Monitor, diagnose, and troubleshoot Azure Storage: ServicePoint is deprecated in netcore6

In the section "Investigating client performance issues" the following code is suggested:
ServicePoint queueServicePoint = ServicePointManager.FindServicePoint(queueServiceClient.Uri);
queueServicePoint.UseNagleAlgorithm = false;

However in netcore6 ServicePoint is deprecated. Documentation here.
I don't know how to disable Nagle Algorithm in netcore6. Anyway, in my opinion, the documentation should not suggest deprecated code. I guess it needs to be adjusted.

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

ID: 8196beea-f457-3813-6135-71c5ec2dbf05
Version Independent ID: 119a21e3-be2f-b981-6b5d-f57c2f555c97
Content: Monitor, diagnose, and troubleshoot Azure Storage
Content Source: articles/storage/common/storage-monitoring-diagnosing-troubleshooting.md
Service: storage
Sub-service: common
GitHub Login: @normesta
Microsoft Alias: normesta

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

@joaocpribeiro - Even though this is deprecated, it still works, and it's the best option we can offer at this time.
#please-close


Added better error feedback and websocket control

Added websocket error callback.
Prevent end-user defined callbacks from blocking websocket code execution (see my previous pull request).
Added connect/disconnect methods accessible by end-user.
Also refactored the code somewhat to make it more readable and testable.

In this PR I've added an onError callback which the end-user can use to detect any errors during communication with OBS. Currently, the end-user won't be noticed about any errors and just kind of needs to trust that all the code is working, including his own. By passing the error message and exception with this callback, the user can filter out the errors he wants to deal with and ignore the rest within his own callback.
I've also added two separate commands for connection and disconnection to the websocket, as there is currently no clean solution to close the connection with the websocket (and then re-open it again).
Of course I've also added some more tests ;)

After merging this PR (or not), could you please release the new version on Maven repository?

Will release to central tomorrow! Thanks for your contribution

Great, can't wait until the release!

Sorry, forgot about it. The change is released and available from version 1.0.5 onwards! May take some minutes to duplicate to central though.

Awesome, thanks!


Create the voters table

User Story

As a user, I can request a list of voters alphabetized by last name.

As a user, I can request a single voter's information.

As a user, I can create a voter.

As a user, I can update a voter's email.

As a user, I can delete a voter.

Created table and routes


Working with pull requests that require ESMValCore changes

It is unavoidable that some diagnostic pull request will require some changes in ESMValCore, being those bug fixes or additions.
Currently we are testing using the last release of ESMValCore, so it is quite possible (although not guaranteed, as we are not testing recipes itself) that test fail even if everything is correct when using the corresponding version of ESMValCore.
My proposal will be:

Detail in pull request which ESMValCore pull requests are required for it to work
Merge them before evaluating ESMValTool pull request
Change automatic tests here to use ESMValCore development branch

...and, albeit a trivial task, always link the associated ESMValCore issue and PR on the gitHub page of the issue and PR in ESMValTool (or the other way round, don't matter, as long as the resferences are linked)

Change automatic tests here to use ESMValCore development branch

One of the advantages of not doing this, is that diagnostic developers have a much more stable version of esmvalcore to make their pull request against. This was a complaint we got fairly often, that the ground kept changing under their feet all the time.
Maybe we could set up a system that allows users to request testing against the development version of the core with a special tag in the commit message, similar to [skipci].

Still relevant?

Yes


Revert "[flutter_test] Adds method to mock EventChannels"

Reverts flutter/flutter#123726
Analysis failures on CI https://ci.chromium.org/ui/p/flutter/builders/prod/Linux analyze/12890/overview

cc @Rexios80

@Rexios80 Looks like your branch may have been outdated and didn't have these deprecations yet.

I thought I avoided the deprecated methods. How do we continue? Do I need to make a new PR?

@Rexios80
It was likely an indirect conflict with a different recent merge that only became apparent after merging. You'll have to make a new PR that avoids the method mentioned in the analyzer.
Relands typically move a lot faster though as the main code usually doesn't need to change much to resolve the issue.


Fix N+1 MySQL query performance issue

Use eager loading or preload?

i think it will be fixed with vue build


TypeScript 4.9.md - Remove the link that broke the title display on the page

This "a" tag interfered with the normal display of the title among the anchor headings.

     Auto-Accessors in Classes

Thanks, dupe of https://github.com/microsoft/TypeScript-Website/pulls?q=is%3Apr+is%3Aopen+4.9


Make J.ParameterizedType#getType() return a JavaType.Parameterized

This is a draft changing J.ParameterizedType#getType() to return a JavaType.Parameterized rather than always a JavaType.Class object.
Most likely the type should be saved in a transient field at construction time. But this is just a proof-of-concept.

@sambsnyd This change does break a few recipes and tests, but I would actually have expected more to break.
Anyway, I created this draft so it can be used as a basis for discussion.

Maybe the solution would be something more along these lines?


apps sc: Fix Harbor registry credentials

What this PR does / why we need it:
Fixes the Harbor registry credentials which prevented it from authenticating.
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[x] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

We have another bug in the update-ips script that doesn't see when Harbor uses Swift, so it doesn't configure those.


Logo for  Sunspotter Citizen Science Challenge

To feature on Sunspotter and will also use this on signage for the Adler floor facilitation of this on August 29th at Summer of Science - Power of the Crowd.  Description of the facilitated program -
As part of the Adler's Summer of Science activities floor facilitators will Adler invites guests to, as Sarcastic Rover says, “Do a science”, by joining in Zooniverse’s Summer Sunspotter Citizen Science Challenge (try saying that three times fast).  From 8/29- -9/5.  Zooniverse volunteers will be challenged to contribute 250,000 classifications to the Sunspotter (sunspotter.org) online citizen science project.  Sunspotter enlists volunteers to rank the complexity of sunspot groups to predict how the Sun's magnetic activity affects us on Earth.

Still a work in progress, but I wanted to provide some sort of update to this.

Thanks Heath.  Let me know when this is done.  Adler social media is going to share all this out as part of the summer of science stuff.  WOOOOOO!

This should be the final. If this works let me know and I'll generate the assets. If not, I'll try to fix it!

These are great.  Asset generate away.
On Wed, Aug 26, 2015 at 2:05 PM, Heath V<EMAIL_ADDRESS>wrote:

This should be the final. If this works let me know and I'll generate the
assets. If not, I'll try to fix it!
[image: citscisuns]
https://cloud.githubusercontent.com/assets/4551411/9503232/51409cc6-4bfb-11e5-9545-28b3aff53de1.jpg
—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Sunspots/issues/12#issuecomment-135141929.

--
Citizen Science Education Lead
Adler Planetarium

Two different versions at two different sizes. They're labeled 'for dark' and 'for light' too for whatever purpose they're used.

I'm assuming this goes on the front page?

I assumed it did: http://www.sunspotter.org/staging/


Block recvonly media tracks

On a AD410 doorbell (unsure about others) when you use go2rtc to simply view the camera it also starts a recvonly stream if they exist so the microphone can talk to teh doorbell.  The issue though is while this is fantastic, it also poses a functional problem with the doorbell.  When the track is selected, it completely disables the doorbell BUTTON as it thinks a call to the doorbell is underway.
This means I cannot view the doorbell, send video to remote devices (pipup, etc) without completely disabling the doorbell button.  I generally have motion triggering video on my Google Hubs/TVs for example.
This severely limits go2rtc with doorbells.  Is there a way to tell go2rtc to NOT attempt to connect on recvonly audio?  I've tried many approaches including modifying the webrtc.html files.  If I view a stream on VLC directly, the doorbell button continues to function correctly.
Any advice or enhancement?  I don't believe this is fixable by configuration only.  Maybe a parameter/filter to pass?
[
  {
    "media:0": "video, sendonly, 26 JPEG/90000",
    "media:1": "audio, sendonly, 0 PCMU/8000",
    "media:2": "audio, recvonly, 8 PCMA/8000",
    "receive": 689716,
    "remote_addr": "<IP_ADDRESS>:554",
    "send": 104580,
    "track:0": "8 PCMA/8000, sinks=0",
    "type": "RTSP client producer",
    "url": "rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1\u0026subtype=1\u0026authbasic=64/"
  },
  {
    "receive": 695520,
    "remote_addr": "udp4 host <IP_ADDRESS>:55984",
    "send": 688900,
    "type": "WebRTC server consumer",
    "user_agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
  }
]

Oh wow, my partner mentioned the doorbell button wasn't working and I figured it was just bugged again, but that makes a lot of sense.

As fast solution, add #backchannel=0 to RTSP link in config.

How can I help move this forward, Coming the the hass-card thread

As fast solution, add #backchannel=0 to RTSP link in config.

Just to mention, this seems only applicable to ffmpeg streams but not to plain RTSP URLs:
ffmpeg:rtsp://admin:123@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif#video=copy#audio=copy#backchannel=0

The above works. But the below doesn't:
rtsp://admin:123@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif#backchannel=0

As fast solution, add #backchannel=0 to RTSP link in config.

Just to mention, this seems only applicable to ffmpeg streams but not to plain RTSP URLs:

ffmpeg:rtsp://admin:123@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif#video=copy#audio=copy#backchannel=0

The above works. But the below doesn't:

rtsp://admin:123@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif#backchannel=0

I don't think ffmpeg streams support back channel?
Also it definitely worked for me on the base rtsp urls (no ffmpeg) with the ad410 doorbell

I don't think ffmpeg streams support back channel?

Maybe that's why it works. :D
But anyway, when I keep use the plain RTSP with backchannel=0, this is what info shows:

Which appears to indicate that backchannel is there.
While when using ffmpeg:

Never mind, it's working as expected. https://github.com/blakeblackshear/frigate/discussions/5156#discussioncomment-4762455


[SPARK-17795] [Web UI] Sorting on stage or job tables doesn’t reload page on that table

What changes were proposed in this pull request?
Added anchor on table header id to sorting links on job and stage tables. This make the page reload after a sort load the page at the sorted table.
This only changes page load behavior so no UI changes
How was this patch tested?
manually tested and dev/run-tests

Test build #66412 has started for PR 15369 at commit 2351a76.

Test build #66412 has finished for PR 15369 at commit 2351a76.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66412/
Test PASSed.

merged to master. Seems like a clean improvement.


proposal: net/netip: add new IP address package, use in net

I propose we fix #18804 (net: reconsider representation of IP) by importing the inet.af/netaddr into the standard library, probably as net/netaddr, so the IP type is netaddr.IP (the net package already has an IP type).  We wouldn't need to import all of it, at least not right away, but I think it'd be nice if we did... the package types work together very well.
This blog post explains the advantages of netaddr.IP over net.IP:
https://tailscale.com/blog/netaddr-new-ip-type-for-go/
Notably, it's small, comparable, and doesn't allocate.
Code is at https://github.com/inetaf/netaddr. Everybody has a Go CLA filed ( https://github.com/inetaf/netaddr/issues/181) and the license is compatible.
Having an allocation-free IP address in the standard library means we'd be able to fix #45886 ("net: add API to receive multiple UDP packets (potentially in one system call)") which ends with https://github.com/golang/go/issues/45886#issuecomment-832885959 ("We may want to wait on doing anything here until we figure out what to do with IP addresses, which still allocate."). More generally, this would improve Go's UDP performance, which has never gotten much attention. But with things like QUIC and WireGuard (both UDP-based), Go's alloc-heavy UDP handling is starting to get in the way.
Yes, we'd then have two IP types in the standard library.
As part of this, we'd then add:

conversion funcs in net to go between them (net would depend on netaddr, not vice-versa)
the net package internals would switch to netaddr.IP for performance/allocs, converting to net.IP or IPAddr on the edges only.
a couple new methods would be added (notably to UDPConn) to send/receive UDP packets using netaddr.IP alloc-free (we'd then have ~5 ways to send/recv UDP packets instead of ~4)

/cc @danderson, @josharian, @mdlayher, @crawshaw, @tklauser (co-authors), @neild (co-author for #45886)

cc @marten-seemann for quic-go

If there's any way we could address the JSON marshalling of CIDR address formats at the same time, that would be very convenient -- rather than having to rely on making custom encoders etc.
I realise that the backwards compatibility guarantee means that's unlikely to be fixed in the standard library version of "net", but if it could be addressed in this proposed new package, it would certainly make the life of network engineers much simpler!
Example: https://play.golang.org/p/3as8Ux9AzJG

If there's any way we could address the JSON marshalling of CIDR address formats at the same time, that would be very convenient -- rather than having to rely on making custom encoders etc.

https://play.golang.org/p/5QWiD-tArCc
fmt:	 <IP_ADDRESS>/24
json:	 "<IP_ADDRESS>/24"

As someone who had to invent their own IP datatype (https://pkg.go.dev/github.com/bio-routing/bio-rd/net#IP) for the very same reasons, I'm really glad to see progress on this topic. Looking forward to see a decent IP datatype in Golang.
Thanks!

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Would it be worth considering adding a runtime primitive of some sort to help avoid the "workarounds" in the intern package?  I don't think it would need to be done at the same time, but having a  user for it in the stdlib might make it more compelling.

@kylelemons There have been and are some proposals related to that, most notable probably #43615. In the interim, the workarounds are much less problematic when they are in the stdlib, because if anything is changed in the implementation that would prevent them from working, they can be changed alongside with it.

@kylelemons, what @Merovius said. And to be clear (to anybody just researching the intern package and being horrified), we are definitely not proposing exposing the intern package or any of its API. It's very much an internal implementation detail.

I don’t want to start bikeshedding, but i think that the proposed type names look a little bit cluttered, since they all share the IP prefix:
net/netaddr.IP
net/netaddr.IPPort
net/netaddr.IPPrefix
net/netaddr.IPRange
net/netaddr.IPSet
net/netaddr.IPSetBuilder

Couldn’t the IP-part just move into the package name instead:
net/ip.Addr
net/ip.Port
net/ip.Prefix
net/ip.Range
net/ip.Set
net/ip.SetBuilder

Or maybe something like net/netip as package name, if net/ip is too short?
Otherwise: Thank you, @bradfitz, for this great proposal and your highly enjoyable blog post!

My only nitpick about the package name ip is that I'd guess that is the single most commonly used variable name for any variable of type net.IP, so there's a high likelihood of having to change significant sections of code to avoid shadowing the import net/ip in code being retrofit with the new package APIs.

@mdlayher While i still think that ip is the nicest option in theory, you have certainly a valid practical concern. Maybe something net/ipa (for ›Internet Protocol address«), to avoid shadowing and jet have something short and sensible?

Might also make it ip2 as introduced in Go "2". Or use netip as package if we can forget that it belongs below net for a second.

Opened a discussion at https://github.com/golang/go/discussions/47323.

Over on #47323, people seem generally OK with package net/netip containing
type Addr
type AddrPort
type Prefix
type Range

Commenting here for more visibility. Please comment on #47323 if you have opinions. Thanks.

 Please comment there if you have opinions. Thanks.

Minor updates at https://github.com/golang/go/discussions/47323#discussioncomment-1334939.

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group


Bug fixes

Description
Talk about the great work you've done!
What's included?

One
Two
Three

Test Steps

[ ] do this
[ ] then this
[ ] finally this

Screenshots or link to CodePen/Plunker/JSfiddle

First this area is meant to be filled to explain what you worked on. See example by @pembemiriam : https://github.com/apache/fineract-cn-group-finance/pull/5
Also there is a merge conflicts since Pembe sent a PR fixing some of the issues you identified in the above PR...
Please check fix the problem and send a new PR again..
Thanks.


Add a physics joint component

Joint Component
This PR add support for physics joints (AKA constraints):

You can even enable spring 'motors' to power constraints:

Internally, it uses the ammo.js btGeneric6DofSpringConstraint class to implement a generic 6 degrees of freedom joint.
API Overview
Here is the new API (it will be private initially until it has had further testing):

API
Type
Description

pc.JointComponent#angularDampingX
number
Spring damping of angular X

pc.JointComponent#angularDampingY
number
Spring damping of angular Y

pc.JointComponent#angularDampingZ
number
Spring damping of angular Z

pc.JointComponent#angularEquilibriumX
number
Spring equilibrium of angular X. Can be -180 to 180 degrees.

pc.JointComponent#angularEquilibriumY
number
Spring equilibrium of angular Y. Can be -180 to 180 degrees.

pc.JointComponent#angularEquilibriumZ
number
Spring equilibrium of angular Z. Can be -180 to 180 degrees.

pc.JointComponent#angularLimitsX
pc.Vec2
The lower and upper angular limit for the X axis

pc.JointComponent#angularLimitsY
pc.Vec2
The lower and upper angular limit for the Y axis

pc.JointComponent#angularLimitsZ
pc.Vec2
The lower and upper angular limit for the Z axis

pc.JointComponent#angularMotionX
string
The allowed movement for angular X. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#angularMotionY
string
The allowed movement for angular Y. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#angularMotionZ
string
The allowed movement for angular Z. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#angularSpringX
boolean
Enables a spring motor for angular X

pc.JointComponent#angularSpringY
boolean
Enables a spring motor for angular Y

pc.JointComponent#angularSpringZ
boolean
Enables a spring motor for angular Z

pc.JointComponent#angularStiffnessX
number
Spring stiffness of angular X

pc.JointComponent#angularStiffnessY
number
Spring stiffness of angular Y

pc.JointComponent#angularStiffnessZ
number
Spring stiffness of angular Z

pc.JointComponent#breakForce
number
The impulse required to break the constraint

pc.JointComponent#enableCollision
boolean
Are collisions between linked bodies taken into account

pc.JointComponent#entityA
pc.Entity
The first entity linked by the constraint (must have a rigidbody component

pc.JointComponent#entityB
pc.Entity
The second entity linked by the constraint (must have a rigidbody component

pc.JointComponent#linearDampingX
number
Spring damping of linear X

pc.JointComponent#linearDampingY
number
Spring damping of linear Y

pc.JointComponent#linearDampingZ
number
Spring damping of linear Z

pc.JointComponent#linearEquilibriumX
number
Spring equilibrium of linear X

pc.JointComponent#linearEquilibriumY
number
Spring equilibrium of linear Y

pc.JointComponent#linearEquilibriumZ
number
Spring equilibrium of linear Z

pc.JointComponent#linearLimitsX
pc.Vec2
The lower and upper linear limit for the X axis

pc.JointComponent#linearLimitsY
pc.Vec2
The lower and upper linear limit for the Y axis

pc.JointComponent#linearLimitsZ
pc.Vec2
The lower and upper linear limit for the Z axis

pc.JointComponent#linearMotionX
string
The allowed movement for linear X. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#linearMotionY
string
The allowed movement for linear Y. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#linearMotionZ
string
The allowed movement for linear Z. Can be "locked", "limited" or "free". Defaults to "locked".

pc.JointComponent#linearSpringX
boolean
Enables a spring motor for linear X

pc.JointComponent#linearSpringY
boolean
Enables a spring motor for linear Y

pc.JointComponent#linearSpringZ
boolean
Enables a spring motor for linear Z

pc.JointComponent#linearStiffnessX
number
Spring stiffness of linear X

pc.JointComponent#linearStiffnessY
number
Spring stiffness of linear Y

pc.JointComponent#linearStiffnessZ
number
Spring stiffness of linear Z

Code Example:
    entity.addComponent('joint', {
        angularLimitsX: new pc.Vec2(0, 0),
        angularLimitsY: new pc.Vec2(0, 0),
        angularLimitsZ: new pc.Vec2(0, 0),
        breakForce: 100,
        enableCollision: true,
        entityA: entityA,
        entityB: entityB,
        linearLimitsX: new pc.Vec2(0, 0),
        linearLimitsY: new pc.Vec2(0, 0),
        linearLimitsZ: new pc.Vec2(0, 0)
    });

Proposed Editor UI
The following is the proposed UI for the joint component in the Editor. It's prototyped below as a script component.

Note that the spring checkboxes should probably show/hide stiffness and equilibrium attributes of the corresponding DOF.
Open questions

At the moment, a joint component would live on its own entity, separate from entityA and entityB. But should a joint component be added to the same entity as entityA? This would mean the entityA property would be implicit. One benefit of that is that you'd require one fewer entity, so your hierarchy would be simpler. But then a system for offsetting/editing the position/orientation of the joint would be needed.

Should the joint expose presets for making it easier to configure simple, commonly needed joint types like a hinge?

Should this component leverage the other ammo.js constraint types for these presets like:

btPoint2PointConstraint
btHingeConstraint
btConeTwistConstraint

Or should everything be built using the btGeneric6DofConstraint API? Are the more specialized constraint types more stable and/or more performant? It would probably make the code bulkier to utilize the other ammo.js constraint classes.

Should limits be in pairs (so 3 pc.Vec2s for angular limits and 3 for linear)? Or should there be 2 `pc.Vec3's for lower and upper for angular and the same again for linear? Or should they be individual numbers? For now, I've made them pairs (one for each axis) because I think that's easier to visualize when configuring a joint.

Fixes #478
I confirm I have signed the Contributor License Agreement.

Not sure if you were looking for feedback here or on the forum post but a few points.

I think that having to explicitly define entity A and entity B is a more clear API, but maybe you can have both by having entity A default to the parent entity of the component if it's not defined? Not sure if this would be too tricky to implement / look weird in the editor.

Presets would be very nice

I think those should be exposed as there are specific scenarios where one is better than the other, for example in page 39 of the bullet manual it suggests that for ragdolls you should use a combination of btConeTwistConstraint and btHingeConstraint.

Personally pairs seems easier to reason about.

I think that having to explicitly define entity A and entity B is a more clear API, but maybe you can have both by having entity A default to the parent entity of the component if it's not defined? Not sure if this would be too tricky to implement / look weird in the editor.

Many constraint configurations can have only single body defined, that way constraint will be between world and body. Also, constraint entity, might have a spring model related to it, and it will be undesirable for that entity to be a child of one of related bodies.
Also it is best to avoid "magical" behaviours.

Presets would be very nice
+1. I think best would be if Engine as well as Editor would provide "type" for constraint, with more simple controls for simple ones, like ball joint, or hinge joint, and if developer needs - full on 6dof custom one.

At the moment, a joint component would live on its own entity, separate from entityA and entityB. But should a joint component be added to the same entity as entityA? This would mean the entityA property would be implicit. One benefit of that is that you'd require one fewer entity, so your hierarchy would be simpler. But then a system for offsetting/editing the position/orientation of the joint would be needed.

I think a separate entity per joint is probably best - it also may be clearer if a single rigid (or soft) body has many of joints/constraints?
+1 for presets - and ability to create custom 6 DOF joint - and regarding limits when using a preset, you would want to make specifying limits as intuitive as possible for each type of preset - e.g for btConeTwistConstraint cone direction and cone angle etc would be easier for the user?

I've done some more work on this PR. I've added spring support for each linear/angular axis. It's pretty cool. See tweet:
https://twitter.com/willeastcott/status/1373391145166897153

When looking over the introduced API with X, Y and Z, I felt exposing those as Vec3 would be nicer. And for the limits where the value is Vec2, I'd prefer Vec3 lower and Vec3 upper. It would also make the inspector more readable I think.

I'd be also great to create a new issue for the follow up work, so that a good comments from this PR are considered for later - like the different ammo constrain types.

When looking over the introduced API with X, Y and Z, I felt exposing those as Vec3 would be nicer. And for the limits where the value is Vec2, I'd prefer Vec3 lower and Vec3 upper. It would also make the inspector more readable I think.

Thanks for the review, @mvaligursky. So it's tricky. Because often, you just want to enable 1, or maybe 2, degrees of freedom. The current API lets you consider each DoF in turn. And imagine what the Editor UI would look like. For each DoF, there is a boolean to enable the spring. If that's unchecked (the default for each DoF), damping, stiffness, equilibrium can all be hidden. These properties need to be grouped together for each DoF if that's going to work well.

Because often, you just want to enable 1, or maybe 2, degrees of freedom

Hey now that makes sense .. I didn't realize that. I take back my suggestion then.

Some comments: Would using alternative naming help with understanding what each axis constrains? For example roll or twist for the Z axis and maybe pitch and yaw for Y and X axis. Also, although grouping limits into Vec2 in fine for the underlying implementation - expressing that the first value is the lower limit and second value is the upper limit could be useful in the naming in the API - at least in the editor inspector? Also, maybe beyond the scope of this PR, what are the plans for in-editor visualization of joint setup?

@raytranuk We don't use roll, pitch and yaw anywhere else in the API - and Bullet don't use those terms in their public API either.
In the Editor, we can have labels lower and upper in the Vec2 attribute in the UI. Unfortunately, we can't easily have different vector representations in the UI vs the runtime because the tooltip for the UI form should be the API equivalent.
For in-editor visualization, we will need a joint gizmo. Scary job, but yes, we'll need that at some point, once the runtime side is nailed down.

@raytranuk We don't use roll, pitch and yaw anywhere else in the API - and Bullet don't use those terms in their public API either.

It does make sense to stay consistent - so that knowledge gained from working with other places that use rotations in the engine will apply here - good tool tips in editor (and eventually good editor gizmos) will be helpful too.

In the Editor, we can have labels lower and upper in the Vec2 attribute in the UI. Unfortunately, we can't easily have different vector representations in the UI vs the runtime because the tooltip for the UI form should be the API equivalent.

It maybe worth considering exposing accessors for lower and upper limits to be set individually - if we feel users would find that useful - but it would mainly be a convenience.

For in-editor visualization, we will need a joint gizmo. Scary job, but yes, we'll need that at some point, once the runtime side is nailed down.

Agree.

Is this the recommended way of doing constraints today? I noticed it's not in the public API docs but is in the engine.
Alternatively, there are the constraint scripts written here: https://playcanvas.com/project/618829/overview/physics-constraints
For reference, I'm trying to build a ragdoll.

It is not recommended currently. A joint must be destroyed before any of the attached rigidbodies are destroyed. At the moment rigidbody component does not consider, if there is a constraint attached to it on body destruction, which will crash Ammo.

I have modified a fork of playcanvas [here] to implement multiple joint types using native bullet/ammo implementations (6DOF, spherical/cone-twist, hinge/revolute, slider/prismatic, and fixed). In addition, this version of playcanvas supports bullet multibody articulations. I do not have an example, though multibodies are supposed to be much more stable (than the current rigid bodies) for simulating articulations with many joints.


Add MIDI controller device index to InputEventMIDI.device property.

It is possible to query the OS for the connected MIDI controllers, but the event messages' device field was not being used. This implements controller index being sent in InputEventMIDI messages in the device property, matching the index from OS.get_connected_midi_inputs().
Based on the work done by @ramdor in this archived PR
Closes godotengine/godot-proposals#7733

The co-author didn't apply, you need to make the part in the arrow brackets their email, check out their branch and use git log to get a valid author to use 🙂

The co-author didn't apply, you need to make the part in the arrow brackets their email, check out their branch and use git log to get a valid author to use 🙂

Done. Seems to work now.

Your commit seems not to be linked to your GitHub account. See: Why are my commits linked to the wrong user? for more info.

Your commit seems not to be linked to your GitHub account. See: Why are my commits linked to the wrong user? for more info.

Fixed. (Apparently I'm as good with github as Sheldon is good with the flute. Eventually I'll get better.)

This needs to get pushed up.

hi @fbcosentino . I know this has been merged now, based on the changes I was dabbling with a long time ago. However, there are some issues with the coremidi implementation. I built a quick mac test and it seems like the device_index (InputEvent.device) is garbage data.
It looks to be caused by line 68 of midi_drive_coremidi.cpp where the pointer to 'i' is being used. This should not be a pointer, but the actual value of 'i'.  Otherwise multiple read callbacks will use the same pointer. Also 'i' will go out of scope and result in junk.
We need to provide the actual value of i to MIDIPortConnectSource so that when the callback function read is called when midi events come in, src_conn_ref_con is the actual value of i that was provided when MIDIPortConnectSource was called and can be used as device_index.
I hope this makes sense.  Cheers.

some test code that does correct type casting :
#include <iostream>
//#include <cstdint>

void testFunction(void *src_conn_ref_con)
{
    intptr_t device_index = reinterpret_cast<intptr_t>(src_conn_ref_con);
    std::cout << device_index << std::endl;
}

int main()
{
    int sources = 16;
    for (int i = 0; i < sources; i++) {
        testFunction(reinterpret_cast<void*>(static_cast<intptr_t>(i)));
    }
}

Hi @ramdor !
I actually don't have a mac (nor access to one). Would you be comfortable to make these changes yourself?


fix: allow connect() in dedicated method

Fixes #23
Think this needs more docs.

Thanks for the PR!

Hey, sorry for not getting back to you sooner.
So I think what remains for this PR are

Check that the examples where allow_connect was added actually require allow_connect
Add a test showing it working (i.e. blocking an http request without allow_connect and allowing one with it, or something similar)
Allow connect always inside allow_start_tcp_clients

I think it's also equally valid to do what you said in a comment and just allow connect for allow_start_unix and allow_start_udp sockets as well though. I don't see how it could be misused since you always need to be able to create the fd before connecting.

Sorry for the roundabout way we got to this change! Thanks for sticking with it.
Would you mind squashing everything down to 1 commit? Then I'll merge.

No problem!

Thanks again!


Update service.yaml

fixed port to deploy integration test in cloud

will merge PR to test if integration test will run on cloud


Needs tests

Shouldn't this have some tests? =)

Much better.
BTW, I've linked to this repo from my Essential JavaScript Links document.

Eric

Wow, thanks!


[Analytic] Insert analytic & feedback link to poc2

I found a privacy-first analytic tool. We can give a try
please insert the following code to the body:
Project ID : aN8DjCSj9oaz
swetrix doc:
https://docs.swetrix.com/install-script

there is noscript section seems doesnt show in the description

Similar to feedback button like we had on poc1 (https://poc1.channel4.wtf/) ?
feedback link in poc1 : https://airtable.com/shrGNTW2IFm2o0cKJ

ah yeah, let's add the feedback link to this poc 2,
I think Thomas has plan to capture feedback

@thebeyondr  can I simply put the code from docs in app folder as a component ?
OR
I can use this : https://github.com/Swetrix/swetrix-nextjs ?

won't be easier just to insert the

Best to use what's recommended so the app plays nicely: https://github.com/Swetrix/swetrix-nextjs

This can be closed now i think. Analytics are added. for feedback we can create separate issue.


Is hiding partials from the menu possible?

I have partials that I want to include, but not show up in the Fabricator menu. And also not as atoms, molecules, etc on the pages.
They are pure presentational (section, container wraps, repeating elements, etc to keep things dry). They are not part of what I want to feature, but help display them better.

Resolved!
Found several ways to do this here : https://github.com/fbrctr/fabricator/issues/230#issuecomment-181928049 I went for the one by  @jraeruhl


Report Error File

Create a new attribute named files and allow the reporting of mapdl specific files.  This should be done in the same approach as we use for the parameters and post_processing attributes. For example
mapdl.files.output_error_file()

This way we can capture the error file output when the server dies:
~/ansys/source/pymapdl/ansys/mapdl/core/errors.py in wrapper(*args, **kwargs)
    115             # Must close unfinished processes
    116             mapdl._close_process()
--> 117             raise MapdlExitedError('MAPDL server connection terminated') from None
    118
    119         if threading.current_thread().__class__.__name__ == '_MainThread':

MapdlExitedError: MAPDL server connection terminated

We need to report the server died and then include the entire error printout in the exception.  This will only work when MAPDL is local, but it's better than our current obscure error.

Hello, I would like to ask what is the problem with the application of the above method (sorry,I am a beginner)
Traceback (most recent call last):
File "D:\Python\lib\idlelib\run.py", line 559, in runcode
exec(code, self.locals)
File "C:\Users\abc\Desktop\1\R\新建文件夹\Main-with-uncertainty.py", line 73, in
mapdl.files.output_error_file()
AttributeError: 'MapdlGrpc' object has no attribute 'files'

Hi @donald-zero
It has not being implemented yet, hence you cannot use it :)

How do you intend it to use it?

Because when I run the program I always get
“MapdlExitedError: MAPDL server connection terminated”

Sorry, I meant, "why do you want to use it?". What kind of information are you looking for in the output file?

I want to know why my program is running with this error, find the reason and fix it. Also, thank you very much for your answer!


Bump starlette from 0.18.0 to 0.19.0

Set of breaking changes:

https://github.com/encode/starlette/pull/1435 (mypy)
https://github.com/encode/starlette/pull/1431

Starlette 0.19.0 is not released yet. Feel free to ignore this for now.

I need to update this PR. I'll do it today.

Still works for me, including the newly-ignored warning. Thanks!

Thanks for the work @Kludex! :rocket: :tada:
This is now available in FastAPI version 0.77.0 :bookmark:


python312Packages.tencentcloud-sdk-python: 3.0.1189 -> 3.0.1190

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 327605 run on x86_64-linux 1

4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


Add Communication and LightSensor Blocks

This PR adds a send message and receive_message block for mBot2.
This PR also adds a lightSensor option to the quadRGB block.

accepted with ffeaec36e93ecbf4399eaa178d47ced43feecb81 and 5d4e931a419f301f6f9b8b6a67078074be585ba2


fix-mongo-tests

Description
MongoGeoTemporalIndexIT and MongoGeoIndexerFilterIT had 5 tests failing between them.
Updated to extend MongoITBase.  Added unique mongoDBs for isolation.
Tests
MongoGeoTemporalIndexIT and MongoGeoIndexerFilterIT
Checklist

[ ] Code Review
[ ] Squash Commits

People To Reivew
@amihalik
@meiercaleb

asfbot build

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/396/Build result: FAILURE[...truncated 390.63 KB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 04:24 min[INFO] Finished at: 2017-08-15T20:43:20+00:00[INFO] Final Memory: 129M/3051M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (make-assembly) on project rya.pcj.fluo.app: Failed to create assembly: Error creating assembly archive jar-with-dependencies: Error finalizing component-set for archive. Reason: Permission denied -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.pcj.fluo.appchannel stoppedSetting status of b2303f7705304851d800f864cb0d46345dac827c to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/396/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

asfbot build

asfbot build

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/397/Build result: FAILURE[...truncated 390.30 KB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 04:38 min[INFO] Finished at: 2017-08-15T20:51:51+00:00[INFO] Final Memory: 128M/3239M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (make-assembly) on project rya.pcj.fluo.app: Failed to create assembly: Error creating assembly archive jar-with-dependencies: Error finalizing component-set for archive. Reason: Permission denied -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.pcj.fluo.appchannel stoppedSetting status of b2303f7705304851d800f864cb0d46345dac827c to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/397/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/398/Build result: FAILURE[...truncated 385.36 KB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 05:05 min[INFO] Finished at: 2017-08-15T20:56:45+00:00[INFO] Final Memory: 129M/3053M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (make-assembly) on project rya.pcj.fluo.app: Failed to create assembly: Error creating assembly archive jar-with-dependencies: Error finalizing component-set for archive. Reason: Permission denied -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.pcj.fluo.appchannel stoppedSetting status of b2303f7705304851d800f864cb0d46345dac827c to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/398/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

asfbot build

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/399/


Clarify doc comments of SegmentsIntersection::Point

Point-intersection only has only one intersection point, so the original doc comments "Location of the first intersection point on the first segment." and Location of the second intersection point on the second segment" are confusing. It seems like they were copied from the Segment-intersection where those descriptions make sense.

Thanks!


Laravel 5.1 support

@FarhadMohammadi and a few others have asked about Backpack working on Laravel 5.1.
I haven't actually given any thought to making it work on Laravel 5.1, since I believe the LTS tag is BS - I have projects with 5.1 bugs that still have not been fixed, though reported, but upgrading to Laravel 5.2 fixes them.
I guess the only difference to make it work on 5.1 would be Middleware Groups.
I personally have no need for Backpack to work on Laravel 5.1, so there's no immediate plan to support it, but if someone puts in the effort, I'm more than happy to help and merge it.

After much consideration, it would be very very difficult to support Laravel 5.1, 5.2 and 5.3. There just isn't enough time/manpower for that.
Since LTS is BS for Laravel, I think the best way here is to accept the fact that once Laravel releases a new version, we should upgrade.
P.S. I'll go ahead and close this issue so we don't clog the section. Feel free to open it again if you have follow-ups.


Sync all data more often, including account true.

Hoping to clean up some inconsistencies in mailchimp data.

Do you think we should sync ACCOUNT: FALSE when a user delete's their account?

@Justin-Holmes I wasn't sure about that... The user is unsubscribed from the list so they don't get included in queries. I think if they were to re-sign up they would be have it set to false at the first screen then true again if they completed sign up. shrug What do you think?

Oh I see. Yeah, I think we're totally fine then.


Enter button submits form unexpectedly

From https://reportedcab.slack.com/archives/C802R14UX/p1579035335051800?thread_ts=1578940577.050500&cid=C802R14UX:

I think the web app saved the field values from a previous report, and took my return key as a submission

Ooh yeah, it does save values under some circumstances (so that you don't lose everything if you accidentally close the page), but tries to clear them out after they're submitted. I'm guessing something went wrong with the clearing.
The enter button thing is just the default way that html forms work, but I should probably disable that it's not very intuitive here.

Looks like this has a decent explanation of how to fix it: https://dzello.com/blog/2017/02/19/demystifying-enter-key-submission-for-react-forms/

There's a similar issue on Android (likely iOS too) where editing the license plate field shows a magnifying glass button on the keyboard, and pressing that button submits the form. See here for context:

hey, I accidentally submitted a false report while investigating a webapp issue. I tried to delete it from the Parse DB, but it looks like the backend scripts got to it first. Can you delete this tweet? https://twitter.com/Reported_NYC/status/1572202770949627906

Not sure if there's anything we can do about 311/NYPD submissions, though

For context, I noticed that the webapp license plate  element causes Android to render a magnifying glass button on my keyboard (because the type attributes is set to search) so I tried clicking it, without realizing that it would actually submit the

I briefly tried to see if I could prevent the form from submitting that way, but didn't find anything. I'll have to keep looking


🐛 BUG: wrangler dev fails with Error: No API token found instead of starting an oauth sequence

What version of Wrangler are you using?
2.1.15
What operating system are you using?
Mac
Describe the Bug
$ wrangler logout
$ wrangler dev
 ⛅ wrangler 2.1.15
--------------------

✘ [ERROR] Error while creating remote dev session: Error: No API token found.

However if I call wrangler publish I trigger the auth flow as expected:
 $ wrangler logout
 $ wrangler publish
 ⛅ wrangler 2.1.15
--------------------

Attempting to login via OAuth...
Opening a link in your default browser: https://dash.cloudflare.com/oauth....

any new ?


Add Clever Cloud's components in faq/component-libraries

Hey, I propose an entry in the faq/component-libraries for the components we built at Clever Cloud :wink:

 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.

thxxxx 🤗


The accursed glyph alignment bug rears its ugly head

Having never written a text renderer, I have no idea why these are so weirdly common, but the w is one pixel lower than it should be. This appears to be the case with any lowercase w in the default font. I haven't caught it happening with any other letters, including capital W.

Usually when I see this it's because I'm trying to draw text at fractional coordinates, but not in this case. I also looked at the vertex buffer itself and it doesn't appear that there are any off-by-ones in the quads for any of the glyphs, which makes me think the font_get_uvs() texture coordinates might be wrong under certain conditions.
test - scribble jr.zip

tyvm will take a look soon

That project doesn't reproduce the issue for me. So that's a thing.

oh exciting. usually when that happens it's because of some GPU-specific nonsense (nvidia here). what GPU are you running on?

GTX 1070

that's pretty similar to mine (1060), wouldn't expect that to cause any differences. wait for someone else to come by with the problem, i suppose?

Yep!

I decided to check out the test - scribble jr.zip myself, and well it looks like I'm getting the same issue.
GPU: GTX 1080
Driver version: 546.17 (November/14/2023)

Also happening for me

Think I've identified the issue: there's some loss of accuracy in texture UVs which is causing the texture to be slightly misaligned. I think I have a fixed now and I'm working on porting that solution over. I further believe this issue to affect all vertex buffer bakers, not formatting-enabled versions.

https://github.com/JujuAdams/ScribbleJunior/commit/b3d80bbcd5e08fb6c77cca03fb2f4d2f9a730479


Offer Link wrapper component in TSX

The styled and wrapped version of the Next.js Linkcomponent provided by the Material UI next-js template/example is not 100% usable in TypeScript projects because IntelliSense does not work with the current JavaScript version of the component. For example, there are no suggestions available for its props.
I converted the JS version to TSX partially. It is usable and IntelliSense works in VS-Code. I am missing just one more type, as far as I can tell. I've noted it with a TODO comment in this code gist.

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

Summary 💡

The Link component should be usable in other TSX components and provide IntelliSense in editors like VS-Code.
Examples 🌈

Motivation 🔦

I, like many others, prefer TypeScript over JavaScript and this is the only official starter template for Next.js + Material UI, but it is only JS-oriented. At the moment, the Next.js template only contains a few demo components which will be deleted anyway, but the Link component is usable. It would be great if there was a TSX version of it as well.

@brokenthorn I'm not sure to follow. Are you reporting an issue with https://github.com/mui-org/material-ui/blob/next/examples/nextjs-with-typescript/src/Link.tsx?

I think that we can aim to link all the examples in https://next.material-ui.com/getting-started/example-projects/#official-examples, so do:
diff --git a/docs/src/pages/getting-started/example-projects/example-projects.md b/docs/src/pages/getting-started/example-projects/example-projects.md
index aba703ac5c..23d9424374 100644
--- a/docs/src/pages/getting-started/example-projects/example-projects.md
+++ b/docs/src/pages/getting-started/example-projects/example-projects.md
@@ -13,7 +13,6 @@ You can find some example projects in the [GitHub repository](https://github.com
 - [CDN](https://github.com/mui-org/material-ui/tree/next/examples/cdn)
 - [Plain server-side](https://github.com/mui-org/material-ui/tree/next/examples/ssr)
 - [Use styled-components as style engine](https://github.com/mui-org/material-ui/tree/next/examples/create-react-app-with-styled-components-engine)
-- And more

 Create React App is an awesome project for learning React.
 Have a look at [the alternatives available](https://github.com/facebook/create-react-app/blob/master/README.md#popular-alternatives) to see which project best fits your needs.

@brokenthorn do you want to solve that?

@oliviertassinari, I can take this issue if @brokenthorn is not looking into it.

@brokenthorn I'm not sure to follow. Are you reporting an issue with?
https://github.com/mui-org/material-ui/blob/814fb60bbd8e500517b2307b6a297a638838ca89/examples/nextjs-with-typescript/src/Link.tsx#L37-L39

Sorry I'm late. I had other pressing projects keeping me busy (and tired).
Yes, that is what I was referring to. The nextjs-with-typescript example had/has a custom Link component that wraps Next.js's Link component, and that custom component was unusable in TS projects. The gist I gave tried to fix that.
Anyway I'm still busy on another project so it will be a while until I get back to this. This stemmed from a personal project which is now on hold.


Create a Paginator that can also use images

Make a new PaginatorImage class which can also send images in each page.

py-cord now has it's own pagination module. I won't be implementing this.


Ad hoc email support

@dospromptman - I was talking with my friend Skye Tyler about flows and she mentioned using Screen Flow and the Data Fetcher to do maybe solve address this email scenario.  Since with Data Fetcher we could capture all the contacts into a collection for the recipient list and use screenflow to write the message, pull in some standard items like activity name, shift time, etc. and then use Send Email Action to send it.
anyways wanted to share - definitely not as fancy as what you've built with the UI, but I wonder if it could help by-pass some of the limitations.  Here's her presentation deck on Data Fetcher from CzechDreamin and she's presenting at MidWest Dreamin on this next week.  I know the deck doesn't have the demo, but it does have some linked resources and I can reach out to her if you think it would be worth exploring to see if she can share access to her demo org or do a walk through with you.


This add the possibility to define minimum and maximum for Duration

With the help of some crate like serde_with, it is possible to serialize and deserialize Duration.
With modification serde_valid is able to define minimum and maximum for this type.
To define such minimum, we use the attribute validate with the parameter minimum_duration like this
#[validate(minimum_duration="10ms")], "10ms" is transformed into Duration::from_millis(10).
We can also use s and ns prefix

@yassun7010
Is this something achievable with the current implementation of custom, after a brief search I think not but you know better than me.
May be I could try to implement something like #[validate(not_json_schema(minimum_duration("10ms")))], with such things, the custom attribute will remain a tool for the user to implement custom function. And we will have a dedicated attribute to implement, inside the library, validation that are not in json

@yassun7010 @StivenAigleIxxi
I think the not_json_schema is irrelevant in a crate above Serde (that can (de)serialize something other than JSON).

@StivenAigleIxxi @B14ck6u4rd
I've written my idea in https://github.com/yassun7010/serde_valid/pull/63;
What do you think?
The way of the limitation is redundant. But, the resolution by custom maintains the position of this crate (based on JsonSchema).
My concern is that the JsonSchema specification will support equivalent validations in the future under different names.

@StivenAigleIxxi @B14ck6u4rd
I've written my idea in #63;
Does the method using custom meet your requirements?
The way of the limitation is redundant. But, the resolution by custom maintains the position of this crate (based on JsonSchema).
My concern is that the JsonSchema specification will support equivalent validations in the future under different names.

I very like your solution @yassun7010 !

I released v0.20.0

Thanks for your work @yassun7010 !


Fix reference link expansion

fixes: #105
TL;DR had an extra | in the regex when there shouldn't have been 🤦♂
/cc @vishakhanihore

/lgtm
Looks Great !!


Allow plugins to contribute multiple tab responses

Describe the problem/challenge you have
Octant is great and the extensions API allows me to add a single new tabs for the specified Kubernetes object. For example, in Starboard plugin we add the Vulnerabilities, which contains vulnerability reports for the given workload containers.

Describe the solution you'd like
Starboard also checks deployment descriptors for insecure configurations and we'd like to add another tab, next to the Vulnerabilities tab, which contains config audit report and is called Configuration Audit.
Anything else you would like to add:

We could always add a single generic tab called maybe Starboard, which contains tabbed pane inside, but this hides the intention of the tab or UI component contributed by the plugin.
Support for multiple top level tabs will allow users to spot new items they can click and experiment with.
It would be nice to have it in Go and Typescript APIs as we haven't migrated to Typescript yet

Environment:

Octant version (use octant version): 0.16.0
Kubernetes version (use kubectl version): any
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): any

This is going to be a breaking API change if the tab response is to return a list of tabs. Another aspect to start considering is tab order across one or more plugins.


apacheHttpd: 2.4.52 -> 2.4.53

Description of changes
https://downloads.apache.org/httpd/CHANGES_2.4.53
The configure failed to find a working pcre-config, so I decided to try
out pcre2 instead, which resulted in the same problem. Putting it into
PATH during preConfigure worked, but it isn't a great workaround.
Migrating to pcre2 was recommended in the release notes, since pcre 8.x
is over 20 years old and has now reached its end of life.
Fixes: CVE-2022-23943, CVE-2022-22721, CVE-2022-22720, CVE-2022-22719

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval


⚠ Jenkins Plugins Artifactory has degraded performance

In b9431a4, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1224 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 093beba after 12 minutes.


⚠ gorzdrav.org has degraded performance

In 5828586, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 4221 ms

Resolved: gorzdrav.org performance has improved in ab7312c.


Added host locale provider

Codecov Report

Merging #486 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #486   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          53     54    +1
  Lines        1642   1657   +15
  Branches      241    248    +7
=====================================
+ Hits         1642   1657   +15

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <100%> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

lib/sky-pages-module-generator.js
100% <ø> (ø)
:arrow_up:

runtime/i18n/host-locale-provider.ts
100% <100%> (ø)

Continue to review full report at Codecov.

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


Bug: Performance issue : Urgent: Performance Issues with Saleor Core App Deployment

What are you trying to achieve?
I hope this message finds you well. We are currently experiencing performance issues with the Saleor Core app deployed inside an EC2 instance using Docker containers. Some API requests are processing with significantly lower latency than others, and we are seeking your assistance to identify and resolve these discrepancies.
Despite monitoring the system, we have observed that the CPU and memory utilization do not seem to align with the latency issues we are encountering. We have attached a screenshot for your reference to provide additional information.
Key Details:
SDK Version:
"@apollo/client": "^3.9.2"
"graphql": "^16.8.1"
Issue Description:
Inconsistent latency with API requests.
CPU and memory utilization appear normal, but certain requests are taking longer than expected.
Attached screenshot for further insights.
Requested Assistance:
We kindly request your support in identifying the root cause of the latency discrepancies and optimizing the performance of our Saleor Core app. As this issue is affecting the user experience, we consider it urgent and appreciate your prompt attention to this matter.
Attached Screenshot:
[Attach screenshot here]
Thank you for your immediate attention to this matter. We are eager to work collaboratively with you to resolve these performance issues and ensure the seamless operation of our Saleor Core app.
Steps to reproduce the problem
Install the mobile app and run the application.

What did you expect to happen?
I want to achive all the api's should be respond in less then 1 sec.
Logs
No response
Environment
Saleor version: 3.18.3

OS and version: DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Thank you for your report @Ramesh534. We have made a lot of inprovements to Saleor's performance in 3.20, feel free to test the newest version and reopen if this still happens 🙌


Always generate the JSON doc when running the rake task

I'm super enthusiastic about the potential for folks to build things on
top of the JSON output, we've had several related conversations at
Config Management Camp and on puppet-dev recently. I think this is a
sane default, and calling the file strings.json seems a nice
reinforcement.

Maybe we need to parse command line arguments in the rake task so we can control this easily when running from a CI (jenkins) server.

@vStone I think this being configurable is a good idea, but I also think this is a better default until such a time as things are configurable. I don't at least see a downside of also outputting this file (locally or in a CI system) that can't be avoided by .gitignore or similar, but might be missing something.

I missed this - is there a ticket for this?

@hlindberg not that I created or am aware of. Happy to open one to discuss there if preferable.

@garethr Please do file a ticket. Tickets and discussions are far more visible and helps with priorities.

@hlindberg done, opened https://tickets.puppetlabs.com/browse/PDOC-70

thanks @garethr

@garethr Sorry to be pedantic, but could you also update the commit to reference the ticket? :)

@HAIL9000 no problem. Done.

@garethr As per the discussion on the Jira ticket, could you quickly add a few sentences in the Rake Tasks section of the README explaining that a .json file will be generated?

I'm gonna go ahead and merge this one, then I'll open another pull request to update the README before we release 0.4.0


My bugs and some translation issues

Tested on the Chrome extension
General Fixes:
•	Currency Alternative should put ~5 most used currencies (USD, EUR etc) at the top
•	When scanning a QR-Code adress in the send menu it should directly paste the adress into the send
•	Scrolling down in the transaction log stutters at the end
•	The search feature in the transaction log should be explained, it’s not clear what exactly you can and can not search for
•	Not chosing a backup warning shows BitPay (this was on the android app)
German translations
Not translated:
•	Settings -> Wallet -> Advanced -> Wallet Adresses: Explanation string not translated
•	Receive: Request specific amount string not translated
•	Receive: Generate new adress not translated
•	Send: Search or enter NavCoin adress not translated
•	Send: Private Payment -> Private Transaktion
•	Settings -> Wallet -> Advanced -> Wallet Service URL: Explanation string not translated
•	Home -> Recent Transactions -> Transaction -> Fee: x % of the transaction should be x% der Transaktion
•	Home -> Recent Transactions -> Transaction -> Fee -> View on blockchain: Title of popup window not translated, open cryptoID not translated
Not ideal:
•	Personal Wallet should be Translated as Persönliche Wallet not Persönliches Wallet
•	Settings -> Wallet -> Guthaben Verstecken should be Guthaben verstecken (lowercase v)
•	Settings -> Wallet -> Sicherung should stay Backup, Sicherung usually means fuse box
•	Settings -> Wallet -> Berechtigungscode abfragen should be Passwort or Passphrase
•	Settings -> Wallet -> Advance -> Public key should stay public key
•	Settings -> Advanced -> Unbestätigte Mittel einsetzen should be Unbestätigtes Guthaben einsetzen, Vermögen in the explanation text should also be changed to Guthaben
•	Settings -> Advanced -> Kürzlich Ausgeführte Transaktionen Karte makes no sense at all, should either be Kürzliche Transaktionen anzeigen or „Kürzliche Transaktionen“-Widget anzeigen
•	Settings -> Advanced -> Nächste Schritte Karte Anzeigen should be Tutorials anzeigen or Tutorials-Widget anzeigen
•	Home -> Recent Transactions -> Keine aktuellen Transaktionen should be keine kürzlichen Transaktionen

•	Currency Alternative should put ~5 most used currencies (USD, EUR etc) at the top
Feature request #41
•	When scanning a QR-Code adress in the send menu it should directly paste the adress into the send
Duplicate #36
•	Scrolling down in the transaction log stutters at the end
Can you please provide more info on #42
•	The search feature in the transaction log should be explained, it’s not clear what exactly you can and can not search for
•	Not chosing a backup warning shows BitPay (this was on the android app)
#43

I have added the translation issues to #61 . Going to close this ticket as we've split all the parts out into other tickets


fix test name for diurnal cycle e3sm-diags run

This PR fixes an issue that diurnal cycle in e3sm-diags runs won't run. i.e. ""OSError: No file found for 20210603.v2rc3c.piControl.naRRM and JJA in climo_atm_monthly_diurnal_8xdaily_180x360_aave"" where 20210603.v2rc3c.piControl.naRRM is a user specified short_name, but test_name should be used to search for required diurnal cycle climatology files.

@forsyth2 this should fix the diurnal cycle in RRM run. In the piControl run, short name = case name, so there was not an issue.


Launch Java application support

Match VSCode Java support by supporting java application launching from Atom

Launch and debug are going to be treated the same and can only be done once atom-ide-ui's debugger lands.  Will track on #72


Scrolling issues (Opera GX)

The script works fine but there are some annoying things. Both of my issues come from scrolling.
The first issue is that there is a random horizontal scroll bar. When I am in theater mode it does nothing. When I am in fullscreen you can scroll right to another scroll bar?? (I saw that having a scroll bar in fullscreen was another issue)

I'd assume this is just because of how the script works but it's still kinda annoying.
The other issue has already been touched on but sometimes scrolling locks when I enter a page. Whenever I reload it just works fine but it's still annoying.
Other than that it works fine, thank you to all who has helped with this :D

The horizontal bar randomly disappeared??? It's literally just gone now lol idk what happened. I'll just close it now ig

(closed because the other issues are in other posts)


Nonsense predictions after training

Hello, everybody,
I'm working on reproducing some of the paper results before starting to play with the code/parameters. However, when running main.lua with default parameters I'm still getting nonsense predictions even after training is finished. Please see the example below.
Am I missing something?
Best regards,
Waldir
$ th main.lua -gpuidx 1 -target_length 6 -target_nesting 3
After a few hours:
Some exemplary predictions for the Test dataset
Input: f=816435;
c=7325;
print((c-(f-(765000+576123))))
Target: 532013.
Prediction: (tt +..
-----------------------------
Input: a=(835459*4)
for x in range(14):a-=518673
f=739545;
print((f-a))
Target: 4659131.
Prediction: njef;117
-----------------------------
Input: d=741596;
print(((d+958900)*10))
Target: 17004960.
Prediction: +1.stfsn+
-----------------------------

epoch=136, Training acc.=3.28%, Validation acc.=3.72%, Test acc.=2.99%, current length=6, current nesting=3, characters per sec.=14168, learning rate=0.001 Training is over.

Just for the record, the problem was solved when I went back to commit "6a3a94f...". This probably means some of the pull requests broke the code.


Chaning the name of server in deploy option if target is Azure

If project target is Azure, adding the name "SQL Server Azure" to all the titles and messages

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

22 of 41 (53.66%)  changed or added relevant lines in 6 files are covered.
113 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 42.357%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/controllers/projectController.ts
0
2
0.0%

extensions/sql-database-projects/src/dialogs/deployDatabaseQuickpick.ts
0
3
0.0%

extensions/sql-database-projects/src/dialogs/utils.ts
1
5
20.0%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
7
28.57%

extensions/sql-database-projects/src/dialogs/publishDatabaseQuickpick.ts
2
7
28.57%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/dialogs/utils.ts
1
41.67%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
112
19.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
27452

Relevant Lines:
60595

💛  - Coveralls


remove limit order from liquidity

This PR removes LimitOrder from the Liquidity enum. This was done as a first step towards refactoring to make it easier to add new liquidity such that:

Liquidity type will eventually be all the baseline liquidity that we fetch. This will hopefully allow us to simplify the whole solver liquidity vs API liquidity issue and make it easier to compute baseline solutions in the orderbook API for bad token detection, etc.
We were grouping limit orders and AMM liquidity only to split it back up again in every solver: ([LimitOrder], [Amms]) -> Liquidity -> ([LimitOrder], [Amms])
If we add actual AMM limit orders in the future (such as 0x orders) then we would need to distinguish them between the user orders.

Test Plan
Mostly refactored for new split, should be caught by existing CI.

Codecov Report

:exclamation: No coverage uploaded for pull request base (solver-batch-interface@ca7da8d). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             solver-batch-interface    #1068   +/-   ##
=========================================================
  Coverage                          ?   64.23%
=========================================================
  Files                             ?      123
  Lines                             ?    24012
  Branches                          ?        0
=========================================================
  Hits                              ?    15425
  Misses                            ?     8587
  Partials                          ?        0


fix(plugins): Fix SplitChunksPlugin cacheGroup priority option

priority option should belong to cacheGroups.{cacheGroup}, should not belong to cacheGroups

@butsalt please sign CLA

@EugeneHlushko Weird, I have signed CLA yesterday.

Or please try 'Recheck PRS'.

IIRC there was one more issue earlier, can we try reopening this PR?

So what else I can do? :)

Thanks!


MAINT: Return nan from daily bcolz get_value.

Match the behavior of the minute bar reader, now that the session and
minute bar readers share a common interface.
isnull is slightly slower than checking against -1; however, n cases
where we check against illiquid trades in a tight loop, volume is
checked which is not using nan. The change here should be marginal with
regards to performance.

This should take care of https://github.com/quantopian/qexec/issues/11328.

Coverage decreased (-0.004%) to 86.962% when pulling 098d38ac76ac3d9199699ecc6591f7a82af48eed on return-nan-from-bcolz-daily-reader into 0c81ee4af6cfc46eb01fb92936a93da0cecbeac9 on master.


Accessibility requirements for fides-js

Is your feature request related to a specific problem?
We need to make sure our fides-js components are as accessible as possible!
Describe the solution you'd like
Here's a running checklist of things we need to do. I'm not 100% sure if these are strictly requirements are suggestions, so we should do our due diligence with reading the standards, but for now I'm going to drop everything I see.
These don't include standard a11y things, like high contrast text and heading logic, as those things can typically be caught by automated tools (https://github.com/ethyca/fides/issues/3306)
Banner

[x] Banner should be the first focusable element in the page, before skip link and website's nav (so that visitors interact with the banner before anything else)
[x] Banner buttons must be of type <button>
[ ] When banner closes, we should not be able to tab through it

Modals

[ ] Trap focus inside the modal (cannot tab outside the modal)
[ ] Modal size should allow text to be readable at all screen sizes
[ ] Initial focus should be set within the modal (often to the first focusable element)
[ ] Closing a modal (either through confirmation or closing) returns focus to the last focused item on the main screen
[ ] ESC closes the dialog
[ ] Can Tab + Shift Tab through the modal
[ ] Strongly recommended to include a close icon or button
If the modal is meant to operate such that users cannot interact with anything outside of the modal and dims the background:

[x] Element that serves as the dialog container has a role of dialog
[x] All elements required to operate the dialog are descendants of the element that has role dialog
[x] Dialog container element has aria-modal set to true

[ ] The dialog has either

A value set for the `aria-labelledby property that refers to a visible dialog title
A label specified by aria-label

Toggles

[x] SPACE changes the state of the switch
[x] Switch has the role switch
[x] Switch has an accessible label by one of the following:

Visible text content contained within the element with role switch.
A visible label referenced by the value of aria-labelledby set on the element with role switch.
aria-label set on the element with role switch.

[x] When on, the switch element has state aria-checked set to true.
[x] When off, the switch element has state aria-checked set to false.
[x] If the switch element is an HTML input[type="checkbox"], it uses the HTML checked attribute instead of the aria-checked property.

Disclosures (accordions)

[x] The element that shows/hides the content has role button
[x] When the content is visible, the element with the button role has aria-expanded set to true. When the area is hidden, it's false
[x] Optionally, the element with role button has a value specified for aria-controls that refers to the element that contains all the content that is shown or hidden.
[x] When disclosure control has focus, ENTER and SPACE activate the visibility

Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Resources:

https://www.smashingmagazine.com/2023/04/potentially-dangerous-non-accessibility-cookie-notices/
https://www.youtube.com/watch?v=Uaqo4FOI_DY
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/dialog/
https://www.w3.org/WAI/ARIA/apg/patterns/switch/
https://quentin-bellanger.com/blog/accessible-cookies-banner/
https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/

The modal is going to be tricky—I think we should use a 3rd party lib or else we'll probably mess something up. I'd like to use this one as it is tiny but I haven't been able to get rollup to play well with importing a React package.
Without any intervention, when I try to use the package, rollup gives the error
[!] RollupError: "A11yDialog" is not exported by "../node_modules/react-a11y-dialog/dist/index.js", imported by "src/components/ConsentModal.tsx".
https://rollupjs.org/troubleshooting/#error-name-is-not-exported-by-module
src/components/ConsentModal.tsx (3:9)

This is solved by using commonjs, but commonjs also inflates the bundle size a lot! (the package is only 2.7kb, yet the size increases by around 14kb!!)
npm run build

><EMAIL_ADDRESS>build
> NODE_ENV=production rollup -c

src/fides.ts → dist/fides.js...
❌ ERROR: fides.js build failed! Gzipped size (24.06 KB) exceeded maximum size (20 KB)! If you must, update GZIP_SIZE_* constants in clients/fides-js/rollup.config.mjs
npm ERR! Lifecycle script `build` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace<EMAIL_ADDRESS>npm ERR!   at location: /Users/aking/workspace/ethyca/fides/clients/fides-js

I tried various parameters passed into both commonjs and node-resolve, but haven't had much luck.
These articles explain why commonjs causes larger bundle sizes: https://blog.logrocket.com/does-my-bundle-look-big-in-this/ https://web.dev/commonjs-larger-bundles/ but I haven't quite figured out how to get around it yet.

Documenting that Neville did some investigating around bundle size, below:
After some bundle optimization, the impact of this library is now adding ~8.6K to the gzip size, which is still a lot. We're unlikely to optimize that further since it comes from requiring the Preact compat code to import React modules
We have a few options to proceed:

Investigate other optimizations to see what I missed
Optimize our other code to make room in the bundle
Look for Preact modal libraries instead, which wouldn't require the compat import
Implement the a11y features ourselves
Finish other work first, then investigate options 1-4

For now we'll go with option 5

moving to done


Adds spo customaction add command

Adds customaction add to the commands list should solve #18
spo customaction add validation and help refactoring
Adds unit tests for the base permissions class
Renames the command from set to add
Removes command set
Adds all the unit tests
Adds customaction add docs
unused file removed

Coverage remained the same at 100.0% when pulling 3eb54dcf2c20c610095b3f4862d8eee272d231fa on VelinGeorgiev:customaction-add into 38ad176f7450e692b910f4ecae2401eeace14b28 on SharePoint:dev.

Coverage remained the same at 100.0% when pulling e8961b0e51d02316f8833be18d048e074a83bbac on VelinGeorgiev:customaction-add into 38ad176f7450e692b910f4ecae2401eeace14b28 on SharePoint:dev.

Coverage remained the same at 100.0% when pulling 05f2f11995f6d43036ff1feba5826081f63e651c on VelinGeorgiev:customaction-add into 38ad176f7450e692b910f4ecae2401eeace14b28 on SharePoint:dev.

Merged manually


Add eqMac2 to Music

System-wide Audio Equalizer

This repo is of apps I use and like. Will take a look at eqMac2 though. Thank you.


git_ignore/template/*.gitignore not included in build

Trying to fix.
Current workaround:
git clone https://github.com/hanpannet/Git-ignore.git
cd Git-ignore
pip install -e .

Fixed.


add tests vo4 #181

Closes #181

Codecov Report

Merging #182 (43c1cd0) into main (5f3f3a5) will increase coverage by 1.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #182      +/-   ##
==========================================
+ Coverage   86.65%   87.71%   +1.05%
==========================================
  Files          49       49
  Lines        1994     1994
==========================================
+ Hits         1728     1749      +21
+ Misses        235      213      -22
- Partials       31       32       +1

Impacted Files
Coverage Δ

client.go
33.15% <ø> (ø)

oauth2.go
88.00% <100.00%> (+84.00%)
:arrow_up:

Continue to review full report at Codecov.

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


docs clarification

In the documentation, you provide short examples on how to encrypt and decrypt some data. My question is: in Entity.create("entity_id")); what exactly is the entity_id?
I assume that string must a be a secret key? In other words, am I right in thinking that if you steal somebody's encrypted content and guess this string, you will b able to decrypt the message? If that is the case, I believe the "entity_id" string should be renamed something that conveys the importance of keeping this string secret.
Thanks

The secret value is the key, provided by the KeyChain implementation.
That's what's used for encryption and for hashing content.
Entity id is a ok-to-be-public value that represents the identity of that file. It's used to check integrity.
Let's say we encrypt two files F1 and F2. An attacker doesn't have access to the key. What could the attacker do?

change encrypted content to produce another intended plain content: they lack the key (from key chain) to use it
change encrypted content to produce some random intended plain content: they could do that, but there's an extra step on encryption for integrity check (to know it wasn't touched). That step generates a tail tag (or integrity tag) from (key, the IV [a random value used only once when encrypting], and the entity). It's guaranteed by algorithm properties (AES/GCM) that an attacker cannot produce a modified encrypted content and find the corresponding integrity tag for the changed content.
swap two valid files: let's say an attacker renames our two files: F1 -> F2, and F2 -> F1. All the integrity checks would pass. If we want to avoid this we need to link somehow the entity id to that. For example, entity id can be the file name. In that case if we try to decrypt F1 we will say it's entity = F1, therefore, if the file has been swapped it will fail integrity check and we will detect this case.

Summarizing: the entity is used to identify the content in a unique way among your different files/contents. It's ok for it to be public as the secret used to encrypt is the key. And the general health of the encryption is guarded by the secret key and the only-used-once IV value, generated for each call to a new encryption. [See AES/GCM documentation for more insight on how that works]

i find that the entity is useless , i use different value in input and output , but it still work well , there is no error.


preg_match(): Compilation failed: regular expression is too large at offset 156184

This happens while using<EMAIL_ADDRESS>because hostname/Biz.php contains enormous regular expression
Trace looks like this:
preg_match('/^[\x{002d}0-9a-z\x{3447}\x{3473}\x{359..(156088 chars skipped)..9FA0}\x{9FA2}\x{9FA4}\x{9FA5}]{1,20}$/iu','tapi4457@hsoqvf')
/vendor/zendframework/zend-validator/src/Hostname.php:1877
PHP Version 7.1.7

Originally posted by @ac-dc at https://github.com/zendframework/zend-validator/issues/219

I can't reproduce the compilation error with latest laminas-validator:
➜  laminas-validator git:(master) php -a
Interactive shell

php > include 'vendor/autoload.php';

php > var_dump((new Laminas\Validator\Hostname())->isValid('tapi4457@hsoqvf.biz'));
php shell code:1:
bool(false)

I'm closing it.

That’s strange, the same test on my machine leads to the warning mentioned above:
php > include 'vendor/autoload.php';
php > var_dump((new Laminas\Validator\Hostname())->isValid('tapi4457@hsoqvf.biz'));
PHP Warning:  preg_match(): Compilation failed: regular expression is too large at offset 156184 in /home/apidev/current/vendor/laminas/laminas-validator/src/Hostname.php on line 2104
bool(false)

"name": "laminas/laminas-validator", "version": "2.13.4",
PHP Version:
PHP 7.4.7 (cli) (built: Jun 12 2020 07:48:26) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.7, Copyright (c), by Zend Technologies

ok, reopen it.

@Thaix @samsonasik this issue might be depended on the pcre limits
Could you both please post the results of your php configuration here:
php -i | grep pcre | grep imit
pcre.backtrack_limit => 1000000 => 1000000
pcre.recursion_limit => 100000 => 100000

It seems the compilation error too larget because of big regex at  https://github.com/laminas/laminas-validator/blob/96529e873a6eaca7edf097c5130414e9ff7ec3ea/src/Hostname/Biz.php#L25-L2901

Verified as well. Defaults for both INI values are 100000, as it turns out. I tried bumping each to 1000000, and still hit the limits.
We're either going to need a separate validation for .biz domains, or have somebody with good PCRE knowledge audit and simplify our regex.

For quick fix, probably just check if string has "@" character...

I created PR https://github.com/laminas/laminas-validator/pull/67 for possible fix by handle if hostname has @ character


futures::sync::mpsc::UnboundedSender::send conflicts with Sink::send

And it has a different signature and semantics. I wrote this PR to tokio-proto to call it explicitly:
https://github.com/tokio-rs/tokio-proto/pull/117
Can we rename it so that there is no conflict? Ideas for names:
send_unbounded() pretty explicit, and clear where the method is coming from
send_now() reflects the fact that it will complete immediately

Thanks for the report! I think this is tracked in https://github.com/alexcrichton/futures-rs/issues/261, so I'm going to close in favor of that

Oops, didn't notice. Sweet.


[TC-WNCV-5.1] - Script should be updated by removing the PICS for 1a  PICS: WNCV.C.Afffc

From chip-test-scripts created by Rajashreekalmane: CHIP-Specifications/chip-test-scripts#688
Description  :
[TC-WNCV-5.1] - Script should be updated by removing the PICS for 1a  (PICS: WNCV.C.Afffc) Due to the PICS ( {PICS_CA_FEATUREMAP}.Read)) at 1a, Test-step is skipping in UI .
PFA UI Screenshot :

PFA Test-Plan screenshot :

PFA script screenshot :

Additional Information :
Version: TH Fall2023
Sha: 3f84bff5
Test-Plan updated : https://github.com/CHIP-Specifications/chip-test-plans/pull/3464

@Rajashreekalmane fixed in PR 29727 please verify it and close the ticket.

Issue resolved in latest image


This project is fucked!

 It's a sad joke...