text:
Expose Cluster health metrics

What this PR does / why we need it:
This PR exposes a new Interoperator custom metrics called interoperator_cluster_up.
The interoperator_cluster_up exposes the reconciliation status of the provisioner in the clusters. This gives an idea of the health of the cluster. The reconciliation fails when the clusters are not accessible or the provisioner is unhealthy.

Metric
Labels
Description

interoperator_cluster_up
cluster
State of the clusters. 0 - down  1 - up

Does this PR introduce a user-facing change?
The interoperator_cluster_up can be scraped from Prometheus endpoint of the multiclusterdeployer.
Additional documentation

Interoperator Metrics Documentation
Feature: HCPCFS-3013

I created these Grafana dashboards for testing. If you feel these are useful, then I will add these to our Grafana sample.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n+n+n is succeeded.

Do you plan to add any unit tests for these changes?

Do you plan to add any unit tests for these changes?

For effective unit testing we need to mock implementations of the prometheus.Counter and prometheus.Registerer interfaces. I felt this might be overkill in our scenario.
The changes are already covered by the existing testcases. I will add some assertions using ToFloat64 exposed by prometheus testutil

authors: Pooja-08 anoopjb vinaybheri


text:
Could you upload the stemcell image to cn-northwest-1?

Currently the images just have to following regions available:
us-gov-west-1: ami-5361f732
ap-northeast-1: ami-a29966dd
ap-northeast-2: ami-ab14bcc5
ap-south-1: ami-3c81ad53
ap-southeast-1: ami-3bc0fd47
ap-southeast-2: ami-15b56677
ca-central-1: ami-3d3aba59
eu-central-1: ami-10301bfb
eu-west-1: ami-7f7d4406
eu-west-2: ami-ad9478ca
eu-west-3: ami-ce68d9b3
sa-east-1: ami-6d306e01
us-east-1: ami-8f9afdf0
us-east-2: ami-85d3efe0
us-west-1: ami-0c7e656c
us-west-2: ami-47661f3f
cn-north-1: ami-d105dbbc
** Example extracted from version light-bosh-stemcell-3586.16-aws-xen-hvm-ubuntu-trusty-go_agent
It would really be helpful. Thanks!

Thanks - we'll be tracking this work in Story #158503787.

Going to close this issue as we've been publishing light stemcells to cn-northwest-1 since September.
e.g., from light-bosh-stemcell-170.5-aws-xen-hvm-ubuntu-xenial-go_agent.tgz/stemcell.MF:
---
name: bosh-aws-xen-hvm-ubuntu-xenial-go_agent
version: '170.5'
bosh_protocol: '1'
sha1: da39a3ee5e6b4b0d3255bfef95601890afd80709
operating_system: ubuntu-xenial
stemcell_formats:
- aws-light
cloud_properties:
  ami:
    us-gov-west-1: ami-36e68357
    ap-northeast-1: ami-0f24b194859a2b2ce
    ap-northeast-2: ami-046cdc2a44f8cd11b
    ap-south-1: ami-0c254c5728469884c
    ap-southeast-1: ami-0feed6c5b34d50c40
    ap-southeast-2: ami-00202119002231c81
    ca-central-1: ami-088a4d7ada337154a
    eu-central-1: ami-0ce57dc6e1121ab03
    eu-west-1: ami-051b094309d3af8e4
    eu-west-2: ami-06a229cebecbe4ba1
    eu-west-3: ami-04de5962a8093fdf1
    sa-east-1: ami-0bf04826c653abcc2
    us-east-1: ami-0f229395f95f6490f
    us-east-2: ami-01db65f19ea1272b4
    us-west-1: ami-0b312c13b491d7ec7
    us-west-2: ami-0b69af436b34ce2ae
    cn-northwest-1: ami-0492b3e1be7e504fc
    cn-north-1: ami-03bd762fd953b9de4

source: gharchive/issue

authors: Rydros dpb587-pivotal jrussett

repo: cloudfoundry/bosh-deployment

license_type: permissive

license_source: github-api


text:
Websockets timeout with HAProxy

Hi,
Were using WebSockets with the HAProxy and its timing out after 5 mins. See the simple example https://gist.github.com/att-bdpaas/af45d4703137244ded71.
We tried using SO_KEEPALIVE but this only sends a keep alive packet to the HAProxy every 2hrs, and it doesn't keep the connection from the client side alive.
Looking at the HAProxy Documentation there seems to be a lot of options related to this problem:

The timeout tunnel which overrides the default timeout client and timeout server and would only be used for WebSockets, see doc.
It seems in our version (1.5-dev19) the default connection is TUN but it seems to be changing to KAL in 1.5dev21, see doc.
Many stackoverflows suggestion using http-server-close along with http-pretend-keepalive

Thanks,
@tlabeeuw + @chendrix

@tlabeeuw We'll be updating HAProxy to 1.5.10 in the next cf-release.

authors: att-bdpaas dieucao

repo: cloudfoundry/cf-release


text:
update global cli flags documentation

Related to this PR: https://github.com/cloudfoundry/bosh-cli/pull/634

FYI i'm waiting on PR to be merged and new CLI for this PR

https://github.com/cloudfoundry/bosh-cli/pull/634 is merged now. I guess this can be merged then as well

!! We have to update the cli version first in this PR before we merge it !!

source: gharchive/pull-request

authors: fmoehler lnguyen

repo: cloudfoundry/docs-bosh

license_source: bigquery


text:
Log-cache process consuming 50% of the memory in the VMs

Hi,
Its more of a question -I can see log-cache process is  consuming around 50% of the memory in my doppler VMs. So Is this a normal behavior (50% of total memory) for log-cache since its persisting data in memory.
Is there a way to flush out all the logs ?
Thanks

Yes, this is expected behavior. Log Cache will continually monitor memory usage on the VMs, and drop logs as needed so as not to overwhelm the system. With a rough target of 50%, we haven't seen this adversely affect other components on the system.
Note that this target is a percentage, not an absolute amount, so scaling the VMs will not change this.
If you're seeing issues on your Doppler VMs, please let us know! You can adjust the memory usage target with the memory_limit_percent property (https://github.com/cloudfoundry/log-cache-release/blob/develop/jobs/log-cache/spec#L35), but we don't expect most folks to have to use that.

I'm going to close this out for now; please let us know if you have any further questions!

repo: cloudfoundry/log-cache


text:
Remove unused metron_endpoint.dropsonde_port property

Description

Remove unused BOSH property metron_endpoint.dropsonde_port and associated config field from traffic controller
Pass GRPCAddress rather than UDPAddress when creating a test server. gRPC-Go v1.52.0+ will error if the provided endpoint is empty: https://github.com/grpc/grpc-go/pull/5732

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing performed?

[X] Unit tests
[X] Integration tests
[ ] Acceptance tests

Checklist:

[X] This PR is being made against the main branch, or relevant version branch
[ ] I have made corresponding changes to the documentation
[ ] I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

Should this be marked as a breaking change?

I don't think it's a breaking change as I don't believe the property has been effective since traffic controller switched to using gRPC for metrics in this story.

repo: cloudfoundry/loggregator-release


text:
Too many container need destory, however, this parameter (diego.executor.garden_healthcheck.timeout) setting is too large to be unreasonable?

Hi,:
Recently, I had a problem that only happens when I redeploy pivotal cloud foundry.
the diego.executor.garden_healthcheck.timeout is 600, but we have about 50 containers need destoryed,  It takes too much time, and cause the post-start.sh failed. For us, this has been a long time, is there have some better suggestions to solve this problem?
Version:
PAS 2.1.6
Thanks.

Hi, @wdxxs2z,
Since you're using PCF, please open a support ticket with Pivotal to get assistance in resolving this issue.
Thanks,
Eric, CF Diego PM

repo: cloudfoundry/rep


text:
Fix OIDC well-known endpoint to be in compliance with spec

This change provides a fix for issue #652
As per the spec, issuer value returned by the config should be identical to the <issuer_url> used to obtain the config (ex: <issuer_url>/.well-known/openid-configuration) and the iss claim in the id_token

Coverage increased (+0.004%) to 86.49% when pulling 94c69d16339c970a654b62820d0b557767763d24 on GESoftware-CF:fix/oidc_well_known_endpoint into 51d1983a25a8de9997253c80a3dbfedc952f72ad on cloudfoundry:develop.

This PR changes the endpoint from
/.well-known/openid-configuration

to
/oauth/token/.well-known/openid-configuration

That is a breaking change we can't accept. Instead we want this PR to change
/.well-known/openid-configuration

to
/.well-known/openid-configuration
/oauth/token/.well-known/openid-configuration

This should also limit the changes to existing test cases, and just introduce new test cases.
unless you have a compelling reason why the old endpoint shouldn't continue to function

@fhanik Fair enough. I will update the PR

@bsekar Are you able to update the PR based on comments from @fhanik
We would like to release this in the upcoming version aka 4.6.0

I can fix it. https://github.com/cloudfoundry/uaa/commit/4b8e9a039d2d97b49d6268ae31c59b016bb6ef5c

Thanks @fhanik @sreetummidi

Is this going to be included in release 4.6? I'm still blocked by this when trying to make it work with k8s. thx.

@maplain Yes, this work is in develop which means it should be included in the next release.

Hi, @jhamon thanks for the reply. I did try to do ./gradlew build both on prerelease/4.6.0 and develop, but they all failed a few tests. Could you please give me some advice on how to try this out in deployment? Any help is appreciated!

@maplain Have you ever run the tests successfully before? Or is this your first time running them?
I can give more useful advice if you can provide more detail about the failures you're seeing.

Some of the SSL tests require certificates to be generated. The .travis.yml file really helps to understand what our test suites do

@jhamon yes, this is my first time. What I did are basically just: pull corresponding branch and run a './gradlew build'.
logs are here: log.tar.gz.
Failed tests are:
DefaultSecurityContextAccessorTests. zoneAdminClientIsAdmin
DefaultSecurityContextAccessorTests. zoneAdminUserIsAdmin
DefaultSecurityContextAccessorTests. zoneAdminUserIsNotAdmin_BecauseOriginIsNotUaa

all because of NullPointerException. Looks like I may need to provide something here?

@maplain ok, those tests should work 100% every time unless you broke them yourself.
Make sure you run Java 8, and that JAVA_HOME is correctly set, then
./scripts/travis/install-ldap-certs.sh
./gradlew test

and it should fly through.

@fhanik thanks. this is what I got:
kubo@jumphost:~/uaa$ java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
kubo@jumphost:~/uaa$ echo $JAVA_HOME
/usr/lib/jvm/java-1.8.0-openjdk-amd64
kubo@jumphost:~/uaa$  ./scripts/travis/install-ldap-certs.sh
Generating keystore file for server.
Exporting certificate for client
Certificate stored in file </tmp/valid-self-signed-ldap-cert.jks.crt>
Generating keystore file for server.
Exporting certificate for client
Certificate stored in file </tmp/expired-self-signed-ldap-cert.jks.crt>
Installing /tmp/expired-self-signed-ldap-cert.jks.crt with alias expired-self-signed-ldap-cert
Installing /tmp/valid-self-signed-ldap-cert.jks.crt with alias valid-self-signed-ldap-cert
kubo@jumphost:~/uaa$ ./gradlew test
:compileJava UP-TO-DATE
:compileJava took 2ms
:processResources UP-TO-DATE
:processResources took 1ms
:classes UP-TO-DATE
:classes took 0ms
:compileTestJava UP-TO-DATE
:compileTestJava took 1ms
:processTestResources UP-TO-DATE
:processTestResources took 1ms
:testClasses UP-TO-DATE
................................................
................................................
org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminUserIsNotAdmin_BecauseOriginIsNotUaa FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:120

org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminUserIsAdmin FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:101

org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminClientIsAdmin FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:134
org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests took 36ms
org.cloudfoundry.identity.uaa.security.X509ExpiryCheckingTrustManagerTest took 22ms
org.cloudfoundry.identity.uaa.security.CsrfAwareEntryPointAndDeniedHandlerTest took 6ms
Gradle Test Executor 3 took 7ms
Gradle Test Run :cloudfoundry-identity-server:test took 164ms

2432 tests completed, 3 failed, 13 skipped
:cloudfoundry-identity-server:test FAILED
:cloudfoundry-identity-server:test took 149176ms

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':cloudfoundry-identity-server:test'.
> There were failing tests. See the report at: file:///home/kubo/uaa/server/build/reports/tests/test/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

@maplain this is a clean branch?
Let's try this
git stash
git checkout develop
git pull
git clean -fd
./gradlew clean
./scripts/travis/install-ldap-certs.sh
./gradlew test

ie, you must try this on a clean working branch. What we are trying to make sure is that you have a passing test suite before you make any changes. That way you know the changes you put in are either passing or not.

@fhanik I understand. I changed nothing. Like I said above, I just want to have a build that I can deploy since current latest version 4.5 still has this .well-known/openid-configuration bug blocking integration with k8s.
kubo@jumphost:~/uaa$ git stash
No local changes to save
kubo@jumphost:~/uaa$ git checkout develop
Already on 'develop'
Your branch is up-to-date with 'origin/develop'.
kubo@jumphost:~/uaa$ git pull
remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (1/1), done.
From https://github.com/cloudfoundry/uaa
   629b4b6..d593f29  develop    -> origin/develop
Updating 629b4b6..d593f29
Fast-forward
 uaa/src/test/java/org/cloudfoundry/identity/uaa/integration/feature/FacebookLoginIT.java   | 15 +++++++++++----
 uaa/src/test/java/org/cloudfoundry/identity/uaa/integration/util/IntegrationTestUtils.java |  9 ++++++++-
 2 files changed, 19 insertions(+), 5 deletions(-)
kubo@jumphost:~/uaa$ git clean -fd
kubo@jumphost:~/uaa$ ./gradlew clean
:clean
:clean took 1ms
:cloudfoundry-identity-client-lib:clean
:cloudfoundry-identity-client-lib:clean took 2ms
:cloudfoundry-identity-model:clean
:cloudfoundry-identity-model:clean took 5ms
:cloudfoundry-identity-samples:clean UP-TO-DATE
:cloudfoundry-identity-samples:clean took 0ms
:cloudfoundry-identity-server:clean
:cloudfoundry-identity-server:clean took 64ms
:cloudfoundry-identity-uaa:clean UP-TO-DATE
:cloudfoundry-identity-uaa:clean took 0ms
:cloudfoundry-identity-samples:cloudfoundry-identity-api:clean UP-TO-DATE
:cloudfoundry-identity-samples:cloudfoundry-identity-api:clean took 0ms
:cloudfoundry-identity-samples:cloudfoundry-identity-app:clean UP-TO-DATE
:cloudfoundry-identity-samples:cloudfoundry-identity-app:clean took 1ms

BUILD SUCCESSFUL

Total time: 0.907 secs
Task timings:
Test timings:
kubo@jumphost:~/uaa$ ./scripts/travis/install-ldap-certs.sh
Generating keystore file for server.
Exporting certificate for client
Certificate stored in file </tmp/valid-self-signed-ldap-cert.jks.crt>
Generating keystore file for server.
Exporting certificate for client
Certificate stored in file </tmp/expired-self-signed-ldap-cert.jks.crt>
Certificate already installed. Replacing it
Certificate already installed. Replacing it
kubo@jumphost:~/uaa$ ./gradlew test
:compileJava UP-TO-DATE
:compileJava took 0ms
:processResources UP-TO-DATE
:processResources took 0ms
.....
org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminUserIsNotAdmin_BecauseOriginIsNotUaa FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:120

org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminUserIsAdmin FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:101

org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests > zoneAdminClientIsAdmin FAILED
    java.lang.NullPointerException at DefaultSecurityContextAccessorTests.java:134
org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests took 21ms
org.cloudfoundry.identity.uaa.security.X509ExpiryCheckingTrustManagerTest took 21ms
org.cloudfoundry.identity.uaa.security.CsrfAwareEntryPointAndDeniedHandlerTest took 5ms
Gradle Test Executor 3 took 5ms
Gradle Test Run :cloudfoundry-identity-server:test took 165ms

2432 tests completed, 3 failed, 13 skipped
:cloudfoundry-identity-server:test FAILED
:cloudfoundry-identity-server:test took 151511ms

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':cloudfoundry-identity-server:test'.
> There were failing tests. See the report at: file:///home/kubo/uaa/server/build/reports/tests/test/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2 mins 41.056 secs
Task timings:
    745ms  :cloudfoundry-identity-client-lib:test
   1867ms  :cloudfoundry-identity-model:test
   1284ms  :cloudfoundry-identity-server:compileJava
   4479ms  :cloudfoundry-identity-server:compileTestJava
 151511ms  :cloudfoundry-identity-server:test
Test timings:
   5270ms  org.cloudfoundry.identity.uaa.scim.bootstrap.ScimGroupBootstrapTests
   5491ms  org.cloudfoundry.identity.uaa.provider.saml.LoginSamlAuthenticationProviderTests
   6004ms  org.cloudfoundry.identity.uaa.client.ClientAdminBootstrapTests
   8886ms  org.cloudfoundry.identity.uaa.scim.jdbc.JdbcScimUserProvisioningTests
  20788ms  org.cloudfoundry.identity.uaa.scim.endpoints.ScimGroupEndpointsTests
  21044ms  org.cloudfoundry.identity.uaa.util.CachingPasswordEncoderTest

or I shouldn't do './gradlew build' at all?
my goal is to make uaa work with k8s.
my problem is version 45 still has '/.well-known/openid-configuration' endpoint, but issuer being '/oauth/token' so you will see
E0825 18:27:30.380495   18382 oidc.go:178] oidc authenticator: failed to fetch provider discovery data: missing required field subject_types_supported

in kube-apiserver's log.
kubo@jumphost:~/kubo-deployment$ curl --cacert ./ca.pem -H "Accept: application/json"  https://192.168.112.3:8443/login | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   372    0   372    0     0   3275      0 --:--:-- --:--:-- --:--:--  3292
{
  "app": {
    "version": "4.5.0"
  },
  "links": {
    "uaa": "https://192.168.112.3:8443",
    "passwd": "/forgot_password",
    "login": "https://192.168.112.3:8443",
    "register": "/create_account"
  },
  "zone_name": "uaa",
  "entityID": "192.168.112.3:8443",
  "commit_id": "df80f63",
  "idpDefinitions": {},
  "prompts": {
    "username": [
      "text",
      "Email"
    ],
    "password": [
      "password",
      "Password"
    ]
  },
  "timestamp": "2017-07-21T15:45:01-0700"
}

kubo@jumphost:~/kubo-deployment$ curl --cacert ./ca.pem  https://192.168.112.3:8443/.well-known/openid-configuration | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1141    0  1141    0     0  11291      0 --:--:-- --:--:-- --:--:-- 11410
{
  "issuer": "https://192.168.112.3:8443/oauth/token",
  "authorization_endpoint": "https://192.168.112.3:8443/oauth/authorize",
  "token_endpoint": "https://192.168.112.3:8443/oauth/token",
  "token_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "client_secret_post"
  ],
  "token_endpoint_auth_signing_alg_values_supported": [
    "RS256",
    "HS256"
  ],
  "userinfo_endpoint": "https://192.168.112.3:8443/userinfo",
  "jwks_uri": "https://192.168.112.3:8443/token_keys",
  "scopes_supported": [
    "openid",
    "profile",
    "email",
    "phone",
    "roles",
    "user_attributes"
  ],
  "response_types_supported": [
    "code",
    "code id_token",
    "id_token",
    "token id_token"
  ],
  "subject_types_supported": [
    "public"
  ],
  "id_token_signing_alg_values_supported": [
    "RS256",
    "HS256"
  ],
  "id_token_encryption_alg_values_supported": [
    "none"
  ],
  "claim_types_supported": [
    "normal"
  ],
  "claims_supported": [
    "sub",
    "user_name",
    "origin",
    "iss",
    "auth_time",
    "amr",
    "acr",
    "client_id",
    "aud",
    "zid",
    "grant_type",
    "user_id",
    "azp",
    "scope",
    "exp",
    "iat",
    "jti",
    "rev_sig",
    "cid",
    "given_name",
    "family_name",
    "phone_number",
    "email"
  ],
  "claims_parameter_supported": false,
  "service_documentation": "http://docs.cloudfoundry.org/api/uaa/",
  "ui_locales_supported": [
    "en-US"
  ]
}
kubo@jumphost:~/kubo-deployment$ curl --cacert ./ca.pem  https://192.168.112.3:8443/oauth/token | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   108    0   108    0     0   1047      0 --:--:-- --:--:-- --:--:--  1048
{
  "error": "unauthorized",
  "error_description": "An Authentication object was not found in the SecurityContext"
}
kubo@jumphost:~/kubo-deployment$ curl --cacert ./ca.pem  https://192.168.112.3:8443/oauth/token/.well-known/openid-configuration | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   108    0   108    0     0   1089      0 --:--:-- --:--:-- --:--:--  1090
{
  "error": "unauthorized",
  "error_description": "An Authentication object was not found in the SecurityContext"
}

The uaa I'm using is:
  value:
    name: uaa
    version: "45"
    url: https://s3.amazonaws.com/bosh-compiled-release-tarballs/uaa-45-ubuntu-trusty-3445.2-20170822-204123-42127651-20170822204129.tgz
    sha1: 41cb1ea7c1dca2cc8c4a815eb498a163321c3965

@maplain
Let us know if file:///home/kubo/uaa/server/build/reports/tests/test/index.html has a deeper stack trace.
If not, then you're test is failing on
assertTrue(new DefaultSecurityContextAccessor().isAdmin());

that means the code
new DefaultSecurityContextAccessor()

returns null
if this is the case, you have a botched Java runtime installed. This should obviously never happen. Install a new JDK and then clean you ~/.gradle caches and try again

{
  "error": "unauthorized",
  "error_description": "An Authentication object was not found in

the SecurityContext"
}
oh wow, this is something completely different. Let me look into this
Filip
On Fri, Aug 25, 2017 at 11:34 AM, Fangyuan Li notifications@github.com
wrote:

The uaa I'm using is:
value:
name: uaa
version: "45"
url: https://s3.amazonaws.com/bosh-compiled-release-tarballs/uaa-45-ubuntu-trusty-3445.2-20170822-204123-42127651-20170822204129.tgz
sha1: 41cb1ea7c1dca2cc8c4a815eb498a163321c3965
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/uaa/pull/672#issuecomment-325003596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAlExYimBdOB3y-_cRQRdOPSmYdrmAMvks5sbxOdgaJpZM4OltWA
.

@fhanik thanks a lot! here is the log.
log.tar.gz
at the same time, I'll reinstall jdk and try again.

@maplain JDK is probably fine, this is your actual error
java.lang.NullPointerException
	at java.lang.String.replace(String.java:2240)
	at org.cloudfoundry.identity.uaa.security.ContextSensitiveOAuth2SecurityExpressionMethods.replaceContext(ContextSensitiveOAuth2SecurityExpressionMethods.java:39)
	at org.cloudfoundry.identity.uaa.security.ContextSensitiveOAuth2SecurityExpressionMethods.replaceContext(ContextSensitiveOAuth2SecurityExpressionMethods.java:48)
	at org.cloudfoundry.identity.uaa.security.ContextSensitiveOAuth2SecurityExpressionMethods.hasAnyScope(ContextSensitiveOAuth2SecurityExpressionMethods.java:79)
	at org.springframework.security.oauth2.provider.expression.OAuth2SecurityExpressionMethods.hasScope(OAuth2SecurityExpressionMethods.java:106)
	at org.cloudfoundry.identity.uaa.security.ContextSensitiveOAuth2SecurityExpressionMethods.hasScopeInAuthZone(ContextSensitiveOAuth2SecurityExpressionMethods.java:88)
	at org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessor.isAdmin(DefaultSecurityContextAccessor.java:85)
	at org.cloudfoundry.identity.uaa.security.DefaultSecurityContextAccessorTests.zoneAdminClientIsAdmin(DefaultSecurityContextAccessorTests.java:134)

Ok. so we have two problems
https://login.run.pivotal.io/oauth/token/.well-known/openid-configuration is asking for username/password. this is a high priority for us to investigate.
and then you're unable to run the test suite for a strange reason.

@maplain mystery solved
https://login.run.pivotal.io/.well-known/openid-configuration
the current OIDC discovery endpoint is
/.well-known/openid-configuration
the
/oauth/token/.well-known/openid-configuration
is not yet available in a release. you will have to wait for that to come out.

@fhanik thanks for looking into this.
Isn't this the problem this PR(where our discussion happens) tries to address? I understand you have made changes to make /oauth/token/.well-known/openid-configuration available and I saw this change in develop and prerelease/4.6.0 branches, but not in 4.5 release.
so here comes why I was trying to build on develop. Because I was trying to get a 'self built release' that incorporates your changes mentioned above, thus I can deploy an uaa with '/oauth/token/.well-known/openid-configuration' enabled and to further verify k8s can successfully talk to uaa.
BTW, if you don't mind, may I ask the planned release date for 4.6?
Thanks again!

this error
{
  "error": "unauthorized",
  "error_description": "An Authentication object was not found in the SecurityContext"
}

shows that you are trying to access and endpoint that doesn't exist.
if you want to build your own release, that is super simple
./gradlew assemble

then deploy the WAR file in uaa/build/libs to your web server
The answer to why your tests fail is still a myster

@fhanik ok. I'm using bosh to deploy it. so I'm not clear how to tell bosh to use that WAR file. or maybe I should look into uaa-release. probably need to read some documentation firstly. anyway, really appreciate your help. and my tests, yeah, that is weird..

Here is how we create, finalize and upload a bosh release to bosh.io
https://github.com/cloudfoundry/uaa-release/blob/develop/scripts/perform-release.sh
In a nutshell, one command called
bosh create release
yields your stuff. so in uaa-release you would bump the UAA submodule to develop

cool. will look into that.

authors: bsekar coveralls fhanik jhamon maplain sreetummidi

repo: cloudfoundry/uaa


text:
Simplify paths

Drizzle's paths seem a lot more verbose than similar projects.
I'm not against verbosity, but in this case it makes partials and data significantly harder to use.
Examples
Paths
{{! Pattern Lab (fuzzy matching) }}
{{> components-ordered }} {{! or }} {{> components-lists-ordered }}

{{! Fabricator }}
{{> lists.ordered }}

{{! Drizzle }}
{{> patterns.components.lists.ordered }}

Data
{{! Pattern Lab }}
{{specimens.paragraph}}

{{! Fabricator }}
{{data.specimens.paragraph}}

{{! Drizzle }}
{{drizzle.data.specimens.contents.paragraph}}

Fixed with the data helper @erikjung built

authors: megnotarte tylersticka

repo: cloudfour/drizzle-builder

license: mit


text:
GetTopicConfigs takes much longer to return since PR #97

In version 2.1.0 the GetTopicConfigs was limited to just the cleanup.policy config https://github.com/cloudhut/kminion/blob/v2.1.0/minion/describe_topic_config.go#L22
However in PR #97 the limitation was removed https://github.com/cloudhut/kminion/pull/97/files#diff-ea87a33952172ffd5cd3de385e172c2398f88c1c76808a63919c6bed164fa4a8L23
In Kafka clusters with tens of thousands of topics this starts taking a very long time to return and eventually hits the 60 second timeout here https://github.com/cloudhut/kminion/blob/master/prometheus/exporter.go#L224 and/or promethues scrape timeouts.
Can the GetTopicConfigs function be modified to use the config option infoMetric.configKeys so it doesn't try to get all config items for the topics?

Thinking about, maybe it makes sense to cache topic config like metadata is https://github.com/cloudhut/kminion/blob/cc3d571a471a772b9e5b2a76830c9fb234f2775f/prometheus/collect_topic_info.go#L12
Topic configs won't change often.

Hey @rmb938 ,
thanks for filing this issue. Unfortunately I'm very busy at the moment, but during the holidays I should have some time to look into this.
I wasn't aware that requesting more/all topic configs has such a large impact on the performance for clusters with large numbers of topics. We will figure out something! Making it configurable via a config could be an option for sure, unsure if we should reuse the config from the infoMetric because it's been created specifically for one metric series. Good idea though!

I second this! Thanks for filing this @rmb938!
When I initially developed PR #97 my local benchmarks shows no impact when querying one or all topic configurations in kafka so I opted to do the filtering based on configured infoMetrics later when the metrics are exposed. We could definetly move the filter upper and only query the selected topic config keys in Kafka

Thanks @weeco , I completely understand being busy and have no issue staying on 2.1.0 until this is fixed.
@amuraru Yea it is a bit weird and I'm not 100% sure your PR caused the issue but it was the only one that seemed to make any change related to querying Kafka, however using a version from before your PR was merged in doesn't have the same performance issue.
It may make sense to "make metrics for the metrics" i.e add timer metrics to the Kakfa function calls so we could easily measure and record these types of perf issues.

authors: amuraru rmb938 weeco

repo: cloudhut/kminion

license: MIT


text:
Update Requirement documentation

Since it use expo in the development so it needs to configure expo module for the people who are going to use it in bare react native.
And since I do develop the project using bare react native and only need the upload feature so it seems not suitable for me to install the expo module.
Do you have any suggestion for it?

Hey @naufanituharish,
Would you please clarify what the issue is here?

Halo there, I was trying to use the react native cloudinary SDK in my react native project. I do develop the project using bare react native, not using expo. I could not use the SDK after installing it. The error said that I need to install expo module.
So I thought it's better to update the documentation to explain how to use the SDK in react native project that not use expo.
So it need to install expo module before I can use it in bare react native.
Here is the documentation to install expo module in bare react native
https://docs.expo.dev/bare/installing-expo-modules
Regards,
Naufan Harish

Hi @naufanituharish ,
Currently our SDK is supported with Expo only.  The decision was not taken lightly, and was following the community best practices.
I hope this helps.

That's what I said before, it is only support the development that using expo. So I thought it's better to update the documentation an mention it on the readme.
Regards,
Naufan Harish

@naufanituharish thx, i will pass that back to our docs team.

Please update your documentation soon. I spent the entire night going through your documentation trying to figure out why the upload was not working for me. Just came across this issue now and finally saw it only works with Expo React native project.

authors: atdcloud momohyusuf naufanituharish rnamba-cloudinary tommyg-cld

repo: cloudinary/cloudinary-react-native


text:
cannot use dpr(auto()) in React component (React SDK)

For which package is this issue?
React
Describe the issue in a sentence or two.
Hi, trying to upgrade cloudinary-react to use the updated frontend framework and having some trouble implementing image 'dpr'.
I have a custom reusable react "image" component that utilizes AdvancedImage, and I imported 'dpr' from cloudinary delivery folder. The custom image component has a 'imageDPR' prop and takes in a string, I have a function that calls dpr(auto()) or dpr(imageDPR input) on the cloudinary instance. Then passing that instance to AdvancedImage.
I'm getting an error that 'auto' is not defined.
I imported 'dpr' from the delivery folder, is there somewhere else I should import from?
Any help is appreciated... thank you.
Issue Type (Can be multiple)
[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[x] Behaviour - Functions aren’t working as expected
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Incorrect Types
[x] Other (Specify)
import {dpr} from "@cloudinary/url-gen/actions/delivery"; and using dpr(auto()) is returning an error
related cloudinary imports:
import { AdvancedImage, responsive, placeholder } from '@cloudinary/react'
import { Cloudinary } from '@cloudinary/url-gen';
import {dpr} from "@cloudinary/url-gen/actions/delivery";

function in component showing "auto" is not defined:
// imageDPR prop value is 'defaultAuto' and the below function returns error that auto is not defined...
function setImageDPR(imageDPR) {
    switch (imageDPR) {
      case 'defaultAuto':
        return dpr(auto());
      case imageDPR.length:
        return dpr(imageDPR.toString());
      default:
        return '';
    }
  }

Versions and Libraries (fill in the version numbers)
Node - v16.16.0
NPM - 8.11.0
Config Files (Please paste the following files if possible)
"@cloudinary/react": "^1.4.1",
"@cloudinary/url-gen": "^1.8.0",

Hey Leah,
setDPR('auto') is now deprecated. The new syntax will be setDPR(devicePixelRatio || 1). A user can use dpr_auto but this has no meaning on the Cloudinary servers.  (The legacy SDK replaces auto with a number, for example dpr_2).

Thanks!

authors: PixelCook leahwchang

repo: cloudinary/frontend-frameworks


text:
Shut down cluster

Hello, we have been recently migrating from a different PG operator to cloudnative-pg and the experience has been fantastic.
One feature I've been unable to find is the ability to place a specific cluster in 'shutdown' mode. Effectively to safely close off the database when not in use in order to save resources. Through the plugin I've found the hibernate command, which I think is what I'm looking for, but would it be possible to support that at the Cluster CRD? Something like spec.hibernate: true/false?
Thanks again for the great operator!

Hi Tom,
We had thought of using annotations for hibernation but decided to come out first with an "imperative" way of doing it.
Alternatively, if you want to shut down the database safely, you can fence it. That can be done using annotations. Pods will be up, but without using compute resources (definitely disk). If you want you can scale to 1 first, then fence.

authors: gbartolini tom-asmblr

repo: cloudnative-pg/cloudnative-pg


text:
[REFAC] - Standardize Bootstrap Controller

As part of the standardisation of the reconciliation loop for Greenhouse controllers, this controller needs to be updated to follow the common recommendation for the Reconciliation
Acceptance Criteria

[ ] Implement the Interface
[ ] Use the standardised patch for updating the status instead of the deferred update (if applicable)
[ ] Convert the tests to use test.TestSetup (if applicable) including creation of missing resources

This controller will be skipped for the standardisation

repo: cloudoperators/greenhouse


text:
Allow using a ServiceAccount in any Kubernetes namespace. Allow scoping IAM role to an entire Kubernetes namespace

what

Allow using a ServiceAccount in any Kubernetes namespace
Allow scoping IAM role to an entire Kubernetes namespace

why

Allow using a ServiceAccount in any Kubernetes namespace (wildcard service_account_namespace). Useful for unlimited preview environments where we deploy each pull request into a separate Kubernetes namespace
Allow scoping IAM role to a Kubernetes namespace (wildcard service_account_name). Provides the ability to scope the role to an entire namespace (use the namespace as a boundary) to allow any ServiceAccount in the namespace to assume the role

related

Closes #6

references

https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-technical-overview.html#iam-role-configuration:~:text=To scope a role to an entire namespace (to use the namespace as a boundary)%3A

notes
  If both var.service_account_namespace and var.service_account_name are provided and not equal to "*",
  then the role ARM will have one of the following formats:
  - if var.service_account_namespace != var.service_account_name: arn:aws:iam::<account_number>:role/<namespace>-<environment>-<stage>-<service_account_name>@<service_account_namespace>
  - if var.service_account_namespace == var.service_account_name: arn:aws:iam::<account_number>:role/<namespace>-<environment>-<stage>-<service_account_name>

  If var.service_account_name is provided and not equal to "*", and var.service_account_namespace == "*",
  then the role ARM will have format arn:aws:iam::<account_number>:role/<namespace>-<environment>-<stage>-<service_account_name>,
  and the policy will use "StringLike" in the test condition to allow ServiceAccounts in any Kubernetes namespace to assume the role (useful for unlimited preview environments)

  If var.service_account_name == "*",
  then `module.this.name` must be provided (to correctly name the role and policy),
  and the role ARM will have format arn:aws:iam::<account_number>:role/<namespace>-<environment>-<stage>-<name>,
  and the policy will use "StringLike" in the test condition to allow to scope IAM roles to a namespace (allow different ServiceAccounts in the same namespace to assume the role)

/test all

/test all

/test all

/test all

repo: cloudposse/terraform-aws-eks-iam-role


text:
--interface option on server create and update does not work

It's unclear what the format of the --interface argument data should be. I assume it's meant to be the JSON dict specified in the API documentation for interfaces. But this does not work:
$ cloudscale --debug server create --interface '{"network":"7f3ef3c8-8ae9-401b-a3d3-fe82925574c7"}' --image debian-10 --flavor flex-2 --name test-interface
2021-01-18 11:39:56,726 - cloudscale.log:INFO:Started, version: 0.6.2
2021-01-18 11:39:56,726 - cloudscale.log:INFO:Using profile default
2021-01-18 11:39:56,726 - cloudscale.log:INFO:API Token used: 2fbb...
⠋ Creating test-interface2021-01-18 11:39:56,727 - cloudscale.log:INFO:HTTP payload: {'name': 'test-interface', 'flavor': 'flex-2', 'image': 'debian-10', 'interfaces': ('{"network":"7f3ef3c8-8ae9-401b-a3d3-fe82925574c7"}',), 'use_public_network': True, 'use_private_network': False, 'use_ipv6': True}
2021-01-18 11:39:56,727 - cloudscale.log:INFO:HTTP POST to https://api.cloudscale.ch/v1/servers
⠙ Creating test-interface2021-01-18 11:39:56,855 - cloudscale.log:INFO:HTTP status code 400
API Response Error (400): {'interfaces': 'Invalid data. Expected a dictionary, but got str.'}

The problem here is that the argument is not unserialized to a Python dict and thus sent as a string. But simply unserializing the argument does not work as then the API complains about a confilict with the use_public_network and use_private_network parameters. These have to be completely omitted when using the interface parameter.
The easiest way to solve this is to correctly handle JSON argument data by unserializing it and omitting the other two parameters in this case. Some validation should be done to not silently ignore parameters and to catch invalid JSON data (that cannot be unserialized).
A more elegant way to solve this would be to define a syntax that is more suitable for a CLI tool for the interface argument data and then to convert this to the format expected by the API.
The same problem probably exists for the update command. But I did not look into this in depth.

Fixed in #47.

authors: ctx gaudenz

repo: cloudscale-ch/cloudscale-cli


text:
GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.13",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cce476954401e3421afafb25bbaa926050688b1d"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "cce476954401e3421afafb25bbaa926050688b1d",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ALSA: hda: intel-sdw-acpi: harden detection of controller\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.13 by commit cce476954401e3421afafb25bbaa926050688b1d. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000063

repo: cloudsecurityalliance/gsd-database


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.28 to before v4.4.289",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=46abc02175b3c246dd5141d878f565a8725060c9",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=25e9f88c7e3cc35f5e3d3db199660d28a15df639"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "46abc02175b3c246dd5141d878f565a8725060c9",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "25e9f88c7e3cc35f5e3d3db199660d28a15df639",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "phy: mdio: fix memory leak\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.4.289 by commit 25e9f88c7e3cc35f5e3d3db199660d28a15df639, it was introduced in version v2.6.28 by commit 46abc02175b3c246dd5141d878f565a8725060c9. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001494

repo: cloudsecurityalliance/uvi-database


text:
feat: make importer work with current storage design

Main points
This PR makes the block importer fully works with the in-memory EthStorage implementation, but performance is awful.
It works this way for each block to import:

For each block to import, each transaction is re-executed and the temporary account changes are stored in the storage and the transaction execution changes are collected to a vector.
After all transactions are re-executed in the block, the external block is converted to the internal block format with the related transactions and executions.
The storage state is rolled-back using reset to its initial state before all temporary data was stored.
The produced block with the is saved permanently to the storage.

The bottleneck of this flow is the reset method. Even the in-memory implementation is slow and can possibly be improved.
PostgreSQL is not working yet because save_account_changes method is not implemented, and it probably requires some changes to make it work. Saving temporary account changes to PostgreSQL without having a related block is not possible because the foreign key constraint that does not exist in the in-memory implementation, but exists in PostgreSQL.
It is clear that this approach is not the best and #222 is the correct way to handle this by splitting temporary and permanent storage.
Additional points

I removed the ConversionError enum in favor of anyhow error because it is how errors are being handled in the entire application. There was no specific use that required ConversionError to exist.
There are several possible conversion problems that I annotated with TODOs.

@renancloudwalk No. I save only the account changes first. Then reset and save block, transactions and account changes again.

repo: cloudwalk/stratus


text:
增加调整时间的接口

游戏开发过程中经常遇到时间相关的逻辑不好测试，有一个调时间的接口还是很方便测试的，直接修改底层获取时间的接口，没这个接口的话也可以在逻辑层绕过去，但是这个接口暴力有效。云大以为是否有必要？

如果你有这个需要, 可以在 config 里定义自己的 lualoader
然后在 lualoader 里改写 skynet.time/now 函数, 定义成你需要的样子.
在 2015年3月7日 下午3:50，snail notifications@github.com写道：

游戏开发过程中经常遇到时间相关的逻辑不好测试，有一个调时间的接口还是很方便测试的，直接修改底层获取时间的接口，没这个接口的话也可以在逻辑层绕过去，但是这个接口暴力有效。云大以为是否有必要？
—
Reply to this email directly or view it on GitHub
https://github.com/cloudwu/skynet/issues/246.

--
http://blog.codingnow.com

比如说有个需求是测试每天0点做什么事情，这个实现是用skynet.timeout来实现的，这种改法没办法影响到timer的触发。

又想了一下，在lua层改一下timer的实现，用sleep来做，修改时间的时候把timer thread wakeup一下，再判断时间到没到，也可以实现，就是麻烦一点。

类似 cron 的服务你应该单独做一个服务方便管理, 而不应该直接用 timeout . 这种定期活动就可以向 cron 服务注册申请和调整.
在 2015年3月8日 下午4:02，snail notifications@github.com写道：

比如说有个需求是测试每天0点做什么事情，这个实现是用skynet.timeout来实现的，这种改法没办法影响到timer的触发。
—
Reply to this email directly or view it on GitHub
https://github.com/cloudwu/skynet/issues/246#issuecomment-77738061.

--
http://blog.codingnow.com

嗯，是有一个单独的服务来管理的。每个服务还是有一些自己管理的timeout，如果调时间的话还是要保证这些timeout的触发，保持整个skynet网络的逻辑时间一致。

那这些 timeout 改成对唯一服务的 call 调用. 这个服务做时间安排.
ps. skynet response 可以用的上. 不要用 sleep.

好的

authors: cloudwu niuys

repo: cloudwu/skynet


text:
skynet怎么设置keepAlive 呀？

服务器需要进行掉线检测，skynet怎么设置keepAlive 呀？有相关文档、网页，或者相关代码，给个链接，谢谢了，大神！！！

你是要这玩意吗？
https://github.com/cloudwu/skynet/blob/master/examples/agent.lua#L27

@hanxi 多谢了


text:
wakeup多个coroutine时，中间抛error会停住，请问这个情况是设计如此吗？

类似这样的写法：
local skynet = require "skynet"

local coList = {}
local function wakeup()
        for k, co in pairs(coList) do
                skynet.wakeup(co)
        end
end

local function wait(i)
        local co = coroutine.running()
        coList[i] = co
        skynet.wait(co)
        if i == 5 then
                error("no:"..i)
        else
                skynet.error("yes:", i)
        end
end

skynet.start(function()
        for i=1, 10 do
                skynet.fork(wait, i)
        end
        skynet.fork(wakeup)

        -- skynet.sleep(1)
end)

到了i=5抛出错误时，只打印了前四个coroutine的log，就停住不动了。
但如果在最后sleep一下，则会继续打印6~10
看skynet.lua代码，suspend会把错误抛出，所以没有执行接下来的dispatch_wakeup。

造成这个问题的原因是 skynet 是由消息驱动的，fork 出来的 coroutine 并非由外部消息触发，所以必须借助已有消息。目前是放在 SUSPEND 指令中的。除了阻塞调用外，正常的消息处理完也会触发一次 SUSPEND ，但是异常消息不会。
该问题设计的时候就考虑过，但是考虑到完全没有外部消息的场合很少（基本上是做纯运算），所以并没有特殊处理。如果要解决这个问题，可以在 error 的时候注册一个 timeout 0 ，跑一个空消息即可。我已经提交了 patch 。

btw, 上面例子中的写法不推荐。因为目前并没有承诺 fork 的 coroutine 的唤醒次序。如果 wakeup 在  wait 之前先被运行，将导致 coList 中尚未写入 wait 的 coroutine 。

@cloudwu 这样会延迟wakeup_queue中co的执行，因为消息队列中可能已经有消息了。
#870 wakeup的co需要在新的消息之前处理完。

@hongling0 wakeup 的运行时机并没有做任何承诺（比其它消息先还是后），目前只保证 wakeup 本身的次序。插入 fork_queue 会导致 wakeup 本身无序，我倾向于在同一个位置分发 wakeup 的消息。

authors: cloudwu drinkwithwater hongling0


text:
更新socket.listen函数，返回id与port。当传入的port为0时，会返回绑定的随机端口

为了简化配置服务使用的端口，采用了系统随机端口。于是修改了socket.listen函数的返回值
local id, port = socket.listen('0.0.0.0', 0)
skynet.error(port)

do_bind 函数原型修改后，为何能编译通过？

此改动存疑，已 revert 。
现在采用另一种解决方法：https://github.com/cloudwu/skynet/commit/c8197328a4a17b5b1ec6cbac5bb36acb876558d1
socket.listen 变成一个阻塞函数，等待底层的 connect 消息。该消息现在会报告本地的 addr 和 port 。

authors: cloudwu zaxbbun


text:
Fix dockerfile

I believe this fixes #38

Thanks, testing this now!

authors: cloudymax lmunch

repo: cloudymax/pxeless


text:
Typo errors - Document parsing

I have trained Donut model in my custom dataset following this tutorial from @NielsRogge .
I have managed to get a decent accuracy 0.65% if I expect the values to be exactly the same (not using edit distance to compare expected value and prediction). I have been evaluating the results of the model and I have seen that the errors I get that don't help to get a better accuracy are related to typos.
They are small typo errors, like missing a number in value, wrong typo, missing quote... Do you know why this could be happening? Too much training?
For finetuning this model for you custom extraction task, is it neccessary to finetune encoder or decoder? Or can I just freeze the encoder and just train the decoder?
Thanks in advance! @gwkrsrch  @moonbings

Hello @WaterKnight1998 have you tried fine tuning with al layers? and for how many steps did you run the model?

repo: clovaai/donut


text:
Add secondary logos for presets

These are to be used at smaller sizes.

Closed with 8d2c06eb1906e2db2c8c6920a0746a089ba4190c

repo: cloverleaf/web


text:
Use tower-service to build more robust clients

Hi this project is fantastic!
I was curious if you'd be interested in possibly making the api use tower_service::Service intead of just using reqwest internally.
A couple big reasons this might be good is that you don't need to depend on reqwest directly which can be a heavy dep. You can let users easily configure how they might wanna do retries, timeouts, etc. It is easier to use a mock like tower-test to let users test their kube code.
Now tower is still getting worked on as you can currently see with the master branch but I know at least for some of my use cases I would love to have this support.
Example code that I have used before with the older tower-service but should work just the same with 0.3 is here https://github.com/LucioFranco/tower-consul/blob/master/src/lib.rs#L33
If you notice this entire crate doesn't depend on hyper but allows you to plug hyper in. Hyper 0.13 will also support Service out of the box.
I wrote this a bit quick but just wanted to start a discussion!

Hey there, thank you! And thanks for all your work on tower, even though I haven't actually gotten to use it yet.
Short answer; Yes, possibly!
Being able to replace reqwest has certainly been asked requested before :slightly_smiling_face:
Long answer
The ideas that tower presents very much align with a bunch of issues we already have tracked (#34, #78, possibly helps with #66 since that's not even in the reqwest async ver afaikt), and we do need a better testing story herein (which we don't even have an issue for atm).
That said, embedding a bunch more traits herein certainly looks like it'll make things a lot more complicated, and have a few questions:
Would this influence the server side parts of things? I.e. does it move it closer to something better support tower-web? And would this hinder compatibility with embedding within other web frameworks such as actix-web / rocket?
Would this work with streaming api calls without having a hard dependency on hyper or reqwest? Like, we need to embed the logic on how we deal with chunking, so presumably we need to bind to one http client anyway?
When is the tower release? :slightly_smiling_face: Not that I wanna add more pressure on this (going to be gone for about a month anyway), just curious what timelines you are working with.

So for server side of things, Im not sure exactly what you are looking for around this but it shouldn't affect anything because in the end it all turns into a future.
For streaming calls, that would be abstracted via the http-body crate which you should use anyways as the generic trait bound around Request<B: http_body::Body>.
So tower-service is already released which should enable you to support all the use cases you need right now.
Also sean's latest blog post talks about tower service which should explain it a bit better https://seanmonstar.com/
I am hopping to write soon a blog post that should explain how I think these pieces should fit together. I would also be happy to submit a PR at some point in the future to add this if no one else does :D

It makes a lot more sense now, thank you.
I would be happy to take a PR for this.

Hi @LucioFranco, I've been experimenting to swap reqwest with hyper (#376). I refactored all API requests (including WebSocket connection) to go through a single method that calls hyper::Client::request. Then started to experiment with tower and ended up with kube::Client with inner tower::Service :tada: However, I've been having trouble figuring out one last piece and I'd really appreciate your help. The PR is huge and messy (it's not meant to be reviewed/merged), so I'll try summarizing what I'm trying to achieve here.
I'm thinking of providing kube::Service based on hyper::Client for users to use by default so that their workflow is not affected. It's hyper::Client with Request modified based on kube::Config:
let client: HyperClient<_, Body> = HyperClient::builder().build(connector);
let inner = ServiceBuilder::new()
    .map_request(move |r| set_cluster_url(r, &cluster_url))
    .map_request(move |r| set_default_headers(r, default_headers.clone()))
    .service(client);

I'd like to handle Authorization header similarly, but it'll be async (may need to refresh the token) and can fail (returns kube::Error). What is the recommended approach?
This is currently done in kube::Client by calling Authentication::to_header and modifying the request before calling the inner service.
let (mut parts, body) = request.into_parts();
if let Some(auth_header) = self.auth_header.to_header().await? {
    parts.headers.insert(http::header::AUTHORIZATION, auth_header);
}

Because of some restrictions to make this fit in kube, the type of service used by kube::Client at the moment is
Buffer<BoxService<Request<hyper::Body>, Response<hyper::Body>, hyper::Error>, Request<hyper::Body>>

Buffer is necessary for cheap clone and not using generics to avoid type parameters in kube::Client.

I'm not good at this either; I would've hoped a .map_request with an async block could have worked, but if not, maybe it's possible to do a Layer for it, from what I have seen they should at least to handle errors and be async.

map_request with async block doesn't work because that makes Service<Future>.
Creating AuthLayer should work. We need AuthService with AuthFuture (a future that wraps Authentication::to_header(), inserting header, and calling inner service). (I'm not familiar with pinning and working with futures directly, so I need to play with them first.)
AuthLayer should be something that works similar to the following (based on the code you found), but without requiring Clone:
pub(crate) fn auth_layer<S>(
    auth: Authentication,
) -> impl Layer<
    S,
    Service = impl Service<
        Request<Body>,
        Response = Response<Body>,
        Error = BoxError,
        Future = impl Future<Output = Result<Response<Body>, BoxError>> + Send,
    > + Clone,
> + Clone
where
    S: 'static + Service<Request<Body>, Response = Response<Body>> + Clone + Send,
    S::Error: Send + Sync,
    BoxError: From<S::Error>,
    S::Future: Send,
{
    tower::layer::layer_fn(move |svc: S| {
        let auth = auth.clone();
        tower::service_fn(move |mut req: Request<Body>| {
            let auth = auth.clone();
            let mut svc = svc.clone();
            async move {
                if let Some(auth_header) = auth.to_header().await? {
                    req.headers_mut().insert(AUTHORIZATION, auth_header);
                }
                Ok(svc.call(req).await?)
            }
        })
    })
}

I don't think we can get rid of Clone, but hyper::Client is Clone so it works fine. Just pushed the initial implementation.

authors: LucioFranco clux kazk

repo: clux/kube-rs


text:
Code doesn't work without internet

Silently fails, no error or warning
Run yarn test produces empty out.svg
To test, turn off wifi on compy

Need to get better error reporting but issue categorized wrong


text:
How to format to other base?

怎么把 IBig, UBig 这些变成非十进制的字符串? 需要一个 from_str_radix 的反函数.

用官方的fmt接口就可以
let n = UBig::from_str_radix("1234", 10);
let s = format!("{:X}", n);

如果想转换成任意进制可以使用in_radix函数。
这些我之后都会放到guide里面，不过最近没什么时间写guide 😢

authors: cmpute oovm

repo: cmpute/dashu


text:
Remove libc as a dependency.

If you choose to remove the generated ioctls from (request #9), this pull request additionally removes the dependency on the libc crate by using std::os::raw::* definitions for c_int and c_ulong.

The std::os::*::raw types were deprecated in Rust 1.8 (rust-lang/rust#31551).

authors: Slabity docbrown

repo: cmr/ioctl


text:
Drop hospitalizations forecasts for most US territories

Drop hospitalizations forecasts for US territories that HHS does not report for. This filter is narrow so that other forecasts with missing actuals and/or scores continue to be carried through to the S3 bucket.

Let’s run the workflow in this branch before merging into dev

authors: kateharwood nmdefries

repo: cmu-delphi/forecast-eval


text:
Use full path in entrypoint

I use your container for my tests, and was trying to get it working in my Jenkins CI environment to automatically run tests against during builds.
Unfortunately, Jenkins with the Kubernetes plugin overwrites the WORKDIR on all containers it spins up, which causes this container to fail because it uses relative paths.
This PR fixes that.

This change is

Awesome! Thank you very much @veqryn

thank you!

authors: cnadiminti veqryn

repo: cnadiminti/docker-dynamodb-local


text:
[ACTION] Rename Sub Components to Configs

Part of Proposal-001 - Trigger and Deploy GitHub Action workflow from an upstream CNCF project

Task Description

In #102 we renamed project sub components to configs in proposal 1 to have clearer naming. More specifically, Falco has three different different drivers (ebpf, modern-ebpf, kmod) that are each a valid configuration of Falco, rather than subcomponents of Falco.
This issue tracks implementing this renaming.
New structure for projects.json

{
    "projects": [
        {
            "name": "falco",
            "organization": "falcosecurity",
            "configs": [
                "ebpf",
                "modern-ebpf",
                "kmod"
            ]
        }
    ]
}

Tasks

[ ] Rename sub_components to configs in projects.json
[ ] Update the project_trigger.sh to use the new JSON format
[ ] Rename cncf_project_sub input to config in benchmark-pipeline.sh

Hi! I've been very interested in WG Green Reviews' work lately and would love to get involved. I think it would be a great starting point to get some more context on what you do. :smile:

repo: cncf-tags/green-reviews-tooling


text:
Add shortcode for easier embedding of meshery designs

This pull request introduces a new shortcode that allows embedding interactive architecture diagrams created using Meshery Kanvas. These embeddings are particularly useful for showcasing cloud-native architectures, enabling users to integrate visually rich, interactive designs directly into their documentation, blog posts, and architecture pages.
Usage:
Here’s how to use the new shortcode in your Markdown files:
{{< meshery-design src="path/to/your/embed.js" id="unique-design-id" style="height: 40rem; width: 80%;" >}}

src: Path to the exported JavaScript file generated from Meshery Kanvas.
id: Unique ID for the container element.
style: Customize the container style as needed. Defaults to a responsive layout if omitted.

Benefits:

Interactive Visualization: Replace static images with dynamic, interactive designs.
Consistency in Architecture Documentation: Ensure that stakeholders view and interact with standardized designs directly within the site.

Additional Notes:

Full details on creating and exporting designs in Kanvas can be found in the official documentation

I'll leave it for others to evaluate the need for this feature, however, would just like to mention that we have already enabled Mermaid designs for this site. I'm not sure if that overlaps with Meshery Kanvas.

Thank you for the PR @aabidsofi19 .
I would propose to stay with mermaid for now as it's already integrated and mostly known by potential ref-arch contributors.
Let's not add an additional option for contributors where they could choose without having the different pros and cons described well.

authors: aabidsofi19 bavarianbidi cjyabraham

repo: cncf/architecture


text:
Sound currently not working

@DavidVentura, for some reason apps crash when trying to initialize the sound under the current setup.  I spent a bit trying to debug it, but I don't understand the code very well.  Can you pull the latest everything then uncomment the call here, and see if it crashes for you?
//InitCNFAAndroid( Callback, "A Name", SAMPLE_RATE, 0, 1, 0, SAMPLE_COUNT, 0, 0, 0 );

Also, it's currently breaking CI.  See this: https://github.com/cnlohr/rawdrawandroid/actions/runs/5626850417/job/15248435884

Interesting, with the current code base, when I re-enable audio, this loop is infinite:
while( !MyWebView.WebViewObject ) usleep(1);

though it's not easy for me to debug, as current master crashes within ~5 seconds on my phone.
Just messing with the code, moving the line
      InitCNFAAndroid( AudioCallback, "A Name", SAMPLE_RATE, 0, 1, 0, SAMPLE_COUNT, 0, 0, 0 );

after
      while( !MyWebView.WebViewObject ) usleep(1);

makes the audio work again. Though, I still crash within 5 seconds.
The failure on the build seems unrelated though, as it's still present when audio is disabled:
https://github.com/cnlohr/rawdrawandroid/actions/runs/5659840530/job/15441189400

Ah, I should not rely on webview being a thing.  What is your SDK version and what version of Android are you running on?

ndk is 21.3.6528147 and android version is 11

Do you know which SDK version you're on?

SDK version is 30

authors: DavidVentura cnlohr

repo: cnlohr/rawdrawandroid


text:
如何读入一个自定义的shp文件

cnmaps库能写一个读取shp文件的实例吗？我想用它进行掩膜shp背景栅格信息，类似于白化背景处理

@xiaosongding 因为 shp 文件内部结构相对比较灵活，目前还没有开发读取 shp 的功能，但是后面可以添加。

authors: Clarmy xiaosongding

repo: cnmetlab/cnmaps


text:
Enum SRP_NGType out of order

Values from enum SRP_NGType are used as indices into the array global_Ng_constants, but the enum and array values are not in the same order. Only group 1024 happens to be in the position declared by the enum. Asking for any other group gives you a different group's values.

Should be fixed now. This will break backwards compatibility but it's the correct approach.

authors: cocagne wyoung

repo: cocagne/csrp


text:
diagnostics reporting: add a note about version checks

In the section on disabling diagnostics reporting, we should note that nodes also check for new versions periodically and notify you in the UI / logs if a new version is available.
These checks can be disabled by setting the environmental variable COCKROACH_UPDATE_CHECK_URL="".

Thanks, @dt. Is this new in 2.0, or was it just previously undocumented?

@dt, does disabling diagnostics reporting automatically disable the new version check as well? Or are these separate?

yep, since filing this, we decided and implemented that disabling diagnostics now also disables version checks, so nothing to do here now.

will land soon for 2.0 in https://github.com/cockroachdb/cockroach/pull/23007

Hmm, we might still want to mention this somewhere, so I'll reopen.

I wouldn't worry about it -- I think with the fix (which we're cherrypicking to 1.x) as well it works basically like anyone would expect.

authors: dt jseldess

repo: cockroachdb/docs


text:
Orchestrate a Local Cluster with Kubernetes Doc Update

Exalate commented:
Re: Orchestrate a Local Cluster with Kubernetes
Issue Description
Wrong name of pod "default.node.cockroachdb-3"
Step 6.
...
3. Approve the CSR for the new pod:
kubectl certificate approve default.node.cockroachdb-3
...
Suggested Resolution
It have to be "default.node.my-release-cockroachdb-3"
Jira Issue: DOC-287

Ok. Updated. Thanks!  🎉


text:
Incorrect description of behaviour with clock skews greater than threshold

Looking at https://www.cockroachlabs.com/docs/dev/operational-faqs.html#what-happens-when-node-clocks-are-not-properly-synchronized, we have the following:

For this reason, when a node detects that its clock is out of sync with at least half of the other nodes in the cluster by 80% of the maximum offset allowed (500ms by default), it spontaneously shuts down. This avoids the risk of violating serializable consistency and causing stale reads and write skews, but it's important to prevent clocks from drifting too far in the first place by running NTP or other clock synchronization software on each node.

Even with clock skew greater than the upperbound, we never violate serializable consistency. We may however violate single-key linearizability, which is what I believe "causing stale reads and write skews" alludes to.
+cc @nvanbenschoten

I'm also not sure if we can have write skews. Thinking about it for 30s tells me no, we can't, given we don't violate serializability.

I'm also not sure if we can have write skews. Thinking about it for 30s tells me no, we can't, given we don't violate serializability.

That's exactly correct.

@irfansharif, would you mind taking a swing at a quick rewrite of the paragraph above?

@jseldess: #6329.

authors: irfansharif jseldess nvanbenschoten


text:
LearnDot Email Filtering

Setup email filter in LearnDot so that internal users are directed to a different survey form than external users. This will require LearnDot Support but should be replicable once we understand how the system does this. If possible, have in place on Feb 13.

Support has acknowledged the request, but they're waiting on internal engineering resources to comment.

This change has been implemented.


text:
sqlmigrations: add migration for 19.2-style schema change jobs

PR: https://github.com/cockroachdb/cockroach/pull/46504
From release notes:

Schema changes started in 19.2 will now be automatically migrated in the background in 20.1 after upgrade finalization so that they can run to completion. [#46504][#46504] {% comment %}doc{% endcomment %}

Docs are already accurate here.


text:
Improve the first sentence for a better search result summary

Improve the first sentence for a better search result summary
It was reported that in the search result, the summary is the first sentence of https://www.cockroachlabs.com/docs/stable/deploy-cockroachdb-with-kubernetes#helm-version, and there's a theory that it's because the actual first sentence ends in a : instead of a period. Maybe Google search skips the first sentence if it ends in something other than a period. This seems like a low-risk way to test it.
Previews
src/current/v22.2/deploy-cockroachdb-with-kubernetes.md
src/current/v23.1/deploy-cockroachdb-with-kubernetes.md
src/current/v23.2/deploy-cockroachdb-with-kubernetes.md

FYI @JosephNickdow

Let's merge and see if it helps. Can't really test this outside of production.

authors: mdlinville mikeCRL


text:
can add some examples on how GUI data could be retrived and used in javascript?

The github.io page of tweakpane explains how GUI elements are set. But there is no example code to show how the GUI data could be retrieved and used to affect other variables in a javascript when GUI elements are changed.

You can do it by handling a change event and applying its value to other variables. Explained in Events section:
https://cocopon.github.io/tweakpane/misc.html#events

authors: cocopon hopezh

repo: cocopon/tweakpane


text:
Add guide for Pack maker tools

Staged
Also fixed the name of the "Insert" and "Packs" menus in various other pages.

Sorry for the late review, but LGTM!

authors: ekoleda-codaio patrick-codaio

repo: coda/packs-sdk


text:
Server Status:  submissions limit removed

@ mention of reviewers
@Didayolo
A brief description of the purpose of the changes contained in this PR.

Server status page: submissions limit (250 or 2 days old) removed
Paginations added to handle many submissions (50/page)
Monitor queues moved to a separate page (http://localhost/monitor_queues)
Monitor queues page link added to menu

Screenshots
Server status first page

Server status middle page

Server status last page

Server status single page where no pagination is needed (submissions count < 50)

Monitors queue new page

Monitor queues in the menu

Issues this PR resolves

#1549

Checklist

[x] Code review by me
[x] Hand tested by me
[x] I'm proud of my work
[x] Code review by reviewer
[ ] Hand tested by reviewer
[x] CircleCi tests are passing
[ ] Ready to merge

@ihsaan-ullah
You removed the 250 limit? Do we have a limit or does all submissions appear (in the different pages)?
Also, I'm not sure that "Server Status" is clearer than "Recent Submissions".

Also, I'm not sure that "Server Status" is clearer than "Recent Submissions".

Updated back to "Recent Submissions"

Perfect.

authors: Didayolo ihsaan-ullah

repo: codalab/codabench


text:
Upgrade ginkgo to v2

Fixes: Issue #3258
Integration tests should run as before.
Output file seems to have changed structure, might need to specify some options in reporter config.

/retest

/retest

/retest

@jsliacan integration tests failing on the CI with following error, which means it is not able to generate the Junit files.
 ------------------------------
[ReportAfterSuite] [FAILED] [0.001 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
  Failed to generate JUnit report:
  open out/integration.xml: no such file or directory
  In [ReportAfterSuite] at: /home/packer/crc/vendor/github.com/onsi/ginkgo/v2/reporting_dsl.go:127

/retest

/retest

authors: jsliacan praveenkumar

repo: code-ready/crc


text:
cleaned up the App-Bar- and as per kirats request removed the pnpm-lock file

PR Fixes:

Cleaned-Up The App-Bar

This is What it looks like when hovering

When not hovering

Resolves #[Issue Number if there]
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I assure there is no similar/duplicate pull request regarding same issue

Already fixed in #319

Here is the ss from last pr for context

did not added discord logo closing this

did not added discord logo closing this


text:
Fixes for 4.23

Builds with 4.23

@jimsimonz thanks to committing this.
But the project has a script to generate the 'build.cs' file. You can refer here.

Thanks for your commit, @jimsimonz.
It supports the UE4.23 in f0fad2ee9c0d80ba52289921cf6eb363cbd94ae2.

Replace the Build.cs by the python script(Extras/Batch/SetupForUE4Project.py) with the configuration file(Extras/Batch/SetupForUE4Project.ini)
Fix some warning in UE4.23

authors: alexchicn jimsimonz


text:
WIP: when switching to near me mode, sort by distance.

Howdy @joshreisner - I'm taking a stab at sorting by distance when a user switches to Near Me mode. I've hit an impasse, and Google hasn't been much help. Every time I think I'm getting better at ReactJS, I step away a few weeks, and its back to square one! :)
Here's a WIP branch - what I'm expecting is that the console.log statements should have the arrays in different orders. The first should have the initial order (by time), and the second should be sorted by the distance. However, the second is still sorted by the distance. Any idea why?
You can see the diff, but here are the console logs in question:
https://github.com/code4recovery/react/blob/feature/nearme-sort-distance/src/helpers/data.js#L62
I'll keep pounding on it, but I'm wondering if you see something obvious.

This example may shed some light, but I'm not understanding why.
let x = []

x = [
    {"name": "erika", "distance": 0.123},
    {"name": "andrew", "distance": 5.1234},
    {"name": "david", "distance": 25.1234},
    {"name": "chris", "distance": 3.21},
    {"name": "bart", "distance": 4.321}
];

x.sort((a, b) => a.name > b.name);
console.log(x);

x.sort((a, b) => a.distance - b.distance);
console.log(x);

I'd expect this to show the list sorted by names first, then a second time sorted by distance. Instead, it shows it twice sorted by distance. If I exclude the second sort and console.log, it shows it sorted by name.

Hey @FlipperPA I think it has to do with objects and references. I believe that x in your example is a reference to an array, not a value like a string or number. (Also for this reason I think you could use const?)
const x = [
  { name: 'erika', distance: 0.123 },
  { name: 'andrew', distance: 5.1234 },
  { name: 'david', distance: 25.1234 },
  { name: 'chris', distance: 3.21 },
  { name: 'bart', distance: 4.321 },
];

const y = [...x];

x.sort((a, b) => a.name.localeCompare(b.name));
console.log(x);

y.sort((a, b) => a.distance - b.distance);
console.log(y);

All this said, we don't actually sort meetings by distance in the plugin. We filter by distance, so that users may find meetings within, say, 2 miles, but meetings are always sorted by time.

Looks like we already have a ticket for the distance filtering: https://github.com/code4recovery/react/issues/37

Thanks @joshreisner - my love to JavaScript is not increasing. :)
I was looking for a quick improvement while waiting for a friend to work on the distance filter, but I'm guessing time might be better spent just doing it.

authors: FlipperPA joshreisner


text:
Frame / Photo margin ?

Hi,
I've tried to make a custom frame, basic one with the front face as the full picture, but it looks like I have some margin I can't remove/change:

The scale is like that on the generated frame:

If I happens to change from 100.6667 to 66.67:

The frame is now the same size as the picture:

Is it a builtin margin ? Or maybe I haven't managed to find the setting for that.
Some of my settings:

It seems most likely that the issue here is your picture frame is the wrong size.
PhotoFrameType > PhotoDimensions tells the photo frame manager how big the photo should be to fit into the picture frame. You have it set to "Larger Side Is One". This means the larger side of the photo should be one unit length to fit the photo frame. (Note the scale of the photo frame in the scene is completely separate. It is done afterwards to both the photo and the frame and does not effect this setting.)
Most likely your picture frame model is simply the wrong size. From the scale values in the screen shots the slot for the photo looks to be 1.509925 x 1.509925 units. From the settings the photo frame manager assume slot for the photo to be 1 x 1 units. Assuming this is the problem here a few different ways to fix the issue (you only need to do one)...

Simplest: Set the FBX scale factor to 0.66228455 for unity to scale the model to the correct size while importing. (0.66228455 is simply = 1 / 1.509925)
Edit the picture frame in another program making the slot for the photo be 1 x 1 units and reexport the FBX.
Set PhotoFrameType > PhotoDimensions to "Use Aspect Ratio". This setting lets you tell the photo frame manager the exact dimensions for the photo slot. Set PhotoFrameType > photo frame model list > Aspect Ratio to (x: 1.509925, y: 1.509925).

Do let me know if this answer solves your problem. Additionally the section on Photo Frame Type Files has been expanded with more detail.

I did go the easy route by changing the FBX scale factor, I might have done a whoopsie when exporting the FBX, I will redo it later, thanks !

authors: codec-xyz rhaamo


text:
Paypal Sync Subscription Payments

Add the ability to purchase year or lifetime subscriptions through PayPal.

Coverage increased (+0.04%) to 57.43% when pulling c487db01e1f99591f5ea4ae3047148a19c1b3af9 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.04%) to 57.43% when pulling 27e8ed463c60eaf54c79fc5a50bb1913a3ec6c99 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.06%) to 57.443% when pulling 73b4426bc3fa7661c304ef864823497e43426b0f on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.04%) to 57.43% when pulling 5b176dd4e71bd9c8a2ebd4e0c5b1416cc1a39a20 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.04%) to 57.43% when pulling 5b176dd4e71bd9c8a2ebd4e0c5b1416cc1a39a20 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.06%) to 57.443% when pulling bd937d8905324b944f910ac15d8162d5664a2265 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.04%) to 57.43% when pulling bd937d8905324b944f910ac15d8162d5664a2265 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.06%) to 57.443% when pulling 86552d4d8d36bea118c6a72f2523d718afa19b8c on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

Coverage increased (+0.04%) to 57.43% when pulling f391dfb2980d090f79cd381bcbccc3f2996686b6 on paypal into ba1985d2a9687e9060a8185f13428dad42e8ab97 on master.

authors: coveralls sderickson

repo: codecombat/codecombat


text:
Homepage redesign

Update homepage, plus common base-flat footers and headers.
Still TODO: analytics events

High level thoughts:
Do we still want the home page locked to a viewport of width 1024px?

Ideally we support <meta name="viewport" content="width=device-width, initial-scale=1"> and ensure the home page works on various devices.

How accessible should the home page be?
Maybe we should support some of the minimal effort changes such as image alt text. Accessibility checklist
Should we be using semantic elements instead of divs?

There is a strange parsing issue in the #built-for-teachers carousel.

Looking great but still some changes mentioned in comments.
Other immediately required changes:
Banner button to yellow.
Footer on smaller screen.
Meta tag so that nav bar shrinks correctly to fit width of mobile. (observe horizontal scroll on chrome)

Updated the banner.
Not seeing the nav bar shrinking problem, can you provide steps or screenshot?
Not seeing problem with foot on smaller screen, screenshot?

In reference to the footer:

Shasha's note: "The columns in the footer don't need to be stacked. Can be the same as in the desktop version."

I can't repro navigation bar width so it may have been an anomaly.
I locally tested what <meta name="viewport" content="width=device-width, initial-scale=1"> does to the current design and it looks like it would be much more work to properly support mobile responsiveness. For example we'd need to use more relative measurements over pixels like em.
I ran a google lighthouse test and the checklist provided was very useful.

It can be run from the Audit tab in Chrome Developer Tools.
A large opportunity for performance is serving images in a much more performant file format. I can tackle some image conversion if that's worth it. (I think it may be). Although the CDN will end up helping with compression it's probably worth the effort for a faster load.

We can remove .style-flat from the hardcoded pages as it's being applied in the base-flat.jade file.
This caused pages to be wrapped with .style-flat twice.

authors: AndrewJakubowicz differentmatt


text:
Add CI support for targeting current and previous two major Go releases

This project should be built and tested against not only the current Go release, but the previous two Major releases.

We in fact are doing the three most current releases, and tip.
However, we have external users that are tied to Go 1.6, so that may have to stick around even when Go 1.9 comes out.

authors: akutz codenrhoden

repo: codedellemc/libstorage


text:
ScaleIO Snapshot enhancments

@akamalov commented on Tue Mar 29 2016
Hey Clint, just a question: will REX-Ray Support ScaleIO Snapshots ? For instance, if I want to present a snapshot volume to another container ?
Thanks!!
Alex

@clintonskitson commented on Tue Mar 29 2016
Alex,
It does today already. You can create snapshots of volumes, create volumes
from snapshots, or create volumes from volumes (uses snaps).
These are all available via CLI or via the volume drivers (docker/Mesos).
On Tuesday, March 29, 2016, akamalov notifications@github.com wrote:

Hey Clint, just a question: will REX-Ray Support ScaleIO Snapshots ? For
instance, if I want to present a snapshot volume to another container ?
Thanks!!
Alex
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/345

@akamalov commented on Tue Mar 29 2016
Thanks Clint. So I created a snapshot using "scli". The snapshot volume is
there, but when I issue 'rexray volume list', it does not list the snapshot
volume.
Alex
On Tue, Mar 29, 2016 at 3:11 PM, Clinton Kitson notifications@github.com
wrote:

Alex,
It does today already. You can create snapshots of volumes, create volumes
from snapshots, or create volumes from volumes (uses snaps).
These are all available via CLI or via the volume drivers (docker/Mesos).
On Tuesday, March 29, 2016, akamalov notifications@github.com wrote:

Hey Clint, just a question: will REX-Ray Support ScaleIO Snapshots ? For
instance, if I want to present a snapshot volume to another container ?
Thanks!!
Alex
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/345

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/345#issuecomment-203056865

@clintonskitson commented on Tue Mar 29 2016
Can you try creating a snapshot via RR? Curious as to whether those devices are being represented differently.
Are you using 0.3.2? Previously, the storage pool that was configured in config.yml was the only one being searched for volumes.

@orioncuba commented on Tue Mar 29 2016
Hi folks
Question from customer can we use rexray in a Openshift broker(kubernetes)+ dockers install
Ann do scaleio snaps.
Openshift v3
Oscar

@akamalov commented on Tue Mar 29 2016
Hey Clint,
I stand corrected. It does show. I for some reason assumed that it will be visible under "volume list" and I should have done "snapshot list".
Thanks again!!!
Alex

@clintonskitson commented on Tue Mar 29 2016
No problem @akamalov. Yeah, the RR volume list gets filtered based on if the ancestorid is filled or not. But to ScaleIO they are all volumes.

@akamalov commented on Fri May 20 2016
Hey Clint @clintonskitson
Just a small question: Does REX-Ray support "snap-back" or snap-restore feature ? Let's say I took a volume snapshot, later data got corrupted on a primary volume, and I can go ahead and restore data  back onto that volume? Can it be done ?
Also, if I want to create a new volume off existing snapshot would this be the right syntax:
rexray volume create --volumename="mongo005_restored" --snapshotid="XXXXXXXXXXXXX"
I tried it, however, getting an error:
[root@node264 ~]# rexray volume create --volumename="mongo005_restored" --snapshotid="552c2df100000009"
INFO[0000] [linux]
INFO[0000] [docker]
INFO[0000] [scaleio]
INFO[0000] storage driver initialized                    apiVersion= endpoint=https://192.168.158.236/api insecure=true moduleName= provider=ScaleIO useCerts=false
INFO[0000] docker volume driver initialized              availabilityZone= iops= moduleName= provider=docker size= volumeRootPath=/data volumeType=
INFO[0000] os driver initialized                         moduleName= provider=linux
INFO[0000] sdm.CreateVolume                              IOPS=0 availabilityZone= driverName=ScaleIO moduleName= runAsync=false size=0 snapshotID=552c2df100000009 volumeID= volumeName=mongo005_restored volumeType=
FATA[0000] error creating volume                         IOPS=0 availabilityZone= inner=problem getting response: Interface error moduleName= provider=ScaleIO size=0 snapshotID=552c2df100000009 volumeID= volumeName=mongo005_restored volumeType=pool1
[root@node264 ~]#

I am running RexRay version: 0.3.3

@clintonskitson commented on Fri May 20 2016
@akamalov That should technically work. We will have to review it and see what is going on for that not to occur.
But today the rollback feature to an existing volume is not supported with REX-Ray. We can also look at globally supporting a rollback feature as it is would be valuable.

@dvonthenen commented on Mon May 23 2016
@akamalov I was able to create a volume from a snap, but the only difference in the command line used for me was to also specify the size (same as the snap). You would think that the size might not be needed since the snap already has size. Give that a try and see if that works for you.
Looks like we need to enhance the create and if a snapid is provided to either copy the size from the snap or if it isnt required, then to remove the restriction.

@akamalov commented on Tue May 24 2016
@dvonthenen Thanks David. Yep, it worked when size is provided. Thanks a lot!
Alex

@dvonthenen commented on Tue May 24 2016
Good to hear. Will take a look at simplifying the usability so that size doesn't need to be specified.

From the sound of the old issue, need to take a look at how we handle creating volumes from existing snapshots. The size parameter is required, when it could actually be inferred.


text:
EFS SecurityGroup Warning

This patch fixes #511 by sending an instance's full SG list to the remote service where the EFS storage driver examines the server-side SG list with the client-side list. If any of the server-side SGs are not present in the client-side list a warning will be logged in order to assist with debugging.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #583   +/-   ##
=======================================
  Coverage   28.42%   28.42%
=======================================
  Files          34       34
  Lines        2016     2016
=======================================
  Hits          573      573
  Misses       1381     1381
  Partials       62       62

Continue to review full report at Codecov.

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

authors: akutz codecov-io


text:
Fix character encoding issues

This PR fixes character encoding issues (#26) by

always reading binary data (both from files and from stdin) and letting the XML parser deal with the decoding
always writing binary data (both to files and to stdout) since we assume an UTF8 encoding for the output and already encode it accordingly

Tests on Windows 7 with Python 3.5.0 and Python 2.7.11 as well as on Ubuntu 15.04 with Python 2.7.9 worked well for files with UTF and ISO 8859-15 encoding. I tested both file input as well as stdin/stdout input/output.

awesome! thanks for that!

repo: codedread/scour


text:
causes title/progress bar screen to hang

When enabled causes the progress bar/ title to hang on prime/imdb/live channels content until play/pause pressed. 4k firestick fully updated.

Thanks for your report, I'll investigate.

repo: codefaktor/FTVLaunchX


text:
Update scalatest to 3.2.10

Updates org.scalatest:scalatest from 3.2.5 to 3.2.10.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: test-library-update, semver-patch

Superseded by #186.

repo: codefeedr/kafkaquery


text:
VirtualTourXR (Editor): Does not seem to work well when run as subcontent

When edited as subcontent, the editor widget does not create a scene from the image that is used and crashes if one tries to add something onto the empty scene.

params are not correctly passed from column type... i think this needs further investigation

@otacke any hint how to adapt? i guess column type?

This needs further investigation, yes. I highly doubt that Column is responsible. It's likely that this is some issue in the editor widget of the EscapeRoom original or even in the VirtualTour original that EscapeRoom was derived from.

The cause is a bug in the original Virtual Tour implementation that implicitly assumes that the parent instance is the main editor form which does not provide params the way that an editor library widget does - the latter is what we deal with when the content is run as subcontent.
Fixed in https://github.com/codefluegel/h5p-editor-virtual-tour-xr/pull/1

authors: otacke patrickfrohmann


text:
Added Referral Code Social Share Component

Issue Number
fixes  related Issue  #279

Describe the changes you've made

Describe if there is any unusual behavior (Any Warning) of your code(Write NA if there isn't)

Added Referral Code Social Share Component
Additional context (OPTIONAL)

Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] The title of my pull request is a short description of the requested changes.

Provide a Deployed link of route/page that needs to review
Preview: Deployed preview link
https://user-images.githubusercontent.com/47661086/116033056-5cec1d00-a67e-11eb-8e04-5a1cadd133d8.mp4
<!-- Please add deployed link to here text >

Hey @Abhishek-kumar09, please review this PR and please let me know if this change is valid as per the use case of the application!

repo: codeforcauseorg/edu-client


text:
[webapp] Assets can not be loaded

Fixed in 11.2.0

repo: codefoundries/UniversalRelayBoilerplate


text:
Environment Variable BLOGIT_MODE not honoured by start script

Description
Even if the environment variable BLOGIT_MODE is set to 1(which stands for production), the server is started in development mode.
Steps to reproduce
Steps to reproduce the behavior:

Open a terminal
Enter the following command:
Unix:
$ export BLOGIT_MODE=1

Windows:
> set BOGIT_MODE=1
3. Run python -m scripts.start
4. It will start flask development server along with WDS
Expected behaviour
It should start production server and shouldn't run WDS.

This has been fixed in ebba9eb. Now users can set run mode through the environment variable BLOGIT_MODE.

-1 for development.
0 for testing.
1 for production.

repo: codegods/blogit


text:
Rails 5 makes belongs_to association required by default

When using resort in a rails 5 application, testing breaks due to validation requiring a 'next' parameter by default:
ActiveRecord::RecordInvalid:
        Validation failed: Next must exist

Having the same issue

authors: aszecsei bendelonlee

repo: codegram/resort


text:
$cleanValidationRules in model is not working

PHP Version
8.1
CodeIgniter4 Version
4.2.10
CodeIgniter4 Installation Method
Composer (as dependency to an existing project)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MariaDB 10.6.7
What happened?
I'm arising the issue again $cleanValidationRules.  Its still not working, even cleanRules() failed to fullfill the requirement.
Steps to Reproduce
In the model set $validationRules and then set $cleanValidationRules = true.
Expected Output
We exepct the required rules to be removed if the data is not passed.

After dig down the BaseModel.php , I came to know that some lines there which making it.
        // Set $cleanValidationRules to false temporary.
        $cleanValidationRules       = $this->cleanValidationRules;
        $this->cleanValidationRules = false;

            // Restore $cleanValidationRules
            $this->cleanValidationRules = $cleanValidationRules;

        // Restore $cleanValidationRules
        $this->cleanValidationRules = $cleanValidationRules;

The above statements are in methods insert(), insertBatch(). These statements are actually causing the issue if we remove them, it works perfectly for insert(), insertBatch(), save().
I'm not making the pull request, I want someone expert to test it further for now its working for me.
Line 706: BaseModel.php Line:706
Line 788: BaseModel.php Line:788

This is not a bug. It is intentional.

Whether validation rules should be removed that do not exist in the passed data. This is used in updates.
https://codeigniter4.github.io/CodeIgniter4/models/model.html#clean-validation-rules

Why do you need to remove rules when you insert?

Here in documentation I can see that its a bug.

https://codeigniter4.github.io/CodeIgniter4/models/model.html#clean-validation-rules
Prior to v4.2.7, $cleanValidationRules did not work due to a bugs

When I read BaseModel, in the insert() the cleanValidationRules setting up as false, before transforming data, which is causing issue of removing validation for non passed data.
Removing that lines helped to solve the issue, when we pass data to model,  so the validation will be removed for non passed data.

No. $cleanValidationRules works for updates only.
Prior to v4.2.7 it did not work at all.

We use GitHub issues to track BUGS and to track approved DEVELOPMENT work packages. We use our forum to provide SUPPORT and to discuss FEATURE REQUESTS.

authors: SyedMuradAliShah kenjis


text:
Refactor Database Collector display

Description
Fixes #5539
Supersedes and closes #5543
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

This is not in this PR, but I got JS error and when I click the Toolbar icon, it does not show up (remain closed).
Uncaught TypeError: this.toolbar is undefined
    showTab http://localhost:8080/ line 37 > injectedScript:92
    createListeners http://localhost:8080/ line 37 > injectedScript:64
    init http://localhost:8080/ line 37 > injectedScript:21
    onreadystatechange http://localhost:8080/index.php?debugbar:49
    loadDoc http://localhost:8080/index.php?debugbar:14
    EventListener.handleEvent* http://localhost:8080/index.php?debugbar:1
line 37 > injectedScript:92:14
    showTab http://localhost:8080/ line 37 > injectedScript:92
    (Async: EventListener.handleEvent)
    createListeners http://localhost:8080/ line 37 > injectedScript:64
    init http://localhost:8080/ line 37 > injectedScript:21
    onreadystatechange http://localhost:8080/index.php?debugbar:49
    (Async: EventHandlerNonNull)
    loadDoc http://localhost:8080/index.php?debugbar:14
    (Async: EventListener.handleEvent)
    <anonymous> http://localhost:8080/index.php?debugbar:1

This is not because of this PR, but I got JS error and when I click the Toolbar icon, it does not show up (remain closed).

Mine, too.

Uncaught TypeError: Cannot read properties of undefined (reading 'querySelectorAll')
at HTMLAnchorElement.showTab (:88:27)

The bug comes from #5544.

@paulbalandan I rebased this branch on my local.
Two things:

line number color is gone
the buttom line of backtrace is changed

Before:

After:

Sorry, I didn't see these comments when I force pushed my new changes.

For the change in last item, I am not sure where it changed, but seems that the calling function is duplicated as the last item (that's why I removed it now)
For the coloring, I opted to color the file:line instead to be the same with our CLI rendering

The last line was fixed, from APPPATH/Controllers/Home.php:11 to FCPATH/index.php:37.
Before this PR, it was SYSTEMPATH/Commands/Server/rewrite.php:43, but we don't need it.

For the coloring, I opted to color the file:line instead to be the same with our CLI rendering

Okay, you changed the output, and it is acceptable.

Another quirk of PHP, providing DEBUG_BACKTRACE_IGNORE_ARGS ignores args for most but not require_once() args
1) CodeIgniter\Debug\Toolbar\Collectors\DatabaseTest::testDisplay
Failed asserting that an array does not have the key 'args'.

/home/runner/work/CodeIgniter4/CodeIgniter4/tests/system/Debug/Toolbar/Collectors/DatabaseTest.php:58
phpvfscomposer:///home/runner/work/CodeIgniter4/CodeIgniter4/vendor/phpunit/phpunit/phpunit:97

How about removing the first two lines?
  1    SYSTEMPATH/Events/Events.php:149
        CodeIgniter\Debug\Toolbar\Collectors\Database::collect()
  2    SYSTEMPATH/Database/BaseConnection.php:636
        CodeIgniter\Events\Events::trigger()

Why?

These lines are DBQuery event trigger and always the same.

LGTM.

This looks good to me. Thanks everyone! Merging.

authors: kenjis lonnieezell paulbalandan


text:
NavBar

The navbar should take the entire width of the screen

.

This issue is not properly explained.

Hey @roshanchatei, thanks for logging these issues! I have a couple of links here which have some tips for creating a really good github issue - please do take a read through!

https://medium.com/nyc-planning-digital/writing-a-proper-github-issue-97427d62a20f
https://hackernoon.com/45-github-issues-dos-and-donts-dfec9ab4b612

In particular, in this case: How does one reproduce the bug you've reported? It would be great to know:

what browser you're using, and if it occurs in other browsers.
what you'd expect to happen.
what actually happens.
How I (as an issue reader) can reproduce the bug if I want to try to fix it or revew the bug myself.

authors: ikayz roshanchatei yochannah