FC search behavior/es pages indexing common mistake

documented default FC search choices and the common mistake on M2 retated to page indexing

closed cause of this comment. we will fix the default behavior in FC. and then maybe create a documentation for M2 search and in that we can mention the cms pages and how to enable them


Parallel pipelines can create entites in DB

Describe changes
This PR solve a few parallelization issues we had:

save_artifact logic is improved, so it is now tolerant to parallel creation of Artifact and has a retry logic to create a new Artifact Versions for those without an explicit version name
Model Version creation is now also tolerant to parallel execution and equipped with retry logic to ensure that parallel runs do not get dumped into same Model Version
Both cases are loaded with heavy parallel test cases to proof it is sustainable on a long run
New MAX_RETRIES_FOR_VERSIONED_ENTITY_CREATION constant introduced and set to 10 reties for now with 0.2 seconds of cooldown growing by retry count (e.g. 0.2 * retry_num). 10 is quite empirical and might need some further tunning.

Tiny side improvement:

Decreased logging warning for Model config mismatch, because it doesn't make sense in production usage, based on user feedback and is only annoying

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[x] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@coderabbitai review


Question about fine-tuning

Hello people,
I have been struggling to train the 38M parameters model on a fasta dataset from the RCSB.
I had to alter the dataloader, but when running the script, it leads to batch size issues.
Did anybody try to re-train their models on its own data ?
Thanks in advance for any of your insight.
Best,
Lo

May I ask how you implement fine-tuning?


fix(discriminator): looking through parents hierarchy to find discrim…

…inator
Information

Type
Breaking change

Feature/Fix/Doc/Chore
Yes/No

Todos

[ ] Tests
[ ] Coverage
[ ] Example
[ ] Documentation

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

v7.8.1
GitHub release

Your semantic-release bot :package::rocket:


python311Packages.pylint-plugin-utils: 0.7 -> 0.8.2, python311Packages.pylint-django: refactor

Description of changes
Fix build (https://hydra.nixos.org/build/246593226)

Things done

Built on platform(s)

[ ] 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.05 Release Notes (or backporting 23.05 and 23.11 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.

Result of nixpkgs-review pr 282373 run on x86_64-linux 1

2 packages failed to build:

prospector
prospector.dist

8 packages built:

python311Packages.pylint-celery
python311Packages.pylint-celery.dist
python311Packages.pylint-django
python311Packages.pylint-django.dist
python311Packages.pylint-flask
python311Packages.pylint-flask.dist
python311Packages.pylint-plugin-utils
python311Packages.pylint-plugin-utils.dist

Result of nixpkgs-review pr 282373 run on x86_64-linux 1

2 packages failed to build:

prospector
prospector.dist

10 packages built:

python311Packages.mypy-boto3-builder
python311Packages.mypy-boto3-builder.dist
python311Packages.pylint-celery
python311Packages.pylint-celery.dist
python311Packages.pylint-django
python311Packages.pylint-django.dist
python311Packages.pylint-flask
python311Packages.pylint-flask.dist
python311Packages.pylint-plugin-utils
python311Packages.pylint-plugin-utils.dist

requirements-detector fails because astroid<3.0,>=2.0. This will be fixed in an additional PR.


Utility docs

What is up with the commit history we're seeing here? Dating back to June 2016?
Added a comment. Also, needs a rebase... Otherwise LGTM

Sorry mate what are you referring to? The complete history of the project?
Also what is lgtm?

LGTM - looks good to me.
I’m referring to the commit history that’s on this PR. Seems to be showing historic commits unrelated to this work?


Implements DataFrame.persist() with additional tests for DataFrame.cache()

Resolves #1373
Here, we have a DataFrame named df
>>> import pyspark
>>> df = ks.DataFrame([(.2, .3), (.0, .6), (.6, .0), (.2, .1)],
...                   columns=['dogs', 'cats'])
>>> df
   dogs  cats
0   0.2   0.3
1   0.0   0.6
2   0.6   0.0
3   0.2   0.1

Set the StorageLevel to MEMORY_ONLY.
>>> with df.persist(pyspark.StorageLevel.MEMORY_ONLY) as cached_df:
...     print(cached_df.count())
...
dogs    4
cats    4
Name: 0, dtype: int64

Set the StorageLevel to DISK_ONLY.
>>> with df.persist(pyspark.StorageLevel.DISK_ONLY) as cached_df:
...     print(cached_df.count())
...
dogs    4
cats    4
Name: 0, dtype: int64

If a StorageLevel is not given, it uses MEMORY_AND_DISK by default.
>>> with df.persist() as cached_df:
...     print(cached_df.count())
...
dogs    4
cats    4
Name: 0, dtype: int64

Codecov Report

Merging #1381 into master will decrease coverage by 2.29%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1381      +/-   ##
==========================================
- Coverage   95.23%   92.94%   -2.30%
==========================================
  Files          34       34
  Lines        7792     7799       +7
==========================================
- Hits         7421     7249     -172
- Misses        371      550     +179

Impacted Files
Coverage Δ

databricks/koalas/frame.py
93.39% <100.00%> (-3.40%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
24.32% <0.00%> (-70.28%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50.00% <0.00%> (-50.00%)
:arrow_down:

databricks/koalas/__init__.py
78.72% <0.00%> (-14.90%)
:arrow_down:

databricks/conftest.py
88.67% <0.00%> (-7.55%)
:arrow_down:

databricks/koalas/namespace.py
87.43% <0.00%> (-1.37%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0.00%> (-0.96%)
:arrow_down:

databricks/koalas/testing/utils.py
78.26% <0.00%> (-0.73%)
:arrow_down:

databricks/koalas/groupby.py
90.26% <0.00%> (-0.21%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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

Thanks! merging.


Library Guides content work

What is the problem to solve?
To ensure that the guides provided for library users are concise and useful
What stage of research is it? (discovery/general usability testing/post release)
Content Discovery
What are the objectives?
Understand the user needs for mapping content to and developing a framework for further guides
What are the assumptions?
That the current drafts of the users guides are too long and contain too much site specific generic content
What research technique is required?
Content mapping workshops
Optimal number of participants
Acceptance criteria
Deadline for results/dependencies:

Miro board to develop the user needs for the library guides https://miro.com/app/board/o9J_l8ezil0=/


Feedback on other Serverless setups

We are using this plugin in production but would be useful to get some information how does it handle other setups.
Cheers! 😃

I've just converted a project to use it (25 functions) and it's sped up deployment a lot. I've had some issues with using npm projects that don't play nicely with (I suspect) browserify (such as nodemailer) which I'm still working through.
Errors such as:
Unable to import module '_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler': Error
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at s (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:554)
at /var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:745
at Object.467.semver (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:86189:18)
at s (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:694)
at /var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:745
at Object.1190.chalk (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:235973:15)
at s (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:694)
at /var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:745
at Object.1188../css (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:235686:14)
at s (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:694)
at /var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:1:745
at Object.1189../css (/var/task/_optimize/tsz-serverless-api-dev-wp-shared-email/functions/workers/shared/email/handler.js:235965:15)

Currently working through these to see what the issue is.

@darbio  did u get to resolve this issue?

@bwistero yes and no.. See #54 - I removed the offending packages and replaced them with ones that could be webpacked. We're using it in production now with no issues.


Add command line switch for opening a new tab

It would be nice if extraterm could open a new tab when called via it's executable.  For example, for a context menu entry.

This is closely related to issue #132.

This is the current behaviour these days.


update smoke tests, use latest released versions

/azp run js - smoke-tests

The changes to the app code was from pre-GA to get to GA. I went back to GA versions of storage and KV locally and the tests run and pass. The app code required no changes to pass.
I'll run this test on the other PRs.


[BUG] prevent using recv() without send()

Hello,
just find that if I wrongly run recv() without send(), then the program will goes into like an infinite loop.
It would very easily to occur in jupyter or interactive console or program bug.
Would it be better to add a timeout function inside recv() function?
Best regards.

I don't think it's possible because, from EnvPool's perspective, it cannot predict the single env step elapsed time. It's hard to tell the difference between user's wrong calling pattern and env's slow execution speed.


redpanda: convert rbac.yaml to go code

This PR converts rbac.yaml to Go code using gotohelm.
Fixes #1213

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

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

@charlie-haley Thank you for contribution. I adjusted your change.


Dependencies are set up in constructors, not Functions

This may be obvious to some, but to those who rely heavily on templates, or have used so many workarounds as to confuse ones self, remember that dependencies are listed/added in the constructor, not the function. For example, to use IConfiguration you would use
public class TestFunction
{
    private readonly IConfiguration _configuration;

    public TestFunction(IConfiguration configuration)
    {
        _configuration = configuration;
    }

    [FunctionName("TestFunction")]
    public async Task<IActionResult> Run(
        [HttpTrigger(AuthorizationLevel.Function)] HttpRequest req,
        ILogger log)
    {
        log.LogInformation(_configuration["AzureWebJobsStorage"]);

        return new OkObjectResult($"Success");
    }
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5786402e-9d88-5de0-607a-1c2a143af006
Version Independent ID: 15368d1c-b22e-7eb2-413f-cc0d41d2b909
Content: Use dependency injection in .NET Azure Functions
Content Source: articles/azure-functions/functions-dotnet-dependency-injection.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: jehollan

Hi @MisinformedDNA Thanks for sharing! Since this channel is for driving improvements towards MS Docs, let us know if there is anything that you feel we should update in this documentation. Otherwise, we'll proceed to close this thread :)

@MisinformedDNA is there an article that we can link to that encapsulates this information?

They link to the best page.

Dependency injection addresses these problems through...Injection of the service into the constructor of the class where it's used. The framework takes on the responsibility of creating an instance of the dependency and disposing of it when it's no longer needed.

Injection has to happen on object creation, so constructors make the most sense. (There is also a concept of property injection, but that ends up as less than ideal.)

In the case of Durable Functions, I believe there may be value in supporting method injection. Many of the examples of Durable Orchestration Functions just include the activities as methods of the orchestration class. However, it seems at best confusing, and at worst unsafe, to use constructor-injected dependencies in a class housing multiple activity functions (think thread safety, immutability, etc).
This would suggest a pattern of creating an individual class to house each separate activity function, in order for each activity function to have a constructor into which its specific dependencies can be injected. The amount of clutter this would cause defeats some of the purpose of the "lightweight" nature of functions.
It seems like method injection via support for [FromServices] might be a good way to reduce the clutter for durable functions.


Poster Network: Option for Admin to Mark "Approved for General Viewing"

The reason for an admin controlled "marker" would be to flag posters that are not going to violate any partner or service TOS external of WaterWolf. So say for rendering random posters for the WaterWolf TV effort. This would be behind moderator and admin level control, and not settable by a general user.
Additionally, this mark should prevent the replacement of a poster image that has the flag set, or clear the "approved" flag if the poster image is replaced.
An additional parameter of "approved-only=true" in the URL bar would trigger a filter to only those flagged as approved.

Also, this should prevent incrementing the view counter, since this an internal use function, and I don't want to give view credit everytime we load a poster for the WaterWolf TV or other such function... but I don't know how easy that would be.


TypeError in the DriverFactory when use AttributeDriver

Bug Report

Q
A

Version(s)
v0.1

Summary
When I use \Doctrine\ORM\Mapping\Driver\AttributeDriver, I get an error:

Uncaught TypeError: Doctrine\ORM\Mapping\Driver\AttributeDriver::__construct(): Argument # 1 ($paths) must be of type array, Doctrine\Common\Annotations\CachedReader given, called in ... vendor\skar\laminas-doctrine-orm\src\Service\DriverFactory.php on line 49...

How to reproduce

// config/autoload/orm.global.php

<?php

declare(strict_types=1);

return [
    'doctrine' => [
        'connection' => [
            'orm_default' => [
                'driver_class' => \Doctrine\DBAL\Driver\PDO\MySQL\Driver::class,
            ],
        ],
    ],
];

// local.php

<?php

/**
 * Local configuration.
 *
 * Copy this file to `local.php` and change its settings as required.
 * `local.php` is ignored by git and safe to use for local and sensitive data like usernames and passwords.
 */

declare(strict_types=1);

return [
    'doctrine' => [
        'connection' => [
            'orm_default' => [
                'params' => [
                    'host'     => '<host>',
                    'port'     => '<port>',
                    'user'     => '<user>',
                    'password' => '<pass>',
                    'dbname'   => '<dbname>',
                ],
            ],
        ],
    ],
];

Run vendor/bin/laminas doctrine:migrations:diff

Thanks! Maybe this part should be rewritten in the future, but for now this should work.


undefined behavior in the Rust code

https://github.com/jonhoo/volley/blob/master/servers/rust/main.rs#L46-L47
This is technically invoking undefined behavior, as you are aliasing &mut pointers, through the transmute.
I'm willing to send in a patch to fix this, but I can't right this moment, and didn't want to forget.

The goal of this was to avoid an extra allocation within the loop for either the integer or the buffer. I assume you're thinking of borrowing buf as mutable within a limited sub-scope so that we can operate on challenge as an integer without breaking the aliasing rules?

When I asked @gankro, our resident unsafe expert, he said
19:02 < Gankro> steveklabnik: I would suggest
        they transmute the u32 to a
        [u8; 4] directly
19:02 < Gankro> It's a no-op, and any copies
        should be trivially elided

But, I don't think that would give you your 'integer or buffer' behavior...

Hmm, I don't know the Rust internals well enough, but I don't think that would work quite the same way. The performance impact of keeping two pieces of memory around and copying between them is probably tiny, but I'd prefer to avoid it in the inner loop if possible. The prospect of undefined behavior isn't great though, so if this is the only way, then I'll change it.

Basically, the issue is that &mut is a very strong guarantee: there are no other pointers to this particular piece of memory. The optimizer will assume this...
But, thinking about it some more, you should be able to do what @gankro was talking about: before you want to use it as an integer, transmute() to an integer, before you use it as a [u8; 4], transmute() it to that array. transmute() is literally a no-op, so it should be very cheap.

Thanks @steveklabnik!

Thank you! It's cool that you can get away with no allocations and that this is safe, even if it does require some trickery.

Agreed! The reason I decided to conduct these benchmarks in the first place was because I wanted to figure out what the theoretical upper limits for my memcached clone in Rust should be: https://github.com/jonhoo/rucache
rucache has a bunch of other tricks too, many of which are similar to this buffer trick. In particular, it turns out that it is quite often useful to be able to interpret a sequence of bytes both in a structured and in an unstructured way, particularly when dealing with low-latency network operations. I wish there was a cleaner way of doing it though -- the whole [u8; N] thing feels like a bit of a hack, partially because the N is not necessarily known at compile-time.

Oh neat!
Type-level integers should help in the future with arrays being awkward, it's certainly a thing right now.


Abort dev app installation process if error occurred during cloning.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues

If it can't clone fork repository it continues the installation process and throws an exception: PHP Warning 'yii\base\ErrorException' with message 'chdir(): No such file or directory (errno 2)'

Merged. Thanks!


Enhanced multitasking

Description of the new feature / enhancement
Enhanced multitasking. Automatically adds the Maximized Window app to a new desktop, and automatically deletes the new desktop when it is closed。
Scenario when this would be used?
Enhanced multitasking capabilities when the display is single. Forms an effect similar to MACOS.
Supporting information
No response

#13993 closed because of this -  this closed because of #13993.  Cool. ok)


Updates v8 branch from master's changes.

Update v8 branch from master's changes.
This will merge the current master to v8 branch.

@antonmedv Please also merge this one https://github.com/deployphp/test-laravel/pull/2 thanks.


Nomad doesn't sync AD password after update to ventura

I initially create a post in the jamf community about this issue.
https://community.jamf.com/t5/jamf-pro/nomad-doesnt-sync-ad-password-after-update-to-ventura/m-p/284898#M255739
and someone from the community is saying that nomad is end of support???
Is this true?

There is no support from team ?

jamf said because its an open source product - they do not support this. they recommend me jamf connect which is about $2.50 per user per month


investigate the reason of duplicated commit

https://github.com/ngaut/unistore/pull/565 has fixed the bug, but there should not be duplicated commit, need to investigate the reason.

Fixed by https://github.com/ngaut/unistore/pull/568


[0.10.0] CREATE CONTINUOUS QUERY causes lease conflicts in cluster

When repeating this in a one-node cluster, I don't see these lease conflict issues.
When running a 3-node fully replicated (default settings) cluster, I get conflict responses in the logs of
the node where the CREATE CONTINUOUS QUERY was run, since another node (n2) has acquired the lease on the continuous query, and is running them.
// n1
> create database cqtest
> use cqtest
Using database cqtest
> insert cpu value=1
> CREATE CONTINUOUS QUERY cqmin ON cqtest BEGIN SELECT min(value) INTO cqtest."default".foo FROM cqtest."default".cpu GROUP BY time(10s) END

According to the logs, at this point n2 actually gets the lease for this CQ, and runs it every 10 seconds. However, in the mean time n1 is trying to get the lease, and apparently either succeeding (200 response), or getting a conflict (409 response).


CardLayout styles are broken

https://www.dropbox.com/s/81ill1uu0qwemwr/Screenshot 2018-03-20 12.07.39.png?dl=0
The boxes around the hard sections  are too small by a line height or two. We should fix this so cards will look right again.

Just cloned the repo and tested. The above referenced PR does fix this issue.

I tested this as well and it seems to be fixed. Moving to QA to double check!


The security token included in the request is invalid error even though my token is valid

I am using external-secrets version 0.7.2 with kubernetes 1.22.17 on a k3d cluster.
I am trying to setup a ClusterSecretStore using tmp credentials. Shown below:
apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
    name: secretstore
spec:
    provider:
        aws:
            service: SecretsManager
            region: eu-west-1
            auth:
                secretRef:
                    accessKeyIDSecretRef:
                      name: awssm-secret
                      key: access-key
                      namespace: external-secrets
                    secretAccessKeySecretRef:
                      name: awssm-secret
                      key: secret-access-key
                      namespace: external-secrets
                    sessionTokenSecretRef:
                      name: awssm-secret
                      key: session-token
                      namespace: external-secrets

When deploying external-secrets i get a :
{"level":"info","ts":1674477410.8171813,"logger":"provider.aws","msg":"using aws session","region":"eu-west-1","credentials":{}}
{"level":"info","ts":1674477410.8172092,"logger":"provider.aws.secretsmanager","msg":"fetching secret value","key":"dev-shared-environment-vault-secret","version":"AWSCURRENT"}
{"level":"error","ts":1674477411.3760185,"logger":"controllers.ExternalSecret","msg":"could not get secret data from provider","ExternalSecret":"qct-coverage/common-vault","error":"UnrecognizedClientException: The security token included in the request is invalid.\n\tstatus code: 400, ","stacktrace":"github.com/external-secrets/external-secrets/pkg/controllers/externalsecret.(*Reconciler).Reconcile\n\t/home/runner/work/external-secrets/external-secrets/pkg/controllers/externalsecret/externalsecret_controller.go:190\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:235"}

The thing is that the session token is valid, all the awssm-secret values and keys are correct and I have not a clue why my secrets are not deplyed to my namespace. Since I am all out of ides a am trying a hail mary here. Perhaps someone will be able to point me in the right direction.

The session token may be expired (1-12h) or it may have an invalid character (newline etc) these are the two predominant issues i've run into

The session token is not expired for sure. As for the invalid char - there doesn't seem to be an invalid char but I will look deeper into it. If anyone can think of anything else, I am really eager to hear since I am really stuck on this one.

Hey, no update here, just a sidenote: we're using this (short-lived session tokens via sessionTokenSecretRef) in our e2e tests, i'm very confident that this works when correctly configured.


Certain parts of game continue during menu paused state resulting in much-weirdness

Describe the bug
The menu button on a hardware device when pressed displays some things and indicates the game is PAUSED. Under some circumstances parts of the game appear to carry on running and then afterwards the game is left in an unusual state and strange phenomena can occur that do not follow the normal behaviour of the code. There may be a problem with the counting of remaining lives too.
This is compiled on 0.14.9 / 5.21.14.
To Reproduce
Steps to reproduce the behavior:

Run up latest Chomper game https://arcade.makecode.com/75342-75047-13962-10112
Download to a hardwave device.
Get killed on level 1 by the red ghost.
Press menu button quickly, i.e. during death throes.
Stay on menu screen for about 6 seconds and carefully observe a sprite appearing under the buttons and moving off the screen through a solid wall to the right!
Return to game and observe unusual game state:

player cannot move,
death effect carries on running (resulting in what could be termed endless burnination),
Enemy is AWOL,
other game code appear to be working ok.

Expected behavior
Paused should mean paused.
Screenshots
MakeCode Arcade paused bug (YouTube) - note the sneaky running away of the red ghost around 00:05-00:07. The number of lives also looks suspicious as it goes from 3 to 2 to 3.
Desktop (please complete the following information):

OS: n/a
Browser:
Version:

Device (please complete the following information):

Device: Adafruit PyGamer
OS: v3.7.0 bootloader.

Additional context
Not relevant to this bug but this game gives errors on the current beta beta.

This is effectively the same situation as https://github.com/microsoft/pxt-arcade/issues/1272:

the overlap spawns a fiber, as the collisions are handled asynchronously. the playUntilDone pauses the fiber until the sound is complete, and it calls restartCurrentLevel after that is completed; when you open the menu before the sound is completed, the sound completes while the scene is open, and that function (restartCurrentLevel) is invoked while in the menu scene, spawning the enemy on top of the menu / messing up the rest of the game state.
side note, real good edge case bug in the additional context portion, filed here: https://github.com/microsoft/pxt-arcade/issues/1444

This is duplicate of https://github.com/microsoft/pxt-arcade/issues/1272


unixPB: add CentOS Stream 10 static docker file

CentOS Stream 10 is now available and this will be the basis of RHEL10 so it makes sense for us to be ahead of the game at run testing of Temurin on it.
Minor doc fixes are included in this too including updating the list of static docker hosts that we have which is well out of date (Maybe we should just remove the explicit list?)

Checklist

[x] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[x] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[x] VPC/QPC not applicable for this PR
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

Draft for now as we don't have a working replacement for Xvfb which is not in the repositories since CS10 has moved exclusively to Wayland.

Raised issue to investigate weston's feasibility: https://github.com/adoptium/infrastructure/issues/3851


Create challenge

Thank you for submitting the code. Unfortunately, the code is too similar to an existing pull request. So we cannot accept this. If you want you can resubmit the pull request after making the following changes
Please change the code such that, instead of replacing the search string with #, the program should reverse the search string and replace the original.
For example, if the input file contains the following text:
"The term "cut and paste" comes from the traditional practice in manuscript-editings whereby people would cut paragraphs from a page with scissors and paste them onto another page"
and the search string is: page
The output should be:
"The term "cut and paste" comes from the traditional practice in manuscript-editings whereby people would cut paragraphs from a egap with scissors and paste them onto another egap"


Integrate clang-tidy and scan-build into Linux.

Tested by hand.
ubuntu-log.txt

@pspoerri thanks for the contribution!
Can you give a little more background on these tools and the benefit for having them pre-installed? If a tool can be installed during the build, we like to evaluate how much time is saved vs. how much space is used by having the tool pre-installed.

Can you give a little more background on these tools and the benefit for having them pre-installed?
clang-tidy and scan-build are extra tools belonging to clang.

clang-tidy is a linter tool which integrates a wide array of checks. Primary focus are code style checks.
*scan-build is the wrapper tool for the clang static analyzer.

Here's a demo project that shows how clang-tidy and the scan-build are typically integrated with a CMake project.
Both the clang-tidy and the static analyzer are tools you would want to run on every pull-request.

If a tool can be installed during the build, we like to evaluate how much time is saved vs. how much space is used by having the tool pre-installed.

I believe that both tools are useful for the developer community relying on C and C++ code-bases. Installing the tool with the image ensures that clang-tidy and scan-build are installed with the same version as the default clang installation.

@pspoerri thank you so much for the contribution. However, after looking into it, I don't see enough benefit to preinstall this to make it worth the risk and ongoing maintenance effort. An alternative you might want to consider to simplify it's use on Actions is to write a setup-clang-tidy Action perhaps?


Bug: Menu doesn't scroll with the input field

Hi there,
if one modifies the static data example so that it's contains some space (whatever the content actually is) and a scrollbar will be shown, one can type in some characters, so that the menu will be visible, and scroll the page. The menu will remain at a fixed position and suddenly detach from the input field.
My fix would be: change the "position" value from "fixed" to "absolute" in Autocomplete.js line 48.

Hi!
Thanks for taking the time to report this (and the other issues).
We're aware that the default menu styles cause a fair bit of headache. The best bet is to use props.menuStyle/props.renderMenu to customize the menu and its styles to your needs.


Release azure-cli-configure 2.0.1

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Release of 'azure-cli-configure' with version '2.0.1' successful. View at https://pypi.python.org/pypi/azure-cli-configure/2.0.1.

GitHub release created. https://github.com/Azure/azure-cli/releases.


Issue with iOS-SDK AlchemyAPI

I tried to use keyword extraction to extract keyword, but there is one parameter I need is "sentiment = 1" by default is 0. After checking sdk code I found after WatsonDeveloperCloud SDK build, some values are missing for http parameters. Below are the screens. So in the end I call AlchemyAPI Rest API instead.

Struct is empty no parameters

In git master there are parameters

My code sample where I need set the parameters

Hi @LinZhao1. Sorry to hear about the bug!
I committed a fix to the remove-testable-annotation branch, which will be merged into master as soon as this pull request is complete.
Unfortunately, our branching model has slowed down our ability to push quick fixes. We're going to change that very soon so we can respond quicker to bugs like this.


Possible to use as in-memory mock storage

I notice this package is a great substitution for *redis.Client. However all calls to it must be prepared with mock.ExpectGet(..).SetVal(..).
I am hoping to use this as a mock redis implementation in my main application code (where I use redis as a "cache") that just accepts the commands, and ignores them.
So I'm almost looking for an in-memory implementation of *redis.Client (because I don't want to run redis-server to have my app run locally). It does not have to actually store/serve the data.
Does this exist –or is there a way I can use redismock in this way, say something like mock.ExpectAnything().

That's useful, thanks!

there is also miniredis: http://github.com/alicebob/miniredis its an inmemory implementation

Actually that's far more useful. Thank you. 🙏


python311Packages.mizani: 0.11.2 -> 0.11.3

Description of changes
Changelog: https://github.com/has2k1/mizani/releases/tag/v0.11.3
cc @samuela

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.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 310444 run on aarch64-darwin 1

6 packages marked as broken and skipped:

python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.bsuite
python312Packages.bsuite.dist

4 packages failed to build:

python311Packages.plotnine
python311Packages.plotnine.dist
python312Packages.plotnine
python312Packages.plotnine.dist

4 packages built:

python311Packages.mizani
python311Packages.mizani.dist
python312Packages.mizani
python312Packages.mizani.dist

Result of nixpkgs-review pr 310444 run on x86_64-darwin 1

6 packages marked as broken and skipped:

python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.bsuite
python312Packages.bsuite.dist

4 packages failed to build:

python311Packages.plotnine
python311Packages.plotnine.dist
python312Packages.plotnine
python312Packages.plotnine.dist

4 packages built:

python311Packages.mizani
python311Packages.mizani.dist
python312Packages.mizani
python312Packages.mizani.dist

Result of nixpkgs-review pr 310444 run on aarch64-linux 1

14 packages built:

python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.mizani
python311Packages.mizani.dist
python311Packages.plotnine
python311Packages.plotnine.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.bsuite
python312Packages.bsuite.dist
python312Packages.mizani
python312Packages.mizani.dist
python312Packages.plotnine
python312Packages.plotnine.dist

Result of nixpkgs-review pr 310444 run on x86_64-linux 1

14 packages built:

python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.mizani
python311Packages.mizani.dist
python311Packages.plotnine
python311Packages.plotnine.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python312Packages.bsuite
python312Packages.bsuite.dist
python312Packages.mizani
python312Packages.mizani.dist
python312Packages.plotnine
python312Packages.plotnine.dist


Figure size not available in plot_fwhm_resolution

Figure size is not mentioned in the function. So have to fix it.

fixed in ad7432cdaf6728747d3ca60a0b5c65b51636e6aa


fixed dashbuilder jobs

MERGE after https://github.com/dashbuilder/dashbuilder/pull/414

@mbiarnes this in conflict now. Are the changes still valid?

@psiroky yepp - will be fixed by https://github.com/kiegroup/kie-jenkins-scripts/pull/109/files -
the renaming to $kieVersion is for running the job alone - without running the parent job, that "transfers" the value kieVersion, before. The script https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/script/release/kie-wbSmokeTestsMatrix.sh doesn't use the value releaseVersion. As I didn't run the jobs seperately they always get the right value. Last week I run this job alone and it didn't run because of the missmatch of releaseVersion and kieVersion. This PR can be closed.


LabSampleCode error in the AddPoint form

@denvaar and I finally isolated the issue with adding points from a csv and the tool worked for me. However, the LabSampleCode is giving a warning flag (red X) for the uploaded NULL values. If I go in and edit the value and set to NULL, the error goes away. I'm wondering if this also has to do with the line break character as it is the last field in a line.

Amber, can you check if there is an extra space character in front of the NULL values. As I have been updating some things, I've found that sometimes there was a hidden space before NULL.

I don't see any extra space in the file that I was using.

Resolved by @denvaar


MAINT: special: deprecate orthopoly1d

The orthopoly1d class does three main things:

Lets you evaluate orthogonal polynomials
Lets you get roots and weights for Gaussian quadrature
Gives you coefficients of orthogonal polynomials in the power basis

The first two things can be done directly with the eval_* and *_roots functions. The third thing is unstable since the coefficients are constructed from the roots of the polynomial. One could fix the situation by making a new class that subclasses numpy's polynomial and constructs the polynomial directly from its coefficients, but IMO this is not worth it: when does one actually need the power-basis coefficients of an orthogonal polynomial? (Note that for arithmetic with series of orthogonal polynomials there's already numpy.polynomial.chebyshev et. al.)
Instead this deprecates orthopoly1d and requests that users call the eval_* and *_roots functions directly.
Closes gh-1777; related to gh-6586.
Edit: at this point closes gh-6586 too.

The quadrature etc. tests may be worth "porting over" from the deprecated framework.

The quadrature tests are all in--the only aspect of orthopoly1d they were using was the weight function, which has been switched out. What's getting thrown out is the tests that compare coefficients constructed from roots to data, which don't seem worth keeping around?

I actually like weight_function being somewhere together with _roots, weights and eval_. Saves a bit of fuzzing around to figure out factors of two or q vsq-1s in definitions.
Maybe we should add some replacement sugar. Something along the lines of
class AbstractOrthoPoly(object):
    def roots_and_weights(self):
        raise NotImplementedError

    def weight_func(self, x):
        raise NotImplementedError

   def __call__(self, x, out=None):
      """This does *not* convert to the power basis."""
       raise NotImplementedError

    def to_poly_basis(self):
        """Exposition only. Return a `np.polynomial`.  Do NOT use for evaluation.  """
       raise NotImplementedError

class HermiteOrthoPoly(AbstractOrthoPoly):
       def __init__(self, n):
           self.n = n

       def roots_and_weights(self):
           return h_roots(self.n)

       def __call__(self, x, out=None)
           return eval_hermite(self.n, x, out)

      def weight_function(self, x):
          return np.exp(-x**2)

      def to_power_basis(self):
        ....

Or, we could add the weight functions as public functions in scipy.special.
They're very simple but may be useful to have so that you don't have to re-type them.

Unrelated to above discussion, but how inconceivable would it be back-compatibility wise to deprecate the current *_roots functions and rename them to be more consistent with the eval_* functions?
e.g. changes like
p_roots -> legendre_roots
which would match with eval_legendre.

Having matching names would IMO be better. Not sure whether roots_legendre or legendre_roots, though.
The *roots functions were added to the documentation only recently in 142277e8fae. However, they have been public since b618415241c2f and I think also used in the wild. I think deprecation is possible if we want to rename them for consistency --- but maybe with a comment in the source that we will keep these aliases around for a long time (ie. not scheduled for removal currently).

New changes:

Added weight functions as ufuncs
Renamed the *_roots functions (but kept the old ones around and deprecated them with a note in the code to not remove them)
Added a section to the tutorial about orthogonal polynomials

An example of the new naming scheme:
eval_legendre - evaluate Legendre polynomials
roots_legendre - roots and quadrature weights for Legendre polynomials
weight_legendre - weight function for Legendre polynomials
If there's a strong push for also wrapping everything in an object then I'll do that too. (But will wait to gauge public opinion. We're currently at +1 from @ev-br)

I won't press for the wrapper classes, triplets of _roots, _eval and weight_funcs are fine for me, as long as the usage is documented and the functions are cross-linked in the docs.

I'm putting off the release notes because there's yet one more deprecation I'd like to broach.
Currently there's a public submodule special.orthogonal which mirrors the orthogonal-polynomial functions in special, e.g. there's special.eval_legendre as well as special.orthogonal.eval_legendre. AFAICT orthogonal is undocumented (though it looks like it used to be the default way of accessing these functions?), can we deprecate the entire submodule?

Our policy of prefixing private modules with _ wasn't always in place, and it's not a very widely adopted Python convention for modules. There are a number of modules in Scipy which are intended to be private but are without underscore. The actual API surface is defined in https://github.com/scipy/scipy/blob/master/doc/API.rst.txt. Of course, there is some code in the wild that imports stuff from private modules, despite them having never been documented.
There's an example of deprecating modules here:
https://github.com/scipy/scipy/blob/master/scipy/linalg/calc_lwork.py
So it's OK in principle to do, but in this case it may not be that urgent to do, since we are not removing orthogonal.py.

Now:

The "See Also" sections for the *_eval, *_roots, and *_weights functions link to each other.
The tutorial has an example
The release notes have been updated

Won't try to do anything about deprecating orthogonal, so we'll just leave the eval_* imports at the end lurking around.
The documentation could still be improved (most notably adding "Parameters" and "Returns" sections in the *_eval functions), but this is already massive so I'm removing the "needs-work" label. (Which I might regret since Travis isn't finished yet.)

mainly a question (I'm not sure I understand correctly in skimming this PR):
Will hermite and similar from scipy.special import hermite, chebyt still return some polynomial objects or not? i.e. are those deprecated without direct alternative in scipy?
(I have some sandbox code that was written a long time ago, before numpy.polynomial. My code was never updated but still seems to runs fine. It uses only low order polynomials.)

Will hermite and similar from scipy.special import hermite, chebyt still return some polynomial objects or not? i.e. are those deprecated without direct alternative in scipy?

They will be removed, and there will be no replacement function that returns a polynomial object. The replacement is using the eval_*, roots_* and weight_* functions directly.

(I have some sandbox code that was written a long time ago, before numpy.polynomial. My code was never updated but still seems to runs fine. It uses only low order polynomials.)

Even high order polynomials would work fine as long as they we just being used for evaluation and getting roots/weights since the __call__ method was overridden by the eval_* functions. Problems would pop up when doing polynomial arithmetic with high degree polynomials.
To try and summarize: orthopoly1d was good for three things: evaluation, getting roots/weights, and weight functions. Those will be separate functions. If was not good for polynomial arithmetic, so this removes the temptation to try and do that.

It was not good for polynomial arithmetic, so this removes the temptation to try and do that.

But that was my main usage, after estimating the coefficient for the linear combination of orthogonal polynomial basis functions, it's easy to evaluate at new points and have available the other methods that polynomials provide.
I don't want to write a wrapper for the different methods myself, so that might mean switching to numpy.polynomial.
(maybe it's a bit like taking away numpy.linalg.inv because you should never use the matrix inverse. We just replaced numpy.linalg.inv by an svd in statsmodels for one of the central calculations, but inv worked happily for 7 years.)

I'm -0 because for new users numpy.polynomial should work well enough (I don't have enough experience with it to tell.)
as background: When I worked with the orthogonal polynomials, I had very little background, and the applied literature used mainly the standard polynomial representation. It was relatively easy for me to figure out how to work with the scipy.special polynomials, while doing everything from scratch would have been above my knowledge. (The only problem I had was with figuring out the orthonormal version of the polynomials.)
The question is what's the easy usage when we don't know or don't want to worry about numerical precision details.

But that was my main usage, after estimating the coefficient for the linear combination of orthogonal polynomial basis functions, it's easy to evaluate at new points and have available the other methods that polynomials provide.
I don't want to write a wrapper for the different methods myself, so that might mean switching to numpy.polynomial.

A good idea: numpy.polynomial.chebychev.Chebychev, numpy.polynomial.legendre.Legendre, numpy.polynomial.laguerre.Laguerre, numpy.polynomial.hermite.Hermite, and numpy.polynomial.hermite_e.HermiteE do a much better job of this. They do fitting and provide accurate evaluation of series of orthogonal polynomials.

The question is what's the easy usage when we don't know or don't want to worry about numerical precision details.

Use the numpy versions. I added a note to the tutorial about using them, but I should probably add it to the main documentation too so that it's very visible.

As a silly example of how pleasant it is to use the numpy stuff:
>>> import numpy as np
>>> from numpy.polynomial.chebyshev import Chebyshev
>>> x = np.linspace(-1, 1, 200)
>>> y = np.exp(x)
>>> series = Chebyshev.fit(x, y, 100) # least squares fit of a 100 degree Chebychev series
>>> np.max(np.abs(y - series(x)))
1.3100631690576847e-14

The documentation for the eval_* functions is now complete. (Full definitions of functions and proper "Parameters"/"Returns" sections.)

Does anyone have opinions on renaming the weight_* functions to weightfun_*? e.g.
weight_jacobi -> weightfun_jacobi.
If a function were called weights_jacobi then I would expect it to compute the quadrature weights for Gauss-Jacobi quadrature, and I'm worried that weight_jacobi is too similar.

There are a number of pieces of information one could want about each family of orthogonal polynomials:

the weights
the roots
the evaluation method
the interval
the recurrence relation

It would be nice if these were all associated in some way, perhaps in a factory function that took n as input and provided an object wrapping up the above information for that n. That's what orthopoly1d currently is, with a side order of making the power-basis coefficients available. I certainly don't mind dropping the power basis representation, but in your proposed interface, where is the interval information? Is there any way to specify a family of orthogonal polynomials, say to a quadrature routine?
The recurrence relation is currently not available, and it's not really clear how to make it so in a manageable way, but it would be useful for someone who had (say) a polynomial expressed in an orthogonal-polynomial basis who wanted to evaluate it using Clenshaw's algorithm.

Ok, let's see if we can reach a consensus. What if we:

Introduce a new orthogonal polynomial object that doesn't inherit from poly1d or polynomial which wraps the appropriate eval_*, root_*, and weightfun_* functions and also has a domain attribute to describe the interval. (Use the name domain for compatibility with numpy's Polynomial.)
When possible, allow the user to do arithmetic with orthogonal polynomials by casting them to the appropriate numpy orthogonal polynomial series first (the resulting object would also be a numpy orthogonal polynomial series). This would work for Legendre polynomials, Chebyshev polynomials of the first kind, Legendre polynomials, Laguerre polynomials, and Hermite polynomials and raise a NonImplementedError for the others.

Thoughts?

The recurrence relation is currently not available, and it's not really clear how to make it so in a manageable way, but it would be useful for someone who had (say) a polynomial expressed in an orthogonal-polynomial basis who wanted to evaluate it using Clenshaw's algorithm.

This seems like it would fit better as an enhancement to the numpy stuff since it already provides several orthogonal polynomial series and evaluates them with Clenshaw recursion.

NumPy Polynomial uses domain for the fitted data and  window for the natural domain of the polynomial that the data is mapped to. Hmm, I don't know if there is a generally accepted name for what we want here. If the weight function is zero outside the interval of integration, it could be called the support.

The numpy.polynomial.chebyshev.Chebyshev doc says that domain is

Domain to use. The interval [domain[0], domain[1]] is mapped to the interval [window[0], window[1]] by shifting and scaling. The default value is [-1, 1].

so isn't domain the natural domain? We should probably make shifting and scaling to arbitrary intervals work, so we should be able to piggyback on the numpy notation.

Nope. For Chebyshev polynomials the domain is mapped to [-1, 1] by affine tranformation and evaluated there. In this case the window is [-1, 1], and domain is where the unmapped data sits.

The default value of the domains is also set to [-1, 1] so that the result is an ordinary unscaled and unshifted Chebyshev polynomial, useful for pedagogical purposes, but when used to represent data the domain will generally be where the data unless specifically chosen otherwise.

After starting to write the object-oriented interface I'm feeling more bearish about the idea, so maybe I'll push back a little.
About quadrature, in particular

Is there any way to specify a family of orthogonal polynomials, say to a quadrature routine?

A quadrature routine needs roots, weights, and possibly the interval on which the polynomials are orthogonal. Two of those things are provided already by the roots_* functions, what if we add an option to also return the interval and let a quadrature routine accept a callable? If we go for an object-oriented design then a user would need to provide an evaluation function and a weight function too. (Unless they were optional, but then we're essentially asking them to provide a roots_* function and calling it something else.)

I'm not hung up on an object-oriented framework; for one thing, it's not clear whether the objects should be for families or individual polynomials. It's just that the possibility of doing other things with scipy's orthogonal polynomials came up in discussions of quadrature and ODE solving.

Can we leave the question of an object-oriented framework open for now? If there's consensus that orthopoly1d should be deprecated, then we don't have to replace it with something right away. Perhaps as things advance on the quadrature/ODE solving fronts it will become more clear what kind of object we want. Let me just say that I'm not opposed to an object-oriented framework in principle; I'm just not sure yet what it should look like to be useful and not a lot of boilerplate. I also don't see the changes here as precluding an object-oriented interface since I think there should be a ufunc interface regardless.

@aarchiba: what if the roots_* functions returned a lightweight object (named tuple or similar) called maybe GaussQuadInfo which bundled together the roots, weights, sum of the weights, and quadrature interval? Then something like fixed_quad could be extended to something like fixed_quad(..., method=None, ...) where method could be a string parameter or an instance of GaussQuadInfo.
What were the ideas about using orthogonal polynomials in ODE solving?

After thinking about this a little longer:

This PR is way too bloated; reviewing it is going to be a pain.
I'm going to close this and break it into chunks, starting with the small uncontroversial parts like improving the documentation.
Maybe by the time all the current bits are cleaned up the correct object-oriented API will be more clear.

A lightweight return object seems sensible - though keep in mind that an adaptive or Romberg quadrature will need to be able to extract it for many ns, so you'd want to pass a factory function of some kind.
The use in ODE solving is that some methods are "collocation methods", that is, to extend the solution forward, they search for a polynomial whose derivative matches the ODE's vector field at specified times - and those times are the zeros of an orthogonal polynomial. This polynomial can also be used to interpolate the solution between stopping points (though it can be of lower order than you want). The descriptions I have read all seem to use the power basis and don't worry about numerical instability; to be fair, they're using order 8 or 12 at most. So really, all they need are the roots, and often they'll just type in values from a table (or mpmath).

Passing thought, it should be possible to make a class factory that produces numpy polynomial classes given the recursion relationship, the support of the weight function, and perhaps the integration/differentiation formulas.


Push-pull based batched dataflow.

This is a mock-up of a push/pull-based dataflow runtime with built-in batching. The main classes are now in pipeline.operator -- see Operator, Stream, etc.
Could use better names. All tests pass.

@edgan8 @sahaana @kexinrong: following our convo

There are at least three high-level questions to discuss:

If an operator wants to throw an exception, where/how should it do so? This is most obvious in the SQLIngester components, where we often want to delay connecting to the server until necessary. (It's a little awkward to connect at construction time...)
What nomenclature do we want for processing elements? (Right now: Operator, UnaryOperator; I'm thinking: Processor?) For batches? (Right now: Stream, but this is overloaded with the new Java 8 API.)
I've stubbed out initialize and shutdown methods for now but don't call them. Maybe okay, will definitively be useful in the future. Do we like this design?

If an operator wants to throw an exception, where/how should it do so? This is most obvious in the SQLIngester components, where we often want to delay connecting to the server until necessary. (It's a little awkward to connect at construction time...)

Now throws in the operator.

What nomenclature do we want for processing elements? (Right now: Operator, UnaryOperator; I'm thinking: Processor?) For batches? (Right now: Stream, but this is overloaded with the new Java 8 API.)

MBStream, MBConsumer, MBProducer

I've stubbed out initialize and shutdown methods for now but don't call them. Maybe okay, will definitively be useful in the future. Do we like this design?

Keeping them for the future.

@edgan8: these address your comments.

LGTM, pipeline structure looks great, percentileclassifier and csvingester look good!
I think DumpClassifier as a wrapper now class is pretty redundant now since we can access the output of the classifier directly, but I can do that in a future diff to improve the dumping logic.

@edgan8: Thanks. Agreed that we can remove DumpClassifier later.


bounded caches

Hi there,
I've been using this great library for some time now, thanks for opening it up to the public!
My use case involves large amounts of data, so I had to change the library slightly to be able to use a bounded cache. I have made it configurable so that each type of request can either use a bounded cache of a given size, or an unbounded cache.
In order to configure it, I have added an additional typeclass that has a DataSource has to be an instance of. It has a single function, cacheSize, that determines the size of the cache for each request (which may be infinite).
If this is useful to other people, I'd be glad to do a pull request. Notice however, that this would be a breaking change, since all DataSources have to add an instance of the new typeclass (which is easy to do).
I have not yet added tests that check that the cache stays within the specified bounds, nor done benchmarks (but it's on my agenda).
Best,
Philipp

I can understand the need to limit the cache size in certain use cases.  However, as soon as we stop caching everything, we lose the nice replayability property that Haxl has now: the cache is a complete record of the execution, and the request can be replayed without fetching any data.
So I'm open to doing this so long as we can make it non-invasive, and make it clear that it breaks replayability.

I agree, caching everything should stay the default, since that is the typical use case.
I'll add a default implementation that chooses an unbounded cache and make it explicit in the docs that changing the default sacrifices replayability, before opening a pull request.


Making the Check Repo analysis logic re-usable

@shawnps @hermanschaaf

@tariq1890 just FYI, we've been having a lot of issues on the server recently, and we reverted this change to see if it's related. I'm wondering if maybe the boltdb is not closing properly.

Sure! I'll have a look as well.

Still trying to find out why this would cause an issue. Do you have any server logs that will help with the analysis?


Update akka-persistence-cassandra, ... to 0.99

Updates

com.typesafe.akka:akka-persistence-cassandra
com.typesafe.akka:akka-persistence-cassandra-launcher

from 0.62 to 0.99.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "com.typesafe.akka" }]

labels:

For the record: Upgrading from 0.62 to 0.80 or later requires some migration steps.
https://doc.akka.io/docs/akka-persistence-cassandra/0.99/migrations.html#migrations-to-0-80-and-later

@guersam yeah, I know. Got to exclude akka-persistence-cassandra from Scala Steward watch.


mormalize per_page

fixes #3490

Missing closes #3490 in the PR description to close the issue automatically

Missing closes #3490 in the PR description to close the issue automatically

Thanks! I just added this.


pythonPackages.pytest_3: fix build

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/64440
cc: @peti
Things done

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

[X] NixOS
[X] 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 nix-review --run "nix-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
[X] Fits CONTRIBUTING.md.

Sorry for the delay, I've added pluggy_0_8.
pytest_3 tests are failing with pluggy>=0.9, because pluggy made changes to PluginManager.load_setuptools_entrypoints; it's not related to the python version

@GrahamcOfBorg build pythonPackages.pytest_3 python3Packages.pytest_3

We indeed need to drop pytest_3 then.

Dropping pytest_3 won't help me fix https://github.com/NixOS/nixpkgs/issues/64440, though.


[BUG] 初始化知识库抛异常信息'PGVector' object has no attribute 'connect'

初始化知识库抛异常信息/ Problem Description
'PGVector' object has no attribute 'connect' / Describe the problem in a clear and concise manner.
复现问题的步骤 / Steps to Reproduce

执行 'python.exe .\init_database.py --recreate-vs' / Run 'python.exe .\init_database.py --recreate-vs'
问题出现 / Problem occurs
Traceback (most recent call last):
File "D:\Langchain-Chatchat-0.2.9\init_database.py", line 108, in
folder2db(kb_names=args.kb_name, mode="recreate_vs", embed_model=args.embed_model)
File "D:\Langchain-Chatchat-0.2.9\server\knowledge_base\migrate.py", line 128, in folder2db
files2vs(kb_name, kb_files)
File "D:\Langchain-Chatchat-0.2.9\server\knowledge_base\migrate.py", line 113, in files2vs
kb.add_doc(kb_file=kb_file, not_refresh_vs_cache=True)
File "D:\Langchain-Chatchat-0.2.9\server\knowledge_base\kb_service\base.py", line 129, in add_doc
self.delete_doc(kb_file)
File "D:\Langchain-Chatchat-0.2.9\server\knowledge_base\kb_service\base.py", line 143, in delete_doc
self.do_delete_doc(kb_file, **kwargs)
File "D:\Langchain-Chatchat-0.2.9\server\knowledge_base\kb_service\pg_kb_service.py", line 72, in do_delete_doc
with self.pg_vector.connect() as connect:
AttributeError: 'PGVector' object has no attribute 'connect'

附加信息 / Additional Information
添加与问题相关的任何其他信息 / Add any other information related to the issue.
win10
python version: 3.10.11
Name: pgvector
Version: 0.2.4
Summary: pgvector support for Python
Home-page: https://github.com/pgvector/pgvector-python
Author: Andrew Kane
Author-email<EMAIL_ADDRESS>License: MIT
Location: d:\Langchain-Chatchat-0.2.9\venv\lib\site-packages
Requires: numpy
Required-by:

I find the bug-fix Merge，It‘s work now
https://github.com/chatchat-space/Langchain-Chatchat/pull/2591/commits/205dcd8b396ead6021fa107f5efaf675022b4275


Can T5 be trained on Autotrain?

I tried to use T5 - 'google/flan-t5-base'
But got an error  ValueError: Unrecognized configuration class <class 'transformers.models.t5.configuration_t5.T5Config'> for this kind of AutoModel: AutoModelForCausalLM. Model type should be one of........

t5 is a seq2seq model. you cannot train llm tasks on it


Update secure-apis-using-basic-authentication.md

Fixed a grammatical error

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


Forces https basemaps if https property has been explicitly defined

Fixes #500
@matallo

looks good to me, thanks for the https support, what about adding a small case breakdown in the docs?

Sure thing, I'll add that and merge.


Question: EEG CVPR40 Dataset's Channel Names

https://github.com/perceivelab/eeg_visual_classification/issues/4
I confirmed in the paper that the EEGCVPR40 Dataset you used was acquired using the same measurement method as EEGImageNet. The link above is the address of a question posted in the issue category of Github for the EEG-ImageNet Dataset. When you enter the link, the channel names are indicated and the order in which the 128 channels shown in the picture below are located. I'm also curious as to whether the CVPR40 Dataset has the same or different channel order as presented here, and whether microvolts are the same as EEGImageNet.

The link above is the address of a question posted in the issue category of Github for the EEG-I

Hi @gyuseok0917 , CVPR40 is actually the same dataset that is used in eeg_visual_classification. For the convenience, in our work we just name it so.


Snapshot purge progress support

In order to address https://github.com/longhorn/longhorn/issues/581 and provide better usability, we want to provide snapshot purge (snapshot rm from manager's POV) progress support.

Move the snapshot purge operation to the sync agent server.
Store the progress information in the sync agent server.
Report the progress using longhorn snapshot purge-status command.
Prevent multiple snapshot purge happens at the same time.

@smallteeths Backend merged.

@ttpcodes Can you document the API?

I've already sent the API over Slack via DM.

Validation: PASSED
Steps to test:
Create a volume with size 64 GB, attach it to a node, format it, and mount it to a directory on attached node.
Create a datafile with size 32 GB, and on Volume Detail page. create a snapshot
repeat previous step with volume sizes 16 GB & 8 GB
Use kubectl -n longhorn-system get lhe  -o yaml Find engine process port in status.port and related instance manager in status.instanceManagerName
Use kubectl -n longhorn-system exec -it  bash to enter instance manager pod.
Run longhorn engine cmd longhorn --url localhost: snapshots`. Get snapshots IDs
Remove all snapshots using longhorn engine cmd longhorn --url localhost: snapshot rm <snapshot_id>
UI: on Volume Detail page. create a snapshot.
UI: on Volume Detail page. Delete last created snapshot.

Expected result:

Purge progress should appear indicating if the purge process is completed.
only one snapshot, the last one is shown in the system hidden.


DeveloperGuide: update product scope

DeveloperGuide: update product scope

Target user profile
Value proposition

Coverage remained the same at 93.746% when pulling c350375d9b3437001049a01c259b247f6835e33a on truegitnovice:DG_ProductScope into dd71fc10bfe1df78ceedd483d01771b08a04e87c on cs2113-ay1819s2-t09-1:master.

Thanks for the great work!


Remove images on service/doc delete

Description of the feature
We store images in /media, we need to remove them when they are not use anymore
Describe the solution you'd like
Delete when a service or a documentation is delete

Done and merged in dev


🐛 [firebase_crashlytics] Errors reported with recordError have custom keys mixed up

Bug report
Describe the bug
When you report two errors with recordError, close to each other, their custom keys can get mixed up.
import 'dart:convert';

import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_crashlytics/firebase_crashlytics.dart';
import 'package:flutter/material.dart';

Future<void> main() async {
  Crashlytics.instance.enableInDevMode = true;
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();

  Crashlytics.instance.setString("foo", "123");
  await Crashlytics.instance.recordError(
    "error1",
    StackTrace.current,
  );

  Crashlytics.instance.setString("foo", "456");
  await Crashlytics.instance.recordError(
    "error2",
    StackTrace.current,
  );

  runApp(MyApp());
}

Steps to reproduce
Steps to reproduce the behavior:

Run the code above
Wait till crash report is sent
Check the Crashlytics console

Same issue, same instance, "Keys" tab:

Expected behavior
Custom keys should not mix up.
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.1, on Mac OS X 10.14.6 18G6020, locale en-PL)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
[!] Android Studio (version 4.0)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[!] IntelliJ IDEA Ultimate Edition (version 2020.2)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] IntelliJ IDEA Community Edition (version 2020.2)
[!] VS Code (version 1.47.3)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 3 categories.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.9.0
Flutter SDK 1.20.1
test1 1.0.0+1

dependencies:
- cupertino_icons 0.1.3
- firebase_core 0.5.0 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.1.4+1 [flutter stack_trace]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.4.2 [collection]
- boolean_selector 2.0.0 [source_span string_scanner]
- characters 1.0.0
- charcode 1.1.3
- clock 1.0.1 [meta]
- collection 1.14.13
- fake_async 1.1.0 [clock collection]
- firebase 7.3.0 [http http_parser js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.0 [firebase firebase_core_platform_interface flutter flutter_web_plugins meta js]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- http 0.12.2 [http_parser path pedantic]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- js 0.6.2
- matcher 0.12.8 [stack_trace]
- meta 1.1.8
- path 1.7.0
- pedantic 1.9.0
- plugin_platform_interface 1.0.2 [meta]
- quiver 2.1.3 [matcher meta]
- sky_engine 0.0.99
- source_span 1.7.0 [charcode collection meta path term_glyph]
- stack_trace 1.9.5 [path]
- stream_channel 2.0.0 [async]
- string_scanner 1.0.5 [charcode meta source_span]
- term_glyph 1.1.0
- test_api 0.2.17 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.2.0 [collection]
- vector_math 2.0.8

Pull Request solving this issue: https://github.com/FirebaseExtended/flutterfire/pull/3415

A new Crashlytics plugin has now landed on master which should solve this issue.
Checkout the migration guide to get started on upgrading to the new Crashlytics plugin: https://firebase.flutter.dev/docs/migration/


issue installing..

I added integration and logged in with the right information, got these errors
2023-03-15 18:23:40.963 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.ecowater_softener.sensor
2023-03-15 18:23:40.967 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform ecowater_softener.sensor: Platform not found (Exception importing custom_components.ecowater_softener.sensor).

Did you manage to resolve this issue @Polcdev?

I will close this issue due to a lack of activity. Feel free to re-open it if you need @Polcdev!


merge package from arlac77/npm-package-template

package.json

chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

LICENSE

chore(license): add current year 2019

Codecov Report

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

@@           Coverage Diff           @@
##           master     #328   +/-   ##
=======================================
  Coverage   84.11%   84.11%
=======================================
  Files           1        1
  Lines         214      214
=======================================
  Hits          180      180
  Misses         34       34

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 00fdd0e...65686ce. Read the comment docs.

Coverage remained the same at 84.81% when pulling 65686cee9432335048060b8c251680c8d5734c9b on template-sync-1 into 00fdd0eb0ba93f7bc61433c41c255b8984c24cea on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Need Feeedback on a client acting as a local evaluator

I plan to heavily use flagr, unfortunately at  x Billions of request per day, goflagr (that I use as client) takes too much time.
To fix that network issue, I created https://github.com/tkanos/flagrc,
That act as a local evaluator (for all evaluation request except the EntityID ones) :

load and cache the flags (locally in client side)
execute evalFlag to evaluate (in client side)
if it's an entityID request, it fallback to goflagr (that ask to the server)

Do you think that the client/evaluator is a good idea ?
Do you see concepts that can prevent that to fully work ?
If you look at the code (https://github.com/tkanos/flagrc), you will see that I only use flagr functions, to act as much as evaluator as possible :

for the Cache
for the entities
for all functions used by evalFlag and evalSegment
The only exception being evalFlag and evalSegment that I copied/paste in my own code (because this functions are not public in flagr)
Can you make them public I can rely completely on flagr code ?

Thanks for the feedback.

Very interesting use case, we didn't think of embedding flagr as a go package for other go applications before. I think it makes sense and there's a demand for client evaluation. Thanks for the library, and feel free to open PR if you want some functions to be public.
In general, I'd like to have a clear picture of client-side evaluation, so here are some open questions:

How do we handle client side vs server side evaluaiton in general?
What feature parity we'd like to keep between client side and server side?
How do we sync flag updates to client side?
How do we keep client side update to date with new evaluation logic from server side?
How do we support languages other than go?

This could be a good starting point. Originally I was thinking of sidecar deployment approach, or compile flagr client to wasm and can be included in any language that can support wasm.

- How do we handle client side vs server side evaluaiton in general?
For now all that is not EntityID, is done in client side. (once I finish that part, I will maybe do the EntityID configurable in client side as well)
- What feature parity we'd like to keep between client side and server side?
The server is only use for :

EntityID evaluation (at least for now)
Evaluation of client that doesn't have the local evaluator
Update all the others evaluator (aned client as well) thanks to the endpoint /export/eval_cache/json.

- How do we sync flag updates to client side?
I use the json_http flagr mechanism, that will call each EvalCacheRefreshInterval (3 sec by default) the server /export/eval_cache/json endpoint.
- How do we keep client side update to date with new evaluation logic from server side?
For flagrc, I took flagr as a package, so If flagr changes its logic, most of the time, I only need to synchronize the modules.
- How do we support languages other than go?
Not being part of checkr, I fortunately don't have to answer that question :D, But if I need the same behavior for one of the language I know, I think I will have to implement all by myself (not being able to use flagr internal package/logic)
So I'm finishing the flagrc code  (https://github.com/tkanos/flagrc), when it's done :

I will test it, in some of my internal projects
maybe do the EntityID evaluation (confgurable) in client side
Dinr the beer of victory :D

Hello @zhouzhuojie
So after some tests on github.com/tkanos/flagrc, here are my conclusions.
As you know I have to handle billions of connection per day, and I should be fast, unfortunately with goflagr client, I had to have x*10 flagr servers (each server costing y$), to handle billions of request. And it was slow (20 ms/op).
Using github.com/tkanos/flagrc, I only need 1 flagr server. (so economy of [(x10y)-y]$), and it is super fast (4000 ns/op) soI can handle even more connection.

goflagr
flagrc

servers
x*10
1

cost
x10y
y

speed
20 ms
4000 ns

For now I only did my tests for request without EntityID, Tomorrow I should be able to do the tests using EntityID (but it should be ok), and release the final version of flagrc (with all features).
btw, I am absolutely fan how you handle the Distribution.


Saving Getting code actions from` happening all the time

Getting frequent Saving Getting code actions from from VSCode.
VSCode freezes, the file is NOT saved. It seems to happen for Prettier, Eslint, React plugins, so many. This didn't used to happen, now it happens all the time.
Is there a way to STOP this from happening?

Version: 1.52.1
OS Catalina

I have the exact same issue.

I have the exact same issue.

Do you also see this if you disable the ESLint extension?. If so can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

Do you also see this if you disable the ESLint extension?. If so can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

We're experiencing the same issue, VSCode is starting 4 Code Helper (Renderer) threads all at around 100% CPU and never finishing.
It only happens when ESLint is enabled.
In our case we have it enabled for Vue files with TS support. It might be related to the vue plugin.
I can't share our business repo unfortunately.

We're experiencing the same issue, VSCode is starting 4 Code Helper (Renderer) threads all at around 100% CPU and never finishing.
It only happens when ESLint is enabled.
In our case we have it enabled for Vue files with TS support. It might be related to the vue plugin.
I can't share our business repo unfortunately.

The DutchCoder. Without steps to reproduce hard to tell why it is not working. What is strange is the fact that all 4 processes are at 100%. ESLint only starts one server. So this sounds like a broader problem. Can you provide me with the command line of the 4 processes.

The DutchCoder. Without steps to reproduce hard to tell why it is not working. What is strange is the fact that all 4 processes are at 100%. ESLint only starts one server. So this sounds like a broader problem. Can you provide me with the command line of the 4 processes.

@dbaeumer I also had "PropTypes generate" extension just like @stoplion so first I tried to disable it to if that somehow caused this issue. I got the error with just ESlint too.
Unfortunately I can't share the repos I'm working on but I'm getting this on multiple repos. It's not happening all the time, most of the time ESlint is pretty smooth, but occasionally something triggers this and the error shows up with every save.

@dbaeumer I also had "PropTypes generate" extension just like @stoplion so first I tried to disable it to if that somehow caused this issue. I got the error with just ESlint too.
Unfortunately I can't share the repos I'm working on but I'm getting this on multiple repos. It's not happening all the time, most of the time ESlint is pretty smooth, but occasionally something triggers this and the error shows up with every save.

@wunnle thanks. Would you be able to distill a case. Without any steps it is very hard to track this down.

@wunnle thanks. Would you be able to distill a case. Without any steps it is very hard to track this down.

I mark this as a dup of #1055 which has more info.


Marker pauses between movements

First of all, I am a big fan of this library, and the issue I'm about to post may be related to the "Improve speed" future objective at the end of the documentation. I am using Google Maps' Roads API to generate a path of points fixed along a road, and am using this library to move the marker from point to point smoothly. I am trying to move the marker with a uniform 'velocity', so am adjusting the marker's duration attribute (with setDuration) before each movement after calculating the distance to the next point an multiplying by 10. So if it's 10m between points A and B, the duration would be 100ms. If it's then 100m between B and C, the duration would be 1000ms, effectively matching the speed of travel of the shorter distance. It's a little scrappy, but it serves a purpose for the moment.
My issue is that the smooth movement is interrupted, because between each movement the marker pauses for a brief moment. My fear is that this is simply a limitation of the library and there's not much that can be done about it, but if you have any solutions to stop this stop-start movement, I would be very happy to hear them.

Never mind - I think this was my fault and I was able to fix it.


Add option to skin weight export to turn off normalize weights

Currently vetala forces normalize weights when importing.  This can slow down heavy props or sets that have tons of skin weights.  Having an option in the skin weight data to turn off normalize (and make sure your weights are normalized before export)  would help speed up heavy assets

On one example of about 10 objects the import time went from 0.23 to 0.3.  If you have 1000s of objects this can add make it significantly slower, especially if your skin weights are already normalized.


docs(proxy events): fix new syntax

Description
fix proxy events documentation
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Coverage remained the same at 97.531% when pulling 79306c62480ec0c966c95290fabdd0e736f56938 on fix-proxy-events-docs into d6f0d1735e4f8104495d9488b208dcc11425733e on v3.


squid:S1155 - Collection.isEmpty() should be used to test for emptiness

This pull request is focused on resolving occurrence of Sonar rule
squid:S1155 - Collection.isEmpty() should be used to test for emptiness.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1155
Please let me know if you have any questions.
George Kankava

Automated message from Dropbox CLA bot
@georgekankava, it looks like you've already signed the Dropbox CLA. Thanks!

lgtm!


fix(deps): update module go.opentelemetry.io/proto/otlp to v1.4.0

This PR contains the following updates:

Package
Type
Update
Change

go.opentelemetry.io/proto/otlp
require
minor
v1.3.1 -> v1.4.0

Release Notes

open-telemetry/opentelemetry-proto-go (go.opentelemetry.io/proto/otlp)
v1.4.0
Compare Source
Release of the v1.4.0 version of the OTLP, including updated Profiles signal.
What's Changed

Bump google.golang.org/protobuf from 1.34.1 to 1.34.2 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/179
Bump google.golang.org/protobuf from 1.34.1 to 1.34.2 in /slim/otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/178
Bump google.golang.org/grpc from 1.64.0 to 1.65.0 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/180
Bump go.opentelemetry.io/build-tools/multimod from 0.13.0 to 0.14.0 in /internal/tools by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/182
Bump go.opentelemetry.io/build-tools/dbotconf from 0.13.0 to 0.14.0 in /internal/tools by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/181
Bump github.com/grpc-ecosystem/grpc-gateway/v2 from 2.20.0 to 2.21.0 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/184
Bump github.com/grpc-ecosystem/grpc-gateway/v2 from 2.21.0 to 2.22.0 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/185
Bump google.golang.org/protobuf from 1.34.2 to 1.35.1 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/186
Bump google.golang.org/protobuf from 1.34.2 to 1.35.1 in /slim/otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/187
Bump github.com/grpc-ecosystem/grpc-gateway/v2 from 2.22.0 to 2.23.0 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/188
Bump google.golang.org/protobuf from 1.35.1 to 1.35.2 in /otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/191
Bump google.golang.org/protobuf from 1.35.1 to 1.35.2 in /slim/otlp by @dependabot in https://github.com/open-telemetry/opentelemetry-proto-go/pull/192
Switch from dependabot to renovate by @dmathieu in https://github.com/open-telemetry/opentelemetry-proto-go/pull/196
Document and test supported versions of Go by @dmathieu in https://github.com/open-telemetry/opentelemetry-proto-go/pull/205
Prevent the use of toolchain in go.mod by @dmathieu in https://github.com/open-telemetry/opentelemetry-proto-go/pull/202
Update module go.opentelemetry.io/build-tools/multimod to v0.15.0 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/201
Update module golang.org/x/text to v0.20.0 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/206
Update google.golang.org/genproto/googleapis/rpc digest to e639e21 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/198
Update module golang.org/x/net to v0.31.0 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/203
Update google.golang.org/genproto/googleapis/api digest to e639e21 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/197
Update module github.com/grpc-ecosystem/grpc-gateway/v2 to v2.24.0 by @renovate in https://github.com/open-telemetry/opentelemetry-proto-go/pull/209
Remove compat from go mod tidy by @florianl in https://github.com/open-telemetry/opentelemetry-proto-go/pull/213
Clean the gen folder before running tidy by @dmathieu in https://github.com/open-telemetry/opentelemetry-proto-go/pull/211
Don't run clean-gen twice by @dmathieu in https://github.com/open-telemetry/opentelemetry-proto-go/pull/214
Upgrade proto to v1.4.0 by @florianl in https://github.com/open-telemetry/opentelemetry-proto-go/pull/193

New Contributors

@dmathieu made their first contribution in https://github.com/open-telemetry/opentelemetry-proto-go/pull/196
@renovate made their first contribution in https://github.com/open-telemetry/opentelemetry-proto-go/pull/201

Full Changelog: https://github.com/open-telemetry/opentelemetry-proto-go/compare/v1.3.1...v1.4.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: dagger/go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: dagger/navecd imports
	dagger/navecd/internal/dagger: package dagger/navecd/internal/dagger is not in std (/usr/local/go/src/dagger/navecd/internal/dagger)


no-unused-variable does not recognize destructuring assignment

Bug Report

TSLint version: 3.6.0
TypeScript version: 1.8.9
Running TSLint via: SublimeLinter

TypeScript code being linted
class Foo {

  private bar: string = 'bar';

  public method(): void {
    const { bar } = this;
    console.log(bar);
  }

}

with tslint.json:
"no-unused-variable": true

Actual behavior
Error: unused variable: 'bar'
Expected behavior
should detect that bar is used through destructuring assignment

Hi @jnu, the warning comes because of the line:
private bar: string = 'bar';

That bar, is in fact, unused. ;)

what? yes, it is used.
compare the semantically equivalent:
class Foo {

  private bar: string = 'bar';

  public method(): void {
    console.log(this.bar);
  }

}

there is, correctly, no lint error in this case. the linter appears not to be catching that bar is used through destructuring assignment.

Whoops, my bad! I just skimmed your code for this.bar and wasn't really paying attention to how you were in fact using it...

:) thanks!

So this is actually a somewhat complicated issue... the tricky thing there is that the bar in const { bar } = this actually refers to two things: the identifier of the field on this and the identifier of the local variable it creates.
To determine if a variable is used, we use an API of TypeScript that finds all the references to an identifier. (This is the same API that atom-ts or vscode uses when you select a variable and choose something like "find references").
This is a confusing scenario, because it can be unclear what should happen. And in fact, there are many TS issues about similar situations:
https://github.com/Microsoft/TypeScript/issues/6459
https://github.com/Microsoft/TypeScript/issues/6312
etc.
There's been a recent PR that loos helpful and suggests that this situation may have been fixed: https://github.com/Microsoft/TypeScript/pull/7945
Essentially this is an issue that we just have to hope changes in TS, which will fix things here in TSLint. If there's a definite bug in TS (even given the changes above), I'll file an issue with them.

great, thanks for looking into it!

Should be fixed by #2235.


Remove defaults channel?

I'm not fully up-to-date on the changes with Anaconda but it might be best to stick with conda-forge for now?

Yes, that's the current recommendation

Gotcha -- thanks!


Question / Feature Suggestion

#[delegate]
pub trait SomeTrait {
type SomeType;
fn some_method();
}
this currently gives me an Error. Are associated types not supported atm?

#[delegate]
pub trait SomeTrait {
fn some_method() -> impl Error;
}
this also does error.

Thank you for the report!
Those are probably a bug.
We will now look into those in more detail.


Homepage formatting

Adding and formatting header and buttons on the homepage

This looks great! This will be looking noice in no time.


Inform users that they don't need all logs enabled at all times

Summary
Discussion in discord demonstrated that some users run their servers with all logs toggled on all the time. While this probably isn't harmful, it does produce hundreds of thousands of lines of log output on any given server, and makes troubleshooting issues difficult.
Proposal
We should add a message to SEGSAdmin's logs window letting users know that log messages only need to be set to true for debugging specific issues. We can enable logMapEvents and logSlashCommands by default, if we must, but the rest can be false.

Could always add a message to the Readme too, cover two bases that way.

Good idea @Stitchified