Handle file paths with whitespace

Before submitting a pull request, please make sure the following is done...

Fork the repo and create your branch from master.
If you've added code that should be tested, do a sanity check on vim8 and neovim
If you've changed APIs, update the README and documentation ./doc/prettier.txt

Please use the simple form below as a guideline for describing your pull request.
Thanks for contributing to vim-prettier

Summary
Wrap the path used for --stdin-filepath in quotes. This allows prettier to work with files that have whitespace in their paths.
references #108
Test Plan

Edit a file in a location with whitespace in the path (e.g., /Users/jason/Library/Mobile Documents/foo.md).
Run :Prettier.
Verify that prettier runs without error.

Thank you! Will test this and merge it ASAP

Merging this once builds pass


error on getting trans saturn planets

Hello,
If i try chart.get(const.SUN) it works fine, but if i try consts.NEPTUNE (uran, pluto), it throws me error:
from flatlib import const
from flatlib.chart import Chart
from flatlib.datetime import Datetime
from flatlib.geopos import GeoPos

date = Datetime('1991/01/01', '10:00', '+02:00')
pos = GeoPos('40n50', '03e62')
chart = Chart(date, pos)
print(chart.get(const.NEPTUNE).num())

Traceback (most recent call last):
  File "/home/milan/PycharmProjects/elboh_astro/venv/test.py", line 9, in <module>
    print(chart.get(const.NEPTUNE).num())
  File "/home/milan/.local/lib/python3.5/site-packages/flatlib/chart.py", line 92, in get
    return self.getObject(ID)
  File "/home/milan/.local/lib/python3.5/site-packages/flatlib/chart.py", line 72, in getObject
    return self.objects.get(ID)
  File "/home/milan/.local/lib/python3.5/site-packages/flatlib/lists.py", line 44, in get
    return self.content[ID]
KeyError: 'Neptune'

Process finished with exit code 1

Please try it and tell me if its error on my side or You can reproduce it. I don't see error in git or swiss ephemeris library constants, but on my side also not.
thanks :o)

Hello Zebyja,
I think when initiating the the chart object you need to set the list of objects you would like to use. The library, as configured bu default, uses traditional set of objects, see here in chart.py lines 46,47 and 48:
       # Handle optional arguments
       hsys = kwargs.get('hsys', const.HOUSES_DEFAULT)
       IDs = kwargs.get('IDs', const.LIST_OBJECTS_TRADITIONAL)
You would have to initiate your chart with IDs = const.LIST_OBJECTS
Regards,
Marek

Hello Marek,
thank you very much, it looks really hope.
Regards
Zebyja


Change project name from pyscript collective to PlanetPyScript

Checklist

[X] I added a descriptive title
[X] I searched for other issues and couldn't find a duplication

What is the issue/comment/problem?
Since this project is very much a work in progress a few PyScript folks thought the name PlanetPyScript might be cooler than PyScript Collective.
It was proposed by @ntoll and his inspiration came from https://planetpython.org/
What do you all think about the change?
Votes as 👍 or 👎 ?
Any other thoughts? Add it down here!

The hope is that the Collective is half work product (examples, Gallery) and half people (collaborators who onboard contributors into collaborators.) For me, the name "Collective" focuses on people, making it a more social endeavor.
I'm ok though with a different name.

I'm with Paul on this one.
Also, it's a cool name, but PlanetPython is really a news aggregator - not what we're doing here.

Alright, so I guess we don't.
Thanks folks.


new gyrification as surface area ratio

native over unfolded surface area

The gyrification metric is now the native surfarea divided by unfold surfarea, and the surfarea metric is also produced now..
Ran on one test subject and seems to work well -- the gyrification maps for the new variable density surfaces now have approx same values/range, so the value now does not depend on the density.
The 32k gyrification looks a little bit different from the others (maybe an artifact of the vertex density), but is proportional to the old gyrification maps (by a multiplicative constant), and the old maps are still available  if needed for backwards compatibility (they are just called 32k surfarea.shape.gii).. But I think we should just avoid the 32k density maps for surface-based features from now on..

closes #87


Fix Mobile Interface

The mobile interface is currently busted, especially on the home page.  The fix is that the website needs to be updated so that the footer doesn't float, but is actually a hard coded part of the page.

All fixed and merged back into Milestone 1.


Document Mixed Offline/Online Behavior

Can you document the behavior if the self-hosted (or public) backend is not available while hishtory is active during a shell session?  Will history events be relayed as soon as network connectivity returns?  Will errors be thrown while offline?
Thank you for an innovative capability.

Fixed in 1de0e60. https://blog.daviddworken.com/posts/hishtory-explained/ has the full details on how syncing works with going offline.
But the tl;dr is that it behaves optimally while offline: Saving history entries and relaying them once network connectivity returns.

Wow, this is a great explanation.  Thanks for posting it and for putting a really nifty tool out there.


az apim api create authorization-server-id does not take effect

This is autogenerated. Please review and update as needed.
Describe the bug
--authorization-server-id does not take effect when an API is created using Azure CLI
The API is created however the section for the authenticationSettings remains blank
  "authenticationSettings": {
    "oAuth2": null,
    "openid": null
  },

Should be
  "authenticationSettings": {
    "oAuth2":  "<oAuth2Provider>",
    "openid": null
  }

Of note, this was tested using az rest it did work when running against the CreateOrUpdate endpoint:
https://learn.microsoft.com/en-us/rest/api/apimanagement/current-ga/apis/create-or-update?tabs=HTTP
Where this property is set at: authenticationSettings
Command Name
az apim api create
Errors:
No error reported

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Create a standard tier API Management instance
Configure the Oauth2 Provider as documented here: https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-oauth2#configure-an-oauth-20-authorization-server-in-api-management
az apim api create --resource-group {} --service-name {} --api-id {} --path {} --authorization-server-id {oAuth2Provider} --display-name {} --protocols {} --service-url {}

Expected Behavior
When --authorization-server-id is set the resulting API created should have an entry like this and the authentications set properly
  "authenticationSettings": {
    "oAuth2":  "<oAuth2Provider>",
    "openid": null
  }

Environment Summary
Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.31, Ubuntu 20.04.5 LTS
Python 3.10.8
Installer: DEB

azure-cli 2.44.1 *

Extensions:
application-insights 0.1.17
account 0.2.5

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

Adding Service team to look into this.
@adrianhall, @KedarJoshi Could you please look into this once you get a chance ? Thanks in advance.

Currently, the CLI command requires --authorization_scope parameter to be not empty for setting authorization server. I've created a PR on make scope parameter optional https://github.com/Azure/azure-cli/pull/27555


Add an Experiment class

Summary
Add an Experiment class where the user can define all thing related to the specific set up of an experiment, including:

initial conditions
cycling profile
SOC to concentrations calculator
cooling set up?

Feel free to suggest other things that should be in this
Motivation
Performing different experiments on models will be one of the main use cases of PyBaMM so we should have a clear and simple method for setting this up.

Some experiments (GITT, HPPC...) are based on applying pulses to the battery. This can be easily implemented as a time dependent current, but it would be interesting to include a pulse function so it is friendly to users who are not used to coding. This can be helpful when including it in the GUI.


Cilium has issues with kubevirt specifying a custom interface MAC

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Use case: I have a k3s/cilium cluster with kubevirt. If kubevirt VMs run in a bridge mode with a force specific mac address then cilium is lost about the pod's mac. I have to force a static MAC because otherwise the guest VMs' cloud-init is unhappy about seeing a brand new eth0 and bails out. #19789 was – supposedly – going to fix this in a general way but it looks dead.
kubevirt network config:
          interfaces:
          - bridge: {}
            macAddress: ea:4b:c2:ab:2b:1e
            name: default

guest$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::e84b:c2ff:feab:2b1e  prefixlen 64  scopeid 0x20<link>
        ether ea:4b:c2:ab:2b:1e  txqueuelen 1000  (Ethernet)
        RX packets 36  bytes 4445 (4.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13  bytes 1166 (1.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

guest$ tcpdump -nvve icmp
tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
09:14:12.317772 ea:4b:c2:ab:2b:1e > fe:96:9e:22:f1:42, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 42818, offset 0, flags [DF], proto ICMP (1), length 84)
    <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 2, seq 15, length 64
09:14:12.324435 fe:96:9e:22:f1:42 > ea:4c:59:c8:64:25, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 117, id 0, offset 0, flags [none], proto ICMP (1), length 84)
    <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 2, seq 15, length 64

You can see the returned ICMP is for ea:4c:59:c8:64:25 instead of ea:4b:c2:ab:2b:1e.
host$ cilium bpf endpoint list|grep 168
<IP_ADDRESS>:0                                id=3768  flags=0x0000 ifindex=171 mac=EA:4C:59:C8:64:25 nodemac=FE:96:9E:22:F1:42

I'm not sure how it'd work with endpoint delete because that one crashes:
host$ cilium bpf endpoint delete
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/cilium/cilium/cilium/cmd.glob..func5(0x3b047a0?, {0x40a0430, 0x0, 0x0?})
        /go/src/github.com/cilium/cilium/cilium/cmd/bpf_endpoint_delete.go:21 +0x138
github.com/spf13/cobra.(*Command).execute(0x3b047a0, {0x40a0430, 0x0, 0x0})
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:860 +0x663
github.com/spf13/cobra.(*Command).ExecuteC(0x3af9b20)
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:902
github.com/cilium/cilium/cilium/cmd.Execute()
        /go/src/github.com/cilium/cilium/cilium/cmd/root.go:36 +0x25
main.main()
        /go/src/github.com/cilium/cilium/cilium/main.go:15 +0x17
command terminated with exit code 2

Cilium Version
Client: 1.12.1 4c9a630 2022-08-15T16:29:39-07:00 go version go1.18.5 linux/amd64
Kernel Version
Linux h1 5.18.19 #1-NixOS SMP PREEMPT_DYNAMIC Sun Aug 21 13:18:56 UTC 2022 x86_64 GNU/Linux
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.4+k3s1", GitCommit:"c3f830e9b9ed8a4d9d0e2aa663b4591b923a296e", GitTreeState:"clean", BuildDate:"1970-01-01T01:01:01Z", GoVersion:"go1.18.5", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I stumbled on #21347 and while this one seems similar, I think a persistent MAC is much less disruptive to the setup than a persistent pod IP. It's somewhat unexpected that cilium tracks the mac addresses of the pod-side interfaces on its own.

If kubevirt VMs run in a bridge mode with a force specific mac address then cilium is lost about the pod's mac. I have to force a static MAC because otherwise the guest VMs' cloud-init is unhappy about seeing a brand new eth0 and bails out.

Could you provide more details here? What is this "branch new eth0"? What do you mean by "force specific mac address"?

The way kubevirt works it bridges the pod-side interface and the qemu's host-side interfaces. So what you see is:
tcpdump within the guest:
10:30:59.712668 ea:4b:c2:ab:2b:1e > 02:26:d6:b8:35:f2, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 44316, offset 0, flags [DF], proto ICMP (1), length 84)
    <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 21, length 64
10:30:59.717700 02:26:d6:b8:35:f2 > ca:8b:e4:05:ff:a9, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 117, id 0, offset 0, flags [none], proto ICMP (1), length 84)
    <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 1, seq 21, length 64

qemu guest:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::e84b:c2ff:feab:2b1e  prefixlen 64  scopeid 0x20<link>
        ether ea:4b:c2:ab:2b:1e  txqueuelen 1000  (Ethernet)
        RX packets 52  bytes 11985 (11.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 35  bytes 3099 (3.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pod network (nsenter into the pod):
eth0: flags=130<BROADCAST,NOARP>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        ether 92:40:8e:6a:1e:3e  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0-nic: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::49b:7bff:fe8f:e9e6  prefixlen 64  scopeid 0x20<link>
        ether 06:9b:7b:8f:e9:e6  txqueuelen 1000  (Ethernet)
        RX packets 216  bytes 58120 (56.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 219  bytes 20152 (19.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

k6t-eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::49b:7bff:fe8f:e9e6  prefixlen 64  scopeid 0x20<link>
        ether 06:9b:7b:8f:e9:e6  txqueuelen 0  (Ethernet)
        RX packets 46  bytes 4564 (4.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9  bytes 1369 (1.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::6c7d:7aff:fe84:2eef  prefixlen 64  scopeid 0x20<link>
        ether 6e:7d:7a:84:2e:ef  txqueuelen 1000  (Ethernet)
        RX packets 195  bytes 16981 (16.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 213  bytes 57737 (56.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

the bridge:
bridge name     bridge id               STP enabled     interfaces
k6t-eth0                8000.069b7b8fe9e6       no              eth0-nic
                                                        tap0

cilium's expectations:
# cilium bpf endpoint list|grep \\.96
<IP_ADDRESS>:0                                 id=256   flags=0x0000 ifindex=229 mac=CA:8B:E4:05:FF:A9 nodemac=02:26:D6:B8:35:F2

Kubevirt does some non-obvious things to the network in the pod:

it renames eth0 to eth0-nic (note how the dummy eth0 is DOWN).
it changes that interface's mac to be the same as of a newly created bridge.
at this point the original cilium-issued mac is irrevocably lost.
the rest seem to be reasonably harmless.

From the kubevirt's POV it seems that the expectation is that CNI will just do the ARP lookup and it will flow through the k6t-eth0 bridge. It works as expected from the pod's network ns:
# arping -I k6t-eth0 <IP_ADDRESS>
ARPING <IP_ADDRESS> from <IP_ADDRESS> k6t-eth0
Unicast reply from <IP_ADDRESS> [EA:4B:C2:AB:2B:1E]  0.876ms

It works fine with flannel because that's just one more bridge on top. I don't quite know why it works with calico and I don't have a calico CNI box at hand to try now.
I think that cilium's issue is that cilium absolutely expects the pod to never change its interface's MAC. I figured the issues with bpf endpoint delete and even when I delete the EP it comes back with the same cilium-issued mac.
A recap

my VM must have a stable MAC because otherwise cloud-init goes insane.
kubevirt can either masquerade the traffic (and then everything WAI, but all the VMs have the same internal IP <IP_ADDRESS>), or bridge the pod network.
in the latter case, kubevirt expects CNI to discover the pod's mac with arp. Cilium doesn't do that.

not stale


OpenUpwardsPageTransitionsBuilder is never used on P

OpenUpwardsPageTransitionsBuilder is never used on P
I am building for P build my breakpoint this line is never hit -> https://github.com/flutter/flutter/blob/1aedbb1835/packages/flutter/lib/src/material/page_transitions_theme.dart#L233
Instead this line is always called -> https://github.com/flutter/flutter/blob/1aedbb1835/packages/flutter/lib/src/material/page_transitions_theme.dart#L208
Route onGenerateRoute(RouteSettings settings) {
    switch (settings.name) {
      case SplashScreen.routeName:
        return MaterialPageRoute(builder: (context) => const SplashScreen(), settings: settings);
   }
  return null;
}

flutter doctor -v
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15 19A582a, locale en-BE)
    • Flutter version 1.9.1+hotfix.6 at /Users/vanlooverenkoen/flutter
    • Framework revision 68587a0916 (7 weeks ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/vanlooverenkoen/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • Xcode 11.0, Build version 11M382q
    • CocoaPods version 1.7.5

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] VS Code (version 1.39.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Android SDK built for x86 • emulator-5554                        • android-x86 • Android 9 (API 28) (emulator)
    • iPhone Xs                 • B8666846-82A3-4FC8-888E-41BF2DF0591A • ios         • com.apple.CoreSimulator.SimRuntime.iOS-13-0 (simulator)

! Doctor found issues in 1 category.

You have to set the PageTransitionsTheme to use that particular transition, since FadeUpwardsPageTransitionsBuilder is the current default. So, you would have to set the builder to use OpenUpwardsPageTransitionsBuilder in your MaterialApp's theme.

Then I do not understand this part of the documentation
/// Used by [PageTransitionsTheme] to define a vertical [MaterialPageRoute] page
/// transition animation that looks like the default page transition
/// used on Android P.

Currently the default behavior (which is expected) is that all Flutter apps on Android should be using the FadeUpwardsPageTransitionsBuilder.
Flutter, by default, uses the latest OEM behavior. This means that regardless of the Android version, we should be using the latest Android 10 page transitions. I'm currently working on a PR to implement to update the default, but it's causing more test failures than I expected so I intend to work through those failures when I have the time.

Hmm I should expect that every os version has the correct transition

My understanding is that this provides the benefit of having the latest interaction behaviors despite having an older OS (ie. Android P app being able to use Android 10 transitions and components for free).
Since this is working as intended, I'll close this issue for now. If you would like to raise this particular expectation of how behaviors should match OEM versions, you could file another issue regarding that topic and discuss your thought process behind those expectations.


[charts/redis-ha] don't kill container during sync

What this PR does / why we need it:
Consider the container healthy if redis sync is in progress with the master
Which issue this PR fixes

fixes #80

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@Eraac Sorry for the delay in reviewing this.
I thought by default if we don't get a PONG back we will fail? Let me triple check this.

@Eraac Sorry, I can't believe its been 24 days already... Getting this merged in now. Waiting for the tests!

@Eraac Sorry, I can't believe its been 24 days already... Getting this merged in now. Waiting for the tests!

@Eraac Sorry again, can you pull in master? Has some fixes for the CI.

@Eraac Sorry again, can you pull in master? Has some fixes for the CI.


[Bug] Broken Icons

Version
1.0.7
Reproduction link
https://demos.creative-tim.com/soft-ui-dashboard-pro/pages/dashboards/default.html
Operating System
Windows 10
Device
Asus ROG GL503VD
Browser & Version
Mozila Firefox latest
Steps to reproduce

Go to the Live Preview of Soft UI Dashboard Free or Pro.
The Icons of Font Awesome is broken.

What is expected?
Icons should be display
What is actually happening?
https://kit.fontawesome.com/42d5adcbca.js is forbidden

Solution
Additional comments

I am experiencing the same issue. The social button icons are not displaying.

Experiencing same issue. Drop Down icon become cross in square.

It problably means that the kit is expired somehow. Providing own FontAwesome handle or hosting FA yourself fixes the issue, so a fix would be to generate new kit to be expected by the live preview

@GusrifarisYudaAlhafis @laandrad @sn0wm1ku @Rottenland thank you for pointing out. Font Awesome became a Paid service so the solution would be to have the Official Bootstrap Icons itegrated: https://icons.getbootstrap.com/
We will integrate them in the next release.
Till then:

Replace the code from
 with <link rel="stylesheet"<EMAIL_ADDRESS>

Replace the icons where you have them  with

More icons istallation can be found here: https://icons.getbootstrap.com/#install
@dragosct @marqbeniamin please note this for future updates and we also need to check other products and replace the icons.
Best,
Alex


⚠ PrivateHD has degraded performance

In 5a36645, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 3979 ms

Resolved: PrivateHD performance has improved in 2f113d2.


chore: remove internal/scripts folder and move it to scripts.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

chore: remove internal/scripts folder and move it to scripts.

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.988%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2614

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.988%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2614

💛  - Coveralls


New interface to mode=x

Newer LuaTeX/luaotfload features use more mode= settings. Need to re-think the interface...

Some details about what is needed:
mode=XYZ allows to use a custom font reader/shaper. It works by calling a fonts.readers.XYZ function which then does the hard job. Currently we have as mode basic, node, harf (in luahbtex-harf) and plain (only as small example somewhere in luaotfload github). But it is possible to create more.
So some code is needed to declare a new mode  XYZ, and to call it so that it is used instead of mode=node. For the second part I'm currently using
\ExplSyntaxOn
\keys_define:nn {fontspec-renderer}
 {
  Renderer / harf .code:n =
   {
      \tl_set:Nx \l_fontspec_mode_tl {harf}
      \tl_gset:Nx \g__fontspec_single_feat_tl { mode=harf }
   }
 }

\ExplSyntaxOff

Beside this such a font reader perhaps wants to pass more info. In the special case of the harf reader, Khaled would like to pass AAT/Graphite etc to the underlying harfbuzz  e.g.  as mode=harf;shaper=AAT.

Thanks Ulrike, the extra detail is great. Are there an arbitrary number of options like shaper or is it a well-defined set for the time being? If arbitrary we could fall back on something like
Harfbuzz  % → `mode=harf`
Harfbuzz = {shaper=AAT}  % → mode=harf;shaper=AAT

If there's only one or two I'd be inclined to have
Renderer = Harfbuzz, Shaper = AAT

or if there is only shaper then even more abbreviated like
Renderer = Harfbuzz : AAT

The list of shapers is not fixed. Currently HarfBuzz supports ot, aat-coretext, graphite2 and fallback, and might add default and aat in the near future, and who knows what would happen long term. So I’d rather we have an interface that can be easily extended in the future. Note that the shapers are more or less the same thing as the /OT, /AAT and /GR font modifiers that XeTeX supports, so a unified interface for both might be a good ides.

@khaledhosny — I just realised that we shouldn't need something like
Renderer = Harfbuzz

since can't that be detected by the fact that the engine in use is luahbtex ? So if we assume that mode=harf can be automatically picked up, I would propose
Renderer = OpenType
Renderer = AAT
Renderer = Graphite
Renderer = Fallback
Renderer = Default
Renderer = <foo>  % ← uses `shaper=foo`

Is that right, or do we need to differentiate between luaotfload and Harfbuzz even in your forked engine?

Right now luahbtex is for all practical purposes the same as luatex with an additional luaharfbuzz module, so we can’t assume HarfBuzz is used (furthermore, one can build luaharfbuzz and use it with regular luatex. But I think the following mapping should work and is still backward compatible:
Renderer = Node     % mode=node
Renderer = Base     % mode=base
Renderer = HarfBuzz % mode=harf
Renderer = OpenType % mode=harf,shaper=ot
Renderer = AAT      % mode=harf,shaper=coretext_aat
Renderer = Graphite % mode=harf,shaper=graphite2
Renderer = <foo>    % mode=harf,shaper=foo

If we want to automatically detect if HarfBuzz can be used and enable it, then I probably need to turn luahbtex-harf into a proper LaTeX package and provide, say, an \ifharfbuzz check that can be used to conditionally turn on HarfBuzz support. The package would be responsible for checking the presence of luaharfbuzz module and gracefully handle its absence.

Also, related to this. Even if \defaultfontfeatures{Renderer=harf} is used (with @u-fischer code above), fontspec still seems to make many font definition calls without using mode=harf (see https://github.com/khaledhosny/luahbtex-harf/issues/30) and I think we need to make sure the mode is always passed.

I’ve pushed code for the Renderer but not yet looked into all of the “trial” font loading code. That might take me a little longer to get around to, sorry...

since can't that be detected by the fact that the engine in use is luahbtex ? So if we assume that  mode=harf can be automatically picked up, ...

even if the engine is luahbtex we can't assume that every font should be loaded in this mode.


PWA-grey back ground

https://docs.google.com/document/d/1GXSk0tJutfjnfblU_Z22d6Vuaychs7fmJeWaivopsVU/edit#
Documentation link Attached


Feature: Toggle Button for Wider Text Layout (Both Web and Desktop App)

Description:
Add a button to toggle a wider text layout (100 characters per line) when reading or editing a document. This would offer an alternative reading and editing experience, catering to users who prefer a wider text display.

Yes it would be nice to have a "view settings" where the reader can change cosmetic settings for their own needs and preferences, including font size, wider text layout, dark/light mode, and more


Add an option for a dev server to ignore EADDRINUSE

I have jest-puppeteer set up with a create-react-app project with the config.server option set to start the dev server. This works perfectly in CI 😊.
When locally developing, it's common to separately keep the dev server running in the background to keep a web page open with the latest changes. You then have to remember to close that server before running jest-puppeteer tests. It's not always practical to specify them to run on different ports.
Can the soon-to-be jest-dev-server server startup logic have an option to ignore?:
Error: listen EADDRINUSE <IP_ADDRESS>:3000
    at Server.setupListenHandle [as _listen2] (net.js:1342:14)
    at listenInCluster (net.js:1383:12)
    at doListen (net.js:1498:7)
    at process._tickCallback (internal/process/next_tick.js:114:19)
Emitted 'error' event at:
    at Server.emit (C:\Code\WebClient\node_modules\spdy\lib\spdy\server.js:237:40)
    at emitErrorNT (net.js:1362:8)
    at process._tickCallback (internal/process/next_tick.js:114:19)

Side benefit: setup of tests will be faster for not having to start up the dev server.

Oh, this is in user land. Never mind!


Use docker's ParseRepositoryTag when pulling

Docker 1.6 adds support for referencing images by their immutable digest, which is of the form <repo>@<digest>. Digests are of the form <algorithm>:<value>, and because they contain a :, parseImageName doesn't return the proper repo and tag_or_digest. This fixes that issue.

@smarterclayton PTAL

Note: this only pulls in the 1 file I need from docker/docker/pkg/parsers. If it makes life easier to pull in all of them, let me know.

I think it's ok to pull the one for now.
----- Original Message -----

Note: this only pulls in the 1 file I need from docker/docker/pkg/parsers. If
it makes life easier to pull in all of them, let me know.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/5558#issuecomment-82489916

LGTM. This is actually in my todo list. Thanks for fixing.

I believe this pull has stopped pods from scheduling at all on our e2e runs. The next run after this, the system add-on pods never get out of pending. This was the only pull, and the run before was clean. (cc @ixdy)

What docker version do you have on your nodes?
On Tue, Mar 17, 2015 at 6:16 PM Zach Loafman<EMAIL_ADDRESS>wrote:

I believe this pull has stopped pods from scheduling at all on our e2e
runs. The next run after this, the system add-on pods never get out of
pending. This was the only pull, and the run before was clean. (cc @ixdy
https://github.com/ixdy)
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5558#issuecomment-82621083
.

All of the Salt based configurations are locked to 1.5.0 currently. If you're going to modify that, please do it very early in the release cycle, like now (we just cut 0.13.0). Historically, docker revs take most of the release to shake out, and then some.
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cluster/saltbase/salt/docker/init.sls

I just wanted to make sure it wasn't some ancient version. Are you running
e2e on GCE?
On Tue, Mar 17, 2015 at 6:25 PM Zach Loafman<EMAIL_ADDRESS>wrote:

All of the Salt based configurations are locked to 1.5.0 currently. If
you're going to modify that, please do it very early in the release
cycle, like now (we just cut 0.13.0). Historically, docker revs take
most of the release to shake out, and then some.
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cluster/saltbase/salt/docker/init.sls
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5558#issuecomment-82623227
.

Yup.

Ok I'll take a look after dinner
On Tue, Mar 17, 2015 at 6:28 PM Zach Loafman<EMAIL_ADDRESS>wrote:

Yup.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5558#issuecomment-82623938
.

FWIW, I don't think we're against bumping Docker. It's just sometimes a bumpy ride.


one term per file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

48 of 58 (82.76%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.8%) to 89.045%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sis_provisioner/utils.py
22
23
95.65%

sis_provisioner/models.py
2
4
50.0%

sis_provisioner/management/commands/create_file.py
0
7
0.0%

Files with Coverage Reduction
New Missed Lines
%

sis_provisioner/utils.py
1
88.99%

Totals

Change from base Build<PHONE_NUMBER>:
-1.8%

Covered Lines:
317

Relevant Lines:
356

💛  - Coveralls


Support multiple templates per invocation

(fixes #149)
cc @asottile

I have a usability issue. There's poor interaction between -a/-i and positional template specification.
The issue is a commandline like cfn-lint -i E001 test.yml
Argparse parses this as two ignore rules, because the positional arguments are optional. You can fix parsing the usual way (cfn-lint -i E001 -- test.yml) but this would be very annoying.
We could fix this by making the positional argument mandatory. This would fix the above case but is a backwards compatibility break as discussed in #168. There would still be issues when specifying multiple files (cfn-lint -i E001 test.yml test2.yml) as the -a/-i would try to consume all but the last one, but I don't see a way around that.
cfn-lint has a few modes which don't require templates (update specs, update docs, list rules) which would be affected by this change. I propose those can be dealt with as special cases.
What do you think?

Other tools handle this by allowing an argument to be specified more than once:
cfn-lint -i E001 -i E002 -i E003

or to use commas and parse after-the-fact
cfn-lint -i E001,E002,E003

Following discussion in Slack:

Need the CLI to transition to supporting multiple templates slowly, so code editor integrations can catch up (so allow existing template specification methods to keep working)
A separate PR can be made to change how -r/-i/-a handling is done as per examples from asottile in previous comment

I'll open a new PR soon, because this one got a little side tracked. SIde note I'm going to be AFK for a few weeks soon so apologies in advance


HTTP Error 403 after Downloading Provider Redirect Page using Comcast_SSO on ABC

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
United States
Provide a description that is worded well enough to be understood
ABC locks certain shows behind a tv provider login. I have been using Comcast_SSO and my Comcast login to download ABC shows for half a year now. Today it is giving me an HTTP Error 403: Forbidden when yt-dlp is downloading the provider redirect page. AFAIK ABC is not DRM-protected, as I can still download episodes from a week ago (which are not locked behind the tv provider login).
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--ap-mso', 'Comcast_SSO', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', 'https://abc.com/episode/48ff9051-9242-4682-aeb8-020bd134d132/playlist/PL557226598']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds [6f9e65374] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-07-02-git-50f34172e0-full_build-www.gyan.dev (setts), ffprobe 2023-07-02-git-50f34172e0-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.07.04, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.35.5, urllib3-2.2.2, websockets-13.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1830 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-master-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds)
[Go] Extracting URL: https://abc.com/episode/48ff9051-9242-4682-aeb8-020bd134d132/playlist/PL557226598
[Go] PL557226598: Downloading webpage
[Go] vdka37498618: Downloading JSON metadata
[debug] Loading ap-mvpd.ABC from cache
[Go] VDKA37498618: Downloading Provider Redirect Page
ERROR: [Go] Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)
  File "yt_dlp\extractor\common.py", line 740, in extract
  File "yt_dlp\extractor\go.py", line 250, in _real_extract
  File "yt_dlp\extractor\adobepass.py", line 1448, in _extract_mvpd_auth
  File "yt_dlp\extractor\adobepass.py", line 1366, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 960, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 909, in _request_webpage

  File "yt_dlp\extractor\common.py", line 896, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 4165, in urlopen
  File "yt_dlp\networking\common.py", line 117, in send
  File "yt_dlp\networking\_helper.py", line 208, in wrapper
  File "yt_dlp\networking\common.py", line 340, in send
  File "yt_dlp\networking\_requests.py", line 365, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden

Per https://github.com/yt-dlp/yt-dlp/issues/516#issuecomment-2307679054 , it looks like some MSO providers are blocking the user-agent strings for older versions of Chrome that yt-dlp uses by default
You could try adding --user-agent "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" to your command
However if you get past the MSO provider login, then you may still run into #8073

Same problem this week with ABC.  Adding in the user-agent string did work.  Didn't run into #8073 in making this change.  At least with ABC.

I’m seeing something similar on both ABC and NBC. If I don’t use the user-agent, it just comes back with [403] Forbidden
[debug] Command-line config: ['-vU', '--write-subs', '--write-auto-subs', '--ap-mso', 'Comcast_SSO', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', 'https://abc.com/episode/7616024b-f0bd-4225-be2e-61abfaa5d381/playlist/PL553044961']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [e8e6a982a] (zip)
[debug] Python 3.11.2 (CPython aarch64 64bit) - Linux-6.6.47-v8-16k+-aarch64-with-glibc2.36 (OpenSSL 3.0.14 4 Jun 2024, glibc 2.36)
[debug] exe versions: ffmpeg 5.1.6-0 (setts), ffprobe 5.1.6-0
[debug] Optional libraries: Cryptodome-3.11.0, certifi-2022.09.24, requests-2.28.1, sqlite3-3.40.1, urllib3-1.26.12
[debug] Proxy map: {}
[debug] Request Handlers: urllib
[debug] Loaded 1832 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[Go] Extracting URL: https://abc.com/episode/7616024b-f0bd-4225-be2e-61abfaa5d381/playlist/PL553044961
[Go] PL553044961: Downloading webpage
[Go] vdka37633739: Downloading JSON metadata
[Go] VDKA37633739: Downloading Provider Redirect Page
ERROR: [Go] Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 740, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/go.py", line 250, in _real_extract
    auth = self._extract_mvpd_auth(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1448, in _extract_mvpd_auth
    provider_redirect_page_res = self._download_webpage_handle(
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1366, in _download_webpage_handle
    return super()._download_webpage_handle(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 960, in _download_webpage_handle
    urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 909, in _request_webpage
    raise ExtractorError(errmsg, cause=err)

  File "/usr/local/bin/yt-dlp/yt_dlp/networking/_urllib.py", line 398, in _send
    res = opener.open(urllib_req, timeout=self._calculate_timeout(request))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 525, in open
    response = meth(req, response)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 634, in http_response
    response = self.parent.error(
               ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 557, in error
    result = self._call_chain(*args)
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 749, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 525, in open
    response = meth(req, response)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 634, in http_response
    response = self.parent.error(
               ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 557, in error
    result = self._call_chain(*args)
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 749, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 525, in open
    response = meth(req, response)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 634, in http_response
    response = self.parent.error(
               ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 563, in error
    return self._call_chain(*args)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 896, in _request_webpage
    return self._downloader.urlopen(self._create_request(url_or_request, data, headers, query, extensions))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 4165, in urlopen
    return self._request_director.send(req)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/networking/common.py", line 117, in send
    response = handler.send(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/networking/_helper.py", line 208, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/networking/common.py", line 340, in send
    return self._send(request)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/networking/_urllib.py", line 403, in _send
    raise HTTPError(UrllibResponseAdapter(e.fp), redirect_loop='redirect error' in str(e)) from e
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden

Here’s some examples with the user-agent workaround:
[debug] Command-line config: ['-vU', '--write-subs', '--write-auto-subs', '--ap-mso', 'Comcast_SSO', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', '--user-agent', 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36', 'https://abc.com/episode/7616024b-f0bd-4225-be2e-61abfaa5d381/playlist/PL553044961']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [e8e6a982a] (zip)
[debug] Python 3.11.2 (CPython aarch64 64bit) - Linux-6.6.47-v8-16k+-aarch64-with-glibc2.36 (OpenSSL 3.0.14 4 Jun 2024, glibc 2.36)
[debug] exe versions: ffmpeg 5.1.6-0 (setts), ffprobe 5.1.6-0
[debug] Optional libraries: Cryptodome-3.11.0, certifi-2022.09.24, requests-2.28.1, sqlite3-3.40.1, urllib3-1.26.12
[debug] Proxy map: {}
[debug] Request Handlers: urllib
[debug] Loaded 1832 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[Go] Extracting URL: https://abc.com/episode/7616024b-f0bd-4225-be2e-61abfaa5d381/playlist/PL553044961
[Go] PL553044961: Downloading webpage
[Go] vdka37633739: Downloading JSON metadata
[Go] VDKA37633739: Downloading Provider Redirect Page
ERROR: [Go] Unable to extract post url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 740, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/go.py", line 250, in _real_extract
    auth = self._extract_mvpd_auth(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1490, in _extract_mvpd_auth
    provider_login_page_res = post_form(
                              ^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1395, in post_form
    post_url = self._html_search_regex(r'<form[^>]+action=(["\'])(?P<url>.+?)\1', form_page, 'post url', group='url')
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 1369, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags, group)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 1333, in _search_regex
    raise RegexNotFoundError(f'Unable to extract {_name}')

����������������������������������������������������������������������������������������������������������������������������������������������[debug] Command-line config: ['-vU', '--write-subs', '--write-auto-subs', '--ap-mso', 'Comcast_SSO', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', '--user-agent', 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36', 'https://www.nbc.com/the-wall/video/joel-and-suzanne/9000242414']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [e8e6a982a] (zip)
[debug] Python 3.11.2 (CPython aarch64 64bit) - Linux-6.6.47-v8-16k+-aarch64-with-glibc2.36 (OpenSSL 3.0.14 4 Jun 2024, glibc 2.36)
[debug] exe versions: ffmpeg 5.1.6-0 (setts), ffprobe 5.1.6-0
[debug] Optional libraries: Cryptodome-3.11.0, certifi-2022.09.24, requests-2.28.1, sqlite3-3.40.1, urllib3-1.26.12
[debug] Proxy map: {}
[debug] Request Handlers: urllib
[debug] Loaded 1832 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[NBC] Extracting URL: https://www.nbc.com/the-wall/video/joel-and-suzanne/9000242414
[NBC]<PHONE_NUMBER>: Downloading JSON metadata
[NBC]<PHONE_NUMBER>: Downloading JSON metadata
[debug] Loading ap-mvpd.nbcentertainment from cache
[NBC]<PHONE_NUMBER>: Downloading Provider Redirect Page
ERROR: [NBC]<PHONE_NUMBER>: Unable to extract post url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 740, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/nbc.py", line 212, in _real_extract
    query['auth'] = self._extract_mvpd_auth(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1490, in _extract_mvpd_auth
    provider_login_page_res = post_form(
                              ^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1395, in post_form
    post_url = self._html_search_regex(r'<form[^>]+action=(["\'])(?P<url>.+?)\1', form_page, 'post url', group='url')
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 1369, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags, group)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 1333, in _search_regex
    raise RegexNotFoundError(f'Unable to extract {_name}')

I’ll give my account if it helps get this straightened out.

I just tried it without the user-agent workaround as well, and that also seems to be working properly for me. Y’all rock. 👍👍

I still have to use a cookies file for downloading, even with the MSO config. How did you work around it?

My current working config is kinda simple, this is my .bash_aliases that still works:
alias ytget='yt-dlp --write-subs --write-auto-subs --remux-video mkv --cookies-from-browser chromium' #removed --embed-subs and --embed-chapters seems to burn in
alias ytgetmp4='yt-dlp --write-subs --write-auto-subs --remux-video mkv -S vcodec:h264,res,acodec:m4a --cookies-from-browser chromium' #removed --embed-subs and --embed-chapters seems to burn in
alias ytgetmp4-1080='yt-dlp --write-subs --write-auto-subs --remux-video mkv -S vcodec:h264,res:1080,acodec:m4a --cookies-from-browser chromium' #removed --embed-subs and --embed-chapters seems to burn in
alias ytgetcomcast='yt-dlp --write-subs --write-auto-subs --remux-video mkv --ap-mso Comcast_SSO --ap-username "someusername" --ap-password "somepassword"'
alias ytgetcomcast4='yt-dlp --write-subs --write-auto-subs --ap-mso Comcast_SSO --ap-username "someusername" --ap-password "somepassword"'
Hope that helps… sorry, I’m kinda newb myself.  The comcast lines are the ones I use to grab stuff related to this issue. Only real difference is the container, via “remux-video”

You're using cookies from browser.  Got it.


E2E kamelets.camel.apache.org "my-own-timer-source" already exists failure

Common checks are failing because of kamelets.camel.apache.org "my-own-timer-source" already exists

I'll look into it.

@squakez As far as I am concerned this issue is solved. I opened an issue about the recent e2e failure : #4774.


Character using multiple files

Describe your problem here.
How do i make a character out of multiple files? like there's up.png and up.png and etc

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

I do not recommend this, but, if you wish so, then my advice is you probably can.
Use a Lua script to change the poses in some way, not completely sure on how, but I'm sure it's possible.
You should probably just make a character comprising of one file, not several.

I do not recommend this, but, if you wish so, then my advice is you probably can. Use a Lua script to change the poses in some way, not completely sure on how, but I'm sure it's possible. You should probably just make a character comprising of one file, not several.

I mean yea, that could work, but this one specific character is MASSIVE, im not even sure if image that big is allowed to exist

Vs tricky done it


Refresh Switch Entity

Firstly, it works great as is, I got it plugged into HA with ease, thank you. But is there any way to force a refresh of the car without interacting with the drone mobile application? When I configured this, it showed the location of my vehicle at a place I was at like 3 weeks ago (the last time I opened the app to remote start).

You should be able to call the service "drone_mobile.refresh_device_status_[Vehicle Name With Spaces Replaced By Underscores]" in Home Assistant to trigger an update from the car as if you were opening the app. I usually call this before running any automations that I have set (like locking the doors at night) to ensure that they are in the status I expect them to be in. I kept this call separate from building it in to automations or status trackers, because there is a data limit for the API and I didn't want to get people blacklisted. ;) Also, this service call causes the drone mobile module in the car to wake up and use more power than it normally does, and I figured it would be best to allow a user to determine how fast they wanted to kill their car battery. :)

That being said, I am not paying for the GPS functionality, so if there is an issue with it not working correctly, I will need to get API payloads from someone that is paying for that functionality so I can figure out what's up with the API call.

Owner

I am, and the location appears to be functioning properly for me.


feat: support swagger 2.0 and JSON Schema draft 4 inputs

Description
This PR refactors some of the core input processor code and adds new schema models for draft 4 and swagger 2.0 schema.
One question you might have looking at this, "why not use already pre-defined types for these schemas?", well they are faulty and unprecise in most cases. This way we are sure on the content on the schemas files.
Related document for seeing which schema properties are related:

Related issue(s)
Related to #360
Fixes #86

Split out PR into 3:

https://github.com/asyncapi/modelina/pull/377
https://github.com/asyncapi/modelina/pull/378
https://github.com/asyncapi/modelina/pull/379


[issue-721] update Actor regex and parsing

The new logic follows this rule:
First, split off the ActorType part.
Then, if the last character in the string is a closing bracket and there exists a corresponding opening bracket, match everything between these two brackets as email and the rest of the string as name.
If the the last character is not a closing bracket, match the whole string as name.
I also added some more tests for this.
fixes #721

I think #721 is good. Thank you


(dbg, node, windows): run_node.bat failed

https://grpc-testing.appspot.com/job/gRPC_master/16208/config=dbg,language=node,platform=windows/console
1) channel watchConnectivityState should complete if a connection attempt is forced:
     Uncaught Error: The async function encountered an error
      at Error (native)

Looks like a flake because there are green builds before and after

Looks like this is passing consistently now.


Error with query

When I search for a query I got this:
{
"error": 500,
"msg": "please report this!",
"exc": "KeyError('damage_done',)"

}

Ok I see, I must update the API on my server


PlayerController: implement dropping down

If a player is on a jump-through platform with one-way collision box, they should be able to drop down somehow.
Consider Rolling Thunder game, where player presses down and PC vaults over the railing to drop to the lower level.

basic drop is done, along with pass-thru platforms.


Fix: prefect API not found

Changes

fixes api not found issue in prefect

Thank you for the PR 💜.


Feat/autorepeat rewind timeline

Auto-repeat rewind timeline action from:
KeyboardBinding.Triggered(UserActions.PlaybackNextFrame)
Now the timeline moves automatically when Shift+Left\RightArrowKey is pressed

Closing this for now.


Hello World Example Failed with clang++ as Complier

What version of gRPC and what language are you using?
gRPC version: v1.27.3; language: c++
What operating system (Linux, Windows,...) and version?
Raspberry Pi 4 (arm7vl), Raspbian GNU/Linux 10 (buster)
What runtime / compiler are you using (e.g. python version or version of gcc)
clang version 7.0.1-8+rpi3 (tags/RELEASE_701/final)
Target: armv6k-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
Selected GCC installation: /usr/bin/../lib/gcc/arm-linux-gnueabihf/8
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
My project requires clang++ to compile on raspberry pi, so I tested gRPC examples with clang++ instead of native g++. I changed the Makefile by replacing g++ with clang++. Although the examples can be complied by make, it encountered the "Segmentation fault" after I executed the client (greeter_client) while greeter_server worked well. I used gdb to track the error and the information is as follows:
Thread 1 "greeter_client" received signal SIGSEGV, Segmentation fault.
0x00020e28 in grpc::internal::BlockingUnaryCallImpl<helloworld::HelloRequest, helloworld::HelloReply>::BlockingUnaryCallImpl(grpc::ChannelInterface*, grpc::internal::RpcMethod const&, grpc_impl::ClientContext*, helloworld::HelloRequest const&, helloworld::HelloReply*) ()

after executing bt
#0  0x00020e28 in grpc::internal::BlockingUnaryCallImpl<helloworld::HelloRequest, helloworld::HelloReply>::BlockingUnaryCallImpl(grpc::ChannelInterface*, grpc::internal::RpcMethod const&, grpc_impl::ClientContext*, helloworld::HelloRequest const&, helloworld::HelloReply*) ()
#1  0x0001df38 in grpc::Status grpc::internal::BlockingUnaryCall<helloworld::HelloRequest, helloworld::HelloReply>(grpc::ChannelInterface*, grpc::internal::RpcMethod const&, grpc_impl::ClientContext*, helloworld::HelloRequest const&, helloworld::HelloReply*) ()
#2  0x0001d464 in helloworld::Greeter::Stub::SayHello(grpc_impl::ClientContext*, helloworld::HelloRequest const&, helloworld::HelloReply*) ()
#3  0x00033c40 in GreeterClient::SayHello(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#4  0x00033750 in main ()

What did you expect to see?
I expected to see "Greeter received: Hello world" as I complied it using g++.
What did you see instead?
Segmentation fault
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?
N.A.

I'm seeing that same thing with the async_server example when compiled with clang
Thread 1 "TestGRPC" received signal SIGSEGV, Segmentation fault. 0x00000000007d85c0 in grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest (this=0xeddef0, registered_method=0x0, payload=0xede070, notification_cq=0xed4400) at /home/kevin/Source/thirdparty/grpc/grpc-1.27.2/src/cpp/server/server_cc .cc:219 (gdb) bt #0  0x00000000007d85c0 in grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest (this=0xeddef0, registered_method=0x0, payload=0xede070, notification_cq=0xed4400) at /home/kevin/Source/thirdparty/grpc/grpc-1.27.2/src/cpp/server/serve r_cc.cc:219 #1  0x00000000007a59cf in grpc::ServerInterface::PayloadAsyncRequest<helloworld::HelloRequest>::PayloadAsyncRequest (this=0xeddef0, registered_method=0xed7740, server=0x0, context=0xedd050, stream=0xedd488, call_cq=0xed4400, notification_c q=0xed4400, tag=0xedd040, request=0xedd448) at prebuilt/thirdparty/grpc-1.27.2/linux-x86_64/include/grpcpp/impl/codegen/server_interface.h:288 #2  0x00000000007a57ed in grpc::ServerInterface::RequestAsyncCall<helloworld::HelloRequest> (this=0x0, method=0xed7740, context=0xedd050, stream=0xedd488, call_cq=0xed4400, notification_cq=0xed4400, tag=0xedd040, message=0xedd448) at prebu ilt/thirdparty/grpc-1.27.2/linux-x86_64/include/grpcpp/impl/codegen/server_interface.h:354 #3  0x00000000007a56df in grpc::Service::RequestAsyncUnary<helloworld::HelloRequest> (this=0x7fffffffe190, index=0, context=0xedd050, request=0xedd448, stream=0xedd488, call_cq=0xed4400, notification_cq=0xed4400, tag=0xedd040) at prebuilt/ thirdparty/grpc-1.27.2/linux-x86_64/include/grpcpp/impl/codegen/service_type.h:144 #4  0x00000000007a51fd in helloworld::Greeter::WithAsyncMethod_SayHello<helloworld::Greeter::Service>::RequestSayHello (this=0x7fffffffe190, context=0xedd050, request=0xedd448, response=0xedd488, new_call_cq=0xed4400, notification_cq=0xed4 400, tag=0xedd040) at TestGRPC/helloworld.grpc.pb.h:157 #5  0x000000000079a8b2 in ServerImpl::CallData::Proceed (this=0xedd040) at TestGRPC/greeter_async_server.cc:95 #6  0x000000000079a6d3 in ServerImpl::CallData::CallData (this=0xedd040, service=0x7fffffffe190, cq=0xed4400) at TestGRPC/greeter_async_server.cc:82 #7  0x0000000000798d16 in ServerImpl::HandleRpcs (this=0x7fffffffe188) at TestGRPC/greeter_async_server.cc:146 #8  0x0000000000797157 in ServerImpl::Run (this=0x7fffffffe188) at TestGRPC/greeter_async_server.cc:69 #9  0x0000000000796c64 in main (argc=1, argv=0x7fffffffe2d8) at TestGRPC/greeter_async_server.cc:168

grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest has a nullptr to the server_.

It looks to me (at least in my case) that std::vectors have a different memory layout in the grpc library code to what they do in example code when it's built by clang++, which causes has_async_methods() to return false when it should return true.

@kevza Thanks for updating. On my side, I temporarily fixed the issue by compiling  gRPC source, protobuf and our own program using clang++.

@erheng-dawnlight, in our case the cause was setting -D_GLIBCXX_DEBUG on debug builds. The solution was to either remove the define from our builds or do a special debug build of gRPC with it set there.

I think you need to keep the compiler and the compiler option consistent across gRPC and all dependent libraries. I close this because it's not directly a gRPC issue but please feel free to reopen if you think it's relevant.


The avatar of invited users are not displayed in the details member activity if he did not joined any other room

It is properly displayed in the room members list but it is not in the detailled member activity

Should be fixed with
https://github.com/vector-im/vector-android/commit/23001a1a7e85bd847eda61ca1b663c78198cc238


(PUP-5099) Add code_id to environment catalog from request

This follows the model of agent catalog compilation, passing code_id
from the HTTP request to the environment compiler, which adds it to the
catalog. We then read code_id from the environment catalog and include
it in our response.
This allows environment catalogs and agent catalogs to be correlated
with one another and against a specific version of code.

This needs a puppet-server change to actually pass code-id through to the request handler, but this change can go in on its own.

:+1: Looks good to me.

@thallgren @hlindberg Any chance one of you could take a glance at this?

@nicklewis reading...

@hlindberg Updated with a comment explaining the code_id vs. catalog.code_id as well as improved tests around unspecified/differing code ids.

Good to merge - only found a couple of wide lines (not that bad feel free to ignore).
Added tests are all good.


Allow underscores in numeric literals

Allow any number of underscores in address literals. This allows addresses to be separated into groups of 5 similar to how we'd use spaces if we were writing such a hex digit out by hand.

Is this a convention for representing ethereum addresses? I haven't come across it before and I don't see much benefit in ignoring underscores otherwise.

It's a relatively common modern language feature that I thought would be useful for legibility with the 40 digit long addresses. It's not a big feature but it fits in with the flint mantra of making it easier to spot mistakes in smart contracts.

I guess this could be useful for addresses, but I think most addresses are copy pasted anyway. I think it’s a good feature for number literals, especially when specifying Wei.

This also allows underscores in identifiers which is actually something we need for ERC20 although originally unintended


Throws reference error when using Browserify (assuming will also throw error with other bundlers?)

Looks like d4 variable isn't available inside subsequent closures after the first when compiling with Browserify. As a quick-fix, I declared d4 variable outside all closures. Thoughts?
var d4;

(function() {
  'use strict';

  var root = this;
  var breaker = {};

  // Create a safe reference to the d4 object.
  d4 = function(obj) {
    if (obj instanceof d4) {
      return obj;
    }
    if (!(this instanceof d4)) {
      return new d4(obj);
    }
    this.d4Wrapped = obj;
  };
...

Looks reasonable to me. I'd suggest making this change as a PR after you ensure all tests pass (and adding tests as you feel necessary). I'd be happy to merge it down then.

closing this due to the PR you submitted.


Some ArchiveOfOurOwn stories do not show

Some Ao3 stories need you to be logged in before you can read those stories. Those stories have a :lock: in the story name.
Summarium should either:

Create a bot account on ao3 just for checking those stories (I do not like this)
or
Respond with an embed telling the user they need to log in to view this story

I went with the second option.


Pull request builder flaking on DNS / Probing container

http://goto.google.com/prkubekins/job/kubernetes-pull-build-test-e2e-gce/1456 is an example, but I've seen it a bunch:
Kubernetes e2e suite.DNS should provide DNS for the cluster
Kubernetes e2e suite.Probing container with readiness probe that fails should never be ready and never restart

I'm not seeing similar failures on kubernetes-e2e-gce-parallel

cc @ixdy @quinton-hoole

The flaky tests have occurred on all of the executors, so it doesn't seem like it's related to that.
A lot of the recent failures are all on #10487 (e.g. builds 1486, 1484, 1474, 1473, 1466) though there are failures for other PRs earlier than that.
Still digging...

The probing container test failed on the kubernetes-e2e-gce-parallel build once: https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-e2e-gce-parallel/2531/

Also a DNS flake in build 2490 on June 29: https://cloud.google.com/console/storage/kubernetes-jenkins/logs/kubernetes-e2e-gce-parallel/2490/

The probing container test shows an error message like the following before failing:
STEP: Collecting events from namespace "e2e-tests-container-probe-3x5iw".
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {scheduler } scheduled: Successfully assigned nginx-e8a70908-1ffd-11e5-be80-42010af07603 to pull-e2e-0-minion-nfdy
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} pulled: Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} created: Created with docker id 3956dffea70e
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} started: Started with docker id 3956dffea70e
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} pulled: Successfully pulled image "nginx"
INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/669e5d583ce9b05fe811ea4f8556f6e115d89d4eb5737ed98090948af4b7cd18-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/17239846605d44aed3864d9203a4b25a77f34a5f8004ab150d0de2e2ac6f07a8-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/75bbee02176bd7c5e69f8a26c0841bc01046d0ed28e765d529e1c8d71162752f-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/8d2e609778cff6ac51765719dd023d7bf501a4ca883085033db8c9db3ee4b735-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/b2f3f8a07398d4738a544141893cd54da24923e193e7897b2ab1013fd8672634-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/e8cfbc6e95caf523a5a4a9338fb71c6d245084b02d9be926b200cc1fd5e0a3c4-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/a6d77f267addd85fa132b5e9db7da93ca74ae258fea71b0098f6a4e6d2c4ebcb-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/1f3de7151e52bf8026519b0a245e8861c033506d69ecb9896b90f6458c250a36-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/2cff807974c6149dc02047c1798f0303a9c327ccc43c9d55595f7ce80b1c5801-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/9f2e297afd646a3bd2cb52005cb04d66dea70d43c077c5e59564147302ae7feb-init: invalid argument

INFO: event for nginx-e8a70908-1ffd-11e5-be80-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/eda7977d57fccc4f8a8914ecdcbb0b82e2fd20fdde37e8accd3a42b5e6a6a4c3-init: invalid argument

STEP: Destroying namespace "e2e-tests-container-probe-3x5iw" for this suite.
• Failure [100.284 seconds]

I'm not sure how to interpret this.

Similar error messages from the DNS test.
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {scheduler } scheduled: Successfully assigned dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603 to pull-e2e-0-minion-nfdy
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} pulled: Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} created: Created with docker id 6359a7570a4b
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} started: Started with docker id 6359a7570a4b
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} created: Created with docker id 763b2e1358ce
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} started: Started with docker id 763b2e1358ce
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} pulled: Successfully pulled image "gcr.io/google_containers/dnsutils"
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} created: Created with docker id de33cca553e1
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} started: Started with docker id de33cca553e1
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} pulled: Successfully pulled image "gcr.io/google_containers/jessie-dnsutils"
INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/13ba216123e17f3189be739f5e1cce06a3ffa0dddc02b5c7d9bd4eda33e7f70b-init: invalid argument

INFO: event for dns-test-dfa67cf7-1ffd-11e5-869d-42010af07603: {kubelet pull-e2e-0-minion-nfdy} failed: Failed to create docker container with error: API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/34a61d31c14ce0be078057f1e6b6727aa95aef9551d082cd25c4cb44c18a0f96-init: invalid argument

etc.
Is there some issue with docker that we're hitting?

cc @dchen1107 !

The reason I opened this bug is that I saw multiple cases yesterday where the pull builder turned up one of these, I asked it to retest, and it went away.

Yeah, I am not sure why this is occurring much more heavily on the pull builder than on our post builders.

I believe you are running into this issue: https://github.com/docker/docker/issues/13742

The docker errors are from the kubelets, not from our Jenkins instance, so I'm not sure that issue is (entirely) related.

I just got hit by a bunch, and they seem to clump on these tests. I had to look back at some other PRs to see if I was going insane, but #10680 got this clump:
Kubernetes e2e suite.Probing container with readiness probe should not be ready before initial delay and never restart
Kubernetes e2e suite.DNS should provide DNS for the cluster
Kubernetes e2e suite.DNS should provide DNS for services
Kubernetes e2e suite.Kubectl client Simple pod should support exec

And my #10687 just got hit with this about 3-4 times, all of which seem kubelet related:
Kubernetes e2e suite.DNS should provide DNS for the cluster
Kubernetes e2e suite.DNS should provide DNS for services
Kubernetes e2e suite.Probing container with readiness probe should not be ready before initial delay and never restart
Kubernetes e2e suite.Kubectl client Simple pod should support exec
Kubernetes e2e suite.Kubectl client Simple pod should support port-forward

I tested #10687 manually and can't get those to repro.

@ixdy Any progress on this one?  It's one of our few remaining v1.0 priority 0's.

No progress. I have no idea why docker is failing more consistently on the pull request jenkins.

The DNS tests were already using images from gcr.io, so the fix in #10758 seems unlikely to be the issue.

@ixdy are you busy debugging, or do we need to find someone else?

@ixdy Is it perhaps the GCE project in which you're running that has badly configured network routes or load balancers?

I'm not actively debugging. I don't really know where to look.
Nothing about the GCE project used for the pull request Jenkins looks any different from the other GCE projects.

It also seems like these tests aren't failing anymore?
Services should serve a basic endpoint from pods is looking flaky, but I haven't checked the post-commit Jenkins to see if it's flaky there too.

OK, I guess I'll take it then.

@krousey kindly stepped up to take this one - reassigned.

Note that these DNS failures are not limited to the pull request builder.  Our normal Jenkins runs are seeing similar errors:
e.g.

job/kubernetes-e2e-gce-parallel/3023/
job/kubernetes-e2e-gce-parallel/3035/
job/kubernetes-e2e-gce-parallel/3028/

I'm increasingly convinced that there are some wrong network configs (or quota limits) on the underlying GCE projects.  Checking...

No, there's nothing obviously wrong in the underlying GCE project (although it would be good for @krousey to double-check me).
Back to you @krousey ...

The framework occurs in the generic framework cleanup and is not specific to DNS or probe tests. It's waiting for all nodes to be ready. For each failure, the same node is in a not ready state with the reason: network not configured correctly

It seems this might be a new failure and unrelated to the original.

That reason is given here https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L2066 and the boolean that determines it is only modified here https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1951 . Neither of the log messages in that function show up in the kubelet log, so I assume the branch that executed was https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1962 .
@dchen1107 It seems that len(kl.podCIDR) == 0 is causing some e2e test flakiness. I'm not that familiar with kubelet. What does it mean for this to be empty?

cc @cjcullen @roberthbailey

I think we have two separate issues here. In

job/kubernetes-e2e-gce-parallel/3023/
job/kubernetes-e2e-gce-parallel/3035/
job/kubernetes-e2e-gce-parallel/3028/

We seem to have a single flake in node readiness that gets reported multiple times for each cleanup that happens to run at that time. It happens in the middle of a test run and then goes away. The root cause of this is unknown. @cjcullen noticed a race at https://github.com/GoogleCloudPlatform/kubernetes/blob/b27a8e1d902adf5ef0e3e4c4a248e40642879f88/pkg/kubelet/kubelet.go#L2098 that probably needs to be protected by kl.networkConfigMutex. This may be the cause of it... somehow.
Since the node status is updated in a 30 second loop, we could add logic to the tests to retry up to 30-60 seconds after the last status update on the failing nodes. This would probably reduce random test failures, but wouldn't solve the underlying issue.
The second issue seems to be docker failing to build containers like in job/kubernetes-e2e-gce-parallel/3046/.
E0708 20:05:35.510816    3077 manager.go:1579] Error running pod "dns-test-a6805741-25ac-11e5-8fa6-42010af01555_e2e-tests-dns-8q0vk" container "jessie-querier": API error (500): error creating aufs mount to /var/lib/docker/aufs/mnt/b2a84be51ae21ce45bc2cf1ecb944be2b4345c25798af0249260874185622e64-init: invalid argument

I forked the AUFS issue off on it's own.

To be clear, the "first" issue above looks as follows in the logs:
All nodes should be ready after test, Not ready nodes: [...[{Ready False 2015-07-08 05:23:10 -0700 PDT 2015-07-08 05:23:10 -0700 PDT network not configured correctly }] ...

The above is also causing remaining failures in #10657

@krousey Is there anything left to do in this issue, or can we close it.  Seems like we still need to track down the "network no configured correctly" issue, and the "AUFS mount" issue, but there are separate issues tracking those?

@quinton-hoole Nothing left. The root causes have other issues and my change mitigates the effect of the most common one.


Out-of-box progressive web app support

might use offline-plugin by @NekR
// pr welcome, I'm no expert in this

I'm no expert either 😂

as reference maybe similar to the pwa plugin of the upcoming vue-cli: https://www.npmjs.com/package/@vue/cli-plugin-pwa


[Do not merge][Issue] Reproduce:messagesConsumedCounter of cursor is …

This is an issue, not a PR( show the way of reproduce issue)
1.A compensation mechanism for backlog less than 0
The field backlog of the subscription can be less than zero(this only can be caused by messagesConsumedCounter of cursor is larger than total entries of ML). We can see that there is a patch here to handle this scenario:
https://github.com/apache/pulsar/blob/e2851da923a729423de54dc3a95d1e7a43b6e08a/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L1110-L1114

2.Backlog wrong caused by messagesConsumedCounter wrong
When create subscription(initialized position to earliest) and send messages are executed concurrently, an incorrect count occurs, leading to the field backlog of subscription less than 0. For example:
2-1. Create a new topic, the field currentLedger of the managed ledger is 3. Then send 10 messages.
2-2. Concurrently processes

time
thread: create new cursor
thread: add entry

1

increment entriesAddedCounter( before: 0, after: 1 ) of ML

2
get entriesAddedCounter of ML: 1

3
get lastConfirmedEntry of ML: 3:0

4
set messagesConsumedCounter to 1

4
set markDeletePosition to 3:0

5

update lastConfirmedEntry(3:1) of ML

(Highlight)Now consumer doesn't consume any messages, but messagesConsumedCounter of cursor is already 1
2-3. Error occur

After sending 10 messages, the field entriesAddedCounter of ML will be 10
After consuming all 10 messages, the messagesConsumedCounter of the cursor will be 1 + 10
Then ManagedLedgerImpl.ENTRIES_ADDED_COUNTER_UPDATER.get(ledger) - messagesConsumedCounter will be -1.

3. Reproduce issue
Since it is hard to write a non-invasive test. You can reproduce by StatsBackLogTest.testMessagesConsumedCounterCorrect

You should open the PR in your own fork to avoid the waste of CI resources when you want to reproduce an issue.


PickSingleItemAsync() throws an Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)

 picker = new GraphicsCapturePicker();

GraphicsCaptureItem item = await picker.PickSingleItemAsync();

As mentioned in the title, the exception is thrown when calling PickSingleItemAsync() from a Unity-UWP Application.
I'm even able to capture & save some images in a UWP Project made from VisualStudio, but not from a Unity3D to UWP project.
Permissions are set up. But I'm not sure if it's a problem with Unity or if I'm supposed to  handle few things in the main App class
class App : IFrameworkView, IFrameworkViewSource
    {
        private WinRTBridge.WinRTBridge m_Bridge;
        private AppCallbacks m_AppCallbacks;

        public App()
        {
            SetupOrientation();
            m_AppCallbacks = new AppCallbacks();

            // Allow clients of this class to append their own callbacks.
            AddAppCallbacks(m_AppCallbacks);
        }

        public virtual void Initialize(CoreApplicationView applicationView)
        {
            applicationView.Activated += ApplicationView_Activated;
            CoreApplication.Suspending += CoreApplication_Suspending;

            // Setup scripting bridge
            m_Bridge = new WinRTBridge.WinRTBridge();
            m_AppCallbacks.SetBridge(m_Bridge);

            m_AppCallbacks.SetCoreApplicationViewEvents(applicationView);
        }

        /// <summary>
        /// This is where apps can hook up any additional setup they need to do before Unity intializes.
        /// </summary>
        /// <param name="appCallbacks"></param>
        virtual protected void AddAppCallbacks(AppCallbacks appCallbacks)
        {
        }

        private void CoreApplication_Suspending(object sender, SuspendingEventArgs e)
        {
        }

        private void ApplicationView_Activated(CoreApplicationView sender, IActivatedEventArgs args)
        {
            CoreWindow.GetForCurrentThread().Activate();
        }

        public void SetWindow(CoreWindow coreWindow)
        {
            ApplicationView.GetForCurrentView().SuppressSystemOverlays = true;

            m_AppCallbacks.SetCoreWindowEvents(coreWindow);
            m_AppCallbacks.InitializeD3DWindow();
        }

        public void Load(string entryPoint)
        {
        }

        public void Run()
        {
            m_AppCallbacks.Run();
        }

        public void Uninitialize()
        {
        }

        [MTAThread]
        static void Main(string[] args)
        {
            var app = new App();
            CoreApplication.Run(app);
        }

        public IFrameworkView CreateView()
        {
            return this;
        }

        private void SetupOrientation()
        {
            Unity.UnityGenerated.SetupDisplay();
        }
    }

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

ID: f607a1db-43b3-bf1c-c6d1-6283c1280743
Version Independent ID: c1c72175-3e9c-59f6-e30e-7d6f821c5876
Content: Screen capture - UWP app developer
Content Source: windows-apps-src/audio-video-camera/screen-capture.md

The solution is to create an AppCallBackItem, and invoke it through the UIThread
   ```

public App()
{
SetupOrientation();
m_AppCallbacks = new AppCallbacks();
        ScreenCaptureHandler.OnCaptureDemanded+= OnCaptureDemanded;
        // Allow clients of this class to append their own callbacks.
        AddAppCallbacks(m_AppCallbacks);
    }

    private void OnCaptureDemanded()
    {
        var callBack = new AppCallbackItem(async () =>
       {
           //The StartCaptureAsync() only calls the picker.PickSingleItemAsync() right now
           var handler = new StaticHandler();
           await handler.StartCaptureAsync();
       });

        m_AppCallbacks.InvokeOnUIThread(callBack, true);
    }

Hi @Chalghouma, glad to hear that you got it working! I'm afraid I couldn't follow your code, but I did manage to get the screen capture picker to pop in a Unity sample using the following code:
CoreWindow window = CoreApplication.MainView.CoreWindow;

await window.Dispatcher.RunAsync(CoreDispatcherPriority.Normal, async () =>
{
    await StartCaptureAsync();
});

You're right, it needs to be called on the UI thread. I will add this to the documentation.


Merged configuration cache file and module map cache file are never reseted

Surely due to this commit https://github.com/zfcampus/zf-development-mode/commit/8339569b332c2593420373886d879b1bf6c0bd73 both, the merged configuration cache file and module cache file are never reseted. This is because in the factory, you are retrieving the related config key (config_cache_key and module_map_cache_key)  at the wrong place (top level config instead of module_listener_options).

@weierophinney
Could you review the related PR and merge?
Thank you ;)


Confusion about authentication in TUTORIAL.md

I have followed the entire tutorial to the point that I know authenticate will create the JWT to user, and PostgraphQL will use the JWT that is embedded in HTTP request’s Authorization header.
From what I understand authenticate would be available for query with GraphQL via reflection as well, so that is how client will get the JWT string (Do a GraphQL query with your ID and Password). Could someone guide me to put the JWT from authenticate into user's browser so it uses that on every future HTTP requests? (Of course it would need some kind of time out too)
From my guess I will need to do a GraphQL query via the fetch API with the method set as POST so the password would not show up in the URL, to get the JWT and then put that into document.cookie. Next I will keep using that cookie with all further fetch API but with one of the headers set to Authorization : JWT string.
I haven't try this, but I am wondering if this is the recommended way or not. Thank you.

Here's what I use for an express stack, perhaps it's of use?
    const getJWTToken = (req, res) => (
      jwt.encode({
        aud: 'postgraphql',
        role: postgraphqlRole,
        user_id: (req.user && req.user.id) || undefined,
      }, process.env.JWT_SECRET)
    );

    const populateJWT = (req, res, next) => {
      req.headers.authorization = 'bearer ' + getJWTToken(req, res);
      next();
    };

    expressApp.use('/graphql', populateJWT);
    expressApp.use('/graphiql', populateJWT);
    expressApp.use(postgraphql(pgPool, postgraphqlSchema, options));

(I use regular session management, and then convert that to a JWT token for PostGraphQL.)

@5argon
Here's a standalone example:
query(request) {
      let data = {};
      if (request.query) data['query'] = printGraphQL(request.query);
      if (request.variables) data['variables'] = JSON.stringify(request.variables || {});
      if (request.debugName) data['debugName'] = request.debugName;
      if (request.operationName) data['operationName'] = request.operationName;
      let headers = {Accept: 'application/json', 'content-type': 'application/json'};

      // get the JWT from local storage if it exists

      let jwt = localStorage.getItem('jwt');
      if (jwt) {
        headers['Authorization'] = `Bearer ${jwt}}`;
      }
      return fetch(url, {headers, body: JSON.stringify(data), method: 'POST',}).then(result => result.json());
}

If you're using apollo-data's client for your browser side code, look into the methods networkInterface.use and applyMiddleware, otherwise the above example should work out for you.
Notice we're using the http fetch API, some browsers may require a polyfill.

Thank you everyone. I have learned many things!


Claim URL

Describe the bug
I cannot get the claim url and am burning a ton of tokens asking for it...I keep getting this...I apologize, but I'm currently experiencing an issue with the deployment tool. The deployment command is not working as expected. This is why I haven't been able to provide you with the claim URL. Let me know if you'd like me to try a different approach or if you'd prefer to deploy the site manually through Netlify's interface.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-ujw8mn
Steps to reproduce
Ask it for the claim url
Expected behavior
Getting the claim url
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 193449185,
  "usedJSHeapSize": 163429313,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = rm2024!
Chat ID = 3b1223e8e9b9

Additional context
Is there any way I can get tokens added? I have probably asked it 40 times for the claim urls this week...I don't mind burning tokens for legit chats but not this over and over....I don't mean to complain and your product is awesome and I know you are trying to make it better...

Appreciate the feedback! We are aware of this issue and are tracking it here: #2020.


How to use in web components?

How to use in web components?

I've no support for the web components but you can wrap this lib into the Web Components
Maybe it will help you a little.
https://gilfink.medium.com/wrapping-react-components-inside-custom-elements-97431d1155bd

thank you~~


Split proguard files

[ ] Normal proguard rules file exists
[ ] Test proguard rules file exists

Closed by commit 48def3c09edd2b5ae54129084bc6d2f266396fb2


Cannot read property 'primaryKey' of undefined

Hello everyone.
I'm trying to persist data from a frontend to a backend server using vuex orm graphql plugin.
async createNewCar() {
        await Car.create( {data: this.car} )
        let car = Car.query().whereFk("n").first()
        await car.$persist()
      }

this.car is a computed property and looks like this:
      car() {
        return {
          id: "n",
          name: this.name,
          garage_id: this.garage.id,
        }
      }

After calling the await car.$persits() command, I get the following error message:
app.js:764 TypeError: Cannot read property 'primaryKey' of undefined
    at<EMAIL_ADDRESS>(vendors.app.js:3624)
    at<EMAIL_ADDRESS>(vendors.app.js:1079)
    at<EMAIL_ADDRESS>(vendors.app.js:1066)
    at<EMAIL_ADDRESS>(vendors.app.js:3051)
    at<EMAIL_ADDRESS>(vendors.app.js:3895)
    at<EMAIL_ADDRESS>(vendors.app.js:3564)
    at<EMAIL_ADDRESS>(vendors.app.js:755)
    at<EMAIL_ADDRESS>(vendors.app.js:3051)
    at<EMAIL_ADDRESS>(vendors.app.js:3895)
    at<EMAIL_ADDRESS>(vendors.app.js:3564)

Hope anyone can help me.
Thank you ;)

How does your model definition of car looks like? And what computed prop is that? I'm not sure I fully understood your code :D

Good morning ;)
I'm sorry and I understand you.

The frontend is a nuxt application using vuex orm in combination with the graphql plugin.
So in our case the frontend will be used to create a cars which should be stpred in the database in the backend.
When I create a car the $persist() function crashes.
I hope that will help you to give me some support.
As I said, I'm very sorry for my shitty use case :D

Okay I solved the Problem.
The Garage type has a many to many relation and I forgot to register the pivot model.
That was the reason for the undefined property.
Never the less I have another question.
Is there a possibility to create a new model (e.g. a car one) via $persist() and avoid to create the related models?
async createNewCar() {
        await Car.create( {data: this.car} )
        let car = Car.query().whereFk("n").first()
        await car.$persist()
      }

The command above (await car.$persist()) creates the following query:
mutation CreateCar($car: CarInput!) {
  createCar(car: $car) {
    id
    name
    garage {
      id
      name
      area
      street
      region
      municipality
      owner {
        id
        lastname
        firstname
        email
      }
    }
  }
}

And I want just to do this:
mutation CreateCar($car: CarInput!) {
  createCar(car: $car) {
    id
    name
    garage_id

avoid to create the related models?

It doesn't create the other models, it just generates a query to fetch those related stuff after the server has created them. On the server you can decide wether you want to create them or not.
However currently there is no possibility to disable eagerLoading (which is what happens here) for single queries. Maybe in the future.

Moved to https://github.com/vuex-orm/plugin-graphql/issues/95