Support for Host Records?

There is no support at the moment for host records
New-IBHostRecord / Get-IBHostRecord / Set-IBHostRecord?

no, haven't gotten around to that one yet, but definitely on the list of to-dos.

Well I only did classes once and I am an ops guy from origin not a dev guy, but will give it a go if i get around to it ;)

heh, me too man, this dev stuff is all new to me.  The trick with host records as I understand it is they contain other records as child objects, so like the A and cname and all that.  Hopefully with all those classes already defined it shouldn't be too difficult to reference them all in the host class definition.
I've sort of been doing the feature branch method of organization here, where I'll branch master for whatever new feature I'm adding, then once that's done and manually tested I'll merge it back to master to kick off the appveyor build and publish to the gallery.  Not sure how that works with multiple people working on it, I assume I'd make the branch then you could do pull requests against that?


cmd/main.go: remove unnecessary blank line

Just nits. Thanks!

Coverage remained the same at 23.943% when pulling bcbeec82a0e08a6915a7fa60aaa5ea72ea00ec78 on gyuho:minor-format into 734cbf1574222fced2fb38c486713d2c2dd693c5 on kubernetes-sigs:master.

Probably good to get another PR with you in OWNERS :+1:


Rescue Nearby functionality missing

Subject of the issue
If I have excess food/water/cloth, I should be able to geo-locate requests from places nearby for specific resources and be able to provide them the same easily.
Your environment

version of your python
which browser and its version
OS Type (iOS/Android/Linux/Windows)

Steps to reproduce
It is a feature request
Expected behaviour
I should have an endpoint that shows my location and nearby requests for help
Actual behaviour
No such behavior

will be added support via #20


Horizontal-form layout breaks when label is too long

Don't know how to fix, just reporting.
http://plnkr.co/edit/zRqA9CkrmP8A1rlYjviY?p=preview

Hi @RiccardoDalFiume!
You appear to have posted a live example (http://run.plnkr.co/plunks/zRqA9CkrmP8A1rlYjviY/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

W001: <head> is missing UTF-8 charset <meta> tag
W002: <head> is missing X-UA-Compatible <meta> tag that disables old IE compatibility modes
W003: <head> is missing viewport <meta> tag that enables responsiveness
line 5, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2
line 6, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

http://plnkr.co/edit/zRqA9CkrmP8A1rlYjviY?p=preview

Hi @RiccardoDalFiume!
You appear to have posted a live example (http://run.plnkr.co/plunks/zRqA9CkrmP8A1rlYjviY/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

W001: <head> is missing UTF-8 charset <meta> tag
W002: <head> is missing X-UA-Compatible <meta> tag that disables old IE compatibility modes
W003: <head> is missing viewport <meta> tag that enables responsiveness
line 5, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2
line 6, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

http://plnkr.co/edit/zRqA9CkrmP8A1rlYjviY?p=preview

Hi @RiccardoDalFiume!
You appear to have posted a live example (http://run.plnkr.co/plunks/zRqA9CkrmP8A1rlYjviY/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 8, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2
line 9, column 5: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.3.2

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

http://plnkr.co/edit/zRqA9CkrmP8A1rlYjviY?p=preview

No worries about the errors there, I run into them all the time :D.
Your only real options are to use a different column class for the label column—thereby making it wider—or using CSS text truncation (check the docs section on utilities).


API .NET 6 - Error with EnvelopesApi

Hi all,
I mad a prototype in Console .NET 6 with the DocuSign.Esign.dll. Everything working great but I just start implementation of the prototype in the definitive project and I got each time a error when I use EnvelopesApi.
The error is : One or more errors occurred. (Error setting value to 'StatusChangedDateTime' on 'DocuSign.eSign.Model.Envelope'.)
I use the last version of Nuget package.
My init code :
`
        _client = new ApiClient(_apiUrl);

        _integrationKey = integrationKey;

        _userId = userId;

        _authUrl = authUrl;

        _accountId = accountId;

        _templateId = templateId;

        _rsaKey = File.ReadAllText(rsaKey);

        _oAuthToken = _client.RequestJWTUserToken(_integrationKey, _userId, _authUrl, Encoding.UTF8.GetBytes(_rsaKey), 1, _scopes);

        _envelopesApi = new EnvelopesApi(_client);
        _templatesApi = new TemplatesApi(_client);`

Any idea why I got this change ?
Thank you
Cheers,
Zibeug

11_OK_GetEnvelope.txt
There is my test. It's look very strange because the request return 200 OK but always the same error.
One time on StatusDateTime and for this request : Catch error:One or more errors occurred. (Error setting value to 'CreatedDateTime' on 'DocuSign.eSign.Model.Envelope'.)

I think the values are not the problem because I made an  another project with same values and It's working great. (CopyPaste)
It's an API made by another company and I'm working on DocuSignPart. But when I make my own solution with a API project that work great.
Maybe something with the timezone of the API ?

I think I found the problem after a long time of debug. I start my service in a thread. Outside of this thread everything is working great. Inside the thread I got the error.

That's a good news indeed. It could be interesting anyway to understand why it didn't work using a thread. We would need then to have a stack trace/concrete elements in order to investigate. Let me know if you wanted to continue the analysis in this way...

I found the problem It's during the deserialize of JsonConvert. I tried to put a random string and I got a return from ApiClient model. After downloaded your code I changed all Model with Date in string to DateTime and the error is gone. Maybe you can change it for the new version ! :-D


feat: Support "discriminated union".

i.e. unions which have type distinctions that affect how they're mapped.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

12 of 12 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1760

Relevant Lines:
1760

💛  - Coveralls


Display enumeration error

Thanks for this very nice addition to the voicemeeter ecosystem :)
I've noticed one very small issue - I have dual displays here, and often use the secondary display only. This means that when I enable my primary display (read: turn on my other monitor), what was display '0' becomes display '1'.
I always want the popup to appear on that secondary display (as the primary is for gaming exclusively) so I have FancyOSD configured to use display 1.
When only the secondary is enabled, this fails gracefully and uses display 0, being the secondary monitor, and all is well.
When both displays are enabled, this works as configured and uses display 1, being the secondary monitor, and all is well.
But If I start FancyOSD with only the one (secondary) monitor enabled, then enable the primary monitor, the monitor enumeration changes during FancyOSD's run time, and the OSD appears on my primary display, display 0, in spite of being configured to use display 1.
No big stress about this but if there's a performant way to deal with it, that'd be nice, so I thought I should report it.

As far as I know Display enumeration works like that because of the OS. The program is designed to show OSD on available display event if settings, so probably when the primary display is disabled, the secondary display you mention in your case is 0 and when you connect primary - connected display becomes 1. I dont think I can fix that easily.

Sorry, I have neglected to mention an important detail, my workaround: After enabling/disabling a display, simply exit and restart FancyOSD, or, open the Settings and Info dialog and change the display number to something random and then back to the same number (1).
So, you're right about how windows is handling it, but the problem here is not that the displays are enumerated incorrectly when they are enumerated, it is that FancyOSD assumes that the enumeration has not changed since it was initialised. If, after enabling or disabling a monitor, I force it to re-enumerate the displays, everything works as expected.
So I guess, there would need to be a function to detect when display enumeration changes (ie: monitors are disabled/enabled), or to enumerate them before every OSD display (sounds expensive, I don't know though) or something like that.... I don't know how practical this kind of thing would be in reality, so, no pressure! I'm quietly hoping there's a windows API you can hook into on enumeration changes and it'll be really simple :)

It's already keeping tracks of possible changes, but maybe display disconnection is not detected properly. Try this build and enable logger. Check what log file says when you disconnect/connect display. There will be something like
DEBUG DISPLAY ENUMERATION: Windows settings change detected - Desktop
VoicemeeterFancyOsd-x64-<IP_ADDRESS> disp enum test.zip

I see it detects. It will help to investigate further if I have some problem in my code or in the library that enumerate displays.

Try this version
VoicemeeterFancyOsd-x64-<IP_ADDRESS>-preview.zip

Works like a charm!  Thanks so much :)
There are no debug log messages in this one, I am guessing that's intentional, but I thought I should mention it.


FreeCAD Draft Workbench error

Describe the bug
Navigating to Draft produces the following error in console:
<built-in function SoFieldContainer_getField> returned a result with an exception set
Traceback (most recent call last):
  File "<string>", line 149, in Activated
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_snapper.py", line 1629, in show
    self.setTrackers()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_snapper.py", line 1673, in setTrackers
    self.grid = trackers.gridTracker()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_trackers.py", line 972, in __init__
    pick.style.setValue(coin.SoPickStyle.UNPICKABLE)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4744, in __getattr__
    field = self.getField(name)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4601, in getField
    return _coin.SoFieldContainer_getField(self, name)

All the tools appear to be broken as well:
Running the Python command 'Draft_Facebinder' failed:
Traceback (most recent call last):
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_facebinders.py", line 66, in Activated
    super(Facebinder, self).Activated(name="Facebinder")
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_base_original.py", line 287, in Activated
    super(Creator, self).Activated(name, noplanesetup)
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_base_original.py", line 152, in Activated
    Gui.Snapper.setTrackers()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_snapper.py", line 1673, in setTrackers
    self.grid = trackers.gridTracker()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_trackers.py", line 972, in __init__
    pick.style.setValue(coin.SoPickStyle.UNPICKABLE)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4744, in __getattr__
    field = self.getField(name)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4601, in getField
    return _coin.SoFieldContainer_getField(self, name)

<built-in function SoFieldContainer_getField> returned a result with an exception setRunning the Python command 'Draft_Trimex' failed:
Traceback (most recent call last):
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_trimex.py", line 84, in Activated
    super(Trimex, self).Activated(name="Trimex")
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_base_original.py", line 307, in Activated
    super(Modifier, self).Activated(name, noplanesetup, is_subtool)
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_base_original.py", line 152, in Activated
    Gui.Snapper.setTrackers()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_snapper.py", line 1673, in setTrackers
    self.grid = trackers.gridTracker()
  File "/nix/store/va42205c0jp3ik02ap2yrnrcm8j933q6-freecad-0.20/Mod/Draft/draftguitools/gui_trackers.py", line 972, in __init__
    pick.style.setValue(coin.SoPickStyle.UNPICKABLE)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4744, in __getattr__
    field = self.getField(name)
  File "/nix/store/dq8yly6isjzq6imm0i0qjxkang5rcq84-python3.10-pivy-0.6.6/lib/python3.10/site-packages/pivy/coin.py", line 4601, in getField
    return _coin.SoFieldContainer_getField(self, name)

<built-in function SoFieldContainer_getField> returned a result with an exception set

Steps To Reproduce
Open FreeCAD and navigate to Draft Workbench.
Expected behavior
No errors in console.
Notify maintainers

@viric @gebner @AndersonTorres

Possibly related to how old cond3d is?


AuthApiError "Invalid login credentials" has undefined code

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When attempting to login a user with invalid credentials, the returned error is missing a code:
const { data, error } = await supabase.auth.signInWithPassword({
  email: loginDto.email,
  password: loginDto.password,
});
if (isAuthApiError(error)) {
  if (error.code == 'user_not_found') {
    throw new UnauthorizedException();
  } else {
    throw new InternalServerErrorException(
      `Unhandled Supabase auth error code: ${error}`, // <-- error.code undefined
    );
  }
} else { /* ... */ }

Output:
Unhandled exception: {
  "statusCode": 500,
  "message": "Unhandled Supabase auth error code: AuthApiError: Invalid login credentials",
  "error": "Internal Server Error"
}

The source of AuthAPIError has code as undefined:
https://github.com/supabase/auth-js/blob/29fc62ce2da7ca60504d2513012fd3bb2820e632/src/lib/errors.ts#L78-L82
To Reproduce

Perform supabase.auth.signInWithPassword({ /* ... */ }) with incorrect credentials
Observe error.code is undefined

Expected behavior
Per docs:

Use isAuthApiError instead of instanceof checks to see if an error you caught is of this type.

Do not use string matching on error messages! Always use the name and code properties of error objects to identify the situation.

code should be defined for an AuthApiError.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: macOS
Version of supabase-js: 2.45.0
Version of Node.js: v21.7.3

It looks like this is also here: https://github.com/supabase/auth/issues/1631
I figured this issue was JS-specific, but it appears not?

My workaround:
if (isAuthApiError(error)) {
  if (error.code == 'user_not_found') {
    throw new UnauthorizedException();
  } else {
    throw new UnauthorizedException(`${error}`);
  }
} else if (error) {
  throw new InternalServerErrorException(
    `Unhandled unknown error: ${error}`,
  );
}

Hey,
Thanks for flagging the issue. A fix has been merged and this should be patched later this week or early next week with our next deploy
Hope this helps. I'm going to close for now but feel free to re-open or head to #804 if there are any issues after upgrading. You can track the version under Settings > Infrastructure > Service Versions > Auth version. Should be good to go once your project version is v2.159.0 or later


use DOMParser instead of innerHTML

The pre-rendered document we are fetching is actually an HTML document with both a Style tag and a div with the content.  In order for React hydration to work, the DOM needs to match what is ultimately rendered, which means just the div part needs to be added to the widgetContainer.  We can put the Style tag directly in the head.
@Blainegunn

lookin' good.  FCP=LCP.  hydrate is working.


[Testing] Add note about unsupported scenarios for specific channels on Node

Hi @JuanAr, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


pulp: remove pulp

OSBS-5098
Remove all references to pulp in order to complete the transition to quay.io.
Signed-off-by: Mark Langsdorf<EMAIL_ADDRESS>

We can ignore the coveralls decrease.

doc PR at https://github.com/containerbuildsystem/osbs-docs/pull/96

Added to RN under "Build JSON Changes":

Removed support for building Pulp images.


Clipping is broken + suggestions

Hi there,
Your extension is much needed and I cant believe twitch hasn't implemented it yet.
Clipping is currently broken, no matter which channel im on and whether an ad is playing or not it gives the error message. Is this fixable?
Also is it possible to add a theater mode button? I know you can use the shortcut but its a lot nicer to have the button.
Thank you!
edit: Also the clipping button goes away when you rewind. Is it possible to still have it if you are not live? Very often I will want to clip something that happened previously - if this extension can't do it then I'd have to just go to the VOD anyways which defeats the point of it.

I fixed clipping in VOD mode in the latest release (should be coming out soon).
hm, for deleted and hidden vods, I don't think that the video urls are deterministic so I don't think I can get the video URL without calling twitch's api (which doesn't return deleted VODs). I could definitely be wrong though.
As for compatibility with video adblock for twitch, as an ex-twitch employee I unfortunately don't feel super comfortable explicitly supporting compatibility with that extension, I'm sorry :(.


Failures using marshal_dump with v1.3.0

We started hitting failures related to RecursiveOpenStruct#marshal_dump that appear to be introduced by #72
The return value is different causing callers that assume the same API contract, specifically something like ros.marshal_dump.each { |key, val| ... } now fails because it is iterating over an array of the ostruct and the options.
Example code that fails: https://github.com/fog/fog-kubevirt/blob/master/lib/fog/kubevirt/compute/compute.rb#L94-L97
Related Issue: https://github.com/fog/fog-kubevirt/issues/161
Since this changes the return format IMO this was a breaking change and should have been a major version release.

Note that marshal_dump and marshal_load were inherited from ostruct with this implementation: https://github.com/ruby/ostruct/blob/master/lib/ostruct.rb#L217-L227, and the new interface in #72  changes that contract.

Apologies, I didn’t consider how this might’ve been a breaking change when I merged #72 .
I’ll push a patch release later today to revert the marshal_dump change, and will move the marshal_dump change to a new major release.

I pushed 1.3.1, which reverts the marshalling changes

And restored #72 and released as major version 2.0.0

:bow: thanks for the quick fix @aetherknight !


Migration building stock data of EU datasets

This PR consists of a migration related to the update of building stock data for EU datasets. With this migration, the set values and default value settings of building stock inputs are preserved for existing scenarios.
Goes with:

https://github.com/quintel/etsource/pull/3139
https://github.com/quintel/etlocal/pull/560
https://github.com/quintel/etdataset/pull/1023
https://github.com/quintel/etengine/pull/1469

I have tested the migration and it works!
There is one issue that arises:
If before the migration I have set the slider to a value that is higher than the new max value, and then run the migration I will see the new max values in the front-end:

While actually in the engine, the slider value is equal to the old value I put in before the migration

@noracato Is this behaviour expected?
This might confuse users.


python38Packages.dpkt: 1.9.6 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.dpkt is: "Fast, simple packet creation / parsing, with definitions for the basic TCP/IP protocols"
meta.homepage for python38Packages.dpkt is: "https://github.com/kbandla/dpkt"
meta.changelog for python38Packages.dpkt is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/bv9qismkqaqc6x4ayhnnshh2qdlsa7gi-python3.8-dpkt-<IP_ADDRESS>

found <IP_ADDRESS> in filename of file in /nix/store/bv9qismkqaqc6x4ayhnnshh2qdlsa7gi-python3.8-dpkt-<IP_ADDRESS>

directory tree listing: https://gist.github.com/75fc9cbff743f670f3c8d3d2f5ec93a2

du listing: https://gist.github.com/d4ab96982da2fcdda233100dcb2db571

Rebuild report (if merged into master) (click to expand)

40 total rebuild path(s)

10 package rebuild(s)

10 x86_64-linux rebuild(s)
10 i686-linux rebuild(s)
10 x86_64-darwin rebuild(s)
10 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
john
python38Packages.angr
python38Packages.angrop
python38Packages.dpkt
python38Packages.pypcap
python39Packages.angr
python39Packages.angrop
python39Packages.dpkt
python39Packages.pypcap
visidata

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bv9qismkqaqc6x4ayhnnshh2qdlsa7gi-python3.8-dpkt-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.dpkt https://github.com/r-ryantm/nixpkgs/archive/8d8616be35646e22a8b5643801dcbc4105eaf7f2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bv9qismkqaqc6x4ayhnnshh2qdlsa7gi-python3.8-dpkt-<IP_ADDRESS>
ls -la /nix/store/bv9qismkqaqc6x4ayhnnshh2qdlsa7gi-python3.8-dpkt-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

10 packages built:

john
python38Packages.angr
python38Packages.angrop
python38Packages.dpkt
python38Packages.pypcap
python39Packages.angr
python39Packages.angrop
python39Packages.dpkt
python39Packages.pypcap
visidata

Maintainer pings
cc @bjornfor for testing.

I like how fast and python is used in one sentence: The dpkt project is a python module for fast, simple packet parsing, with definitions for the basic TCP/IP protocols.


Upgrade from PyMC3 to PyMC

Everything seems to work fine, but I will test it a bit more before merging into main.


Add some Features

Todo

[ ] make the reach us section workable
[ ] Automatic add the contributor in UI
[ ] Add some good-looking UI in the Header section / you can completely change the header section Also

sure , Thanks @Aditya-Narayan-Nayak


cloud_provider_* metrics include configured node name as label

The cloud_provider_* metrics include an id label that represents the name of the ASG in the cloud provider, and not the name of the node group configured in nodegroup.yml. Other metrics include the node_group label that does represent the configured name. This difference makes it difficult to correlate metrics since there's no shared key:value pair.
I started making a PR, but it got pretty ugly adding a Name() function to cloudprovider.NodeGroup and felt wrong to have the provider abstraction include a field just for tying back to the non-provider nodegroup config. I decided to abort the PR and file this issue instead to start the discussion.
Does this seem like a reasonable change to the metrics? What's the best way to implement it? Should I just extend cloudprovider.NodeGroup and take the aesthetic hit?

Great suggestion! I'm completely happy to have the Name() field added to the NodeGroup interface as it's something that should of originally been added to the metrics. I suggest updating CloudProvider. RegisterNodeGroups to take a slice of some sort of struct containing both the ID + name instead of a slice of strings so we can nicely pass in the node group name.
Let me know what you think.


Connected host has failed to respond...

I can visit fanbox, but cannot download.
I'm sure the creator name is correct.
The SESSID is from below and I think it's also correct:

It appears that the connection at the TCP level is being denied. It is possible that some security tool on your PC is running.
Try closing the security tool or running Powershell as administrator and execute fanbox-dl.


Specify ruby version

Use the .ruby-version convention to specify a ruby version.

Thanks for the contribution @leesmith! If this were a private app and it had a corresponding production environment, I'd be keen to include this PR and keep the Ruby version as up-to-date as possible. As its an educational project, this change would add an extra dependency that might stop some developers from running it on their machine. Its OK for it to run on an older Ruby version.
I can imagine that the app not having the .ruby-version file specified would get in the way of getting it up and running in some dev environment setups, I've encountered that recently on another project I needed to run. If it did get in the way, I'd be interested in alternative ideas on how to simplify the setup and keep it flexible enough to work on multiple ruby versions. Perhaps a variation on this idea might be helpful: https://gist.github.com/eliotsykes/8fecb12f96bb21fcb582

I see where you're coming from.  In that case though, I would at least mention something about a recommended Ruby version to use in the README. At least tell beginners that Rails 4 requires Ruby 2+?


[AMORO-2982] UI optimization when no available optimizer groups

Why are the changes needed?

Close #2982.
Brief change log

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)


"there are no support language"

Region and Brand of car
Sweden / EU / Kia EV6
Version of the integration
2.14.1
Describe the bug
The Kia app spam with Notifications : "there are no support language, check device language"
acording to Kia Connect Support , this is caused by the Home Assistant app kia_uvo
Any idea what this is caused by?
It started after the last update , but i dont remember what step I took.

Integration is using the home assistant system language and falls back to English. Assuming home assistant language is not supported by kia contrary to what we think. Share more information about your home assistant setup.
By the way, how is Kia aware of this integration? This is not an official thingy just reverse engineering their work and I am sure they wouldn't want this

Okey, I use swedish as my system language, is it possible to force this integration to go directly to English?
Kia Support referd to third party application, I translated that to Home Assistanse in the fault report since I only use that for communication to "kia"

Share your debug logs and let me see the exact flow and we can solve it


Added imagePath getter and setter in PaymentConnectorConfiguration wh…

Added imagePath getter and setter in PaymentConnectorConfiguration when calling the Token Service > Active Version: api: /api/token-version/active-version

This feature was included in previous version. Thanks for sharing your knowledge with us.


🐛 [flutterfire_ui] SMS Auth Code Flow Gets stuck with: Bad state: Future already completed

Bug report
Describe the bug
SMS Code Flow fails sometimes on Phone Auth method.
flutter: ‼ 14:39:08.058876 ERROR    Global Loggy - ERROR:Bad state: Future already completed
flutter: #0      _AsyncCompleter.complete (dart:async/future_impl.dart:44:31)
#1      PhoneAuthFlow.verifySMSCode (package:flutterfire_ui/src/auth/flows/phone_auth_flow.dart:93:23)
#2      _SMSCodeInputViewState.submit (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:39:12)
#3      _SMSCodeInputViewState.build.<anonymous closure>.<anonymous closure> (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:75:21)
#4      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:992:21)
#5      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:198:24)
#6      TapGestureRecognizer.handleTapUp (package:flutter/src/gestures/tap.dart:613:11)
#7      BaseTapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:298:5)
#8      BaseTapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:269:7)
#9      GestureArenaManager.sweep (package:flutter/src/gestures/arena.dart:157:27)
#10     GestureBinding.handleEvent <…>

══╡ EXCEPTION CAUGHT BY GESTURE ╞═══════════════════════════════════════════════════════════════════
The following StateError was thrown while handling a gesture:
Bad state: Future already completed

When the exception was thrown, this was the stack:
#1      PhoneAuthFlow.verifySMSCode (package:flutterfire_ui/src/auth/flows/phone_auth_flow.dart:93:23)
#2      _SMSCodeInputViewState.submit (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:39:12)
#3      _SMSCodeInputViewState.build.<anonymous closure>.<anonymous closure> (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:75:21)
#4      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:992:21)
#5      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:198:24)
#6      TapGestureRecognizer.handleTapUp (package:flutter/src/gestures/tap.dart:613:11)
#7      BaseTapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:298:5)
#8      BaseTapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:269:7)
#9      GestureArenaManager.sweep (package:flutter/src/gestures/arena.dart:157:27)
#10     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:448:20)
#11     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:424:22)
#12     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:326:11)
#13     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:379:7)
#14     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:343:5)
#15     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:301:7)
#16     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:284:7)
#20     _invoke1 (dart:ui/hooks.dart:170:10)
#21     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:331:7)
#22     _dispatchPointerDataPacket (dart:ui/hooks.dart:94:31)
(elided 4 frames from dart:async)

Steps to reproduce

Choose Phone Sign In for the existing user on fresh device.
Will enter phone number (marked as test phone in Firebase auth)
Will enter SMS confirmation code as set for the test number
Will see the error logs
Will continue seeing SMS Auth Code screen without any error message

Sometimes it works as expected, sometimes it does not.
Expected behavior
Flow would continue or generate some error message.
Sample project
SignInScreen(
      providerConfigs: [
        // EmailProviderConfiguration(),
        PhoneProviderConfiguration(),
      ],
    );

Additional context
Add any other context about the problem here.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 2.10.0-1.0.pre.423, on macOS 12.2 21D49 darwin-arm, locale en-EE)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.63.2)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
flutter pub deps -- --style=compact
Dart SDK 2.17.0-79.0.dev
Flutter SDK 2.10.0-1.0.pre.423
play_faire 1.0.1+1

dependencies:
- cloud_firestore 3.1.7 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- date_picker_timeline 1.2.3 [flutter intl]
- firebase_analytics 9.1.0 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 3.3.6 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.12.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_dynamic_links 4.0.5 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- flutter 0.0.0 [characters collection material_color_utilities meta typed_data vector_math sky_engine]
- flutter_form_builder 7.1.0 [flutter intl]
- flutter_hooks 0.18.2 [flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path typed_data vector_math]
- flutter_loggy 2.0.1 [flutter loggy rxdart]
- flutter_picker 2.0.2 [flutter]
- flutterfire_ui 0.3.2 [cloud_firestore collection crypto desktop_webview_auth email_validator firebase_auth firebase_core firebase_database firebase_dynamic_links flutter flutter_facebook_auth flutter_localizations flutter_svg google_sign_in sign_in_with_apple twitter_login]
- fluttertoast 8.0.8 [flutter flutter_web_plugins]
- form_builder_extra_fields 7.1.0 [flutter flutter_form_builder flutter_chips_input flutter_colorpicker dropdown_search signature flutter_touch_spin intl flutter_typeahead flutter_datetime_picker_bdaya flutter_rating_bar]
- form_builder_phone_field 1.0.0-beta.0 [flutter flutter_form_builder phone_number country_pickers]
- form_builder_validators 7.4.0 [flutter flutter_localizations intl collection]
- freezed_annotation 1.1.0 [collection json_annotation meta]
- hooks_riverpod 1.0.3 [collection flutter flutter_hooks flutter_riverpod riverpod state_notifier]
- intl 0.17.0 [clock path]
- intro_slider 3.0.3 [flutter]
- loggy 2.0.1+1 [stack_trace]
- mixpanel_flutter 1.4.4 [flutter flutter_web_plugins js]
- package_info_plus 1.3.0 [flutter package_info_plus_platform_interface package_info_plus_linux package_info_plus_macos package_info_plus_windows package_info_plus_web]
- share_plus 3.0.4 [meta mime flutter share_plus_platform_interface share_plus_linux share_plus_macos share_plus_windows share_plus_web]
- shared_preferences 2.0.12 [flutter shared_preferences_android shared_preferences_ios shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- url_launcher 6.0.18 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]

dev dependencies:
- build_runner 2.1.7 [args async analyzer build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_gen_runner 4.1.5 [flutter_gen_core build]
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph typed_data]
- freezed 1.1.1 [analyzer build build_config collection meta source_gen freezed_annotation]
- json_serializable 6.1.4 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- sentry_flutter 6.3.0 [flutter flutter_web_plugins sentry package_info_plus]

transitive dependencies:
- _fe_analyzer_shared 34.0.0 [meta]
- analyzer 3.2.0 [_fe_analyzer_shared cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.1.11 [crypto path]
- args 2.3.0
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.2.1 [analyzer async convert crypto glob logging meta path]
- build_config 1.0.0 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.0.1 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.6 [analyzer async build crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.1.4 [built_collection collection fixnum meta]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- cli_util 0.3.5 [meta path]
- clock 1.1.0
- cloud_firestore_platform_interface 5.4.12 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.6.7 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.1.0 [built_collection built_value collection matcher meta]
- collection 1.15.0
- color 3.0.0
- convert 3.0.1 [typed_data]
- country_pickers 2.0.0 [flutter]
- crypto 3.0.1 [collection typed_data]
- dart_style 2.2.1 [analyzer args path pub_semver source_span]
- dartx 1.0.0 [characters collection crypto meta path time]
- desktop_webview_auth 0.0.2 [crypto flutter http]
- dropdown_search 2.0.1 [flutter]
- email_validator 2.0.1
- fake_async 1.2.0 [clock collection]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase_analytics_platform_interface 3.0.5 [firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.4.0+6 [firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.1.11 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.3.7 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.2.4 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.5.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_database 9.0.6 [firebase_core firebase_core_platform_interface firebase_database_platform_interface firebase_database_web flutter]
- firebase_database_platform_interface 0.2.0+5 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_web 0.2.0+5 [firebase_core firebase_core_web firebase_database_platform_interface flutter flutter_web_plugins js]
- firebase_dynamic_links_platform_interface 0.2.0+5 [firebase_core flutter meta plugin_platform_interface]
- fixnum 1.0.0
- flutter_chips_input 1.10.0 [flutter]
- flutter_colorpicker 1.0.3 [flutter]
- flutter_datetime_picker_bdaya 2.0.0 [flutter]
- flutter_facebook_auth 3.5.7 [flutter flutter_facebook_auth_platform_interface flutter_facebook_auth_web]
- flutter_facebook_auth_platform_interface 2.7.1 [flutter plugin_platform_interface]
- flutter_facebook_auth_web 2.6.0+2 [flutter flutter_web_plugins js flutter_facebook_auth_platform_interface]
- flutter_gen_core 4.1.5 [path yaml mime xml dartx color collection json_annotation dart_style analyzer args pub_semver source_span]
- flutter_keyboard_visibility 5.1.1 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_web flutter]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_rating_bar 4.0.0 [flutter]
- flutter_riverpod 1.0.3 [collection flutter meta riverpod state_notifier]
- flutter_svg 1.0.3 [flutter meta path_drawing vector_math xml]
- flutter_touch_spin 2.0.0 [flutter intl]
- flutter_typeahead 3.2.4 [flutter flutter_keyboard_visibility]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta typed_data vector_math]
- frontend_server_client 2.1.2 [async path]
- glob 2.0.2 [async collection file path string_scanner]
- google_sign_in 5.2.3 [flutter google_sign_in_platform_interface google_sign_in_web]
- google_sign_in_platform_interface 2.1.1 [flutter quiver]
- google_sign_in_web 0.10.0+4 [flutter flutter_web_plugins google_sign_in_platform_interface js pedantic]
- graphs 2.1.0 [collection]
- http 0.13.4 [async http_parser meta path]
- http_multi_server 3.0.1 [async]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image 3.1.1 [archive meta xml]
- io 1.0.3 [meta path string_scanner]
- js 0.6.4
- json_annotation 4.4.0 [meta]
- lints 1.0.1
- logging 1.0.2
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- meta 1.7.0
- mime 1.0.1
- package_config 2.0.2 [path]
- package_info_plus_linux 1.0.3 [package_info_plus_platform_interface flutter path]
- package_info_plus_macos 1.3.0 [flutter]
- package_info_plus_platform_interface 1.0.2 [flutter meta plugin_platform_interface]
- package_info_plus_web 1.0.4 [flutter flutter_web_plugins http meta package_info_plus_platform_interface]
- package_info_plus_windows 1.0.4 [package_info_plus_platform_interface ffi flutter win32]
- path 1.8.1
- path_drawing 1.0.0 [vector_math meta path_parsing flutter]
- path_parsing 1.0.0 [vector_math meta]
- path_provider_linux 2.1.5 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.3 [flutter platform plugin_platform_interface]
- path_provider_windows 2.0.5 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 4.4.0 [meta]
- phone_number 0.12.0+1 [flutter meta]
- platform 3.1.0
- plugin_platform_interface 2.1.2 [meta]
- pool 1.5.0 [async stack_trace]
- process 4.2.4 [file path platform]
- pub_semver 2.1.0 [collection meta]
- pubspec_parse 1.2.0 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.0.1+1 [matcher]
- riverpod 1.0.3 [collection meta state_notifier]
- rxdart 0.27.3
- sentry 6.3.0 [http meta stack_trace uuid]
- share_plus_linux 2.0.4 [share_plus_platform_interface file flutter meta url_launcher]
- share_plus_macos 2.0.2 [share_plus_platform_interface flutter]
- share_plus_platform_interface 2.0.1 [flutter meta mime plugin_platform_interface]
- share_plus_web 2.0.4 [share_plus_platform_interface url_launcher flutter flutter_web_plugins meta]
- share_plus_windows 2.0.3 [share_plus_platform_interface flutter meta url_launcher]
- shared_preferences_android 2.0.10 [flutter shared_preferences_platform_interface]
- shared_preferences_ios 2.0.9 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.0.4 [file flutter path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.2 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.3 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.0.4 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.2.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sign_in_with_apple 3.3.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- signature 5.0.0 [flutter image]
- sky_engine 0.0.99
- source_gen 1.2.1 [analyzer async build dart_style glob meta path source_span yaml]
- source_helper 1.3.1 [analyzer collection source_gen]
- source_span 1.8.2 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- state_notifier 0.7.2+1 [meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- time 2.1.0 [clock]
- timing 1.0.0 [json_annotation]
- twitter_login 4.0.1 [flutter crypto http]
- typed_data 1.3.0 [collection]
- url_launcher_android 6.0.14 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.0.14 [flutter url_launcher_platform_interface]
- url_launcher_linux 2.0.3 [flutter]
- url_launcher_macos 2.0.3 [flutter]
- url_launcher_platform_interface 2.0.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.7 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 2.0.2 [flutter]
- uuid 3.0.5 [crypto]
- vector_math 2.1.2
- watcher 1.0.1 [async path]
- web_socket_channel 2.1.0 [async crypto stream_channel]
- win32 2.3.10 [ffi]
- xdg_directories 0.2.0+1 [meta path process]
- xml 5.3.1 [collection meta petitparser]
- yaml 3.1.0 [collection source_span string_scanner]

I tried the scenario mentioned couple of times using latest stable (2.10.0) but was unable to see the mentioned error log.
I was able to go through the auth flow properly without any issues.
Labeling it based on the error log reported.

OK, I will update to latest and will do some addition testing and debugging to give more clear scenario.
You mentioned 2.10.0, but flutterfire latest version is flutterfire_ui: ^0.3.3

I encounter this problem often as well.
It's easy to reproduce, too:

Navigate to the "Enter SMS code" screen
Enter a wrong verification code on purpose, hit "verify" button
Enter the correct verification code, hit "verify" button

Expected behavior:
Pressing the "verify" button with the corrected verification code now logs the user in.
Observed behavior:
Pressing the "verify" button does nothing. Login is impossible, unless the user restarts the auth flow.
The console logs:
======== Exception caught by gesture ===============================================================
The following StateError was thrown while handling a gesture:
Bad state: Future already completed

When the exception was thrown, this was the stack:
#1      PhoneAuthFlow.verifySMSCode (package:flutterfire_ui/src/auth/flows/phone_auth_flow.dart:93:23)
#2      _SMSCodeInputViewState.submit (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:39:12)
#3      _SMSCodeInputViewState.build.<anonymous closure>.<anonymous closure> (package:flutterfire_ui/src/auth/views/sms_code_input_view.dart:75:21)
#4      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:1004:21)
#5      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:247:24)
#6      TapGestureRecognizer.handleTapUp (package:flutter/src/gestures/tap.dart:612:11)
#7      BaseTapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:298:5)
#8      BaseTapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:269:7)
#9      GestureArenaManager.sweep (package:flutter/src/gestures/arena.dart:157:27)
#10     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:449:20)
#11     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:425:22)
#12     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:329:11)
#13     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:380:7)
#14     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:344:5)
#15     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:302:7)
#16     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:285:7)
#17     _invoke1 (dart:ui/hooks.dart:167:13)
#18     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:341:7)
#19     _dispatchPointerDataPacket (dart:ui/hooks.dart:94:31)
(elided one frame from dart:async)
Handler: "onTap"
Recognizer: TapGestureRecognizer#c6574
  debugOwner: GestureDetector
  state: ready
  won arena
  finalPosition: Offset(218.5, 350.9)
  finalLocalPosition: Offset(179.2, 12.8)
  button: 1
  sent tap down
====================================================================================================

My analysis
Upon hitting the "verify" button, the following method in phone_auth_flow.dart is called:
  @override   void verifySMSCode(String code) {     _smsCodeCompleter.complete(code);   }
The problem is that the complete method may only be called once at most, after which it will throw the Bad state: Future already completed error. That is why pressing the verify button can never work after trying it once.


Migrate to PDFBox 3.0.0

When PDFBox 3.0.0 leaves RC status, will merge and release Tabula 1.1.0.

superceded by #541


 has a regression with deeply nested nodes

Description
The regression is showcased by the following test case: https://github.com/Shopify/react-native-skia/blob/main/package/src/renderer/tests/e2e/Blending.spec.tsx#L83
Version
0.1.165
Steps to reproduce
The test case linked above should pass
Snack, code example, screenshot, or link to a repository
https://github.com/Shopify/react-native-skia/blob/main/package/src/renderer/__tests__/e2e/Blending.spec.tsx#L83

Fixed in #1340


Make tests compatible to phpunit 10

Make tests compatible to phpunit 10
Base on phpunit document setMethods and at will be removed. I removed these methods so it can be easily possible to use phpunit 10.

This PR includes changes not related to title topic

It seems it is not working on 6.x.


update syntax for block result support in ink

Depends upon https://github.com/JunoLab/atom-ink/pull/31 and Atom master.

Superseded by #144.


WIP: QRCode generation and Product attribute timeline

[x] Generate and Show QR Code on view modal for each QRCODE
[x] QRCODE must be scanned and lead to a timeline css of the Product and its attributes

QRCODE in view modal of product

QRCODE Destination mobile

QRCODE destination desktop

NEW MOBILE VIEW

NEW DESKTOP VIEW

ATTRIBUTE PAGE EXTENDED URL


IPNS name publish failed on v0.13.3-rc2

Regular startup of the daemon will produce the following log output after the OpenBazaar service starts:
13:08:05.066 [ERROR] [core/publish] name publish failed

This appears only on certain nodes, but it is unclear what the conditions for which nodes are affected. It's very likely a side-effect of some data mismatch in changing from IPFS 0.4.18 to 0.4.19 and will likely be highly correlated with nodes that have started with version 0.13.2 (last release version) or earlier.

Report on Reddit with log:
https://www.reddit.com/r/OpenBazaar/comments/ahcgsx/openbazaar_megathread_post_bugs_troubleshooting/eo1i6p8/
Another from support ticket:
"Publishing failed. Retry." -- I get that error all the time when I'm publishing something.

System: Ubuntu 18.04.2 (Cinnamon DE)

What I've done:

* Deleted cached files -- not helped.


authorize_access_token broken POST?

Hello, I'm really not sure if it is a bug, but when I am trying to use authorize_access_token there is no params in POST body, as I understand they are sending in a new TCP packet (see a tcpdump picture)?
oauth = OAuth()
oauth.register(
    'zoom',
    client_id=os.environ['ZOOM_CLIENT_ID'],
    client_secret=os.environ['ZOOM_CLIENT_SECRET'],
    access_token_url='http://zoom.us/oauth/token',
    refresh_token_url='http://zoom.us/oauth/token',
    authorize_url='http://zoom.us/oauth/authorize',
    client_kwargs={'token_endpoint_auth_method': 'client_secret_post'},
)

def zoom_login(request):
    redirect_uri = request.build_absolute_uri('/zoom_authorize')
    return oauth.zoom.authorize_redirect(request, redirect_uri)

def zoom_authorize(request):
    print(request)
    token = oauth.zoom.authorize_access_token(request, body='aaaa=bbbbb')
    #resp = oauth.zoom.get('user', token=token)
    #resp.raise_for_status()
    #profile = resp.json()
    # do something with the token and profile
    #return profile

I've started tcpdump and can see this:

I think it should be something like this?
POST /oauth/token HTTP/1.1
Host: zoom.us
User-Agent: Authlib/0.15.5 (+https://authlib.org/)
Accept-Encoding: gzip, deflate
Accept: application/json
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded;charset=UTF-8
Content-Length: 216

aaa=bbb&client_id=xaaaaa&client_secret=aaaaaaaa&redirect_uri=ffsadfasd

Not sure what you are printing. It looks like the payload is encoded. Maybe it is because:
Accept-Encoding: gzip, deflate

hm, I didn't set any additional headers, this code that I've posted is all logic, I just get it from the documentation. I have route /zoom_login -> def zoom_login and /zoom_authorize -> def zoom_authorize.
I go to zoom_login it redirects me to authorize_url='http://zoom.us/oauth/authorize' and after this it is redirects me to /zoom_authorize. and this POST query is generated by authorize_access_token(request)
I will google why Accept-Encoding is here and how to remove it


support torch=2.4.0 and python=3.12

vllm wihch depends on xformers == 0.0.27.post2 can support python 3.12 and torch2.4.0, I think it's time to support the new versions.

#442

Yep working on it!

Upgraded Unsloth to make it work with all new TRL versions, Python 3.12 and Torch 2.4/2.5!

Upgraded Unsloth to make it work with all new TRL versions, Python 3.12 and Torch 2.4/2.5!

Last night, I pulled the main branch of unsloth and set up a Jupyter Lab development environment with Python 3.12 and torch 2.4 for GPU using Docker. I noticed that num_train_epochs seems to serve the same purpose as max_steps. What I mean is, no matter how large the amount of data, the number of training steps remains consistent with num_train_epochs. For example, if I set num_train_epochs to 1, then the total number of steps is 1, and the training speed is noticeably slower than the stable release version.

Ok weird so this only happens with the latest update?

Ok weird so this only happens with the latest update?

I'm not sure. Since I discovered the issue with the latest version, I've rolled back unsloth to the support llama3.1 release and reverted the torch version to 2.3, after which everything returned to normal. It's worth mentioning that the new development environment I set up last night was based on the image nvidia/cuda:12.5.1-devel-ubuntu24.04, whereas now I'm using nvidia/cuda:12.4.0-devel-ubuntu22.04, and the CUDA Version on my host machine is 12.4.

I had the "same" problem with @zs856. I was using a legacy version months ago, downloading from a Youtuber's post.
With that version I can finish fine-tuning llama 3-8B-instruct within 1 hour on my 4090 laptop.
After pulling the latest version, the training was much slower - around 100s./it.
I'm considering downgrade to that version, but still wondering why...

@hanzheng Wait you're saying the new Unsloth version makes training slower??!


add s to speed and reduce so copy is gramatically correct

Summary
The current use of speed and reduce on the code-splitting page of the documentation is incorrect. To be grammatically correct, I've added an s.
Test plan
No tests needed as it is just a grammar update to the documentation 😃

Thanks!


How to run the model with parameters ['hidden_dim'] other than 'same''

Currently, i am trying to run the model with parameters['hidden_dim'] set to 64.
Getting following error: ValueError: Trying to share variable ae_discriminator/rnn/multi_rnn_cell/cell_0/gru_cell/gates/kernel, but specified shape (65, 128) and found shape (128, 128).

Thank you so much for pointing out this issue! It appears the error is related to the mismatch in the shape of the ae_discriminator parameters, likely due to the current configuration of hidden_dim and the GRU cell’s expected input size.
I’ll investigate this further and work on resolving the issue. I’ll ensure to upload a new version of the framework with the necessary fixes soon.
Thank you again for bringing this to my attention!


getAlternatives() not working in BaatoRouting.js

https://github.com/baato/js-client/blob/a86bfb72f4a358957cf9f82918e1664052febfda/src/BaatoRouting.js#L39

Marking this as closed, turns out I was using v1.0.11


[questions] variable in the function

Hello,
I have a quick question.
The variable new in the function traj_segment_generator in trpo_mpi/utils.py has not been updated and, thus nextvpred always returns zero. Is it intended?
I just realized in the original baseline, nextvpred is correctly set.

Hello,
Thanks for your remark, this looks like a bug.
I'll take a look. @hill-a I think I'll push a fix on the release 2.4.1 branch soon.

Thanks for the reply :)

@junhyeokahn the fix is pushed (will be merged with master soon) and you are now credited in the changelog ;)


[ACA] [308598] Add reference to setting up private DNS zone.

PR review team: please do not merge or review this PR. This PR is part of an established workflow. Thank you!

#sign-off

#sign-off

#sign-off


Don't build windows debug internally

Currently the master branch builds both debug and release configurations internally, and both try to publish. This creates a race condition by which we sometimes wind up publishing debug packages/symbols - one symptom is mismatched symbols being published to msdl, among potentially others. This isn't an issue in 3.1 as we don't try to publish from the debug configuration there. The safest way to fix the issue is just to disable windows debug builds on the internal side.
CC @NTaylorMullen @mmitche @MattGal @dougbu @JunTaoLuo
Internal build: https://dev.azure.com/dnceng/internal/_build/results?buildId=582612

Internal build no longer has a 'Windows Debug' job running, so I think this worked

@Pilchie @anurse we may want to consider porting this to the preview3 branch - without it there's a chance we'll ship debug bits (as far as I can tell we shipped release in preview1 & preview2)

one symptom is mismatched symbols being published to msdl, among potentially others

Could this be the root cause of https://github.com/dotnet/aspnetcore/issues/20313 ? cc @shirhatti @jkotalik

@wtgodbe yep, let's backport this one. Probably tell-mode but I'm also happy to take it to shiproom.

Could be!

Any objection to me aggressively merging this and we can address feedback in a follow up? We have bits in VS right now without symbols that are getting flagged left and right with watson violations + LiveShare is waiting for symbols from us 😄

@NTaylorMullen fine by me.
@wtgodbe please also cherry-pick this into the preview3 branch.

@NTaylorMullen fine by me.
@wtgodbe please also cherry-pick this into the preview3 branch.

Yes please.

Oh and btw, IT WORKED!


Automated cherry pick of #4592: Fix missing call of removing groupDb cache when deleting OVS

Cherry pick of #4592 on release-1.10.
#4592: Fix missing call of removing groupDb cache when deleting OVS
For details on the cherry pick process, see the cherry pick requests page.

/skip-all


Azure App Service Authentication (Easy Auth) #4095

Added Link to Core Authentication Index with link for Easy Auth steps per #4095

@isaac2004,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@Rick-Anderson

@isaac2004  review URL that link doesn't work. I didn't know we could use ~ relative links

We're in a different repo so you need to use https://docs.microsoft.com/azure/app-service/app-service-authentication-overview

@Rick-Anderson sorry about that, fixed

@isaac2004  Thanks!


logloss issue with multiclass task

Hi HunterMcGushion,
I am doing a multi-classification task and I wanna set sklearn.metrics.log_loss as the experiment metric, but I have a trouble:
env = Environment(
    results_path=HPHPATH,
    train_dataset=df,
    target_column='Quality_label',
    metrics=['log_loss'],
#     metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3])),
    cv_type=StratifiedKFold,
    cv_params=dict(n_splits=6, shuffle=True),
#     global_random_seed=seed
)

experiment = CVExperiment(
    model_initializer=RandomForestClassifier,
    model_init_params=dict(
        n_estimators=20
    )
)

See, the target has 4 labels, 0 to 3. When I run the code above, it triggers a value error:
ValueError: y_true and y_pred contain different number of classes 4, 2.

If I set labels for logloss metric, metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3])), it throws out another error:
ValueError: The number of classes in labels is different from that in y_pred.
I checked the examples and previous issues like #90, and I wonder have you tested logloss for multiclass task?

Thanks for opening this! Sorry I don't have a more helpful update, but I just wanted to say that I'm looking into this, and I do think there's a bug here. I'm making some regression tests using the Iris dataset, with a single label-encoded target column, so I'll probably ask you to try to reproduce some of my results when I'm further along in the bug hunt.
In the meantime, have you tried adjusting the do_predict_proba kwarg of your Environment? Are you expecting log_loss to be called with a single column of label-encoded predictions, or four columns of class probabilities? Because I believe the former won't work, as log_loss automatically assumes a 1-dimensional y_pred to be binary...
Like I said, I need to investigate some more, but I'd really appreciate you commenting any of your findings here!

Thanks for your quick reply!
Sure I tried setting do_predict_proba=True but it didn't help. Seems that it refused to accept multi-column predicts for some reason.
I have to say log_loss is a bit special 'cause it requires (n_samples,n_classes) y_pred, while other examples you tested before, I guess, forced the input y_pred to be 1 column.
Here is the code I used to test:
import numpy as np
import pandas as pd
from sklearn.datasets import make_classification
from sklearn.ensemble import RandomForestClassifier
from sklearn import metrics
from hyperparameter_hunter import Environment, CVExperiment, BayesianOptPro

# make a toy dataset
x,y = make_classification(n_samples=1000,n_classes=4,n_informative=10)
train_df = pd.DataFrame(x, columns=range(x.shape[1]))
train_df["y"] = y

'''
TEST 1
metrics=["log_loss"]
do_predict_proba=False

ValueError: y_true and y_pred contain different number of classes 4, 2.
Please provide the true labels explicitly through the labels argument. Classes found in y_true: [0 1 2 3]
'''
env1 = Environment(
    train_dataset=train_df,
    results_path="HyperparameterHunterAssets",
    target_column="y",
    metrics=["log_loss"],
    do_predict_proba=False,
    cv_type="StratifiedKFold",
    cv_params=dict(n_splits=5, random_state=32),
    verbose=1,
)

'''
TEST 2
metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3]))
do_predict_proba=False

ValueError: The number of classes in labels is different from that in y_pred.
Classes found in labels: [0 1 2 3]
'''
env2 = Environment(
    train_dataset=train_df,
    results_path="HyperparameterHunterAssets",
    target_column="y",
    metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3])),
    do_predict_proba=False,
    cv_type="StratifiedKFold",
    cv_params=dict(n_splits=5, random_state=32),
    verbose=1,
)

'''
TEST 3
metrics=["log_loss"]
do_predict_proba=True

ValueError: Wrong number of items passed 4, placement implies 1
'''
env3 = Environment(
    train_dataset=train_df,
    results_path="HyperparameterHunterAssets",
    target_column="y",
    metrics=["log_loss"],
    do_predict_proba=True,
    cv_type="StratifiedKFold",
    cv_params=dict(n_splits=5, random_state=32),
    verbose=1,
)

'''
TEST 4
metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3]))
do_predict_proba=True

ValueError: Wrong number of items passed 4, placement implies 1
'''
env4 = Environment(
    train_dataset=train_df,
    results_path="HyperparameterHunterAssets",
    target_column="y",
    metrics=dict(logloss=lambda y_true, y_pred: metrics.log_loss(y_true, y_pred, labels=[0,1,2,3])),
    do_predict_proba=True,
    cv_type="StratifiedKFold",
    cv_params=dict(n_splits=5, random_state=32),
    verbose=1,
)

experiment = CVExperiment(
    model_initializer=RandomForestClassifier,
    model_init_params=dict(n_estimators=10),
)

@chwang1991,
Thanks for posting your sample code! It's very helpful! Sorry for the delay, but I've been busy with other things lately. I'm looking at this issue again today, and I have to agree with you log_loss does seem rather weird. Although I may just be thinking that because I haven't done too much experimentation with other metrics.
Do you know of any other metrics that behave similarly or might cause other problems?
Also, do you think that another Environment kwarg might be necessary to clear up behavior in situations like this? do_predict_proba seems like half of the solution... But I'm thinking we need one kwarg to declare how predictions should be passed to metrics, then a second to declare how predictions should be saved in a situation like this. I'd love to hear your thoughts!

@HunterMcGushion
Sorry for my late reply, bit busy these days...
I think there are only two metrics that accept multi-column predicted probabilities: log_loss and hinge_loss. I think do_predict_proba is enough, as you already indicated in the document:

If True, it will call models.Model.model.predict_proba(), and the values in all columns will be used as the actual prediction values

I know in most cases there is no need to take proba into consideration, even logloss is mostly applied as loss function rather than metric, but in my recent case I have to evaluate how much "confidence" the model has in the results so I can improve it.


Remove watson from the files/folders name or replace it with speech

We can use Watson speech to text/text to speech. We need to either add ibm at the beginning or remove watson and use the legal names which are Speech to Text and Text to Speech.

@germanattanasio can you be more specific about this issue? thank you

sent you an email


Rework from Size animations to Scale animations, add StackAlignment + StackDensity

This PR contains several changes:

Rework to use Scale instead of Size for resizing middle and back cards.
The current Size method worked fine for images, but when embedding text in cards it caused issues do to text wrap as the container was resizing. I've reworked the resizing to use Scale animations instead.

Added Stack Alignment & StackDensity
In the current implementation there's no way to change how the stack looks. Cards are always on top of each other, with the middle and back cards sticking out at the bottom of the widget.
With StackAlignment you can change where the middle and back cards peek out.
With StackDensity you can change how much the middle and back cards stick out.

I've tried to maintain as much similarity to the old (Size) resizing as possible, but it might introduce minor visual changes, so I would flag this as a breaking change.

I'm closing this PR as it as deviated from the original package by a substantial amount and would cause too many breaking changes in dependend apps/packages.


CRUD operations to be created

Hi Pep,
Could you please create the missing CRUD operations for all the services?
Thanks!

Hi Vik,
CRUD operations has been created and pushed in additional branch.
Please review and update accordingly.
Thank you.


[Feature Request] PEP 612 support

Hey bear~d~ lovers! This was definitively not an obscure reference
The start of a journey
The other day I designed a decorator that adds one parameter to a function. I know the following example is silly but bear with me:
def with_secret(fct):
    def wrapped(*args, **kwargs):
        return fct("p4ssw0rd", *args, **kwargs)
    return wrapped

def guess_size(secret, size):
    return len(secret) == size

assert guess_size(6) == False
assert guess_size(8) == True

With type hints
Adding the extra parameter as first positional parameter was no coincidence: I am limited by PEP 612. Which gives the following code with type hints everywhere:
from typing import Callable, Concatenate, ParamSpec, TypeVar

P = ParamSpec("P")
T = TypeVar("T")

def with_secret(fct: Callable[Concatenate[str, P], T]) -> Callable[P, T]:
    def wrapped(*args: P.args, **kwargs: P.kwargs) -> T:
        return fct("p4ssw0rd", *args, **kwargs)
    return wrapped

@with_secret
def guess_size(secret: str, size: int) -> bool:
    return len(secret) == size

Mypy is happy, therefore I am. Rejoice!
Where I try to fix things
However, inspect.signature as well as typing.typing.get_type_hints look sad, therefore I am.
>>> signature(guess_size)
<Signature (*args: P.args, **kwargs: P.kwargs) -> ~T>
>>> get_type_hints(guess_size)
{'args': P.args, 'kwargs': P.kwargs, 'return': ~T}

Adding functools.wraps is a good step forward, but the extra parameter appears:
>>> signature(guess_size)
<Signature (secret: str, size: int) -> bool>
>>> get_type_hints(guess_size)
{'secret': <class 'str'>, 'size': <class 'int'>, 'return': <class 'bool'>}

I cry, then persevere:
from functools import wraps
from inspect import signature

def with_secret(fct: Callable[Concatenate[str, P], T]) -> Callable[P, T]:
    @wraps(fct)
    def wrapped(*args: P.args, **kwargs: P.kwargs) -> T:
        return fct("p4ssw0rd", *args, **kwargs)

    sig = signature(fct)
    parameters = tuple(sig.parameters.values())

    # fix signature
    # see https://github.com/python/mypy/issues/12472 about the ignore below
    wrapped.__signature__ = sig.replace(  # type: ignore
        parameters=parameters[1:],
    )

    # fix annotations
    try:
        del wrapped.__annotations__[parameters[0].name]
    except KeyError:
        pass  # maybe the first parameter of fct has no type hint

    return wrapped

Now things seems better:
>>> signature(guess_size)
<Signature (size: int) -> bool>
>>> get_type_hints(guess_size)
{'size': <class 'int'>, 'return': <class 'bool'>}

Let the bear in
And now for the grand finale I introduce our bear friend:
from beartype import beartype

@beartype
@with_secret
def guess_size(secret: str, size: int) -> bool:
    return len(secret) == size

Alas! The bear is hibernating and does not react to the following calls:
>>> guess_size(None)
False
>>> guess_size("wrong type")
False

Note that changing the decorators order (beartype/with_secret) seems to work but prevents use cases such as the beartype decorator being added automatically.

At this point my guess is that the bear needs understanding and sympathy, and my decorator needs some more trickery.
Could you give a little help in awaking the bear so that invalid calls are roared at? :bear::speech_balloon:

OMG.  Cuddle up, cubs! Its @beartype time.
Sadly, I'm currently waist-deep in a critical issue with nested generics at issue #140. Because Murphy's Law means continual pain for those on the front lines of QA, ...yup, it's us again resolving that issue will probably consume the better part of the week and my last remaining hair follicles.
Please prod me with a hot butter-knife :butter: :fork_and_knife: in a week or two if I haven't managed to meaningfully respond to your stunning plea for help here. I promise to solve everything. Clearly, @beartype is badly at fault here:
>>> guess_size(None)
False  # <-- wut?
>>> guess_size("wrong type")
False  # <-- WUT!?!?

In theory, @beartype explicitly handles decorated callables wrapped by @functools.wraps. In practice, there's a landmine field of edge cases around every dark corner. You appear to have stumbled into that dark corner. :expressionless: :exploding_head: :boom:

Quoted for truth.

I cry, then persevere:

Let us both cry and persevere together, then. Having vanquished critical issues left and right in #140 and #142, we proceed alone to the Summit: this issue, which will almost certainly take a turn for the worst and leave me stranded without a snow shovel as I plaintively cry to the frigid heavens above Canada.
In other words, this is our next and final action item for beartype 0.11.0. Rejoice!
Please, Stop Talking
Very well... I now type something meaningful.
After having thoroughly investigated this for one minute, I can confirm that @beartype's issue with your magically dark decorator is that you are probably not repairing everything properly. Notably, @beartype still believes that the size parameter is the second rather than first parameter.
Witness this verbose debug output:
from beartype.typing import Callable, Concatenate, ParamSpec, TypeVar
from functools import wraps
from inspect import signature

P = ParamSpec("P")
T = TypeVar("T")

def with_secret(fct: Callable[Concatenate[str, P], T]) -> Callable[P, T]:
    @wraps(fct)
    def wrapped(*args: P.args, **kwargs: P.kwargs) -> T:
        return fct("p4ssw0rd", *args, **kwargs)

    sig = signature(fct)
    parameters = tuple(sig.parameters.values())

    # fix signature
    # see https://github.com/python/mypy/issues/12472 about the ignore below
    wrapped.__signature__ = sig.replace(  # type: ignore
        parameters=parameters[1:],
    )

    # fix annotations
    try:
        del wrapped.__annotations__[parameters[0].name]
    except KeyError:
        pass  # maybe the first parameter of fct has no type hint

    return wrapped

from beartype import BeartypeConf, beartype

# @beartype
@beartype(conf=BeartypeConf(is_debug=True))
@with_secret
def guess_size(secret: str, size: int) -> bool:
    return len(secret) == size

The @beartype(conf=BeartypeConf(is_debug=True)) line is key here. That enables debug-friendly output, printing the definition of the type-checking wrapper function that @beartype generates on your behalf. Maniacal drum-roll, please! This output is...
(line 0001) def guess_size(
(line 0002)     *args,
(line 0003)     __beartype_func=__beartype_func, # is <function guess_size at 0x7fb8d022ecb0>
(line 0004)     __beartype_get_violation=__beartype_get_violation, # is <function get_beartype_violation at 0x7fb8d0060700>
(line 0005)     **kwargs
(line 0006) ):
(line 0007)     # Localize the number of passed positional arguments for efficiency.
(line 0008)     __beartype_args_len = len(args)
(line 0009)     # Localize this positional or keyword parameter if passed *OR* to the
(line 0010)     # sentinel "__beartype_raise_exception" guaranteed to never be passed.
(line 0011)     __beartype_pith_0 = (
(line 0012)         args[1] if __beartype_args_len > 1 else
(line 0013)         kwargs.get('size', __beartype_get_violation)
(line 0014)     )
(line 0015)
(line 0016)     # If this parameter was passed...
(line 0017)     if __beartype_pith_0 is not __beartype_get_violation:
(line 0018)         # Type-check this passed parameter or return value against this
(line 0019)         # PEP-compliant type hint.
(line 0020)         if not isinstance(__beartype_pith_0, int):
(line 0021)             raise __beartype_get_violation(
(line 0022)                 func=__beartype_func,
(line 0023)                 pith_name='size',
(line 0024)                 pith_value=__beartype_pith_0,
(line 0025)             )
(line 0026)
(line 0027)     # Call this function with all passed parameters and localize the value
(line 0028)     # returned from this call.
(line 0029)     __beartype_pith_0 = __beartype_func(*args, **kwargs)
(line 0030)
(line 0031)     # Noop required to artificially increase indentation level. Note that
(line 0032)     # CPython implicitly optimizes this conditional away. Isn't that nice?
(line 0033)     if True:
(line 0034)         # Type-check this passed parameter or return value against this
(line 0035)         # PEP-compliant type hint.
(line 0036)         if not isinstance(__beartype_pith_0, bool):
(line 0037)             raise __beartype_get_violation(
(line 0038)                 func=__beartype_func,
(line 0039)                 pith_name='return',
(line 0040)                 pith_value=__beartype_pith_0,
(line 0041)             )
(line 0042)
(line 0043)     return __beartype_pith_0

Specifically, there's your problem:
(line 0011)     __beartype_pith_0 = (
(line 0012)         args[1] if __beartype_args_len > 1 else
(line 0013)         kwargs.get('size', __beartype_get_violation)
(line 0014)     )

Specifically, @beartype incorrectly believes that the size parameter still has the positional index of 1 (i.e., args[1]) in the parameter list. Sadly, it no longer does. Since your magically dark decorator mostly just defers to the standard library to perform its magical darkness, the standard library is probably at fault here.
Specifically, this statement does not appear to be having the intended effect of fully deleting the first secret parameter:
    wrapped.__signature__ = sig.replace(  # type: ignore
        parameters=parameters[1:],
    )

Why. Oh Gods Why.
Okay. Bear with me, plucky bear cubs. :bear:
For both efficiency and robustness, @beartype generally ignores the inspect module. Sometimes, the inspect module knows what it's talking about. Mostly, it doesn't. Moreover, even when the inspect module does know what it's talking about, it's absurdly slow to do so. And as we know, @beartype don't go slow.
What I'm trying to say is that @beartype Goes Its Own Way (BGIOW). We actually wrote our own hyper-fast pure-Python function argument parser. It's a stupidly overtuned generator called iter_func_args() that we profiled into the ground – and then we profiled it again. It's almost certainly the fastest argument parser for Python in pure-Python. You know. Just sayin'. Kinda proud of our Bad Boy Arg Parser.
But it wasn't always this way. Oh, no. Previously, @beartype actually did defer to the inspect module. We stopped doing that in beartype 0.10.0. The argument parsing performed by inspect turned out to be the main performance bottleneck in the @beartype decorator. That was bad. So, we wrote our own argument parser.
Weep for us.
Is This Where I Come In?
It is.  Maniacal drum-roll anyway! :drum:
@beartype efficiently parses function arguments by inspecting code objects. For example, here's how @beartype inspects the total number of optional and mandatory non-keyword-only parameters accepted by a function:
    args_len_posonly_or_flex = func.__code__.co_argcount

In other words, @beartype just performs a trivial constant-time O(1) lookup of the poorly documented co_argcount instance variable of the poorly documented __code__ instance variable of the func in question. It's stupidly fast.
@beartype ignores string-based function signatures entirely, because trying to parse string-based function signatures – even with a hand-rolled C parser, which no one should ever write in 2022 – would reduce @beartype to a crawl. We'd be as slow as our geriatric Maine Coon on an all-night catnip bender.
Do we all see the problem inherent in @beartype's code object-based approach? Usually, there are no problems inherent in that approach. But if everyone starts writing magically dark decorators that modify the string-based signatures of functions without also modifying the underlying code objects implementing those functions, then @beartype is suddenly in the Terror Zone.
Because the string-based signature has become desynchronized from the code object underlying your decorated function, @beartype no longer correctly generates the expected type-checking wrapper.
And... I'm Passed Out Drooling on My Trackball Now
Yes. We are all right there with you – all two of us who are still reading this.
I know you're out there... somewhere.
Ultimately, what's needed here is for your magically dark decorator to repair the underlying code object of the decorated function as well. Unfortunately, that appears to be hard. Python sensibly prohibits runtime modifications to code objects, so we can't just trivially monkey-patch the existing code object itself: e.g.,
>>> def yam(): pass
>>> yam.__code__.co_argcount = 1
Traceback (most recent call last):
  Input In [2] in <cell line: 1>
    yam.__code__.co_argcount = 1
AttributeError: readonly attribute

</gulp>
The only possible recourse you have left is to dynamically generate a wrapper function. That is to say, rather than simply generically defining a one-size-fits-all wrapper function like this:
    def wrapped(*args: P.args, **kwargs: P.kwargs) -> T:
        return fct("p4ssw0rd", *args, **kwargs)

...you'd need to instead dynamically generate one unique wrapper function for each decorated function like this:
    from beartype._util.func.utilfuncmake import make_func
    wrapped = make_func(...)  # <-- Don't bother, honestly.

This is actually what @beartype does. This is not what most decorators do, however. Why? Mostly, it's hard. Also, kinda a waste of time for everybody other than us.
You Can Fool Some of the...

You can fool some of the static type checkers all of the time.
You can fool all of the static type checkers some of the time.
You can fool all of the static type checkers all of the time.
But you cannot fool @beartype any of the time.

@beartype's greatest asset is its greatest weakness here.
You want to fool type checkers here. You can easily fool static type checkers, because static type checkers can't properly infer types even for simple honest code that's not trying to actively deceive them. But @beartype?
You can't fool @beartype. @beartype sees all and knows all. @beartype is the megalomaniacal Sauron Eye Tower of Pythonic typing.

pretty much @beartype
Therefore, @beartype must begin deceiving itself.  If @beartype grokked PEP 612, my keyboard would still have working keys. Alas, here we are.
The real solution, therefore, is for @beartype to support PEP 612. This won't be easy. Fooling yourself never is. Our function argument parser will need to be cybernetically augmented... somehow.
But how do we even detect PEP 612 from within a runtime type-checker? I... I'm not sure we even can feasibly do that. After all, when we write a decorator pancake stack like this...
@beartype
@with_secret
def guess_size(secret: str, size: int) -> bool:
    return len(secret) == size

The @beartype decorator never actually sees the @with_secret decorator; @beartype only sees the wrapped closure created and returned by that decorator. But the PEP 612-compliant Callable[Concatenate[str, P], T] type hint is annotated on the fct parameter of @with_secret! The wrapped closure that @beartype sees isn't annotated by anything useful.
In other words, the PEP standards process made yet another standard that seems to be functionally useless at runtime. This is why my palms are now permanently attached to my face.

IT WAS ALL FOR NOTHING THEN!!!
...heh. Another GitHub issue amounts to diddly squat.
Nonetheless, let's pretend that we can actually do something about this by leaving this issue permanently open in a shambollic zombie state that harmfully attracts drama, angry memes, and fruitless debates about Season 4 of Stranger Things.

Oh my! Yet an other lovely novel to read with a favourite beverage on hand. Last time I did that, it was @beartype's readme which got me entertained for a while. The alchemy of obscure words coming from a country known for its 2018 indie platformer interleaved with code snippets got me in a state of awe, which explains that I don't remember that PEP 612 was not in the list of supported PEPs. Either that or I was tipsy from the aforementioned beverage. But I think it definitively was the charming words to my non-native ears. Definitively.
On an unrelated note: have you tried getting in touch with the development of the Python language? If there is some feature missing for dynamic type checkers, maybe writing a PEP could be a long-term alternative to black magic (or call stack inspection, whatever you want to name it)? Maybe it's because of your reverse-psychology about PEP 563, but looking back to the related Pydantic case makes me think that maybe things would be for the better if dynamic-typing library authors were more involved in PEPs & stuff. But that's just wishful thinking of a peasant here, I am of course in no place to suggest anything, especially how you use your time. One thing is sure though: I would be delighted to read any PEP you may write since you obviously have a thing for captivating documentation.
I know realise that my whole message amounts no nothing else that sending positive waves your way in hopes that you continue doing what you do best, whatever that may be. It is high time I add something somewhat constructive so here I go: I am in no hurry of having PEP 612 supported by @beartype, as I'm not expecting to deploy impacted code anywhere for at least a few months. So there is no rush to include this in 0.11.0 as far as I'm concerned. That's it, I will stop wasting any more of your precious time now, until next time!

...country known for its 2018 indie platformer...

A fellow gentleman of culture, I see. I instinctively knew that you (of course) referred to the modern monument to Canadian suffering that is Celeste – despite having never played Celeste. Why? Because... this. is. Canada.

Horrifying West Coast mountain ranges literally embodying our constant struggle with wintertime depression are in our collective DNA here. Although I myself grapple with PEP Standards Angst, pretty sure it's a thing my Dad wrestled the shadowy demon of depression his entire adult life.
In honour of him, Celeste is always a thing I wanted to 100% – B-sides, C-sides, and all. This 1:35-minute run of the Chapter 7: The Summit C-side gets me every time. There is anguish implicit in that run.
When I was a mere scruffy ruffian, only Mega Man 2 Wily's Fortress: Stage 3 was well-known by pale-faced, thin-wristed millennials the world over to harbour such devilish wall spike level design yet unmatched by mankind. Like, seriously – that cluster of three fall-into-narrow-wall-spike-chimney screens at the 1:00-minute mark still engenders a nostalgic shudder of bittersweet hatred "joy."
Then Celeste happened and invalidated all my childhood. :anger:

...have you tried getting in touch with the development of the Python language?

 I jest, of course. Alas, Guido and whatever resident Python BFDL is currently wearing the Guido Mask don't necessarily align with runtime type-checking. Python's established dev culture isn't exactly opposed to runtime per say – but ignoring runtime kinda does constitute a kind of opposition, doesn't it? It's like a "lie by omission." Technically, that's not a lie. Pragmatically, that's pretty much a lie.
It's true. I could vociferously argue while pounding my fists in the general direction of the Steering Council. But over the last tumultuous 40-oddball years, I've learned that humans don't particularly respond to logical argumentation that contradicts cherished assumptions; humans only respond to action. Therefore, I act. I contradict cherished assumptions by creating something that, by all accounts, shouldn't exist.
That's actually how I derive most of my fun here. I'm anti-authoritarian by nature. Honestly, I blame childhood poverty in Los Angeles. That's pretty much the breeding ground for anti-authoritarian dispositions right there.
So, I love doing things I shouldn't. Runtime type-checking in Python is a thing no one should do, because:

It feels NP-hard – and probably is.
It feeds on continual dark magic. Implementing standards never intended to be implemented requires:

Exploiting deep flaws in the CPython runtime.
Violating privacy encapsulation in the standard library.
Circumventing perpetual roadblocks with eval-based Aikido throws.
Giggling incoherently to myself as tests pretend to finally pass.

It means subverting community expectations, standards bodies, and multinational corporations – all of which have gone all-in on static type-checking to the exclusion and detriment of runtime type-checking.
There's utterly no fame, fortune, or tangible incentive in it (because prior point).

Like, seriously. The Big Three (so: Google, FaceBook Meta, and Microsoft) each created their own ad-hoc unofficial third-party static type-checker for Python – none of which work particularly well and all of which argue with one other and Python's official first-party static type-checker mypy about everything. Really? Nobody bothered to ever consider runtime, even though it's ultimately only runtime and not "static analysis time" that matters. Really? Yet, it happened. It's sorta unbelievable when you put it in that deadpan historical context.
Basically, it's a one-bear war against QA injustice that we prosecute here. That framing may sound obnoxiously unhealthy (and probably is), but it's the funn(i)est thing I've ever done. Indeed! It's the only thing I've ever done that's consistently captured my undivided attention without any expectation of extrinsic reward.
@beartype is 100% intrinsic reward. We're here because we make code better, despite the world. Fun rapidly ensues. Roar, bear. Roar! :bear:

...looking back to the related Pydantic case makes me think that maybe things would be for the better if dynamic-typing library authors were more involved in PEPs & stuff.

You're absolutely right. Pydantic maintainers and collaborators became heavily involved, averting the obvious pending crisis that was obvious to everyone except CPython devs.
But... Pydantic's popular. Pydantic fuels FastAPI (ironically, despite being slow-as-molasses), which fuels over 230 downstream dependencies. These include friggin' Pycharm, which comes bundled with a FastAPI project type out-of-the-box.
Meanwhile, @beartype quietly lumbers about in the background.
But, really? I just don't like arguing with people. That's the core low-level issue here. Ultimately, it's me. Can't deflect blame on that one. You know that Little Simz mic-drop Sometimes I Might Be Introvert from a year or so ago? Let's pretend you do. Well...
I like violating expectations by implementing things at runtime. The human side of that equation is equally critical – but it repulses me, because always I am introvert.

I am in no hurry of having PEP 612 supported by @beartype...

:relieved:

...as I'm not expecting to deploy impacted code anywhere for at least a few months.

:disappointed_relieved:
Okay. I tell you what we are going to do.
For you, we'll do something. PEP 612 is a bit beyond even the immediate horizon of the next several months. But fear not! I see that you are munging the PEP 362-compliant func.__signature__ dunder instance variable up above:
    wrapped.__signature__ = sig.replace(  # type: ignore
        parameters=parameters[1:],
    )

That's wonderful. Surprisingly, that's standardized. Equally surprisingly, that requires no risky call stack inspection on @beartype's part. Instead, @beartype should be mildly refactored to obey the algorithm outlined by PEP 362:

If the callable being decorated by @beartype defines the func.__signature__ attribute, @beartype should parse arguments from that signature. This should be mostly trivial. Rejoice! The inspect.Signature API is object-oriented, sane, and readable.
Else, @beartype should parse arguments from the code object underlying the decorated callable. We already do this. Rejoice again!

Rejoice is what I'm saying. Oh, and gently prod me if I neglect this. You need this, so I need and want to do this. Also, it sounds fun. Right? Let's do even more things we're not supposed to, everyone! :partying_face:

Note that changing the decorators order (beartype/with_secret) seems to work but prevents use cases such as the beartype decorator being added automatically.

So is this the automatic decoration of entire modules the only thing that is holding @beartype back from full support of PEP 612? In other words, if you manually write your @beartype decorators every time, is it safe to say @beartype supports PEP 612?
I have run into this issue with the [Any, ...]s many times and never even knew there was a PEP for it until reading this issue. Definitely like the idea of @beartype supporting this.
Although now that I think of it, really the only time I write nontrivial decorators is when I'm testing some kind of nonexistent experimental feature for @beartype.

Belated reply arrives... belatedly.
Let's admit this has been a busy summer and we'll agree to leave it at that. Thankfully, tomorrow is lakeside kayaks and trailside bicycles under a baking hot sun all day. Thank you, sun. We give thanks in Canada for your infrequent existence. :sun_with_face:
In other news...

So is this the automatic decoration of entire modules the only thing that is holding @beartype back from full support of PEP 612?

Depends on what we mean by "full support of PEP 612," right?
Ideally, that should mean actual support for deep runtime type-checking typing.ParamSpec(...) and typing.Concatenate[...] type hints. Pragmatically, the convenient fact that @beartype type-checks at runtime does kinda mean we can wildly wave our hands around and pretend we're doing something we're actually not.
Actual PEP 612 support is definitely still on the plate. But PEP 362 support via the func.__signature__ dunder variable is deliciously easier and achieves similar (but arguably even more useful) goals... So, we'll probably run over that goalpost first.
Until then, please reorder your decorator chains is what I'm saying. @beartype demands precedence, because it's jerkish. At least @beartype isn't snuffling around in your backyard composter – unlike some bears and raccoons I could mention. :face_exhaling:
The Shape of What Is to Come
Incidentally, I've fully implemented (but have yet to actually test) import hooks.
Once this lands in beartype 0.11.0 or 0.12.0, you'll be able to trivially @beartype all callables and classes across your entire app stack or Python process with this two-liner at the top of your {package_name}.__init__ submodule:
# Congrats. You just @beartyped literally everything. UwU
from beartype.claw import beartype_all
beartype_all()

Thanks as always, everyone, for being special. You're all awesome! You drive us to better @beartype and thereby better ourselves. :lotus_position_man: ⇐ you after @beartype