Ubuntu-18.04-Missing-Resource-Invalid-block-definition

Seems to be an issue with some of the terraform files when doing a validate.
Ubuntu-18.04
Terraform v0.12.9
azure-cli                         2.0.73
The resource Type and Name are missing been surrounded by ""
Azure Automation accounts - Multiple

Error: Missing name for resource

azurerm_automation_account
All resource blocks must have 2 labels (type, name).

Error: Invalid block definition

azurerm_automation_account
Either a quoted string block label or an opening brace ("{") is expected here.

azurerm_log_analytics_solution - Multiple

Error: Missing name for resource

azurerm_log_analytics_solution
All resource blocks must have 2 labels (type, name).

Error: Invalid block definition

azurerm_log_analytics_solution
Either a quoted string block label or an opening brace ("{") is expected here.

azurerm_managed_disk - Multiple

Error: Missing name for resource
-azurerm_managed_disk

All resource blocks must have 2 labels (type, name).

Error: Invalid block definition

azurerm_managed_disk
Either a quoted string block label or an opening brace ("{") is expected here.

azurerm_network_interface - Multiple

Error: Missing name for resource
-azurerm_network_interface

All resource blocks must have 2 labels (type, name).

Error: Invalid block definition

azurerm_network_interface
Either a quoted string block label or an opening brace ("{") is expected here.

Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Invalid resource name
Error: Invalid resource name
Error: Invalid resource name
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Invalid resource name
Error: Invalid resource name
Error: Invalid resource name
Error: Invalid resource name
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error with terraform init

Hi,
Could you post some of the debug output please using:
./az2tf.sh -s yoursub -r automation_account -v yes -d yes
This will help me see what's going on in your case.

Please see below
python2.7 ../../scripts/az2tf.py -s 9acaa416-e542-46e1-855d-e207e2582998 -r automation_account -d yes 2>&1 | tee -a import.log
resource filter=automation_account
Debug=True
Get Access Token from CLI
Subscription: 9acaa416-e542-46e1-855d-e207e2582998
Found subscription 9acaa416-e542-46e1-855d-e207e2582998 proceeding ...
azurerm_automation_account 8
{
"name": "Automation",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/Automation",
"location": "westeurope",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-03-07T13:57:33.25+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__Automation {
name = "Automation"
location = "westeurope"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "Automation2",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/Automation2",
"location": "West Europe",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-04-05T12:56:29.12+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__Automation2 {
name = "Automation2"
location = "West Europe"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "Automation3",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/Automation3",
"location": "West Europe",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-04-05T12:57:47.927+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__Automation3 {
name = "Automation3"
location = "West Europe"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "Automation4",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/Automation4",
"location": "West Europe",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-04-05T13:03:31.457+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__Automation4 {
name = "Automation4"
location = "West Europe"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "Automation5",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/Automation5",
"location": "West Europe",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-04-05T13:10:29.907+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__Automation5 {
name = "Automation5"
location = "West Europe"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "automation-NM",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/automation-NM",
"location": "westeurope",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-04-08T21:37:02.69+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__automation-NM {
name = "automation-NM"
location = "westeurope"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
{
"name": "Kickstart",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/Kickstart/providers/Microsoft.Automation/automationAccounts/Kickstart",
"location": "westeurope",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:45.853+00:00",
"creationTime": "2019-05-01T13:03:55+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account kickstart__Kickstart {
name = "Kickstart"
location = "westeurope"
resource_group_name = "Kickstart"
sku_name = "Basic"
tags = {
}
}
{
"name": "efewfefe",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Automation/automationAccounts/efewfefe",
"location": "uksouth",
"type": "Microsoft.Automation/AutomationAccounts",
"properties": {
"lastModifiedTime": "2019-07-23T01:33:46.57+00:00",
"creationTime": "2019-04-05T13:29:24.96+00:00"
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_automation_account 123__efewfefe {
name = "efewfefe"
location = "uksouth"
resource_group_name = "123"
sku_name = "Basic"
tags = {
}
}
terraform init
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
Error: Missing name for resource
on azurerm_automation_account.123__Automation.tf line 2:
2: resource azurerm_automation_account 123__Automation {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__Automation.tf line 2:
2: resource azurerm_automation_account 123__Automation {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__Automation2.tf line 2:
2: resource azurerm_automation_account 123__Automation2 {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__Automation2.tf line 2:
2: resource azurerm_automation_account 123__Automation2 {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__Automation3.tf line 2:
2: resource azurerm_automation_account 123__Automation3 {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__Automation3.tf line 2:
2: resource azurerm_automation_account 123__Automation3 {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__Automation4.tf line 2:
2: resource azurerm_automation_account 123__Automation4 {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__Automation4.tf line 2:
2: resource azurerm_automation_account 123__Automation4 {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__Automation5.tf line 2:
2: resource azurerm_automation_account 123__Automation5 {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__Automation5.tf line 2:
2: resource azurerm_automation_account 123__Automation5 {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__automation-NM.tf line 2:
2: resource azurerm_automation_account 123__automation-NM {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__automation-NM.tf line 2:
2: resource azurerm_automation_account 123__automation-NM {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
on azurerm_automation_account.123__efewfefe.tf line 2:
2: resource azurerm_automation_account 123__efewfefe {
All resource blocks must have 2 labels (type, name).
Error: Invalid block definition
on azurerm_automation_account.123__efewfefe.tf line 2:
2: resource azurerm_automation_account 123__efewfefe {
Either a quoted string block label or an opening brace ("{") is expected here.
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error: Missing name for resource
Error: Invalid block definition
Error with terraform init

This seems to be down to your resource group name starting with a number
That resource group name is used as part of the terraform resource name   eg "123__efewfefe"
And terraform doesn't seem to like the resource name beginning with a number
If I change it so it starts with a letter:
resource azurerm_automation_account r123__efewfefe {
It validates ok.
I'll have to check the terraform docs to see it this is a bug or expected behaviour for resource names.

started posting fixes for this - I have to change every provider. But I started with the ones you are seeing errors on.

should be in better shape for you now. Let me know how you get on

This looks loads better, ran a fuller lookup. If I only have numbers, these resource groups still fail. These are testing resource groups, so I would not normally deploy them like this.
I am seeing issues with an interpolation expression
terraform init
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
Error: Extra characters after interpolation expression
on azurerm_network_interface.rg_123__test01938.tf line 8, in resource "azurerm_network_interface" "rg_123__test01938":
8:    network_security_group_id = "${azurerm_network_security_group.123__test01-nsg.id}"
Expected a closing brace to end the interpolation expression, but found extra
characters.
Error: Extra characters after interpolation expression
{
"name": "test01938",
"tags": {},
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Network/networkInterfaces/test01938",
"etag": "W/"8059d985-bf1b-44f8-a8bf-c6ee83bd23bc"",
"location": "ukwest",
"type": "Microsoft.Network/networkInterfaces",
"properties": {
"provisioningState": "Succeeded",
"dnsSettings": {
"dnsServers": [],
"appliedDnsServers": []
},
"networkSecurityGroup": {
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Network/networkSecurityGroups/test01-nsg"
},
"resourceGuid": "41e04110-bf30-4db9-8522-2210951ed9df",
"enableIPForwarding": false,
"ipConfigurations": [
{
"properties": {
"subnet": {
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Network/virtualNetworks/123-vnet/subnets/default"
},
"primary": true,
"privateIPAddressVersion": "IPv4",
"publicIPAddress": {
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Network/publicIPAddresses/test01-ip"
},
"privateIPAllocationMethod": "Dynamic",
"privateIPAddress": "<IP_ADDRESS>",
"provisioningState": "Succeeded"
},
"etag": "W/"8059d985-bf1b-44f8-a8bf-c6ee83bd23bc"",
"type": "Microsoft.Network/networkInterfaces/ipConfigurations",
"name": "ipconfig1",
"id": "/subscriptions/9acaa416-e542-46e1-855d-e207e2582998/resourceGroups/123/providers/Microsoft.Network/networkInterfaces/test01938/ipConfigurations/ipconfig1"
}
],
"enableAcceleratedNetworking": false
}
}
File generated by py-az2tf see: https://github.com/andyt530/py-az2tf
resource azurerm_network_interface rg_123__test01938 {
name = "test01938"
location = "ukwest"
resource_group_name = "123"
enable_ip_forwarding = false
enable_accelerated_networking  = false
network_security_group_id = "${azurerm_network_security_group.123__test01-nsg.id}"
ip_configuration {
name = "ipconfig1"
subnet_id = "${azurerm_subnet.123__default.id}"
private_ip_address_allocation = "Dynamic"
public_ip_address_id = "${azurerm_public_ip.123__test01-ip.id}"
primary = true
}
tags = {
}
}

working on fixes for that .....

posted up some fixes - please give it another go - will test more thoroughly later.

Thanks, tested and just the expected warnings for NSG and route association. I will test this across some other subscriptions and let you know If I find anything else.

Tested this on 6 other subs no other issues found


Humbug doesn't properly kill mutations that run into timeout

My humbug run reports nine timeouts - and after finishing the run, I have nine processes "php5" on my machine running forever and eating significant amounts of CPU.
I'd expect humbug to kill these endless loops. :)
I currently use commit a3e6269 for this.

It seems like there is some messy situation with Symfony\Process not correctly detecting the real process ID and/or not correctly killing child processes. Please see http://symfony.com/doc/current/components/process.html#process-signals for some pointers to issue tickets explaining the situation.

Reopening the issue, primarily because the fix is currently scoped only to non-Windows environments. Will need feedback on whether the fix is Windows compatible, or if the problem persists there also before closing it off.


release: fitsio v0.21.2

This is a release PR for version 0.21.2.
Use a merge commit.
To trigger builds initially, close and then immediately re-open this PR once.

Coverage: 77.602%. Remained the same when pulling 62d987d484bd140815541900642afc477d97b9c4 on release/fitsio/0.21.2 into f2b8cb31dd82e62ad9a589eb07b231ba8d64dfaf on main.


Addon causes radio input controls to lose their selection

Visit a Storybook with the addon enabled, e.g: https://daimresearch.github.io/sb-addon-permutation-table
Pick a Story with controls, e.g: Example > NestedComponent > Primary
Select a radio option, e.g: "small"
Switch back and forth between options

The option will change (as is evidenced by the URL changing) but the radio option itself will "flash" and lose selection. The issue appears to impact all stories once the addon is installed. The issue does not appear to impact the function of the Storybook controls -- the options still apply -- so this is not a breaking issue, more so it's just a bit confusing.

Thanks!

I will check this with #28 Thanks for reporting this!

@shrink omg I fixed this in #26. but I didn't apply the updated version of addon in our deploy site.... I totally forgot it. We'll update it right away, sorry!

@shrink We fixed this 😉 In v.1.0.2, you won't find this inconvenience


cannot find package "github.com/google/go-github/v29/github"

Describe the bug
we have cicd simple stage to execute gitleak :
.gitleaks:
  stage: validate
  image: golang
  script:
    - echo "Scanning Git repository for leaking secrets"
    - go get -u github.com/zricethezav/gitleaks
    - gitleaks --repo-path="$PWD" --verbose $GITLEAKS_OPTS

To Reproduce
This stage was working well for a while, but recently we are facing the following issue
 $ go get -u github.com/zricethezav/gitleaks
 package github.com/google/go-github/v29/github: cannot find package "github.com/google/go-github/v29/github" in any of:
 	/usr/local/go/src/github.com/google/go-github/v29/github (from $GOROOT)
 	/go/src/github.com/google/go-github/v29/github (from $GOPATH)
 ERROR: Job failed: exit code 1

Screenshots
If applicable, add screenshots to help explain your problem.

Basic Info (please complete the following information):

GitLab Community Edition 12.8.8

cc @zricethezav

I was able to workaround this in our CI environment with export GO111MODULE=on; while manually testing installs as root.
However, to get it to work in our automation for Ansible/Jenkins, the following was the magic incantation (for running under jenkins user):
shell: sudo su -c "export GO111MODULE=on; go get github.com/zricethezav/gitleaks" -s /bin/bash jenkins

@tomi-roam your workaround works well, thanks
sage used on our side become:
.gitleaks:
  stage: validate
  image: golang
  script:
    - echo "Scanning Git repository for leaking secrets"
    - export GO111MODULE=on;
    - go get github.com/zricethezav/gitleaks
    - gitleaks --repo-path=\"$PWD\" --verbose $GITLEAKS_OPTS

@boly38 @tomi-roam I just merged a PR that bumps the go-github version to v31.
does
go get -u github.com/zricethezav/gitleaks

work for you now?

thank you @zricethezav I will tell you that on monday 👍

Hi @zricethezav ,
I test it again and here are my tests results as today:
.gitleaks:
  stage: validate
  image: golang:1.14.2-alpine3.11
  script:
    - echo "Scanning Git repository for leaking secrets"
    - export GO111MODULE=on;
    - go get -u github.com/zricethezav/gitleaks
    - gitleaks --repo-path=\"$PWD\" --verbose $GITLEAKS_OPTS

with export GO111MODULE=on; : go get downloads deps and gitleaks execution ok - I'll keep this state for now

without export GO111MODULE=on; line :

 $ go get -u github.com/zricethezav/gitleaks
 go: missing Git command. See https://golang.org/s/gogetcmd
 package github.com/zricethezav/gitleaks: exec: "git": executable file not found in $PATH

with image: golang (solved with image sha256:2421885b04daf2f5095c46fe1889887d89e5ab77157e54423d97ea6816db54b6) && without export GO111MODULE=on; line :

 $ go get -u github.com/zricethezav/gitleaks
 package github.com/go-git/go-billy/osfs: code in directory /go/src/github.com/go-git/go-billy/osfs expects import "github.com/go-git/go-billy/v5/osfs"
>Running after_script
Uploading artifacts for failed job
> ERROR: Job failed: exit code 1

(I've no more details this this last one, took a little time after osfs line log)

Is this still an issue? @boly38 @tomi-roam

my side, a working way is enough to close it, then I'll let you manage this issue state. Thanks 👍

@ zricethezav It's still failing for me based on a quick test without the workaround. Some details below:
Ansible playbook steps
- name: As jenkins user - go get -u github.com/zricethezav/gitleaks
  shell: sudo su -c "go get -u github.com/zricethezav/gitleaks" -s /bin/bash jenkins

Build failure*
13:00:57      amazon-ebs: TASK [jenkins-worker : As jenkins user - go get -u github.com/zricethezav/gitleaks] ***
13:01:24      amazon-ebs: fatal: [jenkins_worker]: FAILED! => {"changed": true, "cmd": "sudo su -c \"go get -u github.com/zricethezav/gitleaks\" -s /bin/bash jenkins", "delta": "0:00:25.323057", "end": "2020-06-02 18:01:22.134342", "msg": "non-zero return code", "rc": 1, "start": "2020-06-02 18:00:56.811285", "stderr": "package github.com/go-git/go-billy/osfs: code in directory /home/jenkins/go/src/github.com/go-git/go-billy/osfs expects import \"github.com/go-git/go-billy/v5/osfs\"\npackage github.com/google/go-github/v31/github: cannot find package \"github.com/google/go-github/v31/github\" in any of:\n\t/usr/lib/go-1.13/src/github.com/google/go-github/v31/github (from $GOROOT)\n\t/home/jenkins/go/src/github.com/google/go-github/v31/github (from $GOPATH)", "stderr_lines": ["package github.com/go-git/go-billy/osfs: code in directory /home/jenkins/go/src/github.com/go-git/go-billy/osfs expects import \"github.com/go-git/go-billy/v5/osfs\"", "package github.com/google/go-github/v31/github: cannot find package \"github.com/google/go-github/v31/github\" in any of:", "\t/usr/lib/go-1.13/src/github.com/google/go-github/v31/github (from $GOROOT)", "\t/home/jenkins/go/src/github.com/google/go-github/v31/github (from $GOPATH)"], "stdout": "", "stdout_lines": []}

And with that cleaned out a bit the error is:
package github.com/go-git/go-billy/osfs: code in directory /home/jenkins/go/src/github.com/go-git/go-billy/osfs expects import \"github.com/go-git/go-billy/v5/osfs
Going to try a few more things and will update separately if I find anything useful.

go get -u github.com/zricethezav/gitleaks
package github.com/google/go-github/v29/github: cannot find package "github.com/google/go-github/v29/github" in any of:
/usr/local/go/src/github.com/google/go-github/v29/github (from $GOROOT)
/go/src/github.com/google/go-github/v29/github (from $GOPATH)
ERROR: Job failed: exit code 1
how to resolved this error.
thanks

@tomi-roam @Ndh-31 can you try the solution presented here https://github.com/zricethezav/gitleaks/issues/405#issuecomment-653691458 please and let me know if this issue can be closed out.

@tomi-roam @Ndh-31 can you try the solution presented here #405 (comment) please and let me know if this issue can be closed out.

Just ran a successful build with that suggestion, so should be good to close with that.


RuntimeError

Traceback (most recent call last):
File "train.py", line 907, in
main()
File "train.py", line 97, in main
main_worker(args.train_gpu, args.ngpus_per_node, args)
File "train.py", line 415, in main_worker
loss_train, mIoU_train, mAcc_train, allAcc_train = train(train_loader, model, criterion, optimizer, epoch, scaler, scheduler, gpu)
File "train.py", line 519, in train
scaler.scale(loss).backward()
File "/home/vrlabhlbs/anaconda3/envs/spheretest/lib/python3.7/site-packages/torch/tensor.py", line 245, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "/home/vrlabhlbs/anaconda3/envs/spheretest/lib/python3.7/site-packages/torch/autograd/init.py", line 147, in backward
allow_unreachable=True, accumulate_grad=True)  # allow_unreachable flag
RuntimeError: transform: failed to synchronize: cudaErrorAssert: device-side assert triggered

I have got the same error

Hi, I have got the same error. Have you guys solved it already?


gfortran in Ubuntu images broken because of added -gdwarf-5 flag

Description
Today all Ubuntu jobs in the SciPy CI on Azure DevOps started breaking because gfortran is no longer able to compile anything. The way this shows up is:
as: unrecognized option '--gdwarf-5'
/home/linuxbrew/.linuxbrew/bin/gfortran -Wall -g -ffixed-form -fno-second-underscore -Wall -g -fno-second-underscore -fPIC

We are not installing Linuxbrew explicitly, nor are adding a -gdwarf-5 flag. This is likely to be a mixup in GCC specs caused by gh-6258.
See https://github.com/scipy/scipy/issues/17058 for more details on the SciPy build failures in CI.
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions

Runner images affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
I'll note that the Ubuntu 22.04 image should also be affected, however we don't have any CI jobs using that image so I can't be sure that it is affected.
Images affected:
Image: ubuntu-20.04
Version: 20220919.1

Image: ubuntu-18.04
Version: 20220919.2

Is it regression?
Yes. The problem started about 6 hours ago. The previous image was 20220905.1, that worked fine.
Expected behavior
gfortran should not be passed a flag -gdwarf-5, and compiling Fortran code with gfortran should work.
Actual behavior
See issue description.
Repro steps
Here is a CI job that fails: https://github.com/scipy/scipy/blob/main/azure-pipelines.yml#L58.
Compiling any Fortran code with gfortran -g should reproduce the issue.

Hey @rgommers.
We will take a look at it.

Ubuntu 22.04 should not be affected as Homebrew does not need to install newer gcc there.

gfortran symlink removed, changes will be released this week.

Thanks @mikhailkoliada! It looks like in the meantime the default image got reverted to an older build, so our CI is working again.

homebrew has been removed from $PATH so it will not affect you anymore (though we still remove gfortran symlink too, so if you add homebrew back to PATH it should work too).


Accesing an element of an array at the same time it is defined fails

this fails :
imm x = [1, 2, 6][2]

Fixed.


gnu(5488)=668

gnu(5488)=668
GAP      4.8.3
GrpConst 2.5
Runtime: 166889 ms (2.77 min)
Isomorphic groups eliminated
In case this value is new, add the next line to data/gnudata.g
GNU_SAVE( 5488, 668, WITH_GC );

gap>
System : Windows Vista

Thank you for submitting new gnu(n). We will recalculate it and add to the database if we get the same result.
Checklist for the reviewer:

[ ] checked and assigned labels "new (n<50000)" or "recomputation", if needed
[ ] set "replication needed" label (unless it starts immediately)
[ ] changed it to "replication in progress" label when the replication has been started
[ ] changed it to "replicated" after successful replication review
[ ] reproducible value of gnu(n)
[ ] no essential runtime differences
[ ] sufficient level of technical details

Checklist for the maintainer:

[ ] correct arguments of command to store data
[ ] correct location of new line in the data file
[ ] mention submitter and reviewer in the commit message
[ ] Close corresponding issue from the commit message

gnu(5488)=668
GAP      4.8.3
GrpConst 2.5
Runtime: 101915 ms (1.68 min)
Isomorphic groups eliminated
Replicated by @alex-konovalov on Ubuntu 16.04 on Azure cloud standard DS13 v2 instance (8 cores, 56 GB memory)
To maintainers: for new results, add to data/gnudata.g this line:
GNU_SAVE( 5488, 668, WITH_GC );


Rename CODE_OF_CONDUCT.md to links.naturalhealthcity.net

Store

This Mancunian is trying to change the md file's name to a web store in which this person is likely affiliated with. Please reject.


404 - Page not found Errors

All of the links in this page are giving 404 - Page not found errors

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

ID: 9518823a-7a0f-b8c5-20cf-5f0235ee0a19
Version Independent ID: be59ee76-39d4-e905-dc5e-9a7b0dba6f87
Content: Azure Monitor docs: What's new for April 2021 - Azure Monitor
Content Source: articles/azure-monitor/whats-new.md
Service: azure-monitor
Sub-service: general
GitHub Login: @bwren
Microsoft Alias: bwren

@thepaulmacca Thanks for your valuable feedback. We will update the document soon.

@thepaulmacca Thanks for bringing it to our notice. PR has been raised by content author to fix the changes and it will be live soon.
We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


SQL Tools Service - Database Connection Error

Issue Type: Bug
When I connect to my Azure SQL databases using Data Studio, I get the following error the first time I connect. Happens on three separate databases across two VMs. First instance of this error was immediately after last Data Studio update, and has been constant since then. The output window shows this happening to the SQL Tools Service.
[Error - 7:10:43 AM] Request connection/listdatabases failed.
Message: Microsoft.Data.SqlClient.SqlException (0x80131904): Login failed for user ''.
at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)    at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)    at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)    at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)    at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)    at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)    at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry, SqlConnectionOverrides overrides)    at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)    at Microsoft.Data.SqlClient.SqlConnection.Open()    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<Open>b__29_0() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 286    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.RetryPolicy.<>c__DisplayClass25_0.<ExecuteAction>b__0(RetryState _) in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/RetryPolicy.cs:line 128    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.RetryPolicy.<>c__DisplayClass26_0.<ExecuteAction>b__0(RetryState retryState) in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/RetryPolicy.cs:line 141    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.RetryPolicy.ExecuteAction[R](Func2 func, Nullable1 token) in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/RetryPolicy.cs:line 179    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.RetryPolicy.ExecuteAction(Action1 action, Nullable1 token) in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/RetryPolicy.cs:line 138    at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.RetryPolicy.ExecuteAction(Action action, Nullable1 token) in //src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/RetryPolicy.cs:line 127
at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.Open() in //src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 282
at Microsoft.SqlTools.ServiceLayer.Connection.ListDatabaseRequestHandler`1.HandleRequest(ISqlConnectionFactory connectionFactory, ConnectionInfo connectionInfo) in D:\a_work\1\s\src\Microsoft.SqlTools.ServiceLayer\Connection\ListDatabaseRequestHandler.cs:line 71
at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.ListDatabases(ListDatabasesParams listDatabasesParams) in D:\a_work\1\s\src\Microsoft.SqlTools.ServiceLayer\Connection\ConnectionService.cs:line 1058
at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.<>c__DisplayClass78_0.<b__0>d.MoveNext() in D:\a_work\1\s\src\Microsoft.SqlTools.ServiceLayer\Connection\ConnectionService.cs:line 1250
ClientConnectionId:52e96711-6d80-4ae5-bf87-34d6180767e1
Error Number:18456,State:1,Class:14
Code: 0
Azure Data Studio version: azuredatastudio 1.41.1 (33dce95b152227c4f10f6251ab30690fe9895c0c, 2023-01-28T00:46:39.274Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
63.73GB (48.76GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

admin-pack
Mic
0.0.2

admin-tool-ext-win
Mic
0.1.2

agent
Mic
0.49.0

dacpac
Mic
1.12.0

import
Mic
1.5.4

machine-learning
Mic
0.12.0

powershell
ms-
2022.7.2

profiler
Mic
0.12.2

query-history
Mic
0.5.3

schema-compare
Mic
1.18.0

server-report
Mic
0.2.3

sql-assessment
Mic
0.6.4

sql-database-projects
Mic
0.21.0

whoisactive
Mic
0.1.4

@cheenamalhotra any ideas what could be happening here?  It looks like the connection is SqlLogin so probably not related to MSAL updates I guess.

I think this might be also related to Query Editor, as when opening a new query, a connection/listdatabases request is sent..

@KDunn5517
Can you confirm this happens when you start a 'New Query' on a non-master database?

I have two users, and admin user and a developer user.  This issue is only occurring with my developer user.
Yes, this is happening every time I open a new query window on a non-master database, as my developer user does not have access to the master db.

Thanks for confirming.

First instance of this error was immediately after last Data Studio update, and has been constant since then.

Can you also specify the last ADS version that worked fine for you? Was it 1.40.2?

Sorry, I don't remember the version number.  I keep it up to date as soon as a version is available and after I took the last one this started occurring.

Greetings, same issue here. Opening a new query window or even switching between tabs gets the Request connection/listdatabases failed error.
I'm on the latest 1.41.1 version and the last working one for me was 1.40.2.

@alanrenmsft it looks like there have been several reports of similar issues since the 1.41 release.  Could you please investigate what's happening here?

These are potential duplicates of this issue.
https://github.com/microsoft/azuredatastudio/issues/21752
https://github.com/microsoft/azuredatastudio/issues/21804
https://github.com/microsoft/azuredatastudio/issues/21803

@KDunn5517 @VytenisJ we are going to release a hotfix to fix the issue of error popping up in an annoying way.
for the issue with database list for contained users, I've created an issue to track it here: https://github.com/microsoft/azuredatastudio/issues/21884, it will be fixed in March 2023 release.
for the query hang issue, there is already an issue for it: https://github.com/microsoft/azuredatastudio/issues/7440, we are actively investigating it.


Cannot sync chain from scratch due to block import error

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
Description
Since we've upgraded from polkadot-v0.9.19 to polkadot-v0.9.24, we cannot sync a node from scratch.
It always get stuck trying to import block 1086612 but it fails due to WASM call stack exhaustion.
If we downgrade to latest client before polkadot-v0.9.24 upgrade, the block is imported successfully.
We've upgraded to polkadot-v0.9.26 but error still persists.
Log
Here is the log from one of our collators (about 2 weeks old):
collator_20220707.txt
What Was Investigated So Far
From what I can see in the log, an EVM-related call is being executed and it ends up with call stack exhausted error.
I followed the stacktrace and my guess is that it's some contract that perhaps has infinite recursion (or calls lots of functions) and used to fail due to gas limit. I cannot confirm that but according to blockscout, 1 EVM transaction is marked as failed.
In the evm repo I found this:
Opcode::CALL => system::call(state, CallScheme::Call, handler),
Opcode::CALLCODE => system::call(state, CallScheme::CallCode, handler),
Opcode::DELEGATECALL => system::call(state, CallScheme::DelegateCall, handler),
Opcode::STATICCALL => system::call(state, CallScheme::StaticCall, handler),

hence my guess it's a recursive call (this part constantly repeats itself in the stacktrace).
My guess is that with latest upgrade(s), the callstack depth was reduced for wasmi and that's why it fails with new but works with old client. I haven't been able to verify this since I haven't managed to find where this is configured. (might be totally wrong, of course).
I did find this, although it relates to wasmtime:
https://bytemeta.vip/repo/bytecodealliance/wasmtime/issues/4214
We also have regalloc2 as dependency, not sure if it is relevant though.
Zoomed Part of the Log
The following is taken from the provided log to point out repeated calls:
2022-07-07 20:10:15 [Parachain] ⚙  Syncing, target=#1389107 (7 peers), best: #1086611 (0x1c8b…6b8f), finalized #0 (0x9eb7…29c6), ⬇ 3.9MiB/s ⬆ 17.1kiB/s
2022-07-07 20:10:16 [Parachain] 330 storage transactions are left open by the runtime. Those will be rolled back.
2022-07-07 20:10:16 [Parachain] 330 storage transactions are left open by the runtime. Those will be rolled back.
2022-07-07 20:10:16 [Parachain] Block prepare storage changes error: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: call stack exhausted
  WASM backtrace:
  0: <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
  1: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
  2: 0x11d364 - <unknown>!<evm::executor::stack::executor::StackExecutor<S,P> as evm_runtime::handler::Handler>::call::h69ec87fd06dc45ef
  3: 0xb3968 - <unknown>!evm_runtime::eval::system::call::h87659850f0b00992
  4: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
  5: 0xe9d05 - <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
  6: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
  7: 0x11d364 - <unknown>!<evm::executor::stack::executor::StackExecutor<S,P> as evm_runtime::handler::Handler>::call::h69ec87fd06dc45ef
  8: 0xb3968 - <unknown>!evm_runtime::eval::system::call::h87659850f0b00992
  9: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
 10: 0xe9d05 - <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
 11: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
 12: 0x11d364 - <unknown>!<evm::executor::stack::executor::StackExecutor<S,P> as evm_runtime::handler::Handler>::call::h69ec87fd06dc45ef
 13: 0xb3968 - <unknown>!evm_runtime::eval::system::call::h87659850f0b00992
 14: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
...
...
...
1634: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
1635: 0xe9d05 - <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
1636: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
1637: 0x11d364 - <unknown>!<evm::executor::stack::executor::StackExecutor<S,P> as evm_runtime::handler::Handler>::call::h69ec87fd06dc45ef
1638: 0xb3968 - <unknown>!evm_runtime::eval::system::call::h87659850f0b00992
1639: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
1640: 0xe9d05 - <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
1641: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
1642: 0x11d364 - <unknown>!<evm::executor::stack::executor::StackExecutor<S,P> as evm_runtime::handler::Handler>::call::h69ec87fd06dc45ef
1643: 0xb3968 - <unknown>!evm_runtime::eval::system::call::h87659850f0b00992
1644: 0x2300be - <unknown>!evm_runtime::eval::eval::hc1a492a7d69a6d92
1645: 0xe9d05 - <unknown>!evm_runtime::Runtime::run::h9658b50101d9a1f1
1646: 0x11a23f - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::call_inner::hdfd6092bf3da0b18
1647: 0x119716 - <unknown>!evm::executor::stack::executor::StackExecutor<S,P>::transact_call::habd7cd23fb2ca77f
1648: 0xdb284 - <unknown>!<pallet_evm::runner::stack::Runner<T> as pallet_evm::runner::Runner<T>>::call::hce6b1473ecdc4939
1649: 0xe5235 - <unknown>!pallet_ethereum::<impl pallet_ethereum::pallet::Pallet<T>>::apply_validated_transaction::heb98eb14d23df8cc
1650: 0xecd87 - <unknown>!<pallet_ethereum::pallet::Call<T> as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::h747abd25cb98a9d2
1651: 0x9f7ff - <unknown>!<astar_runtime::Call as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::h77ff5d2bdf975aed
1652: 0x9cac5 - <unknown>!<astar_runtime::Call as sp_runtime::traits::Dispatchable>::dispatch::h0b11be2c27055c06
1653: 0x9ca2f - <unknown>!<astar_runtime::Call as fp_self_contained::SelfContainedCall>::apply_self_contained::he16e52be80a30fbe
1654: 0x22ce7f - <unknown>!<fp_self_contained::checked_extrinsic::CheckedExtrinsic<AccountId,Call,Extra,SelfContainedSignedInfo> as sp_runtime::traits::Applyable>::apply::h1c69cda9a66cc589
1655: 0x547e5 - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::apply_extrinsic::h775d70717e8f3dba
1656: 0x52d76 - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::execute_block::h019662ea5c7bf877
1657: 0x175ca8 - <unknown>!Core_execute_block

Steps to reproduce
Issue can be reproduced by downloading latest client from here.
To be on the safe side, the issue was first reported with the v4.7.0 client so I recommend to try out with that one.
Use the following command to start the node:
astar-collator --chain astar --parachain-id 2006 --name "CannotImport" --execution wasm --prometheus-external --ws-port 9944 --port 33333 --state-cache-size 1 --rpc-port 29933 --prometheus-port 39616

It shouldn't be related to anything wasmi, since that's compiled into the runtime AFAIK, so any change to its maximum callstack length limit wouldn't affect historical blocks.
It's probably due to a new version of wasmtime, and their new register allocator being the culprit is a good guess considering how deep the stack trace is.
I'll take a look at this. It shouldn't be too hard to verify what exactly makes this explode if I'd just roll back to a previous version of wasmtime and try again. Even so, I'm not entirely sure what we could do to actually fix this, hm.... The EVM pallet should probably be fixed to not have this kind of unbound recursion, but that won't fix the issue for any of the historical blocks.
cc @pepyakin

The EVM pallet should probably be fixed to not have this kind of unbound recursion, but that won't fix the issue for any of the historical blocks.

Oh, absolutely.

Okay, I can confirm that the issue is due to a wasmtime upgrade. From what I can see the wasmtime 0.34 does not exhibit this issue, while wasmtime 0.35 does. If we look at wasmtime's changelog we can see this:

The native stack size allowed for WebAssembly has been decreased from 1 MiB to 512 KiB on all platforms to better accomodate running wasm on the main thread on Windows.

I've restored the original maximum stack size and I can confirm that it fixes this issue.
So the culprit here is not a different register allocator, but just simply a reduced default native stack size.
While I'm in general against increasing the stack size limit any further (and if the cause of this issue were due to the register allocator I would advocate for alternative measures) in this case I think we might as well just restore it to what it was originally, especially since it can potentially brick syncing for existing chains like we see here. @pepyakin Does this sound good to you?
(Note: this does not mean that the EVM pallet shouldn't be fixed to not have such deep recursion; it still should, and that's something I also intend to look into)

Given all of that, I'd approach increasing the stack limit for wasm cautiously.

Agreed. This is precisely why I'd rather not increase it any further, but since we already implicitly guaranteed a stack size of 1MB and then accidentally reduced it to 512KB it'd make sense to me to just restore the original status quo, especially since (as we can see here) some people actually depended on it.
Although if there's a good reason to stay at the 512KB stack size I'm willing to be convinced. Technically an alternative fix to this would look like this:

Fix the EVM pallet so that it doesn't recurse, but that the results are still the same.
Recompile the affected runtime.
Use the code substitutes hack to replace the runtime during sync with the fixed version. (We do this ourselves on polkadot.)

So it's obviously a lot more involved, and if any other chain encounters this issue it'll have to be done separately for them.

Technically an alternative fix to this would look like this:

If going this way, I think a better way would be instead of adding code subs, just allowing to tweak executor parameters for particular blocks.
I am leaning toward fixing this on our side though.
When I said cautiously, I meant that we should inspect the code on having any host functions that do recursive calls or consume stack space excessively, with a feeling that it's probably alright. Also, potentially, employ the same fix that was done on the PVF side: increase the stack space allocated for the thread that enters into wasmtime.

Also, potentially, employ the same fix that was done on the PVF side: increase the stack space allocated for the thread that enters into wasmtime.

Currently the runtime calls are made on whatever threads they incidentally end up being made, but I do want to refactor how we call into the runtime anyway to support async calls + QoS prioritization and that will entail running the executor on its own thread pool anyway, so yeah, that's something we definitely can do to have full control over the stack size.

Hi @koute, thanks for looking into this!
Can you perhaps share when will the revert/fix for stack size be merged into substrate?
This is making lives of our node operators quite messy (they have to switch between old and new node to bypass the problematic block). If this cannot be done soon, we can look into forking wasmtime and increasing the stack size to what it was before, just to fix Astar/Shiden (we'd switch to your solution once it's merged).
From the discussion above, I don't believe this should be problematic, but we'd prefer to avoid messing with that repo if possible :sweat_smile:

@Dinonard Sorry for the inconvenience. Fixing this won't require forking wasmtime and can be easily patched on Substrate's side. I will have a PR ready next week.

@koute no inconvenience, thanks for looking into it!
Will it be possible to backport this fix into polkadot-v0.9.26 or polkadot-v0.9.27 perhaps?

@Dinonard Well, I suppose we could backport it, but unless it's a more widespread issue it might not actually be necessary? The fix's not going to be anything complex, and it should be trivial to even just make your own temporary fork of polkadot-v0.9.26 and apply it there (I could even prepare it for you if necessary).
Anyway, I'll ping you again once I push the PR with the fix.

Sure, we can do that, it's not a problem if fix won't be complex.
Atm we're at polkadot-v0.9.27 so I doubt there will have been any major changes since that branch released.

@Dinonard PR's available here: https://github.com/paritytech/substrate/pull/11993

Awesome!
I'll prepare a fork, apply your PR and test just to confirm this particular issue is gone.
Thanks!

I can confirm that the issue is gone :+1:


Add @azure prefix to typescript readme package-name properties

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-js

Can one of the admins verify this patch?

@lmazuel Can you merge this PR for me since the only problem with it is the python generation?

@AutorestCI rebuild


[#175476527] release pipeline

Same changes applied in https://github.com/pagopa/io-functions-services/pull/96.
Changes in brief

Introduce the Release stage on the pipeline which marks a release on the repository
Refactor the whole CI/CD to have

separated pipelines for code review and deploy scenarios
everything is into .devops folder now

/azp run

no healthcheck

There's no such feature in the project, yet

/azp run


A bit lame

This acritical explains all of the obvious bits and doesn't add much value, so it would be useful to know something about top issue to look for, or in what order to deal with the issues or how the actual plan differs from the live plan in its final state etc etc

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

ID: 1e7b8b29-f3e3-0f7e-04b1-ae53738085d5
Version Independent ID: 780e2aec-7997-a92f-2f30-ff88e7f75972
Content: Analyze an Actual Execution Plan - SQL Server
Content Source: docs/relational-databases/performance/analyze-an-actual-execution-plan.md
Product: sql
Technology: performance
GitHub Login: @rwestMSFT
Microsoft Alias: randolphwest

@TUIMike -- Mike, thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@rwestMSFT -- Randolph, please look into this issue.

@TUIMike Thank you for your feedback. The breadth of plan analysis is outside the scope of this article, considering that many books have been written on the topic of SQL Server performance tuning.
We already state:

Query performance troubleshooting requires significant expertise in understanding query processing and execution plans, in order to be able to actually find and fix root causes.

If you wish to learn more about in-depth query plan analysis, there are many training options online. You can start with the Query processing architecture guide.
Good luck!
#please-close


Fixed, including items.


Tracking issue.

My head and controller moving even when I am still.
Tracking is super smooth outside LAVR app but when streaming it is moving randomly.
Also, I have only one controller.

Same with me.
Sent with GitHawk

For all i know the version you can download here is not compatilble with the newest Quest Firmware. For an easy fix try Downloading and installing 'Sideload'. A wonderfull app for user generatet content. There you have easy acess to a ALVR version that has the fix for the 'oinly one Controller' Problem.

Thanks. Still my tracking issues are not resolved. Also in every few
seconds it gets a stutter. Connection and speed is fine.
On Wed, Sep 11, 2019 at 11:20 PM pvtpaula<EMAIL_ADDRESS>wrote:

For all i know the version you can download here is not compatilble with
the newest Quest Firmware. For an easy fix try Downloading and installing
'Sideload'. A wonderfull app for user generatet content. There you have
easy acess to a ALVR version that has the fix for the 'oinly one
Controller' Problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/polygraphene/ALVR/issues/520?email_source=notifications&email_token=ACXUXC7ZYQEOQBRPJ7EBYKLQJEVVPA5CNFSM4IT2OJ72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6PKOFI#issuecomment-530491157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACXUXCZIJZD2ROA2IRYFCO3QJEVVPANCNFSM4IT2OJ7Q
.

For Oculus Quest you can try JackD83's fork.
It works only with Quest, and it has several Quest specific improvements.


Restart-Computer wait for PowerShell never completes

Steps to reproduce
Restart-Computer -ComputerName myServer -Wait -For PowerShell -Force
Expected behavior
Restart-Computer should complete waiting for PowerShell when it comes avaible after restart.
Actual behavior
Restart-Computer never completes.
Additional
Restart-Computer -ComputerName myServer -Wait -For WinRM -Force   (this works as expected)
Environment data
PSVersion                                 7.1.0-preview.1
PSEdition                                  Core
GitCommitId                             7.1.0-preview.1
OS                                             Microsoft Windows 10.0.18362
Platform                                    Win32NT
PSCompatibleVersions              {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion     2.3
SerializationVersion                  <IP_ADDRESS>
WSManStackVersion                 3.0
Edit
Did some more testing and it seem to be a problem for previous versions also.
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
PSVersion                      7.0.0-rc.3
PSEdition                      Core
GitCommitId                    7.0.0-rc.3
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
PSVersion                      6.2.4
PSEdition                      Core
GitCommitId                    6.2.4
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Found my way here after experiencing the same issue. Testing a previously working workflow and it hung at Restart-Computer, waiting for PowerShell which never completes. Same command from/to the same systems works as expected at a 5.1 prompt.

6 months and no change?

At a guess, @PaulHigin might have some familiarity with how this is supposed to work / what might be going wrong here? 🤔 k

I'm not familiar with this code very much.  But I believe @daxian-dbw has some experience with it, and may be able to provide more information.

This has been an issue for many many years, and occurs in Windows PowerShell. It seems like it only happens the first time you attempt to remotely restart a system and wait for PowerShell. I found just rebooting manually then restarting the script after the reboot point works.

I have the same almost behavior but randomly the Restart-Computer return an error "Restarting the computer did not finish within the time limit." The computer has restarted and PowerShell is ready.
Restart-Computer -ComputerName "MyComputer" -Force -For PowerShell -Wait -Timeout 600 -Delay 10
Environment data:
PSVersion                      5.1.17763.1490
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.1490
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Hello,
@doctordns, no, it's really random.
Each week end I reboot 2 times all Remote Desktop Session servers because I have an issue with FSLogix and for apply updates.
Sometimes, I have no issue with Restart-Computer and another weekend, I can have 10% of failed Restart-Computer.

Possible dup #11002


Added RawTemplate android project

Note to the contributors:
Have you read the Contribution Guidelines? If not, check CONTRIBUTING.md file first.

What kind of change does this PR introduce? (select / add custom)
(new project)
Description
RawTemplate is an Android project or a template that can be used to save a lot of time while developing projects. The project is developed in Kotlin using XML.

Checklist

mark [X] to make it checked.

[X] I've read the contribution guidelines.
[X] I've mentioned my project in the Readme as per guidelines.
[X] I've checked that my project is not a duplicate project and I have cross checked the exisiting projects in this repository.

Related Issues
Fixes Issue #19

Hey @binayshaw7777 can you make the requested changes?

Hey @binayshaw7777 can you make the requested changes?

What changes??

Hey @binayshaw7777 can you make the requested changes?

You mean to resolve the merge conflict?

Hey, I am so sorry, I forgot to submit the review 😬

Yeah, that's what I was going to reply about, anyway it's completely okay. I'll make the changes soon.
Thanks.


Give bars the possibility to movetoworkspace by dragging a window on a workspace

Description
Idk how this would be done or if it's even possible in the first place, but I think it would really be a nice feature to be able to just drag a window on top of a workspace number/icon/whatever on my bar and just drop it there.
Maybe it's possible to trigger an event or something if a window is dropped with the exact display location so bars can subscribe to the event to make something like this possible?
I use my pc all the time and while a very keyboard heavy workflow is great for work, it sometimes can be a bit annoying if you actually need 2 hands to move things. I guess I still need 2 hands to even drag a window (I wish there was like a button I could press to enable somehow a mouse only drag and drop kinda workflow for the less productivity heavy stuff I'm doing; something like a mouse 4 + mouse 1 to drag a window or to be able to show header bars which can be dragged)

only thing that should be done on hyprland's side is adding IPC/plugin events for begin/end dragging window
the rest would have to be handled on the bar's end

not possible


Type instantiation is excessively deep and possibly infinite.

Hello and first of all, thank you for your work with this library.
I was eager to migrate from zod to valibot after encountering this error on the use of schemas with many union and transform but the same one seems to occur.
Is there maybe a good practice to avoid it?
Thank you

Can you send me some code examples?

I have created a repo with my code.
For context, it's a bunch of schemas for the Notion API as well as a fetch wrapper.
My intent with this library is to validate the API responses and use schema transformations to simplify the structure sent by Notion.

The schemas/inputs contains the schemas I constructed and refactored from the API results (Notion API has a lot of union types).
The schemas contains the transformations.
The problem occurs in page

If I comment properties which is a record of an union of many schemas, the problem disappears :

export const vIPage = merge([
  vIPageOrDatabaseCommon,
  object({
    object: literal('page'),
    parent: union([vIParentDatabase, vIParentPage, vIParentWorkspace]),
    // properties: record(vIPageProp),
  }),
]);

Yes, the problem is vIPageProp which is used with properties: record(vIPageProp) in vIPage. However, I have not found out the exact cause yet. I will investigate this further.

I was able to reproduce the problem. However, I could not find the bug yet. I will investigate further in a moment. It is interesting to note that the problem does not occur in TypeScript v4.9.5. Therefore, it could also be a bug in TypeScript v5.
import { merge, omit, object, union, transform, record, string } from "valibot";

const Merge1 = merge([object({}), object({ key: string() })]);

const Merge2 = merge([Merge1, object({})]);

const Object1 = merge([Merge2, object({})]);

const Object2 = merge([omit(Merge2, ["key"]), object({})]);

const Record = record(union([Object1, Object2]));

transform(Record, (a) => a); // Error here

So as a workaround, you could downgrade TypeScript. It is important that you set the TypeScript version in VS Code to the version in your package.json. If you don't know how to do that and can't figure it out yourself, I can explain it to you here.

I have thoroughly checked the source code of omit and merge and cannot find any problem. I also noticed that when I copy the source code of merge into the project and update the imports, the problem disappears, even though it is the same code.
Since I have similar problems with Modular Forms using TypeScript v5, I assume that it must be a bug in TypeScript. I can't explain it any other way at the moment. If anyone else wants to investigate the issue further, I'm happy to hear the results. Until then, for all other users, I recommend downgrading TypeScript to v4.9.5.

Thank you for your reactivity! Yes, I'll try to downgrade and see if everything works smoothly :) At the same time, I'll investigate about that problem too.

It should be related to :

https://github.com/microsoft/TypeScript/issues/53514

Thank you for the tip. I will try to investigate this in the next few weeks.

I've ran into this issue a few times. Changing how I import valibot to
import * as v from 'valibot' removes the error every time.

I'm getting the same error message when using with object + merge.
As a workaround I'm using ObjectSchema.object property, like this:
import {object} from "valibot"

import {FileOutput} from "./FileOutput.js"
import {ImageSize} from "./ImageSize.js"

export const ImageOutput = object({
  ...FileOutput.object,

  metadata: ImageSize
})

Yes, that works too. Thank you! Another workaround that works in most cases is intersection:
import { intersection, object, string } from 'valibot';

const Object1 = object({ key1: string() });
const Object2 = object({ key2: string() });
const Object3 = intersection([Object1, Object2]);

Here is a guide that help to choose between intersect and merge: https://valibot.dev/guides/intersections/

I am toying with the idea of removing merge because of this TypeScript problem. Meanwhile, Valibot has a workaround that accomplishes exactly the same thing with a good DX. Please give me feedback.
import * as v from 'valibot';

const ObjectSchema1 = v.object({ key1: v.string() });

const ObjectSchema2 = v.object({ key2: v.number() });

const MergedSchema1 = v.merge([ObjectSchema1, ObjectSchema2]);

// This is the workaround that accomplishes exactly the same thing
const MergedSchema2 = v.object({
  ...ObjectSchema1.entries,
  ...ObjectSchema2.entries,
});

I think this is fixed in v0.30.0


Custom stage problem

Whenever I add a custom stage to the stages folder the mods/stages and load it the characters load in perfectly fine but the stage assets don’t load in

Where did you put your stages? And what is the code for the stage?

i put my stage assets in the shared assets and this is the image for the code

but when i run the lime test windows i get this error

This is the source code in the playstat

e

I think the game is actually expecting a closet bracked in the line 385 not 360. That if there is an open bracket in 359

The problem seems to actually start before line 360


How to set trophyGroupId for getUserTitles request ?

Hello!
I see in your documentation that for the getUserTitles query you specify "To retrieve trophies from all groups within a title (ie. the full trophy set), then trophyGroupId should be set to 'all'". Based on the answer to this query the percentage shows me the progress on all groups. I would like to know if it is possible to set the trophyGroupId to 'default' so that when we have the progress on the main game.
Thank you!

Hi @landscht ,
Sorry, after triple checking this is actually a documentation mistake on my part. It turns out this kind of querying is unsupported by this particular PSN endpoint. This endpoint can only retrieve the list of summarized user progress. After this list is retrieved, for deep progress, subsequent API calls must be used. The one you're looking for is probably getUserTrophiesEarnedForTitle.
I will update this documentation after work today and leave this issue open until that is done.

Docs updated via https://github.com/achievements-app/psn-api/pull/111. I've also included a note about subsequent calls w/ getUserTrophiesEarnedForTitle.


OP-6269_Houdini-Redshift-ROP-instance-image-format-bug

Problem :
"RS_outputFileFormat" parm value was missing
and there were more "image_format" than redshift rop supports
Fix:

removed unnecessary formats from image_format_enum
add the selected format value to RS_outputFileFormat

Task linked: OP-6269 Houdini Redshift ROP instance image format bug


Potential optimization

So I have a potential optimization, if you want to mix rasterization and raytracing,
So when you hit a voxel using raytracing you should draw all of the visible faces of that voxel using rasterization
do your usual depth comparisons, skip pixels that already have a voxel face drawn on them for raycasting, except for the edges, because of anti aliasing. (use a sobel edge filter)
The reason I think this might work is that any other visible voxels aren't going to be entirely smack dab on the voxel you've drawn, they're going to be slightly offsetted, larger, or entirely not visible, and using the depth comparison you can draw them in the correct order anyway, letting you skip raytracing to each and every pixel, only ones that haven't been drawn to yet.
This method should work as long as you rasterize every part of the voxel that should be visible.
I'm going to make a diagram in blender for this, of course transparent voxels still need the full raycasting treatment, until the ray hits a solid, anyway.

Look at this line of cubes, try and find a scenario where one cube entirely covers up another when it's not supposed to. Make new screenshots even, show a scenario where one cube that's supposed to be drawn would be covered up due to it's pixels already being taken entirely.

hello, thanks for reaching out.
i think this would work but isn't very good for parallelization. for this to be most useful you'd have to do rasterization between raytracing passes and then find what pixels still need to be rendered incurring a massive performance cost. I'm also not sure how you'd figure out what pixels need to be raytraced as even if a pixel is rasterized there could be a closer voxel (assuming you have LOD).
however, hybrid raytracing and rasterization can be very fast the other way around. in alex I rasterize my chunks then ray trace their interior. because there are no decisions (everything is rasterized) it's very parallelizable, so the idea of a hybrid system is quite a good one.


Deployment

Auto-deploy to staging on PR
Deploy to prod on master merge
Automate deployment with GitHub actions

Completed by #43 and #44


sdist: automatically add metadata file referenced files

Summary of changes
This is a first approximation to issue https://github.com/pypa/setuptools/issues/2821, where the lack of automatic inclusion of file: referenced files into the source distribution was explained. The strategy followed was to read the unexpanded version of supported configuration files, in the egg_info command (called within sdist command), by either:

Option A) Using setupcfg.read_configuration and pyprojecttoml.read_configuration funcs (https://github.com/pypa/setuptools/commit/4194c2a1994ebca396c4f8291784ade0ce970f68).
Option B) Using Distribution.parse_config_files method (https://github.com/pypa/setuptools/commit/abdbe0894236278acc0132db5d2bc91e628b4074).

Finally, all files within file: prefixed strings (setup.cfg case), of file dict keys (pyproject.toml case) are added to the list of distribution files.
Closes https://github.com/pypa/setuptools/issues/2821
Pending questions

Do folks prefer implementation option A, or option B?
Do folks prefer to "hide" this feature behind a feature flag?

Pull Request Checklist

[x] Changes have tests
[x] News fragment added in changelog.d/.

Hi @Sinclert, thank you very much for working on this and contributing to Setuptools.
I will need sometime to go through this PR and do a proper review (if any other maintainer would like to beat me to that, please go ahead 😄).
At a first glance (and I might be completely wrong here), something that caught my attention is that the PR proposes to re-process the configuration files and it also creates an intermediate disposable Distribution object...
This is not something I am (personally) fan of: we can get a performance hit for re-parsing the config files, and applying a unexpanded configuration to a disposable dist object sounds a bit hacky. But I can see the merit of this approach and the tests show it works...
I can imagine a "single-pass" alternative where we set/append-to some attribute in the original Distribution object while parsing/expanding the configuration and then using this attribute to populate the sdist. Of course, this is also not very clean... I don't know if there is a clean alternative to fix this problem (maybe the other maintainers have a suggestion?).

👋🏻 Hey Anderson, happy to contribute.

... the PR proposes to re-process the configuration files and it also creates an intermediate disposable Distribution object

Indeed, that is approach B of the ones stated in the PR description. The other alternative I proposed (option A), was to rely on both the setupcfg.py and pyprojecttoml.py read_configuration functions.

I can imagine a "single-pass" alternative where we set/append-to some attribute in the original Distribution object while parsing/expanding the configuration and then using this attribute to populate the sdist.

Yeah, I considered it. I think that would be the perfect implementation, but would require way more changes than the ones in this PR. I feel I lack context of how code is designed / structured to tackle those 😕

Hi @Sinclert, would you like to have a look on #3779? That is my first attempt on implementing the approach described by option B.
To be sincere, I don't know which one is more elegant...
Something that I dislike in #3779 is that some functions that are supposed to "read/parse" the configuration have the side-effect of modifying the Distribution object... It also pollutes the Distribution object by adding yet another attribute...
Another difference between this PR and #3779 is that in #3779 I also taking the opportunity to tackle closely related problems: project.readme and project.license.file in pyproject.toml.

Oh, I like https://github.com/pypa/setuptools/pull/3779 way more.
Any approach that would avoid re-parsing config files is better than what I propose here.
I know it is still in draft stage, but just in case you missed it: I found this documentation section warning users about making sure they include file: referenced files into their sdist. May be worth an update :)

Also:
I noticed the sdist command displays a bunch of logging messages about which files are copied / created / ... Maybe worth defining some logging messages for these file additions? 🤔

I noticed the sdist command displays a bunch of logging messages about which files are copied / created / ... Maybe worth defining some logging messages for these file additions? 🤔

Hi @Sinclert, so the corresponding logging messages are not being automatically added for the new files?
If that is the case I don't know if it is worthy, because the files get added together with all the files identified in egg_info. I would have to do something different to get those messages separatedly.

I know it is still in draft stage, but just in case you missed it: I found this documentation section warning users about making sure they include file: referenced files into their sdist. May be worth an update :)

Thank you very much for the reminder! I will try to get some parts of this PR to use in the other one if you don't mind :P
I already stole tests 😝 (thank you very much!)

Hi @Sinclert, I did the following experiment to see if the logs indicate the added files:
docker run --rm -it python:3.11 /bin/bash
mkdir /tmp/myproj
cd /tmp/myproj
cat <<EOF > pyproject.toml
[build-system]
requires = ["setuptools @ git+https://github.com/abravalheri/setuptools@add-referenced-files"]
build-backend = "setuptools.build_meta"

[project]
name = "myproj"
readme = {file = "USAGE.md", content-type = "text/markdown"}
license = {file = "DOWHATYOUWANT"}
dynamic = ["version"]

[tool.setuptools.dynamic]
version = {file = ["VERSION.txt"]}
EOF

touch USAGE.md
touch DOWHATYOUWANT
touch README.rst
echo "0.42" > VERSION.txt
python -m venv .venv
.venv/bin/python -m pip install build
.venv/bin/python -m build

...
running sdist
running egg_info
writing myproj.egg-info/PKG-INFO
writing dependency_links to myproj.egg-info/dependency_links.txt
writing top-level names to myproj.egg-info/top_level.txt
reading manifest file 'myproj.egg-info/SOURCES.txt'
writing manifest file 'myproj.egg-info/SOURCES.txt'
running check
creating myproj-0.42
creating myproj-0.42/myproj.egg-info
copying files to myproj-0.42...
copying DOWHATYOUWANT -> myproj-0.42
copying README.rst -> myproj-0.42
copying USAGE.md -> myproj-0.42
copying VERSION.txt -> myproj-0.42
copying pyproject.toml -> myproj-0.42
copying myproj.egg-info/PKG-INFO -> myproj-0.42/myproj.egg-info
copying myproj.egg-info/SOURCES.txt -> myproj-0.42/myproj.egg-info
copying myproj.egg-info/dependency_links.txt -> myproj-0.42/myproj.egg-info
copying myproj.egg-info/top_level.txt -> myproj-0.42/myproj.egg-info
Writing myproj-0.42/setup.cfg
Creating tar archive
...

I can see that the output already includes copying <FILE> -> myproj-0.42.
Is that what you were referreing to? So I think there is no need to do anything special, right?

I will try to get some parts of this PR to use in the other one if you don't mind :P

Please, be my guest.

I can see that the output already includes copying  -> myproj-0.42.
Is that what you were referreing to? So I think there is no need to do anything special, right?

Yeah, that might be enough. However, this PR added custom logging for those file: referenced files, in the same manner that there is a custom message for the license files. For instance, building a package with my proposal could output the following
> python -m build .
...
adding license file 'DOWHATYOUWANT'
adding metadata referenced file 'USAGE.md'
adding metadata referenced file 'VERSION.txt'
...

It is up to you, maintainers, whether to add custom logging, or rely on the default one (copying ...).

I am adding some logs in 9ad7d341aa212de171ce3e734cabf98323980eaf, although only in the "verbose mode" (people already complain that setuptools output is too much).

Closing PR, as superseded by https://github.com/pypa/setuptools/pull/3779


Check SourceLink best practices re PDB files

See https://github.com/dotnet/sdk/issues/1458 and https://github.com/ctaggart/SourceLink - we may be able to remove the extra chunk of the project file that talks about copying the PDBs.

Yay, it looks like this works, although it requires a newer SDK version.
PR for GAX: https://github.com/googleapis/gax-dotnet/pull/236
Once that's in, I'll apply it to this repo too.


Support routing in IoTHub

Add new commands for CRUD of Endpoints and Routes in IoTHub.
Add "Test" commands for route.
Update integration test.
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Thanks for addressing the comments. Please keep debugging the test and make sure CI passes before we can take another look and move towards accepting this PR.

@troydai finally CI passed, Could you please have a another look on this?

sure. I'm looking at it.


Configuring etcd with RBAC and certificates

Todos

[x] Page with the path information for the different components
[x] Write K8s specific doc.

[x] Calico components needed
[x] Manifest updates needed
[x] K8s cert configuration (link to somewhere)

[ ] Maybe docker/libnetwork specific

@lxpollitt Did you want to review this before it is merged?

I don't know why but I can't "Reply" to the comment

We should probably spell this out then. Or change the wording in the "Why you might be interested" section to just be "preventing Calico from accessing Kubernetes data" since as it stands Kubernetes can access Calico data if it has the root role.

But....
If k8s is using etcd v3 then it can't actually access the Calico data since Calico is on the v2 side.


Invalid FIELDALIAS config

Splunk 7.2.5 will crash if it finds an invalid field alias configuration. Lucky day, there's one here!
props.conf line 35:
FIELDALIAS-process_current_directory = CurrentDirectory

Should read:
FIELDALIAS-process_current_directory = CurrentDirectory AS process_current_directory

Thanks!
Dave

Thanks Dave! I just updated that in the master branch.


add Quarto, Manubot, Pandoc Scholar

https://quarto.org/, https://quarto.org/docs/gallery/, https://quarto.org/docs/extensions/listing-journals.html
https://manubot.org, https://manubot.org/catalog/
https://github.com/pandoc-scholar, https://pandoc-scholar.github.io/

+1 to quarto and manubot, looks interesting! PRs welcome
Pandoc scholar is no longer maintained.

I forgot that Quarto was already added in #48. So only manubot remains.


aws x-ray tracer configuration with hostname

Hello guys,
Standard configuration works fine
tracing:
  http:
    name: envoy.tracers.xray
    typed_config:
      "@type": type.googleapis.com/envoy.config.trace.v3.XRayConfig
      segment_name: "Envoy" # You must set this until v1.14
      daemon_endpoint:
        protocol: UDP
        address: <IP_ADDRESS>
        port_value: 2000
      sampling_rule_manifest:
        filename: /xray_daemon/rules.json

But how to use configuration with a host name like this:
tracing:
  http:
    name: envoy.tracers.xray
    typed_config:
      "@type": type.googleapis.com/envoy.config.trace.v3.XRayConfig
      segment_name: "Envoy" # You must set this until v1.14
      daemon_endpoint:
        protocol: UDP
        address: xray-service.amazon-cloudwatch.svc.cluster.local
        port_value: 2000
      sampling_rule_manifest:
        filename: /xray_daemon/rules.json

Error that happened with such config in EKS + Istio
warning envoy config  gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) <IP_ADDRESS>_8080: malformed IP address: xray-service.amazon-cloudwatch.svc.cluster.local:2000
<IP_ADDRESS>_8443: malformed IP address: xray-service.amazon-cloudwatch.svc.cluster.local:2000
Related to
#10442
https://github.com/aws/aws-app-mesh-roadmap/issues/319

Like called out in https://github.com/aws/aws-app-mesh-roadmap/issues/319#issuecomment-811298764 the only solution is  to enhance x-ray extension to send traces to cluster defined in Envoy config.

Is the plan to collect xray traces using otel-collector agent?
Or xray is temp solution, you would eventually like to use OpenTelemetry tracing solution itself?


universe: sort incoming transfer proofs by block height

In this commit, we attempt a simple sorting routine to address: https://github.com/lightninglabs/taproot-assets/issues/591.
Without these, we'll try to validate transfer proofs out of order, which is akin verifying an orphan transaction in the Bitcoin mempool. Rather than do a full on topological sort, we instead just sort by block height. As we don't support spending unconfirmed change, this should be enough to serialize the contents of a block.

Superseded by #594


Change _cnr to stat-cnr_dwimap

Closes #864.
Changes proposed in this pull request

Add stat entity to filename templates.
Replace cnr suffix with stat-cnr_dwimap.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 28.52%. Comparing base (0deeee0) to head (6537f82).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #867   +/-   ##
=======================================
  Coverage   28.52%   28.52%
=======================================
  Files          68       68
  Lines       10146    10146
  Branches     1142     1142
=======================================
  Hits         2894     2894
  Misses       7152     7152
  Partials      100      100

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


Download as a CSV

[x]  Add button for download CSV
[x] Align the button in the popup
[x] Capture the link from which the text is copied
[x] Maintain the original copied text and edited text
[x] Implement Download CSV functionality with data

Is the URL for a specific text added in the CSV?

yes, the URL in CSV is for the link from which the text is copied.


Able to Sign in with Different Emails (Client)

On the client app, whether I use my client email or the admin email, I'm able to sign in.

Hi @MarwaKhalid, I was wondering if you could give me the steps to reproduce the problem and I am unable to reproduce it on my end. Thanks!

This issue has been solved.


The Lost Episodes of 2022

Why none of these were pushed a year ago, I don't know.

PR already made a year ago with updates, still haven't merged them for reasons?

not sure what happened, but it's merged now.


How can I get the output of the net's last layer- symbol.LinearRegressionOutput?

Hi,
I tried to get the net loss by add the loss into mx.sym.Group() like this:
density = self.get_Net(data)
Euclidean_loss = mx.sym.LinearRegressionOutput (data = density,label = label,grad_scale = 1/(2.*BATCH_SIZE),name = 'Euclidean_loss')
group = mx.sym.Group([mx.sym.BlockGrad(data = density), Euclidean_loss])

When training the net, I print the ''texec.outputs '' . Then I found that the loss is same as density. I don't know why ? Can anybody help me?    I'm very appreciated it.
Also I tried to make my own loss by using the mx.sym.Makeloss
Euclidean_loss = mx.sym.MakeLoss(mx.sym.square(density - label).sum()/(2.*BATCH_SIZE))

When I training the net again, I  got that the prediction is zero? I'm very appreciated it if you can help me.

Please use the user forum for how-to questions. You'll get quicker responses there. https://discuss.mxnet.io/
@nswamy Can you please add labels -
Question, HowTo, python

Thanks，I will try it.@Roshrini

why you closed the question, I haven't got a best answer to solve the quenstion
@nswamy

@guoswang Please ask your questions on discuss.mxnet.io.


Use rails_admin with API only Rails 5.2 without asset_pipeline

I was told rails_admin would work "out of the box" with a Rails API only app. I have no asset pipeline as I have no need for assets outside of rails_admin. Is there a way to load the rails_admin assets external to the asset pipeline? This is the error I'm seeing:
ActionView::Template::Error (The asset "rails_admin/rails_admin.css" is not present in the asset pipeline.):

hi @idknox i have rails_admin working with rails api 5.2 out of the box.

have you added the required middleware?

Prueba activar las middelwares, https://medium.com/alturasoluciones/como-hacer-funcionar-activeadmin-en-una-aplicacion-rails-habilitada-como-api-61138656e07


loader: createdevice needs fix for handling ICD extensions from multiple devices per ICD

CreateDevice, in process of filtering out extensions needs to get the ICDs VkPyhsicalDevice object. The way this is done currently only works if the ICD has one physicalDevice rather than multiple physicalDevices.

Need to also consider Instance layer(s) that may wrap the PhysicalDevice object(s) returned by the ICD.

Yes, I think the layer wrapping is already handled properly.

pushed fix to master


Checkpoint ts stuck for 1h+ in test case: dtb_basic_incremental_sync

What did you do?

Testbed: Azure VM + k8s
Test case: dtb_basic_incremental_sync, link: https://tcms.pingcap.net/dashboard/executions/plan/1260512
Workload: simulate one customer's workload
Create a changefeed, pause it, workload prepare, then resume changefeed

What did you expect to see?
No response
What did you see instead?

Workload prepare lasts for 40min, then resume changefeed, more than 1hour later, check changefeed checkpoint ts, it don't move forward at all.

/ # /cdc cli changefeed list --pd=http://upstream-pd:2379
[
{
"id": "basic-incremental-sync",
"summary": {
"state": "normal",
"tso":<PHONE_NUMBER>21787406,
"checkpoint": "2022-09-08 12:55:16.468",
"error": null
}
}
]
/ # date
Thu Sep  8 13:46:26 UTC 2022
/ # /cdc cli changefeed list --pd=http://upstream-pd:2379
[
{
"id": "basic-incremental-sync",
"summary": {
"state": "normal",
"tso":<PHONE_NUMBER>21787406,
"checkpoint": "2022-09-08 12:55:16.468",
"error": null
}
}
]
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):
(paste TiKV version here)
6.1.1

TiCDC version (execute cdc version):
(paste TiCDC version here)
6.1.1

This is performance issue on azure testbed. When downstream mysql use fast-disk instead of HDD, sink write to mysql still slowly:

/severity minior

/close


Change pages team and shop

I have change pages team and shop with border in the cards and responsive.

It's ok, good job !


Test null values for HashMap generic vtype.

The HashMap javadoc does not explain whether null key or values are supported. This is important when replacing the jdk HashMap by the hppc HashMap in existing code, to be sure we also support null key or values, as the jdk HashMap.
This PR proposes to add tests cases to test null values, and to explain in the javadoc when either KType or VType are generic.

Actually I discovered that there existed a testNullValue() method in KTypeVTypeHashMapTest.
I adapted and removed the template conditions on VType generic since the generated test code passes even if VType is not generic.


Add @throws decorator for abstract methods of the interface.

Problem
According to https://reflectoring.io/lsp-explained/ there are several types of breaking Liskov substitution principle.

Solution
from attr import attrs, attrib
from generics import private, throws

@private
@attrs
class User(UserInterface):
    name = attrib()

    @throws(ValueError)
    def greet(self):
        if not self.name:
            raise TypeError  # <== Error
        return f"Hello, {self.name}"

The client code does not depend on the User class. It depends on the interface. This is why the implementation of the interface should not break the contract of the interface.
I don't think there this a point to support @throws decorator without interfaces.
Rules
If the method throws more than one exception type, it is a sign that it does too much.
Even worth, it force client code to do too much as well.
Only one exception type is allowed to be thrown.
Methods are not allowed to throw exceptions by default.
Delegated methods could propagate exceptions only of the same type.
Client code could catch errors using alias:

@delegated(User)
class LoggedUser:
    user = attrib()
    logger = attrib()

    def greet(self):
        self.logger.info('Greeting a user')
        try:
            result = self.user.greet()
        except self.user.greet.exception as error:
            #                  ---------
            self.logger.error('Greeting fails')
        else:
            self.logger.info('Greeting succed')
            return result

According to the number of rules listed here, I'm sure this issue should be split into its own milestone.

It would be redundant to mention same exception twice:

In decorator argument
In raise statement inside method

Probably, we should have more flexible rules not to repeat it.
@delegate decorator could re-raise any exception freely.
We should makes decision what to do with exception propagated by inner calls.
Mentioning throws exception from other layer could be a be a bad idea.


Apple iphone video call freezes on safari browser?

We have installed video call web app and it is working fine in android phones and pc. But in Apple iphone video call freezes on safari browser?

Are you referring to P2P or conference calling code sample?

We are using only P2P

@SANTHILADATABOT
here is a Web conference code sample deployed
https://teatalk.connectycube.com
I use it every day for an internal sync using my iPhone X - so far all is good
Could you please share how it works at your side
meanwhile we will check a P2P code sample

@SANTHILADATABOT
Fixed https://github.com/ConnectyCube/connectycube-web-samples/commit/a55b9e92ec39201ca20466a65e3435f1a45d3909
you can check here
https://connectycube.github.io/connectycube-web-samples/videochat/dist/

We are checking in iphone 7, with the code you gave the video freeze issue is resolved. But scrolling is not happening and because of it i am not able to see the call button, during the call can not see the mute , camera switch and call end button. i have attached the screenshots for your reference.

Any updates on how to resolve this?

@SANTHILADATABOT  we will update soon

@SANTHILADATABOT fixed
https://github.com/ConnectyCube/connectycube-web-samples/commit/61df0b80630d76ec4850aba7366c8080309ffaba


Fix issues identified during integrate

BUILD.bazel: remove import of unused build_test.
BUILD.bazel: order dependencies alphabetically.

This PR ended up being part of an emergency downstream integrate to accommodate potentially breaking changes in MLIR bytecode implementation: https://reviews.llvm.org/D149515. I will force merge it now.


manually populate CFP and schedule with summarised data from 2020

Proposal for (temporary) content for Schedule and CFP pages, featuring 2020 content, while we work out proper archiving strategy.

Thanks!

@corcra @getsarker I've pushed the "develop" branch to gh-pages, so you can see the updates at: https://www.chilconference.org/


[FR] Push Notification trigger scheduling using Admin SDK and FCM.

Is your feature request related to a problem? Please describe.
There doesn't seem to exist a FCM API to schedule a push notification for a later date/time using the Admin SDK.
Describe the solution you'd like
I need to set a schedule/trigger time programmatically based on some calculations done by getting the data of the user from Cloud Firestore.
Hence, I am using Cloud Functions + Admin SDK to get data and do my time calculations, and now I need FCM + Admin SDK to set trigger date based on my calculation results, which doesn't seem possible atm.
Describe alternatives you've considered
I considered using Cloud Scheduler to set up cron jobs but the number of resulting API calls would be far from economical.
Additional context
Not that this matters a lot (or it just might..), I think most other cloud platforms already have this feature and it would be cool to have this incorporated in Firebase as well!

Please file as a feature request at https://firebase.google.com/support
This needs to be implemented as a core FCM feature, and only then SDKs can begin to support it.


Creative items

How can I make the bot get an item from the creative inventory?
I tried these:
ItemInfo diamond = bot.Data.Items.ByName("diamond")!;
bot.GetPlugin<WindowPlugin>().Inventory!.SetSlot(new Slot(new Item(diamond, 1, null, null), 1));

and also this
ItemInfo diamond = bot.Data.Items.ByName("diamond")!;

Window mainInventory = new Window(255, "", 4 * 9, null, null);
Window inventory     = new Window(0, "Inventory", 9, mainInventory, null);

inventory.SetSlot(new Slot(new Item(diamond, 1, null, null), 1));

but both don't work
also how does mining work?
when I do
Block b = worldPl.World.GetBlockAt(new Position(x, y, z));

await worldPl.MineBlock(b, BlockFace.Top);

nothing happens

So the mining works when I try it with a vanilla server but on spigot it doesn't work

Hey,
it is not documented anywhere, but generally you should never use window.SetSlot() with windows from WindowPlugin.
If you use SetSlot, the client and the server window will get out of sync.
I haven't implemented any creative inventory logic yet, but i'll add it to the todo list.

nice ty

alright I made the packet for creative inventory item getting and got it working.

Also added it to the registry

(I didn't clone the repo correctly so I can't make a pull request sorry)

oh thanks a lot, i will add it myself if thats okay for you

ye sure

Okay, so I have added the packet and CreativeInventory in WindowPlugin.
The creative inventory is accessible with bot.GetPlugin<WindowPlugin>().CreativeInventory.
The creative inventory supports

CreativeInventory.Available, indicating whether the creative inventory is available and
CreativeInventory.GetItem(ItemType type, byte count, short inventorySlotIndex) which places count items of type type in the bots inventory at index inventorySlotIndex.


Cognitive Load

I m new to programming and have started using RxBinding about two weeks ago. According to me RxBinding somewhere increases the cognitive load of the code by actually increasing the number of lines for the same thing which can be done in one line previously.
ex. toolbar.setTitle("some string");
same with RxBinding
RxToolbar.title
.accept("some string");
I sthere a way to use RxBinding wihtout increasing the cognitive load ?

You should not be using it for that. The Consumers are exposed such that you can subscribe them to an RxJava stream.
e.g.,
someStream.subscribe(RxToolbar.title(toolbar));

which otherwise would be
someStream.subscribe(new Consumer<String>() {
  @Override public void accept(String s) {
    toolbar.setTitle(s);
  }
});

If you have lambdas and method references just do
someStream.subscribe(toolbar::setTitle)

and don't use RxBinding at all.

Thanks for the suggestions ! Is there a way I can decide when to use RxBinding and when not while at this stage. I feel RxBinding but I need to understand it fully to actually make a difference with it.


Edit protocol http to https

I could not use 'markdown-to-slides' in gh-pages, becaouse the tool is still using http-protocol for calling ibrary.

Hello @ktrysmt
What is the problem with HTTP exactly ?
David

Hi, I used it in gh-pages. But occurred the security caution.
For example: https://ktrysmt.github.io/slides/template/sample-slide.html

Better late than never...
Your changes have been merged, and are available on npmjs as version 1.0.4.
Thank you :)
David


Use Illuscienta icons in Mastodon.

Let's get rid of the default Java icons.
On Mac.

On Windows.

Integrated since beta-21