SpringBoot incompatibility with Jetty 8.1.15 and newer

Gretty farm throws exception:
This context is immutable

when running on Jetty 8.1.15.v20140411 and spring-boot. Cannot upgrade to Jetty 8.1.15.v20140411 until it is fixed.
Jan 2015: the problem is still present with Jetty 8.1.16.v20140903, cannot upgrade.
We are staying with Jetty for a while 8.1.8.v20121106.

@akhikhl did this ever cause an integration-test to fail?


Remove card borders

This PR would remove the borders on nested cards (introduced in HA 2022.11), resolving #2.
Before:

After:

👍Great PR, tested on my instance


fix typo

Can one of the admins verify this patch?

Codecov Report

Merging #828 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #828      +/-   ##
===========================================
- Coverage     25.61%   25.6%   -0.01%
- Complexity     6048    6049       +1
===========================================
  Files          1398    1398
  Lines         83523   83523
  Branches      11701   11701
===========================================
- Hits          21392   21389       -3
- Misses        60076   60079       +3
  Partials       2055    2055

Impacted Files
Coverage Δ
Complexity Δ

...he/kylin/job/impl/threadpool/DefaultScheduler.java
74.41% <0%> (-2.33%)
12% <0%> (ø)

.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java
63.84% <0%> (-2.31%)
0% <0%> (ø)

...core/storage/columnar/GeneralColumnDataReader.java
94.73% <0%> (+5.26%)
7% <0%> (+1%)
: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 800d1c5...1c21211. Read the comment docs.

Pull Request Test Coverage Report for Build 4980

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.004%) to 28.073%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
2
68.46%

core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java
2
80.23%

Totals

Change from base Build 4977:
-0.004%

Covered Lines:
23447

Relevant Lines:
83523

💛  - Coveralls


fix #632

Fix #632  and fix #637

I can't open the error detail page, @AMecea  could you give me a hand ?

@jianhaiqing can I help you with the tests?

@jianhaiqing can I help you with the tests?

@jianhaiqing can I help you with the tests?

I really appreciate it.

@jianhaiqing can I help you with the tests?

I really appreciate it.


Ingress route not updated when deployments are replaced

It appears that we only create the ingress route when we create a deployment and not when we replace a deployment. This might be an issue for developers that are updating ingress paths in their code but not seeing the change on FTL.
Is this something we'll want to support @alecthomas?

Definitely.

I think this was fixed by #857


MINOR: Use equals instead of ==

A few issues found via static analysis.

This includes #183 by @eribeiro with the right attribution (so he will get the credit for this PR). @eribeiro, can you please close #183?

Thanks for fixing these issues.
The change LGTM but is a bit larger than what I feel comfortable without a JIRA (it includes added assertions to a test). Can you open a JIRA, describe the changes and link here?

@gwenshap, I can file a JIRA sure. Note that the assertions are for verifying the MockClient change (it doesn't affect any prod code).

LGTM as well. I am fine either with a JIRA or not, so its your call :)

@guozhangwang @gwenshap Thanks both for reviewing. I filed the JIRA and updated the PR title.

+1. looks good.

Merged to both branches.


Startup Silently

Description of the new feature / enhancement
I expect the software will start silently on Windows boot.
Scenario when this would be used?
PowerToys will startup without showing the settings window. If the feature already exists, please guide me turn on this.
Thanks for the support team 🥰
Supporting information
No response

Thank you for replying to me. I have tried reinstalling the latest version and restarting Windows but PowerToys still shows the setting window like below:

I mean I want this settings window not to appear when I start Windows

I'm wondering if somehow there is a dual 'on startup' somewhere.  if you execute the runner again, we make it so settings will pop up.
that would explain the behavior.  our stuff has it start as a task for UAC.  wondering if maybe you have it in startup apps as well.
/needinfo


Known Issue Migration to dotnet/dnceng

[x] New Infra Known Issues will need to be opened in dotnet/dnceng
[x] Update Known Issue documentation to point to dotnet/dnceng
[x] Migrate the Known Issue template to dotnet/dnceng (delete the one in Arcade)
[x] Update Known Issue code to search for issues in dotnet/dnceng
[x] Update functionality that adds Known Issues to the Known Issue GitHub project
[x] SEE IN THREAD COMMENT FOR BUGS THAT NEED TO BE SORTED

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[x] Internal Infrastructure Improvements

Release Note Description

Known Issue and Critical Infrastructure service will now look in both dotnet/arcade and dotnet/dnceng for issues.
Infra Known Issues to be created in dotnet/dnceng instead of dotnet/arcade

Completed!


Add 2006 interface

Usage
This will add the 2006 interface for the fixed viewport for those who like era when there was combination between 2007 and 2005.
Lastly it will increase the 2005 inventory icon size to match the way it was in 2005, similar to the way the 2006 inventory icon is bigger.
Example
2006 interface

2005 interface before

2005 interface after

You should separate the two changes in this PR into two logical commits.

How would we get this into the client? I have it created. Would be nice to have it in the main RuneLite Client.
https://i.imgur.com/Nn3YS6U.png

If this ever ends up being added I'd like to recommend the tab icons I've included. They more accurately reflect the correct locations for the icons as they were in 2006 (OP's icons aren't quite in the right spots on the tabs). See @UGot0wnedBS picture (icons I've included are those) to this picture of RS (https://img.fireden.net/vg/image/1463/39/1463390620282.png). It also includes the minimap sprite fix from #3501 and colored quest and magic tab icons (needs the raids icon).
2006.zip

It was not, we have 2005 and 2010

Please add this ^

Bumping this as maybe we can get this into the client.
If someone needs the images, I have a folder with the icons. https://i.imgur.com/92llFII.png

I think the part of this which fixed the 2005 inventory icon has since been done. If someone wanted to rebase this with just the 2006 skin I wouldn't mind looking at it again.

Lovely bump D:

I'm working on rebasing this. Due to a busy weekend, I only expect to have this ready by Sunday

I've rebased this and tested the 2006 interface ingame and can confirm it looks "correct". (that is, it doesn't have any wonky positions that I can see)

I've rebased this and tested the 2006 interface ingame and can confirm it looks "correct". (that is, it doesn't have any wonky positions that I can see)

Hope to see it soon :D


Earlgrey: aes_core doesn't work in yosys

aes_core.sv file requires aes_reg_pkg.sv but this file is currently not working in yosys: https://github.com/alainmarcel/uhdm-integration/issues/274

Already moved to UHDM. Closing.


sort unbonding prioritization by validator capacity

Context
Until unbonding from 32+ validators in a single batch is support, this sorts by capacity first to reduce the number of messages.
Changelog

Removed condition to sort unbondings by balance ratio
Added ConsolidateUnbondingMessages in the event that the number of messages is still greater than 32. This function will redistribute the remainder proportionally to each validator in the batch.

Testing

Tested with the unbonding simulator and a large unbond amount (3x the current mainnet amount):

Using mainnet code: 92 messages
Using just the sorting change: 34 messages
Using this branch: 32 messages

LGTM
Looks good in that this is a temporary fix and the times we would fail with error (ie. respond we can't unbond this incoming request) are very unlikely situations in practice.  We are really scraping weird edge cases and most of the time this will work without any issue.  I think everything is sound and your modifications made the algorithm conceptually clearer.

The one edge case I'm thinking through is if the validator's with the highest capacities are NOT the validators with the highest delegated amounts. In this case, the algorithm might return a failure if we're unable to unbond from the highest capacity validators, when we would have instead been able to unbond from the highest delegated validators.

Yeah very good callout! My mental model for this is that for non-LSM chains, this algorithm should behave no different than just splitting messages purely based on weights. And for LSM chains, we target the validators with the most LSM stake first.
So this failure case occurs if the validators with the most LSM stake also all happen to be 0 weight - which in practice, it should be the opposite!
Also, each time we rebalance, this gets "reset"
@shellvish


Setting collectExpiry to NO not respected when scanExpiry set to YES

The functionality I would like to have is the scanner should attempt to scan expiry date, but if it fails the fallback should not be card.io collection (since we have our own form for this with extra validation)
Steps to reproduce:
Using the sample app, add the following lines after initialising the scanViewController:
scanViewController.scanExpiry = YES;
scanViewController.collectExpiry = NO;
scanViewController.collectCVV = NO;

Then scan a card while covering the expiry date and leaving the number visible.
Expected results:
The user should not be prompted to enter an expiry, instead the user should be able to immediately select Done with no prompt to enter an expiry date.
Actual results:
The correct card number is shown, with expiry field shown (as first responder). Done button is disabled until an expiry date is entered

@wattson12 here's the current logic in card.io:

If collectExpiry is NO, then do not attempt to get the expiry, either by scanning or by typing.
If collectExpiry is YES, then

if scanExpiry is NO, collect the expiry in the Manual Entry screen;
if scanExpiry is YES, then

try to scan the expiry;
if expiry-scan was successful, then pre-fill the Manual Entry screen's expiry field;
regardless of expiry-scan success, present the Manual Entry screen to collect/confirm the expiry.

When in the Sample App I set the scanViewController properties as you've described, I can't reproduce your results. Instead, the above logic does indeed seem to be followed: the card number is scanned and the Manual Entry screen never appears.
Getting back to your original question, if what you want to accomplish is to have card.io scan the card and then report back to you its card number and expiry results (which have not yet been confirmed by the user), without ever presenting the Manual Entry screen, then there's a straightforward solution: use a CardIOView rather than a CardIOPaymentViewController.

OK it looks like my case is an edge case which falls outside the current logic:

if scanExpiry is YES, then

try to scan the expiry;
if expiry-scan was successful, then pre-fill the Manual Entry screen's expiry field;
if scan failed AND collectExpiry = NO then don't show expiry entry, otherwise show entry

I will look into using the CardIOView directly though, thanks for the advice and quick response

@wattson12 let us know if you run into any problems with the CardIOView.

Hello,
Scan Expiry is possible using only CardIOView ?
Thanks

@marcoslacerda you can set scanExpiry = YES (which is its default setting) for either a CardIOView or a CardIOPaymentViewController. It works the same in both cases.

Yes!
But, always return 00/00
Other question, cardHolderName works only using CardIOPaymentViewController?
Thanks

@marcoslacerda Unfortunately, CardIO succeeds at expiry scans far less often than it succeeds at card-number scans. But this is the same for either CardIOView or CardIOPaymentViewController. The only difference is that the latter then provides a way for the user to enter the expiry manually.
Re cardHolderName you are correct. This is purely a manual-entry field. CardIO cannot scan the cardholder name.

Debtor for its attention @dgoldman-ebay


ngb-modal no longer scrolable

Modals with long content is no longer scrollable:
Now:

Before:

Implementation from ng-bootstrap, current state and design diverge. Decide which direction to go with this.

@Cian77 and @kaloyanso can you have a look on this and decide how we should implement the scrollbar in the modal.
If there are questions, please contact one of the @swisspost/design-system-maintainers.

Design is up to date https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=16696%3A55910&mode=design&t=nvIt9DZwzRtuNOSk-1

Close as won't fix


fix #89 httpsへのリダイレクト

IBM Cloud toolchain: Delivery Pipeline deployed ir-server to dev, including commit f740363354e7e56f509fa702cea83c8aa9fd14bd


GEI CLI reports 301 and won't queue a migration for a recently renamed repo

Description
The GEI CLI checks if a repo name is already in use before calling the GEI backend to queue a migration. If you rename a repo instead of deleting it then you end up with a 301 response when trying to queue a migration. Which stops the CLI from moving forward.
Reproduction Steps

Migrate a repo. For example, migrate a repo into a new repo called foo.
Rename that repo after the migration completes. For example, rename foo to foo-1.
Try to queue the migration again with the original repo name as the target. For example, try to migrate into foo again.
Note that the CLI errors out on the 301 response from GitHub.

I think removing the when clause on this line should fix it: https://github.com/github/gh-gei/blob/6365933024e905e1fa5d2d9396e30c32a8a27fa9/src/Octoshift/GithubApi.cs#L109

I think it's better not to swallow all exceptions and just modify the when clause to include HttpStatusCode.Moved)


Consider using from file Stream snippets in samples

See comment: https://github.com/Azure/azure-sdk-for-net/pull/11491/files#r413015866

Given that we did not receive negative feedback regarding this matter in the 2 years since this issue was created, I believe this is not an actual concern. Closing this issue.


[spi_device] addr_mode in CMD_INFO to support forced 3B/4B address

This PR changes CMD_INFO fields to support forced 3B/ 4B address commands.
Some of the SPI host issues always 4B address commands. Previous SPI_DEVICE design only allows SW to force to use 3B address size by clearing CMD_INFO.addr_4b_affected. Mainly it was to support Read SFDP command.
I removed addr_en, addr_4b_affected then introduced addr_mode.
The addr_mode is two bit fields:

value
enum
description

2'b 00
AddrDisabled
Address field does not exist

2'b 01
AddrCfg
Address size is affected by CFG.addr_4b_en

2'b 10
Addr3B
Address size is 3B always

2'b 11
Addr4B
Address size is 4B always

this lgtm! So generally speaking is the cfg.addr_4b_en going to be set by a write command from a host that software will process? So if host requests 4b that way, software will set the configuration bit, and it will apply to whatever commands we say it should apply to.  If not, then the address mode will determine whether its disabled / 3b / 4b?

Thanks for the review Tim! Let me merge.


Add voice activation via hotword

Problem:
I want to be able to activate the Assistant via voice, so I don't need to press a button (or spacebar) each time I want to talk to it.

Yeah me too,Have you achieved this?

Hi @elblogbruno . I am from the Assistant SDK team, and filed this issue to allow you guys to keep track of it.
This feature is under development now, and we will be opening a private beta for it soon. If you are interested, please sign up here (and turn on email updates)
Thanks for the interest!

in the meantime, try this, it already has voice control for Assistant using pocketsphinx:
https://github.com/xtools-at/AssistantPi

Seems like this was added in today's update https://github.com/googlesamples/assistant-sdk-python/blob/master/google-assistant-sdk/CHANGELOG.rst#030

Yep, see https://developers.google.com/assistant/sdk/prototype/getting-started-pi-python/ to get started.


Upgrade Sphinx to 1.7.1

Description
Changelog: http://www.sphinx-doc.org/en/stable/changes.html
Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Last time the sphinx build was broken for months. Did you build a local sphinx build ?

Did you build a local sphinx build ?

Of course. There are usually a couple of warning but nothing fatal. Not sure why the move of the constants in the last November that caused the build issue wasn't detected earlier. I suspect that I didn't clean the output directory on a regular base.


DM-31154: Discussion of the portal architecture

This section covers the documentation portal design, cost, and effort estimate.
Draft is available at https://sitcomtn-014.lsst.io/v/DM-31154

Changes excepted into the mater.


Task - Update Applicant Model to include Classifications and other fields

Description
We have a lookup table of departments, which are currently only attached to Job Posters. We want to allow Applicants to attach their current and past Classifications to their profile. This requires a new many-to-many relationship between Applicants and Classifications.
Each Applicant-Classification needs a few more pieces of data: the level (an integer), and an integer representing the correct ordering. (We can assume the 'lowest' ordering represents the user's current classification.)
We also want to add veteran_status_id and citizenship_status_id fields to the Applicant, like what already exist on the JobApplication. These should be foreign keys to their respective lookup tables.
Finally, also add a boolean is_gc_employee field.
Images
These changes are meant to support the new profile design:
https://xd.adobe.com/view/f66135de-6ab1-449d-ac7c-98ade3ce1fd2-a332/screen/22903d0a-6389-4e0b-a349-94d757852618
Acceptance criteria

[ ] Database is updated
[ ] Model classes are updated

Double check that "is GC" field doesn't overlap with Account settings (probably part of user model)

Double check with Jerbo about "Is GC" question being a boolean or radio buttion.

We can remove the "GC" property from this task, as its already kind of part of the User model.


Should Value.CompareTo() use AsNumber instead of AsString as a fallback when types don't match?

Today I noticed some unexpected behaviour. I used an expression like this:
<<if $undefinedvariable <= 2 >>
I was surprised to find $undefinedvariable (which was currently Value.Null) was considered larger than 2.
When I looked inside the Value class, I noticed that CompareTo() uses this line to compare values when the types don't match:
// try to do a string test at that point!
return this.AsString.CompareTo(other.AsString);
What do you think about changing it to use AsNumber instead? This would give behaviour more similar to javascript, so you can compare things like:
false < 2     -> true
false > 0     -> true
null < 0     -> false
null < 1     -> true

This is a really good question to ask, I'm not really sure is the answer.
Personally I like the idea of $undefinedvariable always evaluating to false when compared unless you compare it to Value.Null directly.
Do people think that using JS as the comparison model is the right way to go or should we special case null?

Great question! Rolled in with others in #167 to discuss the behaviours any changes may incur. We'd love to hear your thoughts there!


Revert "Colored cards based on level"

Reverts AnesFoufa/python-teams-logger#7
The fall back to INFO color is buggy

hmm, true. That should have been self._color_map.get(record.levelname, "") (without the "INFO"), so it becomes coloured. I'll create a new PR with the updated code.


Did you try to install TF2.4 from source with GPU accel on Nano or NX?

I am considering installing TF2.4 from source, and I will leverage your script for 2.3 to get there I think.
Not really an issue but I was wondering if you tried it already?
I need TF2.4 nightly installed from source to get TTS fastspeech with TFlight optim to work on the NX, I think. (I get the regular tf model to work on the jetson but not the tflight one due to some operators missing under my TF2.2 current install.

I have not tried building TensorFlow 2.4 myself.  But I definitely think you could use my install_tensorflow-2.3.0.sh as the basis for doing that.


Cannot decorate properties or methods.

I'm not sure what I'm looking for. Can you provide some minimum code to reproduce?


How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://github.com/jacktrip/jacktrip/releases
Publisher: jacltrip
Package Name: jacktrip
Description: multi-machine audio network performance over the Internet
Package Version: 1.10.1
Installer URL:
https://github.com/jacktrip/jacktrip/releases/download/v1.10.1/JackTrip-v1.10.1-Windows-x64-binary.zip
https://github.com/jacktrip/jacktrip/releases/download/v1.10.1/JackTrip-v1.10.1-Windows-x64-installer.msi
https://github.com/jacktrip/jacktrip/releases/download/v1.10.1/JackTrip-v1.10.1-Windows-x64-signed-installer.msi
Homepage: https://jacktrip.github.io/jacktrip/
Changelog: https://github.com/jacktrip/jacktrip/blob/main/docs/changelog.yml

https://github.com/microsoft/winget-pkgs/pull/115758

soft bump

https://github.com/microsoft/winget-pkgs/issues/107639

softest of bumps


Update from base repo

Codecov Report
Base: 88.14% // Head: 81.76% // Decreases project coverage by -6.37% :warning:

Coverage data is based on head (65e4e25) compared to base (66b0071).
Patch coverage: 89.53% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
- Coverage   88.14%   81.76%   -6.38%
==========================================
  Files          25       33       +8
  Lines         970     2221    +1251
==========================================
+ Hits          855     1816     +961
- Misses        115      405     +290

Impacted Files
Coverage Δ

smartmin/middleware.py
100.00% <ø> (ø)

smartmin/templatetags/smartmin.py
77.01% <16.66%> (+2.32%)
:arrow_up:

smartmin/models.py
82.50% <80.00%> (ø)

smartmin/widgets.py
86.11% <80.00%> (-0.99%)
:arrow_down:

smartmin/views.py
82.75% <93.10%> (ø)

...tions/0005_alter_importtask_created_by_and_more.py
100.00% <100.00%> (ø)

smartmin/csv_imports/tasks.py
100.00% <100.00%> (ø)

...tmin/users/migrations/0002_remove_failed_logins.py
100.00% <100.00%> (ø)

...artmin/users/migrations/0003_auto_20210219_1548.py
100.00% <100.00%> (ø)

smartmin/users/models.py
95.91% <100.00%> (+0.17%)
:arrow_up:

... and 13 more

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

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


Add new wizard for login migrations experience

This PR adds a new wizard to migrate logins for SQL MI and SQL VM scenarios.
The first step is to add a new button for login migration on the dashboard:

Step 1 allows the user to enter in information about the target:

Step 2 collects login info from the source and target, and prompts user to select logins for migration. Submitting "Migrate" here starts the migration:

Step 3 monitors the migration as it is proceed. The user cannot return to prior pages:

Here is the link to the figma design: https://www.figma.com/file/UaD2zc58Y2iGKxnqDFQY3Q/ADP-ADSSME-SQL-Inline-Migration-GA?node-id=415%3A14642&t=LXfnKQzEp3ZC5Hmp-0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 41.981%

Files with Coverage Reduction
New Missed Lines
%

extensions/machine-learning/src/common/processService.ts
2
81.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
28896

Relevant Lines:
63969

💛  - Coveralls

Adding Kavitha's comments as she doesn't have permissions to comment here:

On line 61 in sqlUtils.ts: if you could double check the query that DMS V1 code uses for displaying the source and target logins just to make sure. Not a blocker for this PR but something you could check in future.
And like Brian mentioned to remove the console.log timer lines before checkin.


Move Suppressor from core module  to api module

closes: #4932

Moved Suppressor from core to api
Renamed core/Suppressor.kt to InnerSuppressor
Updated detekt-api.api file

This doesn't close #4932 right now. How do the core load the clases that third-party plugins provide? I recommend you to see how FileProcessListener or ReportingExtension work.

@gouri-panda are you going to continue with this one?

@BraisGabin Sure! Let me try once more :)

I'm closing this one as stale. If you have time to work again on it just create a new PR ;)


Tests to fix codecov issue

Just trying some stuff out.  Will ping if it works.

Seems like codecov is passing on simple test with v3 instead of v2.  I am adding back all the other tests I deleted just to see if the version change addressed the codecov problem, so lets see if that works

it works again, but maybe we still like to change the version

They probably re-requested certifications! :) But yea, from what I can tell a lot of the "breaking changes" from v2 to v3 aren't really relevant to us, and seems like the packages are more up to date in v3 vs v2?

But yea, from what I can tell a lot of the "breaking changes" from v2 to v3 aren't really relevant to us, and seems like the packages are more up to date in v3 vs v2?

The latter would be an argument to upgrade. The argument to not upgrade is "don´t change a working setup", but we also know via CI that v3 is working too. Thoughts, @lmmentel, @freddyaboulton?

Let's merge it.


Some intrinsic function related issues in this doc.

Hi, I found some issues in this doc. It would be great if someone could take a look :-)
Some intrinsic functions are missing:
5.71. MADDR32 (Multiply and Add to 32-Bit Word)
5.74. MSUBR32 (Multiply and Subtract from 32-Bit Word)
5.75. MULR64 (Multiply Word Unsigned to 64-bit Data)
5.76. MULSR64 (Multiply Word Signed to 64-bit Data)
Similar issues: #13
Some intrinsic function names doesn't match the instruction name:
5.6. BITREVI (Bit Reverse Immediate)
Should be:
uintXLEN_t __rv__bitrevi(uintXLEN_t a, uintXLEN_t msb);
                       ^

5.54. KSLLIW (Saturating Shift Left Logical Immediate for Word)
Should be
intXLEN_t rvkslliw(intXLEN_t a, uint32_t b);
                ^

5.56. KSLLI8 (SIMD 8-bit Saturating Shift Left Logical Immediate)
Should be:
uintXLEN_t __rv__kslli8(uintXLEN_t a, uint32_t b);
                     ^

5.58. KSLLI16 (SIMD 16-bit Saturating Shift Left Logical Immediate)
Should be:
uintXLEN_t __rv__kslli16(uintXLEN_t a, uint32_t b);
                     ^

5.101. SLLI8 (SIMD 8-bit Shift Left Logical Immediate)
Should be:
uintXLEN_t __rv__slli8(uintXLEN_t a, uint32_t b);
                    ^

5.103. SLLI16 (SIMD 16-bit Shift Left Logical Immediate)
Should be:
uintXLEN_t __rv__slli16(uintXLEN_t a, uint32_t b);
                    ^

5.125. SRAI.u (Rounding Shift Right Arithmetic Immediate)
Should be:
intXLEN_t __rv__srai_u(intXLEN_t a, uint32_t b);
                   ^

5.127. SRAI8, SRAI8.u
Should be:
uintXLEN_t __rv__srai8(uintXLEN_t a, uint32_t b);
                    ^
uintXLEN_t __rv__srai8_u(uintXLEN_t a, uint32_t b);
                    ^

5.129. SRAI16, SRAI16.u
Should be:
uintXLEN_t __rv__srai16(uintXLEN_t a, uint32_t b);
                    ^
uintXLEN_t __rv__srai16_u(uintXLEN_t a, uint32_t b);
                    ^

5.131. SRLI8, SRLI8.u
Should be:
uintXLEN_t __rv__srli8(uintXLEN_t a, uint32_t b);
                    ^
uintXLEN_t __rv__srli8_u(uintXLEN_t a, uint32_t b);
                    ^

5.133. SRLI16, SRLI16.u
Should be:
uintXLEN_t __rv__srli16(uintXLEN_t a, uint32_t b);
                    ^
uintXLEN_t __rv__srli16_u(uintXLEN_t a, uint32_t b);
                    ^

5.186. WEXTI (Extract Word from 64-bit Immediate)
Should be:
uintXLEN_t __rv__wexti(int64_t a, uint32_t b);
                     ^

All of the intrinsic functions of the small immediate type instructions can be the same as the intrinsic functions of the register-type instructions. This is because a compiler can detect constant value (immediate) in the function argument and determine if the constant range fits inside the immediate range. If the constant value fits in the immediate range, the compiler will generate the immediate type of the instruction.

All of the intrinsic functions of the small immediate type instructions can be the same as the intrinsic functions of the register-type instructions. This is because a compiler can detect constant value (immediate) in the function argument and determine if the constant range fits inside the immediate range. If the constant value fits in the immediate range, the compiler will generate the immediate type of the instruction.

Thanks for the reply!

Thanks for the reply!


Add tabs order update operation to DAO

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

[!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

#4734  👈
#4719
develop

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

Join @0nko and the rest of your teammates on  Graphite


WIP Public sharing by source

closing in favor of #317--I know I said it didn't matter but I found it too hard to review the diff with both sets of changes in it so I created a new PR against bg-research-data so I could see just the diff of your changes. :)

Current coverage is 70.84%

Merging #316 into master will decrease coverage by -0.37% as of dc00611

@@            master    #316   diff @@
======================================
  Files          106     106
  Stmts         2845    2881    +36
  Branches         0       0
  Methods          0       0
======================================
+ Hit           2026    2041    +15
  Partial          0       0
- Missed         819     840    +21

Review entire Coverage Diff as of dc00611

Powered by Codecov. Updated on successful CI builds.

looks good so far; going to try running it locally now

works locally as well--going to add some status updates to the migration but we could probably test on staging :)

I added some style stuff to the research data page. I wanted more visual clarity on what source each public data sharing button is associated with, an unrelated task but I'm much happier with how it looks now...


[Add] StatusItemController package

Thanks Jesse!
The CI failure is just that the GH Action doesn't yet have Swift 5.2 available. Merged, thank you. 👍

Thanks @daveverwer ! 💯


Add a script for tagging and making the release

Probably obsolete given the SKIPBUILD option in the release, @saudet ?

Ah, yes, let's use perform-release.sh?


chore(buildpacks): update go, php, nodejs, python, and scala buildpacks

See
https://github.com/heroku/heroku-buildpack-go/compare/v41...v42
https://github.com/heroku/heroku-buildpack-php/compare/v107...v108
https://github.com/heroku/heroku-buildpack-nodejs/compare/v90...v91
https://github.com/heroku/heroku-buildpack-python/compare/v80...v81
https://github.com/heroku/heroku-buildpack-scala/compare/v70...v71

I tested this with all the relevant Deis example apps:
$ SKIP_TEST="-none-" FOCUS_TEST="all (buildpack|dockerfile) apps" make test-integration
ginkgo -slowSpecThreshold=120.00 -noisyPendings=false -p --skip="-none-" --focus="all (buildpack|dockerfile) apps" tests/
Running Suite: Deis Workflow
============================
Random Seed:<PHONE_NUMBER>
Will run 14 of 200 specs

Will run 14 of 200 specs

Running in parallel across 4 nodes

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•••SSSSSSSSSSSSSSSSSSSSSSSSSS•
------------------------------
• [SLOW TEST:120.188 seconds]
all buildpack apps
/Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:97
  with an existing user
  /Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:95
    who has added their public key
    /Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:93
      can deploy an example buildpack app
      /Users/matt/Projects/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table.go:96
        Perl
        /Users/matt/Projects/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46
------------------------------
•••• ••••
------------------------------
• [SLOW TEST:151.662 seconds]
all buildpack apps
/Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:97
  with an existing user
  /Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:95
    who has added their public key
    /Users/matt/Projects/src/github.com/deis/workflow-e2e/tests/buildpacks_test.go:93
      can deploy an example buildpack app
      /Users/matt/Projects/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table.go:96
        Scala
        /Users/matt/Projects/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
Ran 14 of 200 Specs in 759.450 seconds
SUCCESS! -- 14 Passed | 0 Failed | 0 Pending | 186 Skipped


Use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter

https://github.com/trackify-info/Trackify-Consent-CMP/blob/76e7776c2e14ad4501acea7bb06c6c16ba8d8a2c/template.tpl#L292
When reviewing your template we've noticed that it is using parameters to build a url. It's a best practice to use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter.

Hopefully this is fixed now


Fix fusion script/recipe issue found in SERT testing

What this PR does / why we need it:
export variable
label-common-service.sh is using variable TETHERED_NS, but fusion-backup-setup.sh is using variable TETHERED_NAMESPACE1="" TETHERED_NAMESPACE2=""
We need to report new variable name for different script
remove operandconfig from recipe
since we are not labeling operandconfig, we need to remove it from recipe. Otherwise recipe will fail in backup
add fusion catalog and cs catalog in to the env var
add fusion catalog name and common-service catalog name, so we can use different catalogsource to install cs and fusion
update recipe
update namespace in the recipe

/lgtm


Avoid double wrapping of all accelerate.prepare objects

Solves double nested wrapping issues linked as a side-effect to https://github.com/huggingface/transformers/issues/24050.
Also resets step to 0 during free_memory

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@muellerzr @sgugger Hi! I have zero familiarity with the code base, but is it intentional that the added setattr() call sets the "_is_accelerate_prepared" attribute, while the used getattr() calls access the different "_accelerate_prepared" (note missing "_is" suffix) attribute?

Nope, it is not! Would you like to put in a fix @Yura52? Otherwise I can do so quickly :)

Nope, it is not! Would you like to put in a fix @Yura52? Otherwise I can do so quickly :)

Here is the PR: #1560


Acceptance tests are not executing from IDE

Description

Acceptance tests are not executing from IDE.
Acceptance tests are working as expected through test.cmd (.\test.cmd -p "Acce" )

Closing this issue since it is not a blocking item for engineering.


ValueError: ['text_anchor'] are not supported arguments. Look at the documentation for supported arguments.

Exception in Tkinter callback
Traceback (most recent call last):
  File "E:\anaconda3\envs\PY38\lib\tkinter\__init__.py", line 1892, in __call__
    return self.func(*args)
  File "E:\anaconda3\envs\PY38\lib\site-packages\customtkinter\windows\widgets\ctk_button.py", line 554, in _clicked
    self._command()
  File "main.py", line 318, in open_file_explorer
    self.files_listbox.insert("END", filename, text_anchor="w")
  File "E:\anaconda3\envs\PY38\lib\site-packages\CTkListbox\ctk_listbox.py", line 193, in insert
    self.buttons[index] = customtkinter.CTkButton(
  File "E:\anaconda3\envs\PY38\lib\site-packages\customtkinter\windows\widgets\ctk_button.py", line 52, in __init__
    super().__init__(master=master, bg_color=bg_color, width=width, height=height, **kwargs)
  File "E:\anaconda3\envs\PY38\lib\site-packages\customtkinter\windows\widgets\core_widget_classes\ctk_base_class.py", line 46, in __init__
    check_kwargs_empty(kwargs, raise_error=True)
  File "E:\anaconda3\envs\PY38\lib\site-packages\customtkinter\windows\widgets\utility\utility_functions.py", line 18, in check_kwargs_empty
    raise ValueError(f"{list(kwargs_dict.keys())} are not supported arguments. Look at the documentation for supported arguments.")
ValueError: ['text_anchor'] are not supported arguments. Look at the documentation for supported arguments.

The argument 'text_anchor' doesn't exist in the current oficial version of customtkinter library. I had to change the library and i'm waiting for approval by the owner to implement that change. In this repository https://github.com/P3rdigas/CustomTkinter you can find the modified library. If you use poetry, the library will be automatically be install. Mean while this version of the application is very incomplete, i'm currently working in the GUI and discovering the best approaches for the app, so i recommend you to use the released version. Take in mind this program only removes passwords from workbooks, sheets and read-only files, files with password needed to be opened need a brute force tool and vba passwords are currently not supported yet.

thanks
We have found other frameworks and successfully resolved the issue
About this framework GUI
Suggested use
https://github.com/PySimpleGUI/PySimpleGUI

Nice. Thanks for the suggestion, however i think i'm gonna stick with this framework, was the first i used, want to improve it and has a lot of my time invested in. Besides, the result of this framework feels more modern that PySimpleGui!


Log important events

Implement some sort of logging framework, especially for exceptions and debug information.

Done.


Exit code 0 when async run fails

When run('cmd', {async: true}) fails, process will exit with status code 0. Should be 1.

If async call run fails without handling promise rejection, process will still finish with exit code 0 (success). Pure node process by default prints unhandled promise rejection warning in that case (unhandled rejection) and exit with code 0, let's keep that behaviour, so this won't be fixed.

Possible suggestion / idea for this since it wasn't exactly intuitive to me why runs I had changed from sync to async were still passing on errors...
Can we return a promise, and then have failures cause the exit?
Eg.
export function blah() {
    return run('cmd', {async: true});
}

Since the promise is returned runjs could catch any reject and return status code 1.
Otherwise I'm guessing the suggested workaround is this for every async test?:
export function blah() {
    run('cmd', {async: true})
        .catch((err) => {
             process.exit(1);
        });
}

Thanks!

Yes, second example is the way to go. Generally runjs inherits nodejs default behaviour when it comes to handling failures for async processes, that means that parent process will still return success code 0 if async process fails. So it's up to developer how to handle async failures so it has full control of it.

Is this behavior changed in taskfile? It can be a nasty surprise to a have a build fail, but have the build continue to deploy stage because the run command returned success instead of failure.


[SPARK-25161][Core] Fix several bugs in failure handling of barrier execution mode

What changes were proposed in this pull request?
Fix several bugs in failure handling of barrier execution mode:

Mark TaskSet for a barrier stage as zombie when a task attempt fails;
Multiple barrier task failures from a single barrier stage should not trigger multiple stage retries;
Barrier task failure from a previous failed stage attempt should not trigger stage retry;
Fail the job when a task from a barrier ResultStage failed;
RDD.isBarrier() should not rely on ShuffleDependencys.

How was this patch tested?
Added corresponding test cases in DAGSchedulerSuite and TaskSchedulerImplSuite.

Test build #94968 has started for PR 22158 at commit 32ea946.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2331/
Test PASSed.

Test build #94968 has finished for PR 22158 at commit 32ea946.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94968/
Test FAILed.

retest this please

Test build #94998 has started for PR 22158 at commit 32ea946.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2357/
Test PASSed.

Merged build finished. Test PASSed.

LGTM pending Jenkins. Thanks for finding those corner cases!

Test build #94998 has finished for PR 22158 at commit 32ea946.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94998/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2359/
Test PASSed.

Test build #95000 has started for PR 22158 at commit 32ea946.

Test build #95000 has finished for PR 22158 at commit 32ea946.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95000/
Test PASSed.

Merged into master. Thanks!


feat: add user serial via semihosting

This PR, based on #4, implements the user serial SDK functions using ARM semihosting calls.

[x] Simple unbuffered implementation that sends serial to simulator stdout
[x] Panic handler that sends message to simulator stderr
[x] Serial buffer
[x] Printf formatting
[ ] Stdin

Prematurely merging since this makes some pretty significant changes. Stdin can be covered in another PR.


Error "Unexpected error, check log for details" when changing nginx settings

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
When saving any nginx setting (tested with upstreams, locations, stream servers) I get the error message "Unexpected error, check log for details" when saving the changes. In the browser dev tools I see an HTTP 500 error. I checked the logs, both from OPNsense and nginx, but could not find anything relevant.
Even without changing anything, the error is displayed.
Adding or deleting configs works as expected.
To Reproduce
Steps to reproduce the behavior:

Go to 'nginx/Configuration'
Edit any configuration (e.g. Location, Stream, Upstream)
Click save without making changes
See error popup: "Unexpected error, check log for details"

Expected behavior

When saving without making changes no error should be displayed.
More info should be found in the log file as stated by the error message

Describe alternatives you considered
Deleting the configuration and adding it again works without errors.
Screenshots

Relevant log files
no relevant log messages
Additional context

several upstreams, locations, http servers are configured

Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.7.8 (amd64) (upgraded from previous releases)
VM (Proxmox/KVM), 4G RAM, 2 CPUs

duplicate of https://github.com/opnsense/plugins/issues/4342


Hide FAB on scroll down

It would be great if FAB can be hidden while scrolling just like in Google+ App.

See #1 for explanation.


Contextual File Duplications

VSCode Version: Version 1.18.0 (1.18.0)
OS Version: MacOS 10.13 (17A365)

It would be great if the file explorer had the option to duplicate a file as a contextual menu item. In the development that I do, I frequently take existing component files, duplicate them, and then rename as a way to kick start working on a component.
In using Sublime Text/Atom/etc, the file tree allows adds the contextual option. In VS Code, I have to open the file in the Finder, duplicate, rename, and then co back to the app and open/edit.
It would be nice to have that all in one spot.

Currently you can simply cmd+c, cmd+v in the explorer to achieve the same thing.
As an alternative you can context menu -> copy, context menu on parent -> paste.
In vscode we are usually trying to be as minimalstic as possible. Due to that I will not add this action to the explorer. Closing this feature request.


opt-out

Please take this as a formal request from the account
<EMAIL_ADDRESS>to opt-out from having any data associated with this account pass through the bridge.
I joined the Mastodon Fediverse because i saw it as a good alternative to the corporate Social Media Platforms
that already exist.
I do not want my publicly accessible content that i post on any Fediverse Platform to be transferred
to any Corporate non federated Platform. This Bridge should be opt-in or at least should have a better and more clear way to
opt-out. Please reconsider your approach for user participation with this project. I personally don't like how this opt-out method of integration is forced upon all users.
I request a reply that my wish to opt-out is acknowledged.
If i do not get a reply within 14 days and/or see any sign that my data was shared through the bridge,
i will take legal action.

Done, and understood.
I'm working on a new opt in idea, https://github.com/snarfed/bridgy-fed/issues/835#issuecomment-1942046208, hopefully it can replace the original pure opt out. Apologies for not figuring it out sooner.


Reading the source of this module I have a question about a terraform construct I can't find documentation for

https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/blob/master/main.tf#L309
Can anyone point me to documentation for terraform that explains this and { block construct in a dynamic content block?

https://developer.hashicorp.com/terraform/language/expressions/dynamic-blocks
and is just the name of the block within the filter block.
Please ask generic questions like this at https://discuss.hashicorp.com


Runtime module mismatch version of installed npm package

Environment

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     3.6.2
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools, modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/LeonardoRick/temp-nuxt-bug
Steps to reproduce:

Clone the project and set node version to 18
Comment "@nuxtjs/i18n" inside nuxt.config.ts modules definition (otherwise I couldn't even run npm install without an error)

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  devtools: { enabled: true },
  modules: [
    // "@nuxtjs/i18n"
  ]
})

Run npm i
Uncomment "@nuxtjs/i18n" insode nuxt.config.ts
Run npx nuxi info
Run npm ls

Describe the bug
npm ls
nuxt-app@ /Users/leonardorick/Documents/cre8tive/git/leonardorick/temp-nuxt-bug
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
My npm ls shows the right version of @nuxtjs/i18n (8.0.0-beta.13) but nuxt seems to not recognize it properly since it's showing the wrong version on npx nuxi info (7.3.1)
This is causing my application to not being able to start.
I already tried running rm -rf node_modules package-lock.json && npx nuxi cleanup and as this thread implies, this seems not to be a i18n problem in this case.
Am I missing something?

Any workaround would be really appreciated, I've tried a lot of things already without success. It's opened for a while for now and I'm not being able to use i18n on my project because of that.

hey @IvanWala did you managed to make it work? I'm not being able to use i18n because of this. (Can't find a way to make nuxt understand and use the right version.


[AMORO-2115] Support displaying Optimizing taskes

Why are the changes needed?

Close #2115 .
Brief change log

add optimizing detail page with all optimizing taskes
get optimizing taskes http interface return optimizer token

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

In the task details, I found some information that is not very clear. Could you please prefix the newly added files with "new" and the old files with "reWrite"?

In the task details, I found some information that is not very clear. Could you please prefix the newly added files with "new" and the old files with "reWrite"?

@wangtaohz I suggest use new define parameter to display in page, this is also the reason why I added new parameters.

In the task details, I found some information that is not very clear. Could you please prefix the newly added files with "new" and the old files with "reWrite"?

Thanks for your report. After merging this PR, and modify the order of metrics, the new metrics are more clearer

@wangtaohz I suggest use new define parameter to display in page, this is also the reason why I added new parameters.

All the new define parameters are displayed now. You can refer to my last comment.

@wangtaohz
Is it still necessary to display the deprecated parameters (reRowDeletedDataFileCnt, positionalDeleteSize, newFileSize, newFileCnt) on the page?
It will cause some doubts to users, I recommend not display them.

There are two reasons for displaying the old parameters here.
Firstly, since the new parameters of the old task are all 0, omitting the display of old parameters would result in the loss of some information for the old task.
Secondly, I am not very familiar with how to remove these parameters on the front-end. 😅

Looks great. Can we add an action to kill/cancel the running process in this optimizing process detail page?

 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.

Looks great. Can we add an action to kill/cancel the running process in the optimizing process detail page?

Yes, that's what we are going to do after this PR merged.

Show the metrics of optimizing process.

@wangtaohz Thanks a lot for your work.
For the display of optimizing process details, I have some improvement suggestions:

Currently, the metric names for process/task are not very intuitive. I suggest redesigning them by referencing the names used in the Iceberg snapshot summary.
Hide metric information that is not necessary to focus on, rather than displaying all of it.
Can the display of process metrics be consistent with that of tasks, by adding a "+" button at the beginning of the table to expand?

After modification, the pages are like this:

Sorry, I may have some different opinions, from my opinion, this is a detailed page and should show all the information involved, like snapshot page. Instead of showing only part of it.
@zhoujinsong @wangtaohz

Sorry, I may have some different opinions, from my opinion, this is a detailed page and should show all the information involved, like snapshot page. Instead of showing only part of it.

Do you mean showing only part of the metrics when you say showing only part of it? As far as I know, the metrics of the snapshot are also selectively displayed, not all information.

Sorry, I may have some different opinions, from my opinion, this is a detailed page and should show all the information involved, like snapshot page. Instead of showing only part of it.

Do you mean showing only part of the metrics when you say showing only part of it? As far as I know, the metrics of the snapshot are also selectively displayed, not all information.

I mean is that I can get from the information what exactly the current optimize task has done, is rewrite data file or rewrite data pos delele, rewriting 3 datafiles into 1, or rewriting datafile's pos delete file, or outout pos delete count ...

Sorry, I may have some different opinions, from my opinion, this is a detailed page and should show all the information involved, like snapshot page. Instead of showing only part of it. @zhoujinsong @wangtaohz

I agree that we should display the complete metric. However, this does not mean that all processes/tasks will have the same metrics. For instance, with respect to Iceberg v1 tables, there are no metrics related to delete files. Different processes/tasks should only display metrics relevant to themselves.

https://github.com/NetEase/amoro/assets/103108928/3954dec3-ba20-4baa-b4d7-b3879a5f426c

@wangtaohz After I canceled the optimize task, tasks without start time showed abnormal cost time values.

@wangtaohz After I canceled the optimize task, tasks without start time showed abnormal cost time values.

Thanks for your report. I will fix it.

https://github.com/NetEase/amoro/assets/103108928/f40ea0ac-63a4-4d17-b764-ee13fac615f5


Ability to specify multiple SSH authorized keys

The SSH public key input field only allows one key, whether it is pasted or uploaded.
It would be more convenient to be able to paste and upload multiple public keys. Each public key would be separated by a new line.

Feature added in https://github.com/ComputeCanada/mc-hub/commit/7b628f89c23ee85be75b82f14fcce0bb040c3021.

Feature added in https://github.com/ComputeCanada/mc-hub/commit/7b628f89c23ee85be75b82f14fcce0bb040c3021.


HTTP Abstractions

Fundamentals -> HTTP Abstractions
Cover the new HttpContext and how to use it.

Looking forward to this - main question I have is how does the Microsoft.AspNet.Http namespace relate to System.Net.Http? Will there be an HTTP client that uses Microsoft.AspNet.Http?

Looking forward to this - main question I have is how does the Microsoft.AspNet.Http namespace relate to System.Net.Http

There's no relation between the 2 namespaces. You can get at strongly typed headers in System.Net.Http using an extension method http://odetocode.com/blogs/scott/archive/2015/11/30/working-with-typed-headers-in-asp-net.aspx.

Will there be an HTTP client that uses Microsoft.AspNet.Http

Nope. Microsoft.AspNet.Http was designed specifically for the server.

The docs mention that if we "would like to review early drafts and outlines of this topic, please leave a note with your contact information" here. Yes please, my Microsoft alias is timregan

We think this topic is sufficiently covered by the following articles:

https://docs.asp.net/en/latest/fundamentals/middleware.html
https://docs.asp.net/en/latest/fundamentals/request-features.html
https://docs.asp.net/en/latest/fundamentals/servers.html


enh: install common dependencies at beginning of each Dockerfile

Install common dependencies at beginning of each Dockerfile. Update classes to not install those dependencies.

Codecov Report

Merging #8 into master will decrease coverage by 8.88%.
The diff coverage is 87.87%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
- Coverage   80.33%   71.44%   -8.89%
==========================================
  Files          16       16
  Lines         666      676      +10
  Branches       58       62       +4
==========================================
- Hits          535      483      -52
- Misses         96      158      +62
  Partials       35       35

Impacted Files
Coverage Δ

neurodocker/interfaces/spm.py
23.25% <0%> (-67.86%)
:arrow_down:

neurodocker/tests/test_utils.py
100% <100%> (ø)
:arrow_up:

neurodocker/utils.py
80.64% <100%> (+0.31%)
:arrow_up:

neurodocker/interfaces/miniconda.py
82.97% <100%> (-0.36%)
:arrow_down:

neurodocker/interfaces/tests/test_ants.py
50% <100%> (-50%)
:arrow_down:

neurodocker/interfaces/ants.py
88.09% <100%> (-0.28%)
:arrow_down:

neurodocker/tests/test_docker_api.py
100% <100%> (ø)
:arrow_up:

neurodocker/parser.py
51.06% <25%> (-3.49%)
:arrow_down:

neurodocker/interfaces/fsl.py
73.33% <75%> (-2.94%)
:arrow_down:

neurodocker/docker_api.py
75.3% <96.42%> (+1.62%)
:arrow_up:

... and 3 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 305d659...e4f84f5. Read the comment docs.

Build timed out building SPM.


python312Packages.dns-lexicon: 3.16.1 -> 3.17.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.dns-lexicon is: Manipulate DNS records on various DNS providers in a standardized way
meta.homepage for python312Packages.dns-lexicon is: https://github.com/AnalogJ/lexicon
meta.changelog for python312Packages.dns-lexicon is: https://github.com/AnalogJ/lexicon/blob/v3.17.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.17.0 with grep in /nix/store/4fys4gf3fdsyn0b7ba57hj2gmsc41y1d-python3.12-dns_lexicon-3.17.0
found 3.17.0 in filename of file in /nix/store/4fys4gf3fdsyn0b7ba57hj2gmsc41y1d-python3.12-dns_lexicon-3.17.0

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

certbot-full
lexicon
python311Packages.certbot-dns-ovh
python311Packages.dns-lexicon
python312Packages.certbot-dns-ovh
python312Packages.dns-lexicon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4fys4gf3fdsyn0b7ba57hj2gmsc41y1d-python3.12-dns_lexicon-3.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.dns-lexicon https://github.com/r-ryantm/nixpkgs/archive/e6e4878913acf79b0ddf0ee2e654c9eb1bfba356.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e6e4878913acf79b0ddf0ee2e654c9eb1bfba356#python312Packages.dns-lexicon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4fys4gf3fdsyn0b7ba57hj2gmsc41y1d-python3.12-dns_lexicon-3.17.0
ls -la /nix/store/4fys4gf3fdsyn0b7ba57hj2gmsc41y1d-python3.12-dns_lexicon-3.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages failed to build:

certbot-full
python311Packages.certbot-dns-ovh
python311Packages.certbot-dns-ovh.dist
python312Packages.certbot-dns-ovh
python312Packages.certbot-dns-ovh.dist

4 packages built:

lexicon (python312Packages.dns-lexicon)
lexicon.dist (python312Packages.dns-lexicon.dist)
python311Packages.dns-lexicon
python311Packages.dns-lexicon.dist

Maintainer pings
cc @aviallon for testing.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335752 at e6e48789 run on x86_64-linux 1

3 packages failed to build:

certbot-full
python311Packages.certbot-dns-ovh
python312Packages.certbot-dns-ovh

2 packages built successfully:

lexicon (python312Packages.dns-lexicon)
python311Packages.dns-lexicon


Better Collada Exporter - export only deform bones

Hello,
Testing the Better Collada Exporter for Blender, I notice all of the bones in a rig get exported to Godot. A desired way would be to only export those bones that directly influence the mesh (i.e. deform bones). In Blender, bones can be flagged as being 'deform' bones and e.g. the FBX exporter has an option to only export those. It would be nice and very much needed for Better Collada to support this.
A rig is usually made from many bones. There are deform bones which directly deform the mesh, then there are control bones that are used to animate, and also helper bones. Together they make a rig comfortable to use and animate. However, for games, you only need the deform bones, the rest can and should be discarded.

Moved to https://github.com/godotengine/collada-exporter/issues/14.


TresAxesHelper not respecting "size" value

Describe the bug
TresAxisHelper works but it does not respect the "size" constructor parameter:
<TresAxesHelper :size="5" />`
Reproduction
https://stackblitz.com/edit/tresjs-basic-b64iyv?file=package.json,src%2Fcomponents%2FTheExperience.vue
Steps to reproduce
No response
System Info
No response
Used Package Manager
npm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi @akweidler thanks for reaching out.
If you check the ThreeJS documentation https://threejs.org/docs/index.html?q=Ax#api/en/helpers/AxesHelper there is no property 'size' on the object.
You need to pass it to the instance constructor by using the :args="[size]" property (See why here
Let me know if it worked ✌

Thanks @alvarosabu, that worked!
I see now, the :args=[] is for the constructors. Sorry must have read too fast through the documentation and missed it here:
https://tresjs.org/api/instances-arguments-and-props.html#arguments
Cheers!


Addressing Binary Contingency Table rendering issues in readthedocs

Binary Contingency Table Tutorial:

Some of the dot points were not rendering correctly in readthedocs.
I also made two edits for grammar/clarity. If you have better alternative suggestions, please use those suggestions instead.

(Note: I didn't read the entire tutorial to check for grammar/clarity issues. I just happened to notice the two grammar/clarity issues for which I have suggested changes).
My changes render properly in readthedocs on my local machine. They also looked okay when I ran them in Juypter Lab locally.

Source code changes looked good
Read through the rendered notebook on the source fork, looks good there also. I will check readthedocs once it's through.


[patch] for role token exp, "" => 0, invalid duration => crash

crazy user prevention

Codecov Report

Merging #22 into master will decrease coverage by 0.68%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   96.66%   95.97%   -0.69%
==========================================
  Files          10       10
  Lines         569      572       +3
==========================================
- Hits          550      549       -1
- Misses         10       13       +3
- Partials        9       10       +1

Impacted Files
Coverage Δ

service/role.go
96.19% <100%> (-1.05%)
:arrow_down:

usecase/tenantd.go
91.3% <0%> (-4.35%)
: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 bce168b...197cbc3. Read the comment docs.

LGTM


Instance name defined in a text macro doesn't work

Example:
`define MOD_INST u_mysubmod
module mymod;
mysubmod `MOD_INST ();
endmodule

Output:
files:
  - file_name: "some_file.sv"
    defs:
      - mod_name: "mymod"
        insts:

Expected:
files:
  - file_name: "some_file.sv"
    defs:
      - mod_name: "mymod"
        insts:
          - mod_name: "mysubmod"
            inst_name: "u_mysubmod"

This issue still seems to be present with sv-parser 0.8.2.  I filed an issue about it in that project (https://github.com/dalance/sv-parser/issues/20).  For what it's worth, you can work around the issue for now by making the macro a function with a dummy argument, like this:
`define MOD_INST(x) u_mysubmod
module mymod;
mysubmod `MOD_INST(x) ();
endmodule


Add custom properties when receiving messages from Service Bus topics with pubsub component

In what area(s)?
/area runtime
/area operator
Describe the feature
The Dapr pubsub component for Service Bus topics allows to send, together with the body of the message, additional custom metadata that can be used for many purposes.
One of this purpose, as already described in this issue, is to enrich the message with the property Diagnostic-Id in order to propagate traces within systems that have not yet adopted the cloudevents standard.
In our company we are using ELK stack for observability and we would like to leverage Elastic APM to enable end-to-end distributed tracing.
Receiving all the metadata will allow us to extract the traceId from the messages.
The piece of code to adapt in this case, if I am not wrong, should be the following one
https://github.com/dapr/components-contrib/blob/93cf5cb2c96e91940d7d8c2da4376a09062df0b8/common/component/azure/servicebus/message_pubsub.go#L56
The function should be modified to map also the Custom Properties. As an additional remark, these custom properties are correctly transmitted if using the Bindings for Azure Service Bus queue.

I think I misunderstood this issue - I'll close it as a duplicate of github.com/dapr/components-contrib/issues/3428.
Implemented here: https://github.com/dapr/components-contrib/pull/3436
The specific request was for Service Bus Message ApplicationProperties to be delivered as metadata to properties to the subscribed applications.


Commit 3c96681 made Actually Unbreaking stop working

Crash Log

Nevermind, Actually Unbreaking isn't working at all, even without Fabrication

sorry about that, this has been fixed in the newest release! :]


nextTick and eventPropogation Issue

Version
2.6.3
Reproduction link
https://codesandbox.io/s/qx992r339j
Steps to reproduce
Click the open modal button.
What is expected?
The text should display. When you click anywhere other than the text it should be removed.
What is actually happening?
The text flashes on and then off.

The nextTick edge case described in https://gist.github.com/yyx990803/d1a0eaac052654f93a1ccaab072076dd doesn't seem to be completely fixed.

as a workaround you can use .stop to stop the propagation of the event

or add the listener later:
    open() {
      this.showing = true
      window.setTimeout(() => {
        document.addEventListener('click', this.blur)
      }, 0)
    },

This is is because the handler is added manually by you, not by Vue. There is nothing we can do about this case.


Responding to "external" control

Shouldn't some event fire when the ChromeCast stops (because someone pushed stop casting on there phone) ?
It looks like I'm receiving a

RECEIVER_STATUS
CLOSE

but none of the events fire (atleast nothing that I see that says it stopped playing)
I'm watching these events
 ChromecastService.ChromeCastClient.ApplicationStarted += Client_ApplicationStarted;             ChromecastService.ChromeCastClient.VolumeChanged += _client_VolumeChanged;             ChromecastService.ChromeCastClient.MediaStatusChanged += ChromeCastClient_MediaStatusChanged;             ChromecastService.ChromeCastClient.ConnectedChanged += ChromeCastClient_Connected;             ChromecastService.ChromeCastClient.ChromecastStatusChanged += ChromeCastClient_StatusChanged;
Any ideas ?

If you someone pushed stop casting from different device you only receive Status Changed notification
if they did this after connecting to the chromecast application and inside of application you will receive MediaStatusChanged event.


Relative Link Replacement Should Also Update Master Links

Continue relative link replacement as is now.
Add another replacement regex that looks for links directly to master branch.

There is some gotchas here, as there are a couple different ways you can refer directly to master.

We have disabled the relative link and replaced with master link. Also, we switched the master link to release tag link at release. The issue has been resolved. Close it for now. Feel free to reopen if anything left.


leader memory leak when a node is down in linux - raspberry or debian

Reproduced it also with the latest in main 14.3.
It also reproduces in linux - debian wsl.
To reproduce:

modify the DataModifier of the RaftNode example so that it saves every 0.1 seconds (10 times x second)
for x64 run (also reproduces in arm devices): dotnet publish Examples\RaftNode -p:PublishProfile=FolderProfile -c Release -r linux-x64 --self-contained -f net6.0
run the 3 nodes as usual
a few mins later kill one of the non leader nodes
monitor the memory and confirm a few minutes later the leader has gained significant more memory
if you leave it running its memory usage keeps growing / I have had a working set of well over 1GB

Confirmed.
State of the leader immediately after stopping of the follower:
[System.Runtime]
    % Time in GC since last GC (%)                                         0
    Allocation Rate (B / 1 sec)                                      272,072
    CPU Usage (%)                                                          1
    Exception Count (Count / 1 sec)                                      129
    GC Committed Bytes (MB)                                               38
    GC Fragmentation (%)                                                   0.193
    GC Heap Size (MB)                                                     18
    Gen 0 GC Count (Count / 1 sec)                                         0
    Gen 0 Size (B)                                                       192
    Gen 1 GC Count (Count / 1 sec)                                         0
    Gen 1 Size (B)                                                 2,057,480
    Gen 2 GC Count (Count / 1 sec)                                         0
    Gen 2 Size (B)                                                   600,912
    IL Bytes Jitted (B)                                              303,868
    LOH Size (B)                                                   4,130,024
    Monitor Lock Contention Count (Count / 1 sec)                          0
    Number of Active Timers                                                2
    Number of Assemblies Loaded                                           54
    Number of Methods Jitted                                           4,390
    POH (Pinned Object Heap) Size (B)                                 48,360
    ThreadPool Completed Work Item Count (Count / 1 sec)                 188
    ThreadPool Queue Length                                                0
    ThreadPool Thread Count                                                9
    Time spent in JIT (ms / 1 sec)                                         0
    Working Set (MB)                                                     102

30 mins later:
[System.Runtime]
    % Time in GC since last GC (%)                                         0
    Allocation Rate (B / 1 sec)                                      399,528
    CPU Usage (%)                                                          1
    Exception Count (Count / 1 sec)                                      127
    GC Committed Bytes (MB)                                               50
    GC Fragmentation (%)                                                   0.189
    GC Heap Size (MB)                                                     28
    Gen 0 GC Count (Count / 1 sec)                                         0
    Gen 0 Size (B)                                                       192
    Gen 1 GC Count (Count / 1 sec)                                         0
    Gen 1 Size (B)                                                 3,379,200
    Gen 2 GC Count (Count / 1 sec)                                         0
    Gen 2 Size (B)                                                   600,912
    IL Bytes Jitted (B)                                              308,623
    LOH Size (B)                                                  14,747,920
    Monitor Lock Contention Count (Count / 1 sec)                          0
    Number of Active Timers                                                2
    Number of Assemblies Loaded                                           54
    Number of Methods Jitted                                           4,437
    POH (Pinned Object Heap) Size (B)                                 48,360
    ThreadPool Completed Work Item Count (Count / 1 sec)                 193
    ThreadPool Queue Length                                                0
    ThreadPool Thread Count                                                9
    Time spent in JIT (ms / 1 sec)                                         0
    Working Set (MB)                                                     115

It seems some large buffers are leaking because of LOH growth.

Root cause analysis: currently, WAL is using memory pooling to rent LogEntry[] array internally. When all members are healthy, the array has fixed length in every heartbeat iteration. When one of the them becomes unreachable, the leader cannot make any progress on it. Thus, the number of entries is growing over the time. At the next heartbeat iteration, unavailable member is 2 log entries behind, then 3, etc. As a result, LogEntry[] array is growing. ArrayPool in the same time keeps strong references to all requested arrays. Every new requested array has a length larger than existing arrays in the pool. Therefore, GC cannot collected those arrays until full blocking GC (ArrayPool releases all internal arrays in case of full blocking GC).
Mitigation: The first attempt I made was to fix calculation of the expected length of the array (because we have snapshotting, so the length cannot grow indefinitely in practice), and change pooling mechanism in the way that allows to avoid keeping strong references on unused arrays. This approach is implemented by the commits represented above. I called this a naive approach for the following reasons:

Allocation of the array is still required for each read (which is hot path)
Unused arrays from the pool due to their lifetime will be always in Gen 2. So they can be reclaimed in case of full GC only

To completely fix the issue and keep hot path optimized, I decided to change the whole approach. Reader expects generic TList that implements IReadOnlyList<LogEntry>. Thus, we are free to switch from materialized collection (such as array) to lazy ephemeral collection. In that case, the memory needed to represent the collection with all log entries doesn't depend on the number of log entries inside of the collection. In other words, such a collection has O(1) space complexity in contrast to O(n) provided by regular arrays or lists. Of course, there is no free lunch. Usually, reducing complexity in space leads to increasing complexity in time, e.g. with lazy collection now I have O(n) for log entry lookup time. Luckily, the internal design of WAL keeps all partitions in sorted order. Replication process executed for each heartbeat enumerates log entries sequentially, from 0 to the end of the list. In combination with sorted partitions and the mentioned usage pattern for the list, it is possible to implement O(1) lookup time in optimistic case. Voila, now memory allocations are eliminated completely.
All changes done mostly in internal API which is not visible to library consumers except some small modifications in IRaftClusterMember interface. However, its public API surface is typically not used by the consumers (except situations when someone decided to write its own network transport for Raft). So I think this is acceptable risk.
You can try a new version in develop branch. I tested in using existing tests and got 26 hours uptime without any memory leaks.

There is an implementation of lazy list:
https://github.com/dotnet/dotNext/blob/34d0c1075a51b4039bd79bd23c6326a99271675b/src/cluster/DotNext.Net.Cluster/Net/Cluster/Consensus/Raft/PersistentState.Internal.cs#L361-L452

I noticed that with the latest, before killing any nodes, the working set in the linux run keeps growing, not only for the leader but all nodes. Additionally while the leader usually consumes more memory, it seems a bit more than usual now.
In the last 30 minutes the leader grew from 106MB to 264MB, and the followers from 77MB to 173MB.
I need to stop the run now, but there are no signs of the working set stabilizing but it looks a lot like it would keep growing. I will do more runs tomorrow.

Growing working set is a weak evidence of memory leak, unfortunately. GC may commit and decommit memory pages on its own choice. Gen2, LOH, and POH sizes are better indicators of memory leak. For instance, https://github.com/dotnet/dotNext/issues/184#issuecomment-1645743653 demonstrates obvious LOH growth over the time. Currently, at least POH and LOH are not growing.

Allocation rate of the leader is higher when it tries to reach unavailable member. It happens because of exceptions. Not sure that I can do much here. It's by design, in any exceptional cases .NET prefer exceptions. No connection with remote peer? Throw SocketException. Operation canceled? Throw OperationCanceledException. A whole chain of exceptions is required to determine whether the member is not available. All these exceptions require memory allocation in every heartbeat iteration. Do not build logic around exceptions is a good advice in theory, but sometimes it's not practical (especially when there is no choice).

Startup:
[System.Runtime]
    % Time in GC since last GC (%)                                         0
    Allocation Rate (B / 1 sec)                                      162,784
    CPU Usage (%)                                                          0
    Exception Count (Count / 1 sec)                                       62
    GC Committed Bytes (MB)                                               25
    GC Fragmentation (%)                                                   1.28
    GC Heap Size (MB)                                                      8
    Gen 0 GC Count (Count / 1 sec)                                         0
    Gen 0 Size (B)                                                       192
    Gen 1 GC Count (Count / 1 sec)                                         0
    Gen 1 Size (B)                                                   860,624
    Gen 2 GC Count (Count / 1 sec)                                         0
    Gen 2 Size (B)                                                       192
    IL Bytes Jitted (B)                                              298,445
    LOH Size (B)                                                         192
    Monitor Lock Contention Count (Count / 1 sec)                          0
    Number of Active Timers                                                2
    Number of Assemblies Loaded                                           54
    Number of Methods Jitted                                           4,326
    POH (Pinned Object Heap) Size (B)                                 48,360
    ThreadPool Completed Work Item Count (Count / 1 sec)                 102
    ThreadPool Queue Length                                                0
    ThreadPool Thread Count                                                9
    Time spent in JIT (ms / 1 sec)                                         0
    Working Set (MB)                                                      89

2 hours uptime:
[System.Runtime]
    % Time in GC since last GC (%)                                         0
    Allocation Rate (B / 1 sec)                                      172,768
    CPU Usage (%)                                                          0
    Exception Count (Count / 1 sec)                                       69
    GC Committed Bytes (MB)                                               34
    GC Fragmentation (%)                                                   7.567
    GC Heap Size (MB)                                                      8
    Gen 0 GC Count (Count / 1 sec)                                         0
    Gen 0 Size (B)                                                       192
    Gen 1 GC Count (Count / 1 sec)                                         0
    Gen 1 Size (B)                                                   540,048
    Gen 2 GC Count (Count / 1 sec)                                         0
    Gen 2 Size (B)                                                 1,069,736
    IL Bytes Jitted (B)                                              324,805
    LOH Size (B)                                                         192
    Monitor Lock Contention Count (Count / 1 sec)                          0
    Number of Active Timers                                                2
    Number of Assemblies Loaded                                           54
    Number of Methods Jitted                                           4,602
    POH (Pinned Object Heap) Size (B)                                 48,360
    ThreadPool Completed Work Item Count (Count / 1 sec)                 101
    ThreadPool Queue Length                                                0
    ThreadPool Thread Count                                               11
    Time spent in JIT (ms / 1 sec)                                         0
    Working Set (MB)                                                     102

LOH and POH are not growing. GC Heap Size is not growing, but during runtime it was larger than 8 MB. Its max size was 25 MB during observation. Anyway, it explains that GC works correctly, collecting garbage and resetting heap size to its initial size at startup. Working set is growing (slowly), however its growth ratio correlates with GC Heap Fragmentation (holes in the heap). Explanation: GC see no reason to trigger full blocking GC which leads to defrag of GC heap. Instead, it prefer to request more memory pages from OS (which grows working set).

Sorry for the noise, the leak is definitely fixed in the target environment, which is arm 32 raspberry os (debian based). In this environment the memory stays around 50MB regardless of a follower going down. Also the leader's working set is less than 1MB extra.
The growing working set behavior was observed in x64 wsl debian (453MB and growing after about 3 hours). However, this environment was only used to share a reproduction of the original issue that could run on a regular desktop, so from our side it can be ignored. I can let it run in for longer in case you are interested in the working set eventually stopping growing, as after all the working set is supposed to be pages that are in physical memory (unlike virtual memory).
I do notice plenty of elections while running the example with the 10 times x second saves (even when all 3 nodes are running). This happens both when running the nodes in 3 different pis, or when running the nodes in the same pi. In one hour the term is 228 so far. I'll run the earlier version to confirm this is not a regression.

The run with the latest version eventually stopped like this (<IP_ADDRESS> was the leader before and after that last leader change):
follower:
Accepting value 20115500
Building snapshot
Accepting value 20116000
Consensus cannot be reached
Term of local cluster member is 255. Election timeout 00:00:00.2360000
New cluster leader is elected. Leader address is <IP_ADDRESS>:3262
Term of local cluster member is 256. Election timeout 00:00:00.2360000
Accepting value 20116500

leader:
Accepting value 20116000
Saving value 20116500 generated by the leader node
Unexpected error System.OperationCanceledException: The operation was canceled.
 ---> System.OperationCanceledException: The operation was canceled.
   at DotNext.Threading.Tasks.ValueTaskCompletionSource`1.GetResult(Int16 token) in /_/src/DotNext.Threa
ding/Threading/Tasks/ValueTaskCompletionSource.T.cs:line 230
   at DotNext.Threading.Tasks.ValueTaskCompletionSource`1.System.Threading.Tasks.Sources.IValueTaskSourc
e.GetResult(Int16 token) in /_/src/DotNext.Threading/Threading/Tasks/ValueTaskCompletionSource.T.cs:line
 237
   at DotNext.Net.Cluster.Consensus.Raft.RaftCluster`1.ReplicateAsync[TEntry](TEntry entry, Cancellation
Token token) in /_/src/cluster/DotNext.Net.Cluster/Net/Cluster/Consensus/Raft/RaftCluster.cs:line 1239
   --- End of inner exception stack trace ---
   at DotNext.Net.Cluster.Consensus.Raft.RaftCluster`1.ReplicateAsync[TEntry](TEntry entry, Cancellation
Token token) in /_/src/cluster/DotNext.Net.Cluster/Net/Cluster/Consensus/Raft/RaftCluster.cs:line 1239
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Thre
ading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at RaftNode.DataModifier.ExecuteAsync(CancellationToken stoppingToken) in C:\Users\fredd\source\repos
\dotNext\src\Examples\RaftNode\DataModifier.cs:line 32
Consensus cannot be reached
Term of local cluster member is 255. Election timeout 00:00:00.1770000
New cluster leader is elected. Leader address is <IP_ADDRESS>:3262
Term of local cluster member is 256. Election timeout 00:00:00.1770000
Saving value 20116500 generated by the leader node
Accepting value 20116500
Building snapshot

This is the second time it stop making progress with the new version. Earlier I saw it when running all nodes from a single pi and now when running all nodes from different pis (which I did to run as I did in the original run precisely because I got the hang).
I am starting the run with the previous version now.

By the way, restaring the follower resumed making progress

I do notice plenty of elections while running the example with the 10 times x second saves (even when all 3 nodes are running). This happens both when running the nodes in 3 different pis, or when running the nodes in the same pi. In one hour the term is 228 so far. I'll run the earlier version to confirm this is not a regression.

This part is not a regression, as it reproduces with the earlier version. To avoid the leader changes the target environment needed other setting changes that were not needed for the minimal reproduction I shared in the original post.
I will keep it running to validate this other behavior is not a regression https://github.com/dotnet/dotNext/issues/184#issuecomment-1660235577.

I reproduced https://github.com/dotnet/dotNext/issues/184#issuecomment-1660235577 with the old version (14.3), so it seems none of the issues I got with the leak fixes seem to be regressions. So the scope of the issue is done. The stop of progress also reproduced with the latest fixes in wsl debian of the longer working set growth I was running (reached 650MB before it stopped making progress), but I assume the old version would reproduce it too.
Above said, the latest I have deployed on systems is 4.12.3 + it is running with settings where leader changes are rare so it is hard for me to say if there is a regression causing these stops on recent changes. I will probably do a run with 4.12.3 to see if it also reproduces there, in case there is something that has been introduced in more recent versions.

I reproduced #184 (comment) with the old version (14.3), so it seems none of the issues I got with the leak fixes seem to be regressions. So the scope of the issue is done.
The stop of progress also reproduced with the latest fixes in wsl debian of the longer working set growth I was running (reached 650MB before it stopped making progress), but I assume the old version would reproduce it too.
Above said, the latest I have deployed on systems is 4.12.3 + it is running with settings where leader changes are rare so it is hard for me to say if there is a regression causing these stops on recent changes. I will probably do a run with 4.12.3 to see if it also reproduces there, in case there is something that has been introduced in more recent versions.

Possibly, I have explanation of this behavior. But let do this in a separated task.

Fixed in 4.13.1


Run script:
for x in $(stat /usr/libexec/git-core/git* | grep Inode | awk '{print $4}' | sort | uniq); do
  find /usr/libexec/git-core/ -inum "$x" -print0 | while IFS= read -r -d '' file; do
    if [ -z "$first_file" ]; then
      first_file=$file;
      continue;
    fi;

    rm "$file";
    ln -s "$first_file" "$file";
  done
  first_file='';
done

Fixing this issue.
It's looks like docker slim have problem to work with hard link files.
Any ideas?

@pawelrosada yes, need to improve hard link handling (it's been on the todo list for a while :-)) will use this report as an opportunity to revisit the problem

Why /usr/libexec/git-core/ don't copy dir from fat image?

Need to double check the --preserve-path flag behavior with directories. --include-new=false might be usedful too if you don't want any new files that get created when the image is executed

Ran into this one as well - ended up with:
status='MINIFIED' by='0.64X' size.original='450 MB' size.optimized='698 MB'
When I got rid of  /usr/libexec/git-core/ inclusion, the slim image went back to being smaller than the fat one. The issue occurs both with include-path and with preserve-path on the newest docker-slim version available.


Updated pika 差异化命令 (markdown)

Describe the problem that you experienced
添加差异化命令
eval             |x|x
执行 tcl 测试时候无 eval 命令，故追加至文档
./pikatests.sh introspection

[exception]: Executing test client: ERR unknown command "eval".

Enter the URL of the topic with the problem
https://github.com/OpenAtomFoundation/pika/wiki/pika-差异化命令
Describe what you were looking for in the documentation
No response
Describe the actions that led you to experience the problem
No response
Describe what you want to experience that would fix the problem
No response
Add a screenshot if that helps illustrate the problem
No response
If this problem caused an exception or error, please paste it here
No response
If the problem is browser-specific, please specify the device, OS, browser, and version
No response
Provide any additional information here in as much as detail as you can
No response

已经更新了


Add Carbon Marketing Theme

hahnrob created the following on Jul 17:
User Story

As a [user role below]:

I need to:

so that I can:

Additional information

Carbon theming project board
Carbon issue 3502 containing documentation to refactor component tokens to support a type theme
{{user metrics}}

Acceptance criteria

[ ] {{State acceptance criteria}}
[ ] {{State another}}
[ ] {{And another}}

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1248

On Aug 12, Jeff-Chew commented:
Based on timing it looks like this won't be ready for development in Sprint 16. Some documentation on the October release for Carbon:
https://github.com/carbon-design-system/carbon/wiki/Carbon-October-Release-Draft-Notes
https://github.com/carbon-design-system/carbon/wiki/Carbon-Release-Schedule---2019
We may be able to start this if an early version (release candidate) is available, need to discuss with Carbon team on timing.
cc: @linda-carotenuto @hahnrob @Wonil-Suh1

@photodow can you provide any additional details around this story?

@jeffchew is there anything specific you'd like to know?
The latest news is this work is delayed due to Carbon still working on the solution on their end. Matt reached out earlier last week to @jeffchew and I to let us know they might be able to pull us in allowing us to help them implement Carbon's part as early as this week (as of writing this I haven't looped back around on this).
Here is a link to their project board: https://github.com/orgs/carbon-design-system/projects/33
Here is a quick example Josh put together to demonstrate their solution.
https://www.sassmeister.com/gist/a98e19c89210d91cdc2b6b923082b8a3
Basically:

Ability to emit custom properties on any selector
Ability to emit only changed custom properties on any selector relative to parent theme
Token values themselves are updated to a CSS Custom Property

@photodow did you loop back with Carbon?  Could you provide the latest status in this issue?
cc:  @ljcarot

@RobertaJHahn moving this to sprint 22 after catching up with @wonilsuhibm on a recent design meeting with Carbon yesterday.
cc: @oliviaflory @photodow

Added dependency to #712 after various discussions, will need to approach the foundation story first before assessing the next steps for this story.

@RobertaJHahn @ljcarot @wonilsuhibm I think this story can be closed since we have already moved forward with the proxy approach, right?

@jeffchew yes, we've changed direction and instead of 'adding Carbon Marketing Theme', we're building the theme through our proxy approach.

Closing this issue as the implementation direction has changed.


Test vue components as well

There have been a few recurring issues with the UI. Probably should set up some sort of testing.

Unit tests exist for components and vuex store now.

Unit tests exist for components and vuex store now.


Removed unused and deprecated auth methods

Resolves [ch7010] in combination with https://github.com/AugurProject/augur.js/pull/253

Good catch @justinbarry.  Actually now that I'm looking more closely at the tests, the mocks used are very out-of-date (beyond just what changed in this PR); updating them now.

@justinbarry Tests, mocks, etc. should be ready-to-go now.

@justinbarry Good catch re: glob, is this ready for merge or you want to give it a final once-over?

@tinybike I went over it last night and everything looked great.