Upgrade version.error-prone-orig 2.18.0 -> 2.19.1

This PR contains the following updates:

Package
Type
Update
Change

com.google.errorprone:error_prone_annotations (source)
compile
minor
2.18.0 -> 2.19.0

com.google.errorprone:error_prone_core (source)

minor
2.18.0 -> 2.19.0

com.google.errorprone:error_prone_test_helpers (source)
compile
minor
2.18.0 -> 2.19.0

com.google.errorprone:error_prone_core (source)
compile
minor
2.18.0 -> 2.19.0

com.google.errorprone:error_prone_check_api (source)
compile
minor
2.18.0 -> 2.19.0

com.google.errorprone:error_prone_annotation (source)
compile
minor
2.18.0 -> 2.19.0

Release Notes

google/error-prone
v2.19.0: Error Prone 2.19.0
Compare Source
New Checkers:

NotJavadoc
StringCaseLocaleUsage
UnnecessaryTestMethodPrefix

Fixes issues:  #956, #3504, #3654, #3703, #3731, #3737, #3760, #3779, #3796, #3809, #3813
Full Changelog: https://github.com/google/error-prone/compare/v2.18.0...v2.19.0

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade version.error-prone-orig 2.18.0 -> 2.19.0

See:
- https://github.com/google/error-prone/releases/tag/v2.19.0
- https://github.com/google/error-prone/compare/v2.18.0...v2.19.0

Lastly, we should also drop StringCaseLocaleUsage.

I'll create a PR for that :).

I'll create a PR for that :).

Doesn't it belong in this PR? :thinking:

Lol, for some reason I thought I clicked the PSM PR, but yes we should haha.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

Filed: https://github.com/PicnicSupermarket/error-prone/pull/60.
Do we add XXX references when I open the PR upstream and merge then? WDYT?

Rebased. Will merge once built. Decided to leave the @CanIgnoreReturnValue as-is, in favour of a @Suppresswarning. We should not forget to drop them if/when an upstream PR to skip Refaster template methods is merged and released.


Not working as expected in rainy days

On redis connection failure, I do not get exception.
I have upgraded to redis 4.2.0 with the following lambda :
export const handler = async (
    event: APIGatewayEvent, context: Context, callback: APIGatewayProxyCallback
) => {
    try {
        console.log(`Lambda triggered with event: ${JSON.stringify(event)}`);
        context.callbackWaitsForEmptyEventLoop = false;
        const redisClient = redis.createClient({
            socket: {
                host: '<IP_ADDRESS>',
                port: 6379,
                reconnectStrategy: function (retriesAttemptedSoFar: number): number | Error {
                    if (retriesAttemptedSoFar > 3) {
                        // End reconnecting with error
                        return new Error(`Redis retry attempt=${retriesAttemptedSoFar}`);
                    }
                    console.info(` try reconnect after ${Math.min(retriesAttemptedSoFar * 10, 30)}ms`);
                    // reconnect after
                    return Math.min(retriesAttemptedSoFar * 10, 30);
                }
            },
        });
        redisClient.on('ready', () => {
            console.log(`Got "ready" event from Redis. Connection established.`);
        });
        redisClient.on('connect', () => {
            console.log(`Got "connect" event from Redis. Stream is connected to the server`);
        });
        redisClient.on('error', (err) => {
            console.log(`Got an ERROR from Redis. Details: ${err.message}`);
        });
        await redisClient.connect();
        let serverStates : string[] = [];
        const MAX_RETRIES = 3;
        let i = 0;
        while (i < MAX_RETRIES) {
            try {
                serverStates = await redisClient.lRange('123', 0, -1);
            } catch (e) {
                i++;
                const logMessage = i < MAX_RETRIES ?
                    `attempt ${i}: Failed to store message. Trying again...` :
                    `attempt ${i}: Failed to store message. All attempts failed`;
                console.warn(logMessage);
                await new Promise(resolve => setTimeout(resolve, 10));
            }
        }
        if (i >= MAX_RETRIES) {
            throw new Error('Exceeded Max Attempts to store message in Redis');
        }
        console.log(`ServerStates: ${JSON.stringify(serverStates)}`);

        console.log(`${JSON.stringify(event)} Lambda finished successfully`);
        callback(null, {
            statusCode: 200,
            body: 'theResult'
        });
    } catch (e) {
        const error = e as Error;
        console.error(`Lambda execution failed. Got error: ${error.message}`);
        callback(error);
    }
}

If I do not get exception from redis, all works.
If I do not specify reconnectStrategy and redis connection fail, the code trys to reconnect inifinitly.
If redis connection fail with reconnectStrategy code, lambda gets to the catch section after 3 re-connections as expected.

The problem is : If I succeed to connect to redis, but before lrage redis stops (redis connection fail Socket closed unexpectedly) redis client reconnects for 3 times as written in reconnectStrategy, and after the 3 re-connects, the code stops and do not get to the catch section, ending the lambda as successfully finished.
How can I get to the exception section in this scenario ?
In redis 3.1.X, in similar case lambda finished with exception.
Environment:

Node.js Version:  v14.1.0
Redis Server Version: 6.2.6
Node Redis Version: 4.2.0
Platform: Windows 10

summary of error:

I have error handling for everything. with logs.
after successful connect and before await redisClient.lRange('123', 0, -1); (I have "await"!!!!), I stop redis server locally and expect the reconnectStrategy to be triggered inside lRange function.
I do NOT turn on redis server locally.
expected behavior: I am expecting the reconnectStrategy to fail eventually and propagate the error to the await redisClient.lRange('123', 0, -1); (await !!!!).
actual behavior: the error is not propagated to the catch of the await redisClient.lRange('123', 0, -1); and just thrown to the event loop and the process ends gracefully (exit code = 0 !!!! instead of 1").

Hi @idaamit, thanks for reporting it
I've already implemented a fix in #2226, wanna give it a shot (You'll need to clone my fork, checkout to reconnect-strategy-errors branch, and run npm i && npm run build-all) before I'll merge and release it?

Hi @leibale ,
I have downloaded version 4.3.0 and the problem is solved, thank you for attending the issue so rapidly.

From a few seconds the server goes down as in a container, then tried to downgrade to previous versions within 4.+ because of the same local error not 4.0.0 is only stable without errors in version 3.1.2.

Hi @leibale , I have downloaded version 4.3.0 and the problem is solved, thank you for attending the issue so rapidly.
For testing, I was using redis-mock library, but because of the braking changes in version 4.x the library is no longer usable, I have opened an issue on it but I see repository is not maintained :-(. @leibale do you have a different recommendation for mocking library?

@idaamit If you're running Docker https://www.npmjs.com/package/testcontainers might be worth a try since then you could also use a proper watch implementation


update packages

:x: Build TheIdServer 4.0.1-fix-dependencies1-0011 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/2779e6c211 by @)

:white_check_mark: Build TheIdServer 4.0.1-fix-dependencies.1+11.build.1564 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/2779e6c211 by @)


Add  database integration guides

Purpose
Add guides for

querying a mysql database
import a csv file to MongoDB

This PR is updated in https://github.com/wso2/ballerina-integrator/pull/350


text style transfer discriminator only trained on real samples?

Hello, I'm having trouble understanding how your "text style transfer" model works, given that you changed it from discriminating between generated and real samples (i.e. the "discriminator" is only trained on real data). Please explain, that and the independency constraint which you removed. After 6 epochs of training (approximately 18 hours), all the samples are merely duplications. How should I interpret this and how many epochs of training must I complete before I expect the samples to represent what you show in the paper?
Update: you can expect generated output to begin diverging around epoch 12 - for me a day and a half of training.

I should also note that your code, for me, does not resume training from checkpoints, but starts all over if one interrupts and restarts training. I can fix this of course, but I assume you intended your code to resume training from the latest checkpoint, so fyi.

Update, for anyone, is that you can expect generated output to begin diverging around epoch 12 - for me a day and a half of training.

For why the model would work, please read the paper toward controlled generation of text For details.
For resuming from checkpoint, did you specify —resume?

Thank you, I did not specify resume. I am aware of the paper. What I am referring to actually are the changes made in this model from the model described in the paper, and how to interpret those changes. In particular, should I consider this model no longer using the generator samples on the discriminator and dropping the independency constraint as trivial, or something I should treat with greater importance when understanding this particular model in code?

This is a simplified implementation of the model described in the model, and its performance is reasonably strong.

The discriminator here (and in the paper) is a sentiment classifier, rather than a real/fake classifier. In the code we only use real positive/negative data to pre-train the classifier and fix it. Additionally using generator samples to fine-tune the classifier could further improve the classification accuracy (as described in the paper), but we omitted it as the addition of classification accu is not critical for transfer quality. And there are alternative, more straightforward ways to improve the accu — you may use a better classifier architecture, e.g., the classifier based on BERT (see our BERT example).

Independency constraint is omitted just for simplicity.

Overall, the model in code implements the key idea in the paper that uses a style classifier as a direct supervision over the generated samples to drive style change.

Thank you very much for the explanation.


Cannot autowire settings automatically

Any reason why autowire not working properly?
Cannot autowire argument $appSettings of "App\Controller\DefaultController::inject()": it references class "App\Settings\AppSettings" but no such service exists.
I know that adding this line in services.yml it works, but it should be done automatically, right?
App\Settings\AppSettings: ~
https://github.com/pedrocasado/test-settings

This is now fixed. This was caused by the SettingsTrait which made the constructor private and therefore the class non-instantiable.
However, then symfony's class discoverer ignores the settings classes and dont register them as services (even if we dont need the constructor later, as we have a custom factory method). I have done my tests with settings classes without the SettingsTrait (as it is not really required), so I never noticed before.
As a fix I have just made the constructor public again, and let them throw an exception on runtime. There might be a better approach by implementing a custom discovery logic, but the fix should be reasonable for now.


kcp 模式报错

kcp模式之前用的好好的，现在用不了，报这样的提示错误。
2020/05/15 14:17:18 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > EOF

did you ever figure this out, i have same issued

@apfsx No, i don't want to reconfigure my server so i use websocks style. Any ideas you have to solve it?

Same problem. I'm using a docker version. I just forgot to expose my port as udp ( default is tcp-only in docker compose )
"2020:2020"->"2020:2020/udp" fixed it


Margins are broken in bullet lists on 0.5.0rc1

Problem
Margins in bullet lists are extremely large on 0.5.0rc1
Happens on both Sphinx 2.4.4 and Sphinx 3.0.3
Reproducible Project
RTD 0.4.3, Sphinx 2.4.4 (how it should look):
https://docs.discord.red/en/latest/guide_publish_cogs.html
RTD 0.5.0rc1, Sphinx 2.4.4 & 3.0.3 (broken margins):
https://jack1142-red-prs.readthedocs.io/en/v3-bump_deps/guide_publish_cogs.html
Error Logs/Results
RTD 0.5.0rc1, Sphinx 2.4.4 & 3.0.3 (broken margins):

Expected Results
RTD 0.4.3, Sphinx 2.4.4 (how it should look):

Environment Info

Python Version: 3.8.0
Sphinx Version: 2.4.4 & 3.0.3
RTD Theme Version: 0.5.0rc1

Thanks for the report! You actually look to be using the html4 writer still, does the output improve with the html5 writer?
The bug here looks to be a nested
 element and a selector adding margin to :last-child. This in theory shouldn't have changed, but likely there wasn't a test case with a

... structure.

@agjohnson That particular thing looks better on html5 writer, though it's not perfect - margins for the "tip box" are a little off:

Link: https://jack1142-red-prs.readthedocs.io/en/v3-bump_deps_html5_writer/guide_publish_cogs.html

For now I just wanted to see if I can upgrade Sphinx without using new writer, I will move to it eventually, but there are still some problems with it like:

small margins in lists for code blocks (actually not sure if there's an issue for it):

html4 writer (https://docs.discord.red/en/latest/update_red.html#linux-mac):

html5 writer (https://jack1142-red-prs.readthedocs.io/en/v3-bump_deps_html5_writer/update_red.html#linux-mac):

Parameters/Returns/Return Type/etc in functions/methods are unnaturally big (#766 maybe?):

html4 writer (https://docs.discord.red/en/latest/framework_bank.html#redbot.core.bank.set_balance):

html5 writer (https://jack1142-red-prs.readthedocs.io/en/v3-bump_deps_html5_writer/framework_bank.html#redbot.core.bank.set_balance):

This, not sure if it's wrong but looks weird in comparison to what was there before (hard to find an issue if you don't what to look for 😄)

html4 writer (https://docs.discord.red/en/latest/guide_cog_creation.html#getting-started):

html5 writer (https://jack1142-red-prs.readthedocs.io/en/v3-bump_deps_html5_writer/guide_cog_creation.html#getting-started):

I can make issues for those, though I didn't plan to look into html5 writer just yet 😄

Great, that's all very helpful. Seems we need to get some more test cases into the demo docs.
That last one is a good example -- a definition list with multiple words (?) i believe gets a different class (dl.simple) than other definition lists. There is already a fix merged for that one at least, #914.

I should probably make a separate issue for the second (or add a comment on some existing issue if you've got any pointers), the third one is already fixed in master as you said and first one might be related to this issue.

I've opened #939 to address the spacing issues.
I noticed in building a test case that your examples are rendering as blockquotes inside list elements, which will affect display a bit more than simply nesting. This is due to the spacing being different between the reST bullet list and the paragraph/admonition blocks that follow the initial list item text.
I made our test case use the list spacing, not blockquote spacing, but things look more consistent now. I didn't test how this might affect the blockquote usage nested in a list item.
I'm going to treat #939 as the fix to this issue, but perhaps if there is something to change after a 0.5.0rc2 we can decide if it needs to be a theme fix or not.

@agjohnson I'm not entirely sure, is it intended that the margins here are now larger?
0.5.0rc2:

0.4.3:


DEPLOYMENT

Deployment
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

I Did it!😊!!


Convert to python 3

Hi,
I made it work with python 3. Thought I'd send it back to you. It's my first pull request ever, so let me know if anything is wrong.
Cheers!

woops, saw other people already did the same work, so this is duplicate.


Can we put the js file to cdn?

Some of my friend say that they can not visit https://utteranc.es/client.js . Can we put the file to CDN?
Or can I save the js file to my server?
Thank

I don't think that will work. client.js adds an iframe to the page that loads https://utteranc.es/utterances.html


Could not open terminal for stdout: could not get termcap entry

I installed the gradle 4.7 my sabayon linux and I do step by step completed installing.But I can't run the gradle.I type in terminal gradle -v command.I got the following error.

FAILURE: Build failed with an exception.

What went wrong:
Could not open terminal for stdout: could not get termcap entry
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Please help me.

export TERM=xterm-color
https://github.com/gradle/gradle/issues/4426
It's working.Thanks


Close stale cache responses and fix build

okhttp3.internal is not a public API, and ResponseBody.close() already closes quietly.


Fixes #2235 - Add docs for maxJsonSize

Added docs for maxJsonSize
Removed reference to maxUploadSize which has not been used for a long time.  Once upon a time, we used bodyParser.raw for file uploads.  However, that method writes temp contents to disk, which cannot do (both for security and disk space reasons).  So instead, we replaced it with a low level stream model that streams the uploaded content to the storage system (i.e., directly to S3).  Therefore, maxUploadSize has not been relevant for over 2 years.

coverage: 94.347%. remained the same when pulling 71cb6940f39c7eba8c145b6cf7965002bb5359e4 on cody-doc-max-json-size into b244eeae8b279e2935a49894d4b26901d8073220 on main.


Sliders bind incorrect floats if moved quickly.

Describe the bug
Here you can see a breakpoint in the setter of Foo, which WinUI3 hits when I move the slider that's bound to that variable.
In this case, I moved the slider all the way up as fast as I could. You can see that the UI thread hasn't updated yet, but WinUI3 has determined I moved the slider up just slightly to a value of -75. (up from -90, on this slider which ranges -90 to +90)
After allowing execution to continue, the UI updates to reflect the correct, maximal position to which I dragged the slider, but no further updates are made to the bound data value--the breakpoint is not hit again, and I can see in HomeApp that my monitor is still sitting at -75 degrees off center:
I don't know whether it's possible to work around this bug by using something other than slider data bindings (such as OnValueChanged events). If that is possible, it's going to take a lot of refactoring.
Steps to reproduce the bug

Create a slider which is bound to a float property named "float FooFloat" with TwoWay binding mode.
For example
<Slider x:Name="FooSlider" Value="{x:Bind FooFloat, Mode=TwoWay}" AutomationProperties.Name="simple slider" Width ="200" Minimum="0" Maximum="100"/>

Set the slider to maximum value, then set a breakpoint in the setter of FooFloat. Make sure the new value is used inside, so you can observe its value when you breakpoint.

Move the slider to the minimum value extremely quickly. Ideally, automate a mouse macro to move it.

Observe that the breakpoint is hit, as the binding causes the float value to be set. Use the Visual Studio debugger to look at the value being set. It doesn't match the minimum value specified.

If there are any subsequent breakpoint hits due to multiple slider polls, they still won't match the correct value.

The final internal state of the data will be incorrect, and mismatched with the UI, which shows the correct slider value.

Expected behavior

Create a slider which is bound to a float property named "float FooFloat" with TwoWay binding mode.
For example
<Slider x:Name="FooSlider" Value="{x:Bind FooFloat, Mode=TwoWay}" AutomationProperties.Name="simple slider" Width ="200" Minimum="0" Maximum="100"/>

Set the slider to maximum value, then set a breakpoint in the setter of FooFloat. Make sure the new value is used inside, so you can observe its value when you breakpoint.

The internal value matches the final slider value displayed in the UI.

Screenshots
Here you can see a breakpoint in the setter of a slider, which WinUI3 hits when I move the slider that's bound to that variable.
In this case, I moved the slider all the way up as fast as I could. You can see that the UI thread hasn't updated yet, but WinUI3 has determined I moved the slider up just slightly to a value of -75. (up from -90, on this slider which ranges -90 to +90)

After allowing execution to continue, the UI updates to reflect the correct, maximal position to which I dragged the slider, but no further updates are made to the bound data value--the breakpoint is not hit again, and I can see that my app state still reflects -75 as the current value.

NuGet package version
WinUI 3 - Windows App SDK 1.4.1: 1.4.230913002
Windows version
Windows 11 (22H2): Build 22621
Additional context
Please feel free to reach out on Teams:
<EMAIL_ADDRESS>

Having trouble reproducing this now..


Question: how i can deploy lona apps for free?

There are any services that does this with lona? There already are with flask

Hi @nacho00112!
There are no hosting services that offer Lona app hosting, that I am aware of, but Lona is pretty easy to start in a docker container. So any service that offers docker containers should be fine

Hi @nacho00112! There are no hosting services that offer Lona app hosting, that I am aware of, but Lona is pretty easy to start in a docker container. So any service that offers docker containers should be fine

Then may be a good idea to include this theme in the documentation, and also would be cool if lona autogenerates the docker files by itself

@nacho00112: Yes you are absolutely right, and it's been on the wishlist for ages. I will create an issue for it.

@nacho00112: Yes you are absolutely right, and it's been on the wishlist for ages. I will create an issue for it.

Please bro your project is exactly what i'm looking for is very good

Ok :) i'll try to do it this weekend, or next week. Can you review/test the pull-request?

@nacho00112: https://lona-web.org/1.x/deployment/deploying-on-docker.html
I hope this helps. Let me know if some information is missing

What that COPY means? I have to use it with all my app files? Using path globs?

In the dockerfile? That means all contents of the current directory get copied to the image

In the dockerfile? That means all contents of the current directory get copied to the image

All contents, including hello-world.py

Can we close this issue?


Not working for Opensearch v2..>

Hi,
When I try to install the plugin I get:
Exception in thread "main" java.lang.IllegalArgumentException: Plugin [prometheus-exporter] was built for OpenSearch version 1.2.3 but version 2.0.1 is running

Any update on this?

For 2.x, ./bin/opensearch-plugin install https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/releases/download/<IP_ADDRESS>/prometheus-exporter-<IP_ADDRESS>.zip


Add autofix for preferTemplate rule

Currently broken because of the scope.getBinding() issue I mentioned.
Autofix:
// before:
a + "b" + c + "d"
// after:
`${a}b${c}d`

@jamiebuilds Want to rebase? Not sure what changes are in master but this might Just Work™ now.

TODO:

Strip loc information where necessary
Figure out how to handle comments in positions they can't be in anymore (bail?)

One thing that bug me with the current implementation of this rule is that 'a' + 'b' gets fixed into:
`a${'b'}`

Keeping the concat here may be really useful. Especially when concatenating long strings to avoid line wrap.

@ooflorent Yup, that's what this code is doing https://github.com/facebookexperimental/rome/pull/187/files#diff-a4c9c2d24510abf7ef39564000f44422R229-R243

Sorry for letting this hang around for so long @jamiebuilds. I manually merged and committed you as the coauthor in 7f11d0103b1a7528d22c51031b3fff9bba58f335. Thank you!


Add an interactive hover button

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[ ] Proposal to the Repository
[ ] Documentation / README.md changes

Details:

@code-gen21 Assigned to you!

Hi, are you still working on this issue? If you've already made a PR with the changes that have been merged then please close the issue. If you have an open PR, please mention this issue number in your PR in order to link them.


Location of downloaded bin file to deploy

HI,
I want to deploy the model in machine A.
After executing the sh file, the docker seems worked.
Due to the bad internet  quality of machine A, it couldn't sucessfully download the whole bin files(approximately 26 gb) as the docker start up.
So I downloaded the bin files from here https://huggingface.co/yentinglin/Taiwan-LLaMa-v1.0/tree/main to my own computer
and move them to machine A.
However,  it could not work(It still attempt to download the bin files from internet).
I am not certain the path of the bin files I should place to in the project folder.
Any suggestion?

You can specific the absolute path of model in container, e.g.
# Must be aware that the model path can not include dot
git clone https://huggingface.co/yentinglin/Taiwan-LLaMa-v1.0 TwLLaMAv1

# Set other variables as usual
docker run --gpus all \
           --shm-size 1g \
           -p $port:80 \
           -v $PWD/TwLLaMAv1:/TwLLaMAv1 \
           ghcr.io/huggingface/text-generation-inference:latest \
           --model-id /TwLLaMAv1 \
           ...

You can specific the absolute path of model in container, e.g.
# Must be aware that the model path cannot include a dot.
git clone https://huggingface.co/yentinglin/Taiwan-LLaMa-v1.0 TwLLaMAv1

# Following is the script I used in my use case.
docker run --gpus 'device=0' \
           --shm-size 1g \
           -p 8085:80 \
           -v $PWD/TwLLaMAv1:/TwLLaMAv1 \
           ghcr.io/huggingface/text-generation-inference:latest \
           --model-id /TwLLaMAv1 \
           --num-shard 1 \
           --quantize bitsandbytes \
           --max-input-length 1000 \
           --max-total-tokens 2000

It works!
Thanks for kind help!


Inconsistent Length of Private Key Byte Array in deriveKeyPair Method

Inconsistent Length of Private Key Byte Array in deriveKeyPair Method
I stumbled upon this browsing Github and not understanding how the private key was 33 bytes without a prefix.
Description
The deriveKeyPair method occasionally produces private keys with lengths of either 32 or 33 bytes. This inconsistency is attributed to the behavior of the BigInteger.toByteArray() method. It returns the byte array in two's-complement form and occasionally prepends a zero byte to ensure the number is not negative.
      private static KeyPair deriveKeyPair(final UnsignedByteArray seedBytes, final int accountNumber) {
        Objects.requireNonNull(seedBytes);

        // private key needs to be a BigInteger so we can derive the public key by multiplying G by the private key.
        final BigInteger privateKeyInt = derivePrivateKey(seedBytes, accountNumber);
        final UnsignedByteArray publicKeyInt = derivePublicKey(privateKeyInt);

        return KeyPair.builder()
          .privateKey(PrivateKey.of(UnsignedByteArray.of( /*>>>*/ privateKeyInt.toByteArray() /*<<<*/ )))
          .publicKey(PublicKey.fromBase16EncodedPublicKey(
            UnsignedByteArray.of(publicKeyInt.toByteArray()).hexValue()
          ))
          .build();
      }

The length of the byte array byteArray is sometimes 33 bytes and sometimes 32 bytes, which could lead to potential issues downstream where a fixed-length byte array might be expected.
Expected Behavior
Consistent length for the private key's byte array.
Actual Behavior
Variable length of 32 or 33 bytes for the private key's byte array.
Why
The inconsistency is due to the two's-complement representation that BigInteger.toByteArray() uses. Sometimes a 0 byte is prepended to make sure the number is not interpreted as negative.
Note
The JavaScript edition of ripple-keypairs uses a 33-byte representation with a 0 byte prefix. The secp256k1 curve generally uses 32-byte scalars naturally.
Possible Solution
Normalize the private key to a consistent length. Either:

Consistently use a 33-byte representation with a 0 byte prefix for compatibility with other Ripple products.
Or normalize to a 32-byte scalar which aligns with the natural length used in secp256k1.

Fixtures

Seed Hex
Private Key Hex
Private Key Length

358c75d5ad5e2ff5e19256978f18f0b9
00fbd60c9c99ba3d4706a449c30e4d61dcc3811e23ef69291f98a886cec6a8b0b5
33

b7e99c6bb9786494238d2ba84eabe854
7030cbd40d6961e625ad73159a4b463aa42b4e88cc2248ac49e1edcb50af2924
32

@sublimator, I spoke with @sappenin yesterday and we've decided to normalize all secp256k1 private keys to 33 bytes, prefixed with 0x00 to be consistent with xrpl.js and xrpl-py. PR should be ready soon.

This is now fixed via #487.


New Firebase Segment on Oh My Posh!

Thanks for suggesting this!
I decided to take you up on this functionality and add this as a legitimate segment on Oh My Posh:
https://github.com/JanDeDobbeleer/oh-my-posh/pull/4840
It was just merged in and is live! https://ohmyposh.dev/docs/segments/firebase
Since you're actively using this functionality, give the new segment a try and let me know if there are any bugs!
Thanks for your suggestion and I hope the new segment helps!
Take care,
- Ivan

Hi
Thank you so much for doing the dirty work 😜
However it doesn't work exactly like the script I originally made, because if you are in a child folder of the active firebase project the segment doesn't display.
I'll close this issue and open one on the official repo with more information.
Thanks again for adding this segment, which I think will be useful to many people.

Ah! Good catch. I'll put out a patch to check if the current path is part of the active project path


XML::Builder behaves strangely with respect to namespaces

Originally pointed out on nokogiri-talk by Corey Powell (who I think is @IceDragon200 on GitHub):

This gist contains a sample script, the expected and actual output from nokogiri
https://gist.github.com/IceDragon200/873139e6c7d395dfcd9793949f9b2246
Summary: For some reason, namespaces are being passed down to child elements, is there anyway to disable this behaviour? (without some voodoo XML fragment magic)

Whoo, this got complicated and this behavior is going to be reverted in v1.12.4 but Documents will have an attribute you can set to change this behavior to what's described above; and Builder will allow you to set that attribute via the initializer. Keep your eyes open for that version and check out the update Builder docs.

See #2320 for the changes I'd like to make. Comments and feedback welcome.


docker build image failed

build base image时报错，最小内存需要多大？
ImportError: /usr/local/lib/python3.8/dist-packages/sklearn/__check_build/../../scikit_learn.libs/libgomp-d22c30c5.so.1.0.0: cannot allocate memory in static TLS block
完整的stack：

=> [internal] load build definition from Dockerfile.base                  0.0s
=> => transferring dockerfile: 696B                                       0.0s
=> [internal] load .dockerignore                                          0.0s
=> => transferring context: 2B                                            0.0s
=> [internal] load metadata for nvcr.io/nvidia/pytorch:22.12-py3          1.9s
=> [1/5] FROM nvcr.io/nvidia/pytorch:22.12-py3@sha256:09a80f272dd173c9d8  0.0s
=> CACHED [2/5] RUN pip config set global.index-url https://pypi.tuna.ts  0.0s
=> CACHED [3/5] WORKDIR /app                                              0.0s
=> CACHED [4/5] RUN echo -e 'from transformers import AutoTokenizer, Aut  0.0s
=> ERROR [5/5] RUN python /get-models.py &&     rm -rf /get-models.py     2.2s

[5/5] RUN python /get-models.py &&     rm -rf /get-models.py:
#8 1.924 Traceback (most recent call last):
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/sklearn/__check_build/init.py", line 44, in
#8 1.924     from ._check_build import check_build  # noqa
#8 1.924 ImportError: /usr/local/lib/python3.8/dist-packages/sklearn/__check_build/../../scikit_learn.libs/libgomp-d22c30c5.so.1.0.0: cannot allocate memory in static TLS block
#8 1.924
#8 1.924 During handling of the above exception, another exception occurred:
#8 1.924
#8 1.924 Traceback (most recent call last):
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/utils/import_utils.py", line 1126, in _get_module
#8 1.924     return importlib.import_module("." + module_name, self.name)
#8 1.924   File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
#8 1.924     return _bootstrap._gcd_import(name[level:], package, level)
#8 1.924   File "", line 1014, in _gcd_import
#8 1.924   File "", line 991, in _find_and_load
#8 1.924   File "", line 975, in _find_and_load_unlocked
#8 1.924   File "", line 671, in _load_unlocked
#8 1.924   File "", line 848, in exec_module
#8 1.924   File "", line 219, in _call_with_frames_removed
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/pipelines/init.py", line 61, in
#8 1.924     from .document_question_answering import DocumentQuestionAnsweringPipeline
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/pipelines/document_question_answering.py", line 29, in
#8 1.924     from .question_answering import select_starts_ends
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/pipelines/question_answering.py", line 8, in
#8 1.924     from ..data import SquadExample, SquadFeatures, squad_convert_examples_to_features
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/data/init.py", line 26, in
#8 1.924     from .metrics import glue_compute_metrics, xnli_compute_metrics
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/data/metrics/init.py", line 18, in
#8 1.924     if is_sklearn_available():
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/utils/import_utils.py", line 565, in is_sklearn_available
#8 1.924     return is_scipy_available() and importlib.util.find_spec("sklearn.metrics")
#8 1.924   File "/usr/lib/python3.8/importlib/util.py", line 94, in find_spec
#8 1.924     parent = import(parent_name, fromlist=['path'])
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/sklearn/init.py", line 81, in
#8 1.924     from . import __check_build  # noqa: F401
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/sklearn/__check_build/init.py", line 46, in
#8 1.924     raise_build_error(e)
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/sklearn/__check_build/init.py", line 31, in raise_build_error
#8 1.924     raise ImportError("""%s
#8 1.924 ImportError: /usr/local/lib/python3.8/dist-packages/sklearn/__check_build/../../scikit_learn.libs/libgomp-d22c30c5.so.1.0.0: cannot allocate memory in static TLS block
#8 1.924 ___________________________________________________________________________
#8 1.924 Contents of /usr/local/lib/python3.8/dist-packages/sklearn/_check_build:
#8 1.924 check_build.cpython-38-aarch64-linux-gnu.so__init.py               pycache
#8 1.924 setup.py
#8 1.924 ___________________________________________________________________________
#8 1.924 It seems that scikit-learn has not been built correctly.
#8 1.924
#8 1.924 If you have installed scikit-learn from source, please do not forget
#8 1.924 to build the package before using it: run python setup.py install or
#8 1.924 make in the source directory.
#8 1.924
#8 1.924 If you have used an installer, please check that it is suited for your
#8 1.924 Python version, your operating system and your platform.
#8 1.924
#8 1.924 The above exception was the direct cause of the following exception:
#8 1.924
#8 1.924 Traceback (most recent call last):
#8 1.924   File "/get-models.py", line 1, in
#8 1.924     from transformers import AutoTokenizer, AutoModelForSeq2SeqLM, pipeline
#8 1.924   File "", line 1039, in _handle_fromlist
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/utils/import_utils.py", line 1116, in getattr
#8 1.924     module = self._get_module(self._class_to_module[name])
#8 1.924   File "/usr/local/lib/python3.8/dist-packages/transformers/utils/import_utils.py", line 1128, in _get_module
#8 1.924     raise RuntimeError(
#8 1.924 RuntimeError: Failed to import transformers.pipelines because of the following error (look up to see its traceback):
#8 1.924 /usr/local/lib/python3.8/dist-packages/sklearn/__check_build/../../scikit_learn.libs/libgomp-d22c30c5.so.1.0.0: cannot allocate memory in static TLS block
#8 1.924 ___________________________________________________________________________
#8 1.924 Contents of /usr/local/lib/python3.8/dist-packages/sklearn/_check_build:
#8 1.924 check_build.cpython-38-aarch64-linux-gnu.so__init.py               pycache
#8 1.924 setup.py
#8 1.924 ___________________________________________________________________________
#8 1.924 It seems that scikit-learn has not been built correctly.
#8 1.924
#8 1.924 If you have installed scikit-learn from source, please do not forget
#8 1.924 to build the package before using it: run python setup.py install or
#8 1.924 make in the source directory.
#8 1.924
#8 1.924 If you have used an installer, please check that it is suited for your
#8 1.924 Python version, your operating system and your platform.

executor failed running [/bin/sh -c python /get-models.py &&     rm -rf /get-models.py]: exit code: 1

在最近的测试和构建中，我使用的机器基本是 32/64+，但理论来说，如果你开启 swap 应该是没有问题的。（参考某些模型流式处理
ps：有同学在 M1/M2 不修改代码运行起来，应该不是最重要的要素，可解。


podinfo-hr stuck in progressing

I've followed the instructions in readme. Everything went smoothly, but the podinfo-hr seems to be stuck in "progressing" state.

$ kubectl describe applications -n argocd  podinfo-hr
---
Name:         podinfo-hr
Namespace:    argocd
Labels:       app.kubernetes.io/managed-by=flamingo
              flamingo/destination-namespace=podinfo-helm
              flamingo/source-type=HelmRepository
              flamingo/workload-name=podinfo
              flamingo/workload-type=HelmRelease
Annotations:  weave.gitops.flamingo/base-url: http://localhost:9001
              weave.gitops.flamingo/cluster-name: Default
API Version:  argoproj.io/v1alpha1
Kind:         Application
Metadata:
  Creation Timestamp:  2024-01-31T17:37:53Z
  Generation:          16
  Resource Version:    4646
  UID:                 d98adc9e-fa49-4159-870b-2c1891721479
Spec:
  Destination:
    Namespace:  podinfo-helm
    Server:     https://kubernetes.default.svc
  Project:      default
  Source:
    Chart:  podinfo
    Helm:
      Release Name:   podinfo
    Repo URL:         oci://ghcr.io/stefanprodan/charts
    Target Revision:  *
  Sync Policy:
    Sync Options:
      ApplyOutOfSyncOnly=true
      FluxSubsystem=true
Status:
  Controller Namespace:  argocd
  Health:
    Status:  Progressing
  History:
    Deploy Started At:  2024-01-31T17:43:12Z
    Deployed At:        2024-01-31T17:43:12Z
    Id:                 0
    Source:
      Chart:  podinfo
      Helm:
        Release Name:   podinfo
      Repo URL:         oci://ghcr.io/stefanprodan/charts
      Target Revision:  *
  Operation State:
    Finished At:  2024-01-31T17:43:12Z
    Message:      successfully synced (no more tasks)
    Operation:
      Initiated By:
        Username:  admin
      Retry:
      Sync:
        Revision:  *
        Sync Options:
          ApplyOutOfSyncOnly=true
          FluxSubsystem=true
        Sync Strategy:
          Hook:
    Phase:       Succeeded
    Started At:  2024-01-31T17:43:12Z
    Sync Result:
      Revision:
      Source:
        Chart:  podinfo
        Helm:
          Release Name:   podinfo
        Repo URL:         oci://ghcr.io/stefanprodan/charts
        Target Revision:  *
  Reconciled At:          2024-01-31T18:01:30Z
  Resources:
    Group:  helm.toolkit.fluxcd.io
    Health:
      Message:  Helm install succeeded for release podinfo-helm/podinfo-helm-podinfo.v1 with chart<EMAIL_ADDRESS>      Status:   Healthy
    Kind:       HelmRelease
    Name:       podinfo
    Namespace:  podinfo-helm
    Status:     Synced
    Version:    v2beta1
    Group:      source.toolkit.fluxcd.io
    Health:
      Message:  Waiting for HelmRepository to reconcile ...
      Status:   Progressing
    Kind:       HelmRepository
    Name:       podinfo
    Namespace:  podinfo-helm
    Status:     Synced
    Version:    v1beta2
  Summary:
  Sync:
    Compared To:
      Destination:
        Namespace:  podinfo-helm
        Server:     https://kubernetes.default.svc
      Source:
        Chart:  podinfo
        Helm:
          Release Name:   podinfo
        Repo URL:         oci://ghcr.io/stefanprodan/charts
        Target Revision:  *
    Status:               Synced
Events:
  Type    Reason              Age   From                           Message
  ----    ------              ----  ----                           -------
  Normal  ResourceUpdated     24m   argocd-application-controller  Updated sync status:  -> Synced
  Normal  ResourceUpdated     24m   argocd-application-controller  Updated health status:  -> Progressing
  Normal  OperationStarted    19m   argocd-server                  admin initiated sync to *
  Normal  OperationCompleted  19m   argocd-application-controller  Sync operation to  succeeded

It's because of Flux v2.2.x and the Helm apiVersion being implicitly promoted to v2beta2, which we haven't supported yet.
We'll update Flamingo to support them shortly.

Fixed in v0.8.2


get_logged_in_athlete_activities() fails with after set to slang dates e.g. last year

get_logged_in_athlete_activities() fails with after set to slang dates e.g. last year.
The problem is likely in wrong usage of maya parse and when methods.

Solved in e0407a798f71b64d55f899a54440679d64945289


[TSI] not configure SNI if it looks like an IP address

IP addressed are not allowed as host names. So we want to ignore the given server_name_indication when it looks like an IP.

What I am not sure is if this would introduce any performance concern since we are examining the char array every time creating a client handshaker.

What I am not sure is if this would introduce any performance concern since we are examining the char array every time creating a client handshaker.

I think this should be fine, since the looks_like_ip_address function is just doing a linear pass of the target name, and target names are generally relatively short.

Also I see this comment on looks_like_ip - do we need to enhance this to generally handle all IPs?
https://github.com/grpc/grpc/blob/78825f79caec2a4a2d6afa952f7b9bad954ccb6f/src/core/tsi/ssl_transport_security.cc#L237-L239

Also I see this comment on looks_like_ip - do we need to enhance this to generally handle all IPs?
https://github.com/grpc/grpc/blob/78825f79caec2a4a2d6afa952f7b9bad954ccb6f/src/core/tsi/ssl_transport_security.cc#L237-L239

If I didn't miss any edge cases, anything that looks_like_ip returns true for is definitely NOT a valid host name, even if it's not an IP. So we should be good for now. A more rigorous check doesn't seem cheap to me.


bluepill-build-test-for-ios 0.3.0

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Bump -- can this get a merge please?

@godrei Please merge the PR.

Thanks 😀


chore: upgrade to go 1.20

Upgrades to go 1.20.0 for this go module as well as for all builds.
Related to #196

/gcbrun

/gcbrun


Adding awesome-flask

No thanks. It doesn't look maintained anymore. I'd rather give the opportunity to someone that actually cares ;)


[KBM] Support the dual key remap to have different remaps depending on whether another key is pressed together

Summary of the Pull Request
This pull request implements the dual key remap functionality in Keyboard Manager.
What is this about:
The dual key remap allows a single key assigned to different keys depending on whether the key is pressed together with another key or alone. Some products already utilize it.

Space-and-Shift (a.k.a. SandS) to convert Space key to Shift key when other keys are pressed while pressing Space key. euxn23/win-sands-ahk and fiore57/SandSExe are some of those examples.
alt-ime-ahk to convert left / right Alt keys to IME off / on keys when Alt key is pressed alone.

In addition, #5679 has 8 upvotes as well as 6 duplicate issues. There are some demands on the feature worth being supported in Keyboard Manager, I believe.
What is included in the PR:
See also https://github.com/microsoft/PowerToys/issues/5679#issuecomment-1053542523 for the brief spec.

Add a combo box under the arrow symbol for each single key remap in Keyboard Manager Editor to choose one of either "Always", "Alone", and "In combination" (any suggestion on better names is welcome).
Show the remap condition label for each single key remap in Keyboard Settings PowerToys Settings page.
Rename State::GetSingleKeyRemap to State::GetSingleKeyRemapResult which now returns SingleKeyRemapResult having a list of key to handle the case where a dual-remapped key is being pressed.
Convert RemapBufferRow from a tuple to a standard struct with a new field condition.
Split MappingConfiguration::singleKeyReMap into alwaysSingleKeyRemapTable, aloneSingleKeyRemapTable, and combinationSingleKeyReMap tables for "Always", "Alone", and "In Combination" remaps, respectively.
Move EditorHelpers::IsValidShortcut to Shortcut.h for sharing it with KeyboardManagerEngineLibrary.
Pass std::vector<INPUT> instead of LPINPUT to SendVirtualInput because predicting the number of key events beforehand becomes more difficult and C-style arrays are difficult to handle safely.

How does someone test / validate:

[x] All existing test cases pass.
[x] "In Combination" remap works only when the key is pressed together with another key.
[x] "Alone" remap works only when the key is pressed alone.

Quality Checklist

[x] Linked issue: #5679
[x] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[x] Localization: All end user facing strings can be localized
[x] Docs: Added/updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)

[x] A CLA must be signed. If not, go over here and sign the CLA.

I'd say it's an expected behavior in edge cases. While I used standard keys (e.g. A) for (over-)simplifying my explanation, I expect most people to dual-map modifier keys only because we usually don't press a standard key together with other keys.

Ok. I thought so. Thanks for clarifying.

Please remember to ask for the next review after you think the requested changes have been pushed. Thank you.

@masaru-iritani when should we look at this again?

@stefansjfw @jaimecbernardo @crutkas
I didn't have enough time to consider and implement the way to indicate remap errors while allowing further edits. My current idea is to show a small error indicator on the array with the hover tooltip. I'm not sure if it is aligned with other PowerToys designs. Any suggesiton is welcome.

@masaru-iritani right now looks like a tooltip is thrown up.
here i did 1 against 1 and it reset the option that was last used.

@crutkas As you explained, the current design resets invalid remaps immediately. I believe we should allow remaps for the same key during editing while saving them should be blocked.

@masaru-iritani , is this ready for reviewing again?
I think it's gotten quite some conflicts since the last time.

@jaimecbernardo I'm sorry for the delay. Let me push my ongoing work and make this pull request draft until I find an appropriate and consistent design to allow tentative mapping errors.


ROIs reportlet showing intermediate result for ME-EPI

We introduced a regression with #2117, affecting all +20.x series.
Before:

After:

Just to be clear: for this to be fixed we need to roll back the plotting to the whole brain, unmasked.

@oesteban is this resolved? Latest run: https://15342-53175327-gh.circle-artifacts.com/0/tmp/ds210/derivatives/fmriprep/sub-02.html

Yes, I'm finding myself in the same situation. But I believe that the CI run you posted seems to be using the echo combination.


Add offset for picture.

My question is similar to https://github.com/SmartToolFactory/Compose-Cropper/issues/4 but I need to solve it by adjusting the offset for a picture, not by removing the offset of an overlay. Is this possible?
It might look something like this:

Any ideas or suggestions? I need it because I should implement functionality where user can crop vertical picture and they can put whole height or width of picture inside the crop area (if aspect ratio of picture not the same as crop area) but I should use static way for the crop border and dynamic picture under it.


Gurobi can not solve MIP model

Hi,
the appended MIP problem solves fine with the glpk or cplex interface but is declared infeasible when using the gurobi interface. Tested Gurobi version was 7.02.
Model in JSON (renamed to .txt for upload)

I found and fixed a few bugs in the gurobi interface. I can now optimize the model to the same value as cplex.

Thanks! :smile:


[RFC] Consolidate component theming into a one API (aka styleOverrides)

~As discussed in https://github.com/mui-org/material-ui/issues/28107#issuecomment-997368895, there are 2 current APIs that provide component theming.~
~- styleOverrides~
~- variants~
~A quick history of why there are 2 APIs: In v4, styleOverrides is not able to support dynamic props via callback due to the limitation of JSS. That's when we introduce another API (variants) to inject a specified style when a set of props is matched. However, it causes some confusion with the component variant prop (ex. #29455) and exposes new syntax but has limitations because it cannot create matching props like this (variant === 'filled' && color !== 'success').~
~If we step back, we will see that both of the APIs are trying to provide the same thing, component theming. Fortunately, in MUI v5, the styleOverrides supports callback thanks to emotion & styled-components so it is worth to drop variants and expose only one theming API.~
For history, @oliviertassinari explain in https://github.com/mui/material-ui/issues/30412#issuecomment-1018467855
Here are all the requirements that styleOverrides can/should support:

static style that target slots{
  MuiButton: {
    styleOverrides: {
      root: {
        background: 'linear-gradient(...)'
      },
      startIcon: {
        marginRight: 12,
      }
    }
  }
}

[new] dynamic style from props (in v4, we provide classes that can be used to target each prop){
  MuiButton: {
    styleOverrides: {
      // colorPrimary: { ... }, in v4 we do this
      // which can be translated into
      root: (props) => ({
        ...props.color === 'primary' && { ... }
      }),
      // other slots can be function as well
    }
  }
}

[new] support array syntax for using a lot of pseudo-class (or nested class), so that it does not override each other. (this is an existing feature that emotion & styled-components are already supported){
  MuiButton: {
    styleOverrides: {
      // root: props => ({
      //  '&:after: { display: 'block', color: 'red' },
      //  ...props.color === 'primary' && {
      //    '&:after: { color: 'blue' }, // this `display` in the upper :after is gone because this is object.
      //  }
      // }),
      root: [
        { '&:after: { display: 'block', color: 'red' } },
        props => ({
          ...props.color === 'primary' && {
            '&:after: { color: 'blue' }, // this `display` in the upper :after is still there.
          }
        })
      ]
    }
  }
}

[new] it can be used with the new experimental_sx utility!{
  MuiButton: {
    styleOverrides: {
      root: sx({
        p: 2,
        bgcolor: 'primary.main',
      }),
    }
  }
}

Deprecation

styleOverrides should contain only slot keys and deprecate all classes because those can be done by using callback. eg: for Button, the styleOverrides should beMuiButton: {
  styleOverrides: {
    root: {},
    startIcon: {},
    endIcon: {},
    // outlinedPrimary, outlinedSecondary, ..., sizeSmall, sizeLarge, ...etc. should be deprecated but still work in v5
  }
}

~variants should be deprecated.~ (We don't plan to deprecate variants at this moment)

Plan
I think it is possible to aim for NO breaking change, but some deprecations are expected. We can try to create codemod that helps migrate the deprecation.
✅ 1st PR https://github.com/mui-org/material-ui/pull/30524

make styleOverrides support callback (only for slot keys)
~deprecate variants themeing feature~ reverted
update docs about the callback support

2nd PR

deprecate non-slot class keys (only in theming styleOverrides)
create codemod for

migrate classes format in styleOverrides to callback
~migrate variants to styleOverrides callback~ (We don't plan to deprecate variants at this moment)

✅ 3rd PR

[optional] a blog post announcement

In the end, we can close #22259, #27415 and #28107
cc @mui-org/core

Agree with the API.
If we update the types for styleOverrides to support the functions and arrays, we could immediately unlock this API. After this, we could deprecate variants and the other class keys in favor of using the root and other slots keys in the styleOverrides.
Then, in v6 we can drop the other keys and provide codemod for each key in the components (this is the most important part). We want to make v6 easy for adoption after making that many breaking changes in v5.

Just because I was playing with the API intended to be deprecated the other day and for me to learn as well: if I only want to override styles of the small size variant, how would I do that, given that sizeSmall would be deprecated?

Just because I was playing with the API intended to be deprecated the other day and for me to learn as well: if I only want to override styles of the small size variant, how would I do that, given that sizeSmall would be deprecated?

You can look up the props via a callback.
{
  MuiButton: {
    styleOverrides: {
      root: (props) => ({
        ...props.size === 'small' && { ... }
      }),
    }
  }
}

Got it. Thanks, Jun! Must say though that just from a first glance perspective, it looks more complex than using the sizeSmall approach 😅

Hi, I didn't want to create a new issue without knowing if I am doing something wrong. The styleOverrides does not work.
@mnajdova
https://codesandbox.io/s/globalthemeoverride-material-demo-forked-srvfc?file=/demo.tsx
https://stackoverflow.com/questions/69577570/mui-v5-styleoverrides-not-working-with-themes
Am I doing something wrong?

Got it. Thanks, Jun! Must say though that just from a first glance perspective, it looks more complex than using the sizeSmall approach 😅

One reason might be the familiarity of the existing API (sizeSmall). It might be frustrating for some people at the beginning
because they have to change the way they used to do but I am pretty sure that we will have fewer issues in long term. Also, I believe that some people will love it (at least I am 😂).
sizeSmall approach is a NO-go for sure as far as I know. Take a look at chipClasses, there are around 20 classes that are incomplete and we can't create every possible combination of classes because we don't know who will use or not use them. So it is definitely better to let developers own the styling via callback.
I also wonder once we deprecated all the classes, how much bundle size will decrease.

Right, thanks for the explanation! I believe it's a great idea to add this reasoning to the documentation when explaining the changes :)

Hi, just a very happy MUI user with a quick clarifying question on this set of changes so we can plan our migration:
Is the ButtonPropsVariantOverrides interface going away as well, or will we still be able to define custom variants and style them using the new styleOverrides callback?
For example, will this continue to work (works now, in v5.3.0):
declare module '@mui/material/Button' {
  interface ButtonPropsVariantOverrides {
    customVariant: true;
  }
}

const theme = createTheme({
  MuiButton: {
    styleOverrides: {
      root: ({ ownerState }) => ({
        ...ownerState.variant === 'customVariant' && { ... }
      }),
    }
  }
});

Is the ButtonPropsVariantOverrides interface going away as well, or will we still be able to define custom variants and style them using the new styleOverrides callback?

No worries, the ButtonPropsVariantOverrides interface still works as-is. Once you augment the interface, you will be able to see it in the ownerState as well! That's one of the main goals of having style overrides as callback!.

A quick history of why there are 2 APIs

@siriwatknp From my perspective, this is not the reality of what happened. It was not about JSS. The introduction of the variant API: #15573, #21749. But I also realize that these issues don't cover the point I'm going to detail: static definition. #21648 might be the most insightful on the different options that we considered.
From my perspective, the key selling point of the variant API is that the resolution is deterministic. In practice, the variant API allows:

Empower low-code design tools to build a design system in a Figma-like interface. This is the path that Modulz is pushing, and why they have a variant API in stitches https://stitches.dev/docs/variants
Empower smarter TypeScript resolution, with no efforts: https://github.com/mui-org/material-ui/issues/19466#issuecomment-821900112
It might empower static extraction, or at least caching to improve performance: https://vanilla-extract.style/documentation/recipes-api/.
It might force an API on the developers to more clearly organize their styles, hopefully making it easier to maintain, when the styleOverrides is for more niche use cases of customizations.

On point 2. see the feedback about TypeScript in https://engineering.udacity.com/choosing-the-right-component-library-for-your-design-system-mui-vs-chakra-45c4c949d150.

@mhespenh a quick question. 😅
What would be the type in this situation which I can provide to typescript?

@oliviertassinari You mentioned vanilla-extract, does it mean that at some point in the future, MUI is considering to let developers to replace built-into mui emotion with plain CSS.
To be transparent, while asking this, I don't think the replacement is even possible not mentioning the effort, but I'm just in hopes MUI team considers to have styles without a runtime (plain css for better performance).

vanilla-extract seems to result in best performance, while keeping satisfactory DX

You mentioned vanilla-extract, does it mean that at some point in the future, MUI is considering to let developers to replace built-into mui emotion with plain CSS?
To be transparent, while asking this, I don't think the replacement is even possible not mentioning the effort, but I'm just in hopes MUI team considers to have styles without a runtime (plain css for better performance).
vanilla-extract seems to result in best performance, while keeping satisfactory DX

We initially envisioned being able to create a wrapper for any CSS in JS solution, like the ones we have for emotion & styled components, @mui/styled-engine and @mui/styled-engine-sc. At MUI, we don't plan at this moment adding support for more CSS in JS solutions, but if the community wants to give a try by creating a new standalone packages for some other styling solutions, it would be interesting for us to see if the abstractions work :)

As I understand it, moving forward with this plan would solve #38544 for free, and help a bit with performance. Each styled component wouldn't need to resolve all the theme.components.NAME.styleOverrides values.

Would it make sense to extend the variants theming feature towards a more similar approach as styleOverrides ? To me it feels like the variants theming feature is missing a lot .
It would be awesome to have something like that:
// ...
MuiCard: {
  variants: [
    {
      props: { variant: 'newOne' },
      styleOverrides: {
        // ...
      }
  ]
}
// ...

What is also a bit confusing to me is the fact, that we do not get the scoped theme in the current variants style function. Therefore we have to use something like that:
// ...
MuiCard: {
  variants: [
    {
      props: { variant: 'newOne' },
      style: ({ theme }) => {
        return {
          color: theme[THEME_ID].palette.secondary.main,
        };
      }
  ]
}
// ...

I would like to open the discussion again since we added variants to styled API to support both emotion and zero runtime.
This makes the theme.variants unnecessary because users can specify variants inside each slot's styleOverrides. The benefits I see are:

Consistent API. What users write with styled is the same as styleOverrides which lets the code to be moved between instance and theme.
Solve the slot issue #28107. The current theme.variants only supports the root slot (need to increase CSS specificity to override a slot which does not work well for theming components) but theme.styleOverrides can be targeted at any slot.
Since styled argument and theme.styleOverrides are the same, the code should be simpler and the types should be the same.

cc @mnajdova @brijeshb42

Here, then it also makes sense to move defaultProps inside each slot instead of being a top-level key.


Use nix derivation in CI

Currently CI seems to be failing due to the stack project not working without Nix set up. This pulls in Nix in CI and uses nix to run the build and test commands. Since Nix will handle downloading Stack, we no longer need to install it manually either.
I removed --copy-bins as well, since it doesn't seem to be necessary and seems to error for me locally when run using Nix.

Hi Sarah, thank you for your contribution. As you're probably aware, the Vaultenv source code is licensed as BSD-3-Clause. Should we merge your changes, they will be included under the same terms. Do you accept this?

Hi Sarah, thank you for your contribution. As you're probably aware, the Vaultenv source code is licensed as BSD-3-Clause. Should we merge your changes, they will be included under the same terms. Do you accept this?

Yes, I do.


Update manually-submit-port-order.md

Updated information to address things in a more efficient way for customers

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


splunkchi: Support github.com/go-chi/chi/v5

https://github.com/go-chi/chi released v5 some time ago which we should support.

We want to use v5 too. Please support it.

You can consider using https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and use its RouteTag option or https://pkg.go.dev/github.com/riandyrn/otelchi.
You can also take a look at https://github.com/open-telemetry/opentelemetry-go-contrib/pull/4017 for inspiration how otelhttp could be used with github.com/go-chi/chi/v5


chrome tab opens but instantly closes

Tried 12 | Line : 873 | Message: session not created: This version of ChromeDriver only supports Chrome version 86
Current browser version is 93.0.4577.82 with binary path C:\Users\mjajd\AppData\Local\Google\Chrome\Application\chrome.exe

Delete chromedriver.exe and patched_drivers folder from the project folder..then try again

that fixed it
thankewww


Pomodoro: Count the number of pomodoros

It would be great to see the timer (and also the reports) counting the number of Pomodoros not only the duration.

Could you please share more details. Do you means pomodoros for one day or how exactly and where would you like to see the number.

Sorry I just realised that I wrote this request in toggl button instead of Toggl desktop. Yes, I mean the number of Pomodoro tracked in one day. If the Pomodoro timer is activated, it would be great to see beside the tracked duration the  number of Pomodoros.
For example : Today 1 h 30 min             3 Pomodoros
In the web application it would be greate to see reports on the number of pomodoros per week or at least have an option to show the number of pomodoros beside the duration in the existing reports.
I suggested that because as a personne working with the Pomodoro technique, it is more significant (and encouraging to continu working) for me to see the number of pomodoros per day than the number of hours, especially that the number of hours counts also the break duration so it does not represent only the productive time.
Thank you.

Thank you for the detailed explanation.
We'll take this request under consideration when planning our next developments.

Would be really great if it was able to work similar as http://pomelloapp.com/ which I've been using. That it logs number of pomodoro for a day / task but also storing the number of pomodoros on Trello cards really helps with estimations overview etc.

would be great to have this feature. I think it adds much value towards being accountable to the goals.


Change component generation workflow to normalize with other adapters

Current Behavior

Currently the component-generator workflow is stale and fails.
Desired Behavior

Use the same workflow as other adapters and generate components by running the adapter.
Implementation

Acceptance Tests

Mockups

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@gr455  will you be able to knock this one out? https://github.com/meshery/meshery-istio/blob/master/.github/workflows/component-generator.yaml Use this as reference

@gr455 will you be able to knock this one out? https://github.com/meshery/meshery-istio/blob/master/.github/workflows/component-generator.yaml Use this as reference

Yep

@Revolyssup The component generator workflows for both of the service meshes (Istio and Nginx-SM) look the same
https://github.com/meshery/meshery-nginx-sm/blob/master/.github/workflows/update-oam-defs.yml
https://github.com/meshery/meshery-istio/blob/master/.github/workflows/component-generator.yaml

@Revolyssup The component generator workflows for both of the service meshes (Istio and Nginx-SM) look the same https://github.com/meshery/meshery-nginx-sm/blob/master/.github/workflows/update-oam-defs.yml https://github.com/meshery/meshery-istio/blob/master/.github/workflows/component-generator.yaml

Hmm, I must have been mistaken then. I think we can close this issue.


Add mem_nr and email to participant-list

closes #3723
closes #3732

sort email: Sorting is not alphabetical

The sort seperates between has Email and has no Email.
The internal sortings from these blocks (has Email/ has no Email) is not alphabetical, the internal sorting is dependent on the previous sortings from them.
This behaviour is the norm in every other sorting list


Embedding @manipulate commands?

If have a case with two parameters, e.g.:
@manipulate for k=1:100,j=1:100
    g=myfunction(k)  # expensive function that depends only on k
    f=anotherfunction(g,j)    # cheap function that reuses g
end

It would be nice to have the j slider responsive, even when the k slider is less so.  So I'd want to do something like:
@manipulate for k=1:100
    g=myfunction(k)  # expensive function that depends only on k
    @manipulate for j=1:100
        f=anotherfunction(g,j)    # cheap function that reuses g
    end
end

Is this possible?

Or rather, I should say, the code I used is not working so is there an alternative that does?

I think this is what you want:
k = slider(1:100; label="k")
j = slider(1:100; label="j")
g = map(myfunction, signal(k)) # g is a signal whose value is myfunction(k)
f = map(anotherfunction, signal(g), signal(j)) # f is a signal whose value is anotherfunction(g,j)
map(display, [k,j]) #display widgets
map(display, [g,f]) #display results (that will update when you move the sliders);

unfortunately that didn't work for me.

Oh, can you provide a code snippet, error message, or explain in more detail what didn't work?
This works for me:
using Interact

myfunction(k) = begin
    zeros(Int(1e9)) #takes a few secs on my machine
    2k
end
anotherfunction(g,j) = g*j
k = slider(1:100; label="k")
j = slider(1:100; label="j")
g = map(myfunction, signal(k)) # g is a signal whose value is myfunction(k)
f = map(anotherfunction, g, signal(j)) # f is a signal whose value is anotherfunction(g,j)
map(display, [k,j]) #display widgets
map(display, [g,f]) #display results;

As in, after moving slider j, f updates quickly, but if I move slider k, the results take a few secs to update.

Hmm, your example works for me but the following doesn't (this is a simplification, the actual case would replace f(0.1,0.2) with a plot):
k = slider(-100.:.1:100.; label="k")
x₀ = slider(-2.:0.1:2.; label="x₀")
y₀ = slider(-2.:0.1:2.; label="y₀")

QR = map(k->qrfact([B;Δ+k*I]), signal(k))
f = map((x0,y0)->((x,y)->exp(-(x-x0)^2-(y-y0)^2)), signal(x₀), signal(y₀))
p = map(f->f(0.1,0.2),signal(f))

map(display, [k,x₀,y₀]) #display widgets
map(display, p) #display results;

Change the last line to display(p) or map(display, [p])

Ah, I see, I was confusing map for signals with map for lists.  Thanks!
FYI Here's my code that plots the solution to Helmholtz, where the it's fast for moving x_0 and y_0:
``julia
using ApproxFun, Interact, Plots
plotly()
d=Interval()^2
B=Dirichlet(d)
Δ=Laplacian(d)
k = slider(-100.:.1:100.; label="k")
x₀ = slider(-2.:0.1:2.; label="x₀")
y₀ = slider(-2.:0.1:2.; label="y₀")
QR = map(k->qrfact([B;Δ+k*I]),signal(k))
f = map((x0,y0)->Fun((x,y)->exp(-(x-x0)^2-(y-y0)^2)), signal(x₀), signal(y₀))
u = map((QR,f)->linsolve(QR,[0.0;f];tolerance=1E-4),QR,f)
map(display, [k,x₀,y₀]) #display widgets
display(map(contour,u)) #display results;

Nice. Yep, easily confused.
Btw was curious to run your example but I get UndefVarError: Dirichlet not defined

Pkg.checkout(“ApproxFun”,”development”)

On 4 Nov. 2016, at 3:22 pm, Joel Mason<EMAIL_ADDRESS>wrote:
Nice. Yep, easily confused.
Btw was curious to run your example but I get UndefVarError: Dirichlet not defined
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/JuliaLang/Interact.jl/issues/114#issuecomment-258342037, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLDqf5hPJbtBV0I2gHghvyPSyhq-Yifks5q6rL8gaJpZM4Kgtl9.

Nice, cheers.


Add action-pushbullet

Allow users to send notifications via Pushbullet to their devices

@ShaunLWM thanks for adding this!


Create SSO "login" option

Part of https://aptible.atlassian.net/browse/DP-199
Allow the user to store a given token for later use to enable SSO
"logins" via the CLI. The SSO login process involves redirects that must
be done in a browser. Therefore, the way to allow users in SSO enforced
organizations to use the CLI is to provide a way for them to copy a
token from their browser (where they complete their SSO login) and store
it via the CLI for use.
The command is `aptible login --sso token'. If no token is provided, the
user will be prompted for one.
This persisted token will overwrite their existing one. Therefore, they
will need to issue aptible login again to access other orgs beyond the
one the SSO "organization" token is valid for.

Sorry, I just realized i never changed the reviewer on this one! It's ready to go now that we deployed the UI changes that pair with this.
We may want to hold on this until we're ready to announce SSO in some form though.


[FEATURE REQUEST] Move some features of Relm4 to gtk-rs

Relm4 and gtk-rs share the goal to make GUI development with GTK on Rust as convenient as possible. Over time, Relm4 has gained features that might be useful for gtk-rs users too. Therefore, I thought it would be nice to write down a list of features that don't depend on Relm4 and could be moved to gtk-rs.
Of course, this is just a suggestion and you can decide which features are suitable to be included and how they should be included.
Features

Type-safe actions: example and implementation
Menu macro to create menus conveniently, together with type-safe actions: example
Multithreaded async runtime based on glib (not published yet)
view! macro to initialize widgets conveniently (even without the relm4 crate)

Extension traits

WidgetPlus: convenience methods that extend WidgetExt
RelmIterChildrenExt: Iterate over the children of widgets
RelmContainerExt: A re-implementation of ContainerExt for suitable widgets
RelmSetChildExt: container_set_child method
RelmRemoveExt: container_remove method

Type-safe actions: example and implementation
Menu macro to create menus conveniently, together with type-safe actions: example
Multithreaded async runtime based on glib (not published yet)

Especially those sound very useful to me

Multithreaded async runtime based on glib (not published yet)

I think that should be a separate crate as that gets away from bindings quite a bit. Sounds interesting though. I assume that's juggling lots of main contexts and then schedules tasks between them in some way?

Yes, I planned to create a crate called "glib_async_executor" for this. Indeed, it's just a bunch of main contexts and a flume channel in a nutshell. It doesn't have outstanding latencies but works quite well otherwise. I think I will publish my local code very soon.

I have more questions about that but let's discuss that in a separate issue or PR once the code is there :)

I've posted the code of the runtime here. It still needs quite a bit of polish but the core features are implemented.

As long as it stays that small I guess we can put it behind a feature flag into the glib crate, but I'm not entirely sure what the use case of this is. How are you using it? :)
Also you probably want to implement the various executor traits from the futures crate and provide the various functions that other runtimes have like block_on, spawn_local, etc.

Relm4 allows you to run background tasks in your components (like commands in Elm), for example for HTTP requests or CPU intensive tasks. So far, this has been handled by tokio, but we want to allow users to choose other runtimes: https://github.com/Relm4/Relm4/issues/114

Apart from of the async runtime discussions, what features are you interested in?

The others are all quite GTK specific so I'm the wrong person to ask. For me they all sound quite interesting though

Any opinions @bilelmoussaoui?
Or something to ask for feedback in the matrix room?

Regarding the extensions traits, all of them except RelmIterChildrenExt should be suggested as APIs upstream but most of them were removed in gtk3 due to reasons like the removal of GtkContainer API. For type safe actions, there is already a PR for that in gtk-rs-core, maybe helping finishing that one would be great & see if there are things that could be added to it.
The menu! & view! macros looks interesting though. Do you mind sharing some examples how they work or a link to their source code?

For type safe actions, there is already a PR for that in gtk-rs-core, maybe helping finishing that one would be great & see if there are things that could be added to it.

One small note here, if possible I think it would be nice if Relm4 and the bindings would end up with the same API in the end.

Regarding the extensions traits, all of them except RelmIterChildrenExt should be suggested as APIs upstream

We don't have a GTK dev in our team and although I know C and can understand most of GTK's source code, some guidance would be appreciated. Also, this is not just an extension of GTK's widgets, but is implemented for some types from libadwaita and libpanel too.

The menu! & view! macros looks interesting though. Do you mind sharing some examples how they work or a link to their source code?

Docs with examples including the macro expansion and the source code:

view: docs, code
menu: docs, code

The view! macro itself doesn't need any Relm4-specific features, but I should note that it supports additional features in certain contexts (for example combined with the #[component] attribute macro) that only work together with Relm4. Entirely separating those features into another crate does not make sense because a lot of code is shared, but those features could be put behind a feature flag.
The menu! macro is a lot simpler in comparison and does not depend on anything else but the type safe actions implementation of Relm4. I hope we can work together on a type safe actions implementation. Honestly, I'm not entirely sure which PR in gtk-rs-core you were referring to.

We don't have a GTK dev in our team and although I know C and can understand most of GTK's source code, some guidance would be appreciated. Also, this is not just an extension of GTK's widgets, but is implemented for some types from libadwaita and libpanel too.

Opening an issue with API suggestions and seeing how the upstream gtk developers want to go forward is a good idea. The implementation part is a different story but I definitely don't want the bindings to try and fix the original API. gtkmm did that and it ended up in a very bad shape.

I'm not entirely sure which PR in gtk-rs-core you were referring to.

https://github.com/gtk-rs/gtk-rs-core/pull/67

https://github.com/gtk-rs/gtk-rs-core/pull/67

Maybe we should discuss this separately, but I think this PR is doing something very different for a different use-case. It seems to target use-cases in combination with UI templates, whereas the approach from Relm4 is more lightweight and less opinionated (but rather targets UIs built with Rust code). Naturally, UI templates that use GTK builder can't transport any type information. However, the implementation in Relm4 is explicitly type safe: you can't accidentally pass an action with the wrong signature nor misspell the action name.


"You tried to stop a wad that never played" is unecessary

I stop all my Wads so that only the desired one plays, and this log info is spamming my console.
I don't find this info of any value and think it should be removed.

I just updated the logging system in the latest version of Wad.js. Now, you'll need to manually enable logging by increasing the verbosity of Wad.js: Wad.logs.verbosity = 1.
By default, the latest version of Wad.js will print nothing to your console.
Thanks for using Wad.js and raising this issue.


L515 cannot be detected by the Laptop

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ L515 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 16/20) / MacOS

Kernel Version (Linux Only)
5.4.0-107-generic

Platform
PC

SDK Version
{2.49 }

Language
{python }

Segment
{others }

Issue Description
<Describe your issue / question / feature request / etc..>
L515 performs differently on three different platforms.

It works well on my desktop. The system is ubuntu 20.04. It can work with USB 3.1 mode.
It cannot be detected on my Macbook now. It worked well 2 months ago. It suddenly couldn't work after one night before. The device cannot be detected by the system report. I have tried another 2 Macbooks. They can find the Intel device in the system report.
It cannot be detected on my Linux laptop. The system is ubuntu 16.04. I tried different USBs to connect to the laptop. The original USB cannot be detected for most trials but it happened to be recognized once as the USB 2.0 mode.  lsusb cannot detect the camera.

Hi @sunwell1994   If your L515 camera can function on an Ubuntu desktop and two Macbooks but not one other Macbook and an Ubuntu laptop then it sounds as though the camera hardware and its firmware driver are okay and it may be an issue with the USB ports or operating system on those two particular computers that it is not detected on.
As a starting point in investigating this case, please try unplugging the micro-sized end of the USB cable from the base of the L515, turning the connector around the other way and re-inserting it into the base of the camera (USB Type-C cables are two way insertion at the micro-sized end).  Does this resolve the problem, please?
In regard to the Macbook with the problem, which MacOS version is it using please?   If it has been upgraded to Monterey then there have been USB problems with RealSense camera detection that have only recently been solved by an installation guide at https://lightbuzz.com/realsense-macos/

please try unplugging the micro-sized end of the USB cable from the base of the L515, turning the connector around the other way and re-inserting it into the base of the camera (USB Type-C cables are two way insertion at the micro-sized end). Does this resolve the problem, please?
It does not make L515 work.

In regard to the Macbook with the problem, which MacOS version is it using please? If it has been upgraded to Monterey then there have been USB problems with RealSense camera detection on that MacOS version that have only recently been solved by an installation guide at https://lightbuzz.com/realsense-macos/
All systems are Monterey. But 2 Macs can detect the Intel device by USB while the other one cannot find it at all.

Has the camera ever worked on the 16.04 laptop or has it only just started being undetected on that PC overnight like with the one Macbook?

Has the camera ever worked on the 16.04 laptop or has it only just started being undetected on that PC overnight like with the one Macbook?

Thanks for your reply. It has never worked on the Ubuntu 16.04 laptop.

If lsusb cannot detect the camera on the 16.04 machine then it seems unlikely that it is a problem related to the librealsense SDK.
You could test whether it is a conflict with the Linux kernel by building the SDK from source code with the libuvc backend method at the link below.  This build method is not dependent on Linux versions or kernel versions and does not require patching.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

If lsusb cannot detect the camera on the 16.04 machine then it seems unlikely that it is a problem related to the librealsense SDK.
You could test whether it is a conflict with the Linux kernel by building the SDK from source code with the libuvc backend method at the link below. This build method is not dependent on Linux versions or kernel versions and does not require patching.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

I agree that the issue may not be related to the librealsense SDK. The laptop should detect the realsense device as Intel Corp at the USB port even without the SDK.
I also tried the link but some downloads  cannot complete in the shell file.

Does detection of the camera on the 16.04 machine change if you reload the udev device handling rules with the instruction below:
sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/99-realsense-libusb.rules && sudo udevadm control --reload-rules && udevadm trigger

It did not work as well.

There are a small number of cases where a camera may work normally on one machine but never work on another and the exact reason why is never able to be found.  The Ubuntu 16.04 machine may fall into this category of unsolveable problems.  As the libuvc backend build failed despite its installation script having been originally designed for 16.04, this suggests that there may be a hidden issue with the computer (such as a glitch in the USB system) that is unrelated to librealsense.
The Macbook problem is unusual, since the camera worked normally until a particular day and it works with the other two Macbooks.  In 'it worked fine until today' cases, I would tend to suspect that an update may have been installed on the operating system of that particular computer that conflicted with the camera.

Hi @sunwell1994  Do you require further assistance with this case, please?  Thanks!


recursive download

Feature request: support recursive download, i.e. download Favicons for sites in nested folders.
Stated another way, download icons for entries when "Download Favicons" is selected on a folder containing their parent folders.

This is easy to do, but I'm not sure how to distinguish both options (one level or nested).
Maybe two items on the context menu or one setting on the tools menu? Any suggestion on that?
I think I'm almost three months behind on the "error report" that I promised.
I started messing with a mail server and the thing is much harder than I expected, but I still have plans for YAFD.

Is the one-level option sometimes still preferable/useful if the recursive
method were available? If not, you could just change the behavior. If so...
IDK that I have a preference of two options in the context menu vs. a
behavior selector in settings/options for the one option in the context
menu.
Another option would be settings/options to show one, the other, or both in
the context menu. (I think I'm partial to that, actually.)
If a "default behavior" makes sense in the context of whatever UI you
choose, IMO recursive should be the default.

Ugh, GitHub removed my line breaks. I can't login right now to correct it.
I hope the above still makes sense.

Just to know, did you enable the "Show Entries of Subgroups" in the "View" menu?

did you enable the "Show Entries of Subgroups" in the "View" menu?

No.

This is a great idea. If someone wants it just one level deep they can temporarily move the subfolders they don't want parsed, run the plugin and then move the subfolders back. I think most people would be very happy with just a means to do a recursive sweep.


Upgrade PHPUnit

Upgrade tests to use real namespaces and unlock the phpunit version

@tmatsuo Rebased and fixed the class name for the new tests just added in the last 2 PRs


pretrained model weights

Is it possible to release the pretrained model weights?
Particularly, looking for the Anonymization and Auxiliary Privacy model weights.
This would be super helpful. Thanks!
could you please confirm if you're loading actually pretrained weights from the First phase i.e., the Training of the anonymization function in L396 and L398?
https://github.com/DAVEISHAN/SPAct/blob/main/anonymization_training/train_ssl_minimax2.py
#L396
ft_model =  load_r3d_classifier(saved_model_file= '/home/c3-0/ishan/privacy_preserving1/ucf101_with_unetrecon/saved_models_and_logs/model_50_bestAcc_0.6262.pth')
#L398
fb_model = ssl_privacy_load(saved_model_file = '/home/c3-0/ishan/privacy_preserving1/vispr_with_unetreocon/saved_models/SSL_unet_recon/model_160.pth')

did you get the weights or train the model yourself yet by any chance?

Pl find the initializations points and anonymization model from our follow-up work: TeD-SPAD.


feat: eleventy plugin metagen

added eleventy-plugin-metagen
&& cleaned up some data related errors

we keep making edits at the same time,
i see that you're messing around with the eleventy-plugin-vue too


Use registered schema in Next.js validation

What happened?
I changed a fresh Next.js started clone in a way that should (as far as I understand) clearly trigger a schema validation error but I didn't get any error from npm run dev or npm run build. I expected the build to fail both using the dev and the build script.
To reproduce

Clone the Next.js starter project and install dependencies using npm install
Modify the callout tag to only allow paragraphs as children

export const callout = {
   render: Callout,
   description: 'Display the enclosed content in a callout box',
-  children: ['paragraph', 'tag', 'list'],
+  children: ['paragraph'],
   attributes: {
     title: {
       type: String,

Start the development server with npm run dev and open the page in a browser
Nest two callout tags on a page (which should be disallowed)

{% callout %}
{% callout %}
This is a full-featured boilerplate for a creating a documentation website using Markdoc and Next.js.
{% /callout %}
{% /callout %}

The page refreshes with the nested callout tags and no error is shown

You can also add a validation function that always fails to the definition of callout which appears to have no effect either.
import {Callout} from '../../components';

export const callout = {
  render: Callout,
  description: 'Display the enclosed content in a callout box',
  children: ['paragraph', 'tag', 'list'],
  attributes: {
    title: {
      type: String,
      description: 'The title displayed at the top of the callout',
    },
  },
  validate(node, config) {
    return [
      {
        id: "my-error",
        level: 'critical',
        message: "This should fail",
      }
    ]
  },
};

All of this also applies to nodes.
Version
0.1.4
Additional context
The exact commit of the starter repository used is cf36368f405a41499aded8b61b136c0bda44c0e3.

@symmb I'm changing this issue from a bug report to an enhancement, since this is currently working as intended.
We just need to include the correct config here: https://github.com/markdoc/next.js/blob/main/src/loader.js#L68.
Previously, I had not included the config there because then it needs to be imported in 2 places, though at this point, I think that is worth it.
(Cc @matv-stripe)


Knowledge - .doc files are reported as not supported.

Steps to reproduce the problem:

Create an agent with local knowledge files with extension .doc
Ingestion of these files fail with following error

failed to convert file: unsupported file type "ws://acorn.io/ - Website Terms and Conditions template 07-28-2023.doc"

Expected Behavior:
We should be able to support .doc file type.

Able to ingest .doc files successfully with latest build.


Incompatible test libraries, mockito-all and Junit 4.11+

Execute the following test somewhere in the engine-tests project to reproduce:
    @Test
    public void test() {
        org.junit.Assert.assertThat(42, org.hamcrest.CoreMatchers.is(43));
    }

Instead of
java.lang.AssertionError:
Expected: is <43>
     but: was <42>
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)

I am getting
java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V

The issue seems to be in the dependencies of the test project:
    compile group: 'junit', name: 'junit', version: '4.12'
    compile group: 'org.mockito', name: 'mockito-all', version: '1.10.19'
    compile group: 'org.jboss.shrinkwrap', name: 'shrinkwrap-depchain-java7', version: '1.1.3'

The problem here is, that mockito-all bundles hamcrest 1.1 but junit has a transitive dependency to hamcrest 1.3. The IDE picks up the hamcrest version from junit but the tests get executed with the one from mockito which is not compatible to junit 4.11+ See also [1] and [2].
It would be interesting to know if this is an Eclipse-only problem and maybe can be fixed with a workspace change or if it also affects our IntelliJ developers.
A possible solution would be to import hamcrest at first, e.g. like
    compile group: 'org.hamcrest', name: 'hamcrest-core', version: '1.3'
    compile group: 'junit', name: 'junit', version: '4.12'
    compile group: 'org.mockito', name: 'mockito-all', version: '1.10.19'
    compile group: 'org.jboss.shrinkwrap', name: 'shrinkwrap-depchain-java7', version: '1.1.3'

but we may also consider to move away from mockito-all and use mockito-core instead, maybe even in the latest version 2.2 which has some improvements like better java 8 support, e.g. mocking default method. [3]
[1] https://tedvinke.wordpress.com/2013/12/17/mixing-junit-hamcrest-and-mockito-explaining-nosuchmethoderror/
[2] http://stackoverflow.com/questions/15833015/nosuchmethoderror-with-hamcrest-1-3-junit-4-11
[3] https://github.com/mockito/mockito/wiki/What's-new-in-Mockito-2

Left a note on the PR that oddly I get different behavior in IntelliJ - but Jenkins appears to be fine.
Also curious to hear more IDE reports from anybody else able to test. @msteiger & @skaldarnar maybe? @vampcat?

I can verify that I get the same results - NoSuchMethod exception in IntelliJ.
That being said, @Cervator It is interesting to note that the problem I encountered with DestSol and guava was pretty much identical, with version mismatch leading to problems. Is there any way to prevent inclusion of old versions of library in gradle, if a newer one is already present?

compile("project") { exclude module: "dependency"} I believe this is how gradle deals with such things. At least it's what I've used in projects

This issue was moved to Wafflemon/Frothleikr#5


Bump pulumify version

error: --yes must be passed in to proceed when running in non-interactive mode

🤦 Oops, forgot we have to explicitly pass --yes now in Pulumi 2.0.
PR to do that in pulumify: https://github.com/pulumi/actions-pulumify/pull/16

It looks like there's an edge case bug in pulumify: if pulumify had previously created a stack, but failed to update, subsequent runs of pulumify will attempt to run pulumi config refresh -f (since the stack exists), but this will fail because there is no previous deployment.
+ PULUMI_STACK_NAME=pulumi/pulumify-pulumi-docs-justin-pulumify-upgrade
+ echo '# PR stack name: pulumi/pulumify-pulumi-docs-justin-pulumify-upgrade'
+ pulumi stack select pulumi/pulumify-pulumi-docs-justin-pulumify-upgrade
# PR stack name: pulumi/pulumify-pulumi-docs-justin-pulumify-upgrade
+ PULUMI_STACK_EXISTS=0
+ '[' 0 -eq 0 ']'
+ pulumi config refresh -f
error: no previous deployment

I'm just going to close this PR and open a new one with a different branch to work around the issue.


Can't find pop.h

I'm having trouble finding pop.h inside of JOTextField.h. Any help

You have to use cocoapods and install pod framework as dependency from there.

What is the name i search for because i can't find it


Explorer has no "search bar" on mobile

Unlike the on desktop, the Stacks Explorer on mobile does not have a search bar.
Not sure if it's a bug, or a feature request. Let you guys decide.

closed by #938


Don't alert for Macie being an s3 exfiller

Add macie.amazonaws.com to excepted principals from the s3 exfil rule.

Resolved in #578


[flutter_tools] allow filtering of adb logcat by "flutter" to be configured from CLI args

ADB logcat logs are very verbose, so we filter it by lines that contain the pattern 'flutter'. We should make this configurable via a command-line flag, so that developers who want to debug the full logs can see this. This would also be leveraged by editor plugins, since--for example--Android Studio provides a UI for viewing full logcat logs in a natively launched application.
cc @jacob314

If the volume of traffic is high, there may be value in allowing it to be stopped/started while the app is running (via a message to the flutter run daemon, or over the a VM Service extension).
This could allow the user to start the log, perform some action in the app, then stop the log, rather than having to wade through large amounts of logging.

Some logcat lines don't contain the string flutter (unless that part of the line has already been suppressed):
D/EGL_emulation( 4571): app_time_stats: avg=39.67ms min=0.97ms max=650.57ms count=26

This debug line in particular really pollutes the log.
The prefix gives the log level: D/ is debug, W/ is warning, E/ is error. So in addition to the proposal of enabling or disabling the filter for logcat lines containing flutter, I suggest also allowing the user to set a minimum loglevel.

Any news on this? It really makes it impossible to work with my terminal.

Fwiw, I looked into this briefly today.

ADB logcat logs are very verbose, so we filter it by lines that contain the pattern 'flutter'.

... is not totally true - there are two branches:

Current app process (i.e. your flutter app): virtually no filtering
Another process (i.e. another app, possibly Flutter): filtering based on things like flutter

The vast majority of so-called log-spam (e.g. D/EGL_emulation) are in the current process ID, meaning its not filtered.
I am very supportive to adding much more liberal adb logcat filtering, similar to what we did in the engine:
https://github.com/flutter/engine/blob/main/testing/scenario_app/bin/utils/adb_logcat_filtering.dart
... however that is a potentially larger change. If the tool team is supportive of more aggressive Android filtering, I'd be happy to contribute here; removing triaged-tool to get an opinion before moving forward.

yes filtering is safe and personally when developing I would prefer to see level filtering and the exclusion of anything out of process without and opt in. If I want to see what is happening in android more broadly I should use adb the flutter tools should help me debug my app.

Thanks Reid! I think this is something we should move forward with at some point.


ci: datapath-verifier: also run on 6.6 kernel

6.6 is the latest longterm-stable kernel, give it the usual coverage in CI.
Use the 6.1 complexity configs for now, until we depend on any 6.6-specific kernel capabilities.

/test


[pfe-button]: color context design spec

Description of the issue
The pfe-button component does not switch colors when the parent has a color-palette of "darker" or "darkest".  This is in contrast to the guidelines on Red Hat UX's site and we will want to revisit whether or not this is expected behavior for the patternfly elements button components.

As per our discussion we do not think that we need to mimic the Red Hat design doc completely but want to make sure that what is there is the expected behavior.

#1976 partially addresses this, but we need some design direction. When that PR is merged, let's rename this issue to [pfe-button]: color context design spec or some such
cc @markcaron

See also #1997  and #2014