text:
Use App configuration as default configuration for the project

Latest change still doesn't seem to work on my side. Create a fresh clone of the project directly via command line, checked out this branch, then opened in AS EE Canary 9, and after sync finished app-nia-catalog was still the first entry in the run configuration.

Can you try one more time?
Steps to reproduce:

Fresh clone of the project
Open Android Studio, File > New > Import project...
Your project should have 2 configurations, app and design catalog

Result with the latest changes:

Fresh clone, checkout this branch
Open project
While project is syncing, the 2 configurations are app and design catalog, with app selected
Once syncing completes, there are 3 configurations: app, design catalog and app-nia-catalog, with app-nia-catalog selected

Just retested this and had the same result as @alexvanyo. app-nia-catalog is the default run configuration.

Closing due to inactivity

authors: JolandaVerhoef alexvanyo dturner mmoczkowski

repo: android/nowinandroid


text:
wip! update to use application builder by default

Would you mind explaining the relationship between the new-ish @angular-devkit/build-angular:browser-esbuild, and the brand new @angular-devkit/build-angular:application ?
I was under the impression that @angular-devkit/build-angular:browser-esbuild would eventually replace the old @angular-devkit/build-angular:browser. But that now that @angular-devkit/build-angular:application has been released in developer preview, I am a bit confused. Does @angular-devkit/build-angular:application  somehow uses @angular-devkit/build-angular:browser-esbuild under the hood ? or will @angular-devkit/build-angular:browser-esbuild be replaced by @angular-devkit/build-angular:application even before being getting promoted as generally available ?

Under the hood the @angular-devkit/build-angular:browser-esbuild uses @angular-devkit/build-angular:application, The browser-esbuild is a compatibility layer as it is used to normalize several options to be compatible with the browser builder to allow users to switch back and forth between an esbuild and webpack based builders without changing much in builder configuration.
The application builder will replace the browser-esbuild. This builder has additional functionality which is not exposed via the browser-esbuild builder such capabilities to generate an app-shell, ssr and prerendering application. Hence, this will replace and the remove the need for the prerender, server and app-shell builders.

source: gharchive/pull-request

repo: angular/angular-cli

license: MIT

license_type: permissive

license_source: github-api


text:
maint: Update conf.py

This fixes the issues you were seeing with the enums @rchopade7

repo: ansys/pyprimemesh


text:
Update README.md

Codecov Report

Merging #135 (632398c) into main (bf4d4b2) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #135   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          612       612
  Branches        50        50
=========================================
  Hits           612       612

Continue to review full report at Codecov.

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

authors: antonagestam codecov-commenter

repo: antonagestam/phantom-types


text:
ARROW-16185: [C++] Fix uninitialized output data in strptime kernel

@github-actions crossbow submit test-conda-cpp-valgrind

@github-actions crossbow submit test-r-linux-valgrind  test-ubuntu-18.04-r-sanitizer test-fedora-r-clang-sanitizer

On my computer, the Python benchmark posted on ARROW-11989 goes from this:
Time to access example at i=0%	: 5.3μs
Time to access example at i=10%	: 4.0μs
Time to access example at i=20%	: 5.5μs
Time to access example at i=30%	: 7.1μs
Time to access example at i=40%	: 8.6μs
Time to access example at i=50%	: 10.0μs
Time to access example at i=60%	: 12.8μs
Time to access example at i=70%	: 13.6μs
Time to access example at i=80%	: 15.2μs
Time to access example at i=90%	: 16.8μs

to this:
Time to access example at i=0%	: 4.3μs
Time to access example at i=10%	: 1.8μs
Time to access example at i=20%	: 1.7μs
Time to access example at i=30%	: 1.6μs
Time to access example at i=40%	: 1.6μs
Time to access example at i=50%	: 1.4μs
Time to access example at i=60%	: 1.6μs
Time to access example at i=70%	: 1.7μs
Time to access example at i=80%	: 1.9μs
Time to access example at i=90%	: 1.9μs

authors: jonkeane pitrou

repo: apache/arrow


text:
JAMES-4888 FILTER: forward loop issue

Tests should be way easier to read.
I did let a few comments on how to achieve this.

Needs a rebase though :)

I have pushed a new commit to resolve some issues

JMAPFilteringTest is failing on this branch.
I let you debug it...

Fixed JMAPFilteringTest issue
Simplified the overall handling by tracking only recipients that are converted to forward. This is easier to do if the localCopy is done with the forwarded mail.
Misc code style improvments based on earlier remarks.

Also please fix ticket number: JAMES-4448 is NOT a valid JIRA...

IMO could be closed in favor of https://github.com/apache/james-project/pull/1762

authors: Arsnael chibenwa hungphan227

repo: apache/james-project


text:
Try fixing eval of non-ascii URI for windows native executable

I think the issue here is that Path.of("日本语.pkl") is turning into path ???.pkl on Windows.
This is throwing:
https://github.com/apple/pkl/blob/8b0118fec5d62da0f0949b59c9feb759a0c9afbd/pkl-commons-cli/src/main/kotlin/org/pkl/commons/cli/commands/BaseOptions.kt#L52
Not sure why we're getting a bunch of question marks, though.

@bioball The main branch builds fine for me.
Otherwise you'd have heard from me already. :-)
On my laptop, the ??? seems to be a terminal encoding issue:
jshell> Path.of("日本语.pkl").toString()
$13 ==> "???.pkl"

jshell> $13.equals("日本语.pkl")
$14 ==> true

@bioball Please ignore my earlier (now deleted) comment. I'm getting the same error as CI.
I don't know more yet, but I'll investigate a bit.

This looks much like: https://github.com/oracle/graal/issues/8593
The solution described here makes gw testNative pass on my laptop:
https://github.com/oracle/graal/issues/8593#issuecomment-2009163353
Not sure what this means for Pkl's CI build.

Looks like we're blocked by the GraalVM folks on this.

In the meantime, you could try to find a different solution. For example, you could try chcp 65001. But from what I read, this should already be enable on GitHub runners. Probably there's also a registry equivalent of "Enable experimental UTF8 support", which solved the problem for me.

I'll give that a shot, but if that doesn't work, I'm not going to spend too much time debugging this one.

I think that every Java app running on Windows faces this issue, not just Graal native images.
Until I enabled experimental UTF8 support, I'd get scrambled output from spotless, JMH, etc.

The same test is passing in our JVM-based language snippet tests on Windows, so, it seems to be working at least when not in native-image.

The same test is passing in our JVM-based language snippet tests on Windows,

That's because JVM based snippet tests don't pass filenames as command line arguments, which is where the problem lies.

Hm, interesting.
I'm merging this for now. I think we can re-visit this again when that issue has been resolved, but if you have any other ideas what what to try in CI, I'm happy to fire up another PR just for testing purposes.

authors: bioball translatenix

repo: apple/pkl


text:
Check which execute actions can be run in parallel for Performance Infra Dashboard

@Rhitottam is this about the execute action or about the perf infra dashboard. Please add some desc for clarity!

source: gharchive/issue

authors: Rhitottam somangshu

repo: appsmithorg/appsmith


text:
请问有图表组件吗

没有的

推荐百度的 ECharts

authors: 987603843 LuckyHookin kirazxyun

repo: arco-design/arco-design-vue


text:
最新データが取得できていないバグの修正

取得できていない場合
https://github.com/asha-ndf/omu-covid19-chart/runs/7861277793?check_suite_focus=true#step:3:23
取得できた場合
https://github.com/asha-ndf/omu-covid19-chart/runs/7871767113?check_suite_focus=true#step:3:24

対応完了を確認しました
https://github.com/asha-ndf/omu-covid19-chart/actions/runs/2926680065


text:
Update Composer dependencies (2022-05-06-00-11)

Visual regression test passed!
View the visual regression test report

repo: ashaal/elrom


text:
好像还不支持多个key轮询？

No description provided.

此依赖提供基本功能，复杂的功能实现，此依赖不提供。
当然扩展实现多个key轮询也很简单，在你的项目中引入此依赖，使用自定义扩展的openAiProxyService，初始化项目时，构建全局多个key和service的关系，再写一个策略，调用服务时自定义获取key对应的service的策略就好了。

authors: asleepyfish harryyhy

repo: asleepyfish/chatgpt


text:
Update style.css

add screenshot of the changes


text:
Revert "Remove deep copy from bundle (#597)"

/hold

/approve
/lgtm

/unhold

authors: TerryHowe jonahjon

repo: aws/eks-anywhere-packages


text:
saim

Saimakin@saimakin.info

repo: ayvazjet/github-slideshow


text:
dperf支持分布式吗？

请描述更详细些

多dperf的客户端和服务端模式下那种，有总的控制或者汇总统计那样

没有；文档里没有秒数的功能，就是没有。

repo: baidu/dperf


text:
Feat/spacing viewports

:rocket: Welcome to Baloise ChatOps based GitOps Bot :tada:
- If you want to enable preview environments for this PullRequest, comment with `/preview`.
- If you want to disable the preview environment for this PR, comment with `/undeploy`.
- If you need help or want to see the docs, comment with `/help`.

Make sure to refresh this page after submitting a command.
Preview environments can be redeployed automatically if you enable the webhook for updates to the source branch. :new:

Have fun building awesome apps! :hammer:  :whale2:  :truck:  :ship:

repo: baloise/design-system


text:
add disclaimer pop out

The security warnings are related to noopeners on the gov links. We don't need them in that case so we can let it slide. Feel free to add them if you want but I dont think it's required in this case

authors: dhlevi yzlucas

repo: bcgov/nr-bcws-wfnews


text:
datetime.utcnow() will be deprecated

Hi @bebleo
I know #337 is not fixed yet and  #342 not merged yet, but would you consider releasing the main branch as it is, so everyone would at least benefit from this patch and make their testsuite more quiet? :pray:

Thank you! :heart:

authors: azmeuk bebleo

repo: bebleo/smtpdfix


text:
Circle vs Circle collision with friction applying rotation

Reference - https://www.euclideanspace.com/physics/dynamics/collision/twod/index.htm
See subheading "Collision in 2 dimensions (with rotation no friction)"

See also - https://www.cs.ubc.ca/~rhodin/2020_2021_CPSC_427/lectures/D_CollisionTutorial.pdf
See subheading "How to solve a (single) collision"

repo: bendapootie/neurons


text:
Cleanup GeometryTree#fromModel

Technically this is breaking, but I'm gonna push it anyway into the 1.20.6 release
I'll get Kyo's thing while we're there

repo: bernie-g/geckolib


text:
En tant que déclarant, je dois pouvoir télécharger/ transmettre un récap de mon dossier après l'avoir soumis

Actuellement le déclarant imprime sa déclaration pour conserver une trace.
La façon de faire n’est pas la même d’un moteur de recherches à l’autre.
Ce n’est pas optimisé
proposition 1 : (privilégiée)
Faire un bouton pour exporter en PDF sa déclaration
proposition 2 :
Faire un bouton pour envoyer la déclaration par mail

Dans ce cas l'idéal serait que l'application permette l'impression d'une déclaration formatée correctement pour l'affichage papier - et donc du PDF.
Dans les fenêtres d'impression on a l'option « sauvegarder en tant que PDF », par exemple, si j'essaie d'imprimer cette page :

Pour moi la feature pourrait être que la page imprimée soit adaptée et contienne toute l'information nécessaire de la déclaration. Elle ne devrait par exemple pas contenir le header ou le footer de l'application ni les boutons car pas pertinent dans un contexte papier. Donc la page qu'on voit dans le dialog d'impression ne serait pas être la même que celle qu'on voit dans le navigateur.
Un exemple assez basique c'est cette page démo.

authors: Fantine-py HeleneDubourdieu alemangui

repo: betagouv/complements-alimentaires


text:
updated male css

by sree

repo: binitworld/Shop-Sphere


text:
https://share.bitdefender.com/s/9D4bBE7H8XTdYDB.     can not open

Don't use the dot at the end please, it looks like it is working https://share.bitdefender.com/s/9D4bBE7H8XTdYDB (I don't know if there were any other connectivity problems recently with the sharing platform). Thank you!

repo: bit-ml/AnoShift


text:
Make it more clear what is server and what is client

https://github.com/bjartnes/http-workshop/commit/99e3936efc0ee2ba9cf8c94ae0bcb0dc1798a0b7

repo: bjartnes/http-workshop


text:
added pt_br

What about european portuguese (pt_pt)? Can this language file be used for that as well?

What about european portuguese (pt_pt)? Can this language file be used for that as well?

No, there are many differences between pt-br and pt-pt, commonly those who use pt-pt are angry with pt-br... so it's better not to


text:
Netznutzungsabrechnungsdaten sollen in Marktlokation enthalten sein

@hf-kklein Woher kommt die Anforderung?

authors: hf-fvesely hf-kklein


text:
support proxy

implemented with 3fc4cf2320a857f44042d3997eab3806460c2bd2

repo: bodsch/ansible-postfix


text:
警告通りに --production=falseから--omit=dev に変更

オプションの使い方間違い。一旦今のまま

repo: boushi-bird/eiketsu-deck


text:
update settings

Codecov Report
Patch and project coverage have no change.

Comparison is base (f69f441) 82.84% compared to head (6b186cd) 82.84%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   82.84%   82.84%
=======================================
  Files          22       22
  Lines         542      542
=======================================
  Hits          449      449
  Misses         93       93

Flag
Coverage Δ

tests
82.84% <ø> (ø)

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

Files Changed
Coverage Δ

core/settings.py
96.87% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
get images from brainart SIG 2022

http://brainhack.org/global2022/gallery/


text:
Upgrade to go-tools v0.8.0

The upgraded linter will catch more violations that will have to be remediated. This expands the scope of this change beyond what might be considered a "good first issue." Assigning to myself.

repo: brigadecore/brigade-cloudevents-gateway


text:
Breaking proto changes

Pull Request Test Coverage Report for Build 9356097723
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 1.201%

Totals

Change from base Build 9278024109:
0.0%

Covered Lines:
166

Relevant Lines:
13822

💛  - Coveralls

authors: bstoll coveralls

repo: bstoll/gnoi


text:
Save chart data to URL

Closed via 826be0c

repo: bvaughn/planner


text:
juno.py: No clone_osc when writing juno voices.

Thanks dan!!

repo: bwhitman/amy


text:
feat: Support NestJS 9.0.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant DanKoPrecise

repo: camunda-community-hub/nestjs-zeebe


text:
Publish a release to maven central

done

repo: cardano-foundation/merkle-tree-java


text:
Update Composer dependencies (2024-12-21-00-11)

Visual regression test passed!
View the visual regression test report


text:
fix: return right after error response on GetUserInfo

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@frankurcrazy good PR! Can you also tell me which bug this issue causes?

Perhaps still getting status 200 even if GetUserInfo failed.

authors: CLAassistant frankurcrazy hsluoyz

repo: casdoor/casdoor


text:
UCO Issue 632: Migrate software properties of operating systems into new objects; add relationships

This PR is ready for review and merge.

Note that in response to UCO Issue 632, some of the examples were updated to move observable:OperatingSystemFacets off of observable:Devices, because in each case a SoftwareFacet needed to be populated.  I also moved core:name out of the OperatingSystemFacet and SoftwareFacet, and instead directly onto the OperatingSystem object.

repo: casework/CASE-Examples


text:
Update Terraform to 0.6.2

Looks like @milkcocoa was 4 minutes quicker than me in: #13062 :D

repo: caskroom/homebrew-cask


text:
hermes.rb: updated vendor comment

Merged as aacf3e1c3f7839b40fd8919ffb789e176b40be51.


text:
Add tests for TransactionDetailsCard

@valfaro123 please provide estimation :)


text:
test(coverage): ✅ increase coverage

[sc-234] completes as well

repo: cesarnml/waka-shortcut-time-stats


text:
Fix snapshot timestamp

Would u be able to add a test for this change

Well, I tried something simple, since the tests are looking a little bit weird to me. But I'm afraid I don't have time for anything more complex.

Closes #691.

authors: Andarist jakubmazanec

repo: changesets/changesets


text:
I added the video link to the CHAOSS working groups

Hi @geekygirldawn could you please review this? Thank you

@frontEndDoctor  Thanks so much. Let me know when you will be free for the recording so I can book a slot for you.
We normally use Fridays and Mondays or Weekends, Anyone that works for you.

I will be re-assigning this issue, thanks @frontEndDoctor  for your effort in working on this

authors: frontEndDoctor peculiaruc

repo: chaoss/education


text:
Added support for combined character classes (using ',')

I don't think this actually works yet.
For example, if I add the following test cases:
        [TestCase("minlength: 8; required: lower,upper; required: digit",
                  "aaaaa333")]
        [TestCase("minlength: 8; required: upper; required: digit",
                  "BBBBB444")]

to PasswordMatchesRuleTests.MatchesRule() and:
        [TestCase("minlength: 8; required: lower,upper; required: digit",
                  "11111111")]

to PasswordMatchesRuleTests.DoesNotMatchRule(), then this one fails:
Test | Duration | Traits | Error Message
-- | -- | -- | --
MatchesRule("minlength: 8; required: lower,upper; required: digit","aaaaa333") Failed | 24 ms |   | Expected: True   But was:  False

…and I think the other two only succeed incidentally.

Shouldn't the first two be one rule that is OR-combined?

(This relies on my assumption that ,-combining means OR. It's not 100% clear to me if that's Apple's intent.)

authors: chucker ricardoboss

repo: chucker/PasswordRulesSharp


text:
Add flag --filter-trace-only-bpf to trace only BPF (TC/XDP) progs

@sachintiptur Yep, go for it. Thanks.

repo: cilium/pwru


text:
[CU-868ahguw7] Fixes model not included in showcase collection when creating/updating

Task linked: CU-868ahguw7 Adding a Collection Using the Showcase Collection Feature in Model Details Does Not Add the Model to Selected Collection

authors: JustMaier manuelurenah

repo: civitai/civitai


text:
feat: Driver crate refactor for FaultDisputeGame

Current dependencies on/for this PR:

main

PR #6

PR #7   👈

This comment was auto-generated by Graphite.

repo: clabby/op-challenger


text:
Update project README's to 1.6

I did not realise I should have run ./render.hs. The README update is only user-visible starting with PR #17.

Didn't the CI check fail?

My bad then in understanding what @leonschoorl said with regards to the status of the CI.

repo: clash-lang/stack-templates


text:
First try at a meson-based build

This is stuck because I don't understand enough about how meson actually works to know how to debug the builds.

repo: climlab/climlab-rrtmg


text:
Update README.md

already in the list

repo: cloudcommunity/Free-Certifications


text:
chore: fix compile markdown.entry.ts

This PR has been reverted because it broke  marketplace-publish job actions/runs/7061200934

authors: cnblogs-dudu laggage

repo: cnblogs/vscode-cnb


text:
Sync with repo version

Sure thing - see #110


text:
import: Add best practices/tradeoffs of using IMPORT vs INSERTs

cc: @kathancox  @mwang1026 for visibility

repo: cockroachdb/docs


text:
Propageted i18n

Thank you, @nixel2007

glad to help :)

repo: codecombat/codecombat


text:
add favicon in calculator

Good

authors: Prathamesh-Dukare codersalman


text:
chore: add volunteer EmmanuelOmoiya

Thanks @EmmanuelOmoiya for volunteering. Added few comments

authors: EmmanuelOmoiya codewithvoid

repo: codewithvoid/AskDevs


text:
WIP: Rerender after global pinning changes

Wait for outcome of https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5685


text:
use a command instead of label to run benchmark.

\easy-benchmark

Codecov Report

Merging #483 (5029693) into main (565d1ce) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #483      +/-   ##
==========================================
- Coverage   61.09%   61.07%   -0.02%
==========================================
  Files          85       85
  Lines       12416    12416
==========================================
- Hits         7585     7583       -2
- Misses       4831     4833       +2

\easy-benchmark

\easy-benchmark

\easy-benchmark

!github easy-benchmark

or can we just use a manual trigger like this?
https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow

or can we just use a manual trigger like this? https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow

That's a good idea but I think it is better if there is a history by comments or else.

!github easy-benchmark

!github easy-benchmark

I found out it seems the issue_comment trigger doesn't activate before merging. I tried to merge it into the main branch in my forked repository and tried it, and it worked.
comment
https://github.com/utam0k/youki/pull/10#issuecomment-974739328
and work
https://github.com/utam0k/youki/runs/4276125789?check_suite_focus=true

@tommady Can I ask you to review it?

authors: codecov-commenter tommady utam0k

repo: containers/youki


text:
add doravota ibc channel: cosmoshub, nolus, coreum

@JeremyParish69 Hi, We have new ibc channel that need to be merged ASAP, thanks!

repo: cosmos/chain-registry


text:
Use @distube/ytdl-core

Works really well

Thank you!

authors: CoocooFroggy IIyn emlazzarin

repo: crackodille/evobot


text:
fix: update translation in 4.8

Thanks ❤

authors: CYL-collab mancuoj

repo: csfive/composing-programs-zh


text:
[fix] Typo in redirect, Add sponsors

@hqasmei can you please rebase this branch with beta and resolve the above conflicts?

on branch beta
git pull origin beta
git checkout fix/links
git rebase -i beta
in vim, type :wq
resolve conflicts in your editor (VSCode, etc)
either click "Continue" in VSCode or run git rebase --continue in your terminal
git push -f origin fix/links

@danstepanov thanks just did it

@hqasmei Also, can you reduce the white space here on mobile?

authors: danstepanov hqasmei

repo: danstepanov/create-expo-stack


text:
Fix typo in Quickstart doc

@nathanjmcdougall Hi. Thank you for your contribution. Please change the target branch from master to dev.

Done, thanks.

@nathanjmcdougall Hi. I think you are still branched from master. Please, rebase to dev.

I'm going to open a separate PR with dev as the base.

license: Unlicense


text:
Migration: change current edit links to be share infrastructure with stack trace edit links

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.

repo: dart-lang/sdk


text:
Add Prometheus Layer support so that users can use prometheus client instead

can we pass a registry parameter to the prometheus layer? so it can easier to integrate with the caller's prometheus config.

can we pass a registry parameter to the prometheus layer? so it can easier to integrate with the caller's prometheus config.

Seems interesting.
I know litter about rust-prometheus's API now so I don't know if we can. But I will take this into consideration.

After a quick look on rust-prometheus docs, I found allowing user-input registry is required.
We will implement it. @flaneur2020

Is this issue work in progress?
RisingWave used to implement it's monitoring system 1.0 via rust-prometheus and grafana dashboard, which include some basic metrics for storage. If no one is assigned , I'd like to try it.

Can you describe the requirements in detail?

PrometheusLayer should be exactly the same with MetricsLayer, the only difference is all metrics are sent via promethues handler.

I saw that there are already MetricsHandler in layers, do you want users to be able to observe these metrics or add more metrics?

PrometheusLayer and MetricsLayer are different layers that users can enable one of them or at the same time.

For observation, I prefer to introduce grafana dashboard to monitor these metrics, just like Tikv or RisingWave;

Great! PrometheusLayer or MetricsLayer are built for this. It may be a good idea to include a grafana template json in our docs for our users to get started.

for more detailed metrics, may add some metrics for the basic operations on object, eg. op_latency, op_count, object_size.

Latency and count are already covered. And we have opendal_bytes_total for read & write, maybe that enough?

Thanks for @wcy-fdu 's work, this issue has been implemented.

authors: Xuanwo flaneur2020 wcy-fdu

repo: datafuselabs/opendal


text:
Fixes for studentview

Ser om allt brinner ner nu...

repo: datasektionen/ddagen


text:
Disable Lint/MissingSuper rule

Closing in preference of https://github.com/davidrunger/runger_style/pull/18 , to which I have cherry-picked this PR's commit.


text:
Divide epoch manager

@Mackyson
とりあえずEpochManagerを分離して最低限の機能だけつけたので共有します．基本的なAPIは以下の5つです．たぶん今回の実装で必要なのは後半3つで，ScanがCreateEpochGuardを，Write/Update/DeleteがGetPortectedEpochsを，B木内で動かすエポック用スレッドがForwardGlobalEpochを呼び出すことになると思います．

GetCurrentEpoch: 現在のグローバルなエポックの値を取得する．
GetMinEpoch: 保護されているエポックの中で最小の値を取得する（GetCurrentEpoch() >= GetMinEpoch()）．
GetProtectedEpochs: 保護されているエポックの配列をshared_ptrとして取得する（重複排除済みかつ降順でソート済み．なお参照のみで中身の変更不可）．最初の要素として現在のエポック値（GetCurrentEpoch()）が含まれる点に注意．
ForwardGlobalEpoch: 現在のエポックおよび保護中のエポックリストを更新する．
CreateEpochGuard: 現在のスレッド用にエポックの保護を開始する．

補足としては，前述したようにGetPortectedEpochsは現在のエポック値を最初の要素に持っているので，これを書き込むバージョン値として，残りを保護しなきゃいけないエポック値として扱ってください．また，EpochManager自体は自動ではエポックの増加を行わないので，以下のようなスレッドを用意して適当なタイミングで値を更新する必要もあります．
auto forwarder = [this]() {
  const std::chrono::microseconds epoch_interval{epoch_interval_us};
  while (is_running_.load(std::memory_order_relaxed)) {
    std::this_thread::sleep_for(epoch_interval);
    epoch_manager_.ForwardGlobalEpoch();
  }
};

epoch_thread_ = std::thread{forwarder};

逆に言えば，EpochManagerを外部で用意すればいつグローバルなエポック値を更新するかもそこで制御できるので，単体テストを組んで動作を確認する際はそうした方が楽そうです．

ありがとうございます！
保護されたエポックリストを持ってくる機能まで書いていただいて本当にありがたいです．
1点質問があるのですが，GetProtectedEpochsはprotected_epochs_のコピーを返している（のでワーカースレッドが各々で中身をコピーする必要はない）という認識で合っていますか？

@baycedar

@Mackyson いえ，GetPotectedEpochsで参照する先の配列は全てのスレッドで共通です．ここで作成しているのはshared_ptrのコピー（i.e., 参照カウントを加算）で，参照先の配列に関してはノータッチです．なので，どこかのスレッドで配列内の値を変更されるのはまずく，const vector<szie_t>と宣言することでshared_ptrの中身を変更不可にしています．

@baycedar
なるほど，ありがとうございます！
（ただの参照ならコピーしないとprotected_epochs_を読んでる最中に書き換えられて死にそうなのでコピーを渡すのかなと思っていたのですが， ForwardGlobalEpoch内で所有権破棄（reset）があるので書き換えの心配がないことに気が付きました．お騒がせしました．）

authors: Mackyson baycedar

repo: dbgroup-nagoya-u/memory-manager


text:
feat: update node-normalize-path to 3.0.0+_3.0.0

/approve

/approve

/approve

authors: UTsweetyfish Zeno-sole

repo: deepin-community/node-normalize-path


text:
fix install path by changing debhelper to dh-sequence-nodejs

/ok-to-test

/integrate

authors: YukariChiba prcups shiptux

repo: deepin-community/node-strict-uri-encode


text:
Update getting_started.md, adding brackets to "like AlpineJS"

Your effort is appreciated, but this PR is too small in nature and you’ve created at least 10 other such PRs. Please create one single PR will all language changes and I’ll happily review it all in one go.

repo: delaneyj/datastar


text:
Add JsonNamingPolicy support

Maybe we should pass whole JsonOptions instead of only NamingPolicy?

Nice thought, i'll add it

Great! Appreciate it man

authors: denissden wellWINeo

repo: denissden/fastconfig


text:
Issue 3

Issue closed

authors: desharpe xaltjc

repo: desharpe/PickelProjectMessaging


text:
feat: add cmctl binary to distributions

Thanks @eze-kiel

authors: eze-kiel leucos

repo: devops-works/binenv


text:
Clean up Python code

plz avoid committing .idea and other IDE specific files, you can add them to your local or global ignore list to avoid it happening automatically

repo: diasurgical/devilutionx-gamelist


text:
Update Ruby versions

Hm, what's up with the CI?

authors: CvX tgxworld

repo: discourse/docker-ruby


text:
Feat/add ecr repos

sads

repo: docker/docker-gs-ping


text:
Database design

I have made the initial design for our resource management system, considering the growing demand and scalability requirements. After careful consideration, I’ve chosen to implement this system using a NoSQL database.

DynamoDB (NoSQL) has been replaced by PostgreSQL, because of complexities with the Django backend.
Here's the updated Database Design.

repo: dosXdev/banQuest


text:
Update OrchardCore.Localization.Core to 1.5.0

@Rick-Anderson seems there's already a sample that target .NET 6, but the underlying package it not upgraded, please close #18559 once you merge
I might revise the other samples


text:
Remove NoWarn

will produce a lot of warnings when removed

Why not fix these warnings instead of ignoring them?

Again, it is a NUKE style guide to ignore these warnings. iirc one of those is missing accessibility attributes which are intentionally omitted when writing NUKE build scripts for example.

@Perksey Both warnings are related to redundant fields. One of them is fields that are never assigned, and the other is about fields that are never used.
I don't see how this could be a "style guide"
Example code that produces both warnings:
public class C
{
    // warning CS0649: Field 'C._x' is never assigned to, and will always have its default value 0
    private int _x;

    // warning CS0169: The field 'C._y' is never used
    private int _y;

    public void M()
    {
        _ = _x;
    }
}

Ah in that case that has to do with how NUKE resolves parameters, though the unused field one is interesting. Nonetheless, unless you intend to fix the warnings please don't remove the NoWarn.

Closing this due to inactivity, feel free to reopen.


text:
Create To carolina-zhu-from-jennifer-xu

Filename doesn't follow the standards of this open source project.

repo: dr-spaceman/apcsp-final-project


text:
[MAINT] Async repository

Oh, and it looks like there are about 778 vulnerabilities in the dependencies. It would be worth running npm audit to reveal them and npm audit fix to fix them. Just make sure everything still works after the fixes.

authors: enver-bisevac knagurski

repo: drone/ff-nodejs-server-sdk


text:
Enable a write-back cache for persistent variable writes

this should be on the badge side

repo: duplico/gamequeer


text:
Make https://explorer.e.cash/block/10000 (block height) a valid URL

So the way the app is setup https://explorer.e.cash/block-height/10000 is already a valid url... It just resolves to /block/(block-hash)
There may be a way to check for a block height and resolve the height and/or hash with /block/...but if you just want a valid block-height url, that does already exist...

https://reviews.bitcoinabc.org/T2902

I think it's still useful as many other block explorers support this. Even if we just simply do a redirect (to block-height), that would work (when the block hash is invalid and it's a number).

authors: Klakurka johnkuney

repo: ecashxec/explorer


text:
(feat):Page Header Banner accessibility

build storybook

@eea-jenkins build storybook

repo: eea/volto-eea-design-system


text:
Add QuTiP recipe.

@wolfv Let me know if I messed anything up or can improve anything. I'm in Room 115 if you want to stop by.

Awesome! Let's see what the CI says :)

Looks like what I said yesterday wasn't entirely true about SciPy! Sorry :/
I think we might have to move cython to build (instead of host).

I've removed cython from host (it was already in build).

Which bits of SciPy are not yet working?

Ah, there is no SciPy package yet. Did anyone try yet? How hard is adding one likely to be?

Yes, I thought we had it already. Sorry!
I think we could do it by porting the recipe from pyodide https://github.com/pyodide/pyodide/tree/main/packages/scipy
Alternatively you can also add your recipe there and it would be available as part of pyodide :)

@wolfv I don't understand the relationship between Emscripten and Pyodide. Would you recommend I try bring the SciPy recipe here, or try add a QuTiP recipe to pyodide?

Hi @hodgestar I think both ways are equally good :) Pyodide and emscripten-forge are pretty similar right now, and I think you could just as easily add your recipe in their repository. For the moment, pyodide is also a bit more complete (includes SciPy). In the meantime, we're working hard on getting Scipy and some other packages into emscripten-forge as well.
The differences is that emscripten-forge goes the "conda / mamba" way and separates concerns a bit more vs. pyodide, but ultimately the two projects are somewhat similar (emscripten-forge is also more language-agnostic).
Hopefully by next week, emscripten-forge will also have a Scipy build!

@wolfv Thank you for explaining. I might just wait for next week given that I am still sort of on holiday post SciPy so not working flat out on anything. :)

We do have scipy now, so I am re-running the job -- let's see what happens! :)

It looks like the build passes but the test fails. However, the test failure is a bit obscure -- it complains about python_data.js being missing. I assume the .js file is part of the harness that runs the tests or retrieves the results?

Hey, yeah, is probably an issue with our software. We're still ironing things out :)
Did you check the test_qutip.py file by any chance? Do these smoke tests make any sense?

Hey, yeah, is probably an issue with our software. We're still ironing things out :)

It happens. :)

Did you check the test_qutip.py file by any chance? Do these smoke tests make any sense?

The tests look okay, except for the line with q + 5. If you like I can write a slightly more comprehensive set of tests, but perhaps let's getting everything working first?
The big missing bits of functionality that I would add tests for are:

QobjEvo (which is used to represent time-dependent quantum operators)
Solvers (particularly sesolve and mesolve, which solve ODEs)

If you could write some simple tests for some core functionality, just to make sure it works, that would be wonderful. I think we'll get this to work tomorrow!

Yay, it is working again. Let me write some slightly extended tests while debug is still active.
@wolfv Do you know why the import * broke things? (Not that we should use import *, but I'm curious about what went wrong).

@hodgestar it appears that Python forbids star imports that are not at the module level :) Nothing WASM specific.
However, in our tests we try to import at test-level to localize issues better.
Thanks for writing some additional tests. Feel free to push! I am finishing the changes in empack, they will soon be merged back to main.

@hodgestar the empack issues are fixed in main now – I am happy to merge this as is. But also happy to wait for your additional tests :)

@wolfv Additional tests added -- could you approve the workflow so the tests run?
I'm curious to see how numerical accuracy turns out on the WASM builds.

great! This has worked :)

Yay! This is awesome. Thanks for making this work @wolfv!

@wolfv How do I try this out?

@hodgestar I will add a tiny writeup late today (hopefully) on how to use an emscripten-forge build python package in:

jupyterlite (with xeus-python)
within a website with vanilla javascript

@hodgestar there is already content in a README https://github.com/jupyterlite/xeus-python-kernel which explains the jupyterlite / xeus-python usage

It looks like the QuTiP package never got built because the build of the merge commit to main was cancelled -- https://github.com/emscripten-forge/recipes/actions/runs/2781789562.
And it also looks like each build only builds the files diffed in that commit? So perhaps the early cancellation is a bit too early?

right, sorry, I merged another commit soon after, and that probably canceled the previous run.
Your package should appear in this list shortly: https://beta.mamba.pm/channels/emscripten-forge

@wolfv Thanks! The qutip package has appeared. :D

@DerThorsten I followed the readme and successfully built a jupyterlite environment with numpy but the following:
jupyter lite build --XeusPythonEnv.packages=numpy,scipy,matplotlib,qutip

fails with
Looking for: ['python=3.10', 'xeus-python', 'numpy', 'scipy', 'matplotlib', 'qutip']

emscripten-forge/emscripten-32                              Using cache
emscripten-forge/noarch                                     Using cache
conda-forge/noarch                                          Using cache
pkgs/main/noarch                                              No change
conda-forge/emscripten-32                          358.0 B @ 810.0 B/s 404 failed  0.4s
pkgs/main/emscripten-32                            286.0 B @ 571.0 B/s 404 failed  0.5s
pkgs/r/noarch                                                 No change
pkgs/r/emscripten-32                               284.0 B @ 465.0 B/s 404 failed  0.2s
conda-forge/emscripten-32                           93.0 B @  36.0 B/s 404 failed  2.5s
conda-forge/noarch                                   8.9MB @   3.4MB/s  2.7s
Encountered problems while solving:
  - nothing provides requested qutip

Do I need to wait a bit more? Or somehow specify a different emscripten-forge URL?

emscripten-forge/emscripten-32                              Using cache

maybe its still using outdated repodata. @wolfv what was the command/the file to delete to get ride of the cache?

rm -rf $MAMBA_ROOT_PREFIX/pkgs/cache or micromamba clean --index-cache

It's working for me (better in Firefox than in Chrome!)
I think we might still have problems if you try to run this from a non-linux machine.
I was running jupyter lite on Github codespace and that worked fine:

PS: cy_grape_unitary also seems to run fine, takes a while though.

@wolfv That's awesome! I am running from a Linux machine and using Firefox but I still haven't managed to do "import qutip" from a locally built jupyterlite instance.
The build seems to go fine now, but when I run the server I get
[LiteServeApp] WARNING |

        Serving JupyterLite Debug Server from:
            /home/simon/projects/qutip-emscripten/_output
        on:
            http://127.0.0.1:8000/index.html

        *** Exit by: ***
            - Pressing Ctrl+C
            - Visiting /shutdown
404 GET /api/contents/all.json (127.0.0.1) 1.08ms

on start up and
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
Input In [1], in <cell line: 1>()
----> 1 import qutip

ModuleNotFoundError: No module named 'qutip'

Importing numpy,  scipy and matplotlib all seem to work fine.

And in the Javascript console I get:
Starting WebSocket: ws://127.0.0.1:8000/api/kernels/b3fb81ad-da29-4e6f-b4c4-2e547ce3dcb1 [default.js:66:20](webpack://_JUPYTERLAB.CORE_OUTPUT/node_modules/@jupyterlab/services/lib/kernel/default.js)
Loading distutils 2 [load-package.ts:329:20](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loaded distutils 2 [load-package.ts:389:22](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Python initialization complete 2 [pyodide.asm.js:14:294679](https://cdn.jsdelivr.net/pyodide/v0.20.0/full/pyodide.asm.js)
distutils already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loading micropip, pyparsing, packaging 2 [load-package.ts:329:20](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loaded micropip, packaging, pyparsing 2 [load-package.ts:389:22](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
distutils already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
packaging already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
pyparsing already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loading matplotlib, cycler, six, fonttools, kiwisolver, numpy, pillow, python-dateutil, pytz 2 [load-package.ts:329:20](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loaded cycler, six, python-dateutil, pytz, fonttools, kiwisolver, pillow, matplotlib, numpy 2 [load-package.ts:389:22](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
distutils already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
pyparsing already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
six already loaded from default channel 2 [load-package.ts:311:6](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loading pygments, setuptools, decorator, jedi, parso 2 [load-package.ts:329:20](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
Loaded decorator, parso, setuptools, pygments, jedi 2 [load-package.ts:389:22](https://cdn.jsdelivr.net/pyodide/v0.20.0/src/js/load-package.ts)
SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

before running any notebook cells.

this looks like the error is coming from the pyodide python kernel, but to use the emscripten-forge stuff one needs to run the xeus-python kernel. @hodgestar do you also see the xpython/xeus-python kernel available?

@DerThorsten I have xeus-python installed in the virtualenv I'm building in. Do I need to install it somewhere else?

@hodgestar you actually need to pip install xeus-python-kernel (https://xeus-python-kernel.readthedocs.io/en/latest/)
It's confusing. We need to write more docs & find better names.

Sorry, it shoudl be pip install jupyterlite-xeus-python, my bad!

Once you have that installed, the jupyter lite build --XeusPythonEnv.packages=numpy,scipy,matplotlib,qutip command will do more than before, and you should see a xeus python interpreter in jupyterlite :)

I installed jupyterlite-xeus-python and opened the XPython kernel. Woot & thanks!
However, matplotlib fails to import as follows:

And I get the following output in the Javascript console:

Thank you all for all your help so far. It's been a slightly bumpy journey, but it's helpful that I know it's possible to make this work. I'm hoping that I can build my own copy and deploy it to the QuTiP website.

Also happy to continue this conversation somewhere other than this PR if that would be more helpful.

Hi @hodgestar I think you're hitting a bug in empack that we fixed yesterday. Any chance you could try to update empack? micromamba update empack or install the current main branch from https://github.com/emscripten-forge/empack with pip
Did importing qutip work, though?!
We can also chat on https://gitter.im/QuantStack/Lobby

Importing QuTiP failed still because it tries to import matplotlib (and catches an ImportError, but not a FileNotFoundError).

authors: DerThorsten hodgestar wolfv

repo: emscripten-forge/recipes


text:
entgql: cleanup source code by copy content to a single file

I don't change anything, just cleanup to prepare for refactoring phase.

repo: ent/contrib


text:
add vhdl syntax check test

@glencoe we spoke about excluding this test from the pipeline. Should I do it by excluding paths in the workflow file? Or do you have a different idea? I never worked with the workflow stuff and I'm a little bit afraid to break everything :D

I moved the test file to your suggested folder but it is still executed in the ci-cd pipeline. So I would propose to exclude it from the pipeline?

I moved the test file to your suggested folder but it is still executed in the ci-cd pipeline. So I would propose to exclude it from the pipeline?

i think we still have to change the command that we run the tests with to only pick the tests in specific folders

If this test is in creator/integration_tests/vhdl and we run python -m unittest discover creator/tests to run our unit tests we would not execute the vhdl syntax check.

Okay, but this means, we only execute unit tests and no integration and system test anymore. Do we want it like this? If so, I will change the workflow file to the command you suggested.

I think we should talk about this again, but for now i'd say let's just execute the unit tests in the pipeline


text:
Recurly

https://ethyca.atlassian.net/wiki/spaces/EN/pages/2708471809/Recurly+Connector+Specification

repo: ethyca/fides


text:
Change linter from Pylint to Ruff

Done in v6

repo: explodinglabs/jsonrpcserver


text:
chore: remove cross-fetch

:tada: This issue has been resolved in version 16.16.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v16.16.3

Your semantic-release bot :package::rocket:

repo: eyereasoner/eye-js


text:
run linter on all source files except on output directory

Codecov Report

Merging #167 (44cd372) into main (b48429b) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #167   +/-   ##
=======================================
  Coverage   97.37%   97.37%
=======================================
  Files          14       14
  Lines         723      723
  Branches      286      293    +7
=======================================
  Hits          704      704
  Misses         19       19

Files
Coverage Δ

src/core/generateZodSchema.ts
96.16% <100.00%> (ø)

src/core/jsDocTags.ts
98.50% <100.00%> (ø)

src/utils/resolveModules.ts
100.00% <100.00%> (ø)

authors: codecov-commenter schiller-manuel


text:
increase some default storage requests

[merge]

license_source: bigquery


text:
lets add a large timeout to avoid the first project in a new fabric8-forge pod taking a huge amount of time to return

[merge]


text:
Update pom property init-tenant.version to vaebd9c0

[merge]


text:
README: Remove overlay from docs

Is it the only place where overlay is documented? Did you check inside doc/

I checked, but it is easy to miss something.

repo: farcaster-project/farcaster-node


text:
Generate alt text

Closes #201

repo: felixmokross/lapuertahostels


text:
Add uv setup

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant doctorina-main

repo: flet-dev/website


text:
Release 1.53.0

Topic : https://my.flexio.io/informations/topic/edit/5d24e927858a543b5e1a7a26

repo: flexiooss/hotballoon-shed


text:
refactor: remove unused files

We need to also remove the credentials file being imported in index.ts at root in scenario

authors: Xillians braaar

repo: flexisoftorg/conf


text:
Add live test

To access Flojoy-studio build from this pull request, you can use the following URLs:
Windows installation: http://547_windows.flojoy-test.com:3000
Linux installation: http://547_linux.flojoy-test.com:3000
Please note that it may take a few minutes for the instance to start up, so please be patient.
It is important to know that the instance will automatically shut down after 4 hours to conserve resources. If you wish to start the instance again after it shuts down (or restart it to pickup new changes), you can use this API :
Windows: https://kgpsoscpc4q52d4mtwuu7jhvie0qdiso.lambda-url.us-east-1.on.aws/start_instance?instance_id=i-05aad69599e8efa95&domain=547_windows
Linux: https://kgpsoscpc4q52d4mtwuu7jhvie0qdiso.lambda-url.us-east-1.on.aws/start_instance?instance_id=i-0a5e76c75a858edc2&domain=547_linux

repo: flojoy-io/studio


text:
Update client version in readme

LGTM, but I have noticed that we still have the page_size in the examples. Will open a separate PR to take it out.

Good point, thank you!


text:
dont sync facility status when syncing from devicectl to nautobot

Fixed by #25

authors: grizz vegu

repo: fullctl/devicectl


text:
[Task] Replace require statements with imports - report.js

closed by https://github.com/gabrielcsapo/module-detective/commit/c36aa8f50f34a5070ca5da3b4fac9d84d4f73ab4 (i forgot to create a branch).

repo: gabrielcsapo/module-detective


text:
prepare final example bot

move the example code into separate repository
commit generated code
add configuration/switch/asserts for developer vs production url/user/pass

https://github.com/gdg-garage/space-tycoon-example-bot

authors: malytomas tivvit

repo: gdg-garage/space-tycoon


text:
add: openai moderation

LGTM

LGTM

LGTM

LGTM

authors: Justin-ZL better629 shenchucheng

repo: geekan/MetaGPT


text:
Implement API for claims repository (GDEV-1429)

Thanks for the review, all good points. Readey for review again.

repo: ghga-de/auth-service


text:
Update code for V2

Some good tweaks and clean up here. Thanks.
I want to spend a little time going through it. Also, before I merge, I want to rename all instances of 'schedule' to 'event'.(I'm happy about this change, since everyone else calls it an 'event'! :) )

I tested it straight away. Works as expected.
No problem :)

I would like to open a better communication channel. What do you think of Slack? Or do you have another suggestion for better communication?

Do you have the rendering issue?

I wanted to get your stand from the new branch first. But I can only do that if you merge, because otherwise I have to discard my commits.

authors: KevinKrueger gismofx


text:
请问一下模型下载好后在哪个目录呢？

./dataroot/models目录下

repo: git-cloner/aliendao


text:
Add ratelimiter

Current dependencies on/for this PR:

master

PR #14   👈

This stack of pull requests is managed by Graphite.

repo: gneiru/kd


text:
my study

I'm sorry that just my study.

repo: googlecodelabs/android-compose-codelabs


text:
Fix build failure on release6x  branch

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

authors: bot-gradle donat wolfs

repo: gradle/gradle


text:
[Spike] Finner grained immutable workspace caching

@bot-gradle test PT

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForNightly build

@bot-gradle help

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN>

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle test and merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test PT

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForNightly build

@bot-gradle test PT

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForNightly build

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForNightly build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle clean

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle clean

@bot-gradle test APT

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForRelease build

@bot-gradle test this APT

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build
AllPerformanceTestsReadyForRelease build

@bot-gradle test this APT

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build
AllPerformanceTestsReadyForRelease build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

We decided we will rather use move sematics and not finer grained caching. See https://github.com/gradle/gradle/pull/26970

authors: asodja bot-gradle


text:
allow users to type EID in addition to  in the evidence manager

This behavior should also be added to the main evidence selector input.

authors: acoffman susannasiebert


text:
docs(docs): gh pages

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

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

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

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

repo: guiseek/nxgs


text:
Exported import

Current coverage for CombineSchedulers is 5.74%
✅ No files affecting coverage found

Current coverage for ComposableArchitecture is 11.43%
✅ No files affecting coverage found

Current coverage for GitHubAPIClientTests is 97.40%
✅ No files affecting coverage found

Current coverage for NetworkingTests is 86.03%
✅ No files affecting coverage found

Current coverage for Trending.app is 16.38%

Files changed
-
-

MockGitHubAPIClient.swift
0.00%
:skull:

World+Unimplemented.swift
50.00%
:warning:

Powered by xcov

  Generated by :no_entry_sign: Danger

repo: gwikiera/github-trending-app


text:
write complete backend skeleton (ts definitions to fit implementation within)

job done in 68b5cca88c7fca572369de866cba7b1db7d3582c

repo: haumea-group/namaka


text:
fix: trace_span should not be bound to placeholder

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.30%. Comparing base (aa32f9a) to head (f2a94db).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #104      +/-   ##
==========================================
+ Coverage   85.27%   85.30%   +0.02%
==========================================
  Files          14       14
  Lines         523      524       +1
==========================================
+ Hits          446      447       +1
  Misses         77       77

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
useSetTransactionRequestAtom

Looked at the ones we have left ...it is possible all three need to be done together, but I'm going to start with this one first bc it is used in currentNetworkKeyState.

It does appear they all need to be worked on together, so I assigned them all to myself. The work will also close:
https://github.com/hirosystems/stacks-wallet-web/issues/2617

repo: hirosystems/stacks-wallet-web


text:
Change of coruse model

Reviewed


text:
algo: Debug files decorator tweaks

⭐

authors: hodgerpodger jumperavocado

repo: hodgerpodger/staketaxcsv


text:
update cta button css & dashboard header menu css

Both the CDE & the Dashboards UI look great, @bhushankhope ! Approved!

authors: LibbyUX bhushankhope

repo: hubmapconsortium/hra-ui


text:
Adds experimental AnthropicFunctions wrapper

I'm also working on this feature~😂

I'm also working on this feature~😂

Ah shoot! I can still have a look at your other PR - I think Minimax supports a similar API natively though no?


text:
Remove .Release.name from namespace labels

Removing the namespace from the namespaces section of the pattern causes the pattern to encounter a sync failure on trying to install the subscription (since the NS has to exist first, then apparently the operator does some things with it?).

Another approach to fix this problem (which I've tested) is to override .Release.name in the pattern overrides section. However, I maintain that using helm variables this way (outside of a context where we're explicitly helm installing something) might be inviting oddities like this, since in most places ArgoCD will "helm template" which won't set these variables

I am fine with this change. Do we know why we needed/added the label in the first place? Was there a special reason or it just seemed a good idea at the time?

authors: mbaldessari mhjacks

repo: hybrid-cloud-patterns/common


text:
Update Cargo.toml minor change http => https

Thanks for accepting the PR. If you are interested on this page you can see all of your crates, which one has the link, and then which ones have CI configured. I hope it will be useful to you.

repo: hyperledger/sawtooth-sdk-rust


text:
Move datasets from Nextcloud to CSCS

Update from Victor.:
In order to avoid authenticating, one needs to use FirecREST (https://products.cscs.ch/firecrest/), which requires its machinery set… (edited)
9:33
There is no way that one can copy files without authentication. What FirecREST does for you is: it holds your authentication on your behalf for a given amount of time. But you have to authenticate to FirecREST, in the first place…
white_check_mark
eyes
raised_hands
9:33
Please read the page, and tell me if you are interested in using it. I can set up a meeting with the developers and they explain to you more in details how to use it and what you need to do to do use it…

Ok, I managed to set it up, the following way:

Read https://github.com/eth-cscs/openstack/tree/master/cli
source openstack/cli/castor.env
swift post karabo_public --read-acl ".r:*,.rlistings"
swift upload karabo_public example_file.fits

After this, everyone can access example_file.fits via https://object.cscs.ch/v1/AUTH_1e1ed97536cf4e8f9e214c7ca2700d62/karabo_public/example_file.fits
@rohitcbscient @cvoegele What files should I move there?

9749844c0df9081b5c6f50eb080ffb721fa8173e uses CSCS URLs now. Documentation not yet completed.

authors: cvoegele deiruch


text:
Add paging to query the subgraph

Closed: proper pagination will be implemented in another PR

authors: Le-Caignec PierreJeanjacquot


text:
feat: docker example

Locked by: https://github.com/iai-callgrind/iai-callgrind/pull/103/files#r1539396580

Do you want to make use of this or does it only serve as an example?

@gamma0987 hello, sorry, 🚀 across the country do not allow to get a good night's sleep and finish PR (I'll try tomorrow).
This is good example for macOS users, but also can used in CI when need qemu

Sorry for what is going on in your country. Don't feel pressurised by my question. I just wanted to know the purpose of this pr, so thanks for sharing an example :) Please move the example into a sub-directory examples instead of tools. Maybe examples/docker/multiple_targets. Or, if you have a better name than multiple_targets then use whatever your example describes best.
If the iai-callgrind version in your example needs to be in sync with the version number in this repo, then it's best to add your file(s) to .bumpversion/version. Please add more explanations of your example in its README about what it does, for whom it is intended, what is needed to make if work for another target (supported by valgrind) etc.

repo: iai-callgrind/iai-callgrind


text:
Create a thin/lower module of only rpc aws client calls

We can use our crudBuilder2 helper to invoke an EC2 client function using a string.
const methodName: string = 'describeVpcs';
const methodAsType: keyof typeof ec2Client = methodName as keyof typeof ec2Client;
const res = crudBuilder2<typeof ec2Client, typeof methodAsType>(methodAsType, () => ({}))

@mtp1376 was able to do it for more than ec2 in straightforward way!

repo: iasql/iasql


text:
changed 2022 to 2021

first pull request


text:
适配 vlook 16 的配色方案

适配了 vlook17的配色方案。

repo: idea-zone/mini-vlook


text:
fix block_name_to_quantize and hymba tuning issue

Add a hymba test in gpu test later

repo: intel/auto-round


text:
Implement AudioRenderCapacity

Sorry I should have mentioned this earlier but I just remember hoch told me this API is not likely to actually land in the browsers due to security concerns.
I would say it is still nice to have for us because the concerns do not apply to node/rust applications, just for browser sandboxes. Since everything is nicely spec'd and all it would be a shame to not have it.

Thanks for the info, and agreed this is a nice to have anyway!

authors: b-ma orottier

repo: ircam-ismm/node-web-audio-api


text:
[WIP] Upload benchmark suites artifacts

I was implementing something similar too at https://github.com/iree-org/iree/pull/10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

I was implementing something similar too at #10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

Oh thanks. The iree folder is generated by the new benchmark framework. We're in the process to replace the current benchmark suites. Will need to update the part you've done later.

I was implementing something similar too at #10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

Oh thanks. The iree folder is generated by the new benchmark framework. We're in the process to replace the current benchmark suites. Will need to update the part you've done later.

Got it. When do you plan to open this PR for review? I can hold off my PR and base it on this work once it is landed.

Oh, and we would need to archive all the flagfiles too (unless that part is also changed), otherwise we can't tell from one compile config to another based on the .vmfb alone.

I was implementing something similar too at #10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

Oh thanks. The iree folder is generated by the new benchmark framework. We're in the process to replace the current benchmark suites. Will need to update the part you've done later.

Got it. When do you plan to open this PR for review? I can hold off my PR and base it on this work once it is landed.

So I reviewed #10442 and here are some of my thoughts:
Essentially we want to have iree_run_module_test with some fixed inputs and expected outputs to check each benchmark we defined in the benchmark suites (and maybe some extra cases outside the benchmark suites). The new framework we are working on now is using python to define models/compile flags/run flags/... For example:

https://github.com/iree-org/iree/blob/main/build_tools/python/e2e_test_framework/models/model_groups.py
https://github.com/iree-org/iree/blob/main/build_tools/python/benchmarks/iree/definitions.py

This frees us from the limited CMake expressiveness and we don't need to parse those directory names to get the parameters of a benchmark (like this part), which is fragile and hard to maintain.
So since this e2e list is basically a copy of the benchmark list, I'm wondering it might be a good idea to also generate that list with a python script, similar to what we are doing now for the new benchmark suites (https://github.com/iree-org/iree/blob/main/benchmarks/generated_benchmark_suites.cmake).
If we use python scripts to generate the e2e test list, you can easily get all of the benchmark parameters (arch, driver, runtime, run flags...) by importing those python modules. And we won't miss the new added benchmarks because they will also be generated in the list.
The whole framework is not completely ready now, I can try to make everything ready for e2e tests next week. In the meantime, I won't block #10442 if you want to merge it first, but eventually we will remove the current benchmark_suites and we need to refactor.

I was implementing something similar too at #10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

Oh thanks. The iree folder is generated by the new benchmark framework. We're in the process to replace the current benchmark suites. Will need to update the part you've done later.

Got it. When do you plan to open this PR for review? I can hold off my PR and base it on this work once it is landed.

So I reviewed #10442 and here are some of my thoughts:
Essentially we want to have iree_run_module_test with some fixed inputs and expected outputs to check each benchmark we defined in the benchmark suites (and maybe some extra cases outside the benchmark suites). The new framework we are working on now is using python to define models/compile flags/run flags/... For example:

https://github.com/iree-org/iree/blob/main/build_tools/python/e2e_test_framework/models/model_groups.py
https://github.com/iree-org/iree/blob/main/build_tools/python/benchmarks/iree/definitions.py

This frees us from the limited CMake expressiveness and we don't need to parse those directory names to get the parameters of a benchmark (like this part), which is fragile and hard to maintain.
So since this e2e list is basically a copy of the benchmark list, I'm wondering it might be a good idea to also generate that list with a python script, similar to what we are doing now for the new benchmark suites (https://github.com/iree-org/iree/blob/main/benchmarks/generated_benchmark_suites.cmake).
If we use python scripts to generate the e2e test list, you can easily get all of the benchmark parameters (arch, driver, runtime, run flags...) by importing those python modules. And we won't miss the new added benchmarks because they will also be generated in the list.
The whole framework is not completely ready now, I can try to make everything ready for e2e tests next week. In the meantime, I won't block #10442 if you want to merge it first, but eventually we will remove the current benchmark_suites and we need to refactor.

Thanks for the review. However, the full test list should happen in the benchmark framework. What we put in tests/e2e/models is a small sublist that provides us the safeguard on 1) compiler codegen change 2) upstream toolchain change that could cause a garbage/wrong module output. It is NOT meant to be complete, and we may extend it as needed, but not required.
I am all for not parsing the archive structure in CMake, and hence the question I asked in the discord #builds channel (https://discord.com/channels/689900678990135345/689957613152239638/1019035921817018469). If we have a tool in place that can make this task easier, I am more than happy to change the function once the new feature is landed.

I was implementing something similar too at #10442 :p
I don't think there is a build-benchmarks/benchmark_suites/iree-* object. The benchmark_suites currently has two subdirectories, TF and TFLite
Also, I found that if we excluded .mlir and .tflite we could reduce the archive size from 6GB to 2GB
tar --exclude '*.tflite' --exclude '*.mlir' -cf \
            "${BENCHMARKS_ARCHIVE}" "${BENCHMARKS_DIR}/benchmark_suites"

Oh thanks. The iree folder is generated by the new benchmark framework. We're in the process to replace the current benchmark suites. Will need to update the part you've done later.

Got it. When do you plan to open this PR for review? I can hold off my PR and base it on this work once it is landed.

So I reviewed #10442 and here are some of my thoughts:
Essentially we want to have iree_run_module_test with some fixed inputs and expected outputs to check each benchmark we defined in the benchmark suites (and maybe some extra cases outside the benchmark suites). The new framework we are working on now is using python to define models/compile flags/run flags/... For example:

https://github.com/iree-org/iree/blob/main/build_tools/python/e2e_test_framework/models/model_groups.py
https://github.com/iree-org/iree/blob/main/build_tools/python/benchmarks/iree/definitions.py

This frees us from the limited CMake expressiveness and we don't need to parse those directory names to get the parameters of a benchmark (like this part), which is fragile and hard to maintain.
So since this e2e list is basically a copy of the benchmark list, I'm wondering it might be a good idea to also generate that list with a python script, similar to what we are doing now for the new benchmark suites (https://github.com/iree-org/iree/blob/main/benchmarks/generated_benchmark_suites.cmake).
If we use python scripts to generate the e2e test list, you can easily get all of the benchmark parameters (arch, driver, runtime, run flags...) by importing those python modules. And we won't miss the new added benchmarks because they will also be generated in the list.
The whole framework is not completely ready now, I can try to make everything ready for e2e tests next week. In the meantime, I won't block #10442 if you want to merge it first, but eventually we will remove the current benchmark_suites and we need to refactor.

Thanks for the review. However, the full test list should happen in the benchmark framework. What we put in tests/e2e/models is a small sublist that provides us the safeguard on 1) compiler codegen change 2) upstream toolchain change that could cause a garbage/wrong module output. It is NOT meant to be complete, and we may extend it as needed, but not required.
I am all for not parsing the archive structure in CMake, and hence the question I asked in the discord #builds channel (https://discord.com/channels/689900678990135345/689957613152239638/1019035921817018469). If we have a tool in place that can make this task easier, I am more than happy to change the function once the new feature is landed.

Add a TODO in https://github.com/iree-org/iree/pull/10442/files#diff-60a9e2ce1837000bf7fa23331fc2a8b98a63b2aed1a9edf305fbd92a01091cf5R101 to mark the future cleanup.

authors: hcindyl pzread

repo: iree-org/iree


text:
Rewrite readme with example queries

see also #96


text:
Extract duplicate persistentfilter api call logic from Tasklist.vue and ProcessInstances.vue

Klärt sich im Rahmen der Umstellung auf Tanstack-Query

repo: it-at-m/digiwf-core


text:
please update this package for ups

UPS is already implemented.

authors: ivanmitrikeski nextgenbite

repo: ivanmitrikeski/laravel-shipping


text:
Table Menu Section

Completed in https://github.com/j-rockwell/kame/pull/21

repo: j-rockwell/kame


text:
Development

Ran Plan for project: terragrunt-example dir: non-prod/us-east-2 workspace: default
Show Output
time=2022-04-28T14:30:03-05:00 level=info msg=The stack at /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2 will be processed in the following order for command plan:
Group 1
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster

time=2022-04-28T14:30:03-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql]
time=2022-04-28T14:30:03-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster]
time=2022-04-28T14:30:03-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster]
time=2022-04-28T14:30:03-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/16/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql]

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding latest version of hashicorp/aws...

Initializing provider plugins...
- Finding latest version of hashicorp/aws...

Initializing provider plugins...
- Finding latest version of hashicorp/aws...

Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.11.0...
- Installing hashicorp/aws v4.11.0...
- Installing hashicorp/aws v4.11.0...
- Installing hashicorp/aws v4.11.0...
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
Releasing state lock. This may take a few moments...
Releasing state lock. This may take a few moments...
Releasing state lock. This may take a few moments...

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
Releasing state lock. This may take a few moments...
time=2022-04-28T14:30:20-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.11.0...
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-28T14:30:20-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.11.0...
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-28T14:30:20-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.11.0...
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-28T14:30:20-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.11.0...
- Installed hashicorp/aws v4.11.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

:arrow_forward: To apply this plan, comment:

atlantis apply -p terragrunt-example

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p terragrunt-example

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis unlock

All Atlantis locks for this PR have been unlocked and plans discarded


text:
Update README.md

ok


text:
Fix upstream CI

Whoops this is actually a dupe of #231. Closing this.


text:
add react devtools extension

Don't want to handle extension update, and stuff, do keep electron-extension-installer.
Backport security and reload in #19 instead

repo: jdeniau/tiana-tables


text:
Generate plugins registry

this is great, but it's in the wrong repo. It needs to be in jdx/mise so it can be automatically run when mise is released like how we generate cli-reference.md for the docs See: https://github.com/jdx/mise/blob/main/docs/cli-reference.md
https://github.com/jdx/mise/blob/7dea795967ee11526af6e95a55e19bf7fddb3315/src/cli/render_help.rs#L16
https://github.com/jdx/mise/blob/7dea795967ee11526af6e95a55e19bf7fddb3315/scripts/release.sh#L76

I don't mind it being written in node, we'll just need to add a new render task like render:registry
https://github.com/jdx/mise/blob/7dea795967ee11526af6e95a55e19bf7fddb3315/.mise.toml#L67

authors: jdx taskylizard

repo: jdx/mise-docs


text:
Update pom property kubernetes-client.version to 2.5.8

[merge]

repo: jenkinsci/kubernetes-pipeline-plugin


text:
components and Game.js page commented out and structured to be cleaner

All tested!


text:
Added Video Converter & Audio Converter

@jfversluis Thank you!
Yes, I have made changes by Alphabetical order

@jfversluis
Do let me know if you want to try & review the app, I'll send you promo.

I would love that! Find my email on my GitHub profile please!

I would love that! Find my email on my GitHub profile please!

Done! I've sent you promos on your email.

repo: jfversluis/built-with-maui


text:
Spring Boot Security: OAuth2

Ready!

Options:

Custom
Keycloak
Okta
Auth0

work in progress here: https://github.com/pascalgrimaud/tmp-jhlite-oauth2

AdminUserDTO:12
Do we still want to provide such login regex? see https://github.com/jhipster/generator-jhipster/issues/12740.
SecurityConfiguration:194
SecurityConfiguration:241
Interesting to see that session management and CSRF are still needed for monoliths to provide oauth2Login.
With a JHipster OAuth2 monolith (indeed, the generator warns it is stateful), we still rely on the JSESSIONID cookie so It looks like the JWT layer is not used at all. At least for /api/account, but I did not see any Authorization header management in the generated frontend. I'll need some time to test and understand what's going on ;)
.antMatchers("/api/auth-info").permitAll()
What is this?

AdminUserDTO needs some refactoring, it's related to Account context, I didn't finish this part yet.
About aurh-info, see https://github.com/jhipster/jhipster-sample-app-oauth2/blob/main/src/main/java/io/github/jhipster/sample/web/rest/AuthInfoResource.java

Now I have a clear understanding of everything JHipster currently generates (a bit late I admit!).
JHipster OAuth2 simply relies on the default session-based login for monoliths, but it also enables a JWT resource server so the generated API can be consumed by other applications with Authorization Bearer.
I just tested it and it works pretty well on your tmp-jhlite-oauth2 repository as well as in a JHipster generated app.
The generated web_app client does not allow direct access grants so I enabled it to get an access token from keycloak directly.
So the tmp-jhlite-oauth2 repository would be the "full" or "monolith" option, proving the 3 layers:

OAuth2 Client, which is required in all scenarii

with CustomClaimConverter for authority mapping with private providers (aka keycloak, okta, auth0)

OAuth2 Login, which is useful for user-facing backends (monoliths)
OAuth2 Resource Server JWT, which is useful for all kinds of web services, including microservices, but optional for user-facing backends (monoliths)

Obviously, for microservices, OAuth2 Login is disabled and only Authorization Bearer is supported. I guess it should be another option of JHipster Lite and I wonder how we'll separate them.

Monolith
Microservice

OAuth2 Client
required
required

OAuth2 Login
user-facing
N/A

OAuth2 Resource Server
web service
required

authors: pascalgrimaud pblanchardie

repo: jhipster/jhipster-lite


text:
Fix django-renderpdf typo

Thanks for this.


text:
Fix sidebar

Pull Request Test Coverage Report for Build 4174844607

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.557%

Totals

Change from base Build 4173807145:
0.0%

Covered Lines:
1240

Relevant Lines:
1724

💛  - Coveralls

authors: coveralls mark-tate

repo: jpmorganchase/mosaic


text:
Fix typos [ci skip]

Thank you!


text:
Spike: Boot assessment

Closing this, most of the infos are already in the whitepaper

repo: kairos-io/kairos


text:
Use Fiber scheduler

Thank you for the PR.
Based on the provided code I have updated the implementation so that we can switch between the implementations; see 372db73. Thread is kept there as the default, as it is faster; see https://twitter.com/kazuho/status/1608205292239736833.

Thank you!

authors: kazuho shugo

repo: kazuho/rat


text:
added funding.json for drips rewards

@haroune-mohammedi once this is merged, I can set the drips rewards through their portal

repo: keep-starknet-strange/abi-wan-kanabi


text:
Can keras work with Pytorch Geometric?

I assume it can -- maybe you can try it and let us know how it goes.

authors: codingmagical fchollet

repo: keras-team/keras


text:
Update JenkinsFile

approved

s

repo: khaja-pt/Jenkins-Zero-To-Hero


text:
chore(workflows): enable slack digest + jira sync

/lgtm

authors: djzager eriknelson

repo: konveyor/crane-plugin-imagestream


text:
Update README.md

ありがとうございます


text:
feat: stop accepting (but still wait with poll) when we've reached maximum clients

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

repo: kristof-mattei/endless-ssh-rs


text:
update dep known-folders

Thanks!

authors: franciscod kristoff-it

repo: kristoff-it/bork


text:
Deny the /Trace.axd endpoint

@raviknox change is done by @vishnusomank. Hence Merging the PR

authors: salman-accuknox vishnusomank

repo: kubearmor/policy-templates


text:
Update OWNERS

/lgtm
/approve

authors: AvineshTripathi chris-short

repo: kubernetes-sigs/contributor-tweets


text:
Fix #1051 memory profile (global free, API breaking change)

Same intent as #74, but with a privately held cache and no globals. The exception processing interface is affected.
cc: @dwertent @matthyx

Interface changes LGTM, I think you can move forward.
So you deprecate #74 in favor of this one?
I am still not sure whether the tuple (DesignatorType, WLID, WildWLID, SID) is unique... @amirmalka ?

@matthyx cleaned and squashed everything

@matthyx cleaned and squashed everything

looks good thanks a lot Fred! I'll let David check as well.

@matthyx @dwertent reflecting on the rather weak hashing function I have introduced (simply summing the hashes of a set into a larger integer), I admit that I am a bit wary of the likelihood of hash collisions here.
I'd need a little time to survey the literature and find a stronger, yet still memory-efficient way of hashing an unordered set.  Something like this https://people.csail.mit.edu/devadas/pubs/mhashes.pdf
I believe that the current method is good enough for what we do. Anyhow, I'm going to work on improving that part next week, in a separate "improvement" PR for the sake of clarity.

@matthyx @dwertent reflecting on the rather weak hashing function I have introduced (simply summing the hashes of a set into a larger integer), I admit that I am a bit wary of the likelihood of hash collisions here.

@matthyx @dwertent I've improved the inner hash used by the cache (#82), to implement set-hashing in a more thorough way.

Well done @fredbi !!

@matthyx @matthyx  thank you so much.
There is a follow-up on that one: #82 , which strengthens the hash function. I am okay with refactoring it if you think that the gory details of finite field arithmetic should be offloaded ... :)

authors: dwertent fredbi matthyx

repo: kubescape/opa-utils


text:
Fix multiplatform test

Fix verified by https://github.com/kuzudb/kuzu/actions/runs/7004587201/job/19052643035

repo: kuzudb/kuzu


text:
feat: upgrade kubernetes-gateway-api to v0.8.0

@hassnatahmad Hi,
Thank you for the PR. Is there any specific reason to upgrade the gateway API to v0.8.0? Obviously, it would be nice to have the latest API version, however, we haven't got the time to test out, if everything works as it should. Have you experienced this with your version?
@rg0now May we have your opinion about the gateway API upgrade?

@davidkornel Thank you for quick response.
Reason being, if you have or need kubernetes gateway api crd's then you are bound with this chart.
Ideally we should install them from official kubernetes sig.
As for as this version is concerned i did in my local kind setup and it is working

The problem is that we need to upgrade the Go imports in the operator as well: currently we use sigs.k8s.io/gateway-api v0.7.1 and this should be bumped to v0.8.0 first. So I'd like to ask you guys to hold this PR back until we manage to do the upgrades there first, should be no more than a week or so.
Thanks for the PR though!

@hassnatahmad As the upgrades are done
I accept it, thanks for the PR

authors: davidkornel hassnatahmad rg0now


text:
Update non-React dependencies.

I'm not worried about the drop in coverage, it's so minor and likely the result of deleting a few lines of code here and there to account for updated lint errors.


text:
update tests and functions to use config

Codecov Report
Base: 73.77% // Head: 75.05% // Increases project coverage by +1.27% :tada:

Coverage data is based on head (22a32c7) compared to base (a133db5).
Patch coverage: 63.41% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
+ Coverage   73.77%   75.05%   +1.27%
==========================================
  Files           4        4
  Lines         450      477      +27
==========================================
+ Hits          332      358      +26
- Misses        118      119       +1

Impacted Files
Coverage Δ

bdnex/lib/utils.py
50.94% <53.12%> (+13.90%)
:arrow_up:

bdnex/lib/archive_tools.py
100.00% <100.00%> (ø)

bdnex/lib/bdgest.py
82.31% <100.00%> (+0.12%)
:arrow_up:

bdnex/lib/cover.py
68.75% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter lbesnard

repo: lbesnard/bdnex


text:
Tap on notification by text and by index on iOS

Nice blogpost:

https://medium.com/@t.camin/testing-push-notifications-with-ui-tests-e9c9ccd8aa9f

authors: bartekpacia mateuszwojtczak

repo: leancodepl/patrol


text:
[macOS] supports sandbox mode

+1

+1

license: mit


text:
feat: port RingTheory.OreLocalization.OreSet

bors merge