Layer 4 Load Balancing Disabled With MetalLB Configured

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Run Rancher 2.2.0-Alpha6, install and configure MetalLB (BGP), attempt to deploy a pod with Layer 4 load balancing.
Result:
Cannot select Layer 4 load balancing from the drop down as it's set to disabled.
Other details that may be helpful:
This was working in version 2.1.6, prior to updating the rancher deployment.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher/rancher 2.2.0-Alpha6
Installation option (single install/HA): Single Install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): Metal; 96 Cores, 251GiB Ram across 4 nodes
Kubernetes version (use kubectl version): 1.12.4

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:46:00Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T06:59:37Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:27 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:47:25 2019
  OS/Arch:          linux/amd64
  Experimental:     false

What's the value of capabilities.loadBalancerCapabilities.enabled field for the cluster?
If it is not false, it will be fixed in https://github.com/loganhz/ui/commit/0136803f17b7be779fd7332c5158df162ab5b107

I think the question that DarkRider1768 asking is, Racher UI of  Rancher 2.2.x is set capabilities.loadBalancerCapabilities.enabled to "false" for on-premise Kubernetes. Howerver, if MetalLB is setup in on-premise K8S, then the Layer 4 Load Balancing should be able to set to "Enabled".
Now the question is "How can Rancher 2.2.x to allow to change capabilities.loadBalancerCapabilities.enabled=true?"

Echoing the above question - how would one edit the cluster to set capabilities.loadBalancerCapabilities.enabled=true ?

@loganhz I have the same question. Which @erhwenkuo phrased very well. When I first setup my cluster (bare metal on premises) I used "none" as the cluster provider, which sets capabilities.loadBalancerCapabilities.enabled=false however I have since installed MetalLB to provide load balancing and would like to allow users to select "Layer-4 Load Balancer" when deploying their workloads.

How do I change the value of capabilities.loadBalancerCapabilities.enabled now that I have a load balancer available to my cluster?

CC @mrajashree

I think the question that DarkRider1768 asking is, Racher UI of Rancher 2.2.x is set capabilities.loadBalancerCapabilities.enabled to "false" for on-premise Kubernetes. Howerver, if MetalLB is setup in on-premise K8S, then the Layer 4 Load Balancing should be able to set to "Enabled".
Now the question is "How can Rancher 2.2.x to allow to change capabilities.loadBalancerCapabilities.enabled=true?"

@loganhz @mrajashree do we have a way to override this setting? This destroys the ease-of-use of Rancher with an on-prem solution like MetalLB installed.

@Oats87 I guess there is no workaround for now. We need a fix for it.

The "nodePortRange" under is capabilities is also broken. It will never get updated when we change the default range in cluster settings.

Capabilities is just a reflection of cluster settings. Think of it as of a generic way of representing certain fields of GKE/RKE/EKS clusters. It doesn't work the other way around - you can't set the loadBalancerCapabilities to true to enable the LB.

capabilities.loadBalancerCapabilities.enabled will be set to true by Rancher only when we know that the provider is enabled. Like EKS, GKE, or RKE with CloudProvider != nil (which passes cloudProvider flag to k8s api server). We set it to false when we think LB is not enabled. And we leave it empty when we don't know. I think for "false" use case, we should be more deterministic - we should investigate if there is a way to determine if on prem LB provider runs in a cluster

@loganhz for nodePortRange, there must be a bug. If you are able to set it on a cluster settings via API, we should read it from there when populating the capabilities.

@alena for nodeport range issue. UI is looking at both range in capabilities and range in RKE API. And UI will choose the intersection.

@alena1108  Can we get this functionality patched out then? I realize this was just added but it is a breaking bug for what I imagine is a large number of deployments. Until there is logic in place to detect a load balancing solution like MetalLB, it doesn't make sense to prevent it's selection in the menu for people who have it deployed.

@DarkRider1768 my team has had success be creating the service via the Rancher UI as a ClusterIP, and then using kubectl to change its type to a LoadBalancer, at which point MealLB picks it up and the Rancher UI does the right thing. Its manual but it is an OK work around.
@alena1108 The current behavior described is fine, and makes good sense as a default. My team doesn't necessarily need Rancher to automatically understand if a LoadBalancer is installed, we just need a way to override the "when we think LB is not enabled" part of the logic. We need to be able to configure a "no really a LB is installed" option :-)
Thanks so much for talking the time to look at this.

@alena1108 I echo @rajha-korithrien 's comments. The default makes sense since most on-prem K8S is lack of LoadBalancer capability. However, providing a configure to allow on-prem K8S administrator to enable this setting and have Rancher UI ease to help deploy LoadBalancer workload on on-prem K8S is surely a very attractive feature that Rancher can offer.
The key value proposition of MetalLB is to address the imbalance by offering a Network LB implementation on bare metal, and I think the support from Rancher to enable this feature helps a lot.

I disagree. I understand that this "feature" is to cut back on the number of support tickets submitted by people who don't know to configure a load balancer before assigning the setting, however, beyond that it adds no functionality and fully breaks rancher for environments with a load balancer. As a workaround until the logic is in place, making it configurable is the absolute least that should be done but I'd argue that the "feature" is more of a bug in it's current state and could be done without.

So... any way to do this in 2.2.2 yet? It's been quite a pain to work around and kubectl edit cluster reverts immediately after a change. Perhaps some sort of Custom Cloud Provider can be set?

@DarkRider1768 @rajha-korithrien @erhwenkuo @junkiebev we will look at the ways to address it in our next planned maintenance release.
@junkiebev having cloud provider on an rke node would enable LB in capabilities. But that cloud provider should be something k8s understands.

@DarkRider1768 @rajha-korithrien @junkiebev @erhwenkuo Are you all using MetalLB or have you added some other bare metal LB provider?

@mrajashree why does the LB provider they are using matter, past intelligent recognition? There are other L4-load balancer providers that would require this functionality as well.

Because there's no such thing as "intelligent recognition"?  Any recognition is going to be looking for the specific resources they create, there's nothing .  The point was "what other balancers".

@vincent99 the question posed to the users was asking additionally about the installation method, which frankly shouldn't matter in this case and lead me to believe we were going to try and look for MetalLB. The ability to enable load balancer as a "capability" should most definitely be a generic, enable-able feature, rather than looking for certain resources for a specific load balancer/etc.

We're going to do both, but MetalLB is the only one most people have ever seen and she's just trying to make sure we can detect it the way actual people are installing it.  If you're worried about others then those need to be enumerated but that's a separate question.

@vincent99 thanks for the clarification. There are other L4 load balancer solutions that I've seen in use, but as long as the capability can be force-enabled this should be fine.

@Oats87 for your previous questions, word for word what @vincent99 said.
Can you also share the other bare metal lb you've seen being used?

@DarkRider1768 @rajha-korithrien @junkiebev @erhwenkuo Are you all using MetalLB or have you added some other bare metal LB provider? And if yes then have you installed it using the helm chart for it from stable repo? https://github.com/helm/charts/tree/master/stable/metallb

We are using MetalLB in BGP mode via the helm chart available through the web GUI. We looked as Istio and others but MetalLB was the only thing out there that looked like it ticked all the boxes we were looking for.
Let me know if there is anything I can do to help and I'll try to assist. Someone in our environment accidentally updated us to Rancher 2.2.2 and we've lost the ability to create pods with load balanced ports and/or create new clusters, so it's currently a priority of ours to get these fixed.

@mrajashree My team has used MetalLB via unsolicited ARP method, installed manually and via the helm chart. We have also written our own controller (from before we found MetalLB) that interacts with our permitter F5 but prefer the MetalLB solution (less support work on our end). Agree with @Oats87 as long as there is a "force enable" option everything should be fine :-) thanks for taking some time on this!

Okay thanks @DarkRider1768 and @rajha-korithrien we'll update this issue soon

@DarkRider1768 @rajha-korithrien @junkiebev @erhwenkuo Are you all using MetalLB or have you added some other bare metal LB provider? And if yes then have you installed it using the helm chart for it from stable repo? https://github.com/helm/charts/tree/master/stable/metallb
I'm using MetalLB from official the helm catalog repo, deployed via the UI.

@vincent99 - Y'all might want to mention/document that sometimes deploying a workload with the service type ClusterIP and then changing it to LoadBalancer via editing the YAML directly is a workaround. One potential breaking problem with this is that Rancher doesn't currently handle variable ordering correctly (there's a bug report in for this), so it can be dangerous.

After discussing the steps to go forward with @vincent99 offline, here are the steps we are going to take:

Do not set LB capability to false for RKE clusters. Set it to unknown (nil) if the cloud provider is not enabled. UI would treat unknown as true, and Load Balancer tab will be enabled. There can be various ways of enabling LB service on a cluster, and the bottom line is - ideally it should always be enabled as Load Balancer should be a core capability of the cluster, which brings the point 2)
Add native Load Balancer support to Rancher provisioned clusters (RKE) - the option that can always be turned of in leu of deploying a custom controller, out of the tree cloud provider, or enabling the cloud provider on the cluster directly. https://github.com/rancher/rancher/issues/20068

After discussing the steps to go forward with @vincent99 offline, here are the steps we are going to take:
Do not set LB capability to false for RKE clusters. Set it to unknown (nil) if the cloud provider is not enabled. UI would treat unknown as true, and Load Balancer tab will be enabled. There can be various ways of enabling LB service on a cluster, and the bottom line is - ideally it should always be enabled as Load Balancer should be a core capability of the cluster, which brings the point 2)
Add native Load Balancer support to Rancher provisioned clusters (RKE) - the option that can always be turned of in leu of deploying a custom controller, out of the tree cloud provider, or enabling the cloud provider on the cluster directly. #20068

Will this be the case with Custom Clusters as well?

@junkiebev yes

will be available to test in rc8. This issue is to track 1) only. 2) will be tracked in https://github.com/rancher/rancher/issues/20068

Tested with master build from June 11.

Created DO RKE cluster
Deploy a workload.
Layer4 - LoadBalancer option is enabled in Port Mapping section when deploying workloads.

In Cluster API , there is no enabled flag set for loadBalancerCapabilities.
loadBalancerCapabilities": {
"healthCheckSupported": false,
"type": "/v3/schemas/loadBalancerCapabilities"
},
"nodePoolScalingSupported": true,
"nodePortRange": "30000-32767",
"type": "/v3/schemas/capabilities"
},

Also ,verified the same for a custom cluster.


ProjectBucket doesn’t propagate provenance

We lose provenance after a ProjectBucket node. There is a workaround for now which should handle the queries supported by the current version of SQL², but isn’t general enough for full MRA.

This is no longer valid given qsu.


Disable multi-tenancy section title is misleading

The section title "Disable multi-tenancy" is misleading. There is no setting to enable/disable multi-tenancy, just whether there is a single directory, or multiple directories (multi-tenancy). Removing a tenant directory does not disable multi-tenancy, if there are still 2 or more directories configured.
This leads to customer confusion, when they want steps to remove one or more guest directories, but leave other multi-tenant directories in place.
Customer verbatim from SR<PHONE_NUMBER>02614 - "...he said I could remove both of those unhealthy tenants.  However, your link you supplied says disable multi-tenancy which is not want I want to do. I just want to remove those 2 that are unhealthy."
Suggestion: Rename the "Disable multi-tenancy" section title to something like "Remove a guest directory tenant"

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

ID: cea6b2d3-c2a7-a7f1-2473-34c76e32c835
Version Independent ID: b3cd3369-fdab-225e-2cc9-d90f9b5bffff
Content: Configure multi-tenancy in Azure Stack Hub - Azure Stack Hub
Content Source: azure-stack/operator/azure-stack-enable-multitenancy.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @BryanLa
Microsoft Alias: bryanla

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! We are currently investigating and will update you shortly.

@SaiKishor-MSFT - please assign this one to me. This article needs multiple revisions, including the ones called out by @alexsmithMSFT.

@SaiKishor-MSFT - please assign this one to me. This article needs multiple revisions, including the ones called out by @alexsmithMSFT.

@SaiKishor-MSFT - please assign this one to me. This article needs multiple revisions, including the ones called out by @alexsmithMSFT.

Assigned. Thanks!

@SaiKishor-MSFT - please assign this one to me. This article needs multiple revisions, including the ones called out by @alexsmithMSFT.

Assigned. Thanks!

@SaiKishor-MSFT thanks for taking this one. One other issue I noticed, is with the comment in the second script under "Disable multi-tenancy", which mentions creation of a registration resource. I think it was copied verbatim from earlier sample to "Configure Azure Stack Hub directory".
## Replace the value below with the name of the resource group in which the directory tenant registration resource should be created (resource group must already exist).

@SaiKishor-MSFT thanks for taking this one. One other issue I noticed, is with the comment in the second script under "Disable multi-tenancy", which mentions creation of a registration resource. I think it was copied verbatim from earlier sample to "Configure Azure Stack Hub directory".
## Replace the value below with the name of the resource group in which the directory tenant registration resource should be created (resource group must already exist).

@alexsmithMSFT - done. I'm making several other revisions to make this more intuitive as well. I'll send you a link to the preview when it's ready..

@alexsmithMSFT - done. I'm making several other revisions to make this more intuitive as well. I'll send you a link to the preview when it's ready..

Substantive changes made to Configure multi-tenancy in Azure Stack Hub to address this issue.
#please-close


Issue 3 adjustments to home page

Closes #3

fixes headshot sizing
removes min-height from body text

this fixes the big gap above buttons, but also means the project descriptions should be about equal length in number of words if you want the "Read More" buttons to line up

I don't know what the "wonky project icon movement" part of the issue is, so consider it not fixed.

@tlcharnetzki accept this pls

Thanks, looks good!


Add editorCursor.background

We are adding foreground and background settings for the terminal cursor -
https://github.com/Microsoft/vscode/issues/30294
Currently when using a block cursor, the editor sets the color of the overlapped character to the opposite of the cursor foreground color. But you can end up with strange color combinations, and it's not necessarily high contrast. For example with "editorCursor.foreground": "#808080", the character color is also #808080.

@roblourens I like this idea. The only catch is they way we set CSS make it confusing
editorCursor.foreground --> .cursor { background: }
editorCursor.background --> .cursor { color: }

Yeah, @Tyriar and I were just talking about that. I think it makes sense that the cursor "foreground" is the color of the actual cursor block, and the 'background' is the color of the overlapped character. The implementation just looks odd.

Yeah it's confusing, styling the block cursor are the opposite of what you would intuitively think, but it feels correct for the other cursor styles.


Is there any easy way/guide on how to create a vertical slider?

I'm having a hard time creating a vertical slider and I was wondering if I could get any help from the developers or any other that have stumbled upon this as well.
I made a small codepen sampling my tries on this. Basically, it's hard to position the slider correctly after rotating it...

Please use StackOverflow for support and integration assistance. This tracker is only for problems with the code provided by Material Design Lite.
Thank you.


ModuleNotFoundError: No module named 'torch'

🐛 Describe the bug
this is jetson orin with jetpack 5.1
I want to run yolov5 with pytorch on jetson orin, so i installed pytorch first with PyTorch v2.0.0
https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-ml
https://docs.nvidia.com/deeplearning/frameworks/install-pytorch-jetson-platform/index.html
only got this error
ERROR: Invalid requirement: 'LD_LIBRARY_PATH=/usr/lib/llvm-8/lib:$LD_LIBRARY_PATH'
Hint: It looks like a path. File 'LD_LIBRARY_PATH=/usr/lib/llvm-8/lib:$LD_LIBRARY_PATH' does not exist.
since my $LD_LIBRARY_PATH is empty
I export LD_LIBRARY_PATH=/usr/lib/llvm-8/lib
I guess I have already installed torch properly
`python3
Python 3.8.10 (default, Mar 13 2023, 10:26:41)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import torch
pring>>> print(torch.file)
/home/li/.virtualenvs/pytorchyolo/lib/python3.8/site-packages/torch/init.py`

So I run setup torchvision
sudo apt install -y libjpeg-dev zlib1g-dev git clone --branch v0.15.1 https://github.com/pytorch/vision torchvision cd torchvision sudo python3 setup.py install
but i got
Traceback (most recent call last):
File "setup.py", line 9, in
import torch
ModuleNotFoundError: No module named 'torch'
why? Is there any resolution?
Versions
git clone --branch v0.15.1 https://github.com/pytorch/vision torchvision

You ran python3 to check if torch is available, but used sudo python3 to run the installer. I guess, your Python is only installed for your user and not the superuser. You can try with sudo python3 -c 'import torch'. Not sure why you do it in the first place, but I would drop the sudo from the installation.
In any case, this is an environment issue and thus not actionable for us.

You ran python3 to check if torch is available, but used sudo python3 to run the installer. I guess, your Python is only installed for your user and not the superuser. You can try with sudo python3 -c 'import torch'. Not sure why you do it in the first place, but I would drop the sudo from the installation.
In any case, this is an environment issue and thus not actionable for us.

you are right, it is about sudo and not sudo .
I followed pytorch tutorial to install pytorch and torchvision. I don't know why they pip install torch without sudo, and install torchvision with sudo.
Actually, on jetson orin to install pytorch or torch vision, pip goes very well , don't follow the other words about run setup.py...


Exception App id not found

🐛 Bug Report
Exception App id not found ,
the same codes working fine with fbsdk but when i migrate to fbsdk next i got this error on ios
To Reproduce
add react native fbsdk next to your project and try to use it
Expected Behavior
it should prompt the login page
Environment
Xcode: 12.5
React-Native : 64.2
System:
OS: macOS 11.4
CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Memory: 67.70 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.3.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.15.1 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4

Do not forget this step:
[FBSDKApplicationDelegate initializeSDK:launchOptions]; // Facebook SDK Initialization
It is happening to the ones who upgraded from "react-native-fbsdk" due to facebook's decision to discontinue it.

Duplicate #56 please search issues lists prior to posting, this was active literally yesterday


Adding MPLS Static test case

Test follows the following flow
configures DUT Interfaces
ConfiguresOTG interfaces
Configures Static LSP
Configures Traffic Flow
Sends Traffic
Validate traffic by verifying packet capture on ATE port2 has the expected label

Pull Request Functional Test Report for #2587 / 110224aa599e3e2a580234f7b064cee5a949a8f5
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TE-9.1: MPLS based forwarding Static LSP

Cisco 8000E

TE-9.1: MPLS based forwarding Static LSP

Cisco XRd

TE-9.1: MPLS based forwarding Static LSP

Juniper cPTX

TE-9.1: MPLS based forwarding Static LSP

Juniper ncPTX

TE-9.1: MPLS based forwarding Static LSP

Nokia SR Linux

TE-9.1: MPLS based forwarding Static LSP

Openconfig Lemming

TE-9.1: MPLS based forwarding Static LSP

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TE-9.1: MPLS based forwarding Static LSP

Cisco 8808

TE-9.1: MPLS based forwarding Static LSP

Juniper PTX10008

TE-9.1: MPLS based forwarding Static LSP

Nokia 7250 IXR-10e

TE-9.1: MPLS based forwarding Static LSP

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 54.484%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1847

Relevant Lines:
3390

💛  - Coveralls

@mastarkey Please can you resolve conflicts - proto/metadata_go_proto/metadata.pb.go

Hi @LimeHat / @AmrNJ  / @nraghavendran
Can we kindly merge this if there are no open items. I resolved the readme issue so there should be no outstanding items.

This resolved #3165


Non Virtual usage?

I would like to use this plugin for controlling different switches and Devices with the Shell...all Scripts i used previusly with the cmdswitch2 Plugin...this plugin is interesting because i can choose from a huge number of differend characterristics and Device Types...but how i can actually Control a real Device with this plugin? Like with the cmd_on and cmd_off Argument...?

Hi,
I'm glad you found my homebridge-cmd4 plugin.  You most certainly can control a real device and with all the possible options too.
Maybe I should create a section in the README about porting from the original home bridge.  I just did not want to trample on the other fellas work, but it is something I will think about as many have found homebridge-cmd4 more useful.
Everything. Is possible, it all depends on your scripting ability. It all starts with the homebridge config.json file. The one I provide has all the possible options,  so I will give you an example of controlling a real light.

Edit your .homebridge/.config.json file
Copy and paste all the lines between the braces {} for My_Dimmable_Light.  Don't forget the comma after the bracket to signify that there are more entries afterwards.
3)In the new copied section, change My_Dimmable_Light to Your_Dimmable_Light. Adding spaces really complicates scripting, so I would avoid doing that.
4)Change the state_cmd from "node .homebridge/Cmd4Scripts/State.js" to "node .homebridge/Cmd4Scripts/YourState.js"
There are a couple of points I would like make about the this line.

The command executied by homebridge-cmd4 would be exactly what you would write here, plus options that will be discussed later.
This command is executed from your $HOME directory. You can try it yourself for debugging purposes.
No environmental variables or any shortcuts in your .bashrc file or any .rc file are used. This is a big no no in scripting. When debugging, keep this in mind as it may fool you.
The command that is executed does not have to be a nodejs script. It could have been an executable or bash script, so long as it accepts and responds to the format of homebridge-cmd4, which is the HAP spec.
An example instead would be "my_light.sh" or "/usr/local/bin/perl .homebridge/my_scripts/my_light.pl"

Create the script  .homebridge/Cmd4Scripts/YourState.js.   As noted in the previous item, this could be a bash script, perl or whatever.
UnLike the original cmd tool, homebridge-cmd4 responds to options. If you read the top of the State.js file, it does give some information.
Your new script must accept and respond accordingly.  They are not random and are spelled out in the HAP spec, but I will continue with an example.
The parameters are:
Get
Set

The "Get" or "Set" would be $1 in your script.
The characteristic would be $2
The value would be $3 if the first option was "Set"
so unlike the original cmd tool, the script sends these options.
What you want to do in your script is up to you.  You could have your script execute another command that actually does something like turn on or dim a real light.
6)Lastly, the YourState.js file has to respond with an exit code of 0 for PASS or something else for fail.
Study the existing State.js file as it has all the pieces of the puzzle you need.  I'll leave this issue open until I update the README accordingly.
Take care,
John Talbot

I updated the README with an example of migrating from Homebridge-cmdswitch2 which gives a real example


Container fails to start

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy to azure using the "Deploy to Azure" button

Any log messages given by the failure

2023-07-14T10:23:25.987Z ERROR - Container ctfd-app-jiibwegyv3xy6_1_240b2df1 for site ctfd-app-jiibwegyv3xy6 did not start within expected time limit. Elapsed time =<PHONE_NUMBER> sec
2023-07-14T10:23:26.031Z ERROR - Container ctfd-app-jiibwegyv3xy6_1_240b2df1 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.
2023-07-14T10:23:26.076Z INFO  - Stopping site ctfd-app-jiibwegyv3xy6 because it failed during startup.

Expected/desired behavior

504.0 GatewayTimeout on the website that I am trying to open

OS and Version?

Windows 11

Versions

latest

Mention any other details that might be useful

The deployment seems to be successful, without any errors
It seems to be the same error as the one previously raised in a closed thread with the same name, however redeploying did not seem to solve the issue, as it did in the other person's case :(

Thanks! We'll be in touch soon.
logs.zip

Thanks for reporting this @aniajj9 , i'll fix the issue and hope to get a patch out soon.

fixed by #16


Something went wrong...

my log id: 949cdd22a8ed52228909391c
Not really sure what else to report except that the "People" tab is completely unusable for me now. I tried quitting the app and it doesn't have any effect.

I had the same issue today (log id 4b0549820b003c46b7184f1c) on MacOS Sierra.
There was nothing unusual in the log (at /Library/Logs/keybase.system.log). As noted, the error was limited to the people tab, but for me more specifically to 'search' on the people tab.
The issue recurred for me for several minutes, temporarily fixed by restarting the app, but since touching the log to have a look, I haven't been able to reproduce the error.

I rebooted my machine a few times, and it eventually went away but I have no idea what the resolution was or what caused it.


Update gopkg.in/yaml.v3

Test name
Status

scaling
passed

scheduled-backup
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

storage
passed

cross-site
passed

upgrade-haproxy
passed

haproxy
passed

big-data
passed

security-context
passed

demand-backup
passed

self-healing
passed

init-deploy
passed

pitr
passed

limits
passed

self-healing-chaos
passed

demand-backup-encrypted-with-tls
passed

self-healing-advanced
passed

monitoring-2-0
passed

self-healing-advanced-chaos
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

operator-self-healing-chaos
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1167/commits/ccafdf8dfcea5c60d52fd970a72a60a93d39db34
image: perconalab/percona-xtradb-cluster-operator:PR-1167-ccafdf8d

Test name
Status

scaling
failed

upgrade-haproxy
failed

haproxy
failed

cross-site
failed

recreate
failed

scheduled-backup
failed

storage
failed

big-data
failed

scaling-proxysql
failed

init-deploy
failed

restore-to-encrypted-cluster
failed

self-healing
passed

self-healing-chaos
failed

upgrade-proxysql
failed

limits
failed

demand-backup
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

security-context
failed

smart-update
failed

monitoring-2-0
failed

pitr
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

upgrade-consistency
failed

affinity
failed

demand-backup-encrypted-with-tls
failed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

users
failed

tls-issue-self
failed

tls-issue-cert-manager
failed

tls-issue-cert-manager-ref
failed

validation-hook
failed

proxy-protocol
failed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1167/commits/37defcb7e58df5233553f2decc8cac8e6410c882
image: perconalab/percona-xtradb-cluster-operator:PR-1167-37defcb7

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1167/commits/37defcb7e58df5233553f2decc8cac8e6410c882
image: perconalab/percona-xtradb-cluster-operator:PR-1167-37defcb7

Test name
Status

storage
passed

cross-site
passed

scaling
passed

upgrade-haproxy
passed

haproxy
passed

recreate
passed

scheduled-backup
failed

big-data
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

upgrade-proxysql
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

smart-update
passed

affinity
passed

one-pod
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

We run 33 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1167/commits/37defcb7e58df5233553f2decc8cac8e6410c882
image: perconalab/percona-xtradb-cluster-operator:PR-1167-37defcb7


Updating theme does not download new volt.toml

Lapce Version
0.2.4
System information
Linux
Describe the bug
Updating a theme seems to not download the new volt.toml file. This causes the 'Update' notification to remain, as the version on the plugin-repository is still ''newer'' than the local version.  Uninstall and reinstalling (thus forcing volt.toml to be redownloaded) fixed the issue.
(Does this affect all plugins, or just themes?)

@MinusGix is that still occurring?

Nope.


  This aims to provide the capacity to cleanly handle temporary filesystem resources, and also aims to use more carefully those resources which we do generate.
Broad fixes to testing infrastructure

Add custom rmtree function to handle windows rms
Only warn on failure to remove a tree
This should mitigate a large portion of our windows test failures
After sufficiently substantial time investment I am currently of the opinion that there is no real elegant way to handle this (I have tried programmatically finding all processes with open file handles, terminating them with a 500ms retry and a 15s timeout)
Close and handle tempfiles in resolvers
Only create tempfiles for non-editable deps
set umask and PIP_SRC for test context
Warn instead of throwing exceptions
Backport TemporaryDirectory for python2/3 compatibility and reliance on custom rmtree error handling
Vendor backport of weakref.finalize for TemporaryDirectory.cleanup()
Add PyTest fixtures to wrap and cleanup PIP_SRC directory at the module level to avoid permissions errors on appveyor
Add resource warnings for PY2 compat Lock instead of installing complex resolver test
Add a special condition for allowing access errors

rebase required!

waiting on #1372 (has a hidden test dependency) + needs a minor refactor before it can be merged


Accessibility Panel, Feature Loading, OSM / AC ID Discriminators

Accessibility Panel
First and foremost is the integration of the existing components for the accessibility panel, allowing to dynamically create a UI which properties are being shown to any place:

Feature Loading
Another point of contingency is loading features correctly.
The new process involves:

compiling feature ids into a list of normalized RDF compliant formats, ie: osm:amenities/node/10582857 or ac:PlaceInfo/39868291
passing the list into useExpandedFeatures
useExpandedFeatures will then;

compile URLs for AC PlaceInfos and OSM IDs against the correct endpoint
utilize useSWRInfinite to load all passed feature id entries
check the AC features if they have OSM ids attached, and if so, load the OSM data
check the OSM features if they are known as AC features, and load their data

finally, collectExpandedFeatures will massage the data into a more usable format

Type Discrimination
In order to facilitate and deprecate ID nomenclatures, a bunch of helpers have been written to brand OSM / AC ID strings and discriminate of them, to prevent passing strings that do not conform expected formats. This paves the way for keeping the way of passing strings as arguments, but with additional type guarding that eases development on both, user and implementation developer side.

currently there's a regression that [host]/ac:PlaceInfo/iMnCHew5emCSbAqKn cannot be resolved


added some unfunny joke

added some joke and a cool text art :)

This is so funny and i see nothing wrong with it good job


add repr_html for qcodes instruments

Changes proposed in this pull request:

Add _repr_html_ for all qcodes instruments. This gives a nice representation in tools like jupyter notebook.

New representation:

Old representation:

@jenshnielsen

Thanks @peendebak  Looks very useful. We will have a look


support of async views

Similarly to Flask, the framework should support async function for a view - see https://flask.palletsprojects.com/en/2.1.x/async-await/
Under the hood, Flask executes asyncio.run() and returns the resulting value to the client.
When trying to define the view function with async, one gets TypeError: The view function did not return a valid response. The return type must be a string, dict, tuple, Response instance, or WSGI callable, but it was a coroutine.
Workaround is simply to create a "regular" sync function that executes (asyncio.run()) a separate async function but it could be simpler and match Flask functionality.
Our use case: use Google Cloud Functions from BigQuery Remote Function to call external APIs concurrently (using aiohttp).

Have a look at unsync library. We use it all the time now.


UserInteractionOptions

Issue / Steps to reproduce the problem
We are receiving NullReference exceptions because we do not fill in the UserInteractionOptions. Earlier in the v2.2.0 build, this was automatically filled with default values when the IdentityServerOptions is initialized. Now in the preview of v2.3.0, it looks like the default path is no longer filled in automatically. It remains furthermore null causing NullReference exceptions on other places.
Related: https://github.com/IdentityServer/IdentityServer4/issues/2532

Do you have a repro for this or a call stack? I can't seem to cause this NRE in our host with our samples.

@silamon any update? if you can't help us repo this report, then there's nothing we can do to fix it.

Sorry for the late response. I reverted back to 2.2.0 after submitting the bug report. The exception no longer happens when I return to 2.3.0 preview now so I have not been able to reproduce this anymore. I can still remember that the NRE was caused on login. In LoginPageResult _options.UserInteraction.LoginUrl was null. Then a bit later it tries to invoke AddQueryString on null. Related code:   https://github.com/IdentityServer/IdentityServer4/blob/dev/src/Endpoints/Results/LoginPageResult.cs#L61-L69.

I've been able to reproduce it now. That day I tried to set different authentication schemes.
This is the original code:
 .AddAuthentication( IdentityServerAuthenticationDefaults.AuthenticationScheme )
Then I played around and used:
.AddAuthentication(options => {
    options.DefaultScheme = IdentityServerAuthenticationDefaults.AuthenticationScheme;
    options.DefaultAuthenticateScheme = IdentityServerAuthenticationDefaults.AuthenticationScheme;
    /* ... */
})

Ok, that helps. I'll look into it.

Can you show me your entire Startup that's not working?

IdentityServerAuthenticationDefaults.AuthenticationScheme is "Bearer", mind you. So that's fundamentally wrong for the default scheme. That's not something that should have been working previously.

And so to complete my thought... the default scheme needs to be your cookie scheme, or you can set the new CookieAuthenticationScheme on the IdentityServer AuthenticationOptions like this:
 services.AddIdentityServer(options =>
{
options.Authentication.CookieAuthenticationScheme = "YourCookieScheme";
})

Thanks for helping me out, but I've already found a solution now that both API & Auth are combined.
For this issue, it may be great if you could add an (better) exception which is given if the authentication scheme is not correctly set. It didn't really work in v2.2 but gave an exception after correct login: InvalidOperationException: The authentication handler registered for scheme 'Bearer' is 'IdentityServerAuthenticationHandler' which cannot be used for SignInAsync. The registered sign-in schemes are: idsrv, idsrv.external.. In v2.3, you get the NRE for the same code. In v2.2, it was filled in automatically and therefore giving no NRE.
If you don't feel like an exception is required, you may close the issue.

This exception is thrown by the Microsoft plumbing, not us. I think what might be nice is if we check at startup if we can determine the default authentication scheme and if it is cookies and if not then we issue a warning/error in the logs.

I added additional logging at startup to help with this issue. @leastprivilege please have a look.

all done and reviewed


State Feedback from embedded systems

Acquiring the observable output state from an embedded system might be useful for verifying the accuracy of models designed and simulated in Drake. With state feedback, it is possible to Optimize model accuracy with machine learning.
Proposed changes:

Create a new abstract SheldrakeObserver class that exposes an abstract method getObservableState
Implement getObservableState on Sheldrake_Serial.

Alternatively, what would the implications be of just including getObservableState as a part of the Sheldrake library?
The equivalent issue in the Sheldrake Interpreter:
https://github.com/m516/sheldrake-arduino-template/issues/5

Done. Example coming soon


Add ansible-playbook argument setting option

Adds an extension setting under ansible.playbook.arguments to add arguments to ansible-playbook runs.
Demo:
ansible-playbook run,  without arguments set:

How to set the argument in settings, and then running ansible-playbook:

Additional changes:

Made a minor bugfix in src/features/runner.ts. The SettingsManager class now replaces ExtensionSettings.
Refactored the getFilePath() helper function (now getFixturePath() )to be more generic , and adjusted function calls as needed.
Added tests for ansible-playbook and ansible-navigator commands.

Closes #1042.

@priyamsahoo fixed! Added the setting to the list in README.md.


improve local UI testing and ability for pluggable UI

This pull requests allows the user interface to be loaded from disk. You can provide the path to your user interface
DRONE_WWW=/path/to/website

This directly should container the application entrypoint as an index.html file. The index.html file must include a <!-- inject:js --> placeholder.
<!doctype html>
<html lang="en">
	<head>
		<!-- inject:js -->
		<!-- endinject -->

The <!-- inject:js --> placeholder is replaced with the following javascript code that provides the web application with the authenticated user and csrf token. The web application code should look for these values.
<!doctype html>
<html lang="en">
	<head>
		<!-- inject:js -->
		<script>
			window.ENV = {};
			window.ENV.server = window.location.protocol+"//"+window.location.host;
			window.ENV.csrf = "..."
			window.USER = {...}
		</script>
		<!-- endinject -->

Drone will load files from disk matching the below paths. If you are building a custom user interface, you should place all static files in the /static directory and use index.html as the main entrypoint.
/index.html
/favicon-32x32.png
/favicon-16x16.png
/src/*
/bower_components/*
/static/*

This should simplify local development and should allow pluggable user interfaces.
cc @alansouzati

cool stuff, can't wait to try this with Grommet. I'm working on Grommet 2.0 as of now so I will probably get back to it and change grommet-drone-ui to use this new stuff and also migrate the existing UI to Grommet 2.0 👍

@alansouzati cool, I look forward to it 😄


Add EventLockUser after user get locked

This allows people to do something like track user got locked activity.

Hi @raven-chen, sorry I haven't got to this for so long. Did you close this pull request because I hadn't attended to it or because you no longer needed it?


Add edge_data_volume_size to Terraform samples

Users should be aware of this variable which is missing in OpenStack
Terraform sample files.

lgtm


Example cfg for NERSC

Example cfg for NERSC. This is the NERSC example for #233.

Replaced by #264 / #282.


Build 1.2 with sources from 2015-04-27 causes segfault

I'm constantly building versions for opensuse and am getting this error after opening the password to enter a connection to a Windows 7 system:
2015-04-27T09:02:25.333674+02:00 c-web1 remmina.desktop[14606]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
2015-04-27T09:02:41.419764+02:00 c-web1 kernel: [ 3426.258494] remmina[14617]: segfault at c ip 00007f3d1b1f4f66 sp 00007f3d115de0a0 error 4 in libfreerdp.so.1.2.2[7f3d1b190000+14e000]
Last version (2015-04-16) worked normally. As I'm not working with cmake normally, you can possibly give me a hint how to turn on debug symbols? I could give better log-details.

@weberhofer can you retry with latest master if the problem still exists?

Thank you! The problem has been resolved.


Remove lifetimes

In this large PR, I removed the requirement to use explicit lifetimes. This sorts the issue reported #127.
Please let me know if this PR removed any recent modifications in the code.

Hello @ppamorim, thanks for your PR, and thanks @Mubelotix for helping @ppamorim on this issue (#127) 🙂
Are these changes breaking for the users?

@curquiza There are a bunch of breaking changes. I will list them below:
The host and api_key are now stored inside Client.config. The constructor of Client will sort this automatically and no breaking change is applied to the initializer.
The function with_attributes_to_crop has been changed to accept the struct AttributeToCrop:
query.with_attributes_to_crop(
  Selectors::Some(
    vec!(
      AttributeToCrop::new("value", Some(50)),
      AttributeToCrop::new("kind", None)
    )
  )
);

This was required to allow the past type alias to accept either String and &str.
I need to update the examples from the code-samples file.

@ppamorim How can I help? I can finish myself the PR if you want to. I can also make reviews but I it will be slower.
@curquiza They should not be breaking since we can use generics

@Mubelotix I didn't remove, not every function expects the type AsRef<str> where it supports either String and &str.
I forgot to tell that most of the function that were using &[] or &[&[]] are now expecting vec!() or vec!(vec!()).

@ppamorim How can I help? I can finish myself the PR if you want to. I can also make reviews but I it will be slower.
@curquiza They should not be breaking since we can use generics

This was required to allow the past type alias to accept either String and &str.

But why did you remove these references? These weren't causing any problem right?

I had to replace the type definition of AttributeToCrop because there is no way to make it either accept String and &str in a type alias. The only way to make it accepts is through a struct with the new constructor.
I am curious why the tests are hanging in my machine. I need to check this out.

@Mubelotix The CI is failing because I had to add #![feature(min_const_generics)] in the lib.rs. Locally I am getting errors. Any idea of what can be done?

I didn't remove, now every function expects the type AsRef where it supports either String and &str.

That's a great thing but why didn't you choose Into instead? In the case of a String, that would avoid a useless clone.

I forgot to tell that most of the function that were using &[] or &[&[]] are now expecting vec!() or vec!(vec!()).

This is an issue. It worked like this before and it was quite bad especially for examples. We should either keep the references, either write a new trait to support multiple types. I prefer the last solution as it is the most flexible and powerful.

@Mubelotix The CI is failing because I had to add #![feature(min_const_generics)] in the lib.rs. Locally I am getting errors. Any idea of what can be done?

It seems that you are still using an old Rust version. Try running rustup update.

I didn't remove, now every function expects the type AsRef where it supports either String and &str.

That's a great thing but why didn't you choose Into<String> instead? In the case of a String, that would avoid a useless clone.

I tried this, this doesn't work.

I forgot to tell that most of the function that were using &[] or &[&[]] are now expecting vec!() or vec!(vec!()).

This is an issue. It worked like this before and it was quite bad especially for examples. We should either keep the references, either write a new trait to support multiple types. I prefer the last solution as it is the most flexible and powerful.

I don't know how we could do this. :)

@Mubelotix The CI is failing because I had to add #![feature(min_const_generics)] in the lib.rs. Locally I am getting errors. Any idea of what can be done?

It seems that you are still using an old Rust version. Try running rustup update.

Thank you, I remember running this command last week, strange...

I tried this, this doesn't work.
I don't know how we could do this. :)

I can do this but how am I supposed to do this? By sending pull requests to you fork?

@curquiza What's the best option do you think?

I can do this but how am I supposed to do this? By sending pull requests to your fork?

I usually do this.

I tried this, this doesn't work.
I don't know how we could do this. :)

I can do this but how am I supposed to do this? By sending pull requests to your fork?

So yes :)

Only if you have time for this @Mubelotix of course, and if you think this is useful! No rush!
@ppamorim, can you put back the new line at the end of each file, please?

Only if you have time for this @Mubelotix of course, and if you think this is useful! No rush!
@ppamorim, can you put back the new line at the end of each file, please?

I will do but I don't remember removing then, maybe it was my VSC?

I don't know what you use to code, this problem comes from your settings in your own text editor.
Also, we have a .editorconfig file in this repo to prevent contributors to do this kind of mistake. If you use VSCode, please install the editorconfig plugin: it will keep the newlines at each save.

@curquiza Sorted! This happened because I copied and pasted the code from other files.

Hi @Mubelotix , is there any work done here?

Hi @Mubelotix , is there any work done here?

Not yet. I have things to do this week but it will be done right after.

@ppamorim I have made a PR which should solve most change requests I would have made in my reviews.

@Mubelotix I can see that the explicit lifetimes returned to the traits Query, Progress. I do understand the requirement but it's a bit concerning. I did merge anyway.

@Mubelotix I can see that the explicit lifetimes returned to the traits Query, Progress. I do understand the requirement but it's a bit concerning. I did merge anyway.

If handling queries is hard, here is what to do:
pub struct OwnedQuery {
    pub query: String,
    pub attributes_to_highlight: Vec<String>,
    // and any other fields you need
}

impl OwnedQuery {
    pub as_query<'a>(&'a self, index: &Index) -> Query<'a> {
        Query::new(&index)
            .with_query(&self.query)
            .with_attributes_to_highlight(self.attributes_to_highlight.map(|a| a.as_str()).collect());
            // and any other fields you need
    }
}
I hope it will help.
Note that lifetimes on `Progress` have been removed.

@Mubelotix Is that right or am I missing something? https://github.com/ppamorim/meilisearch-rust/blob/master/src/progress.rs#L24

@Mubelotix Is that right or am I missing something? https://github.com/ppamorim/meilisearch-rust/blob/master/src/progress.rs#L24

This file is on the master branch

I don't see any change. I will be waiting for the PR.

@ppamorim can't you apply yourself the change @Mubelotix suggested here: https://github.com/meilisearch/meilisearch-rust/pull/132#issuecomment-846863526? It's not always convenient to do a PR on a PR, we would rather let the author work on it if possible 🙂
Also, there are git conflicts to fix 🙂

I don't see any change. I will be waiting for the PR.

You merged that PR two days ago.
Here is the current src/progress.rs file. You can see that Progress does not have lifetime anymore.

@curquiza

Also, there are git conflicts to fix 🙂

I am going to fix them but first I will review this PR.

Thanks a lot @Mubelotix!

@Mubelotix Sorry my bad and thank you for your work!

bors try

bors try

Thank you very much @ppamorim!!! 😊 And also @Mubelotix for your review!
bors merge

There is merge conflicts with #142 that has just been merged! 😕 Sorry @ppamorim, can you rebase please?

@Mubelotix Any idea why it failed?

Whoops. I added a very small feature that is now required to build the example web app. We have to add to modify the CI. Adding --features=sync here will fix it.

@curquiza @Mubelotix Should be sorted by now.

@Mubelotix Now it failed in the integration-tests, there is something wrong with a validation.

It seems that a test is failing sometimes but as this is the first time it must be very rare. This is not related to this PR. Let's run the CI again. It should work this time. We will fix that in another PR.


Add checks to Flyway changes in GHA PR Checks

Recently, we had two PRs that changed the structure of Flyway components on kogito-apps and kogito-runtimes:

https://github.com/apache/incubator-kie-kogito-runtimes/pull/3672
https://github.com/apache/incubator-kie-kogito-apps/pull/2102

These changes had a great impact on installations already in place. Users had to make manual changes to their databases to accommodate these structural changes, such as checksum changes and constraint naming.
We must avoid this type of change in the future to avoid impacting users during a version upgrade. Or, if so, comprehensive migration documentation instructing users on how to do it.
Having said that, we must implement a PR check to GHA to verify for changes in Flyway scripts already committed to avoid messing up with checksums. Also, when changing the component placement or nomenclature, attach a script to be applied to the Flyway metadata database.

@pefernan, can you assess it since you did the modifications to Flyway resulting in this issue?


How can I configure TFS that I can build iOS libraries

Agent version and platform
Version of your agent? 2.102.0

OS of the machine running the agent? OSX

VSTS type and version
VisualStudio.com

If VisualStudio.com, what is your account name? http://escamoteur.visualstudio.com

What's not working?
There is no Task available to just build iOS libaries like I can do for Android using iOS build
This is needed to create Nuget packages for Android and iOS from TFS.

Got it working. I was missleaded by thinking I need a MAC to build an iOS lib.


remaining BCMR bugs

Hello, thanks for resolving #170, however after more thorough testing I still found some remaining issues.
Now I can import the BCMR linked in the token genesis with the tokenId (pre-genesis).
However, when a transaction is made from the token genesis this metadata dissapears from addMetadataRegistryAuthChain and instead it errors... This makes it unusable for tokenmetadata.

[ ] addMetadataRegistryAuthChain should return array with all linked opreturns, not error when the latest tx does not contain an opreturn. example authcain of  c166ed3c7238b4419cfa01f8dbfdc604118542ccee8a8b0d21028105e6eebcd4
[ ] Error mainnet-1.0.14.js:3 Uncaught Error: Invalid authchain transaction (does not spend 0th output of previous transaction)
when authchain is valid. example: https://chipnet.chaingraph.cash/tx/16ec71de01a4e5f4ff528f4a006e5f27adf4f49d693f9211384f6f69d05b390b
[ ] if the opreturn data gets over 228 hexadecimal character in length I get an error
Error: the transaction was rejected by network rules. scriptpubkey (code 64)
[ ] an extra whitespace or enter after a seedphrase causes the wallet import to fail, is this expected to be filtered client side??

here's the full chain of txs for the 2 examples so it's easier to follow the BCMR stuff
0) pre-genesis: https://chipnet.chaingraph.cash/tx/c166ed3c7238b4419cfa01f8dbfdc604118542ccee8a8b0d21028105e6eebcd4

token genesis with BCMR in opreturn: https://chipnet.chaingraph.cash/tx/0eb7b9f6660a6d32cf2f0a68579c875d1f1c6d7d8b9768e688d7b836c0e7efd0
1st 'DogeCash' token transaction: https://chipnet.chaingraph.cash/tx/b9bb14185a8ef6c72e94b47a3175be32524be79e175106e214164f9113fdd122
2nd  'DogeCash' token transaction: https://chipnet.chaingraph.cash/tx/90310f3e060e75959628e6fee3d48301bebac1cd59d0670537b4227dc30787ba

the other one I used for testing is called 'example token'
0) pre-genesis:  https://chipnet.chaingraph.cash/tx/51094fb26daa7c9804cc7938716cd5b8d50d5c3df3a38c90d03931ce4e904e23

token genesis with BCMR in opreturn:
https://chipnet.chaingraph.cash/tx/0090123ce181289927317ee6c209d66bf5934ed389f555da7715b46e843a24ed
1st 'example token'  transaction: https://chipnet.chaingraph.cash/tx/f17a09cfbcfd18d03f7a19a0def29679ff33ce171b93a31fa33d231c679af683
2nd  'example token' transaction: https://chipnet.chaingraph.cash/tx/4009132a9c87d11c77efc12f653057ff0f4d7b084d00380f6f9ceb43ca220f59

the metadata was correct with addMetadataRegistryAuthChain after the tokengenesis but after the 1st transaction it errors

Should be fixed in release 1.0.15 https://github.com/mainnet-cash/mainnet-js/releases/tag/1.0.15

Indeed it was a pesky bug with long pushes in op_return. See release 1.0.16 which fixes that


terraform-providers.yandex: 0.40.0 -> 0.54.0

This terraform module has been moved to the yandex-cloud organization
and the old one archived, thus not receiving any updates.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117507 at 27ac5016 run on aarch64-linux 1

2 packages built successfully:

terraform-full
terraform-providers.yandex

Used this to deploy some test resources, confirmed working.


[ISSUE #2988] Fix fail to send trace of last message before shutting down producer

What is the purpose of the change
Fix #2988 fail to send trace of last message before shutting down producer
Brief changelog
in AsyncRunnable::run , traceContextQueue.poll use 5ms to get data in queue, during the 5ms, traceContextQueue is empty but data in queue is placed to contexts,   waiting for traceExecutor.submit.
so, if call traceExecutor.shutdown() in this 5ms, the data is lost, and exception is thrown.
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.1%) to 54.16% when pulling 6cf284c6826a87ffb22687d9799ff46b9c13b095 on yuz10:develop3 into 52348b862c0dda897764c3b51fe1436c1a5ae0fe on apache:develop.

Codecov Report

Merging #2989 (6cf284c) into develop (52348b8) will decrease coverage by 0.04%.
The diff coverage is 72.72%.

@@              Coverage Diff              @@
##             develop    #2989      +/-   ##
=============================================
- Coverage      47.91%   47.86%   -0.05%
+ Complexity      4560     4552       -8
=============================================
  Files            552      552
  Lines          36628    36632       +4
  Branches        4844     4845       +1
=============================================
- Hits           17549    17535      -14
- Misses         16857    16869      +12
- Partials        2222     2228       +6

Impacted Files
Coverage Δ

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
77.61% <72.72%> (+5.02%)
:arrow_up:

...ain/java/org/apache/rocketmq/test/util/MQWait.java
43.24% <0.00%> (-10.82%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
71.15% <0.00%> (-7.70%)
:arrow_down:

...a/org/apache/rocketmq/logging/inner/SysLogger.java
28.57% <0.00%> (-5.72%)
:arrow_down:

...apache/rocketmq/remoting/netty/ResponseFuture.java
85.00% <0.00%> (-5.00%)
:arrow_down:

...rocketmq/remoting/netty/NettyRemotingAbstract.java
46.86% <0.00%> (-4.06%)
:arrow_down:

...java/org/apache/rocketmq/logging/inner/Logger.java
52.63% <0.00%> (-3.35%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
49.25% <0.00%> (-2.99%)
:arrow_down:

...ava/org/apache/rocketmq/test/util/VerifyUtils.java
46.26% <0.00%> (-2.99%)
:arrow_down:

...rocketmq/client/impl/factory/MQClientInstance.java
50.94% <0.00%> (-1.46%)
:arrow_down:

... and 11 more

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 52348b8...6cf284c. Read the comment docs.


added fireEvent util

What: added fireEvent utility

Why: https://github.com/kentcdodds/dom-testing-library/issues/5

How: src/events.js

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

there are a couple events we'll need to fallback to triggering synthetic events for (change, select, mouseenter, mouseleave) so I'll add that logic there

@jomaxx Could you please clarify about synthetic events? How does Cypress handles these events from within the browser?

@sompylasar let's move discussion about synthetic events to https://github.com/kentcdodds/react-testing-library/pull/48

Thanks so much for your help! I've added you as a collaborator on the project. Please make sure that you review the other/MAINTAINING.md and CONTRIBUTING.md files (specifically the bit about the commit messages and the git hooks) and familiarize yourself with the code of conduct (we're using the contributor covenant). You might also want to watch the repo to be notified when someone files an issue/PR. Please continue to make PRs as you feel the need (you can make your branches directly on the repo rather than your fork if you want). Thanks! And welcome to the team :)

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Accel map or brake map does not exist

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I want to use accel_brake_map_calibrator for calibration and ensure that my CSV file location is correct. After running ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true, rviz does not display the map, and an error appears: 'Accel map or brake map does not exist.
I confirm that the map is in
/home/prius428/autoware.prius428/install/autoware_raw_vehicle_cmd_converter/share/autoware_raw_vehicle_cmd_converter/data/default/
Expected behavior
An Accel map or brake map must exist.
Actual behavior
[accel_brake_map_calibrator-1] [WARN] [1729581052.907277212] [accel_brake_map_calibrator]: Accel map or brake map does not exist
Steps to reproduce
1.Start autoware
2.ros2 launch autoware_accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Versions
Ubuntu 22.04
ROS2 Humble
Possible causes
No response
Additional context
No response

These warnings can be ignored. The files will be created once calibration data starts being recorded.
Right now I tested calibration with Carla and I was able to generate the accel_map.csv and brake_map.csv.


⚠ Bofrost.be has degraded performance

In 7ffcdce, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1446 ms

Resolved: Bofrost.be performance has improved in eda2652.


Misc cleanups in the parser

This refactors sway-parse with various de-duplications, simplifications, as well as adding docs in some places.

We will actually be moving to sway fmt v2 very soon, which is a complete rewrite. That being said, one of the old formatter tests is failing.

Nice. I really like the guarded_parse method, that does simplify the code in a lot of places.
LGTM :+1:


Do some general cleanup

This moves code into distinct packages, to help solidify interfaces. It also adds some tests and comments.
r? @scottjab
This can be reviewed commit by commit.

LGTM


After successfull login redirect is not working

Hi,
First I want to say that project is great, and after playing around with zitadel and oauth2-proxy for 2 days with multiple trial and errors this just works and now I dont need another service.
But I have one issue, after login redirect is not working.
this is my middleware setup:
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: oidc-auth
  namespace: traefik
spec:
  plugin:
    traefik-oidc-auth:
      provider:
        url: "https://zitadel.mydomain"
        clientId: "clientId"
        usePkce: true
      secret: "secret"
      scopes:
        - "openid"
        - "profile"
        - "email"

I am trying to protext traefik dashboard and I apply this middleware and that part work like a charm, but redirect is not working.
When I open network tab after login i can see two requests both with 302 status code:
POST ON https://zitadel.mydomain/ui/login/mfa/u2f/verify
GET ON https://zitadel.mydomain/oauth/v2/authorize/callback?id=300474110239049093
If I take url from second request and paste it in new tab redirect works.
in Zitadel I have project with app that have redirect uri:  https://traefik.mydomain/oidc/callback

Thx @zarnautovic,
your redirect url config in ZITADEL looks correct.
What i've tried:
middlewares:
    oidc-auth:
      plugin:
        traefik-oidc-auth:
          LogLevel: DEBUG
          Provider:
            UrlEnv: "PROVIDER_URL"
            ClientIdEnv: "CLIENT_ID"
            UsePkce: true
          Scopes: ["openid", "profile", "email"]

  routers:
    dashboard:
      entryPoints: ["web"]
      rule: "Host(`dashboard.localhost`)"
      service: dashboard@internal
      middlewares: ["oidc-auth@file"]
    dashboard-api:
      entryPoints: ["web"]
      rule: "Host(`dashboard.localhost`) && PathPrefix(`/api`)"
      service: api@internal
      middlewares: ["oidc-auth@file"]

In ZITADEL i've whitelisted http://dashboard.localhost:9080/oidc/callback.
Now if i navigate to http://dashboard.localhost:9080 in the browser i get redirected to ZITADEL and after login i get redirected back to http://dashboard.localhost:9080, showing the traefik dashboard.
What is your router config?


Puppet 8 compatibility

puppet-lint issues:
WARNING: legacy fact 'memorysize' on line 37 (check: legacy_facts)
WARNING: legacy fact 'selinux' on line 107 (check: legacy_facts)
WARNING: top scope fact instead of facts hash on line 37 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 55 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 57 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 59 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 64 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 71 (check: top_scope_facts)
WARNING: top scope fact instead of facts hash on line 107 (check: top_scope_facts)

Related to #90 as well. Any updates on this, or if the module is being maintained (#93)?


Add quiet mode for invoke-scuba

🗣 Description
Allows for execution of Invoke-Scuba with or without invoking browser to automatically show report.
Closes #272
💭 Motivation and context
Allows execution of Invoke-Scuba on systems without default application support for HTML files.
Adds support option for Windows Server Core by using -Quiet switch
🧪 Testing

Executed Invokee-SCuBA with and witout -Quiet switch.
With: Show report in browser
Without: Does not show report in browser but report is on file system (can bring up manually)

Execute Unit Test
Additional test cases added to check Quiet is passed apropriately

✅ Pre-approval checklist

[X] This PR has an informative and human-readable title.
[X] Changes are limited to a single goal - eschew scope creep!
[X] All future TODOs are captured in issues, which are referenced
in code comments.
[X] All relevant type-of-change labels have been added.
[X] I have read the CONTRIBUTING document.
[X] These code changes follow cisagov code standards.
[X] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[X] Tests have been added and/or modified to cover the changes in this PR.
[X] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

@crutchfield The testing description states that the report is supposed to show the report with the quiet switch, but testing shows the opposite. Which one is it supposed to be?

@crutchfield The testing description states that the report is supposed to show the report with the quiet switch, but testing shows the opposite. Which one is it supposed to be?

:)  I fixed description.


Enable snapshot image creation for PUSH and TIMER [master]

To ensure that the snapshot image creation happens more regularly,
we ensure that the preparation for it happens for both a PUSH and
a TIMER trigger.
This will ensure that the images are updated on a daily basis,
not just when a new patch merges.
Issue: RE-2278

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.

recheck_all

Until https://github.com/rcbops/rpc-openstack/pull/3509 merges, the syntax/lint tests will fail.

recheck_container_ansible-lint_tox-test
recheck_container_ansible-syntax_tox-test


UART C

Hi,
Apologies, for leaving this message here. I was wondering if here are any example of the UART being used for read and write in C. The example shows the UART context being created, however, nothing is ever done with the context. Are there any examples online?
Any help would be really appreciated as I am use to programming c# which is obviously not nearly as low level.
Best regards,
Seamus

Check out the C++ example, it has a full cycle except reading, is that good enough for you?

I've modified the example to perform a write, it's not as complete as the C++ example but shows the basics. Is that enough for you? See e4810262273c9eab4fcddbfeefbe82aba344e

Thanks very much for your help. That is great. Thanks again!


Serde cleanup.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #441 into master will decrease coverage by <.01%.
The diff coverage is 79.54%.

@@            Coverage Diff             @@
##           master     #441      +/-   ##
==========================================
- Coverage   82.38%   82.37%   -0.01%
==========================================
  Files         149      149
  Lines        8628     8635       +7
==========================================
+ Hits         7108     7113       +5
- Misses       1520     1522       +2

Impacted Files
Coverage Δ

src/gluonts/core/serde.py
86.01% <79.54%> (-0.76%)
:arrow_down:


Semi-automated Emacs package updates

Still getting the following trying to eval:
nixpkgs $ nix-instantiate -A emacsPackagesNg.melpaPackages
error: anonymous function at /Users/mbauer/Projects/nixpkgs/pkgs/applications/editors/emacs-modes/melpa-generated.nix:1594:34 called without required argument ‘font-lock-plus’, at /Users/mbauer/Projects/nixpkgs/lib/customisation.nix:74:12

Is it possible to fix easily?

@matthewbauer I have a PR for this https://github.com/NixOS/nixpkgs/pull/31302

@adisbladis Thank you for the reminder, I've merged it.
How do we test such updates to many emacs packages? Can we require everything provided by emacsWithPackages?

@orivej If someone wanted to put together a hydra job that would trigger when I pushed to a branch, I'd be happy to do that.  It should be fairly light-weight to evaluate all the expressions.

Automatic evaluation of emacs packages would be great, but I was thinking about testing the packages with Emacs, e.g. by calling (require) for each (provide), or forcing all autoloads.

@orivej That sounds like a nightmare of busywork for anyone trying to keep the package sets current.  It is also a more stringent standard than melpa itself takes.

I mean that’s basically what the Emacs compiler is doing right?

@matthewbauer I'm not sure what you mean when you say "the Emacs compiler"?

@matthebauer You are right, I forgot about it. But we are missing the ability to build all emacs packages, right? nix-build -A emacs25PackagesNg fails with Package … is marked as broken, refusing to evaluate, and hydra and nox-review do not recurse into emacs25PackagesNg.

@mdorman emacs -L . --batch -f batch-byte-compile *.el in pkgs/build-support/emacs/trivial.nix.

Yeah that's an issue that maybe should be looked at in NixOS/nix.
You can do something like this:
nix-build -E 'with import <nixpkgs> {config.allowBroken = true;}; lib.filterAttrs (key: value: (lib.isDerivation value) && !((builtins.hasAttr "broken" value.meta) && value.meta.broken)) emacsPackagesNg'

But it's going to be a huge number of packages.

So I tried that nix-build expression.  It appears to have done some reasonable amount of testing, in a not-outrageous amount of time, and far fewer packages failed than I expected.  I'll look into incorporating the process into the update workflow.


Memory leak when closing Firefox Dev Tools

Vue devtools version
6.4.5
Link to minimal reproduction
n/a
I am able to reproduce the error with a minimal Vue app:
yarn create vite
-> Vue
-> Typescript

cd <dir>
yarn
yarn dev

Steps to reproduce & screenshots

Open Dev Tools on a website with Vue application
Go to the "Vue" tab in the dev tools
Close Dev Tools

Monitor RAM usage to see the memory leak:

What is expected?
Memory stays constant.
What is actually happening?
Memory usage increases and within a few seconds all memory is used.
System Info
System:
    OS: Linux 6.0 KDE neon 5.26
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
    Memory: 34.02 GB / 62.60 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.13.1 - /tmp/fnm_multishells/19446_1670227570518/bin/node
    Yarn: 3.2.3 - ~/code/redacted/node_modules/.bin/yarn
    npm: 8.1.2 - /tmp/fnm_multishells/19446_1670227570518/bin/npm
  Browsers:
    Firefox: 107.0.1

Any additional comments?
How can I debug this issue to give you the required information? I am unable to re-open the Dev Tools after closing them for the first time, so I cannot export a memory dump or a profiler recording.
I cannot leave the Dev Tools open since the bug only occurs when closing them.

The exact same thing also happens on Windows.

Same on chrome mac with vite + vue 3

I am using a Webpack setup with Vue 3. On Firefox Developer Edition, 111.0b8. Vue Dev Tools is 6.5.0.
The memory consumption skyrockets once I open Vue Dev Tools inside Firefox Dev Tools. The browsers will very soon become unusable afterwards. Sometimes I did not realise what happened, because I was doing something else. Then suddenly Firefox ate all of my 32GB of memory, or what was remaining to use. The same does not happen in Chrome with VDT.

I am seeing something similar, but the Dev Tools extension also begins to cause sustained CPU usage >= 100%. I captured a 5-second profile in Firefox's process manager and it looks like these functions may be the culprit:

Extension "Vue.js devtools" (ID: {5caff8cc-3d2e-4110-a88a-003cc85b3858}): moz-extension://47a39889-b497-4b9c-8195-d7a8ea28bc8f/build/detector.js:1:42537
Extension "Vue.js devtools" (ID: {5caff8cc-3d2e-4110-a88a-003cc85b3858}): moz-extension://47a39889-b497-4b9c-8195-d7a8ea28bc8f/build/backend.js:14502:18

Same issue here: once you close Vue devtools, memory usage increases steadily until all memory is used. The only caveat is that I need to open and close Vue devtools twice in order to reproduce, so:

Open Vue devtools
Close Vue devtools
Open Vue devtools
Close Vue devtools

And memory usage begins to skyrocket.
OS: Ubuntu 22.04
Browsers: Mozilla Firefox 115.0.2, Google Chrome 114.0.5735.198
Vue devtools version: 6.5.0

This issue is still relevant for many users, which makes the DX using Vue Devtools almost useless.

@tobias-kuendig
Are you running any other devtool extensions, e.g. React Developer Tools, Redux DevTools, Angular DevTools? If so, disable all of these as for me these were causing somehow the memory leak. It can also be due to another extension that is causing this issue. I know this is the poor man's solution, but it works for now.
These are my global settings:

Might be of interest:
https://github.com/vuejs/devtools/issues/2103#issuecomment-1785125872


fix(fastify.js): fix reply end handling

:tada: This PR is included in version 1.28.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow forward seeking in caching stream

@jeremeamia @jeskew
Addresses https://github.com/aws/aws-sdk-php/issues/587

The docblock still says a RuntimeException will be thrown if you seek from SEEK_END, but otherwise :shipit:

Docblock fixed. Thanks.


Changed the endian that we send to network endian

The webots repo uses network endian for sending the size of the messages. I've changed it to network endian on (my pr)[https://github.com/NUbots/NUbots/pull/394] so I suppose it should be changed here also.

@Bidski @tayloryoung6396 can you two please test this change? I don't know if anyone else has the test working yet lol


There is an issue with rendering in WSL

Code not rendered or rendering error

Also, it is not possible to enter the function internally, so it is necessary to close the notebook file and then open it to be effective

Got similar issues since the last update of vscode.
Original loaded cell:

Adding space between:

Writing new code in the cell:

Seeing similar issues also without using WSL since the last update (Jupyter: v2024.2.0).
Seems so far as if only notebooks which existed already before the update are affected.

自上次更新 vscode 以来遇到了类似的问题。
原始加载单元：
在以下内容之间添加空格：

在单元格中编写新代码：

Jupyter 扩展版本：v2024.2.2024022602（预发布）
快速解决方法：删除单元格并按 Ctrl+Z，或将单元格切换到 markdown (M)，然后返回代码 (Y)

Thank you, I'll try it

自上次更新 vscode 以来遇到了类似的问题。
原始加载单元：
在以下内容之间添加空格：

在单元格中编写新代码：

Jupyter 扩展版本：v2024.2.2024022602（预发布）
快速解决方法：删除单元格并按 Ctrl+Z，或将单元格切换到 markdown (M)，然后返回代码 (Y)

It still doesn’t work in my notebook. I have to close the file again and reopen it.

Same issue in remote container (docker).
I cannot see any logs but Python Language Server says repeatedly: "Received change text document command for closed file."
I did not have this issue in the last month. I got this one after update in this Monday.

I have the same issue, with garbled syntax highlighting for jupyter notebooks in vscode. It seems to be similar to this one from 2 years ago:
https://www.reddit.com/r/vscode/comments/rh5irl/syntax_highlighting_is_completely_broken_outside/
Note that deleting the settings.json file seemed to fix it back then for that person, but that's not something I want to (or should) do.

This is a bug in VS Code: https://github.com/microsoft/vscode/issues/206487
It's already fixed in VS Code Insiders and assuming the fix behaves well in insiders, could ship VS Code stable as soon as tomorrow.
Alternatively, you can work around this issue by downgrading to the VS Code 1.86.2.


Replace ThemableElement with ThemableMixin

ThemableMixin in Vaadin 23 has support for LitElement
https://github.com/FlowingCode/fc-applayout/blob/7a434b131181699950a7e57a22650e9ae8d2234b/src/fc-applayout.ts#L34

Implemented in this commit


ReferenceError: callback is not defined

I am getting the issue
Error in Success callbackId: FirebasePlugin75355054 : ReferenceError: callback is not defined
I am using the cordova-ios 5.1.1
And following cordova plugins:
br.com.brunogrossi.MediaScannerPlugin 0.1.3 "Media Scanner Plugin"
com.dawsonloudon.videoplayer 1.0.0 "VideoPlayer"
cordova-custom-config 5.1.0 "cordova-custom-config"
cordova-open-native-settings 1.5.2 "Native settings"
cordova-plugin-android-permissions 1.0.0 "Permissions"
cordova-plugin-androidx 1.0.2 "cordova-plugin-androidx"
cordova-plugin-androidx-adapter 1.1.0 "cordova-plugin-androidx-adapter"
cordova-plugin-badge 0.8.8 "Badge"
cordova-plugin-calendar 5.1.4 "Calendar"
cordova-plugin-certificates 0.6.4 "Certificate Plugin"
cordova-plugin-device 2.0.3-dev "Device"
cordova-plugin-dialogs 2.0.2 "Notification"
cordova-plugin-enable-multidex 0.2.0 "Enable Multidex"
cordova-plugin-file 6.0.2-dev "File"
cordova-plugin-file-opener2 2.2.0 "File Opener2"
cordova-plugin-file-transfer 1.7.1 "File Transfer"
cordova-plugin-firebasex 8.0.1 "Google Firebase Plugin"
cordova-plugin-geolocation 4.0.2-dev "Geolocation"
cordova-plugin-inappbrowser 1.2.1 "InAppBrowser"
cordova-plugin-local-notification 0.9.0-beta.3 "LocalNotification"
cordova-plugin-network-information 2.0.2 "Network Information"
cordova-plugin-splashscreen 5.0.3 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-uniquedeviceid 1.3.2 "UniqueDeviceID"
cordova-plugin-whitelist 1.3.4 "Whitelist"
cordova-plugin-wkwebview-engine 1.2.1 "Cordova WKWebView Engine"
Please let me know if I am doing anything wrong here.

From the log extract it looks like you are calling grantPermission() without passing in the required callback function for the plugin to pass the result to so it is failing when attempting to parse and pass the boolean result to the callback.
Pass in the callback as required and it should fix your issue.
Please also see the example project for a working reference.

@dpa99c So is the callback is expected but not required to fulfill the general functionality? I'm guessing its more for logging purposes or to implement some other logic in case of a failure?

@dpa99c So is the callback is expected but not required to fulfill the general functionality? I'm guessing its more for logging purposes or to implement some other logic in case of a failure?

yes but I'd think it unlikely you wouldn't want to define a callback in a production app, e.g. to inform the user of the consequence and/or log an event to analytics

@dpa99c for sure, thanks for the reply.


Document --database.old-system-collections startup option

https://github.com/arangodb/arangodb/pull/12700 3.8.devel
https://github.com/arangodb/arangodb/pull/12708 3.7.3
Internal ref: https://arangodb.slack.com/archives/CQEAB4727/p1603398643009500

Default value changed and deprecated in 3.8, will be removed. It's documented in the release notes.


[Feat] Add graceful detection of signal to exit + SignalConnector and merge SlurmConnector.

What does this PR do?

Right now, when the script is being killed, a fault tolerant checkpoint would be saved.
However, Lightning can't always ensure it is always fully happening in reproducible part of the codebase.
When running in the cloud, there is 2-3 min to kill the script.
The proposal is to add a mechanism to detect a killing signal as been sent and Lightning will terminate on the next reproducible part in this time windown.
Parts #9567
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Think looks great! Thanks for adding the mechanism @tchaton!


feat: implement map to retain original struct field names in schema

Description:
This pull request introduces a new enhancement that addresses the feature request outlined in #116. A public map[string]string has been added to the Schema struct which serves to preserve the original names of struct fields as reflected before any modifications by struct tags or KeyNamer.
The primary purpose of this new field is to provide an accessible means through the schema object, enabling the matching of an instantiated struct's fields with the corresponding schema definitions during a post-processing phase.
Usage Example:
An envisioned application of this feature, pending its acceptance and merge, can be previewed in the lazygit project's open pull request, specifically at generate.go#L43.
With this addition, developers can now directly utilize the unaltered struct field names from the schema object, simplifying and streamlining the schema manipulation process.

Added a test.


Bug resolution suggestion

Hi, I'm not sure if this PoC is still maintained, but I found what a believe to be a bug in the code. I guess it occurred due to some updates to Microsoft's API (as the PoC is getting quite old).
Problem:
After running the script multiple times, the condition on line 294 If ($badpwdcount -lt ($threshold - 1)) will start to evaluate as false, even though badpwdcount is actually less than threshold-1. That results in an infinite loop.
Proposed solution:
On line 290, change the code from $badpwdcount = $userObj[$i].Properties.badpwdcount to $badpwdcount = $userObj[$i].Properties.badpwdcount[0], adding the index bracket.
Argumentation:
The badpwdcount property is of type System.DirectoryServices.ResultPropertyValueCollection, hence the missing index brackets result in assigning the whole collection to the $badpwdcount variable, which is then compared to an integer.
Note:
If you agree with me, I can create a pull request for it.

Thanks, I agree. If you could make a pull request that would be awesome,
thanks!
BR
/Jakob
On Mon, Jun 28, 2021, 20:29 Tomáš Vašíček @.***> wrote:

Hi, I'm not sure if this PoC is still maintained, but I found what a
believe to be a bug in the code. I guess it occurred due to some updates to
Microsoft's API (as the PoC is getting quite old).
Problem:
After running the script multiple times, the condition on line 294 If
($badpwdcount -lt ($threshold - 1)) will start to evaluate as false, even
though badpwdcount is actually less than threshold-1. That results in an
infinite loop.
Proposed solution:
On line 290, change the code from $badpwdcount =
$userObj[$i].Properties.badpwdcount to $badpwdcount =
$userObj[$i].Properties.badpwdcount[0], adding the index bracket.
Argumentation:
The badpwdcount property is of type
System.DirectoryServices.ResultPropertyValueCollection, hence the missing
index brackets result in assigning the whole collection to the $badpwdcount
variable, which is then compared to an integer.
Note:
If you agree with me, I can create a pull request for it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ZilentJack/Spray-Passwords/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTPQCINGSAEKVY3QYF47ZDTVC5RNANCNFSM47OPUPKA
.

Thanks, I agree. If you could make a pull request that would be awesome, thanks! BR /Jakob
…
On Mon, Jun 28, 2021, 20:29 Tomáš Vašíček @.***> wrote: Hi, I'm not sure if this PoC is still maintained, but I found what a believe to be a bug in the code. I guess it occurred due to some updates to Microsoft's API (as the PoC is getting quite old). Problem: After running the script multiple times, the condition on line 294 If ($badpwdcount -lt ($threshold - 1)) will start to evaluate as false, even though badpwdcount is actually less than threshold-1. That results in an infinite loop. Proposed solution: On line 290, change the code from $badpwdcount = $userObj[$i].Properties.badpwdcount to $badpwdcount = $userObj[$i].Properties.badpwdcount[0], adding the index bracket. Argumentation: The badpwdcount property is of type System.DirectoryServices.ResultPropertyValueCollection, hence the missing index brackets result in assigning the whole collection to the $badpwdcount variable, which is then compared to an integer. Note: If you agree with me, I can create a pull request for it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTPQCINGSAEKVY3QYF47ZDTVC5RNANCNFSM47OPUPKA .

I've made the pull request a few days ago and you haven't reacted to it yet. Could you please confirm that it's visible and valid?
(It's the first pull request I've ever created, I might have messed something up. So I'm just checking to be sure it's ok.)


More information

Thanks for sharing this, I really appreciate your effort on sharing it :)
Do you have any tutorial or can recommend something where I can understand better things like: where/how to add authentication, adding mods, adding the GSLT and api keys for workshop, and so on?

So basically what you need to learn is how to work with docker. You can always just clone this repo and start modifying it. Addig mods/authentication/etc is basically copying/modifying files inside the container.


docs(portal-cli): update to match readme

This doc is based on readme of repo, however changes made did not get reflected here.

I broke the link to https://github.com/Kong/kong-portal-templates =[

@HenriPro I made some suggested changes. Please update as you see appropriate. Thx!

Awesome, wow I feel slightly illiterate 😂, good catches. I think I got all those now.


validate that non-ref parameters are not written to in archetype and procedure bodies

For example, the following should be invalid.
--mpcal Invalid {
  archetype Arch(a) {
    l1:
        a := 1;
  }
  variables i = 0;
  process (Proc = 0) == instance Arch(i);
}

this check should be run after macro expansion.

validation in place as of dee731daeb3d


Update hololens-known-issues.md

OPS Build status updates of commit c7df622:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/hololens-known-issues.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Opening CanadianAboriginal with Glyphs 2.5b (1125) warns about components shifted

If I open the NotoSansCanadianAboriginal-MM.glyphs file with the latest available Glyphs.app beta 2.5b (1125) (as of today March 27 2018), I get this warning:

opening a file from a older version will apply the following changes. Check the boxes for the values that you would like to keep unchanged

If I check them all and press "Keep Selected" and save, in the git diff I see many changes in the alignment field (from value 1 to -1). I don't know what that attribute is meant to do.
If I don't check the boxes and proceed, I see several changes to the components' offsets.
I don't know whether there is a problem with the source files, or in my Glyphs.app global settings, or whether the problem is in the version of Glyphs.app used to produce the source file, or with the beta one that I'm using...
I would like to reduce to the minimum all unnecessary changes, retain as much as possible the original data, while doing minor changes to some custom parameters (mostly to address #107).
cc @punchcutter @schriftgestalt

There where some situations where you couldn't activate the alignment. So I changed the algorithm slightly to fix that. But that had the consequences that some components would be aligned automatically and move to different places. To avoid changed to the shape, I added the test and ask the user if he likes those changes or not and give him the option to disable it (it can be activated for each component later if needed).
To keep things consistent, I recommend to set up the file that all components can be aligned automatically. There are several ways to do that, with normal spacing/kerning, mark and entry/exit anchors. (details here: https://glyphsapp.com/tutorials/reusing-shapes-component-tricks)


Suggestion: Use project directory name for workspace: base directory

Using src as the default base path seems arbitrary.
Would it not make more sense to use the projects directory name as the base as that is what the developer who created the project decided already?
And I only say this because some tools do expect the project directory to be the same across builds.
Just a suggestion. Perhaps it's too much of a breaking change - feel free to close.

Thanks for the suggestion, however, we will not be able to accommodate the request. Similar to the Go 1.0 compatibility guarantee [1] we are trying to avoid breaking changes now that Drone 1.0 is released. You can change the default directory, however, with the following syntax:
workspace:
  base: /go
  path: src/github.com/foo/bar

This historical reason for having a separate base and path was to support Go projects. The base could be set to the gopath to ensure dependencies were saved between steps. Going forward this is less important with the advent of Go modules, and with the addition of temporary volumes [2].
[1] https://golang.org/doc/go1compat
[2] https://docs.drone.io/examples/language/golang/


Fix performance regression caused by disabling ed25519-dalek's fast feature

Motivation

ed25519-dalek's default features ended up transitively including getrandom as a dependency, which was an issue for Linera Wasm applications that use linera-sdk. Therefore, it was disabled by PR #2602. However, that also disabled the fast feature, was caused a performance regression.
Proposal

Re-enable the fast feature, together with the zeroize feature which is also important.
Test Plan

The long faucet chain test should now not timeout in CI.
Release Plan

Nothing to do / These changes follow the usual release cycle, because this fixes a regression for an issue that is not present in any released version.

Links

reviewer checklist

Nice catch!

Thanks @afck for the insights that pointed to the root cause :D


file.type is undefined when setting ngf-src

On version 7.0.6 this worked, on version 7.0.9 it doesn't.
So I have this html:

Drop cover picture here (500x500)

When the page is loaded from the server the controller sets vm.cover to the url of the already uploaded image. When a user drops a new image into that div it changes vm.cover to a File.
On version 7.0.6 on page load the img showed the correct image loaded from the given url in vm.cover, on latest version it throws an error saying file.type is undefined.
I was able to narrow it down to the new $watch  statement added to the ngf-src directive.
Regards

Fixed in version 7.0.10

Having the same problem.
		<md-button ngf-select ng-model="locality.profile_picture" ngf-multiple="false">

		</md-button>

This is the Edit form, so initially locality.profile_picture is a valid URL string. On page load I get "file.type is not defined"

Try to assign the initial url to another model and have ngf-src="locality.profile_picture || default_pic"


Error Type: <type 'exceptions.AttributeError'>

21:59:44 T:140095424284416   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.AttributeError'>
Error Contents: 'xbmc.RenderCapture' object has no attribute 'waitForCaptureStateChangeEvent'
Traceback (most recent call last):
File "/storage/.kodi/addons/script.service.hyperion-master/addon.py", line 48, in
next_state = state.execute()
File "/storage/.kodi/addons/script.service.hyperion-master/resources/lib/state.py", line 103, in execute
self.__capture.waitForCaptureStateChangeEvent(200)
AttributeError: 'xbmc.RenderCapture' object has no attribute 'waitForCaptureStateChangeEvent'
-->End of Python script error report<--

Fixed