Fix: Upgrade vendored to v1.13.0 & Replace glog to klog

1.Describe what this PR did
Upgrade vendored Kubernetes to v1.13.0 & Replace glog to klog
2.Does this pull request fix one issue?
NONE
3.Describe how you did it
Upgrade vendored Kubernetes to v1.13.0 & Replace glog to klog
4.Describe how to verify it
Env:
k8s:v1.13.0
networkPlugin: weave:2.5.0
docker:18.06.1-ce
cri-tool:
NONE
Kubernetes:
runtime-docker:
[root@frakti1-13-1 ~]# kubectl create -f frakti-docker-1.yaml
deployment.apps/frakti-docker-1 created
[root@frakti1-13-1 ~]# kubectl create -f frakti-docker-2.yaml
deployment.apps/frakti-docker-2 created
[root@frakti1-13-1 ~]# kubectl get pod  -owide
NAME                               READY   STATUS    RESTARTS   AGE   IP          NODE           NOMINATED NODE   READINESS GATES
frakti-docker-1-984f44ff9-nlsqx    1/1     Running   0          43s   <IP_ADDRESS>   frakti1-13-1   <none>           <none>
frakti-docker-2-6c7d559876-fwvql   1/1     Running   0          39s   <IP_ADDRESS>   frakti1-13-2   <none>           <none>

Cross host network:
[root@frakti1-13-1 ~]# docker exec -it e53f5e5d0987 bash
[ root@frakti-docker-1-984f44ff9-nlsqx:/etc/nginx ]$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.066 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.080 ms
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.066/0.073/0.080/0.007 ms
[ root@frakti-docker-1-984f44ff9-nlsqx:/etc/nginx ]$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=44.2 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.569 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.615 ms
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.569/15.159/44.294/20.601 ms

Delete deployment:
[root@frakti1-13-1 ~]# kubectl get deployment
NAME              READY   UP-TO-DATE   AVAILABLE   AGE
frakti-docker-1   1/1     1            1           2m48s
frakti-docker-2   1/1     1            1           2m44s
[root@frakti1-13-1 ~]# kubectl delete deployment frakti-docker-1
deployment.extensions "frakti-docker-1" deleted
[root@frakti1-13-1 ~]# kubectl delete deployment frakti-docker-2
deployment.extensions "frakti-docker-2" deleted
[root@frakti1-13-1 ~]# kubectl get deployment
No resources found.
[root@frakti1-13-1 ~]# kubectl get pod
No resources found.

Example yaml:
[root@frakti1-13-1 ~]# cat frakti-docker-1.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: frakti-docker-1
  labels:
    frakti: frakti
spec:
  selector:
    matchLabels:
      frakti: frakti
  template:
    metadata:
      annotations:
        runtime.frakti.alpha.kubernetes.io/OSContainer: "true"
      labels:
        frakti: frakti
    spec:
      nodeName: frakti1-13-1
      containers:
      - name: frakti
        image: gcr.io/google_containers/nginx
        env:
          - name: TESTNAME
            valueFrom:
              fieldRef:
                fieldPath: status.hostIP

Hi, @resouer @eparis .Is there anything else that needs improvement?


<IP_ADDRESS>_W_ACDC-Switch-LaptopComputer

The “PowerACBattery” function is only displayed in the setup screen on the laptop.
Function in “power plans

in “SettingsDlg” there are some window initialization and click event logic “dgvPowerSchemes_CellClick” “SettingsDlg_Load”.
“HandleBtnOkClick” in “SettingsDlg” is used for initialization after saving.
“Program” is used to initialize the “Guid” for startup.
“ProcessMonitor” shares “baselinePowerSchemeGuid” globally in order to realize the correct regulation logic.

Thank you for the PR. Please give me a few days to check the changes. I'm a bit busy right now.
But I've already seen that github is showing most files as completely changed. I think you might have pushed your changes with CR/LF (Carriage Return / Line Feed) line endings.
Usually with git, the git client will convert line endings to whatever the default for your system is during checkout. So CR/LF for Windows and LF for Linux.
This can be configured in the git client you're using. Though I haven't seen anything in Visual Studio to change set. When installing the git command line client on windows, it sets 'core.autocrlf true' in the configuration file. This will do exactly as I described above. If this setting is missing completely, it should use the '* text=auto' setting in the .gitattributes file from the repository.
Sadly I can't tell you exactly how you could change set. If you use the git command line tool, you can set the 'core.autocrlf true' in the configuration. If you're using Visual Studio, it shouldn't have been an issue in the first place. I can't find the option in Visual Studio Code or in SourceTree.
If you can't find a way to fix, it's not too bad. If I checkout your branch, I can see your changes properly in Visual Studio since it fixes the line endings during checkout.
So don't worry too much. I can review your changes perfectly. I just need a few days time.

I'm sorry I'm used to Notepad++ not vs problem,,didn't notice this problem,

I tried to use vs to synchronize the commit but it didn't work, so I used the github HTML commit again.
I'll try the vs commit again.

Okay, I checked the PR.
Everything is pretty okay. I like that the checkboxes for AC and Battery are hidden in the SettingsDlg when the system doesn't even have a battery. I wouldn't have thought of that.
I can't really test the code. I don't have a laptop at hand. But I don't see a reason it shouldn't work.
I will rework some of the code. Just to make it look a little nicer. Some reformatting and stuff. But the functionality stays the way you implemented it.
But I will check the other PR before I change anything, to avoid conflicts.


Example app

Hi @anlumo, be awesome if there were a demo app for this.
Also, I tried building for macOS and failed, is this linux-only?

Yeah, it definitely needs a cleanup.
macOS isn't supported yet because I've only implemented Vulkan so far, and that's not supported on that platform (only Metal). Windows and Linux should work.
In theory Metal can be implemented in just the same way as Vulkan, but I've been just too busy with work stuff to get around to it yet.


[question] performance regarding Snowflake table updates

Hi community,
I'm wondering if anyone has encountered slowness when managing Snowflake resources via pulumi, specifically Snowflake tables.
Our team has a stack with roughly 300 Snowflake tables.  With tracing enabled (pulumi up --tracing ...), Pulumi runs table updates synchronously. See trace waterfall below:

Each 7 shape in the waterfall corresponds to a table update. What's intriguing is that there is a delay between each update of 2 to 3 three minutes where execution seems to be doing nothing.
My questions are:

Is it possible to parallelize these table updates?
Why are there large gaps of no work being done between each table update? I'm running this locally on my laptop in Windows with the following:

Processor	Intel(R) Xeon(R) E-2276M  CPU @ 2.80GHz   2.81 GHz
Installed RAM	64.0 GB (63.7 GB usable)
System type	64-bit operating system, x64-based processor

I also found this discussion post that suggests that maybe we shouldn't use IaC like pulumi to manage Snowflake tables, and instead use SQL scripts to manage the schema. I wasn't able to find the webinar in question to understand why this was suggested.

https://github.com/Snowflake-Labs/terraform-provider-snowflake/discussions/707

Hi @ajsaclayan. Thanks for filing an issue and lettings us know. This is definitely much slower than it should be! Pulumi should parallelize the table updates unless there is some dependency between them.
Could you include the contents of pulumi about run on this stack. We'd like to understand why this is so slow for you.

Hi @iwahbe,
From what I can tell, there is no dependency between each table update. Attaching the contents of pulumi about. Due to privacy I have to omit the names of the resources.
C:\Redacted\Snowflake [troubleshoot-pulumi ≡ +4 ~1 -0 !]> pulumi about
running 'dotnet build -nologo .'
  Determining projects to restore...

  All projects are up-to-date for restore.

  Repo.Name -> C:\Redacted\Snowflake\Repo.Name\bin\Debug\net6.0\Repo.Name.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:01.70

'dotnet build -nologo .' completed successfully
CLI
Version      3.55.0
Go Version   go1.20
Go Compiler  gc

Plugins
NAME       VERSION
dotnet     unknown
snowflake  0.16.1

Host
OS       Microsoft Windows 10 Enterprise
Version  10.0.19044 Build 19044
Arch     x86_64

This project is written in dotnet: executable='C:\Program Files\dotnet\dotnet.exe' version='7.0.102'

Current Stack: ***

TYPE                           URN
pulumi:pulumi:Stack            urn:pulumi:StackName::Repo.Name::pulumi:pulumi:Stack::Repo.Name-StackName
pulumi:providers:snowflake     urn:pulumi:StackName::Repo.Name::pulumi:providers:snowflake::default_0_16_1
snowflake:index/schema:Schema  urn:pulumi:StackName::Repo.Name::snowflake:index/schema:Schema::REG
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
pulumi:providers:snowflake     urn:pulumi:StackName::Repo.Name::pulumi:providers:snowflake::default_0_14_0
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X
snowflake:index/table:Table    urn:pulumi:X

OPP TYPE  URN
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X
updating  urn:pulumi:X

Backend
Name           ***
URL            azblob://pulumi
User           ***
Organizations

Dependencies:
NAME              VERSION
Pulumi.Snowflake  0.16.1
YamlDotNet        12.0.2

This is very interesting, thanks for reporting!
One known issue that prevents full parallelism is that Pulumi currently sequentially stores state updates to the state store after every resource. This does prevent some programs from initiating resources in parallel.. Just looking at the issue I'm not sure if this is in play or there's another problem preventing parallelism, but it might be worth it to experiment with disabling the checkpoints.
There's an experimental option PULUMI_EXPERIMENTAL=true PULUMI_SKIP_CHECKPOINTS=true that would not save checkpoints at all during the program execution until the update finishes. More detail on it in https://github.com/pulumi/pulumi/issues/10668 . It's not yet mainstreamed due to less polished error handling in case the program is interrupted or hard-fails mid-update.
If you run your program with PULUMI_EXPERIMENTAL=true PULUMI_SKIP_CHECKPOINTS=true and it behaves much faster this definitely narrows things down to the checkpoint saving.
I also notice that you might be using file state with Azure Blob service to save the state?
URL            azblob://pulumi

Is it an option to try httpstate with Pulumi cloud backend? Would it work faster for this use case?
Regarding unexplained gaps in the trace, it very well might be that we're missing a tracing annotation on one of the filestate operations. The trace would be more complete in the case of using httpstate backend.

Hey all, these environment variables seem to have improved execution time considerably (10 minutes). Based on the tracing, updates are now running in parallel:

I believe writing the state to Azure after every update was the primary bottleneck. I'll be opening an issue with Microsoft to see if we can optimize anything from our end.

Opened https://github.com/pulumi/pulumi/issues/12315 to ask or these operations to appear in the trace.


Any component that has at least one element with a class results in a preprocessor error

Describe the bug
I see the following error exposed by the Svelte VS Code extension on any component that has at least one element with a class:

Looking at the Svelte extension output, this is the stack trace for the error:
Preprocessing failed
TypeError: _a.classes.replaceAll is not a function
    at Magician.processClassAttribute (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:16850:76)
    at Magician.extract (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:16835:10)
    at markup (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:17020:23)
    at process_markup (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:16754:27)
    at preprocess (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:16776:32)
    at markup (file:///workspace/node_modules/svelte-windicss-preprocess/dist/index.mjs:17211:29)
    at async process_markup (/workspace/node_modules/svelte/compiler.js:31608:24)
    at async Object.preprocess (/workspace/node_modules/svelte/compiler.js:31638:31)
    at async Function.create (/home/node/.vscode-server/extensions/svelte.svelte-vscode-105.8.0/node_modules/svelte-language-server/dist/src/plugins/svelte/SvelteDocument.js:85:30)
    at async SvelteDocument.getTranspiled (/home/node/.vscode-server/extensions/svelte.svelte-vscode-105.8.0/node_modules/svelte-language-server/dist/src/plugins/svelte/SvelteDocument.js:44:38)

I'm happy to help if you need any more information. Thanks!
System Info
System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (2) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 1.97 GB / 5.80 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 16.13.1 - /usr/local/bin/node
    Yarn: 1.22.15 - /usr/bin/yarn
    npm: 8.1.2 - /usr/local/bin/npm
  IDEs:
    Nano: 5.4 - /bin/nano
    VSCode: 1.63.2 - /home/node/.vscode-server/bin/899d46d82c4c95423fb7e10e68eba52050e30ba3/bin/code
  npmPackages:
    svelte: ^3.38.3 => 3.44.3
    svelte-windicss-preprocess: ^4.2.5 => 4.2.5

Used Package Manager
npm

So with Jason's help on the Svelte Discord, I figured out the issue was the bundled version of Node that ships with VS Code doesn't yet support String.prototype.replaceAll. Changing the extension setting svelte.language-server.runtime to explicitly point to my Node executable at /usr/local/bin/node fixed the issue.
Thank you!

Yeah I was just thinking it has to be a node issue, but since you have node 16 I was confused.
We can rebuild that function to use global regexes ..

Just to add on to this:
Node 14 throws this error. Node 16 doesn't throw this error. If you're using .nvm, set your .nvmrc to 16 or run nvm use 16 before running rpm run dev to avoid this error.


📋 Add click-to-copy button for markdown

For the generated code section to be more useful a copy-to-clipboard button should be added. In the generated section at the left top, a button should be added that copies the output markdown to the user's clipboard.

Hey, shall I work on this?
Initial Approach - fetch the innerText of the main tag of CodeResult  and then store in clipboard through clipboardAPI.

Hi! You're more than welcome to. If you need any help or if you have any further suggestions let me know. The initial approach sounds great.

check this out - https://github.com/dannyverp/markdownprofile/pull/9


Fix/dockerfile

Description
Somehow the copying doesn't work anymore...
Is this PR related with an open issue?
Related to Issue #
Types of changes

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

Checklist:

[ ] Follows the code style of this project.
[ ] Tests Cover Changes
[ ] Documentation

Funny gif

Probably good idea to test locally before merging...

testing locally with the latest commit looks the circuits folder is not there:
$ docker exec -it nevermined-keeper-node sh

/home/openethereum # ls /nevermined-contracts/
artifacts   artifacts2  circuits2
/home/openethereum #


SetDefaultDevice times out due to invalid device - Catch Error

System.TimeoutException: COM operation 'SetDefaultDevice' did not complete in the requested time period.    at AudioSwitcher.AudioApi.CoreAudio.CoreAudioDevice.SetAsDefault(CancellationToken cancellationToken)    at FortyOne.AudioSwitcher.AudioSwitcher.Form_Load()

Most likely caused by the device being in an invalid state when trying to set it as the default.
I assume you have a start up device set.
The error doesn't mean much, it may have still set the default device, but it took longer than expected.
It's on the fix list for the next version.
And for some reason it's not included in 1.7.1, this issue can track it.

Duplicate of #2007

@xenolightning I got similar error when I pressed RMB on AudioSwitcher tray icon and selected headphones.  Before that it had stopped switching to headphonesmy hotkey. Switching to speakers works fine. Earlier I had installed Audio Repeater and played with channeling (channelled headphones mic and line-in in one channel). Maybe this information could help.
Also I'll post stacktrace here, the report button doesn't seem to work in the report window.
System.TimeoutException: COM operation 'SetDefaultDevice' did not complete in the requested time period.
   at AudioSwitcher.AudioApi.CoreAudio.CoreAudioDevice.SetAsDefault(CancellationToken cancellationToken)
   at FortyOne.AudioSwitcher.AudioSwitcher.notifyIconStrip_ItemClicked(Object sender, ToolStripItemClickedEventArgs e)
   at System.Windows.Forms.ToolStrip.OnItemClicked(ToolStripItemClickedEventArgs e)
   at System.Windows.Forms.ToolStripDropDown.OnItemClicked(ToolStripItemClickedEventArgs e)
   at System.Windows.Forms.ToolStrip.HandleItemClick(ToolStripItem dismissingItem)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

@xenolightning Oops, restart fixed it so nevermind :D


[1.27] CVE 2023 44487 fixes

Backporting https://github.com/kubernetes-sigs/descheduler/pull/1270

@a7i @knelasevero ptal

/approve

/lgtm


Upgrade hpke dep to v0.10

Just released v0.10.0. Small update; doesn't affect any features used in this crate. See changelog for more detail.

Looks good to me. Thank you for keeping it up to date!


Create sabrinebendimerad-medium.json

Hi, i want to create a pull request to add my blog to the pyladies repo,
Thanks,
Sabrine

@sbendimerad It looks great, thanks so much! And thanks so much for making free and accessible content 🥳
I made two quick changes:

Added a jpg path to your image (apparently web-based images are not displayed correctly)
Removed the Mastodon handle (it was empty and the bot would then post an empty handle next to your name)

I also knit the README.md with your updated entry to make sure that it looks good. If you agree with the changes, let me know and I'll merge them into main ☺

Thanks, everything is ok for me, you can merge :)

Done - thanks again for contributing 🙌


Migrating test/code-coverage from TravisCI to github actions

I'll remove the TravisCI integration once this gets merged.  It runs MUCH faster and does the same job


Typo "/imports:system.globalization"→"-imports:system.globalization"

https://docs.microsoft.com/en-us/dotnet/visual-basic/reference/command-line-compiler/imports
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Duplicate #16517.
Closed #16532.


format実行と依存関係の更新

CI link: https://github.com/UR-deR/praha-github-actions-hands-on/actions/runs/10748444963/job/29812162160


How much solar/grid/battery power?

ac_output_active_power and  ac_output_rating_active_power are very useful for seeing how much power I am using.
Still, these don't tell me anything if this energy comes from the grid, battery or solar? Is there any way to get this data?

As far I read the protocol document, I never seen such information avalable. Once can substract the . ac_output_active_power with the (PV_power + battering_charging) but it won't be super accurate.

Yes on the PIP8048 wtih two strings pv_charging_power is replace with pv1_charging_power etc....
maybe you can use the pip8048 branch to test with your easun.

It may be helpful to note, the voltronic PV power cuts off its input power if the batteries are full or reached your float / bulk voltage setting.  I have perfect sunny day, but you can see from the chart when I reached full charge state the blue line PV input current drops off. The purple is my battery discharge current out.

Looking at PV power curve

If you read the binary sensor     ac_charging_status:   and its status is on, then maybe that can deduce how often the AC is being used.   I use an external energy monitoring plug for the AC in, and AC out of the inverter that I can then do that subtraction independent of the inverter.
Does the Easun app show power with that string variable PV1. . ...? or is it also 0W?

@bogdanr Could you try to use the feature branch:
external_components:
  - source: github://syssi/esphome-pipsolar@pip8048
    refresh: 0s

And update/change your config yaml a bit: https://github.com/syssi/esphome-pipsolar/pull/10/files#diff-dbc81de7d9fb76af6e67b9c8b02f69c8ea7f35b243a2898f26520c759e0d7b6dL122-R145

Wouldn't the answer be in implementing QED QEY and rest of them? This would allow you to see how much PV actually generated and used, and then rest of it was used from the grid....

I shorted my inverter and it took a while to get parts to fix it.
I confirm the changes from branch PIP8048 improve things. I now have a sensor for looking at the solar production (pv1_charging_power).
I can also see a battery_discharge_current sensor but I am missing a sensor which shows charging current.
I suggest you merge this pull request.


Haul does not recognize react-native as a peerDependency

Your Environment
We work in a monorepo that hoists common dependencies up to the root folder with Lerna. This means that react-native itself is not installed in the project folder, but is two levels higher in the filesystem.
Current Behavior
haul init throws an error that it can't find react-native
haul start --platform ios also cannot find react-native and exits
Expected Behavior
Haul should resolve up the file system tree as node/webpack does to find a version of react-native
Haul Configuration (webpack.haul.js)
Minimal config in a test application

software
version

Haul
v0.6.0

react-native
44.0

node
v6.9.1

npm or yarn
npm 3.10.8

A couple ways to fix this up:

Use node-resolve (or similar) to resolve to a react-native install (package here)
Add a react-native-location field to the config file
2.1) haul init prompts the user to enter the location of react-native then writes it to the config

I prefer option one. Any foreseen issues with going in that direction?

Shouldn't require work anyway even if React Native is installed two levels up the directory? All in all, that's how require traverses up the file system.
Have you installed haul globally or locally? Have you tried installing it on the same level as React Native? Does it work then?

Two things that I found
src/commands/init.js: if (pak.dependencies['react-native']) { won't allow peerDependencies but thats a pretty easy fix to swap to if (pak.dependencies['react-native'] || pak.peerDependencies['react-native']) {
then the only other blocker is actually in building the haste map
/src/utils/makeReactNativeConfig.js has the location of react-native hard coded to directories: [path.resolve(root, 'node_modules/react-native')], which may not actually be its final install location. In the case of the repo I'm looking at it ends up being ../../node_modules/react-native but that will vary by how deeply the project is nested in your repo.  The idea would be to use node-resolve or something to find where it really is when that config is built rather than use a relative path.

to add a bit more detail, this is essentially how the directory structure ends up after a lerna bootstrap
main/
   mobile/
      appname/
         webpack.haul.js
         package.json
         index.ios.js
   node_modules/
      haul-cli/
      react/
      react_native/

The idea would be to use node-resolve

This sounds good to me

Fixed in master in #165


Error message: ENOENT: no such file or directory, open 'C:\Users<redacted>\ca.pem'

Hi,
I have this issue with DockerToolbox-1.8.3.exe for Windows 7
I think the problem is that in some parts the VM is referred as "dev" whereas in some other parts (like the real physical path where the VM files are stored, etc) is referred as "default"
What I've done is just regenerate the certificates using the proper VM name and it now works!
Run from the Windows command line:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Program Files\Docker Toolbox>docker-machine regenerate-certs -f dev
Regenerating TLS certificates
Error: Host does not exist: dev

C:\Program Files\Docker Toolbox>docker-machine regenerate-certs -f default
Regenerating TLS certificates

C:\Program Files\Docker Toolbox>

And that will do the trick!

If you had previous versions of Kitematic/VM installed, is possible that errors could've been generated. Moving forward all VM are created with the name of 'default' - It looks like your last command worked and got your up and running. I'll close this for now but feel free to re-open it if the issue happens again.

How long did the command take for you ?
I'm running around 10 minutes with it just sitting at this screen.
C:\Program Files\Docker Toolbox>docker-machine regenerate-certs -f default
Regenerating TLS certificates

@rwatts3 Can you try to run it with some debug info?
docker-machine -D regenerate-certs -f default


CreatingLoadBalancerFailed :timed out waiting for the condition

Hi - I followed https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-app-update and it worked great. I created a static ip and using the RG as MC_RG-TRG01-LAB01-GOPI_gopiAKSCluster_eastus I created a public IP <IP_ADDRESS>.
After updating the load balancer service as below
apiVersion: v1
kind: Service
metadata:
name: azure-vote-front
spec:
type: LoadBalancer
loadBalancerIP: <IP_ADDRESS>
ports:

port: 80
selector:
app: azure-vote-front
Applying the template still keeps the original public IP instead of the static ip.

Name:                     azure-vote-front
Namespace:                default
Labels:                   <none>
Annotations:              kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"azure-vote-front","namespace":"default"},"spec":{"loadBalancerIP":"<IP_ADDRESS>...
Selector:                 app=azure-vote-front
Type:                     LoadBalancer
IP:                       <IP_ADDRESS>
IP:                       <IP_ADDRESS>
LoadBalancer Ingress:     <IP_ADDRESS>
Port:                     <unset>  80/TCP
TargetPort:               80/TCP
NodePort:                 <unset>  30124/TCP
Endpoints:                <IP_ADDRESS>:80
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
Type     Reason                      Age               From                Message

Normal   LoadbalancerIP              18m               service-controller  -> <IP_ADDRESS>
Normal   EnsuringLoadBalancer        3m (x10 over 4h)  service-controller  Ensuring load balancer
Warning  CreatingLoadBalancerFailed  3m (x9 over 18m)  service-controller  Error creating load balancer (will retry): failed to ensure load balancer for service default/azure-vote-front: timed out waiting for the condition

I see this reported else where https://github.com/Azure/AKS/issues/326 not sure if this is a bug.

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

ID: 7179d4ae-db6e-7f7c-a855-db0e0475dae9
Version Independent ID: 1a6fa0e8-e175-ae4d-a9d6-d170255a598e
Content: Use a static IP address with the Azure Kubernetes Service (AKS) load balancer
Content Source: articles/aks/static-ip.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Events:
Type     Reason                      Age               From                Message

Normal   LoadbalancerIP              18m               service-controller  -> <IP_ADDRESS>
Normal   EnsuringLoadBalancer        3m (x10 over 4h)  service-controller  Ensuring load balancer
Warning  CreatingLoadBalancerFailed  3m (x9 over 18m)  service-controller  Error creating load balancer (will retry): failed to ensure load balancer for service default/azure-vote-front: timed out waiting for the condition

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

Thanks.
Just to add, I think the static IP may not have provisioned correctly.
az network public-ip list -g MC_RG-TRG01-LAB01-GOPI_gopiAKSCluster_eastus
For the above command you can see that <IP_ADDRESS> has blank ipConfiguration.

@g0pinath
The most common cause for this error is that Contributor access is missing for the service principal used to create the cluster. Please have a look at this comment.
Are you having this error for only this service or other services also?
are you trying to create a ip first and then assign it to the service?
Whats the version of your cluster?
Generally if you create a service with type LoadBalancer, AKS will create a load balancer and link it with the service.

Please close this thread, it was use error. I changed the service name to azure-load-balancer as listed in the article and no more errors.


fix bug of guessrequester crashing on certain slot ranges

logs:
INFO - Retrying...
INFO - Downloading blocks 290001 to 300000...
INFO - Downloaded 9902 blocks in 42.44 seconds. Found 98 missing blocks.
ERROR - Error while backfilling: list index out of range
ERROR - Max retries reached, aborting
Reindex: False
Traceback (most recent call last):
  File "/app/load_db.py", line 181, in <module>
    main()
  File "/app/load_db.py", line 155, in main
    backfillSlots(last_slot_saved, classifier, model_folder, node_url, add_to_model, db)
  File "/app/load_db.py", line 107, in backfillSlots
    raise e
  File "/app/load_db.py", line 85, in backfillSlots
    loadSlotGuessesDatabase(
  File "/app/load_db.py", line 53, in loadSlotGuessesDatabase
    guesses = getSlotGuesses(
              ^^^^^^^^^^^^^^^
  File "/app/guessRequester.py", line 120, in getSlotGuesses
    slot = block_rewards[block_rewards_index]
           ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
IndexError: list index out of range

Bug seems to occur when there slot range ends with missing slots. Example: https://beaconscan.com/slot/300000


Publish to npm?

Any chance you could publish this module to npm so it could be used with Browserify?

Sorry about the delay!  Package is now up on npm at https://www.npmjs.com/package/angular-progress-arc


Gogogate2 0.1.1

Description:
Update to use latest version of gogogate2 component. Expose device temperature as attribute

## Checklist:
  - [ ] The code change is tested and works locally.
  - [ ] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass**

If user exposed functionality or configuration variables are added/changed:
  - [ ] Documentation added/updated in [home-assistant.github.io](https://github.com/home-assistant/home-assistant.github.io)

Please fix the build error!


Warning: severe limitation of superpose3D

as the author pointed out:
Note: This function does not attempt to determine which pairs of points from either cloud correspond. Instead, it infers them from the order of the arrays. (It assumes that the i'th point from X corresponds to the i'th point from x.)
This assumption does not hold for generic point cloud registration such as atom point clouds of crystals.
If you want to do superpose3d for un-ordered points, you'd better try open3d, which I have spent a lot of effort to make it work.
import open3d as o3d
import numpy as np
source = o3d.geometry.PointCloud()
target = o3d.geometry.PointCloud()
np.random.seed(0)
pointset = np.random.rand(10, 3)
source.points = o3d.utility.Vector3dVector(pointset)  # Random points
Generate target point cloud
target.points = o3d.utility.Vector3dVector(pointset)  # Random points
target.transform([[1, 0, 0, 0.5],
[0, 1, 0., 0.0],
[0, 0.2, 1, 0],
[0, 0, 0, 1]])
Apply ICP registration
threshold = 5
trans_init = np.identity(4)  # Initial transformation matrix
reg_p2p = o3d.pipelines.registration.registration_icp(
source, target, threshold, trans_init,
o3d.pipelines.registration.TransformationEstimationPointToPoint(),
o3d.pipelines.registration.ICPConvergenceCriteria(max_iteration=1000))
print("Transformation matrix:")
print(reg_p2p.transformation)
print("Matching points:")
print(np.asarray(reg_p2p.correspondence_set))
print(f"% of match:{reg_p2p.fitness*100}%")
print(reg_p2p.inlier_rmse)

This is awesome, usccolumbia!  I'll post a link to it on the front page.


Store solutions of the same bonfire in a drop-down or similar.

As of now, all solutions to bonfires are saved to your profile instead of just the most recent one, which is great; it does, however, clutter up your profile, especially if you play around in the same bonfire a lot, adding stuff and testing it over and over. Could solutions to the same bonfire be stored in some sort of openable menu, so that each bonfire only appears on your profile once? Maybe the solutions part of the profile could look like the Map page and clicking the bonfire would show the solutions?

Thanks for the suggestion, this is already mentioned in issue #356. Closing as a duplicate. Please comment in that issue's thread.


VideoStream error on last version

@helzapps
One other issue is in our script we are doing something like so:
    var vs = new VideoStream(
      "./videos/SIRTeX_IllustratedMoGraph_Update_v06_noAudio.mp4"
    );
    if (vs != null) {
      var texture = new VideoTexture(vs);
      ...
    }

The null test worked in version 0.97.14 and would bypass actually trying to create the video texture in our editor running. But now in 0.98.5 and today's 0.98.6 that test is failing in that even though that file isn't local in our test runs, the vs var is not null and it's attempting to create the VideoTexture but then it throws an error (first screen shot in my description). Should this be coded differently or in fact is there a separate bug that should be reported for this issue now? Thanks?

This is a bit weird that vs variable should never be null in any situation.

Can you please show what error you are getting when accessing the VideoStream?

If I console.log out the VS object it is now printing:
vs = {"name":"video","uuid":"3C575387-B7C8-4C17-A261-9A61C6358895","type":"Video","format":"url","encoding":"mp4","data":"./videos/SIRTeX_IllustratedMoGraph_Update_v06_noAudio.mp4"}
It's possible that previously it wasn't null and had this same JSON object, but the data property wasn't null that it's trying to read.

To be clear, the video assets are located in the web project in which we are embedding our nunu scene.

More info:
If I take your Video Tutorial project and attempt to load and run it, then I get this error:

The main difference is you are loading yours in the initialize() function. If I move it into a function like how we are doing it (which I don't know why we are doing it this way...) then I get the same error:
`
var videosLoaded = false;
function initialize()
{
}
function loadVideo()
{
var texture = new VideoTexture(new VideoStream("https://nunustudio.org/learn/basics/17_video/sample.mp4"));
var material = program.getMaterialByName("default");
material.emissiveMap = texture;
material.emissive.setHex(0xFFFFFF);
}
function update(delta)
{
if (!videosLoaded) {
videosLoaded = true;
loadVideo();
}
}
Then I get the same error as in our project where it cannot read property ofdata` of null.

So this error persists in the latest version 0.98.7, but something else wrong or this is still related. I cannot create new video textures. I tried creating a super simple scene with three boxes with planes associated with them. To then created three standard materials as is suggested for dynamically loading a video texture. I then assigned them to the three planes in the project explorer. When I publish for web and run, I get a TON of WebGL errors:
[.WebGL-0x7fdf0400a200]RENDER WARNING: texture bound to texture unit 0 is not renderable. It might be non-power-of-2 or have incompatible texture filtering (maybe)?
WebGL: INVALID_VALUE: tex(Sub)Image2D: video visible size is empty
...

Hello
Thanks a lot for the additional information i think that i have figured out what is wrong with the video texture.
That second render warning should be while rendering with the texture still uploading.
Thanks a lot once. Working on it.

This bug should be fixed now in the version 0.98.8,
Thanks a lot for reporting this issue.

While I no longer get the scripting error from the editor, I am still getting the errors mentioned in this comment: https://github.com/tentone/nunuStudio/issues/420#issuecomment-663749707
Opening a new issue.


Cannot Read Property 'url' of Undefined

react-dom.production.min.js:196 TypeError: Cannot read property 'url' of undefined
at t.value (Playlists.js:212)

I have this too, I'm guessing because I don't have a profile photo. Where it fails:
image={this.state.user.images[0].url ? this.state.user.images[0].url : blank_profile}

Should be fixed! Instead of trying to read the url property from the images array in that conditional, I just see if any urls are there at all - then decide to use profile image or the default fallback in case there is none.

Cool thanks! @NLeRoy917


How is 2 a word?

"two"

I think it's like jpg2png or like "I've sent it 2 u"

Yes, I was right
issue #77


Refactor to avoid not necessary conversion

Signed-off-by: Jose Donizetti<EMAIL_ADDRESS>Minor refactor to avoid the conversion string <-> []byte.
Let me know if you okay with small changes like this. Thanks

Let me know if you okay with small changes like this. Thanks

These changes are great! We love the help.


[Go] actually parse Facebook desktop markup, and unescape '--' properly

Previously we were doing a plain text search for proof text in the
desktop page. That was a little sketchy structurally, but it also ran
into a correctness issue: comments can't contain a "--" character, and
if proofs contained that pair (as it does in a random 1% of our base64
medium sig IDs), we weren't matching it properly.
The simplest possible thing would be to just replace "--" with "--"
before we match. That would probably work. However there's a lot of
basic HTML escaping (like &) that's allowed in this context, so
comparing escaped strings char-by-char is an escaping-flexibility
landmine just waiting to explode and break us again.
Instead of looking for escaped text in the page, we should be
unescaping text and comparing it to our known string. To do that right
we need to properly structurally parse the page instead of blindly
string searching it. That requires a second parse in the middle, which
is a little complicated, but it works, and it feels much safer in the
long term. (Way less likely to get confused by other text that could
sneak into the page.)
r? @maxtaco @mlsteele

👍


Missing parent: group translocation activity

GO term ID and label for which you request a new superclass

GO:0008982 protein-N(PI)-phosphohistidine-sugar phosphotransferase activity
GO:0090563 protein-phosphocysteine-sugar phosphotransferase activity

New superclass (parent) suggested
group translocator activity
or perhaps
group translocation activity

definition
Enables the transfer of a substance from one side of a membrane to the other where the substrate is modified as part of the transport process.

is_a
GO:0022857 transmembrane transporter activity

Reference(s)
PMID:16707683
Example
malP Bacillus subtilis
UniProtKB:P54715

xref
xref TC:4

As part of #27495

Remove is_a active transmembrane transporter activity parent relation for
GO:0008982 protein-N(PI)-phosphohistidine-sugar phosphotransferase activity
GO:0090563 protein-phosphocysteine-sugar phosphotransferase activity

Hi @pgaudet
They could have that as a parent would map to the TC4.A https://tcdb.org/search/result.php?tc=4.A, but that term would ideally have the parent 'group translocator activity' parent to fit with the TC system for TC4 https://tcdb.org/search/result.php?tc=4


changed sysctl modifications via writing to a file

This PR changes the way we interact with sysctl by swapping subshelling to bash with a write to a respective file
Closes #52
Additionally, the same approach is used to add LLDP capability to a linux bridge.

tested locally


Add i18n translation for admin.py

To complete translations, I added _( ... ) around the fieldsets in admin.py.

Changes Unknown when pulling 3d2e8768b53f09016b6056f6d70be4330a243f09 on fsbraun:develop into ** on nephila:develop**.

Current coverage is 92.32% (diff: 100%)

No coverage report found for develop at 999f0bc.

Powered by Codecov. Last update 999f0bc...3d2e876

@fsbraun ouch, what a blunder!

Translation pushed to transifex


A few issues with Iron Storm

In Iron Storm(2005) I'm having 2 main issues. I'm unable to add lights to textures using remix. The textures flash green in game when I hover over them in the remix menu but does nothing when I select the texture. The second issue I think is a result of the first issue where depending on where I'm looking, a random light will appear behind me. I assume this is a back up light being added by remix due to remix not detecting any other lights. Using "In View Transform" seems to change that but also adds a really bad looking motion blur effect that I'm unsure is intended or not. Motion blur is turned off in game and in remix post processing.
In the discord I saw that someone else is having a similar issue with the lighting in Return to Castle Wolfenstein if that is easier to take a look at.
Apologize if any info is missing or if my issues aren't clear. Please let me know if I need to expand on anything
Software information
Iron Storm, settings in video are all on but still occurs when everything is low/off
System information

GPU:RTX 3080 FE
Driver:531.79
DXVK version: 538155a

Log files
d3d9.log
IronStorm_d3d9.log
https://github.com/NVIDIAGameWorks/dxvk-remix/assets/112427434/fa7e23eb-611c-40c4-8d6f-1f47b90a313c

Hi. Typically replacing emissive texture requires authoring of new textures as emissive. Using in-game albedo as emissive is not expected to work very well. Please refer to the Discord community for further help. https://discord.gg/rtxremix


Unable to deploy to BAMI Tenant

Deployment issue with BAMI  based on https://github.com/microsoft/aitour-llmops-with-gen-ai-tools/blob/main/session-delivery-resources/deployment/README.md
@cedricvidal  @revodavid
Issues
User cannot created using azd up services to a BAMI Tenant
Validation of steps
az login --use-device-code --tenant ID
Login correct
azd auth login --tenant id
Login error Error: unknown flag: --tenant
azd auth login
az account show
Show correct tenant and subscription ID
azd config set tenant ID
Set correct tenant
azd up
Only shows subscription in primary @microsoft.com tenant
Solution - FIX
On Codespaces/Linux
export AZURE_SUBSCRIPTION_ID=<your_subscription_id>
export AZURE_TENANT_ID=<your_tenant_id>
On Windows
set AZURE_SUBSCRIPTION_ID=<your_subscription_id>
set AZURE_TENANT_ID=<your_tenant_id>
Then run
azd auth login
Then
azd up
Failure ERROR: listing locations: failed retrieving Azure location for account 'SubID': failed to resolve user 'UserID' access to subscription with ID 'SubID'. If you recently gained access to this subscription, run azd auth login again to reload subscriptions.
Otherwise, visit this subscription in Azure Portal using the browser, then run azd auth login
However running
az Login shows correct tenant and subscription
and running
az account show --query "[name, id, tenantId]"
Shows correct tenant and subscription

Fixed ensure you use
azd auth login --tenant-id 'tenantID' --use-device-code as the command


Add character: Mando/Baby Yoda

Hero Description
Characters from the Mandalorian series
Concept Art

Inspiration
Characters from the Mandalorian series. The character Mando is responsible for taking care of the baby Yoda who has Jedi powers. They are always together and help each other with their independent skills.
The idea is to make them in the game as a pair, in which Yoda drinks follows Mando and helps with skills.
Moves
Idle

[STICK] Walk
I keep walking and baby Yoda is always following him.

[LEFT] Accurate shot/blaster
1º Mando would take his sniper and take a very long shot that would deal damage equivalent to the distance covered. (It would have a laser sight, and shoot at a high speed)
2º Mando would shoot with his laser gun, if he hits the shot, the target would be marked and a missile would come out of the jetpack and hit the target, causing minor damage in the area. Shooting distance would equal midle string.
It will be possible to change left 1 and 2 by pressing Q

Reference:

[MIDDLE] Paralyzing rope
Mando would cast briefly, and a rope would come out of his wrists and wind like a loop causing slowness.
Reference:
[RIGTH] attack_name
Mando raises his arm and activates a flamethrower for x seconds that would have the same action as LOL's Rumble, having more burst and less area damage.
Reference:

[SPACE] Ultimate: attack_name
Baby Yoda gives a channel for x seconds. Elevating everyone around you causing slowness.
Reference:

[E] TAUNT
Taunt is a funny animation you character will do like laugh, dance aiming to make fun of the enemies
### OPTIONAL
[Q] extra skill
Tasks

[x] Idle
[x] Walk
[ ] Hurt
[x] [LEFT] Accurate shot/blaster
[ ] [MIDDLE] add skill name
[ ] [RIGHT] add skill name
[ ] [SPACE] add skill name

Approved by Victor. Waiting for the description of the skills

Approved for work. We are going to update the set of skills with the help of Alexandre

21/02/2020 a 23/02/2020
Modeling Mando and baby Yoda, idle animation, walk, LEFT
16h

24/02/2020 a 26/02/2020
Modeling and animation of RIGHT, MIDDLE, HURT, Ultimate, taunt.
13h

I reviewed the character gameplay


Missing warnings for application deployments and task sequence references

This is all the work of @LeeViewB ❤
In this revision of clean up scripts for ConfigMgr Apps, he adds warnings for deployments and task sequence references. The user is warned and the script aborts if either of these are true. They're advised to remove the associations and deployments, and re-run the script.
It is recommended customers re-deploy or re-associate the applications with their task seqeunce when the applications are remade.
@CodyMathis123 may you resign please?

hold fire @CodyMathis123 , i'll ping again when ready

This should be signed and ready to be merged :)


Cannot explore table storage accounts in 1.2.0

Storage Explorer Version: 1.2.0
Platform/OS Version: Windows
Architecture: ia32
Regression From: Was working in 1.1.0
Steps to Reproduce:
Find some old and very large table storage account and expand it
Expected Experience:
Expecting to see the usual list consisting of blob containers, file shares, queues, and tables, allowing to dig deeper
Actual Experience:
After about two minutes of loading animation, the arrow to expand/collapse the account disappears, nothing else shows up

You're getting gateway timeout errors. Azure Storage was down briefly yesterday (14 Jun). Have you tried again since then?

Just tried and all good, must've been the downtime. I was confused because it only affected my classic accounts. Thanks for the update!


Partiture Show to streamlit app

I add the show of the partiture loaded into the streamlit demo. In particular in the system in which I can test the lib maybe I do not see the Japanese character under the partiture, instead in the system in which I'm not able to install nnsvs correctly I can see the Japanese character, I think that it depends on the language installed, you can try to test on your computer it the text under the partiture is visible.

I'm not be so careful, The music21 seams to work fine on huggingface spaces but not on streamlit demo it seams a problem about where the tmp file are stored into music21 app

I have no idea why it doesn't work for steramlit, but I think using huggingface spaces is okay.
The other problem I found is that lyrics are not property synced with notes when I tried this branch locally. I can see Japanese characters correctly though.


Remove inactive repo owners

The binaries affected:

[x] openstack-cloud-controller-manager
[x] cinder-csi-plugin
[x] k8s-keystone-auth
[x] client-keystone-auth
[x] octavia-ingress-controller
[x] manila-csi-plugin
[x] manila-provisioner
[x] magnum-auto-healer
[x] barbican-kms-plugin

What this PR does / why we need it:
Remove inactive owners
Which issue this PR fixes:
fixes #
Special notes for reviewers:

Release note:

NONE

cc @anguslees @dims @dixudx @FengyunPan2 @flaper87 @hogepodge @NickrenREN @rootfs
Thanks for all your contributions to this repo, and you are welcome to come back one day once the condition changed.

@chrigl @ramineni please let me know your thoughts

/lgtm

Thanks for doing this. Can you remove these guys from reviewers too please ?

I fully support this. Thanks.

I'm listed as a reviewer for this PR.  If I approve it, am I no longer inactive? :thinking:
/lgtm

/approve


CombineMeleeAndRangedWeaponSlots setting is wrong

Introduction is：If true, melee weapons will have their own reserved slot.
But in fact，when CombineMeleeAndRangedWeaponSlots is false,It still exists.
And on the client side, the situation is exactly the opposite. When the host is set to shut down, there still exists on the client side.

Ah, I messed up the wording. It should say: "If set to false, melee and ranged weapons will have their own reserved slots. (two slots instead of one)". Thanks! I'll get this fixed


merging snes-msu into snes

After the merge of both systems I got two Aladdins, two Top Gear 3000. that is not ok. if you want to merge please tag msu games with "[msu-1]" following the name of the game. Otherwise the situation is confusing.

There's an option for that


Check that GGIR version in parallel processes is identical to GGIR version from machine that runs GGIR

In a project I am working on the GGIR version centrally installed by the admin of a computing cluster was different from the user installed GGIR version and when using parallel processing inside GGIR the parallel processes used the centrally GGIR version while the part of GGIR that does not run parallel used the user GGIR version.
Although we could argue that it is the user's responsibility to make sure that the correct GGIR version is available it may help to run a quick check prior to running GGIR in parallel and warn the user if there are any inconsistencies.
Proposal:

Add a short parallel process in GGIR.R prior to all the actual data processing which only compares the GGIR and R versions between central process and the parallel processes.

I have been exploring this today. If we add this chunk of code then all unit tests that do not specify do.parallel = FALSE will run it somehow testthat does not like this causing the test to fail without providing clear error messages that the cause is this additional bit of code.
I think this is too risky as we cannot always remember to turn do.parallel to FALSE inside a unit test. Implementing this inside each part would be a lot extra lines and duplicated testing for the same thing. So, my conclusion for now is that it is better to not do this and leave this up to the responsibility of the suer. They need to ensure that they export they library paths such that their user library is used.
Therefore, I am now closing this issue.


3.0.0 Migration update

3.0.0 Migration update
Updated Circle Ci
Github - update GitHub workflow
Build Gradle - change to Kotlin files
testapp - update testapp name space and name
Deprecated API - remove registerExtension
grade.properties update
Spotless, License header update will be in next PR.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@kevinlind @PravinPK, thanks for the comments, ready to review.


Integrate EarlyBound Generator API

PR for Integrate EarlyBound Generator #378
Added a new useEarlyBoundGeneratorApi flag to allow for using the EBG vs the Spkrl logic.  Mapped all settings of earlyboundtypes except generateStateEnums and GenerateGlobalOptionSets as there are no settings currently for this in the EarlyBoundGenerator.
Updated EarlyBoundTypeConfig to inherit from DLaB.EarlyBoundGeneator.Settings.POCO.ExtensionConfig. This means all settings in the EarlyBoundGenerator will be allowed (except it they are overriden with the current settings of the EarlyBoundTypeConfig. Also added names for the action, and optionSet.
Updated Tests.

Not sure why, but the tests failed for the older logic when generating a file per entity because the entities.cs file wasn't getting deleted.  I don't believe I've done anything to remove any code that deletes those files, so I've left it there.  If I have some how, then let me know and i'll figure out how to add it back I guess.

Here is the update to the documentation:
Wherever you can, it's best practice to use early bound types in your C# code. You can easily get spkl to generate these classes in a way that can be repeatedly run and refreshed when your schema changes.
There are two main options for generating earlybound types, spkl has it's own built in generator, as well as the EarlyBoundGeneratorApi, the same one built for the XrmToolBox.
To use the spkl internal generator your spkl.json would look like:
{
  "earlyboundtypes": [
    {
	  "useEarlyBoundGeneratorApi": false
      "entities": "account,contact,quote",
      "actions": "dev1_simpleaction",
      "generateOptionsetEnums": true,
      "generateStateEnums": true,
      "generateGlobalOptionsets": true,
      "filename": "EarlyBoundTypes.cs",
      "classNamespace": "TestPlugin",
      "serviceContextName": "XrmSvc",
	  "oneTypePerFile": false
    }
  ]
}

useEarlyBoundGeneratorApi - Optional, defaults to false.
entities - Comma seperate list of entity logical names. I've not provided support for -all- entities because this results in unnecessarily large plugins!
actions - Comma separated list of actions request/responses to generate - leave empty or omit for none
generateOptionsetEnums - Set to 'true' to generate Enums for optionsets
generateStateEnums - Set to 'true' to generate Enums for States and Statuses
generateGlobalOptionsets - Set to 'true' to generate Enums for Global optionsets
filename - The path (relative to this file) to output
classNamespace - The namespace to put the classes under
serviceContextName - The name of the Service context to create - leave blank or omit for none
oneTypePerFile - Splits the files into seperate files.

To use the EarlyBoundGeneratorApi your spkl.json would look like:
{
  "earlyboundtypes": [
    {
	  "useEarlyBoundGeneratorApi": true,
      "entities": "account,contact,quote",
      "actions": "dev1_simpleaction",
      "classNamespace": "TestPlugin",

	  // Optional - Recommend only including if needed
	  "generateOptionsetEnums": true,
      "filename": "Entities.cs",
      "actionFilename": "Actions.cs",
      "optionSetFilename": "OptionSets.cs",
	  "serviceContextName": "XrmSvc",
	  "oneTypePerFile": true,
	  "AddDebuggerNonUserCode": true,
	  "AddNewFilesToProject": true,
	  "DeleteFilesFromOutputFolders": false,
	  "EntityAttributeSpecifiedNames": "EntityName1:FirstAttributeNameWithCustomCasing,SecondAttribute|EntityName2:FirstAttributeNameWithCustomCasing,SecondAttribute",
	  "GenerateActionAttributeNameConsts": true,
	  "GenerateAttributeNameConsts": true,
	  "GenerateAnonymousTypeConstructor": true,
	  "GenerateConstructorsSansLogicalName": false,
	  "GenerateEntityRelationships": true,
	  "GenerateEntityTypeCode": false,
	  "GenerateOnlyReferencedOptionSets": true,
	  "GenerateOptionSetMetadataAttribute": true,
	  "InvalidCSharpNamePrefix":"_",
	  "MakeAllFieldsEditable": false,
	  "MakeReadonlyFieldsEditable": false,
	  "MakeResponseActionsEditable": true,
	  "LocalOptionSetFormat": "{0}_{1}",
	  "OptionSetLanguageCodeOverride": 1033,
	  "ProjectNameForEarlyBoundFiles": "MyEarlyboundProject.proj",
	  "PropertyEnumMappings": "EntityName.PropertyName,EnumName|EntityName2.PropertyName,EnumName",
	  "RemoveRuntimeVersionComment": true,
	  "ReplaceOptionSetPropertiesWithEnum": true,
	  "UseTfsToCheckoutFiles": false,
    }
  ]
}

useEarlyBoundGeneratorApi - Required since it defaults to false if not provided.
entities - Comma seperate list of entity logical names. I've not provided support for -all- entities because this results in unnecessarily large plugins!
actions - Comma separated list of actions request/responses to generate - leave empty or omit for none
classNamespace - The namespace to put the classes under
generateOptionsetEnums -  Set to 'false' to not generate Enums for optionsets.  Default is true
filename -  The path (relative to this file) to output of the entities.  Defaults to entities.cs.  If oneTypePreFile is specified, used as the folder name.
actionFilename -  The path (relative to this file) to output of the entities.  Defaults to actions.cs  If oneTypePreFile is specified, used as the folder name.
optionSetFilename -  The path (relative to this file) to output of the entities.  Defaults to optionsets.cs  If oneTypePreFile is specified, used as the folder name.
serviceContextName -  The name of the Service context to create
oneTypePerFile - Splits the files into seperate files.
AddDebuggerNonUserCode - Specifies that the debugger should skip stepping into generated entity files.
AddNewFilesToProject -  Adds newly created files to Project File
AddOptionSetMetadataAttribute -   Adds the OptionSetMetadataAttribute to enums to be able to access enum metadata.  Ensure Generate Option Set Metadata Attribute is true to generate the attribute definition, unless this has been handled in some other manner.
DeleteFilesFromOutputFolders -  Clears all .cs files from output folders prior to file generation.  This helps to remove files that are no longer being generated.  Only used if Create One File Per Action/Entity/OptionSet is true.
EntityAttributeSpecifiedNames -  Formatted as a single string in the format of "EntityName1:firstAttributeName, ... ,lastAttributeName|EntityName2:firstAttributeName, ... ,lastAttributeName|..." Basically split each entity by pipe, use then split by colon, then comma, with the first value being the entityName  Allows for the ability to specify the capitalization of an attribute on an entity
GenerateActionAttributeNameConsts -  Specifies the generation of an Attributes Struct containing logical names for all attributes for the Action
GenerateAttributeNameConsts -  Specifies the generation of an Attributes Struct containing logical names for all attributes for the Entity
GenerateAnonymousTypeConstructor -  Specifies the generation of AnonymousType Constructors for entities
GenerateConstructorsSansLogicalName -  Adds Constructors to each early bound entity class to use constructors available to Microsoft.Xrm.Sdk.Entity
GenerateEntityRelationships -  Specifies the generation of Relationships properties for Entities
GenerateEntityTypeCode -  By default the CrmSvcUtil generates the Entity Type Code, this is considered dangerous and not recommended since it is a system generated value, and not one defined in the solution metadata, changing from environment to environment.
GenerateOnlyReferencedOptionSets -  Specifies that only option sets that are referenced by Entities that are generated.
GenerateOptionSetMetadataAttribute -  Generates an OptionSetMetadataAttribute class used to allow for storing of the metadata of OptionSetValues i.e. display order, name, description, etc.  Only used if Add Option Set Metadata Attribute is true.
InvalidCSharpNamePrefix -  Specifies the Prefix to be used for OptionSets that would normally start with an invalid first character ie "1st"
MakeAllFieldsEditable -  Defines that Entities should be created with all attributes as editable.  Helpful for writing linq statements where those attributes are wanting to be returned in the select.
MakeReadonlyFieldsEditable -  Defines that Entities should be created with editable createdby, createdon, modifiedby, modifiedon, owningbusinessunit, owningteam, and owninguser properties.  Helpful for writing linq statements where those attributes are wanting to be returned in the select
MakeResponseActionsEditable -  Specifies that the properties of Response Actions should be editable.
LocalOptionSetFormat -  Defines the format of Local Option Sets where {0} is the Entity Schema Name, and {1} is the Attribute Schema Name.  The format Specified in the SDK is {0}{1}, but the default is {0}{1}, but used to be prefix{0}_{1}(all lower case)
OptionSetLanguageCodeOverride -  Overrides the default (English:1033) language code used for generating Option Set Value names (the value, not the option set)
ProjectNameForEarlyBoundFiles -  The name of the project to add newly created files to. If not value is provided, the first one found will be used.
PropertyEnumMappings -  Used to manually specify an enum mapping for an OptionSetValue Property on an entity.  Format: EntityName.PropertyName,EnumName|
RemoveRuntimeVersionComment -  Remove the Runtime Version in the header comment
ReplaceOptionSetPropertiesWithEnum -  Used in Conjunction with GenerateEnumProperties.  Allows for replacing the OptionSet properties, rather than duplicating them
UseTfsToCheckoutFiles -  Uses TFS to checkout files.

No matter which generator you use, you can refresh the classes file by calling:
spkl earlybound

This is a great idea. I wonder about a slightly different use case.
Could the earlyboundconfig generated by XrmToolbox be referenced in the config when using Daryls Early Bound generator within spkl?  This gives the benefits of the XrmToolbox configuration screens, whilst the consistent/combined usage within spkl, something like:
"earlyboundtypes": [
{
"useExternalEarlyBoundGeneratorApi": true,
"earlyboundConfigXml":      #
}
I'm not sure if that will introduce tool close a version dependency - e.g. if XrmToolbox logic is updated, but spkl doesn't have a corresponding release using the updated EBG library then the config might not be used.  A thought anyway.

In order to be as compatible with the Spkl framework as possible, I used the config settings from spkl to override the EBG settings.   Where there wasn't a compatible setting, I used the same settings as the EBG.  So it would not be too hard to transfer the settings over manually.  And if you are opening the EBG to generate the config, you might as well just use the EBG to generate your entities.

This is great @daryllabar ! Would you mind to also add possibility of having entities and actions as collection like proposed by me in #353 ? This really matters for big projects with a lot of entities and many people merging spkl.json in parallel and it's super simple to have it as an alternative to single, comma separated string.

The EBG itself supports putting the logical names on new lines, while still being pipe delimited, so if it's essential, you can decide just to use that instead.  Problem is I use the same method as the Spkl framework to get the logical names, so that won't work in your case.  The simplest thing I can think of is to create an override setting that points to an EBG xml file, Instead of the JSON.  Once this PR gets approved, feel free to submit a PR for either approach, it would be rather trival.

Not sure why, but the tests failed for the older logic when generating a file per entity because the entities.cs file wasn't getting deleted. I don't believe I've done anything to remove any code that deletes those files, so I've left it there. If I have some how, then let me know and i'll figure out how to add it back I guess.

This looks like it's because of https://github.com/scottdurow/SparkleXrm/commit/c53631f8ca4773213fdce80b9c1f5cf333933c4c#diff-a3e89ccc902720e9929d5a1f5ef72f68

Sorry, it's been awhile since i looked at this.  I'm guessing you want me to make the older tests pass, and to check out the code that you are calling out as the culprit?

Thanks @daryllabar  - No it's fine - I've got a branch where I'm testing before merging - I've added the delete of entities.cs back in.
@ewingjm - I think the issue here is that the code splitting should split out the context - rather than leaving the original entities.cs in there.

@daryllabar - Not sure why, but the EbgApi version of the unit tests take 10 times longer to run - any idea why?

Not sure.  I do a lot of work with naming of entities that require me to go loop through the generated code multiple times before it's actually written to disk.  Maybe that's it?  Any improvement for tests that don't split the file up into multiple files?

@ewingjm - I think the issue here is that the code splitting should split out the context - rather than leaving the original entities.cs in there.

Ah, yes -  that makes much more sense!

Done some testing this morning:

It is spkl not sprkl 😋
It seems to require the DLaB.EarlyBoundGenerator.Api package to be installed even if not using it for early bound generation
The DLaB.EarlyBoundGenerator.Api needs to be added to the nuspec because it's a dependency of the tasks assembly now.
I've done some tests using a local packaged version of the NuGet package and it seems that even when useEarlyBoundGeneratorApi=false - the DLaB.Xrm.EarlyBoundGenerator.Api package is required

It is spkl not sprkl 😋
Doh!  Do I need to update this?

It seems to require the DLaB.EarlyBoundGenerator.Api package to be installed even if not using it for early bound generation
Yeah, the reason for this is I reference the POCO objects in the DLaB.EarlyBoundGenerator.Api to create the serialization entities, so that is why the package is required.   Did you assume that it would download whatever it needed when you first flipped the flag to use the EBG.API?

The DLaB.EarlyBoundGenerator.Api needs to be added to the nuspec because it's a dependency of the tasks assembly now.
Do I need to update this?

I've done some tests using a local packaged version of the NuGet package and it seems that even when useEarlyBoundGeneratorApi=false - the DLaB.Xrm.EarlyBoundGenerator.Api package is required
This could probably be undone by moving the EBG.Api logic. into a different class so it doesn't attempt to load the assembly.  And again, would you like me to do anything?

I can fix those things.
I've had to make the loading of the crmsvcutil in the spkl version specifically look for the coretools because it always tries to pick up the latest version of the coretools - rather than deploy a version with spkl it's self.
Also - I had to add logic to only set MaskPassword to true if the connection string contains a password - currently the https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/blob/033048492159d7bbd2a5354e3c7f6b01143804c7/DLaB.EarlyBoundGenerator.Logic/Logic.cs#L217 will fail with Index was out of range.

Also - in your PR - you've added a reference to Microsoft.VisualBasic - is that really needed?

I've added an issue on my side for the Mask Password thing.  Thanks for pointing it out.
As far as the VB thing, what's going on?    LOL.  Actually I had to look at the check-ins and no, that is no longer needed.  I do use it in a different project since it will parse CSVs for you really nicely.  I'll remove that dependency, and I can push that out now if it makes a difference to you.

Replaced by https://github.com/scottdurow/SparkleXrm/pull/389


Datepicker: when used inside Modal cannot be displayed

Info
When a date picker is inside a modal, it cannot be clicked on and display the calendar.
Provide Code
<GoAButton onClick={() => setInputModalOpen(true)}>Save and continue</GoAButton>
<GoAModal heading="Address has changed"
  role="dialog"
  open={inputModalOpen}
  actions={
    <GoAButtonGroup alignment="end" mt="l">
      <GoAButton type="secondary" onClick={() => setInputModalOpen(false)}>
        Undo address change
      </GoAButton>
      <GoAButton type="primary" onClick={() => setInputModalOpen(false)}>
        Confirm
      </GoAButton>
    </GoAButtonGroup>
  }
>
  <GoAContainer type="non-interactive" accent="filled" padding="compact" width="full">

Before

123456 78 Ave NW, Edmonton, Alberta

After

881 12 Ave NW, Edmonton, Alberta

  </GoAContainer>
  <GoAFormItem label="Effective date">
    <GoADatePicker onChange={onChangeEffectiveDate} name="effectiveDate" value={effectiveDate} />
  </GoAFormItem>
</GoAModal>

To Reproduce
Click on the date picker
https://jam.dev/c/f205174a-fa51-433d-a507-29dc985b4677
Acceptance Criteria

The Datepicker component works as expected when used inside a Modal component

Closing this issue as it can't be replicated any further


Need to support push notifications

The API for registering a device for push notifications is documented here: https://github.com/hartlco/Icro/issues/5#issuecomment-530878037

Client side implementation is done. Need server certs.

Cert is mostly ready to go. Will be deploying on Tuesday with the M.b 2.0 rollout.

This is done. Woohoo!


Cannot clone using ed25519 key on Windows while the same code and key work fine on Linux

Hi, I can't make the ed25519 keys work when cloning on Windows. All operations other than clone work fine, I've tried pulling, committing + pushing with 100% success rate, but when cloning I get this error:
Error: Git(Error { code: -1, klass: 23, message: "failed to start SSH session: Unable to exchange encryption keys" })

Crate version from Cargo.toml:
git2 = "0.19.0"

I've tried many different things together with converting my keys to PEM as suggested here: #659, unfortunately those are no longer supported.
I looked for any outdated libssh versions in the dependencies, since I've seen a few past comments mentioning updating their dependencies helped solve similar problems, but no luck here.
I've tried using the auth-git2 crate, as well as this code:
let mut repo_builder = git2::build::RepoBuilder::new();
let mut fetch_options = git2::FetchOptions::new();
let mut remote_callbacks = git2::RemoteCallbacks::new();

remote_callbacks.credentials(|_, _, _| {
    let credentials = git2::Cred::ssh_key(
        "git",
        Some(Path::new("HOME_PATH/.ssh/id_ed25519.pub")),
        Path::new("HOME_PATH/.ssh/id_ed25519"),
        None,
    )
    .expect("Could not create credentials object");

    Ok(credentials)
});
fetch_options.remote_callbacks(remote_callbacks);
repo_builder.fetch_options(fetch_options);

let _ = repo_builder.clone(url, &target_path.join("../test"))?;

I even tried copying the keys that worked on my Linux machine, but with no results. (I of course changed the paths on both platforms to the correct ones and made sure there are no mistakes by printing the file contents and comparing with what I expected to see).
All git operations work just fine when I'm using git from CLI.
All of the above failed only on Windows and only when attempting to clone a repo. The same setup works on Linux like a charm.
Any ideas what else I could check? I would really love to make this thing work and I'm happy to provide all the info necessary.

I just tried calling cargo install --git ssh://git@path.to:private/repo.git and got an identical result. To my best knowledge, cargo also uses this crate internally, so it looks like a bug, and not a mistake on my end or an intended behavior. Could be a configuration problem, but I can't quite figure out what could be wrong with my setup. I tried on another Windows machine and the results are identical.
error: failed to clone into: [home dir]\.cargo\git\db\[crate name]-06c804456fc504ca

Caused by:
  network failure seems to have happened
  if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
  https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
  failed to start SSH session: Unable to exchange encryption keys; class=Ssh (23)

I found a workaround
I made both cargo install and cloning work on Windows by using the https://path.to/private/repo.git instead, so I'll be using this approach for now.

Unfortunately I think this is a limitation of the WinCNG backend of libssh2. You can maybe try to set the openssl-on-win32 feature on the ssh2 crate assuming you have an environment capable of using or building openssl.

Thanks, I'll give it a go soon

Ok, I tested the suggested solution and it worked, thank you, @ehuss!
I also learned a valuable lesson that you can enable a feature in a dependency of your dependency as it seems. I'm not using ssh2 directly in my crate, so I was a little skeptical at first.
Since I haven't found any useful info about it, for those having similar problems - the overall solution was to:

Add ssh2 with openssl-on-win32 feature as a dependency[dependencies]
# ...
ssh2 = { version = "0.9.4", features = ["openssl-on-win32"] }

Set up openssl on Windows. I struggled with this setup for a bit, so here is how I made it work

install openssl, e.g. from slproweb.com
clone https://github.com/microsoft/vcpkg and run .\scripts\bootstrap.ps1 -disableMetrics from within the cloned repo
install static openssl libraries using vcpkg: vcpkg install openssl:x64-windows-static (from within the same directory as above, or add vcpkg to your path)
put this root cert: https://curl.se/ca/cacert.pem somewhere in your system e.g. C:/certs/cacert.pem
you can now set up some environment variables, for example in your powershell $profile or just for the current session:

$Env:VCPKG_ROOT = 'C:\path\to\your\vcpkg'
$Env:OPENSSL_NO_VENDOR = 1
$Env:RUSTFLAGS = '-Ctarget-feature=+crt-static'
$Env:SSL_CERT_FILE = 'C:\certs\cacert.pem'

This should be enough of a setup, but I may have had some preexisting dependencies on my system, so your milage may vary.
I decided to make this optional, so I can install my tool by using cargo install --git ... on machines that don't have the whole openssl setup. For example:
In Cargo.toml:
[features]
openssl-on-win32 = ["dep:ssh2"]

[dependencies]
# ...
ssh2 = { version = "0.9.4", optional = true, features = ["openssl-on-win32"] }

Then it can be used by adding --features openssl-on-win32 to cargo build, cargo run or cargo install, etc.
I hope this helps someone in the future.


fix: correctly set organization_id in metal_project data source

The metal_project data source was attempting to read the organization ID for the specified project by looking directly at the organization.id field.  That field is only present on a project when the API request has organization in the include parameter.  Rather than include organization details and make the data source slower, this replicates the logic from the metal_project resource, which uses the organization's href field to get the organization ID.
While I was in this area of the code I also removed some debugging print statements that were merged unintentionally.

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (a60c71f) 44.71% compared to head (628b806) 45.31%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

internal/resources/metal/metal_connection/speed.go
81.25%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #538      +/-   ##
==========================================
+ Coverage   44.71%   45.31%   +0.59%
==========================================
  Files          98       18      -80
  Lines       19888     2006   -17882
==========================================
- Hits         8893      909    -7984
+ Misses      10961     1045    -9916
- Partials       34       52      +18

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


The string can be extended leading to different identifiers

Cool, thanks!
What's the policy for this to reach the master branch?


Handle undefined

Handle these cases: .select('Table', ['*'], {}) .select('Table', ['*'], { a: undefined }) .select('Table', ['*'], undefined).

[ ] tests and linter show no problems (npm t)
[ ] tests are added/updated for bug fixes and new features
[ ] code is properly formatted (npm run fmt)
[ ] description of changes is added in CHANGELOG.md
[ ] update .d.ts typings

It's a good idea to add this in this separate PR, please reopen, describe a principle, how do you want to handle undefined and let's implement this before #172


Week 4 Assignment

Hi Dr. Neumann, I need to get your help in class so that I can figure out what to do for the last step because everything ai did returned a syntax error.  I also have the answers for the review added.  The header is only on pigetty.py because I had heard that we were not supposed to change pigify.py, so the header was excluded.

Good work


Update edge-ie-mode-add-guidance-cookieshare.md

Removed duplicate entries in "To share session cookies from Microsoft Edge to Internet Explorer" list.
Added entry for Win10 1809/Server 2019 in "To share session cookies between Microsoft Edge and Internet Explorer" list.

#sign-off


[AppConfig] Prepare for 1.1.9 February AppConfig patch release

Remove the sdk/appconfiguration/azure-spring-cloud-appconfiguration-config/pom.xml which is empty file while resolving conflict in the base release branch. The spring cloud folder had already move to other place.
Upgrade the azure core, dependency libs to the latest in the master.

Since AppConfig has no beta code, AppConfig should release directly from the master


Using recent PETSc version breaks interface

My current setup is mfem/master in combination with petsc/master. Running the petsc example 1
ex1p -m ../../data/amr-quad.mesh --petscopts rc_ex1p

results in the following error
[0]PETSC ERROR: KSP gmres does not support NATURAL

This is due to the fact that the KSP_TYPE is changed back to KSPGMRES on the call KSPSetFromOptions in the petsc interface in PetscSolver::Customize().
I don't know the reason for this or the correct way to handle it.

Please ignore this issue. My compiler setup used different versions of the petsc library.


owntracks skips updates due to inside regions but its not.

Home Assistant release (hass --version):
44.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
device_tracker/owntracks
Description of problem:
I see:
2017-05-22 18:35:08 DEBUG (MainThread) [homeassistant.components.device_tracker.owntracks] Location update ignored, inside region []
messages on all location updates, even though the new localtions are clearly not within any defined region. Also region[] looks very suspicious to me.
Expected:
Should update the location accordingly
Problem-relevant configuration.yaml entries and steps to reproduce:
my zoness.yaml
- name: MPIP
  latitude: !env_var HA_WORK_LATITUDE
  longitude: !env_var HA_WORK_LONGITUDE
  radius: 350
  icon: mdi:work

- name: Home
  latitude: !env_var HA_LATITUDE
  longitude: !env_var HA_LONGITUDE
  radius: 180
  icon: mdi:home

- name: Scool
  latitude: !env_var HA_SCOOL_LATITUDE
  longitude: !env_var HA_SCOOL_LONGITUDE
  radius: 350
  icon: mdi:school

- name: Mo
  latitude: !env_var HA_MO_LATITUDE
  longitude: !env_var HA_MO_LONGITUDE
  radius: 100

and I have the Zones MPIP and Home as well defined within owntracks as geofencing region. Further, Home is also a beacon region, although this has never worked on Android for me.

+1 I have been having this issue too. It usually occurs when home assistant has been running for 24 hours or more. Restarting home assistant resolves the issue temporarily but it will reoccur again within a few days

yep this restarting behaviour I see to. By the way I use owntracks 1.1.7


RangeError: Maximum call stack size exceeded with force:source:manifest:create command

Summary
force:source:manifest:create command is failing to generate package.xml and showing the below error.
{
"status": 1,
"name": "RangeError",
"message": "Maximum call stack size exceeded",
"exitCode": 1,
"commandName": "create",
"stack": "RangeError: Maximum call stack size exceeded\n    at MetadataResolver.getComponentsFromPathRecursive (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\resolve\metadataResolver.js:102:24)\n    at MetadataResolver.getComponentsFromPathRecursive (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\resolve\metadataResolver.js:102:37)\n    at MetadataResolver.getComponentsFromPathRecursive (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\resolve\metadataResolver.js:102:37)\n    at MetadataResolver.getComponentsFromPath (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\resolve\metadataResolver.js:49:25)\n    at buildComponents (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\collections\componentSet.js:73:50)\n    at Function.fromSource (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\collections\componentSet.js:78:9)\n    at Function.build (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\source-deploy-retrieve\lib\src\collections\componentSetBuilder.js:39:59)\n    at createManifest (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\plugin-source\lib\commands\force\source\manifest\create.js:51:81)\n    at create.run (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\plugin-source\lib\commands\force\source\manifest\create.js:32:20)\n    at create._run (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\command\lib\sfdxCommand.js:81:51)\nOuter stack:\n    at Function.wrap (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\core\lib\sfdxError.js:171:27)\n    at create.catch (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\command\lib\sfdxCommand.js:248:67)\n    at async create._run (C:\Users\xxxx\AppData\Local\sfdx\node_modules\@salesforce\command\lib\sfdxCommand.js:85:13)\n    at async Config.runCommand (C:\Program Files\sfdx\client\node_modules\@oclif\config\lib\config.js:173:24)\n    at async SfdxMain.run (C:\Program Files\sfdx\client\node_modules\@oclif\command\lib\main.js:27:9)\n    at async SfdxMain._run (C:\Program Files\sfdx\client\node_modules\@oclif\command\lib\command.js:43:20)\n    at async Object.run (C:\Program Files\sfdx\client\dist\cli.js:162:47)",
"warnings": []
}
System Information
{
"cliVersion": "sfdx-cli/7.135.0",
"architecture": "win32-x64",
"nodeVersion": "node-v16.13.2",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"alias 1.2.0 (core)",
"apex 0.7.0 (core)",
"auth 1.8.1",
"config 1.3.23",
"custom-metadata 1.0.12 (core)",
"data 0.6.8 (core)",
"generator 1.2.1 (core)",
"info 1.2.0 (core)",
"limits 1.3.0 (core)",
"org 1.11.2",
"salesforce-alm 53.7.5 (core)",
"schema 1.1.0 (core)",
"sfdx-cli 7.135.0 (core)",
"sfdx-codescan-plugin 1.0.7",
"source 1.8.20",
"telemetry 1.4.0 (core)",
"templates 53.1.0 (core)",
"trust 1.1.0 (core)",
"user 1.7.0 (core)"
],
"osVersion": "Windows_NT 10.0.19044"
}

Hi, can you provide us with an org that causes this error to repro or include the instructions to reproduce ?

This is happening on our production source and unfortunately, I can't share you the source details. But this is happening when we have multiple metadata(more than 3L files including all metadata types) in a package directory.

hi @ar-srinivas, it seems like some of your plugins are pinned to specific versions (org, source, auth, config) is there a reason for that? I would suggest running sfdx plugins:uninstall <plugin> for those plugins and trying again. You're missing the latest fixes to all of those plugins

I had the correct versions and as part of debugging this issue, I tried updating the individual plugins.
Here is the original plugin versions with the 7.134 version
{
"cliVersion": "sfdx-cli/7.134.0",
"architecture": "linux-x64",
"nodeVersion": "node-v16.13.2",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"alias 1.2.0 (core)",
"apex 0.7.0 (core)",
"auth 1.4.3 (1.4.3)",
"config 1.3.14 (core)",
"custom-metadata 1.0.12 (core)",
"data 0.6.8 (core)",
"generator 1.2.1 (core)",
"info 1.2.0 (core)",
"limits 1.3.0 (core)",
"org 1.11.0 (core)",
"salesforce-alm 53.7.2 (core)",
"schema 1.1.0 (core)",
"sfdx-cli 7.134.0 (core)",
"source 1.8.0 (core)",
"telemetry 1.4.0 (core)",
"templates 53.1.0 (core)",
"trust 1.1.0 (core)",
"user 1.7.0 (core)"
],
"osVersion": "Linux 5.4.0-1060-aws"
}

Ok, that makes sense.

Did this issue just start happening for you? When was the last time it succeeded?
Are you able to source:deploy whichever directory/file path you're trying to create a manifest from?
Is this in a very large project? Or one with a complex structure?

it's stemming from here and I'm trying to understand what's causing it to happen for you. That method hasn't changed in quite a while

The issue is occurring on different machines for the same and even other huge source. It started as soon as I upgrade to this specific version and start using this command.
I didn't try the source:deploy as I don't have the package.xml for the whole source.
It's  a large and even complete structure

Even if I split the source into multiple package directories, I am ending up with the same issue.

Thank you.
if you're able to share the project that is causing this issue that'll be hugely helpful in reproducing the error. But I'll be looking into this

Thank you @WillieRuemmele for your response.
Since it is our production metadata, I can' share you. But in size the metadata is around 3GB...
We are also facing another issue with the same command where it keeps running for more than 30-40 mins in case where we have the metadata of size 3.5GB. Just to complete this command and generate package manifest it is consuming high CPU and running for more than 40 mins. Does this tested with such high source systems and is there any fix for such issues in later releases. We are on 7.134 version as mentioned above.

@ar-srinivas I still don't know how to reproduce this.  I'm gonna ask some questions that might seem strange, but relate to known things that have caused trouble in the past.  We can fill up a repo with thousands of apex classes and not have problems.  So it's not just the size that's the problem.
Can you describe your customLabels?  How many labels have you got, in how many different files?
Can you describe your zipped staticResources?  How many files and how large are the total size of each resource?  Are there lots of nested folders in there?
Are there any symbolic links anywhere?
Is this still a problem on a current CLI (7.159 or 7.160)?

@ar-srinivas please open a new case with repro steps if you can still see this happening.  We've made quite a few changes on the problem types I mentioned, so I'm cautiously optimistic it may have helped yours