text:
Figma File Clean Up

UX team needs to organize the CTI Figma file to reflect the finalized decisions, UI and annotations for MVP launch.
File Clean Up

[ ] Update page breadcrumbs to reflect finalized nav labels. (i.e. Radical Collaboration has been changed to Collaborate with Us)
[ ] Remove old screen drafts and artifacts on pages that are listed as finalized.
[ ] Double check all screens have been created and placed on a page with appropriate breakpoint size. (i.e. There is a screen for every page created for LG, MD and SM).
[ ] Ensure all components have been added to the design system.

Resources:
Figma File
CTI - Site Clean Up
CTI Site Map

Feedback from @joycekimdesigns from 6.7.21:
Question areas:
3.1 About / FAQ (FAQ Search Result: is the breadcrumb going to read “Home / About / FAQ”?

Yes, this should read as Home / About / FAQ and I believe it will be Home / About / FAQ / FAQ Results when an input is entered (need to verify though, it could function as the Search Projects behavior where it doesn't redirect to another page.)

4.0 Organization (Page Flow Completed) - Index Contributors: is the breadcrumb going to read “Home / Contributors”? Also, this is missing from the CTI spreadsheet
4.0.2 Individual Organization Page “Home / Organizations / Code for All / Code for America / Open Oakland” has been changed to→ “Home / Organizations / Open Oakland”

This page has become "Organizations" and the breadcrumb should be Home / Organizations
For child pages, it will either be displayed as Home / Organizations / Code for All (Grandparent) / Code for America (Parent) / Open Oakland (Child) to represent the organization levels gathered in the database.
Will add individual organization page to spreadsheet

Confirm - 6.0.1 Search Projects Results - “Home / Search Projects” → shouldn’t it be “Home / Search Projects / Results”?

When entering search criteria in, the page just goes to a different state rather than a new page. So I believe it will remain as Home / Search Projects (need to verify though)

The following Figma file page titles need to be edited:
[ ] 4.0.2 Individual organization page
[ ] 5.0 Collaborate With Us section
[ ] 6.0 Search Projects section

Will note to follow up on these items in the Figma file.

@chalimar since our navigation labels are changing, we need to update the breadcrumbs spreadsheet and screens for dev.

@chalimar since our navigation labels are changing, we need to update the breadcrumbs spreadsheet and screens for dev.

Proposed breadcrumbs listed below and on Google Sheets.

@FarzanaPrianka We will need to make sure the new breadcrumbs are incorporated into the Figma pages. Category labels are not clickable please as an annotation. See Org pages and individual org pages to begin.

Will start working on it from tonight.
ETA:  1 July 2021 (Thursday)
Blockers: None at this moment

The breadcrumbs has been updated

@chalimar @FarzanaPrianka @joycekimdesigns
Progress: How much progress have you made on the issue?
•	Blocks: Are you facing any blockers?
•	Availability: How much time do you have to work on it this week?
•	ETA: When do you think it will be completed?

I updated the breadcrumbs in Figma file (until June 28) as per the google sheet attached . Will look into it again if there is any update required since then.

Updated the breadcrumbs in Figma file for the finalized artboards.

Need to add underlines under breadcrumb links on the website.

authors: DrIffathsultana FarzanaPrianka chalimar mariastudnicka

repo: civictechindex/CTI-website-frontend


text:
More updates for Add Org workflow

Closes #661

Add "http(s)://" validation for URL fields

Add more unit tests in add-org.spec.js

This looks great, Bruce.
Question, though. You removed some validation code around GitHub tags, but that is not mentioned in Issue #661 nor this Pull Request. Could you provide some context / commentary / documentation about that change?

@kevinashworth Thanks for the review and merge!  For the github tag, now it's required for the user to fill it in to enable the next step button on the add org workflow.  Before that update, the back end checked that the user entered something for the tag (not if the tag existed on any org).  Either way, the only level of validation is to check for a blank tag.

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Connect simultaneously with Panasonic app

Connect simultaneously with Panasonic app
To use the native Panasonic application together with Aquarea Smart Cloud you only have to connect with two different emails.
From the native Panasonic application you create a guest account (you can even give it administrator privileges). Now you log in to Home Assistant with the second account.
There is no problem, what is done in one place is seen in a few seconds in the other. It doesn't disconnect. Perfect.
I have two Gmail emails, but I would like someone to check if it can be done with the same email but with two aliases.

Could you explain how to add a guest account?

source: gharchive/issue

authors: lasota-piotr lmahave

repo: cjaliaga/home-assistant-aquarea


text:
I am an amazing person.

Biography로 발전 시켜보실?

zzzㅋㅋㅋㅋㅋ재밌겠다


text:
Cannot view guideline documents.

URL to the linked Repo/Org:
https://github.com/SAPDocuments
Steps to reproduce the problem:

Open link to CLA assistant page
Try to view Contributing Guidelines documents:
https://github.com/SAPDocuments/Tutorial-Contribution/blob/master/contributing.md
https://github.com/SAPDocuments/How-To-Contribution/blob/master/contributing.md

What is the expected result?
Open the documents so I can read them
What happens instead?
GitHub 404 not found page

Hi @pacaceres, You can view the Guidelines of this project here in https://github.com/cla-assistant/cla-assistant/blob/master/README.md

authors: ibakshay pacaceres

repo: cla-assistant/cla-assistant


text:
Support GRPC load balancing with SRV records

Hi,
I'm looking to set up some instances of clangd remote servers and have a load balancer arbitrate between them.
There's an example of a server-side set up for load balancing over at https://github.com/clangd/llvm-remote-index.
In my case it would be simpler if I could use the SRV mechanism optionally configurable in GRPC, per https://github.com/grpc/proposal/blob/master/A5-grpclb-in-dns.md.
This implies a minimal change in the way GRPC channels are configured in clangd, to enable GRPC_ARG_DNS_ENABLE_SRV_QUERIES. In that mode, it performs an initial _grpclb._tcp srv query to get a list of servers and runs in load balancer mode between them.
Presumably this should not break existing clients because it didn't work so there was no reason to set up dns that way.
Would you be open to upstream a change that enables this mode for the clangd remote client and monitor?

Ah, I see grpclb is considered deprecated now, in favor of xDS (Evolution of gRPCLB).
The SRV functionality is only used when the load balancing policy is set to grpclb, so it doesn't seem worthwhile to support it in clangd.
Thanks for your prompt response.

repo: clangd/clangd


text:
Opening in Conemu

Is there a way to open musikcube in conemu and not seperate window?

It's not currently possible, but should be achievable. Right now we link against a specific version of the curses library on Windows that uses a "native" window and emulates console behavior -- that's because it has higher fidelity font rendering, or at least did on older versions of Windows. There's another variant of curses that runs as a true console app that we should be able to link against instead, and generate a separate exe that runs within cmd.exe or conemu.
Let me give this a little bit of thought to see if I can figure out a low-cost way to generate the other variant.

Here's a proof of concept -- it seems to work well:

I still haven't figured out how to automate building it, though.

Thanks for responding, I will waiting for this feature!

If you somehow manage to get this right and working, please mention it in the changelog of the upcoming version of musikcube.
Enjoy your weekend!

Alright, I think I worked out all the logistics. This will be part of the next release.

repo: clangen/musikcube

license_source: bigquery


text:
Adds translatableSelector prop to SortableContainer

Currently trying to use react-sortable-hoc with table rows currently works in most browsers, just not IE & Edge.
This is because while dragging, other SortableItems are translated using CSS, and IE & Edge don't support
translating table rows, or things styled using display: table-row
They do, however, support translating table cells.
By using translatableSelector="td" and ensuring the table's style lives on the table cell rather than the row
this will work in IE & Edge.
I first considered just fixing this automatically if the SortableItem is a table row, but it requires
CSS considerations, I thought it better to be explicit.
Fixes #293
Maybe #151

I couldn't figure out how to see the examples working running yarn start so the example might be a bit broken since moving stuff from the root index.js, but It's pretty close.

Hi, Is there anything I can do to help this get merged?

@robotdana I think this repo is abandoned
My PR is also waiting for a while

@robotdana @clauderic This has been sitting for a while... Is this repo abandoned? I would really love to make use of this PR...

Feel free to use my fork, it’s been working fine the last 11 months

authors: priyanshuchauhan robotdana supernoir

repo: clauderic/react-sortable-hoc


text:
Replace SHA1 with bcrypt for local authentication

I've made some simple changes to my fork to use bcrypt-nodejs to provide more secure, salted password hashes.  I've verified that I can successfully create passwords and subsequently log in using this code, but haven't extensively tested it (or, indeed, know what testing needs to be done apart from simply verifying that I can log in).
The bcrypt-nodejs project uses a 3-clause BSD license, which I believe is compatible with jingo's MIT license, but I'd like to get confirmation from someone who understands these things better than I.
Any comments or suggestions for improvement before this is ready for a pull request?

Hi,
I don't see any particular problem for that to happen, unless of course it could pose a backward compatibility problem. I try to maintain Jingo as simple as possible, for the user to install and maintain and for me to maintain it. Do you think that this would be a drop-in replacement for an existing (possibly 2 or 3 years old) installation or would it be a breaking change? Would we need to add a specific condition in the configuration file, something like "useCrypt: bcrypt" (defaulting to the previous one?)
Looking at your code it seems that this is the case (old password won't work anymore if you just update jingo).

You're right, this is the case.  It would work fine for new installations, but break all the passwords for an existing one.
I could add the config option.  Another possibility is to default to bcrypt for creating new passwords, but when verifying an existing password, try the old SHA1 hashing if bcrypt doesn't verify.  That way, everyone's current password continues to work, but if/when they change their password, it will use the more secure hash.  From the end user's standpoint it would be completely transparent.

authors: cholling claudioc

repo: claudioc/jingo

license: mit


text:
🛑 www.offsitedatasync.com is down

In effadd9, www.offsitedatasync.com (https://www.offsitedatasync.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.offsitedatasync.com is back up in 2302356.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

In 9cf6760, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 39e2eaa.


text:
🛑 livevault is down

In 33c3075, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in f0a39ec.


text:
🛑 livevault is down

In 6ba9b0b, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in c4cfef1.


text:
Feature request: Ability to reload the app within a tux session

My app is set up such that the main file is app.rb, and that file requires several files that contain models.  If I update one of these models, I have to kill my tux session and then start another tux session in order to force a reload.  I would like if I could call "reload!" within the tux session, similar to the Rails console.  It might also be helpful in some cases of highly iterative development if I could set a command-line flag at session start time to always reload the session.
If this feature already exists in some form, then this issue would be solved by a clearer description of that feature in the README.  Thanks!

@cldwalker Thanks for that snippet, super helpful!

authors: bwiggs clizzin

repo: cldwalker/tux


text:
tests: Fix JSON list format tests for go1.9+.

Historically, it has been possible to marshal and demarshal a time.Time and
compare the original and demarshaled values for equality (successfully).
However, go tip (what will presumably become go1.9) changes this behaviour. It
introduces a monotonic element to the time.Time internal representation. Thie
monotonic value (shown as "m=±ddd.nnnnnnnnn" when calling String() on the
time.Time object) is NOT retained when marshaling a time.Time.
This ensures comparing the unmarshaled value with the original will fail.
The fix is to call Truncate(0) on the original time.Time object to remove the
monotonic element before attempting comparing with the unmarshaled value.
This change corrects the required "fixup" behaviour in TestStateToJSON() to be
in line with golang expectations.
See: https://go-review.googlesource.com/c/36255/7/src/time/time.go#54
Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

Coverage remained the same at 35.423% when pulling e60514b0df0247544d0bf14b2ec7b427741668bc on jodh-intel:fix-crazy-golang-time-behaviour-change into 04f53c338488589e4788428c14ddb924cf6c9a62 on clearcontainers:master.

Coverage remained the same at 35.423% when pulling e60514b0df0247544d0bf14b2ec7b427741668bc on jodh-intel:fix-crazy-golang-time-behaviour-change into 04f53c338488589e4788428c14ddb924cf6c9a62 on clearcontainers:master.

lgtm

LGTM

lgtm

authors: coveralls devimc dlespiau jodh-intel sboeuf

repo: clearcontainers/runtime


text:
Can I ask ckpt_and_bfm.zip file?

First, thanks for sharing your great work
I found your repo while checking the below model
(https://github.com/Hangz-nju-cuhk/Rotate-and-Render)
The author said the model is borrowed from 3DDFA
and when I tried to download [ckpt_and_bfm.zip], there was no page
I think I need this file; '106_index.npy'
Would you share it?

+1


text:
fail to load clerk.browser.js

[x] Review the documentation: https://clerk.com/docs
[x] Go through package changelog files.

I success to deploy in production for my project.
however, my project never load clerk.browser.js so i cannot enjoy auth service from clerk.

I checked DNS records, I already verified clerk.turned-e.com , add a cname record for clerk pointing to frontend-api.clerk.services.
https://www.tms.turned-e.com/
everthing work fine in development but not production
Do i miss anything?

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

repo: clerk/javascript


text:
@Clerk/remix broken SSR

Package + Version

[x] @clerk/remix

Version:
0.3.5

Description
After upgrading to version 0.3.5 of clerk/remix SSR seems to no longer work.
Everything has been configured per the clerk/remix setup instructions.
Here is my root loader (note loadUser):
export const loader: LoaderFunction = (args) =>
  rootAuthLoader(
    args,
    {
      loadUser: true,
    }
  )

Here's my page:
const Page = () => {
  const auth = useAuth()

  console.log(auth)

  if(auth.isSignedIn){
    return
Some user!

  }

  return
No user!

}

On the server the log is like so:
{
  isLoaded: true,
  isSignedIn: false,
  sessionId: null,
  userId: null,
  signOut: [AsyncFunction (anonymous)],
  getToken: [AsyncFunction (anonymous)]
}

On the client the log is like so:
isLoaded: true
isSignedIn: true
sessionId: "..."
userId: "..."
signOut: async (...args) => {…}
getToken: async (options) => {…}

The end result for the user is a flash on page load which shows "No user", and then it switches to "Some user!" once the client has finished loading.

Hello @jtparrett, thanks for the report. My first guess is that this is an env variable mismatch Can you check that both the CLERK_FRONTEND_API and CLERK_API_KEY environment variables point to the same instance?
Some more questions that could help:

Which version were you using before?
Is this happening locally or when deployed? If it's the latter, where is the app deployed to?
Is there a live URL we can take a look at?

@nikosdouvlis thanks for your response!
I checked all my keys and they seemed to be in order.

I was using 0.3.4 before.
It was happening locally and in production.
Unfortunately I can't grant you access to the project as it's a closed beta (I might be able to spin up a fake project to replicate if I get time today)

Update: I cleared all my browser data (including 3rd party cookies), then re-authenticated and the problem seemed to go away. So is it possible the cookie/localstorage stuff had gotten out of sync during the update?

I just saw your message on Twitter:

I raised the original issue 😁 thank you so much! It’s definitely related to a change that happened in 0.3.5 as I can downgrade to 0.3.4 and the issues goes away. Will try 0.3.6 later today!

Thank you for the additional context!

Hi @colinclerk , thanks for the response!
Sorry for hijacking your marketing tweet.
Yes, I am running production and staging from the same domain 😄
Is there somewhere I can keep updated about the progress of this bug?
I've also just tried to create a fresh application and was not able to replicate the problem even when switching between 0.3.4 and 0.3.5 which makes me think it must be the domain issue!
I've also just upgraded to 0.3.6 (latest) and upgraded to the latest remix version in my main application and i'm not seeing the original problem at all 🤞 so I'll close this issue for now, thanks again so much for getting back to me!

authors: colinclerk jtparrett nikosdouvlis

repo: clerkinc/javascript


text:
stripeCustomerId errors on return due to casing mismatch

The findOrCreateCustomerId() function returns the Clerk user's Stripe Customer ID from the publicMetadata object, however it seems that Clerk converts camelCase to snake_case, so this becomes undefined, causing a typescript error due to the string requirement.
Changing this line to return this instead works:
return user.publicMetadata.stripe_customer_id as string;

This was fixed with latest updates

authors: ndimatteo perkinsjr

repo: clerkinc/use-stripe-subscription-demo


text:
🛑 Portal Docentes is down

In 4e1da65, Portal Docentes (https://portaldocentes.twk.cl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal Docentes is back up in c826bd7.

repo: cleyan/status-umas


text:
bug:prometheus 调用 clickvisual /read 接口无数据

prometheus配置:
global:
   external_labels:
     monitor: 'example'

clickvisual 生成sql
SELECT COUNT() AS CNT, (intDiv(toUInt32(ts), 10) * 10) * 1000 as t, name, tags, quantile(0.750000)(val) as value FROM metrics.samples WHERE date >= toDate(1700186682) AND ts >= toDateTime(1700186682) AND ts <= toDateTime(1700186992) AND arrayExists(x -> x IN ('alarmId=1' ), tags) = 1 AND arrayExists(x -> x IN ('filterId=3' ), tags) = 1 AND arrayExists(x -> x IN ('uuid=44fe9021-b5d2-458c-853b-20a191215716' ), tags) = 1 AND  name='clickvisual_alert_metrics'  AND arrayExists(x -> x IN ('monitor=example' ), tags) = 1 GROUP BY t, name, tags ORDER BY t

where 里多了 arrayExists(x -> x IN ('monitor=example' ), tags)。  但是metrics.samples表tags根本没有monitor，导致没有数据.

版本是clickvisual-1.0.0-rc11

这个 sql 是 prometheus 查询 clickhouse 的数据，理论上不会添加这个 tag，可能是 prometheus 增加的查询条件
read 流程可以参考这个代码库
https://github.com/clickvisual/prom2click
可以看本地是否有这个配置，如果有会被添加到查询中

这个 sql 是 prometheus 查询 clickhouse 的数据，理论上不会添加这个 tag，可能是 prometheus 增加的查询条件
read 流程可以参考这个代码库 https://github.com/clickvisual/prom2click
可以看本地是否有这个配置，如果有会被添加到查询中

prom2click处 没有这个tag.
通过网络抓包，prometheus 向/read接口传了这个参数。
在prometheus配置里 把 external_labels 去掉了， clickvisual 生成的sql 就没有了。 所以clickvisual是不是要忽略这个external_labels

repo: clickvisual/clickvisual


text:
Navigator actions should be populated with policies from CCLW

Navigator should be initially populated with actions by importing data from CCLW.
Use CCLW export files to map and load CCLW data into Navigator.
This data should be mapped to Actions using the following mapping.

CPR
CCLW
Mapping

Action name
Policy title

Action description
Description

Action date
Policy date
(@Anonymous) (@Anonymous) does this come from CCLW events?

Action type
Policy type
1 to 1 mapping from CCLW to CPR action types

Location of publication
Country code
Check CCLW ISO country codes match those used in Navigator

Instrument
Instrument list
[link]

Sector
Sector list
[link]

Keyword(s)
Keyword list
[link]

Theme
Response; Frameworks*
[link]

Events
Events
[link] [link]

*Note: the precise distinction between CCLW’s ‘Response’ and ‘Frameworks’ metadata categories is not clear, given that both categories contain the same set of values. We should consider which of the categories we should use when importing data from CCLW.

@chrisaballard Re: action date coming from CCLW events:
Yes, action date comes from the first CCLW event associated with an action, as they don’t have standalone dates for the actions themselves

authors: chrisaballard danny-waite-cpr

repo: climatepolicyradar/navigator


text:
Remove scipy from Windows env

Closes #3 (if tests pass)

Fails in the same way as https://github.com/climlab/climlab-rrtmg/pull/5 without scipy in the env.
So I'll close this and we'll keep scipy for now.

repo: climlab/climlab-emanuel-convection


text:
Abstract runes

Exploration to see if we can abstract decoding out of if Split and Splitter, since they (should) only care about runes. Can they be made non-generic?
The idea is to offer a non-generic Runes interface. RuneTokenizer will have to be generic, but its methods for navigating the string of runes need not be.

First pass was a 2x performance regression. Latest bits are dow to ~2%!

Went with https://github.com/clipperhouse/uax29.net/pull/21 instead.


text:
Add Metadata support & fixes for support of Cassandra 3

This pull request consists of 2 parts:

Update of dependencies for DataStax Java driver - unfortunately it wasn't possible to make this as a separate PR due the differences in layout of system tables, so tests weren't passing.
Addition of functions that can fetch metadata from cluster - information about cluster itself, hosts, keyspaces, tables, etc.  These functions replace other functions, such as client/get-hosts, cql/describe-table, ... - these functions are removed from source code.

The code was tested on both Cassandra 3 (3.11.1) & Cassandra 2 (2.2.11).
What is missing - support for fetching of DSE-specific flags, as it's not clear how to use both drivers together - DSE-specific driver has license clause that it should be used only with DSE, not with open source Cassandra.
It would be useful to get feedback on the code style, etc. I have time to refactor code.

It looks like that it's not enough resources on Travis, so some of checks are timed out...

@alexott thank you.

Thank you for accepting it - I'll continue with addition of more Cassandra 3 features as separate PRs

authors: alexott michaelklishin

repo: clojurewerkz/cassaforte


text:
"cfsp instance post" command fails with exception 429 "TOO MANY REQUESTS"

Exception when calling InstancesApi->cf_manager_rest_api_post_instances: (429)
Reason: TOO MANY REQUESTS
HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'Content-Length': '0', 'Server': 'Werkzeug/1.0.1 Python/3.6.8', 'Date': 'Fri, 28 Jan 2022 08:40:27 GMT'})

Hi @zrlhle, this is an "expected" error when there is insufficient quota in your project. (if you navigate to http://<swagger_ip>:8080/ui/#/Instances/cf_manager.rest_api.post_instances you can see that the error code 429 corresponds to "Insufficient Quota".
This means that either you are not part of this group, or there is no fpga available in this group.
In the former case, you may contact the administrator to add you to a group.
In the latter case, you need to make sure that no other instances of yours reserve FPGAs (e.g. deled them if you don't need them), or contact again the administrator to increase your quota.
But this might be a common problem, thx for the feedback, maybe we need to add to the documentation @fab7 ? On the other side, this is a notification from the cFRM API and it doesn't make sense to report each of the 100s error/status codes in every project, right? Maybe we can add a notification like: For a comprehensive list of status/error codes of cFSP, please check cFRM API at http://<swagger_ip>:8080/ui/

So it looks like the problem is that my userID "hle" is not associated with any projects ... is the assumption that this association gets done when the user asks for an account?
@bringlein could you please fix this for me?

@zrlhle yes your account wasn't associated with any cF project, I corrected this just now.
@diamantopoulos I support the idea to point the user to the swagger UI to check for more details on errors.

@bringlein thank you, works now

authors: bringlein diamantopoulos zrlhle


text:
🛑 telkom.co.id is down

In bd99b61, telkom.co.id (https://www.telkom.co.id/sites) was down:

HTTP code: 0
Response time: 0 ms

Resolved: telkom.co.id is back up in e3083d0.

repo: cloudbip/upptime


text:
🛑 dewaweb.com is down

In 9db9c7d, dewaweb.com (https://dewaweb.com) was down:

HTTP code: 403
Response time: 213 ms

Resolved: dewaweb.com is back up in 12f9d2e after 52 minutes.


text:
🛑 webflow.com is down

In 8600faf, webflow.com (https://webflow.com) was down:

HTTP code: 406
Response time: 194 ms

Resolved: webflow.com is back up in c6c6014 after 15 minutes.


text:
🛑 hostingan.id is down

In cd253b9, hostingan.id (https://hostingan.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hostingan.id is back up in 658bad9.


text:
🛑 my.dewabiz.com is down

In 9aba860, my.dewabiz.com (https://my.dewabiz.com) was down:

HTTP code: 403
Response time: 1955 ms

Resolved: my.dewabiz.com is back up in 6e7c269.


text:
🛑 cbn.id is down

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

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 2e740c1.


text:
🛑 member.idwebhost.com is down

In 9073725, member.idwebhost.com (https://member.idwebhost.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: member.idwebhost.com is back up in 8d521bd.


text:
🛑 cbn.id is down

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

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 46f2343.


text:
🛑 myrepublic.co.id is down

In bfb6366, myrepublic.co.id (https://myrepublic.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: myrepublic.co.id is back up in 87544dd.


text:
Fast.io no longer available

As of January 16th, 2021, Fast.io has discontinued service.
https://fast.io/

thanks! removed!

authors: karentamrazyan umarmw

repo: cloudcommunity/Free-Hosting


text:
Recover from panic in handler fn

resolves #584

/cc @n3wscott @slinkydeveloper

@n3wscott can you check out the failing test? seems like an issue with TestBlockingSenderReceiver test

There is some 5% tolerance in place in the test, maybe it should be increased?

@n3wscott when I increased that time tolerance from 5% to 10% the tests are passing.

@n3wscott when I increased that time tolerance from 5% to 10% the tests are passing.

thanks, I think the circleci builder machines are not the best. :D

LGTM
just need to sign that last commit and the DCO will be happy.

So I should include the More time tolerance in TestBlockingSenderReceiver commit?

I am fine adding more budget to that test, thanks for fixing!
LGTM

authors: matejvasek n3wscott slinkydeveloper

repo: cloudevents/sdk-go


text:
[SSL/TLS] Remove resolved caveat in total-tls/enable.md

Summary
Total TLS now allows users to change the CA without first disabling the feature.

If we could wait to merge this until next week that'd be great.

Looks like it works... but still shows an error message?

@kodster28 - Sorry about that we had rolled back the change temporarily, but it's back out now.

repo: cloudflare/cloudflare-docs


text:
[Docs Site] Re-render Mermaid diagrams when theme changes

Summary
Re-render Mermaid diagrams when theme changes.

Helpful comments! Not sure the data-processed is needed — none of the other examples on mermaid.js.org have it — but whatevs :)

It's normally only relevant when using the initialize/run functions, but we apply some CSS to pre.mermaid:not([data-processed]) for FOUC/noscript purposes.

There's still some layout shift, since the size of the definiton in the pre isn't representative of the rendered diagram, but it's a little better than nothing.
I'd prefer server-side rendering but that requires Playwright & makes builds pretty flaky (OOM and/or timeouts).


text:
Support for worker resource bindings

resolves #313
Description
To enable the management of worker resource bindings in Terraform.
Has your change been tested?
Automated test coverage.
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x ] I have added tests to cover my changes.
[ x] All new and existing tests passed.

Is this different to the work in #311 and #310? At first glance, there looks to be some overlap.

Hi @jacobbednarz yes I did not see #311 there is some overlap. I would say that as you asked for more abstraction over the creation of the multipart message, mine fulfils those criteria better? There is no overlap with #310 I have been watching that one as I am also looking for KV support in Terraform :) Mine is just for creating WASM and KV bindings rather than managing KV namespaces.

Actually it duplicates #293 too

I like the higher abstraction here. @adampointer-form3, is there a way we can abstract the part from WASM as well? Seems like an implementation detail from the multi-part upload we would want to hide.

Is that better?

@Electroid are there any other requirements here? This is starting to block internal projects. I don't want to resort to using forks really.

....and now duplicates #363 too 🙂 By the looks of things, we can go with #363 and once that is merged, build off it as it should cover the previous use cases mentioned in other PRs too.

Closing on behalf of #363 which I merged. Thank you @adampointer-form3 for the effort, I appreciate that.

authors: Electroid adampointer-form3 jacobbednarz patryk

repo: cloudflare/cloudflare-go


text:
Implement KEMTLS based on Delegated Credentials

This PR implements KEMTLS based on @claucece's DC branch (#28). There are a few minor fixes included in the DC stuff, surrounding the negotiation of DC supported algorithms.
This branch is targeted at the cf because that makes this PR reviewable: otherwise all of circl is included on top of my changes to the DC implementation and crypto/tls in general.
The following is currently implemented

[x] KEMTLS
[x] crypto/kem ergonomic KEM api

This package implements:

Kem25519: a KEM-variant of X25519. Useful for testing, but should be deleted before merge.
SIKEp434 provided via circl
Kyber512 provided via circl

[ ] KEMTLS client authentication

New TLS options
New supported signature algorithms (for DC):

[x] KEMTLSwithSIKEp434
[x] KEMTLSwithKyber512

New supported keyshare types (these can be negotiated independently in TLS 1.3):

[x] SIKEp434
[x] Kyber512

Testing

[ ] Unit tests

I've currently tested it by hard-coding the type of DC that the DC tests use. Unfortunately, those tests still need to be refactored a bit before it's easy to add more types of supported DC — but I'm sure that was on @claucece's list :smiley:

Stuff to do still:

Expand the number of KEMs based on newer versions of Circl (~Kyber, hopefully, soon~)

People who may be interested: @claucece, @bwesterb, @chris-wood

Hi, @thomwiggers ! This is great! I have some time this week.. so I'll review and also update the DC branch. I was going to add DC support for client auth if it is useful for you as well. Let me know ;)

That would be great for KEMTLS client auth as well

@thomwiggers I'm starting a new branch with this changes and refactors, as this will be too difficult to merge.

Yeah, I'd wondered if that would be necessary.

Closing in favour of #44

authors: claucece thomwiggers

repo: cloudflare/go


text:
Ability to delete preview site when pr is closed

Hi,
The action is working great, however we're ending up with a lot of preview sites that are no longer needed as they don't appear to know that the pr is closed/merged.
Is there any ability, or plan to handle the deletion of preview sites when pr's are merged?
Thanks.

I am wondering if there will be support for this as well.
I wonder if there is a workaround that we can run via the API to delete it? Seems "hacky" to do, but it would be nice to get official word if this is planned to be supported or not before messing with the API. 🙌
Source
https://community.cloudflare.com/t/delete-cloudlfare-pages-deployments/345640

Looking into this further, I noticed when I deleted the environment from GitHub it automatically deleted it from the CloudFlare dashboard too.
I wonder if managing this through the GitHub API might be a better approach?
https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment

@andrewgbell I really appreciate this request. ❤
@jaydrogers Cloudflare Pages and Github Environment are two completely isolated things.
Said that, I would see a proper workflow like this:
flowchart LR
    A[Pull-request is opened] --> B[Environment is provisioned]
    B -->|Provision| Environment
	subgraph Environment
	C[Github Environment] -. matches .- D[Cloudflare Deployment]
	end

    E[Pull-request is merged] --> F[Environment is decomissioned]
    F -->|Decomission| Environment

Thanks a ton for the diagram! This makes sense. I'll play around with this and see if I can provide some examples that work for me.
I appreciate your attention to detail @limakzi!

The action @rmoff linked seems to use a basic api fetch: https://github.com/unlike-ltd/github-actions-cloudflare-pages/blob/main/src/cloudflare/deployment/delete.ts#L7
The pages-action also uses some fetches already, so it might be possible to adapt: https://github.com/cloudflare/pages-action/blob/aeb0d936a7e08b4861c3d0ac8811fe39138085f9/src/index.ts#L52

this action works:
name: Delete Cloudflare Pages Preview Deployment

on:
  pull_request:
    types: [closed]

jobs:
  delete-preview-deployment:
    runs-on: x64
    steps:
      - name: Get branch name
        id: get-branch
        run: echo "branch=$(gh pr view $PR_NO --repo $REPO --json headRefName --jq '.headRefName')" >> $GITHUB_OUTPUT
        env:
          REPO: ${{ github.repository }}
          PR_NO: ${{ github.event.pull_request.number }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

      - name: Delete Cloudflare Pages preview deployments
        run: |
          DEPLOY_BRANCH="${{ steps.get-branch.outputs.branch }}-deploy"
          deployment_ids=$(curl -s -X GET "https://api.cloudflare.com/client/v4/accounts/${{ secrets.CLOUDFLARE_ACCOUNT_ID }}/pages/projects/${{ github.event.repository.name }}/deployments" \
            -H "Authorization: Bearer ${{ secrets.CLOUDFLARE_API_TOKEN }}" \
            -H "Content-Type: application/json" \
            | jq -r --arg DEPLOY_BRANCH "$DEPLOY_BRANCH" '.result[] | select(.deployment_trigger.metadata.branch == $DEPLOY_BRANCH) | .id')

          for deployment_id in $deployment_ids; do
            echo "Deleting deployment $deployment_id"
            curl -s -X DELETE "https://api.cloudflare.com/client/v4/accounts/${{ secrets.CLOUDFLARE_ACCOUNT_ID }}/pages/projects/${{ github.event.repository.name }}/deployments/$deployment_id?force=true" \
              -H "Authorization: Bearer ${{ secrets.CLOUDFLARE_API_TOKEN }}" \
              -H "Content-Type: application/json"
          done

This action works:
name: Delete Cloudflare Pages Preview Deployment

on:
  pull_request:
    types: [closed]

jobs:
  delete-preview-deployment:
    runs-on: x64
    steps:
      - name: Get branch name
        id: get-branch
        run: echo "branch=$(gh pr view $PR_NO --repo $REPO --json headRefName --jq '.headRefName')" >> $GITHUB_OUTPUT
        env:
          REPO: ${{ github.repository }}
          PR_NO: ${{ github.event.pull_request.number }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

      - name: Delete Cloudflare Pages preview deployments
        run: |
          DEPLOY_BRANCH="${{ steps.get-branch.outputs.branch }}"
          deployment_ids=$(curl -s -X GET "https://api.cloudflare.com/client/v4/accounts/${{ secrets.CLOUDFLARE_ACCOUNT_ID }}/pages/projects/${{ github.event.repository.name }}/deployments" \
            -H "Authorization: Bearer ${{ secrets.CLOUDFLARE_API_TOKEN }}" \
            -H "Content-Type: application/json" \
            | jq -r --arg DEPLOY_BRANCH "$DEPLOY_BRANCH" '.result[] | select(.deployment_trigger.metadata.branch == $DEPLOY_BRANCH) | .id')

          for deployment_id in $deployment_ids; do
            echo "Deleting deployment $deployment_id"
            curl -s -X DELETE "https://api.cloudflare.com/client/v4/accounts/${{ secrets.CLOUDFLARE_ACCOUNT_ID }}/pages/projects/${{ github.event.repository.name }}/deployments/$deployment_id?force=true" \
              -H "Authorization: Bearer ${{ secrets.CLOUDFLARE_API_TOKEN }}" \
              -H "Content-Type: application/json"
          done

@andrewgbell Thanks for the suggestion! This seems like something that might be better managed within Pages instead of as part of an action. I'll pass this request to the Pages core team as a possible new feature. In the meantime, please use the workaround posted above. Thanks!
cc @nevikashah

@nprogers is there a way we can track this feature request to Pages core? Would also love my preview deploys to be automatically deleted when a PR is merged (and this would probably free up a certain amount of storage on CF data centers).

Workaround with hard-coded api-calls? 🥸
(Not blaming @acrogenesis; he did amazing job working around lack of simple logic in software.)
What blocks us from delivering similar action called: pages-actions-destroy?

authors: acrogenesis andrewgbell dargmuesli jaydrogers limakzi nprogers robinmetral

repo: cloudflare/pages-action


text:
chore: put vendored sjcl into devDependencies

sjcl is built, vendored (and source controlled) so putting it as a production dependency is redundant

will be closed by #35

repo: cloudflare/voprf-ts


text:
refactor websockets to be more idiomatic

The current WebSocket api is closely modeled after the JavaScript WebSocket api which is functional but seems like a strange fit inside of a rust program. This PR is meant to refactor the WebSocket api to feel more rust-y.
Inspiration was taken from several other rust http frameworks (primarily axum and warp) but some of the restrictions JavaScript places on us requires us to make some changes. The biggest different in my opinion is that we don't use a Sink for sending messages through the WebSocket, which is because send does not return a promise for when it has finished sending the message and I thought having an async trait that always acts synchronously is strange.
This PR is a draft so if you have opinions on what the WebSocket api should look like leave your opinion, I'd love some feedback on this.

https://github.com/cloudflare/workers-rs/pull/133/files#diff-9429c18070f1b18618d23f33d40eb65a6e19ce99be5ffeaf5744cd5db2526de9R58
idk why I can't leave a comment in the PR inline there, but I'd change send_with_binary to send_with_bytes. not critical, but if you rename the MessageEvent methods to match Request ones, it makes more sense.

authors: nilslice zebp

repo: cloudflare/workers-rs


text:
Remove beta warning for durable objects in README.md

They're not beta anymore woohoo

🎉🎉🎉 thank you!

authors: nilslice threepointone


text:
🐛 BUG:Could not start vitest when using Cloudflare Vectorize

Which Cloudflare product(s) does this pertain to?
Workers AI, Wrangler, Miniflare
What version(s) of the tool(s) are you using?
3.91.0
What version of Node are you using?
v22.9.0
What operating system and version are you using?
macOS 14.5
Describe the Bug
Observed behavior
Could not run test with vitest and @cloudflare/vitest-pool-workers
Expected behavior
Run test
Steps to reproduce
Run test with vitest-pool-workers (version 0.5.32)
Write vector config in wrangler.toml
[[vectorize]]
binding = "VECTORIZE"
index_name = "webapp-dev"

Write vitest.config.ts
import { defineWorkersProject } from "@cloudflare/vitest-pool-workers/config";

export default defineWorkersProject({
  esbuild: {
    // Required for `using` support
    target: "ES2022",
  },
  test: {
    globals: false,
    include: ["**/src/**/(*.)+(spec|test).+(ts|tsx)"],
    poolOptions: {
      workers: {
        singleWorker: true,
        wrangler: {
          configPath: "./wrangler.toml",
        },
      },
    },
  },
});

Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
> vitest --run

 RUN  v2.1.6 /Users/codehex/go/src/github.com/codehex/webapp/workers/webapp

Using vars defined in .dev.vars
[vpw:inf] Starting single runtime for vitest.config.ts...
workerd/server/workerd-api.c++:797: error: wrapped binding module can't be resolved (internal modules only); moduleName = miniflare-internal:wrapped:__WRANGLER_EXTERNAL_VECTORIZE_WORKERVECTORIZE
workerd/jsg/util.c++:274: error: e = workerd/server/workerd-api.c++:827: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 102b6d2a3 10311f267 103103fbf 102b0fe47 102b16517 102b19ea7 102b185ef 102b094e7 10546c2c7 10546c5cb 10546aeef 10546ac87 102af87c3 1917220df; sentryErrorContext = jsgInternalError
service core:user:vitest-pool-workers-runner-: Uncaught Error: internal error

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
 ❯ #assembleAndUpdateConfig ../../node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:9983:13
 ❯ process.processTicksAndRejections node:internal/process/task_queues:105:5
 ❯ Mutex.runWith ../../node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:3632:16
 ❯ #waitForReady ../../node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:10040:5
 ❯ getProjectMiniflare ../../node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1430:5
 ❯ Object.runTests ../../node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1683:20
 ❯ executeTests ../../node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/resolveConfig.RxKrDli4.js:7680:5
 ❯ ../../node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js:10798:9
 ❯ Vitest.runFiles ../../node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js:10820:12

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_RUNTIME_FAILURE' }
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  no tests
      Tests  no tests
     Errors  1 error
   Start at  16:32:23
   Duration  559ms (transform 0ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)

[vpw:dbg] Shutting down runtimes...
error during close MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:9983:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Mutex.runWith (/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:3632:16)
    at async #waitForReady (/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js:10040:5)
    at async getProjectMiniflare (file:///Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1430:5)
    at async Object.runTests (file:///Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1683:20)
    at async Promise.all (index 5)
    at async executeTests (file:///Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/resolveConfig.RxKrDli4.js:7680:5)
    at async file:///Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js:10798:9
    at async Vitest.runFiles (file:///Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js:10820:12) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined,
  type: 'Unhandled Error',
  stacks: [
    {
      method: '#assembleAndUpdateConfig',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js',
      line: 9983,
      column: 13
    },
    {
      method: 'process.processTicksAndRejections',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/workers/webapp/node:internal/process/task_queues',
      line: 105,
      column: 5
    },
    {
      method: 'Mutex.runWith',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js',
      line: 3632,
      column: 16
    },
    {
      method: '#waitForReady',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/miniflare@3.20241106.1/node_modules/miniflare/dist/src/index.js',
      line: 10040,
      column: 5
    },
    {
      method: 'getProjectMiniflare',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs',
      line: 1430,
      column: 5
    },
    {
      method: 'Object.runTests',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/@cloudflare+vitest-pool-workers@0.5.32_@cloudflare+workers-types@4.20241127.0_@vitest+runner@_rspzct5a3s4gq7qtap7afu3hsu/node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs',
      line: 1683,
      column: 20
    },
    {
      method: 'executeTests',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/resolveConfig.RxKrDli4.js',
      line: 7680,
      column: 5
    },
    {
      method: '',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js',
      line: 10798,
      column: 9
    },
    {
      method: 'Vitest.runFiles',
      file: '/Users/codehex/go/src/github.com/codehex/webapp/node_modules/.pnpm/vitest@2.1.6_@types+node@22.0.0_jiti@1.21.6_yaml@2.6.1/node_modules/vitest/dist/chunks/cli-api.FAAw0S6C.js',
      line: 10820,
      column: 12
    }
  ]
}
/Users/codehex/go/src/github.com/codehex/webapp/workers/webapp:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  webapp@ test: `vitest --run`
Exit status 1

This also occurs if you just use workers ai binding ffs.

authors: Code-Hex OultimoCoder

repo: cloudflare/workers-sdk


text:
WAFFLE-538 Integrate ratelimits to wrangler dev --local

What this PR solves / how to test
Author has addressed the following

Tests

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[ ] Not necessary because:

@oliy can merge? get in release?

Yay!  Should be ready now?  I don't have merge privileges, so @mrbbot will probably have to do it for me?

Does this have to land today? We have just locked main for today's release.
We will be doing another release tomorrow morning.

authors: irvinebroque oliy petebacondarwin


text:
Improve init --site error for existing wrangler.toml

💡 Feature request
For wrangler init --site if wrangler.toml exists already instead of erroring, make the worker-site directory and ask the user to append to their wrangler.toml bucket and entry-point
Basic example
Instead of:
this-wrangler init --site
Error: A wrangler.toml file already exists! Please remove it before running this command again.

output
this-wrangler init --site
⬇ Installing cargo-generate...
⚠ Append to the parent environment in your wrangler.toml:
[site]
bucket = "./static-folder"
entry-point = "workers-site"
🌀  🐑  Generating a new webpack worker project with name 'workers-site'...
🔧   Creating project called `workers-site`...
✨   Done! New project created /Users/victoriabernard/cf-github/workers-docs/workers-site

Nit: Succesfully should be spelled Successfully while we at it

so the trick with this is that we don't know what the user's static file directory is called. i can make a PR to improve the message tho- let me see what i can come up with

repo: cloudflare/wrangler


text:
2032: Upgrade tar dependency

Fixes #2032

@dhaynespls why did you remove the npmshrinkwrap file?

@jyn514 Shouldn't be removed -- just a big diff

I specifically ran npm audit fix w/ npm version 6.14.5


text:
chore: update undici to latest

Also, aligns the names of workspaces in the monorepo with their containing folder, to help keep things consistent.
Note the HeadersInit type changed slightly so it needed a small refactor. See https://github.com/nodejs/undici/pull/1199

Oh thank god they fixed it, the Iterable signature was confusing as hell to manage. Thanks for updating it here!

we should also update this on miniflare so we don't ship two versions

we should also update this on miniflare so we don't ship two versions

See https://github.com/cloudflare/miniflare/issues/220

authors: petebacondarwin threepointone


text:
[badges / badge v1.10.3] green badge color has changed

** poor readability of green badge color **
** changed color --- green from 600 to 400 & font color from white to gray/900 **
** Figma **
Priority (medium)

The issue is closed by using the existing badge component.

repo: cloudforet-io/mirinae


text:
fix(p-json-schema-form): use PSearchDropdown if schema has prefixItems

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[x] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Updated Storybook documents
[ ] Tested with console

Description

:tada: This PR is included in version 1.1.0-beta.438 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
Homebrew formula defaults to bosh binary

Now that the CLI is GA, this should be the default.
Note: build.without? still works even though the property is with.

@wendorf chatting with a few people, i think we should keep this for a little bit as is until more people flip over to the new cli.

Sounds good to me. Can we keep the story/PR open and maybe prioritized for
a couple iterations away? I'd rather push it down a couple times than
forget about it.
On Tue, May 2, 2017 at 9:12 AM, Dmitriy Kalinin notifications@github.com
wrote:

@wendorf https://github.com/wendorf chatting with a few people, i think
we should keep this for a little bit as is until more people flip over to
the new cli.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh-cli/pull/210#issuecomment-298683004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAY3LkXRycsLidcTicysMqmV7NC2iZHrks5r11XzgaJpZM4NNvG-
.

closing in favor of https://github.com/cloudfoundry/bosh-cli/pull/190. that PR has code that is necessary for the actual change.

authors: cppforlife wendorf

repo: cloudfoundry/bosh-cli


text:
Change type of credential field to text in service_key table.

Solves https://github.com/cloudfoundry/cloud_controller_ng/issues/468

Probably already solved by https://github.com/cloudfoundry/cloud_controller_ng/blob/965dbc4bdf65df89f382329aef39f86a916b3f05/db/migrations/20150713133551_enlarge_service_keys_credentials.rb


text:
TOC Bootstrapping

Proposal:
First election places 5 people in seats. First two highest number of votes start 2 year terms. 3 next are 1 year terms. Election cycle kicks off a year later.
Initial elig proposal:
Need to propose who is elig to run for TOC initially, since the requirements post formation include roles that don't exist during startup. What if TOC elig == vote elig?

I also want to note that we discussed (but didn't come to a conclusion on) the more general question of whether TOC eligibility should equal voter eligibility (that is, you don't need to be a WG lead or approver to be a member of the TOC) in all elections, not just the initial election. The reasoning being that if we trust the election process enough to allow any contributor to be a candidate for the TOC in the first election, why wouldn't that also work in subsequent elections?

I also want to note that we discussed (but didn't come to a conclusion on) the more general question of whether TOC eligibility should equal voter eligibility (that is, you don't need to be a WG lead or approver to be a member of the TOC) in all elections, not just the initial election. The reasoning being that if we trust the election process enough to allow any contributor to be a candidate for the TOC in the first election, why wouldn't that also work in subsequent elections?

authors: chipchilders jenspinney

repo: cloudfoundry/community


text:
add support for TLSv1.3

add support for TLSv1.3 for the tomcat

test fails because defaults expect to be the values before your change,
see:
../all-properties-tomcat-server.xml
Since you are from vmware you should be able to a property for these settings, so that we can have configuration in future. Default can be the values of your PR

@strehle Thanks, I have fixed the test.

authors: adam-jian-zhang strehle

repo: cloudfoundry/uaa-release


text:
Bug: uncaught panic error when incorrect cursor is supplied

When a before/after cursor is supplied to a query with a different set of orderBy keys, the loadCursor will panic because there is a mismatch in map keys.

In the screenshot you can see if the cursor deserialises and has keys that are not within the orderBy map then the string conversion will panic

Raised a PR!

@juunini Hello! Is there any chance you could take a look at this PR?

Oh, sorry, I was too late to see this issue and PR

authors: captchanjack juunini

repo: cloudmatelabs/gorm-gqlgen-relay


text:
feat: add PodMonitor relabeling options

Hi,
Prometheus relabeling rules are often used to deal with deployment specific cases where exporter metrics have to be altered or filtered before recording.
These changes add two new options monitoring.podMonitorMetricRelabelings and monitoring.podMonitorRelabelings to pass slices of RelabelConfig to the PodMonitor.
This contrib is probably still missing some docs or other required changes I'm not aware of. Looking forward for your feedbacks.
Thanks!
Related to: https://github.com/cloudnative-pg/charts/pull/148
Closes #2501

I'll implement it for PoolerMonitoringConfiguration too. Just figured out it's missing...

/test

This should be a generic fix for #2501 (#2954) with no API breakage

@armru should I be worried about the failed e2e jobs?

Hello @npdgm, nothing to worry about for the moment.
Thanks for the contribution, we will review it ASAP

E2E tests running in EDB fork https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/6638192579

This should be a generic fix for #2501 (#2954) with no API breakage.
Users wanting to free the cluster label because it conflicts with federation could use:
monitoring:
  podMonitorEnabled: true
  podMonitorMetricRelabelings:
  - sourceLabels: [cluster]
    targetLabel: cnpg_cluster
  - sourceLabels: [cluster]
    action: labeldrop

As the creator of #2501, I can say this approach of PodMonitor relabeling does not really fix my issue.
As a user of centralized observability (= one view on multiple sources where cnpg-based psql DBs are created) we then still cannot re-use alerts and dashboards, as those still use the cluster label for referring to the psql cluster.
We cannot really be backwards-compatible here; at least with respect to monitoring artifacts (alerts and dashboards).
My main question is: Do you even want to offer first-level support for those use-cases?
So far, we forked alerts and dashboards and maintain them ourselves moving forward. That's basically the price to pay for not supporting it :)

@sjentzsch, let me recap:

We currently emit metrics setting a label "cluster" for 2 metrics returned by instances (not the operator), cnpg_collector_up and cnpg_collector_postgres_version.
Other multi-cluster tools expect the "cluster" label to be used for the Kubernetes cluster the metric is coming from.
Our dashboard expect the "cluster" label on cnpg_collector_up to get the available clusters and show them in the drop down.
The only alerts we provide, don't use the cluster label at all atm.
Other people's custom dashboards and alerts could potentially expect the "cluster" label as we intend today to be there.
Just adding a second label would not solve your issue because the other tools would still not overwrite the old one.
It would be awesome if we could avoid introducing a breaking change both on people using our own dashboard or a customised version of it and their own custom alerts.

The Prometheus Operator allows you to rewrite labels via both PodMonitor and ServiceMonitor, if you are not using those you can still configure Prometheus to do so via metric_relabel_configs, which if I got it correctly, @sjentzsch, you are already doing and you would be fine continuing doing, right? So your issue, @sjentzsch, is actually that you have to fork the dashboard, correct? Because if that's the issue we could just find another way to infer all the available clusters in the dashboard and leave the "cluster" label as is, providing people suggestions about how to rewrite it if needed. WDYT?

can you integrate the PR with some documentation?
Sure, I'll look into that.

As for the discussion on whether this cluster label should be renamed, I also have a hard time forging an opinion on what's best for the project and how to deal with a potentially breaking change. Here we tend to tweak most upstream dashboard anyway. So I won't claim relabelings are the solution for all, but they surely have other uses and still be nice to have.

I added support for them in the pooler, too. Are you okay with that?
Of course, thanks a lot!

@sjentzsch, let me recap:
1. We currently emit metrics setting a label "cluster" for 2 metrics returned by instances (not the operator), `cnpg_collector_up` and `cnpg_collector_postgres_version`.

2. Other multi-cluster tools expect the "cluster" label to be used for the Kubernetes cluster the metric is coming from.

3. Our dashboard expect the "cluster" label on `cnpg_collector_up` to get the available clusters and show them in the drop down.

4. The only alerts we [provide](https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/main/docs/src/samples/monitoring/prometheusrule.yaml), don't use the cluster label at all atm.

5. Other people's custom dashboards and alerts could potentially expect the "cluster" label as we intend today to be there.

6. Just adding a second label would not solve your issue because the other tools would still not overwrite the old one.

7. It would be awesome if we could avoid introducing a breaking change both on people using our own dashboard or a customised version of it and their own custom alerts.

The Prometheus Operator allows you to rewrite labels via both PodMonitor and ServiceMonitor, if you are not using those you can still configure Prometheus to do so via metric_relabel_configs, which if I got it correctly, @sjentzsch, you are already doing and you would be fine continuing doing, right? So your issue, @sjentzsch, is actually that you have to fork the dashboard, correct? Because if that's the issue we could just find another way to infer all the available clusters in the dashboard and leave the "cluster" label as is, providing people suggestions about how to rewrite it if needed. WDYT? CC @achanda

Good summary, yes, I do agree that my issue is currently with the dashboard that we require to fork.
However, in general, if we decide to stick with the cluster label, new metrics & alerts might arise in the future, making it even harder to align alerts & dashboards for both use cases (introducing non-breaking changes while supporting multi-cluster setups). I can totally understand both perspectives.
I think one of the things to put on the roadmap maybe is: configurability of alerts & dashboards, using jsonnet or other tooling, in order to allow for different environments.
However, this discussion might be out-of-scope for this PR 👍

/ok-to-merge

@npdgm I have added the following to my cluster but I am not seeing the cnpg_cluster label being populated.
https://github.com/onedr0p/home-ops/blob/556982317381ddb0800601a0da7816b898b7e3e8/kubernetes/main/apps/database/cloudnative-pg/cluster/cluster16.yaml#L32-L39
I didn't know if it was worth commenting here, or in the linked issue, or creating a new issue.

authors: armru mnencia npdgm onedr0p phisco sjentzsch

repo: cloudnative-pg/cloudnative-pg


text:
[Grafana]使用している画像について

若干画像が違う部分があるので、可能なのであれば全体的に差し替えた方がよいかも？
ただ、画面はよく変わるし、今の画像でもハンズオン自体はできると思うので、タスク状況によってはやらない選択肢もありだと思います。
以下気づいた点

謎の白いスペースがある

https://github.com/cloudnativedaysjp/cnd-handson/blob/cndw2024/chapter_grafana/image/dashboards.png

adminの画面ではない？画像がちらほら

adminでログインする想定だと思うので、画面も合わせた方が良いかも？
これとか：https://github.com/cloudnativedaysjp/cnd-handson/blob/cndw2024/chapter_grafana/image/import-dashboard.png

Grafanaのversionアップによる変更？

タブに変わってる
https://github.com/cloudnativedaysjp/cnd-handson/blob/cndw2024/chapter_grafana/image/notifications.png

こちらのプルリクエストで対応済み
https://github.com/cloudnativedaysjp/cnd-handson/pull/393

repo: cloudnativedaysjp/cnd-handson


text:
feat(test): creating local cluster for e2e

Creating a local cluster:
$ make e2e-local-cluster-create
cd test/e2e/local-cluster && go run .
I0629 13:22:52.739416  580350 create_cluster.go:63] "configuration loaded" kindClusterName="greenhouse-e2e" dockerImageRepository="greenhouse" dockerImageTag="e2e-latest" dockerImageBuildSkip=false kubeconfigName="e2e.kubeconfig" kubeconfigInternalName="e2e.internal.kubeconfig"
I0629 13:23:08.063941  580350 create_cluster.go:80] "cluster created successfully"
I0629 13:23:08.332099  580350 create_cluster.go:108] "kubeconfig exported successfully"
I0629 13:23:09.076845  580350 create_cluster.go:118] "Docker image built successfully"
I0629 13:23:16.396176  580350 create_cluster.go:127] "Docker image loaded to the cluster successfully"
I0629 13:23:39.179051  580350 create_cluster.go:135] "Greenhouse manager is deployed successfully"

@IvoGoman  @uwe-mayer  I have updated the files rebasing the main & scoping down to creating local cluster only. It is ready to have another look 👀

⎈ /g/s/g/c/greenhouse > docker rmi greenhouse:e2e-latest
Untagged: greenhouse:e2e-latest
Deleted: sha256:0d48f04c01d1d4fec4e2c16dada00c968101b4ac5d22a8bce19e7d62409f4c71

⎈ /g/s/g/c/greenhouse > kind delete clusters greenhouse-e2e
Deleted nodes: ["greenhouse-e2e-control-plane"]
Deleted clusters: ["greenhouse-e2e"]

⎈ /g/s/g/c/greenhouse > make e2e-local-cluster-create
cd test/e2e/local-cluster && go run .
I0711 11:45:22.514215 2340085 create_cluster.go:82] "configuration loaded" kindClusterName="greenhouse-e2e" dockerImageRepository="greenhouse" dockerImageTag="e2e-latest" dockerImageBuildSkip=false kubeconfigName="e2e.kubeconfig" kubeconfigInternalName="e2e.internal.kubeconfig"
I0711 11:45:39.319226 2340085 create_cluster.go:99] "cluster created successfully"
I0711 11:45:39.555364 2340085 create_cluster.go:127] "kubeconfig exported successfully"
I0711 11:46:23.526305 2340085 create_cluster.go:137] "Docker image built successfully"
I0711 11:46:31.278263 2340085 create_cluster.go:146] "Docker image loaded to the cluster successfully"
I0711 11:46:33.850611 2340085 create_cluster.go:154] "idproxy is deployed successfully"
I0711 11:46:46.652780 2340085 create_cluster.go:162] "Greenhouse manager is deployed successfully"

⎈ /g/s/g/c/greenhouse > export KUBECONFIG=./test/e2e/local-cluster/e2e.kubeconfig
⎈ /g/s/g/c/greenhouse > kubectl get pods -n greenhouse
NAME                                            READY   STATUS      RESTARTS   AGE
greenhouse-controller-manager-bb9756c78-z48lr   1/1     Running     0          23s
greenhouse-kube-webhook-certgen-qf7dq           0/2     Completed   0          23s
⎈ /g/s/g/c/greenhouse >

@uwe-mayer @IvoGoman  fyi

@IvoGoman @onuryilmaz Totally agree on changing the kubeconfig env var to run remote tests against.
See https://github.com/cloudoperators/greenhouse/pull/250/commits/4a8f594a546d973ca2b0b813ac4df03c2caf1ea9
PR is good to go from my side...

authors: onuryilmaz uwe-mayer

repo: cloudoperators/greenhouse


text:
Allow setting monitoring_role_arn

what

Allowed to configure monitoring_role_arn

why

"Error: Error creating DB Instance: InvalidParameterCombination: A MonitoringRoleARN value is required if you specify a MonitoringInterval value other than 0."
Apparenty the ARN must be set, if the monitoring interval is being set

references

closes https://github.com/cloudposse/terraform-aws-rds/issues/61

/readme-rebuild

/rebuild-readme

/terraform fmt

/terraform-fmt

/test all

Looks like a typo in the variable monitorin_role_arn -> monitoring_role_arn

@deiga can you rebase please?

/test all

@deiga look like this has been already added to the module, there is 0 files modified.

@jamengual Yup, seems so.

authors: deiga jamengual nitrocode tibbing

repo: cloudposse/terraform-aws-rds


text:
Update context.tf and github actions

what

Update to context.tf

why

Keep the module up to date

/test all


text:
docs: Hint that strings need not be quoted in ini files

Save future me some time debugging this again :)

@mhutter thx

authors: mhutter resmo

repo: cloudscale-ch/cloudscale-cli


text:
[Bug]: jest test can't run - cannot use import statement ...

Browser
Chrome
Package version
3.0.10
React version
v18.2.0
Description
I'm trying to implement Cloudscape design in a simple React app. The UI runs fine; however when I run Jest tests I encounter a (import ...) bug. Here are my steps to reproduce the issue.

create react app using npx command
install cloudscape components using the following guide
run npm test
get the following error: SyntaxError: Cannot use import statement outside a module

I've tried to create babel.config.js and write certain settings, however to no avail. (as recommended by SO)
Any ideas on how to ameliorate this issue?
Source code
https://github.com/adnjoo/cloudscape-test/
Reproduction
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

I'm running into this issue too and tried using ts-jest with no luck.
https://jestjs.io/docs/getting-started#using-typescript

@18clans Hi I fixed this issue by replacing test with react-scripts test --transformIgnorePatterns 'node_modules/(?!my-library-dir)/ inside package.json

@adnjoo thank you for the fix.

For future peepz: CloudScape has a jest-preset package that takes care of this

jest-preset

Unfortunately if you're using CRA (like OP) this package is not usable unless you eject (which you should never do)

For future peepz: CloudScape has a jest-preset package that takes care of this

Unfortunately if you're using CRA (like OP) this package is not usable unless you eject (which you should never do)

I fixed this issue by replacing react-scripts test with react-scripts test --transformIgnorePatterns 'node_modules/(?!my-library-dir)/ inside package.json.

Note: If you already set transformIgnorePatterns in your package.json, you will need to merge them.
For example:
// Before
"transformIgnorePatterns": [
  "<rootDir>/node_modules/(?!react-merge-refs)"
]

// After

"transformIgnorePatterns": [
  "<rootDir>/node_modules/(?!react-merge-refs|@cloudscape-design)/"
]

authors: 18clans adnjoo lasley reillyjodonnell xuesichao

repo: cloudscape-design/components


text:
UVI Request

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

This issue has been assigned UVI-2021-1001071

repo: cloudsecurityalliance/security-database


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.14.16",
  "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=d3ed72495a59fbfb9377450c8dfe94389a6509a7"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d3ed72495a59fbfb9377450c8dfe94389a6509a7",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "drm/amdgpu: fix out of bounds write\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.14.16 by commit d3ed72495a59fbfb9377450c8dfe94389a6509a7. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002130

repo: cloudsecurityalliance/uvi-database


text:
Support request priority

This PR supports the request priority in command-level and transaction-level.
I added a minimum test, but for full functionality test we need to inspect a real RPC request object using Cloud Spanner Emulator or mock server like spannertest. It requires more effort, so let me do it for future work.
Added feature
Command line option:
 --priority=   Set default request priority (HIGH|MEDIUM|LOW)

Transaction-level option:
# Read-write transaction with low priority
BEGIN PRIORITY LOW;

# Read-only transaction with low priority
BEGIN RO PRIORITY LOW;

# Read-only transaction with 60s stale read and medium priority
BEGIN RO 60 PRIORITY MEDIUM;

# Read-only transaction with exact timestamp and medium priority
BEGIN RO 2021-04-01T23:47:44+00:00 PRIORITY MEDIUM;

The default priority for all request is MEDIUM.
close #109

@apstndb Sorry it's a little bit large PR, but could you have a chance to look at this?

Thanks @apstndb for your review!

repo: cloudspannerecosystem/spanner-cli


text:
Need to include AWS::Cloudformation::Init - commands

See http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html#aws-resource-init-commands
Here is a short snippet.

You can include AWS::CloudFormation::Init in your stacks like this (note the use of python dicts):
https://github.com/cloudtools/troposphere/blob/master/examples/CloudFormation_Init_ConfigSet.py

Thanks, I should have checked that.

repo: cloudtools/troposphere


text:
the demo:flutter-webrtc-demo-master is also crash, on flutter 1.12.13 。Debug is ok ,but release will crash .

Describe the bug
flutter-webrtc-demo-master crash in release, debug is ok .
To Reproduce
Expected behavior
flutter-webrtc-demo-master is also crash Debug is ok ,but release will crash .
Platform information

Flutter version:
flutter 1.12.13
Plugin version:
0.2.2
OS:
Android
OS version:

Fixed https://github.com/cloudwebrtc/flutter-webrtc/commit/4966ab01bf256ce27f9d32b96a4768100e9e664e

repo: cloudwebrtc/flutter-webrtc


text:
UnsatisfiedLinkError

Hello,
While trying out your example app I have ran into a problem. On Android i get the UnsatisfiedLinkError
whole stacktrace:
com.cloudwebrtc.webrtcexample E/org.webrtc.Logging: NativeLibrary: Failed to load native library: jingle_peerconnection_so
    NativeLibrary: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/data/app/com.cloudwebrtc.webrtcexample-zASNzno6_zbJwbicSb0Dpg==/base.apk"],nativeLibraryDirectories=[/data/app/com.cloudwebrtc.webrtcexample-zASNzno6_zbJwbicSb0Dpg==/lib/x86_64, /system/fake-libs64, /data/app/com.cloudwebrtc.webrtcexample-zASNzno6_zbJwbicSb0Dpg==/base.apk!/lib/x86_64, /system/lib64]]] couldn't find "libjingle_peerconnection_so.so"

The app works great on iOS, but I cant get around this on Android. Every suggestion would help.

you need import android/libs/*.jar files

import exactly how? it is in the build.gradle of webrtc module if that is what you mean

@SnowcatSVK
From the log analysis, does not support the x86_64 architecture so, you are using the ARM architecture?
If not, you can apply doc/patchs/m63_patch_for_flutter_webrtc_plugin_v0.patch to recompile webrtc M63 to support x86_64 architecture.

@cloudwebrtc first i tried it on x86_64 emulator and when i saw the logs i have tried it on pixel 2, where i get the same error, only there it said it couldnt find armeabi_v8a, so then i guess i would have to recompile it for both x86_64 and armeabi_v8a?

@SnowcatSVK Yes, you can try to recompile it for both x86_64 and armeabi_v8a(arm64).
Normally, if you run the Android native app, armv7 library can run in the arm64 platform, and x86 library can run in x86_64 architecture. As far as I know flutter is still unable to run in x86 or x86_64 even arm64 platform, you need to exclude the errors caused by it.

ok then, i will try to recompile it and see if that helps, thank you for your time

Could some notes about this eventually be added to the readme ? Ir even better a make file to see how to do this sort of ISA architecture shuffling ?
Just because its quite complex to know what to do on android to get it working in Sim and on real device.

Ok, I will update README.md and add x86_64 and arm64 architecture to the next commit.

@SnowcatSVK We have recompiled this native sdk, support armv7, arm64, x86, x86_64 on android, you can view the latest commit.

@cloudwebrtc Just tested it out and everything works rather nicely, thank you very much for your help

authors: SnowcatSVK cloudwebrtc gedw99 kangshaojun


text:
Migrated to AndroidX using Refactoring from Andoid Studio

Since Flutter 1.1.8 was released, it created a bit of a havoc in the Flutter community because of migrating to AndroidX. AndroidX replaces the Google Android support libraries, which has been an issue because of version compatibility. Here are some of the open issues related to AndroidX support that I came across as someone who uses a lot of Flutter plugins in a single app:
Plugins are broken since move to AndroidX
Plugins do not support AndroidX
Flutter-webrtc happens to be one of the plugins that's causing issues since migrating to AndroidX. While there's an interesting workaround for utilizing non-AndroidX plugin which involves setting android.enableJetifier=true, that workaround is not perfect and it doesn't address the core issue which is the inability of different versions of support libraries to co-exist. The right thing to do is to migrate all Flutter plugins to AndroidX. This commit is exactly that. I performed automatic migration by using the Refactoring method described in this document: Migrating to AndroidX.
I tested my changes by running the example project on iOS and Android.

@aryzhov
Thanks for you PR, I have added you to collaborators. :)

Would it be possible to cut a release of this? ☺
I can't build my app for Android currently since some other plugins I'm using (the first-party Firebase plugins from Google) have migrated...

@LinusU You can always specify git dependency instead of pub
  flutter_webrtc:
    git: https://github.com/cloudwebrtc/flutter-webrtc.git

I can't push to pub, only @cloudwebrtc has permission to do that

authors: LinusU aryzhov cloudwebrtc rostopira


text:
WIP: feat: muxpool supports graceful closing of connections when called Clean

What type of PR is this?
feat
What this PR does / why we need it (English/Chinese):
en: muxpool supports graceful closing of connections when called Clean
zh: 连接多路复用场景，client 端支持连接优雅关闭
Which issue(s) this PR fixes:

The solution moved to #395

repo: cloudwego/kitex


text:
Support json! macro

Is your feature request related to a problem? Please describe.
serde_json has a very convenient macro json!, it's better that sonic-rs provide a similar one too.

Thanks, we will investigate it.

Finished in sonic-rs 0.3.0.

repo: cloudwego/sonic-rs


text:
Use _DEFAULT_SOURCE instead of _BSD_SOURCE

This should fix #13

Added the "time.h" header, since that's what seems to make the build fail.

repo: cloudyourcar/minmea

license: WTFPL


text:
Crie uma rota que retorne o local do evento através do nome do evento

Seu código funcionou para esse exercício? Pois no meu não funcionou ...

Olá amigo. Desculpa. Só pude olhar agora. Meu projetinho tá rodando no Heroku com pipeline automático do GitHub. Dá uma olhada:
https://python-agenda.herokuapp.com/

O usuário é "convidado" e a senha é "user12345" como está no meu README.md

authors: clovisdanielcosta joaopblume

repo: clovisdanielcosta/python-agenda


text:
How to calculate fee with tx size?

How to get the byte count or vSize of a transaction in order to accurately calculate an adequate fee?

Hello. I just updated the library to version 1.2.8. There is now a Tx.getTxSize(txdata) method which will return an object with all the various sizes (base size, vsize, weight, etc.)
Let me know if that works for you!

Awesome! Thank you for the swift update

repo: cmdruid/tapscript


text:
Question: Can the tool be used to generate a select without any conditions?

Hello,
Sometimes there are small tables that I want to load in the memory. Is there a way to generate the type that selects all records from the table, something like - type: select.
Thanks

Not currently. I use these kinds of queries myself, but since they're so trivial (SELECT * FROM TableName), I haven't bothered. But if you want, I can probably add it.

If it's not too much work... I would appreciate if you add it. I am very new to your library, I just started to explore it today (yesterday that is), so off the top of my had I don't know how much boiler plate one would have to write for select * from TableName to give you a more informed answer.

The difference is that instead of having the following in facil.yaml:
- type: selectAll

Then you have an .sql file with the following:
SELECT * FROM TableName

As you can see, there is basically no difference. That's why I'm not sure there's much point in adding it.
Try out the library for a week, and let me know what you think after that. 👍

Thinking about it, there is one difference: With the tableScripts option, the select columns would be explicitly specified (instead of * in the SQL file I showed). That is a good practice. So perhaps I should add it after all. I'll look into it.

Releasing in v2.1.0.

Thank you!
Does version 2.1.0 support .Net 5?

No, from 2.0.0 it's .NET 6 only.

If it is not too much to ask and it doesn't require too much work, could you  please include this feature in the version that supports .Net 5? Right now I am stuck to .Net 5... But I understand if you don't want to do it.
Thanks

Sorry, I simply don't have the capacity to backport stuff. I recommend you transition to .NET 6. It is probably a trivial change; just change net5.0 to net6.0 in your project files and install the .NET 6 runtime or hosting bundle in the environments where you publish your code.

repo: cmeeren/Facil


text:
[Traitement des demandes] - Possibilité d'ajouter un commentaire pendant le paramétrage

Ajouter la possibilité de mettre un commentaire de traitement sur les hôtes et services pour indiquer par exemple

les choix réels de paramétrage si la demande est incohérente.
difficulté rencontré lors du paramétrage
point de blocage...

le commentaire sera ajouté dans le cadre administration en dessous du statut.
le champ sera éditable en permanence (champ de type mémo)


text:
Fix copyright link

Fixes #28

Hi @hubdotcom,
thanks, but could you please also update the link in all the other file headers?

authors: cmfcmf hubdotcom

repo: cmfcmf/OpenWeatherMap-PHP-Api


text:
updates to scala config

changes to the new Olympian diacritic style
changes to the limma-fraction and apotome-fraction EDO notations of the periodic table (adding native fifth notations for 9, 20, 25, 28, 30, 32, 33, 35, 37, 40, 42, 44, 47, 52, 54, 59, 61, 66, 71 and changing existing native-fifth notations for 10, 16, 21, 23, 27, 49, 51, 58, 68)
various corrections
uses the 809EDA boundaries for the JI notations instead of 233EDA
uses the new Short ASCII representations of symbols

I have tested these changes in Scala and to the best of my understanding believe they work as expected.

Merged externally.

repo: cmloegcmluin/sagittal-calculator


text:
Control Hint Uses Default Keybind

The control hint for the emote radial menu on session start shows the default keybind and not the configured keybind.
TooManyEmotes version: 1.7.19

Interesting. Let me see if this part hasn't been updated since I started supporting inpututils. I will check on this when I get home, thanks!

I'm going to remove this from the HUD for the next patch, but I will bring it back in the next one. The fix won't be hard, so it will return the next update!


text:
Fix uploading the EventSetup conditions from multiple streams

When multiple CUDA streams are trying to initialise the same EventSetup object, the first one to do
so starts the asynchronous operations, and the others are supposed to wait for it to finish.
However, code for recording the CUDA event was missing, so the other streams would find the default-
constructed event, which is always "valid".
Adding the missing call to record the event fixes the problem.

Fixes #188

The same fix seems to be working fine also in CMSSW (see e.g. https://github.com/cms-sw/cmssw/pull/34725).

repo: cms-patatrack/pixeltrack-standalone


text:
Minor update to delphi_utils tests

Description
While working on #1685, I thought there was an issue with county zero padding. Turns out I was wrong, but I figured we can add the tests I wrote, so others don't have the same doubts later.
Changelog

add a county with zero padding to test_archive
adjust spacings for readability in test_archive
remove manual temp_dir in test_export and use pytest tmp_path

I'm thinking the county test is probably worth it.

repo: cmu-delphi/covidcast-indicators


text:
Consider using -mavx rather than -mavx2 in build.sh's build of meow_bench

-mavx -maes is fine on both Linux/clang++ and Linux/gcc++.
-mavx2 doesn't seem to actually emit avx2-specific code on clang8, or meow_bench is getting lucky. :)
But -mavx2 prompts GCC to emit code that genuinely needs avx2 (and will crash on avx1-only), which seems surplus to the requirements of the actual meowhash implementation.

We cannot use -mavx for meow_bench because if you want to actually benchmark against other hashes (which we ourselves always do), some of them do not get optimal performance without -mavx2.  The requirements for Meow Bench will only get more stringent, since we will release newer, more modern optimizations of Meow Hash over time, and Meow Bench is for testing the fastest possible path.
- Casey

authors: adamdmoss cmuratori

license: Zlib


text:
[Spanish] localize 'Policy as Code (PaC)'

Localize the content/en/policy-as-code.md document to Spanish

Hey @electrocucaracha, I would like to work on it. Can you please assign it to me?

repo: cncf/glossary


text:
Taylorwaggoner kcsps

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 250 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)?
[ ] ~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"?

Deploy preview for landscape ready!
Built with commit de528d4b84afced9e712094d277e2d4f0d3395a4
https://deploy-preview-1059--landscape.netlify.com

LGTM

authors: CNCF-Bot taylorwaggoner

repo: cncf/landscape


text:
Automation of tag-app-delivery repo

There is discussion amongst the platforms-wg slack to automate the tag-app-delivery repo. Ideas are to use (one of) Prow, Github Actions, etc. Will update this GH Issue after we talk about it in detail in the WG Meeting.
Note: This carries over the conversation from this slack thread:
https://cloud-native.slack.com/archives/C020RHD43BP/p1707944806442839

WG Meeting Notes:
Collect automation needs across the TAG
Some ideas mentioned:

Action for translation alert, awareness
Assignment of issues and prs

I would love to add good first issue label to this one as I think it is concrete and focused for pick up. Do you think we should try to clarify the needed actions more in this issue or create associated issues that are clear and easy to be picked up?

I would love to add good first issue label to this one as I think it is concrete and focused for pick up. Do you think we should try to clarify the needed actions more in this issue or create associated issues that are clear and easy to be picked up?

Yes, I think opening this up as a good first issue without something more specific would make this harder for people to pick up.

authors: abangser olivercodes roberthstrand

repo: cncf/tag-app-delivery


text:
Grant access to QLS workgroup leads

Grant write access to QLS workgroup leads Chris Larsen and Vijay Samuel.

Invite sent. @manolama @vjsamuel pl accept the invites.

@manolama and @vjsamuel can you confirm this is resolved? If it is, I will close the issue

Ah yeah it is resolved now, so safe to close. Thanks!
On Mon, Oct 16, 2023 at 11:32 AM Ken Finnigan @.***>
wrote:

@manolama https://github.com/manolama and @vjsamuel
https://github.com/vjsamuel can you confirm this is resolved? If it is,
I will close the issue
—
Reply to this email directly, view it on GitHub
https://github.com/cncf/tag-observability/issues/114#issuecomment-1765063844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKQLJBDJRXT6XZNJQBGHN3X7V4TLAVCNFSM6AAAAAA27H26FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGA3DGOBUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sincerely,
Chris Larsen

authors: alolita kenfinnigan manolama

repo: cncf/tag-observability


text:
Composer.lock file should be in git repo

Just messing around with Canvas tonight and pulled in the latest version from the develop branch. I saw the commits showing Barryvdh Debugbar. As such, I did a composer install to update any packages that might be missing. Surprisingly I did not see Barryvdh Debugbar being installed and a php artisan config:cache throw errors on Barryvdh Debugbar based on the configuration inside config/app.php.
Based on this StackOverflow comment, I think we should just let the composer.lock file remain inside the repo. This should apply to future package updates that come along with each Canvas update.

PR Merged in #336. Closing this.

repo: cnvs/canvas


text:
README.md: Add about section

Closes https://github.com/coala/corobo/issues/228
Reviewers Checklist

[ ] Appropriate logging is done.
[ ] Appropriate error responses.
[ ] Handle every possible exception.
[ ] Make sure there is a docstring in the command functions. Hint: Lookout for
botcmd and re_botcmd decorators.
[ ] See that 100% coverage is there.
[ ] See to it that mocking is not done where it is not necessary.

@refeed PTAL?

@refeed PTAL

ack 23505873

@rultor merge

@rultor merge

@meetmangukiya OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@meetmangukiya Done! FYI, the full log is here (took me 2min)

authors: meetmangukiya rultor

repo: coala/corobo


text:
The Link in the footer of the demo site has a missing letter

Hi
The link in the footer of the demo site that goes to your github is broken.
Where you have "Template developed by Jacobo Martínez" it links to https://github.com/covidev
I.e. it's missing the "b" in your username
Paul

Hi Paul! Hope you're doing well.
Thank you for notice that 🙌
Commit: https://github.com/cobidev/simplefolio/commit/0f73e845f9edde41eaeae59f4e5405e8201286fc

authors: cobidev pvptowers

repo: cobidev/simplefolio


text:
Load balancing in Kubernetes deployment

Our Kubernetes config defines a service for load balancing client traffic: https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/bring-your-own-certs/cockroachdb-statefulset.yaml#L60
In the SQL shell step of our Kubernetes tutorial, we point the shell at that load balancer (--host=cockroachdb-public). But we never explicitly mention anything about the load balancer and that client traffic should use it.
In contrast, in all of our manual deployment docs, we are very explicit that a load balancer is important, e.g., https://www.cockroachlabs.com/docs/stable/deploy-cockroachdb-on-google-cloud-platform.html#step-4-set-up-load-balancing.
We should find a way to explicitly mention load balancing in the Kubernetes deployment docs.

Load balancer for the Operator: https://github.com/cockroachdb/cockroach-operator/blob/c8490eff8f9aca5d5bc5fccbd68a308715f32f7d/pkg/resource/public_service.go
For Helm deployments: https://github.com/cockroachdb/helm-charts/blob/eca29c95a1d3e2edccc28530f684841ef8f0c606/cockroachdb/templates/service.public.yaml

authors: jseldess taroface

repo: cockroachdb/docs


text:
PR #93644 - sql: enhance SHOW RANGES (2 of 6)

Exalate commented:
Related PR: https://github.com/cockroachdb/cockroach/pull/93644
Commit: https://github.com/cockroachdb/cockroach/commit/e67d2fd95546fb5af9e765a5cde1ae597f357373

Release note (backward-incompatible change): The format of the
columns start_key and end_key for SHOW RANGES FROM DATABASE
and SHOW RANGES FROM TABLE have been extended to include which
table/index the key belong to. This is necessary because a range
can now contain data from more than one table/index.
Jira Issue: DOC-6470

NB: The new behavior will be opt-in in v23.1, and the old behavior becomes deprecated.
See: https://github.com/cockroachdb/cockroach/pull/98979

knz @.***> writes:

NB: The new behavior will be opt-in in v23.1, and the old behavior
becomes deprecated.
See: cockroachdb/cockroach#98979

Thanks knz!!!  Appreciate the heads up
FYI the autogenerated docs issue for the change in
cockroachdb/cockroach#98979 is DOC-7311, which I will work on as part of
the larger tracking docs issue DOC-6732 for v23.1

authors: cockroach-teamcity knz rmloveland


text:
Better make buildoss command

From the forum:
You can make "portable binaries" with the following command:
build/builder.sh make buildoss TYPE=release-linux-gnu

@knz If you think we should integrate this into the docs, please leave open, otherwise, glad to have this closed.

I think it's a good idea.

Yes, we should document both the buildoss target and the portable build methods somewhere (only TYPE=release-linux-gnu or should we document TYPE=portable too?)

We added a callout about buildoss: https://www.cockroachlabs.com/docs/stable/install-cockroachdb.html (build from source).

authors: bdarnell jseldess knz sploiselle


text:
Docs of the week (March 11)

https://docs.google.com/spreadsheets/d/1kNZwNqhjR75qgQUQJo9wLJdGBPswRV991wU6dlFrpp4/edit#gid=0

On CockroachCloud, your CockroachDB cluster is automatically upgraded to the latest stable version, and other administrative actions are handled for you as well. Find out more in our docs.

https://www.cockroachlabs.com/docs/cockroachcloud/stable/cockroachcloud-upgrade-policy.html

Want to change a table's primary key without interrupting data access? CockroachDB's upcoming v20.1 release lets you do that. Use a beta release to test it out.

https://www.cockroachlabs.com/docs/dev/alter-primary-key.html

In a distributed SQL database like CockroachDB, it's important to understand how reads and writes are routed and coordinated behind-the-scenes. This doc is a good introduction.

https://www.cockroachlabs.com/docs/stable/architecture/reads-and-writes-overview.html


text:
stop should wait for processes to exit

stop should wait for the processes to exit in order to prevent the caller from running into problems with restarting cockroach too quickly before the previous cockroach has released OS file locks. Something along the lines of:
while $(kill -0 $PID 2>/dev/null); do
  sleep 1
done

This is somewhat complicated by the fact that roachprod stop supports sending arbitrary signals, but I guess we don't really care about supporting roachprod stop --signal SIGHUP.

We could also condition that waiting on the signal being sent (i.e. only wait for a small set of whitelisted signals). Or add a --wait flag (default false) so that you can do roachprod stop --signal SIGHUP --wait false.

I like the wait flag idea. With the exception of SIGKILL you can’t be
assured that the process will exit in any kind of timely fashion. And if
I’m not mistaken roachprod stop is also used to stop things that are not
cockroach?
On Thu, Oct 18, 2018 at 9:47 AM Peter Mattis notifications@github.com
wrote:

We could also condition that waiting on the signal being sent (i.e. only
wait for a small set of whitelisted signals). Or add a --wait flag
(default false) so that you can do roachprod stop --signal SIGHUP --wait
false.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/roachprod/issues/219#issuecomment-431014974,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA15ICFgZrlkrGVCXAzvVuzs9WPsSMFmks5umIZigaJpZM4Xtd5Q
.

Yes stop sends a signal to all processes with the ROACHPROD=%d env var.

I'm taking a crack at this. Rather than kill -0, I think we can loop looking for processes with the ROACHPROD=%d env until there are none left.

authors: benesch petermattis

repo: cockroachdb/roachprod


text:
enableShadow with arguments make the title of a button invisible

var title = button.getTitleRenderer();
button.setTitleColor(cc.color.RED);
//title is invisible
title.enableShadow(cc.color.BLACK, cc.p(2.0,-2.0));

//this is ok
//title.enableShadow();

fixed in #1370