text:
Feature/event bus

Codecov Report

Merging #7 (3703030) into develop (85b0378) will decrease coverage by 14.53%.
The diff coverage is 32.20%.

@@             Coverage Diff              @@
##           develop       #7       +/-   ##
============================================
- Coverage    93.01%   78.48%   -14.54%
============================================
  Files           70       79        +9
  Lines         2019     2398      +379
  Branches       295      333       +38
============================================
+ Hits          1878     1882        +4
- Misses         110      467      +357
- Partials        31       49       +18

Impacted Files
Coverage Δ

...Contrib.BasicAbility.Dcc/ConfigurationApiClient.cs
84.46% <ø> (ø)

...Contrib.BasicAbility.Dcc/ConfigurationApiManage.cs
100.00% <ø> (ø)

...Ability.Dcc/Internal/DccConfigurationRepository.cs
63.79% <ø> (-32.76%)
:arrow_down:

...b.Data.Contracts.EF/ServiceCollectionExtensions.cs
100.00% <ø> (ø)

...rationEvents.Dapr/IntegrationEventHostedService.cs
0.00% <0.00%> (ø)

...Dapr/Processor/DeleteLocalQueueExpiresProcessor.cs
0.00% <0.00%> (ø)

...r/Processor/DeletePublishedExpireEventProcessor.cs
0.00% <0.00%> (ø)

...tionEvents.Dapr/Processor/InfiniteLoopProcessor.cs
0.00% <0.00%> (ø)

....IntegrationEvents.Dapr/Processor/ProcessorBase.cs
0.00% <0.00%> (ø)

...ationEvents.Dapr/Processor/RetryByDataProcessor.cs
0.00% <0.00%> (ø)

... and 39 more

Continue to review full report at Codecov.

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


text:
Provider text

Codecov Report
Patch and project coverage have no change.

Comparison is base (d2377a2) 41.30% compared to head (3b6298e) 41.30%.

: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     #388   +/-   ##
=======================================
  Coverage   41.30%   41.30%
=======================================
  Files          15       15
  Lines        1058     1058
=======================================
  Hits          437      437
  Misses        575      575
  Partials       46       46

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

source: gharchive/pull-request

authors: codecov-commenter pivilartisant

repo: massalabs/thyra-plugin-wallet

license: MIT

license_type: permissive

license_source: github-api


text:
added colors

@Pierregvx this PR is in code review for a very long time. Please make sure to solve the comment ASAP so we can merge it.
It's blocking the story book to be tested correctly ;)
Also for front-end tickets, the review process is: 1) Paul or Max, 2) Mario. That's it! Way too many devs on this PR

authors: Pierregvx SlnPons

repo: massalabs/ui-kit


text:
Update README.md

add mcds's file


text:
whoops

whoops

يي

authors: annaPerdomo astromerov neom-im

repo: mckaywrigley/chatbot-ui


text:
#2052 - Config option to save audit events

@LJNIC - ack!  Sorry, I missed your updates!  Taking a closer look now.  Feel free to @-mention or ping on Discord or Slack if you ever feel like PR's are ignored!  Sorry again!

Merged in https://github.com/medplum/medplum/pull/2357
Thanks @LJNIC!

authors: LJNIC codyebberson

repo: medplum/medplum


text:
Update GitHub actions for Node 20

I tried to parallel lint, test and test:types, but since each require to re-run the use actions and pnpm install, it ends up taking 35 seconds instead of around 19 seconds. 🙃
Not sure there’s a way to parallel the few steps taking a couple of seconds nor if it’s worth it (probably not).

repo: meduzen/datetime-attribute

license: WTFPL


text:
Preparing for v.0.3.2

Codecov Report

Merging #12 (eba00d0) into master (f27f4dd) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #12   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity         9         9
===========================================
  Files              2         2
  Lines             11        11
===========================================
  Hits              11        11

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 f27f4dd...eba00d0. Read the comment docs.

authors: codecov-commenter mfvanek

repo: mfvanek/pg-index-health-test-starter


text:
Link watcher for flash notifications.

Link watcher with orange pi or ttgo via Bluetooth so it will show notifications with flash and alerts or error with buzzer sound.

source: gharchive/issue

repo: mhamidjamil/Watcher


text:
Remove unused global variables (#645)

Correct! We only use the nested table now.

repo: micahstairs/bga-innovation


text:
Merge main to release/v2 for 2.6.0-preview release

@jimmyca15, I think this needs to be merged by an admin. There are two issues here:

We dont have the buddy build yaml in release/v2 branch yet, so our build requirement is blocking the merge. This PR contains the buddy build pipeline so we should be able to run buddy builds on release/v2 in future.
Not sure why its showing that the changes are out of date with base branch. I dont see any merge conflicts, all the revert commits are stacked properly. Maybe you have permission to force merge it?

@avanigupta it says this branch is behind because of the merge commits in the release branch.

@avanigupta merged.

Oh that's strange. We always have extra merge commits in release branches, but I've never seen that message before. Thanks for merging @jimmyca15 !

authors: avanigupta jimmyca15 rossgrambo

repo: microsoft/FeatureManagement-Dotnet


text:
🐛 Add missing link references for "God Objects" and Ternary enum definition

@HolgerJeromin Thank you. Just applied the change.

repo: microsoft/TypeScript-Compiler-Notes


text:
Users/yueqianli/blender nopsexec

Amazing! Please adjust the PR title, and also scramble the data unless the perf data is ok to be public.

authors: LiYueqian-James yangpanMS

repo: microsoft/VirtualClient


text:
[TRANSLATION] added a Spanish translation for 8.1 section

@microsoft-github-policy-service agree

repo: microsoft/Web-Dev-For-Beginners


text:
Fix bug for wget when force_run is false and log file has been deleted

@squirrelsc Can we prioritize this PR?

@kamalca thank you for remaindering, merged.

authors: LiliDeng kamalca squirrelsc

repo: microsoft/lisa


text:
Provide more details in error message for decision and perf log files not found

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 72.02%. Comparing base (50e3008) to head (f4cd2d7).

Files with missing lines
Patch %
Lines

simulator/analysis/plot_utils.py
0.00%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
- Coverage   72.16%   72.02%   -0.15%
==========================================
  Files          21       21
  Lines        1024     1026       +2
  Branches      125      126       +1
==========================================
  Hits          739      739
- Misses        235      236       +1
- Partials       50       51       +1

Flag
Coverage Δ

unittests
72.02% <0.00%> (-0.15%)
:arrow_down:

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

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

authors: codecov-commenter jcamachor

repo: microsoft/vasim


text:
Fix a high hitting crash in ctest processing

If the break on line 175 was not hit before [cursor + i] grew larger than the length of the array, then untrimmedLine on line 173 would be assigned undefined and line 174 would throw an exception.

repo: microsoft/vscode-cmake-tools


text:
added -> operator to unique_wdf_object_reference

I'm not quite sure I see the utility of adding this. Overloading -> makes sense when what is returned is itself a pointer, so that you can apply indirection on it to access its fields/methods. But in this case, what is returned is a WDF object type like WDFREQUEST, which doesn't have any fields/methods. Can you please exemplify the use-case with some sample code?
Note that this is also the reason why unique_any also does not have an overloaded ->. unique_any is meant for "handle" types, not pointer types.

this is what I'd like to do:
wil::unique_wdf_object_reference<PDRIVER_OBJECT> device;
IoGetDeviceObjectPointer(&name, FILE_WRITE_DATA, &file_object, &device);
irp = IoAllocateIrp(device->StackSize, FALSE);

oops, sorry I screwed up.

authors: bevancollins rahul-ramadas

repo: microsoft/wil

license: mit

license_source: bigquery


text:
Notify for offline using device class

If works it can be used for instant battery notifications

repo: mikevansighem/homeassistant


text:
Logarithmic regression is not Found. It has been implemented?

Is it different to the logistic regression (which we have)?

Logarithmic regression is not the logistic regression, Logarithmic regression is like y = a + blnx, same to linear regression.

@targos https://github.com/DoubleCorner/regression-logarithmic I have implemented it ~

Hello,
If there is anything remaining related to this issue, please let me know.
Thank you.

authors: Aterolite24 DoubleCorner targos

repo: mljs/ml


text:
refactor: update useInterval.ts

:tada: This PR is included in version 0.12.12 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: morewings/react-forge-ui


text:
Update packages and translations

/botio test

Thank you!

authors: Snuffleupagus timvandermeij


text:
Create front end

LGTM!

authors: Kutuputih mraihanaf

repo: mraihanaf/SIOTICS-Garden-IoT


text:
💥 breaking: new structure + rocket chat (#72) (#75)

Codecov Report

Merging #76 (a8001c0) into main (ab28085) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #76   +/-   ##
=======================================
  Coverage   75.26%   75.26%
=======================================
  Files           2        2
  Lines          93       93
=======================================
  Hits           70       70
  Misses         23       23

authors: codecov-commenter mraniki

repo: mraniki/iamlistening


text:
[docs] Replace some images, gifs with videos

I think the videos are definitely more useful than the images! The only thing I noticed is that maybe some of them are too fast? Such as the one about theming. We do want to keep the videos short but maybe we can make it a bit easier for someone new to follow without having to pause the video?

I purposely made them 2x to reduce their size. I agree, users will have to pause and that's what I like about video over gifs.

Add some comments with what I think makes it more readable

repo: mui/mui-toolpad


text:
Update Composer dependencies (2021-04-10-00-10)

Visual regression test passed!
View the visual regression test report


text:
Build updates

Pull Request Test Coverage Report for Build #347
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

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 92.971%

Totals

Change from base Build #346:
0.0%

Covered Lines:
202

Relevant Lines:
217

💛  - Coveralls

authors: coveralls hazendaz

repo: mybatis/spring-native


text:
fix(api): minor changes

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

authors: napse-investment tomjeannesson

repo: napse-invest/django-napse


text:
OPERA-SDS-VnV-12: Verify the generation rate for the L3_DSWX_HLS product

Question: how does the system effectively catch up after it has been down for a certain amount of time?

repo: nasa/opera-sds-int


text:
Try

@daninesaing please do not open random issues, if you have one, please provide information

repo: nashsu/FreeAskInternet


text:
feat: add code coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@6a82a5c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage        ?   37.83%
  Complexity      ?       10
=======================================
  Files           ?        7
  Lines           ?       74
  Branches        ?        5
=======================================
  Hits            ?       28
  Misses          ?       46
  Partials        ?        0

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 6a82a5c...a3fb712. Read the comment docs.

authors: codecov-commenter ndaniskas

repo: ndaniskas/nu-localization-be


text:
add feature to support #39, use @javax.persistence.Transient

@wey-gu
What do you think of the beta release based on the current version.

@wey-gu What do you think of releasing a beta version based on current.

I am good with a beta release :)

I am good with a beta release :)

Has the release process we metioned earlier been determined ?
If not, this version would be released directly, ok ?

I am good with a beta release :)

Has the release process we metioned earlier been determined ? If not, this version would be released directly, ok ?

Yes, please release directly now :)

authors: CorvusYe wey-gu

repo: nebula-contrib/ngbatis


text:
broadcast and persist s3_sk_lsn

done

authors: arssher stepashka

repo: neondatabase/neon


text:
catch sigterm and exit go routines cleanly

Codecov Report

Merging #59 (db3815d) into main (ada5811) will decrease coverage by 0.05%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
- Coverage   52.23%   52.18%   -0.06%
==========================================
  Files          26       26
  Lines        1411     1422      +11
==========================================
+ Hits          737      742       +5
- Misses        641      647       +6
  Partials       33       33

Flag
Coverage Δ

unittests
52.18% <57.14%> (-0.06%)
:arrow_down:

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

Impacted Files
Coverage Δ

cmd/flowlogs2metrics/main.go
0.00% <0.00%> (ø)

pkg/pipeline/encode/encode_prom.go
77.93% <72.72%> (-0.61%)
:arrow_down:

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 ada5811...db3815d. Read the comment docs.

authors: KalmanMeth codecov-commenter


text:
Data utils

Hey @oesteban, do you know what this error is?

AttributeError                            Traceback (most recent call last)
Input In [44], in <cell line: 1>()
----> 1 transformed_nii = (~xfms).apply(nii)
File ~/miniconda3/envs/eddymotion/lib/python3.8/site-packages/nitransforms/linear.py:440, in LinearTransformsMapping.apply(self, spatialimage, reference, order, mode, cval, prefilter, output_dtype)
437 data = np.squeeze(np.asanyarray(spatialimage.dataobj))
438 output_dtype = output_dtype or data.dtype
--> 440 ycoords = self.map(_ref.ndcoords.T)
441 targets = ImageGrid(spatialimage).index(  # data should be an image
442     _as_homogeneous(np.vstack(ycoords), dim=_ref.ndim)
443 )
445 if data.ndim == 4:
AttributeError: 'NoneType' object has no attribute 'ndcoords'

Yup, you need to set a reference image for the transform

@oesteban The tests seem to be passing now, any thoughts or is this ready to merge?

Looks like the test failure is unrelated to this PR. Just one of those intermittent/random failures of the registration.

authors: arokem oesteban teresamg

repo: nipreps/eddymotion


text:
missing github repo in package.json

done.

repo: nonzzz/vite-plugin-stylex


text:
Leftpanel updates

power corrupts

repo: notorious-rubber-ducks/FEC


text:
solved issue and added quizes

@notsoocool  please review this

@notsoocool please review this pr

@KapuluruBhuvaneswariVspdbct why did you add the quiz?? and i have mentioned you earlier that you have to add the function in only layout.tsx file why did you added it to all the files??

authors: KapuluruBhuvaneswariVspdbct notsoocool

repo: notsoocool/codecache


text:
fix(): argument size change

Pull Request Test Coverage Report for Build 2954802228

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.461%

Totals

Change from base Build 2847521225:
0.0%

Covered Lines:
220

Relevant Lines:
220

💛  - Coveralls


text:
fix: don't hint to preload/prefetch styles loaded on page

Codecov Report

Merging #51 (db51ab5) into main (ad2e20e) will increase coverage by 0.01%.
The diff coverage is 100.00%.

: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.
@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
+ Coverage   97.54%   97.56%   +0.01%
==========================================
  Files           6        6
  Lines         530      533       +3
  Branches      112      112
==========================================
+ Hits          517      520       +3
  Misses         13       13

Files Changed
Coverage Δ

src/runtime.ts
99.30% <100.00%> (+<0.01%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter danielroe

repo: nuxt-contrib/vue-bundle-renderer


text:
Update asr proto for offline diarization

@ryanleary @findkim please review these proto changes for diarization

repo: nvidia-riva/common


text:
"确认关闭该会话"?这个提示过于繁琐了,觉得可以简化一下.

去掉吗？

不是去除,,,比如有些,"关闭"操作就没有必要在给这个提示了.现在的操作应该是只要是点击"标签页"的"关闭"就会提示这个"确认关闭该会话"这个对话框.个人觉得没这个必要去时时提醒的,,旨在关键窗口防止误操作给个提示即可,比如,打开了一个服务器连接窗口标签页,当关闭这个服务器标签时,这种带有危险性的操作时.,,,,其他的类似"设置""修改"会话属性等等这些非关键重要性的操作个人觉得没必要提示是否要关闭这样的提示的.

thanks! 我们可以考虑下
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2022年01月13日 23:34 |
| 收件人 | @.> |
| 抄送至 | @.@.> |
| 主题 | Re: [nxshell/nxshell] "确认关闭该会话"?这个提示过于繁琐了,觉得可以简化一下. (Issue #138) |
不是去除,,,比如有些,"关闭"操作就没有必要在给这个提示了.现在的操作应该是只要是点击"标签页"的"关闭"就会提示这个"确认关闭该会话"这个对话框.个人觉得没这个必要去时时提醒的,,旨在关键窗口防止误操作给个提示即可,比如,打开了一个服务器连接窗口标签页,当关闭这个服务器标签时,这种带有危险性的操作时.,,,,其他的类似"设置""修改"会话属性等等这些非关键重要性的操作个人觉得没必要提示是否要关闭这样的提示的.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>

确实有点频繁了，建议要么直接去掉，要么加个设置项，不再提示。

Agree. For tabs that are already disconnected from the remote server can be safely closed without alter.

最新版本已更新优化，请更新到最新版本体验，感谢关注与建议！

authors: bzw1204 hongruiji nxshell ywp-repo zeakey

repo: nxshell/nxshell


text:
minimal change for test PR

re: #27

repo: nychealth/EH-dataportal


text:
Pull request for task #316 - caching for user initiated search

@JanVana Hi, unless https://github.com/odalic/sti/issues/338 is solved, I cannot verify that turning off the cache worked.

@brodecva The issue #338 may not be fixed in the project. Please my comments on #338 on what to avoid when testing this pull request.

@brodecva The issue #338 may not be fixed in the project. Please my comments on #338 on what to avoid when testing this pull request.

OK. I was able in some cases to find the resource, and these were probably the few where the clas/properties restriction does not prevent from the resource to appear in the search results.
So this might verify that the caching indeed works as intended.

authors: JanVana brodecva

repo: odalic/sti


text:
fix(firehose): telegraf config parsing from shield metadata

closing in favour of #22

repo: odpf/dex


text:
feat(gen): initial webhook support

Closed to move branch from fork to this repo, use #622.

repo: ogen-go/ogen


text:
Research unit auth

Codecov Report

Merging #242 (d9b0480) into main (85aa927) will increase coverage by 0.06%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##             main     #242      +/-   ##
==========================================
+ Coverage   85.64%   85.71%   +0.06%
==========================================
  Files          19       19
  Lines         425      427       +2
  Branches       54       54
==========================================
+ Hits          364      366       +2
  Misses         56       56
  Partials        5        5

Impacted Files
Coverage Δ

backend/controllers/logs.js
55.55% <0.00%> (ø)

backend/controllers/admissions.js
71.42% <100.00%> (+1.21%)
:arrow_up:

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 85aa927...d9b0480. Read the comment docs.

authors: codecov-commenter suomalainenmari


text:
Add FirestoreGateway.updateDoc tests

All updates made here will be merged in the last PR (#211), in this nested chain of collection execution PRs.

repo: olmps/memo


text:
Release 3.8.1

Yeah, I don't think we should actually add that here, though, since we don't load that IG into the g10 validator.

@Jammjammjamm was there an issue with inferno core 0.4.19? I was wondering why it's locked on 0.4.18 now after these changes?

Yes, we inadvertently included a breaking change in 0.4.19. We released 0.4.20 yesterday to revert that change (#393 reverts the breaking change). None of the other changes in 0.4.19 seemed urgent enough to delay the g10 release, so we locked it to 0.4.18.

authors: Jammjammjamm nathanloyer


text:
Renamed CustomerID to clientID in baggage.md

@open-telemetry/specs-semconv-approvers Please have a look.

Hmm, for this one I don't think we need SIG approval, as it's just updating the example text to be consistent with the image.

authors: HsantoshaKumara cartermp theletterf


text:
pull request for e2e test at 12/02/2016 05:45:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
pull request for e2e test at 12/23/2016 23:15:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
pull request for e2e test at 01/19/2017 00:45:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
pull request for e2e test at 02/02/2017 09:15:16

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
pull request for e2e test at 12/02/2016 02:26:08

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
pull request for e2e test at 01/15/2017 03:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
:robot: Triggering CI on branch 'release-next' after synching to upstream/main

OCF Webhook is merging this PR

repo: openshift-knative/client


text:
bump version table, issue template

/retest

repo: openshift/oadp-operator


text:
Skip share test when there is no manila endpoint

/test

/hold

/hold cancel

We should backport it
/cherry-pick release-4.18 release-4.17 release-4.16

authors: MiguelCarpio itzikb-redhat

repo: openshift/openstack-test


text:
Correct a typo in the parameter name

thank you for fixing it, we also need to update the readme: https://github.com/openstack-k8s-operators/ci-framework/blame/main/ci_framework/roles/rhol_crc/README.md#L15

@raukadah oh, right, thanks!

/lgtm

authors: adrianfusco cjeanner raukadah


text:
Kvm create virtio-blk unit tests

@artek-koltun tests failed on
2023-03-16T12:45:55.4596984Z     --- FAIL: TestDeleteVirtioBlk/spdk_failed_to_delete_virtio-blk (0.00s)

due to
2023-03-16T12:45:55.4576875Z 2023/03/16 12:45:55 DeleteVirtioBlk: Received from client: name:"virtio-blk-42"
2023-03-16T12:45:55.4577172Z 2023/03/16 12:45:55 error: stub error
2023-03-16T12:45:55.4577555Z 2023/03/16 12:45:55 Error running underlying cmd on opi-spdk bridge: stub error
2023-03-16T12:45:55.4578298Z     kvm_test.go:434: Not all expected calls were performed

thanks for looking into the logs.
Apparently, race condition for callIndex member due to -race test option. Need some time to investigate and adjust. Pls do not merge

per @artek-koltun request waiting with this until race condition is addressed
-race adds some random delays to execution flow. Put a mutex around sensitive operations and ran the tests 50_000 times with no failures. Suppose we can merge the patch.

repo: opiproject/opi-spdk-bridge


text:
Apply version-buildId to createUiDefinition

Fixed by #21

repo: oracle/weblogic-azure


text:
A few small bugfixes

@ajsuth build errors resolved

repo: ordercloud-api/headstart


text:
feat: add package 'ykchorus'

I just released version 0.2.3 of ykchorus, but I would like to merge this PR before updating the PKGBUILD to have a real-life test whether the nvchecker notification triggers.

Also, congrats to your release 🥳

authors: SpotlightKid cbix

repo: osam-cologne/archlinux-proaudio

license: Unlicense


text:
Konflux pipelines

Looks sane to me I guess, but I am curious what changed to make this necessary?

The Konflux application+component disappeared. No idea how it happened.  So, I decided to use one application for both centos-bootc-c9s and bootc-image-builder components.

repo: osbuild/bootc-image-builder


text:
Limpiar json syft

Missing documentation and usage for this

Que documentación se puede crear para un script de parse?

Cómo se instala
Cómo se invoca.
Qué parametros tiene

Pero no se instala, y se llama desde la cli, los parámetros están dentro del docustring de la función

entonces ya está


text:
56 any doesnt match mocked objects

Codecov Report
Attention: Patch coverage is 92.85714% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 87.81%. Comparing base (ece9f1f) to head (cd82f69).

Files
Patch %
Lines

registry/handler.go
66.66%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
+ Coverage   87.54%   87.81%   +0.26%
==========================================
  Files          14       14
  Lines        1036     1042       +6
==========================================
+ Hits          907      915       +8
+ Misses        105      103       -2
  Partials       24       24

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

authors: codecov-commenter ovechkin-dm

repo: ovechkin-dm/mockio


text:
ci: remove cargo nextest because cargo test is now faster

Current dependencies on/for this PR:

main

PR #1341   👈

PR #1342

This stack of pull requests is managed by Graphite.

Merge activity

Nov 16, 12:31 AM: @Boshen started a stack merge that includes this pull request via Graphite.

repo: oxc-project/oxc


text:
fix(transformer): correctly jsx-self inside arrow-function

#3224  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


text:
Update Composer dependencies (2021-07-22-00-06)

Visual regression test passed!
View the visual regression test report

repo: pantheonsteve/nasdaq-buildtools-demo


text:
Visualizacion_2024_13_09

@Tokherd , seguiras usando el branch o lo borramos?

hola, lo seguire usando, lo agregue por accidente a  la main

authors: Tokherd jpgil


text:
feat(docs): add docusaurus integration

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

repo: parasutcom/frame-design-system


text:
Update: November 2023 Edition

No problem @ordian! There's also this in case you missed it:
https://github.com/ordian/kuddelmuddel/pull/4

repo: paritytech/pvf-checker


text:
[ci] Disable publish-crates-locally

Why not just set

allow_failure:                   true

@ordian because the job tries to upload 12198 files and directories as artifacts and this is too much. I'd prefer to disable it completely for now and find out with @joao-paulo-parity how it can be improved.

@joao-paulo-parity there are no artifacts now. Should we still collect them in this job?

there are no artifacts now. Should we still collect them in this job?

@alvicsam yes. This PR specifically doesn't produce artifacts because it has no changes at the moment, but other PRs will.

I've verified that the job doesn't exhibit the same problematic behavior on several occasions, so closing this

authors: alvicsam joao-paulo-parity ordian

repo: paritytech/substrate


text:
[DO NOT MERGE][ci] Test new benchmark runner

BENCHMARKS
   NATIVEWASMTIME   BENCHMARKMASTERPRDIFFMASTERPRDIFFWASMTIME OVERHEAD    execute/bare_call_0  1.03ms  1.04ms  :green_circle: -0.81%  902.39µs  914.03µs  :red_circle: 1.29%  :green_circle: -12%execute/bare_call_0/typed  542.59µs  527.21µs  :green_circle: -2.84%  420.88µs  405.10µs  :green_circle: -4.12%  :green_circle: -23%execute/bare_call_1  1.06ms  1.05ms  :green_circle: -0.37%  1.13ms  1.15ms  :red_circle: 1.36%  :green_circle: 9%execute/bare_call_16  2.41ms  2.15ms  :green_circle: -10.01%  4.79ms  4.79ms  :green_circle: -0.41%  :red_circle: 122%execute/bare_call_16/typed  1.51ms  1.49ms  :white_circle: -1.30%  2.17ms  2.04ms  :green_circle: -5.72%  :green_circle: 37%execute/bare_call_1/typed  628.10µs  615.68µs  :green_circle: -2.25%  701.27µs  754.47µs  :red_circle: 7.54%  :green_circle: 23%execute/bare_call_4  1.25ms  1.20ms  :green_circle: -4.64%  1.75ms  1.79ms  :red_circle: 2.73%  :green_circle: 50%execute/bare_call_4/typed  655.73µs  628.99µs  :green_circle: -4.39%  850.58µs  837.60µs  :green_circle: -1.32%  :green_circle: 33%execute/br_table  648.27µs  630.20µs  :white_circle: -4.26%  907.30µs  954.64µs  :red_circle: 4.88%  :yellow_circle: 51%execute/count_until  651.62µs  651.62µs  :white_circle: 0.02%  2.06ms  2.06ms  :white_circle: 0.23%  :red_circle: 217%execute/factorial_iterative  305.41µs  304.13µs  :white_circle: -0.42%  852.37µs  847.18µs  :white_circle: -0.72%  :red_circle: 179%execute/factorial_recursive  607.85µs  617.97µs  :red_circle: 1.63%  1.26ms  1.30ms  :red_circle: 3.35%  :red_circle: 110%execute/fib_iterative  1.63ms  1.43ms  :green_circle: -12.34%  4.47ms  4.47ms  :white_circle: -0.16%  :red_circle: 212%execute/fib_recursive  5.83ms  6.00ms  :red_circle: 2.75%  11.36ms  11.82ms  :red_circle: 4.00%  :yellow_circle: 97%execute/global_bump  948.88µs  950.11µs  :white_circle: 0.08%  3.73ms  3.29ms  :green_circle: -12.09%  :red_circle: 246%execute/global_const  717.86µs  717.81µs  :white_circle: -0.07%  2.32ms  2.32ms  :white_circle: -0.06%  :red_circle: 223%execute/host_calls  28.74µs  28.79µs  :white_circle: 1.23%  38.37µs  37.81µs  :green_circle: -1.44%  :green_circle: 31%execute/memory_fill  1.28ms  1.28ms  :white_circle: -0.10%  3.98ms  3.99ms  :white_circle: 0.00%  :red_circle: 211%execute/memory_sum  1.25ms  1.25ms  :white_circle: 0.10%  3.96ms  3.98ms  :white_circle: 0.79%  :red_circle: 218%execute/memory_vec_add  2.82ms  2.60ms  :green_circle: -7.95%  9.53ms  8.21ms  :white_circle: -7.09%  :red_circle: 216%execute/recursive_is_even  1.12ms  1.12ms  :white_circle: 0.26%  2.13ms  2.10ms  :green_circle: -1.34%  :yellow_circle: 88%execute/recursive_ok  145.74µs  146.29µs  :white_circle: -0.27%  295.06µs  309.81µs  :red_circle: 4.82%  :red_circle: 112%execute/recursive_scan  181.11µs  179.70µs  :white_circle: -0.45%  386.44µs  384.77µs  :white_circle: -0.37%  :red_circle: 114%execute/recursive_trap  14.40µs  14.97µs  :red_circle: 4.32%  28.39µs  28.29µs  :white_circle: -0.58%  :yellow_circle: 89%execute/regex_redux  546.72µs  556.34µs  :red_circle: 1.75%  1.46ms  1.45ms  :white_circle: -0.91%  :red_circle: 160%execute/rev_complement  509.09µs  510.01µs  :white_circle: -0.07%  1.43ms  1.43ms  :white_circle: -0.56%  :red_circle: 181%execute/tiny_keccak  373.48µs  371.95µs  :white_circle: -0.26%  1.22ms  1.22ms  :white_circle: 0.13%  :red_circle: 229%execute/trunc_f2i  923.00µs  911.50µs  :white_circle: -1.16%  2.43ms  2.43ms  :white_circle: -0.38%  :red_circle: 166%instantiate/wasm_kernel  63.19µs  60.90µs  :green_circle: -3.41%  92.98µs  67.28µs  :green_circle: -27.83%  :green_circle: 10%translate/erc1155  207.64µs  208.14µs  :white_circle: 0.29%  372.29µs  374.91µs  :white_circle: 0.65%  :yellow_circle: 80%translate/erc20  101.83µs  101.92µs  :white_circle: 0.10%  182.07µs  199.06µs  :white_circle: 4.34%  :yellow_circle: 95%translate/erc721  145.84µs  145.87µs  :white_circle: 0.04%  265.10µs  266.03µs  :white_circle: 0.60%  :yellow_circle: 82%translate/spidermonkey  0.00ns  0.00ns  :white_circle: 0.88%  0.00ns  0.00ns  :white_circle: -0.02%  :green_circle: 0%translate/wasm_kernel  3.80ms  3.77ms  :white_circle: -0.68%  7.05ms  7.04ms  :white_circle: -7.79%  :yellow_circle: 87%
Link to pipeline

authors: alvicsam paritytech-cicd-pr

repo: paritytech/wasmi


text:
Bump Go versions and use '.x' to always get latest patch versions

@QuentinPerez Ping

repo: parnurzeal/gorequest


text:
adds is_done to events to indicate they are in the past

Awesome, thx!

authors: jsoares suzannaaltman

repo: pathfindertools/scaling-filecoin


text:
Docker build

looks like this is breaking the netlify preview somehow, mind looking into this? I rely on it pretty heavily to review PRs so don't want to merge this until that's in a good state :)

I merged your main into my branch and the the build ran successfully this time. The original error message makes it seem like a flaky test could be the culprit:
"Uncaught exception: Error: 'expect' was used when there was no current spec, this could be because an asynchronous test timed out"

Thanks for fixing it -- yeah the tests have some asynchronous calls so unfortunately they can be flaky, but it usually passes locally for me.
I'll go ahead and merge this, but do you want to expand in the readme section about requiring powershell? Just don't want folks to get surprised by that requirement. And maybe a sentence on what advantages this has over building locally :)
thanks a bunch!

(also going to wait on the last checks to run)

authors: brandonmcclure pcottle

repo: pcottle/learnGitBranching


text:
Update becomes.n3

Thanks!

authors: josd phochste


text:
Create .gitattributes

Looks good to me

repo: php-fig/container


text:
introduce realcompact and basic theorems

I think this is ready and makes progress on #332. It'd be nice to have a counterexample for the converse of https://topology.pi-base.org/theorems/T000384 but I'd delay that to a future contribution.

Actually there's a pretty direct example, asserted at https://math.stackexchange.com/questions/4731883/

P162: the name of the property used in the literature is "realcompact".  Everybody who knows or cares about the property uses that name.  So I think that should be the main name, not an alias.  (It's also shorter, easier to parse in lists of theorems.)

As for "Closed subset of Euclidean space", that seems misleading.  As far as I know, Euclidean space always refers to some $\mathbb R^n$ with a finite $n$.  So would recommend to drop that, even as an alias.

P162 README: It would be good to add some equivalent more intrinsic definition, of which there are several, usually in terms of the Stone-Cech compactification.  I am not familiar enough with them to make a recommendation here.  This could be added later in a separate PR.

S3 is P162:  The same argument shows more generally that any discrete space is realcompact (embed D into $\{0,1\}^D$ (itself a closed subspace of $\mathbb R^D$) by sending $x\in D$ to its characteristic function.  So turning this into a theorem instead would be more general.

Not all discrete spaces are realcompact. If there were a proof of that, you'd prove that it's inconsistent that measurable cardinals exist, which is highly unlikely.

Thanks @Moniker1998, I'm reverting this to a draft until this is addressed.

P162 README: It would be good to add some equivalent more intrinsic definition, of which there are several, usually in terms of the Stone-Cech compactification. I am not familiar enough with them to make a recommendation here. This could be added later in a separate PR.

One definition using Stone-Cech compactification is by first defining the Hewitt realcompactification of $X$, If $X\subseteq \beta X$, consider the largest subspace of $\beta X$ in which $X$ is $C$-embedded. This is Hewitt realcompactification $\upsilon X$ of $X$. If $\upsilon X = X$ we say that $X$ is realcompact. Alternatively you can define $\upsilon X$ as set of those $x\in X$ such that if we consider any $f\in C(X)$ and $f^:\beta X\to \mathbb{R}^$, the map into extended reals, then $f(x)\in\mathbb{R}$.
There's also a definition using $z$-ultrafilters that I mentioned before. A space $X$ is realcompact iff every real z-ultrafilter $\mathcal{U}$ on $X$ is fixed i.e. we can find $x\in X$ such that $\mathcal{U} = {Z\in Z(X) : x\in Z}$. Here $Z(X)$ are zero sets of $X$.

@Moniker1998 So the characterization you used for the Mysior plane is the one in terms of z-ultrafilters then.

Yes, I used that definition to prove Mysior plane is not realcompact. It seems to be the most topological and direct, and seems to be the best tool in dealing with proving that something is realcompact when all other methods and theorems fail.

So as a summary, T000387 is false and unless we add the property of having non-measurable cardinality (which I don't see why anyone would do that), it's not fixable.
S000003 is realcompact, but not for the reasons given in the file
All regular Lindelof spaces are realcompact, and all pseudocompact spaces are realcompact iff they are compact.
Those properties should be deduced from other theorems, so the only concerning spaces for which property is yet to be determined should be those Tychonoff spaces that are not pseudocompact and not Lindelof, and I will only discuss those below:
Theorem 15.25 in Gillman and Jerison "Rings of continuous functions" states that any metric space of non-measurable cardinal is realcompact. Thus S000003, S000133, S000134 are realcompact.
This leaves us with six spaces S000057, S000074, S000091, S000107, S000135, S000137.
Corollary 8.18 in Gillman and Jerison tells us that since the identity map from S000107 to $\mathbb{R}^\omega$ with product topology, and $\mathbb{R}^\omega$ is hereditarily realcompact, it follows that S000107 is hereditarily realcompact. The same corollary applied to map from S000057 to $\mathbb{R}$ tells us that S000057 is hereditarily realcompact. Also the map from S000074 to closed half-plane ${(x, y) : y\geq 0}$ is continuous so S000074 is hereditarily realcompact. The identity map from S000135 to S000134 is continuous, so S000135 is hereditarily realcompact.
For S000091, I think I have a proof that it's not realcompact.

In this paper, https://doi.org/10.4153/CJM-1972-081-9 corollary 2 states that if $X$ is any normal metacompact $T_1$-space with the property that all discrete subspaces are realcompact (i.e. of non-measurable size), then $X$ is realcompact. In particular a normal metacompact $T_1$-space $X$ of non-measurable size is realcompact.
S000137 is a normal metacompact $T_1$-space of size $|Y| \leq |X| = 2^{2^\mathfrak{c}}}$. Since $2^{2^{\mathfrak{c}}}$ is non-measurable, S000137 is realcompact

I'm new to github and how it all works, so let me know if I'm writing in a wrong place.

Sorry for letting this slide. I'm going to try to fix up the PR now but if time runs out I'll take a stab next week.

Okay let's try this again @prabau.
Thanks for the notes @Moniker1998 - I haven't done much with large cardinals in my work, but I'm hoping I'm right in understanding that the reals have non-measurable cardinality in ZFC, so we have theorems to get all metrizable spaces of cardinality $|\mathbb R|$ or less listed as realcompact.
I don't like to make huge pull requests, so I did not implement all your notes. I encourage you to move what I didn't address to an appropriate Issue or Discussion. You're also welcome to join us at the next community meeting https://github.com/orgs/pi-base/discussions/334 and we can find a time for someone to sync up with you to walk through how to make a pull request yourself if you like.

I only have few comments on your additions.
T000387 and T000387 could be one theorem by using P000059 which already exists in pi-base
Additionally it could be strengthened by:

In this paper, https://doi.org/10.4153/CJM-1972-081-9 corollary 2 states that if X is any normal metacompact T1-space with the property that all discrete subspaces are realcompact (i.e. of non-measurable size), then X is realcompact. In particular a normal metacompact T1-space X of non-measurable size is realcompact.

i.e. T_4 + metacompact + smaller than or equal continuum => realcompact
It would be good to replace those two theorems with this one.
As for measurable cardinals, if $\exp^n(\kappa) := \exp(\exp^{n-1}(\kappa))$ and $\lambda\leq \exp^n(\aleph_0)$ for some $n$, then $\lambda$ is non-measurable. Here $\exp(\kappa) = 2^\kappa$ so that $\exp^n$ is iterated exponentiation of cardinals. Reference could be found in "Rings of continuous functions" by Gillman and Jerison, though it could probably be also found in some set theory texts. Measurable cardinals are unimaginably huge.

So I think "non-measurable cardinality" might be worthwhile to add as a property. As a ZFC database, no space in the pi-Base will ever be marked as "not non-measurable cardinality". But we could have P59 imply this property, and then we could use this property with your suggested theorem, mostly for future-proofing (e.g. if we add "Cardinality $=\aleph_7$", we could mark it as non-measurable with a theorem).

At this point I'm waiting to merge in #350 before this.

So I think "non-measurable cardinality" might be worthwhile to add as a property. As a ZFC database, no space in the pi-Base will ever be marked as "not non-measurable cardinality". But we could have P59 imply this property, and then we could use this property with your suggested theorem, mostly for future-proofing (e.g. if we add "Cardinality =ℵ7", we could mark it as non-measurable with a theorem).

I agree wholeheartedly.  That was going to be my first comment.

Okay maybe now this is really, really ready. @prabau

ah nuts let me add the other realcompact characterization

P164 (non-measurable cardinality): I don't think "Certain Subsets of Products of metacompact ..." should be a reference for this.  How about replacing it with mention of Gillman & Jerison, ch. 12, which explains the notion of measurable cardinality very clearly.
T383: "inaccessible" means strongly inaccessible in this case, right?  Could be good to spell it out.  I don't see measurable cardinals mentioned in the wikipedia article about Inaccessible cardinal.  On this other hand, inaccessible is mentioned in the wikipedia article about Measurable cardinal, so that might be a better reference.  Also Gillman & Jerison section 12.6 says: "Theorem 12.5 states that the smallest measurable cardinal (if any exist) is strongly inaccessible."  That could be another ref.
https://babel.hathitrust.org/cgi/pt?id=uc1.b4407145&view=1up&seq=179

Sounds good. Feel free to incorporate those and merge if you get to it before I do.

Sounds good. Feel free to incorporate those and merge if you get to it before I do.

Sure, I'll do that.  I may also have a few more substantial comments, still taking a look.

My last comment was about T382 (T4 + metacompact + nonmeasurable card ==> realcompact), which I had some reservations about.  The justification given is a paper of Zenor, which I have not read, but seems difficult and also using results involving notions not in pi-base, and make use of results referenced in other papers.  All fine for a research article, but maybe not exactly the best for a reference in pi-base?  I tried to find a more self-contained account of this, but in particular could not find the result even mentioned in the realcompact chapter of Encyclopedia of Gen Topology (Hart, Nagata, Vaughan) or in Engelking.
On the other hand, there are more basic results about realcompact spaces that are not even in pi-base.
Also, the first sentence of the Zenor paper refers to the more basic result that in discrete spaces realcompactness is equivalent to nonmeasurable cardinality.  That is also proved in Gillman & Jerison and Engelking.  One half of this: [discrete + realcompact ==> nonmeasurable] cannot currently be deduced in pi-base and would seem to be worth having.  The other half [discrete + nonmeasurable ==> realcompact] is not there, but deducible from the proposed T382, assuming we want T382.
Maybe I am mistaken about this, but I would find it worthwhile, if only just for myself, to have a brief discussion in the meeting tomorrow about how to approach a result like T382.

It'd be hard to find something like this in Engelking when it's an article from 2018, I think. It's very new research.
We could stick to result for metrizable spaces instead, being well-established, if using such a new result bothers you, and switch to this one when someone carefully checks its validity.

I think https://www.cambridge.org/core/services/aop-cambridge-core/content/view/CF5EC3B7193934ABD4F84FD8C8504467/S0008414X00037986a.pdf/certain_subsets_of_products_of_metacompact_spaces_and_subparacompact_spaces_are_realcompact.pdf is pretty clear? Cor 2 says T4 metacompact spaces with () are realcompact, and according to the introduction () is equivalent to discrete subspaces having non-measurable cardinality. Phil taught me topology as an undergrad so I'm willing to trust him on this. ;-)

Ok, sounds good.  I'll approve a little it later.  Need to be off my computer right now.

As for [discrete + realcompact => non-measurable], it certainly wouldn't hurt to have, but it probably wouldn't serve much of a purpose other than being a theorem on pi-base.

I agree it wouldn't be used to determine any traits of any sample spaces.  Still, seems it would be good to have for the record.

Thanks @Moniker1998 for pushing this forward! Please feel free to contribute more PRs fleshing out realcompact results in the pi-Base now that we've got some scaffolding for them.

authors: Moniker1998 StevenClontz prabau

repo: pi-base/data


text:
S87 Update.

Why do you have so many commits? Is there something wrong in the way you are editing files?  What editor are you using exactly?

I have done it here on the website, for each step it would make a commit. I need to learn how to use an editor.

Here are a few pointers on how to do things more effectively.
You should use a more convenient editor that allows you to modify multiple files at the same time and then do a commit covering these changes involving multiple files.  The recommend editor is the one from github.dev, which you can also use directly from the web site.
By the way, remember the recommendations I gave you in https://github.com/pi-base/data/issues/677#issuecomment-2197900369, about how to become familiar with the basics, and specifically to go through the hello world tutorial, get familiar with git and the github help and the github.dev editor?  That would really be useful, instead of jumping ahead and creating more work for everyone unnecessarily.  I really recommend you to experiment with creating branches, deleting branches, commits, edit multiple files, github.dev, etc in your own repository first, where it's completely isolated and you can try everything to your heart's content.
To get to github.dev from the "Files changed" tab of a particular PR, typing a single dot (.) will bring up the github.dev editor.  That also works from the "Code" tab from the top level page for a repository, for example your https://github.com/Almanzoris/Alman_pibase repo.
Another useful point: if you work on a branch forked from the main repository (like the branch S87 for this PR), every time you do a commit, there is automatic compilation of it in the background (which you can see in the Actions menu: https://github.com/pi-base/data/actions) to determine if there are any obvious errors.  The commit is then marked with either a green checkmark (good) or a red cross (not good).  So when you commit something, you should wait for the compilation to finish, and if you see a red cross, you should follow up and see the cause of the mistake and fit it then, instead of piling up more commits on top, all failing.  To check what the problem was, you can directly click on the red cross next to the bad commit and look at "Details".  In this case, it mentions a problem with refs:.
Anyway, it does not matter if this PR take more time.  We don't care if pi-base gets updated now or in a week.  But take this as an opportunity to learn the basics.  I suggest you play with github.dev, etc and when you feel comfortable, I'll give you more feedback about minor content changes to complete this PR.  How does that sound?

Sounds fair. I am going to follow that.

@Almanzoris As you can see in https://github.com/orgs/pi-base/discussions, tomorrow 3pm EST we have our monthly zoom meeting.  If you can join, that would be great.  We could do a demo to show how to use github.dev/vscode.

Sure! I will try to join and get to follow the demo. Thanks for your dedication.

authors: Almanzoris prabau


text:
link some more editors, mostly self-linking ones

Thanks!

authors: matkoniecz piebro

repo: piebro/openstreetmap-statistics


text:
remove should be optimized

With JsonPtr we walk the tree from the root, since we have information about every parent node, there is an opportunity for a more optimized implementation based on prepare/patch

interesting benchmark
posFromPtr:
  Collected 1000000 samples in 2.3879 s
  Average time: 0.0016 ms
  Stddev  time: 0.0002 ms
  Min     time: 0.0001 ms
  Max     time: 0.0207 ms
270
traverse:
  Collected 1000000 samples in 1.9752 s
  Average time: 0.0012 ms
  Stddev  time: 0.0001 ms
  Min     time: 0.0000 ms
  Max     time: 0.0255 ms
270
parent:
  Collected 1000000 samples in 1.9107 s
  Average time: 0.0011 ms
  Stddev  time: 0.0000 ms
  Min     time: 0.0000 ms
  Max     time: 0.0051 ms

Working backwards is as slow as the opposite with all those string comparisons but faster than splitting the string.

fixed in 472561e5dd28f88fc9945f488872055fb26711c5 . It need a benchmarks.

Code that got discarded, it used an iterator
iterator posFromPtr(tree: JsonTree; path: string; n: NodePos; noDash = true): NodePos =
  # Warning: must break from the iterator manually when nilNodeId is returned.
  var n = n
  yield n
  var cur = ""
  var last = 1
  while last <= len(path):
    var first = last
    while last < len(path) and path[last] != '/':
      inc(last)
    let last1 = last == len(path)
    copyTokenToBuffer(cur, path, first, last)
    case n.kind
    of opcodeObject:
      unescapeJsonPtr(cur)
      n = rawGet(tree, n, cur)
      if not n.isNil: yield NodePos(n.int-2)
      yield n
    of opcodeArray:
      var i = getArrayIndex(cur)
      if i == -1:
        if not noDash and last1: yield NodePos(n.int+n.operand); break
        else: raiseSyntaxError(path)
      block searchLoop:
        for x in sonsReadonly(tree, n):
          if i == 0:
            n = x
            break searchLoop
          dec i
        yield nilNodeId
    else: yield nilNodeId
    inc(last)

proc remove*(tree: var JsonTree, path: JsonPtr) =
  ## Removes `path`.
  var insertPos: seq[PatchPos] = @[]
  for x in posFromPtr(tree, path.string, rootNodeId):
    if x.isNil: break
    insertPos.add x.PatchPos
  var n = insertPos.pop().int
  if insertPos.len > 0 and kind(NodePos insertPos[^1]) == opcodeKeyValuePair:
    n = insertPos.pop().int
  let diff = span(tree, n).int32
  while insertPos.len > 0:
    let pos = insertPos.pop().int
    let distance = tree.nodes[pos].operand - diff
    tree.nodes[pos] = toNode(tree.nodes[pos].kind, distance)
  let oldfull = tree.nodes.len
  for i in countup(n, oldfull-diff-1): tree.nodes[i] = tree.nodes[i+diff]
  setLen(tree.nodes, oldfull-diff)

proc posFromPtr(tree: JsonTree; path: string): NodePos =
  result = nilNodeId
  for x in posFromPtr(tree, path.string, rootNodeId):
    result = x
    if x.isNil: break


text:
rotation, redrawing

ah ... about the performance issue, i see that in the help, there are currently scopes with clip:1 ... those are way slower than the unclipped versions. should i change this?

repo: porres/pd-else


text:
Support existing figures, dash integration & improving docs

Codecov Report

Merging #26 (7f9399b) into main (234ea36) will decrease coverage by 1.72%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
- Coverage   96.68%   94.96%   -1.73%
==========================================
  Files           5        5
  Lines         302      318      +16
==========================================
+ Hits          292      302      +10
- Misses         10       16       +6

Impacted Files
Coverage Δ

plotly_resampler/figure_resampler.py
93.80% <70.00%> (-2.39%)
:arrow_down:

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 234ea36...7f9399b. Read the comment docs.

authors: codecov-commenter jonasvdd

repo: predict-idlab/plotly-resampler


text:
fix: remove unexpected .tsbuildinfo file

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

Comparison is base (455b9e7) 85.45% compared to head (cd8fc32) 85.45%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #185   +/-   ##
=======================================
  Coverage   85.45%   85.45%
=======================================
  Files           8        8
  Lines         165      165
  Branches       49       49
=======================================
  Hits          141      141
  Misses         21       21
  Partials        3        3

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

authors: JounQin codecov-commenter

repo: prettier/pretty-quick


text:
WIP: filter workloads in/out

so?

authors: CMGS anrs


text:
support SyncGroupReqV0/V4/V5 encode and SyncGroupRespV0/V4/V5 decode

Codecov Report

Merging #21 (672617c) into main (f3f8a47) will decrease coverage by 0.12%.
The diff coverage is 83.96%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   90.83%   90.71%   -0.13%
==========================================
  Files          55       55
  Lines        2236     2336     +100
==========================================
+ Hits         2031     2119      +88
- Misses        154      162       +8
- Partials       51       55       +4

Impacted Files
Coverage Δ

codec/sync_group_resp.go
80.70% <66.66%> (-4.60%)
:arrow_down:

codec/sync_group_req.go
92.80% <89.87%> (-0.96%)
:arrow_down:

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

repo: protocol-laboratory/kafka-codec-go


text:
MLC Blog Post

@susanev I think that because of the upcoming work on provider authoring, we probably don't want to publish this.

repo: pulumi/pulumi-hugo


text:
Dummy auth

DummyAuth in interuss has a GET /token endpoint only. However, during various UTM tests USSes have been using FIMS auth server, which has a POST /token endpoint. Hence, while trying to run uss qualifier tests with dummy auth, rather than having to make changes in USS to use GET endpoint of dummy auth, it was better that dummy auth had a POST /token endpoint. The spec used to add POST endpoint is from FAA FIMS spec. There is no validation added for message signed headers, the aim is to provide an interface for USSes that have been using POST /token endpoint.
There are also well-known endpoints that have been added for the flow of getting tokens using POST endpoint.

repo: punamverma/dss


text:
Staging env

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Subramanian:x: kksubbu72Subramanian seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: puppetlabs/control-repo


text:
Goodies changes

 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.Selma Vidimlic seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: qgis/QGIS-Hugo


text:
chore: Stylistic changes

Do we care about the failing coverage test? How do we want to handle this in the future?

Thanks! Currently we can ignore it.

authors: david-zwicker qiangyicheng

repo: qiangyicheng/flory


text:
don't pin requirements

Closing in favor of #105

repo: qiskit-community/qiskit-research


text:
Allow asynchronous request handling

Implemented in v2

repo: qixils/java-crowd-control


text:
l10n/po/ja_JP/_guides/infinispan-client.adoc.po

https://github.com/quarkusio/ja.quarkus.io/pull/844


text:
Updated to 3.5.0

It wouldn't have helped with this update, since it's a proper migration, but do we want renovate or dependabot running on this sample?

We have a Quarkus 3 branch that contain this.

authors: holly-cummins phillip-kruger tqvarnst

repo: quarkusio/todo-demo-app


text:
Aggregation

Codecov Report

Merging #1262 (d35d65d) into main (732f684) will decrease coverage by 0.12%.
The diff coverage is 24.65%.

@@            Coverage Diff             @@
##             main    #1262      +/-   ##
==========================================
- Coverage   94.27%   94.15%   -0.13%
==========================================
  Files         206      211       +5
  Lines       34992    35361     +369
==========================================
+ Hits        32990    33295     +305
- Misses       2002     2066      +64

Impacted Files
Coverage Δ

src/aggregation/bucket/histogram.rs
0.00% <0.00%> (ø)

src/aggregation/bucket/range.rs
0.00% <0.00%> (ø)

src/aggregation/metric/average.rs
0.00% <0.00%> (ø)

src/lib.rs
98.82% <ø> (ø)

src/aggregation/agg_tree.rs
100.00% <100.00%> (ø)

src/indexer/segment_updater.rs
94.44% <0.00%> (-0.92%)
:arrow_down:

src/store/index/mod.rs
97.83% <0.00%> (-0.55%)
:arrow_down:

src/directory/watch_event_router.rs
96.15% <0.00%> (-0.03%)
:arrow_down:

src/reader/warming.rs
95.21% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #1262 (dbb96a3) into main (d18ac13) will increase coverage by 0.02%.
The diff coverage is 93.65%.

@@            Coverage Diff             @@
##             main    #1262      +/-   ##
==========================================
+ Coverage   93.98%   94.00%   +0.02%
==========================================
  Files         204      213       +9
  Lines       34539    35552    +1013
==========================================
+ Hits        32461    33422     +961
- Misses       2078     2130      +52

Impacted Files
Coverage Δ

common/src/writer.rs
94.33% <ø> (ø)

query-grammar/src/user_input_ast.rs
97.77% <ø> (ø)

src/aggregation/bucket/histogram.rs
0.00% <0.00%> (ø)

src/aggregation/bucket/range.rs
0.00% <0.00%> (ø)

src/aggregation/executor.rs
0.00% <0.00%> (ø)

src/aggregation/metric/average.rs
0.00% <0.00%> (ø)

src/collector/count_collector.rs
100.00% <ø> (ø)

src/collector/filter_collector_wrapper.rs
84.84% <ø> (ø)

src/collector/mod.rs
48.21% <ø> (ø)

src/directory/directory_lock.rs
88.88% <ø> (ø)

... and 155 more

Continue to review full report at Codecov.

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

@PSeitz : Good job! I think you solved all of the technical difficulties.
We can now focus on :

Making the code easier to enter: I think this is already quite readable.
Doing a definitive pass on the object names, and then writing a short README for the agg directory explaning the relationship of the different objects however would be helpful.
Add unit tests ?
Some cleanup (remove commented code, etc.?)
Eventually add more metric aggregation... but that's not necessary right away I guess. We can merge, and integrate with quickwit, and then add functionality if you prefer.

authors: PSeitz codecov-commenter fulmicoton

repo: quickwit-oss/tantivy


text:
submission for intern-project

Thanks for the submission! Closing so others don't look at the solution.

repo: rainmakerresearch/intern-project


text:
Livewire 3 support

Hi @VincentBean!
I'm currently working on supporting Livewire 3, I hope to release this soon.

Support for Livewire 3 has been released in version 3.0.0 :rocket:

Awesome!

authors: VincentBean ramonrietdijk

repo: ramonrietdijk/livewire-tables


text:
Improving release notes visibility

@nunix I added a button library I found out there, in fact this is used in docusaurus docs as an example of importing external components, that's why I choose this one. I am not sure if there is any other recommended way of doing it for our docs.

repo: rancher/elemental-docs


text:
Add istio 1.4.3

This PR needs to rebase on https://github.com/rancher/system-charts/pull/143 and rerun script to pick up kiali fix.

repo: rancher/system-charts


text:
Migrate trustworthiness and silhouette_score stats from RAFT

CI failures are fixed by https://github.com/rapidsai/cuvs/pull/314

/merge

repo: rapidsai/cuvs


text:
[FEA] Update to Arrow v8.0.0

Might as well figure them out on my machine, I'm likely to spend a couple more days refactoring and improving #392.

authors: thomcom trxcllnt

repo: rapidsai/node


text:
Fix wait for multiple tasks

@github-actions crossbow submit -g example

@github-actions crossbow submit -g example

authors: kou raulcd

repo: raulcd/arrow


text:
update live-cat-library

➡

repo: ray-streaming/live-cat-library


text:
when copy/pasting a tagged node, it should get untagged

rsCopyPaste now has fetcher_is_tagged function to validate if an input is tagged

repo: raysunvfx/Input-Fetcher


text:
Added the OutOfProcessPlugin Template

 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.

Closing older PRs. Pls resubmit on latest branches if required.

authors: CLAassistant DineshkumarJP anand-ky

repo: rdkcentral/rdkservices


text:
Add missing concatenation operator

Thank you :+1:

authors: BlueM TomasVotruba

repo: rectorphp/getrector-com


text:
Tracking issue: Add web-viewer to examples and docs

Some potential steps:

Add blueprint_url query param to web
Deprecate url query param, replace with recording_url or similar
Fix the styling issue where the viewer tries to take over the whole screen with position: absolute
Save all recording and blueprint files from all of our examples (including code-examples` snippets)

We decided not to have the viewer inline for now, but link to it instead. The data-inline-viewer is repurposed as a means to transform a screenshot to an app.rerun.io example link.
Remaining work:

https://github.com/rerun-io/rerun/pull/5618

authors: emilk jprochazk

repo: rerun-io/rerun


text:
Refactor claimRewards parameters

Updated to respond to your comments @cajubelt, going to merge for now.

repo: revo-market/contracts


text:
AWS Cloudfront 도입

#25 해당 pr에서 해결

repo: rhythm-gamers/rg-front


text:
Add files via upload

Thanks


text:
SECURITY.md

It's just a template


text:
Use proper casing and naming in all columns

Pull Request Test Coverage Report for Build 1166677340

6 of 7 (85.71%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 89.793%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pygef/gef.py
4
5
80.0%

Files with Coverage Reduction
New Missed Lines
%

pygef/gef.py
3
90.34%

Totals

Change from base Build 1165943256:
0.0%

Covered Lines:
1126

Relevant Lines:
1254

💛  - Coveralls

authors: coveralls tversteeg


text:
Add Symbol types

Supports roblox-ts/roblox-ts#1826, roblox-ts/roblox-ts#2537, and roblox-ts/roblox-ts#2616

authors: Dionysusnu osyrisrblx

repo: roblox-ts/compiler-types


text:
Feat.asset layer changes

closed because included in #1430

repo: rodekruis/IBF-system


text:
Use social media to point to our site

This is already happening! Wahoo!

authors: lisaratner rossettistone

repo: rossettistone/bizport


text:
Page layout with checklist

@rossettistone ready for your review


text:
Can this be used with copilot?

Not really no, copylot has a very different purpose... and to my knowledge does not provide an API, but if I am wrong please let me know...

authors: midichlorianrich royerloic

repo: royerlab/napari-chatgpt


text:
Docs v2 add simplified Chinese translation

Looking great, nice work!

authors: laiiihz rrousselGit

repo: rrousselGit/riverpod


text:
Update deku

I'll wait till https://github.com/sharksforarms/deku/pull/454 to get this working, that mistake really hurt this library.


text:
Use uv for pip package installs

#573  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @carolineechen and the rest of your teammates on  Graphite

repo: run-house/runhouse


text:
Change Confined::try_from to take impl AsRef<[C::Item]>

Not possible: requires allocation. Confined::try_from_iter should be used instead

repo: rust-amplify/rust-amplify


text:
adds thermal aspects

@JuliaRegistrator register

Error while trying to register: Register Failed
@bodokaiser, it looks like you are not a publicly listed member/owner in the parent organization (ryd-yb).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.

authors: JuliaRegistrator bodokaiser


text:
Fix setup.py classifier (forgot a comma, f**k)

Codecov Report

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

@@           Coverage Diff           @@
##           master      #26   +/-   ##
=======================================
  Coverage   97.58%   97.58%
=======================================
  Files          15       15
  Lines         496      496
=======================================
  Hits          484      484
  Misses         12       12

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 c78ed51...24082fb. Read the comment docs.

authors: codecov-io ryukinix

repo: ryukinix/decorating


text:
Add tutorial for error mitigation and qnn training.

Also fixes all remaining examples, hence closes issues #171 , #164, and #117

Apart from the gitignore, it  looks good to me 😄

authors: David-Kreplin MoritzWillmann

repo: sQUlearn/squlearn


text:
added Quick Sort.js

@all-contributors add @Hashininirasha for code


text:
BinarySearch.java

Upload another code, this one already exists

repo: sainik-khaddar/MY-LEETCODE-SOLUTIONS


text:
chore: sync package.json

no downgrades

authors: SF-CLI-BOT mshanemc

repo: salesforcecli/plugin-user


text:
Switch (back) from revue to convertkit

📝 Changed routes:

/newsletter

(view full size)

And 1 other route:

/api/subscribe

Commit e47ffd9dd1b737151af25c35380d96fe71b744d1 (https://samuelkraft-next-lu6mhdlb5-samuelkraft.vercel.app).

repo: samuelkraft/samuelkraft-next


text:
[java, nightwatch] - native clip selector and ignore selectors on mobile native full page

LGTM

authors: kb-kerem paweltomaszewskisaucelabs

repo: saucelabs/visual-sdks


text:
[2.x] Fix SbtRefactorings and run SessionSettingsSpec

This is used for session save?

This is used for session save?

Yes, I think so

repo: sbt/sbt


text:
docs: Gocq 部署流程改为分离部署教程，修正错误的提示，优化文件命名

感觉没什么需要改的，但szz说要来点review

星尘佬，给个 Approve 啊苦呀西

repo: sealdice/sealdice-manual-next


text:
Run CI on pre-release Julia versions instead of nightlies

Ambiguity issue on pre-release run due to https://github.com/fhs/ZipFile.jl/issues/108


text:
docs: add react with vite installation guide

@samuelkurdz Thanks so much for creating the docs for this. Can we move it to installation.mdx?

Can we move it to installation.mdx?

I was thinking the same thing. It would be great to have tabs in the Installation page for all the different frameworks.

@samuelkurdz Thanks so much for creating the docs for this. Can we move it to installation.mdx?

@shadcn  Yes of course.
Although I initially created the React with vite page like a sub-page under installation.
 {
  title: "Installation",
  href: "/docs/installation",
  items: [
    {
      title: "React with vite",
      href: "/docs/react-with-vite",
      items: [],
    },
  ],
},

but it did not appear as such.

@samuelkurdz Something like this:

Is anyone on this? or can I?

@samuelkurdz I don't think so, go ahead

@dan5py I kind of have a decision between the page quick links by the right.
so I want to share between the options I created.
1.

2.

@samuelkurdz  I think the first is cleaner.

@dan5py PR updated.

@samuelkurdz This looks great. Question: do we want the following config in tsconfig.json?
"baseUrl": ".",
"paths": {
  "@/*": ["./src/*"]
}

So that aliases such as @/components/... are resolved?
Here's a CodeSandbox I was testing: https://codesandbox.io/p/sandbox/shadcn-ui-vite-m9ry84?file=%2Ftsconfig.json%3A8%2C22

Yeah, this would keep the same aliases for different frameworks.
So I suggest keeping the @ alias format:
- alias: [{ find: "src", replacement: path.resolve(__dirname, "./src/") }],
+ alias: [{ find: "@", replacement: path.resolve(__dirname, "./src/") }],

And also the CLI prompt would remain the default ones:
- Configure the import alias for components: › src/components
- Configure the import alias for utils: › src/lib/utils
+ Configure the import alias for components: › @/components
+ Configure the import alias for utils: › @/lib/utils

@shadcn @dan5py
I experimented with your suggestions and it works if the tsconfig.json and vite.config.ts updates comes first.
So I will be updating this PR. Thanks.
Without that
Configure the import alias for components: › @/components
Configure the import alias for utils: › @/lib/utils

This above created an @ folder in the root of the application that contains the components and utils file.

This above created an @ folder in the root of the application that contains the components and utils file.

Yeah I'm aware of this. Just add the paths on the Edit tsconfig.json step.

This above created an @ folder in the root of the application that contains the components and utils file.

Yeah I'm aware of this. Just add the paths on the Edit tsconfig.json step.

Updated!

By the way, this is my first open-source contribution. Thanks for being nice!

No. Thank you. This is amazing!

By the way, this is my first open-source contribution. Thanks for being nice!

You did a really great job! 🎉

Really nice !!!!!! Thanks for supporting Vite :)

I am curious, CLI will be work on this ? @shadcn @samuelkurdz ?

Hi @samuelkurdz,
@mdloop is developing the installation page with Tabs where the content of each framework has its own file (to keep things cleaner). If #753 gets merged I'd like you to add the docs for vite that you created.

@dan5py Should this one be merged first or #753?

@dan5py Should this one be merged first or #753?

First #753. Then @samuelkurdz will update this PR.

@samuelkurdz The new layout has been merged to main. You can now add the vite docs. Thanks in advance 💪.

Awesome. Thanks so much @samuelkurdz

authors: CarlosZiegler dan5py samuelkurdz shadcn

repo: shadcn/ui


text:
Shakil

update


text:
Add links to DESCRIPTION

What are the odds...

Thanks to both of you!

authors: krlmlr olivroy shchurch

repo: shchurch/countland


text:
[fix][#4572] clear master on cloning page

Coverage remained the same at 0.0% when pulling 65bafc2a74e9328e4e915deaf75d0c9c595f71c5 on fix-ss-4572 into aadc461df0a8f1eaa1da6a4cd9df48bc284524fb on master.

repo: shirasagi/shirasagi


text:
Uploading new soundtracks and themes

didnt know how to include the other main music track, that's the reason for closing and not merging this pr


text:
implement signing JWT

Pull Request Test Coverage Report for Build 3097606232

0 of 45 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.9%) to 43.784%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/jsonutils/encode.go
0
7
0.0%

jwt/jwt.go
0
38
0.0%

Totals

Change from base Build 3095205459:
-1.9%

Covered Lines:
479

Relevant Lines:
1094

💛  - Coveralls


text:
Gamepad support

Look great, can wait to try it out :) Still waiting for my Joy-Con to arrive. Quick note: I’d remove all commented console.logs. They were clearly used for debugging purpose and are not needed anymore. Don’t you think?

Oh, I'm sorry, I'm forgot remove this "feature")

authors: jag-k pepelsbey

repo: shower/core


text:
changes

NutriVision


text:
Setup github action check jobs for EL8 and EL9

/build rpm


text:
[FRE-1238, FRE-1242] fix history page stuck loading

Im not getting routes on this branch!
https://github.com/user-attachments/assets/2a95d2a8-c4d0-4648-85ea-5ea24208b0f7

huh works fine on my end @ericHgorski

huh works fine on my end @ericHgorski

usually I can break loop with clicking max or clearing inputs but that didnt work this time for some reason.
also changed the max-width so it didnt squeeze the time since info. rest LGTM!

authors: codingki ericHgorski

repo: skip-mev/skip-go


text:
fix: add asserts syntax in json imports

Current dependencies on/for this PR:

main

PR #89   👈

This comment was auto-generated by Graphite.

repo: skyleague/therefore


text:
K8s Test Runner - Add support for service account

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

Project coverage is 16.84%. Comparing base (5ae1d04) to head (f5fca0d).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #868      +/-   ##
==========================================
+ Coverage   16.79%   16.84%   +0.05%
==========================================
  Files          36       36
  Lines        4419     4440      +21
==========================================
+ Hits          742      748       +6
- Misses       3597     3613      +16
+ Partials       80       79       -1

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

@skudasov pls review

authors: codecov-commenter lukaszcl


text:
query is breaking when first loading

It only throws that error on signin and looks like it fixes itself by the time user-search is loaded


text:
add container option in tag

done


text:
pull request

merge

merge

repo: snake-fl/tiktokshop-php


text:
Create PSWAPliquidvestingRFP

Could this also be done by using NFT's to represent the remaining vested rewards?

repo: sora-xor/rfps


text:
feat: trigerring release

:tada: This PR is included in version 4.1.0 :tada:
The release is available on:

v4.1.0
GitHub release

Your semantic-release bot :package::rocket:

authors: srv-rr-github-token uoboda-splunk

repo: splunk/pytest-splunk-addon


text:
Automated Package Upgrade

:tada: This PR is included in version 2.2.119 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: sprucelabsai/spruce-error


text:
Automated Package Upgrade

:tada: This PR is included in version 25.3.144 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: sprucelabsai/spruce-schema


text:
Automated Package Upgrade

:tada: This PR is included in version 7.0.88 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: sprucelabsai/spruce-test


text:
feat: Get rid of custom image for lakehouse Spark job

Good catch! We might want to put the contents in the spark docs, as customers will properly ask how to build custom images (we might already have it in the docs ^^)

repo: stackabletech/demos


text:
updated dependencies

Task linked: RND-2488 Update and test Stackbit NPM dependencies for starters

authors: TomasBankauskas youvalv

repo: stackbit-themes/nextjs-starter


text:
Future3 ooo patch 1

formatting updates

repo: stakervali/grincc-next


text:
fix(starknet_integration_test): fix config when creating multiple nodes

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2348
#2426  👈 (View in Graphite)
#2299
#2242
#2253
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

authors: reviewable-StarkWare yair-starkware

repo: starkware-libs/sequencer


text:
Console api experiments

🚀 Deployed on https://62cf5376c689c95a5a84714b--cozy-fox-0defec.netlify.app

authors: jacob-statsig jasonwzm

repo: statsig-io/docs


text:
YELLOW-5904

LGTM! Perhaps nice to also get rid of the Cellar module?

Sure, we will need to refactor this whole decoding anyways.

repo: stimtech/go-bankid


text:
ACM 10581 MCH asserts HubSize to MCE

/lgtm

repo: stolostron/multiclusterhub-operator


text:
New Rule (Attachment): HTML file contains exclusively Javascript

/update-test-rules

authors: aidenmitchell morriscode

repo: sublime-security/sublime-rules


text:
Update ja.json

Thank you very much. The PR will be included in next release.

repo: sunner/ChatALL


text:
feature/SLARA-9_document_usage_in_readme

@SirNarsh  comments

[ ] Group properties by operation
[ ] Describe "why to override properties ?"

@amrography conflicts

Resolved

authors: HassanElZarkawy amrography

repo: supaapps/supalara


text:
chore(ci): Reduce CI time

Is it time to use yarn@3 ?

Not sure. I'm doing this mainly because some crates like swc uses way too much time

repo: swc-project/swc


text:
fix(controller): fix condition to validate user congregation role

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


text:
ci(ci/cd): refactor pipelines

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


text:
Update Composer dependencies (2023-03-05-00-08)

Visual regression test passed!
View the visual regression test report


text:
Refactor resetPassword

Lisätty, hyvä huomio 👍

repo: tasera-ry/tss


text:
Upgrade GSRI modpack

pending the rest of the milestone issues

done


text:
111

111


text:
Ensure SDK does not retry "internal" errors

See the list of retryable client codes:
https://github.com/temporalio/sdk-php/blob/master/src/Client/GRPC/BaseClient.php#L22

authors: bergundy wolfy-j

repo: temporalio/sdk-php


text:
Tnsor

@Fergibson,
Could you please provide the details about what platform you are using (operating system, architecture). Also include your TensorFlow version if you are having any issue on the tensorflow side. Thank you!

Closing this as stale. Please reopen if this is still a valid request. Thank you!

authors: Fergibson tilakrayal

repo: tensorflow/tensorflow


text:
Remove nobradobic from codeowners /python/ add vcanic

Resolved.

repo: tenstorrent/tt-mlir


text:
@ #iorad/devops/148 | use latest dev img, lockfile

@datphan please make sure CI checks are passed

authors: datphan hoatle


text:
Add stim effects to item stats

.deploy

repo: the-hideout/tarkov-dev


text:
remove git diff and reformat

hi @thenickdude, i was trying to work through this and get proxmox up and running on ec2 but was unsuccessful. after updating the cloud-init script to remove the git diff detail and fix the formatting the installation seems to complete, and i get the log output all the way to

Welcome to the Proxmox Virtual Environment. Please use your web browser to
configure this server - connect to:

  https://<my-ip>:8006/

------------------------------------------------------------------------------```
but so far have not been able to reach the UI over the public ip associated with the ec2 instance. If you have any further information that could help i'd love to know your thoughts. Im new to proxmox and was hoping to help a user in our open source community. looking forward to hearing from you. thanks in advance!

Networking is broken without this patch applied, you can't just remove it like this.
Which version of Proxmox are you testing?

thanks for letting me know, im using the cloud-init.yaml from this repo with no changes (noted the hostname and fqdn can be set up top) but the latest release
https://github.com/thenickdude/proxmox-on-ec2/blob/master/cloud-init.yaml#L71-L72

Probably my patch doesn't apply on the latest version, I'll try it out and update it

hi again, im not sure what i did different this time around, but i just restarted the walk through and was able to successfully get on the box and get to the proxmox ui, the most notable change was the ssh key update when proxmox took over the ec2 instance i think

Yep, looks like the cloud-init script still works with the very latest version of Proxmox, it tested fine for me here too.
It's possible there was a race condition where the networking was restarted at the wrong instant

authors: jarededwards thenickdude


text:
chore(ci): add codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@19b7c8a). Click here to learn what that means.
Patch has no changes to coverable lines.

: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      #36   +/-   ##
=======================================
  Coverage        ?   66.35%
=======================================
  Files           ?        8
  Lines           ?      428
  Branches        ?        0
=======================================
  Hits            ?      284
  Misses          ?      115
  Partials        ?       29

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

authors: codecov-commenter thevilledev

repo: thevilledev/vault-plugin-secrets-vercel


text:
feat: node interfaces + migration

PR inludes now:
Node objects:

Added field interfaces
Removed field uptime


text:
Started branch develop

@gabrielpalves let's merge this PR

authors: gabrielpalves tiagokretzerwalter

repo: tiagokretzerwalter/wedding-planner


text:
🌐 Update Chinese translation for docs/zh/docs/tutorial/sql-databases.md

📝 Docs preview for commit b39f2bb400ac987bbe3874fdaa28af4a5685fdf8 at: https://c33476c1.fastapitiangolo.pages.dev

Thanks for the help! :partying_face: @chaoless @mahone3297

authors: alejsdev chaoless tiangolo

repo: tiangolo/fastapi


text:
Add fw cmd to get UDI

Merged. Note that this requires https://github.com/tillitis/tillitis-key1/pull/43 in firmware.

authors: mchack-work quite


text:
test_failure_33 ast that has UOps.UNMUL after linearize

from #5269

repo: tinygrad/tinygrad


text:
[etc] application Link 생성 로직 추가

잘못된 브랜치 생성으로 새 브랜치로 다시 작업하여 pr 올렸습니다.

repo: tmax-cloud/hypercloud-multi-operator


text:
Create UML Model Creation for the Cardiovascular Data Generator

Requirements:

Study the Data Generator:
○ Begin by examining the source code and documentation of the cardiovascular
data generator provided in the GitHub repository.
○ Understand how the data generator creates and assigns unique IDs to each
patient and how it generates sequential cardiovascular data, ordered by
timestamp.
Identify Key Components:
○ Identify the main classes and interfaces within the data generator. Consider the
following aspects:
■ The structure of patient data: What attributes are being simulated (e.g.,
heart rate, blood pressure, oxygen saturation)?
■ Data generation mechanisms: How the generator simulates the flow of
data for multiple patients.
■ Unique patient ID assignment: How patient IDs are generated and
managed.
○ Note the output strategies. These are the ways that the software outputs the
generated data.
Design the UML Class Diagram:
○ Using a UML modeling tool of your choice, design a class diagram that
represents the structure and relationships of the classes identified in the data
generator.
○ Ensure your class diagram includes:
■ Class names and visibility.
■ Attributes and operations of each class, with appropriate data types and
visibility.
■ Relationships between classes, including association, aggregation, and
inheritance as applicable.
■ Multiplicity notations to indicate the number of instances in relationships.
Incorporate Realism:
○ While the data generator simulates patient data, your class model should
realistically reflect what actual patient monitoring data might encompass. This will
help in later stages when extending the generator's functionality.
Documentation:
○ Accompany your UML diagram with a brief documentation that explains the
rationale behind the design decisions you made. Include any assumptions or
simplifications you have adopted.


text:
Switch to kind.local for tests with ko

no reason to get this in.


text:
fix: escape brace in regex

Thanks! What problems did this cause (no tests failed)?

it's for https://github.com/tree-sitter/tree-sitter/pull/2838

authors: amaanq calebdw

repo: tree-sitter/tree-sitter-php


text:
add 'CryptoLyzer'

Para adiciona uma moeda digital siga os seguintes passos (1) crie uma conta numa corretora confiável (2) adicione dinheiro. Corretora de criptomoedas no valor e pronto você adicionou uma moeda digital.😂

ok

authors: DellFensse c0r0n3r goshtdreamer

repo: trimstray/the-book-of-secret-knowledge


text:
feat(react-query): add skipToken functionality

FYI @Gabrola I think this broke tsr.posts.get.useQuery.useQuery({ options }) "options" parameter types for me.
We are using "@ts-rest/react-query": "3.50.0" and upgrading to 3.51.0 makes the "options" parameter resolve to "any". This is as far as I've investigated. Let me know how else I can help.

@jhleao not sure if I follow, or if you mean the useQuery(options) and not useQuery({ options })
If the former, I am not having this issue. You can see here that the types are working properly.
If the latter, there was never an options property in the options object.

authors: Gabrola jhleao

repo: ts-rest/ts-rest


text:
Containerise using Docker.

Added postgres to docker container

repo: tsotetsi/bloodhound


text:
Some change

Close for final re-run


text:
Main known UI enhancements of turms-chat-demo

#1309
Support of Text#selectionHeightStyle:

https://github.com/flutter/flutter/issues/68675
https://github.com/flutter/flutter/issues/154231

repo: turms-im/turms


text:
[feature] 是否能支持导出pdf等类型文件

暂时不支持，做完大部分基础功能后，后面会放到迭代计划


text:
Release version 1.1.0

👍

authors: jeremydurham samn

repo: twitter-fabric/galley


text:
latest Zanata translation changes in uberfire-extensions from 2016-09-07

+1 to merge.

authors: kiereleaseuser manstis

repo: uberfire/uberfire-extensions


text:
5.0.0/features/front

Pull Request Test Coverage Report for Build 11809778430
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

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 100.0%

Totals

Change from base Build 11715306468:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls

authors: Isoldios coveralls


text:
Introduce Swift Formatting

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

repo: unum-cloud/usearch


text:
Temporary disable swift-format to figure out issues with building swift-format on CI

See original issue: https://github.com/val-lang/val/issues/222

hmm... CI seems to behave in completely unexpecred ways today... not sure why swift-format check is still running after the last commit.

repo: val-lang/val


text:
webcast player fixes

also moved the VOD-only events to IVbrickVideoEmbed and added the load event to IVbrickBaseEmbed

repo: vbrick/rev-sdk-js


text:
Phone numbers should be recognised and clickable in room history

+1, there are on riot-android now: https://github.com/vector-im/riot-android/issues/1077

authors: jeangb manuroe

repo: vector-im/riot-ios


text:
Add example for (connecting to) endpoints

ping @jobergum

Much better!

authors: jobergum kkraune

repo: vespa-engine/pyvespa


text:
More comments in the signalling code

[minor] could you add your name to your comments to follow Eric's convention? I know people can use git blame but sometimes these are harder to follow.
// Note(erd):

authors: RoxyFarhad ohEmily

repo: viamrobotics/goutils


text:
Added my profile

Hey @devwander
You need to provide at least 5 bookmark links and those bookmark links should be your twitter or LinkedIn bookmarks not your social links.

authors: devwander vijayyprajapati

repo: vijayyprajapati/Share-Your-Bookmarks


text:
Latest gradle

Code Coverage

Total Project Coverage
36.17%
:white_check_mark:

repo: violinyanev/my-kitchen


text:
docs: only selected animated examples added.

only tool change

repo: vizzuhq/ipyvizzu


text:
Cu 28888wh

Task linked: CU-28888wh Подкрутить  сi

repo: vkrivozubov/dressed-app


text:
Add Maven Wrapper

This was already merged as part of #684.


text:
Fixes for cuda

These changes seem to increase speed exponentially, however they result in a fatal error (see image)
@phhusson this is a patch reflecting the changes in the patch you uploaded here. Did you happen to see anything similar to this on your end?

I just updated with cuda support.  Does it match the performance you achieved?

@kuprel yes I am able to generate images in approximately 25 seconds without mega, 1 minute with (both using torch).
i have an rtx 2080s, wondering if there's a way to get this to run even faster


text:
Set up Semantic Layer + Viz on Preset

The connection with Preset

Could not get the databricks connection to load any table into the Preset workspace and our transformation stages were still ongoing. In the interest of time, decided to switch dashboard plan over to Databricks SQL.

Issue closed and new issue for DB created


text:
fix: Post release patchs

This PR is included in version 1.0.1 :tada:

repo: wandb/terraform-azurerm-wandb


text:
Wheelhouse builder

closing as it is outdated

authors: kptkin vanpelt

repo: wandb/wandb


text:
FIX : Invisible Player / Default skin / Removing Hat ( with mask )

Thank you

authors: kukiiii wasabirobby

repo: wasabirobby/fivem-appearance


text:
Updated unit tests workflow

Previous commit excluded python 3.7 from the wrong Ubuntu version, now fixed.

repo: whad-team/whad-client


text:
Use the customElement decorator instead of customElements.define function

Depends on https://github.com/43081j/eslint-plugin-lit/issues/195


text:
Create Dynamic Clipping library for impression and duration measurements

This change is


text:
debug

debug模式不进行代码织入（太浪费时间）

debug模式不进行代码织入（太浪费时间）

这个你自己项目根据需求进行开关配置就好了

authors: protectedMan wurensen


text:
create a sky

This was fixed by just setting zone sky 1

repo: xackery/eqgzi


text:
Bugfix: Remove TActiveTransaction from TExecutionUnit.OpsInFly on cancel

Там кстати тесты трейсинга подозрительно фейлятся, возможно что-то меняется в том как оно трейсится?

Там кстати тесты трейсинга подозрительно фейлятся, возможно что-то меняется в том как оно трейсится?

Не похоже, вот например та же самая ошибка
https://nebius.testmo.net/automation/runs/results/7923?group_id=6538226&test_id=120091931
Но могу перезапустить конечно для верности

authors: kunga snaury

repo: ydb-platform/ydb


text:
Operator needs to recover missing tasks and solved them

Duplicated


text:
Test against PHP 8.3

I've updated vimeo/psalm to the latest version in the master branch. Please, rebase your PR.

Thanks!

authors: snapshotpl yethee

repo: yethee/tiktoken-php


text:
Add a full stack blog feature

Need to start writing technical blogs on my own blogging platform. Add blog implementation with MDX format.


text:
拷贝有些漫画需要登录才能看到，比如相合之物，但这里登录也搜不到

没有接入登录相关的功能，sorry了

没有接入登录相关的功能，sorry了

之后可以做么

后面也不考虑接入，因为做登录兼容插件工作量大，非常抱歉

authors: youniaogu yuduotianguang

repo: youniaogu/MangaReader


text:
typescriptGraph は Promise を返す

Warnings

:warning:
Please include a description of your PR changes.

:warning:
This PR does not include changes to tests, even though it affects app code.

Messages

:book:
PR Title: typescriptGraph は Promise を返す

TypeScript Graph - Diff
flowchart
    classDef modified fill:yellow,stroke:#999,color:black
    subgraph src["src"]
        src/outputGraph.ts["outputGraph.ts"]:::modified
        src/index.ts["index.ts"]:::modified
        src/addStatus.ts["addStatus.ts"]
        src/extractAbstractionTarget.ts["extractAbstractionTarget.ts"]
        src/extractNoAbstractionDirs.ts["extractNoAbstractionDirs.ts"]
        src/log.ts["log.ts"]
        src/config.ts["config.ts"]
        src/getRenameFiles.ts["getRenameFiles.ts"]
        src/getFullGraph.ts["getFullGraph.ts"]
        src/index.test.ts["index.test.ts"]
    end
    src/outputGraph.ts-->src/addStatus.ts
    src/outputGraph.ts-->src/extractAbstractionTarget.ts
    src/outputGraph.ts-->src/extractNoAbstractionDirs.ts
    src/outputGraph.ts-->src/log.ts
    src/outputGraph.ts-->src/config.ts
    src/index.ts-->src/getRenameFiles.ts
    src/index.ts-->src/getFullGraph.ts
    src/index.ts-->src/outputGraph.ts
    src/index.ts-->src/log.ts
    src/index.test.ts-->src/index.ts
    src/log.ts-->src/config.ts
    src/getFullGraph.ts-->src/log.ts
    src/getFullGraph.ts-->src/config.ts

  Generated by :no_entry_sign: dangerJS against 3094e4b852c2e01b14e5e51058b86c7144f2f1e2


text:
云联壹云企业版的api与开源版是一样的吗？

开源版和企业版接口一致。

repo: yunionio/cloudpods


text:
gateway路由这一块我目前有个问题弄不清楚，例如我能看到虚拟机列表这个请求 200 2368d4 GET /api/v1/parameters/LIST_VMInstanceList (10.96.0.1:48150) 13.56ms  但是这个路由是怎么注册的呢？由谁注册的呢？

pkg/mcclient/modules/yunionconf/mod_parameters.go init 函数
是 pkg/apigateway/handler/init.go 引用后，自动注册的apigateway是转发请求到各个服务，路由入口可以看下pkg/apigateway/handler/resource.go


text:
assertions: use AssertJ

has been merged

authors: termitehuegel yxyx-github


text:
feat: add alissonsleal bun entry

Seu PR está em draft propositalmente?

@zanfranceschi sim, essas últimas validações me quebraram KKKK
Estou ajustando aqui e quando estiver pronto eu deixo como ready

@zanfranceschi PR pronto pra subir :rocket:

authors: alissonsleal zanfranceschi


text:
d_menu_ring OK

Thanks! What was the issue?

All good saw it in discord

repo: zeldaret/tp