text:
update ref arch for GA

Description

Update date
Set metadata to allow publishing to production in Cloud docs.

Release required?

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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

GitHub release
v1.1.0

Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
1c3409f -> f497c08

github.com/IBM/go-sdk-core/v5
require
minor
v5.16.5 -> v5.17.0

github.com/IBM/platform-services-go-sdk
require
patch
v0.62.5 -> v0.62.6

Release Notes

IBM/go-sdk-core (github.com/IBM/go-sdk-core/v5)
v5.17.0
Compare Source
Features

send user-agent header with auth token requests (#216) (90f0ba5)

IBM/platform-services-go-sdk (github.com/IBM/platform-services-go-sdk)
v0.62.6
Compare Source
Bug Fixes

Usage Reports: re-gen service after recent API changes (#320) (aad1c24)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

source: gharchive/pull-request

repo: terraform-ibm-modules/terraform-ibm-cbr

license_type: permissive

license_source: github-api


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
cc55b9b -> 69b1da8

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.29.8 -> v1.30.0

terraform-ibm-modules/common-pipeline-assets
action
patch
v1.21.6 -> v1.21.7

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.30.0
Compare Source
Features

Added Opentofu support (#780) (e4ee8d7)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.21.7
Compare Source
Bug Fixes

Move Pipeline Failure Notifications to Separate Workflow (#655) (38c8c30)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
0e4338f -> d50e7e6

terraform-ibm-modules/common-pipeline-assets
action
patch
v1.22.2 -> v1.22.3

Release Notes

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.22.3
Compare Source
Bug Fixes

Revert "Update post-usage.yml (#693)" (#696) (7d333b0)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
fafc30b -> 05291e2

github.com/gruntwork-io/terratest
require
patch
v0.46.1 -> v0.46.5

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.23.14 -> v1.23.15

Release Notes

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.46.5
Compare Source
Modules affected

k8s

Description

Added RestConfig field to extend auth options for Kubernetes client.

Special thanks

Special thanks to the following users for their contribution!

@kirecek

Related links

https://github.com/gruntwork-io/terratest/pull/1354

v0.46.4
Compare Source

Description

Updated dependency github.com/docker/docker from 20.10.7+incompatible to 24.0.7+incompatible

Related links

https://github.com/gruntwork-io/terratest/pull/1362

v0.46.3
Compare Source

Description

Updated dependency google.golang.org/grpc from 1.51.0 to 1.56.3

Related links

https://github.com/gruntwork-io/terratest/pull/1360

v0.46.2
Compare Source

Description

Updated dependency github.com/docker/distribution from 2.7.1+incompatible to 2.8.2+incompatible

Related links

https://github.com/gruntwork-io/terratest/pull/1286

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.23.15
Compare Source
Bug Fixes

deps: update gomod (#691) (076b114)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
64fc718 -> 16e53c8

github.com/gruntwork-io/terratest
require
minor
v0.46.16 -> v0.47.0

Release Notes

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.47.0
Compare Source
Modules affected

packer
aws
helm
azure

Description

Added support for Packer 1.10
Fixed error checking in Azure
Fixed tests and documentation for helm, aws, packer modules

Related links

https://github.com/gruntwork-io/terratest/pull/1395
https://github.com/gruntwork-io/terratest/pull/1419

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.8.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.17.0

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
minor
4.16.11 -> 4.17.0

Release Notes

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.17.0
Compare Source
Features

exposed the ability to set the provider_visibility in the DA. Learn more. (#586) (53580ae)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline


text:
chore(deps): update common-dev-assets digest to dd53916

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
5fa5912 -> dd53916

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.11.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
5f5fd35 -> 5cf7d9c

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.42.5 -> v1.42.6

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.42.6
Compare Source
Bug Fixes

deps: update module github.com/gruntwork-io/terratest to v0.48.1 (#905) (511dc17)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

github.com/gruntwork-io/terratest
v0.48.0 -> v0.48.1

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

github.com/gruntwork-io/terratest
v0.48.0 -> v0.48.1

/run pipeline

/run pipeline


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
ce8fceb -> 0bb740c

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.30.3 -> v1.30.5

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.30.5
Compare Source
Bug Fixes

deps: update gomod (#788) (3f7c30b)

v1.30.4
Compare Source
Bug Fixes

create schematics tar file in correct temp dir (#783) (f0cd2ce)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
2015ae9 -> d6af6b1

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.31.8 -> v1.33.2

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.33.2
Compare Source
Bug Fixes

nil to NULL (#814) (3522e90)

v1.33.1
Compare Source
Bug Fixes

bugs (27bbbf0)

v1.33.0
Compare Source
Features

enhancements to cloud project and stack testing (#812) (a8342e2)

v1.32.0
Compare Source
Features

added variable for passphrase protected ssh keys. (#771) (8dee786)

v1.31.9
Compare Source
Bug Fixes

Logging improvements (#807) (11a3f1a)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.31.8

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.31.7 -> v1.31.8

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.31.8
Compare Source
Bug Fixes

deps: update gomod (#809) (5f06800)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 4.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to d583c56

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
eec8f4a -> 5e148b9

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-resource-group to v1.0.5

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-resource-group
module
patch
v1.0.4 -> v1.0.5

Release Notes

terraform-ibm-modules/terraform-ibm-resource-group
v1.0.5
Compare Source
Bug Fixes

deps: update terraform ibm to v1.49.0 (#160) (711118b)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-observability-instances to v2.10.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-observability-instances
module
minor
v2.9.2 -> v2.10.0

Release Notes

terraform-ibm-modules/terraform-ibm-observability-instances (github.com/terraform-ibm-modules/terraform-ibm-observability-instances)
v2.10.0
Compare Source
Features

updated the required terraform version range to >= 1.0.0, < 1.6.0 (#368) (0e33928)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.9.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/base-ocp-vpc/ibm (source)
module
patch
3.11.0 -> 3.11.3

terraform-ibm-modules/key-protect-all-inclusive/ibm (source)
module
patch
4.4.1 -> 4.4.2

terraform-ibm-modules/landing-zone-vpc/ibm (source)
module
minor
7.11.0 -> 7.13.1

terraform-ibm-modules/observability-agents/ibm (source)
module
minor
1.12.2 -> 1.15.1

terraform-ibm-modules/observability-instances/ibm (source)
module
patch
2.10.0 -> 2.10.1

Release Notes

terraform-ibm-modules/terraform-ibm-base-ocp-vpc (terraform-ibm-modules/base-ocp-vpc/ibm)
v3.11.3
Compare Source
Bug Fixes

removed alb-oauth-proxy and istio from allowed addons as they are not supported on OCP (#308) (c26e55e)

v3.11.2
Compare Source
Bug Fixes

Onboard to IBM Cloud catalog registry (#300) (1d0b0ff)

v3.11.1
Compare Source
Bug Fixes

removed support for deprecated OCP version 4.10 (#298) (3208f2d)

terraform-ibm-modules/terraform-ibm-key-protect-all-inclusive (terraform-ibm-modules/key-protect-all-inclusive/ibm)
v4.4.2
Compare Source
Bug Fixes

deps: update terraform-module (#371) (e1489e9)

terraform-ibm-modules/terraform-ibm-landing-zone-vpc (terraform-ibm-modules/landing-zone-vpc/ibm)
v7.13.1
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/resource-group/ibm to v1.1.4 (#671) (f03b300)

v7.13.0
Compare Source
Features

cleanup, updated variables and basic example (#670) (b1a38d0)

v7.12.0
Compare Source
Features

added support to create resources in existing VPC and use existing subnets. See Existing VPC and subnets Example (#638) (f0c5b08)

terraform-ibm-modules/terraform-ibm-observability-agents (terraform-ibm-modules/observability-agents/ibm)
v1.15.1
Compare Source
Bug Fixes

deps: update icr.io/ext/logdna-agent docker tag to v3.9.0-20231204.f89f0d6c94267329 (#242) (e4eea2b)

v1.15.0
Compare Source
Features

deps: update icr.io/ext/sysdig/agent docker tag to v12.18.0 (#236) (2aee2f5)

v1.14.0
Compare Source
Features

deps: update icr.io/ext/logdna-agent docker tag to v3.9.0-20231127.1da2b0706ea2d823 (#235) (baf7329)

v1.13.0
Compare Source
Features

added support for LogDNA metadata filtering (#226) (51e1325)

terraform-ibm-modules/terraform-ibm-observability-instances (terraform-ibm-modules/observability-instances/ibm)
v2.10.1
Compare Source
Bug Fixes

add extra validation to the global_event_routing_settings to ensure only one of the supported target regions are passed. Supported regions are currently "eu-gb", "eu-de", "au-syd", "us-east", "us-south", "eu-es" (#401) (413e582)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

Test failed with this:
TestRunUpgradeCompleteExample 2024-02-16T09:47:51Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1; ╷
│ Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
│
│   with module.ocp_all_inclusive.module.observability_agents[0].helm_release.log_analysis_agent[0],
│   on .terraform/modules/ocp_all_inclusive.observability_agents/main.tf line 49, in resource "helm_release" "log_analysis_agent":
│   49: resource "helm_release" "log_analysis_agent" {
│
╵
╷
│ Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
│
│   with module.ocp_all_inclusive.module.observability_agents[0].helm_release.cloud_monitoring_agent[0],
│   on .terraform/modules/ocp_all_inclusive.observability_agents/main.tf line 136, in resource "helm_release" "cloud_monitoring_agent":
│  136: resource "helm_release" "cloud_monitoring_agent" {
│
╵
╷
│ Error: Get "http://localhost/api/v1/namespaces/kube-system/configmaps/iks-ca-configmap": dial tcp 127.0.0.1:80: connect: connection refused
│
│   with module.ocp_all_inclusive.module.ocp_base.kubernetes_config_map_v1_data.set_autoscaling[0],
│   on .terraform/modules/ocp_all_inclusive.ocp_base/main.tf line 444, in resource "kubernetes_config_map_v1_data" "set_autoscaling":
│  444: resource "kubernetes_config_map_v1_data" "set_autoscaling" {
│
╵}

Retrying..

/run pipeline

The upgrade test is failing with this:
TestRunUpgradeCompleteExample 2024-02-16T17:13:15Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1; ╷
│ Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
│
│   with module.ocp_all_inclusive.module.observability_agents[0].helm_release.log_analysis_agent[0],
│   on .terraform/modules/ocp_all_inclusive.observability_agents/main.tf line 49, in resource "helm_release" "log_analysis_agent":
│   49: resource "helm_release" "log_analysis_agent" {
│
╵
╷
│ Error: Kubernetes cluster unreachable: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
│
│   with module.ocp_all_inclusive.module.observability_agents[0].helm_release.cloud_monitoring_agent[0],
│   on .terraform/modules/ocp_all_inclusive.observability_agents/main.tf line 136, in resource "helm_release" "cloud_monitoring_agent":
│  136: resource "helm_release" "cloud_monitoring_agent" {
│
╵
╷
│ Error: Get "http://localhost/api/v1/namespaces/kube-system/configmaps/iks-ca-configmap": dial tcp 127.0.0.1:80: connect: connection refused
│
│   with module.ocp_all_inclusive.module.ocp_base.kubernetes_config_map_v1_data.set_autoscaling[0],
│   on .terraform/modules/ocp_all_inclusive.ocp_base/main.tf line 444, in resource "kubernetes_config_map_v1_data" "set_autoscaling":
│  444: resource "kubernetes_config_map_v1_data" "set_autoscaling" {
│
╵}

Will try re-run and see if it reproduces..

/run pipeline

@Aashiq-J This pipeline keeps failing with the same error - could you take a look? It seems to be just happening on upgrade test

/run pipeline

@ocofaigh ,
The changes in the vpc release v7.13.3 is causing the vpc to get recreated which in-turn is recreating the cluster. This causes the data block ibm_container_cluster_config to return null which makes the resources dependent on the helm and kubernetes provider to fail.

OK, so @Aashiq-J as it only impact our example here, and nothing related to the module itself, lets skip the upgrade test so we can merge this PR

/run pipeline

:tada: This PR is included in version 2.16.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: Aashiq-J ocofaigh shemau terraform-ibm-modules-dev terraform-ibm-modules-ops


text:
chore(deps): update common-dev-assets digest to f09e570

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
59ed87c -> f09e570

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v6.0.0

Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to f78cebd

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
e06c45b -> f78cebd

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Cert manager deprecation

When you provision a certificate manager instance you get a deprecation warning:

IBM Cloud Certificate Manager is deprecated. You will be able to continue working as normal until 30 September 2022. At that time you will no longer be able to create new instances of the service and the tile will be removed from the catalog. On 31 December 2022, support for the service will be removed and any existing instances will be deleted.

The guidance suggests to use Secrets Manager instead of Certificate Manager: https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-migrate-from-certificate-manager
Secrets manager is in the IBM Cloud Catalog at: https://cloud.ibm.com/catalog/services/secrets-manager

Secrets manager module has been created to replace this,
https://github.com/cloud-native-toolkit/terraform-ibm-secrets-manager

source: gharchive/issue

authors: rich-ehrhardt triceam


text:
Failed to retrieve available versions for module "network" (main.tf:19) from registry.terraform.io: host does not provide a modules service

Зашел в директорию https://github.com/terraform-yacloud-modules/terraform-yandex-kubernetes/tree/main/examples/clusters
Сделал terraform init
Сделал terraform apply
Получаю ошибку
╷
│ Error: Error accessing remote module registry
│
│   on main.tf line 1:
│    1: module "iam_accounts" {
│
│ Failed to retrieve available versions for module "iam_accounts" (main.tf:1) from registry.terraform.io: host does not provide a modules service.
╵

╷
│ Error: Error accessing remote module registry
│
│   on main.tf line 19:
│   19: module "network" {
│
│ Failed to retrieve available versions for module "network" (main.tf:19) from registry.terraform.io: host does not provide a modules service.
╵

Fix by https://github.com/terraform-yacloud-modules/terraform-yandex-kubernetes/pull/35


text:
[Snyk] Fix for 2 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
:sparkles: Snyk has automatically assigned this pull request, set who gets assigned.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

uasdm-server/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

399/1000  Why? Has a fix available, CVSS 3.7
Information Exposure SNYK-JAVA-COMMONSCODEC-561518
com.amazonaws:aws-java-sdk:  1.12.300 -> 1.12.302
No
No Known Exploit

561/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 4.8
Cryptographic Issues SNYK-JAVA-ORGBOUNCYCASTLE-2841508
org.keycloak:keycloak-servlet-filter-adapter:  19.0.1 -> 19.0.2
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

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
👩💻 Set who automatically gets assigned
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Out of date

authors: jsmethie rrowlands

repo: terraframe/osmre-uav


text:
Добавлен meta tag witter:card

для отображения большой картинки в телеграм
Чтобы в Телеграме показывать картинку так же, как в остальных соцсетях, нужно добавить к Опенграф‑тегам ещё один, максимально неочевидный:

https://bureau.ru/soviet/20221027/
https://t.me/svoddru/3535

максимально неочевидный

Бабушке моего кота очевиден (с)

authors: audetv iprst

repo: terratensor/svodd


text:
光标移到中间位置按退格，原密码不能正确的删除对应字符

目前将就得做法：退格就清空input

好的，這個問題稍後修正。修正後會 close 這個issue

已修正了，可以確認看看。

authors: ganl terrylinooo

license: MIT


text:
Android Crash on startup

The application crashes on startup for Android. "Unfortunately, ReanimatedGalleryExample has stopped". Used Lenovo phone & OnePlus6.

Could you please post here logs using adb logcat?

Apologies for the late reply; I managed to get the logs.
logcat.txt

Thanks. I'll try to reproduce and debug it tomorrow.
For now, you can use Reanimated's playground repo. It should be ready to go.

I just upgraded the whole example application to the latest RN and Reanimated versions.
Let me know if it works for you.

I pulled the latest code but still, the app crashes on startup.

Make sure to re-install node modules in example project (it's better to remove them completely and install again), clean watchmen and run the packager with
--reset-cache and then run ./gradlew clean before run-android.
Those all should make sure there is no any caching issues.

Any updates on this?

Closing because of no activity. Feel free to reopen this one.

repo: terrysahaidak/reanimated-gallery


text:
RFC: Add support for image or image list by URL

This allows OCR of images from the internet without downloading them first:
tesseract http://IMAGE_URL OUTPUT ...

It uses libcurl.
Signed-off-by: Stefan Weil sw@weilnetz.de

Is this a feature which is useful for others, too?
I want to use it for distributed OCR of books and newspapers with thousands of pages to avoid
downloading of temporary image files to disk.
libcurl not only supports http: and https:, but also other schemas like ftp: or ssh:, which could be added
to the new code, too, if needed.

Tesseract already accepts images on stdin. Why not use the curl binary and
pipes to avoid temp files?

I also wonder if it might cause any issues for larger software that uses
Tesseract as a component, such as ffmpeg or opencv.

Maybe it's possible to add this into tesseract binary, not library, in case if you need this on command line.
If you use tesslib it is possible to integrate curl into your app.

This works for me:
curl "http://d2jaiao3zdxbzm.cloudfront.net/wp-content/uploads/figure-65.png" | tesseract - -

If the feature is already available, way to add additional dependency to tesseract?

The current implementation adds curl in baseapi,cpp, so it's part of the library. Of course I could make curl support optional with --disable-curl being the default configure setting.
The pipe solution needs an additional step to add the image name to the hOCR output.

See https://groups.google.com/forum/#!topic/tesseract-dev/ZFn38UEOWM8 with a discussion to extend URL support to get traineddata models, too.

I think this will be a useful addition, specially from command line.
The concerns raised are addressed by @stweil's suggestion:

I could make curl support optional with --disable-curl being the default configure setting.

@Shreeshrii : see my comment at tesseract-dev forum

https://twitter.com/@xsamas12

https://twitter.com/@xsamas12

Is PR ready for merging?
If yes, no need to keep it longer unmerged.

Is PR ready for merging?

Technically it is ready, but it currently only works with autoconf (CMake support is still missing), and there is also no configure option like --disable-curl which allows disabling it at build time.

authors: MakaWeli Shreeshrii egorpugin jbreiden stweil zdenop

repo: tesseract-ocr/tesseract


text:
Wrong version number in console

I installed setup_RobotFramework_AIO_OSD5Linux_0.8.1.1.deb.
After this I installed RobotFramework_AIO_0.8.1.3-0_amd64.deb (from https://github.com/test-fullautomation/RobotFramework_AIO/actions/runs/5219911236)
But I forgot to uninstall the previous version 0.8.1.1
During installation of 0.8.1.3-0 the console tells:
Unpacking robotframework-aio (0.8.1.3) over (0.8.0.0) ...
But from where did the installer get the information about version 0.8.0.0? I would expect:
Unpacking robotframework-aio (0.8.1.3) over (0.8.1.1) ...

Hi Holger,
The version information which you are concerning is get from the control file.
With version 0.8.1.1 (and previous versions), version information in control file is not updated properly.
That is the reason why you observed 0.8.0.0 instead of 0.8.1.1.
That version information is updated properly in current versions:

0.8.1.2
0.8.1.3

Currently, this information is updated manually by Thomas and it should be updated for each release tag. So, Thomas has already raised a ticket to update this file automatically with build pipeline here.
As soon as that feature is implemented, the mismatched version as your observation will be solved because that version information will be same as release tag.
Thank you,
Ngoan


text:
fix issue with JAVA_HOME setting, only remind user to install java

Hi all,
I create this PR to fix current issue with JAVA_HOME as my proposal.
Please review and give your feeling about this change.
Thank you,
Ngoan

Hi Ngoan,
maybe you exchange
For using PlantUML
by
For using PlantUML on Linux
Because I assume that on Windows other installation routines than sudo apt-get are usual.

Hi Holger,
This file is only used for Linux machine, so that the message is only logged when installing on Linux.
Thank you,
Ngoan


text:
withClasspathResourceMapping copies empty file

Hi, as title says - I'm using a withClasspathResourceMapping functionality, and as I can see - library copies empty file to container filesystem
I've made a small reproducible example here https://github.com/IgorPerikov/testcontainers-file-issue
steps to reproduce:

clone repo
put a debug point here
launch test with default debug config
when debug point achieved check container name with docker ps -a
get container fs docker export your_container_name > ~/log.tar
open archive, check /tmp/myfile

I've checked it with 1.6.0 and 1.5.1 versions, both copies empty file
➜  ~ docker -v
Docker version 17.12.0-ce, build c97c6d6

Hello, @rnorth @bsideup! Can you provide any help here, please?

Hi @IgorPerikov,
Sure, let me take a look. Also, @rnorth is out file system ninja, maybe he has some ideas :)

... and thank a lot for the demo repo 👍

@IgorPerikov I just tried and it worked on my machine (macOS, Docker for Mac)
Try this patch:
Index: src/test/java/com/github/igorperikov/issue/MovingFileToContainerTest.java
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- src/test/java/com/github/igorperikov/issue/MovingFileToContainerTest.java	(revision 62929eaeb02fcb592f069322d64a03739a51a632)
+++ src/test/java/com/github/igorperikov/issue/MovingFileToContainerTest.java	(date 1519997751000)
@@ -1,6 +1,10 @@
 package com.github.igorperikov.issue;

+import com.github.dockerjava.api.DockerClient;
+import org.apache.commons.compress.archivers.tar.TarArchiveInputStream;
+import org.apache.commons.io.IOUtils;
 import org.junit.Test;
+import org.testcontainers.DockerClientFactory;
 import org.testcontainers.containers.BindMode;
 import org.testcontainers.containers.GenericContainer;

@@ -9,9 +13,17 @@
             .withClasspathResourceMapping("myfile", "/tmp/myfile", BindMode.READ_ONLY);

     @Test
-    public void justToMakeADebugPoint() {
+    public void justToMakeADebugPoint() throws Exception {
         container.start();
         System.out.println("I'm up");
-        container.stop();
+
+        DockerClient client = DockerClientFactory.instance().client();
+
+        try (TarArchiveInputStream tar = new TarArchiveInputStream(client.copyArchiveFromContainerCmd(container.getContainerId(), "/tmp/myfile").exec())) {
+            tar.getNextEntry();
+            String content = IOUtils.toString(tar);
+
+            assert content.startsWith("this\nis");
+        }
     }
 }

Also, what OS and method (docker-machine, Docker for Mac/Windows, native) are you using?

Test with this patch is passed. But when I verify it's content with docker export it still says that the file is empty.
Right now I've tested it with Ubuntu 14.04.5 LTS
My previous runs was at Ubuntu 16.04.? LTS
Speaking about method - I don't know how to answer for this part of question

@IgorPerikov on Linux it's "native" (no virtualization involved) :)
https://docs.docker.com/engine/reference/commandline/export/#parent-command

The docker export command does not export the contents of volumes associated with the container. If a volume is mounted on top of an existing directory in the container, docker export will export the contents of the underlying directory, not the contents of the volume.

that's why you're not seeing it I suppose :) But the file is there as you can see from my version of the test

Oh, that's why. Thanks for your help

@IgorPerikov always welcome :)

authors: IgorPerikov bsideup

repo: testcontainers/testcontainers-java

license: mit

license_source: bigquery


text:
Improve couchbase container startup resilience

Wait before CouchbaseContainer setup is run to reduce risk of apparent partial configuration/race conditions, and increase general wait strategy timeout.
Also add trace level logging, used in diagnosis and possibly useful in
future.
Possible fix for #1453.
Currently running tests repeatedly to determine whether this has truly gone away.

@rnorth so based on your debugging it is because the config is sent before the rest api is available?

I believe it may be. As-is, I don't think it looks safe, and after making this change I'm not able to reproduce the errors I was seeing.
I think I'm going to need to repeat tests on a less powerful machine than I'm using right now; the failure rate seems to be higher on slower machines (which suggests a race condition).

Damn, I was mistaken - running this on a slower machine still results in failures, so this is not a solution.
Still, I'd like to go ahead with this PR as it improves the error logging a little, and I don't see waiting for the REST API to be available before calling it to be a bad thing.
Sorry for getting peoples' hopes up though.

#2106 improved our test stability, though #1453 really should remain open until the module itself can be made more resilient.
We don't need this PR immediately, and I expect this to become irrelevant when @daschl comes back with findings on stabilising the module. As such, I'll close this particular PR.

authors: daschl rnorth


text:
Root cause of a not working container runtime strategy is not logged

Expected Behaviour
If a container runtime strategy does not work I would expect the root cause to be logged.
Actual Behaviour
You get a message that the container runtime strategy does not work, but the real error is swallowed.
Testcontainer Logs
Container runtime strategy UnixSocketStrategy does not work
Steps to Reproduce
Using a Docker runtime remove your user from the docker group.
Environment Information

Operating System: OpenSUSE Leap 15.5
Docker Version: 24.0.5-ce, build a61e2b4c9
Node version: v20.8.1
Testcontainers version: 10.2.1

I tried to use Testcontainers with Docker runtime, but got the message Container runtime strategy UnixSocketStrategy does not work. I checked the source code and realized that the root cause is not logged, not even catched. So I modified the code locally to catch and log the error. It was connect EACCES /var/run/docker.sock and caused by that my user was not part of the docker group.

Fixed by https://github.com/testcontainers/testcontainers-node/pull/787

authors: cristianrgreco gabor-s

repo: testcontainers/testcontainers-node


text:
При запуске параметризованных тестов в TestIT создаётся только 1 автотест

testit-adapter-pytest 3.2.1
testit-api-client 4.0.0
testit-python-commons 3.2.1
pytest 8.2.2
python 3.12
Пример теста
import pytest

class TestTest:
    @pytest.mark.parametrize('param', [0, 1])
    def test_test(self, param):
        assert 1 == 1

В TestIT ещё нет этих автотестов.
Запуск с tmsAdapterMode=2
Ожидаемый результат: создано 2 теста в TestIT
Фактический результат: создан 1 тест в TestIT

Это решается, если указывать externalId для теста с соответствующим параметром.
Например так
import pytest
import testit

class TestTest:
    @testit.externalId('test_test{param}')
    @pytest.mark.parametrize('param', [0, 1])
    def test_test(self, param):
        assert 1 == 1

И это будет корректней для связи с ручными тестами.
Но мне кажется стоит учитывать параметры и в случае автоматической генерации externalId.
Сейчас в случае, если не указан externalId, он генериться так
item.test_external_id = utils.get_hash(item.parent.nodeid + item.function.__name__)

Наименование метода для параметризованных тестов одинаковое.
Соответственно получается одинаковый test_external_id .
В примере выше, без указания @testit.externalId('test_test{param}'), для двух тестов хеш вычисляется от такой строки
tests/jobs/test_test.py::TestTesttest_test (с учётом струкруры проекта)

Можно, например, вместо этого генерировать `externalId` так
item.test_external_id = utils.get_hash(''.join(item.nodeid.split('::')[-2:]))

И аналогично использовать str(item.nodeid.split('::')[-1]) в качестве наименования автотестов в TestIT (но это, наверное, уже отдельная тема)
Или использовать просто item.nodeid в качестве уникального наименования при генерации externalId.
Note: не тестировал подробно предложенные решения. Это только пример

Потестил ещё немного.
Текущее поведение выглядит логичным.
При выполнении одного автотеста из TestIT, который связан с параметризованным тестом в pytest в Прогоне мы видим несколько результатов (для каждого параметра).
Соответтсвенно при добавлении новых параметров в этот тест, у нас по прежнему останется 1 тест в TestIT, но при выполнении будут учтены все новые параметры (в отличие от варианта создания разных автотестов в TestIT на каждый параметр).

repo: testit-tms/adapters-python


text:
Add smoke test before uploading release

Right now, we don't test the operating system matrix works before uploading a release. We should check what we expect to work, noting that this could be impacted by what envoy supports. For example, we have to be careful that cutting a new version like 1.21, which expands the OS version matrix, that doesn't prevent cutting a patch of an older version like 1.19. Also, not all operating systems may be available at the same time. For this reason, a manual target could be acceptable instead, that runs the checks.
TL;DR; a manually triggered workflow that runs all operating systems we want to expect, building as necessary that just invokes envoy version will be helpful. For example envoy version segfaults currently on macOS 12 and that's easier to start with vs a more elaborate test (see #28)

Note: this won't be able to test macOS 12 because no major CI supports it, yet, and as far as I know, there's no way to run it in docker.
GHA: https://github.com/actions/runner/issues/1171
CircleCI: https://circleci.com/docs/2.0/testing-ios/#supported-xcode-versions
Travis: https://docs.travis-ci.com/user/reference/osx/

https://github.com/tetratelabs/archive-envoy/pull/32 tests what we can, but doesn't block releases as there are reasons why things might not pass (ex homebrew PR not merged). The important thing is we will know what worked or not.

repo: tetratelabs/archive-envoy


text:
(wip) refactor wazeroir to use quasi-union

a PoC of the change mentioned in #1202 the way I have understood it. Commented out code is intended as this is still wip

(more wip on https://github.com/evacchi/wazero/tree/wip/refactor-wazeroir-quasiunion)

I guess we can close this and separate PRs are coming to us 🏁

authors: evacchi mathetake

repo: tetratelabs/wazero


text:
Narrows compiler support to operating systems currently known to work

This narrows to what the internal/platform package supports, which is
currently bound by Go SDK source that include Mprotect or windows.
Ex. zsyscall_linux_amd64.go includes Mprotect, but
zsyscall_freebsd_amd64.go does not.
This should prevent errors like below, by allowing wazero.NewRuntime()
to properly fallback to the interpreter.
.../mmap.go:74:16: undefined: syscall.Mprotect

A later change will implement FreeBSD. This is just here to ensure users
don't crash on unexpected OS.
See #607

I believe this is not enough as Go's compiler resolves all symbols in the package regardless of the actual compiler pass
$  GOOS=freebsd go build ./...
# github.com/tetratelabs/wazero/internal/platform
internal/platform/mmap.go:55:16: undefined: syscall.Mprotect

need platform/unsupported.go to define symbols

(maybe I'm wrong though :D)

cool I can fix platform also!

thanks for the eagle-eyes @mathetake and @anuraaga I forgot we can override runtime.GOOS to test compilation, though sadly GitHub Actions for freebsd won't be so easy 😅

authors: codefromthecrypt mathetake


text:
Call onInput in onInit to mask initiial value.

Turns out this is needed still!! Initial value was no longer getting masked...not sure how that slipped by. Sorry!

No worries, will publish soon!

Published as angular2-text-mask@0.20.1

authors: andyrue msafi

repo: text-mask/text-mask

license: Unlicense


text:
splitting args for carriers to allow plating

Kausi added a line to split the args of the carriers (so eg ['6, 4']) into a list of strings (['6', '4']), so that plated carriers don't trigger the value error below. This allows the python frontend to generate knitout code with plating

Looks reasonable to me. (Though, relative to your example, it would probably split '6, 4' into ['6,', '4'].) Probably impacts discussion in issue #2, but does not resolve it.

authors: heread ixchow

repo: textiles-lab/knitout-frontend-py


text:
Errors occured when trying to run example_environment.py

Dear Thomas,
I got an error as shown below, could you please help me with that?
"import sconepy
ImportError: dlopen(/Applications/SCONE.app/Contents/MacOS/lib/sconepy.cpython-39-darwin.so, 0x0002): tried: '/Applications/SCONE.app/Contents/MacOS/lib/sconepy.cpython-39-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Applications/SCONE.app/Contents/MacOS/lib/sconepy.cpython-39-darwin.so' (no such file), '/Applications/SCONE.app/Contents/MacOS/lib/sconepy.cpython-39-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64'))"
Kind regards.

It is indeed true that there is no SCONE release for Apple silicon (arm64). When running SCONE studio, this is handled automatically via Rosetta, but apparently this is not the case for SconePy. It seems the architecture is tied to the Python environment here.
Do you have the option to use a Python environment based on x86_64? Then everything should run properly through Rosetta.

Thanks Thomas, I will try to run it using the x86_64 based Python environment to see if it works.

Thanks, let me know!

Hey,
I fixed the error on Mac by installing it on conda environment:
conda create -n my_x86_env -y
conda activate my_x86_env
conda config --env --set subdir osx-64
Then install everything as stated in the instruction

authors: LiangliangXiang Nazerek tgeijten

repo: tgeijten/sconegym


text:
.connection(dbConnection) works well?

Hello.
I tried to use ".connection(dbConnection)" for bellow.

I want to query for tow or more databases in one connection.

In brief code as bellow, I expect some_queries to be applied each DB in same connection.
But doesn't. I found that each connection have different threadId at lib/client.js
var knex = require('knex')(conf); // DB1
var knex2 = require('knex')(conf2); // DB2
var con = require('mysql').createConnection({host: '127.0.0.1', user: 'knex_user', password : 'knex_pass'});
con.connect();
Promise.reduce([knex, knex2], function(promise, k) {
    return k.connection(con)._some_queries_;
}, 0);
con.end();

To be precise, I need XA Transaction. This vote is the detail of my question.
I am new at javascript, so maybe I wrote wrong code...
I hope somebody kindly aid me.
Thanks.

@hidetaka-f-matsumoto Sorry, this took forever, but I think what you are asking for was finally implemented in https://github.com/tgriesser/knex/pull/2817 and is available in 0.16.x "@next" branch.

authors: hidetaka-f-matsumoto kibertoad

repo: tgriesser/knex


text:
Fix OS X V8 build to actually be the V8 build

See https://github.com/thaliproject/CI/issues/25#issuecomment-200241341 for background.
My hope would be that we still keep also the SpiderMonkey build, but just host it with a filename that matches the content.

updated the CDN and initiated a purge. I verified jx -jsv is V8 after. SM is still there too
curl -o jx.zip http://jxcore.azureedge.net/jxcore/0312/release/jx_osx64v8.zip
unzip jx.zip
cicoriasmbp13@Shawns-MBP:~/Downloads/jx_osx64v8$ ./jx -jsv
Google V8 v3.14.5.9

While CDN purge may take time, the direct link to origin is: https://jxcore.blob.core.windows.net/jxcore-release/jxcore/0312/release/jx_osx64v8.zip

authors: cicorias vjrantal


text:
Won't work when I try to change the audio src.

I wrote code like below in my web app
<ReactHowler           src={media[this.state.page].bgmUrl}         />
when I change the state like this:
this.setState(       {         page: 3,       }     );
the component won't work, it start to request hundreds of source mp3 files like this

What can I do?

This looks like media[this.state.page].bgmUrl doesn't change after state changed. So howler.js downloaded the same file.
Could you add some log to make sure media[this.state.page].bgmUrl was changed ?

XMLHttpRequest cannot load http://www.stephaniequinn.com/Music/Allegro%20from%20Duet%20in%20C%20Major.mp3. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8000' is therefore not allowed access. DemoComponent.js?582c:49 Now the src url is http://www.stephaniequinn.com/Music/Allegro%20from%20Duet%20in%20C%20Major.mp3 localhost/:1 XMLHttpRequest cannot load http://www.stephaniequinn.com/Music/Canon.mp3. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8000' is therefore not allowed access. DemoComponent.js?582c:49 Now the src url is http://www.stephaniequinn.com/Music/Canon.mp3 localhost/:1 XMLHttpRequest cannot load http://www.stephaniequinn.com/Music/Allegro%20from%20Duet%20in%20C%20Major.mp3. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8000' is therefore not allowed access.
Here's the log. According to it, the src did change after state changed.
I read your source code, and the function componentWillReceiveProps made sure that when the props src is changed, the old howler will be destroyed and the new one will be initailized. So now I'm so confused about this problem.

Btw, I can still hear the sound even if the log tell me that XMLHttpRequest cannot load http://www.stephaniequinn.com/Music/Allegro from Duet in C Major.mp3. So I ignored this problem.

'Access-Control-Allow-Origin'

This is a common problem with hot-linking resources from other websites. You should download these files to your server/ or have a proxy that download these files on the fly.
As you pointed out, componentWillReceiveProps make sure this kind of situation won't happen so I have no idea what may caused this.

I've realized the requirement in another way
`this.state = {
page: 0,
playing: [true, false, false, false]
}

          {media.map(function (item, i) {
            return ()
          })}

`
using the playing array in this.state to control the whole React-howler group.
But the problem still exists. I think maybe it can be related to some low-level implementation of React. Some just keep on studying!  hahahaha

Thanks for investigating this. Please let me know if you find a solution for this

I have the same issue, changing the audio src causes the component to create infinite Howler instances.

My simplified version of this component works as expected. I'm not sure why it doesn't here (maybe because I'm using the master version and not beta?), but I've noticed a few other things:

this.howler = null will not null the instance, you check for truthiness of the passed value in the setter
runIfSet(props.mute, this.mute(props.mute)) doesn't do what you expect it to do. Instead if passing a function, you pass the result of the function call. Note that you also never call callback in runIfSet.

componentWillReceiveProps triggers howl.play() twice, first via autoplay in initHowler and another time in toggleHowler, so you're getting two plays with a single src change.

@jgillich I don't use this component anymore so I'm looking for maintainer. I'm happy to give you write access to this repo.

authors: jgillich pfncfen thangngoc89


text:
store: Add LRU caching for posting offset / adaptive postingOffsetInMemSampling based on traffic

After we fixed postingOffset sampling which was broken (we were keeping in memory all of them, instead of 1/32 as we intended), some of the users see extreme improvement:

This means that the about of postings is extreme in some setups, so what we keep in memory in terms of posting offsets really matters. This means we might need some caching for posting offsets as well. While we store them on disk, still disk lookup might be slower than in memory. I doubt there would be a benefit to storing this in remote cache though.
cc @d-ulyanov @mkabischev

This needs like some very advanced logic, which is not needed, yet. Closing for now.

repo: thanos-io/thanos


text:
specifally query thnoas sidecars from thanos queriers when using grafana

While writing queries in grafana, How can I mention I need the data to be fetched from specific sidecars only for faster retrieval instead of store gateway?

There are two ways I can think of:

Use a recent time range. Sidecar always has the latest data while store gateway usually has not so updated data. If you select a recent query time range then it is possible to skip store gateway.
You can use store filtering in the Thanos UI to only query sidecars. But it is not easy to do this in Grafana. IIRC you can only set customQueryParams in the datasource configuration but it is global for this datasource.

Try set store gateway flags --max-time=1d to serve only time 1 day ago.

the querier will use sidecar/store external label as first filter.
for example:
there are two prometheus，one config team='a' external label. another config team='b' external label.
if the query is 'up{team='a'}'，it only query the first one prometheus sidecar.
the store gateway has relabel config filter and time range filter，it can on serve a part of labels or time range across all the blocks. for example， set store gateway flags --max-time=1d to serve only time 1 day ago.

@denniceritchie Will close this issue for now. Let me know if you still have other questions.

authors: denniceritchie hanjm yeya24


text:
[Website] fixed overflow company images and hero section logo

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
This PR Fixes two issues in the website
Overflow company images in Used By section

Extremely Small logo image in Hero section (from viewport 576px - 750px)

Verification

After Changes
Fixed Overflow company images in Used By section

Extremely Small logo image in Hero section (from viewport 576px - 750px)

Looks really clean! Do you think it's possible to make them all equal in size? Now it sort of looks like "premium" users due to the size difference :)

@wiardvanrij I see :thinking: . Actually, the containers are of the same sizes. It is just that the image logo styles are different.

Tried using object-fit: fill results in,

Now it sort of looks like "premium" users due to the size difference :)

I think we already had this problem before, so I wouldn't make it a blocker for this fix. Nevertheless, I think that the fundamental issue there is that our containers have a specific width:height ratio so logos that are closer to that ratio will appear larger. On top of that, some logos have more padding in their images than others.
I don't think there's anything we can do trivially to solve these issues, other than cropping logos to be the same size. An additional option would be to fix one dimension, e.g. height, and allow the other dimension to grow. However, this would result in a page that is not a fixed grid and would actually give non-square logos an advantage. Logos that are very wide would have tons of area while square or narrow logos would have much smaller areas.

Ah, @NikhilSharma03 I think what @wiardvanrij is referring to is actually the last row. Because this row has fewer logos, the containers are all larger. Can we make it so that containers are always the same width?

@squat Actually All of the containers are of the same width. In the Screenshot (Last Row), I just cropped out the SoundCloud logo only since it was the one going out of the container.
Preview:
https://deploy-preview-5015--thanos-io.netlify.app/

Right, awesome job 😎

Ah ok, I see, the were two different images

Looks pretty good @NikhilSharma03 Can you share "after" screenshots too?

You can actually open the Netlify preview to see the difference :sunglasses:

authors: GiedriusS NikhilSharma03 squat wiardvanrij


text:
Authentication failure when requesting a Submission

I'm trying to read a public submission, which is also accessible via public url https://www.reddit.com/r/announcements/comments/4dmnn6/.json
When trying to read the submission via JRAW api, a 403 Unauthorized gets thrown.
Is there any way around this, to get Submissions through the API without authorizing the app?

Reddit has deprecated cookie-based authentication, which is what that URL relies on. OAuth-based authentication requires every single client to be authorized in order to access any data on the site. Since JRAW is an OAuth-only library, you must authenticate your client. If your app/script does not need a user to be logged in, you can use application-only OAuth. See more in the wiki.

Great, that solves the issue. Thanks!

authors: radonthetyrant thatJavaNerd

repo: thatJavaNerd/JRAW


text:
Documentation for Android call

On this page the docs for the onUserChallenge call are out of date. It doesn't seem to require the REDIRECT_UTL for this call.
return helper.onUserChallenge(params[0], REDIRECT_URL, creds);

Thank you for bringing this to my attention. It's now been fixed.


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64640


text:
Improve documentation

More documentation on how to customize the package would be appreciated.
Also, behaviour of menu and how to call them i.e. using Menu::display('name') should be documented

Indeed, I will work on this once I get the time. However I'm still open for pull requests to the documentation.

@kirtangajjar https://voyager-cheatsheet.ulties.com/
maybe this can help

@hugosvent I need to set some time off to remake that for v0.11.

Btw, closing this since the menu section have been documented.

authors: hugosvent kirtangajjar marktopper

repo: the-control-group/voyager


text:
PHP7 compatibility fix for spatial traits

Getting lat and lng data from point value with the list function is ambiguous and incoherent between PHP5 and PHP7
This lead to wrong or right location coords depending on the verion of php you use
Excerpt from PHP.net documentation below (php list function)

Warning
In PHP 5, list() assigns the values starting with the right-most parameter. In PHP 7, list() starts with the left-most parameter.
If you are using plain variables, you don't have to worry about this. But if you are using arrays with indices you usually expect the order of the indices in the array the same you wrote in the list() from left to right, which is not the case in PHP 5, as it's assigned in the reverse order.
Generally speaking, it is advisable to avoid relying on a specific order of operation, as this may change again in the future.

IMHO I don't think this patch is going to change anything since $lat and $lng are plain variables, therefore, not affected.

@MrCrayon you are right, see
http://sandbox.onlinephpfunctions.com/code/ce68db17444bff512b6e4d93ec33432429ec405e
If you are using plain variables, you don't have to worry about this.

I'll investigate a bit more but currently this what i am facing.
I am runnin my code on php 7.2 as specified
Lets suppose you want to store New York location in a point data type.
New York position on map is (40.712765, -73.884957)
lat -> 40.712765
lng -> -73.884957
the point is correctly stored
But there is a issue when you retrieve the lat and lng from db using list function you get this.
PHP5 list
[40.712765, -73.884957] -> corresponds to new york
PHP7 list
[-73.884957, 40.712765] -> corresponds to Antarctic
I think this should be addressed because it can leads an app to provide unreal data and is not acceptable in the field of mapping.
I'll investigate and provide update, if anyone can also figure out what it happening i'll be good also

I'm not using this Trait so I can't say for sure is working.
Can you provide the piece of code where you are using getCoordinates()?

After running a script on different servers, find results below, I understood what's the real issue.
It has nothing to do with php version or the use of list but list parameters were simply swapped, fix should be:
-                        list($lat, $lng) = explode(' ', $point);
+                        list($lng, $lat) = explode(' ', $point);

script:
<?php
$point = "lat lng";
list($lat, $lng) = explode(' ', $point);
$lngLat = explode(' ', $point);

echo phpversion(). "\n";
echo $lat . ' ' . $lng . "\n";
echo $lngLat[0] . ' ' . $lngLat[1] . "\n";

results:
5.4.45-0+deb7u11
lat lng
lat lng

5.6.11-1ubuntu3.4
lat lng
lat lng

7.0.28
lat lng
lat lng

7.1.15
lat lng
lat lng

@MrCrayon you are right, and your fix is right and ok.
But what about the comment on php.net. They state we should not rely on order of parameters returned by list function because it can be changed at any php release.

Generally speaking, it is advisable to avoid relying on a specific order of operation, as this may change again in the future.

We can make sure future releases of php won't have any side effect on the spatial trait by not using the list function  as the order is not reliable
my solution is the array indexes as in my PR, any other solutions or we should simply swap the parameters of list (taking risks of inconsistences across php releases)

@bab55z it's not the order of parameters is the "order of operation", that's why it affects only if you use array with indices.
Try this with php5 and php7:
$point = "lng lat";
$lngLat = [];
list($lngLat[], $lngLat[]) = explode(' ', $point);

echo phpversion(). "\n";
echo $lngLat[0] . ' ' . $lngLat[1] . "\n";

I meant ditching the list function
$point = "lng lat";
$lngLat = explode(' ', $point);
echo $lngLat[0];
echo $lngLat[1];

But you are right, we simply need to invert parameters order.

What I was trying to point out it that you misunderstood what php documentation stated, using list or using an array as in your first commit it's exactly the same thing, but IMHO using list is a bit more readable.
But the important thing is that another bug is about to be eliminated :thumbsup:

yes i misunderstood, that lead me to another field to find a solution. but every things is right now thanks for explanations.

Makes sense.
The saving-order was changed in https://github.com/the-control-group/voyager/pull/2425

authors: MrCrayon bab55z emptynick


text:
1.x

sk.zip
Slovak language translation support.

Hello,
sorry, did I do something wrong? I just wanted to publish my Slovak translation of Voyager App.
I was doing it for the fist time so please apologize me if I made a mistake. Can you please
navigate me how to do it right?
Thanks.
S pozdravom,
Boris Tetřev - ALTERWEB
mobil: 0905 315 251
email: tetrev@alterweb.sk

Dňa 28. 8. 2018 o 6:33, Eric Fletcher notifications@github.com napísal:
Closed #3506 https://github.com/the-control-group/voyager/pull/3506.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/the-control-group/voyager/pull/3506#event-1812108406, or mute the thread https://github.com/notifications/unsubscribe-auth/AhC0EUmEbXmILMsfQpMi1lLaneMU46fUks5uVMgfgaJpZM4WO2oi.


text:
date alignments are off

same with the next scroll when it highlights

believe this is on resize when the canvas doesn't get a new width

authors: jadiehm polygraph-umg

repo: the-pudding/country-radio-viz


text:
Python Gameoflife

I want to add my gameoflife in Python with a good UI and mouse generable

@danieleavolio
Go ahead

@danieleavolio
I'm yet to receive a PR.

authors: danieleavolio theadeyemiolayinka

repo: theadeyemiolayinka/python-scripts


text:
UFCS

UFCS, or Unified Function Call Syntax, is a feature employed in procedural languages to allow method call style syntax without explicitly coupling data and processing-- methods without OOP, essentially.
Using UFCS, the following function:
fn add(a, b: into): int {
  return a + b;
}

is callable as
1.add(2)

or the normal
add(1, 2)

This is another idea taken from Nim along with Concepts that I think is really nice syntactically. Other languages such as D and Rust (to some extent) have it, and there is a proposal to add it to C++.

wonder full sugestion we will definityl implment it

I would go the route kotlin goes and add extension functions. the syntax would look something like this:
fn i32.add(other: i32): i32 {
    return this + other;
}

That would be nice to have as well for method style functions, but I don't think the two need be mutually exclusive.

I like this a lot it might be the way to go about adding calls to base data types in the stdlib, i like @jorolf sugestion with the kotlin style more for the pre bootstrap stages becuase its realy simple when it comes to scemantic and type cheacking, but i like the nim style to so we can add both when we go post bootstrap

authors: MyvarHD davidgarland jorolf


text:
Do you have any plans to port this to 1.16.5?

If not, would you have any issues with me including these patches in a 1.16 performance mod (with credit)?

Hey, no I don't intend to back-port to 1.16 at all. Feel free to do that (the MIT licence allows it I believe 🙂), and credit is appreciated but not required 😄

authors: embeddedt thebrightspark

repo: thebrightspark/AsyncLocator


text:
firepicker box hide the half of the color value

Like the title say , the box where i see the color hide the half of the edit color value in firebug...so  it's more difficult to edit it.
Am i alone?

http://www.flickr.com/photos/31792685@N02/6544697623/in/photostream
The color editor obscures the CSS. I fixed it by going to
MAC:
/Users/[user_name]/Library/Application Support/Firefox/Profiles/[random].default/extensions/firepicker@thedarkone/chrome/skin/classic/css-attribute-dialog.css
WIN7:
C:\Users\[user_name]\AppData\Roaming\Mozilla\Firefox\Profiles\[random].default\extensions\firepicker@thedarkone\chrome\skin\classic\css-attribute-dialog.css
WIN-XP
C:\Documents and Settings\[user_name]\Application Data\Mozilla\Firefox\Profiles\[random].default\extensions\firepicker@thedarkone\chrome\skin\classic\css-attribute-dialog.css
and changing the margins on the class .firepicker_color_container
from
margin-top: -10px;
margin-left: 4px;
to: margin:0px;

Hello,
this has been fixed in the newest version.
Thanks!

authors: decembre thedarkone verbatim

repo: thedarkone/firepicker


text:
Error thrown in Dropdown dismissHandler

When the Dropdown dismissHandler is called it is possible for eventTarget[parentNode] to evaluate to null, causing the following error when using v2.0.26 of the library on safari and chrome (desktop and mobile):
Chrome 73.0.3683.103:
Uncaught TypeError: Cannot use 'in' operator to search for 'Dropdown' in null
    at HTMLDocument.dismissHandler (bootstrap-native.2.0.26.js:914)

Safari 12.1:
TypeError: null is not an Object. (evaluating 'stringDropdown in eventTarget[parentNode]')

Interestingly, the issue does not occur in v2.0.19 or 2.0.20 of the library but starts occurring after that point. I was able to resolve the issue in my site by replacing this code that starts at dropdown-native.js line 46:
hasData = eventTarget && (stringDropdown in eventTarget || stringDropdown in eventTarget[parentNode]);

With this code, lifted from v2.0.19 of the library:
hasData = eventTarget && (eventTarget[getAttribute](dataToggle)
                   || eventTarget[parentNode] && getAttribute in eventTarget[parentNode]
                   && eventTarget[parentNode][getAttribute](dataToggle));

Thanks for the contribution, can you please make a test setup/guide on how to replicate, and also confirm the issue apply to V3 as well?
Thanks so much.

Here is a test app with repro steps for v4. I can't replicate for v3, but I do not have much experience with Bootstrap 3 and there may be a different way Dropdowns are handled/toggled.
v4_test.html.zip

@jhunschejones that isn't a proper Bootstrap Dropdown markup. If you would work with the default dropdown markup there shouldn't be any issue.

Interesting. What about it is standing out as non-standard? This example app works with no errors when using Bootstrap's normal library/plugins.

That's because jQuery pollyfills the heck out of that code to make it work with anything you throw at it. At the cost of performance, space and long term maintenance time. So we try to do things different.
But I have an idea to make some test these days, we might roll back to the previous working revision.

Thanks for taking the time to explain all this, I really appreciate it. v2.0.26 fixed some modal behavior issues I was having, so I was happy to make the upgrade (after working through this dropdown blocker.) Let me know if there is anything else I can do to help!

authors: jhunschejones thednp


text:
[WIP] Update README for route/controller actions

Relates to conversations on #39 to clearly illustrate the options for implementing ember-impagination. Waiting to see if ember-route-action-helper is a possible recommendation for defining fetch in an actions hash, on the route, and implemented as a closure-action

Need to revisit this as of 0.2.0

Closing in Favor of #130

repo: thefrontside/ember-impagination


text:
19284 - Kunimaipa

Lat-lons for songs 63 and 64 are inaccurate. They correspond with Port Moresby, but the location listed is Kunimaipa Valley, which is located between the Lakekamu River and Mount Yule. Suggest choosing a lat-lon in that region and assigning it to those songs.

Done

repo: theglobaljukebox/cantometrics


text:
Off state for Desktop controls

https://github.com/theglus/Home-Assistant-Config/blob/3c757322d926023aa4f0ae775af16bb8d3542741/includes/lovelace/views/3_system.yaml#L86-L194
Requirements

[ ] Define off state for Locomotive.
[ ] Establish Lovelace funtionality to hide Desktop Controls when state = off.

Resources

Conditional Card

This should be accomplished with my next PR.

repo: theglus/Home-Assistant-Config


text:
Add a statuspage app

@mrchrisadams Migrating this from the old admin env to a public page on https://status.thegreenwebfoundation.org so we can make this visible.
We can extend this later with other statistics.

Seems one of the tests is failing, which is not caused by this change.

Hey @arendjantetteroo does this need anything else?

Some way to deploy this :)
Currently it's just a copy/paste of whats on the server, but would be nice to keep it tracked in git.

Hey @arendjantetteroo - given that the graphite web app let us make these, you reckon we still need this?
We have dashboards like this, and I think we can make them accessible publicly too. This would mean you don't need to use git to make changes.
👍 ?
https://graphite.thegreenwebfoundation.org/dashboard/Rabbit

authors: arendjantetteroo mrchrisadams


text:
Add options to save output in any format

Add options to save output in any format. For e.g., txt, xml etc.

Please assign me this issue

I have raised a PR for this. Please do check.


text:
Rank features groups obs

PR Checklist

[x] This comment contains a description of changes (with reason)
[x] Referenced issue is linked
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] Documentation in docs is updated (via docstrings)

Description of changes
Resolves #593.
As outlined in this issue, this PR adds an additional functionality for the user to use rank_features_groups: for the .obs field only (as opposed to using .X/.layers).
It does so by allowing the user to specify an additional argument rank_obs_columns in rank_features_groups. It is by default None, and takes the values "all" or a list of keys if only a selection of observation columns is wished/meaningful to be ranked.

Technical details
Uses move_to_x and encode (autodetect=True, encodings="label"). Makes no changes to the passed adata except for adding the respective entries in adata.uns.

Questions

What do you think in general?
Remarks on code?
What do you think of this new option for the user? More arguments? Better argument name suggestions?
Should we we want to take care of strange stuff (e.g. dates/times) or expect user to only specify columns that make sense & have it blow up if this is not done properly
More tests?

Additional context
Example:
import ehrapy as ep
import numpy as np
import pandas as pd
import scanpy as sc

def create_dummy_dataset_numerical_in_obs():
    """
    Create a dummy dataset with numerical and non-numerical variables in .obs.
    Also, has numerical variables in .X.
    """
    dummy_obs = {"disease":['A', 'A', 'A', 'A', 'B', 'B', 'B', 'B', 'C', 'C', 'C', 'C'],
                "station": ['ICU', 'ICU', 'MICU', 'MICU', 'ICU', 'ICU', 'MICU', 'MICU', 'ICU', 'ICU', 'MICU', 'MICU'],
                "syst_bp_entry": [138, 139, 140, 141, 148, 149, 150, 151, 158, 159, 160, 161],
                "diast_bp_entry": [78, 79, 80, 81, 77, 78, 79, 80, 55, 56, 57, 58]}

    dummy_var = pd.DataFrame({"Unit": ["mg/dl", "kg"]})
    dummy_var.index = ['glucose', "weight"]
    dummy_X = np.array([[80, 90, 120, 130, 80, 130, 120, 90, 80, 90, 120, 130],
                        [77, 76, 60, 90, 110, 78, 56, 76, 67, 82, 59, 81]]).T

    adata_dummy = sc.AnnData(X=dummy_X, obs=dummy_obs, var=dummy_var)

    adata_dummy.uns['numerical_columns'] = ['glucose', 'weight']
    adata_dummy.uns['non_numerical_columns'] = []
    adata_dummy.uns['encoded_non_numerical_columns'] = []

    return adata_dummy

adata_dummy = create_dummy_dataset_numerical_in_obs()

# classical way of using .X
ep.tl.rank_features_groups(adata_dummy, groupby='disease',)
ep.pl.rank_features_groups(adata_dummy)

# added way of using .obs
ep.tl.rank_features_groups(adata_dummy, groupby='disease', rank_obs_columns="all", key_added="rank_obs")
ep.pl.rank_features_groups(adata_dummy, key="rank_obs")

@eroell this is exactly what I had in mind! Really like the None / all / some_list options too :)

What do you think of this new option for the user? More arguments? Better argument name suggestions?

Perfectly fine.

Should we we want to take care of strange stuff (e.g. dates/times) or expect user to only specify columns that make sense & have it blow up if this is not done properly

Maybe we should check the dtype of the obs columns and shout at least if we saw dates/times?

More tests?

Only if we're handling date and time. Otherwise LGTM

New version now can consider highly variable features in .X/.layers[layer], .obs, or both.
This introduces two new arguments:

field_to_rank: available options are 'layer' (default), 'obs' (what has been possible above), 'layer_and_obs' (new here)
columns_to_rank: default 'all', but can be dict with var_names and obs_names keys, e.g. {"var_names": ["glucose"], "obs_names": ["syst_bp_entry", "station"]}. The ability to select columns from .obs is probably important due to many columns likely not of interest (such as dates); Since var and obs is less strictly separated here than in single-cell though, having the column selection option for both cases probably makes sense, especially if combining them in an analysis this way...

But it might be that this has become overengineered, with more pitfalls of how it could raise Errors in a confusing way
@Zethson what do you think?
@juzb once more - what do you think of the examples below? More confusing to use than the example above?
Example
import ehrapy as ep
import numpy as np
import pandas as pd
import scanpy as sc

def create_dummy_dataset_numerical_in_obs():
    """
    Create a dummy dataset with numerical and non-numerical variables in obs.
    Also, has numerical variables in .X.
    """
    dummy_obs = {"disease":['A', 'A', 'A', 'A', 'B', 'B', 'B', 'B', 'C', 'C', 'C', 'C'],
                "station": ['ICU', 'ICU', 'MICU', 'MICU', 'ICU', 'ICU', 'MICU', 'MICU', 'ICU', 'ICU', 'MICU', 'MICU'],
                "syst_bp_entry": [138, 139, 140, 141, 148, 149, 150, 151, 158, 159, 160, 161],
                "diast_bp_entry": [78, 79, 80, 81, 77, 78, 79, 80, 55, 56, 57, 58]}

    dummy_var = pd.DataFrame({"Unit": ["mg/dl", "kg"]})
    dummy_var.index = ['glucose', "weight"]
    dummy_X = np.array([[80, 90, 120, 130, 80, 130, 120, 90, 80, 90, 120, 130],
                        [77, 76, 60, 90, 110, 78, 56, 76, 67, 82, 59, 81]]).T

    adata_dummy = sc.AnnData(X=dummy_X, obs=dummy_obs, var=dummy_var)

    adata_dummy.uns['numerical_columns'] = ['glucose', 'weight']
    adata_dummy.uns['non_numerical_columns'] = []
    adata_dummy.uns['encoded_non_numerical_columns'] = []

    return adata_dummy

# classical way of using .X
adata_dummy = create_dummy_dataset_numerical_in_obs()
ep.tl.rank_features_groups(adata_dummy, groupby='disease')
ep.pl.rank_features_groups(adata_dummy)

# added way of using .obs
adata_dummy = create_dummy_dataset_numerical_in_obs()
ep.tl.rank_features_groups(adata_dummy, groupby='disease', field_to_rank="obs")
ep.pl.rank_features_groups(adata_dummy)

# added way of using both
adata_dummy = create_dummy_dataset_numerical_in_obs()
ep.tl.rank_features_groups(adata_dummy, groupby='disease', field_to_rank="layer_and_obs")
ep.pl.rank_features_groups(adata_dummy)

# added way of using e.g. both, with selecting only a some variables
adata_dummy = create_dummy_dataset_numerical_in_obs()
ep.tl.rank_features_groups(adata_dummy, groupby='disease',
    field_to_rank="layer_and_obs",
    columns_to_rank={"var_names": ["glucose"],
                                   "obs_names": ["syst_bp_entry", "station"]
                                   }
)

authors: Zethson eroell juzb

repo: theislab/ehrapy


text:
Differential Expression with a fixed reference

When I run sc.tl.rank_genes_groups and I set the reference argument to one of my groups I am testing, I get the error
     91         groups_order = [str(n) for n in groups_order]
     92     if reference != 'rest' and reference not in set(groups_order):
---> 93         groups_order += [reference]
     94     if (reference != 'rest'
     95         and reference not in set(adata.obs[groupby].cat.categories)):

TypeError: must be str, not list

That's because 'groups_order'  is not a list at this point of the code when the argument groups is at its default all. When I change this and I pass a list, e.g. ['0', '1'], then the error vanished, because groups order will then be a list that we can add to. This should be changed, because the setting 'all' is the default value.

Hi Alex!
Sorry for this long delay, I just forgot completely.
Maybe I wasn't clear enough in my original post, here is where the issue lies:
When I run
sc.tl.rank_genes_groups(adata_f, groupby = 'ClusterName', groups = 'all')
everything is fine and I get my desired result. However, when I just change the reference setting
sc.tl.rank_genes_groups(adata_f, groupby = 'ClusterName', reference='CA', groups = 'all')
then I get the following error
`    100         groups_order = [str(n) for n in groups_order]
101     if reference != 'rest' and reference not in set(groups_order):
--> 102         groups_order += [reference]
103     if (reference != 'rest'
104         and reference not in set(adata.obs[groupby].cat.categories)):
TypeError: must be str, not list`
I absolutely understand how to solve this - as you said, I can just use the tutorial call and select groups explicilty
sc.tl.rank_genes_groups(adata_f, groupby = 'ClusterName', reference='CA', groups = ['OPC', 'Granule'])
and then it works again. I was just wondering whether this is the desired behavior - most users will leave the groups attribute at it's default setting when they change the reference attribute and wonder why it does not work - at least that was my idea. Maybe I am wrong.

Thank you for pointing it out, that's obviously a bug!

I got the same issue recently, may I ask if you have fixed the bug, please?

I also had this issue with scanpy 1.6.0, which is fixable in the way mentioned by Marius1311, but I agree it is not the expected behavior

authors: Fronttooth Marius1311 falexwolf michael-swift

repo: theislab/scanpy


text:
Errors should be JSONified (and not assume Accept: text/plain header)

Errors should really be JSON responses with appropriate Content-Types headers.
The following sends a JSON request using Accept and Content-Types set to application/json:
➜  ~  http -j http://localhost:9000/ip/8.8
HTTP/1.1 406 Not Acceptable
Content-Length: 78
Content-Type: text/plain; charset=UTF-8
Date: Sun, 01 Feb 2015 10:43:21 GMT
Server: akka-http/2.3.9

Resource representation is only available with these Content-Types:
text/plain

When I explicitly say I'm accepting test/plain it's fine:
➜  ~  http -j http://localhost:9000/ip/8.8 Accept:text/plain,application/json
HTTP/1.1 400 Bad Request
Content-Length: 24
Content-Type: text/plain; charset=UTF-8
Date: Sun, 01 Feb 2015 10:44:13 GMT
Server: akka-http/2.3.9

8.8: incorrect IP format

The same happens with the following when it's implicitly assumed POST in JSON Accept and Content-Types headers:
➜  ~  http http://localhost:9000/ip/8.8.8.8 ip1=8.8.8.8 ip2=8.8
HTTP/1.1 406 Not Acceptable
Content-Length: 78
Content-Type: text/plain; charset=UTF-8
Date: Sun, 01 Feb 2015 10:46:06 GMT
Server: akka-http/2.3.9

Resource representation is only available with these Content-Types:
text/plain

With explicitly accepting non-JSON responses using Accept:text/plain it works:
➜  ~  http http://localhost:9000/ip/8.8.8.8 Accept:text/plain,application/json ip1=8.8.8.8 ip2=8.8
HTTP/1.1 400 Bad Request
Content-Length: 24
Content-Type: text/plain; charset=UTF-8
Date: Sun, 01 Feb 2015 10:45:07 GMT
Server: akka-http/2.3.9

8.8: incorrect IP format

As errors are presented in plain text, this behaviour is expected. You could easily JSONify all errors by:

JSONifying by hand where you handle it manually (like case Left(errorMessage) => ToResponseMarshallable(BadRequest -> errorMessage)),
overriding default exception handler (http://doc.akka.io/api/akka-stream-and-http-experimental/current/index.html#akka.http.server.ExceptionHandler)
overriding default rejection handler (http://doc.akka.io/api/akka-stream-and-http-experimental/current/index.html#akka.http.server.RejectionHandler)
It's easy to do but goes beyond simple example like this one - not every project needs well-formed JSON APIs.

The behaviour is correct, but it can be annoying. I would want to do simply complete(StatusCodes.NotFound), but as the clients I'm dealing with often only accept application/json, they get a quite unhelpful 406.
I found the simplest way to deal with it was something like:
  implicit val m: ToResponseMarshaller[StatusCode] = Marshaller.oneOf(
    Marshaller.fromStatusCode,
    Marshaller.withFixedContentType(ContentTypes.`application/json`) { s =>
      HttpResponse(s, entity = HttpEntity(ContentTypes.`application/json`,
        s"{\"message\":\"${s.defaultMessage}\"}"))
    }
  )

I don't think it makes sense to build this in to the default marshaller.

@quelgar That's a very interesting approach, thanks for sharing!

authors: jaceklaskowski luksow quelgar

repo: theiterators/akka-http-microservice


text:
App settings with disabling head-up notifications

Hi, i dont like huge head-up notifications over screen during playback, so i make app settings with the possibility disable this notifications. Please merge, thx :)

Thank you.

authors: lukasmesicek thekirankumar

repo: thekirankumar/youtube-android-auto


text:
Add Variety of Encryption Methods

I would like to propose a feature that adds support for multiple encryption algorithms in Cipherion. Currently, the project exclusively uses AES encryption. By implementing additional encryption methods, we can enhance the flexibility and security options available to users.

Hi @Rishitshivam ,
This idea sounds good to me, I'm assigning this issue to you. 👍

#7

authors: Rishitshivam thelegendev

repo: thelegendev/Cipherion


text:
[Maintenance] No updates?

Hello! Just wanted to know if the project is on hold or cancelled. I am really willing to contribute. Thanks!

It's not dead, I'm just not having the time to write.

Thanks for the answer, looking forward for this =)

authors: felipecustodio thelostt

repo: thelostt/ricing


text:
Some problem about use self defined params in config.toml

1. Is there some documents for adding self defind params in config.toml?

2.How can i use other icon , such as fa-icon rather ti-icon. I use fa-icon, but it seems take no effect. Is there anything else i should change at the same time?

3. How can i adjust image width in my markdown file

this is a free template and we comment in the code. that's why there is no other documentation.

We used themify icon pack in this template. so you can't use fa-icon, if you need more icon then visit : https://themify.me/themify-icons

In markdown file. the image will adjust automatically.

I see, thanks a lot

repo: themefisher/parsa-hugo


text:
[components] Drawer

We need to implement the Drawer Label component as described in the core library.
https://flowbite.com/docs/components/drawer/
Describe the solution you'd like
PR must have:

Component (w/ Theme support)
Storybook
Documentation
Unit test

Describe alternatives you've considered
n/a
Additional context
n/a

Why is drawer not/no longer in this repo? https://github.com/themesberg/flowbite-react/commit/6e2b0911ce566b3ec91ebd775fbfde7047669f36

However, there is a PR to implement it: https://github.com/themesberg/flowbite-react/pull/1265

@rluders I messed up when copy pasting link earlier, I wanted to point out drawer being commented out in components.tsx
Thanks for the link to #1265  👍

@dhensen yet, it was never available as a component here. It is just commented in the sidebar to make it easy to enable it when it gets created.

authors: NoHaxito dhensen rluders

repo: themesberg/flowbite-react


text:
feat(list.stories.tsx): add horizontal stories

[x] I have followed the Your First Code Contribution section of the Contributing guide

Add list horizontal stories
There are no breaking API changes.

@SutuSebastian This PR is ready to be merged 🙏


text:
yield* test now fails with iojs

no idea why
1a85931965fdc519631bd933d895bcc4f499c675

yield* iterates through the iterable ~_~

repo: thenables/composition


text:
Get reliable body response on error.

Certain responses (pretty JSON) cause issues when you try to explode the raw response. This affects the Google provider in my experience. Using the getBody method should be more reliable.
Might be related to #193.

Any thoughts on this @ramsey or @alexbilbie? This is causing breaking issues for me when using the Google+ provider.

Sorry, @dolfelt. I was traveling when you submitted this and haven't been able to look yet. This fixing the breaking issues you were seeing?

@ramsey Yep. The problem is that the error response coming back from Google is formatted JSON. The JSON itself has line breaks in it.
When using this:
$raw_response = explode("\n", $e->getResponse());
$response = end($raw_response);

It causes the $response object to come back as }, rather than the whole JSON object.

Thanks, @dolfelt!

authors: dolfelt ramsey


text:
Check graphApiVersion format

Hi!
graphApiVersion param could be checked for proper format, to have
letter v at beginning:
v2.7 vs 2.7
This might help catch earlier if improper format is used.

I would be OK with this if someone would like to make a PR for it! :)

Alright, added checks, it pretty annoyed me when had 2.4 in app configuration and facebook requests resulted in 404.

Merged in #26. :)

authors: SammyK pmaselkowski


text:
Implement all standard functions listed in GatewayInterface

I found myself needing to add void() and capture() functions so I could test my project, and then it sort of took off. \Omnipay\Common\GatewayInterface lists functions which should be standard in any gateway, so I just implemented a dummy version of all of them.

Makes sense to me. If we would really want to complete, we should also allow for a redirect response probably though.

Noted, I have a massive backlog of real world work at the moment, will try to clear my github/omnipay backlog early next week.

+1 - Having the refund method on Dummy will be super-useful!

@coatesap comment about the docblocks is correct -- these need to be fixed.
Also I see that some parts of the markup in the class docblock have changed, e.g. the headings removed.  I see no good reason for that.

OK notwithstanding the fact that travis is passing the tests, this PR needs the docblocks fixed before I can merge.

@delatbabel The GatewayInterface says the methods return a RequestInterface.
@jtgrimes I'd really like to see this merged. You OK with me doing a new PR based on this with the docblocks fixed?

@kynx - you bet! I'm sorry I lost track of this PR - if you want to pick it up, that's great!

@jtgrimes Is your fork at https://github.com/jtgrimes/omnipay-dummy now redundant? Can we move back to using https://github.com/thephpleague/omnipay-dummy? (I think so, just would like to confirm).

@rquadling yep - it was merged in and my fork is actually behind the current repo - definitely switch back.

authors: barryvdh coatesap delatbabel jtgrimes kynx rquadling

repo: thephpleague/omnipay-dummy


text:
Callable type hints

May I suggest the removal of the callable type hints in the development branch?
When I provide [ SomeClass::class, 'methodName' ] as a handler (implying that SomeClass be resolved from the DI container), multiple warnings are raised saying that methodName should not be invoked as a static method (because it isn't static). I can work around the warnings by prepending the @ to the map statement, but I don't think that's a decent solution.
Worse even, when I provide 'SomeClass::methodName' as handler (which should be legal), a fatal error is raised.

With all my testing, these situations should be fine, however, I will look in to it and ensure they work before the release of 2.0.0
—
Sent from Mailbox
On Sat, Sep 19, 2015 at 5:52 PM, Bernardo notifications@github.com
wrote:

May I suggest the removal of the callable type hints in the development branch?
When I provide [ SomeClass::class, 'methodName' ] as a handler (implying that SomeClass be resolved from the DI container), multiple warnings are raised saying that methodName should not be invoked as a static method (because it isn't static). I can work around the warnings by prepending the @ to the map statement, but I don't think that's a decent solution.
Worse even, when I provide 'SomeClass::methodName' as handler (which should be legal), a fatal error is raised.
Reply to this email directly or view it on GitHub:
https://github.com/thephpleague/route/issues/71

Is everything left as default for strategies etc? Trying to determine whether the warnings/errors are being triggered in Route or Container as there is a unit test for each of those callable types for the RequestResponseStrategy

What if... you'd pass some kind of object that is a callable.
class ContainerCallable
{
    private $container;

    public function __construct(ImmutableContainerInterface $container)
    {
        $this->container = $container;
    }

    public function withInvokable($invokable)
    {
         $that = clone($this);
         $that->invokable = $invokable;
         return $that;
    }

    public function __invoke()
    {
        return $this->container->call($this->invokable);
    }
}

$callable = new ContainerCallable($container);

$router->get('/foo', $callable->withInvokable([SomeClass::class, 'methodName']));

Just exploring the use of decoration here.

Well, is_callable should actually return true on those types of callables even if they technically are not, running tests with E_ALL and they all pass. This is why I'm wondering if it's the ParamStrategy and it's failing in the container from some sort of oversight on my part?

For a quick and dirty example.
<?php

class Something
{
    public function action()
    {
        return 'Hello, World!';
    }
}

$callable1 = [Something::class, 'action'];
$callable2 = 'Something::action';

var_dump(is_callable($callable1)); // true
var_dump(is_callable($callable2)); // true

function test(callable $callable) {
    return is_callable($callable);
}

var_dump(test($callable1)); // true
var_dump(test($callable2)); // true

Valid across PHP5.5.0 to PHP7.0. Would also be valid in PHP5.4 without the ::class constant.
https://3v4l.org/gJroH

Oh wait, different results when I click the results link. My bad on strict standards, callable type hint !== is_callable. I'll fix this.

Thanks, that's exactly what I meant.
You might also want to consider the third test I've added:
https://3v4l.org/hubg8
This simulates a scenario where non-class-name names are used in a DI container.
Removing the callable type hint should be sufficient to fix that, but you might want to incorporate it in to the unit tests.

As the callable type hint and is_callable are not the same (baffling as to why) I'll be removing the type hint throughout the tree and swapping for an is_callable check until the point where a solid callable is built within the dispatcher. That should cover all bases.
Thanks for picking up on this, it's annoying as my environment has been ignoring E_ALL for some reason that I can't figure out.

Would it also be possible to remove the type hint from the StrategyInterface?
It would allow $controller to be null. This could be useful for dynamic routing strategies, where the controller is determined by the dispatcher based on other information from $this->request or $vars.
I can work around this by using a dummy callable, but it's not the most elegant solution.

I'd prefer it to stay in as by that point a callable has been built and it would require more checks in the default strategies to ensure it can be invoked if it is not there.

authors: hannesvdvreken philipobenito thebigb

repo: thephpleague/route