[Snyk] Security upgrade golang from 1.16.4-alpine to 1.24rc1-alpine

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

scenarios/ecs_takeover/terraform/website/Dockerfile

We recommend upgrading to golang:1.24rc1-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Read SNYK-ALPINE313-APKTOOLS-1533754
  714

Buffer Overflow SNYK-ALPINE313-OPENSSL-1569448
  714

Buffer Overflow SNYK-ALPINE313-OPENSSL-1569448
  714

Out-of-bounds Write SNYK-ALPINE313-ZLIB-2976175
  714

Use After Free SNYK-ALPINE313-BUSYBOX-1920735
  614

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free

Checkmarx One – Scan Summary & Details – 35c041a6-d766-4be8-a966-d4258397a879
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-45311
Npm-fsevents-1.2.9
Vulnerable Package

CVE-2023-49569
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

CVE-2024-3817
Go-github.com/hashicorp/go-getter-v1.5.9
Vulnerable Package

CVE-2024-41110
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CloudWatch Unauthorized Access Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for unauthorized API calls

CVE-2021-41092
Go-github.com/docker/cli-v20.10.7
Vulnerable Package

CVE-2022-24778
Go-github.com/containerd/imgcrypt-v1.1.1
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apiserver-v0.20.6
Vulnerable Package

CVE-2023-44487
Go-google.golang.org/grpc-v1.38.0
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apimachinery-v0.20.6
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-49568
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

CVE-2024-21538
Npm-cross-spawn-6.0.5
Vulnerable Package

CVE-2024-21538
Npm-cross-spawn-5.1.0
Vulnerable Package

CVE-2024-21626
Go-github.com/opencontainers/runc-v1.0.0-rc93
Vulnerable Package

CVE-2024-24786
Go-google.golang.org/protobuf-v1.26.0
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-45338
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2024-6257
Go-github.com/hashicorp/go-getter-v1.5.9
Vulnerable Package

Cx477c10a4-5717
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cx9c51b693-b977
Go-github.com/containerd/containerd-v1.5.2
Vulnerable Package

Cxb421a484-d05a
Go-github.com/cyphar/filepath-securejoin-v0.2.2
Vulnerable Package

Cxb6dee8d5-b814
Go-gopkg.in/square/go-jose.v2-v2.5.1
Vulnerable Package

DB Instance Storage Not Encrypted
/rds.tf: 50
AWS DB Instance should have its storage encrypted by setting the parameter to 'true'. The storage_encrypted default value is 'false'.

DB Instance Storage Not Encrypted
/rds.tf: 46
AWS DB Instance should have its storage encrypted by setting the parameter to 'true'. The storage_encrypted default value is 'false'.

ECS Task Definition Volume Not Encrypted
/ecs.tf: 71
Amazon ECS Task Definition does not have encryption for data at transit enabled. To prevent such a scenario, enable the attribute 'transit_encryption'

EFS Not Encrypted
/efs.tf: 1
Elastic File System (EFS) must be encrypted

IAM Policy Grants Full Permissions
/iam.tf: 108
IAM policy should not grant full permissions to resources from the get-go, instead of granting permissions gradually as necessary.

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Passwords And Secrets - Generic Token
/cognito.tf: 85
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cognito.tf: 86
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cognito.tf: 84
Query to find passwords and secrets in infrastructure code.

S3 Bucket Object Not Encrypted
/s3.tf: 81
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 51
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 61
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 49
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 29
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 63
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 19
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 39
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 71
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 91
S3 Bucket Object should have server-side encryption enabled

SNS Topic Not Encrypted
/sns.tf: 12
SNS (Simple Notification Service) Topic should be encrypted

SNS Topic Not Encrypted
/sns.tf: 2
SNS (Simple Notification Service) Topic should be encrypted

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 77
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 53
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 102
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Unknown Port Exposed To Internet
/ec2.tf: 78
AWS Security Group should not have an unknown port exposed to the entire Internet

Unrestricted Security Group Ingress
/ec2.tf: 78
Security groups allow ingress from <IP_ADDRESS>:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 106
Security groups allow ingress from <IP_ADDRESS>:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 82
Security groups allow ingress from <IP_ADDRESS>:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 58
Security groups allow ingress from <IP_ADDRESS>:0 and/or ::/0

ALB Deletion Protection Disabled
/lb.tf: 27
Application Load Balancer should have deletion protection enabled

ALB Is Not Integrated With WAF
/lb.tf: 27
All Application Load Balancers (ALB) must be protected with Web Application Firewall (WAF) service

ALB Listening on HTTP
/lb.tf: 74
AWS Application Load Balancer (alb) should not listen on HTTP

ALB Not Dropping Invalid Headers
/lb.tf: 27
It's considered a best practice when using Application Load Balancers to drop invalid header fields

API Gateway Access Logging Disabled
/apig.tf: 316
API Gateway should have Access Log Settings defined

API Gateway Access Logging Disabled
/apigateway.tf: 38
API Gateway should have Access Log Settings defined

API Gateway Access Logging Disabled
/apigateway.tf: 38
API Gateway Stage should have Access Logging Settings defined

API Gateway Access Logging Disabled
/apig.tf: 316
API Gateway Stage should have Access Logging Settings defined

API Gateway Deployment Without Access Log Setting
/apig.tf: 309
API Gateway Deployment should have access log setting defined when connected to an API Gateway Stage.

API Gateway Method Does Not Contains An API Key
/apig.tf: 89
An API Key should be required on a method request.

API Gateway Method Does Not Contains An API Key
/apig.tf: 82
An API Key should be required on a method request.

API Gateway Method Does Not Contains An API Key
/apig.tf: 99
An API Key should be required on a method request.

API Gateway With CloudWatch Logging Disabled
/apig.tf: 316
AWS CloudWatch Logs for APIs should be enabled and using the naming convention described in documentation

API Gateway With Open Access
/apig.tf: 102
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway With Open Access
/apig.tf: 85
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway With Open Access
/apig.tf: 92
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway Without Configured Authorizer
/apig.tf: 65
API Gateway REST API should have an API Gateway Authorizer

API Gateway Without SSL Certificate
/apig.tf: 316
SSL Client Certificate should be enabled

API Gateway without WAF
/apig.tf: 316
API Gateway should have WAF (Web Application Firewall) enabled

CVE-2021-41190
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20210513164829-c07d793c2f9a
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.8
Vulnerable Package

CVE-2024-29018
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CVE-2024-35195
Python-requests-2.26.0
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CloudTrail Log Files S3 Bucket with Logging Disabled
/cloudtrail.tf: 49
CloudTrail Log Files S3 Bucket should have 'logging' enabled

CloudWatch AWS Config Configuration Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for AWS Config configuration changes

CloudWatch Changes To NACL Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for changes to NACL

CloudWatch Disabling Or Scheduled Deletion Of Customer Created CMK Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMK

CloudWatch Log Group Without KMS
/cloudwatch.tf: 1
AWS CloudWatch Log groups should be encrypted using KMS

CloudWatch Management Console Auth Failed Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for AWS Management Console authentication failures

CloudWatch Root Account Use Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for root acount usage

CloudWatch S3 policy Change Alarm Missing
/cloudwatch.tf: 43
Ensure a log metric filter and alarm exist for S3 bucket policy changes

CloudWatch S3 policy Change Alarm Missing
/cloudwatch.tf: 11
Ensure a log metric filter and alarm exist for S3 bucket policy changes

CloudWatch VPC Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for VPC changes

Cloudwatch Cloudtrail Configuration Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for CloudTrail configuration changes

Cloudwatch Security Group Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for security group changes

Container Capabilities Unrestricted
/docker_stack.yml: 4
Some capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnecessa...

Cx47e4310e-3167
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cx68162182-3f7b
Go-github.com/containerd/containerd-v1.5.2
Vulnerable Package

EC2 Instance Has Public IP
/ec2.tf: 29
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 122
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 119
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 96
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 183
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 61
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 43
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 137
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 25
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 6
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 98
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/dev_machine.tf: 52
EC2 Instance should not have a public IP address.

EC2 Instance Monitoring Disabled
/ec2.tf: 132
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 178
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 114
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 37
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 93
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 25
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 23
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 57
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 3
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 91
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/ec2.tf: 117
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

EC2 Instance Monitoring Disabled
/dev_machine.tf: 52
EC2 Instance should have detailed monitoring enabled. With detailed monitoring enabled data is available in 1-minute periods

ECR Image Tag Not Immutable
/sdlc.tf: 58
ECR should have an image tag be immutable. This prevents image tags from being overwritten.

ECS Task Definition Network Mode Not Recommended
/ecs.tf: 45
Network_Mode should be 'awsvpc' in ecs_task_definition. AWS VPCs provides the controls to facilitate a formal process for approving and testing all...

Healthcheck Not Set
/docker_stack.yml: 4
Check containers periodically to see if they are running properly.

IAM Database Auth Not Enabled
/rds.tf: 50
IAM Database Auth Enabled should be configured to true when using compatible engine and version

IAM Database Auth Not Enabled
/rds.tf: 46
IAM Database Auth Enabled should be configured to true when using compatible engine and version

IAM Policies Attached To User
/iam.tf: 24
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 85
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/initial_iam_user.tf: 6
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 98
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/dev_machine.tf: 76
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 119
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 106
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 120
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/rw_iam_user.tf: 6
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 89
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 102
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 19
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 115
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 55
IAM policies should be attached only to groups or roles

IAM Policies With Full Privileges
/iam.tf: 108
IAM policies shouldn't allow full administrative privileges (for all resources)

Memory Not Limited
/docker_stack.yml: 4
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than t...

Missing_HSTS_Header
/scenarios/ecs_takeover/terraform/website/main.go: 51
Attack Vector

RDS With Backup Disabled
/rds.tf: 46
Make sure the AWS RDS configuration has automatic backup configured. If the retention period is equal to 0 there is no backup

RDS With Backup Disabled
/rds.tf: 50
Make sure the AWS RDS configuration has automatic backup configured. If the retention period is equal to 0 there is no backup

RDS Without Logging
/rds.tf: 46
RDS does not have any kind of logger

RDS Without Logging
/rds.tf: 50
RDS does not have any kind of logger

REST API With Vulnerable Policy
/apig.tf: 325
REST API policy should avoid wildcard in 'Action' and 'Principal'

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

S3 Bucket Logging Disabled
/s3.tf: 6
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/cloudtrail.tf: 49
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 27
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 9
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 49
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 38
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/codepipeline.tf: 8
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 9
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Policy Accepts HTTP Requests
/cloudtrail.tf: 56
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Policy Accepts HTTP Requests
/s3.tf: 4
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Policy Accepts HTTP Requests
/s3.tf: 15
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Without Versioning
/s3.tf: 38
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 9
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 6
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 9
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/cloudtrail.tf: 49
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 49
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 27
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/codepipeline.tf: 8
S3 bucket should have versioning enabled

Secretsmanager Secret Without KMS
/secretsmanager.tf: 1
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Secretsmanager Secret Without KMS
/secrets_manager.tf: 12
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Secretsmanager Secret Without KMS
/secrets_manager.tf: 1
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Security Opt Not Set

More results are available on AST platform


Add [Okcoin okcoin.com] #exchange #memo-required GDCDYZ…IIAECE

Address: GDCDYZ42EOC4UBLKLOA6ZR5OSXL5WHLWAJLXJ7O646FQ5EMUG6IIAECE
Tags: exchange memo-required
Title: Okcoin  Domain: okcoin.com
Requested by @rulisboy

Yes

Combined with https://github.com/stellar-expert/public-directory/issues/332


Improve average_precision_metrics

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

Project coverage is 100.00%. Comparing base (a9039de) to head (ed24b97).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #140   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           46        46
  Lines         1091      1092    +1
  Branches       130       129    -1
=========================================
+ Hits          1091      1092    +1

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


Default prefix property is not working anymore

Very recently I noticed that default prefix is not working anymore.
I am using versions:
org.springframework.cloud:spring-cloud-stream:1.0.0.BUILD-SNAPSHOT
org.springframework.cloud:spring-cloud-stream-binder-rabbit:1.0.0.BUILD-SNAPSHOT

Before when I set property spring.cloud.stream.binder.rabbit.default.prefix=customprefix. I could see in RabbitMQ exchange customprefix.input and queue customprefix.input.default. I haven't changed properties file but currently I see this names without prefix. Only input and input.default.

How do I set default prefix?
Can I override default prefix for one channel? How?

Thanks for any help
Mike

Hi,
The default prefix is moved to be a binding specific producer/consumer property and hence it needs to be specified as spring.cloud.stream.rabbit.bindings.<channelName>.consumer.prefix or spring.cloud.stream.rabbit.bindings.<channelName>.producer.prefix based on whether the channel binding is for a producer or consumer.
This change is the result of major refactoring on introducing typesafe producer/consumer properties.
For more detail please refer the doc: https://github.com/spring-cloud/spring-cloud-stream/blob/master/spring-cloud-stream-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc
Thanks

I double checked, it works nice. Thank you!


Delete ignored key from config.json

Since the exercise implementations are all in the exercises directory
we no longer need to ignore any non-exercise directories in the root
of the track.
See https://github.com/exercism/meta/issues/3 for context.

I've created another PR, #64, which normalizes all of the whitespace in the config.json so
that the change in this PR is minimized and easier to see.
If you merge the other PR first, I'll go ahead and rebase this one onto master.
Sorry about the noise!


Uncaught Parse error in .ftpconfig JSON : SyntaxError: Unexpected token

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.0
System: Mac OS X 10.10.4
Thrown From: Remote-FTP package, v0.7.1
Stack Trace
Uncaught Parse error in .ftpconfig JSON : SyntaxError: Unexpected token
At /Users/jamesbiddle/.atom/packages/Remote-FTP/lib/client.js:78

undefined

Commands
     -1:31.1.0 remote-ftp:connect (div.offline)
     -1:22.4.0 remote-ftp:create-ftp-config (atom-text-editor.editor.is-focused)
     -0:55 core:paste (atom-text-editor.editor.is-focused)
 12x -0:53.3.0 core:move-left (atom-text-editor.editor.is-focused)
     -0:50.6.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:49.6.0 core:move-down (atom-text-editor.editor.is-focused)
  2x -0:49.4.0 core:move-right (atom-text-editor.editor.is-focused)
     -0:48.8.0 core:move-down (atom-text-editor.editor.is-focused)
  2x -0:48.4.0 core:move-right (atom-text-editor.editor.is-focused)
  4x -0:47.1.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:44.3.0 core:move-down (atom-text-editor.editor.is-focused)
  4x -0:41.3.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:36.7.0 core:move-down (atom-text-editor.editor.is-focused)
  2x -0:36.1.0 core:move-left (atom-text-editor.editor.is-focused)
     -0:06.2.0 remote-ftp:toggle (atom-text-editor.editor.is-focused)
     -0:00.6.0 remote-ftp:connect (div.offline)

Config
{
  "core": {
    "disabledPackages": [
      "wrap-guide"
    ],
    "themes": [
      "atom-dark-ui"
    ]
  }
}

Installed Packages
# User
Remote-FTP, v0.7.1
atom-alignment, v0.12.1
atom-beautify, v0.28.7
autoclose-html, v0.18.0
autocomplete-php, v0.3.6
highlight-line, v0.11.0
jshint, v1.3.9

# Dev
No dev packages

Please provide a copy of the .ftpconfig file that is causing these issues; it's most likely a syntax error in your config causing the issue. Make sure it contains valid JSON (you can check at http://jsonlint.com/).


[DiskRP] Swagger changes for API version 2019-11-01

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@raych1 I added a directive to suppress the IOPS lint errors mentioned above, but they do not seem to be working. Can you take a look to see if I did this correctly in the readme? Thanks!

Hi @raych1 could you please help us about the LintDiff error?
Property named: 'diskIOPSReadOnly', for definition: 'DiskProperties' must follow camelCase style. Example: 'diskIopsReadOnly'
Here IOPS I believe this is an abbreviation which should be all capitalized, how could we by-pass this?

@pollock4595, @ArcturusZhang , please suppress this rule if necessary. /CC @jianyexi

@raych1 I added a directive to suppress the IOPS lint errors mentioned above, but they do not seem to be working. Can you take a look to see if I did this correctly in the readme? Thanks!

Hi @raych1 could you please help us about the LintDiff error?
Property named: 'diskIOPSReadOnly', for definition: 'DiskProperties' must follow camelCase style. Example: 'diskIopsReadOnly'
Here IOPS I believe this is an abbreviation which should be all capitalized, how could we by-pass this?
@pollock4595, @ArcturusZhang , please suppress this rule if necessary. /CC @jianyexi
@raych1 I added a directive to suppress the IOPS lint errors mentioned above, but they do not seem to be working. Can you take a look to see if I did this correctly in the readme? Thanks!

@pollock4595 , looks like there's typo for suppress in your commit. If the suppression is in same file, it can have multiple items in where array. Please refer to this example.

Hi @raych1 could you please help us about the LintDiff error?
Property named: 'diskIOPSReadOnly', for definition: 'DiskProperties' must follow camelCase style. Example: 'diskIopsReadOnly'
Here IOPS I believe this is an abbreviation which should be all capitalized, how could we by-pass this?
@pollock4595, @ArcturusZhang , please suppress this rule if necessary. /CC @jianyexi
@raych1 I added a directive to suppress the IOPS lint errors mentioned above, but they do not seem to be working. Can you take a look to see if I did this correctly in the readme? Thanks!

@pollock4595 , looks like there's typo for suppress in your commit. If the suppression is in same file, it can have multiple items in where array. Please refer to this example.

@raych1 Sorry I didn't notice that, thanks!

/azp run automation - sdk

Hi @pollock4595 there are conflicts in this PR, after you resolve these, this PR is good to merge

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Hi @pollock4595 there are conflicts in this PR, after you resolve these, this PR is good to merge

@ArcturusZhang This is good to merge when you get a chance.


[Proposal] Use .localhost for TLD in local development

Use .localhost for TLD in local developmen

State: Draft
Created:
Tags:

Context
Bikeshedding about TLD for local development
Resolution

You MUST use .localhost for local development DNS resolution

Links

https://www.rfc-editor.org/rfc/rfc2606#section-2
https://www.pluralsight.com/blog/software-development/choose-internal-top-level-domain-name

From https://www.reddit.com/r/homelab/comments/vlmzc0/comment/idwa8ct/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Best practice is to get a registered domain and then use a subdomain for AD. You can get some very cheap domain names for something like $8 a year.
The AD domain should then look like:
ad.domain.com or internal.domain.com
Using .local has been discouraged since Server 2003 (with the exception of Small Business Server).
Having a registered domain name guarantees unique names.
.local can interfere with apple services like Bonjour which uses .local on a local subnet without DNS lookup.
I also have read that it can interfere with autodiscovery in AD.
Sure, you can probably get by using .local... But if you want to do it right, .local is a bad idea.


Typedoc ci

fixes #1052

this needs a change to the test layout. I'll do this in another pr

this needs a change to the test layout. I'll do this in another pr

please stick a ticket in for it :)

blocked by #1088

I've disabled the docs ci check until further notice because I can't get it working reliably on gha. The paths end up being different than on my local pc
We'll be fine without it atm as the publish workflow regens the docs before publishing

Marking as draft, we can potentially close since we're moving away from typedoc iirc

closing this in favour of new branch system and change to the docs setup


Put numeric config values as numeric

Numerics as strings cause etcd to explode
with div by zero.
Closes: https://github.com/cristifalcas/puppet-etcd/issues/17
Signed-off-by: Bogdan Dobrelya<EMAIL_ADDRESS>

PTAL @cristifalcas @nbyl @KarolisL @MiyamotoAkira

can't fix travis for ruby 1.9.3, it should be removed from the matrix perhaps

Thank you @bogdando . I will probably remove ruby < 2.1


Cannot set custom install_dir or data_dir

Cookbook version
5.4.1
Chef-client version
12.21.26
Platform Details
Windows server 2016
Scenario:
Setting a different/custom install dir or data dir.
Doesnt matter which SQL Server version. Tried SQL 2014 Express, SQL 2016 Express and 2017 express.
Steps to Reproduce:
Set "sql_data_dir" or "install_dir" with a valid path like "c:\sql_data\" and run chef-client.
Expected Result:
That SQL server will install succesfully and in correct directory.
Actual Result:
Chef-client run fails with:
================================================================================
Error executing action install on resource 'sql_server_install[Install SQL Server]'
================================================================================
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
windows_package[Microsoft SQL Server 2014 (64-bit)] (c:/chef/cache/cookbooks/sql_server/resources/install.rb line 163)
had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0, 42, 127, 3010], but received '-2061893624'
---- Begin output of start "" /wait "c:\chef\cache\package\sqlexpr_x64_enu.exe"   /q /ConfigurationFile=c:/chef/cache/ConfigurationFile.ini  & exit %%%%ERRORLEVEL%%%% ----
STDOUT:
STDERR:
---- End output of start "" /wait "c:\chef\cache\package\sqlexpr_x64_enu.exe"   /q /ConfigurationFile=c:/chef/cache/ConfigurationFile.ini  & exit %%%%ERRORLEVEL%%%% ----
Ran start "" /wait "c:\chef\cache\package\sqlexpr_x64_enu.exe"   /q /ConfigurationFile=c:/chef/cache/ConfigurationFile.ini  & exit %%%%ERRORLEVEL%%%% returned -2061893624

Chrisism - I have managed to set directories with my installs..
Have you checked the "Summary.txt"  log file for error details?  I got similar errors to what you are showing above, but for various reasons... it was only when I checked the Summary file that I got the real error...  should be found some where like => C:\Program Files \Microsoft SQL Server\120\Setup Bootstrap\Log\Summary.txt

@chrisism Are you still having this issue or was the input fro @jonoped able to get you working?


Add a test that reveals GCSA2 indexing not working

First off, this PR is meant to fail tests.
I've found this bug in the GCSA2 indexing while trying to maybe use it as a faster aligner for the graph bake-off. I'm going to move forward with the rocksdb aligner rather than trying to fix it now, since it's important that I stop messing about with test runs and get to running a nontrivial number of samples, but I figured that I ought to make a note of the problem here.

Do you have any sense of what's broken?
On Sep 2, 2015 8:22 PM, "adamnovak"<EMAIL_ADDRESS>wrote:

First off, this PR is meant to fail tests.
I've found this bug in the GCSA2 indexing while trying to maybe use it as
a faster aligner for the graph bake-off. I'm going to move forward with the
rocksdb aligner rather than trying to fix it now, since it's important that
I stop messing about with test runs and get to running a nontrivial number
of samples, but I figured that I ought to make a note of the problem here.
You can view, comment on, or merge this pull request online at:
https://github.com/ekg/vg/pull/94
Commit Summary

Add a test that reveals GCSA2 indexing not working

File Changes

A test/reversing/cactus.json
https://github.com/ekg/vg/pull/94/files#diff-0 (21)
A test/reversing/cactus.vg
https://github.com/ekg/vg/pull/94/files#diff-1 (0)
M test/t/06_vg_index.t
https://github.com/ekg/vg/pull/94/files#diff-2 (6)

Patch Links:

https://github.com/ekg/vg/pull/94.patch
https://github.com/ekg/vg/pull/94.diff

—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/pull/94.

Unfortunately not really. It still manages to work on the other reversing
edge test case, so maybe it has something to do with node order?
On Wed, Sep 2, 2015 at 4:21 PM, Erik Garrison<EMAIL_ADDRESS>wrote:

Do you have any sense of what's broken?
On Sep 2, 2015 8:22 PM, "adamnovak"<EMAIL_ADDRESS>wrote:

First off, this PR is meant to fail tests.
I've found this bug in the GCSA2 indexing while trying to maybe use it as
a faster aligner for the graph bake-off. I'm going to move forward with
the
rocksdb aligner rather than trying to fix it now, since it's important
that
I stop messing about with test runs and get to running a nontrivial
number
of samples, but I figured that I ought to make a note of the problem
here.
You can view, comment on, or merge this pull request online at:
https://github.com/ekg/vg/pull/94
Commit Summary

Add a test that reveals GCSA2 indexing not working

File Changes

A test/reversing/cactus.json
https://github.com/ekg/vg/pull/94/files#diff-0 (21)
A test/reversing/cactus.vg
https://github.com/ekg/vg/pull/94/files#diff-1 (0)
M test/t/06_vg_index.t
https://github.com/ekg/vg/pull/94/files#diff-2 (6)

Patch Links:

https://github.com/ekg/vg/pull/94.patch
https://github.com/ekg/vg/pull/94.diff

—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/pull/94.

—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/pull/94#issuecomment-137271858.

I'm also running into problems with graphs that have cycles in them.

I've found the time to look into this, and it seems to be related to 2df58205279335c46e2d49edbd8f7c11ec472126 and the distinct start/end nodes. There's code in that commit to specially handle attaching the end node when the start node is used to break into a cycle. But if you have a graph that has, for example, a graph with two heads and no tails, like this graph I've added here, the start node will be connected but the end node won't. The end node will then produce duplicate and conflicting GCSA2 kmer entries, saying that the overall sing and source aren't connected to anything. This confuses GCSA2 and leads to a crash or an invalid index.
I think the right thing to do is to make the addition of the start and end nodes to the graph only actually add those nodes if they end up connected to anything. A graph with two heads and no tails will get only the start node added, for example. If you're not only looking at the forward kmers, this should work out fine. If you are looking only at the forward kmers, I'm not sure what ought to happen.


Support embeds

Adds UI to each story that exposes an embed code, as well as a new render mode that alters the UI a bit when the story is embedded.
Closes #46

This is very cool!

1 question: How can we make it so the whole embedded story appears, and it doesn't scroll inside the embedded area?
1 feature request: Can the embed code have the option to not show the title of the story at the top? We don't have to add UI for this, it can just be a title=true/false param on the embed src.
1 other question: Thinking about the Insights piece to show this off, I want to make sure: it's possible to embed multiple accounts on 1 page, right?


Create short_d.is-cool.dev.json

Requirements

[v] You have completed your website.
[v] The website is reachable.
[v] The CNAME record doesn't contain https:// or /.
[v] There is sufficient information at the owner field.
[v] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

In the future I will use this domain for college projects, for now it will store links to my college documents on google drive (tests passed, projects, assignments completed).
Link to Website

drago.is-cool.dev
https://dragon-dima.github.io/site/

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA

Is this pull request automatically addressed?  I fixed the domain.


Drop support for CommonJS modules

Changes
WIP
Testing
N/A

Blocker: https://github.com/iTwin/itwinjs-core/pull/7288


i'm prob missing something idk what (error code)

ERROR
PS C:\Users\Mr.Fox>   --key 0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d152c
At line:1 char:5
+   --key 0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d ...
+     ~

Missing expression after unary operator '--'.
At line:1 char:5
+   --key 0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d ...
+     ~~~

Unexpected token 'key' in expression or statement.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpressionAfterOperator
what i tried
i have two keys i tried to also follow this method:
dash-mpd-cli --key<PHONE_NUMBER>3412341234123412341237:12341234123412341234123412341237 \
  --key<PHONE_NUMBER>3412341234123412341236:12341234123412341234123412341236 \
   https://example.com/manifest.mpd -o MyVideo.mp4

with the correct keys one from audio and the other from video without succses these are the  keys for audio and video
9fbfc75592a13fff99ece451a81379fe:b47a1508fe53550399e0a059eb531094
0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d152c
so what is now the correct config i use podman to run it btw

I'm guessing from the error messages that you are using Microsoft Windows and Powershell. It's not clear exactly what commands you have tried, though. Just entering --key 1234:5678 into the shell as you indicate in your first two examples won't do anything useful. The method you show starting with dash-mpd-cli looks correct, but that's not the right command for using the container image.
Try a command of the form described in the documentation for running with podman, but add your --key arguments where the other arguments (like --xslt-stylesheet) are. If that doesn't work, I can't help you unless you specify the exact commandline that you used.
https://emarsden.github.io/dash-mpd-cli/container.html

I  have basicaly 7 keys but iknow only thos that i already provided are the one from audio and video.
this was the command:
podman run --rm --tty -v .:/content ghcr.io/emarsden/dash-mpd-cli  --key 9fbfc75592a13fff99ece451a81379fe:b47a1508fe53550399e0a059eb531094  \  --key 0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d152c  \  --quality best https://my mpd link/.mpd
iknow something is missing idk what  (i dont do the O part)

The "" is for when you type a partial line; you put it at the end of a line to make things easier to read in a script, for example. If you're typing things directly into the terminal you can remove the two "" characters. Otherwise, that command looks correct.

Ah, my "\" was eaten. I meant remove the two "\" characters.

How do i know what key is for the subttitles? or is it just within the mpd  and a quick question i'm not that good with all this but how would that look,with my example? To get the subs?
podman run --rm --tty -v .:/content ghcr.io/emarsden/dash-mpd-cli --key 9fbfc75592a13fff99ece451a81379fe:b47a1508fe53550399e0a059eb531094 --key 0ef95d2d827734ab8d855aff73c6f7bb:7fd8c3c218261f9fa456f4cfbf2d152c --quality best https://my mpd link/.mpd
I rather ask here before i open another issue
BTW the \ where indeed the problem

It depends on your MPD, but most subtitles are not encrypted and do not need a key.
To download subtitles, you'll need to include --write-subs in the commandline (after --quality best for example).
Otherwise, that commandline looks like it should work. Please paste the exact error (add -v to the commandline to get more information) if it doesn't.

With the keys within the comandline and the write subs also tried with only the mpd alone
PS C:\Users\Mr.Fox> podman run --rm --tty -v .:/content ghcr.io/emarsden/dash-mpd-cli --muxer-preference mkv:mkvmerge  --quality best --write-subs https://mylink.mpd -o file.srt
or
C:\Users\Mr.Fox> podman run --rm --tty -v .:/content ghcr.io/emarsden/dash-mpd-cli --muxer-preference mkv:mkvmerge --key 31e69f7874f7334d84ee2fb921fd305b:a76b9b3bde5a773f4ab2ce5215006148 --key f97792222bc83cbea98d7aa38f208acc:a511545c0e5b816c776aa2006301fa12 --key ba52c00c1b4f4294a4e0e87b7b7985b1:453c1d6f6192a95cfde8715bf1fae5ae --key 5dfc821baba4350db455f3a7b996e460:c80599a2c75de87e5fe2ff6869efb096 --key b4aa2ce59fa43f758249db318d78ccfe:21be03aec51f4e66c38477f2c79c0508 --key 6be26c8778c03afb9520e53f1d226c45:574551edaf755f9483fd82a01a61e2b7 --key 4508ffdfb8fc3d6287699fb16d2ff9bd:2f4d2a6b65e3f9ca37f8036390bf1c76 --quality best --write-subs https://mylink.mpd -o file.mkv
[2m] [#################################################>] Muxing audio and video06:59:43  INFO   Muxer preference for mkv is ["mkvmerge"]
06:59:43  INFO   Trying muxer mkvmerge
07:00:24  INFO   Muxing with mkvmerge subprocess succeeded
07:00:24  INFO MP4Box stderr: IsoMedia import dashmpd-subs8PX4FUR.sub - track ID 1 - media type "subt:stpp"
Importing ISO File: |===============     | (76/100)
07:00:24  INFO   Merged subtitles with MP4 container

It depends on your MPD, but most subtitles are not encrypted and do not need a key.
To download subtitles, you'll need to include --write-subs in the commandline (after --quality best for example).
Otherwise, that commandline looks like it should work. Please paste the exact error (add -v to the commandline to get more information) if it doesn't.

Jup what do i do wrong?

The first command is not going to work; it's asking to save audio/video content in a file with an extension corresponding to subtitles.
The second command looks OK, and from the parts you quoted it looks like it worked OK. It included the subtitles as a track in file.mkv, and they should hopefully be playable with a good player (try VLC for example). Why do you say something went wrong?

second command does not work bcs my file is only  (final mkv) same error
[2m] [#################################################>] Muxing audio and video06:59:43 INFO Muxer preference for mkv is ["mkvmerge"] 06:59:43 INFO Trying muxer mkvmerge 07:00:24 INFO Muxing with mkvmerge subprocess succeeded 07:00:24 INFO MP4Box stderr: IsoMedia import dashmpd-subs8PX4FUR.sub - track ID 1 - media type "subt:stpp" Importing ISO File: |=============== | (76/100) 07:00:24 INFO Merged subtitles with MP4 container

164kb big

OK, mkvmerge is reporting success in muxing (merging audio + video streams) but it seems the muxing is not really working.
You might try using ffmpeg to mux, by adding to your commandline --muxer-preference mkv:ffmpeg.
If that doesn't work you can send me the mpd URL (by email if it's private) and I can take a look at what's going wrong.

OK, mkvmerge is reporting success in muxing (merging audio + video streams) but it seems the muxing is not really working.
You might try using ffmpeg to mux, by adding to your commandline --muxer-preference mkv:ffmpeg.
If that doesn't work you can send me the mpd URL (by email if it's private) and I can take a look at what's going wrong.

where can i send the email to? you din't mention the email address

Email<EMAIL_ADDRESS>


IR repeated always 3 times

Good morning Vlad,
I'm using latest version 0.2.4
I'm using it with a rmpro through a function node as your example:
var data = [code];
msg.payload.action = 'send';
msg.payload.data = data;
msg.repeat = 0;
return msg;
The Rmpro node is configured set on msg.payload.
I have tried to change the value for msg.repeat to 1,2.... or even delete the line however it doesn't matter what I set in there the RM always repeat the message 3 times.
There is any way to solve this?
Thanks in advance

Hello, have you solved your problem?  Mine is the same as yours, but mine was sent twice


Add constrained delegation support

I am able to obtain a service ticket for SQL Server using an impersonated credential with Java 8 but when I try to use this with the driver I am getting the next error:

KrbException: The ticket isn't for us (35)

It seems that the problem is in the KerbAuthentication class inside the method intAuthInit(). In this class a context is created for the authentication and this context requests that the initiator's credentials be delegated to the acceptor during context establishment. This behavior is not possible within a constrained delegation scenario.
The service ticket obtained using the impersonated credential is not a forwardable ticket and is not usable for the driver. Changing the next set to false makes the authentication works.
peerContext.requestCredDeleg(true);
I understand this is not the right change since the SQL Server can need to use a delegated credential in order to connect to other SQL Server instances using open delegation, but a change is necessary to set this property to false in a constrained delegation scenery.

Hi @jacobovazquez, can you share the code used for reproducing KrbException?

Hi,
Sure, no problem. You need to change the constant values for the ones of your environment, have the driver in the classpath and execute with Java 8. Let me know if you need more information to reproduce the exception.

best regards,
ImpersonationJDBC.zip

Thanks @jacobovazquez! I'm trying to setup the environment for testing, what was the intermediate server you used, between the client and the SQL Server?

@v-suhame I just created an account in the Active Directory for this purpose, it is not necessary to use a special intermediate server to reproduce the problem. Of course, you need to configure this account to support Constrained Delegation, set an appropriate SPN and create a KeyTab file in order to impersonate the client using this service.

Thanks for confirming @jacobovazquez, I do have the setup you detailed but I'm running into,
Exception in thread "main" GSSException: Failure unspecified at GSS-API level (M echanism level: Attempt to obtain S4U2self credentials failed!)
Caused by: KrbException: S4U2self ticket must be FORWARDABLE
Are you by any chance using OpenJDK9?

No @v-suhame , I'm using the Oracle JDK 8. I think the problem is in the service account configuration in the Active Directory. Since we are using S4U2self, you need to configure the service account to support the transition protocol. In the "Delegation" tab you have to select the option "Use any authentication protocol" instead of "Use Kerberos only".

That worked, I'm able to reproduce the exception, I will investigate it further and keep you updated.

Great that this is being worked on!
Just a question regarding your example code, @jacobovazquez, and the future support for Kerberos Constrained Delegation, @v-suhame: shouldn't the context creation be performed by the JDBC driver (using the Subject of a service principal allowed to delegate and the proxy credentials for the user being delegated), and not the program wrapping the driver?
The few examples I have seen of JDBC drivers explicitly stating that they support Kerberos Constrained Delegation take the delegated user's credential as a property when creating the connection, according to the pattern:
Properties connectionProps = new Properties();
connectionProps.put("userGSSCredential", delegateeGSSCredential);
Connection con = Subject.doAs(serviceSubject,
  (PrivilegedActionException<Connection>) () -> driver.connect(url, connectionProps));

where the delegateeGSSCredential has been obtained via S4U2Self impersonation, or received when the service subject accepted a context initiated by the user.
Is something like this going to be implemented for the MSSQL JDBC driver?

I an agree with you @permagnushansson, both approachs seems ok to me.
In the case of passing the userGSSCredential to the driver, this is the one that has to know the SPN of the SQL Server and generate the service ticket. The client should do as few steps as possible.
On the other hand, you are misusing a Properties objet because you are putting an object different than a String, taking advantage of the bad inheritance of this class.

@jacobovazquez, yes, it would entail using the HashTable nature of the Properties class to transfer a non-String to the driver. I would still prefer this to the hassle of sidestepping the driver by creating a GSSContext directly with the database before calling Driver.connect(..) (which will create a new GSSContext).
For reference, and argument, these are the JDBC driver vendors I have found that do this:
IBM Netezza:
http://www-01.ibm.com/support/docview.wss?uid=swg21997658
Simba Impala:
http://www.simba.com/products/Impala/doc/JDBC_InstallGuide/content/jdbc/im/authenticating/delegatedkerberos.htm
As an application developer, I just want to provide the credentials I have to the driver, and then let the driver manage SPNs and GSSContext negotiations, just like in the unconstrained delegation case.

@permagnushansson that's a good idea. We were just doing the basic investigation, it seems that to fix the issue raised by @jacobovazquez the JDBC driver needs to create the GSSConext using impersonated credential, rather than it being created in the client application. So yes, the implementation is leaning towards your suggestion.

Support for constrained delegation is added in [#178]. Can you please review and test it?
You can add GSSCredential to the driver connection property and pass impersonated credential as value.

I tried both, 4.1 and 4.2, and it is working. Thanks!

It will be helpful if the code you provided for reproducing the issue, can be modified and added under sample code. Can you please tweak it and submit a PR?


Refactor router to separate routing logic from Vue logic

Currently, Framework7 React has its own copy of the routing code in framework7-vue.js, and it also has its own copies of the Pages and View components. The way the routing code is structured, it mixes Vue code in with the routing code. The changes in this PR decouple the routing logic from Vue so that Framework7 React can get rid of all of this duplicate code. Instead, Framework7 React will be able to import the Framework7Router class in the Framework7App component (the counterpart to framework7-vue.js) and fire the route-change event in the same way that it also currently fires the f7init event. I will need to implement a couple more things in the reactifyVue adaptor first, but it should all work just fine.
The real motivation for this PR is what I mentioned in this issue. This PR makes it so that individual components can listen for the route-change event and react appropriately (like the Pages and View component now do in this PR). This makes it easy for additional components like tabs, modals, accordions, etc. to also listen for the route-change event and respond appropriately.

@bencompton thanks! From quick look i like the idea much and looks really great. I'll try to check it more deeper by the end of the week and merge it

@nolimits4web, thanks for the update. I am still working on the code for tab routing that will be built on top of the changes in this pull request and am also still working on integrating the changes into the React version. Feel free to wait until I have those changes ready before merging if you like. I thought I would create a separate pull request for the router refactoring to give you chance to review and try out these changes in isolation and make sure you were okay with it, since it's changing a pretty core part of Framework7 Vue.

Superseded by this pull request.


Show new paper keys in the devices tab after creation

@keybase/react-hackers
We weren't refreshing the devices list after creating a new paper key.

@chromakode I don't use trailing commas in flow types:
Most of our flow types don't have trailing commas, because they predate our trailing commas style and were unincluded in the eslint --fix because eslint doesn't grok flow. Nojima argues we shouldn't have a style we can't enforce, so I leave them out to stay consistent.
What do you think?

@cjb The code I've written and seen in review is putting trailing commas everywhere. I think that it makes sense to use a consistent comma style for new code we write, but not worth spending much time on though since we can't lint it. I wouldn't make a point of *not* using trailing commas to match old code though -- we prefer trailing commas because they make the code a little bit easier to change with in the future. That comment was definitely a :sheep:, just something I noticed while perusing the rest of the code.

👍


Support writing of playlist

This is an implementation to write playlist based on the data structure present in memory.
For convenience it follows the same API structure of the parse methods.
It uses the same handler approach for parsing and writing.
To do so, what was formally a Handler is technically now a Parser. Whereas there is also a Writer interface and a Handler nowadays is the superset providing Parsing and Writing. That way (theoretically) the library could support different stages of supported tags for parsing and writing.
I tried to implement the tags as close to the spec as possible. My testing set might be limited therefore I added the samples from the spec document for further and more intense test cases.
The other PR  #6 (Support for lenient, #3) is applied on this changes in this branch: https://github.com/derjust/open-m3u8/commit/24666bb3e5034deb5a5fe4eaedac0cc6633b0adc

I appreciate all the work, but I don't think I can accept this approach.
The main problem is that handlers should not be both parsers and writers. I see parsing and writing as two very different tasks and they should be kept separate in the code as well. We could rename handlers to parsers though to better distinguish the two. Ideally, the two processes would look something like this:
Parsing
// InputStream -> parse a Playlist -> validate semantics -> return Playlist

PlaylistParser parser = new PlaylistParser(inputStream, format, encoding);

try {
    Playlist playlist1 = parser.parse();
    Playlist playlist2 = parser.parse();
} catch (ParseException exception) {
    // something wrong with the syntax of the playlist
} catch (M3u8Exception exception) {
    // Playlist type was parsed, but there is a semantic error
}

Writing
// Playlist -> validate semantics -> write a Playlist to OutputStream

PlaylistWriter writer = new PlaylistWriter(outputStream, format, encoding);

try {
    writer.write(playlist1);
    writer.write(playlist2);
} catch (M3u8Exception exception) {
    // there is a semantic error
}

Currently on master, semantic validation is mixed together with parsing which is something I would like to change at some point. That is one good reason to not conflate parsing and writing. If I want to refactor the parsing code in the context of the changes in this PR, I would also have to refactor the writing code at the same time. Then maintaining either one of them will become more difficult. It would be better if they were built to be orthogonal to each other sharing only the semantic validation step.
If you would like to discuss this in more depth, you can find me on IRC.
server: freenode
channel: #open-m3u8

For reference, the branch in question is https://github.com/derjust/open-m3u8/tree/writer_squash


TODOs

This is an umbrella issue where we can collectively tackled some problems and improve general open source reading comprehension quality.
Goal
The network is already there. We just need to add more features on top of the current model.

[x] Implement full features stated in the original paper
[ ] Achieve EM/F1 performance stated in the original paper with a single model settings

Model

[x] Increase the hidden units to 128. #15 reported performance increase when the hidden units increased from 96 to 128
[ ] Increase the number of heads to 8
[ ] Add dropouts in better locations to maximize regularization
[ ] Train "unknown" word embedding

Data

[ ] Implement paraphrasing by back-translation to increase the data size

Contribution to any of these issues is welcome and please comment on this issue and let us know if you want to work on these problems.

I have changed the location of dropouts to "after" layer norm from "before" layer norm. It doesn't make sense to drop input channels to layer norm as they normalize across channel dimensions, this will cause distribution mismatch during inference time and training time. We shall see how this improves the model.

To overcome your GPU memory constraints, what about just decreasing batch size?
On a 1080 Ti, I can run 128 hidden units, 8 attention heads, 300 glove_dim, 300 char_dim with a batch size of 12.  At least 16 and above, CUDA is out of memory.  Accuracy seems comparable so far.

You have a valid point, and I would like to know how your experiment goes. I would also suggest trying group normn instead of layer norm as they report better performance with lower batch sizes.

Good suggestion, Min.  Since the paper compares against batch norm, have you found that layer norm generally outperforms batch norm lately?  One could try batch norm also for comparison.  Interestingly the 'break-even' point is about batch size 12 between batch norm and group norm for those paper's conditions.  Layer norm is supposedly more robust to small mini batches compared to batch norm.
Also the conditions from the above comment run fine on a 1070 gpu.
Do you have a sense if model parallelization across multiple gpus is worth it for this type of model?

Hi @mikalyoung , I haven't tried parallelisation across multiple GPUs so I wouldn't know what the best way to go about it is. I heard that data parallelism is easier to get working than model parallelisation. It seems that from #15 using bigger hidden size and bigger number of heads in attention improves the performance, so I would try fitting the bigger model with smaller batches into multiple GPUs.

Right now what is the status reproducing the paper's result?


[Staging & Production] Dataverse: Delete fails when trying to delete a draft file

Steps

Go to a public project with Dataverse authorized (link: https://osf.io/9jtkg/ )
Go to the files tab
Switch the Dataverse folder from Released to Draft
Wait for the folder to re-load with draft files
Click on the red 'x' next to a file to delete it
Hit 'OK' to confirm

Expected
That a dataverse draft file can be deleted from the files tab
Actual
There is an error in the file grid stating that 'Delete failed'. Also the console reports a 500 error.

@rliebz  -- Thoughts? Are we yet running into new version/API issues? Thanks.

The http://thedata.harvard.edu (the Dataverse server we're connected to) has just changed to read-only mode as Dataverse 4.0 is going live. There are a number of backwards incompatible changes that prevent us from using 4.0 in its current state, so the OSF will not be able to upload or delete files until we we merge https://github.com/CenterForOpenScience/osf.io/pull/2426 and the corresponding waterbutler PR, https://github.com/CenterForOpenScience/waterbutler/pull/32.

@sloria with Dataverse 4.0 going live, can we get this included?

I'm hoping #2426 can be merged soon. @rliebz has done some fantastic work. See also #1219.

Agreed @pdurbin -- working it in --- and appreciate the support you have provided here! Thanks!

The read-only issue is resolved, but we will still run into some unintuitive behaviors while https://github.com/IQSS/dataverse/issues/1784 is still open.
Essentially, after publishing a dataset, you have to upload at least one file before you can delete any files.

@nicipfeiffer, was this error only when trying to delete draft dataverse files through the files grid? Or were you also getting errors when deleting files from the file detail page?
Right now, there is no option to delete draft dataverse files through the files grid and deleting from the file detail page is successful.

Closing since dataverse draft files can now be successfully deleted from the files tab.


Use rzls.dll on macOS

https://github.com/dotnet/vscode-csharp/commit/c2666b4af8f1f56bb7eccc773cc923f17a1ef1e6 but for Razor
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2111269
My hypothesis is that now that we use nupkgs, our publishing happens on windows so can't be signed in a mac compatible way.

My hypothesis is that now that we use nupkgs, our publishing happens on windows so can't be signed in a mac compatible way.

Yeah if all your build and packaging happens on Windows mac executables won't be codesignd

My hypothesis is that now that we use nupkgs, our publishing happens on windows so can't be signed in a mac compatible way.

Yeah if all your build and packaging happens on Windows mac executables won't be codesignd

Is there a way we can build the nugets on macos? It seems like we were building on macos before so we have it as part of our pool. Maybe it won't be too hard to build mac on mac?

Is there a way we can build the nugets on macos? It seems like we were building on macos before so we have it as part of our pool. Maybe it won't be too hard to build mac on mac?

I assume its possible.  Probably need to split your signed build into multiple parts (a windows step and mac step) and only build mac binaries on mac.
We haven't done it for Roslyn because its quite a bit of work to split our the signed build.


OasysUnits v1.2.0

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

Project coverage is 12.16%.  Consider uploading reports for the commit 6b48a95 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   13.93%   12.16%   -1.77%
==========================================
  Files         643      671      +28
  Lines      119622   125408    +5786
  Branches     5248     5583     +335
==========================================
- Hits        16665    15259    -1406
- Misses     102736   109932    +7196
+ Partials      221      217       -4

Flag
Coverage Δ

numberExtensions
32.06% <ø> (-0.23%)
:arrow_down:

serialization
7.00% <ø> (-1.75%)
:arrow_down:

unittests
75.96% <ø> (-2.69%)
:arrow_down:

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

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


Use Rubocop to check homebrew/versions style.

It passes brew style so whitelist it to be checked. This will allow more taps to be added in future.

maybe STYLE_CHECKED_TAPS? Well-styled sounds so sartorial.

Well-styled sounds so sartorial.

That was intentional 😆


Task-based Inspection for Mingsai #10

Please review the DD6 in 4.4.4 Data Definitions section of the SRS, could you explain the unit of $V_{salt}$ (t/cm/km)? Are there any unit conversion during the calculation, if so, what are they?

The salt application rate is assumed to be influenced by snowfall amount, so it is normalized for snowfall. It is measured in ton salt/km roadway lane/cm snow. The unit of h_total is cm and the unit of W_lane is m, so no unit conversion is needed.


Add Databricks handler for get_table_types_sql.sql

resolves #768
This is a:

[ ] documentation update
[x] bug fix with no breaking changes
[ ] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation
get_relations_by_pattern throws an error when using the databricks adapter on schemas in a Unity catalog. The error comes from the table having the table_type MANAGED in the information_schema.tables table.
Adding a handler for databricks allows the macro to as expected with data in a Unity catalog.
Checklist

[ ] This code is associated with an Issue which has been triaged and accepted for development.
[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[ ] Redshift
[ ] Snowflake
[x] Databricks

[x] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[x] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[ ] using the limit_zero() macro in place of the literal string: limit 0
[ ] using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

Tests for Redshift and bigquery are failing but the proposed change does not affect them in any way.


Add component to existing application

One of the original goals for templates was to be able to add new components to existing applications.  For example:
$ spin new http-empty myapp
$ cd myapp
$ spin add http-rust ui
$ spin add http-rust api
$ spin add static-fileserver assets
$ spin add static-fileserver downloads

The user experience should be similar to spin new: the difference is that the new component manifest should be added to the existing spin.toml, instead of a new spin.toml being created.
Note this creates the constraint that new components must have the same trigger as the spin.toml to which they are being added.

Fixed via #889


Compatibility with Django 1.3

Hi,
Is this compatible with Django 1.3?

Maybe. I only test and fix issues with currently supported and upcoming Django releases, so right now 1.6, 1.7, and 1.4ESR. That doesn't mean it won't work, necessarily.


Updated: goland 192.6817.25

Newer version of goland (192.7142.47) is now available in master. 500a745d31f46049e026e100994d9fc789fa4d83


Create prime.html

html/javascript to obtain result on browsers

what's the point of this app?
its actually javascript but in html


CUDA RuntimeError during losses.backward()

❓ Questions and Help
Hi. Thank you for your great efforts.
I'm trying to use my own dataset which only has a single class.
I implemented e.g. maskrcnn/data/datasets/mydata.py following README,
set ROI_BOX_HEAD.NUM_CLASSES=2, and updated some other files correspondingly.
(Detailed description is omitted since the error can be simply reproduced in a different way as described below)
Error message
Traceback (most recent call last):
  File "tools/train_net.py", line 174, in <module>
    main()
  File "tools/train_net.py", line 167, in main
    model = train(cfg, args.local_rank, args.distributed)
  File "tools/train_net.py", line 73, in train
    arguments,
  File "/maskrcnn-benchmark/maskrcnn_benchmark/engine/trainer.py", line 76, in do_train
    losses.backward()
  File "/miniconda/envs/py36/lib/python3.6/site-packages/torch/tensor.py", line 106, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/miniconda/envs/py36/lib/python3.6/site-packages/torch/autograd/__init__.py", line 93, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: cublas runtime error : the GPU program failed to execute at /opt/conda/conda-bld/pytorch-nightly_1549566635986/work/aten/src/THC/THCBlas.cu:259

How to reproduce

Build docker image & setup maskrcnn-benchmark
Due to #167, I commented out https://github.com/facebookresearch/maskrcnn-benchmark/blob/13b4f82efd953276b24ce01f0fd1cd08f94fbaf8/docker/Dockerfile#L51
And run nvidia-docker build -t maskrcnn-benchmark docker/
Afterward, run python setup.py build develop inside the container

Add this line
target.extra_fields['labels'].clamp_(0, 1)
above here:
https://github.com/facebookresearch/maskrcnn-benchmark/blob/13b4f82efd953276b24ce01f0fd1cd08f94fbaf8/maskrcnn_benchmark/data/datasets/coco.py#L91-L96
This will reduce 80 classes into a single foreground class

Place COCO dataset in /maskrcnn-benchmark/datasets/coco

Run (single GPU)

python tools/train_net.py \
    --config-file "configs/e2e_faster_rcnn_R_50_FPN_1x.yaml" \
    MODEL.ROI_BOX_HEAD.NUM_CLASSES 2 \
    SOLVER.IMS_PER_BATCH 2

I found that increasing NUM_CLASSES makes a few iterations successful.
What am I missing? Please help!

Hi,
I think you might have a buggy version of PyTorch.
Are you using a PyTorch nightly? If yes, which version?
Also, can you try installing either 1.0.0 or 1.0.1?

Yes. It turned out to be a problem with PyTorch-nightly.
I was using it because Docker installs it.
The previous version of PyTorch was
>>> torch.__version__
'1.0.0.dev20190207'

After I replaced this line
https://github.com/facebookresearch/maskrcnn-benchmark/blob/327bc29bcc4924e35bd61c59877d5a1d25bb75af/docker/Dockerfile#L35
with
RUN conda install -y pytorch -c pytorch \
, the problem was resolved.
Now the PyTorch version is
>>> torch.__version__
'1.0.1.post2'

Thanks a lot!

Cool, great! For information, the latest PyTorch master has fixed the aforementioned problem

For anyone else running into this issue, I was able to solve it by installing the latest pytorch (pytorch-nightly still seemed to give this error, even recent versions, but I may have just been screwing something up), and then reinstalling this library. I didn't reinstall the library at first, and it caused some headaches.
In short,
conda uninstall pytorch-nightly
conda install pytorch -c pytorch
cd path/to/maskrcnn-benchmark
python setup.py build develop

Again, for me, it's important to run that last step. Seems kinda obvious in hindsight, but not at the time :)

Yes, whenever we update pytorch we need to recompile maskrcnn-benchmark, which generally involve removing the build folder as well

Great reminder! I did that reflexively, but forgot to note it. Just added it to the steps above, along with the .egg-info file.


Tinker with a Linked List based Sequencer

Fixes #16
this time, from the CORRECT to2local directory.

committed from the wrong workspace. using a merge in case i end up with a mix of good and bad.


How to displaying Multiselect in Swagger UI?

Hi there,
I notice in the public Petstore swagger example, "Find Pet by Status", you can provide a multiselect list of strings.  http://petstore.swagger.io/#!/pet/findPetsByStatus
How do we do that with Swashbuckle?
I've tried each of an array of enums, List of enums, IEnumerable of  enums, and enabled " c.DescribeAllEnumsAsStrings();" in Swashbuckle Config.
Thanks, and thanks for a brilliant tool!
Tim

I used attributes, and fixed values, see: SwaggerEnumValue in
https://github.com/valentinedwv/CuahsiWOFSwagger/blob/master/Wb/Wb/SwaggerDefaultValues.cs


BufferroosDataStore does not need all function

I think BufferroosDataStore should have just common function (for example : getUsers).

It's because of the interface, please see https://github.com/bufferapp/clean-architecture-koin-boilerplate for a simplified version


dict.iteritems is not yet implemented in Skulpt

Steps to reproduce:

Open any problem.
Type the following in the coding window, and run it:

    d = {'a': 1}
    for x, y in d.iteritems():
        return x

You'll get the following error trace:
NotImplementedError: dict.iteritems is not yet implemented in Skulpt on line 3

If we keep using Skulpt, we might want to consider implementing this upstream. A possible local hack would be to substitute items() for iteritems() (which does work in Skulpt, but presumably has runtime complexity implications).

Implementing upstream doesn't seem too complicated from a cursory glance at the code. The dict class doesn't do anything particularly complicated. I'm actually wondering what the catch is, since it seems like it'd be trivial for them to have implemented already.
It might be quicker and easier, short term, to simply have the client download a portable, minimal version of python on launch, rather than using skulpt to compile and execute an incomplete version of the language.


Use node 16.x

It required converting mocha tests code into async since @wdio/sync is deprecated starting with node v16. It removed the dependency on fibers and on node-gyp + python indirectly though which is a great thing.
Also moved away from node-sass to sass since node-sass is deprecated which addresses #762 .
It is also a beginning of Maputnik upgrade #775
Feel free to share comments.

Was looking into why test/standalone-chrome keeps failing all the time and apparently there might be a problem with sandbox + /dev/shm size for Docker image. Will try to use runner machine instead of Docker images.

Thank you @pathmapper ! This is actually my first contribution to OSS in my life. I didn't expect such great experience! 😄
Hope that it will stay along with more PRs that will come 😉

@propheel glad you chose this project :smile:
If you would like to tell something about what you're using Maputnik for, please feel free to post it in https://github.com/maputnik/editor/issues/164.


Radio Reboot on Dev RC

Since installing latest Rev I am getting big connection issues.
Rebooting to fix radio errors!
The system is going down for reboot at Tue 2017-11-14 23:52:02 PST!
Keep getting this repeated on my rig that has a TI stick. Trying to step back and see what is causign it.

On My explorer board rig, when looking at Pump Loop Tail I get this:
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!) mmtune: TypeError: Odd-length string

When I then run mmtune I get this on the explorer board:
retry 0  (Do you need to run 'export RFSPY_RTSCTS=0' first?)

Double-check your serial number: I think I got Odd-length string when I typo'd my serial number as 5 digits instead of 6...

I always copy paste the entries so this is unlikely - I am stepping through to try to reproduce.
I was able to resolve by switching and synching master branch, installing, switching and synching to dev, running npm run global-install and then installing.
Doesn't help too much. WIll report back with what I find.

Closing for now.  Please re-open if you see this again.


use Spring Boot 1.5.8

@yungez

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   79.09%   79.09%
=======================================
  Files          15       15
  Lines         440      440
  Branches       60       60
=======================================
  Hits          348      348
  Misses         54       54
  Partials       38       38

Continue to review full report at Codecov.

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


Bevy 0.14 crash: called Option::unwrap() on a None value

Bevy version
v0.14
[Optional] Relevant system information
cargo 1.79.0 (ffa9cf99a 2024-06-03)

The app crashes before printing the adapter info, but:

Linux (Pop!_OS)
NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER]

What you did
Run my game after updating to Bevy 0.14.
See the full source code here: https://github.com/TimJentzsch/invasion_by_nightfall/pull/5
What went wrong
The app crashes immediately.

Stacktrace
    Finished `dev` profile [optimized + debuginfo] target(s) in 8.21s
     Running `target/debug/invasion_by_nightfall`
thread 'main' panicked at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_state-0.14.0/src/app.rs:74:67:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0: rust_begin_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:652:5
   1: core::panicking::panic_fmt
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panicking.rs:72:14
   2: core::panicking::panic
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panicking.rs:146:5
   3: core::option::unwrap_failed
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/option.rs:1984:5
   4: core::option::Option<T>::unwrap
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/option.rs:932:21
   5: <bevy_app::sub_app::SubApp as bevy_state::app::AppExtStates>::init_state
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_state-0.14.0/src/app.rs:74:67
   6: <bevy_app::app::App as bevy_state::app::AppExtStates>::init_state
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_state-0.14.0/src/app.rs:186:9
   7: <invasion_by_nightfall::core::CorePlugin as bevy_app::plugin::Plugin>::build
             at ./src/core/mod.rs:26:9
   8: bevy_app::app::App::add_boxed_plugin::{{closure}}
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_app-0.14.0/src/app.rs:456:55
   9: core::ops::function::FnOnce::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5
  10: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panic/unwind_safe.rs:272:9
  11: std::panicking::try::do_call
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:559:40
  12: std::panicking::try
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:523:19
  13: std::panic::catch_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panic.rs:149:14
  14: bevy_app::app::App::add_boxed_plugin
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_app-0.14.0/src/app.rs:456:22
  15: <P as bevy_app::plugin::sealed::Plugins<bevy_app::plugin::sealed::PluginMarker>>::add_to_app
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_app-0.14.0/src/plugin.rs:158:17
  16: <(S0,S1,S2,S3) as bevy_app::plugin::sealed::Plugins<(bevy_app::plugin::sealed::PluginsTupleMarker,P0,P1,P2,P3)>>::add_to_app
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_app-0.14.0/src/plugin.rs:184:23
  17: bevy_app::app::App::add_plugins
             at /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_app-0.14.0/src/app.rs:552:9
  18: invasion_by_nightfall::main
             at ./src/main.rs:14:5
  19: core::ops::function::FnOnce::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I would expect either for there to be no crash, or to get an error message explaining what I did wrong.

I ran into this panic as well. In my case, the problem was not adding StatesPlugin.
I agree that the error message is quite bad, and we probably shouldn't be crashing, but logging an error/warning or something.

I ran into this panic as well. In my case, the problem was not adding StatesPlugin to my app. (at a glance, looks like the same issue for you)
I agree that the error message is quite bad, and we probably shouldn't be crashing, but logging an error/warning or something.

Ah, you are correct.
Actually, I already added DefaultPlugins which contains StatesPlugin, but apparently in the wrong plugin of my app, causing it to get loaded too late.
Kinda surprising to me, I thought plugins were assembled before the rest.
In any case, I will adjust the issue to reflect that this is more of a docs/error message problem.

I ran into this error message in 0.14. I was calling init_state before add_plugins (with the DefaultPlugins). That worked fine prior to 0.14.  The fix was to move init_state to after the add_plugins call

Closing as resolved due to #14160.


NLS chars not accurately dealt with

NLS characters are not dealt with accurately, need to use k-functions.

Hi @stephanweigandt ,
And this is another issue that has been reported against your DIAP entry.
I think you were already working an adding this feature as well, right?

Created new pull request to address this issue!

Pull request that addresses this issue is: #23
(TIP: GitHub markup supports autolinked references to issues and pull requests)


Errno::EPIPE: Broken pipe

Hi Team,
I am trying to send notifications to multiple devices , but it fails and throws the error below:
Errno::EPIPE: Broken pipe
    from /Users/mohantysan/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/1.9.1/openssl/buffering.rb:318:in `syswrite'
    from /Users/mohantysan/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/1.9.1/openssl/buffering.rb:318:in `do_write'
    from /Users/mohantysan/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/1.9.1/openssl/buffering.rb:336:in `write'
    from /Users/mohantysan/.rvm/gems/ruby-1.9.3-p362@echo/gems/grocer-0.6.1/lib/grocer/connection.rb:24:in `block in write'
    from /Users/mohantysan/.rvm/gems/ruby-1.9.3-p362@echo/gems/grocer-0.6.1/lib/grocer/connection.rb:56:in `with_connection'
    from /Users/mohantysan/.rvm/gems/ruby-1.9.3-p362@echo/gems/grocer-0.6.1/lib/grocer/connection.rb:23:in `write'
    from /Users/mohantysan/.rvm/gems/ruby-1.9.3-p362@echo/gems/grocer-0.6.1/lib/grocer/pusher.rb:8:in `push'

Code:
notifications = Array.new
message = am.message.body
am.app.devices.find_each(:batch_size => 1000) do |device|
  notification = Grocer::Notification.new(
    device_token:      device.token,
    alert:             message,
    badge:             42,
    sound:             "siren.aiff",         # optional
    expiry:            Time.now + 60*60,     # optional; 0 is default, meaning the message is not stored
    content_available: true                  # optional; any truthy value will set 'content-available' to 1
  )
  notifications << notification
end

puts pusher = Grocer.pusher(
  certificate: "/Users/mohantysan/Documents/Certificates/SecureApp.pem",      # required
  passphrase:  "",                       # optional
  gateway:     "gateway.sandbox.push.apple.com", # optional; See note below.
  port:        2195,                     # optional
  retries:     1                         # optional
)

notifications.flatten.each do |notification|
  puts notification.inspect
  puts pusher.push(notification)
end

Can you also check the Feedback channel and see if any errors are being returned? Perhaps you're sending a flood of invalid notifications and so Apple is closing the connection and then blocking you?

@jyoti2shine Any updates? I'm going to close due to inactivity, but please re-open if you have more info.


⚠ Samsung has degraded performance

In ea1981f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2394 ms

Resolved: Samsung performance has improved in cf3cf7a.


fix issue #105

Update project to lattest version, android studio 2.0, api 23
fix issue #105.

You mentioned #105. Is that fixed in this PR?

Yes, I have tested it.
2016年4月16日 下午2:00于 "Mathew Kurian"<EMAIL_ADDRESS>
You mentioned #105
https://github.com/bluejamesbond/TextJustify-Android/issues/105. Is
that fixed in this PR?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/bluejamesbond/TextJustify-Android/pull/114#issuecomment-210728158


Fix subset_sorting when sorting interface has recording registered

In BaseSortingExtractorInterface.subset_sorting(), if the sorting interface has recording registered, there's a chance that 1.1 * max_min_spike_time is greater than the number of samples in the recording, which causes this check to fail in SpikeInterface. Fixed by capping end_frame at the number of samples in the recording if one is registered.

Why do we have the 1.1 at all?

Why do we have the 1.1 at all?

I believe the reasoning was just to get a 'little bit' more spike timing data from all units. Clipping at the latest first spike time was otherwise usually too early to really see any spiking behavior
Out of all the subsetting methods this is the most heuristic, I suppose due to the irregular stochastic nature of the data type itself. Open to other ideas

I suppose the best interpreted setting of all stubbing anywhere would to report 'some small static amount (~10 MB per data stream?) of data that is likely some smaller percentage of the total data size'
So calculating how many spikes that is, equating that to how many frames gets you that many spikes, might be the best way to go
Might be something easier to do in the new backend refactor

@felixp8 Can you think of a way to make a test for this?

Great, thanks!


Error when trying to execute commands

Hi, I'm having an issue when trying to execute parallel and stress commands.
When I execute run-parallel with two specific files it runs well until the end and then this appears:
Command completed in 14 seconds.

D:(...)\node_modules\cypress-utils\node_modules\async\asyncify.js:114
            throw e;
            ^

TypeError: results.filter(...).map(...).flat is not a function
    at computeResults (D:(...)\node_modules\cypress-utils\index.js:88:84)
    at handleResults (D:(...)\node_modules\cypress-utils\index.js:128:28)
    at err (D:(...)\node_modules\cypress-utils\node_modules\async\internal\map.js:27:9)
    at wrapper (D:(...)\node_modules\cypress-utils\node_modules\async\internal\once.js:12:16)
    at iterateeCallback (D:(...)\node_modules\cypress-utils\node_modules\async\internal\eachOfLimit.js:63:24)
    at D:(...)\node_modules\cypress-utils\node_modules\async\internal\onlyOnce.js:12:16
    at _iteratee (D:(...)\node_modules\cypress-utils\node_modules\async\internal\map.js:24:13)
    at invokeCallback (D:(...)\node_modules\cypress-utils\node_modules\async\asyncify.js:111:9)
    at promise.then.value (D:(...)\node_modules\cypress-utils\node_modules\async\asyncify.js:103:9)`

When I execute the stress command as npx cypress-utils stress-test business --trialCount 12 --threads 4, the same error appears:
Array(...).fill(...).flat is not a function

Do you have any idea about this and how to solve it?

Hey Sergio 👋🏻
The first issue is a bit involved, and it's not clear what's causing the issue.
I created a branch named issue-8-debug that you can checkout and reply with the output. I've added some console logging that should help us find the issue.
As for the second issue, I'm almost certain you are running this from a version of NodeJS older than 11.0.
If you look at the compatibility charts for Array#fill and Array#flat, you'll see that the minimum Node versions are 4.0.0 and 11.0.0 respectively.
Try checking your current version of NodeJS with node --version and upgrade it if necessary. Let me know how it goes, I can add a minimum Node version in the package.json to mitigate this issue for others.

I've published<EMAIL_ADDRESS>which enforces the user to have a compatible Node version.
Going to close this issue as resolved, but please leave a comment if you continue to have issues!


Add a check for a perfect initial rewiring before applying rewiring techniques

Right now, quilc will make its best guess for a good rewiring, even when the identity mapping requires no swaps at all. This can sometimes cause unnecessary swaps.

@ecpeterson do you have an example of when this happens?

Yes: have a look at benchmarking/quil-available/0020q-0000143-3f7b88e4-sampling_quinoa.quil on Acorn (a/k/a (build-skew-rectangular-chip 0 4 5)). If you run it with PRAGMA INITIAL_REWIRING "NAIVE" prefixed, it'll compile with no SWAPs. If you run it with the supposedly more intelligent PRAGMA INITIAL_REWIRING "PARTIAL", it'll compile with plenty of SWAPs.

I'm not confident how this could be solved. My initial thought was to test that the adjacent qubits to each used logical qubit were in the set of used logical qubits: if yes, use the identity rewiring. But that's not quite right.
Hints @ecpeterson?

There's more than one way to skin this cat, but I was imagining a check in prog-initial-rewiring along the following lines:
(when (loop :for instr :across (parsed-program-executable-code parsed-prog)
                       :always (or (not (typep instr 'gate-application))
                                   (lookup-hardware-object-by-qubits chip-spec (application-arguments instr))))
  ;; install the NAIVE rewirer, which will effect no SWAPs
  ;; break early)
;; otherwise, continue making decisions

There might be some fuss in that disjunction about dead qubits.

I think this is closed by #380.


Add text chat function

Added a text chat function that can be used alongside the microphone. It doesn't interfere with current functionality, it's just an optional extra way of interacting with the chat.
FYI: I've never made a pull request before, and I also used AI, so please review thoroughly.
Pre-commit passes and I've tried to check different ways it can be used, it all works fine for me. Hopefully this is useful to someone even if it isn't merged.

Thank you for your PR, it's a nice addition


SSR error - "SyntaxError: Unexpected token 'export'" with<EMAIL_ADDRESS>

Describe the bug
I get the following error message in the node environment with<EMAIL_ADDRESS>(node:70395) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
12:02:02 PM [vite] Error when evaluating SSR module /src/apollo/apollo.ts: failed to import "@vue/apollo-option"

12:02:02 PM [vite] Error when evaluating SSR module /src/apollo/main.ts:

12:02:02 PM [vite] Error when evaluating SSR module /src/apollo/entry-server.ts:

/Users/packman/code/behance/sandbox/gql-cache-prototypes/node_modules/@vue/apollo-option/dist/vue-apollo-option.esm.js:1500
export { ApolloProvider, createApolloProvider };
^^^^^^

SyntaxError: Unexpected token 'export'
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1195:20)
    at Module._compile (node:internal/modules/cjs/loader:1239:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)

This bug only happens on 4.0.0-beta.4. It works fine on 4.0.0-beta.2
Versions
vue: 3.2.47
@vue/apollo-option: 4.0.0-beta.4,
@apollo/client: 3.7.11
Additional Context
I am importing entry-server.ts with vite.ssrLoadModule

Workaround that works for me is to insert "type": "module" into the package.json and prefixing the exports with "./"
...
"type": "module",
"exports": {
    ".": {
      "types": "./dist/esm/index.d.ts",
      "import": "./dist/esm/index.js",
      "require": "./dist/cjs/index.js"
    },
    "./*": "./*"
  },
...

Also changeing from
import * as serializeJs from 'serialize-javascript';
to
import serializeJs from 'serialize-javascript';
in the esm/index.js

Is there a fix planned for the next beta-5, rc or major release @Akryum ?

I'm still experiencing issues directly related to esm imports with this package. It seems to only work when the steps above (https://github.com/vuejs/apollo/issues/1469#issuecomment-1494960430) are manually changed in node_modules.


Supoort grouping metrics by frontend, backend and server names

See the changes in README.rst for a detailed explanation of the
new functionality.
This commit introduces the following configuration options:

[graphite] group-namespace
[graphite] group-namespace-double-writes
[frontend-groups] section
[backend-groupss] section
[server-groups] section

Additionally, the haproxystats-process daemon now accepts the
--dir command line option.

Hi,
I am reviewing it.
Thanks,
Pavlos


does this work to imitate anyone's voice?

Virtually anyone, but you should be clear with the meaning of the term “imitating”. Our work enables us to convert anyone’s speech into a timbre of limited number of speakers, which are included in training set. (a.k.a. Any-to-Many conversion)
fyi please be sure to check our new work: Assem-VC.


Does this not work with existing Distribution Id?

I have the below code
and get the following error
Could not find resource with logical name "E3QDJSNRIE!!!!"
Does this not work with existing Distribution Id?
plugins:

'@silvermine/serverless-plugin-cloudfront-lambda-edge'

service: iam-lambdaedge-api # NOTE: update this with your service name
frameworkVersion: ">=1.36.3"
provider:
name: aws
runtime: nodejs8.10
memorySize: 1024 # overwrite default memory of 1024
versionFunctions: false
stage: ${opt:stage, 'dev'}
region: us-east-1
timeout: 7
stackTags: # Optional CF stack tags
application: ${self:provider.stage} - ${self:service.name}
tags: # Optional service wide function tags
stage: ${opt:stage, self:provider.stage}
custom:
distribution:
prod: ETWLECI9S!!!! #not real one
dev: E3QDJSNRIE!!!!
stage: ${opt:stage, self:provider.stage}
functions:
redirecthandlerLG:
name: "${self:provider.stage}-${self:service.name}-LG"
handler: edgeHandler.edgeHandlerLG
memorySize: 1024
timeout: 4
lambdaAtEdge:
-
distribution: "${self:custom.distribution.${self:custom.stage}}"
eventType: 'viewer-response'
-
distribution: "${self:custom.distribution.${self:custom.stage}}"
eventType: 'viewer-request'
-
distribution: "${self:custom.distribution.${self:custom.stage}}"
eventType: 'origin-request'

See #15


fix(location): throw a MinErr when base path has the wrong case #4082

If the user inputs a url where the base path has the wrong case, an MinErr is now thrown instead of a stack trace.
From the issue:
This issue is common when serving files from a case-insensitive filesystem, where the files may serve from /Base/ and /base/ but the href is set as /base/. This behavior is preferable because it encourages developers to follow the best practice of treating their files and URLs as case-sensitive.
Fixes #4082 #ng-europe

I have moved this to 1.5 as it is really a breaking change.
@btford I have unassigned you for now as it seems likely that you have other things on your plate.

This is a breaking change and so it cannot be landed now even if we felt it would be worth it, which it probably isn't since we should not necessarily restrict app developers in this way.