fix(graphql-elasticsearch-transformer): to support non string key in es

Updated the streaming lambda function support to handle non string type in key directive fields
fix #5140
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks for the fast resolution :-). I am new to Amplify, and am not familiar with how long it will take for the fix to be making it to the latest applify cli version, and what version should this fix be in?

Thanks for the fast resolution :-). I am new to Amplify, and am not familiar with how long it will take for the fix to be making it to the latest applify cli version, and what version should this fix be in?

The fix should be included in the next weeks release. I can't give you the exact date or version number as they are determined based on the changes included in the next release


Training sampling

Add ability to do uniformly-weighted image selection at runtime in the training routine, if the user desires. Currently, training images are selected randomly with weight equal to the sum of the inverse class frequency of the objects in each image. The user should be able to specify which of these methods they want.

Resolved by commit fbf8c2b .


The purpose of Pulsar

Hi, i am reading your project, why don't u use Kafka or RabbitMQ as message queue instead of Pulsar, can you tell me why you choose Pulsar, do you know the pros and cons of Pulsar, if yes, can tell me, thank u so much

Hi, I'm too busy to read your question just now. Compared to kafka, pulsar is relatively new and has some late-mover advantages, such as geographic replication features, strong consistency of things, etc. Of course, pulsar is not the only MQ in the design. At present, we are trying to abstract the public layer, which can easily access kakfa/pulsar/rabbitmq/elasticsearch, etc., to reduce the additional deployment cost of users

@HelloTo4x


Bug: RuntimeError

Home Assistant now gives the next error:
RuntimeError: Detected that custom integration 'hass_agent' calls hass.async_create_task from a thread other than the event loop, which may cause Home Assistant to crash or data to corrupt. For more information, see https://developers.home-assistant.io/docs/asyncio_thread_safety/#hassasync_create_task at custom_components/hass_agent/init.py, line 147: hass.async_create_task(handle_apis_changed(hass, entry, apis)). Please report it to the author of the 'hass_agent' custom integration.
I can't find the cause of this error, but it seems to be serious.
Coreversion: 2024.6.1
Supervisor: 2024.06.0
Operating System: 12.3
Frontend: 20240605.0
Hass.Agent: 2022.14.0

I'm getting the same error message!

Started seeing this error as well, not sure how long it's been happening.
However I'm investigating as something keeps maxing out the RAM in the container, so I'm going to disable this one just in case.


Transaction, PG Connection and Async IO

Does transaction requires a given Postgres connection to be reserved exclusively until commit command or it can be used in another transaction ?
Assuming that someone is using this driver for web application for which all HTTP requests needs transaction, if Postgres connection need to reserved exclusively, then there would be 1 Postgres connection per HTTP request. I wonder How much benefit one might achieve by using this async (non-blocking) driver instead of sync (blocking) jdbc driver ?

If your full request is running in a transaction, than you need as many connections as you want to serve requests concurrently. You still have the benefits of non-blocking, although your application will only be as responsive as your database backend can be.

Cool thanks. Are there any real world benchmark results compared to JDBC driver which I can look at ?


1.5 Properties:  ComplianceLevel doesn't match Examples

In pulling down this data, the 'complianceLevel' field in section 1.5 Properties doesn't match 1.6 Examples where it has an 's' on the end.  I'm using the field complianceLevels with the 's' so hopefully you just update section 1.5.

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

ID: 3fac6a9e-cd46-de91-7808-d2a7a2916e26
Version Independent ID: 3fac6a9e-cd46-de91-7808-d2a7a2916e26
Content: Security baselines assessment configurations
Content Source: microsoft-365/security/defender-endpoint/get-security-baselines-assessment-configurations.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @siosulli
Microsoft Alias: siosulli

@PaulFeaser Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/11559
Once the author approves, the changes will be live.
Thanks
Sri

@msbemba Thank you!


Exercise dict, branch v2-fem

[X ] Describe the bug
yarn test produces errors, and the test does not pass when running the solution

[ X] To Reproduce
Solution for dict exercise assumed to be located at this location

yarn test is run in challenges/dict. produces error shown in screenshot.

[ X] Screenshots (optional)
If applicable, add screenshots to help explain your problem.

Fixes for this and a couple of other minor things in #264 . v2-fem branch has been updated, and tests should now pass on it

Closing b/c #264 is merged. Please feel free to re-open if necessary


Allow users to start auto-annotation again if the previous request fails

Motivation and context

Currently, if an auto-annotation request fails, the UI doesn't re-enable the "Automatic annotation" menu item. This seems like a mistake, since at that point there's no reason why a new request could not be started - in fact, it's possible to do if you just refresh the page.
Fix this by only disabling the menu item if the current AR is still in progress.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[x] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

New Features

Users can now restart the automatic annotation process directly from the UI if a previous request fails, enhancing recovery options.

Version Updates

Updated the application version from 1.66.1 to 1.66.2.

Improvements

Enhanced state management for inference tasks, providing a more accurate reflection of task statuses in the UI.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.26%. Comparing base (4354f72) to head (69d5c4a).
Report is 10 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8587      +/-   ##
===========================================
+ Coverage    74.24%   74.26%   +0.02%
===========================================
  Files          403      403
  Lines        43287    43313      +26
  Branches      3914     3914
===========================================
+ Hits         32137    32165      +28
+ Misses       11150    11148       -2

Components
Coverage Δ

cvat-ui
78.71% <ø> (+0.04%)
:arrow_up:

cvat-server
70.47% <ø> (+<0.01%)
:arrow_up:


Hi I'm Rapptd with this extension.

I have the Power Tabs sidebar open all the time, so I was wondering if you could change the click function on the group Title from 'expanding the list' to 'Going to the desired group'.
Click on the chevron  to expand the group.
Click on the Group name to goto group.


"stdout maxBuffer exceeded" error when fetching many commits

I recently ran into this issue when using repo.commits and trying to fetch 500+ records.
Depending on the amount of text from the commits it would fail when fetching between 500 to 600 commits due to the stdout maxBuffer filling up.
I added this http://cl.ly/image/140L2o1S0j0K to git.js and it worked for my repo.
Is there a way you could allow this to be set up as an option, or maybe increasing it by default in order to support fetching larger repos?
Thanks

I had success with the same approach.  I know this is an old issue, but this would be an extremely helpful addition.
      exec(bash, {
        cwd: git_dir,
        encoding: 'binary',
        maxBuffer: 524288
      }, callback);

Adjusting the maxBuffer sent to exec allowed me to get around the problem.


Improve base-unit representation

[ ] Use kg instead of g.
[ ] Make sure that it is always sorted in the same way
[ ] Use exponent-notation instead of division (m s^(-1) instead of m/s). This makes it easier to compare different representations

Closed in favor of https://github.com/sharkdp/insect/issues/58


GameService Tests are Flaky

Test Fusion

Status?

@dzlier-gcp May have an update.

ping

GameServices No longer appears in our repo.


It doesnt work well

When I play the video It's still below the Image video.
I am using rails-assets-video.js 4.12.12 and rails-assets-videojs-youtube 1.2.12
My code is :
<video id="vid1" src="" class="video-js vjs-default-skin" controls preload="auto" width="640" height="360">   </video>
<script>   videojs('vid1', { "techOrder": ["youtube"], "src": "http://www.youtube.com/watch?v=xjS6SftYQaQ","controls": true, });   </script>

You'll need to be more specific on how to reproduce the bug


Use volta cache server

Using the volta cache server (as opposed to dev) for the claims exchange as it is a little more stable and it makes more sense for partners we're integrating with to be using the Volta Switchboard (instead of the dev Switchboard)

Temporary pause on using volta for now as cache-server has a bug that needs to be fixed


SQL database, elastic pool, and capabilities 2017-10-01-preview

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

The service is not yet fully deployed, but it is ok to merge because package-composite-v3 is not yet default tag. When the service is available in production, @payiAzure will issue follow-up PR where she updates the default tag to package-composite-v3.

Automation for azure-libraries-for-java

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

There are some model validation errors in RecommendedElasticPools_ListByServer that I am not planning to fix. The model change is deliberate in order to decouple Database API from RecommendedElasticPools.

There are still errors/warnings:

Consider changing operation name
Lists operations missing and some documentation
Model validation errors

Yeah, these remaining warnings are all in existing files that are unrelated to this change. I don't know why they are showing up for this PR, but I won't fix them.

More specifically:

Missing descriptions: in existing longTermRetention.json file that this PR did not touch.
Consider changing operation name: these are already used in SDKs so would be SDK breaking change.
Model validation: these are due to genuine service bug where these old api versions are actually not returning time zone in the datetime string. They are unrelated to this change, just showing up because I modified sql.core.json where these are used.

Some of them are related to this PR. Let me specify better some of them:

Model validation error. This error is on specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/capabilities.json file.
Other errors I linked specify which lines from the CI logs to take a look at.

I recommend searching for 2017-10-01-preview in the CI logs for the model validation and the linter, so you don't even look at issues from other files.

PostOperationIdContainsUrlVerb for Databases_Rename ( https://travis-ci.org/Azure/azure-rest-api-specs/jobs/357637299#L847-L860 ): I would prefer to leave it as-is since it has already shipped in SDKs as Databases_Rename. I think that this warning didn't exist when this operation was originally added (in a previous api version). What do you think?
TrackedResourceListByResourceGroup for Databases ( https://travis-ci.org/Azure/azure-rest-api-specs/jobs/357637299#L1057-L1140 ) - we actually tried implementing this but ARM doesn't support list by resource group for tracked resources under other tracked resources.
Capabilities model parameter name warning ( https://travis-ci.org/Azure/azure-rest-api-specs/jobs/357637300#L766 ) - fixed

Thank you for your attention to detail and spotting these warnings that I had missed :)

Thanks so much Mariana! I am going on vacation so another one of my teammates such as @payiAzure or @nathannfan will confirm when it has reached the first production cluster and is therefore ready to merge. :)

@mcardosos , @jaredmoo, @nathannfan  Hi Mariana, I just confirmed that our changes reached the first production cluster on Sunday, and it is ready to merge this PR.


refactor(psql_pagination.go): optimize pagination info using Count with Limit(1)

Optimizes obtaining the page info. A Count of all the items could be expensive. This version uses Count with a Limit of 1.

Updated to replace COUNT with the existence check.


Support for running under async-std executor

Describe the bug
Since the crate depends on async-std and has generic futures functions it seems like the crate is meant to work when running under the async-std executor, rather than just tokio.
However, since the crate uses reqwest as its HTTP client, even the futures-based functions only function under tokio due to reqwest only supporting tokio.
To Reproduce
use s3::bucket::Bucket;
use s3::creds::Credentials;

#[async_std::main]
async fn main() {
    let credentials = Credentials::from_env().unwrap();

    let bucket = Bucket::new(
        "foo",
        s3::Region::Custom {
            region: "eu-central-1".to_string(),
            endpoint: "eu-central-1.linodeobjects.com".to_string(),
        },
        credentials,
    ).unwrap();

    bucket.put_object("foo", b"bar").await.unwrap();
}

Backtrace
thread 'main' panicked at 'not currently running on the Tokio runtime.', /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.22/src/runtime/handle.rs:118:28
stack backtrace:
   0: rust_begin_unwind
             at /rustc/ffa2e7ae8fbf9badc035740db949b9dae271c29f/library/std/src/panicking.rs:483:5
   1: core::panicking::panic_fmt
             at /rustc/ffa2e7ae8fbf9badc035740db949b9dae271c29f/library/core/src/panicking.rs:85:14
   2: core::option::expect_failed
             at /rustc/ffa2e7ae8fbf9badc035740db949b9dae271c29f/library/core/src/option.rs:1260:5
   3: core::option::Option<T>::expect
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:349:21
   4: tokio::runtime::handle::Handle::current
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.22/src/runtime/handle.rs:118:9
   5: tokio::runtime::blocking::pool::spawn_blocking
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.22/src/runtime/blocking/pool.rs:65:14
   6: tokio::task::blocking::spawn_blocking
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.22/src/task/blocking.rs:130:9
   7: <hyper::client::connect::dns::GaiResolver as tower_service::Service<hyper::client::connect::dns::Name>>::call
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/dns.rs:120:24
   8: <S as hyper::client::connect::dns::sealed::Resolve>::resolve
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/dns.rs:338:13
   9: hyper::client::connect::dns::resolve::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/dns.rs:348:5
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  11: hyper::client::connect::http::HttpConnector<R>::call_async::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/http.rs:306:25
  12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  13: <hyper::client::connect::http::HttpConnector<R> as tower_service::Service<http::uri::Uri>>::call::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/http.rs:247:40
  14: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  15: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/future.rs:119:9
  16: <hyper::client::connect::http::HttpConnecting<R> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/connect/http.rs:387:9
  17: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/either.rs:63:36
  18: <hyper_tls::client::HttpsConnector<T> as tower_service::Service<http::uri::Uri>>::call::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-tls-0.4.3/src/client.rs:127:23
  19: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  20: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/future.rs:119:9
  21: <hyper_tls::client::HttpsConnecting<T> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-tls-0.4.3/src/client.rs:156:9
  22: reqwest::connect::Connector::connect_with_maybe_proxy::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.10.8/src/connect.rs:346:26
  23: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  24: reqwest::connect::with_timeout::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.10.8/src/connect.rs:500:9
  25: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  26: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/future.rs:119:9
  27: <hyper::service::oneshot::Oneshot<S,Req> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/service/oneshot.rs:50:28
  28: <F as futures_core::future::TryFuture>::try_poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.7/src/future.rs:83:9
  29: <futures_util::future::try_future::into_future::IntoFuture<Fut> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/try_future/into_future.rs:31:9
  30: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/map.rs:49:37
  31: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  32: <futures_util::future::try_future::MapErr<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  33: <F as futures_core::future::TryFuture>::try_poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.7/src/future.rs:83:9
  34: <futures_util::future::try_future::into_future::IntoFuture<Fut> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/try_future/into_future.rs:31:9
  35: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/map.rs:49:37
  36: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  37: <futures_util::future::try_future::MapOk<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  38: <F as futures_core::future::TryFuture>::try_poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.7/src/future.rs:83:9
  39: <futures_util::future::try_future::try_flatten::TryFlatten<Fut,<Fut as futures_core::future::TryFuture>::Ok> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/try_future/try_flatten.rs:45:34
  40: <futures_util::future::try_future::TryFlatten<Fut1,Fut2> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  41: <futures_util::future::try_future::AndThen<Fut1,Fut2,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  42: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/either.rs:63:36
  43: <hyper::common::lazy::Lazy<F,R> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/common/lazy.rs:59:27
  44: futures_util::future::future::FutureExt::poll_unpin
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/mod.rs:561:9
  45: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/select.rs:92:36
  46: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/map.rs:49:37
  47: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  48: <futures_util::future::future::flatten::Flatten<Fut,<Fut as core::future::future::Future>::Output> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/flatten.rs:45:36
  49: <futures_util::future::future::Then<Fut1,Fut2,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  50: <F as futures_core::future::TryFuture>::try_poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.7/src/future.rs:83:9
  51: <futures_util::future::try_future::into_future::IntoFuture<Fut> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/try_future/into_future.rs:31:9
  52: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/future/map.rs:49:37
  53: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  54: <futures_util::future::try_future::MapOk<Fut,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  55: <F as futures_core::future::TryFuture>::try_poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.7/src/future.rs:83:9
  56: <futures_util::future::try_future::try_flatten::TryFlatten<Fut,<Fut as futures_core::future::TryFuture>::Ok> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/try_future/try_flatten.rs:45:34
  57: <futures_util::future::try_future::TryFlatten<Fut1,Fut2> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  58: <futures_util::future::try_future::AndThen<Fut1,Fut2,F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/lib.rs:113:13
  59: hyper::client::Client<C,B>::retryably_send_request::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/mod.rs:255:26
  60: <futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.7/src/future/poll_fn.rs:54:9
  61: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/future.rs:119:9
  62: <hyper::client::ResponseFuture as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.13.8/src/client/mod.rs:627:9
  63: <reqwest::async_impl::client::PendingRequest as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.10.8/src/async_impl/client.rs:1318:29
  64: <reqwest::async_impl::client::Pending as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.10.8/src/async_impl/client.rs:1297:51
  65: s3::request::Request::response_future::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-s3-0.26.3/src/request.rs:486:24
  66: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  67: s3::request::Request::response_data_future::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-s3-0.26.3/src/request.rs:503:24
  68: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  69: s3::bucket::Bucket::put_object_with_content_type::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-s3-0.26.3/src/bucket.rs:772:12
  70: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  71: s3::bucket::Bucket::put_object::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-s3-0.26.3/src/bucket.rs:807:9
  72: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  73: fra::main::main::{{closure}}
             at ./src/main.rs:19:5
  74: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  75: fra::main::{{closure}}
             at ./src/main.rs:5:1
  76: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  77: <async_std::task::builder::SupportTaskLocals<F> as core::future::future::Future>::poll::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-std-1.6.5/src/task/builder.rs:199:17
  78: async_std::task::task_locals_wrapper::TaskLocalsWrapper::set_current::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-std-1.6.5/src/task/task_locals_wrapper.rs:60:13
  79: std::thread::local::LocalKey<T>::try_with
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:272:16
  80: std::thread::local::LocalKey<T>::with
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:248:9
  81: async_std::task::task_locals_wrapper::TaskLocalsWrapper::set_current
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-std-1.6.5/src/task/task_locals_wrapper.rs:55:9
  82: <async_std::task::builder::SupportTaskLocals<F> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-std-1.6.5/src/task/builder.rs:197:13
  83: <futures_lite::future::Or<F1,F2> as core::future::future::Future>::poll
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-lite-1.11.2/src/future.rs:526:33
  84: async_executor::Executor::run::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-executor-1.3.0/src/lib.rs:214:9
  85: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  86: async_executor::LocalExecutor::run::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-executor-1.3.0/src/lib.rs:393:9
  87: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  88: async_io::driver::block_on
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-io-1.1.10/src/driver.rs:142:33
  89: async_global_executor::reactor::block_on::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-global-executor-1.4.3/src/lib.rs:48:22
  90: async_global_executor::reactor::block_on
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-global-executor-1.4.3/src/lib.rs:55:9
  91: async_global_executor::block_on::{{closure}}
             at /home/kyrias/.cargo/registry/src/github.com-1ecc6299db9ec823/async-global-executor-1.4.3/src/lib.rs:205:36
  92: std::thread::local::LocalKey<T>::try_with
             at /home/kyrias/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:272:16
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Expected behavior
Uploads should function while running under async-std.
Environment

Rust version: nightly-2020-10-24
lib version: 0.26.3

@kyrias thanks for the report, I've been eyeing this improvement for a while now, will take a closer look at implementation and report back :)

Awesome, thanks!

@kyrias Hi, I actually just ran into the same issue, I was unsure if there was a way to plug surf and async-std into the crate through some sort of configuration. I tried a few things before realizing it was reqwest.
@durch would we need to tell the crate to use surf & async-std when the fix lands?

@kennetpostigo yes, it'll be feature flagged, and turning it on will swap out reqwest for surf

#130 will land today, that in turn will make it easy to swap out backends, async-std should land in the next few days.

Code is done, tests are passing. Last thing left is documentation, I'm a bit obsessive here, but I'd like to nail it. There are a lot of features now, and that could be confusing for folks

Docs done as well, I've pushed 0.27-beta0 to crates.io in case anyone wants to test.
rust-s3 = {version = "0.27-beta0", default-features = false, features = ["with-async-std"]}

Turns on the async-std backend. In addition in case you need a sync version of the methods anywhere in the code there is the blocking feature which will generate a *_blocking method for each async method using async_std::task::block_on.

Docs done as well, I've pushed 0.27-beta0 to crates.io in case anyone wants to test.
rust-s3 = {version = "0.27.0-beta0", default-features = false, features = ["with-async-std"]}

is how you can turn on the async-std backend. In addition in case you need a sync version of the methods anywhere in the code there is the blocking feature which will generate a *_blocking method for each async method using async_std::task::block_on.

Just updated my gallery updated to -beta1, and it seems to be working well!


Fix DatePicker uses incorrect overlay color from DatePickerTheme and add missing tests

fixes YearPickerState in calendar_date_picker is using dayOverlayColor instead of yearOverlayColor
Description

Fix year selection uses incorrect overlay color from DatePickerTheme
Update defaults tests to check for overlay color for different modes
Add tests to check overlay color is resolved.

Code sample

expand to view the code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        datePickerTheme: const DatePickerThemeData(
          yearOverlayColor: MaterialStatePropertyAll<Color>(Colors.green),
          dayOverlayColor: MaterialStatePropertyAll<Color>(Colors.amber),
        ),
        useMaterial3: true,
      ),
      home: Directionality(
        textDirection: TextDirection.ltr,
        child: Material(
          child: Center(
            child: DatePickerDialog(
              initialDate: DateTime(2023, DateTime.january, 25),
              firstDate: DateTime(2022),
              lastDate: DateTime(2024, DateTime.december, 31),
              currentDate: DateTime(2023, DateTime.january, 24),
            ),
          ),
        ),
      ),
    );
  }
}

          yearOverlayColor: MaterialStatePropertyAll<Color>(Colors.green),
          dayOverlayColor: MaterialStatePropertyAll<Color>(Colors.red),

Before

After

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

CC @QuncCccccc - this may break golden image tests.

It looks like there is an extra circle drawn on the web in the pressed state. 🤔


Conversation history

Hey is there a clear example anywhere on how to have it maintain conversation history?
I want to be able to provide it the previous human/ai responses and have context of them.
v0.5.0 working great by the way!

solved!
did something like this:
  // Get the input text prompt.
  const prompt = inputs['input'][0] as string

  // Initialize conversationMessages array
  const conversation = inputs['conversation']?.[0] as any
  const conversationMessages: string[] = []

  // Add elements to conversationMessages
  conversation?.forEach(event => {
    const message =
      event.observer === event.sender
        ? `${Anthropic.AI_PROMPT} ${event.content}`
        : `${Anthropic.HUMAN_PROMPT} ${event.content}`

    conversationMessages.push(message)
  })

  // append the new user prompt to the conversation messages
  conversationMessages.push(`${Anthropic.HUMAN_PROMPT} ${prompt}`)

  // combine all messages into one string and append the AI prompt to the end
  const conversationMessagesString =
    conversationMessages.join() + `${Anthropic.AI_PROMPT}`

Thanks @coffeeorgreentea! We'll put together an example script showcasing this behaviour as well to help anyone else out in the future.


Update SessionConfigurator.cs to fix inference error when running onnx model

Fixes the inference issue when running an onnx model on Windows (issue encountered with RX 570 and RTX 3060) and MacOS (https://github.com/edbeeching/godot_rl_agents/issues/115). Set the inference to run on CPU for all cases (including Intel GPUs, as they may show the same error), until issues with using DirectML are solved. Also auto-aligned the code.

Hello,
Automatically updating the plugin so that examples use the latest plugin
from the repo sounds good to me, the only part I'm not sure of is the
.csproj file, since that one needs to have the name of the example project
(unless they are all named the same as the plugin project). A similar issue
exists when installing the plugin in a new Godot project, you get the
.csproj file but you have to do some copying or editing to use them in the
project.
On Thu, Jun 29, 2023 at 2:57 PM Edward Beeching @.***>
wrote:

Merged #6 https://github.com/edbeeching/godot_rl_agents_examples/pull/6
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/edbeeching/godot_rl_agents_examples/pull/6#event-9676595780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYTZURFIJCHJ56ACZ66EJLXNV3VBANCNFSM6AAAAAAZMIYMLA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


Make it more clear that video_player doesn't support audio (even if it's accidentally supported in some platforms)

Use case
When looking for packages to play audio, it is very common (at least for me) to look for official packages as they are usually more widely used and better supported. Trying video_player seems to be a common pattern and since it mostly work (at least in Web and Android), some users (like me) start using it, only to eventually bump into some wall and finding out audio is not officially supported and getting a "tough luck you spent time with video_player but this won't fix".
This is a non-exhaustive list of audio-related issues I found, which suggests I'm not alone here:

#38480
#47105
#75508
#48008

There is even people answering questions and recommending to use video_player as an audio player in stackoverflow:

https://stackoverflow.com/questions/59499342/how-to-play-audio-on-the-all-platforms-including-web-in-flutter

Proposal

Just add some clear message at the top of the package home page saying that even when audio-only playing might work incidentally, it is not officially supported and it should not be used, and ideally listing alternative package to reproduce audio (like just_audio). It would be also put another note in the supported formats section, since when you click in there you'll find audio-only formats listed as supported.

Whilst this is a sound proposal, I would like to see the video_player support audio formats as well. The benefits of having a first-party plug-in for such a fundamental capability is huge.
The underlying components do support audio and there is already support for audio that in web and Android. The iOS uses AVPlayer which supports various audio formats.


Pull organization data from folio for data export vendors

folio-test has a POD organization with the data to connect to POD: https://folio-test.stanford.edu/organizations/view/7c010c6a-dc51-46ff-b698-7ee5d9a6dfd1
Follow the VMA pattern of populating the airflow connections with a task that pulls data from folio.

Duplicate of https://github.com/sul-dlss/libsys-airflow/issues/884


[fix] bad conformsTo url in lpfConverter

Missing fix in the unit tests: https://github.com/readium/readium-desktop/blob/40ed7ac45f02aba5fd4f590c2890cf22f9f2cdcf/test/lpfConverter.test.ts#L128


Ability to revoke/cancel a request

Description
A privacy request manager may need to cancel a request in case it was submitted in error or approved in error. Furthermore, as part of Consumer Report's DRP specification, they do require support for revoking a request in the event that the consumer chooses to do so.
This may be challenging to do for in progress requests at this time. We have limited the scope of this ticket to support cancelling a request only if the request is in a NEW state.
Acceptance Criteria

Demonstrate that a request can be cancelled (limit to only requests that haven't started processing aka NEW requests)
If a request was cancelled, demonstrate that the status of the request moves to "Cancelled"

on the SR landing/list page, we should update the status dropdown to include "cancelled" as a filterable status
you should not be able to restart cancelled requests (users should submit new requests)

https://github.com/ethyca/fidesops/issues/418


Demo code

Hi,
Thank you for your excellent work.
Can you provide a Python script that can run inference from 2 images?
By the way, have you tested the end-2-end inference speed?
Looking forward to hearing from you soon.

Hi. Sorry for the late response.

Can you provide a Python script that can run inference from 2 images?

For the demo code, you can refer to our Jupyter Notebook scripts in qualitative/qualitative-matches.ipynb. It provides a example for matching a pair of images using different features.

have you tested the end-2-end inference speed?

We mainly tested the runtime of ALIKE-L on Jetson Xavier NX. It took about 125ms for the extraction of ALIKE, and our FeatureBooster took extra 46ms to get the ALIKE+Boost-X.
Besides, by using our Jupyter Notebook scripts in qualitative/qualitative-matches.ipynb, you can easily to tested the end-to-end inference speed by yourself.


New solvers

Here's an issue to gather all the solvers we might want to implement someday, I'll update the list with new propositions.
All

[ ] ODE fixed step Runge-Kutta of order 5(4) (@gautierronan)
[ ] Dormand–Prince of order 8 (@gautierronan)
[ ] torchdiffeq ODE solvers
[ ] torchdyn ODE solvers

Schrödinger equation sesolve()

[ ] Propagator by diagonalizing the Hamiltonian
[ ] Truncated Taylor series expansion of the propagator

Lindblad Master Equation mesolve()

[x] Propagator by exponentiating the Lindbladian explicitely
[ ] Propagator by diagonalizing the Lindbladian
[ ] Truncated Taylor series expansion of the propagator

Stochastic Master Equation (diffusive) smesolve()

[x] Rouchon (@pierreguilmin)
[ ] Rouchon v2 (exact trace normalisation and smart trajectory sampling) (@pierreguilmin)
[ ] Milstein (see https://en.wikipedia.org/wiki/Milstein_method)
[ ] torchsde SDE solvers

Replaced by https://linear.app/dynamiqs/issue/DYN-61/implement-new-solvers.


Git lfs fetch failed with exit code 2

Have you tried troubleshooting?
Troubleshooting doc - Yes
Agent Version and Platform
Version of your agent? 2.165.2
OS of the machine running the agent? Linux
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com)
What's not working?
Git checkout fails when files tracked with git lfs should be downloaded:
git version 2.25.1
git-lfs/2.10.0 (GitHub; linux amd64; go 1.13.4)

git -c http.https://git.***.com.extraheader="AUTHORIZATION: basic ***" lfs fetch origin c4f979100309f660f6b914f7f5accdd095c6b702
##[debug]Starting process:
##[debug]  File name: '/usr/bin/git'
##[debug]  Arguments: '-c http.https://git.***.com.extraheader="AUTHORIZATION: basic ***" lfs fetch origin c4f979100309f660f6b914f7f5accdd095c6b702'
##[debug]  Working directory: '/home/vsts/work/1/s'
##[debug]  Require exit code zero: 'False'
##[debug]  Encoding web name:  ; code page: ''
##[debug]  Force kill process on cancellation: 'False'
##[debug]  Redirected STDIN: 'False'
##[debug]  Persist current code page: 'False'
##[debug]  Keep redirected STDIN open: 'False'
##[debug]  High priority process: 'False'
##[debug]Updated oom_score_adj to 500 for PID: 2783.
##[debug]Process started with process id 2783, waiting for process exit.
fetch: Fetching reference c4f979100309f660f6b914f7f5accdd095c6b702
LFS: Client error: https://git.***.com/storage/lfs/8836/objects/daa50021370ddddefe66a340a008e48458fde248a18f70de4ae04719d846ea38
LFS: Client error: https://git.***.com/storage/lfs/8836/objects/904df687607c5486ad1f6e29a467e5b7a00914ad94dc19067ffcbfc341472065
##[debug]STDOUT/STDERR stream read finished.
##[debug]Exited process 2783 with exit code 2
LFS: Client error: https://git.***.com/storage/lfs/8836/objects/d670bbf756e8e16cd90d4242b59825ad2a32d4500bbc5d005f3a0b84648f98b3
LFS: Client error: https://git.***.com/storage/lfs/8836/objects/9b8483fb1bb84a8c5f1018944def162f1889a8baf91013c093c02d0c0bd67562
error: failed to fetch some objects from 'https://git.***.com/***.git/info/lfs'
##[debug]STDOUT/STDERR stream read finished.
##[debug]Finished process 2783 with exit code 2, and elapsed time 00:00:24.1173237.
##[warning]Git lfs fetch failed with exit code 2, back off 2.434 seconds before retry.

This is not the first issue concerning git lfs checkout, see #2272, #2079, #1548 and #1382. Why does this keep happening?

I'm seeing the same errors with version 2.172.2 of the agent, on a self-hosted Ubuntu build agent.
@klamann Did you ever find a resolution for this?


Dont process containerEvent if host is removed.

Addresses https://github.com/rancherio/rancher/issues/1445.
If a host is removed and we try to process a container event, that
event will hang forever and a huge queue will build up for it in
processInstances. To avoid this, immediately exit if host is removed.

Couldn't think of a good way to add tests for this as it requires a scenario where an containerEvent is created and the host is removed before that event is processed.
Manually tested using break points to pause containerEvent processing and removed the host while it was paused.
Our load test environment has roughly 25 thousands such containerEvents, so it will be a good test bed for this fix.

LGTM

LGTM


BAU: bump react dev tools

This bumps react-dev-tools to a version containing a fix for the Immer vulnerabilities:
Prototype Pollution in immer (critical severity): CVE-2021-3757.
Prototype Pollution in immer (high severity): CVE-2021-23436.
More information can be found in:
https://github.com/facebook/create-react-app/pull/11364
https://github.com/facebook/create-react-app/issues/11443

[x] A changeset describing the change and affected packages. (more info)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks! Gonna be a bit annoying here ask that we don't do this bump and ignore the vulnerability instead. We'd prefer to bump up to v12 once it's done rather than getting on a prerelease.

No worries at all, understood

The vulnerability itself isn't really something we're touching, in fact it seems immer isn't even used within react-dev-utils itself. Either way, prototype injection in devtools is arguably a very minor issue, especially when it's not through contents of source code.

Yeah I'm with you on that

To ignore vulnerabilities we use .snyk policy files such as the one in the CLI package. These rules can then be copied by people that want to do so, and potentially even be included in the published packages at some point. Is this something you want to look at instead? otherwise we can take care of it.

If ok? Probably best if you folks do it


Not Working ?

"cp sample.env .env" command is not working ...

"cp sample.env .env" command is not working ...

Actually it's working. This command had copied example.env to .env now do vim .env and edit the vars by pressing i after editing press Esc and type :wq!  Enter.

@ChankitSaini helping hands🤝

learn linux basics!

learn linux basics!

lol


Objects removed from a manifest file aren't removed from the cluster

Environmental Info:
K3s Version: v1.23.6+k3s1
Node(s) CPU architecture, OS, and Version: any
Cluster Configuration: 1 server
Describe the bug:
When a manifest file is put in the /var/lib/rancher/k3s/server/manifests directory, the objects are correctly deployed to the cluster. However, if an object is removed from the file (for example, if the file is made blank), the objects will not be removed from the cluster.
Steps To Reproduce:

Install K3S via curl
Put a file in the referenced directory to deploy an simple nginx deployment
Wait for the pods to be deployed.
Change the file's contents to be blank.

Expected behavior:
The nginx deployment is removed from the cluster.
Actual behavior:
The nginx deployment is not removed from the cluster.
Backporting

[x] Needs backporting to older releases

We used to track the DesiredSet GVKs in the AddOn's status.gvks field, but stopped doing so when we switched to using Wrangler's apply in
https://github.com/k3s-io/k3s/commit/c0702b04927fb18693b168ddb3b12be40d845d5c#diff-c4f8a6638f496b7edccd14823bd72217e2b7fda10b88f055c43d754d0ef742c2L164-L168
Prior to that change the GVKs were nilled out and reset based on the list of objects to be applied, so it wasn't used when removing.
The code to delete things was added in
https://github.com/k3s-io/k3s/commit/0374c4f63d056df01c3e9e8cf4d77a6461169070#diff-c4f8a6638f496b7edccd14823bd72217e2b7fda10b88f055c43d754d0ef742c2R200-R203
That code is still mostly used, but relies on having the file around to discover the list of GVKs that need to be searched for objects to be deleted. If the file is deleted or modified, the current implementation may not find all the objects that need to be deleted.
The fix from @thedadams is probably a good step towards fixing this, as tracking applied GVKs and then using them when applying future updates SHOULD ensure that wrangler searches the proper GVKs for managed objects. My apologies for dismissing your fix before I had a chance to dig into it; I just assumed something had broken on the wrangler side again.
As an additional step, we should switch to a cluster-scoped AddOn type and use addon.WithSetOwnerReference(false, true) to ensure that the Kubernetes garbage collector catches anything wrangler misses when the AddOn resource is deleted.

Validated using commit id: 1ef34728c99ba8831bb22b34acd18211df7f7155 on master branch
When the nginx deployment file exists and file content is deleted the deployment is removed.
root@ip-172-31-1-111:/var/lib/rancher/k3s/server/manifests# logout
ubuntu@ip-172-31-1-111:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-7b7dc8d6f5-7486h   1/1     Running     0          3m19s
kube-system   coredns-b96499967-4p76m                   1/1     Running     0          3m19s
kube-system   helm-install-traefik-crd-26w5b            0/1     Completed   0          3m19s
kube-system   svclb-traefik-nz948                       2/2     Running     0          3m5s
kube-system   helm-install-traefik-sbmmb                0/1     Completed   1          3m19s
kube-system   metrics-server-668d979685-m5trm           1/1     Running     0          3m19s
kube-system   traefik-7cd4fcff68-75wp7                  1/1     Running     0          3m5s
default       nginx-deployment-6595874d85-tgxps         1/1     Running     0          2m43s
default       nginx-deployment-6595874d85-8vqnk         1/1     Running     0          2m43s
default       nginx-deployment-6595874d85-rlmm4         1/1     Running     0          2m43s
ubuntu@ip-172-31-1-111:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-7b7dc8d6f5-7486h   1/1     Running     0          3m23s
kube-system   coredns-b96499967-4p76m                   1/1     Running     0          3m23s
kube-system   helm-install-traefik-crd-26w5b            0/1     Completed   0          3m23s
kube-system   svclb-traefik-nz948                       2/2     Running     0          3m9s
kube-system   helm-install-traefik-sbmmb                0/1     Completed   1          3m23s
kube-system   metrics-server-668d979685-m5trm           1/1     Running     0          3m23s
kube-system   traefik-7cd4fcff68-75wp7                  1/1     Running     0          3m9s


[Windows] Adding tauri-plugin-window

When Im trying to use tauri-controls in my existing Tauri 2.0. Got following errors

Cargo.toml

All the previous steps were followed correctly. Seams the error is with desktop_commands.rs.

Got the same issue here!

I spent about an hour looking for a solution and couldn't find anything. Now I look here and see that it's a known issue. Nice...

trying to use tauri-plugin-window on linux and getting error

73 |         Some(l) if !l.is_empty() => window.get_window(&l).ok_or(Error::WindowNotFound),
   |                                            ^^^^^^^^^^
   |
help: there is a method `get_webview_window` with a similar name
   |
73 |         Some(l) if !l.is_empty() => window.get_webview_window(&l).ok_or(Error::WindowNotFound),
   |                                            ~~~~~~~~~~~~~~~~~~

I was facing the same errors, I checked on tauri-plugin-window to find that it's now a public archive!


Unity locking up while importing Terrain Shader

Unity (2019.4.13f1) has locked up while importing the Terrain Shader.
I had to force quit the editor via Task Manager.
upon restarting the console gave this error:
"A default asset was created for 'Assets/FlatKit/Shaders/StylizedSurface/Terrain.shader' because the asset importer crashed on it last time.
You can select the asset and use the 'Assets -> Reimport' menu command to try importing it again, or you can replace the asset and it will auto import again."

Hi,
If you are working with the Built-in Rendering Pipeline version of Flat Kit, some time is required in order to get it imported.
It's advised that you used the Universal Rendering Pipeline, as the URP version of Flat Kit loads virtually immediately in a URP project.
If you plan to go on with Built-in RP, however, please start re-importing the asset and give it from 5 to 30 minutes (the time depends on the computer resources).

Hi,
If you are working with the Built-in Rendering Pipeline version of Flat Kit, some time is required in order to get it imported.
It's advised that you used the Universal Rendering Pipeline, as the URP version of Flat Kit loads virtually immediately in a URP project.
If you plan to go on with Built-in RP, however, please start re-importing the asset and give it from 5 to 30 minutes (the time depends on the computer resources).


About release 0.29.2

👋 Just curious if the 0.29.2 release got re-tagged? Found the checksum mismatch when regression testing against rust 1.65.0 release, raising this issue to double confirm. Thanks!
cc @curquiz

Hello @chenrui333
Sorry for the inconvenience.
We indeed had an issue with v0.29.2 that involved us adding a commit and moving the tag. I completely forgot to let you know (Homebrew) about it, sorry.
We had an issue with the docker image, so the v0.29.2 you have is the same as ours, but without the Dockerfile fix.
Anyway, we will release v0.30.0 on Monday, you should not have the issue on your side anymore.
The problem we currently have with our process is the homebrew PR is created immediately after we create the release, via our Homebrew CI. Meaning if any failure is happening with our binary compilation or docker image creation, it's too late, and the PR is already done on your side
We need to change this and run the Homebrew CI once every other CI is passed and not trigger it at the same time as the other because way faster. I will open an issue soon for this!
Sorry again for the trouble!

We need to change this and run the Homebrew CI once every other CI is passed and not trigger it at the same time as the other because way faster. I will open an issue soon for this!

yeah, I think it can be easily fixed by having homebrew bump step as last step (while having conditions to check all the previous steps passed).
Another way, similar to the above idea is to have a separate workflow to be triggered when all the CI flows passed.
let me know if you need any help on that

Closing the issue as I got what I need :)

Thanks for your input @chenrui333
I definitely need to spend time refactoring our current CI to ensure I don't break anything.
Thanks for suggesting your help!
See you around 👋

I've opened an issue about this and I realized it's not that easy to implement on our side. Maybe I'm wrong? See https://github.com/meilisearch/meilisearch/issues/3146
If anyone has any insight on this, it would be really appreciated 🙏


Bot API 6.4 (December 30, 2022)

@cheeghi It's ready #68.
First commits diff might look weird, cause I had to move and make things sorted like how telegram documents are; it should help maintenance in the future.
Also if there are any violations of coding style and standards lemme know 👀


Update copyright notice

@bgrant0607 @mikedanese any updates on this?

@errordeveloper I emailed the lawyers but no word from them yet. I am hesitant to continue without approval from someone with more authority than me here. The kubernetes project has not so far accepted contributions that have a second copyright outside of third_party/ or vendor/ and I want to hear someone say that this is ok to do.

From Weaveworks, LGTM on the changes to the headers.
The NOTICE file should read:
Kubernetes Anywhere
Copyright 2015-2016 The Kubernetes Authors

@errordeveloper can you change that, please?

I've changed it now.

LGTM, thanks.


Minor cleanup of the "New Script" dialog

Make so that it stops doing theme related stuff through its GridContainer (why the hell it was doing that in the first place?).
Untoggle the "Parent Search" as flat, since no other button in the dialog is.

Thanks!


Incorrect parsing when string contains }} (two closing braces)

https://astexplorer.net/#/gist/50f0fc500a626ee33ec2ea9205f4e598/8be358100a557256023ef600d4aa7e32486ea369
Two closing braces inside a string should not be seen as the end of the expression container.
This will happen frequently when using something like ICU message formatting, as seen in the example at the URL above.

I think your template is incorrect as SFC.

Vue 2 Template Explorer
Vue 3 Template Explorer

So I think this parser is working fine.

I think your template is incorrect as SFC.

Vue 2 Template Explorer
Vue 3 Template Explorer

So I think this parser is working fine.

I'm not sure I understand how it's incorrect?
<template>

{{ $fm('}}') }}

</template>

This looks like it should be parsable.

I'm not sure I understand how it's incorrect?
<template>

{{ $fm('}}') }}

</template>

This looks like it should be parsable.

Your template cannot be compiled with Vue's compiler.
What do you see and think this template can be parsed?

https://template-explorer.vuejs.org/#
{{ %24doSomething('}}') }}<%2Fp>

Your template cannot be compiled with Vue's compiler.
What do you see and think this template can be parsed?

https://template-explorer.vuejs.org/#
{{ %24doSomething('}}') }}<%2Fp>

'}}' is interpreted by the parser as the end of an interpolation, but it isn't. This looks to me like a bug or improvement opportunity for the Vue parser.

'}}' is interpreted by the parser as the end of an interpolation, but it isn't. This looks to me like a bug or improvement opportunity for the Vue parser.

So this is an issue with @vue/compiler-*?
Does GH allow you to transfer this issue there, or should I open a new issue at vuejs/vue-next?

So this is an issue with @vue/compiler-*?
Does GH allow you to transfer this issue there, or should I open a new issue at vuejs/vue-next?

I can't transfer it, maybe @ota-meshi can?

I can't transfer it, maybe @ota-meshi can?

@LinusBorg Thank you for following me.
I can't even transfer this issue...

@LinusBorg Thank you for following me.
I can't even transfer this issue...

@glen-84 Then please open a new issue in the vue repo

@glen-84 Then please open a new issue in the vue repo

I will do, thanks.

I will do, thanks.

FWIW I guess you are aware that a workaround would be '}' + '}'

FWIW I guess you are aware that a workaround would be '}' + '}'

Ya, @longlho put another workaround in the Format.JS documentation, but I wanted to find out why it was necessary. 🙂
I've opened https://github.com/vuejs/vue-next/issues/2944.
Thanks.

Ya, @longlho put another workaround in the Format.JS documentation, but I wanted to find out why it was necessary. 🙂
I've opened https://github.com/vuejs/vue-next/issues/2944.
Thanks.


How to add the Zooming Feature inside the Camera Plugin

Hi there i want to add the Zooming Functionality into the Camera and you can see that Feature in the SmartPhone Camera App itself. So can someone help me to figure out how to do it ?

@Loopex2019 your suggestion appears to be aiming towards
adding new features to a specific camera plugin rather than to Flutter SDK;
I'm closing this issue, if you disagree please comment and I'll reopen it.

@Loopex2019 your suggestion appears to be aiming towards
adding new features to a specific camera plugin rather than to Flutter SDK;
I'm closing this issue, if you disagree please comment and I'll reopen it.

@Loopex2019 you can take a look into this implementation https://github.com/flutter/plugins/pull/1304. Note that the PR wasn't merged yet. Did you mean such functionality?


[chore]: added leetcode icon

added leetcode icon as per order

@kumarsonsoff3  just wanted to ask this was changing the spaces between the words really necessary? I think they are mostly the same as before. correct me if I am wrong

@kumarsonsoff3 just wanted to ask this was changing the spaces between the words really necessary? I think they are mostly the same as before. correct me if I am wrong

@jaynarayan-vaishnav, If I'm getting you correct, you mean with the spaces in the markdown of the table in icon.md file!?
They are just for formatting purposes, I mean they have nothing to do with the output of the markdown!

Okay thanks for explaining @kumarsonsoff3

The markdown table is breaking up somewhere. Please check the syntax.
If you need any help do let us know!
Screenshot

__        Summary: 🛠 This code needs a fix

cant find where is problem in syntax can you tell me where is need to change


Get connectivity features' resting-state paradigm from configs

While the paradigm data is stored in the preconfigs, it was being replaced with the string "Resting State". The paradigm provides important information when it is provided, so this PR allows siibra to take it from the jsons.

Codecov Report

Merging #275 (75306e1) into main (5d8f673) will increase coverage by 0.13%.
The diff coverage is 37.38%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #275      +/-   ##
==========================================
+ Coverage   35.75%   35.89%   +0.13%
==========================================
  Files          59       59
  Lines        4984     5032      +48
==========================================
+ Hits         1782     1806      +24
- Misses       3202     3226      +24

Impacted Files
Coverage Δ

siibra/configuration/factory.py
26.06% <0.00%> (ø)

siibra/core/concept.py
77.21% <ø> (ø)

siibra/core/region.py
40.32% <ø> (ø)

siibra/core/space.py
67.50% <ø> (ø)

siibra/features/basetypes/feature.py
34.90% <0.00%> (-0.34%)
:arrow_down:

siibra/features/basetypes/regional_connectivity.py
21.29% <ø> (ø)

siibra/features/basetypes/tabular.py
30.00% <ø> (ø)

siibra/features/basetypes/volume_of_interest.py
41.93% <0.00%> (-2.19%)
:arrow_down:

siibra/locations/point.py
26.92% <ø> (ø)

siibra/retrieval/datasets.py
48.43% <ø> (ø)

... and 14 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


BLT Chrome Extension frontend

Solving Issue's
https://github.com/OWASP-BLT/BLT/issues/2243
https://github.com/OWASP-BLT/BLT/issues/2246
https://github.com/OWASP-BLT/BLT/issues/2247
Screenshots

@DonnieBLT @arkid15r @AtmegaBuzz Please review


Many "upstream connectivity issues" messages in the log file

System: Debian Stretch, dnscrypt-proxy 2.0.9 (Release)
With log_level = 1 in dnscrypt-proxy.toml there are a lot of

[2018-04-12 08:24:59] [INFO] Server [XXXXX] returned error code [2] -- It might be experiencing upstream connectivity issues
[2018-04-12 08:25:05] [INFO] Server [XXXXX] returned error code [2] -- It might be experiencing upstream connectivity issues
[2018-04-12 08:26:01] [INFO] Server [XXXXX] returned error code [2] -- It might be experiencing upstream connectivity issues
[2018-04-12 08:26:07] [INFO] Server [XXXXX] returned error code [2] -- It might be experiencing upstream connectivity issues
[2018-04-12 08:26:12] [INFO] Server [XXXXX] returned error code [2] -- It might be experiencing upstream connectivity issues

messages in the log file, for several different servers.
It also happens with a server running a current, original and unmodified dnscrypt-server-docker (jedisct1/dnscrypt-server).

If you are using Cloudflare, it means that you sent too many queries, and have been rate limited.

Oh sorry, didn't notice that it was using a DNSCrypt server docker image.
error code [2] means that the server returned a SERVFAIL response. This comes from Unbound, and can happen if queries were sent to zones with invalid DNSSEC signatures, or if there were too many timeouts for Unbound to resolve some queries.

Yes, it happens with Cloudflare too. But I don't use Cloudflare, I'm using my own server (a current, original and unmodified jedisct1/dnscrypt-server). And as written, there are other servers too.
For me it looks like a general problem or issue.

Getting responses from misconfigured and slow servers happens all the time. Unless is happens with server you know are perfectly fine, this can be ignored especially since these are temporary errors.
Maybe the severity of this message should be decrased even further to DEBUG.

I hope and expect ;-) that my environment - server with your Docker image, client with your dnscrypt-proxy -  is working fine.
It was just irritating that the messages have been logged for/with so many servers, not only my and Cloudflare.
So, you say I should ignore it -> log_level = 2.

Yes, it's safe to ignore it. This is logged for diagnostics purposes, but once your proxy is up and running, you should keep log_level >= 2.

Thanks for the response. I'll close the issue...


Update seasonController.ts

Fixed async call for creating a season
Description
Brief description of changes
fixed an await call
Risks
Limited to creating a season.
Validation
testing
Issue
Link to corresponding issue
Operating System
If you're on Mac, please include whether you are on an Intel or M-series CPU

This change has been fixed on my current branch while working on the seasons instances page.


Azure Database Configuration

Description of your changes
Full config, examples, uptest
I have:

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested
local make e2e + uptest below

/test-examples

ok, forgot to setup creds :D

/test-examples


Performance fix

I'm going to check that this works with the spray-json-shapeless code and will let you know.

OK, this looks good but is failing MiMa, due to what looks like a false positive ... the signature change is internal to a macro implementation and shouldn't affect user code.
I'm completely new to MiMa ... presumably it has a mechanism for marking exclusions?

Wait till I've checked with spray-json-shapeless as well. It's a good stress test.

I call this a success, we can almost all go home now :grinning:  @rorygraves you might want to look and see what else is slowing it down. this might be the singleton string stuff.
[success] Total time: 117 s, completed 12-Jun-2015 10:53:31
...
[info] All tests passed.

Also, ensime-server is using spray-routing-shapeless2 and 2.2.2-SNAPSHOT with this patch ???

The MIMA issue looks similar to the one discussed in https://github.com/scala/scala/pull/4230 and https://github.com/typesafehub/migration-manager/issues/59, with a return type change in our case instead of a removal.
Code that landed in std lib at https://github.com/scala/scala/pull/4328/files#diff-873c1cee0e89e8df586c53df0c303ceaR124.
@fommil Adding a stub like
 final def `shapeless$GenericMacros$$mkCoproductCases$1`(tpe: Type, index: Int): (CaseDef, CaseDef) = {
   /* Body of the previous mkCoproductCases local method */
    ???
  }

fixes it (tested locally).
@adriaanm et al. were implying that it could break binary compatibility under some circumstances (with -optimize).

@alexarchambault can you please create a commit in your branch and I'll cherry pick / flatten.

@fommil Done here: https://github.com/alexarchambault/shapeless/commits/perf_fix

I would just exclude that method from MiMa as it is only called by macros.

@retronym About the method I added a stub I added for? Can't the macro have been expanded by an earlier version of shapeless (with ref to this method) and the resulting bytecode linked with a newer one?

That method is called during macro expansion, not by the expansion itself.

Yeah, I think a MiMa exclusion would be the way to go.

It's not what I meant. There are libraries using this from their own macro implementation, e.g. https://github.com/fthomas/refined/blob/master/src/main/scala/eu/timepit/refined/internal/WeakWitness.scala .
Now, if these are initially compiled on a former shapeless, and their macros are then used and expanded with a newer shapeless at hand, they may not find the methods they're looking for.

Understood. @fthomas ... is this an issue for you?

@milessabin It won't be an issue for @fthomas, he's not using this specific method - I don't know if there are public libs that do, but the point of binary compatibility is to be safe wrt that.

OK, gotcha. I don't encourage people to depend on shapeless macro internals other than in exceptional circumstances, so I'm not particularly concerned about this.
So I really do think the MiMa exclusion is the better approach here.

Yes, that is not an issue for me.
Btw: It seems that the addition of def Witness.Aux() and the change in mkWitness fix my problem I had with Witness (https://github.com/fthomas/refined/issues/2). Awesome!

@milessabin You might want to review the naming and documentation of the new methods I added to Coproduct before merging this. I didn't put too much thought into that side of things, but they will be user visible so should be polished a little.

@retronym I'll tweak this a little and then merge. Thanks again :-)

Meged ... thanks all :-)


error: unknown long flag '--web.config.file'

Hello,
how does the topic already say. I have that error when I started the service from systemd an read in the log from journalctl:
apache_exporter: error: unknown long flag '--web.config.file', try --help
I want to add a configfile  in order to use TLS and define the certspath. Here is my configfragment in the unitfile from systemd.
ExecStart=/usr/local/bin/apache_exporter
--web.config.file="/etc/apache_exporter/web.yml"
--scrape_uri="http://localhost/server-status?auto"
--telemetry.address="<IP_ADDRESS>:9117"
Version of my apache_exporter v0.11.0

hi @chillriver, that's currently not a supported option
Feel free to submit a PR in order to add that option

hi @chillriver, that's currently not a supported option
Feel free to submit a PR in order to add that feature

That's good to hear
Seems I rushed in my reply and give you wrong information!
Would you like to make a quick PR to update the parameter mentioned in the README at https://github.com/Lusitaniae/apache_exporter/blob/aee05657dae4661965fbd40df3fb99fc43b5c016/README.md#tls-and-basic-authentication and anything else you think relevant?

Yes I can edit the README. It should be change the TLS chapter and also the help on flags.

Much appreciated!


fix the doc

because when you executed the command line order, it installed empty package

Installing locust should work (I tried it just now). But the proper fix will be to push the correct package (locust), which @heyman is going to do sooon (maybe next week, right? :)
Closing. Also this is a duplicate of https://github.com/locustio/locust/pull/1346


MixedRealityRaycastHit Throws Exceptions on Every Frame

Describe the bug
MixedRealityRaycastHit throws exceptions on every frame.
A commit was made 7 days ago to wrap access to hitInfo.lightmapCoord in a Try / Catch block. Unfortunately this does not correct the actual condition that's causing the exception to be thrown in the first place.  This introduces a significant performance hit. Exceptions are very expensive and should be avoided at all costs in the render thread.
There is a comment in the recent comment:

Accessing lightmap coord appears to throw a NullReferenceException in some cases, probably when lightmaps are not used.

Rather than catching the exception, effort should be made to determine if this is in fact the root cause and determine a way to avoid accessing the property under this condition. If we determine the condition is unavoidable, we should open a bug with Unity.
To reproduce
Steps to reproduce the behavior:

Create a new Unity project
Import MRTK
Configure MRTK for HoloLens 2
Press play in Unity
Under Exception Settings in Visual Studio, set it to stop on all exceptions (even handled ones).
Attach Visual Studio to Unity

You will see the Visual Studio Debugger break on every frame.
Expected behavior
An exception should not be thrown on every frame.
Your Setup (please complete the following information)

Unity Version: 2018.4.2
MRTK Version: mrtk_develop as of 2019-06-19

Target Platform (please complete the following information)

HoloLens 2

This is bad, I'm fixing this now


`Fix passing chat history into buffer memory, add tests, update docs

Followup to #538
The chatHistory field was not getting passed through to the BaseChatMemory constructor. This fixes that issue, adds tests, and updates the docs with an example.

Would it also make sense to just pass through the entire fields object into the call to super() e.g. here?:
https://github.com/hwchase17/langchainjs/pull/567/files#diff-18454f03f31ddfe1bf30aaeed806985f3089ecb3be4ea0424e31db55a80481a4R26


How can I downgrade?

Hello,
using version 0.9.7 but I need to use 0.9.6.
How can I make downgrade?
Thank you

you need Debian 8
https://github.com/arakasi72/rtinst/issues/349

not good for me. Any way to make clean install of 0.9.6? Really don't want 0.9.7.


A problem occurred when laughing in VS code：Any pushed event handlers must have been removed

(ImageProcessing) F:\Users>imagepy
ipy
Traceback (most recent call last):
File "E:\Program Files\Python38\lib\runpy.py", line 194, in _run_module_as_main
return run_code(code, main_globals, None,
File "E:\Program Files\Python38\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "E:\Program Files\Python38\env\ImageProcessing\Scripts\imagepy.exe_main.py", line 7, in
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy_init.py", line 31, in
show
ImagePy(None).Show()
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\mainframe.py", line 52, in init
if IPy.uimode()=='ipy': self.load_aui()
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\mainframe.py", line 96, in load_aui
self.widgets = widgetsloader.build_widgets(self, 'widgets', 'plugins')
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\widgetsloader.py", line 34, in build_widgets
return build_widgets_panel(parent, datas, panel)
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\widgetsloader.py", line 21, in build_widgets_panel
build_widget(choicebook, i)
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\widgetsloader.py", line 10, in build_widget
parent.AddPage(i(parent), i.title, False )
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\widgets\histogram\histogram_wgt.py", line 17, in init
self.sli_high = FloatSlider(self, (0,255), 0, '')
File "e:\program files\python38\env\imageprocessing\lib\site-packages\imagepy\ui\widgets\normal.py", line 283, in init
subsizer.Add( self.spin, 0, wx.ALIGN_CENTER|wx.BOTTOM|wx.EXPAND, 5 )
wx._core.wxAssertionError: C++ assertion "!(flags & (wxALIGN_BOTTOM | wxALIGN_CENTRE_VERTICAL))" failed at ....\src\common\sizer.cpp(2114) in wxBoxSizer::DoInsert(): Vertical alignment flags are ignored with wxEXPAND
Error in atexit._run_exitfuncs:
wx._core.wxAssertionError: C++ assertion "GetEventHandler() == this" failed at ....\src\common\wincmn.cpp(475) in wxWindowBase::~wxWindowBase(): any pushed event handlers must have been removed

same

+1

same

+1

Hi all, Sorry for not reply for a long time. as I can run with vs code successfully:

about the wx's error:
try the newest github's code and update wxpython!


Document engine fixes

Can’t really test it while so many things are broken with linter. But it should work this way as I have same tests against this codebase with mocha now in side project.

Wrong branch.


Failed to initialize db after install

My Environment

ArangoDB Version: 3.4.4 / 3.4.5
Storage Engine: RocksDB
Deployment Mode: Single Server
Configuration: No password, default DB, defalt installation directories. I've tried single user and all users settings with the same results
Operating System: Windows 10 Enterprise 1803
Total RAM in your machine: 16Gb
Disks in use: SSD
Used Package: Windows Official

Component, Query & Data
Affected feature: Installation

Steps to reproduce

Run installer as administrator following steps above
executable installs all dependencies (sh, imp, dump, etc...) and attempts to initialize _system database
Installer throws general error that  it failed to initialize the DB with a password.

Problem:
I'm unable to install Arango on Windows with any combination of settings. The Windows event viewer says Arango tries to make changes to a few files in C:\vm02-windows, a directory which doesn't exist.
I asked my IT dept. to temporarily give me unrestricted admin access, which they did, and I got the same results. We manage permissions through Avecto Defendpoint, but I've never had issues installing Arango before.
Expected result:
I expect the database to initialize

Hello @zbauer91,
Can you please tell where did you download Windows installer and put here contents of etc\arangodb3\arangod.conf (in installation folder of ArangoDB binaries)?

Hi @KVS85
I downloaded the installer from the Arango website, and I'm using Windows 10 Enterprise 1803
arangod.conf:
# ArangoDB configuration file
#
# Documentation:
# https://docs.arangodb.com/latest/Manual/Administration/Configuration/
#

[database]
directory = @ROOTDIR@var/lib/arangodb3

# maximal-journal-size = 33554432

[server]
# Specify the endpoint for HTTP requests by clients.
#  tcp://ipv4-address:port
#  tcp://[ipv6-address]:port
#  ssl://ipv4-address:port
#  ssl://[ipv6-address]:port
#  unix:///path/to/socket
#
# Examples:
#   endpoint = tcp://<IP_ADDRESS>:8529
#   endpoint = tcp://<IP_ADDRESS>:8529
#   endpoint = tcp://localhost:8529
#   endpoint = tcp://myserver.arangodb.com:8529
#   endpoint = tcp://[::]:8529
#   endpoint = tcp://[fe80::21a:5df1:aede:98cf]:8529
#
endpoint = tcp://<IP_ADDRESS>:8529
storage-engine = auto

# reuse a port on restart or wait until it is freed by the operating system
# reuse-address = false

authentication = true

# number of maximal server threads. use 0 to make arangod determine the
# number of threads automatically, based on available CPUs
# maximal-threads = 0

# gather server statistics
statistics = true

# the user and group are normally set in the start script
# uid = arangodb
# gid = arangodb

# uid = arangodb

[javascript]
startup-directory = @ROOTDIR@/usr/share/arangodb3/js
app-path = @ROOTDIR@var/lib/arangodb3-apps
# app-path = //arangodb3/apps

# number of V8 contexts available for JavaScript execution. use 0 to
# make arangod determine the number of contexts automatically.
# v8-contexts = 0

[foxx]
# enable Foxx queues in the server
# queues = true

# interval (seconds) to use for polling jobs in Foxx queues
# queues-poll-interval = 1

[log]
level = info
# file =<EMAIL_ADDRESS>
[cluster]

[rocksdb]
# encryption-keyfile=/your-encryption-file

windows event logs:
cannot rename saved file 'C:\ProgramData\ArangoDB\VERSION-1.tmp' to 'C:\ProgramData\ArangoDB\VERSION-1': Permission denied
C:\vm02-windows\oskar\work\ArangoDB\lib\Basics\VelocyPackHelper.cpp
arangodb::basics::VelocyPackHelper::velocyPackToFile
732

{startup} writing VERSION file 'C:\ProgramData\ArangoDB\VERSION-1' failed: Permission denied
C:\vm02-windows\oskar\work\ArangoDB\arangod\VocBase\Methods\Version.cpp
arangodb::methods::Version::write
167

Database '_system' initialization failed (Permission denied). Please inspect the logs from the initialization procedure and try starting the server again.
C:\vm02-windows\oskar\work\ArangoDB\arangod\RestServer\UpgradeFeature.cpp
arangodb::UpgradeFeature::upgradeDatabase
205

@zbauer91 thank you for this information.
I have several questions to narrow-down this problem:

was this an "all users" installation (service)?
did you have an ArangoDB installed before on this machine (probably, a previous one version)?
is your account belongs to "Administrators" group?

From what I see the problem is that ArangoDB couldn't deploy DB into C:\ProgramData\ArangoDB (default installation directory for service) due to insufficient rights.

was this an "all users" installation (service)?

Yes, this time. I've also tried performing the installation for myself only, I've also tried changing the install directory to one that I know I have W/R access to. All combinations of installation parameters results in the same error.

all users/just current user
default directory / custom directory
password/no password

did you have an ArangoDB installed before on this machine (probably, a previous one version)?

Yes, I had 3.3.x installed previously.

is your account belongs to "Administrators" group?

That's what I thought. Our company manages administrative privileges through Avecto Defendpoint (as mentioned).  Administrator calls are gated through this software, and I have to sign in to temporarily allow the changes to take place. This isn't full admin, though, so I got the go-ahead from IT to temporarily add my user back to the admin group for the purposes of this installation. With full administrative access, I still received the same errors that I replied with above.

Just checking back in. Is there any more information you need on my end?

Just encountered this issue as well. I set permissions for Everyone on C:\ProgramData\ArangoDB to full control and the error persists.

Additionally, this error affects installation on Windows.

I'm seeing this on a server as well, not sure if Anti Virus is jumping in to stop the VERSION-1 file from being modified.
@natejgardner Did you resolve this issue?

Quick feedback, we fixed this error by changing arangod.conf to disable authentication, and change the log level to 'level = startup=trace' in order to see the details of the startup phase.
Amazingly, that alone fixed it.
So we enabled auth again and changed the level back to info, and it's fine

@Calrain  Could you please detailly tell me how you fixed this issue? I am facing the same problems.

@linpanusst We shut the ArangoDB service down, modified arangod.conf and changed the log level to level = startup=trace (yes, two = signs in there), as well as disabled authentication in the same file.
Then start the ArangoDB service again, then shut it down, and change the log level back to what it was, and reenable authentication, both in arangod.conf.
Probably worth backing up your original arangod.conf before you do it.

@Calrain Thank you for you time. I tried on my PC. It doesn't work. Maybe there are some difference between your side and my side. I install the ArangoDB by .exe file. Is that the method you install on your PC? I know there is another way which is the terminal method to install ArangoDB.

@linpanusst Ah, sorry, just remembered, it was running on Windows 2016, and when I started the database after making the changes to arangod.conf, when I started the server the next time, I opened a CMD window in Administrator mode, changed into the directory that arangod.exe was, ran it, and then i could see that it initialised ok. Control C two times shuts down the process, then I reverted arangod.conf. After that I could run it as a service again.

@Calrain Thanks for the patience and time. If I find out the reason someday, I will share with you.

Hi,
please change this section:

[log]
level = info
# file =<EMAIL_ADDRESS>
of the arangod.conf to point somewhere with write access, and check back whether you have some meaningfull error message in there.

closing as a duplicate of https://github.com/arangodb/arangodb/issues/11041


Cache information schema queries

Laravel Version: 5.3.30
PHP Version: PHP 5.6.27
Database Driver & Version: MySQL 5.6.34
Type: feature request

Description:
When making Schema::hasColumn checks for the my_table table every time it makes a request to the database
select column_name from information_schema.columns where table_schema = 'my_db_name' and table_name = 'my_table'

Instead I think it should cache the query after first time and read from cache. If debug is enabled, cache time can be minutes or seconds (to not create issues during development) and some long period (months ?) for production
I admit that this can be easily implemented manually (I just asked a question in SO - http://stackoverflow.com/q/42056536/932473) , but I think this kind of internal things should be built-in features in the framework and by default would provide great boast on performance
Steps To Reproduce:
if we have these 2 lines
Schema::hasColumn('some_table', 'some_column');
Schema::hasColumn('some_table', 'some_column');

we will have the above query run twice - and during each page load

Looks good.
An idea: The cache could be cleared when running the migrations.

I agree with Paras from S.O, you should define a variable in your model or a config to handle this instead of running a query every time.
I don't think this should be part of the framework, at least, not for this use case.

Multiple calls to Schema::hasColumn can probably be cached during the current http request or artisan command; but accessing them for longer than that sounds bad. It assumes we're in full control of the database, and no other process is modifying it. It would also cause issues for all the developers that does manual changes to their database (even if it's not considered a good practice).

It can be an option (disabled by default) for projects that has full control of the database.

@kamui545 defining does not solve the part of the problem of making the same query on every page load

but accessing them for longer than that sounds bad

@sisve I do not share your point, how often in production mode the table's schema is changed ? I think in 99 % cases only when you apply some update (and we can delete the cache, when running migration as @mariomka suggested, or have some command to delete it), if the user manually changes the database, then its his responsibility to manually delete the cache as well. In development mode as I mentioned we can put the cache time the smallest (or disable at all), so it wont be an issue
for the last resort, as @mariomka sad, it can be disabled by default, but I think this option should exist. I think with easiness of development the framework should have at least basic optimization things built-in, well, even if disabled by default...

5.3 is closed for new features, feel free to open a PR on 5.4 if you want. However, in my opinion this needs to be handled in the app code, not in the core.


[Bug][Linux] Wrong action on click file above expandable folder

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Please look this video : https://gofile.io/?c=Y5AZ3A
When click on expandable folder and then click on a file above the folder that will expand and collapse the folder again and does not open the file, same as when click on folder not the file.

Steps to Reproduce

Click on a folder to expand / collapse / highlight
Click on a folder immediatly above the folder

Expected behavior:
That should open file preview
Actual behavior:
That will expand/collapse the folder that before clicked
Reproduces how often:
100%
Versions
Atom    : 1.38.2
Electron: 2.0.18
Chrome  : 61.0.3163.100
Node    : 8.9.3
OS : Linux, Debian 10
Additional Information
Screen record to reproduce the problem : https://gofile.io/?c=Y5AZ3A

Yeah that's just a workaround - since the One themes are in the main atom/atom repo I transferred the issue over.


spawn child processes in the same shell

I don't run windows, but we do for CI (github actions).
When wireit dependencies run, shell:true happens here (see comment in the code)
Our situation: we have some npm scripts that call ./foo
Our GHA use powershell by default, so these work fine without wireit
Using wireit, they run with cmd.exe (because shell:true => env.comspec => cmd.exe)
cmd.exe can't handle ./
why not use the same shell that the outer invocation (parent) used?

We try to replicate the behavior of standard npm scripts, which is to use /bin/sh on POSIX and cmd.exe on Windows by default (and this just so happens to be the same behavior as node's shell:true, so we just use that).
It is true that we don't currently respect the script-shell configuration, though, which we should do (https://docs.npmjs.com/cli/v9/using-npm/config#script-shell). Are you using this option, or does yarn behave in a different way?
Detecting the parent shell is a quite good idea, since that would allow us to be agnostic about the shell, and just match the behavior of whichever entrypoint runner was used. I guess we can look up the process tree with ps and its equivalent on windows to find the command used for the parent process...

yarn will follow script-shell.

yarn will follow script-shell.

Cool! Are you setting script-shell in this situation? Curious if following a script-shell flag would solve your problem here, or if there is some other way you are setting the shell?

I tried setting that but it didn't help.  Sounds like changes to wireit might be the only way to make this work.
The bonus there would be that users on windows machines wouldn't have to do anything special (config) to use it--it would use whatever shell they were using at the moment.

I guess I'm trying to understand how you are achieving or would achieve what you want using a vanilla npm/yarn script? My understanding is that you will get cmd.exe unless you set --script-shell to something else.

My understanding is that you will get cmd.exe unless you set --script-shell to something else.

I think that may be the source of confusion.
"scripts": {
  "foo": "./bin/dev go"
}

yarn foo runs ./bin/dev go in whatever shell I ran yarn foo from.
  You've chosen powershell (./ depends on it).  The vanilla script runs in Powershell because that's where it's run from.
When foo is used as a wireit dependency of another wireit command, because of the shell:true it's going to run yarn foo using cmd.exe which will fail (on a windows machine locally or in CI).

yarn foo runs ./bin/dev go in whatever shell I ran yarn foo from.

Looking at the source code, it seems like yarn takes the custom-shell, or passes shell:true: https://github.com/yarnpkg/yarn/blob/158d96dce95313d9a00218302631cd263877d164/src/util/execute-lifecycle-script.js#L281
That should pretty much match our behavior, except that we don't currently check custom-shell.
I don't seem to be seeing any code where it tries to figure out what the parent shell was and use that.
This is for yarn 1.x though, yarn 2.x or 3.x might be different. Which version are you using?

after looking at yarn's code, I think I agree with you.  I can't square what the code says vs. what happens in GHA, so maybe GHA is doing some things (which code isn't open for) that cause it to use pwsh extensively.
Then wireit's code is maybe finding a way around those settings and managing to run cmd.exe where GHA wouldn't.
I gave up on trying to figure out why, and just rewrote my commands to be usable from cmd.exe.


Error[Li005]: no definition for "__write" [referenced from           putchar.o(dl7M_tln.a)]

when I compiler arm/mixLanguages it show the error.I want to know how to solve it, thanks.Use the example in the tutorial
.\examples\mix-c-asm\arm
>cmake -G "Ninja" -B_build --toolchain ../../iar-toolchain.cmake
...
>cmake --build ./_build --config Debug
......
[3/3] Linking C executable mixLanguages.elf
FAILED: mixLanguages.elf
Error[Li005]: no definition for "__write" [referenced from
          putchar.o(dl7M_tln.a)]
ninja: build stopped: subcommand failed.

Thanks for your feedback. I will take a look at that.


[WIP] Dom/fix marks

Not sure why it's still WIP, but LGTM. Feel free to merge.

For some reason the gallery doesn't work but I was too tired to debug.
On Tue, Jul 21, 2015 at 6:05 AM, Kanit Wongsuphasawat <
<EMAIL_ADDRESS>wrote:

Not sure why it's still WIP, but LGTM. Feel free to merge.
—
Reply to this email directly or view it on GitHub
https://github.com/uwdata/vega-lite/pull/528#issuecomment-123298281.

gallery/bower_component is occasionally got cleaned up by some commands.
I’m merging this now then.


Create Linux Varnish Recipe

Aha! Link: https://newrelic.aha.io/features/VIRTUOSO-67

Duplicate of #74, closing.


[ACL] - contain fixes for frontend miscellaneous tasks

https://sovryn.monday.com/boards/2218344956/pulses/2562390754
https://sovryn.monday.com/boards/2218344956/pulses/2562393165
https://sovryn.monday.com/boards/2218344956/pulses/2562400509
https://sovryn.monday.com/boards/2218344956/pulses/2562400706

AC is to ensure rBTC is is properly named as RBTC. Please check