text:
Is private registry protected with credentials supported?

I setup a private v1 docker registry with authentication enabled using nginx proxy, and tried to push a docker application in diego. But it failed to stage:

Staging...
Staging process started ...
Staging process failed: Exit trace for group:
builder exited with error: failed to fetch metadata from [docker.mi-ae.com.cn/diego] with tag [latest] and insecure registries [] due to Authentication is required.
Exit status 2
Staging Failed: Exited with status 2

Actually, I already specified the docker username and password when creating the app:

cf curl /v2/apps -X POST -d '{
"name": "dockertest",
"memory":512,
"instances":1,
"disk_quota":1024,
"space_guid":"79f86aed-b38a-4de7-98c6-c25471c2abb7",
"docker_image":"docker.xxxx.xxx.xx/diego",
"docker_credentials_json":{
"docker_user":"libnux",
"docker_password":"password",
"docker_email":"libnux@gmail.com"
},
"diego": true
}'

BTW, no problem using docker client to push/run an image against my registry. I can login successfully.

Can you please try to specify your login server? You can do this by specifying docker_login_server in your request:
cf curl /v2/apps -X POST -d '{
  "name": "dockertest",
  "memory":512,
  "instances":1,
  "disk_quota":1024,
  "space_guid":"79f86aed-b38a-4de7-98c6-c25471c2abb7",
  "docker_image":"docker.xxxx.xxx.xx/diego",
  "docker_credentials_json":{
    "docker_user":"libnux",
    "docker_password":"password",
    "docker_email":"libnux@gmail.com",
    "docker_login_server":"<your login server here>"
  },
  "diego": true
}'

I guess your login server should be the same as the one specified in the logs above (docker.mi-ae.com.cn/diego) unless you have some custom setup.

Thanks, @hsiliev. But the staging still failed.
I found that, to let docker do login, I've to set the DIEGO_DOCKER_CACHE env to true. If not, I got the "Authentication is required" error.
After I set this env varaiable to true, the staging process still failed as show below.
Could please help?
Actually I do not need to cache the image to the same docker registry, is it possible to enable docker login without setting DIEGO_DOCKER_CACHE?
Thanks.
Error message:
Pulling docker image docker.xxx.xxx.xx/diego:latest ...
Pulling repository docker.xxx.xxx.xx/diego
b5f75b6c4fa3: Pulling image (latest) from docker.xxx.xxx.xx/diego
b5f75b6c4fa3: Pulling image (latest) from docker.xxx.xxx.xx/diego, endpoint: https://docker.xxx.xxx.xx/v1/
b5f75b6c4fa3: Pulling dependent layers
cf2616975b4a: Pulling metadata
cf2616975b4a: Pulling fs layer
cf2616975b4a: Download complete
47f0a47155d5: Pulling metadata
47f0a47155d5: Pulling fs layer
47f0a47155d5: Download complete
32e97f5f5d6b: Pulling metadata
32e97f5f5d6b: Pulling fs layer
32e97f5f5d6b: Download complete
246659bee8aa: Pulling metadata
246659bee8aa: Pulling fs layer
246659bee8aa: Download complete
6eca2cb72610: Pulling metadata
6eca2cb72610: Pulling fs layer
6eca2cb72610: Download complete
b5f75b6c4fa3: Pulling metadata
b5f75b6c4fa3: Pulling fs layer
b5f75b6c4fa3: Download complete
b5f75b6c4fa3: Download complete
Status: Downloaded newer image for docker.xxx.xxx.xx/diego:latest
Docker image pulled.
Docker image will be cached as docker.xxx.xxx.xx:443/c10bc7c6-807f-45b7-6a82-8105f6b65b50
Tagging docker image docker.xxx.xxx.xx/diego:latest as docker.xxx.xxx.xx:443/c10bc7c6-807f-45b7-6a82-8105f6b65b50 ...
Docker image tagged.
Pushing docker image docker.xxx.xxx.xx:443/c10bc7c6-807f-45b7-6a82-8105f6b65b50
The push refers to a repository [docker.xxx.xxx.xx:443/c10bc7c6-807f-45b7-6a82-8105f6b65b50] (len: 1)
Sending image list
Authentication is required.
Please login prior to push:
Username: EOF
failed to cache image docker.xxx.xxx.xx/diego:latest exit status 1

Unfortunately you can only do this using the cache. There is a story to support private images without the cache: https://www.pivotaltracker.com/story/show/95230604
Do you use the same registry for caching and for storing private images?

Yes, caching and storing is on the same registry. This kind of caching setup is not supported?
As in my last post, the staging process already successfully logged in and pulled down the image from the registry. I don't understand why it failed when pushing back again.

We do not support credentials protected cache. We rely on network isolation and TLS to secure it since we regard it as internal CF component. Therefore we do not expect to need login for pushing images.
I believe that if you separate the cache and the private registry your scenario will be running fine. It is interesting if these two registries can be co-located to save space, but I haven't tried/searched if this is possible.
Sorry for the troubles, but the cache is pretty new (experimental if you wish) project and that's one of the reasons to have it in separate from Diego repo. The other reason is that we still don't have a full list with all the scenarios we want to support.

The situation and requirement is that
“I have a private docker registry protected by basic authentication, and I want to deploy images from it into diego. It should work if I specify the username,password and login_server. This is not related to docker caching."
Could this be supported?

Hi, @libnux,
We'd very much like for CF+Diego to support running private docker images without relaying them into the diego-docker-cache, but for this even to be feasible we require that Garden-Linux support running images that require credentials. We'll be exploring support for these use cases in the next few rounds of work on Diego and Garden-Linux.
Thanks,
Eric, CF Runtime Diego PM

The feature request for running private Docker images without requiring the caching workflow is captured in the Diego tracker story at https://www.pivotaltracker.com/story/show/95230604. I'm going to close this issue out as a result.

@ematpl, is this feature done in recent diego release?
I tried with diego v0.1441.0 and private v2 docker registry, and it did not work yet.

Hi, @libnux,
No, this feature is unfortunately not done yet. The Diego and Garden teams are still investigating the best way to implement this correctly in a truly multi-tenant environment such as Cloud Foundry, but we expect to have a roadmap for this feature available soon. I would suggest you watch the Diego and Garden team trackers, as well as the cf-dev mailing list, for news about this.
Thanks,
Eric

Hello, could someone please give advise what is the best way to pull docker  images from ECR
I tried to run the following command:
cf push app1 -o 123456789123.dkr.ecr.us-east-1.amazonaws.com/app1:1
but I got the following error:
no basic auth credentials
But I made ecr login and it returned - login successfull, also I tried separate EC2 instance with IAM role attached which have all ECR resources allowed for it, but with no luck.

authors: ematpl hsiliev libnux mirakl577


text:
Fix the gosigar issue that's causing log-cache to leak memory

Acceptance Criteria
Fix https://github.com/cloudfoundry/gosigar/issues/48

Proposed fix https://github.com/cloudfoundry/gosigar/pull/50

source: gharchive/issue

authors: andreas-kupries viovanov

repo: cloudfoundry-incubator/kubecf

license_type: permissive

license_source: github-api


text:
Build KubeCF using Docker for guaranteed reproducibility

The problem
The KubeCF builds are not 100% deterministic, as not all build dependencies, including the transitive ones, are not pinned to specific versions. With Bazel, this was more strict, and now a simple version change on an unpinned dependency can cause hours of delay just to get a build done properly.
The proposal
Have a Docker image with all dependencies pinned and perform the build inside a container using this image. The Dockerfile should be in the KubeCF project and be published to the GitHub Container Registry so everyone leverages the same image.

Ping @jandubois.


text:
permbench: add initial permbench command

This change adds the permbench command. This command will run a suite of
benchmarks against a targeted Perm service deployment. At the moment it
only contains a single benchmark but is written such that adding new
benchmarks is quick and familiar.
Please see the package documentation for more details about the
implementation.

@xoebus Can I close out this PR? Not sure if you still care about this.

source: gharchive/pull-request

authors: jeffpak xoebus

repo: cloudfoundry-incubator/perm


text:
Add quarks secret name in one of the log messages

#175031530

Pull Request Test Coverage Report for Build 330946586

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 77.573%

Files with Coverage Reduction
New Missed Lines
%

pkg/kube/controllers/quarkssecret/namespace_predicate.go
3
65.0%

Totals

Change from base Build 325169566:
-0.06%

Covered Lines:
1304

Relevant Lines:
1681

💛  - Coveralls

authors: coveralls rohitsakala

repo: cloudfoundry-incubator/quarks-secret


text:
Fix ongoing backup

Rel branch pull for https://github.com/cloudfoundry-incubator/service-fabrik-broker/pull/340

Pull Request Test Coverage Report for Build 1431

20 of 20 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 88.319%

Totals

Change from base Build 1417:
0.02%

Covered Lines:
7250

Relevant Lines:
7947

💛  - Coveralls

authors: coveralls muralisc


text:
Allows for clients to customize dashboard URL

Currently the dashboard URL sent back by broker as part of create/update requests are all back to its inbuilt dashboard URLs. However there are some usecases where individual services might like to redirect the dashboard requests to their own hosted solution. To address this, we provide a mechanism via Service plan for end users to specify a dashboard_url_template at plan level which will be evaluated with the following context object:

Request body as recieved in the PUT/PATCH OSBAPI request
Plan object

Services are free to use any of the values of the above context when constructing their template URL (refer sample dashboard url template in settings.yml). The template URL must result in an valid absolute URL, else before the request is even processed an error is thrown back to the end user.
Also since the config will be evaluated via lodash at the start of app when setting up config, the url template provided in the config must be base64 encoded in order to avoid false evaluation of the same upfront.

Pull Request Test Coverage Report for Build 2749

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 90.039%

Files with Coverage Reduction
New Missed Lines
%

data-access-layer/cf/TokenIssuer.js
1
98.57%

Totals

Change from base Build 2743:
0.02%

Covered Lines:
8781

Relevant Lines:
9430

💛  - Coveralls

authors: coveralls jagadish-kb


text:
Firehose can break if filters are unset quickly on first load

Split out from #1964

refresh, quickly click none
shows 'connecting' message forever

@richard-cox Can not reproduce - possibly the fix for log stream connecting issue fixes this.

Fixed by log stream connecting PR. #2235

authors: nwmac richard-cox

repo: cloudfoundry-incubator/stratos


text:
Add new inspect-local-release command

Hi,
This PR adds a new inspect-local-release command, similar to the existing inspect-local-stemcell command.
Please let me know if you have any questions.
Regards,
Dave

One thing I did notice tis that the release.MF metadata file inside a release tarball does not include the job-packageName dependencies, so this information is missing from the output, compared to the same output generated by create-release. Interestingly, the inter-package dependency information is included in the metadata file, so it is displayed by this new command. I haven't looked into what it would take to add the job-packageName information to the metadata file, but I assume it wouldn't be too hard.

Heya @davewalter, thanks for the PR! I'm curious what the use case for this command vs the inspect-release command is?

Hi @mfine30,
Thanks for taking a look at this. I was working with local release tarballs to research an issue with the files our CI was storing in S3, and wanted an easy way to check the version embedded in the metadata file vs the one included in the filename. Uploading the release to a bosh director seemed like overkill, and when I saw that there was an existing inspect-local-stemcell command, it seemed logical to add one for releases.
I started out writing my own output, but then I came across the ReleaseTables helper and figured it would be nice to get as much output as possible "for free".
Dave

@davewalter we went ahead and also implemented the create-release change to add packages to jobs so that this command looks more inline with how create-release and inspect-release present the information.
Thanks for the PR!

authors: davewalter luan mfine30

repo: cloudfoundry/bosh-cli


text:
Redacting properties in diffs only works for either job.properties or global properties

Using bosh_cli and director in version v250
Steps to reproduce

Deploy dummy-boshrelease with the following manifest

---
name: dummy
director_uuid: <your UUID>
releases:
  - name: dummy
    version: latest

networks:
  - name: default
    type: manual
    subnets:
      - <your subnet here>

jobs:
  - name: dummy_with_properties_z1
    template: dummy_with_properties
    instances: 1
    resource_pool: small_pool
    networks:
      - name: default
    properties:
      network_name: default
      echo_value: "is someone here?"

compilation:
  workers: 1
  network: default
  reuse_compilation_vms: true
  cloud_properties:
    instance_type: small_2_2
    availability_zone: <your AZ>

update:
  canaries: 1
  max_in_flight: 3
  canary_watch_time: 3000-600000
  update_watch_time: 5000-600000

resource_pools:
  - name: small_pool
    network: default
    stemcell:
      name: bosh-openstack-kvm-ubuntu-trusty-go_agent
      version: "3140"
    cloud_properties:
      availability_zone: <your AZ>
      instance_type: small_2_2
properties:
  what:
    is:
      going:
        on: here

On the first deploy, all properties are redacted
Change the global properties.what.is.going.on to something different
start bosh deploy and see that the global property is redacted, but don't deploy yet! Cancel instead.
Additionally change the local jobs.dummy_with_properties_z1.properties.echo_value
start bosh deploy and see that the global property is no longer redacted, only the local one.

Screenshots

Redacting the global diff only works

Redacting local and global doesn't work

Additional Easteregg

the property string on seems to be translated to true in the diff, even if it is a key, not a value.

Associated story: https://www.pivotaltracker.com/story/show/112825405

@voelzmo we're getting this fixed for the local vs global level of properties to be redacted, but we're unsure whether the easter egg part means another issue. To clarify, is the key change from "on" to "true" unexpected?
Thanks,
Wagner & @yuzhangcmu

@wcamarao yup, the rename seems weird an unexpected to me. Not sure why this happens, though. Fun fact: once you deployed successfully with the key being changed from on to true, it is impossible to update this deployment. The director tries to calculate a diff on the boolean true, which leads to a stacktrace.
So yes, I'd say the rename should not happen. Maybe this is too much of an edge-case to invest much effort in it, so depending on how hard it is to fix, I would decide. :)

@voelzmo thanks for confirming. After looking into the yaml spec, I don't think we should do something about this. Here's why:
1- Both keys and values in yaml are nodes, meaning keys are not strings (node spec). So, keys could be a boolean for example, in any of its representations. Keys are still expected to be unique but interestingly, keys such as yes and on would result in duplicate keys - read on. :)
2- Yaml booleans could also be represented as a few different English words (bool type), e.g. on/off, yes/no.
This part of the issue seems more related to yaml itself, so I'd suggest that when needed, we wrap such keywords in quotes so they're not evaluated as boolean and instead treated as string. Aye?

We investigated further the deployment always failing after changing key from on to true and we weren't able to reproduce it. Any more details you can provide to help reproduce it + a stacktrace?

@wcamarao making sure that the keys are strings seems to make sense to me.
Some steps to reproduce what I described above:

deploy the above manifest with global properties looking like this:

properties:
  what:
    is:
      going:
        on: here

Note: I saw the deploy fail with recent stemcells with this error
Error 100: undefined method `to_sym' for true:TrueClass

However, I was experimenting with older stemcells at that point, and e.g. with v3140 I could actually deploy it. Maybe due to another ruby version?

can you get stacktrace from the director? we cant repro it for some reason.
Sent from my iPhone

On Feb 7, 2016, at 4:35 AM, Marco Voelz notifications@github.com wrote:
@wcamarao making sure that the keys are strings seems to make sense to me.
Some steps to reproduce what I described above:
deploy the above manifest with global properties looking like this:
properties:
what:
is:
going:
on: here
Note: I saw the deploy fail with recent stemcells with this error
Error 100: undefined method `to_sym' for true:TrueClass
However, I was experimenting with older stemcells at that point, and e.g. with v3140 I could actually deploy it. Maybe due to another ruby version?
—
Reply to this email directly or view it on GitHub.

@voelzmo, is this still an issue?

@dpb587-pivotal seems like this works out now. Thanks for the reminder.

authors: cppforlife dpb587-pivotal voelzmo wcamarao

repo: cloudfoundry/bosh


text:
Allow traffic to istio-sidecar-injector on port 9443.

Problem
NetworkPolicy blocks traffic from API server to istio-sidecar-injector.
Solution

Allow everyone to access istio-sidecar-injector on its https port.
Remove other ports from NetworkPolicy.
Remove NamespaceSelector since API server has no namespace.

Fixes https://github.com/cloudfoundry/cf-for-k8s/issues/69

Thanks @jkbschmid!
I commented on this in the original issue (https://github.com/cloudfoundry/cf-for-k8s/issues/69#issuecomment-601265320), but want to mention it here as well that this is a big indicator that the GKE clusters we're testing with in CI are not providing enough coverage.
Created a placeholder story for us to address this: https://www.pivotaltracker.com/story/show/171883349

authors: jkbschmid tcdowney


text:
[Discussion] Future of Important Repos in the cloudfoundry-community Organisation

What
The most important repositiories that are consumed and maintained in the cloudfoundry-community org must be protected.
Why:
With the recent unavailability of the cloudfoundry-community due to its deletion/attack many of the repositories such as go-cfclient & cf-terraform-provider that were important to developers/users were unavailable.
From discussions, it is understood that this org is not in the purview/control of the CloudFoundry Foundation. (Admins are people from Stark & Wayne?)
How
Therefore, I request the KeyMembers/Drivers/Administrators of the CloudFoundry Foundation to either take control of the org OR fork the most important and popular repositories (or all) to the foundation so that it will be protected, standardized and well maintained.

Right after the incident, we've stripped down to few people that are trustworthy.
The current reduced set of admins are from the CF Foundation, the Gstack (myself) and the FiveTwenty consultancies, which are companies actively involved in maintaining the community's projects.
We are working on re-organizing the way we give access in the future, so that we eliminate risks of similar incidents.
Long story short, this is being worked on. A blog post will also do a full recap of facts and outcomes.

There is a summary of the incident and taken actions to restore trust in the cloudfoundry-community org here. Additionally, we discussed this topic during the TOC meeting on 13th of February (recording).

Therefore, I request the KeyMembers/Drivers/Administrators of the CloudFoundry Foundation to either take control of the org OR fork the most important and popular repositories (or all) to the foundation so that it will be protected, standardized and well maintained.

The driving party here should be the maintainers of those repositories. They should initiate discussions with the CFF and the TOC. From the TOC side we can help to execute the move when we have an agreement.

The driving party here should be the maintainers of those repositories. They should initiate discussions with the CFF and the TOC. From the TOC side we can help to execute the move when we have an agreement.

Makes sense. I believe we should try to get in touch with the maintainers (at least for the active projects that are maintained and heavily used) and work with them to move their repos to the CF Foundation.
For eg: https://github.com/cloudfoundry-community/go-cfclient/issues/379

We discussed this during the TOC meeting today. Our advice for the maintainers willing to move their repositories into the cloudfoundry org is to start the discussion by opening an issue in this repository.

authors: beyhan bgandon vipinvkmenon

repo: cloudfoundry/community


text:
Add "shared_domain" variable

For Cloud Foundry providers it would be nice, if we could use a specific shared domain that we offer, in the docs. For example the page https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html#domains-dns would be easier to comprehend for new users if it included a specific example (e.g. "cfapps.io" for PWS or "scapp.io" for Swisscom) instead of using the generic ".shared-domain.com". I would therefore vote to create a new variable shared_domain in config.yml and use it everywhere instead of examples like "shared-domain.com". The Cloud Foundry docs could still set that variable to "shared-domain.com" to stay generic.
If you guys agree, I can make a PR.

I just noticed that we already have this variable as app_domain. That resolves this issue.

Thanks @mastertinner !

authors: kimahoff mastertinner

repo: cloudfoundry/docs-book-cloudfoundry

license_source: bigquery


text:
[Chore]: Add additional app lifecycle tests to the e2e tests

Background
Several app lifecycle operations are not exercised by any of our tests. Bug here can only be caught through manual acceptance, so nothing blocks regressions.
Action to take
Add tests for the following scenarios to the e2e tests:

Push different code to an existing app and verify that the new code is running (including by curling the app)
Scale up a non-web process on an multi-process app

In addition, there are gaps in our existing app e2e tests. For example, we don't verify that the app is receiving web requests and returning the expected response. This can lead to false positives, such as the API responding "correctly" but the app workload being stopped or unreachable. Add these checks to the existing tests.
Impact
These new tests and new assertions will avoid a class of regressions around the app lifecycle.
Dev Notes
No response

Note: The newly added apps e2e test that queries the /env.json endpoint already verifies the app is receiving web requests and returning the expected response. In addition, the re-push app e2e test in the PR will also verify the app web request response before and after re-push.

authors: clintyoshimura matt-royal

repo: cloudfoundry/korifi


text:
Update controller-gen to v0.9.2 and regen CRDs

Is there a related GitHub Issue?
There is a correlated PR for eirini-controller.
What is this change about?
Regenerates CRDs with updated controller-gen tooling
Does this PR introduce a breaking change?
No.
Acceptance Steps
Run tests as normal.
Tag your pair, your PM, and/or team
@tcdowney

The eirini-controller PR has been released as v0.9.0

authors: Birdrock danail-branekov


text:
cf login failed due to 'Error performing request: Get https://login.system.domain/login: stopped after 1 redirect'

Hi, I used cf-deployment to deploy the Cloud Foundry with  a haproxy set by the operation file(cf-deployment/operations/community/use-haproxy.yml).
I could succeed to  cf api, but failed to login.
root@bosh-build-server-matt:/data/xzd/deployment/cf# CF_TRACE=true cf login -u admin -p admin_pasword
API endpoint: https://api.system.domain
REQUEST: [2017-09-28T05:48:44Z]
GET /v2/info HTTP/1.1
Host: api.system.domain
Accept: application/json
Connection: close
Content-Type: application/json
User-Agent: go-cli 6.29.0+ff886fa.2017-07-24 / linux

RESPONSE: [2017-09-28T05:48:45Z]
HTTP/1.1 200 OK
Connection: close
Content-Length: 611
Content-Type: application/json;charset=utf-8
Date: Thu, 28 Sep 2017 05:48:45 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 83685d19-3f75-4b4f-6665-b163f7ef0f40
X-Vcap-Request-Id: 7ca25f80-6a2b-4d0d-4c45-8c3b7fa98475::0aae3151-882c-4a44-aaf8-18966adcd7e1
{"name":"","build":"","support":"","version":0,"description":"","authorization_endpoint":"https://login.system.domain","token_endpoint":"[PRIVATE DATA HIDDEN]","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.95.0","app_ssh_endpoint":"ssh.system.domain:2222","app_ssh_host_key_fingerprint":"ba:82:a0:ef:e6:0b:ce:08:84:cd:69:a8:02:74:ab:6a","app_ssh_oauth_client":"ssh-proxy","doppler_logging_endpoint":"wss://doppler.system.domain:443","routing_endpoint":"https://api.system.domain/routing"}

REQUEST: [2017-09-28T05:48:45Z]
GET /login HTTP/1.1
Host: login.system.domain
Accept: application/json
Connection: close
Content-Type: application/json
User-Agent: go-cli 6.29.0+ff886fa.2017-07-24 / linux

REQUEST: [2017-09-28T05:48:45Z]
GET /login HTTP/0.0
Host: login.system.domain
Accept: application/json
Connection: close
Content-Type: application/json
Referer: https://login.system.domain/login
User-Agent: go-cli 6.29.0+ff886fa.2017-07-24 / linux

API endpoint:   https://api.system.domain (API version: 2.95.0)
Not logged in. Use 'cf login' to log in.
FAILED
Error performing request: Get https://login.system.domain/login: stopped after 1 redirect

And router(169.50.199.164)'s log is below:
login.system.domain - [2017-09-28T05:15:59.509+0000] "GET /login HTTP/1.1" 301 0 0 "-" "go-cli 6.29.0+ff886fa.2017-07-24 / linux" "169.50.199.247:59072" "169.50.199.176:8080" x_forwarded_for:"159.8.138.204" x_forwarded_proto:"https" vcap_request_id:"0a7d7d30-a660-4969-650f-2e892bb55283" response_time:0.007780665 app_id:"-" app_index:"-" x_b3_traceid:"e3c1555f6d26d097" x_b3_spanid:"e3c1555f6d26d097" x_b3_parentspanid:"-"
login.system.domain - [2017-09-28T05:15:59.526+0000] "GET /login HTTP/1.1" 301 0 0 "https://login.system.domain/login"; "go-cli 6.29.0+ff886fa.2017-07-24 / linux" "169.50.199.247:59076" "169.50.199.176:8080" x_forwarded_for:"159.8.138.204" x_forwarded_proto:"https" vcap_request_id:"d8134595-4d92-417e-7957-c7f8e9099d66" response_time:0.008392151 app_id:"-" app_index:"-" x_b3_traceid:"cba0f0a145e237b6" x_b3_spanid:"cba0f0a145e237b6" x_b3_parentspanid:"-"

We could see x_forwarded_proto, x_forwarded_for is set. And 169.50.199.247 is haproxy's ip, 159.8.138.204 is my ip.
But in uaa log we cloud find 301 Moved Permanently error.
127.0.0.1 - - [28/Sep/2017:05:15:53 +0000] "GET /healthz HTTP/1.1" 200 3
169.50.199.164 - - [28/Sep/2017:05:15:59 +0000] "GET /login HTTP/1.1" 301 -
169.50.199.164 - - [28/Sep/2017:05:15:59 +0000] "GET /login HTTP/1.1" 301 -
127.0.0.1 - - [28/Sep/2017:05:16:01 +0000] "GET /healthz HTTP/1.1" 200 3

Finally, I set require_https to false. It could work.
So my question is if it has other settings in the manifest to make https require work.
Thank you.

For future visitors to this thread, you can resolve this error by configuring X-Forwarded-For and X-Forwarded-Proto. Here is a working NGINX example:
location / {
                proxy_pass http://gorouters;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Server $host;
                proxy_set_header X-Forwarded-Proto https;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Real-IP $remote_addr;
        }

authors: EdwardStudy mxplusb

repo: cloudfoundry/uaa-release


text:
Add consumer leader label to consumer_group_info metric

It would be useful to have the consumer group leader in the metrics

Hi @weeco - right, franz-go maintainer gave me a solution with the current version of the library - let me try find some time and try a PR

repo: cloudhut/kminion

license: MIT


text:
maxFileSize for videos - unable to upload higher than 40MB

Hi there,
When I configure the cloudinary-direct-file to have a high limit (e.g. 500MB), the POST request fails as such:
net::ERR_CONNECTION_RESET

POST https://api.cloudinary.com/v1_1/ralliohq/auto/upload
Referrer Policy:no-referrer-when-downgrade
Provisional headers are shown
Accept:application/json, text/javascript, */*; q=0.01
Content-Type:multipart/form-data; boundary=----WebKitFormBoundarypYQSgXlF0CYBRBkB
Origin:http://localhost:5000
Referer:http://localhost:5000/dashboard/franchisor/5/database/videos/new
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
X-Requested-With:XMLHttpRequest
X-Unique-Upload-Id:~~~

The request payload contains a public id, timestamp, signature, api_key, file - but no reference to maxFileSize. As a result, I am unable to upload any video file greater than 40MB. We're paying for the premium cloudinary service, and should be qualified for up to 1GB AFAIK. Am I missing something?
Thank you!
https://github.com/mileszim/ember-cli-cloudinary/blob/master/addon/components/cloudinary-direct-file.js#L49

Adding some more information, after some consultation with our dev team:

The maxFileSize parameter is a client-side validation parameter (e.g., to display an error message before uploading the file), therefore it won't be included as part of the HTTP request itself.
As mentioned previously, resources larger than 100MB should be uploaded chunked, however, It seems that the ember-cli-cloudinary library currently doesn't have the maxChunkSize parameter implemented, which is necessary for such requests.

A possible workaround would be to alter the ember-cli-cloudinary library's code to something like the following to make it work:
didSetData: Ember.observer('data-form-data', function() {
    Ember.run.next(this, function() {
      this.$().cloudinary_fileupload({
        disableImageResize: this.get('disableImageResize'),
        imageMaxWidth:      this.get('imageMaxWidth'),
        imageMaxHeight:     this.get('imageMaxHeight'),
        acceptFileTypes:    this.get('acceptFileTypes'),
        maxFileSize:        this.get('maxFileSize'),
        maxChunkSize:       this.get('maxChunkSize') // <-- add this line
      });
    });
  }),

👍

authors: marclundgren taragano


text:
Element not catching 'cloudinarydone' trigger

I have a file upload that sends the file just fine, but it isn't registering the trigger afterward:
form
  .append($.cloudinary.unsigned_upload_tag 'cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    }).bind('cloudinarydone', () -> console.log 'finished')

I have also tried variations of
form
  .append($.cloudinary.unsigned_upload_tag 'cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    }).on('cloudinarydone', () -> console.log 'finished')

The image uploads just fine, and I see the data response in the console, but I'm not able to register the trigger (i.e. finished is never logged).
Has this been changed recently, or is there some other obvious problem?

Your syntax is not well formed. Try the following:
$('body').append($.cloudinary.unsigned_upload_tag('cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    })).bind('cloudinarydone', function() {console.log("finished")});

Thanks for your answer.  Sorry for not mentioning, but it is coffeescript and is equivalent to what you have written:
form.append($.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
})).bind('cloudinarydone', function() {
    return console.log('finished');
});

See here for reference
Any other ideas as to what could be the issue?

append will return the form and not the upload tag, so the binding is done on the wrong element.
Try:
$.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
}).appendTo(form).bind('cloudinarydone', function() {
    return console.log('finished');
});

Great, this solved it for me -- thanks!
Solution below (with function inputs) for future reference by others:
$.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
}).appendTo(form).bind('cloudinarydone', function(e, data) {
    return console.log('finished', e, data);
});

authors: TalLevAmi nadavofi twler


text:
[Feature]: Support trusted ca certificates

Is there an existing issue already for this feature request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?
It is only supported to use self-signed server and, or client certificates.
https://cloudnative-pg.io/documentation/1.22/certificates/
Describe the solution you'd like
I would like to use trusted ca certificates.
E.g.  Certificates issued by letcsencrypt (cert-manager)
Describe alternatives you've considered
Terminate TLS connection on ingress controller.
Additional context
Application requires trusted ca certificates to connect to database. Self-signed certificates are not supported.
Backport?
N/A
Are you willing to actively contribute to this feature?
No
Code of Conduct

[X] I agree to follow this project's Code of Conduct

related https://github.com/cloudnative-pg/cloudnative-pg/issues/3503

Indeed, #3503 is still relevant.

Would also be curious about the potential support for this? I see that there was a PR #4940 but it was closed?

authors: elliotcourant phisco weiss-m

repo: cloudnative-pg/cloudnative-pg


text:
feat: make CNPG API exportable

Ref #3762

Abandoned. We used a different method.


text:
Google Analyticsを入れたい

KarteはKarteでとても便利なんだけど、それとは別にGoogle Analyticsも入っていた方が流入経路などの分析がしやすいように感じた。
なので、Google Analyticsのタグもぶっ込んでおきたい

DK側は終わり。UI側は別にIssue建てる

repo: cloudnativedaysjp/dreamkast


text:
右下のアイコンをクリックすると古い情報が表示される

右下が CloudNative Days Tokyo 2020へようこそ というメッセージになってる (アイコンも古い？)

https://event.cloudnativedays.jp/cndo2021
https://staging.dev.cloudnativedays.jp/cndo2021

意図通りの挙動であれば閉じてください:pray:


text:
Record archive video

このPRは配信・録画アーキテクチャ変更の一環で、録画アーキテクチャ部分を変更します。
全体の変更プランは https://github.com/cloudnativedaysjp/dreamkast/issues/989 のDescriptionを参照
harvest_jobsテーブルを追加

MediaLive HarvestJobを管理するためのテーブル

admin/tracksに 録画する ボタンを追加

クリックするとそのHarvestJobの作成画面に遷移する
HarvestJobの作成画面には録画開始時刻と終了時刻の入力フォームがある
開始時刻と終了時刻のデフォルト値はそのセッションの開始時刻と終了時刻
当日の進行状況によっては開始時刻・終了時刻が変わる可能性があるので変更可能になっている
MediaPackageのタイムシフト再生と開始時刻・終了時刻を使ってプレビューできるようになっている
HarvestJobを作成するとAWS側でアーカイブ動画の作成が行われる
RakeタスクでHarvestJobの状態をポーリングし、アーカイブ動画の作成が完了したらHarvestJobレコードとセッションの動画URLを更新する

RakeタスクはCronJobで定期実行することを想定

Review app
https://dreamkast-dk-1100.dev.cloudnativedays.jp

Review app
https://dreamkast-dk-1100.dev.cloudnativedays.jp

authors: showks-containerdaysjp takaishi


text:
Enable toggle for cloudtrail lambda

what

Allow user to disable cloudtrail lambda bucket log forwarding when needed

why

the options was not given before.

/test all

/test all

/test all

/test all

/test all

/test all


text:
principals_push_access does not generate corresponding ECR permission statement, but principals_readonly_access does

Describe the Bug
principals_readonly_access results in an ECR policy statement granting read actions.
But principals_push_access does not seem to generate a corresponding push only statement in ECR policy.
Expected Behavior
Expected the ECR policy to have 2 statements, one for read and one for write
Steps to Reproduce
Via Terragrunt:
terraform {
  source = "${local.base_source_url}//?version=0.32.3"
}

locals {
  base_source_url  = "tfr://registry.terraform.io/cloudposse/ecr/aws"
}

inputs = {

  image_tag_mutability = "IMMUTABLE"

  principals_push_access = [
    local.write_user_arn
  ]

  principals_readonly_access = [
    local.read_user_arn
  ]

}

Screenshots
No response
Environment
$ tf version
Terraform v1.3.3
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v4.67.0

Additional Context
No response

Updating to the latest release solved this.
It would be handy in the doc to see which version added an input option.

repo: cloudposse/terraform-aws-ecr


text:
Add support for spot instances

what

Allow usage of spot instances in beanstalk environments

why

We want to use spot instances in some of our beanstalk environments and this was missing in the module

references

closes #100

/rebuild-readme

/codefresh run test

/terraform-fmt

/codefresh run test

/codefresh run test

@tbilou here is new release: https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/releases/tag/0.20.0

authors: maximmi tbilou


text:
git.io->cloudposse.tools update

what and why
Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
References

DEV-143

/test all

repo: cloudposse/terraform-aws-inspector


text:
refactor: Remove column widths sync from table sticky header

Description
Table's header and sticky header render the same Thead component responsible for assigning column widths. When resizable columns feature is used there is no need to additionally sync the widths because there is no difference between them.
Related links, issue #, if available: n/a
How has this been tested?

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I would not call it unnecessary, check this page: https://d21d5uik3ws71m.cloudfront.net/components/86c5f63d33dc2c2022cbd17d0f064f08c7f43126/index.html#/light/table/sticky-header

After the change, the header and column sizes do not match.

I would not call it unnecessary, check this page: https://d21d5uik3ws71m.cloudfront.net/components/86c5f63d33dc2c2022cbd17d0f064f08c7f43126/index.html#/light/table/sticky-header

After the change, the header and column sizes do not match.

Great observation! :) I didn't realise the sync is necessary when the resizable columns are not used. I will submit another revision to make the change properly scoped and add an extra unit test.

There are still broken cases (which work in mainline)
Screen.Recording.2023-10-13.at.14.55.32.mov
Why do you dislike this code so much? ;) why is it important for you to remove it?

Thanks, I will take a look. The reason I dislike that code is because it includes the "auto" width condition. I would like that one to be figured out by the resizable columns helper exclusively.

Closing due to high complexity.

authors: just-boris pan-kot

repo: cloudscape-design/components


text:
wildcard support for driftignore for inclusion

Description
If the driftignore start with a wildcard, then we can add lines with ! prefix to include only some resources or type of resources.
Example
I want to scan only IAM access keys :
*
!aws_iam_access_key

LGTM!
❯  cat .driftignore2
*
!aws_iam_access_key

❯  driftctl-pre scan --driftignore .driftignore2

Found missing resources:
  aws_iam_access_key:
    - AKIA6PC2YPI65LNDOUOK
        User: circleci_acc_tests_admin
    - AKIA6PC2YPI6W2ZTAH6X
        User: driftctl_qa
Found resources not covered by IaC:
  aws_iam_access_key:
    - AKIAYJFEF7AARU4F6B77
        User: tf-admin

repo: cloudskiff/driftctl


text:
RDS validation check for "AvailabilityZone and MultiAZ" breaks conditional parameters

This validation check in rds.py:195 causes my valid templates to fail:
    if 'AvailabilityZone' in self.properties and \
            self.properties.get('MultiAZ', None):
        raise ValueError("AvailabiltyZone cannot be set on DBInstance if "
                         "MultiAZ is set to true.")

My code, which worked before this validation check was added, sets MultiAz to a Ref of a required boolean parameter and AvailabilityZone to a conditional that may evaluate to AWS::NoValue (meaning CloudFormation disregards the parameter):
database = template.add_resource(
    troposphere.rds.DBInstance(
        ...
        AvailabilityZone=If(
            'DbAvailabilityZoneSpecified',
            Ref(db_availability_zone),
            Ref(AWS_NO_VALUE)),
        ...
        MultiAZ=Ref(db_multi_az),
    )
)

This is the only pattern I know of for handling optional parameters in nested stacks when the resource requires that a parameter be unset to trigger the default.
I think the fix is to simply remove the exclusivity check in validate(), or possibly fail only if the value is not one of the conditional functions.

@sterwill looks like we both provided fixes for this issue. :-) I'll let @phobologic take a look and review.

Your is the better fix (and I made a mess of my branch history in my fork) so feel free to ignore mine.
Thanks for the lightning fast fix.

types.NoneType was removed from Python 3, so the check may have to add some additional "is None" checks.

Merged. Thanks for the bug report.

authors: markpeek sterwill

repo: cloudtools/troposphere


text:
IntelliJ does not create the files in src_managed

Several of our projects have automatically generated source code.  One kind is from the sbt-buildinfo plugin, which allows us to record build information in source code and have it compiled into the jar.  Another kind is one specific to Eidos, the Versioner, which is used to add version information to the ontologies that are automatically retrieved from github.  This is because Ben needs to know that everyone used the same ontology, or at least know what different one was used.
For most of the projects, that's the end of it.  IntelliJ is not interested in these files and sbt will build as expected.  Eidos, however, makes more active use of these files and IntelliJ needs to know about them.  Unfortunately, with the version of sbt we're using, the scala plugin version, the build.sbt file, and anything else influencing the situation, the source files that sbt would normally produce in target/scala-2.12/src_managed are not generated if only IntelliJ is used.  Build problems will ensue.
Right now it appears that the way around it is to make sure that sbt builds the project once and produces the files.  After that, IntelliJ seems to be able to use them.  It may be that this was the behavior the entire time and that anyone using IntelliJ happened to run sbt as well.  Just recently that has not been the case.

@JerryZeyu, thanks for discovering this problem.  @vanh17, you might run into this if you move to Windows and use IntelliJ without sbt.

repo: clulab/eidos


text:
add ClusterSyncResources

How to use:
you can create the crd by yaml
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: ClusterSyncResources
metadata:
  name: cluster-sync-resources-example
spec:
  syncResources:
    - group: ""
      resources:
        - pods
      versions:
        - v1

and edit pediacluster.spec.ClusterSyncResources: cluster-sync-resources-example, then you will see it works!
resolve: https://github.com/clusterpedia-io/clusterpedia/issues/150

Shall we start directly from the v1alpha2 version?

Shall we start directly from the v1alpha2 version?

When the stable version is not considered, new resources can be added directly to the latest version(alpha/beta)

For template deletion we may need to be a bit stricter.
If there are still clusters referencing the template, the template cannot be deleted ？

The relationship between template and pediaCluster should be undone.  the template is only work in creating pediacluster.
I think so, Otherwise it becomes very complicated.

The relationship between template and pediaCluster should be undone. the template is only work in creating pediacluster.

sync resource templates do not only have an effect on creation, future updates to the resource templates will also result in changes to the pediacluster synchronized resources, what do you think?

/retest

Might need to rebase main after https://github.com/clusterpedia-io/clusterpedia/pull/221 is merged.

@RuliXu The first commit doesn't seem to make sense and can be rebased into a single commit

authors: Iceber RuliXu calvin0327 cleverhu

repo: clusterpedia-io/clusterpedia


text:
TS2339 [ERROR]: Property 'toPrimitive' does not exist on type 'never'

... could not find a fix on my own so far.

executed
deno run -c ./tsconfig.json main.ts

like described in the readme imo.

HI there!
Looks like this error relates to https://github.com/cmd-johnson/deno-reflect-metadata/issues/4. I already fixed the issue in deno-reflect-metadata, but didn't update the dependency here in https://github.com/cmd-johnson/deno-dependency-injector.
Should be fixed now in v0.1.2 (https://deno.land/x/inject@v0.1.2)!

authors: cmd-johnson michael-spengler

repo: cmd-johnson/deno-dependency-injector


text:
Improve configuration UX

The current prompt-based configuration UX is bad. I think a webview approach may be better. More info here.

This will also unblock #7

repo: cmoog/vscode-sql-notebook


text:
Banning shared_ptr and std::cerr

Remove usages of shared_ptr and std::cerr from the codebase.
TODO

[x] Whitelist test and third_party, depends if shared_ptr is meant to be a (A) one-time exemption or (B) other all bad words should be exempted or (C) some other bad words should be exempted
[ ] Fix the actual 600-700 existing instances of shared_ptr to presumably use ManagedPtr

John/catalog, Matt/network, Gus/expressions, Pavlo&Ling/logicalops
Remaining, working on it: logger, parser, plannodes, settingsmanager, trafficcop

Sure, I have no strong opinions.

Blocked on logger, please see slack.

We can’t merge this until all of the refactors are done.

authors: lmwnshn mbutrovich

repo: cmu-db/terrier


text:
Gate pulling/syncing data from AWS in safegraph behind a flag in params

Summary:

Adds a flag around pulling/syncing data from AWS in safegraph.run_module().
Adds testing for safegraph.run_module() that skips over any interaction with AWS.
Update safegraph_patterns to use similar variable naming and other paradigms.

Oh didn't even see I had a review requested on this one, sorry. I should add an inbox filter for github emails....

authors: chinandrew sgsmob

repo: cmu-delphi/covidcast-indicators


text:
batch-represent : Could not find any image file in the given input paths

I am following this guide to setup docker container and explore openface. I pulled the docker image bamos/openface and copied training images to a directory called training-images (located inside /root/openface/). I then copied 10 images of the person I want to recognize into this directory and ran the following commands :
1)Pose detection and alignment:
./util/align-dlib.py ./training-images/ align outerEyesAndNose ./aligned/ --size 96

2)generate the representations from the aligned images:
./batch-represent/main.lua -outDir ./generated-embeddings/ -data ./aligned/

However when executing step 2, if get the following ouput :
root@e917ad344dc4:~/openface# ./batch-represent/main.lua -outDir generated-embeddings/ -data aligned
{
  data : "aligned"
  imgDim : 96
  model : "/root/openface/models/openface/nn4.small2.v1.t7"
  device : 1
  outDir : "generated-embeddings/"
  cache : false
  cuda : false
  batchSize : 50
}
aligned
cache lotation: 	/root/openface/aligned/cache.t7
Creating metadata for cache.
{
  sampleSize :
    {
      1 : 3
      2 : 96
      3 : 96
    }
  split : 0
  verbose : true
  paths :
    {
      1 : "aligned"
    }
  samplingMode : "balanced"
  loadSize :
    {
      1 : 3
      2 : 96
      3 : 96
    }
}
running "find" on each class directory, and concatenate all those filenames into a single file containing all image paths for a given class
now combine all the files to a single large file
load the large concatenated list of sample paths to self.imagePath
/root/torch/install/bin/luajit: /root/openface/batch-represent/dataset.lua:193: Could not find any image file in the given input paths
stack traceback:
	[C]: in function 'assert'
	/root/openface/batch-represent/dataset.lua:193: in function '__init'
	/root/torch/install/share/lua/5.1/torch/init.lua:91: in function </root/torch/install/share/lua/5.1/torch/init.lua:87>
	[C]: in function 'dataLoader'
	/root/openface/batch-represent/batch-represent.lua:19: in function 'batchRepresent'
	./batch-represent/main.lua:42: in main chunk
	[C]: in function 'dofile'
	/root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
	[C]: at 0x00406670

I looked inside aligned directory and it has the aligned and cropped face images (in .png format) for the 10 images corresponding to the ones present in training-images folder. Following this thread I executed the commands below :
$ mkdir -p classify-test/raw/{lennon,clapton}
$ cp images/examples/lennon-* classify-test/raw/lennon
$ cp images/examples/clapton-* classify-test/raw/clapton
$ ./util/align-dlib.py classify-test/raw align innerEyesAndBottomLip classify-test/aligned --size 96
$ ./batch-represent/main.lua -outDir classify-test/features -data classify-test/aligned

Which works fine with and gives the following output:
root@e917ad344dc4:~/openface# ./util/align-dlib.py classify-test/raw align innerEyesAndBottomLip classify-test/aligned --size 96
=== classify-test/raw/lennon/lennon-2.jpg ===
=== classify-test/raw/clapton/clapton-2.jpg ===
=== classify-test/raw/clapton/clapton-1.jpg ===
=== classify-test/raw/lennon/lennon-1.jpg ===
root@e917ad344dc4:~/openface# ./batch-represent/main.lua -outDir classify-test/features -data classify-test/aligned
{
  data : "classify-test/aligned"
  imgDim : 96
  model : "/root/openface/models/openface/nn4.small2.v1.t7"
  device : 1
  outDir : "classify-test/features"
  cache : false
  cuda : false
  batchSize : 50
}
classify-test/aligned
cache lotation: 	/root/openface/classify-test/aligned/cache.t7
Loading metadata from cache.
If your dataset has changed, delete the cache file.
nImgs: 	4
Represent: 4/4
root@e917ad344dc4:~/openface#

I double checked ensuring path to directories are correct. What else could throw this error ?
System Information :
Operating system: [Ubuntu 16.04]    64 bit version
Processor : Intel i5

Have you tried it with the trailing /'s as listed in your linked tutorial?
For example:
./batch-represent/main.lua -outDir ./generated-embeddings/ -data ./aligned-images/
vs. yours:
./batch-represent/main.lua -outDir classify-test/features -data classify-test/aligned

Yup. Tried with trailing /'s. Sorry I forgot to mention that above.

@tr-gis are your images contained in a subdirectory of ./aligned-images/? I just encountered the same issue and solved it by creating an arbitrary subdirectory to hold my images, literally ./aligned-images/arbitrary-subdirectory/. The dataset.lua file seems to expect that images will be grouped in folders representing people (e.g. ./aligned-images/will-ferrell/, ./aligned-images/chad-smith/, ./aligned-images/jimmy-fallon/ for the tutorial)

authors: GISDev01 dillontiner tr-gis

repo: cmusatyalab/openface


text:
Feature request: clickable grahps on Stats page

feature request
Have the graphs on the Stats page open a filtered search when interacted with.
example
In the Distribution of projects by rating section of the Stats page it may be helpful that when clicked on, a section opens up a search of projects filtered by the category represented by that part of the graph.

Clicking 'sandbox' grade 'A', could open the following search: https://clomonitor.io/search?foundation=cncf&maturity=sandbox&rating=a&page=1
The other graphs on the page could have similar click through behaviour.
rationale
This may make it easier to find groups of projects that are having the same kinds of issues as well as making the graphs more transparent (showing exactly the projects that make up each category graphed).

#394 is great, thanks for that.
Before we close this, we may want to consider adding this functionality to some of the other types of graphs on the page (I just used the donuts as an example). Or discuss if this functionality is especially useful (it'll be interesting to see the analytics on how often the click through gets used now that the feature is implemented on the one type of graph).

No worries!
Sure, we were going to add some more, we can leave it open in the meantime 🙂
We thought that adding links to the last section of the stats page that displays the percentage of repositories passing each check could be specially useful (as well as enriching the filters on the search page), but there are some details that need to be addressed before as discussed in #391.

Your https://github.com/cncf/clomonitor/discussions/391#discussioncomment-2978085 comment really helped me understand some of the details going on here, thanks!

Response to https://github.com/cncf/clomonitor/discussions/391#discussioncomment-2978085 as I think it is more relevant to this issue than that topic.

checks are not really happening at the project level, but per repository.

That makes sense - The graphs in the second half of the stats page are repository-based, but all search results are projects.

We'd love to add some extra filters that would allow you to get the entities that pass some checks and/or fail others, export the results to csv, etc. The problem is that if the entity was the project, what would it mean to pass or fail a check, that all of the repositories in the project would pass it? any of them? none?

How does this work now?
(thanks so much for including .gitpod, it makes it easier to spin things up and take a look under the hood!)
If the project is a top-level architectural entity, I'd think repos would be their constituent parts. Some repos aren't critical. Is there a way for a project to flag that a repo is not to be considered for scoring? (I expect that Sandbox projects would have more of these kinds of workspace/experimental repos and that by the time a project gets to Graduated that most of these will be removed)
So at the Graduated level, I'd expect that any repo in the project would have all their repos considered when it comes to passing or failing a check.

We are concerned this may not be super intuitive, but it'd be good to know what do you think.

As long as search results are only projects, I agree linking out to a search result from these Repository graphs could be counterintuitive. However, I'd still be interested in knowing which projects are building up the data here. I'm not sure how best to do this -- If you have time, doing some paper-prototype mockups may help to see if it's clear or not.

An alternative approach would be to add a section where the main entity was a repository. The problem just mentioned would disappear immediately given that checks are done per repository. But in this case, we don't know if we'd be complicating the user experience in CLOMonitor

I don't think we should change the primary entity.

How does this work now?

At the moment all filters in the search page are based on project data. Even though all checks are done at the repository level, the project entity itself has a score and a rating, that's the result of merging all its repositories scores. All of this works based on some configurable weights per section and check.

If the project is a top-level architectural entity, I'd think repos would be their constituent parts. Some repos aren't critical. Is there a way for a project to flag that a repo is not to be considered for scoring? (I expect that Sandbox projects would have more of these kinds of workspace/experimental repos and that by the time a project gets to Graduated that most of these will be removed). So at the Graduated level, I'd expect that any repo in the project would have all their repos considered when it comes to passing or failing a check.

At the moment not all the projects' repositories are listed in CLOMonitor. We hand picked most of the pinned ones plus others that seemed relevant. We've been discussing what would be the best way to manage this data going forward, but it's still not clear (admin UI, some config files, etc). At the moment there isn't a way to not consider a repo that's been added to CLOMonitor for scoring, but we usually don't add those. One or more check sets are manually added to each repository, which define what checks we'll run on it.

As long as search results are only projects, I agree linking out to a search result from these Repository graphs could be counterintuitive. However, I'd still be interested in knowing which projects are building up the data here. I'm not sure how best to do this -- If you have time, doing some paper-prototype mockups may help to see if it's clear or not.

Yes, we'll need to experiment a bit with this 👍

I don't think we should change the primary entity.

It wouldn't be changing the primary entity actually, but adding a new page or tab where the main entity is the repository. The search page and stats would remain as they are (based on projects), it'd be something extra accessible from both of them. Maybe we'll have to experiment a bit with this idea too to see if it fits well and doesn't complicate things too much 😉
Thank you very much for taking the time to go through all of this and for the feedback, it really helps!

The graph pointed with the arrow in the screenshot below is now clickable as well. The date input controls in the search page have been improved to accommodate this feature and have more flexibility (before it was only possible to filter per year with a slider).

The graph on its left probably doesn't fit well with clicking, same as the "projects average score per category" one.
The only one remaining would be the bottom one that depends on finding a solution to the projects/repos discussion we were having here and in #391 🙂

Thanks @tegioz! Links on the heat graph work great.

The graph on its left probably doesn't fit well with clicking, same as the "projects average score per category" one.

I agree with you on this.

The only one remaining would be the bottom one that depends on finding a solution to the projects/repos discussion we were having here and in https://github.com/cncf/clomonitor/discussions/391 🙂

Should we convert that conversation into an issue? 🙂

I can't see a way to convert it, but i've opened an issue: https://github.com/cncf/clomonitor/issues/405

Checks in the last graph of the stats page are now linked to the search page 🙂
We'll deploy it in a few hours.

Cool, thanks!

authors: nate-double-u tegioz

repo: cncf/clomonitor


text:
Remove annual review templates

Removing annual review templates as projects are no longer required to submit annual reviews
xref: https://github.com/cncf/toc/issues/1404

Hi @angellk 👋
Thanks for your PR!
These templates are part of the notifier component, that can be used to notify projects of certain events (like when the annual review was due). But this feature is not enabled at the moment in the current CLOMonitor deployment, so projects should not be receiving any notifications from CLOMonitor. The annual review checks were removed from CLOMonitor one year ago (in #1337, in relation to cncf/toc#1181), so they shouldn't appear in any of the projects pages either.
Hope this helps 🙂

Will close this PR for now, please feel free to reopen if needed 🙂

authors: angellk tegioz


text:
[Portuguese] Update tags in all terms

Signed-off-by: edsoncelio edsoncelio2020@gmail.com
Describe your changes
Update tags in all terms localized in Portuguese (Brazil).
Related issue number or link (ex: resolves #issue-number)
https://github.com/cncf/glossary/pull/1583
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

PTAL @seokho-son @jihoon-seo

Closing due to the number of changes - I'll open a new one soon :D

repo: cncf/glossary


text:
Replacing LogDNA SVG Logo

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 250 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Looks Good To Me - LGTM!

Thanks, but we fixed the logdna logo in: https://github.com/cncf/landscape/commit/792b2d6461d557c269cc52fcb5378fc706d2af2c

authors: dankohn smusali

repo: cncf/landscape


text:
Apolicy update to landscape

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape ready!
Built with commit 343007d7232557ca727515e5176a065aa9523dc5
https://deploy-preview-1970--landscape.netlify.app

Deploy preview for landscape ready!
Built with commit 343007d7232557ca727515e5176a065aa9523dc5
https://deploy-preview-1970--landscape.netlify.app

LGTM

LGTM

"LGTM"?

"LGTM"?

fix the branch conflicts :)?

fix the branch conflicts :)?

what branch conflicts?
On Wed, Jan 27, 2021 at 2:12 PM Chris Aniszczyk notifications@github.com
wrote:

fix the branch conflicts :)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape/pull/1970#issuecomment-768612870, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2CD2FDWVZGS2Y6ME75FWLS4CFU5ANCNFSM4WQLVGJQ
.

what branch conflicts?
On Wed, Jan 27, 2021 at 2:12 PM Chris Aniszczyk notifications@github.com
wrote:

fix the branch conflicts :)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape/pull/1970#issuecomment-768612870, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2CD2FDWVZGS2Y6ME75FWLS4CFU5ANCNFSM4WQLVGJQ
.

@eranjl also your SVG seems empty? comes up blank for me

@eranjl also your SVG seems empty? comes up blank for me

in the branch it was fine.
https://deploy-preview-1970--landscape.netlify.app/
you can see it here.
On Wed, Jan 27, 2021 at 3:29 PM Chris Aniszczyk notifications@github.com
wrote:

@eranjl https://github.com/eranjl also your SVG seems empty? comes up
blank for me
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape/pull/1970#issuecomment-768646483, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2CD2AZ65ZTPOZB3GAYBKDS4COWPANCNFSM4WQLVGJQ
.

in the branch it was fine.
https://deploy-preview-1970--landscape.netlify.app/
you can see it here.
On Wed, Jan 27, 2021 at 3:29 PM Chris Aniszczyk notifications@github.com
wrote:

@eranjl https://github.com/eranjl also your SVG seems empty? comes up
blank for me
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape/pull/1970#issuecomment-768646483, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2CD2AZ65ZTPOZB3GAYBKDS4COWPANCNFSM4WQLVGJQ
.

@caniszczyk I removed the new svg file. I don't know what went wrong with it.
I checked and saw that the file under hosted_logos is fine and should work.

authors: CNCF-Bot caniszczyk eranjl


text:
chore: improve non-code projects list

Improve the non-code list of projects

Looks good.

repo: cncf/tag-contributor-strategy


text:
Wrong results

I've limited the Radius(Distance) to 30 km and am getting back results with larger distances even twice the distance i've set

Same problem here I query for 30Km and firebase return results from more than 60Km

Have you found any solution for this? I'm having the same problem

authors: aliakkawi damalo93 guiroco

repo: cngeru/georange


text:
switch between radio button to check box bug

Hi, i discovered a bug in this great lib when trying to switch between radio button and check box (group class).
The 2 buttons allow to choose the kind of object but when you play with check boxes, program crash.

`#include <nana/gui/wvl.hpp>
#include <nana/gui/widgets/button.hpp>
#include <nana/gui/widgets/group.hpp>
class Principal : public nana::form
{
public:
    Principal() : form(nana::API::make_center(400,300)) {

    	m_btnradio.caption("Radio");
    	m_btnradio.events().click([this]{
        	this->m_group.radio_mode(true);
    	});

    	m_btnbox.caption("Box");
    	m_btnbox.events().click([this]{
        	this->m_group.radio_mode(false);
    	});

    	m_group.radio_mode(false);
    	m_group.add_option("Disco");
        m_group.add_option("Blues");
        m_group.add_option("Jazz");
        m_group.add_option("Rock");
        m_group.add_option("Dance");
        m_group.add_option("Rap");
    }

private:

	nana::button m_btnradio{*this,nana::rectangle(50,30,140,20)};
	nana::button m_btnbox{*this,nana::rectangle(210,30,140,20)};
    nana::group m_group{ *this, "Music Style", false, 2, nana::rectangle(50,70,200,200) };

};
int main()
{
Principal f;
f.show();
nana::exec();
return 0;

}`

Hi, Thank you for reporting this bug!

authors: Bluescaster cnjinhao

repo: cnjinhao/nana


text:
Nginx upload limit size

Hi,
I have just installed canvas and tried my first post :)..
When I upload an image I'm getting an error "Error during upload  tap to retry"
The image is 1.3MB and I can see it has been uploaded to /storage/app/public/canvas/images
Any idea what I have done wrong?

playing around it seems to get upset if the image size is >1MB? (largest I tested that worked was 957kb)

Hm interesting. Are there any logs that give more info on the error?

I've run into this before and couldn't figure out why. I remember having to re-export an image to JPEG for it to upload properly because the PNG would upload to 100% and then fail. Unfortunately I can't reproduce this now.

ahh.. 2020/05/16 01:17:25 [error] 1365#1365: *6 client intended to send too large body: 1318859 bytes, client: 192.168.10.1, server: www-ticm.local, request: "POST /canvas/api/media/uploads HTTP/1.1", host: "www-ticm.local", referrer: "http://www-ticm.local/canvas/posts/dc9b1b71-cf7b-4a81-bea7-68afd5f9baa7/edit" now to find out why

ok solution seems to be that by default nginx limits uploads to 1M
however its not so simple to override this - https://stackoverflow.com/a/14358928/9708285 is what I have followed which fixed it - maybe something worthwhile for the wiki?

Good find. I'll close this out since it's not a bug with the package, but I'll see if it can fit in somewhere in the readme.

authors: austintoddj baradhili davidgrzyb

repo: cnvs/canvas

license: mit


text:
Signal danger zone image

Add an image to show where the "danger zone" section is.

Accepted pull request for additional image in documentation

authors: shipshupe westonal


text:
availability of certain GCP cloud regions language update

"Known issue: In addition to the non-GKE regions, we had to temporarily disable the following 4 GCP regions due to technical limitations that we are actively trying to resolve:"
We say this today, but can we change this to explicitly explain that the restrictions are due to resource constraints by GKE rather than any other technical limitation on the Cloud/ CRL side. This makes it sound like a Cloud issue when its really a resource issue for GCP.

Addressed in https://github.com/cockroachdb/docs/pull/7454/

authors: Amruta-Ranade kannanlakshmi

repo: cockroachdb/docs


text:
sql: persist table locality metadata and display in SHOW CREATE TABLE

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

LOCALITY directives on CREATE TABLE are now persisted onto the database. [#57513][#57513] {% comment %}doc{% endcomment %}

IDK if we need to explicitly document this...
@rmloveland You okay with me closing this?

yep, implied - closing!

authors: ericharmeling jseldess rmloveland


text:
cockroach gen docs

Documents cockroach gen.
Closes #98
Closes #648

This change is

@knz If you wouldn't mind taking a look at this, I'd really appreciate it.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f7bc4ab2c001feaa003c0a7cfff463ec21ceadde/

Reviewed 1 of 3 files at r1.
Review status: 1 of 3 files reviewed at latest revision, 13 unresolved discussions.

generate-cockroach-command-resources.md, line 2 at r1 (raw file):

---
title: Generate Cockroach Command Resources

I'm not fond of this title. The problem is that I can't make sense of either ((Cockroach command) resources) nor (cockroach (command resources)).
May I suggest: Automatic generator for configuration files and examples.

generate-cockroach-command-resources.md, line 3 at r1 (raw file):

---
title: Generate Cockroach Command Resources
summary: To generate additional resources for the cockroach command, such as man pages, use the cockroach gen command.

Summary: To generate ancillary data usable in combination with the cockroach command, such as ...

generate-cockroach-command-resources.md, line 9 at r1 (raw file):

You can generate additional resources for the `cockroach` command using `cockroach gen`, including:

- `man` pages

perhaps link to wikipedia here: https://en.wikipedia.org/wiki/Man_page

generate-cockroach-command-resources.md, line 11 at r1 (raw file):

- `man` pages
- `bash` autocompletion script
- Example data

Example SQL suitable to populate test databases

generate-cockroach-command-resources.md, line 70 at r1 (raw file):

### Generate Example Data

To test out CockroachDB, you can generate an example database, `startrek`, that contains 2 tables, `episodes` and `quotes`.

We support multiple example databases. However, please just mention that we support multiple databases and that the user can retrieve a list with help gen example-data, but do not give any details about the intro database. It is meant as an easter egg.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/de0b8e4cff0357eec014e5dcbb310e7470910351/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/53b5757911bb19b9ecf6b9925de61e30049ae833/

Review status: 0 of 3 files reviewed at latest revision, 13 unresolved discussions.

generate-cli-utilities-and-example-data.md, line 70 at r1 (raw file):
Previously, knz (kena) wrote…
> We support multiple example databases. However, please just mention that we support multiple databases and that the user can retrieve a list with `help gen example-data`, but do not give any details about the `intro` database. It is meant as an easter egg.

Added note. Nice easter egg :)

generate-cockroach-command-resources.md, line 2 at r1 (raw file):
Previously, knz (kena) wrote…
> I'm not fond of this title. The problem is that I can't make sense of either ((Cockroach command) resources) nor (cockroach (command resources)).
> May I suggest: `Automatic generator for configuration files and examples.`

Changing to `Generate CLI Utilities & Example Data`

generate-cockroach-command-resources.md, line 3 at r1 (raw file):
Previously, knz (kena) wrote…
> Summary: To generate ancillary data usable in combination with the cockroach command, such as ...

Reworded

generate-cockroach-command-resources.md, line 9 at r1 (raw file):
Previously, knz (kena) wrote…
> perhaps link to wikipedia here: https://en.wikipedia.org/wiki/Man_page

Done.

generate-cockroach-command-resources.md, line 11 at r1 (raw file):
Previously, knz (kena) wrote…
> Example SQL suitable to populate test databases

Done.

generate-cockroach-command-resources.md, line 19 at r1 (raw file):
Previously, jseldess wrote…
> Missing period at end of description. Same for other subcommands.

Done.

generate-cockroach-command-resources.md, line 26 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 29 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 45 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 48 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 51 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 58 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

generate-cockroach-command-resources.md, line 61 at r1 (raw file):
Previously, jseldess wrote…
> Missing colon.

Done.

Comments from Reviewable

authors: cockroach-teamcity knz sploiselle


text:
add launchd configuration to support brew services

Add a launchd configuration so that brew services can manage a single-node Cockroach cluster, if so desired.
Fixes cockroachdb/cockroach#9438.

This supersedes #1, which is inexplicably ignoring my force pushes. @bdarnell, I've updated the formula to serve the admin on port 26256, as discussed, and added a caveat reminding users to only use this configuration in development. The full caveats read:
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start an insecure single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

To run CockroachDB in production, please see:
  https://www.cockroachlabs.com/docs/recommended-production-settings.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start

The last four lines are added automatically when a plist is present.

This change is

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

Formula/cockroach.rb, line 36 at r1 (raw file):

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">

if you put this below test, would that produce easier diff to review? just wondering.

Comments from Reviewable

Perhaps a little bit, but I actually adapted the plist from Postgres's so any similarity with the commented-out one is purely incidental. Plus this is the standard order of Homebrew formulae: install, caveats, plist, test do.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

LGTM, but I think the insecurity needs to be called out prominently in the caveats. "Don't use this mode for data you care about".

How's this? Updated caveats:
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start a single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

Do NOT use this cluster to store data you care about; it runs in insecure
mode and may expose data publicly in e.g. a DNS rebinding attack. To run
CockroachDB securely in production, please see:
  https://www.cockroachlabs.com/docs/recommended-production-settings.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start

recommended-production-settings.html doesn't talk about security. Link to https://www.cockroachlabs.com/docs/secure-a-cluster.html

Good call, thanks. Done.
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start a single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

Do NOT use this cluster to store data you care about; it runs in insecure
mode and may expose data publicly in e.g. a DNS rebinding attack. To run
CockroachDB securely, please see:
  https://www.cockroachlabs.com/docs/secure-a-cluster.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start

authors: bdarnell benesch tamird

repo: cockroachdb/homebrew-cockroach


text:
Explore passing back selectedOriginalKeys to sync formulas

If the doc user has picked certain properties using the new column picker, how does the pack sync formula know which columns were picked?
The updated schema will be passed in with the sync execution context as in context.sync.schema. To get the list correctly, the pack maker basically needs to do const originalKeys = Object.entries(context.sync.schema.items.properties).map([key, property] => property.fromKey || key); to get the list of picked properties.
Passing selectedOriginalKeys in here would make it easier for pack makers.
However, the challenge is that we may be supporting picking properties in a nested structure. (e.g. picking properties in issues->project, where issues is the top level object). A simple array won't be enough to represent the options.
A few alternatives:

passing as a dict from schema identity to the list of keys picked. this may not work if the top level object has two fields of the same object type. (e.g. issue.creator and issue.assignee can be both of schema User)
passing a nested structure like {fieldA: {}, fieldB: {}, fieldC: {subField1: {}, subField2: {}}, fieldD: {}}

I figured either options above are pretty complicated to parse and won't give the pack maker much convenience than they parsing the context.sync.schema object directly. So in this PR I am only adding a simple string[] field that can be used by most simple pack implementations which don't care about nested fields. I'd love to hear what you think about this: do we need this convenient field at all or should we make it more complicated?
@jonathan-codaio @alan-codaio @dweitzman-codaio

With discussions of https://staging.coda.io/d/Packs-Platform-IA-o-packs_d36WK4zgrYx/Nested-properties-in-the-column-picker_suAJG#_lub1p, I don't think it's necessary to support a full nested property selection at the point but we should still make the API flexible. Let me change to a helper approach instead.

we are close to ship column picker. I am coming back to merge this now and update the jira pack to leverage the user picked columns to optimize its data fetching. cc @patrick-codaio as we just chatted.

repo: coda/packs-sdk


text:
Can not access page when page first loaded

Hi, I'm using Microsoft Edge browser 105.0.1343.53 x64 and install this extension from chrome web store.
Also, I installed Local Rest API plugin.
But when I open the web page, it can not access page, and can not set it to acces all host.
I only can access web page by click this extension every time.
Here is the snapshot:

I'm afraid this extension is only tested and supported for use on Chrome.  If you'd like to see if you can find help from others in the community, though, feel free to open a Discussion on the "Discussions" tab.
Cheers & good luck!

authors: acrobatman coddingtonbear

repo: coddingtonbear/obsidian-web


text:
Issue #1216 Update ~/.kube/config with crc contexts

Fixes: Issue #1216
Using the same strategy as minishift (https://github.com/minishift/minishift/pull/2881/files), update kubeconfig with crc-developer and crc-admin context.
It vendors k8s code and a little part of the openshift/oc tokencmd.RequestToken. It implies a large list of replace in go.mod but most of them are only used for dependency resolution and are not included in the final vendor directory. This list is taken from https://github.com/openshift/oc/blob/release-4.5/go.mod#L78 (I tried to trim it without success).
It also allows us to remove this kind of struct https://github.com/code-ready/crc/blob/master/pkg/crc/cluster/clusteroperator.go#L15

One thing to have in mind is that this doubles build times (from a few seconds to 2*a few seconds) and binary size (from 10MB to 20MB).

/retest

@guillaumerose Overall, this looks good to me, able to test it also. I think we should have it as part of single commit instead of vendoring as part of separate commit. I know that @cfergeau suggested it as part of review but to me it doesn't make sense to have vendor part as different commit then using actual module/package.

I merged the 2 commits. We should be good now!
The default context is admin. I chose it because otherwise, oc get all and kubectl get all return lot of errors and admin has already access to default project. Is it ok?

@guillaumerose looks like in case of proxy it is failing in the CI.
Command stderr: level=error msg="Cannot update kubeconfig: proxyconnect tcp: dial tcp 192.168.130.11:3128: connect: connection refused"
Cannot update kubeconfig: proxyconnect tcp: dial tcp 192.168.130.11:3128: connect: connection refused

Yes I will look at it. It also explains why some users might have issue with crc if oc talks to the proxy!

Yes I will look at it. It also explains why some users might have issue with crc if oc talks to the proxy!

This should be handled by oc-env
$ ./out/linux-amd64/crc oc-env
export PATH="/home/teuf/.crc/bin/oc:$PATH"
export HTTP_PROXY="http://squid.redhat.com:3128"
export HTTPS_PROXY="http://squid.redhat.com:3128"
export NO_PROXY="127.0.0.1,localhost,.testing"
# Run this command to configure your shell:
# eval $(crc oc-env)

Why do we want the oc command to use a proxy ? Maybe there are some remote interactions (not only the local server?).

Why do we want the oc command to use a proxy ? Maybe there are some remote interactions (not only the local server?).

@guillaumerose it is mostly because noproxy otherwise .testing also route from proxy which we want to avoid.

/retest

/retest

/retest this please

/retest this please

/retest this please

authors: cfergeau guillaumerose praveenkumar

repo: code-ready/crc


text:
Update golangci-lint to latest version

This also changes the way golangci-lint is installed when it's not available.

ci/prow/images fails with
 go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.44.0: cannot query module due to -mod=vendor

I'll need to investigate this ^^

I'll need to investigate this ^^

May be an older version of go in prow CI side.

authors: cfergeau praveenkumar


text:
Test/integ stream to dest

Description of Change

Adds missing integration test for push restore
Adds missing unit test for get_web_restore_info()
Sets octet-stream Accept header for stream_from_backup().
Removed expected test failure (fails in our Partner org but we don't expect a failure in the mock server)
Addresses python2 warnings
Prettifies a test-JSON blob
Simplifies the path parameter used for web/push restore in tox.ini

Some of these changes are needed for the mocker server test_archive integration test
Issues Resolved
n/a
Testing Procedure

Web restore regression test
Run integration test with mock server

PR Checklist
Did you remember to do the below?

[X] Add unit tests to verify this change
[n/a] Add an entry to CHANGELOG.md describing this change
[n/a] Add docstrings for any new public parameters / methods / classes

I still need to regression test web restore, but visually, this looks good.

@alanag13 For what it's worth, it seems to still work

@alanag13
Do you plan to test that web restore still works from adding that header?  We could alternatively make a small ticket and let QA do a regression test.
(I have also made sure it still works myself and feel confident).


text:
shouldNotHave(text(EMPTY_STRING)) operator isn't working

My code:
private static final String EMPTY_STRING = "";
SelenideElement Element = $(byClassName("phone-box"))
Element.shouldNotHave(text(EMPTY_STRING));
=> Test failed with message:
Element should not have text '' {By.className: phone-box}
Element: '+7 499 955-56-58'
!!!!BUT!!!!
Operator Assert.assertFalse(Element.text().equals(EMPTY_STRING)); is working fine.

Hi @AlexMMelnikov
could you provide simple html page to reproduce problem?

Hello. Yes, sure - https://aurora-tech.ru/

sholdNotBe(empty) work well

@AlexMMelnikov
I guess it isn't Selenide issue.
Explanation:

text(EMPTY_STRING) uses String.contains() and "" occurs between every character and also at start and end of string. That's why shouldNOT assert fails.
text().equals(EMPTY_STRING) - uses String.equals() and "" is not equal any non-empty string.

Hope I helped you.

@AlexMMelnikov Exactly. Methods $.shouldHave(text(...)) and $.shouldNotHave(text(...)) mean substring. Both methods are nonsence with empty string parameter.
(Probably they could throw an exception (or at least write warning) when empty parameter is given.)
What you actually need is $.sholdNotBe(empty)

authors: AlexMMelnikov BorisOsipov SergeyPirogov asolntsev

repo: codeborne/selenide


text:
Remove superfluous DELETE method documentation

As in https://github.com/codebulb/crudlet/issues/2, except that we don't need to edit the source code, only update the README documentation.

Fixed.

repo: codebulb/hapi-bookshelf-crud


text:
customLocator plugin only allows one attribute

What are you trying to achieve?

Allow the customLocator to use multiple attributes as hooks

Details

CodeceptJS version: 3.3.3
NodeJS Version: v16.14.2
Operating System: OSX Big Sur
puppeteer
Configuration file:

exports.config = {
  tests: './test/*.test.js',
  output: './output',
  helpers: {
    Puppeteer: {
      url: 'http://demoqa.com',
      show: true,
      windowSize: '1200x900'
    }
  },
  plugins: {
    customLocator: {
      enabled: true,
      attribute: 'id,data-test-id,data-testid',  // something like this
      prefix: '$',
    }
  },
  include: {
    I: './steps_file.js',
    LoginPage: './pages/LoginPage.js',
  },
  bootstrap: null,
  mocha: {},
  name: 'codeceptjs-issues'
}

attribute as array will be better ;-)
attribute: ['id', 'data-test-id', 'data-testid'],

authors: aruiz-caritsqa rebajz

repo: codeceptjs/CodeceptJS


text:
Thang editor saving bug

While saving a change to a thang through the Thang Editor, when I hit Save, the "Saving..." window appears, but never goes away (it gives the error 409 (Conflict)).
Note: In spite of this, the changes are successfully saved.

Here is the stack trace:
POST http://direct.codecombat.com/file 409 (Conflict)
Q.cors.t.crossDomain.send jquery.js:8625
Z.extend.ajax jquery.js:8161
t.exports.o.uploadGenericPortrait ThangType.coffee:307
(anonymous function) ThangTypeEditView.coffee:495
h jquery.js:3094
c.fireWith jquery.js:3206
i jquery.js:8259
(anonymous function) jquery.js:8600

repo: codecombat/codecombat


text:
Nextup rework

Change NEXT_UP.md file to something table based
Rename to SCHEDULE.md
Include links to challenge.md for each week
Add previously missing content
Utilize named links for user profiles

Before this is merged I would like to remove NEXT_UP.old.md file

repo: codeconnector/CodingDojo


text:
List issues that dont need help anymore

Description
There are a bunch of open github issues that are really old. They most likely don't need any help any more. Lets come up with a way to find issues that dont actually need help any more. Age is probably just the first step.
Start by listing out old issues. We can look at them and see which ones are still valid or not. If we can find something else common with them, then we can easily identify dead issues.
Then we can decide what to do with them.

Manually ping them asking if the issue is still relevant?
Make a bot to ask if the issue is still relevant?
Hide them from the Civic Issue Finder

What is the cut off for an old issue? Created date or last updated date?
https://github.com/GSA/data.gov/issues/100 was created over a year ago, but had the "help wanted" label added within a year. We've pinged them to see if it still needs help.
This issue is as old as the Civic Issue Finder. We've pinged them to see what happens too.
In this highly clicked issue we pinged them and they removed the "help wanted" label.

More evidence that pinging them works.
https://github.com/codefordenver/CodeAcross-2015/issues/12

re: If we wanted to make a bot, Github says that we can:
User accounts are intended for humans, but you can give one to a robot, such as
a continuous integration bot, if necessary.

I think now selecting those issues that we want is now the task. Currently the query I'm using is
q = ''' SELECT html_url,clicks,view_sources FROM issues WHERE state='open' '''
But we can also pull created_at and see how long the issue has been open and only ping issues that are >30 days old.
This is optional but we can also figure out which ones we've pinged and check if their status has changed? Which, one way can be to, check once daily and see if there are any new closed issues that day (check closed_at) or even see if the # of comments increased by more than 1 (that means in addition to our comment, someone else responded) and it can send us an email (or something along those lines) that lets us know there has been an update.

authors: eunicekokor ondrae

repo: codeforamerica/gotissues


text:
Export student roster

Teachers have said how it would be useful to be able to export the student roster into:

a CSV file to do their own analyses & visualization in Excel
a report to show to parents at meetings

Related to #72

Both teachers and principals have said that an export of the roster to CSV or Excel #169 would be more useful than the export of the profile #72.

Data export
"Can you export the Roster for the whole class, whole school?"
"As a teacher I would want to export all my student's data, not each student's data one at a time and have to compile 25 student files"

@alexsoble: Let's remove the export button from the roster for now since it is not functioning and can be confusing.

Will remove. Would be good to actually implement.

authors: alexsoble marimuraki

repo: codeforamerica/somerville-teacher-tool


text:
Check table address when Apartment number is UNDEFINED

Make sure empty string is shown instead of undefined

Looks fixed on latest main


text:
radio group label spacing: ReportFormpage

from beta site testing "report" page
Anonymity question - first line of each option does not line up with corresponding radio button, and line spacing does not clearly separate the options.
EITHER
realign buttons with first line of each option
OR
Separate options with more space
This also falls in line with redoing utility components and converting them from Mui to custom components.
Fixing the spacing or text alignment on the labels may not be super simple since the radio groups are custom components built with multiple custom styled Mui components.


text:
Documentation for simplerest

Could you possibly give a small bit of documentation regarding the different capabilities for Simple rest and what each of them mean? I am new to using applications like postman and I need to test a chatbot.

I added some documentation to the Wiki pages:
https://github.com/codeforequity-at/botium-core/wiki/Botium-Configuration#capabilities-for-operation-mode-simplerest
I hope this is useful for you. If you have troubles setting it up, maybe I can assist.

Thanks for the documentation, I'll try to test my bot and let you know if I run into any problems

This is my code.
const BotDriver = require('botium-core').BotDriver
const Capabilities = require('botium-core').Capabilities
const Source = require('botium-core').Source
function assert (expected, actual) {
if (!actual || actual.indexOf(expected) < 0) {
console.log(ERROR: Expected <${expected}>, got <${actual}>)
} else {
console.log(SUCCESS: Got Expected <${expected}>)
}
}
const driver = new BotDriver()
.setCapability(Capabilities.PROJECTNAME, 'Delta-Chatomate')
.setCapability(Capabilities.CONTAINERMODE, 'simplerest')
.setCapability(Capabilities.SIMPLEREST_URL, 'https://delta-chatomate.herokuapp.com/bot/')
.setCapability(Capabilities.SIMPLEREST_METHOD, 'POST')
.setCapability(Capabilities.SIMPLEREST_BODY_TEMPLATE, {
"userUtterance": "{{msg.messageText}}",
"sender": "765757765"
})
.setCapability(Capabilities.SIMPLEREST_HEADERS_TEMPLATE, '{ "Content-Type": "application/x-www-form-urlecoded" }')
.setCapability(Capabilities.SIMPLEREST_CONTEXT_JSONPATH, '$')
.setCapability(Capabilities.SIMPLEREST_RESPONSE_JSONPATH, '$.utterance.*')
driver.BuildFluent()
.Start()
.UserSaysText('Hello there')
.WaitBotSaysText((text) => assert('Hello there. I am ChatomateBot.', text))
.UserSaysText('What can you do?')
.WaitBotSaysText((text) => assert('I can help you learn about Chatomate. If you have questions, fire away.', text))
.Stop()
.Clean()
.Exec()
.then(() => {
console.log('READY')
})
.catch((err) => {
console.log('ERROR: ', err)
})
This is a screenshot from Postman. I'm not sure what I am doing wrong here.

I see what's the problem - you did everything right, but posting body as x-www-form-urlecoded is not supported right now, just json.
If you know javascript (I suppose you do), you could add the required code in file:
https://github.com/codeforequity-at/botium-core/blob/master/src/containers/SimpleRestContainer.js, function "_buildRequest" at the bottom. Shouldn't be hard to do.

Thanks a lot for your help! Thanks for adding those features!

authors: akshayCha codeforequity-at

repo: codeforequity-at/botium-core


text:
hyperlink asserter is not working.

hyperlink assertion is not working.
In basic asserter js file while accessing botmsg, b.payload is written while in webdrivoerio index file botmsg json is created with button.payload attribute.
basic asserterjs file need to be changed, in if(botmsg.buttons) condition, b.payload needs to be written instead of b.imageuri
same would apply form media condtion.
after above changes hyperlink asserter is worked. attaching the screenshot for ref

@radhabasida thanks for the analysis
@stefan-sev please add the "payload" (for buttons) and the "mediaUri" to the asserter

authors: codeforequity-at radhabasida


text:
神戸市データ追加

神戸市幼稚園・保育所・こども園の施設一覧は情報公開されている。
http://www.city.kobe.lg.jp/child/grow/shinseido/index02_02.html
ただし施設位置情報が無いため、geojson 形式データが生成できていない。
OpensStreetMap から取得できないか？

国土数値情報にデータが揃っている。ただし状況も変化しているので、データの突き合わせが必要。
http://nlftp.mlit.go.jp/ksj/gml/datalist/KsjTmplt-P14.html
一部は openstreetmap にも入っている模様。

repo: codeforkobe/papamama