Fix link issue on menu pages

We need to apply the getPath(name) on the to Link property.
Before:
name: 'My Page' => resulted on /My Page, but the route path is /My-Page, so the link wasn't working.
After:
This is a personal preference, but I also added toLowerCase() into the getPath function, since URLs are usually lowercase & hyphenated
name: 'My Page' => it's now /my-page
BTW, We could also move the getPath function outside the component.

We need to apply the getPath(name) on the to Link property.
Before:
name: 'My Page' => resulted on /My Page, but the route path is /My-Page, so the link wasn't working.
After: This is a personal preference, but I also added toLowerCase() into the getPath function, since URLs are usually lowercase & hyphenated
name: 'My Page' => it's now /my-page
BTW, We could also move the getPath function outside the component.

@carletex  i think its a good idea to move it out if you feel like it.

@ShravanSunder Just moved the getPath function outside the component on https://github.com/scaffold-eth/scaffold-eth-typescript/pull/92/commits/c32061a71619049ccafc3d914fa0d7d88ef2f122


[Documentation Update]: Auto update all translated versions of the readme file using github actions.

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
Using the following: Translate-Github-Readme we can set it to autotranslate the README file to other languages.
Suggested Change
null
Rationale
If implemented any changes to the documentation will only be need to be made once.
Urgency
Low
Record

[X] I have read the Contributing Guidelines
[X] I have starred the repository

@ahaapple If it's ok with you I would like to work on this.

@Riyan-Mo  This is what I wanted to do, thanks


Update firebase auth readme.

What do you think handling this by a future?

cc @kroikie

Seems reasonable, also a bit more darty.


User Experience Feedback for the current state of Franklin.jl

I don't know where to place this, probably nowhere, but I hope it is still somehow valuable to know how painful it is to use Franklin.jl right now
unfortunately when I am working with Franklin, once a week, or more often, I am hitting some bug-like missing feature (something I expect just works) or a plain bug. Everytime something does not work, Franklin plainly crashes, which makes the process of working with Franklin quite difficult.
This state of franklin is quite unexpected given that so many users uses it and even juliacomputing uses Franklin.
I am sorry for these words of sorrow, but with every such issue I feel like I better had used something more mature than Franklin and am now developing Franklin instead of my webpage. However I wanted to make use of Julia in case I need it. Was a difficult decision and probably I already went to far and will stay with Franklin despite all these difficulties.
I would love seeing Franklin more userfriendly in this regard.
My excuses for the hard words, still they may give some valuable insights into the user perspective.

Hey Stephan, no problem, I know it's not always a smooth ride and thanks for giving it a fair shot already.
Some notes:

given the issues you opened here (thanks for those btw, it's always helpful), you're using a lot of 'advanced' features of Franklin; not that these shouldn't be used, but rather that the docs for those is less present and, as far as I could see, the issues you have are often about expecting X to work but in fact there's Y that could have been used instead.

For this, it's always the same; having patient users help me extend the docs is how things can become better.

with respect to other users, there's basically two groups of users: those who don't leverage a lot of the features like lx* or hfun*; for those "things generally work" and when it doesn't they shoot a message on Slack and it usually gets solved very quickly. This group includes the 'big' users you listed (Julia website, etc) and the second are people who do used the advanced features like you or the guy behind the Makie docs, and these people do run into issues because they use things that have been used less and are documented less. I typically try to help these people pretty actively and respond quickly (as I think you saw). The hope is that these people help me by trying stuff out and making suggestions for better docs or for better code.

A final note is that I'm working on a very big refactoring as I think I've mentioned in another issue; this also means that I'm not actively working on the current version (apart from fixes) because I'd like things to "keep working" for people who use Franklin now and have something they're happy with.
The next version will certainly not be perfect but will address a bunch of the issues you've opened recently. One thing to understand is that the initial design of Franklin had a simpler use case in mind but slowly people started using some more advanced stuff to a point which now suggests some core re-design for improved use.
This is a lot of work, and while the main building blocks are in place, there's still a lot of details to finalise before I can offer this for people to beta-test.
Anyway, I understand that things can be frustrating and I apologise; if you want to help me out with adding comments in the docs, this will be much appreciated. I'd also suggest you join the slack #Franklin channel to get help quicker than here (even though in some cases your issues are good reminders that I have to improve the docs on XYZ).


mac OSX support

[ x] Review the documentation: https://facebook.github.io/react-native
[ x] Search for existing issues: https://github.com/facebook/react-native/issues
[ x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (4) x64 Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz
Memory: 3.68 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.1.0 - ~/.nvm/versions/node/v11.1.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v11.1.0/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 26, 28
Build Tools: 28.0.3
System Images: android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.7.0 => 16.7.0
react-native: Microsoft/react-native#master => 0.58.6-microsoft.31
npmGlobalPackages:
react-native-cli: 2.0.1
Description
Hello, I'm trying to integrate this react-native into an existing empty macOs app using cocoapods. I'm receiving the following error:
"[!] The platform of the target my-react-xp-app (macOS 10.14) is not compatible with React/Core (0.58.6-microsoft.31), which does not support osx."
Is macos supported on the current master branch? thanks.
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, share a project, or     share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve

Hi.  Its on our radar to get cocoapods working for mac.   Right now, the mac libs have to be manually integrated into a app.   One way is to aggregate the React and other Library xcodeproj's into your xcodeproj -- like RNTester/RNTester.xcodeproj does in this repo.

Any follow up on this? To simplify the context I'll rephrase the question:  Can we build cross-platform Win10 and Mac OS apps using the current main branch?

I have started work on this here, but it thus far only targets RNTester. Having said that, it might already proof useful to you as-is.

Closing in favour of https://github.com/microsoft/react-native/issues/215


Config sync algorithm should check relevance of current external config and update only plugin related part

For example we don't use TS at the beginning and @zero-scripts/plugin-webpack-babel will generate babel.config.js with support for JS files. But then we started using TypeScript and our current babel.config.js cannot handle TS files.
As a current behaviour after adding TypeScript and creating tsconfig.json developer should delete generated babel.config.js and then this file will be generated again with added plugins/presets. It's slightly weird because config sync feature was added to allow developer to make additional changes with ease and without learning Zero Scripts plugins custom options.
As a solution we should remember all user additions or deletions in configuration and then regenerate this configuration with actual support for TypeScript and with this changes.
Other solution can be to put all conditional configuration parts in config itself, but it will increase configuration size and decrease readability,

After some thinking I understand that config sync is not really needed. But we should leave availability to generate config with command.
run generate-babel-config

Closing in favour of #666


Bootstrapper doesen't handle corrupt paket.exe

Description
If for some reason paket.exe is not completely downloaded during the bootstrap process (for instance , power outage), the file can be corrupted. We observed on a build server that all subsequent calls to the bootstrapper will pull an invalid paket.exe from the cache breaking builds (as in avoiding them from continuing). Cleaning paket's cache is required to continue.
Repro steps
Not sure, but creating and invalid paket.exe and placing it in cache might be enough to exemplify this. Might be able to automate it in a test.
Expected behavior
Bootstrapper should verify that the downloaded paket .exe (wether from the web or cache) is valid, possibly by comparing ti with some checksum. If the paket.exe that is present is determined to be invalid, redownload it and overwrite existing versions.
Actual behavior
A broken paket.exe is put in the .paket directory.
Known workarounds
Manually cleaning the cache will allow for a new download. This step may be limiting due to user access rights to build servers.

Fixed with #2192?

@forki and @enricosada I believe this has been fixed. The only place it is missing is with the NuGet download strategy, and I'm assuming that has built-in hashsum checks natively?


Adding template version as manual input to Wizard publish action

PR Summary
Bumping hardcoded template version string from env vars to GitHub event inputs
PR Checklist

[ ] PR has a meaningful title
[ ] Summarized changes
[ ] This PR is ready to merge and is not Work in Progress
[ ] Link to a filed issue

Need to shelve this idea and discuss the release process more widely.


GitHub runner crashes container on Windows Server 2022

When I run a github-runner container on Windows Server 2022, it crashes when the first job is taken
Repro steps:

Create an Azure VM (Windows Server 2022 Datacenter Server Core - Gen1, Size Standard_D4s_v5)
Run the following script to get the prereqs, the latest Docker version and restart the computer

$ProgressPreference = 'SilentlyContinue'
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V, Containers -All -NoRestart
Invoke-WebRequest -UseBasicParsing -Uri https://download.docker.com/win/static/stable/x86_64/docker-20.10.11.zip -OutFile docker-20.10.11.zip
Expand-Archive .\docker-20.10.11.zip -DestinationPath $env:ProgramFiles
$path = [System.Environment]::GetEnvironmentVariable("Path", "Machine")
[Environment]::SetEnvironmentVariable("Path", "$path;$env:ProgramFiles\docker", "Machine")
& 'C:\Program Files\docker\dockerd.exe' --register-service
Restart-Computer -Force

Add defender exceptions to make sure it isn't interfering and get the needed image

Add-MpPreference -ExclusionPath 'C:\Program Files\docker\'
Add-MpPreference -ExclusionPath 'C:\ProgramData\docker\'
docker pull tobiasfenster/github-runner-windows:ltsc2022

Run the container, connected against an arbitrary GitHub repo

docker run --name github-runner -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -e GITHUBREPO_OR_ORG=tfenster/traefik-for-windows -e GITHUBRUNNERNAME=self-hosted-2022 -e GITHUBPAT=<redacted> --isolation hyperv tobiasfenster/github-runner-windows:ltsc2022

# Runner removal

Cannot connect to server, because config files are missing. Skipping removing runner from the server.
Does not exist. Skipping Removing .credentials
Does not exist.

Start an action in GitHub which is picked up by this worker. Immediately an error occurs and the container crashes

time="2021-11-18T12:03:14Z" level=error msg="Error waiting for container: failed to shutdown container: container d10853dbce3ad842a33dbd14c1cd22679f2d319fe04f0662f370b18f52f98c2a encountered an error during hcsshim::System::Shutdown: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a): subsequent terminate failed container d10853dbce3ad842a33dbd14c1cd22679f2d319fe04f0662f370b18f52f98c2a encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a)"

I also tried installing through the DockerMsftProvider as follows, which gives me Docker 20.10.7, but with the same result:
Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider

The image was created from this Dockerfile, but it is fairly trivial.
Running the 2004 image with hyperv isolation on a 2022 server works (docker run --name github-runner -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -e GITHUBREPO_OR_ORG=tfenster/traefik-for-windows -e GITHUBRUNNERNAME=self-hosted-2022 -e GITHUBPAT=<redacted>--isolation hyperv tobiasfenster/github-runner-windows:2004)
Version infos
docker info when installed through direct download
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.3-docker)

Server:
 Containers: 3
  Running: 0
  Paused: 0
  Stopped: 3
 Images: 2
 Server Version: 20.10.11
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics internal l2bridge l2tunnel nat null overlay private transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: process
 Kernel Version: 10.0 20348 (20348.1.amd64fre.fe_release.210507-1500)
 Operating System: Windows Server 2022 Datacenter Version 2009 (OS Build 20348.350)
 OSType: windows
 Architecture: x86_64
 CPUs: 4
 Total Memory: 16GiB
 Name: bug-repro7
 ID: OLQP:L24P:NV2P:WVDI:IS2D:TJSZ:AB5F:JZL3:VSIK:WGNV:M3N6:J2RA
 Docker Root Dir: C:\ProgramData\docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false
 Product License: Community Engine

docker info when installed through the DockerMsftProvider
docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker Application (Docker Inc., v0.8.0)
  cluster: Manage Mirantis Container Cloud clusters (Mirantis Inc., v1.9.0)
  registry: Manage Docker registries (Docker Inc., 0.1.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 20.10.7
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics internal l2bridge l2tunnel nat null overlay private transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: process
 Kernel Version: 10.0 20348 (20348.1.amd64fre.fe_release.210507-1500)
 Operating System: Windows Server 2022 Datacenter Version 2009 (OS Build 20348.350)
 OSType: windows
 Architecture: x86_64
 CPUs: 4
 Total Memory: 16GiB
 Name: bug-repro7
 ID: OLQP:L24P:NV2P:WVDI:IS2D:TJSZ:AB5F:JZL3:VSIK:WGNV:M3N6:J2RA
 Docker Root Dir: C:\ProgramData\docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

Windows Server version info:
(Get-WMIObject win32_operatingsystem).Version
10.0.20348

@judyliu-ms Any ideas on this yet? I just now tested #181 for which there is a workaround, but confirmed that the problem in this issue still exists and is fully reproducable

@tfenster Thank you for bringing this to our attention. Our engineering team has been investigating this issue and found the root cause problem. We have a solution and are working to port this into a March release for WS2022.

Closing this out since the fix went live.

@judyliu-ms unfortunately, this doesn't seem to be fixed for me. Following the instructions above, I still get
time="2022-03-21T22:03:05Z" level=error msg="Error waiting for container: failed to shutdown container: container 9882a54cbebde91f232054b7be6a4b9f410b47af3eeee6eef3d210194c23468e encountered an error during hcsshim::System::Shutdown: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a): subsequent terminate failed container 9882a54cbebde91f232054b7be6a4b9f410b47af3eeee6eef3d210194c23468e encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a)"

For which Windows build should I see the fix? I created a new VM 15 minutes ago to validate the fix and I get 20348.587. Should that include the fix?

Closing this out since the fix went live.

Where exactly it went live? KB patch number or something?

It's in build 20348.617, KB5011558
It seems I closed this issue one day too early, my apologies!

@judyliu-ms ok, I still get 20348.587 in a VM created right now, but I'll try again tomorrow

@tfenster If I am not mistaken, the Windows images in the Azure gallery are updated on Patch Tuesday cadence. Since this fix went out in the non-security patch (the week following Patch Tuesday), you'll need to wait for next month's VHD (4/12/22) to pick this up, unless you initiate the optional cumulative update (which is the KB patch mentioned above by Judy).

@judyliu-ms @cwilhit I have updated a Windows VM on Azure to 10.0.20348.617, but unfortunately still the exact same behavior:
Microsoft Windows [Version 10.0.20348.617]
(c) Microsoft Corporation. All rights reserved.

vmadmin@sshhost C:\Users\vmadmin>docker run --name github-runner2 -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -e GITHUBREPO_OR_ORG=tfenster/traefik-for-windows -e GITHUBRUNNERNAME=self-hosted-2022 -e GITHUBPAT=<redacted> --isolation hyperv tobiasfenster/github-runner-windows:ltsc2022

# Runner removal

Cannot connect to server, because config files are missing. Skipping removing runner from the server.
Does not exist. Skipping Removing .credentials
Does not exist.    3 minutes ago   Exited<PHONE_NUMBER>) 2 minutes ago             github-runner2
cb66c4fde968   tobiasfenster/github-runner-windows:ltsc2022   "powershell -Command…"   9 minutes ago   Created                                       github-runner

The first in the list, github-runner2 is the one that crashed. The second, github-runner is the one that is stuck in "Created"

@judyliu-ms @cwilhit Any update on this?  Can you repro that it actually isn't fixed?

@tfenster We are taking a look on our side, will let you know when I have an update

Reopening until we doubly confirm this is fixed.

Hi @tfenster, in the hyperv scenario, there is a out-of-date driver in the container image causing the crash. This driver was updated in the VM, but the container base image also needs to be updated and this will be released with the Patch Tuesday cadence (April 12th). For the process-isolated scenario, we have not been able to reproduce this, but I would recommend re-trying when the updated container image is released.

@judyliu-ms ok, I'll test again then. What build number / tag is the the one that should work?

The build should be 20348.617, double-check that the container version is 10.0.20348.617

Thanks! I just now tried again and get 10.0.20348.643 on both host and base container image, but I am very happy to confirm that it now works 😊


Update how-to-troubleshoot-online-endpoints.md

Add separate section for all known Bad Argument errors

@frcai : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Linking polygon2D points to bone2D goes wrong

Godot version:
Godot Engine v3.2.3.stable.official
OpenGL ES 2.0 Renderer: Intel(R) HD Graphics
OpenGL ES 2.0 Batching: ON
OS/device including version:
Processor: Intel(R) Core(TM) i3 CPU       M 330  @ 2.13GHz (4 CPUs), ~2.1GHz
Memory: 4096MB RAM
Card name: Intel(R) HD Graphics
Chip type: Intel(R) HD Graphics (Core i3)
DAC type: Internal
System: Windows 7 Professional x64
Issue description:
When I try to link a few polygon2D points to a bone2D the sprite gets distorted. If I link all the points, the image disappears
Video: https://youtu.be/oqmed2EWGog
Steps to reproduce:
Open "Player.tscn, Select LegR object and click over UV. On UV editor, select Bones and select the bLegR bone. Select a few points and click "OK".
Minimal reproduction project:
GodotTest.zip

This is a very old graphics adapter. I wouldn't expect any OpenGL 2.0+ renderer to run correctly on it.

I don't know if this is a rendering issue or an editor issue, but just in case it is a rendering issue, try the latest build in #42119. This should deal with problems where the GPU does not support the skinning shader. I've only seen reports of this on android, but it could occur on other hardware.
The unified batching has a new software transform path for 2d skinning (you can turn it on and off in projectsettings->rendering->quality->2d->use_software_skinning).
If this doesn't fix it, then it may be an editor issue.

I don't know if this is a rendering issue or an editor issue, but just in case it is a rendering issue, try the latest build in #42119. This should deal with problems where the GPU does not support the skinning shader. I've only seen reports of this on android, but it could occur on other hardware.
The unified batching has a new software transform path for 2d skinning (you can turn it on and off in projectsettings->rendering->quality->2d->use_software_skinning).
If this doesn't fix it, then it may be an editor issue.

I visited the build in #42119 and download the GLES3 Batching version 0.15.
It solved the problem. Thank you very much!
Should I close the issue here ?

I don't know if this is a rendering issue or an editor issue, but just in case it is a rendering issue, try the latest build in #42119. This should deal with problems where the GPU does not support the skinning shader. I've only seen reports of this on android, but it could occur on other hardware.
The unified batching has a new software transform path for 2d skinning (you can turn it on and off in projectsettings->rendering->quality->2d->use_software_skinning).
If this doesn't fix it, then it may be an editor issue.

I visited the build in #42119 and download the GLES3 Batching version 0.15.
It solved that problem, but created another problem. The bones rotation doesn't work properly.
Maybe the problem is my GPU, but everything works fine in DragonBones.
Could you try to run my attached project? If it works well for you, then I'll need a new notebook.

It's more likely there is a small bug in the new 2d software skinning.
There was a small area where I resorted to guesswork, I only had one test project, so it should be quite simple to fix when I have more test cases. Basically the case was where the weights didn't add up to 1.0, or when no weights were applied. I'm really waiting on testing to identify the correct way of doing this, you are the very first tester!
When I tried your project yesterday it seemed the same between the software and old path, but I didn't try bone rotation I'll have a look. :+1:
I'm pretty sure you don't need a new notebook. :smile:

@lawnjelly I appreciate your help. I really need Godot for this project, it will be impossible to make it in Love2D.
Maybe the video wasn't clear enough, but now I've put some subtitles, I think the bug is clear to see.
new video: https://youtu.be/J7u6Fkg5zwA
Just let me know if it is not enough , then I will try to make a new video or a new project.

Yeah I think I see what is going wrong, but I need a project with the vertices weighted to the bones so I can debug it.

@lawnjelly there it goes.
just open the project and click "play"
GodotTest.zip
you should see something like this:

Thanks! :+1: I'm debugging it at the moment.
Getting skinning working is always a bit finicky and there are a few transforms available and with no comments in the code it's a case of trial and error to work out what each does and fit them together in the right order. I'm confident it should work fine though once I've cracked it .. it might be in a few days though, as I have to go away from home again.
Once it is working I'll do another build.

Back home and after spending some time this morning I've finally tracked this down. It was down to an offset on the polygons used to rig the model. God only knows why it actually works in the original shader version lol. :rofl:
And actually I there is a AABB bound check somewhere else pre-existing in the CPU side code for culling that doesn't take this into account which may also be buggy I'll double check this, fix two bugs at once kind of thing.
I'll possibly do a bit of rearranging to make it more efficient, then will need to rebase the PR after Pouley's skinning, then see if I can make a new build for testing. :+1:

@lawnjelly thank you for replying.
It still weird... the skins are stretching when I move the bones.
Sadly, I tested the same code on my nephew's PC, and it was running perfectly!
I need a new notebook.
Anyway, thanks for your help. I appreciate

Double check you have 2d skinning switched on in build 0.16. I'll check I haven't made some mistake in the build. If you are running the test project you gave me, it should either run completely correctly or not at all.
There should be no situation with skin stretching possible using that path, unless you are using a different project (in which case there may be another bug to fix). This is very likely a mistake on my side.
It is very unlikely your computer is at fault. With software skinning the calculations are done on the CPU, and all CPUs can do this. The GPU is only showing on the screen the positions calculated on the CPU. This is very different from GPU skinning, where huge variations in hardware can lead to the process failing.

@lawnjelly the option "use software skinning" was unchecked !
I checked and it works perfect now! Thank you very much!

Yay!! :grin:

Fixed by #42119.


Add cool music!

Like this? (ask author for permission)
https://www.youtube.com/watch?v=sIBzhU06Fl4

https://www.youtube.com/watch?v=xe4bUkk-loI


Import Project Template from AICoE projects

Since redhat-et org doesn't have any cookie-cutter project template, we feel we should import the template just for this Data Science Project, just to get a headstart and a better organized repository.
cc - @suppathak @MichaelClifford @erikerlandson

@MichaelClifford - Yes, I believe the import of the template wasn't done beforehand, so this seems like an option. But since we don't have a lot of content yet, we can always setup a new repo.


Add notBeforeSkew option

When the clock of the identity provider is ahead of the relying party, a SAML assertion may end up having a notBefore date that appears to be in the future. This causes the assertion to be rejected. It would be nice if we could tell SamlClient that we're willing to accept some skew in server time to prevent these assertions failing.
Because assertions already take into account that there may be latency between servers, it does not seem necesary to me to skew the notOnOrAfter date. If we do want this it would be very simple to skew both notBefore and notOnOrAfter, though.
ADFS provides an option notBeforeSkew that allows you to accept assertions that appear to be in the future by a certain amount. This pull request introduces a similar feature to saml-client.
See ADFS docs for more info on the flag. (ctrl-f notbeforeskew)
This blog contains a short how-to (not by me) of using the ADFS version.
If there are any changes you'd like to see I'd be happy to implement them.
Kind regards

Thanks for this! Just one small comment about the exception message, but overall looks perfectly reasonable to me.

Here you go. I published a new release with this change too. Thanks for the contribution!


macOS Touch Bar warning

I am receiving the following warning when I render in OpenAI gym:
2020-11-21 20:55:19.522 python3[24131:283512] Warning: Expected min height of view: (<NSPopoverTouchBarItemButton: 0x7fe5980e7480>) to be less than or equal to 30 but got a height of 32.000000. This error will be logged once per view in violation.
2020-11-21 20:55:19.522 python3[24131:283512] Warning: Expected min height of view: (<NSButton: 0x7fe5987aaab0>) to be less than or equal to 30 but got a height of 32.000000. This error will be logged once per view in violation.
2020-11-21 20:55:19.525 python3[24131:283512] Warning: Expected min height of view: (<NSPopoverTouchBarItemButton: 0x7fe5987adce0>) to be less than or equal to 30 but got a height of 32.000000. This error will be logged once per view in violation.
2020-11-21 20:55:19.526 python3[24131:283512] Warning: Expected min height of view: (<NSPopoverTouchBarItemButton: 0x7fe5987b5a80>) to be less than or equal to 30 but got a height of 32.000000. This error will be logged once per view in violation.

I am using a Macbook Pro with a Touch Bar. The warning seems to indicate that a window with a height greater than 30 is opening in the Touch Bar. This warning does not occur on my other Macbook Pro that does not have a Touch Bar. The code I am running is:
import gym
import numpy as np

env = gym.make('CartPole-v1')

for _ in range(10):
    observation = env.reset()
    done = False

    while not done:
        env.render()
        action = env.action_space.sample()
        observation, reward, done, info = env.step(action)

env.close()

I am not sure if this warning has to do with pyglet, but it only occurs when rendering.
Other info:

macOS 11.0.1 (Big Sur)
Python 3.8.3
pyglet 1.5.11

Could you try a pyglet-only example, and see if it has the same message? Such as the hello_world.py file in the examples folder in the repo.
I see that there are a few reports around Github for other projects with the same error, but didn't see any resolutions.

Sure, will check this out and get back to you.

I ran hello_world.py from /examples and am running into the following error:
Traceback (most recent call last):
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/__init__.py", line 336, in __getattr__
    return getattr(self._module, name)
AttributeError: 'NoneType' object has no attribute 'Window'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "pyglettest.py", line 3, in <module>
    window = pyglet.window.Window()
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/__init__.py", line 342, in __getattr__
    __import__(import_name)
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/window/__init__.py", line 1888, in <module>
    from pyglet.window.cocoa import CocoaWindow as Window
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/window/cocoa/__init__.py", line 44, in <module>
    from pyglet.canvas.cocoa import CocoaCanvas
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/canvas/__init__.py", line 102, in <module>
    from pyglet.canvas.cocoa import CocoaDisplay as Display
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/canvas/cocoa.py", line 41, in <module>
    from pyglet.libs.darwin.cocoapy import CGDirectDisplayID, quartz, cf
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/libs/darwin/__init__.py", line 36, in <module>
    from .cocoapy import *
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/libs/darwin/cocoapy/__init__.py", line 37, in <module>
    from .cocoalibs import *
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/site-packages/pyglet/libs/darwin/cocoapy/cocoalibs.py", line 19, in <module>
    cf.CFStringCreateWithCString.restype = c_void_p
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/ctypes/__init__.py", line 386, in __getattr__
    func = self.__getitem__(name)
  File "/Users/ebolotin/opt/miniconda3/lib/python3.8/ctypes/__init__.py", line 391, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: dlsym(RTLD_DEFAULT, CFStringCreateWithCString): symbol not found

Thoughts?

Hmm, that's pretty strange, especially since pyglet was working as part of Gym. It seems like something strange with the pyglet installation, or potentially the environment.

apparently this is a BigSur issue

apparently this is a BigSur issue

Yeah I think so too... Will close this for now.

It will go away if you compile your native code with a modern-enough Xcode (Command Lines Tools)? package


compare region viewer returns genome_id null

https://patricbrc.org/view/Feature/PATRIC.1396.2531.WBPM01000024.CDS.796138.796953.fwd#view_tab=compareRegionViewer
if you switch genomes from reference to all public genomes, it returns null
this is the payload,
{"params":["fig|1396.2531.peg.5782",10000,10,"pgfam","all"],"method":"SEED.compare_regions_for_peg","version":"1.1","id":64054}

solr side error is Cannot parse \'genome_id: AND (sequence_id: OR accession:) AND (start:[1 TO 10000] OR end:[1 TO 10000]) AND annotation:PATRIC AND NOT feature_type:source\


Privacy policy approval checkbox

Description:
Privacy policy and terms approval
"To continue using, you will agree to our terms and privacy"

This is done with https://github.com/ruuvi/com.ruuvi.station.webui/issues/414


set windows dir to LOCALAPPDIR

Hi!  I am not sure if anyone else is having problems, but my University has put a GroupPolicy in place that no executables can be placed in the LocalAppDir.  (Pretty standard security nowadays).  However, this is causing the Heroku Toolbelt to be unusable because it seems to want to write heroku-cli.exe into the LocalAppDir.
Is there any way to choose a different directory in a settings file or potentially during the installation process?
Thanks so much!


New Endpoints for Static Data API

https://discussion.developer.riotgames.com/articles/4906/announcing-new-endpoints-for-static-data-api.html

Sorry guys I wasn't able to work on this earlier (as well as the caching thing that I recently released), I was pretty stressed about an eye surgery/school/etc. Now that it's done though, I can start working more on keeping this more up-to-date promptly. :)


Admin takeover article additions/revisions

@pebaum @alin.constantin Please review two admin takeover articles.
FREELANCERS: Please DO NOT merge these changes. Thank you.

Im merging to get the changes into the private repo - we can iterate on the live docs as necessary.
PB
From: Leslie H Cole @.>
Sent: Tuesday, January 18, 2022 1:48 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Peter Baumgartner @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Admin takeover article additions/revisions (PR #7425)
@pebaumhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpebaum&data=04|01|peter.baumgartner%40microsoft.com|c6a636e9031047a8a62408d9dacc326b|72f988bf86f141af91ab2d7cd011db47|1|0|637781392842734962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=aUzUT%2FWUb%2FN7xbYFVZAEPbU7XhnFtpMAiJOvHAtoTF4%3D&reserved=0 @alin.constantin Please review two admin takeover articles.
FREELANCERS: Please DO NOT merge these changes. Thank you.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fpull%2F7425%23issuecomment-1015864331&data=04|01|peter.baumgartner%40microsoft.com|c6a636e9031047a8a62408d9dacc326b|72f988bf86f141af91ab2d7cd011db47|1|0|637781392842734962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=7mh8oGLP7c61DGnAV1kIrElnqxNb7O37Lu0GdcwsRkA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHYLATCPHORO3M2SEUSX2BDUWXNY7ANCNFSM5MIIOWIQ&data=04|01|peter.baumgartner%40microsoft.com|c6a636e9031047a8a62408d9dacc326b|72f988bf86f141af91ab2d7cd011db47|1|0|637781392842734962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=P674POmo9DMRijUjHROVlu6OkTMhq%2Bf1iCYxAwIaD8o%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|peter.baumgartner%40microsoft.com|c6a636e9031047a8a62408d9dacc326b|72f988bf86f141af91ab2d7cd011db47|1|0|637781392842734962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=wA1B7vTXKFJfhihifqoVJcOYLWTavsKwZqKEoTtZUGE%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|peter.baumgartner%40microsoft.com|c6a636e9031047a8a62408d9dacc326b|72f988bf86f141af91ab2d7cd011db47|1|0|637781392842784955|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=4USuBPBuTCjExkUSV6bwsHWZbABkG0RgRRa3mE2GLMU%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


[CLI] Double check execution WASM in new crust-node

make sure in the new crust node, we use --execution WASM

We already added in https://github.com/crustio/crust-node/pull/96


wlr_seat: restore NULL behavior for notify_enter

Unifies the behavior of wlr_seat_*_notify_enter with that of wlr_seat_*_enter when NULL is passed for the surface parameter.  Provides a non-breaking alternative for the fix in #2217 by using the grab interface.

We decided against this approach. See the discussion in https://github.com/swaywm/wlroots/pull/2162#issuecomment-625083795

Thanks - missed that part of the discussion.

Yeah, it wasn't properly linked from the PR - sorry about that.


chore: avoiding calling through the mesh to same services components

References https://github.com/lightbend/kalix-proxy/issues/1469 and depends on https://github.com/lightbend/kalix-proxy/pull/1599

I think I understand. When it tries to reach an gRPC from the same Kalix service uses some headers. I think it advertises that is self. But when it reaches another gRPC from another Kalix service it signals that is some other service. Or maybe the lack of self is sufficient. And finally when reaching gRPC not of a Kalix service doesn't say whether if it is self or not self.

You can see the different pairs of headers for self vs other Kalix services coming from the proxy and passed on to each component here:
https://github.com/lightbend/kalix-javascript-sdk/blob/main/sdk/src/kalix.ts#L684
Then used in GrpcUtils here:
https://github.com/lightbend/kalix-javascript-sdk/blob/main/sdk/src/grpc-util.ts#L155
and here:
https://github.com/lightbend/kalix-javascript-sdk/blob/main/sdk/src/grpc-util.ts#L159

See https://github.com/lightbend/kalix-jvm-sdk/pull/1055/files#r925790190

commits squashed and rebased with #400.
Waiting for #400

Depends on #400 (new proxy version)

#400 is merged now

This is now rebased with main (use new proxy version) and is ready for merge.
Johan had a change request, but Cisco has already implemented it.

CI is failing on the testkit's own integration tests, and looks like a relevant failure:
1) The Kalix IntegrationTestkit
       should handle self-delegating actions (with acl):
     Error: 2 UNKNOWN: Cross component call failed

I'll have a look

@franciscolopezsancho, with the change from proxyInfo.proxyPort back to this.proxyPort, does that mean we're not using the proxy port passed from the proxy any longer — breaking the feature, especially in actual deployments?

You are right I fixed it in https://github.com/lightbend/kalix-javascript-sdk/pull/410. Please have a look.


401

Ⅰ. Issue Description
login in Hong Kong, 401 authorization required.

URL: | https://www.cqhyw.cn/
-- | --
Server: | rancher-server
Date: | 2024/08/20 11:02:29

Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

Please contact the corresponding website administrator, the website administrator determines the 401 logic.


Can't get option ROUTER_HANDOVER from ROUTER socket

Hi!
I'm trying to retrieve a socket option from a ROUTER socket, but I get "Exception has occurred: ZMQError".
Minimal example:
import zmq

context = zmq.Context()
socket = context.socket(zmq.ROUTER)
socket.bind("ipc://dev.ipc")
socket.getsockopt(zmq.ROUTER_HANDOVER)

Any ideas?

It looks like ROUTER_HANDOVER is a write-only attribute. It's in setsockopt, but not getsockopt.
You can submit a feature request to libzmq to expose it to getsockopt.


[reasonPhrase:GuzzleHttp\Psr7\Response:private] => Forbidden

I am trying to index url using php (CodeIgniter 4)
My Code Below.
namespace App\Libraries;
use Google_Client;
use GuzzleHttp;
use GuzzleHttp\Client;
use CodeIgniter\HTTP;
require_once ROOTPATH.'/vendor/google/apiclient-services/autoload.php';
class Google
{
// This function converts a string into slug format
public function add_to_index($url)
{
$googleCli = new Google_Client();
$googleCli->setAuthConfig(MY_JSON_FILE');
$googleCli->addScope('https://www.googleapis.com/auth/indexing');
// Get a Guzzle HTTP Client
$httpClient = $googleCli->authorize();
$endpoint = 'https://indexing.googleapis.com/v3/urlNotifications:publish';
// Define contents here. The structure of the content is described in the next step.
$content = '{
"url": "'.$url.'",
"type": "URL_UPDATED"
}';
$response = $httpClient->post($endpoint, [ 'body' => $content ]);
return $response;
}
}
its showing error
GuzzleHttp\Psr7\Response Object
(
[reasonPhrase:GuzzleHttp\Psr7\Response:private] => Forbidden
[statusCode:GuzzleHttp\Psr7\Response:private] => 403
[headers:GuzzleHttp\Psr7\Response:private] => Array
(
[Vary] => Array
(
[0] => X-Origin
[1] => Referer
[2] => Origin,Accept-Encoding
)
        [Content-Type] => Array
            (
                [0] => application/json; charset=UTF-8
            )

        [Date] => Array
            (
                [0] => Tue, 05 Mar 2024 08:23:16 GMT
            )

        [Server] => Array
            (
                [0] => ESF
            )

        [Cache-Control] => Array
            (
                [0] => private
            )

        [X-XSS-Protection] => Array
            (
                [0] => 0
            )

        [X-Frame-Options] => Array
            (
                [0] => SAMEORIGIN
            )

        [X-Content-Type-Options] => Array
            (
                [0] => nosniff
            )

        [Alt-Svc] => Array
            (
                [0] => h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
            )

        [Accept-Ranges] => Array
            (
                [0] => none
            )

        [Transfer-Encoding] => Array
            (
                [0] => chunked
            )

    )

[headerNames:GuzzleHttp\Psr7\Response:private] => Array
    (
        [vary] => Vary
        [content-type] => Content-Type
        [date] => Date
        [server] => Server
        [cache-control] => Cache-Control
        [x-xss-protection] => X-XSS-Protection
        [x-frame-options] => X-Frame-Options
        [x-content-type-options] => X-Content-Type-Options
        [alt-svc] => Alt-Svc
        [accept-ranges] => Accept-Ranges
        [transfer-encoding] => Transfer-Encoding
    )

[protocol:GuzzleHttp\Psr7\Response:private] => 1.1
[stream:GuzzleHttp\Psr7\Response:private] => GuzzleHttp\Psr7\Stream Object
    (
        [stream:GuzzleHttp\Psr7\Stream:private] => Resource id #220
        [size:GuzzleHttp\Psr7\Stream:private] =>
        [seekable:GuzzleHttp\Psr7\Stream:private] => 1
        [readable:GuzzleHttp\Psr7\Stream:private] => 1
        [writable:GuzzleHttp\Psr7\Stream:private] => 1
        [uri:GuzzleHttp\Psr7\Stream:private] => php://temp
        [customMetadata:GuzzleHttp\Psr7\Stream:private] => Array
            (
            )

    )

)

I've the same issue.

I've found the solution for me, verify for you : Web Search Indexing API was not activated.
Now, it's work.

I've found the solution for me, verify for you : Web Search Indexing API was not activated.
Now, it's work.

in my case it's activated and verified
still same issue


Dynamic URLs for pagination

Hi @owen2345,
please let me know how to remove/re-route dynamic URLs, which are generated from pagination.
As per google dynamic URLs need to removed or re-routed to static URL, otherwise it will impact page and site rankings..so pls let me know how to route them as static URLs.
e.g.
http://example.com/sell?page=4
http://example.com/sell?page=5

Hi @mazharoddin
where are generated this url's?
Regards,

I don't think these urls have defined routes, hence the task would be to add such routes rather than change them. The urls are probably generated by will_paginate in the naive fashion of appending page=X param to the current params.

hi @owen2345, these URLs are generated by one of my custom post type, I created one custom post type and added multiple posts, so that custom post type pagination generated these URLs.

It is the pagination generated by will_paginate gem, if you don't want this, please edit the template as you want.


Korok Seed Guide with Credit-Based Assistance Levels

I want a Korok Seed Guide to help me find all 900 Korok seeds hidden throughout Hyrule. I want the option to spend in-game credits for different levels of guidance, allowing me to choose how much help I receive based on my progress and preferences.

Redundant issue.


Vulnerability roundup 91: lua-5.2.4: 1 advisory [7.5]

search, files

[ ] CVE-2020-15945 CVSSv3=7.5 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: 977000f149b; nixos-unstable: 840c782d507. May contain false positives.

See also: #93986

Only applies to lua 5.4 https://ubuntu.com/security/CVE-2020-15945


now with xargs immediately exits

To tidy up old unused deployments, I run a custom script called now-no-alias and I pluck the uid and now rm them.
The workflow is:
$ now-no-alias | json -a uid | xargs now rm

This used to work, and it would prompt me with [Y/n] to remove the deployments. Except, now it doesn't.
When I run it through a pipe from xargs it exits (success) without doing anything:

I'd love to see this fixed again…though I've no idea what now is looking for to make this fail the way it is.

You need to use the --yes flag. i.e.
$ now-no-alias | json -a uid | xargs now rm --yes


Say that we use a dictionary of strings.

Resolves #3856.

Codecov Report

Merging #3857 into master will not impact coverage.

@@           Coverage Diff           @@
##           master    #3857   +/-   ##
=======================================
  Coverage   89.05%   89.05%
=======================================
  Files          15       15
  Lines        1873     1873
=======================================
  Hits         1668     1668
  Misses        205      205

Continue to review full report at Codecov.

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


applying black to the template project

/azp run python - template - ci

This PR has no changes. There must be something else causing the Analyze failure.


undefined symbol: gotoblas issue

my environments:

python
Python 2.7.12+ (default, Nov 22 2016, 00:48:54)
[GCC 6.2.1 20161119] on linux2
Type "help", "copyright", "credits" or "license" for more information.

os

uname -a
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux

the following log:

import numpy as np
File "/usr/lib/python2.7/dist-packages/numpy/init.py", line 153, in
from . import add_newdocs
File "/usr/lib/python2.7/dist-packages/numpy/add_newdocs.py", line 13, in
from numpy.lib import add_newdoc
File "/usr/lib/python2.7/dist-packages/numpy/lib/init.py", line 18, in
from .polynomial import *
File "/usr/lib/python2.7/dist-packages/numpy/lib/polynomial.py", line 19, in
from numpy.linalg import eigvals, lstsq, inv
File "/usr/lib/python2.7/dist-packages/numpy/linalg/init.py", line 50, in
from .linalg import *
File "/usr/lib/python2.7/dist-packages/numpy/linalg/linalg.py", line 29, in
from numpy.linalg import lapack_lite, _umath_linalg
ImportError: /usr/lib/libblas.so.3: undefined symbol: gotoblas

can you post 'pip freeze' and 'help (modules)' (attach .txt if more than dozen lines)
How did you compile/install OpenBLAS and numpy?
What does 'update-alternatives --list libblas.so.3' say?

pip freeze
Traceback (most recent call last):
File "/usr/local/bin/pip", line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

update-alternatives --list libblas.so.3
/usr/lib/libblas/libblas.so.3
/usr/lib/openblas-base/libblas.so.3

Try doing "sudo update-alternatives --set libblas.so.3 /usr/lib/openblas-base/libblas.so.3" to switch from the (unoptimized netlib reference ?) blas version currently installed as default on your system to the OpenBLAS that your numpy build expects.

ok, it is not a openblas bug, when i use anaconda python,  now it can work.
thank you for your support.

Then the anaconda version was probably built against the non-optimized blas - you can read about the options in https://github.com/scipy/scipy.org/blob/master/www/scipylib/building/linux.rst#debian--ubuntu
(I do hope that most if not all of the bugs that made them advise against using OpenBLAS two years ago
have been addressed in the meantime - in my experience, OpenBLAS is substantially faster than Atlas and the reference implementation with its lack of hardware-specific optimization is naturally the slowest.)

your advise  and your link are very helpful, I will try it.

Can you close the issue?
You have ubuntu python in the text you posted. Ubuntu numpy (installed via APT) will respect update-alternatives.
Continuum anaconda (not in posted text) calls openblas 'nomkl' as opposed to default 'mkl', it is described in their numpy documents how to switch back and forth.


spaces, min amount witdraw and add modals

Pull request template
Checklist

[ ] I have read the CONTRIBUTING guide
[ ] branch rebased on develop
[ ] styleguide check npm run validate
[ ] good naming
[ ] keep simple
[ ] video or screenshot attached
[ ] testing instruction attached
[ ] check your PR once again

Description

Video or screenshot

What and how to test

почемуто перезалит пул https://github.com/swaponline/swap.react/pull/1022

@DariaPurtova сделай пруфрид этих надписей

@DariaPurtova сделай пруфрид этих надписей

Make sure the wallet you're sending the funds to supports BTC

(Please note) Miners' fee is 0.001 BTC.  This amount is equivalent to miners' fee

Предлагаю:

фразу "Make sure the wallet you're sending the funds to supports BTC" поместить в "?" после Address. A в поле, куда надо вставить адрес, написать (Enter) BTC wallet address
второе поле: Enter the amount (you want) to withdraw/transfer. You have 0.0054 BTC


Fix page layout in case of hovering over carousel

Signed-off-by: Yash Agarwal<EMAIL_ADDRESS>Description
Fixed the page layout which was being caused by disappearing scrollbars on hover over carousel
This PR fixes #3916
Notes for Reviewers
Although the page layout issue has been fixed. The fix causes a new issue. If we have already scrolled the page a little bit and then we hover over the carousel. It scrolls to the top with a jerk and then disables scrolling for the body. To fix this, I tried to make the scroll a smooth scroll. But since the scroll to top is async function (I guess) changing the document layout to fixed runs first which was causing the issue of jerking while scrolling in the first place. So this method didn't work for me.
I tried to find a solution in which both the issues might get fixed, but I couldn't find a solution for that. Either of the issue always persists.

Codecov Report

Merging #3942 (90a7756) into master (9995635) will decrease coverage by 7.54%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3942      +/-   ##
==========================================
- Coverage   27.28%   19.74%   -7.55%
==========================================
  Files          63       63
  Lines        4787     4787
==========================================
- Hits         1306      945     -361
- Misses       3079     3553     +474
+ Partials      402      289     -113

Flag
Coverage Δ

e2etests
?

gointegrationtests
?

unittests
19.74% <ø> (ø)

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-62.83%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.15% <0.00%> (-55.00%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.90% <0.00%> (-39.10%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
1.78% <0.00%> (-32.15%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.17% <0.00%> (-29.42%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
0.00% <0.00%> (-21.60%)
:arrow_down:

Continue to review full report at Codecov.

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

Umm, i dont think we want this to happen. The scroll feels really tight and just doesnt work in some parts of the screen.
https://user-images.githubusercontent.com/53532328/130057318-c102e4bc-d663-46a8-bea2-c0753fa7ebd2.mov
@sudo-NithishKarthik @Abhishek-kumar09 @Meghana-12 any thoughts on this?

according to me one simple solution would be to disable the scroll over the vertical carousel and instead provide some buttons or rather the clicking on the images on the left also serve the purpose.

One thing is that, we definitely have to change this design, it is what it is because we were focused on first bringing it into meshery. Now that it is here, we should definitely think about redesigning this.
So, It would really be great if we can come up with a better design, pitch in your ideas.
With that being said,

according to me one simple solution would be to disable the scroll over the vertical carousel and instead provide some buttons or rather clicking on the images for metrics on the left also serve the purpose.

This definitely makes sense 💯 , it would be great if you can do it @yagarwal1307 ?
So, the left side scroll indicator is there, because, if a user knows that one of his adapters are connected and he wants to go directly to that one, if the scroll indicator was not there, he would have to keep clicking next till he reaches that adapter, which would degrade the user experience. But, i don't think the indicator is very appealing right now, so, if any of you have any better ideas, we can give it a try.

@sudo-NithishKarthik Okay so if its the final thing then I will surely do it!

@sudo-NithishKarthik Okay so if its the final thing then I will surely do it!

We can merge this once you've done this ✌🏽

@sudo-NithishKarthik I didn't realise that this was final. I thought there was some discussion still going on there as you had asked for some suggestions from others!
Would definitely do it tomorrow then!

@sudo-NithishKarthik I rather found the reason for that scrollbar issue, so I fixed that and now its working as expected.

We will track this in a different issue..

@warunicorn19 sorry was busy yesterday. Sure we should do that, looked weird to me as well.

No problem @yagarwal1307, already put in a fix✌.


Stopped creating kapp app configmap during --diff-run

kapp should not create kapp app configmap while doing any operation with --diff-run flag

I think we can rebase this on develop now.

I am thinking if the effects of --diff-run should just be limited to creation of ConfigMap or should they also extend to updates as well. For example, if we use --labels x=y, along with --diff-run while updating an app, should these labels be added to the ConfigMap?

I am thinking if the effects of --diff-run should just be limited to creation of ConfigMap or should they also extend to updates as well. For example, if we use --labels x=y, along with --diff-run while updating an app, should these labels be added to the ConfigMap?

I would expect nothing to change on the cluster if I use --diff-run. No configmaps created, no labels added, no changes. So in my mind, the answer to should the labels be added is no.

LGTM

Hi @praveenrewar,
As @neil-hickey correctly pointed out in the case of --diff-run we don't want to change anything on the cluster so we won't be adding the labels as well.

Please let me know your thoughts on changing this behaviour to not updating the configmap as part of this PR.

I'd vote for a separate issue / PR. This one should probably remain scoped to just the creation of the configmap.

After discussion with the team, we have decided to address the update flow as part of this PR only.


Fix misnamed MeshLab release tag

Description of changes
The package did not compile due to a misnamed release tag:
fatal: couldn't find remote ref refs/tags/Meshlab-2022.02
This fixes it by using the proper tag, and setting the hash accordingly
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Thanks for your contribution!
Would you please read CONTRIBUTING.md (especially https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions) and rewrite your commit message?
Thanks.

Thanks for the pointer. I hope it fits better now.

Result of nixpkgs-review pr 250485 run on aarch64-linux 1

1 package built:

meshlab


Installing with console throws exception

When installing the plug-in via console/command line an exception is throw because a notice is set on the session in the plug-in install event.
This causes issues for example when using a project.yml file when setting up a new project.
The question is if this check is really necessary on install? If this is the case at least a check should be done if the session is actually available.

If you're talking about the notice that the Contact form plugin is not installed, this only gets triggered when it's not a console request:
if (!Craft::$app->plugins->isPluginInstalled('contact-form') && !Craft::$app->request->getIsConsoleRequest()) {
    Craft::$app->session->setNotice(Craft::t('contact-form-extensions', 'The Contact Form plugin is not installed or activated, Contact Form Extensions does not work without it.'));
}

Is there a different notice you're talking about?

That's the one, but I see you've updated the code already.


how can i use vite with cmd or amd module

I have some file which wrote with cmd,amd,cjs， and I think vite can only use esm, though it can transform cjs to es(node_modules), how can I transform some code(use cmd,amd, cjs) ？
optimizeDeps can only transform node_modules, can I wrote some plugin to use webpack or rollup to transfom to umd which can be import by browser? i want that it only build in prebuild

I have some file which wrote with cmd,amd,cjs， and I think vite can only use esm, though it can transform cjs to es(node_modules), how can I transform some code(use cmd,amd, cjs) ？

As we know, vite can only use esm.I'm not sure for this files still maintaining?

For yes, maybe you should refactor that  by es6.It will help you a lot for future work.
For no, you can use webpack/rollup to transform that and use es6 version inside your codebase.

optimizeDeps can only transform node_modules, can I wrote some plugin to use webpack or rollup to transfom to umd which can be import by browser? i want that it only build in prebuild

Yeah.You can custom plugin to support it, see https://github.com/vitejs/vite/blob/98217e12f1b1c0591e8682f3895c8f5884e38fed/src/node/transform.ts#L47-L50. It can work for dev runtime. If you want it work for prebuild, that will need rewrite some code of vite....
In short, it is need hard work for a little case and it can be resolved by custom plugin.


[GSoC] Master rebase

Master rebase.
Database version Update.

I think that got in while fixing the conflict in PR, will update.


board: silabs: slstk3701a: add i2c2 node

Enable the I2C2 node on the EFM32GG11 SLSTK3701A board

logs:
uart:~$ device list
devices:
- gpio@40088400 (READY)
- leuart@4006a000 (READY)
- usart@40011000 (active)
- usart@40010000 (active)
- gpio@40088180 (READY)
- gpio@40088150 (READY)
- gpio@40088120 (READY)
- gpio@400880f0 (READY)
- gpio@400880c0 (READY)
- gpio@40088090 (READY)
- gpio@40088060 (READY)
- gpio@40088030 (READY)
- gpio@40088000 (READY)
- i2c@40089800 (READY)
- i2c@40089400 (READY)
- i2c@40089000 (READY)

Hi @jhedberg,
Thanks for the approval!
I'm not entirely familiar with the process, so could you let me know if there's anything else I need to do after the PR is approved?

I'm not entirely familiar with the process, so could you let me know if there's anything else I need to do after the PR is approved?

There's nothing else you need to do. The Zephyr project is right now in code freeze for Zephyr 4.0, so the PR should get merged after the release is out.


[release-1.6] Do not enable auto mtls when cluster type is Cluster_ORIGINAL_DST

Manual cherrypick required.
#24319 failed to apply on top of branch "release-1.6":
Using index info to reconstruct a base tree...
M	pilot/pkg/networking/core/v1alpha3/cluster.go
M	pilot/pkg/networking/core/v1alpha3/cluster_test.go
A	pkg/test/framework/features/README.md
M	tests/integration/pilot/cni/cni_test.go
M	tests/integration/security/mtls_first_party_jwt/strict_test.go
M	tests/integration/security/mtlsk8sca/strict_test.go
M	tests/integration/security/reachability_test.go
M	tests/integration/security/util/reachability/context.go
Falling back to patching base and 3-way merge...
Auto-merging tests/integration/security/util/reachability/context.go
CONFLICT (content): Merge conflict in tests/integration/security/util/reachability/context.go
Auto-merging tests/integration/security/reachability_test.go
CONFLICT (content): Merge conflict in tests/integration/security/reachability_test.go
Auto-merging tests/integration/security/mtlsk8sca/strict_test.go
Auto-merging tests/integration/security/mtls_first_party_jwt/strict_test.go
Auto-merging tests/integration/pilot/cni/cni_test.go
CONFLICT (modify/delete): pkg/test/framework/features/README.md deleted in HEAD and modified in disable tls for headless service when mtls is auto detected. Version disable tls for headless service when mtls is auto detected of pkg/test/framework/features/README.md left in tree.
Auto-merging pilot/pkg/networking/core/v1alpha3/cluster_test.go
Auto-merging pilot/pkg/networking/core/v1alpha3/cluster.go
error: Failed to merge in the changes.
Patch failed at 0001 disable tls for headless service when mtls is auto detected

Cherrypicked in https://github.com/istio/istio/pull/25829


Merge pull request #1 from coreos/master

update9.13
Description

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

update

You can't comment at this time — your comment cannot be blank


could you share the X.npy and Y.npy file using in your notebook?

Hi, @AlfredCYL
I like your project as I'm planning doing similar things. It would be helpful if you could share those data files you used in your example notebook. Thanks

Thanks for your interest in the project! You can access the data files used in our example notebook via this link: Google Drive link.
Feel free to use them as a reference for your project. If you have any questions or need assistance in the future, please don't hesitate to reach out.


[WIP] Release payload migration tool

This PR adds a migration tool that interrogates the specified release imagestream (ocp/release by default) and creates all the corresponding ReleasePayload objects from the tags included in the aforementioned imagestream.
By default, the tool will not make any changes to the user's currently configured oc environment, it will only write the JSON resources to a temporary location on the user's filesystem.
./migration-tool
I1215 08:49:20.916239  210308 main.go:127] Running in Dry-Run mode.  No objects will be created on cluster.
I1215 08:49:26.353359  210308 main.go:223] Processing ImageStream: ocp/release
<...>
I1215 08:49:26.366937  210308 main.go:460] Writing 573 ReleasePayloads to: /tmp/payloads-896064367

Calling the tool with the --execute option will perform the resource creation on the cluster.
./migration-tool --execute
I1215 08:56:00.490976  210576 main.go:223] Processing ImageStream: ocp/release
<...>
I1215 08:56:00.504635  210576 main.go:509] Creating ReleasePayloads

It is possible to also specify a --location parameter with the full path to a previous execution's output:
./migration-tool --location /tmp/payloads-753186387 --execute
I1215 08:57:11.955292  210684 main.go:483] Reading ReleasePayloads from: /tmp/payloads-896064367
<...>
I1215 08:57:11.996501  210684 main.go:509] Creating ReleasePayloads

/remove-lifecycle stale

/remove-lifecycle stale
/lifecycle frozen

/remove-lifecycle stale

/close


improve "proxy" preset to support tunnel mode for testing

By providing host and port, the preset will not act as a proxy server but a tunnel server:
// blinksocks.client.json
{
  "host": "localhost",
  "port": 1080,
  "servers": [{
    "enabled": true,
    "host": "localhost",
    "port": 1081,
    "presets": [{
      "name": "proxy",
      "params": {
        "host": "localhost",
        "port": "1082"
      }
    }],
    ...
  }],
  ...
}

Use iperf to test network performance:
applications <----> [blinksocks client] <----> [blinksocks server] <----> localhost:1082
 (iperf -c)           localhost:1080             localhost:1081             (iperf -s)

ea3e8d08b3ef868fbcc7164f980d2a1c2b5319d3


[Docs] Grammar Edit on Enabling HTTPS Using Reverse Proxy

As per title.
This PR fix grammar errors I made from #9491.

Codecov Report

Merging #9649 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #9649      +/-   ##
=========================================
+ Coverage   42.19%   42.2%   +<.01%
=========================================
  Files         583     583
  Lines       77234   77234
=========================================
+ Hits        32590   32594       +4
+ Misses      40636   40634       -2
+ Partials     4008    4006       -2

Impacted Files
Coverage Δ

modules/log/event.go
64.61% <0%> (-1.03%)
:arrow_down:

models/gpg_key.go
55.59% <0%> (+0.55%)
:arrow_up:

services/pull/merge.go
53.92% <0%> (+0.78%)
:arrow_up:

Continue to review full report at Codecov.

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


Godot 4 fails to run on Pop OS

Godot version
Godot Engine v4.0.alpha16.official
System information
Pop OS 22.04
Issue description
The program fails to start up with the follow command line listings.
godot_dump.txt
Steps to reproduce
Attempt to open the program.
Minimal reproduction project
No response

It looks to be an issue with glibc breaking compatibility. Version 3.5 works just fine.

Duplicate of https://github.com/godotengine/godot/issues/65409.


Changing the update procedures generated a new bug

For some reason, when we use the update routine, instead of going to the playstore update page, a page is being presented, with a question: Install in other locations.
See the screen below (in Portuguese) (instalar em outros locais).

Any idea?

Hello, @paulobreim.
What do you mean with "update routine"? The API only provides methods to check if there's updates available, but does not provide any method to update the app.
Can you provide an example?
Thanks!

Hummm you are right. After received that there are a new version, I launch a URL like:
https://play.google.com/store/apps/details?id=aeroescuta.com.br
This command showed to update, but now somethings change there and not work anymore.
I will search to see what Google change.
Tks
paulo


[DO NOT MERGE] Add Skillset operations (customized, generated, unit tests) code

Description

Add Skillset operations (customized, generated, unit tests) code
The corresponding swagger changes are:
https://github.com/Azure/azure-rest-api-specs/pull/3208
https://github.com/Azure/azure-rest-api-specs/pull/3301
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@jeji1101 In future PRs, please create a topic branch before submitting your PR. Instead of merging jeji1101:search-preview to Azure:search-preview, you should be merging from your own branch like jeji1101:add-skillsets or something.

@azuresdkci Test this please

This PR will be closed due to repo updates, please rebase from psSdkJson6 and open a new PR when ready


[ie/NhkRadiru] Extract extended description

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Pieces that make up an extended description are available through a
programme info API. They are, in order:

short summary
longer description
the host(s)
list of songs played

The host(s) field is free text, so it wouldn't be practical to put it in
cast. the order of items is copied from the mobile app - other orders
are used on the website's timetable, but I couldn't find the API etc
where they actually come from.
API info is gotten from https://www.nhk.or.jp/radio/config/config_web.xml,
which is the same endpoint used in NhkRadiruLiveIE. I don't think a
BaseIE etc is worth it at this time.
I've made an attempt to only download the API info once when downloading
a playlist. I'm not sure it's the best/proper way to do it, but it works.
If extracting the extended description fails, it throws a warning and
falls back to the summary.
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

thank you!


Updated kubernetes-csi/external-snapshotter to v6.1.0

Issue #, if available:
closes #1268
Description of changes:
Updated  kubernetes-csi/external-snapshotter to v6.1.0 for all versions. Go version is still 1.18.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_026d650a-11f8-4eac-b792-f9be0d6b66fb/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_026d650a-11f8-4eac-b792-f9be0d6b66fb.git

Docs Build status updates of commit f32f589:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-ServiceAccountCannotAccessRepository] Your repository https://github.com/VSC-Service-Account/docs-archive-test-source has enabled Docs Build service account. It seems that at least one of the accounts, e2ebd1, does not have Read permission to the repo. Please ask your repo admin to grant correct permission to service accounts (refer to this document: https://review.docs.microsoft.com/en-us/engineering/projects/ops/engdocs/how-to-grant-service-account-permission-in-your-repository?branch=master#ops-e2e-ppe) and then retry the build. Don't know who to contact? Refer https://repos.opensource.microsoft.com/VSC-Service-Account/repos/docs-archive-test-source/permissions/ to get admin list of the repo if the repo is in one of the organizations Microsoft owns.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


minor suggestions

2019-chee-wm.pdf
This issue can be closed when you've considered and potentially implemented the suggestions marked above.

closed with #3.


unable to print basis

suddenly without changes by me, the model basis is not printing when I use:
print(model.trace())
print(model.summary())
(I don't recall whether it printed at end of trace or with summary...but it was working fine and just suddenly stopped printing)
also, with
model.basis_
I receive this:  <pyearth._basis.Basis at 0x21d8d8c26c8>
This wasn't what I was expecting...
I was able to get an output with one of the functions in the export file - export_python_string(earth_model, function_name="model") - however I'm not confident in interpreting this output correctly.
I've tried replacing the earth file with a new one, and reinstalling pyearth. So far the best I have is the export output. I'm looking for the basis summary that lists the variables in relation to constant, coefficient and pruning pass result. Any thoughts?
Thank you!

@miele100 There must have been some kind of change.  Did you update Python or some other packages?  Were you using a Python installed by your operating system that might have suffered an automatic update?  Also, can you tell me what is printing when you attempt?  Is it just nothing?  I'm asking because I'm not sure what caused your issue and I want to figure out if it's going to affect other people.
Regardless of the above, I would suggest trying:
print(repr(model.summary())

and
print(str(model.summary())

Perhaps one of those will fix your problem.  If they don't, will you please respond with whatever output you are seeing?

I made no updates, so it was odd to me that it just stopped working.
Thank you for the suggestions. Both result in this syntax error:
print(str(model.summary())
File "", line 1
print(str(model.summary())
^
SyntaxError: unexpected EOF while parsing
print(model.trace()) does not result in error, it returns forward pass and pruning pass results.
print (model.summary) results in a list of the parameters.
Here is the error from print(model.summary()) :
print (model.summary())
Traceback (most recent call last):
File "", line 1, in
print (model.summary())
File "C:\Users\username\Anaconda3\lib\site-packages\pyearth\earth.py", line 919, in summary
data.append([str(bf), 'Yes' if bf.is_pruned() else 'No'] + [
File "pyearth/_basis.pyx", line 883, in pyearth._basis.LinearBasisFunction.str
TypeError: unsupported operand type(s) for +=: 'int' and 'str'
Also, model.mse_, model.rsq, etc. seem to work just fine.

@miele100 I mismatched the parentheses in those print statements.  If you fix them it will fix the syntax error.  However, based on your traceback, it looks like the labels in your basis functions are for some reason integers instead of strings.  Would it be possible to share your entire script?  I would also say that this is a bug in py-earth, since I think py-earth should be able to handle this situation, so I'm marking this issue as a bug.

Yes that was it. I switched scaling functions (I used one from sklearn preprocessing) and it transformed the column headers into integers. When I replaced the integers with the original column headers it worked fine. Thank you!!!

This should be fixed in branch v0.2dev as of 7d296fa33f6aea7259eecab3fc020101b2568f0c.  Closing.


Test keyboard navigation for accessibility

What problem does this feature solve?
When testing a component such as a dropdown, it's important to test if it works properly with the keyboard. For example, when opening a dropdown, by using the Tab key the user should not be able to leave the popover (trapped focus), up/down arrows should navigate through the options, pressing Esc should close it, etc.
I cannot seem to find any way to test for this. A similar issue was brought up already, but it was quickly dismissed. It looks like the docs mention the keyboard but it seems like that only applies to actual listeners. For example, if I have a button like
<button @click="trigger()">Button</button>

and I try to do
wrapper.find('button').trigger('keydown.enter')

that doesn't register (I think) because I never explicitly do
<button @keydown.enter="trigger()">Button</button>.

This means that I'm unable to test the Tab key properly, which is crucial for keyboard navigation. The same with .focus().
What does the proposed API look like?
Something like wrapper.keyboard.press('tab') and wrapper.focus()?

It sounds like this more towards the end to end test side of things... I sense a real browser (not the usual vue-test-utils and JSDOM) combo will not be adequate to fully test this.
In the case that this is something vue-test-utils can accomplish, I'd like an API like this:
const input = wrapper.find('button')
input.focus()
input.trigger('tab')

Or instead of the last line, require the user to create their own event with new Event.
I have a feelling this is more to do with SDOM thing rather than vue-test-utils. It doesn't seem like the above is testing anything unique to Vue.
I am not sure if this will work in JSDOM, but in a browser you can emulate the tab event like this:
var ev = document.createEvent('Events');
ev.initEvent('keydown', true, true);
ev.keyCode = 9;
ev.which = 9;
ev.charCode = 0;
ev.key = 'Tab'
ev.code = 'Tab'

const wrapperEl = wrapper.find('input')
wrapperEl.focus() // or wrapperEl.element.focus() ?
el.dispatchEvent(ev) // or maybe wrapperEl.element.dispatchEvent(ev) ?
expect(document.activeElement).toBe(wrapperEl.element)

I am not sure if this will work in JSDOM, but in a browser you can emulate the tab event like this:

I met the same problem these days. And I found a discussion: https://github.com/jsdom/jsdom/issues/2102 seems that JSDOM doesn't support TAB navigation. That might be really difficult to do this in Vue Test Utils expect JSDOM makes it happen.
Thanks.

As @Jinjiang says, this is because the feature is not implemented by JSDOM. We won't add a workaround to Vue Test Utils


Enable SSL in development

I'd appreciate feedback from application developers about how much harder this will make your lives.
You will need to add this SSL certificate to your Keychain on OS X (or similar system on other operating systems) in order to make using apps in a browser work properly.

This private key will be public, allowing people to serve content using it which would appear to us developers as trusted and secure. I think there might be possible issues there.

That's true, I meant to mention that - thanks!
I think that risk is very small. For people with this certificate installed you'd have to be using a service hosted on *.dev.gov.uk (as far as I know that doesn't exist) or set up DNS for that hostname pointing to an attacker's network and would then have to transmit sensitive information.

Overall, :+1:. I think it'll need some documentation changes in https://github.gds/gds/development/blob/master/README.md, or possibly have it added automatically by https://github.com/alphagov/govuk-puppet/blob/master/development/bootstrap.sh?

I've learnt some scary things about OS X's Keychain and apparently it is possible to install it automatically. I've pushed a change that does that but I don't know if it's something we want.

Also worth noting that this doesn't set the certificate to be trusted (I haven't been able to make that work) so maybe it's not worth doing.

Can we discuss this in the team meeting and either agree to finish it up or close the PR? The longer it's out for the more drift we'll see.

We discussed this in the team meeting and we're not going to deploy it at this time so we'll close the PR for now.


Test of cloud script with new dump folder

This PR was just for testing a modification of this repo


Docs: Fix reference type issue on DropZone reorder save example (#7191)

Description
Fixes an issue where, due to using a reference type with multiple lists, a "server load" example in the docs wouldn't work as expected.
Fixes: #7191
Before
https://github.com/MudBlazor/MudBlazor/assets/15004223/444650ad-79db-4417-9a80-187f55a2d0c8
After
https://github.com/MudBlazor/MudBlazor/assets/15004223/69876f2f-e9db-41fe-b27a-8c3744d88bc1
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.

@ScarletKuro As requested! I used LINQ to keep it short and simple, let me know if you prefer the foreach version I posted in the issue though!

@igotinfected Thanks


Leader election for Tag and Deployment controllers

Tag (controllers/tag.go) and Deployment (controllers/deployment.go) should have their logic wrapped in a leader election mechanism. All the other controllers receive data through or http or grpc and those should be kept free to run in multiple instances at the same time.

Implemented by https://github.com/ricardomaraschini/tagger/pull/52


Updates for the beta release.

release notes and version tag

I will merge these once the most recent master CI build passes and then do the beta release.

Just a doc-update, doing a self-push


CSUB-1382: Unblock runtime upgrade testing for mainnet

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Example of successfull Runtime Upgrade execution against Mainnet: https://github.com/gluwa/creditcoin3/actions/runs/11952245910


Frontend visual fixes

[x] better card and card image aspect ratio sizing
[x] if there's no image, don't show an image
[x] only show three cards - size margins/padding using viewport
[x] make the settings panel aesthetic match the rest (mostly color scheme)
[x] make the settings panel "set username" look like a button
[x] "I'm listening" animation/video looks very weird as it's cropped to a circle
[x] closing the explore iframe causes a seizure to occur with all the elements of the page.
[x] incoming card animation isn't smooth - comes in, slows, then speeds up again - should be smooth/continuous

[x] explicit card should have command label
[x] "listening" image should persist

[x] text sizing on high resolution screens

We can squash and merge this PR


Latest release contains Trojan:Script/Wacatac.B!ml according to windows security

Latest release contains Trojan:Script/Wacatac.B!ml according to windows security
Didn't have this issue with prior release

Hello, thanks for the feedback 🙂 This issue is known already. Pleaase see https://github.com/hdlx/AltAppSwitcher/issues/8
Unfortunately, I believe there is not much I can do. "...!ml" stands for machine learning detection and it's hard to know what makes it detected as Trojan.

Oh! Maybe this is why sometimes the app suddenly closes! And a lot of the time, it doesn't run at startup!
I was about to report it as a bug.

Hello, thanks for the feedback 🙂 This issue is already known (#8) Unfortunately, I believe there is not much I can do. "...!ml" stands for machine learning detection and it's hard to know what makes it detected as Trojan.

Thanks for responding, and sorry for not noticing this was a dupe


DBZ-1144 Test for geometry in public schema

https://issues.jboss.org/browse/DBZ-1144
It needs postres images rebuilt with https://github.com/debezium/postgres-decoderbufs/pull/17 to pass the tests.

Applied. The next build probably will fail due to the DB image not being updated yet, but it should be fine after that.


x/pkgsite: permission error cs.opensource.google

What is the URL of the page with the issue?
This page:
<EMAIL_ADDRESS>links to:
https://cs.opensource.google/go/go/+/go1.18.2:src/errors/wrap.go;l=14
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36

Screenshot

What did you do?
Click link to source code

What did you expect to see?
source code
What did you see instead?
permission error

this issue tracker isn't for cs.opensource.google

@mjacksonest if you haven't figured it out yet, or for anybody else who ends up here like me, I was able to get past this by disabling DuckDuckGo privacy essentials for this site.