clasp-common-lisp: 2.2.0 -> 2.6.0

Description of changes
Same flags as in from debian/arch builds are used (mixed bytecode mode).
This release bundles dependencies that were previously fetched from their git repositories. It means that the repo-pinning code can be deleted.
Clasp needs ASDF with changes not yet merged to the canonical repository. Such a patch was added to the asdf derivation to avoid adding conditionals in the lisp builder.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

@ofborg build clasp-common-lisp.pkgs.jzon

In my use it seems on par with ECL performance. But I don't know how to measure it more properly.


rebuild_avatars scripts references deprecated NoArgsCommand

ImportError: cannot import name NoArgsCommand
https://github.com/django-extensions/django-extensions/issues/808

Hey @bctiemann. This issue was fixed in #141. It hasn't been deployed to PyPI yet. I'll try to get to that soon. In the meantime, install the dependency from GitHub if you need to run that command now.

Got it—thanks!

On Jan 6, 2017, at 11:05 AM, Grant McConnaughey<EMAIL_ADDRESS>wrote:
Hey @bctiemann https://github.com/bctiemann. This issue was fixed in #141 https://github.com/grantmcconnaughey/django-avatar/pull/141. It hasn't been deployed to PyPI yet. I'll try to get to that soon. In the meantime, install the dependency from GitHub if you need to run that command now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/grantmcconnaughey/django-avatar/issues/142#issuecomment-270936415, or mute the thread https://github.com/notifications/unsubscribe-auth/AE4GlbFejhVSE-SW6gBIuBwEor_Lph31ks5rPmZQgaJpZM4Lc2Jp.

Has this fix been deployed yet? When I do a pip install I still get the bug, but I can see the fix on github.
Cheers


LR and loss

You are better than me, I tried a similar and it worked very bad.
I would love to learn from yours.
What LR did you use?
What loss vs epoch did you get?

Hi @johngrabner  you can look at the colab link.


I want Jupiter expanded function to multiple environment setting

Can we simplify settings such as venv, which is almost always used? For example, it could be set automatically in the directory.
Improvement of GUI... Before that, stability is required.
If a bug in the extension makes the notebook unusable
It is not efficient.
run a all notebook proccessing with the extension
The process itself seems wrong to me.

@narukisosu I'm sorry but I don't quite understand the issue.
Please could you provide some screehshots of what needs to be improved and we can go from there.

closing for lack of activity


Merge two locon

I have two LoCon files trained on same hyperparameters (full preset, lora, same network and conv  dim/alpha's), is there a way to merge these model weights (like 0.5 0.5)? I can merge standard lora's but lycoris giving me error. A code snippet would be enough if not implemented easier way not available...
Thanks in advance.

you can just merge their state dict
(match key name, merge the param, and then save)

Thanks for quick reply @KohakuBlueleaf
I am seeing some parameters like this when looking thought keys:

'lora_unet_up_blocks_1_attentions_1_proj_in.alpha'

I should keep these alpha params as original when I merge two models right? (especially when I merge sth like this: model1 * 0.8 + model2 * 0.6)
Is there any other params like this?

Thanks for quick reply @KohakuBlueleaf
I am seeing some parameters like this when looking thought keys:

'lora_unet_up_blocks_1_attentions_1_proj_in.alpha'

I should keep these alpha params as original when I merge two models right? (especially when I merge sth like this: model1 * 0.8 + model2 * 0.6)
Is there any other params like this?

You should also merge them actually.


The saved date and the edit page date do not match.

Laravel Version: #.#.#
PHP Version:
Laravel-admin: #.#.#
we saved date it check the edit page that is not match.

Description:
$grid->column('calling_reminder', __('Calling Reminder'))->display(function ($date) {
return date('d-m-Y', strtotime($date));
}); this is the code for grid.. this code get the date value is correct.
$form->date('calling_reminder', __('Calling Reminder'))->format('DD-MM-YYYY');
     model
     public function setCallingReminderAttribute($value)
{
    // Parse the input date and format it as 'Ymd'
    $this->attributes['calling_reminder'] = \Carbon\Carbon::createFromFormat('d-m-Y', $value)->format('Y-m-d');
}
we click the edit page then show the date is not correct.

Steps To Reproduce:

i added this, but can not work


Provide csrf for MFA

I was trying out the authentication path with 2FA enabled. I was getting a 403 when hitting the /mfa/verify endpoint, even though I was providing all of transaction_id, factor_id, and passcode.
But then I looked at the requests on chrome, and noticed that an additionall (and different) _csrf field is provided in the request. This is a different one obtained from the hidden inputs from the earlier request, and is rather returned - and should be extracted - from hitting /authorize. (It's the same response that you have to check whether there is a passcode field inside of it).
Thought I would share this so the documentation can get updated.

Can you make a PR?

@timdorr Done, let me know if there is any specific format you'd like the community to follow for PRs.


PowerShell doesn't understand unsigned numbers

Steps to reproduce
Description: I can't make powershell use correctly types like [uint32] or [uint64].  The bug seems to be that PS doesn't realize that is has to upcast 0xffffffff to int64 and not to int32, as it won't fit.
PS C:> [uint32]$b=0xffffffff
Cannot convert value "-1" to type "System.UInt32". Error: "Value was either too large or too small for a UInt32."
PS C:> $b=[uint32]0xffffffff
Cannot convert value "-1" to type "System.UInt32". Error: "Value was either too large or too small for a UInt32."
PS C:> $b=[uint64]0x1ffffffff
<so this works, because powershell realizes that 1ffffffff doesn't fit into 31 bit>
PS C:> $b=[uint64]0xffffffff
Cannot convert value "-1" to type "System.UInt64". Error: "Value was either too large or too small for a UInt64."
Expected behavior
PS C:\ > [uint32]$b = 0xffffffff
PS C:\ > $b
4294967295
Actual behavior
PS C:> [uint32]$b = 0xffffffff
Cannot convert value "-1" to type "System.UInt32". Error: "Value was either too large or too small for a UInt32."
At line:1 char:1

[uint32]$b = 0xffffffff

  + CategoryInfo          : MetadataError: (:) [], ArgumentTransformationMetadataException
  + FullyQualifiedErrorId : RuntimeException

Environment data

> $PSVersionTable
PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.15050.0
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15050.0
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

By default PowerShell convert to signed values. Workaround:
[uint32]"0xffffffff"

I am aware of the workaround. It tends to breakdown when you move away from the simple repro steps I added here, and try to use expressions, pass parameters to functions or scripts, or use in classes. It basically forces me to not only pay attention to unwanted conversions to [int], but also add convert back and forth to [string] into the mix.
Any other language I know knows to upcast numbers to the next type that fits. If the given value does not fit in an int32, PowerShell should upcast it to [uint32]. Or to [int64], if it really wants to use signed.
Particularly for uint64 this makes no sense:
0x00000000 - 0x7fffffff works
0x80000000 - 0xffffffff throws
0x0000000100000000 - 0xffffffffffffffff works again
For consistency, I would expect anything above 0x7fffffffffffffff to also throw, because the signed [int64] cannot take it. But here PowerShell knows to silently convert to [uint64]. Why doesn't it know the same for 0x80000000?

I suppose the "0x" prefix to be enough to correct the behavior.

PowerShell arithmetic is complicated with all of the implicit type conversions, implicit widening, etc. We decided not to include unsigned in V1 because it would have made the algorithm significantly more complicated (this was probably a mistake). Anyway, as an alternate workaround, you can use the 'l' long suffix to force 64 bit integers in your constants as in:
[uint32]$b = 0xffffffffl
which works as you'd expect.

We would carry out the necessary cast at parse time in the case of the following notation:
$var = [uint32] 123
$var = [decimal] 123
...

Thank you both for the suggestions!
My example uses constants because I wanted to simplify the repro. For the real project I read an uint64 value from a binary file. The value is a bit field of 64 flags and I want to translate them to strings. Like 0x9 would translate to ("alpha", "delta") where alpha=0x1 and delta=0x8, for example.
Because of this issue I'm complaining about, writing the script is unnecessarily complicated. I spent more time trying to fix it than to actually write it.
(Thanks for the tip with the 'l' suffix - I didn't know it. I checked and there is a 'd' suffix as well, for decimal.)

I don't agree that we should convert negative numbers to unsigned values via a simple cast - we can't infer intent from values:
0xffffffff, -1 | % { [uint64]$_ }

Despite the syntax, PowerShell doesn't have the notion of an explicit conversion - all conversions are implicit. So in that sense, allowing this conversion with this syntax would be unsafe.
Even if we allowed the conversion from a i32 to u64, I don't think it would behave how you want - it would sign extend before changing types - this is how languages like C or Rust work.
If your code is reading a file, I would suggest using something like [System.BitConverter]::ToUInt64($bytes, 0).
If you have fewer bytes in the file than the ultimate type, you can use ToUint32 and that will properly zero-extend to u64 without any complaints from PowerShell.

I'm not sure how this addresses my problem. I don't want to use signed. I don't need signed. I would gladly use unsigned all the way. Except, as you say, powershell does things under the covers, like converting to [int], whether I like it or not, and outside of my control.
When I say [uint32] $b = 0xffffffff it's pretty clear to me that I mean to use [uint32]. If I wanted signed I would have said $b = -1.
I don't know about Rust, but in C/C++ when I say UINT64 c = 0xffffffff the result is 0x00000000ffffffff and not 0xffffffffffffffff, or an exception thrown.
To give another example where powershell gets in the way with its obsession with [int]:
$a = @{};
$a.Add(0, 'Zero');
$a.Add(1, 'One')
$a[0]
Zero
[uint32] $b = 0
$a[$b]
Nothing
$a[[int]$b]
Zero
You may argue that this is by some sort of design - but you cannot argue that this is very error prone.
There used to be another bug, where switch($b) wouldn't match if $b was [byte] or [uint32] - only when $b was [int]. I don't see this repro-ing anymore, so I guess it was fixed.

Many years ago, I worked on C++ compilers, and I always felt hexadecimal literals should never be signed, so I agree with you.
In C++, a hex literal can be either an int or unsigned int depending on the value. I was never a fan of that design, but implicit conversions and the u suffix make it mostly not a big deal.
PowerShell is missing the u suffix and we need to be more cautious with conversions because they are so permissive and there is no distinction between implicit and explicit conversions.
If you're curious about Rust, here is a simple program:
fn main() {
    let val = 0xffffffff;
    let val2: u64 = val as u64;
    println!("{}", val2);
}

You can run it here: https://play.rust-lang.org/
The compiler issues a warning and prints out the sign extended value.
rustc 1.16.0 (30cf806ef 2017-03-10)
warning: literal out of range for i32, #[warn(overflowing_literals)] on by default
 --> <anon>:2:15
  |
2 |     let val = 0xffffffff;
  |               ^^^^^^^^^^

18446744073709551615

My point in bringing up Rust is that it is also a popular language and seems to have chosen consistency (always an i32) instead of sometimes unsigned. Again, I think it would be better to use an unsigned type for hex literals.
As for your hashtable example, I've seen people hit the same problem with strings instead of integers, and I've seen problems in C#, so it's more the unsafe nature of weakly typed keys of hashtable than anything else.

Like C++, C# also chooses int / Int64 or uint / UInt64  based on the value of a [hex] literal.
While the approaches differ - Rust sticks with int, but warns if the result would be a negative number - what these languages have in common is that they honor the fundamental user expectation that a [hex] literal specified without a sign result in a positive number.
By contrast, PowerShell's current behavior depends on whether the literal is decimal or hex:

With decimal literals, the expectation is honored: the type is chosen so that the value fits as a positive number into an - always signed - integer type, and the type chosen goes even beyond [int64], up to [decimal] and, ultimately, [double].

On a side note, I found the following discrepancy surprising<PHONE_NUMBER> is [int32]::MaxValue + 1):
(2147483648).GetType().Name yields Int64, as expected: the smallest signed type that can accommodate the value.
If you use an expression with the same value, the type instantly widens to [Double] rather than [Int64]:
(2147483647 + 1).GetType().Name yields Double.

With hexadecimal literals, the value is unexpectedly treated like a bit pattern: the  always signed target type is chosen based on whether it can accommodate all bits, even if the resulting number is negative.
That is, whenever the bit pattern happens to have the high bit set in the resulting data type, a negative number results.
Unlike with decimal literals,  [int64] is the largest type supported in this case.

Perhaps v6 is an opportunity to fix this problem, a change that probably falls into Bucket 3: Unlikely Grey Area.
As for how this can be done:

If hex literals are treated the same as decimal literals - always resulting in signed types - the range 0x8000000000000000 to 0xffffffffffffffff becomes unavailable, given that widening to [decimal] probably makes no sense for values that are presumed to be bit fields.

Perhaps hex literals could therefore truly be converted to unsigned types, assuming that PowerShell's type-conversion magic prevents any ill follow-on effects.

I presume that generally introducing an u suffix is a more problematic change in terms of backward compatibility.
@viorel-m-git

I would expect anything above 0x7fffffffffffffff to also throw, because the signed [int64] cannot take it. But here PowerShell knows to silently convert to [uint64].

I don't think that's happening : PowerShell never implicitly converts to [uint64].  Values between 0x8000000000000000 (0x7fffffffffffffff + 1)  and 0xffffffffffffffff are converted to [int64] (signed) and result in negative values (-9223372036854775808 and -1, respectively).

/cc @vexx32

Thanks for digging this up! I think... Yeah, I think I pretty much have covered all these cases in #7575.
High-bit hex numbers still get treated as negative, but you can specify the u suffix to parse them as large unsigned numbers.
However, that works only up to uint64, because there are no larger unsigned types to work with. I'm not sure how to deal with a sign bit there, to be honest, but I think at the moment I permit the signed bit for decimals to be used.
Whether that makes the most sense... I can't really say. It does progress to big integer after that if you attempt to go really high, but dealing with a sign bit in that range is essentially meaningless, really. I'm tempted to just have it parse all super large hex literals as always positive (which can then just be prefixed with a negative sign to invert them), but I'm not sure.

@PowerShell/powershell-committee reviewed this.  By default, all number literals are signed in PowerShell.  We would accept a proposal to introduce a u suffix to indicate unsigned numeric literals.

Here's another workaround.  This closed bug has a lot of google juice.
[uint32]('0x{0:X}' -f 0x80000000)


feature: add isNoEnsureStartsWithDot

增加开关可以用于控制 是否需要 StartsWithDot （./）

Pull Request Test Coverage Report for Build 35

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 98.413%

Totals

Change from base Build 33:
0.9%

Covered Lines:
80

Relevant Lines:
80

💛  - Coveralls

Pull Request Test Coverage Report for Build 35

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 98.413%

Totals

Change from base Build 33:
0.9%

Covered Lines:
80

Relevant Lines:
80

💛  - Coveralls

AppVeyor build failed:
EPERM: operation not permitted, open 'C:\projects\wxml-loader\test\src\index.wxml'

Ref to https://github.com/Cap32/wxml-loader/issues/10


Implementation of Issues in Github without pandas structure

Before this commit, the implementation for metrics about issues didn't
exist without using the pandas structure. This commit adds the structure
of issues in Github using just plain Python.
After this pull request, other pull requests will come to implement the following metrics :

Issue New
Issue Closed
Issue Age
Issue Resolution Duration

Signed-off-by: Xavier Bol<EMAIL_ADDRESS>

@xavierbol: thanks for the patch. I'll get back to you in a few days.

@xavierbol: An limitation to keep in mind when implementing Issue metrics with Perceval (especially the reopen_as_new parameter) is that Perceval does not fetch event data. About half a year ago, we had a discussion on this. Fetching issue data is very inefficient, and though a patch to address this was created, it was ultimately not merged. Thus, it isn't currently possible to implement issue metrics in their entirety.
The issue implementations which are already on the master branch were pushed before the events data fetch patch was discarded.
So lets keep this on hold.
The discussion can be found here:
https://github.com/chaoss/grimoirelab-perceval/issues/563
https://github.com/chaoss/grimoirelab-perceval/pull/565

@Polaris000: Ok, interesting. Thanks for this information !

@xavierbol: if you want, you could send the CommitByTag patch for CodeChangesLines. WDYT?

@Polaris000: I can but I need the CommitByTag class implemented in the other pull request. I think it's better to send this after the pull request about CodeChanges metric will be merged.

Ah, my bad. We can carry on once this is merged.

I think the principle purpose of the code examples in this work group is to illustrate examples of how to apply the definitions using the logic of code. So, limitations of Perceval, for example, is not a significant issue for what we are trying to accomplish.

@sgoggins, thanks for your input. Since the reopen_as_new parameter won't work without Perceval fetching the right data, we can either completely scrap the parameter, making it inconsistent with metric definitions or (and I'm leaning towards this) we could disable the parameter and add a note regarding this issue while keeping the code.
@xavierbol, have a look at my review. Meanwhile, I'll add the note to the README.

@sgoggins: I understand the principal purpose of the code examples in this working group. My goal in this PR, it's to add a structure of Issue in GitHub similar to the existing implementation using pandas structure. And then, I'll add code examples for the different metrics about Issues.
Because currently, there aren't code examples for issues in plain python and also no code examples for some metrics about issue, for instance, Issue_Resolution_Duration metric.

@Polaris000: Thanks for your review ! I have made the changes, I hope it's good for you.

LGTM!

@jgbarah : What are your thoughts on merging this?


Fix markdown

Violates markdown style rules on the polkadot-sdk

Done in https://github.com/Snowfork/snowbridge/pull/1106


Incorrect width of children when using align baseline and child in row as reference

Report

[x] I have searched existing issues and this is not a duplicate

Issues and Steps to Reproduce
In the following test:
https://github.com/facebook/yoga/blob/31b6c0ddc91d2f071f4ec7650dd7e2bfed657b14/tests/YGAlignBaselineTest.cpp#L418
The expected left position of root_child1_child1 is 500px while it should be 250px:
https://github.com/facebook/yoga/blob/31b6c0ddc91d2f071f4ec7650dd7e2bfed657b14/tests/YGAlignBaselineTest.cpp#L453-L454
Because its parent's (root_child1) width is 500px with flexDirection: row and 2 children of width 500px each:
https://github.com/facebook/yoga/blob/31b6c0ddc91d2f071f4ec7650dd7e2bfed657b14/tests/YGAlignBaselineTest.cpp#L428-L437
Since the parent's width is only 500px, both children can only take 250px to remain within the bounds of the parent element. This is exactly how Firefox & Chrome layout this combination in this HTML:
<!DOCTYPE html>

    <title>align baseline test</title>

Note: you'll have to use the DevTools to find the width of root_child1_child0 and root_child1_child1 but it is 250px each.
Expected Behavior
The width of root_child1_child0 and root_child1_child1 should be 250px each.
Actual Behavior
The width of root_child1_child0 and root_child1_child1 is 500px each and overflows the parent.
Link to Code
Here's a fiddle: https://jsfiddle.net/0pLaox48/

hi, can I work on this?

Yes please feel free to debug the logic in "CalculateLayout.cpp" for laying out a box with baseline alignment.


[Quick Question] using my existing certificates to be accessed internally only

Great project! thank you for your efforts!
Currently, I run bunch of services on my home network such as plex, sonarr etc. etc.
I can get everything setup without any problems!
Previously, I used to run nginx reverse-proxy and setup an internal rule of:
allow 192.168.X.0/24;
deny all;

by doing that, I was still able to access lets say plex.example.com and the site will be accessible if I was home
but if I do this using your access lists the site wouldn't be accessible unless I put in my public IP address.
Is there a way I could access plex.example.com with letsencrypt certs but only when I am home and not on public network?
thanks

I do this and for the most part seems to work fine.
I have an internal dns server that points at NPM internally for each of my proxy hosts. And I also have 80 And 443 port forwarded from external with an external DNS pointing my proxy hosts to my external IP.
Then my allow lists are setup for the proxy hosts that I only want to access internally.
I'm able to generate and maintain a certificate this way despite being used internally only.


Feature Request: Check for nonce?

I would like to be able to include a nonce in the canonical string for added security.  Would you be in favor of adding this feature?
If not, do you have any suggestions for a workaround?  In my use case, I think I could put a nonce in the request body and Content-MD5.  Is this reasonable?

The use of a nonce doesn't add a new layer of defense, but it doesn't fortify the system again replay attacks.  The option is a nice-to-have in my case, but I could imagine some projects with stricter requirements to use a nonce.  If you agree, we could chat about implementation and I'd be happy to try out an implementation.


FocusSelf causes everything to be focused

This PR fixes bugs when using React 18+ by ensuring that a useEffect call in useFocusable only happens on mount (#8).

We're running into this issue as well with react 18, it'd be awesome to have it fixed. Thanks for looking into it @willbarkoff!

Hello! I have made similar changes and it's already available in the v1.1.0: https://github.com/NoriginMedia/Norigin-Spatial-Navigation/releases/tag/v1.1.0
I have used a bit different useEffectOnce hook that also accounts for the unmount cleanup effects:
https://blog.ag-grid.com/avoiding-react-18-double-mount/

Thanks for the contribution anyways! I have also applied the TS fixes, somehow it got missed during the "build" command and got published like this. ESLint didn't detect them either 🤷


aligning variable name

tiny review

@ElakkiyaMohanRajan i still have some testing to do before we merge, but feel free to review and provide feedback in the meantime


Library should support SignIn and SignOut

I have an app where I want to allow unauthenticated requests, but want to redirect to EasyAuth for certain pages or flows. It would be nice if this library had the simple code required to enable that.
There are other AuthenticationHandler base classes that support this: https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.authentication.signinauthenticationhandler-1?view=aspnetcore-8.0
I believe it should be as simple as:

Make EasyAuthAuthenticationHandler.cs inherit from SignInAuthenticationHandler instead of the base AuthenticationHandler
Add implementations for HandleSignIn and HandleSignOut that simply redirect the user to /.auth/login/aad or /.auth/logout, depending on the flow.

Then users of this library could simply call HttpContext.SignInAsync()/HttpContext.SignOutAsync() as desired.

UPDATE:
I was able to make it work with the following, indicating this approach would work here:
// Program.cs
builder.Serivces.AddAuthorization();
builder.Services.AddEasyAuth(
    o =>
    {
        o.ForwardChallenge = o.ForwardSignOut = "MyEasyAuth";
    })
    .AddScheme<EasyAuthOptions, EasyAuthSignOutAuthenticationHandler>("MyEasyAuth", _ => { });

// EasyAuthSignOutAuthenticationHandler.cs
public class EasyAuthSignOutAuthenticationHandler : SignOutAuthenticationHandler<EasyAuthOptions>
{
    public EasyAuthSignOutAuthenticationHandler(
        IOptionsMonitor<EasyAuthOptions> options,
        ILoggerFactory logger,
        UrlEncoder encoder)
        : base(options, logger, encoder)
    {
    }

    protected override Task<AuthenticateResult> HandleAuthenticateAsync()
        => Task.FromResult(AuthenticateResult.NoResult());

    protected override Task HandleChallengeAsync(AuthenticationProperties properties)
    {
        Response.Redirect($"/.auth/login/aad?post_login_redirect_uri={Request.GetEncodedPathAndQuery()}");
        return Task.CompletedTask;
    }

    protected override Task HandleSignOutAsync(AuthenticationProperties? properties)
    {
        Response.Redirect("/.auth/logout");
        return Task.CompletedTask;
    }
}


[$250]  First QAB missing tooltip for new user

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.57-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ishpaul777
Slack conversation (hyperlinked to channel name): Expensify-bugs
Action Performed:
Sign up with new account
Open FAB, complete scan receipt flow
Open FAB again
Expected Result:
you see a QAB with tooltip
Actual Result:
you see a QAB without tooltip
Workaround:
unknown

this is the tooltip that should be visible ^

Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
https://github.com/user-attachments/assets/2ce97674-a251-4918-a6d0-d20ab2935310
Expected tooltip:

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021853953365086766977
Upwork Job ID:<PHONE_NUMBER>086766977
Last Price Increase: 2024-11-06

Issue OwnerCurrent Issue Owner: @rayane-djouah

Proposal
Please re-state the problem that we are trying to solve in this issue.
The QAB toolltip doesn't show for new user.
What is the root cause of that problem?
This happens after https://github.com/Expensify/App/pull/49682 where we prevent the tooltip to show in a modal. The issue that they are trying to solve is that the tooltip doesn't hide when we open a modal (or RHP).
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L26
But using that condition means that the tooltip isn't allowed to show in a modal.
What changes do you think we should make in order to solve the problem?

Because we want to close the tooltip when a modal will show, we need to change the logic a bit. What we should do instead is, if a modal is previously not shown, but now is visible, then close the tooltip. We can do that inside this onyx subscription.
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L32-L41
let prevModal: Modal;
const unsubscribeOnyxModal = onyxSubscribe({
    key: ONYXKEYS.MODAL,
    callback: (modal) => {
        if (modal === undefined) {
            return;
        }
        if (!prevModal) {
            prevModal = modal;
        } else if ((!prevModal.willAlertModalBecomeVisible && modal.willAlertModalBecomeVisible) || (!prevModal.isVisible && modal.isVisible)) {
            clearTimeout(showTimer.current);
            clearTimeout(autoCloseTimer.current);
            closeTooltip();
        }
    },
});

// If we want to replace above with useOnxy hooks (we use the above logic so it will re-render based on modal only when visible)
// const [modal] = useOnyx(ONYXKEYS.MODAL);
// const prevModal = usePrevious(modal)
// useEffect(() => {
//     if ((!prevModal?.willAlertModalBecomeVisible && modal?.willAlertModalBecomeVisible) || (!prevModal?.isVisible && modal?.isVisible)) {
//         clearTimeout(showTimer.current);
//         clearTimeout(autoCloseTimer.current);
//         closeTooltip();
//     }
// }, [modal, prevModal, closeTooltip]);

And when we close the tooltip, we need to make sure we cancel both the timeout of show and auto close/dismiss.
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L79-L85
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L93-L99
That's why we need to store it on a ref so we can use it later. Then, we can remove this shouldShow and this logic.
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L26
https://github.com/Expensify/App/blob/10454f06334ae3d07d4a28a81c5c79f3d2112c53/src/components/Tooltip/EducationalTooltip/BaseEducationalTooltip.tsx#L73-L77
Also, replaces all shouldShow with shouldRender back.

@ishpaul777 can you provide more details plz?

Sign up with new account

Which do you select here?

Open FAB, complete scan receipt flow
Submit expense or track?

Thx

Was able to reproduce

Video
https://github.com/user-attachments/assets/6e8a67bc-2da1-4a06-9002-168999e0476c

@sakluger , I'm off the next week, can you please keep an eye on this issue til I'm back? Thx

@rayane-djouah could you please check the two proposals we got already to see if they would work? Thanks!

Hey @pecanoro, could you please check the recommended proposal?

Assigning @bernhardoj to the issue!

PR is ready
cc: @rayane-djouah

Thanks @rayane-djouah
Test case created

https://github.com/Expensify/Expensify/issues/449650

Contributor: @bernhardoj due $250 via NewDot
Contributor+: @rayane-djouah paid $250 via Upwork.
Thanks!

Requested in ND.

$250 approved for @bernhardoj


[BUG] from_json ArrayIndexOutOfBoundsException in 24.02

Describe the bug
Calling from_json for json with nested structs can cause an ArrayIndexOutOfBoundsException if the provided schema for the nested struct has fewer fields than are present in the json.
Steps/Code to reproduce bug
Input file test.json
{ "x": { "a": 54321, "b": 1, "c": 2} }
{ "x": { "a": 54321, "b": 1, "c": 2} }
{ "x": { "a": 54321, "b": 1, "c": 2} }
{ "x": { "a": 54321, "b": 1, "c": 2} }

Test Setup
scala> import org.apache.spark.sql.types._

scala> val df = spark.read.text("test.json")

scala> df.write.parquet("test.parquet")

scala> val df = spark.read.parquet("test.parquet")

scala> val df2 = df.withColumn("mystruct", from_json(col("value"), new StructType(Array(StructField("x", new StructType(Array(StructField("a", DataTypes.IntegerType, false))))))))

scala> df2.show

CPU
+--------------------+---------+
|               value| mystruct|
+--------------------+---------+
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
+--------------------+---------+

GPU
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
  at org.apache.spark.sql.types.StructType.apply(StructType.scala:423)
  at com.nvidia.spark.rapids.GpuCast$.$anonfun$castStructToStruct$2(GpuCast.scala:1584)
  at com.nvidia.spark.rapids.GpuCast$.$anonfun$castStructToStruct$2$adapted(GpuCast.scala:1580)
  at scala.collection.immutable.Range.foreach(Range.scala:158)
  at com.nvidia.spark.rapids.GpuCast$.$anonfun$castStructToStruct$1(GpuCast.scala:1580)
  at com.nvidia.spark.rapids.Arm$.withResource(Arm.scala:66)
  at com.nvidia.spark.rapids.GpuCast$.castStructToStruct(GpuCast.scala:1579)
  at com.nvidia.spark.rapids.GpuCast$.doCast(GpuCast.scala:584)
  at org.apache.spark.sql.rapids.GpuJsonToStructs.$anonfun$doColumnar$7(GpuJsonToStructs.scala:227)

Cause
The following code uses index as an index into both from and to types and assumes that they are the same size.
  private def castStructToStruct(
      from: StructType,
      to: StructType,
      input: ColumnView,
      options: CastOptions): ColumnVector = {
    withResource(new ArrayBuffer[ColumnVector](from.length)) { childColumns =>
      from.indices.foreach { index =>
        childColumns += doCast(
          input.getChildColumnView(index),
          from(index).dataType,
          to(index).dataType, options)
      }

Expected behavior
Match Spark behavior
Environment details (please complete the following information)
Additional context

I could not reproduce the issue with latest from branch-24.04
scala> spark.conf.set("spark.rapids.sql.expression.JsonToStructs", true)

scala> df2.show
24/04/02 23:48:01 WARN GpuOverrides:
!Exec <CollectLimitExec> cannot run on GPU because the Exec CollectLimitExec has been disabled, and is disabled by default because Collect Limit replacement can be slower on the GPU, if huge number of rows in a batch it could help by limiting the number of rows transferred from GPU to CPU. Set spark.rapids.sql.exec.CollectLimitExec to true if you wish to enable it
  @Partitioning <SinglePartition$> could run on GPU
  *Exec <ProjectExec> will run on GPU
    *Expression <Alias> cast(from_json(StructField(x,StructType(StructField(a,IntegerType,false)),true), value#0, Some(UTC)) as string) AS mystruct#18 will run on GPU
      *Expression <Cast> cast(from_json(StructField(x,StructType(StructField(a,IntegerType,false)),true), value#0, Some(UTC)) as string) will run on GPU
        *Expression <JsonToStructs> from_json(StructField(x,StructType(StructField(a,IntegerType,false)),true), value#0, Some(UTC)) will run on GPU
    *Exec <FileSourceScanExec> will run on GPU

+--------------------+---------+
|               value| mystruct|
+--------------------+---------+
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
|{ "x": { "a": 543...|{{54321}}|
+--------------------+---------+

The test can pass only after this commit in 24.04. It looks like the commit fixed this issue.
There are some schema handling in the commit that might solve the indexing issue in castStructToStruct, but I don't have much context about from_json.

The issue still exists, at least in a few situations. The problem shows up when we ask CUDF to return data with a specific schema, but CUDF sees something that does not match the schema it expects and decides to return a struct or a list instead of an actual string.
https://github.com/rapidsai/cudf/issues/15278
Is the remaining case that I know causes something like this.

I also manually verified that this is working now for 24.04, once you turn on JsonToStructs. I think we can close this as there are other issues to track the remaining JSON work.


ViewlessStateProvider export missing

I wanted to use the ViewlessStateProvider but it looks like the export is missing from lib/state_view.dart

Thanks!!
Miss you hope the fam is good!

Ah, good catch! I'll update that!

This is resolved with #27. Update to v0.1.2 in order to get the fix.
Family is doing great!


add kotlinxSerialization JSON deseriallization

Thank you for submitting your Pull Request. Please make sure you have
familiarised yourself with the Contributing Guidelines
before continuing.
Description
Implement kotlinx-serialization JSON decoding
Type of change
Check all that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactoring (change which changes the current internal or external interface)
[ ] This change requires a documentation update

How Has This Been Tested?
In case you did not include tests describe why you and how you have verified the
changes, with instructions so we can reproduce. If you have added comprehensive
tests for your changes, you may ommit this section.
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation, if necessary
[ ] My changes generate no new compiler warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

i updated gradle and kotlin versions, now tests work flawlessly
one confusing bit is https://github.com/NikkyAI/Fuel/blob/c12d8f72882217bc1e17bb2f504e9affc2b08b51/fuel-kotlinx-serialization/src/test/kotlin/com/github/kittinunf/fuel/FuelKotlinxSerializationTest.kt#L151-L165
the same test works fine in jackson, although it should not.. parsing null into a non nullable field throws a exceptin in kotlinxSerialization
i am unsure how to handle that error case

Why should it not work? I see number: Int? which means it's nullable, right?

is codecov just very inaccurate with inline functions or how do i get that bad of a coverage report ?

@NikkyAI I have concerned about kotlinxDeserializerOf function that can be not inline.

PS: sorry for not filling out the PR template, creating a Pull request from within gitkraken seems to ignore that

https://github.com/kittinunf/Fuel/pull/450#issuecomment-427159659
cc @kittinunf @markGilchrist

I think this looks great to me! If you would be so kind, can you also add one section in the README to show how it works too? It can be the follow-up PR, though.

yeah well.. this works the same way as the jackson or gson feature does.. and i thought one section for serialization specifics is intended
i will think up some examples where a custom JSON instance or deserializer are passed in to showcase the full power


Don't use synchronous XHR

Chrome and Firefox are both warning me that the reference viewer is using synchronous XHR:

viewer.js:545 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience.

On the last call I mentioned that my copy of Chrome apparently "crashed" when I attempted to test the reference viewer.  Synchronous XHR is likely the culprit, because the main UI thread can hang for long periods of time waiting for network resources.  Even if this behavior was inherited from the previous reference viewer, it needs fixing.  On my local machine, a barrage of such requests cause some kind of deadlock for me, where CPU usage goes high and I can't close the browser tab.
There are two options:  Async XHR, and the Fetch API.  Fetch is newer and modern, but doesn't enjoy as widespread support as async XHR.
I'm fine with either, but we need to fix it to be asynchronous.

Fixed here https://github.com/KhronosGroup/glTF-WebGL-PBR/commit/de3b336e638de0555215016755625a69756bcb34


Update majority of tools for conda & automatic testing

This moves all tools that have conda packages available (or that don't have any dependency) under testing.
While I am at it, I also corrected a subset of flake8 issues, most notably we're avoiding from smRtools import *.
I took care that most tools keep conda and TS dependencies when possible.
Conda-only tools are now mismatch_frequencies , get_sra_info and the goseq tools, which I think I am the only user. These tools had dependency problems anyway.

Alright @drosofff, I think this is ready now.

testing does not work 27 days latter, with sqlite3.OperationalError

The sqlite errors are random hiccups with galaxy amd went away when testing again. That's why we use postgresql in production.
The other failure is a change in the fasta header returned by the NCBI, so that's out of our control. Testa are passing now :).

AH ok, very good, thanks 👍


HDDS-6120. Compute block checksum using chunk checksums

This PR depends on HDDS-6086.
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

Rebased the PR. Still need to add the tests suggested by Rakesh.

Thanks @rakeshadr for the review!


Blazor Transpiler issue with named Tuples

When Blazor attempts at transpiling the following lines of code into a RenderFragment it combines the tuple type and name which generates a type that does not exists.
		[Parameter] 		public Action<(ApiBase Sender, TResponse Response)> WhenSuccessful { get; set; }
Looking at the “razor.g.cs” file you will find the following transpiled code which is incorrect. Interestingly enough this happens to all, but the last parameter of the tuple.
        public static void CreateApi_1<TRequest, TResponse>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, TRequest __arg0, int __seq1, global::System.Net.Http.HttpMethod __arg1, int __seq2, global::System.String __arg2, int __seq3, global::System.Action<(global::ZoyaOpticalEHR.Common.Controls.Apis.ApiBaseSender, TResponse Response)> __arg3, int __seq4, TResponse __arg4, int __seq5, global::Microsoft.AspNetCore.Components.EventCallback<TResponse> __arg5, int __seq6, global::Microsoft.AspNetCore.Components.RenderFragment __arg6)
Notice in the generated code it combines the type and the name of the tuple property.
Using .Net 5.0, and the latest stable version of Visual Studio 2019 (Version 16.8.3)

Can confirm this still repro's for me. @jjonescz Could you take a look? The repro in https://github.com/dotnet/aspnetcore/issues/37209 is easy to reproduce it.


unresolved external symbol

I just copied the example code from the readme and I'm getting this error:
error: linking with `C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX64\x64\link.exe` failed: exit code: 1120
 = note: libhighlights-6d10d8ef55039a48.rlib(highlights-6d10d8ef55039a48.5ptoq1vovgegxtw.rcgu.o) : error LNK2019: unresolved external symbol tree_sitter_rust referenced in function _ZN10highlights11Highlighter3new17h5a2c4522f1121318E
          G:\syntax highlighting\rust\highlights\target\debug\deps\highlights-2195fc3ea40e8e40.exe : fatal error LNK1120: 1 unresolved externals

I'm assuming this is because I do not have the language installed, but there is no documentation on how to do so in rust. If there is a solution for this problem that would be greatly appreciated.

Yeah, that's a linker error. It's happening because you're not including tree_sitter_rust in your program. Tree-sitter parser libraries like tree_sitter_rust are written in C, so in order to use them in a rust program, you either need to either:

Compile them separately as dynamic libraries and then load them dynamically using something like rust-dlopen.
Link them into your rust program at build time.

Option 2 is easier; the README assumes that you're doing that. For some general information about including C files in a rust program, see the Build Scripts chapter of the Rust book.
More specifically, you're going to want to use The cc-rs crate to compile the C code as part of building your crate. In your build.rs file, you'll compile the two source files of tree_sitter_rust:
extern crate cc;

use std::path::PathBuf;

fn main() {
    let tree_sitter_rust: PathBuf = ["path", "to", "tree_sitter_rust", "src"].iter().collect();

    cc::Build::new()
        .include(&tree_sitter_rust)
        .file(tree_sitter_rust.join("parser.c"))
        .file(tree_sitter_rust.join("scanner.cc"))
        .compile("some_output_filename");
}

I fix this setting
$ export RUST_TREE_SITTER_TEST=true
Adding this src/main.rs
extern crate tree_sitter;
use tree_sitter::{Parser, Language};

fn main() {
  let mut parser = Parser::new();

  extern "C" { fn tree_sitter_rust() -> Language; }

  let language = unsafe { tree_sitter_rust() };
  parser.set_language(language).unwrap();

  let source_code = "fn test() {}";
  let tree = parser.parse_str(source_code, None).unwrap();
  let root_node = tree.root_node();

  println!("{}", source_code);
  println!("{}", root_node.to_sexp());
  assert_eq!(root_node.kind(), "source_file");
  assert_eq!(root_node.start_position().column, 0);
  assert_eq!(root_node.end_position().column, 12);
}

Notice the unwrap in let tree = parser.parse_str(source_code, None).unwrap();
and running:
$ cargo run


shareSingle: undefined is not an object

[exp] undefined is not an object (evaluating '_reactNative.NativeModules.RNShare.shareSingle')

node_modules/react-native-share/index.js:62:30 in
node_modules/promise/setimmediate/core.js:45:7 in tryCallTwo
node_modules/promise/setimmediate/core.js:200:23 in doResolve
node_modules/promise/setimmediate/core.js:66:12 in Promise
node_modules/react-native-share/index.js:61:25 in shareSingle

components/PreviewImage.js:72:58 in

node_modules/react-native/Libraries/Core/Timers/JSTimers.js:154:6 in _callTimer
node_modules/react-native/Libraries/Core/Timers/JSTimers.js:411:17 in callTimers
... 5 more stack frames from framework internals

Created question in stackoverflow as well https://stackoverflow.com/questions/49082623/react-native-share-promise-rejection-error

I am facing the same problem too, anyone with a solution? In my case it occurs only in Android.

undefined is not an object (evaluating '_reactNative.NativeModules.RNShare.shareSingle')
I am facing the same problem too. anyone with a solution?
Tried upgrading & downgrading the version but not succeed.
"react": "16.4.1",
"react-native": "0.55.4",
"react-native-share": "^1.1.1",

is happening on both android and ios?

@jgcmarins i haven't tried IOS yet.

Make sure you have import Share from 'react-native-share' instead of import {Share} from 'react-native-share'


Add workflow to upload documentation

This workflow is needed to test #740

Great! Closing this PR since the new modifications in https://github.com/huggingface/text-generation-inference/pull/740/files#diff-f05826b801b9407ec985196b30fc45b111e09b5d98ee8670333493868e2b8dad look good


Designcourse

Fixes Issue
Closes #351
Changes proposed
design course added
Screenshots

Note to reviewers
Give me progressive feedback

thank you Parma!

It's my pleasure 😀


vouch-proxy: init at 0.23.1

Initializes a package for vouch-proxy.  Its developers describe it as
"an SSO and OAuth / OIDC login solution for Nginx using the auth_request
module".
Upstream project is here: https://github.com/vouch/vouch-proxy.
Motivation for this change
https://github.com/NixOS/nixpkgs/issues/90728
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I don't have a lot of time to work on this, so I'm explicitly not stepping up to be a maintainer here.  I may not be very responsive to PR comments, either.  Apologies in advance.
Still, I figure this code drop is better than keeping the work to myself, and so here it is.  If someone else wants to take this PR and run with it, that would be much appreciated.  Feel free to remix the code as you see fit.

vouch-module.nix.txt
Related: I built a rudimentary NixOS module for vouch-proxy, too.  I don't recommend using it as is.  A better module would abstract away the details of vouch-proxy's YAML configs.  A much better module would provide more help in configuring nginx to work with it.
Once again, this is a code drop without promise or maintenance of improvement.  I'm sorry I couldn't offer more, and I hope it's better than nothing.

I don't have a lot of time to work on this, so I'm explicitly not stepping up to be a maintainer here. I may not be very responsive to PR comments, either. Apologies in advance.

We cannot accept new packages without maintainers.

Still, I figure this code drop is better than keeping the work to myself, and so here it is. If someone else wants to take this PR and run with it, that would be much appreciated. Feel free to remix the code as you see fit.

The package itself is very easy and anyone with a bit of nixpkgs experience could reproduce it in a minute. We might as well close this PR if you are not going to complete it.

Thanks for the review and clear explanation.
I would love to step up to be a maintainer, but that would be making promise I can't keep.
I'm fine with closing this.  I figured this starting point is slightly better than starting from zero, but I'll leave it up to the eventual maintainer to decide.
Thank you for all your hard work on nixpkgs.


Config string representation is interchangeable with that from file

As a lib User
I want to be able to transform a Config object into a properly-formatted string
So I can save it to disk and immediately use it with the AWS CLI tool

docs found here


[Bug]

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a theme

Describe the Bug
Small Grey box with nothing inside, no theme was a problem
Expected Behavior
Any fix? I have no idea how to fix this or the real problem
Steps To Reproduce
Error with theme's
Operating System
Windows
Anything else?
Fix I can get some help on how to fix this that will be amazing

It means you have no themes installed. https://docs.steambrew.app/users/getting-started#installing-themes

I have Theme's

Both Zip and file's and it still showing the grey box

Re-read the documentation, specifically at the bottom where there is a "NOTE"


Bug fix for count login accounts

Help from Roy

Thank you for the PR.
I apologize for the extremely slow response. We've changed our processes so this doesn't happen again.
Is this still an issue?


Add support for continue and break statements

#297 introduced the option to implement continue and break statements. This did not exist in hebi before since it did not support loops.
One possible implementation is to keep track of a respective call required to return to the closest loop beginning or end directly (i.e. call adjusted_next or while/for)

Bug bounty: 1000 ADA

@nielstron hey is the bug bounty still open? will have a attempt at this.

Hi @abhishek818, yes it's still open :)


feat(engine): enhanced query selection and improved performance

Closes #1798
Proposed Changes

Improved query selection mechanism
Added analyzer that goes through paths to determine which types of queries to use
Fixed malformed queries

I submit this contribution under the Apache-2.0 license.

I was thinking, is it possible to add a platform field on document? So we could check that on queries if needed...

Looks like a good idea to me

@joaoReigota1 this is awesome! "thanks"


Implement profiling output like generated by cachegrind in the witness generator

Will be discussed and implemented as part of https://github.com/powdr-org/powdr/issues/283


Add test scripts and increase code coverage

Codecov Report

Merging #128 (1799751) into master (054813b) will increase coverage by 0.54%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #128      +/-   ##
==========================================
+ Coverage   77.01%   77.55%   +0.54%
==========================================
  Files         117      117
  Lines       33489    33440      -49
==========================================
+ Hits        25791    25935     +144
+ Misses       7698     7505     -193

Impacted Files
Coverage Δ

dynadjust/dynadjust/dnaimport/dnainterop.cpp
75.91% <0.00%> (+5.35%)
:arrow_up:

dynadjust/dynadjust/dnaimport/dnainterop.hpp
100.00% <ø> (ø)

...st/dynadjust/dnaimportwrapper/dnaimportwrapper.cpp
82.79% <0.00%> (+0.08%)
:arrow_up:

dynadjust/include/config/dnaprojectfile.cpp
74.65% <0.00%> (+0.09%)
:arrow_up:

...djust/include/measurement_types/dnagpsbaseline.cpp
68.44% <0.00%> (+0.15%)
:arrow_up:

dynadjust/include/measurement_types/dnaheight.cpp
66.66% <0.00%> (+0.69%)
:arrow_up:

...just/include/measurement_types/dnadirectionset.cpp
61.85% <0.00%> (+0.74%)
:arrow_up:

...ynadjust/include/measurement_types/dnamsrtally.cpp
77.02% <0.00%> (+1.15%)
:arrow_up:

...ynadjust/include/measurement_types/dnagpspoint.hpp
85.41% <0.00%> (+2.08%)
:arrow_up:

Continue to review full report at Codecov.

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


fixed presentation issue

Two tiny changes in the readme.

Coverage remained the same at 65.947% when pulling 881c45ade423d99239111090127fa6fac878a433 on strayobject:master into 90fd48a58850ba37efe58e8f12515865b678ef93 on icicleio:master.


pull request for e2e test at 12/10/2016 04:56:03

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


Make relation between Packit and Testing Farm more clear

One set of questions we often get is related to Testing Farm: how Packit and Testing Farm are tied together. On top of that, users sometimes ask questions specific to the FMF format, test structure, best practices and tmt. We have @FrNecas on our team that often answers these. Sometimes we need to ask the Testing Farm team for replies.
TODO:

[ ] describe the relationship between Packit and TF
[ ] describe the flow of data and who owns what
[ ] point to best practices for organizing tests and running them in Testing Farm
[ ] link to TF's status page, their documentation, landing page and the way to reach the team

Closing since there was no activity in more than a year.


[DO_NOT_MERGE**] Gatekeeping changes

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the keep-helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

CLosing as the ccd definition upload is not getting reflected, new PR should resolve the issue.


Improve target framework support

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Is there any discussion of updating the package to support newer targets, preferably .NET Standard 2.0? I'd like to consider using Pulumi.Cloudflare, but all of the projects in my solution target .NET 8.

Hey @InteXX. Thanks for raising an issue. All our SDKs are generated, so I'm going to transfer this issue to the repo that does SDK generation.


Added type alias to support internal migration.

Fix to help land #7072. Demo of the fix can be found here: #7078

Decided on alternative path. Closing.


Server (Phoenix Channels) sending binary data to clients (Slipstream)

I'm trying to send some binary data from the server (Phoenix Channels) to the client, running Slipstream.
On the server side, this is something like:
AppWeb.Endpoint.broadcast!("channel", "topic", {:binary, binary_data})

which should invoke handle_message on SlipStream side.
Instead this seems to be invoking handle_info/2 with the following parameters:
#1 nil
#2 state

It looks like the client side stack trace is something like:
deps/slipstream/lib/slipstream.ex:83: ClientApp.Websocket.handle_info/2
lib/slipstream/callback.ex:34

On further investigation, discovered this seems to work for push/3 and not broadcast/3.

Could you give https://github.com/NFIBrokerage/slipstream/pull/61 a try? I believe all we're missing is a function clause to deserialize binary broadcast messages.

That seems to work now - thanks!

Thanks for checking! This is released now as v1.1.1


QuillEditor freezes when adding content or giving a spacebar

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
No response
Steps to reproduce
Tested on Edge, Chrome and Flutter WebApp version of the app
Step 1: Reference below code to create a form with single toolbar and multiple QuillEditor widgets.
Step 2: When I click on "+Add more details" button the first row is added. I click on the quilleditor, get the focus and I can type some content in it.
This is ok
Step 3: When I click on "+Add more details" again to add second row. I click on the second added QuillEditor, get the focus and can see the same content of first quilleditor (because first and second quill editors share the same quillcontroller).
I can see the print command of   print("add more pressed");
This is also ok
Step 4: But when I type a space button in the second QuillEditor, my whole application freezes. I cannot type in the second Quilleditor at all nor interact with any of my widget.
I checked in ver 9.3.6, 09.3.7, 9.3.8 all seem to have same issues. Some isse related to Quilleditor focus or edit exists and user is unable to type
Expected results

I should be able to type in the QuillEditor text when the focus is on without any issues.
I should be able to interact with my web app widgets

Actual results

Not able to any content in the second QuillEditor. Rarely I am able to type in second QuillEditor and add widgets (reproducible steps not identified for successful steps yet)
I am not able to interact with my web app widgets as the whole application freezes with no errors or exceptions

Code sample
Code sample
[Paste your code here]

Screenshots or Video
import 'package:admin/models/Resume.dart';
import 'package:flutter/material.dart';
import 'package:flutter_quill/flutter_quill.dart';
import 'package:provider/provider.dart';

class DynamicAdditionWidget extends StatefulWidget {
  const DynamicAdditionWidget({super.key});

  @override
  State<DynamicAdditionWidget> createState() => _DynamicAdditionWidgetState();
}

class _DynamicAdditionWidgetState extends State<DynamicAdditionWidget> {
  String sectionName = "Information";
  List<Widget> widgets = [];
  List<Widget> editorHeader = [];
  final List<QuillController> _quillControllers = [QuillController.basic()];
  ScrollController _scrollController = ScrollController();
  @override
  void initState() {
    super.initState();
    // TODO: implement initState
  }

  @override
  void didChangeDependencies() {
    // TODO: implement didChangeDependencies
    sectionName = Provider.of<Resume>(context).ActiveSection;
    editorHeader = [];
    editorHeader.add(
      HeaderWidget(
        quillControllers: _quillControllers,
        sectionName: sectionName,
      ),
    );
    super.didChangeDependencies();
  }

  @override
  Widget build(BuildContext context) {
    return Expanded(
      flex: 1,
      child: Container(
        decoration: BoxDecoration(
          border: Border.all(
            color: Color.fromARGB(255, 60, 67, 72), // Border color
            width: 1.0, // Border width
          ),
        ),
        child: Container(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.start,
            children: [
              ...editorHeader,
              Flexible(
                child: Scrollbar(
                  thumbVisibility: true,
                  controller: _scrollController,
                  child: ReorderableListView.builder(
                    onReorder: (oldIndex, newIndex) {
                      setState(() {
                        if (newIndex > oldIndex) {
                          newIndex = newIndex - 1;
                        }
                        final item = widgets.removeAt(oldIndex);
                        widgets.insert(newIndex, item);
                      });
                    },
                    scrollController: _scrollController,
                    itemCount: widgets.length,
                    itemBuilder: (context, index) {
                      return Column(
                        key: ValueKey(widgets[
                            index]), // Use a ValueKey to ensure correct reordering
                        children: [
                          Container(
                            padding: EdgeInsets.only(
                              left: 12,
                              top: 12,
                            ),
                            child: Row(
                              children: [
                                // Your content here
                                widgets[index],
                                Padding(
                                  padding: const EdgeInsets.only(top: 24.0),
                                  child: Column(
                                    mainAxisAlignment: MainAxisAlignment.end,
                                    children: [
                                      IconButton(
                                        icon: Icon(
                                          Icons.close_sharp,
                                          size: 15,
                                          color: const Color.fromARGB(
                                              255, 214, 95, 107),
                                        ),
                                        onPressed: () {
                                          setState(() {
                                            widgets.removeAt(index);
                                          });
                                        },
                                      ),
                                    ],
                                  ),
                                ),
                              ],
                            ),
                          ),
                        ],
                      );
                    },
                  ),
                ),
              ),
              Row(
                mainAxisAlignment: MainAxisAlignment.center,
                children: [
                  Expanded(
                    flex: 11,
                    child: Row(
                      mainAxisAlignment: MainAxisAlignment.end,
                      children: [
                        ElevatedButton(
                          child: Text(
                            "+ Add more details",
                            style: TextStyle(
                              color: Theme.of(context).primaryColor,
                            ),
                          ),
                          onPressed: () {
                            print("add more pressed");
                            setState(() {
                              widgets.add(
                                Expanded(
                                  child: Column(
                                    children: [
                                      Row(
                                        children: [
                                          Expanded(
                                            child: Container(
                                              decoration: BoxDecoration(
                                                border: Border.all(
                                                    color: Colors.grey[300]!),
                                                borderRadius:
                                                    BorderRadius.circular(2.0),
                                              ),
                                              child: QuillEditor.basic(
                                                configurations:
                                                    QuillEditorConfigurations(
                                                  placeholder:
                                                      "Compose your text here ...",
                                                  controller:
                                                      _quillControllers[0],
                                                  // autoFocus: true,
                                                  readOnly: false,
                                                  showCursor: true,
                                                  scrollable: true,
                                                  padding: EdgeInsets.symmetric(
                                                    vertical: 10.0,
                                                    horizontal: 8.0,
                                                  ),
                                                  sharedConfigurations:
                                                      const QuillSharedConfigurations(
                                                    locale: Locale('en'),
                                                  ),
                                                ),
                                              ),
                                            ),
                                          ),
                                        ],
                                      ),
                                    ],
                                  ),
                                ),
                              );
                            });
                          },
                        ),
                      ],
                    ),
                  ),
                  Expanded(
                    flex: 8,
                    child: Row(
                      mainAxisAlignment: MainAxisAlignment.end,
                      children: [
                        ElevatedButton(
                          onPressed: () {
                            // Add save functionality
                          },
                          child: Text("Save"),
                        ),
                        SizedBox(width: 8.0),
                        OutlinedButton(
                          onPressed: () {
                            // Add cancel functionality
                            _quillControllers[0].clear();
                          },
                          child: Text("Cancel"),
                        ),
                      ],
                    ),
                  ),
                ],
              )
            ],
          ),
        ),
      ),
    );
  }
}

class HeaderWidget extends StatelessWidget {
  const HeaderWidget({
    super.key,
    required List<QuillController> quillControllers,
    required this.sectionName,
  }) : _quillControllers = quillControllers;

  final List<QuillController> _quillControllers;
  final String sectionName;

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        Container(
          decoration: BoxDecoration(
            border: Border(
              top: BorderSide(
                color: Colors.grey[300]!,
                width: 1.0,
              ),
            ),
          ),
          child: QuillToolbar.simple(
            configurations: QuillSimpleToolbarConfigurations(
              // fontFamilyValues: ,
              controller: _quillControllers[0],
              showSmallButton: true,
              showCodeBlock: false,
              showSearchButton: false,
              showQuote: true,
              showAlignmentButtons: true,
              showHeaderStyle: true,
              toolbarSectionSpacing: .5,
              toolbarSize: .5,
              sharedConfigurations: const QuillSharedConfigurations(
                locale: Locale('en'),
              ),
            ),
          ),
        ),
        Container(
          width: double.maxFinite,
          padding: EdgeInsets.all(4),
          color: Colors.amber,
          child: Text(
            sectionName,
            style: TextStyle(
              fontSize: 18,
              fontWeight: FontWeight.bold,
            ),
          ),
        ),
      ],
    );
  }
}

Logs
Logs
[Paste your logs here]

Obsereve that in the second editor after the cursor nothing is typed or shown on screen. The whole application froze

It should not freeze.
Using _quillControllers to manage a 'list' of quill controllers is problematic, especially when you are only ever using the first element in the list. Calling widgets.add() and set state is pure evil, of course it won't work. In Flutter, manage values, don't manage widgets. Widgets should be managed by flutter's rendering engine 98% of the time, the other 2% are extremely hard to justify even at the expert level.
Encapsulate value of content of each section in something like a Section value object like Section{int index, String content, etc}, or just String if you only ever care about the content.
Then declares a PropertyValueNotifier<List> sections in your top level widget state, to hold the list of section values.
Design a widget SectionEditor which takes in a section and internally wrap a quill editor inside.
Let SectionEditor manage its own scroll controller, quillController, and focusNode and configuration (ie. declare those objects in its State as private fields).
What you want to have is probably a ValueNotifier<QuillController?> which sends notification to your HeaderWidget to rebuild itself upon active section change. In the parent widget which holds the listViewBuilder which in turn holds the list of SectionEditors, have a ValueNotifier<QuillController?> activeController, Modify SectionEditor to also takes in a callback function which update the active quill controller to the controller of the active SectionEditor,
Pass the activeController to your HeaderWidget
lastly, you may want to pass a Key to the ToolBar derived from the content or index of your activeQuillController, if you are finding the state of the ToolBar is not updating when activeSection is changed.
Of course you should hook active section change call back with some sort of gesture detection or button click in your SectionEditor.
Irrelevant to the problem at hand but may be an improvement to your code anyway:
Ditch Provider if possible especially when the object you are passing is not that deep in the stack, why not pass ActiveSection directly from your calling widget to the current widget?
Favor ValueNotifier over setState
PropertyValueNotifier, is just ValueNotifier with its notifylistener method exposed, if you are not familiar with its purpose or usage just google it.

because first and second quill editors share the same quillcontroller

Each editor must have its own controller. Similarly, there should be one toolbar for each editor/controller - set toolbar visibility based on which editor has the focus.
Can we close this issue?

I have devised alternate solution. you can close this issue


Support detection of the Velero helm chart

This fixes replicatedhq/kots#539
The helm chart uses different label selectors.
There's still a chance this won't work in some cases. There are no static label selector or annotations in this deployment.  But KOTS supports "standard" installations of velero, and this extends support for the velero helm chart installation method.

superseded by https://github.com/replicatedhq/kots/pull/541 (same content, merged repo)


Installation instructions for FlatPak

I've placed the JSON in ~/.config/PulseEffects/output/ but it doesn't appear in PulseEffects. I've restarted my machine.
I'm running PulseEffects 4.8.2 on Pop OS 20.10.  It didn't have a ~/.config/PulseEffects/ directory, so I created one, but the preset never appeared.  I think this is because I've installed it as a FlatPak.
So, I placed it in ~/.var/app/com.github.wwmm.pulseeffects/config/PulseEffects/output/ restarted it, and it worked.
I'll drop in a PR to update the README.

Didn't know about Flatpak. Thank you.

No worries. And thanks for the preset. It has made my conference calls so much more pleasant.


bug: Docker-Desktop starship takes long time

Overview
When setting up Starship locally on docker-desktop based k8s system, pull the docker image seem to take the longest time. It also seems that the docker images are pulled serially.
  Normal  Pulling    6m24s  kubelet            Pulling image "prom/prometheus"
  Normal  Pulled     89s    kubelet            Successfully pulled image "prom/prometheus" in 4m30.000384332s (4m54.848304802s including waiting)

Proposal

We need to add warning on Starship docs page, or troubleshooting section

Maybe add a manual step to pull images before hand
Look into faster pulling of docker images

We need to set ImagePull from Always to IfNotPresent else pods try and fetch images always.

This will force images to be used with tags instead of generics like: latest, nightly etc..

We should also expose this in the config file as well.


Error in the tiled.rs

I'm editting the tiled.rs myself because there are some functions that are not yet updated but I can't get through this part
It's either this error
|     tile_storage_query: Query<(Entity, &TileStorage)>,
|                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `bevy::prelude::Component` is not implemented for `bevy_ecs_tilemap::tiles::TileStorage`

or this error
|     tile_storage_query: Query<(Entity, TileStorage)>,
|                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `WorldQuery` is not implemented for `bevy_ecs_tilemap::tiles::TileStorage

The second one is definitely will not work but I'm not sure why the first one doesn't.
Using bevy 0.9.1 and main bevy_ecs_tilemap

Hey, i got the same error, how did you slove this error?

That class of error: stuff like "The thing that is obviously a Component isn't a Component" is indicative of there being two versions of Bevy on your dependency tree.
You can use cargo tree to get to the bottom of that.
The main branch of this repository is currently compatible with Bevy 0.10 (crates.io release hopefully coming soon). For other versions of bevy, see the compatibility table.


Adding support for alfanumeric index access

You can have alfanumeric keys together with numeric keys. I changed the regular expression to fix this.
Example:
var arrResults = {"ID4":{"MAXNUMBERPRATICA":"27652","_odbc_connection_id":"ID4"},"4":{"MAXNUMBERPRATICA":"123456","_odbc_connection_id":"ID4"}};
console.log(sprintf("check results = %(arrResults[4].MAXNUMBERPRATICA)s",{"arrResults":arrResults}));
console.log(sprintf("check results = %(arrResults[ID4].MAXNUMBERPRATICA)s",{"arrResults":arrResults}));

Thanks for your input. Does .ID4 not work in your case?

errr, I haven't tried that... I just did a test and you are right. That works perfectly.
Feel free to decide wheter or not my change gets included. As you correctly point out, this already works if I change the way I'm requesting the parameter:
console.log(sprintf("check results = %(arrResults.ID4.MAXNUMBERPRATICA)s",{"arrResults":arrResults}));


About the baselines

Hi Dinghuai,
Thank you for releasing the codes.
I have been working on reproducing the results based on your source codes. However, when running PIS and DDS (baseline), I obtained an average LogZ Error of around 0.4 and 0.3 for MoG, whereas the reported one in your paper is just around 0.036 and 0.028. I have attempted to run the official codes, but encountered a series of package issues that I am finding challenging to resolve.
Would you like to provide the baseline codes used for your paper as well? It would be helpful in resolving the discrepancies.
Best,
Dong

Hi, thanks for your interest, I wonder in PIS, have you set the dt to be 0.05? For DDS I think one also needs to change the sigma appropriately as a hyperparameter.

Hi,
Yes, I have set dt = 0.05 for MoG. After double-checking both your codes (as provided below) and mine for PIS. I noticed a difference - DGFS is updated sample-by-sample, each of (N+1, d), while in my implementation, PIS is updated based on all samples (bz, N+1, d).
I am curious about the implementation on your end. Could you share some insights or considerations regarding this difference?
Thank you & regards.
for b_idx in range(batch_size):
     state_b = states[b_idx]  # (N+1, d)
     log_pf = self.log_pf(time_b[:-1], state_b[:-1], state_b[1:])  # (N,)
     log_pb = self.log_pb(time_b[1:], state_b[1:], state_b[:-1])  # (N,)

     flow_b = self.flow(time_b, state_b).squeeze(-1)  # (N+1, 1) -> (N+1,)

     flow_b = flow_b + logrs[b_idx]  # (N+1,)
     flow_b[-1] = logrs[b_idx][-1]  # (1,)

     diff_logp = log_pf - log_pb # (N, )
     diff_logp_padded = torch.cat((torch.zeros(1).to(diff_logp), diff_logp.cumsum(dim=-1)), dim=0) # (N+1,)
     # this means A1[i, j] = diff_logp[i:j].sum(dim=-1)
     A1 = diff_logp_padded.unsqueeze(0) - diff_logp_padded.unsqueeze(1)  # (N+1, N+1)

     A2 = flow_b[:, None] - flow_b[None, :] + A1  # (N+1, N+1)
     if not torch.all(torch.isfinite(A2)):
         import ipdb;
         ipdb.set_trace()

     A2 = (A2 / self.data_ndim).pow(2)  # (N+1, N+1)
     # torch.triu() is useless here
     loss = torch.triu(A2 * self.coef, diagonal=1).sum()
     info["loss_dlogp"] = loss.item()

     self.optimizer.zero_grad()
     loss.backward()
     self.optimizer.step()

Hi,
Yes, I have set dt = 0.05 for MoG. After double-checking both your codes for DGFS (as provided below) and mine for PIS, I noticed a difference - DGFS is updated sample-by-sample, each with the size of (N + 1, dim), while in my implementation, PIS is updated by all mini-batches of samples with the size of (bz, N, dim).
I am curious about the implementation on your end. Did you keep the same way? I quickly tried, but the training would become very slow.
Thank you & Regards.
for b_idx in range(batch_size):
    state_b = states[b_idx]  # (N+1, d)
    ....
    self.optimizer.zero_grad()
    loss.backward()
    self.optimizer.step()

Hi,
The two points do not matter much according to my experience. Do you write your own implementation of the baselines? I suspect that there could be small bugs in your implementation. Feel free to email me for more discussions on the baseline implementation -- it is actually not quite related to the implementation of this repo.


Update terminology.md

Small change.  A sentence was missing a 'with'.

@theheatDK : Thanks for your contribution! The author(s) have been notified to review your proposed change.


SPFx webart to manage SPFx solution using ALM API

Q
A

Bug fix?
no ?

New feature?
no ?

New sample?
yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
SPFx web part to manage all SPFx solution across tenant/sitecollection app catalog using ALM API. Please refer readme file for more information.

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

Cool demo showing the ALM API usage nicely - great work @Ramakrishnan24689. Would you be interested on doing a live demo of this in our community calls?

Cool demo showing the ALM API usage nicely - great work @Ramakrishnan24689. Would you be interested on doing a live demo of this in our community calls?

Thank you @VesaJuvonen, I would love to perform a live demo of this in our community call.


react/no-direct-mutation-state when setting state in constructor

I have always been under the impression that you are SUPPOSED to set state initially in the constructor as follows:
class MyComponent extends React.Component {
  constructor (props) {
    super(props)
    this.state = {foo: 'bar'}
  }
}

The docs even indicate as much in the examples:
https://facebook.github.io/react/docs/state-and-lifecycle.html
However, when I do this, I get complaints that I am setting state directly from react/no-direct-mutation-state. Am I doing it wrong or is that message misleading when setting state in the constructor?

Nevermind. I was doing something wrong. This issue can be deleted. At best it is misinformation and at worst, misleading. I apologize.


Add ability to select a specific ML model in project support workflow

Currently for structure based ML models, you cannot specify an exact model on the project support command line, instead the most recent target-compatible one is pulled. Instead we should have the ability to request one directly.

Until we figure out how to do #976, removing from 0.3.0

We decided to go with autoselection, otherwise use API.


Add pkg-config to OSX brew install list

This is more a dependency of cgo than go-sdl2, but go complains without it.

This change is

Thanks, I don't have OSX to verify but seems like a reasonable change.


Enhancement: Optional callback when multibar completes

This is a feature request.
The new multibar is great and provides some new possibilities. However, it'd be even greater if there was an optional callback method that is called when the multibar stops or when all single bars included in the multibar have finished, respectively.
This would be incredibly helpful because one wouldn't have to iterate over all bars to see if they're active or not.

hi @welljsjs
i fully understand your intention but you might using cli-progress in a wrong way: it is designed as pure ui componenten and not as kind of task queue.
program logic and ui components should always be separated...otherwise your program might hang because of the ui component...

Alles klar, das stimmt. Danke.


Refactor Sign All to use the Action async trait

Refactor the sign all command to use Tokio async methods by implementing the Action async trait for it following all the update command examples.

Completed in the new verify creator and verify creator-all commands.


Update testing documentation

Wiki documentation for testing still references runall.bat
This should be updated with a section on how to use Run-UnitTests.ps1

The wiki has been updated:
https://github.com/Microsoft/WinObjC/wiki/How-to-Contribute#running-tests
Thanks!


How to use the benchmark  script  "simple.py" ? thks

This's doesn't work.. I don't now why..
# ./simple.py --host <IP_ADDRESS> --port 7000 --timeit --pipeline
Usage:
  simple [--host IP] [--port PORT] [--nocluster] [--timeit] [--pipeline] [--resetlastkey] [-h] [--version]
Options:
  --nocluster        If flag is set then StrictRedis will be used instead of cluster lib
  --host IP          Redis server to test against [default: <IP_ADDRESS>]
  --port PORT        Port on redis server [default: 7000]
  --timeit           run a mini benchmark to test performance
  --pipeline         Only usable with --timeit flag. Runs SET/GET inside pipelines.
  --resetlastkey     reset __last__ key
  -h --help          show this help and exit
  -v --version       show version and exit

@ask870 What happens when you run it? Do you get some exception? Does it just look? Do you see any commands on the redis server?

@ask870 Any updates on this issue?

@ask870 I do not find any problem with running that script. Here is the output from my run
$ python benchmarks/simple.py --host <IP_ADDRESS> --port 7000 --timeit --pipeline
10k SET/GET operations inside pipelines took: 0.599034070969 seconds... 16693.5412936 operations per second
20k SET/GET operations inside pipelines took: 1.25131702423 seconds... 15983.159833 operations per second
40k SET/GET operations inside pipelines took: 2.34957194328 seconds... 17024.3776167 operations per second

Ensure you are running python 2.7 when running that script, that you have docopt installed in your python and that your redis cluster is reachable on that IP/PORT you specified.

Closing this with "Works for me". @ask870 If you want to reopen it and add some more information about the problem you can do it.


v8.2.1 still produces tagged pdf

https://github.com/gotenberg/gotenberg/commit/804fcff5b6a06a113f882fc87a2bfa8db709a986 does not work as expected. chromium is still producing tagged pdf
tested on docker image 8.2.1
curl --request POST http://localhost:3000/forms/chromium/convert/url --form url=https://gotenberg.dev/ -o my.pdf

related: https://github.com/gotenberg/gotenberg/pull/818

Thanks @fu-infotrack!
Does it happens with version 8.1.0?

Thanks!
So it seems, whatever the input sent via the DevTool protocol*, Chromium always generates tagged PDF 🤔
*no tagged PDF instruction & explicit disabling of tagged PDF.

According to the internet, another option is to use --disable-pdf-tagging when launching Chromium.

@Deadly0 A new release is required for this change. No idea about the Chromium version that introduced this change.

Fixed in https://github.com/gotenberg/gotenberg/commit/7b7ffb427d7f441a8ef5a9c44601af3fc8570e50.


Crash: Android Maps

Reports were received that there is a crash happening on Android when switching between the Maps and Home tabs on Android Alpha 822, and the experimental branch

Unable to reproduce on experimental or App Store/Play Store, closing.


OPRemoteNotificationPermissionOperation never calls finish

Once didReceiveRemoteRegistrationResponse received we should call [self finish]; to complete the operation. Currently finish is not being called.

Multiple commits. Sorry about that. I was stomping on my own changes. d1a1486 is the appropriate commit. I will make a PR.

@colinmcardell thanks for fixing this!

For sure. Good call!

Resolved with 4e33fac254d7209b65f395a6d8ea50fc2493501c. Closing..


Add a startup message

Add a startup message to be logged in console when service is started that contains:

the name of gearbox (it would be great if a banner is added too)
current version of gearbox
listening on port (http server started on :....)

I'll do it.


feat: password support

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

v1.1.0
v1.1.0
GitHub release

Your semantic-release bot :package::rocket:


Add ssl context support

Adds the global geopy.geocoders.options.default_ssl_context setting and ssl_context param to each geocoder.
By specifying a custom TLS context it's possible to disable TLS verification or use specific CA certificates.
For older versions of Python (before 2.7.9 and 3.4.3) this would issue a warning about missing TLS verification support (even for http schemes):
UserWarning: SSL context is not supported in your environment for urllib calls. Perhaps your Python version is obsolete? This probably means that TLS verification doesn't happen, which is insecure. Please consider upgrading your Python interpreter version.

Usage for disabling TLS verification completely:
import ssl
import geopy.geocoders
ctx = ssl.create_default_context()
ctx.check_hostname = False
ctx.verify_mode = ssl.CERT_NONE
geopy.geocoders.options.default_ssl_context = ctx

from geopy.geocoders import Nominatim
geolocator = Nominatim()
geolocator.geocode("175 5th Avenue NYC")

For using CA bundle used by requests:
import ssl
import certifi
import geopy.geocoders
ctx = ssl.create_default_context(cafile=certifi.where())
geopy.geocoders.options.default_ssl_context = ctx

from geopy.geocoders import Nominatim
geolocator = Nominatim()
geolocator.geocode("175 5th Avenue NYC")

The following issues should be resolved by this PR: #124 #237 #212
This issue is from the current roadmap #267.

I'm making an attempt to implement the new ssl fix, but keep receiving the following attribute error. Is my implementation wrong?
import ssl
import certifi
import geopy.geocoders
ctx = ssl.create_default_context(cafile=certifi.where())
geopy.geocoders.options.default_ssl_context = ctx
from geopy.geocoders import Nominatim
geolocator = Nominatim()
location = geolocator.geocode("318 main street Evansville Indiana")
InnovationPointe = Point(location.longitude, location.latitude)
print(InnovationPointe)
AttributeError: module 'geopy.geocoders' has no attribute 'options'

geopy==1.14.0 has been released 🎉


Remote Function Module (RFC) - Get Data from an On-Premise System Using a Custom Entity

Tutorials: https://developers.sap.com/tutorials/abap-environment-rfc-custom-entity.html
Hi @julieplummer20,
to get this tutorial working against the current ABAP Platform Trial I had to do the following adjustments:
Define a Type for bapi_epm_max_rows
    TYPES:
      BEGIN OF bapi_epm_max_rows,
        bapimaxrow TYPE bapimaxrow,
      END OF bapi_epm_max_rows.

and use it in:
          DATA ls_maxrows TYPE bapi_epm_max_rows.

which I then fill as
          ls_maxrows-bapimaxrow = lv_skip + lv_top.

The fields ProductId and CurrencyCode of the DDL Structure had to be renamed to Product_Id and Currency_Code.
Best Regards
Gregor

Hi Gregor,
Thanks a lot; this is really helpful.
I will update the tutorial accordingly.
Best wishes,
Julie.

Done - changes should be visible in next 24 hours


add ref local reassignment

And build project around the sample.
Sample updates for dotnet/docs#3961

This PR must not be merged until dotnet/docs#4875

Thanks @rpetrusha That comment was a test and a reminder to add a note on another issue.


Feat/3 phase tr

The folder example is miss spelled

Some context on this PR for public viewers.
This PR has had extended discussions internally. From the API design to the 3-phase approach. Some of those are documented in various issues (in particular #139), and in the issues mentioned in the milestone for v1.0.0.
We've chosen to do a so-called "big bang" release, as we didn't want anyone to be blocked by releasing a half-finished and non-feature-parity library.


Added issue events in comment view. Fix #123

Are colors alright?
More events needed?
Closed and reopened.

Merged and closed.

Good stuff!

Will fix the colors tomorrow, I will also later add a new issue for updating the icons so I won't add these to the TypefaceUtils file yet.

Awesome work @Meisolsson!
I've wanted to have this for a long time, I'll try to review the patch today

Ok, just wait until I fixed the string issue

@jonanp I think this should be merged to master ASAP. What do you think?

@fadils agreed, this should go into our next release.
I expect to have the master branch ready tonight and I'd also like to upload a new version of ForkHub (has around 200 users already) to get a bit of testing before the release.

This PR breaks showing a newly added comment.
I've fixed it here and added a few improvements 1, 2 and 3. Feel free to cherry-pick the commits you need.

@jonanp could you please tell me the steps to reproduce it?

Simply add a comment in an issue. You wont see it appearing until you refresh.


Supports lambda function qualifier by URL.

Hi!
Added specify the qualifier of lambda function by URL.
lambda://xxx@function-name/foo/bar calls the lambda function function-name:xxx.

Summary by CodeRabbit

New Features

Added the ability to specify a function qualifier in a URL for AWS Lambda interactions.
Updated documentation with a new example demonstrating this feature.

Tests

Introduced tests to verify the behavior of BufferedTransport with and without a qualifier.

released https://github.com/shogo82148/lambtrip/releases/tag/v0.2.0


Add the project link to the readme file so that contributor can explore the project

hello there, hope your doing well, i think i can help you with this. hope you assign me this issue


Change bullet and spawner _Process to _Physics_process

I created a replay system using _Physics_process, all character movements are recorded frame by frame, but the bullet in this module does not change speed from changing fps, and i think a delta is used which breaks the replay system
Spawner changes speed, but I don’t understand if it works correctly.
Is there a way to change this in godot without changing source code

Hi, and thanks for the bug report! I really appreciate hearing from people using this module in their projects. :)
I'd love to patch up qurobullet and solve this problem for you, but I need some clarification first.
Currently, all bullet movement and collision detection already occurs in physics process, so I need a bit more information about your replay system to figure out what's causing the issue. You mention "changing fps" with the replays, but I'm not sure what you're doing exactly. Are you adjusting Godot's timescale to make slow motion effects, and that's causing things to desync?
Once I know what you're trying to do exactly, I can probably solve this issue!
If it's not too much to ask, if you could give me a sample scene that demonstrates the issue you're having, I could use it to make sure the problem is fixed before I update the repo.

In project settin i change Physics/Common/Physics fps to change game speed
i dont use _process(delta) or delta
my project (litle clearing it but still look awful):
https://drive.google.com/drive/folders/1DHBSaan-J2pguqQvx5AauneECWit_lJz?usp=sharing
wasd to move
replay in project, just press replay, to write new press start move charater and press save, after press replay or start you need reload project to replay or start new record becose it still not finish
well change fps to 30 or 240 and look what happend after press replay (by defoult 60 )

Thanks for getting back to me! I can't look at your example until I'm at my computer (and I don't have much time to work on qurobullet during weekdays), but this information helps me understand the situation a lot better!
Unfortunately, fixing this is not so simple. Bullet physics processing in qurobullet makes use of delta in its calculations, to increase stability in performance, to allow users to get the same behaviour regardless of framerate (so other devs could make their game run at a base of 30fps or 120fps and get roughly the same behaviour in game), and create smoothly interpolated slow motion and fast forward effects at different timescales. Your slow-mo system relies on the bullets moving the same distance per frame, regardless of how long that frame takes to complete.
So, the core of the problem is that qurobullet is built around time, and your system is built around frames.
While I could potentially put in a bandaid type solution to make it work the way you need, it goes against the design of the rest of the program. Also, I don't think changing physics fps in a live game is recommended, and I don't wanna code things in a way that goes against Godot's usual workflow. So, I'm sorry, but I won't implement a fix to this.
Instead, all I can do is recommend you use Engine.time_scale for your game speed changes instead of changing physics FPS (which you'll notice will make your slow mo a lot smoother), and rework your replay system to be based on time rather than frames. Feel free to ask me for advice if you try that and run into issues.

I closed the issue, but this thread will stay open in case you have any questions!

Thank to tell me about Engine.time_scale, timer work good with this (0.012 to 60 tick per second).

No problem! I'm happy that time scale is helpful for you!

So i try hard as can but unfortunately replay system with this module is imposible (right now).
Problem is when change forse fps(_process(delta)) delta change variable and this is good, i actualy can identify each frame fps but  when i change Engine.time_scale delta change variable again and engine go broke(as expected)
func _process(delta):
T = (((1/ delta)*3)*2 / 120 to get current time_scale from fps)
Engine.time_scale = T

After all change fps and check frame using process without predict drop fps just broke replay.
Some time godot give intrestiong expirience --
Mayby later i found how create replay system with this module

this issue is totaly close, i`am idiot
func _physics_process(delta):
for i in range(4)
frame +=1
this give 240 fps and replay work perfect