text:
Move license suggestions into the spdx picker

right now the suggestions are next to the license picker as an 'i'

It would be great to add them to the top of the spdx picker when you open it instead.
Similar to how we separate the NONE/NOASSERTION in the filterbar, we can separate and label the suggestions.
--------------------------
suggested
-----------
MIT (version 1)
Apache-2.0 (version 2)
all
------------
NONE
NOASSERTION
0BSD
AFL
...

(all and suggested would be lighter font)
suggested and all may need to have different padding to make it clear they are grouped

Even if i agree with the solution, i'd like to notice that doing that we can loose some of the suggestions functionalities, like show where the suggestion comes from and why.
Also, the user wont be able to see the suggestion since he starts typing in the License field.
Thoughts?

great points. I was mostly looking to free up some of the icons surrounding the license picker
revert + pencil + eyeball + (i)
it feels like too much.
I think we can ideally show the source of the suggestion in-line with the item
As for losing the suggestion once you start to type, backspacing could bring them back - I think that would work well

Got your point.
Probably we can involve into the discussion someone that actually use the application and can give a feedback from a user point view, like @bduranc for example.

@storrisi @dabutvin :
You've both brought up some very good points.
I agree about being conscious of excess clutter concentrated around key fields. I guess the question to ask ourselves for the UI is "how much is too much in one area?", i.e. is more than two buttons per field a problem. For myself at least, I feel the simpler we keep it the better.
Overall, the suggestion feature itself looks really cool and I think would be really beneficial to curators.
The biggest concern I have is if there are a large number of license recommendations showing up in the list (say anything >5). If this could happen, then the list could get too long and awkward to fit on the UI.
Also, if I may ask, where are these suggestions sourced from? is it whatever source the package was harvested from? or is there a dependence on a source location (GH at this moment) being populated?
Assuming the recommendations are based on an indexing of past component versions, it is beneficial I think to have this history in general, but an additional benefit is you also get to see a trend of license changes version to version. A good enhancement IMO would be what we are already doing for some of the Nuget packages (obtaining data from LICENSE.MD) and checking the history of the license file.
As for the placement of the suggestion feature in the UI, I think it would be nice to see this feature both where it is proposed now, but also inside the modal dialog that results from clicking the "pencil" icon next to the field (since it appears now that is the only way to add an SPDX expression to that field).

The biggest concern I have is if there are a large number of license recommendations showing up in the list (say anything >5). If this could happen, then the list could get too long and awkward to fit on the UI.

Well, i don't know if this is really possible. Since suggestions are taken from other version of the same definition, is there the possibility to have the same field with >5 different values during time?
BTW i agree, if the list becomes too long it would be difficult for the user to interact with.

Also, if I may ask, where are these suggestions sourced from? is it whatever source the package was harvested from? or is there a dependence on a source location (GH at this moment) being populated?

It takes the same information from other version of the same definition that have been curated recently.

it is beneficial I think to have this history in general, but an additional benefit is you also get to see a trend of license changes version to version.

If this is really important as it looks, then i would suggest to keep the list as it is already, and maybe improve it with other useful details.

As for the placement of the suggestion feature in the UI, I think it would be nice to see this feature both where it is proposed now, but also inside the modal dialog that results from clicking the "pencil" icon next to the field

Yes, we can do it.

(since it appears now that is the only way to add an SPDX expression to that field).

Not totally true, a change has been recently released, so now you are able to type a valid SPDX definition in the License picker (if you already know the structure) and use it suddenly.

With all these considerations, are we able to take a decision on this topic? I'd be happy to implement the best solution that meets everyone's needs.

@dabutvin @bduranc do you have any other feedback on this topic?

@storrisi: Overall, I really like the proposal.
I still think it should be in the license picker dialog as this is where the user makes their selection, but the blue "i" button next to the field as originally proposed is a good start. Furthermore, if the "i" button is what we have already done for other recommendation fields, then we should keep it consistent overall.

I like the suggestion of putting suggestions in the popups 👍
I still feel like we should remove the blu "i" to reduce the amount of clutter in the UI and instead prepend the suggestions to the top of the list when choosing inline

authors: bduranc dabutvin storrisi


text:
526 mybabb get ogimage tag to work

Testing with Lorem Picsum url.

Yes, Indeed this configuration works, need to change the inputs and find out why the url for the images only work on an external url,   It needs the https corrected for the website,  Look into the inspect to find it maybe.   Leave this configuration until modified,   Now to check about adding meta with    Front-Matter in Markdown Pages.

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Add no-doc metadata

We don't have a public api, indicate such with no-doc metadata.
This will be helpful to folks stumbling upon our docs on cljdoc.
Also mark private fns as private.

Have opened related issue on cljdoc: https://github.com/cljdoc/cljdoc/issues/474

repo: clj-easy/graal-build-time


text:
cause Value out of range for int: 3562345207

Exception: #error {
:cause Value out of range for int: 3562345207
:via
[{:type java.util.concurrent.ExecutionException
:message java.lang.IllegalArgumentException: Value out of range for int: 3562345207
:at [java.util.concurrent.FutureTask report FutureTask.java 122]}
{:type java.lang.IllegalArgumentException
:message Value out of range for int: 3562345207
:at [clojure.lang.RT intCast RT.java 1248]}]
:trace
[[clojure.lang.RT intCast RT.java 1248]
[clojure.lang.RT intCast RT.java 1218]
[progrock.core$interval_str invokeStatic core.clj 47]
[progrock.core$render invokeStatic core.clj 92]
[progrock.core$print invokeStatic core.clj 98]
[progrock.core$print invoke core.clj 98]
[progrock.core$print invokeStatic core.clj 102]
[clj_holmes.logic.progress$add_watch_to_counter$fn__519 invoke progress.clj 10]
[clojure.lang.ARef notifyWatches ARef.java 81]
[clojure.lang.Atom swap Atom.java 41]
[clojure.core$swap_BANG_ invokeStatic core.clj 2354]
[clj_holmes.engine$check_rules_in_code_structure invokeStatic engine.clj 9]
[clj_holmes.engine$scan_STAR_$fn__1238 invoke engine.clj 21]
[clojure.core$pmap$fn__8467$fn__8468 invoke core.clj 7024]
[clojure.core$binding_conveyor_fn$fn__5758 invoke core.clj 2032]
[clojure.lang.AFn call AFn.java 18]
[java.util.concurrent.FutureTask run FutureTask.java 264]
[java.util.concurrent.ThreadPoolExecutor runWorker ThreadPoolExecutor.java 1128]
[java.util.concurrent.ThreadPoolExecutor$Worker run ThreadPoolExecutor.java 628]
[java.lang.Thread run Thread.java 829]
[com.oracle.svm.core.thread.JavaThreads threadStartRoutine JavaThreads.java 596]
[com.oracle.svm.core.posix.thread.PosixJavaThreads pthreadStartRoutine PosixJavaThreads.java 192]]}

This issue could be solved with the latest version of the progrock project.  But it is not published to clojars yet.

source: gharchive/issue

repo: clj-holmes/clj-holmes


text:
Are you compatible with Docusaurus 3.x.x?

Hello. I'm looking for an opensource plugin that works with Docusaurus 3.x.x. I've searched online and they are still in progress.
Do you have plans to enable compatibility with 3.x.x anytime soon? Thanks

Yes, we are compatible with Docusaurus v3 starting with v0.7.0 😁

repo: cloud-annotations/docusaurus-openapi


text:
[Alibaba:VM] Nil Pointer Access Error with Unsupported Instance Type

[현황]

London Region에는 제공하지 않는 Instance Type ecs.c7.large을 입력으로 VM 생성 요청시 nil pointer access 오류가 발생하는 거 같습니다.
관련 Spider REST APIcurl -sX POST http://localhost:1024/spider/vm \
    -H 'Content-Type: application/json' \
    -d '{
          "ConnectionName": "alibaba-london-config",
          "ReqInfo": {
              "Name": "vm-01",
              "ImageType": "PublicImage",
              "ImageName": "ubuntu_22_04_x64_20G_alibase_20240508.vhd",
              "VMSpecName": "ecs.c7.large",
              "VPCName": "vpc-01",
              "SubnetName": "subnet-01",
              "SecurityGroupNames": ["sg-01"],
              "RootDiskType": "default",
              "DataDiskNames": [],
              "KeyPairName": "keypair-01",
              "VMUserId": "Administrator",
              "VMUserPasswd": "cloudbarista123^"
          }
      }'

{"message":"Internal Server Error"}

[분석]

지원하지 않는 InstanceType이어도 다음 반환 되는 값이 0 size array로 정상 반환됨

https://github.com/cloud-barista/cb-spider/blob/c3cb3aab1164e5f1d89dbe6c676c742149973f80/cloud-control-manager/cloud-driver/drivers/alibaba/resources/CommonHandler.go#L237

위 함수의 반환 값을 접근하는 다음 부분에서 nil pointer 오류 발생으로 추정됩니다.

https://github.com/cloud-barista/cb-spider/blob/c3cb3aab1164e5f1d89dbe6c676c742149973f80/cloud-control-manager/cloud-driver/drivers/alibaba/resources/VMHandler.go#L223

Fixed by https://github.com/cloud-barista/cb-spider/pull/1204

repo: cloud-barista/cb-spider


text:
fixing port conflict for uperf bidrec test

Description
Context: https://github.com/cloud-bulldozer/benchmark-operator/issues/780
Fixes
Assigning a different port for the reverse test so that it doesn't conflict with the forward test port.
Testing screenshot

Codecov Report

Merging #791 (917f1db) into master (94005cd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #791   +/-   ##
=======================================
  Coverage   53.47%   53.47%
=======================================
  Files           8        8
  Lines         331      331
=======================================
  Hits          177      177
  Misses        154      154

Flag
Coverage Δ

gha
53.47% <ø> (ø)

python-3.9
53.47% <ø> (ø)

unit
53.47% <ø> (ø)

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

Continue to review full report at Codecov.

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

authors: codecov-commenter vishnuchalla

repo: cloud-bulldozer/benchmark-operator


text:
Publish IBM Cloud Standard reference architecture

Publish content to:

IBM Cloud - https://github.com/IBM/automation-ibmcloud-infra-openshift

Dependencies

[x] IBM Resource Group
[x] IBM Access Group
[x] IBM VPC
[x] IBM VPC Subnets
[x] IBM VPC Gateways
[x] IBM OCP on VPC (ROKS)
[x] IBM Log Analysis (LogDNA)
[x] IBM Monitoring (Sysdig)
[x] IBM Object Storage
[x] IBM KMS
[x] IBM VPN Server
[ ] [BM VSI Proxy - cloud-native-toolkit/terraform-ibm-vsi-proxy#1
[ ] IBM VSI ArgoCD Bootstrap - cloud-native-toolkit/terraform-vsi-argocd-bootstrap#9
[ ] Portworx storage on IBM Cloud
[ ] ODF storage on IBM Cloud

Definition of Done

[ ] Define BOMs (Account Setup, Shared Services, VPC, Storage) in Automation Solutions repo
[ ] Document installation instructions in README in Automation Solutions repo
[ ] Generate automation logic from BOM in Automation Solutions repo and publish to repo - https://github.com/IBM/automation-ibmcloud-infra-openshift

Dup of IBM/automation-ibmcloud-infra-openshift#3


text:
Fix badarg error in couch_server:try_close_lru/1

The race condition in couch_server's ets table usage rears its ugly head
by leaving an entry in couch_lru. This patch just addresses the issue by
allowing the client pid to use the db and ignores the fact that for the
duration its over the max_dbs_open setting.

Great sleuthing @davisp.  I followed your logic through to the badmatch error and it seems sound.  The patch should address it.

lgtm +1

authors: bdionne davisp kocolosk

repo: cloudant/bigcouch

license_source: bigquery


text:
Add content to changes_docWithConflicts_conflictsShouldBeReturned test

The test com.cloudant.mazha.ChangesFeedTest#changes_docWithConflicts_conflictsShouldBeReturned currently has no content. The steps needed:

Conflict on server needs to be created
Test then determines if a conflicted document can be read from the changes feed.

Alternatively if we think this is of low value we should delete the test.

This library is now end-of-life and this issue won't be fixed.
This issue has been tagged EOL in case any forks want to import it.

repo: cloudant/sync-android


text:
Add force option on commands

Over the past month I have been working on setting up GARM instance and have ran into plenty of times where a --force would have come in very handy.
Examples:

(this happened many times accross 3 providers: k8s, gcp, openstack) Provider is unable to connect to infrastructure. Due to this the creation of a runner fails, but the delete method also tries to reach out to infrastructure and fails too, now I have a runner stuck on "pending_deleting" or "error" for which the retry loop will continue to attempt to delete, until connection is restored. I would like to be able to "force" it to delete the entry from the DB even if it didn't successfully delete from infrastructure. In this case since there is a network problem there was nothing to delete but even if something was created I can go to the infrastructure and do any manual deletion if needed.
Perhaps this is a different ask but: Org oauth2 token lost permission to the org, I need to delete the associated pools, but to delete the pools I need to delete the runners (Error: [DELETE /pools/{poolID}][400] DeletePool default  {Error:Bad Request Details:pool has runners}), but when I try to delete the runners I get error: Error: [DELETE /instances/{instanceName}][409] DeleteInstance default  {Error:Conflict Details:pool manager is not running for Org, Org manager is not running because of error failed to update tools for repo Org: fetching runner tools: GET https://api.github.com/orgs/Org/actions/runners/downloads: 403 Must have admin rights to Repository. so now I have a runner and a pool stuck and no way to force deletion of either.

Hi @Hdom !
In regards to 1), there is a --force-remove-runner|-f available to the runner remove command. In version 0.1.4, that command will transition the runner to pending_force_delete and will ignore any provider error when removing the runner.
In regards to 2), the limitation was intentional, to avoid situations in which a PAT mai expire or a runner may be executing a job, and someone tries to remove it. In such cases we don't really want to remove the runner, as that may cancel a potentially long running job, when the underlying runner just gets removed while executing.
But you are right, this does have the potential to put us in a situation where it's difficult to recover. I think we can have a procedure to purge a pool that has no chance to ever come back up due to having lost access to the entiry it was managing.
I will look into this.
For situations where you can get a new PAT, the quick fix is to replace the old one in the config. The pool should recover.

Oh man, I don't know how I missed that force flag, I swear I had looked at the help menu for the runner delete before and even tried adding a -f, maybe because I was using the 0.1.4-rc version of the cli.

I think I added this after RC1 (not sure). Also, sometimes I forget to properly change the help messages 😅 . But in 0.1.4 it should work. At least for ignoring provider errors. The PAT not having access is a different code path. Will need to see what the best way forward is for that one.

Added a PR to ddress this here:

https://github.com/cloudbase/garm/pull/231

That change adds a -b | --bypass-github-unauthorized to the CLI and a query arg to the API. This flag will work even if the pool manager is stopped due to an Unauthorized error.
If nothing really works and you want to remove the runner from the DB, you can specify both --force-remove-runner and the --bypass-github-unauthorized options. This will bypass the stopped pool and ignore the provider error.
Give it a shot and let me know.

authors: Hdom gabriel-samfira

repo: cloudbase/garm


text:
🛑 cbn.id is down

In d45f0d9, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 188644b.

repo: cloudbip/upptime


text:
🛑 cbn.id is down

In bed5472, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 2ea7309 after 1 hour, 22 minutes.


text:
🛑 connectindo.com is down

In 1c60ee0, connectindo.com (https://connectindo.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: connectindo.com is back up in b65661b.


text:
🛑 mncplay.id is down

In 8e5a4e9, mncplay.id (https://mncplay.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mncplay.id is back up in 6e83170.


text:
🛑 cbn.id is down

In fd4c418, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 3e8329b.


text:
🛑 berdu.id is down

In d1f8bc4, berdu.id (https://berdu.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: berdu.id is back up in a6ada2b.


text:
🛑 cbn.id is down

In ef4a711, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 73927c9.


text:
Duplicate results with Trino

Describe the bug: Duplicate results occur when connecting Trino with hue. But Using sqlalchemy and trino client does not.
Steps to reproduce it:  Sometimes it happens and not have relevant logs.
Hue version: hue-4.9 or hue-4.10, use docker image from docker-hub, run on k8s

This sounds like https://github.com/cloudera/hue/pull/1580

@jojodaser @romainr I am facing same issue with Trino ? Is there any resolution for this ?

@Harshg999 any thoughts on this , looks like its critical bug

Hi @sbbagal13, @jojodaser
We've made some change to the Hue code to better support Trino. Could you please try the latest version of Hue and let us know if you encounter the same issue? Your feedback is valuable. Thank you for reporting the issue.

repo: cloudera/hue


text:
Add error handling

The style of error handling was inspired by https://michael-f-bryan.github.io/rust-ffi-guide/errors/index.html it holds errors in local thread storage and exposes functions last_error_message and last_error_length to access the messages over FFI. All functions return POSIX style return codes:

null for references
-1 for longs and lengths

There are couple of things to consider:

[ ] making it completely panic free by catching all errors using std::panic::catch_unwind checkout https://doc.rust-lang.org/nomicon/ffi.html#panic-can-be-stopped-at-an-abi-boundary but this seems like an overkill for non safety critical app
[ ] if there is any possibility that some code will ever check the error messages from other thread than the one that resulted in the problem itself?

Closes #3

I guess catch unwinding might be necessary in context of encapsulation/decapsulation if the code might possibly panic there, do you think it is possible?

I guess catch unwinding might be necessary in context of encapsulation/decapsulation if the code might possibly panic there, do you think it is possible?

It doesn't look like there are panics on the code paths we use in the ohttp crate, but it is probably a good thing to catch them just in case.

authors: FlakM chris-wood

repo: cloudflare/app-relay-client-library


text:
Content types for stream and byoip

Leaving out SSL b/c it's such a beast...
Added pcx-content-type metadata to two doc products. Also fixed broken links + separated out the get started sections from the main page.

Howdy @Everlag, since it's taken @zaidf a while to respond and our team is trying to get these pcx-content-type values implemented across developer docs (doesn't affect any visible part of the docs), I went ahead and reverted the restructuring around the Stream homepage.
We can go back and discuss/address that in another PR.

LGTM, thanks for making the changes. Happy to continue discussing the other changes in a separate PR.

repo: cloudflare/cloudflare-docs


text:
Update config.yaml

@kodster28 this is a fix for the style guide reviews to run correctly.

TY!!


text:
Fixing: escaping problem

Hi!
I had problem with escaping these symbols : '  (quote) and $ (dollar sign)
I have read that for escaping quote it is possible to insert another quote, but for me it was not enough. I need to escape using backslash.
So escaping dollar sign was not implemented at all, but package clickhouse_orm finds the sign and try to change it as placeholder, so I needed to add another dollar sign ($$) for escaping.

Thanks!

authors: kislenko-artem vavrusa

repo: cloudflare/sqlalchemy-clickhouse


text:
new Response(readableStream).arrayBuffer() stopped working for streams longer than ~247 bytes at ~2023-08-03 20:44:17 +0000 UTC

From https://discord.com/channels/595317990191398933/1012440514135593083/1136901294196535387

(
This turned out to be a regression in workerd which will affect non-WfP workers too!
See this comment for the root cause and our workaround: https://github.com/cloudflare/workerd/issues/970#issuecomment-1665373143
)
We see a complete failure of certain routes that use WfP without any code changes on our end.
First health check failure: 2023-08-03 20:44:17 +0000 UTC
Last health check failure: 2023-08-04 05:59:04 +0000 UTC (Status 500)
The logs show:
  "exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1691128921644
    }
  ]

some failing routes:
https://rtedge.net/
https://elefunc.com/
(These routes now work after we applied the workaround in https://github.com/cloudflare/workerd/issues/970#issuecomment-1665373143)

const st = { // comp.rt.ht

  fo: ['gzip','deflate'][0],

  id: x => x,

  co: (s, f = st.fo) => { if (s === null || s === undefined) return s;
    const c = new CompressionStream(f);
    const w = c.writable.getWriter();
    /**/  w.write(new TextEncoder().encode(s));
    /**/  w.close();
    return new Response(c.readable).arrayBuffer();
  },

  de: (B, f = st.fo) => { if (B === null || B === undefined) return B;
    const d = new DecompressionStream(f);
    const w = d.writable.getWriter();
    /**/  w.write(B);
    /**/  w.close();
    return new Response(d.readable).arrayBuffer().then(B => new TextDecoder().decode(B)).catch(_ => new TextDecoder().decode(B));
  }

};

we have found the call triggering the regression after your update, it is in our exported fetch when we call:
await st.de(v) where v is an ArrayBuffer instance!
This used to work before 2023-08-03 20:44:17 +0000 UTC and now it does not.

If v.byteLength is 243 or less, decompression succeeds.
If v.byteLength is 247 or more, we now get The script will never generate a response..
Decompression never took more than 50ms in any of our deployed routes. I believe whatever causes the error triggers falsely now.

Here is what regressed!
This used to always work in st.de:
new Response(d.readable).arrayBuffer()

and has stopped working at 2023-08-03 20:44:17 +0000 UTC
with The script will never generate a response. errors,
for ReadableStreams longer than ~247 bytes.
Having GPT4 switch our code to use manual concatenation resolved the issue:
ReadableStream.prototype.arrayBuffer = async function() { return st.ab(this); };

const st = { // comp.rt.ht

  fo: ['gzip','deflate'][0],

  id: x => x,

  ab: async r => {
    const  R  = r.getReader();
    const  C  = []; while (true) { const { done, value } = await R.read(); if (done) break; C.push(value); }
    const  AB = new Uint8Array(C.reduce((a, b) => a + b.length, 0)); let p = 0; for (let c of C) { AB.set(c, p); p += c.length; }
    return AB;
  },

  co: (s, f = st.fo) => { if (s === null || s === undefined) return s;
    const c = new CompressionStream(f);
    const w = c.writable.getWriter();
    /**/  w.write(new TextEncoder().encode(s));
    /**/  w.close();
    return c.readable.arrayBuffer();
  },

  de: (B, f = st.fo) => { if (B === null || B === undefined) return B;
    const d = new DecompressionStream(f);
    const w = d.writable.getWriter();
    w.write(B);
    w.close();
    return d.readable.arrayBuffer().then(B => new TextDecoder().decode(B)).catch(_ => new TextDecoder().decode(B));
  }

};

@CetinSert here's a simple test using response of readable stream:
export const arrayBufferOfReadable = {
  async test() {
    const rs = new ReadableStream({
      type: 'bytes',
      start(controller) {
        const enc = new TextEncoder();
        controller.enqueue(enc.encode('0123456789'.repeat(1000)));
        controller.close();
      }
    });

    const read = await new Response(rs).arrayBuffer();
    assert.equal(10_000, read.byteLength);
  }
}

seems to pass if you add it to streams-test.js. Is there a critical step missing here?

I think I have a reproduce in #974 and revert is up in #973

@mikea – has this been reverted at all workerd deployments globally?

@CetinSert — we are in the process of reverting this change in production and will post here once that is complete.

@CetinSert the revert should be complete by now

@mikea – thank you for the prompt response!
Confirming with global Health Checks over the next 5 hours.
I will update and close the issue here by morning (New York).

Sorry for the summer-slow response!
This is just working flawlessly again.

authors: CetinSert irvinebroque mikea

repo: cloudflare/workerd


text:
🐛 BUG: Wrangler - Failed to get worker definitions TypeError: fetch failed

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
3.1.2
What operating system are you using?
Mac
Describe the Bug
Infrequently and inconsistently, when running wrangler dev I get spammed (hundreds of times) with this error. This seems to be the same issue which was resolved previously in #2959 . I was able to resolve the issue by killing all node processes on my machine, one of which seemed to be stuck and needed a force kill.
[1] ▲ [WARNING] Failed to get worker definitions TypeError: fetch failed
[1]
[1]       at fetch (/Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:16584:17)
[1]       at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[1]       at async getRegisteredWorkers (/Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:126327:22)
[1]       at async getBoundRegisteredWorkers (/Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:126346:29) {
[1]     cause: ConnectTimeoutError: Connect Timeout Error
[1]         at onConnectTimeout (/Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:7185:29)
[1]         at /Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:7141:51
[1]         at Immediate._onImmediate (/Users/josh/repos/projects/digester/node_modules/wrangler/wrangler-dist/cli.js:7173:13)
[1]         at process.processImmediate (node:internal/timers:476:21) {
[1]       code: 'UND_ERR_CONNECT_TIMEOUT'
[1]     }
[1]   }

You should keep this open until the bug is actually fixed, unless it's being tracked elsewhere?

authors: jbmanning threepointone

repo: cloudflare/workers-sdk


text:
🐛 BUG: Analytics Engine writeDataPoint not available locally

Which Cloudflare product(s) does this pertain to?
Other
What version(s) of the tool(s) are you using?
3.14.0 [Wrangler]
What version of Node are you using?
18.18.2
What operating system are you using?
Mac
Describe the Bug
Trying to use Analytics Engine locally via wrangler dev (v3.14.0) but I get the following error:
TypeError
Cannot read properties of undefined (reading 'writeDataPoint')

My wrangler.toml file:
[[analytics_engine_datasets]]
binding = "analyticsEngineDataset"

My code:
env.analyticsEngineDataset.writeDataPoint({
        blobs: [user.city, user.country],
        doubles: [order.amount],
	indexes: [user.id],
});

Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs

Thanks for reporting this! Unfortunately Analytics Engine isn't currently supported in wrangler dev—you can follow https://github.com/cloudflare/miniflare/issues/278 to see progress on it's implementation

authors: cezarsmpio penalosa


text:
🐛 BUG: Uncaught Error: Dynamic require of "node:crypto" is not supported

Which Cloudflare product(s) does this pertain to?
Workers Runtime, Wrangler core
What version(s) of the tool(s) are you using?
wrangler@3.22.3
What version of Node are you using?
v20.2.0
What operating system are you using?
Linux
Describe the Bug
Some time ago, I wrote a Cloudflare worker. Today, I added one small change to it. However, I wasn't able to deploy it because wrangler-cli showed me a message that it is too old and refused to work. After upgrading and spending a couple of hours trying to figure out how I could deploy previously working code with the new tool, I gave up.
Basically, this is my .js file, which I can't deploy:
const crypto = require('crypto');

addEventListener('fetch', async function (event) {
    event.respondWith(main(event.request, event).catch(function (error) {
        const m = crypto_encrypt_aes256('SECRET', JSON.stringify({...error, message: error.message, stack: error.stack}, null, 4));
        return new Response(`Failed\n\n${m.toString('base64')}\n`, {status: 400, 'Content-Type': 'text/plain'});
    }));
});

async function main(request, event)
{
    [...]
}

function crypto_encrypt_aes256(password, data)
{
    const iv = crypto.randomBytes(16);
    const key = crypto.createHash('sha256').update(password).digest();
    const cipher = crypto.createCipheriv('aes-256-ctr', key, iv);
    if (iv.length > 255) {
        throw new Error('iv size is too big');
    }
    return Buffer.concat([Buffer.from([iv.length]), iv, cipher.update(data), cipher.final()]);
}

With the old wrangler-cli I used webpack. How could I do it with the new version of wrangler?
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
 ⛅ wrangler 3.22.3
-------------------
Your worker has access to the following bindings:
- Vars:
  - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Total Upload: 3.72 KiB / gzip: 1.46 KiB

✘ [ERROR] A request to the Cloudflare API (/accounts/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/workers/scripts/xxxxxxxxxxxxxxxxx) failed.

  Uncaught Error: Dynamic require of "node:crypto" is not supported
    at null.<anonymous> (worker.js:7:11)
    at null.<anonymous>
  (file:///xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/src/index.js:1:16)
    at null.<anonymous> (worker.js:78:3)
   [code: 10021]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

It looks like you're trying to use Node's crypto module, which isn't supported by default in the Workers runtime. The best path forward will be to enable Node.js compatibility mode by adding this snippet to your wrangler.toml:
compatibility_flags = [ "nodejs_compat" ]

and modifying your import to be require("node:crypto") instead of require("crypto").

I did all of this. The message I got I put into title.
The solution, which worked for me, is custom build:
wrangler.toml
name = "xxxxxxxxxxx"
main = "build/index.js"
compatibility_date = "2022-07-12"

account_id = "xxxxxxxxxxxxxxx"
workers_dev = true

[build]
command = "npm run build"
# cwd = "build"
# watch_dir = "build"

[vars]
XXXXXXXX = "YYYYYYYYYY"

webpack.config.js
const path = require('path');
const pkg = require('./package.json');
const webpack = require('webpack');

const config = {
    mode: 'production',
    target: 'webworker',
    entry: './src/index.js',
    output: {
        path: path.resolve(__dirname, 'build'),
        filename: 'index.js',
    },
    plugins: [
        new webpack.ProvidePlugin({
            Buffer: ['buffer', 'Buffer'],
        }),
        new webpack.DefinePlugin({
            __NAME__: JSON.stringify(pkg.name),
            __VERSION__: JSON.stringify(pkg.version),
            __COMPILED_AT__: JSON.stringify(new Date()),
        })
    ],
    resolve: {
        fallback: {
            buffer: require.resolve('buffer'),
            crypto: require.resolve('crypto-browserify'),
            stream: require.resolve('stream-browserify'),
        },
    },
    performance: {
        hints: false,
    },
};

module.exports = config;

package.json
{
  "name": "xxxxxxxxxxxxxxx",
  "version": "0.0.0",
  "scripts": {
    "build": "webpack",
    "watch": "wrangler --config=wrangler.dev.toml dev",
    "deploy-dev": "wrangler --config=wrangler.dev.toml deploy",
    "deploy-prod": "wrangler --config=wrangler.prod.toml deploy"
  },
  "devDependencies": {
    "buffer": "^6.0.3",
    "buffer-browserify": "^0.2.5",
    "crypto-browserify": "^3.12.0",
    "stream-browserify": "^3.0.0",
    "webpack": "^5.89.0",
    "webpack-cli": "^5.1.4",
    "wrangler": "^3.22.3"
  }
}

For others experiencing a similar error message, make sure your using 'import' instead of 'require'. Unfortunately many npm packages still use the 'require' format.

I'm experiencing this as well but the require statement is in the remix package so I am not able to change that. Any suggestions?
Specifically /node_modules/@remix-run/node/dist/sessions/fileStorage.js on remix v2.7.2

I'm facing the same issue. I've added compatibility_flags = [ "nodejs_compat" ] to wrangler.toml, following the instructions on https://developers.cloudflare.com/workers/runtime-apis/nodejs with import { Crypto } from 'node:crypto'; and I get exactly that error as well locally. So either something's still not supported here or the docs are wrong - or I don't get it.

Trying to deploy a remix-run app to cloudflare with @remix-run/cloudflare also brought me to this thread

Hit this issue today. I'm guessing the exact reason has to do with the file to bundle.

For me this happened with a ESM file containing require('crypto').
Wrangler (and maybe esbuild in it) emits this which apparently fails without a real require in runtime:
var __require = /* @__PURE__ */ ((x) => typeof require !== "undefined" ? require : typeof Proxy !== "undefined" ? new Proxy(x, {
  get: (a, b) => (typeof require !== "undefined" ? require : a)[b]
}) : x)(function(x) {
  if (typeof require !== "undefined")
    return require.apply(this, arguments);
  throw new Error('Dynamic require of "' + x + '" is not supported');
});

...

var crypto = __require2("crypto"); // FAIL

If the input file contains import 'crypto' instead, wrangler emits fine code that imports from polyfilled crypto.
IMO wrangler could do better to either support this imperfect input (this is not rare, not every npm packages ships perfect ESM). At least the error message could be improved.

@jokester what error do you see when you use Wrangler v3.80.0 (https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.80.0)
See: https://github.com/cloudflare/workers-sdk/pull/6872

@irvinebroque Thanks. I tested with wrangler 3.80.0 and realized my previous report could be invalid (the input to wrangler was already a dynamic require).
Wrangler 3.80.0 has no problem recognizing non-dynamic requires like require('node:crypto') , and provide them with polyfills.

authors: NeilWkz delphian irvinebroque jokester mmiondev penalosa sattes-faction vbarbarosh


text:
fix(playground-preview-worker): ensure OPTIONS raw HTTP requests are fowarded

Fixes DEVX-1449.
This PR fixes an issue in which the preview worker does not receive an raw OPTIONS request on both Quick Editor or Workers Playground.

Tests

[ ] TODO (before merge)
[x] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[x] Not required because: no impact to wrangler

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: bugfix

Superseded by #7630


text:
npm 1.10.2 release "bad tar archive"

CI to create release failed because we made a release before CI created one for us. thought we could get around easily by downloading the artifacts created by CI and just putting them in the release, but got an issue w/npm saying it's a bad tar. re-running CI right now to fix this.

fixed!

repo: cloudflare/wrangler


text:
markup on npmjs page renders less than great

https://www.npmjs.com/package/@cloudflare/wrangler

I think this is due to the README being formatted a bit weirdly, we have a bullet list of headings. Should probably just remove the bulleted list and have headers

this appears to have been solved.


text:
502 during compilation phase

We got following error on two different deployments.
Error: CPI error 'Bosh::Clouds::CloudError' with message 'Creating vm: Failed to find Google Image 'stemcell-6ac2b2a0-6086-4de6-78e8-9a645045166f': Get https://www.googleapis.com/compute/v1/projects/cf-pcf-kubo/global/images/stemcell-6ac2b2a0-6086-4de6-78e8-9a645045166f?alt=json: oauth2: cannot fetch token: 502 Bad Gateway
Response: <!DOCTYPE html>

  <meta charset=utf-8>
  <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
  <title>Error 502 (Server Error)!!1</title>

502. That’s an error.

The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.  That’s all we know.
' in 'create_vm' CPI method

Can you provide the CPI version and a repro?

close due to age and a hunch this env is long gone :)

authors: alex-slynko johnsonj


text:
Feature request - pre-stop

Currently we have to do some very elaborate bash scripting to make sure we can trap signals and coordinate with other jobs on the VM in uaa-release.
It would be nice if BPM provided a pre-stop hook.
The UAA, runs as a Java web application on a servlet container. Today we don't have a way to intercept signals in the Java process before the container, Apache Tomcat, starts shutting down.
This feature request may become obsolete once we move to Spring Boot, where we could control the shutdown sequence ourselves.

@fhanik bin/drain doesnt help?

@fhanik we've been chewing on this for a bit and I don't think we'll be adding a pre-stop hook. hopefully the Spring Boot update will resolve this in the long run, or perhaps @cppforlife's suggestion of using drain work for you all. Going to close this out.

authors: aramprice cppforlife fhanik

repo: cloudfoundry-incubator/bpm-release


text:
Uploading stemcell timeout error

In my cloud account, uploading of stemcell takes around 7 minute. But code allows only for 5 minute and throws timeout error.
creating stemcell (bosh-openstack-kvm-ubuntu-trusty-go_agent 3445.7):
CPI 'create_stemcell' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Timed out waiting for Image `24316d83-d90d-4643-9ef5-736e1decb15a' to be active","ok_to_retry":false}
Is there any way I can change the default timeout value.
Thanks,

@vinayakbhat24 This error occurred on the GCP CPI side, and that particular timeout does not seem to be configurable. You can try one of the following:

retry the same upload - it might just work
replace the stemcell URL with the light one - URL: https://s3.amazonaws.com/bosh-gce-light-stemcells/light-bosh-stemcell-3445.7-google-kvm-ubuntu-trusty-go_agent.tgz, SHA1: 4bc264aab6717c81fb3a37783e796982fe9956ca

@jhvhs Thanks for hinting me at file openstack/cpi.yml.  Even I can change default timeout value using this file.
Thanks,

repo: cloudfoundry-incubator/kubo-deployment


text:
v0.2.0 fails to export packages

https://ci2.starkandwayne.com/teams/cfcommunity/pipelines/cfcr-compiled-deployment/jobs/bosh-dns-compile-release-3541/builds/2 - I'm trying to generate a compiled release of bosh-dns v0.2.0 (version used by CFCR) but it fails ... I think because its compiling a Windows package?
I did not get this issue when I first exported v1.4.0 so perhaps the issue is fixed; but I'd like a version of 0.2.X that matches to what cfcr.yml expects, please?

@drnic we probably put in a windows hack in later versions. 0.2.x is super old, they should bump or just rely on runtime config adding bosh-dns (preferred).

"rely on runtime config" - that still uses this boshrelease right, just injected via runtime-config rather than an addon within the deployment manifest?
Does cf-deployment currently assume bosh-dns is always enabled for its cf-deployment.yml?

@cloudoundry-incubator/kubo-deployment are you bumping to latest bosh-dns release soon?

"rely on runtime config" - that still uses this boshrelease, just injected it via runtime-config rather than an addon within the deployment manifest?

https://github.com/cloudfoundry/bosh-deployment/blob/master/runtime-configs/dns.yml

Does cf-deployment currently assume bosh-dns is always enabled for its cf-deployment.yml?

dont think so, but one could exclude certain deployments in runtime configs.

@drnic no plans to fix this for 0.2.x. closing.

authors: cppforlife drnic

repo: cloudfoundry/bosh-dns-release


text:
Fix for enabling XFS on ubuntu trusty stem cells on Google KVM

https://github.com/cloudfoundry/bosh/issues/1722
This issue is currently blocking multiple users from installing XFS filesystems on Ubuntu Trusty stem cells on Google Cloud VMs.
The only workaround for this has been to use persistent disks greater than 2TB. This solution might not be workable for all cases.
This change will make parted as the default FS partitioner on trusty images on Google Cloud.

Ran the below test on the image:
cd /opt/bosh/bosh-stemcell;
STEMCELL_IMAGE=/mnt/stemcells/google/kvm/ubuntu/work/work/google-kvm-ubuntu.raw
STEMCELL_WORKDIR=/mnt/stemcells/google/kvm/ubuntu/work/work/chroot
OS_NAME=ubuntu
bundle exec rspec -fd --tag ~exclude_on_google
spec/os_image/ubuntu_trusty_spec.rb
spec/stemcells/ubuntu_trusty_spec.rb
spec/stemcells/go_agent_spec.rb
spec/stemcells/google_spec.rb
spec/stemcells/stig_spec.rb
spec/stemcells/cis_spec.rb > test_results.log
test_results.log

@babupe-g we dont quite want to enable it for everyone. at the stemcell level configuration is global unfortunately.
i've added https://www.pivotaltracker.com/story/show/156732961 to provide a runtime option for the agent. we'll try to do it shortly, but if you want to tackle it first, let us know.

authors: babupe-g cppforlife


text:
Undeclared dependency on Spiff

Running bin/provision_cf produces this error, and an empty cf-manifest.yml:
/Users/pivotal/workspace/cf-release/generate_deployment_manifest: line 17: spiff: command not found
Incorrect YAML structure in `/Users/pivotal/workspace/bosh-lite/manifests/cf-manifest.yml': expected Hash at the root

This was trivially overcome via the README from the spiff repository
brew tap xoebus/homebrew-cloudfoundry
brew install spiff

@cppforlife would be cool if "provide_cf" script will fail if spiff is not found. I spent 1 hour trying to figure out why it's failing with "you must select deployment first" instead of informative "spiff not found" :)

authors: bsideup quavmo

repo: cloudfoundry/bosh-lite


text:
DNS is missing in vm after deleted bosh VM resurrects

I have cloud foundry deployment .I have 3 kafka,3 zookeper and 3- vault/consul instance.
kafka/0 10.20.0.174
zookeeper/2 10.20.0.242
vault_consul/0 10.20.0.247

For testing purpose i delete one of the vm from each .All the vm's are resurrecting and these vm's have new IP now,but dns is missing in them.
bosh vms output is as follows
 kafka/0             | running | service-net-medium | 10.20.0.251 | n/a  |
 zookeeper/2      | running | service-net-medium | 10.20.0.250 | n/a  |
 vault_consul/0   | failing |   small | 10.20.0.25 | n/a

On Analysing the Microbosh DB I found dns name are still mapped with old ip.
Microbosh PostgresDB output
./psql bosh -c "select id, name, type, content from records;"
46 | 0.kafka.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.174
47 | 174.0.20.10.in-addr.arpa | PTR | 0.kafka.ccc-service-net.cf-devtest21vik.microbosh
28 | 2.zookeeper.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.242
29 | 242.0.20.10.in-addr.arpa | PTR | 2.zookeeper.ccc-service-net.cf-devtest21vik.microbosh
67 | 0.vault-consul.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.247
70 | 247.0.20.10.in-addr.arpa | PTR | 0.vault-consul.ccc-service-net.cf-devtest21vik.microbosh

Microbosh manifest file
<% load 'micro01/micro_bosh.rb' %>
name: <%= $os_tenant %>
logging: level: DEBUG
network: type: manual
ip: <%= $ip_address %>
cloud_properties: name: ccc-bosh-net
net_id: <%= $net_id %>
resources: persistent_disk: 50000
cloud_properties: instance_type: <%= $bosh_flavor %> disk: 16384  cloud: plugin: openstack properties: openstack: auth_url: <%= $os_auth_url %> username: <%= $os_username %> api_key: <%= $os_password %> tenant: <%= $os_tenant %> default_security_groups: [vms-security-group] default_key_name: <%= $key_name %> private_key: <%= $key_file %> ignore_server_availability_zone: true
apply_spec:
properties: director:
max_threads: 32 hm:
resurrector_enabled: true
director_account: user: <%= $bosh_username %>
password: <%= $bosh_password %>
ntp: - <%= $ntp1 %> - <%= $ntp2 %>
dns:
recursor: 8.8.8.8 env: bosh: password: <%= $sha_password %>
Is is possible for VM to have same ip if not at least it should update it MIcrobosh DM.Let me know   how to achieve  this.
Is there any config missing in this. Help me to resolve this issue.

which version of bosh are you using (bosh status output)?
Sent from my iPhone

On May 25, 2016, at 10:25 AM, chrisrana notifications@github.com wrote:
I have cloud foundry deployment .I have 3 kafka,3 zookeper and 3- vault/consul instance.
kafka/0 10.20.0.174
zookeeper/2 10.20.0.242
vault_consul/0 10.20.0.247
For testing purpose i delete one of the vm from each .All the vm's are resurrecting and these vm's have new IP now,but dns is missing in them.
bosh vms output is as follows
kafka/0             | running | service-net-medium | 10.20.0.251 | n/a  |
zookeeper/2      | running | service-net-medium | 10.20.0.250 | n/a  |
vault_consul/0   | failing |   small | 10.20.0.25 | n/a
On Analysing the Microbosh DB I found dns name are still mapped with old ip.
Microbosh PostgresDB output
./psql bosh -c "select id, name, type, content from records;"
46 | 0.kafka.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.174
47 | 174.0.20.10.in-addr.arpa | PTR | 0.kafka.ccc-service-net.cf-devtest21vik.microbosh
28 | 2.zookeeper.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.242
29 | 242.0.20.10.in-addr.arpa | PTR | 2.zookeeper.ccc-service-net.cf-devtest21vik.microbosh
67 | 0.vault-consul.ccc-service-net.cf-devtest21vik.microbosh | A | 10.20.0.247
70 | 247.0.20.10.in-addr.arpa | PTR | 0.vault-consul.ccc-service-net.cf-devtest21vik.microbosh
Microbosh manifest file
<% load 'micro01/micro_bosh.rb' %>
name: <%= $os_tenant %>
logging: level: DEBUG
network: type: manual
ip: <%= $ip_address %>
cloud_properties: name: ccc-bosh-net
net_id: <%= $net_id %>
resources: persistent_disk: 50000
cloud_properties: instance_type: <%= $bosh_flavor %> disk: 16384 cloud: plugin: openstack properties: openstack: auth_url: <%= $os_auth_url %> username: <%= $os_username %> api_key: <%= $os_password %> tenant: <%= $os_tenant %> default_security_groups: [vms-security-group] default_key_name: <%= $key_name %> private_key: <%= $key_file %> ignore_server_availability_zone: true
apply_spec:
properties: director:
max_threads: 32 hm:
resurrector_enabled: true
director_account: user: <%= $bosh_username %>
password: <%= $bosh_password %>
ntp: - <%= $ntp1 %> - <%= $ntp2 %>
dns:
recursor: 8.8.8.8 env: bosh: password: <%= $sha_password %>
Is is possible for VM to have same ip if not at least it should update it MIcrobosh DM.Let me know how to achieve this.
Is there any config missing in this. Help me to resolve this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

bosh --version
BOSH 1.3071.0

root@dev-inception-vm21:/home/ubuntu# bosh status
Config
/root/.bosh_config
Director
Name       installdev2
URL        https://10.20.0.55:25555
Version    1.3155.0 (00000000)
User       admin
UUID       3dc7bb73-4fa6-4c83-ab33-e9c870861e05
CPI        openstack
dns        enabled (domain_name: microbosh)
compiled_package_cache disabled
snapshots  disabled
Deployment
Manifest   /opt/installer/tenant-devtest21vik/cf-deploy/cf-devtest21vik.yml
root@dev-inception-vm21:/home/ubuntu#

ah older version. since that version we have fixed several issues with how we track dns records in the director. i would recommend updating your director to the latest version to get those dns fixes.
Sent from my iPhone

On May 25, 2016, at 11:06 AM, chrisrana notifications@github.com wrote:
bosh --version
BOSH 1.3071.0
root@dev-inception-vm21:/home/ubuntu# bosh status
Config
/root/.bosh_config
Director
Name installdev2
URL https://10.20.0.55:25555
Version 1.3155.0 (00000000)
User admin
UUID 3dc7bb73-4fa6-4c83-ab33-e9c870861e05
CPI openstack
dns enabled (domain_name: microbosh)
compiled_package_cache disabled
snapshots disabled
Deployment
Manifest /opt/installer/tenant-devtest21vik/cf-deploy/cf-devtest21vik.yml
root@dev-inception-vm21:/home/ubuntu#
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

What is the latest version of bosh cli .which one I should use

to clarify you should update your director not the cli to the latest version. though you should also update your cli while you are updating.
see https://bosh.io for the latest versions of bosh release.
Sent from my iPhone

On May 25, 2016, at 11:17 AM, chrisrana notifications@github.com wrote:
What is the latest version of bosh cli .which one I should use
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

@cppforlife, this story was about this issue as well, but sounds like it can be closed as fixed elsewhere?

Bosh director means stemcell version is it ?

@chrisrana, you can try using bosh_cli/1.3232.0 and director/256.2. DNS fixes are mostly director related, but would still recommend using the latest stemcell, currently 3232.4.

I forgot mention I use MicroBosh for deployment because it is Single VM director.

I see. The bosh micro deployment method is deprecated and will be discontinued soon. I'd recommend migrate to bosh-init and upgrade your versions. If you need microbosh, you can still use your current procedure, just bump STEMCELL_VERSION.

Closing - please migrate to bosh-init and update your director release to ensure you have the latest fixes to DNS related issues which may have come up earlier.

repo: cloudfoundry/bosh


text:
cf login -h formatting is missing a newline char within the EXAMPLE section

Notice the missing newline after the fourth example.
{current}  cf login -h output
[....]
EXAMPLE:
cf login (omit username and password to login interactively -- cf will prompt for both)
cf login -u name@example.com -p pa55woRD (specify username and password as arguments)
cf login -u name@example.com -p "my password" (use quotes for passwords with a space)
cf login -u name@example.com -p ""password"" (escape quotes if used in password)   cf login --sso (cf will provide a url to obtain a one-time password to login)
[....]
{desired} cf login -h output
[....]
EXAMPLE:
cf login (omit username and password to login interactively -- cf will prompt for both)
cf login -u name@example.com -p pa55woRD (specify username and password as arguments)
cf login -u name@example.com -p "my password" (use quotes for passwords with a space)
cf login -u name@example.com -p ""password"" (escape quotes if used in password)
cf login --sso (cf will provide a url to obtain a one-time password to login)
[....]

Thanks, we will be fixed for next release.

repo: cloudfoundry/cli


text:
It failed to search by using the filter with GB18030 characters in Services and Applications view.

Stratos Version

4.4.0
Frontend Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] npm run start
[ ] Other (please specify below)

Backend (Jet Stream) Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] Other (please specify below)

Expected behaviour
Can use the filter with GB18030 characters to search in Service.
Actual behaviour
It failed to search by using the filter with GB18030 characters in Service.
Steps to reproduce the behavior

Create a User Provided Servce and input the name with GB18030 characters, for example: 'TrafficServive€酮خد㐁ᠡꀈ༑㘚郂'

In Search by name, type 'traffic' to search
Got an entry, so this service can be found successfully.
In Search by name, copy GB18030 characters  '€酮خد㐁ᠡꀈ༑㘚郂' to search,

Cannot locate the correct service.

Log output covering before error and any error statements
Insert log hereCopy

In step3, use English characters to search, it can get the returned entry.

Note:
After the step4,  English characters will be also failed to search. You need to refresh the web page to continue English characters search.

Detailed Description

Context

Possible Implementation

@xudaniel@ca.ibm.com , @doloresl@us.ibm.com  Could you help to assign it to the related developer for fixing？ Thanks！

The issue is also reproduced in Applications view. Please help to fix together. Thanks!

Created an internal git issue: https://github.ibm.com/CFMigrationRuntime/todo_issues/issues/215 to help devs track the issue

authors: XiaojuanChen xudaniel

repo: cloudfoundry/stratos


text:
Allow backup/restore plugin to be enabled/disabled

Might want to do this for a desktop version

Codecov Report

Merging #4818 (ed42501) into master (41191b3) will decrease coverage by 26.15%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #4818       +/-   ##
===========================================
- Coverage   53.77%   27.62%   -26.16%
===========================================
  Files        1122       59     -1063
  Lines       38799     4623    -34176
  Branches     4932        0     -4932
===========================================
- Hits        20866     1277    -19589
+ Misses      17755     3168    -14587
  Partials      178      178

authors: codecov-io nwmac


text:
Authorization Code Grant Browser flow requires undocumented authorization header

Authorization Code Grant (Browser Flow) doesn't specify any Authorization header requirement, either in the text (there are no Request headers mentioned) or in the example (which only has Host and Accept headers).
If issuing a request with the example form (without an Auth header) the correct response 302 Found is returned and a Location header appears in the response, but this doesn't have a "code" query parameter on it:
HTTP/1.1 302 Found..
Cache-Control: no-cache, no-store, max-age=0, must-revalidate..
Content-Length: 0..
Date: Fri, 17 Jun 2016 12:26:05 GMT..
Expires: 0..
Location: https://uaa.local.pcfdev.io/login..
Pragma: no-cache..
Server: Apache-Coyote/1.1..
Set-Cookie: __VCAP_ID__=647a7f59-5b32-4a0d-6266-f460c798ec06; Path=/; HttpOnly; Secure..
Set-Cookie: JSESSIONID=065E4F67B2F3BF7587426FE92A49C3DD; Path=/; Secure; HttpOnly..
Strict-Transport-Security: max-age=31536000 ; includeSubDomains..
X-Content-Type-Options: nosniff..
X-Frame-Options: DENY..
X-Vcap-Request-Id: fb820273-21af-4cd3-7661-eb4e5f7a2187..
X-Xss-Protection: 1; mode=block..
..

This does not correspond to the example flow given on the doc page.
If an Authorization header (bearer token) is attached to the request, then all is well and we get this response:
HTTP/1.1 302 Found..
Cache-Control: no-store..
Content-Language: en-US..
Content-Length: 0..
Date: Fri, 17 Jun 2016 12:37:41 GMT..
Expires: 0..
Location: https://uaa.local.pcfdev.io/login?code=p32gEa..
Pragma: ..
Server: Apache-Coyote/1.1..
Strict-Transport-Security: max-age=31536000 ; includeSubDomains..
X-Content-Type-Options: nosniff..
X-Frame-Options: DENY..
X-Vcap-Request-Id: 1f80f276-b2a5-413e-7fe0-ee4dc48de023..
X-Xss-Protection: 1; mode=block..
..

(both of these requests omit a redirectUrl).
Please update the doc to specify the correct form of this request, and response.
PS: The response_type field description is prefixed with the word either, but appears to allow only the value "code". Can this be corrected too, please?

The presence of the Authorization header creates a non browser flow.
Here is the documentation link:
http://docs.cloudfoundry.org/api/uaa/index.html#browser-flow

If I omit the header I don't get a code back (as per the example flow in the docs); I posted what I get back above. The doc you linked me to is what I've been trying to get to work. What am I missing?

By the way, the doc is unclear what it is exactly that characterizes each request.  If it is the absence of an Authorization header, it would be helpful if the doc made that clear.  The Token requests are particularly confusing in this regard.

I can't get this request to work as documented.
I issue the request:
GET /oauth/authorize?client_id=ssh-proxy&redirect_uri=http://redirect.to/app&response_type=code HTTP/1.1..
host: uaa.local.pcfdev.io..
Accept: application/x-www-form-urlencoded..

and I receive the response:
HTTP/1.1 302 Found..
Cache-Control: no-cache, no-store, max-age=0, must-revalidate..
Content-Length: 0..
Date: Mon, 20 Jun 2016 12:07:36 GMT..
Expires: 0..
Location: https://uaa.local.pcfdev.io/login..
Pragma: no-cache..
Server: Apache-Coyote/1.1..
Set-Cookie: __VCAP_ID__=9c7d0536-3054-4faf-6809-31d6cf235b47; Path=/; HttpOnly; Secure..
Set-Cookie: JSESSIONID=1D6C44B10328696435AE7C7F947594CD; Path=/; Secure; HttpOnly..
Strict-Transport-Security: max-age=31536000 ; includeSubDomains..
X-Content-Type-Options: nosniff..
X-Frame-Options: DENY..
X-Vcap-Request-Id: d620ccc6-0802-4d72-7a31-98e575918bce..
X-Xss-Protection: 1; mode=block..

in which the Location header doesn't include a code=<value> query parameter. Also it seems to ignore the redirect_uri on the request.

It works as documented.
The user (browser) is being redirected to the login page for authentication. When authentication is complete, you will get a 302 redirect, with a Location header that contains the code.

Having gone to ask a friend I now understand the intended flow, but the documentation is incorrect.  The example response shows a 302 redirect with an authorization code (and the supplied redirect uri) in the location header.  This is not what is returned from the GET request.
Completing the authentication requires further interactions which are not the subject of this REST request.
I have updated the initial description of the problem.

authors: Zteve fhanik

repo: cloudfoundry/uaa


text:
[Bug]: replica cluster switchover doesn't work when only object store replication is configured

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
sujit21agarwal@gmail.com
Version
1.23.1
What version of Kubernetes are you using?
1.27
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
YAML manifest
What happened?
I have created 2 cluster Primary and Replica.Replica cluster is created from object storage s3.
I have inserted data into primary cluster and data is successfully  replicated into the Replica Cluster.After that I followed below steps,

Updating the Primary Cluster  by making
replica:
enabled: true
Updating the Replica Cluster by making
replica:
enabled: false.

I can see the status is changed from  Designated primary to Primary for replica cluster and also vice versa.
The issue which I am facing , when I inserted the data into new primary , data is not replicating into the replica cluster.
Cluster resource
----Primary Cluster---

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name:  primary-cluster-example
  namespace: primary
spec:
  instances: 2
  storage:
    size: 1Gi
  enableSuperuserAccess: true
  superuserSecret:
    name: superuser-secret
  backup:
    barmanObjectStore:
      destinationPath: s3://backup/primary/
      endpointURL: http://seaweedfs-s3.locals3.svc.cluster.local:8333
      s3Credentials:
        accessKeyId:
          name: primary-cluster-example-secret-s3
          key: ACCESS_KEY_ID
        secretAccessKey:
          name: primary-cluster-example-secret-s3
          key: ACCESS_SECRET_KEY
      wal:
        compression: gzip
        encryption: AES256
        maxParallel: 8

  replica:
    enabled: false
    source: secondary-cluster-example

  externalClusters:
    - name: secondary-cluster-example
      barmanObjectStore:
        destinationPath: s3://backup/secondary/
        endpointURL: http://seaweedfs-s3.locals3.svc.cluster.local:8333
        s3Credentials:
          accessKeyId:
            name: primary-cluster-example-secret-s3
            key: ACCESS_KEY_ID
          secretAccessKey:
            name: primary-cluster-example-secret-s3
            key: ACCESS_SECRET_KEY

--Replica Cluster--------------------

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name:  secondary-cluster-example
  namespace: secondary
spec:
  instances: 2
  storage:
    size: 1Gi
  enableSuperuserAccess: true
  superuserSecret:
    name: superuser-secret
  backup:
    barmanObjectStore:
      destinationPath: s3://backup/secondary/
      endpointURL: http://seaweedfs-s3.locals3.svc.cluster.local:8333
      s3Credentials:
        accessKeyId:
          name: secondary-cluster-example-secret-s3
          key: ACCESS_KEY_ID
        secretAccessKey:
          name: secondary-cluster-example-secret-s3
          key: ACCESS_SECRET_KEY
      wal:
        compression: gzip
        encryption: AES256
        maxParallel: 8

  replica:
    enabled: true
    source: primary-cluster-example

  bootstrap:
    recovery:
      source: primary-cluster-example

  externalClusters:
    - name: primary-cluster-example
      barmanObjectStore:
        destinationPath: s3://backup/primary/
        endpointURL: http://seaweedfs-s3.locals3.svc.cluster.local:8333
        s3Credentials:
          accessKeyId:
            name: secondary-cluster-example-secret-s3
            key: ACCESS_KEY_ID
          secretAccessKey:
            name: secondary-cluster-example-secret-s3
            key: ACCESS_SECRET_KEY

Relevant log output
no such logs I can see.

Code of Conduct

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

Hi @sujitkagarwal. Unfortunately, the demotion doesn't work at the moment when you are only using the object store to feed the replica cluster. This behavior is due to how PostgreSQL archives the last wal during the shutdown; see https://github.com/cloudnative-pg/cloudnative-pg/issues/4586 for the details. We are working on a fix.

@mnencia  Do you know when new version will be released 1.24 with partial fix

Jul 16 - see: https://github.com/cloudnative-pg/cloudnative-pg/milestone/22

authors: gbartolini mnencia sujitkagarwal

repo: cloudnative-pg/cloudnative-pg


text:
fix: timeouts for restarts and switchovers

This patch fix the timeouts that we were using during a restart and
during switchovers to use the right fields in the Cluster specification.
Closes #530
Signed-off-by: Leonardo Cecchi leonardo.cecchi@enterprisedb.com

This patch needs to be backported

/test

What about adding some unit tests that make sure that inside "tryShuttingDownSmartFast" the default delay that is passed matches stopDelay's value and that in "tryShuttingDownFastImmediate" it is switchoverDelay's value? @leonardoce @armru
@mnencia would you please look at this patch as well and approve it?

/ok-to-merge

authors: gbartolini leonardoce sxd


text:
chore: improve operator deployment security

After running trivy to diagnose the operator deployment we found a couple
of security issues fixed here:

securityContext.capabilities.drop: ALL
securityContext.runAsNonRoot: true
securityContext.runAsUser: 10001
securityContext.runAsGroup: 10001
securityContext.seccompProfile.type: RuntimeDefault

All of these issues are fixed in the manager deployment and will not affect
the code itself.
Closes #541
Signed-off-by: Jonathan Gonzalez V jonathan.gonzalez@enterprisedb.com

/ready-to-test

/test

/ok-to-merge

authors: phisco sxd


text:
SECURITY: iam:PassRole is dangerous

Describe the Bug
The inline policy *-eb-default in main.tf line 138 is generally overreaching with all of it's permissions, but in particular Action: ["iam:PassRole"] with Resource: "*" is downright dangerous.  See Unit 42 Cloud Threat Report: Misconfigured IAM Roles Lead to Thousands of Compromised Cloud Workloads for details on how to exploit.
Expected Behavior
Privilege escalation should not be possible.  iam:PassRole (and iam:ListRole) should not be used.

@razorsedge what do you think is the best approach? Add inputs to specify a resource pattern for each class of permissions, or make the module more opinionated and specify the resource pattern using the module context?

@joe-niland My naive approach would be to completely remove those two actions.  I do not understand why they would be needed.
Otherwise, forcing a user to specify the role to be passed else not allow that action.

Closed via #215

authors: joe-niland razorsedge


text:
Add user_name to examples

user_name is a required input.

/test all

Thanks for the small addition @yi2020!

repo: cloudposse/terraform-aws-iam-user


text:
add support for custom config and additional users

what

Add support for custom MQ configuration
Add support for setting up additional MQ users

why

Custom MQ configuration was needed for the project
Additional users were needed for the project

Full backward compatibility. Nothing will change if variables mq_additional_users or mq_configuration are undefined.

Any chance to move this forward? We are also needing custom configurations

/terratest

authors: hans-d jseiser kbcz1989

repo: cloudposse/terraform-aws-mq-broker


text:
Bugfix

what && why

Require AWS provider v4.9.0 or later, resolves #137
Properly consider source_policy_documents input, fixes #145

notes
This will become version 2.0

/test all


text:
Add git push proposed run test

what

Add git push proposed run test
Explicitly added a *.rego space policy

why

This is a large policy and it should be tested if any new changes are introduced
Consistency
100% coverage of git_push.proposed-run.rego

references

N/A

$ opa test git_push.proposed-run.rego git_push.proposed-run_test.rego -v
git_push.proposed-run_test.rego:
data.spacelift.test_propose_project_root_affected: PASS (790.886µs)
data.spacelift.test_propose_stack_config_affected_imports_label: PASS (404.527µs)
data.spacelift.test_propose_stack_config_affected_deps_label: PASS (586.646µs)
data.spacelift.test_propose_stack_config_affected_stack_name_root_stack: PASS (419.415µs)
data.spacelift.test_propose_stack_config_affected_stack_stack_label: PASS (437.601µs)
data.spacelift.test_ignore_ready_to_review_with_spacelift_no_trigger_label: PASS (120.209µs)
data.spacelift.test_not_ignore_ready_to_review_without_any_labels: PASS (109.905µs)
data.spacelift.test_not_ignore_draft_with_spacelift_trigger_label: PASS (134.81µs)
data.spacelift.test_ignore_draft_without_any_labels: PASS (551.992µs)
data.spacelift.test_cancel_runs: PASS (337.658µs)
data.spacelift.test_not_cancel_runs: PASS (128.507µs)
--------------------------------------------------------------------------------
PASS: 11/11
$ opa test git_push.proposed-run.rego git_push.proposed-run_test.rego -v -c | jq .coverage
100

/test test/bats

/test test/readme

/test test/bats

/test test/readme


text:
Avoid emitting probe metrics after context cancellation

When a probe is stopped, i.e. via the probe removal process, sometimes the cancellation of the probe context happens while a probe run is in progress. This can cause that probe run to be interrupted mid-execution and return with a failure, which then gets reported through the metrics channel and out to the surfacer as a failed probe, even though the failure was due to probe cancellation rather than an external cause.
This PR adds a check to make sure the context is still live after the probe run is completed but before metrics are emitted. If the context is done, the probe stops without emitting the metrics.
Probe types and their susceptibilities for this issue:

dns

dns does not have the issue because the probe run is not interrupted by context closure

external (non-server)

this does have the issue if the context closes during the process execution as that will forcefully kill the process and result in a failure

external (server)

this does not have the issue because the metrics reporting is bounded by the context, and because process failures are not emitted as event metrics

grpc

this does not have the issue as metrics are emitted on the next loop after running probes, which involves checking the context again. Individual target cancellations are also handled because all target removals delete the probe result before the next metrics emission cycle runs.

http

has this issue, is fixed in the PR. Canceled context can lead to failures.

ping

ping does not have this issue as the inner probe runner does not respect context closure

tcp

tcp uses the sched utility to run probes, which is susceptible to this failure. sched has been updated in the same way as http

udp

udp doesn't have the issue because context cancellation will immediately stop the function that does metrics exporting

udp listener

udp listener doesn't have the issue because context cancellation will immediately stop the function that does metrics exporting

@AdamEAnderson Thanks for this PR. I think it makes sense. I added a few comments.

Hi @AdamEAnderson, just wanted to check if you want to follow up on this PR.

authors: AdamEAnderson manugarg

repo: cloudprober/cloudprober


text:
Update Yoga constraints

Update references to the branch previously known asstable/yoga to unmaintained/yoga

LGTM

authors: gaudenz urscale

repo: cloudscale-ch/octavia


text:
GSD Request

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

This issue has been assigned GSD-2021-1002447

repo: cloudsecurityalliance/gsd-database


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.6 to before v5.12.10",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=59438b46471ae6cdfb761afc8c9beaf1e428a331",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=acc43fc6cf0d50612193813c5906a1ab9d433e1e"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "59438b46471ae6cdfb761afc8c9beaf1e428a331",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "acc43fc6cf0d50612193813c5906a1ab9d433e1e",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "bpf, lockdown, audit: Fix buggy SELinux lockdown permission checks\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.12.10 by commit acc43fc6cf0d50612193813c5906a1ab9d433e1e, it was introduced in version v5.6 by commit 59438b46471ae6cdfb761afc8c9beaf1e428a331. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000799

repo: cloudsecurityalliance/security-database


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.17 to before v4.14.237",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=31434f496abb9f3410b10f541462fe58613dd3ad",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=634f17ff1d59905eb3b4bbbc00805961d08beaee"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "31434f496abb9f3410b10f541462fe58613dd3ad",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "634f17ff1d59905eb3b4bbbc00805961d08beaee",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "NFS: Fix a potential NULL dereference in nfs_get_client()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.237 by commit 634f17ff1d59905eb3b4bbbc00805961d08beaee, it was introduced in version v3.17 by commit 31434f496abb9f3410b10f541462fe58613dd3ad. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000864


text:
SDK version

firstly thanks for the great lib, i just got a quick question,
will this build on the stable flutty sdk channel
or is it strictly on dev channel
thanks

Did you try stable?

Did you try stable?

no i haven't tried

@jason-shen Using stable will only work on mobile, dev channel supports macos and web

authors: cloudwebrtc ghenry jason-shen

repo: cloudwebrtc/dart-sip-ua


text:
docs: add kitex grpc metadata docs

What type of PR is this?
docs
What this PR does / why we need it (en: English/zh: Chinese):
en: add kitex grpc metadata docs
zh: 添加 kitex grpc metadata 使用文档
Which issue(s) this PR fixes:

LGTM

authors: HeyJavaBean li-jin-gou


text:
请问下关于mongodb中update方法如何使用

不清楚update的规范该如何写。

    local ret = client.test.test:update(
        {
            name = 3
        },
        {
            ["$set"] = {
                asdf = 11
            }
        }, true, true
    )

我这样写好像没办法更新到数据库

like this:
db.DocName:update(
{_id = roleId},
{["$set"] = {guessInfo = data}},
{upsert = true}
)

测试通过了。是我那样写的。是自己看错了数据库。

repo: cloudwu/skynet


text:
push notification permissions

plan on adding this any time soon?

Waiting for https://github.com/clusterinc/ClusterPrePermissions/pull/16 to be separated into different requests. Feel free to nudge them!

for sure.

I think it's safe to say at this point that it's never going to be separated into different requests. :) Anyone else up to the task?

+1

+1

https://github.com/clusterinc/ClusterPrePermissions/pull/23

:+1: cheers!

I still cannot see push notifications permissions. Am I looking in the wrong place or is it coming?

Hey folks, I'm merging in @confile's push notification pre-permission, but I have some issues with the change. See here: https://github.com/clusterinc/ClusterPrePermissions/pull/23#issuecomment-141512023
The bottom line is that push notifications permissions don't work the same way as other permissions, and it requires a lot more integration into the app delegate. Supporting it in ClusterPrePermissions is never going to be fully reliable (See my pull request comment).

authors: chetem confile danipralea hsavit1 rsattar s5

repo: clusterinc/ClusterPrePermissions

license: mit


text:
Add to Jenkins list of indicators to build

Description
Fix:
Add covid_act_now to Jenkinsfile list.
Changelog
Fixes

@krivard I forgot this in my first PR.

Looks like this indicator hasn't been added to CI either. Should we do that before merging this PR to make sure all checks pass?

Yeah, good call. Just added.

well lookit that 😉

@eujing would you take a look? we need make test lint to pass before we can deploy the CAN indicator.

I fixed the wip_signal error and the other linting errors, make test lint passes on my side now.

authors: eujing korlaxxalrok krivard

repo: cmu-delphi/covidcast-indicators


text:
[pt] Remove the "What it is" header

Description
Based on this issue, remove the "What it is" header of all definition files.

opa, tenho interesse em trabalhar nessa issue!

opa, tenho interesse em trabalhar nessa issue!

Opa, bem vindo @madfelps!
Vou deixar aqui um resumo do processo de contribuição (caso ainda não tenha feito): https://gist.github.com/edsoncelio/d7fdec7f24d5aba87e3e517c672e9eb5
Mais alguma dúvida entra lá no canal do time no slack da CNCF (se ainda não tiver por lá): #glossary-localization-portuguese
Vou atribuir a issue a você, e de novo: qualquer dúvida só falar :D

authors: edsoncelio madfelps

repo: cncf/glossary


text:
[EN] update Function as a Service

Describe your changes
Update Function as a Service term.
Line 32 says:
FaaS infrastructure will auto-scale the code for heavy use
It's not code that auto-scales, but the underlying infrastructure, the number of instances which are running the code.
I think this will be more accurate:
FaaS will auto-scale the infrastructure for heavy use,
Related issue number or link (ex: resolves #issue-number)
The french localization team noticed this while translating the term: https://github.com/cncf/glossary/pull/2973
As this is a minor fix I didn't open an issue, I opened this PR directly.
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".

@iamNoah1 I agree with you, it's more accurate like that.

Thanks for this @guillaumebernard84, but https://github.com/cncf/glossary/pull/2217 looks to have made this edit obsolete.


text:
update knative description and crunchbase url

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

[x] 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.
[x] 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 added your SVG 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"?

/assign @caniszczyk

repo: cncf/landscape


text:
Member updates 6.7.22

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?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you added your SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] 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)?
[ ] ~30 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"?

LGTM