Timing issue in the TestNonblockingSubmitWithFunc

On some machines this unit would fail due to a timing issue.  Since the Invoke in the loop was using nil as the param, it would (depending on timing) lead to the workers finishing the  (w *goWorkerWithFunc) run() in the range loop over w.args as args would == nil and return.
If an explicit time.Sleep(1 * time.Second) is added before the "	assert.EqualError(t, p.Invoke(nil), ErrPoolOverload.Error()," it is easily reproducible.

name: Pull request
about: Propose changes to the code
title: ''
labels: ''
assignees: ''

1. Are you opening this pull request for bug-fixs, optimizations or new feature?
bug-fix
2. Please describe how these code changes achieve your intention.

stated above
3. Please link to the relevant issues (if any).

n/a
4. Which documentation changes (if any) need to be made/updated because of this PR?

n/a
4. Checklist

[x] I have squashed all insignificant commits.
[x] I have commented my code for explaining package types, values, functions, and non-obvious lines.
[x] I have written unit tests and verified that all tests passes (if needed).
[x] I have documented feature info on the README (only when this PR is adding a new feature).
[x] (optional) I am willing to help maintain this change if there are issues with it later.

Thanks, switched to a waitgroup like the other tests to resolve that read from a closed channel.

Thanks~


Problem when using with InfluxDB.

When I use this lib to generate SQL for InfluxDB, I found it works good, except for that: I can't get the plain SQL.
Today, many databases are using SQL-Like DSL like InfluxDB, but they are using REST API, which needs plain SQL but not ? placeholder and a parameter list.
I think that a method to generate plain SQL is much helpful.

You can interpolate args in the generated sql. In your case, if you're using flavor MySQL, you can call sqlbuilder.MySQL.Interpolate(sql, args) to get a plain SQL without ?.

Oh, thanks, that is helpful~


Question about running all program

Hi,
I came across your article on IEEE, and I'd like to inquire if you could provide more detailed information about this project?
I've carefully examined your code, but I'm still puzzled. I managed to run your network training, but couldn't successfully run your entire net-ekf process.

hi,
this repository is still in a pre-release state. I'm planning on pushing an update to make everything publicly workable in the next couple of weeks


Fix documentation for deprecated args

While reading the API docs, I noticed that some of the deprecation notices seem to have missing pieces. For example, this notice in tf.math.argmax:

I traced the problem to a bug in the @deprecated_args decorator. The message that the decorator generates for docstrings is different from the message it generates for runtime warnings. Instructions that make sense in the context of the runtime warning message don't make sense in the context of the API docs.
This PR makes the deprecation message for docstrings more like the one for warnings. After the changes in this PR, the deprecation notice for tf.math.argmax looks like this:

Overall, this change fixes problems with the deprecation warnings for the following functions:

tf.graph_util.import_graph_def
tf.expand_dims
tf.squeeze
tf.math.argmax
tf.math.argmin

I regenerated the docs on my local copy and checked each of these functions by hand. I also ran regression tests and pylint.
I updated the expected results in deprecation_test.py and added a new test to cover docstrings for functions with 2 or more deprecated arguments.

Thanks!

Nagging Assignee @ymodak: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I think the equivalent of this was already done internally. @frreiss can you check that it's equivalent? I'm sorry we didn't get this in before someone fixed it internally.

Yes, it does appear that a roughly-equivalent set of changes were committed on November 5 from the internal Google branch. Closing out this PR.


struct is not supported in traits or implsor: where canutoipa::path()` be used?

I have an existing warp project that I want to add an OpenAPI spec to. But I had a problem: the handler functions for filters are in traits, so when I tried to use the utoipa::path macro in front of the handler function, I got this compilation error:
error: struct is not supported in `trait`s or `impl`s
   --> cloud_backend/src/crud.rs:465:5
    |
465 | /     #[utoipa::path(get,
466 | |         path = "dataset/",
467 | |         responses(
468 | |             (status = 200, body = String)
469 | |         )
470 | |     )]
    | |______^
    |
    = help: consider moving the struct out to a nearby module scope
    = note: this error originates in the attribute macro `utoipa::path` (in Nightly builds, run with -Z macro-backtrace for more info)

error: implementation is not supported in `trait`s or `impl`s
   --> cloud_backend/src/crud.rs:465:5
    |
465 | /     #[utoipa::path(get,
466 | |         path = "dataset/",
467 | |         responses(
468 | |             (status = 200, body = String)
469 | |         )
470 | |     )]
    | |______^
    |
    = help: consider moving the implementation out to a nearby module scope
    = note: this error originates in the attribute macro `utoipa::path` (in Nightly builds, run with -Z macro-backtrace for more info)

My interpretation of this is that the utoipa::path() macro writes a struct definition, which is then illegal because Rust does not allow those to be defined inside a trait.
Do I have any alternatives here? It would be difficult for me to rewrite the project to extract the handlers out of the trait. Would I have to write stub handlers that call the trait methods, solely for the purpose of being annotated by utoipa?
My ideal option would be if I could annotate Filter objects, because that's the most basic part of my code.
Alternatively--can I write these structs myself? That may be less exciting but would make this work.
I apologize if I misunderstood something; I'm somewhat new to Rust and warp, and I just found out about utoipa today.

If it helps, this is a toy version of what I'm working with:
use async_trait::async_trait;
use warp::Filter;

#[async_trait]
trait Animal {
    const NAME: &'static str;
    const SOUND: &'static str;

    async fn speak_handler() -> String {
        format!("{}", Self::SOUND)
    }
}

struct Dog;

impl Animal for Dog {
    const NAME: &'static str = "dog";
    const SOUND: &'static str = "woof";
}

struct Cat;

impl Animal for Cat {
    const NAME: &'static str = "cat";
    const SOUND: &'static str = "meow";
}

fn generate_animal_endpoint<A: Animal>(
) -> impl Filter<Extract = impl warp::Reply, Error = warp::Rejection> + Clone
where
    A: Send + Sync + 'static,
{
    warp::path("animal")
        .and(warp::path(A::NAME))
        .then(A::speak_handler)
}

#[tokio::main]
async fn main() {
    // GET /animal/dog => 200 OK with body "woof"
    let dog_filter = generate_animal_endpoint::<Dog>();

    // GET /animal/cat => 200 OK with body "meow"
    let cat_filter = generate_animal_endpoint::<Cat>();

    let filters = dog_filter.or(cat_filter);

    warp::serve(filters).run(([127, 0, 0, 1], 3030)).await;
}

Yes, that is actually what happens. The utoipa::path is implemented solely for purpose of decorating free standing functions with it.

My interpretation of this is that the utoipa::path() macro writes a struct definition, which is then illegal because Rust does not allow those to be defined inside a trait.
Do I have any alternatives here? It would be difficult for me to rewrite the project to extract the handlers out of the trait. Would I have to write stub handlers that call the trait methods, solely for the purpose of being annotated by utoipa?

Yes there are 2 ways to get around this and one is as you mentioned to have the stub handlers outside the trait. Or to manually write the path operation. You can see some example from here: https://docs.rs/utoipa/1.0.2/utoipa/trait.Path.html
For example you could implement it manually something like this:
#[derive(OpenApi)]
    #[openapi(
        ...
        modifiers(&CustomPaths)
    )]
    struct ApiDoc;

    struct CustomPaths;

    impl Modify for CustomPaths {
        fn modify(&self, openapi: &mut utoipa::openapi::OpenApi) {
            openapi
                .paths
                .paths
                .insert(String::from("/animal/cat"), PathItem::new(PathItemType::Get,
                        OperationBuilder::new()).build());

            openapi
                .paths
                .paths
                .insert(String::from("/animal/dog"), PathItem::new(PathItemType::Get,
                        OperationBuilder::new()).build());
        }
    }

And of course since it is just a Rust you can organize the code bit better and reuse functions as usual with the manual implementation.

I apologize if I misunderstood something; I'm somewhat new to Rust and warp, and I just found out about utoipa today.

No worries, I'm somewhat new to Rust myself too :joy:

Ah, neat! I had seen the example in Path, but I think what I was missing was the Modify part.
I'll give that a shot and let you know how it goes! Thanks!

Yeah.. Indeed there is no complete example of how to add the path operation using manual implementation. This is indeed something to improve about the docs. And have to admit that the way to add  path items are not super ergonomic at the moment and there is room for an improvement. But anywhow hope that it helps you further.

I wanted to update you--I went on vacation shortly after my original query.
I got finished using this method just recently. It works! But there is a LOT of code to write.
I will have to see how much time I have but I'd like to help this project. But thanks for all you have already!

Thanks for update, I hope you had a good vacation. Yes indeed the manual implementation is really boiler plate heavy. Sure thing all the help is welcome. :)

IDK what the right resolution is here, but I'm going to close it as "resolved" since you answered my question.

Yes probably closed is the correct one to for this. This is quite unique case for declaring endpoints. And does not actually come across with other frameworks that much. It might be worth pondering whether there is something that could be done to improve the handlers in traits support but it won't be a priority.
So far I have no actual solution for them and I only hope that if support for them were to be implemented it would't be a massive rewriting process to the core of the library. But anyway how it has been good and useful library in other aspects. And of course contributions are welcome to improve the library. :)


Patch: Remove duplicate test code for #select edge case on feature/authorization-simple

What does this PR do?

Removes duplicate test code for #select edge case

Note to self: you can finish up this patch, you don't need to test this under a lot of contexts because this is an edge case you're testing, also it doesn't apply to district admins because they bail out early in the authorization tree.

Also don't call JSON in this test.

@alexsoble I pushed a commit fixing this up here: https://github.com/studentinsights/studentinsights/pull/1274/commits/20f54407c5ae3cc95377d99dc1250bac0b697710

@kevinrobinson Oh great. Yep, just saw it. So it looks like this spec was being difficult because there was a real bug in the feature side code. Exactly what we want our specs to do!


cannot get anything when curl

when finished it , I curl  kubectl  get --raw /apis/custom.metrics.k8s.io/v1beta1 | jq and get
{
"kind": "APIResourceList",
"apiVersion": "v1",
"groupVersion": "custom.metrics.k8s.io/v1beta1",
"resources": []
}
the resources is nothing. From the pod ,I get the logs
Response Body: {"kind":"SubjectAccessReview","apiVersion":"authorization.k8s.io/v1beta1","metadata":{"creationTimestamp":null},"spec":{"nonResourceAttributes":{"path":"/","verb":"get"},"user":"system:anonymous","group":["system:unauthenticated"]},"status":{"allowed":false}}

I would start by checking the logs of custom-metrics-apiserver.
Chances are that custom-metrics-apiserver is unable to communicate with Prometheus API.

Any update on this? I am facing the same issue

Any update on this? I am facing the same issue.


RDK-46375-Include the L2 Test in Github Action

Description
Changes Done:

Changed L2 test folder architecture, moved L2 test cases from tests to unit_tests/L2_testing
skipped gui_containers when run in vm
Added test passing count in logs
Enabled only passing tests in runner.py
-  basic_sanity_tests.py
-  container_manipulations.py
-  bundle_generation.py
-  plugin_launcher.py
Fixed SyntaxWarning: invalid escape sequence

Test Procedure

Run in vagrant setup
Run in github workflow.

Type of Change

[ ] L2 test enhancement

Requires Bitbake Recipe changes?

[ ] NA

also, can we rename the "unit_tests" directory to "testing" or just "tests" and then have L1_testing and L2_testing directories under that ?
Having L2_testing directory under "unit_tests" sound a bit wrong.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 87 files pending identification.

Protex Server Path: /home/blackduck/github/Dobby/311/rdkcentral/Dobby

Commit: d332d5291650c52085bea08592f867b9a30c2c31

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 87 files pending identification.

Protex Server Path: /home/blackduck/github/Dobby/311/rdkcentral/Dobby

Commit: 56dbb808f4774aa417fa774720e54fb6e894a969

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 87 files pending identification.

Protex Server Path: /home/blackduck/github/Dobby/311/rdkcentral/Dobby

Commit: 591d8b8e37e9ef30692a98c1518a8904d31d8a40

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: Files being moved

Commit: 591d8b8e37e9ef30692a98c1518a8904d31d8a40


[bug] Could not find the remote named local

>>> git-sweep cleanup --origin=local
Could not find the remote named local

Not sure why it needs a remote named local, it should be able to tell if a branch is local or not without the user having to configure their remotes in a special way.

Hi, not an author of this repo, but one who added a comment in README telling how to clean up local branches. You actually need to add remote named local to make it work, and it's a hack to achieve the desired effect:
git remote add local $(pwd)

Unfortunately this project is dead for a while so feel free to fork it and improve it, especially around local branches. Also Python 3 support is needed already :)


Unclear documentation about manually configuring liqo using CRs

I would like to deploy liqo using gitops principals with ArgoCD.
As the documentation describes for manual authentication :
The authentication process can be manually performed using liqoctl authenticate command or by manually applying the CRs.

Is there an overview of all the resources needed to configure authentication and namespace offloading with liqo?
For instance: In the manual installation steps for creating the nonce  liqoctl create nonce is used. This will create a new namespace and a secret.
I could extract this information, but it's cumbersome.
Environment:

Liqo version: v1.0.0-rc.2
Liqoctl version: v1.0.0-rc.2
Kubernetes version (use kubectl version): v1.30.5
Cloud provider or hardware configuration: BareMetal with Talos
Node image:
Network plugin and version: Cilium v1.15.10-cee
Install tools:
Others:

Hi @remmen-io, thanks for opening this issue.
With Liqo v1.0.0-rc.2 declaratively configuring the authentication is not actually trivial, as it requires an exchanges of resources between the consumer and the provider clusters.
With the new version of Liqo we simplified this procedure and we did a good amount of work to improve the compatibility with tools like ArgoCD.
You can find here a guide where we explain how to configure the peering between two clusters by applying the Liqo CRs. Note that to follow this guide, you will need the latest version of Liqo (which we are planning to release by the next week).
If you already want to try it, you can install the version of Liqo in the main branch, by providing the hash of the latest commit in main. E.g.:
liqoctl install [..args] --version <COMMIT_HASH_IN_MAIN_BRANCH>

or with Helm, by cloning the repository, from the root directory of the repo:
helm install liqo ./deployments/liqo [...args] --tag <COMMIT_HASH_IN_MAIN_BRANCH>


Avoid min name conflict

In some weird C implementations (MSVC), min is defined as (((a) < (b)) ? (a) : (b))

another fix is to disable the non-ANSI C language extensions that Visual Studio enables by default, by passing the /Za compiler flag:
https://msdn.microsoft.com/en-us/library/0k0w269d.aspx
this prevents, among other things, the MSVC <stdlib.h> header to define min and max macros.

Thanks, that's useful


Remove MacOS from workflow

Description

Remove MacOS from workflow in 2.x branch
Main branch don't have MacOS build workflows (removed earlier in https://github.com/opensearch-project/sql/pull/2662)

Issues Resolved

workflow failure

Check List

[-] New functionality includes testing.

[-] All tests pass, including unit test, integration test and doctest

[-] New functionality has been documented.

[-] New functionality has javadoc added
[-] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Just curious, macos is removed #2662 (comment), says "artifacts are not available and those tests will always fail."

What artifact is not available? Is there a known issue with this? The reason I'm asking is that I didn't see an organization-wide issue on this problem.
What is the failed test? Should we mark them as flaky tests and fix them?

Here is the error:
* What went wrong:
Execution failed for task ':doctest:runRestTestCluster'.
> Could not resolve all files for configuration ':doctest:opensearch_distro_extracted_testclusters-doctest-docTestCluster-0-2.16.0-SNAPSHOT-'.
   > Could not resolve opensearch-distribution-snapshot:opensearch:2.16.0-SNAPSHOT.
     Required by:
         project :doctest
      > Could not resolve opensearch-distribution-snapshot:opensearch:2.16.0-SNAPSHOT.
         > Could not get resource 'https://artifacts.opensearch.org/snapshots/core/opensearch/2.16.0-SNAPSHOT/opensearch-min-2.16.0-SNAPSHOT-darwin-arm64-latest.tar.gz'.
            > Could not HEAD 'https://artifacts.opensearch.org/snapshots/core/opensearch/2.16.0-SNAPSHOT/opensearch-min-2.16.0-SNAPSHOT-darwin-arm64-latest.tar.gz'. Received status code 403 from server: Forbidden

2 -> I'm not sure if we should spend time to fix the issue if we don't support macOS. Any thoughts?

Close this since https://github.com/opensearch-project/sql/pull/2830 fixed the build issue and merged.


allow for other providers/models and use groq+llama3-70 as default + …

…minor guardrails optimization

Should we merge this?


Break out Unit tests

PR Summary
This PR breaks out all the tests to single function per file.  It also removes the
InModuleScope VSTeam {
}

From all the tests so the module does not have to loaded to run the tests.
PR Checklist

[ ] Write Help
[x] Write Unit Test
[ ] Update CHANGELOG.md

This will be merged once all the tests are ported. I created it no so I could have CI fire on macOS and Linux to make sure the unit test still pass there as well.

Do you want me to help on that PR?
Please also aware that you need to include applyTypes.ps1 in the unit tests where needed. I had it in my function for PR #283 in this line:
https://github.com/DarqueWarrior/vsteam/blob/569367270c697c60c581b276edcc07c61468fd9e/unit/test/Get-VSTeamBuildTimeline.Tests.ps1#L9
Maybe you want to outsource the includes into an extra file so possible needed includes are done within one ps1 file.

related #279


glTF importer doesn't build

Building with the glTF format enabled causes C++ error spew about no matching constructor for initialization of 'Value' (aka 'GenericValue<UTF8<>>')

https://github.com/MasterQ32/zig-assimp/pull/8 should fix that

Fixed, thanks!


ADU

Our University situated in Uzbekistan and our learners need your company's projects thats why we are here

@Abduqodircoder Pull request merged. Thank you!

We  are glad to know this
чт, 8 окт. 2020 г. в 14:56, Philip Torchinsky<EMAIL_ADDRESS>
@Abduqodircoder https://github.com/Abduqodircoder Pull request merged.
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/9525#issuecomment-705463984, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZHN6CBJBUG6N3AXF4HJZTSJWEGPANCNFSM4SIMQIIQ
.


Added @func for static public functions for tooltips in IDE

Heya -- if you want, you can add these /// headers
I added them to have param tooltips in ide
cheers, Gris

oops - this is in main branch - sorry - i reopen from dev


cloud logging example is misleading where labels.instance_id has to be STRING

The doc says string for instance_id
var resource = {
type: 'gce_instance',
labels: {
zone: 'global',
instance_id: 3
}
};
yet in practice, you will hit the following if you pass an int. ugh...
{ [ApiError: Invalid value at 'entries[0].resource.labels[0].value' (TYPE_STRING), 1]
errors: undefined,
code: 400,
response: undefined,
message: 'Invalid value at 'entries[0].resource.labels[0].value' (TYPE_STRING), 1' }

Can you show the code you're using? The code from the readme works for me.
Also, which version of gcloud-node are you running?

We use:
"gcloud": "0.28.0",
resource = {
type: 'gce_instance',
labels: {
instance_id: instance_id,
zone: zone
}
};
log.write([ logEntry ], function (err, apiResponse) {
if (err) {
logger.error(err);
}
});

https://cloud.google.com/logging/docs/api/ref_v2beta1/rest/v2beta1/LogEntry
also this say labels are string?
labels	map (key: string, value: string)

I was able to reproduce. Thanks for catching this. Any chance you'd be willing to send a PR with the fix for the docs?

sure, will do

Fixed by #1241


Vessel page -> Boardings search link

On the Vessel Overview page (https://mongodb.invisionapp.com/share/2SWVCLE8WJG#/screens/413646959) if you click 'See All' in the Boardings section you should be directed to a Boardings page that shows the boardings that match the vessel you clicked from ('Predator' in this example).

When complete, this will show up as filters for vessel name and permit number (if permit number exists). See design at https://mongodb.invisionapp.com/share/VJXLVXNPGW4#/screens/427645087 and click "see all" under Boardings, which brings you to https://mongodb.invisionapp.com/share/VJXLVXNPGW4#/screens/427645088 - which has the filters for vessel name and permit number. If there's no permit number, don't add the filter for it :D


Some requests

Hello! I would like to request if we could just copy and paste a list of URL links and their chapter names in the automatic/manual tabs so that it would be easier to edit?
For example:
https://www.website.comChapter 1- Chapter Name
It's just that there are some websites that do not automatically add new chapters and adding them always every time I try to download is becoming time-consuming.
I would also like to request if https://foxaholic.com/ could be added to the list of websites supported? Thank you very much! :)

You're talking about the manually adding/editing chapters/order window? How about a new dialog window with 2 areas to paste lines in where one corresponds to a chapter name/link on the other side?
Will add foxaholic.

You're talking about the manually adding/editing chapters/order window? How about a new dialog window with 2 areas to paste lines in where one corresponds to a chapter name/link on the other side?
Will add foxaholic.

Thank you!
Yes, the adding/editing chapters window. Like maybe there could be an option to get lines of code when the program gets the chapters and I could save these code to notepad and then just copy/paste it to a window?

I removed the (single) chapter adding function and replaced it with a new window where it lists all chapter names and links side by side. You can just paste your custom names and links at the end. This also enables you to save the names/links which the grabber stores internally.

Is this what you had in mind?

I removed the (single) chapter adding function and replaced it with a new window where it lists all chapter names and links side by side. You can just paste your custom names and links at the end. This also enables you to save the names/links which the grabber stores internally.

Is this what you had in mind?
I've added limited support for Foxaholic (headless only atm)

Yes, this is what I had in mind. :)

Thank you for the update! I recently had an issue though with CG...there are frequent times when I would encounter this error, especially with longer chapters:
Fetching latest selector JSON from GitHub...
org.jsoup.HttpStatusException: HTTP error fetching URL. Status=403, URL=https://blahblahblah
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:762)
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:707)
at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:297)
at org.jsoup.helper.HttpConnection.get(HttpConnection.java:286)
at grabber.Chapter.saveChapter(Chapter.java:43)
at grabber.Novel.downloadChapters(Novel.java:97)
at gui.GUI.lambda$null$2(GUI.java:243)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


lxd-agent: Allow building on freebsd

By splitting out Linux specific dependencies into Linux only build files.
To be clear: This does not add freebd lxd-agent support
It only provides the ability to build lxd-agent on FreeBSD, which is on the path towards adding support.
Tested using:
CGO_ENABLED=0 GOOS=freebsd go install -v -tags agent,netgo ./lxd-agent

Closes to #11603

Yeah the scope of this pr is to get it to build on freebsd, rather than provide a tested working agent on freebsd (as that isnt something on my current roadmap items). If you would like to use this pr as a basis for your own testing and then send up additional PRS that would be great! I'll close this for now.


PHP container down unexpectedly

I noted that PHP container down unexpectedly and it hangs nginx. error log as follows
<IP_ADDRESS> -  09/Mar/2018:13:51:17 +1300 "GET /11/index.php" 303
[09-Mar-2018 13:51:18] WARNING: [pool www] child 14 said into stderr: "There was a problem sending 178 bytes on socket 7: Broken pipe"
<IP_ADDRESS> -  09/Mar/2018:13:51:18 +1300 "GET /11/admin/index.php" 200
[09-Mar-2018 13:51:18] WARNING: [pool www] child 13 said into stderr: "There was a problem sending 178 bytes on socket 7: Broken pipe"
[09-Mar-2018 13:51:21] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

it seems issue with php-fpm conf https://serverfault.com/questions/479443/php5-fpm-server-reached-pm-max-children

Ah interesting, maybe we should then raise the config for max_children.

done in 6943e6b01309d019256ba4a2855596da77adc83b


IE<=8 no [].reduce, so use 'utils.reduce' instead

Merged via https://github.com/mochajs/mocha/commit/0565fac49e4153cdc65a6431553d1aae80eb7008 We usually only compile mocha.js as part of releases. Thanks!


XamlParseException when using AdonisWindow control

When switching Window control to AdonisWindow, on startup application breaks with a XamlParseException and an inner exception with a message of: IOException: Cannot locate resource 'defaultstyles/calendar.xaml'.
To Reproduce

Create new dotnet core project.
Reference AdonisUI and AdonisUI ClassicTheme.
Replace MainWindow.xaml references to Window with AdonisWindow. Add necessary xmlns namespaces.
Replace backing MainWindow.xaml.cs references to Window with AdonisWindow. Add necessary using namespaces.
Launch Application > break mode

Expected behavior
Expect application to launch and window to appear.

Thank you for reporting this, I was able to reproduce this using the 1.12 nuget package.
Furthermore I was able to verify that it only occurs when using the nuget package in a .NET Core 3.0 WPF application. In a .NET Framework WPF application this exception is not thrown.
Since this error does not occur when using a nuget package created after merging #36 (b4c419d), a temporary fix would be to temporarily reference the projects directly until a new nuget package is released.

I will create a minor release for you which includes the dotnet core update of #36. I might be able to do so this evening (in like 10 h from now) or tomorrow.

Release 1.12.1 is out and I cannot reproduce the issue with that one. @mettelephant please reopen in case you still receive the error.


[BUG] Unable to test new quirks

Describe the bug
ZHA is not taking into account my changes in /usr/local/lib/python3.8/site-packages/zhaquirks.
I don't know why but when I remove __pycache__ folders in zhaquirks folder, they don't come back after a home assistant restart.
To Reproduce
Steps to reproduce the behavior:

Go to /usr/local/lib/python3.8/site-packages/zhaquirks using the portainer addon method as described in the README
Remove __pycache__ folder
Restart home assistant
Come back to /usr/local/lib/python3.8/site-packages/zhaquirks and see that __pycache__ has not been recreated.

Expected behavior
I expected __pycache__ to be recreated.
Additional context
I run HassOS all up to date on a Raspberry Pi 4 4GB.
Thanks in advance for your help !

Ok i setup a virtual machine and now i can test quirks, I don't know why, but with my raspberry pi home assistant version I was not able to test quirks.


New search | Homepage

Related to #170.
This implements the search functionality of #170.
In the GIF below, enter is pressed to go to the search page. You can also click the arrow or "5 Ergebnisse anzeigen".

Changes

Add new homepage with view and controller to show the search form
Add filter_home as the main search method
Add links to jump to the old search page to show results. That page will be updated in a later PR.

Caveats

It is probably hard to understand the "why" when reading the search query. I left a comment which hopefully clarifies it. We need to add weights to have correct sorting, but then SQL's UNION no longer returns unique results if a word appears in different sub-queries with different weights (because the word is unique with a different weight). So we have to wrap everything with another query to get unique results.
This PR doesn't include any design changes yet. I would prefer if we first change the functionality and then at the end change the whole website to the new look and feel (to make sure that we are consistent everywhere).
The browser's autocomplete is a bit annoying if we display the search results directly below the field (see GIF above). @wintermeyer We should probably disable it, do you agree?

The browser's autocomplete is a bit annoying if we display the search results directly below the field (see GIF above). @wintermeyer We should probably disable it, do you agree?

Yes, we do have to disable the browser autocomplete.


Error sending the message.

Describe the bug
I have deployed opencopilot to my server and configured OPENAI_API_KEY. I simply created a copilot. I found that copilot couldn't chat with me.
If you can help me solve this problem, I would be very grateful.

@WKaiH123 please share server logs here

@codebanesr How should I view the log messages?

docker compose logs -f llm-server
From root directory
You can do the same for other containers too

Ok two things to verify

Is your openai api key correct
Is openai available in the region your server is hosted


[feature request] a new dfdaemon sub command for CA generation

Why you need it?

Thanks to @YanzheL 's great work in #1181 , clients that use dfdaemon as proxy for https connection no longer need to explicitly ignore certificate errors. This is a big improvement on usability.
Since the CA is only used for a single host, we can generate the CA when deploying dfdaemon. Adding the CA to system certificate store usually requires root privilege, so it's better we make this into a sub command for dfdaemon which can be easily integrated in users' deploy workflows.
Also we need documentation for how to generate the CA and add it to system trust store, or docker's certificate directory as documtend here. Documentation in #1181 can cover most of this.
How it could be?

The new sub command may look something like this:
dfdaemon generate-ca --key-output path/to/ca.key --cert-output path/to/ca.crt

Other related information

/assign


9 implement search bar for homepage

Summary
Implemented a search bar on the homepage to allow users to input search queries. This task involved designing, integrating, and styling the search bar within the navigation bar.
Changes Made

Added a SearchBar component that includes a category dropdown, search input field, and search button.
Integrated the SearchBar component into the NavigationBar component for better UI consistency.
Styled the search bar to match the overall theme of the application and ensured it is responsive.
Adjusted the NavigationBar CSS to accommodate the search bar and maintain a clean layout.

Acceptance Criteria

The search bar is prominently displayed on the homepage.
The search bar is responsive and looks good on different screen sizes.

Additional Notes

The search bar is designed to provide a good user experience.
Placeholder text for the search bar is "Search Amazon".

It seems like the actual size is different from your screenshot.

I see. The px amount varies between screen sizes. Instead, try using root em. it will make the sizes more responsive to different screen sizes.

I made the changes.


Add Python 3.13 support

(some dependencies seem to still be broken)

Related https://github.com/huggingface/tokenizers/issues/1639


Cortex-M33 / Musca-A1 Support

Hi, does pyOCD support Musca-A1 board? Is there documentation about porting it? Thanks

The Musca-A1 will be supported as part of v8-M support in pyOCD. You can see the work on the dev_v8m branch of my fork. At the moment, I can't guarantee any schedule for completing this work, except that it is relatively high priority.

CM33 support is merged into master with #603.
Musca-A1 support is not fully working yet. Flash programming has issues (partially due to working around chip errata), but you can debug the device.

Hi @flit
I am using VSCode with Cortex-Debug plugin. Could you help on how to setup the launch configurations to  debug Musca-A1?

Hi @danielRep, Unfortunately I'm not familiar enough with the cortex-debug plugin to know what could be causing the problem. I think I remember another user saying that cortex-debug doesn't yet support the combined pyocd tool; it only supports the deprecated pyocd-gdbserver tool. However, pyocd-gdbserver should still be available, as it hasn't been removed yet.
Several questions:

Is pyocd-gdbserver in your PATH?
Is there a way to point cortex-debug at the pyOCD executable?
Is there a way to pass additional arguments to pyOCD?
Do you get any log output from pyOCD? If so, could you please copy it here?

You might also try running pyOCD directly from the command line just to verify the connection. First run pyocd list to print out connected debug probes. Musca-A1 should be in the list. Then run `pyocd-gdbserver, which should connect and start up the gdbserver (if you have more than one probe connected, it will ask which one you want to use).

Hi @flit.
This issue as been solved. It was a problem related with the Cortex-Debug plugin. If anyone encounter this problem, the solution is on this link.
Thanks !

Thanks for the link! Sorry we unintentionally broke cortex-debug when we changed the log message…


Add Pipeline API

Implementation based on https://docs.gitlab.com/ce/api/pipelines.html

Thank you for your contribution.  Your pull request has been merged.  I will add some unit tests and do a release over the weekend.


Add note for Office Hours

/assign @dgoodwin

Sorry :) I realize now people still can't tell when the next meeting is.
I found a publish this event link, can you add in a link with: https://calendar.google.com/event?action=TEMPLATE&tmeid=MzBqcmhoOTJkZjNkcDI4NnZhaTJwcXJhaDBfMjAyMDEyMTFUMTkwMDAwWiBkZ29vZHdpbkByZWRoYXQuY29t&tmsrc=dgoodwin%40redhat.com&scp=ALL

Sorry :) I realize now people still can't tell when the next meeting is.
I found a publish this event link, can you add in a link with: https://calendar.google.com/event?action=TEMPLATE&tmeid=MzBqcmhoOTJkZjNkcDI4NnZhaTJwcXJhaDBfMjAyMDEyMTFUMTkwMDAwWiBkZ29vZHdpbkByZWRoYXQuY29t&tmsrc=dgoodwin%40redhat.com&scp=ALL

This is neat! Fixed.

Perfect, thanks!
/lgtm

/retest


watchExclude option doesn't work for code in node_modules in some cases

Describe the bug
From what I tried so far, the watchExclude for code in node_modules option doesn't work when:

the environment is node.
the environment is jsdom and

the first time you edit the main file of a node module, or
every time you edit a non-main file of a node module

More discussion info: https://github.com/vitest-dev/vitest/discussions/4772#discussioncomment-7896620
Reproduction
https://github.com/Jinjiang/reproductions/tree/vitest-watch-node_modules-20231220
pnpm install

# you can switch environment between 'node' (default value) and 'jsdom'
pnpm test

# in 'node' environment:
#
# modify any code in node_modules
# - the test is not re-run

# in 'jsdom' environment:
#
# modify code in node_modules/foo-cjs/index.js or node_modules/foo-esm/index.js
# - when you first time modify it, the test is not re-run
# - when you further modify it, the test is re-run
#
# modify code in node_modules/foo-cjs/foo.js or node_modules/foo-esm/foo.js
# - the test is not re-run

The expected behavior is that the test is always re-run when any code in node_modules/foo-cjs and node_modules/foo-esm is modified whatever the environment is.
System Info
System:
    OS: macOS 14.3
    CPU: (8) arm64 Apple M1
    Memory: 88.61 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.1.0 - ~/.asdf/installs/nodejs/20.1.0/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 9.6.4 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 8.12.0 - ~/Library/pnpm/pnpm
  Browsers:
    Safari: 17.3
  npmPackages:
    vite: ^5.0.10 => 5.0.10
    vitest: ^1.0.4 => 1.0.4

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

In https://github.com/Jinjiang/reproductions/tree/vitest-watch-node_modules-20231220 when using jsdom environment, Vitest reruns changed node_modules file without any changes.


Using with-open blows up

(ui/default-theme
  {}
  (with-open [purple (paint/fill 0xFF9F2B68)]
    (ui/rect purple
      (ui/label (str "Apple")))))

Blows up with:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000152a3c309, pid=70244, tid=775
#
# JRE version: OpenJDK Runtime Environment Homebrew (19.0.1) (build 19.0.1)
# Java VM: OpenJDK 64-Bit Server VM Homebrew (19.0.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-amd64)
# Problematic frame:
# C  [libskija.dylib+0x2f0309]  _ZNK7SkPaint13nothingToDrawEv+0x9
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/folcon/Code/pankration/hs_err_pid70244.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/Homebrew/homebrew-core/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

However, the below does not:
(ui/default-theme
  {}
  (ui/rect (paint/fill 0xFF9F2B68)
    (ui/label (str "Apple"))))

Both return io.github.humbleui.ui.dynamic.Contextual and io.github.humbleui.ui.rect.Rect:
;; From the first form
=> #object[io.github.humbleui.ui.dynamic.Contextual 0x19813f6 "io.github.humbleui.ui.dynamic.Contextual@19813f6"]

;; From the second form
=> #object[io.github.humbleui.ui.dynamic.Contextual 0x2aff357a "io.github.humbleui.ui.dynamic.Contextual@2aff357a"]

This could just be because io.github.humbleui.skija.Paint is closed with the with-open version when it comes time to render.
I'm only mentioning it as it's something I picked up from your canvas example, it might be worthwhile changing that to use colours set using with-context higher up the app so reusing this sort of logic doesn't break? Unless there's another reason for it?

Well, UI is defined as an object, on which measure/draw/event methods will later be called. That means they will need paint to remain open.
Canvas example is different, in a sense that you define draw function and paint is only used inside the paint, so it’s ok to create/destroy paints on each draw.
Memory-wide, paints are relatively lightweight objects, so it’s ok to not close them explicitly. They’ll eventually be garbage collected

Ok, I might stick to just defining them using with-context for now then. Having stuff close like that seems to be less great.
Not sure if it's the best thing for the app to crash with _ZNK7SkPaint13nothingToDrawEv as the error, but you might feel like it's out of scope to handle this stuff.
I'll close this =)...


Specify disable trailing_whitespace condition by funcion

Request for additional color space
I want to configure like below.
local ccc = require('ccc')
ccc.setup {
  pickers = {
    ccc.picker.trailing_whitespace {
      enable = true,
      disable = function(bufnr)
        return not vim.fn.empty(vim.bo[bufnr].buftype)
      end,
    }
  }
}

Currently, we can specify a list of filetypes to disable, but in most of my use cases I wanted to disable when &buftype !=# ''.
(like terminal, gitcommit, help, mason, fzf etc...)
Request for other features
No response

Please try PR 87

It seem works. Thank you!


Snaptoitem doesn't work with more than 10 elements?

Is this a bug report, a feature request, or a question?
Question
There're 11 cards in my snap carousel. When i try snapToItem(i) where i < 10, it works perfectly fine but when i try snapToItem(10), it just moves to the 10th card. Isn't it supposed to move to the 11th card since i'm passing a index of 10. Is there any kind of limit over number of cards in the snapcarousel?

Hello,
I had the same issue and I solved it by using the initialNumToRender prop !
By default, all the slides are not rendered for optimization so I guess that's why snapToItem was not able to find the slide :)

@eggybot i have the same issue, do you have any solution?

@eggybot thank you, after reverting to 3.7.5 and reverting react from 16.8.3 to 16.6.3 it is working again.

Well, I now need to find out which one of the PR I recently merged is responsible for that.
#443 is a strong candidate IMO. If someone has the time to test if reverting this fixes the issue, I'd really appreciate it.

I have the same issue and going back to 3.7.5 did not solve the problem. React 16.8.3 and RN0.59.8.
@bd-arc I tested if reverting this on 3.8.0 solves the issue, but unfortunately seems not...

@eggybot Thanks 3.7.5 for fixing my problem

Any update on this?
I have a Carousel with almost 300 items, and it's simply impossible to set initialNumToRender that large with acceptable performance. :(

@vittau Have you given a try to version 4.0.0-beta.4?
We're now relying on FlatList's initialScrollIndex, which should help with large datasets.

@vittau Have you given a try to version 4.0.0-beta.4?
We're now relying on FlatList's initialScrollIndex, which should help with large datasets.

Thank you! It really does work correctly now without having to set initialNumToRender. :)

Something interesting I meet when trying fix this problem. I have very loaded screen with carousel of video components and custom interface. When I snap from 1 video to 10+, slider stucks on 6-7th card, but when I set prop windowSize={SCREEN_WIDTH} bug disappeared.
Tested on iPhone 11, iPhone 6s.

Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2

I tried both windowSize and initialNumToRender props but still, it gets stuck on the 6th and 7th item if I call snapToItem(10+)


Fix compressed length calculations for escaped names

Performance hit incoming.
Len will now take escaping into account and return the correct length regardless of escaping.
These are the benchmarks:
name                       old time/op    new time/op    delta
MsgLength-12                  349ns ± 4%     392ns ± 4%   +12.29%  (p=0.000 n=9+9)
MsgLengthNoCompression-12    28.0ns ± 1%    64.0ns ± 2%  +128.59%  (p=0.000 n=10+10)
MsgLengthPack-12             1.10µs ± 8%    1.13µs ±10%      ~     (p=0.143 n=10+10)
MsgLengthMassive-12          26.1µs ± 2%    27.1µs ± 4%    +4.13%  (p=0.000 n=9+10)
MsgLengthOnlyQuestion-12     10.0ns ± 3%    17.2ns ± 2%   +73.11%  (p=0.000 n=10+10)
MsgLengthEscapedName-12      9.25ns ± 1%   96.89ns ± 1%  +947.32%  (p=0.000 n=9+9)
PackMsg-12                    957ns ± 1%    1009ns ± 3%    +5.52%  (p=0.000 n=10+10)
PackMsgOnlyQuestion-12        173ns ± 2%     182ns ± 3%    +5.02%  (p=0.000 n=9+10)

Fixes #841

Codecov Report

Merging #850 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #850     +/-   ##
========================================
+ Coverage    57.9%     58%   +0.1%
========================================
  Files          42      42
  Lines       10661   10675     +14
========================================
+ Hits         6173    6192     +19
+ Misses       3399    3395      -4
+ Partials     1089    1088      -1

Impacted Files
Coverage Δ

msg.go
78.66% <100%> (+1.22%)
:arrow_up:

server.go
66.19% <0%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


When MFA + rotating refresh tokens enabled, getAccessTokenSilently fails with Error: MFA Required

Describe the problem
When a user has MFA enabled, the getAccessTokenSilently throws an Error: MFA Required error when attempting to use the refresh token against the /oauth/token endpoint after the JWT expires (see docs here)
What was the expected behavior?
I would expect that refresh tokens would still work with MFA enabled.  I probably have something configured incorrectly that is causing this refresh failure, but I'm unsure where to look, and the help forums don't seem to cover this case (here, here, and here).  Hoping this issue can also act as some documentation for those stumbling on it in the future!
Currently, I'm using the following logic to work around this (as suggested in the docs) and recover from the error (the handler shown below is my interpretation of this recommendation).
I have also set the allowRememberBrowser: true as documented here, which if checked by the user, will skip the MFA prompt after error is recovered from.  This solution works fine, but seems pretty complex to me (and not sure if filtering these error codes is stable)?  Is there a better way documented somewhere?  Or is this correct?
// Anywhere `getAccessTokenSilently` is called, catch errors and redirect to login
try {
   const token = await getAccessTokenSilently()
   // Do something with token
} catch (err) {
    const authErr =
        err && typeof err === 'object' && 'error' in err && typeof err.error === 'string'
            ? err.error
            : null
    const isRecoverable = authErr
        ? [
                'mfa_required',
                'consent_required',
                'interaction_required',
                'login_required',
            ].includes(authErr)
        : false

    if (isRecoverable) {
        await loginWithRedirect({ appState: { returnTo: window.location.pathname } })
    } else {
        Sentry.captureException(err)
    }
}

Reproduction
I have reproduced this with a minimal repository linked below.  The repository has a README with instructions on how to reproduce the error.
https://github.com/zachgoll/auth0-react-mfa-refresh-bug-reproduction
Environment

Please provide the following:

Version of auth0-react used: - 2.0.0
Which browsers have you tested in? - Chrome
Which framework are you using, if applicable (Angular, React, etc): Next.js in SPA mode
Other modules/plugins/libraries that might be involved: express-jwt, jwks

Hello,
Having looked into it it seems to be expected that Auth0 doesn't allow exchanging refresh tokens when you set allowRememberBrowser to false, which looks like what you are doing.
There isn't much we can do from the SDK side, but if product feedback is always appreciated through https://auth0.com/feedback
Closing, as there isn't anything to action from our SDK.


Reworking to push to print file data to a gcs bucket

Due to the limitation on size for both data store and pubsub the data transfer between action exporter and print file will be done via a GCS bucket.
Action exporter will write the data file to GCS and then publish a message to pubsub with the name of the datafile in it. Print file will then read that file and use the data for templating.

/deploy baileyw

/deploy baileyw

/deploy baileyw


SectionList and Flatlist not scrolling inside reanimated-bottom-sheet

I have added a SectionList (also tried with FlatList) and the scroll for SectionList or Flatlist is not working inside react-native-reanimated-bottom-sheet
`       <BottomSheet
enabledInnerScrolling={true}
ref={fullScreen}
snapPoints={[450, '80%', '50%', '50%']}
    initialSnap={2}

     overdragResistanceFactor={1}

    renderContent={() => renderBottomContent() }

    enabledContentGestureInteraction={false}

  /> `

the SectionList is displaying but it is not scrolling as normal behaviour.

Duplicate of #20


Made background 5000ms from 10000ms

So it'll be more lit.

Accepted

My plan here is to create a slider that changes the color changing frequency, but this will work for now.


Move away from jose jwt to jose4j

I originally updated the jose jwt library version in #199, but was decided against since it'd bundle Gson which is a relatively large json library.
The idea came up to move to an other JWT library which still uses json simple (orgjson) and ultimately ended up with jose4j.
I also included some other changes to EncryptionUtils to make it more useful for projects using Protocol.

Gson is a wide-used json library and many projects which using this library also uses Gson as a json library, i think its better to upgrade the library than replace with another one.

Gson is a wide-used json library and many projects which using this library also uses Gson as a json library, In my opinion its better to upgrade the library than replace with another one.

Using Gson would still be replacing one library with another. We're trying to keep this project as slim as possible with no unnecessarily large dependencies like Gson. Also, not every downstream project uses Gson as their default JSON serialisation library, so including another full-fat library is wasteful, especially when this protocol library doesn't need any fancy serialisation features.


etrac trace cleanup

Removed the old ETRAC0->9 defines to create a single ETRAC define that uses varargs

This did not reduce the compiled size as much as I had expected - but this does seem beneficial in that it cleaned up code, cleaned up error messages, removed unused code and simplified the ETRAC interface.

This is what the error messages look like now:
ERROR: (virtual uint32_t ecmdDataBuffer::flipBit(uint32_t)): cannot flip non-binary data at bit 1
I could have added a function to better format function name, but it added ~40k to the shared lib so I decided against it.


Build task terminal no longer closes on Cmd+D

The build task terminals in vscode repo used to close when I typed Cmd+D but they no longer close.

This is intentional: https://github.com/microsoft/vscode/issues/143407
I don't have a string preference here, but @bpasero, I have had this keybinding for a long time:
	{
		"key": "ctrl+shift+alt+b",
		"command": "workbench.action.tasks.runTask",
		"args": "Kill VS Code - Build"
	}

@alexr00 I guess even cooler would be a command to restart the build tasks, so that everything is just one command?

Add a new task: Restart VS Code - Build.

Neat!


[Suggestion] Create an optional attribute

Bitstrap contains an PropertyDrawer for object that becomes red when the reference is null. This is helpful but it would be good to have a way of showing what is not mandatory.

There is now a Nullable attribute that will tell the editor to not mark them red when null


Processes

Support for multiprocessing in self-play.

this looks awesome. what kind of speedups have you gotten?

It's kind of a hacky attempt (I make a lot of manager servers and shared queues) but I found 3 processes with 16 threads to be the best with 50% speedup (over 1 process)


Using the MultiQueryRetriever in combination with the PGVectorStore ignores metadata for filtering embeddings

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
const pgvectorStore = await PGVectorStore.initialize(
	new OpenAIEmbeddings(),
	pgVectorConfig
);

const retriever = MultiQueryRetriever.fromLLM({
	llm: openaiInstance,
	retriever: pgvectorStore.asRetriever({
		metadata: { chatbot_id: chatbotId }
	}),
	verbose: true,
});

const retrievedDocs = await retriever.invoke(currentMessageContent);

Error Message and Stack Trace (if applicable)
No response
Description
The vector table (PgVector) in my database contains embeddings for multiple different RAG chatbots. When a question is asked in one of those chatbots, I do a similaritySearch() on the subset of embeddings that belongs to that specific chatbot. I filter on the chatbotId. This all works fine using a standard SupabaseVectorStore.similaritySearch(question, {chatbot_id}), but I want to improve my retrieval using a Multi Query Retrieval. Unfortunately this approach seems to completely ignore my attempt to filter on chatbotId, and searches the complete table of embeddings.
System Info
linux
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

@dosu, That does not seem to work unfortunately. MultiQueryRetriever does not have a filter function to call so it will still be ignored.


Firestore transaction timeout parameter in runTransaction does not work

I have a problem with my transaction timeouts. The timeout always takes around 9 seconds independent of how I set the timeout parameter.
final db = FirebaseFirestore.instance;
final docref = db.collection('appdata').doc(docID);
final data = {'rueckruf': FieldValue.serverTimestamp()};

db.runTransaction((transaction) async {
  transaction.update(docref, data);
}, timeout: Duration(seconds: 3)).then((value) {
  //transaction did work do sth.
}, onError: (e) {
  //transaction did not work do sth.
});

@inamaze44
When opening an issue, try to use new issue template and fill out requested details so that we'll have enough details to work with. Looking at code you shared, we can't analyze properly.
Can you provide flutter doctor -v, plugin version and complete minimal reproducible code sample along with current and expected behavior ?

The Link on the page: https://pub.dev/packages/cloud_firestore
on the bottom: Please file FlutterFire specific issues, bugs, or feature requests in our issue tracker took me to a blank entry form.
I suggest to change the link to https://github.com/firebase/flutterfire/issues/new/choose
so I would have chosen the right form.

I will fill out a new form with all the information then.

on the bottom: Please file FlutterFire specific issues, bugs, or feature requests in our issue tracker (https://github.com/firebase/flutterfire/issues/new) took me to a blank entry form. I suggest to change the link to https://github.com/firebase/flutterfire/issues/new/choose

Thanks for pointing this out. I'll forward this to concerned team for the fix.
Meanwhile:

Can you provide flutter doctor -v, plugin version and complete minimal reproducible code sample along with current and expected behavior ?

Bug report
Firestore transaction timeout parameter in runTransaction does not work
Steps to reproduce
Steps to reproduce the behavior:

Login with FirebaseAuth
Put the mobile in Flight mode
Execute the runTransaction command with any data
The transaction timeout always happens after around 10 seconds.

Expected behavior
The transaction timeout should come around the time specified.
In the sample the timeout happens after 10 seconds, and not after the 3 seconds specified with the timeout parameter.
Sample project
final db = FirebaseFirestore.instance;
final docref = db.collection('appdata').doc(docID);
final data = {'rueckruf': FieldValue.serverTimestamp()};
db.runTransaction((transaction) async {
transaction.update(docref, data);
}, timeout: Duration(seconds: 3)).then((value) {
//transaction did work do sth.
}, onError: (e) {
//transaction did not work do sth.
});
Additional context
I have updated to the latest versions and I still get that error.

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 beta, 3.1.0-9.0.pre, on macOS 12.4 21F79 darwin-arm, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.18.0-165.1.beta
Flutter SDK 3.1.0-9.0.pre
tk_assistant_app 1.0.0+1

dependencies:
- cloud_firestore 3.3.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.5
- firebase_auth 3.4.2 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.19.2 [firebase_core_platform_interface firebase_core_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- font_awesome_flutter 10.1.0 [flutter]
- modal_progress_hud_nsn 0.2.1 [flutter]
- rflutter_alert 2.0.4 [flutter]

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

transitive dependencies:
- async 2.9.0 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.1
- clock 1.1.0
- cloud_firestore_platform_interface 5.6.0 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.7.0 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.16.0
- fake_async 1.3.0 [clock collection]
- firebase_auth_platform_interface 6.3.2 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 4.0.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.4.3 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 1.7.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.4
- lints 2.0.0
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.5
- meta 1.8.0
- path 1.8.2
- plugin_platform_interface 2.1.2 [meta]
- sky_engine 0.0.99
- source_span 1.9.0 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.1 [collection]
- vector_math 2.1.2

2. Put the mobile in Flight mode

@inamaze44 Does the reported behavior only occur in this case ? or also happens when you have proper / stable network ?

I have only tested it in this case, when I have no network.

Ok, can you test with WIFI ON and flight mode OFF and see if you still get same behavior ?

My transaction only takes a fraction of a second to fulfill. When I have WIFI on and flight mode OFF the transaction finishes successfully after less than a second and a timeout is neither needed nor called.

Transactions do not work offline - is it throwing an error after the 10 second mark? I'd of thought it should throw an error if it has no network connectivity, but it might be seeing if it comes back online during that time period.

I know, that Transactions don't work offline. That is why I am using them. I want to make sure something is written into the database. The timout parameter should also reflect the time trying for a connection.

Keeping this issue open for further insights from the team on expected behavior.

@Ehesp I am sorry, I did not answer your question. After that 10 seconds of trying the error message is:
[cloud_firestore/unavailable] The service is currently unavailable. This is a most likely a transient condition and may be corrected by retrying with a backoff.

[cloud_firestore/unavailable] The service is currently unavailable. This is a most likely a transient condition and may be corrected by retrying with a backoff.

For this error, you'll need to follow-up in same discussion thread: https://github.com/firebase/flutterfire/discussions/5708

@darshankawar I think the other discussion thread does not apply, because the error I get is justified! Because I am offline!

I want the error message to come! But after the time I specified in the timeout parameter.

Thanks - makes sense. I suspect this is an upstream issue on the native platform sdks (will raise as an issue if so), but we'll confirm first

Hi @inamaze44, which platform is this happening on?

Hi @russellwheatley! I have this behaviour on my real IPhone13 in flight mode.

hmmmm, I've checked this on android as well and it also doesn't respect the timeout if in flight mode. It doesn't respect it if I set the latency on the emulator to higher than the transaction timeout. I don't think this API works as intended and isn't something that is available on the native SDKs either. Even if we called an exception in the transaction handler on the native side, it would still retry (if maxAttempts are set > 0) when we would be responding with a "timeout" exception.
My preference isn't to fix this, but to remove it. It doesn't work, isn't a Firebase SDK API and is misleading as far as I can tell.
Thoughts, @Lyokone?

Why not ask the firebase team to make the parameter available? Somewhere in their code must be the number 9 or 10 seconds as a timeout. Why not make it available for other packages like ours to change it?

I did not find the parameter maxAttemps as described in the cloud_firestore package api description. I had the idea to set it to less than 5 to reduce the number of 9 seconds but in the version I am using, 3.4.6 it does not seem to have the parameter maxAttempts.

hmmmm, I've checked this on android as well and it also doesn't respect the timeout if in flight mode. It doesn't respect it if I set the latency on the emulator to higher than the transaction timeout. I don't think this API works as intended and isn't something that is available on the native SDKs either. Even if we called an exception in the transaction handler on the native side, it would still retry (if maxAttempts are set > 0) when we would be responding with a "timeout" exception.
My preference isn't to fix this, but to remove it. It doesn't work, isn't a Firebase SDK API and is misleading as far as I can tell.
Thoughts, @Lyokone?

Yeah, it could probably be brought up to Firebase to see if implementing in the native SDK could be done.
 I don't see why we couldn't implement the timeout ourselves if it is, but I only see a way to abort a transaction from inside

@Lyokone  As far as I can tell, there is no way of aborting. You can't even cancel (i.e. throwing an exception within the transaction function) it running as it will simply retry until the amount set via maxAttempts has been reached.
@inamaze44 The latest Firestore version has maxAttempts: https://github.com/firebase/flutterfire/blob/master/packages/cloud_firestore/cloud_firestore/lib/src/firestore.dart#L230

I updated to the latest Firestore version and did some experiments with maxAttempts. maxAttempts is actually referring to the local attempts and not (only) to the attempts on the server. In FlightMode maxAttempts = 1 had 0 seconds until the error message appeared, which makes sense.
maxAttempts = 1 -> error after 0s
maxAttempts = 2 -> error after ~2s
maxAttempts = 3 -> error after ~3s
maxAttempts = 4 -> error after ~4s
maxAttempts = 5 -> error after ~9s <- well known 9s
maxAttempts = 6 -> error after ~13s
maxAttempts = 7 -> error after ~21s
maxAttempts = 8 -> error after ~24s
maxAttempts = 9 -> error after ~47s
maxAttempts = 10 -> error after ~82s
maxAttempts = 11 -> error after ~145s
It looks like and exponential function, at least not linear.
By pointing out maxAttempts you have solved my problem! I will set maxAttempts to 3 and have a comfortable localTimeout of 3 seconds in FlightMode. Thank you!!!
I think the timeout parameter refers to the timeout on the server (which I have not tested), how long the transaction is maximally allowed to take on the server, and thus the parameter also makes sense. It would be good to point that out in the documentation.

I'm closing this according to the last message.


not working again

Hey, (I'm not sure why i keep having problems, so sorry about that lol) there is an issue whenever I open the "start" in the folder. the image below constantly repeats, is there a fix to this? thank you!

No problem. Could you delete this folder in C:\Users\<username>\AppData\Local\Temp\.net

The .exe seems to "install" itself there, and deleting the folder makes it reset

this worked! looking at the page now, I can see that there is already a common issue fix there, so sorry about this post! lol


Create human population classes for each HRSA region

This issue is for the OBC.ide OWL file, not for Apollo-SV.


USB dongle Midea EU-SK105

Could you please add EU-SK105 USB dongle support.

Hello two colors,
I found your Node in the Nodered libery and installed it. After registration at MSmartHome and configurate your nodes, its getting some data.

But after it was short green connected, I'm getting "Failed to authenticate" and no communication is possible.
I have a SK105 adapter and a Comfee EcoCoolPro2.9 AC.
So I ask reneklootwijk if I use the right version. He toled me that he is not the developer of the nodered implementation.
In one Issue of him, he write: "I posted version 0.3.0 in January this year where I fixed the signing of packets during discovery".
My Question to you is: Do you use already this 0.3.0 version? And if not, is it possible to implement?
Thank you for the great work and have a nice day.

@VOPAtec try<EMAIL_ADDRESS>, but i think this not well help, support only 103

Hello twocolors,
thank you for your fast replay.
But I have no idea how I can do this.
In nodered install are still 1.2.4:

And also at notered webpage still 1.2.4:

Only npmjs.com is at 1.2.5, but I dont know how to get this inside my installation.
If you have a link were it is explaint, please send.
Thanks a lot.

@VOPAtec wait ~ 30 min and will be in node red flows

hi , update nodejs to 16


I'm having this problem too: Authentication failed because the remote party has closed the transport stream.

I'm having this problem too.
My code:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
using (FtpClient client = new FtpClient(ftp_address, ftp_port, ftp_un, ftp_pw))
{
      client.EncryptionMode = FtpEncryptionMode.Implicit;
      client.SslProtocols = SslProtocols.Tls12;
      client.DataConnectionType = FtpDataConnectionType.AutoPassive;
      client.ValidateCertificate += new FtpSslValidation(OnValidateCertificate);
      client.Connect();

    if (client.IsConnected)
    {
        FtpStatus ftpStatus = client.UploadFile(filePath, ftp_filename, FtpRemoteExists.Overwrite, false, FtpVerify.None, null);
        if (ftpStatus == FtpStatus.Success)
        {
            // log upload
        }
        else
        {
            // log error
        }
        client.Disconnect();
    }
}

Log output:
# Connect()
Status:   Connecting to ***.***.***.***
Status:   FTPS Authentication Successful
Status:   Time to activate encryption: 0h 0m 0s.  Total Seconds: 0.1624838.
Response: 220 FileZilla Server 0.9.60 beta written by Tim Kosse<EMAIL_ADDRESS>Please visit http://sourceforge.
Status:   Detected FTP server: FileZilla
Command:  USER w64upload
'iisexpress.exe' (CLR v4.0.30319: /LM/W3SVC/2/ROOT-6-132665388072666717): Loaded
Response: 331 Password required for remoteFtpServer
Command:  PASS ***
Response: 230 Logged on
Command:  PBSZ 0
Response: 200 PBSZ=0
Command:  PROT P
Response: 200 Protection level set to P
Command:  FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;
Response: MLSD
Response: AUTH SSL
Response: AUTH TLS
Response: PROT
Response: PBSZ
Response: UTF8
Response: CLNT
Response: MFMT
Response: EPSV
Response: EPRT
Response: 211 End
Status:   Text encoding: System.Text.UTF8Encoding
Command:  OPTS UTF8 ON
Response: 202 UTF8 mode is always enabled. No need to send this command.
Command:  SYST
Response: 215 UNIX emulated by FileZilla

# UploadFile("D:\Repos\filename.csv", "filename.csv", Overwrite, False, None)

# FileExists("filename.csv")

# GetWorkingDirectory()
Command:  PWD
Response: 257 "/" is current directory.
Command:  SIZE /filename.csv
Response: 550 File not found

# OpenWrite("filename.csv", Binary)
Command:  TYPE I
Response: 200 Type set to I

# OpenPassiveDataStream(AutoPassive, "STOR filename.csv", 0)
Command:  EPSV
Response: 229 Entering Extended Passive Mode (|||35003|)
Status:   Connecting to  ***.***.***.***:35003

Command:  STOR filename.csv

Response: 150 Opening data channel for file upload to server of "/filename0.csv"
Status:   IOException for file D:\Repos\filename.csv : Authentication failed because the remote party has closed the transport stream.
Status:   Failed to upload file.
Status:   There is stale data on the socket, maybe our connection timed out or you did not call GetReply(). Re-connecting...
Status:   Disposing FtpSocketStream...
Status:   Not sending QUIT because the connection has already been closed.
Status:   Disposing FtpSocketStream...

# Dispose()
Status:   Disposing FtpClient object...
Status:   Disposing FtpSocketStream...
The program '[7044] iisexpress.exe' has exited with code 0 (0x0).

Originally posted by @pmarangoni in https://github.com/robinrodricks/FluentFTP/issues/658#issuecomment-849146410

Your server is rejecting it - Authentication failed because the remote party has closed the transport stream..

The server I'm connecting to is not under my control, and it accepts the same credentials when I manually connect with an ftp client.  They don't seem to have issues with any of their other clients connecting either.  I have given up on FluentFTP. I got it to work just fine with WinSCP and it only took a few minutes to do so.
https://winscp.net/


cocomac: Watch are[\W_]+you[\W_]+looking[\W_]*+for.{0,16}<a href

cocomac requests the watch of the watch_keyword are[\W_]*+you[\W_]*+looking[\W_]*+for.{0,16}<a href. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

are[\W_]*+you[\W_]*+looking[\W_]*+for.{0,16}<a href has been seen in 40 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Reducing mouse+display lag investigations (mainly for Dear ImGui apps)

Sort of a reminder ticket. See here:
https://github.com/floooh/cimgui-sokol-starterkit/issues/2
And this also overlaps with the "only render on input" mode for sokol_app.h (because at least on Windows switching off vsync and rendering from within WM_MOUSEMOVE already makes a dramatic difference).
Also see:
https://github.com/floooh/sokol/issues/341
https://github.com/floooh/sokol/issues/301
https://github.com/floooh/sokol/issues/292
https://github.com/floooh/sokol/issues/248
...these are all more or less related. An idea would be to add a couple different "update modes" to sokol_app.h which would tune the swapchain setup and the place where the frame callback is called for different scenarios. Alternatively instead of modes, add a number of sapp_desc options to tweak unique things instead of grouping them into "modes".

...probably not an option but:
https://github.com/nlguillemot/LateLatching

...another information tidbit:
https://docs.microsoft.com/en-us/windows/uwp/gaming/reduce-latency-with-dxgi-1-3-swap-chains

not sure if really related but I fixed #341 by changing the macOS timer based loop to manual input polling loop like this (borrowed code from glfw, all changes are marked by // CHANGE), haven't tested if it breaks metal so haven't submitted a PR

I'm struggling with the same issue with linux/opengl, i did this quick experiment to reduce the lag.
This adds some padding time before the frame based on the time wasted on the previous frame. The idea is to keep the en of the logic close to the actual swap of the buffer.
Pad -> Logic -> vsync -> Swap buffer -\
 ^                                    |
 |____________________________________|

APP_PUBLIC int
APP_Run_application_loop(int(*application_frame)(void)) {
    assert(application_frame);
    int loop_result = 0;
    static i64 pad_time = 0;
    for (;;) {
        i64 frame_begin = APP_Time();
        // Sleep based on the padding time
        struct timespec remaining, request = {0, pad_time};
        nanosleep(&request, &remaining);

        APP__Process_events();
        loop_result = application_frame();
        if (loop_result != 0) {break;}
        APP__Clear_events();

        i64 frame_end  = APP_Time();
        __builtin_printf("Frame: %fms\n", (f32)(frame_end-frame_begin)*1e-6f);

        i64 swap_begin = APP_Time();
        APP__Swap_buffers();
        APP_Set_swap_interval(0); //_The only way I found to really syncronize :/
        APP_Set_swap_interval(1); //
        i64 swap_end = APP_Time();

        i64 swap_time = swap_end-swap_begin; // This will be the wasted time
        __builtin_printf("Swap: %fms\n", (f32)(swap_time)*1e-6f);

        // If we dont have pad time we add it as 3/4 of the wasted time
        // If we have pad time but the wasted time is greater, we reset it.
        if      (pad_time == 0)        pad_time = 3*swap_time/4;
        else if (swap_time > pad_time) pad_time = 0;

    }
#if defined(APP_WINDOWS)
    PostQuitMessage(0);
#endif
    if (loop_result == 1) {
        return 0;
    }
    return loop_result;
}

Btw one (embarassingly simple) latency improvement on Windows with D3D/DXGI was this recent fix:
https://github.com/floooh/sokol/blob/a18031313cdf7dab461baa296c38b07337ab4d47/sokol_app.h#L5831
For some reason DXGI has 3 frames of latency by default, which is good for video playback, but bad for interactive applications. Dragged items still don't stick to the mouse cursor, but it's at least much better than before.


Getting incorrect timestamps after 12:00 noon

Traced to the following code segment - we modified the hh to HH in the simple date formatter and all is well.
public Timestamp getTimestamp(int index) throws SQLException {
try {
ResultSetMetaData md = getMetaData();
Timestamp timestamp = null;
switch ( md.getColumnType(index)) {
case Types.INTEGER:
case Types.BIGINT:
timestamp = new Timestamp(getLong(index));
break;
case Types.DATE:
timestamp = new Timestamp(getDate(index).getTime());
break;
default:
// format 2011-07-11 11:36:30.0
try {
SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss.S");
java.util.Date parsedDate = dateFormat.parse(getString(index));
timestamp = new Timestamp(parsedDate.getTime());
} catch ( Exception any ) {
any.printStackTrace();
}
break;
  }
  return timestamp;
} catch (android.database.SQLException e) {
  throw SQLDroidConnection.chainException(e);
}

}

eg. timestamp 2015-08-29 12:35:31 getHours() returns 0, also getTimeStamp sets hours to 0.

Hi @zac1608 and @tschoenbachler !
I am busy with other projects.  Can you do a pull request?

@donv, I'll do that as soon as I prepare good patch for it. Workaround is for app level :)

I can confirm that changing SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss.S"); to SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.S"); fixes problem (hh -> HH).

Cool!

If I'm reading this document, https://www.sqlite.org/datatype3.html correctly, it describes the data and time format at:
TEXT as ISO8601 strings ("YYYY-MM-DD HH:MM:SS.SSS").
so the format would appear to be
"yyyy-MM-dd HH:mm:ss.SSS"
That is, the centiseconds and milliseconds should not be dropped.
Issue #37 seems to be caught on both of these problems.
Pragmatically, it might be worth making the SimpleDateFormat a public static (or protected with a getter/setter/whatever) in the SQLDroidResultSet - a little flexibility in date formatting, even if not strictly standard compliant, might not be a bad thing.

@ergouser Sounds like a good idea, but be aware that SimpleDateFormat is surprisingly not thread-safe.

good point, but that's a fairly small area of code to synchronize.  I'm trying to remember if the formatter is forgiving of missing milliseconds.  That is, will "yyyy-MM-dd HH:mm:ss.SSS" parse 2015-08-29 12:35:31?  It seemed to with the tenths (.S) so there may not be an issue with just adding the milliseconds.

The format could also be a static String rather than the formatter.  A DateFormat has more flexibility but that's probably not required.

@ergouser I agree. I've extracted the format String as a constant and added .SSS, which seems to work.
I found that .S also works, but trying the same with JodaTime (in another context), .SSS is required. I think SimpleDateFormat is more lenient. I think .SSS is probably best. I've changed to this in my commit.


VSCode extension - Cannot read properties of undefined (reading 'id')

Description
After installing the extension, getting this error:
Cannot read properties of undefined (reading 'id')
Also not able to view any api definitions (right-click)
Reproduction steps
Steps to reproduce the behavior:

install extension

The error seems to be gone now, but still cant interactive with any defintions or api by right clicking

@Viktorh89 - Did you import these APIs using the Import from API Management functionality in Azure CLI? If so, this is an issue that is fixed. I can share a build with you for our upcoming February release if you email me at<EMAIL_ADDRESS>Thanks!

In the newest updates of the VS code extension, this got fixed @pierceboggan, @Viktorh89


Update link to comment about NaN tagging.

Old link was pointing to outdated comment about NaN tagging which had some issues that have been fixed later.

Thanks!


There is some way to get adapter position?

How to getAdapterPosition from Slim? I want to make some implementations based on adapter position but I don't know how make it.

why you closed this? there is no answer yet


New goals: "versions:update-dependency" and "versions:set-property"

It would be so useful to have a ready to use command line way to update some dependency artifact version in pom.xml to version specified in argument.
Example of command:
mvn versions:update-dependency -Dartifact="com.puppycrawl.tools.checkstyle" -DnewVersion="6.12.1"
and it will update version in target pom.xml from any current to "6.12.1"
mvn versions:set-property -Dproperty="orekit.checkstyle.version" -DnewValue="6.12.1"
and it will update value of property in target pom.xml from any current to "6.12.1"
Use case: https://github.com/checkstyle/checkstyle/blob/master/.travis.yml#L72 we need to update version of certain dependency from old to current SNAPSHOT to make a integration testing.
Right now we use magic of "sed" and other utils.

+1

Same problem here.
I need to change the versions of the project dependencies back to SNAPSHOT

+1
Looks like this pull request does what we want - https://github.com/mojohaus/versions-maven-plugin/pull/18

Done with #18

Made a pull request to solve the versions:set-property issue
https://github.com/mojohaus/versions-maven-plugin/pull/124


Security Group: Egress rule with incorrect to_port takes 3 pulumi ups to correct.

What happened?

Using the code below, start with the egress rule set with from_port=0 and to_port=65535.
Run pulumi up
See error message about how to and from port both need to be 0.
Take a look at Pulumi console and note that the state shows the egress property set with the 0 and 65535 values.
Take a look at AWS console for the security group and note that no outbound rule is defined. Not too surprising given the error.
Change the egress rule so both from_port and to_port are set to 0.
Run pulumi up
See same error message about how both values must be 0 even though they are now set correctly.
Take a look at Pulumi console and note that the state shows the egress is now correctly set to 0 for both from_port and to_port.
Take a look at AWS console and note that there is still no outbound rule defined for the security group.
Run pulumi up again (without any changes to the code) and note that it still shows a diff for the to_port from 65535 to 0. And the update completes successfully.
Take a look at Pulumi console and see that the security group egress rule property is missing.
Take a look at the AWS console and see that there is still no outbound rule shown.
Run pulumi up again and note the diff shows it is adding a complete egress rule and that the update completes successfully.
Take a look at the Puluim console and see the egress rule is now shown.
Take a look at the AWS console and see that the outbound rule is now there.
Subsequent pulumi up shows no changes.

Example
from pulumi_aws import ec2

security_group = ec2.SecurityGroup(
    f"egress-test",
    egress=[
        ec2.SecurityGroupEgressArgs(
            from_port=0, to_port=65535, protocol="-1", cidr_blocks=["<IP_ADDRESS>/0"],
            # from_port=0, to_port=0, protocol="-1", cidr_blocks=["<IP_ADDRESS>/0"],
        )
    ],
)

Output of pulumi about
CLI
Version      3.101.1
Go Version   go1.21.5
Go Compiler  gc
Plugins
NAME    VERSION
aws     6.18.0
python  unknown
Host
OS       darwin
Version  13.5
Arch     x86_64
This project is written in python: executable='/Users/mitch/Downloads/wmg-sg/venv/bin/python3' version='3.11.3'
Current Stack: MitchGerdisch/xxxx/dev
TYPE                                 URN
pulumi:pulumi:Stack                  urn:pulumi:dev::xxxx::pulumi:pulumi:Stack::wmg-sg-dev
pulumi:providers:aws                 urn:pulumi:dev::xxxx::pulumi:providers:aws::default_6_18_0
aws:ec2/securityGroup:SecurityGroup  urn:pulumi:dev::xxxx::aws:ec2/securityGroup:SecurityGroup::egress-test
Found no pending operations associated with dev
Backend
Name           pulumi.com
Dependencies:
NAME        VERSION
pip         23.3.2
pulumi_aws  6.18.0
setuptools  69.0.3
wheel       0.42.0
Additional context
I tested this with Terraform using the latest version of the aws provider and version 5.31.0 which is what the the Pulumi AWS provider is based on.
Terraform does not exhibit this behavior.
You get an error about the to_port=65535 like with Pulumi.
But after changing it to the correct value of 0 and doing a terraform apply, it updates correctly with no errors.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for letting us know @MitchellGerdisch. This looks like a combination of an upstream issue (https://github.com/hashicorp/terraform-provider-aws/issues/34640) and a diff bug (that provides a partial work-around?).

I'm not sure it is the same issue.
I did test the same scenario with TF and although it (correctly) complained about using to_port=65535 after updating to_port=0, a subsequent terraform apply worked as expected. Whereas with Pulumi multiple pulumi ups are needed after fixing the to_port property.

I've went through the steps and it seems go better but not entirely satisfactory now.

errors as before, but pulumi state has no SG. However, AWS console has as SG without egress rules.
after I edit the program and do a pulumi up, I get OK and a new SG created in the console with the expected egress rules
subsequent pulumi up show no changes

So this is almost entirely what we want except the sequence created 2 Security Group instead of one.  That is, validation failure here created an actual AWS security group and then didn't clean it up after it realized there is a problem:
import pulumi
from pulumi_aws import ec2

security_group = ec2.SecurityGroup(
    f"egress-test",
    egress=[
        ec2.SecurityGroupEgressArgs(
            from_port=0, to_port=0, protocol="-1", cidr_blocks=["<IP_ADDRESS>/0"],
        )
    ],
)

Leaving this in the tracker for now, suspect this aspect reproduces upstream.

CLI
Version      3.130.0
Go Version   go1.22.6
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  aws     6.52.0
language  python  unknown

Host
OS       darwin
Version  14.6.1
Arch     arm64

This project is written in python: executable='/Users/anton/Library/Mobile Documents/com~apple~CloudDocs/pulumi-bugs/pulumi-aws-3257/venv/bin/python' version='3.10.13'

Current Stack: anton-pulumi-corp/pulumi-aws-3257/dev

TYPE                                 URN
pulumi:pulumi:Stack                  urn:pulumi:dev::pulumi-aws-3257::pulumi:pulumi:Stack::pulumi-aws-3257-dev
pulumi:providers:aws                 urn:pulumi:dev::pulumi-aws-3257::pulumi:providers:aws::default_6_52_0
aws:ec2/securityGroup:SecurityGroup  urn:pulumi:dev::pulumi-aws-3257::aws:ec2/securityGroup:SecurityGroup::egress-test

Found no pending operations associated with dev

Backend
Name           pulumi.com
URL            https://app.pulumi.com/anton-pulumi-corp
User           anton-pulumi-corp
Organizations  anton-pulumi-corp, moolumi, demo, pulumi
Token type     personal

Dependencies:
NAME        VERSION
pip         24.2
pulumi_aws  6.52.0
setuptools  75.1.0
wheel       0.44.0

Pulumi locates its logs in /var/folders/gd/3ncjb1lj5ljgk8xl5ssn_gvc0000gn/T/com.apple.shortcuts.mac-helper// by default


Not recognize CHARACTER SET in table creation

When use below table creation DDL, JSqlParser cannot find out the encoding for name column.  It only recognizes "NOT NULL" as column spec strings for name column .
CREATE TABLE test (
id int(11) NOT NULL,
name varchar(64) CHARACTER SET GBK NOT NULL,
age int(11) NOT NULL,
score decimal(8,2) DEFAULT NULL,
description varchar(64) DEFAULT NULL,
creationDate datetime DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
JSqlParser version: 2.1

That is because JSqlParser stores the character set within the column data type and not within the additional parameters:
CreateTable stmt = (CreateTable) CCJSqlParserUtil.parse(sql);
ColumnDefinition colName = stmt.getColumnDefinitions().stream()
                .filter(col -> col.getColumnName().equals("name"))
                .findFirst().orElse(null);
assertNotNull(colName);
assertEquals("GBK", colName.getColDataType().getCharacterSet());

I introduced a test like this within JSqlParser, as well.

I got the character set successfully through the test codes.
Close the issue now,  thank you.


Sugarizer don't work on Firefox in private mode

When Sugarizer is launched with Firefox in private mode, the message FATAL ERROR: indexedDB not supported, could be related to use of private mode appears several time and some actions do nothing or stop working.
This issue appears starting https://github.com/llaske/sugarizer/commit/76234ea068d6be234a157362b4c9b0d626f6905a

Starting https://github.com/llaske/sugarizer/commit/76234ea068d6be234a157362b4c9b0d626f6905a, Sugarizer use IndexedDB feature to store local content.
There is an issue in Firefox that prevent usage of IndexedDB in private mode thought it works on other browsers (Chrome, Safari, ...).
The Firefox issue is referenced here: https://bugzilla.mozilla.org/show_bug.cgi?id=781982
We could expect that this error will be fixed shortly.

@llaske sugarizer now works with Firefox in private mode. If this was the issue ,I think it can be closed ow. If this wasn't the issue, i request for some more information to reproduce the error so that I can try to fix it.

@abhishektanwar you can login or create a new user but once connected you can't create anything in the Journal.


Auto-generated header ids can contain invalid CSS selectors

What version of Hugo are you using (hugo version)?

$ 88.1

Does this issue reproduce with the latest release?
Yes - this is the latest version
If I have a markdown header which begins with a number Hugo generates an id beginning with a number. For example ## 1 Test generates
1 Test…

According to w3.org (https://www.w3.org/TR/CSS21/syndata.html#characters) In CSS, identifiers (including element names, classes, and IDs in selectors) … cannot start with a digit, two hyphens, or a hyphen followed by a digit.
This causes the error  Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '#1-test' is not a valid selector. if I try to do a document.querySelector() on this selector. In tests, this seems to be caused by the leading digit.

The querySelector code is used, for example, in a recent Pull Request on the Docsy theme (https://github.com/google/docsy/pull/506)
This format of anchor is produced with both Blackfriday and Goldmark as the markup generator and is independent of the setting of autoHeadingIDType.

Workarounds...
1) Use an attribute (either format):
## 1 Test {#_1-test}

## 2 Test {id="_2-test"}

2) Use a render hook:
layouts/_default/_markup/render-heading.html
{{- $anchor := replaceRE `(^\d)` "_$1" .Anchor -}}
<h{{ .Level }} id="{{ $anchor }}">{{ .Text | safeHTML }}</h{{ .Level }}>
{{- /* Remove trailing newlines */ -}}

Thoughts...
Hugo is generating valid HTML, so I'm not convinced that this is a bug.

Hi,
Thanks for your response. Thanks also for the workarounds, the first is impractical on my site, but I will investigate the second.
Your response has triggered me to do a bit more research. My thoughts are as follows:

I agree that Hugo is generating valid HTML 5 ids. The restriction on starting with a number is, however, in the HTML 4 definition.
Hugo appears to sanitize the ids - it replaces characters such as &, +, ^, ~, …, and £ with hyphens. It is therefore confusing that it seems to be trying to produce anchors in HTML 4 compatible versions, but doesn't actually produce valid ones.
Many articles acknowledge that leading numbers are permissible, but argue for starting with a letter anyway for compatibility: e.g. Mozilla, W3 Schools, and StackOverflow 😀

So agreed: it is not a bug.
Can I make it a feature request?

@MarkvanMents This would be a breaking change (e.g., existing links to example.org/foo#1-test would be broken). Given that (a) this is the first time the issue has been raised, and (b) there is an easy workaround, I am inclined to leave this alone.
Thoughts?

Sorry for coming late to the party.
I would say starting a number should be rare (I guess you're doing that to order them ... but isn't that what CSS is for?), which also means that fixing this shouldn't create too much protests (cross fingers!).


Handle PostgreSQL binary resources

Description
PostgreSQL (PDO) returns binary values as resources. Converting those to UUIDs is possible with this change.
Motivation and context
Fixes https://github.com/ramsey/uuid-doctrine/issues/225 where the uuid_binary type was unusable with PostgreSQL.
How has this been tested?
Added 1 new unit test, cross-checked with MySQL 8 and MariaDB 10.
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)

PR checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING.md document.
[ ] I have added tests to cover my changes.

Thanks for the PR @jankal , this solves the issue!
Any updates on this PR @ramsey ?

Thanks for the reminder, @thePanz. I'll try to take a look very soon.

Sorry for the delay. Thank you for contributing! 🎉


Update MD file on new branch 2017-32-15_05-12-26

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Fix Codacy issue

Fix Codacy issue to improve rating:
In base.py:
Too many positional arguments for method call
39
self.wait_for_clickable(*self.locators.CLOSE_ISSUE).click()

What needs to be done here exactly?


To-Do list : Remove and Add Tasks

In this branch

Removed all hardcoded items from the tasks array.
Created a new JavaScript file for the new functionality.
Implemented a function for adding a new task (add a new element to the array).
Implemented a function for deleting a task (remove an element from the array).
Implemented a function for editing task descriptions.

@Whoistolu Good day, on my computer it looks different and is working correctly you could guide me to understand so I could fix it if there's a problem on my side?
[

]


Lazer crashes on big black, on SS replays on hard maps sometimes it shows that they got a good (100) when they didn't, and sometimes osu lazer breaks where you can't play the game. (mobile issues)

so i don't have any pictures because this was on mobile and it was night and i was tired, but all of this is true sometimes on SS replays (hard maps) shows a good, meh or miss instead of great and on results it shows the still got a SS and no goods, mehs, or miss. And on big black and probably other high circle and slider count beatmaps, it crashes. The game is unresponsive, but the music is still playing.

This is the wrong repository to report lazer issues, this one pertains to the framework specifically.
Please keep issues focused in scope to one problem at a time.
The replay discrepancy is a known issue (see ppy/osu#5514).
Performance is a constant work-in-progress, but is not an immediate focus.

Closing on all above counts. Please think twice before opening issues and use the search functionality and issue tags.