Failed to start container from ECR registry

Hello, there
I'm trying to integrate nydus-snapshotter in an EKS cluster and failing to do so.
I could sucessufully start a public image (ghcr.io/dragonflyoss/image-service/nginx:latest) but when I'm trying a private one stored in my ECR repo, it fails.
The image seems to be downloaded, but the snapshotter apparently has problems reaching out to ECR afterwards for downloading further layers.
On kubernetes API I see the pod in the CreateContainerError state. Its events contains messages as:
  Warning  Failed  12m                   kubelet  Error: failed to create containerd container: mount callback failed on /var/lib/containerd/tmpmounts/containerd-mount16778314: read /var/lib/containerd/tmpmounts/containerd-mount16778314/etc/passwd: invalid argument
  Warning  Failed  12m                   kubelet  Error: failed to create containerd container: mount callback failed on /var/lib/containerd/tmpmounts/containerd-mount2647516877: read /var/lib/containerd/tmpmounts/containerd-mount2647516877/etc/passwd: invalid argument

In the snapshotter's logs I see a strange error and it seems to be using http instead of https and without creds (scheme: \"http\", ..., username: \"\", password: None):
(Note I just change my aws account id to AWS_ACCOUNT_ID)
Jan 24 18:58:12 nydus-node containerd-nydus-grpc[3434]: time="2024-01-24T18:58:12.494327154Z" level=info msg="remote mount options [workdir=/var/lib/containerd-nydus/snapshots/106/work upperdir=/var/lib/containerd-nydus/snapshots/106/fs lowerdir=/var/lib/containerd-nydus/snapshots/105/mnt]"
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: [2024-01-24 18:58:17.390716 +00:00] DEBUG [/src/backend/connection.rs:673] cache-flusher Request: GET http://AWS_ACCOUNT_ID.dkr.ecr.us-west-2.amazonaws.com/v2/python3/blobs/sha256:f8d467138fd4cf0f78a7776d6dbf414f4559974076452f745d804c8a29643f27 headers: Some({"range": "bytes=30245391-30275603"}), proxy: false, data: false, duration: 5000ms
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: [2024-01-24 18:58:17.390903 +00:00] ERROR [/src/error.rs:22] Error:
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: "failed to read metadata for blob f8d467138fd4cf0f78a7776d6dbf414f4559974076452f745d804c8a29643f27 from backend, Request(Common(reqwest::Error { kind: Request, url: Url { scheme: \"http\", cannot_be_a_base: false, username: \"\", password: None, host: Some(Domain(\"AWS_ACCOUNT_ID.dkr.ecr.us-west-2.amazonaws.com\")), port: None, path: \"/v2/python3/blobs/sha256:f8d467138fd4cf0f78a7776d6dbf414f4559974076452f745d804c8a29643f27\", query: None, fragment: None }, source: TimedOut }))"
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: at storage/src/meta/mod.rs:676
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: note: enable `RUST_BACKTRACE=1` env to display a backtrace
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: [2024-01-24 18:58:17.390990 +00:00] INFO temporarily failed to get blob.meta, I/O error (os error 5)
Jan 24 18:58:17 nydus-node containerd-nydus-grpc[3434]: [2024-01-24 18:58:17.391016 +00:00] DEBUG [/reqwest-0.11.16/src/connect.rs:429] starting new connection: http://AWS_ACCOUNT_ID.dkr.ecr.us-west-2.amazonaws.com/
Jan 24 18:58:20 nydus-node containerd-nydus-grpc[3434]: time="2024-01-24T18:58:20.586128236Z" level=info msg="cache usagesha256:d7c238830ced9b4b646aa31b276c02e2d7419ebdf97146cef5ba5b7e754ce044"
Jan 24 18:58:20 nydus-node containerd-nydus-grpc[3434]: time="2024-01-24T18:58:20.586197858Z" level=debug msg="Cache /var/lib/containerd-nydus/cache/d7c238830ced9b4b646aa31b276c02e2d7419ebdf97146cef5ba5b7e754ce044 does not exist"
Jan 24 18:58:20 nydus-node containerd-nydus-grpc[3434]: time="2024-01-24T18:58:20.586224272Z" level=debug msg="Cache /var/lib/containerd-nydus/cache/d7c238830ced9b4b646aa31b276c02e2d7419ebdf97146cef5ba5b7e754ce044.blob.meta does not exist"

I configured the kubelet to use the --image-service parameter, and also add the config to my config.toml:
[root@nydus-node ~]# cat /etc/nydus/config.toml
version = 1
root = "/var/lib/containerd-nydus"
address = "/run/containerd-nydus/containerd-nydus-grpc.sock"

[system]
enable = true
address = "/run/containerd-nydus/system.sock"

[daemon]
nydusd_config = "/etc/nydus/nydusd-config.json"
nydusd_path = "/usr/local/bin/nydusd"
nydusimage_path = "/usr/local/bin/nydus-image"
threads_number = 4
log_rotation_size = 100

[cgroup]
enable = true
memory_limit = ""

[log]
log_to_stdout = true
level = "debug"
log_rotation_compress = true
log_rotation_local_time = true
log_rotation_max_age = 7
log_rotation_max_backups = 5
log_rotation_max_size = 100

[metrics]
address = ":9110"

[remote.auth]
enable_cri_keychain = true
image_service_address = "/run/containerd/containerd.sock"
[root@nydus-node ~]# ps aux | grep -i kubelet
root        4213  1.6  0.6 1971944 101968 ?      Ssl  18:56   0:10 /usr/bin/kubelet --config /etc/kubernetes/kubelet/kubelet-config.json --kubeconfig /var
/lib/kubelet/kubeconfig --container-runtime-endpoint unix:///run/containerd/containerd.sock --image-credential-provider-config /etc/eks/image-credential-p
rovider/config.json --image-credential-provider-bin-dir /etc/eks/image-credential-provider --image-service-endpoint=unix:///run/containerd-nydus/container
d-nydus-grpc.sock

Hi @jonathanbeber What's your nydusd binary version (nydusd -V) ?
It looks like the nydusd is accessing ECR registry by http instead of https, please help to check the configuration /etc/nydus/nydusd-config.json and ensure that the device.backend.config.scheme field is not http: https://github.com/dragonflyoss/nydus/blob/master/docs/containerd-env-setup.md#start-nydus-snapshotter
Note: The device.backend.config.scheme is the URL scheme for the registry. Leave it empty for automatic detection, or specify https or http depending on your registry server configuration.

Thank you very much @imeoer. I feel very sorry for wasting your time with such silly misconfiguration. I used the default config file that is provided inside release package in https://github.com/dragonflyoss/nydus/releases/tag/v2.2.4.
Is there any specific reason the release tar file has it set to http by default instead of letting it empty for automatic discovery?
In any case, I believe that's another discussion and I will close this issue.
Thanks once again!

@jonathanbeber, sorry for the misunderstand in v2.2.4 release, it should will be fixed in the next release.


 the mode styling error

Describe the bug
when clicking on the light mode button, it moves left then right
https://github.com/Bookingjini-Labs/bookingjini-icons/assets/72201773/0fb54370-b2aa-4b0c-ac85-3afa4adadc82
Expected behaviour
The expected behavior when clicking on a light mode button would typically involve the button toggling the interface between light mode and dark mode.
Screenshots
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Issue already covered.


Add support for codeowners to repo

Signed-off-by: Ryan Bogan<EMAIL_ADDRESS>opensearch-project/security-dashboards-plugin pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Enhancement

__Github Issue # or road-map entry, if available:
Progress on: Meta issue

Description of changes:
Add codeowners file

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #861 (61ef33d) into main (a48786e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #861   +/-   ##
=======================================
  Coverage   71.98%   71.98%
=======================================
  Files          87       87
  Lines        1906     1906
  Branches      247      247
=======================================
  Hits         1372     1372
  Misses        480      480
  Partials       54       54

Continue to review full report at Codecov.

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

To expedite merging, created #883 addressing @cliu123's comment.


Fix PyStr::startswith

This pull request tries to fix #3162.
I fixed the bug by using the chars_len method.
Because I don't know the complete reason the chars_len method became a comment, please leave a comment if it must be removed 🙏🏻 .

Hmm, this is intended not to use expensive char_len(). Because our str internal is always a valid utf-8, when it actually startswith or endswith another string, their byte representation must be always same. Did you find the specific point that byte len makes problem? I want to fix it without char_len() if possible

Ah, I got it. start, end in adjust_indices are char index but len is byte index. Could it be solved by processing start and end first as char operations and len later to keep the startswith itself as a byte operation?
impl StartsEndsWithArgs {
    fn get_value(self, len: usize) -> (PyObjectRef, std::ops::Range<usize>) {
        let range = adjust_indices(self.start, self.end, len);
        (self.affix, range)
    }
}

@youknowone I tried to rewrite codes in my best but feel free to suggest your better idea 🙇🏻


Incorrect Handling of Intensity in fisher_mean Calculation

What command was run:
data = [[-45,150,30],[-40,150,35],[-38,145,40]]
pars=pmag.fisher_mean(data = data)
What happened:
a95 missing
The current implementation of fisher_mean includes data with intensity values, which should not be the case. Including intensity leads to an issue where the a95 value cannot be calculated properly. This is because the calculation of a95 implicitly assumes that the input consists of unit vectors.
In the a95 calculation, the number of vectors n is used to offset the resultant vector length. When intensity values are included, the equation a = 1 - b * (N - R) / R results in a being greater than 1, making it impossible to compute a95.
PmagPy version:
4.2.124

Thanks for raising this issue.
Looking at the pmag.fisher_mean function code, the issue is caused by the individual vectors not being normalized when a given data block contains intensity values.
The related code is:
X = np.array(dir2cart(data))
Xbar = X.sum(axis=0)
R = np.linalg.norm(Xbar)
Xbar = Xbar/R
dir = cart2dir(Xbar)
@Swanson-Hysell @ltauxe Shall we 1) force normalizing vectors and support intensity input, or 2) force users to only give [dec, inc] values? My opinion is that it probably does not make sense to include intensity values when calculating fisher mean statistics, but in case there are other functions in PmagPy that use this function in the [dec, inc, int] format, perhaps the best solution now is to force vector normalization?

Thanks for raising this issue. The first thing it made me notice is that the docstring for pmag.fisher_mean() had a poor example.
This example data is not sensical for what should be a nested list (di_block) of declination, inclination pairs:
    >>> data = [[-45,150],[-40,150],[-38,145]]

I have just made a commit (9a458c3) that updates the example to be more sensical:
>>> data = [[150,-45],[151,-46],[145,-38],[146,-41]

Regarding intensity values, as @duserzym writes, a Fisher mean is a mean of unit vectors. So I think the approach here is to allow a nested list of [dec,inc,intensity] to be passed to the function, but to then make them unit vectors when calculating and returning the mean.

Thanks for following up


Add an Into impl for matrix slices to convert them to plain matrices.

Currently, to convert a matrix slice to a plain matrix that owns its data, e.g., a VectorSlice3 into a Vector3, one has to call either .clone_owned() or .into_owned(). For this to be more idiomatic, we should add an Into implementation with the same effect as .into_owned() to matrix slices.

Almost! Your solution will only work for matrices with size known at compile-time. A more generic version that works with dynamically-sized matrix too would be something like:
impl<'a, N, R, C, RStride, CStride> From<MatrixSlice<'a, N, R, C, RStride, CStride>>
    for MatrixMN<N, R, C>
where
    N: Scalar,
    R: Dim,
    C: Dim,
    RStride: Dim,
    CStride: Dim,
    DefaultAllocator: Allocator<N, R, C> {
    fn from(matrix_slice: MatrixSlice<'a, N, R, C, RStride, CStride>) -> MatrixMN<N, R, C> {
        matrix_slice.into_owned()
    }
}

Unfortunately:
error[E0119]: conflicting implementations of trait `std::convert::From<base::matrix::Matrix<_, _, _, base::matrix_slice::SliceStorage<'_, _, _, _, _, _>>>` for type `base::matrix::Matrix<_, _, _, base::matrix_slice::SliceStorage<'_, _, _, _, _, _>>`:
   --> src/base/matrix_slice.rs:864:1
    |
864 | / impl<'a, N, R, C, RStride, CStride> From<MatrixSlice<'a, N, R, C, RStride, CStride>>
865 | |     for MatrixMN<N, R, C>
866 | | where
867 | |     N: Scalar,
...   |
875 | |     }
876 | | }
    | |_^
    |
    = note: conflicting implementation in crate `core`:
            - impl<T> std::convert::From<T> for T;

I think we'd have to specify a separate impl for MatrixVec.

Oh, I did not think of that! Yes, the impl for MatrixVec will have to be separate then.


Fix texture conversion in the GL backend

The line as currently written disallows conversions (except swizzle) because convert can't be true if compressed isn't.

Conversion is fine but it's never called, because compressed == false prevents convert == true.
The same logic at texture creation is even written without compressed (line 5735):
    const bool compressed = bimg::isCompressed(bimg::TextureFormat::Enum(m_requestedFormat) );
    const bool convert    = false
        || m_textureFormat != m_requestedFormat
        || swizzle
        ;


srv6: Move SRv6 encap after internal traffic handlings

Currently, SRv6 encap takes precedense over local delivery, so when configured egress rules overlapping with the local PodCIDR, it takes over the local Pod-to-Pod traffic. Prevent this issue by moving SRv6 encap logic after the local Pod-to-Pod delivery traffic.
srv6: Move SRv6 encap after internal traffic handlings

/test

I'd think that when a VRF is configured and a VPN network overlaps with a local network, you prefer the VPN delivery (for security reasons).

I concluded that at least for now, we should prioritize local delivery because users cannot always control the route imported from upstream, so if the imported route unexpectedly overlaps with Cilium's internal route, then we call it route hijacking. So, for me, always prioritizing the internal route is a safer option.
Also, it's inconsistent with the regular native routing mode (without SRv6). For example, users can install Bird on the node and import the route from an external router. The route will be installed into the kernel's routing table, so it will be evaluated later than local delivery.

Okay I understand the reasoning.

Conformance Ginkgo: https://github.com/cilium/cilium/issues/31336
Conformance Ingress: https://github.com/cilium/cilium/issues/30281

Sorry, but I noticed this doesn't work under endpointRoutes.enabled=true. Let me close this and think about another way around.


moved extractArguments to server class

I think extractArguments should be inside user-facing API, because only user will be passing variable length arguments  and in route-handler arguments become more explicit, need your opinion

I like that. Maybe eventually we could add an object, RouterHandlerDefinitionReader which would be a better home for this function (and testable!).

cool thanks :+1:


Unable to connect to Zulip. Updates may be delayed. Retrying soon

Hi could you please help, having zulip on docker v2.1.4. After last restart of service one of users in browser have this popup errors: Unable to connect to Zulip. Updates may be delayed. Retrying soon... Strange that only one have this problem, another 30 users don't have. Browser cache & data was cleared.

When user connect to chat this errors come in to the logs:
2020-05-21 07:37:31.866 ERR  [] Traceback (most recent call last):
  File "/srv/zulip-venv-cache/6176a52fab8737c09656fc8ad0352547e9801c07/zulip-py3-venv/lib/python3.6/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "./zerver/lib/rest.py", line 35, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/srv/zulip-venv-cache/6176a52fab8737c09656fc8ad0352547e9801c07/zulip-py3-venv/lib/python3.6/site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "./zerver/lib/rest.py", line 172, in rest_dispatch
    return target_function(request, **kwargs)
  File "/srv/zulip-venv-cache/6176a52fab8737c09656fc8ad0352547e9801c07/zulip-py3-venv/lib/python3.6/site-packages/django/utils/decorators.py", line 149, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "./zerver/decorator.py", line 710, in _wrapped_view_func
    return authenticate_log_and_execute_json(request, view_func, *args, **kwargs)
  File "./zerver/decorator.py", line 689, in authenticate_log_and_execute_json
    return limited_view_func(request, user_profile, *args, **kwargs)
  File "./zerver/decorator.py", line 829, in wrapped_func
    return func(request, *args, **kwargs)
  File "./zerver/lib/request.py", line 367, in _wrapped_view_func
    return view_func(request, *args, **kwargs)
  File "./zerver/views/messages.py", line 927, in get_messages_backend
    allow_edit_history=user_profile.realm.allow_edit_history,
  File "./zerver/lib/message.py", line 115, in messages_for_ids
    MessageDict.post_process_dicts(message_list, apply_markdown, client_gravatar)
  File "./zerver/lib/message.py", line 194, in post_process_dicts
    MessageDict.bulk_hydrate_recipient_info(objs)
  File "./zerver/lib/message.py", line 485, in bulk_hydrate_recipient_info
    display_recipients = bulk_fetch_display_recipients(recipient_tuples)
  File "./zerver/lib/display_recipient.py", line 165, in bulk_fetch_display_recipients
    cache_transformer=personal_and_huddle_cache_transformer
  File "./zerver/lib/cache.py", line 395, in generic_bulk_cached_fetch
    db_objects = query_function(needed_ids)
  File "./zerver/lib/display_recipient.py", line 135, in personal_and_huddle_query_function
    result.append((recipient.id, [user_profiles[recipient.type_id]]))
KeyError: 27

After they logoff, erros go out. Can't understand in what problem.
When I open firefox and press F12 in browser and look at network errors I see much 500 errors
URL :https://xxxxxxx/json/messages?anchor=4693&num_before=1000&num_after=0&client_gravatar=true

That looks like some sort of database or cache corruption to me.
I doubt this reflects an issue in Zulip; we can help you debug in the thread you started here:
https://chat.zulip.org/#narrow/stream/49-development-help/topic/unable.20to.20connect.20to.20zulip.20(production)/near/882844


feat(ComposedModal): forward keydown event and add shouldSubmitOnEnter

The dispatched "submit" event fires twice:

https://github.com/IBM/carbon-components-svelte/blob/master/src/ComposedModal/ComposedModal.svelte#L54

The event would fire twice when pressing enter if the focus was on the modal footer primary button. I added an exception for this case.

Can you provide steps that I can test? What is the expected behavior?

I'm using a Form inside a ComposedModal ModalBody and I want to submit the form when I press enter while the focus is on one of the form's components.
Here's some code: https://codesandbox.io/s/objective-chaplygin-9k645?file=/App.svelte
I type the username, then I press tab and and I type the age, then I want to press enter to submit the form, while the focus is still in on the age input.
If you have a better solution than my PR, I'm open to suggestions.

IMO, this relates more to how you're using the form element. I believe that if you have two or more input elements within a form, the "submit" event will not fire when pressing enter unless you have a "submit" button.
What about forwarding the keydown event to the Form component?

IMO, this relates more to how you're using the form element. I believe that if you have two or more input elements within a form, the "submit" event will not fire when pressing enter unless you have a "submit" button.

Yes, pressing enter if I don't have a submit button inside the form doesn't submit the form. The problem with ComposedModal is that the primary button in the footer doesn't have a submit type, so even if I put the modal inside a form then it still wouldn't submit the form when I press enter.

What about forwarding the keydown event to the Form component?

I don't understand how this would help. Can you please elaborate?

I don't understand how this would help. Can you please elaborate?

<!-- Form.svelte -->
<form on:keydown>...</form>

That's what I tried at first but it didn't work. Now I see that the Form component in the library is not forwarding the keydown event :( I replaced the Form in my code with a regular form HTML element and it now works.
Perhaps there should be a keydown event in the Form component?
Anyway, the whole point of this PR is now moot, I'll close it.

Perhaps there should be a keydown event in the Form component?

Yes, that's what I was suggesting

Should I make a PR for this?
On Wed, Mar 24, 2021 at 3:17 PM Eric Liu @.***> wrote:

Perhaps there should be a keydown event in the Form component?
Yes, that's what I was suggesting
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/IBM/carbon-components-svelte/pull/547#issuecomment-805812274,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN5BBFUKFRSF3KMAEQH6TDTFHQ77ANCNFSM4YMFXQQQ
.

Yes, I'd accept a PR for forwarding the keydown event to the Form component


Identify2 Engine

This is the engine for the Identify2 RPC call.  This PR only contains the engine and tests.  It doesn't connect it into any working components just yet.

Integrate a caching system
Handle 3 cases of identify: (a) with tracking; (b) without tracking and with remote assertions; and (c) neither of the above.
Closes CORE-2182, CORE-2171 and CORE-2204

r? @patrickxb

Fine to merge

@patrickxb maybe take a quick second look.  This is much cleaner. The new approach is to run the whole shebang in a background Go routine, but to signal "early out OK" to the calling function via channels.  Now we can use a simple single-flighting system.

LGTM


Bump go version

Bump go version and components used for tests
Signed-off-by: Arnaud Meukam<EMAIL_ADDRESS>

cc @BenTheElder

there's a new lint failure. https://github.com/kubernetes-sigs/oci-proxy/pull/21/files needs to be extended to ReadHeaderTimeout

gimme is currently not supporting 1.19 (not working with 1.19). I'll switch to 1.19 when https://github.com/travis-ci/gimme/pull/203 is merged.
cc @dims

gimme does not need to know that a go version exists to download it, you just need to make sure to use 1.19 not 1.19.0 (1.19.0 is not a go version) https://github.com/kubernetes-sigs/kind/blob/main/hack/third_party/gimme/gimme


Full reindex week of [7/15/2024]

What maintenance needs to be done?
Las time we ran a full reindex was the week of May 20th, 2024
Level of urgency

[x] High
[ ] Moderate
[ ] Low

EOL upgrade

[ ] EOL Date MM/DD/YYYY

Why is this maintenance needed?
Due to lib-sftp disk space issues we're missing incremental files on bibdata events since Jun 11th. See https://github.com/pulibrary/bibdata/issues/2411#issuecomment-2225416951

we swapped the index on 7/17/2024


I.G.I. 2: Covert Strike

https://www.gog.com/index.php/en/game/i_g_i_2_covert_strike

Thanks for your contribution, it’s always appreciated!
Feel free to apply changes to the document directly. Then I can simply approve the change, which makes it a little easier.


Fix SSR

Fix for server side rendering

Fixes https://github.com/gribnoysup/react-yandex-maps/issues/9


Angular Material's component harnesses support for Jest and Cypress

What support is available out of the box for Jest and Cypress as I can only see support for Karma unit tests and Protractor.
https://material.angular.io/guide/using-component-harnesses

Unfortunately the Angular Team does not have the capacity to maintain official support for these, but the component harness framework has been written in a way that allows users to plug in support for additional test environments. It is our hope that the community will share their implementations for test frameworks like the ones you mentioned so that others may benefit. We have some documentation on how to author plugins for other environments, and the official environments should serve as good examples:

TestbedHarnessEnvironment
ProtractorHarnessEnvironment


Question about multiple app logout (Or a single logout)

We have a scenario where we have app1(spa) navigating to app2 (Spa). The user then decides to logout from app2. Are there any suggestions on how the user can be prompted to login if they hit the backbutton  and go to app1? If there is a better forum to ask this, please let me know. I was reading this : https://developer.forgerock.com/docs/platform/how-tos/building-sso-client-your-rest-apis-oidc and decided I would ask the question here.

Take a look at https://github.com/ForgeRock/oidcSessionCheck . You can add this to pretty much any web app, and it will help you with single-logout. If you have any questions or trouble with it, please feel free to follow up with questions in that project. Thanks


package(top-app-bar): permit otherProps

I can see most of components permit otherProps.
If there is any reason to permit otherProps.
I want to add and use it.
Thank you for read :)

@googlebot
I signed it!


Bugfix unscheduled reason

Related issue: kube-HPC/hkube#1970
Resolved an issue where an algorithm's failed scheduling reason persisted even after the algorithm successfully ran. Now, the reason is correctly removed when the algorithm no longer encounters scheduling failures.

This change is

/deploy

/deploy

Deployment did not failed, checked pod and it is updated.
Works as expected.


portaudio / Couldn't get BlueALSA PCM: PCM not found

I have (at least i thought that) a well configured Alsa/bluezalsa Bluetooth Environment on my Raspberry Pi4.
 Thx a lot.

thanks borine !
i tryed both, compiled the newest version of alsa-lib and setting --keep-alive=1.
Some new Messages when launching pyo now appearing,
on the starting its:
ALSA lib dlmisc.c:170:(snd_dlsym_verify) unable to verify version for symbol snd_func_private_integer
ALSA lib conf.c:4556:(_snd_config_evaluate) symbol snd_func_private_integer is not defined inside (null)
ALSA lib conf.c:5047:(snd_config_expand) Evaluate error: No such device or address
ALSA lib conf.c:3694:(snd_config_hook_load) Unable to expand filenames in the pre-load section
ALSA lib conf.c:3572:(snd_config_hooks_call) function snd_config_hook_load_for_all_cards returned error: No such device or address
and after this lines:
D: ../../../src/asound/bluealsa-pcm.c:1057: Getting BlueALSA PCM: PLAYBACK AC:20:19:08:92:D9 sco
D: ../../../src/asound/bluealsa-pcm.c:921: /org/bluealsa/hci0/dev_AC_20_19_08_92_D9/hfpag/sink: Setting constraints
D: ../../../src/asound/bluealsa-pcm.c:431: /org/bluealsa/hci0/dev_AC_20_19_08_92_D9/hfpag/sink: Closing
there comes:
ALSA lib pcm_direct.c:2023:(snd1_pcm_direct_parse_open_conf) Unknown field tstamp_type
Maybe i post it in the github issues of pyo,portaudio and alsa-lib too...

Those ALSA lib messages suggest that either your portaudio library or your bluealsa build (or both) are not compatible with your build of alsa-lib. Does aplay -L still work? if not I suspect the problem may be in your alsa-lib build, or possibly your alsa-lib installation is now part new-build and part original? I'm not an expert on diagnosing alsa-lib errors, but it does appear to me in the above log messages that the clients have different symbol definitions from the library - perhaps a mix of headers from one alsa-lib version and libraries from another?
When I'm building alsa-lib on Ubuntu, I configure it with:
configure --libdir=/usr/lib/x86_64-linux-gnu/

because that is how the Ubintu package does it. You may need to modify your own alsa-lib configure options to make it compatible with your system.

i recompiled alsa-lib and before tried your hint:
configure --libdir=/usr/lib/x86_64-linux-gnu/
so the 6 lines of "new" errors are gone again.

Playing a 48000 khz wav file with aplay dont works:

What if you try
aplay --start-threshold=1 pyo_rec.wav

I take a complete different way, without bluealza.
pulseaudio and compiled the portaudio with pulseaudio host  (https://github.com/illuusio/portaudio).
More Latency but even it is working, thank you for trying to help me....


API to generate keyObject with certificate's id and subject

Add NewPublicKeyObjectFromCertificate and NewPrivateKeyObjectWithCertifiate that generate keyObject with certificate's id and subject. Required by NSSDB (Firefox and Chrome).
Add more attributes to certificate object.

What clients need this? Would you mind adding that in a comment? :)
Instead of having a lot of NewXWithY APIs, I'd prefer this on the object itself. E.g. something like:
func (o *Object) SetSubject(cert *x509.Certificate) error

What clients need this? Would you mind adding that in a comment? :)
Instead of having a lot of NewXWithY APIs, I'd prefer this on the object itself. E.g. something like:
func (o *Object) SetSubject(cert *x509.Certificate) error

I can do that. What method name do you like? We need set 3 attributes -- Subject, Id, ObjectId.
How about
func (o *Object) SetSubject(cert *x509.Certificate) error
func (o *Object) SetId(cert *x509.Certificate) error

Thanks for the help here!
I like the changes to NewX509CertificateObject. Happy to see those attributes set by default.
For public and private keys, is there a strong reason to CKA_ID as a separate method? Or does encapsulating everything in SetSubject work?
certObj, err := p11kit.NewX509CertificateObject(cert)
if err != nil {
    // ...
}
pubObj, err := p11kit.NewPublicKeyObject(cert.PublicKey)
if err != nil {
    // ...
}
// Sets CKA_ID, CKA_SUBJECT, CKA_OBJECT_ID
if err := pubObj.SetSubject(cert); err != nil {
    // ...
}

Then we can add SetID later if we need it?
I've been trying to keep the amount PKCS #11 knowledge to a minimum to use this package :sweat_smile: If a user just needs to know "I call SetSubject to associate a key with a certificate" then we do the heavy lifting, that works for me

Thanks for the help here!
I like the changes to NewX509CertificateObject. Happy to see those attributes set by default.
For public and private keys, is there a strong reason to CKA_ID as a separate method? Or does encapsulating everything in SetSubject work?
certObj, err := p11kit.NewX509CertificateObject(cert)
if err != nil {
    // ...
}
pubObj, err := p11kit.NewPublicKeyObject(cert.PublicKey)
if err != nil {
    // ...
}
// Sets CKA_ID, CKA_SUBJECT, CKA_OBJECT_ID
if err := pubObj.SetSubject(cert); err != nil {
    // ...
}

Then we can add SetID later if we need it?
I've been trying to keep the amount PKCS #11 knowledge to a minimum to use this package 😅 If a user just needs to know "I call SetSubject to associate a key with a certificate" then we do the heavy lifting, that works for me

Sounds good, if we want to hide PKCS11 knowledge. How about
func (o *Object) SetCertificate(cert *x509.Certificate) error

It is accurate describe what the method does (link a cert with key) and also hide the details.

SetCertificate sgtm!


Is the isInterstitialReady working properly?

MAX Plugin Version
2.3.1
Flutter Version
latest
Device/Platform Info
Latest Android
Current Behavior
Hi,
I experience that after calling AppLovinMAX.loadInterstitial(_interstitial_ad_unit_id) and getting a callback that says loaded the plugin  will still not  reply true to this call isReady = (await AppLovinMAX.isInterstitialReady(_interstitial_ad_unit_id))!
In the description it says that once the status is loaded the add is ready to be shown.
In my case 33% if the calls to await AppLovinMAX.isInterstitialReady(_interstitial_ad_unit_id) returns false.
Is this a bug, normal behavior or me misunderstanding something ?
Expected Behavior
No response
How to Reproduce
Run code live against bidding system and track results.
Additional Info
No response

Closing this issue due to inactivity for more than 180 days.   This might be caused if the AppLovinMAX is not initialized yet with AppLovinMAX.initialize().


Fixes Numeric exact match queries to use range queries internally

Description
Updates term and terms queries for numeric fields to use IndexOrDocValues where appropriate.
Related Issues
Resolves #11097

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[X] Public documentation issue/PR created

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

@reta @msfroh addressed your comments. Looks good now?

Gradle failure looks unrelated to my change, although it is hard to tell because this doesn't look like a simple flaky test.

Gradle failure is flaky test -- https://github.com/opensearch-project/OpenSearch/issues/5329

@harshavamsi please rebase against latest  main, thank you

@msfroh could you please take a look? (waiting for your signoff) thank you

Just a residual merge conflict on the changelog, where you picked up a couple of other changes. Otherwise, it looks good to me 👍

Just a residual merge conflict on the changelog, where you picked up a couple of other changes. Otherwise, it looks good to me 👍

Thanks @msfroh, fixed the changelog.


Explore ChatGPT data analysis capabilities

https://openai.com/index/improvements-to-data-analysis-in-chatgpt/
How can we use this with the API?

Dropping this for simplicity.


Autograding code sample

Hello!
Thank you for the great tool!
You mentioned in README, that it can be used in autograding of contests.
Do you have a sample code to check student's work? I have a student's code, teacher's code and inputs to check. How I understand, I need to wrap teacher's code and student's code with autograding code and then perform grading, am I right?
If such a code exists, can you share?
Best reagards,
Evgenii

what was meant in the readme is that it is the engine that evaluates code for emkc contests https://emkc.org/contests. piston itself has no concept of grading, it's only role is execution of code in a sandboxed environment. the method that deals with evaluation of code contest submissions on emkc is here: https://github.com/engineer-man/emkc/blob/develop/platform/api/controllers/ContestsController.js#L193. keep in mind though this has nothing to do with piston.


fet-sh: 1.8 -> 1.9

Motivation for this change
Things done

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

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

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

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

1 package built:

fet-sh


[Question] How to accurately calculate the transfer fee?

Hello, I've faced with the issue that estimated fee doesn't math the real fee paid for the transfer.

const fee = await wallet.methods.transfer({
  secretKey: key.secretKey,
  toAddress: '0QB_kdbjnUbUvL0x8RjwikMOx19XZ_BKXFIiFTrrCIWLXX_u',
  amount: 100,
  seqno,
  payload: 'Hello',
}).estimateFee();

console.log('estimate:', fee);

await wallet.methods.transfer({
  secretKey: key.secretKey,
  toAddress: '0QB_kdbjnUbUvL0x8RjwikMOx19XZ_BKXFIiFTrrCIWLXX_u',
  amount: 100,
  seqno,
  payload: 'Hello',
}).send();

Estimation output
{
  '@type': 'query.fees',
  source_fees: {
    '@type': 'fees',
    in_fwd_fee: 1564000,
    storage_fee: 108,
    gas_fee: 3308000,
    fwd_fee: 1000000
  },
  destination_fees: [],
  '@extra': '1707860854.2520125:2:0.9797682220993219'
}

Sum of storage_fee + in_fwd_fee + fwd_fee + gas_fee equals 5872108 which is 2 gram less then real fee paid for the transaction https://testnet.tonscan.org/tx/2xRWxV-7sIxMWpT8xmLGYgc5Z8YOk93GZVURJzw2Ro0= (0,00587211 TON = 5872110).
How to accurately calculate the transfer fee?

Fee estimation shortage may differ from 2 to 100 grams, but always less then real fee.

same, here is the code piece:
  const estimatedFee: {
    "@type": "query.fees";
    source_fees: {
      "@type": "fees";
      in_fwd_fee: number;
      storage_fee: number;
      gas_fee: number;
      fwd_fee: number;
    };
    destination_fees: [];
    "@extra": string;
  } = await wallet.methods
    .transfer({
      secretKey: keyPair.secretKey,
      toAddress,
      amount: amountInNanoTon,
      seqno,
      payload,
    })
    .estimateFee();

then i sum it all up:
  const allFees = [
    estimatedFee.source_fees.fwd_fee,
    estimatedFee.source_fees.storage_fee,
    estimatedFee.source_fees.gas_fee,
    estimatedFee.source_fees.in_fwd_fee,
  ].reduce((acc, curr) => new BN(curr).add(acc), new BN(0));

eventually such a test fails:
      const targetWalletBalanceAfterWithdrawal = await tonweb.getBalance(
        targetWallet.address!
      );

      expect(new BN(targetWalletBalanceAfterWithdrawal).toString()).toBe(
        withdrawalAmountAfterAllFees
      );

Error:
error: expect(received).toBe(expected)

Expected: "112416255"
Received: "112316255"

считаю amountToWithdrawInNanoTon вот так new BN(amount).sub(allFees)

or this error:
error: expect(received).toBe(expected)

Expected: "96813476"
Received: "96713476"

its always off by 1

Related issue: https://github.com/ton-org/ton/issues/23

it's always off by 100000, it's driving me crazy:
error: expect(received).toBe(expected)

Expected: "503042562"
Received: "502942562"

here is the amountInNanoTon: "508872563" i have, here is the calculated fee: allFees: "5830001", then i subtract the allFees from the amountInNanoTon and get this finalAmountInNanoTon: "503042562", then i check the wallet balance and it's 502942562 which is less for 100000 than expected

here are the fees from estimateFee method and calculation example:
FEES {
  estimatedFee: {
    "@type": "query.fees",
    source_fees: {
      "@type": "fees",
      in_fwd_fee: 1572000,
      storage_fee: 1,
      gas_fee: 2994000,
      fwd_fee: 1000000,
    },
    destination_fees: [],
    "@extra": "1708581252.9725988:5:0.8027042964642166",
  },
  allFees: "5566001",
}

ok, in my case the missing 100000 was gas fee for the receiver wallet. The expected amount-fees correctly lands to the receiver wallet, but then the gas fee of 100000 is subtracted, so all good for me

May I ask how to convert mnemonics into public and private keys？

@895268679long
import * as tonMnemonic from "tonweb-mnemonic";
const mnemonics = ["your mnemonics"]
const keyPair = await tonMnemonic.mnemonicToKeyPair(mnemonics as string[]);

Can someone tell me how to accurately estimate gas fee for TON, using javascript?

ty
On Sat, 10 Aug 2024, 10:41 pm Martins Ojakominor, @.***>
wrote:

Can someone tell me how to accurately estimate gas fee for TON, using
javascript?
—
Reply to this email directly, view it on GitHub
https://github.com/toncenter/tonweb/issues/124#issuecomment-2282146837,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJSQDLHMUT5TNMY7KMZQIXLZQYRB7AVCNFSM6AAAAABDHHXOEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGE2DMOBTG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Markdown in attachments

In the slack api docs they state that attachments by default have markdown turned off.
The only way to enable them is to pass the mrkdwn_in field and pass an array of the items that should have markdown enabled.
https://api.slack.com/docs/formatting
"attachments": [
        {
            "title": "Title",
            "pretext": "Pretext _supports_ mrkdwn",
            "text": "Testing *right now!*",

            "mrkdwn_in": ["text", "pretext"]
        }
    ]

A basic solution would be to add the Mrkdwn_in variable to SlackAttachment class
public List<string> Mrkdwn_in {get;set;}

To make this better have accessible variables that return the possible fields that markdown can be enabled on pretext, text, fields

Thank you! I really wanted markdown in my attachments


fontconfig_210: remove

fontconfig 2.10.x hasn't had a release in years, is nowhere used inside
nixpkgs and vulnerable to CVE-2016-5384.
Motivation for this change
https://github.com/NixOS/nixpkgs/issues/88289
Things done

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

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

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

We might want to also backport this to 20.03 (there's https://github.com/NixOS/nixpkgs/issues/73630 for it), but I leave this decision to @NixOS/nixos-release-managers.

Okay, I can remove this. We might want to resurrect the code when bumping fontconfig to 2.13 and keep backwards-compat support for 2.12, but then it can easily be resurrected from the history I guess.

Urgh, just took a closer look - in fontconfig-conf we use $out/etc/fonts/conf.d for the old version, and $out/etc/fonts/${latestVersion}/conf.d for the more recent version… Shouldn't it be the other way around?

Urgh, just took a closer look - in fontconfig-conf we use $out/etc/fonts/conf.d for the old version, and $out/etc/fonts/${latestVersion}/conf.d for the more recent version… Shouldn't it be the other way around?

If there's any issue see here so we can fix them in one go https://github.com/NixOS/nixpkgs/pull/73795

I expect that severity of 2.10 remaining is low (in the current way).  Just getting the config files from 2.10 shouldn't be vulnerable, and it seems very unlikely that someone opted in to use 2.10 in some other way.  Still, it would be nice to clean this up during the 2.13/2.14 update.

Okay, fine to not pursue this any further if we can address this during #73795 soon - it was already suggested in https://github.com/NixOS/nixpkgs/pull/73795#issuecomment-648460377 anyways.

Doesn't look like this made it into https://github.com/NixOS/nixpkgs/pull/73795. Should we reopen?

I reopened https://github.com/NixOS/nixpkgs/issues/88289.

@cole-h would you be up to proposing a PR addressing #88289?

I'm unclear on what direction I should go in, if I were to accept. Do we want to remove 2.10, or just patch it (https://cgit.freedesktop.org/fontconfig/commit/?id=7a4a5bd7897d216f0794ca9dbce0a4a5c9d14940, according to the vulnerability page)?
In the case we want to remove it, how should I handle the aforementioned nixos/modules/config/fonts/fontconfig.nix? I will admit, I'm not well-versed in fontconfig (much less our fontconfig situation), so I don't expect to get it right upon submission.
Once these questions are answered, I can find some time during the week to tackle this. However, I wouldn't be offended if somebody beats me to the punch... ;^)

I expect we want to bump supportVersion to 212 (and thus bring back the 2.12.6 expression), at least from https://github.com/NixOS/nixpkgs/pull/73795#issuecomment-657076484

2.12 is not necessary since our patched 2.14 should be compatible with 2.11+. We should just drop support version altogether once we are sure there are no regressions.


Implement new CertStore CRD to replace secretStoreCSI driver

It will be more flexiable if Ratify implemented our own keyvault fetching logic. The CSI driver has limitations below:
Since csi driver uses volume mounts, new certs or change of mount location will require pod restart
CSI driver requires specifying individual cert object

This is a must for RC1.

Feature has been merged.


tests: Fix duplicate testname and adjust parameters

Two tests had the same function name and the simple dict test never got run.

Ok, needs some tweaks for Python 3.5 which actually does not guarantee order.

Now fixed and should be ready to merge.

Thanks for your contribution @cjgu. Keep it coming! 🌈


Add body, is it colliding?

Looked around but don't see an easy way to do this.  When adding a body to the world, is there a way to easily ask if that body is "on top" (colliding with) any existing body?  Tried to process "collisionStart/End" but it looks like those happen only as bodies move around.
Two additions:

To explain: I need to detect if an application drag/drop event, which normally would add a body to my world, would result in a colliding body.  If so, I want to change its collisionFilter characteristics.
I've studied the code in the MouseConstraint and think it will work for me with some modification.

So comments would be welcome, otherwise you can close this issue.  Thanks.

Try this:
var collision = SAT.collides(bodyA, bodyB);

if (collision.collided) {
    // do something
}

Where bodyA is your new body and bodyB is some other body to check, so naturally you should loop this over every body that could be collided. For instance those from Composite.allBodies(world).
Actually, this might be a nice addition to Matter.Query.

Shamelessly stealing code, I created a routine that returns intersecting (colliding) bodies given a body and a filter.  I use this to detect drag/drop collisions, but also to display intersections among bodies.

        self.intersections = function (target, filter) {
            var result = [],
                oldFilter = target.collisionFilter;

            target.collisionFilter = filter || FILTER_TILE;

            var _getRegion = function (body) {
                var grid = engine.broadphase,
                    bounds = body.bounds,
                    startCol = Math.floor(bounds.min.x / grid.bucketWidth),
                    endCol = Math.floor(bounds.max.x / grid.bucketWidth),
                    startRow = Math.floor(bounds.min.y / grid.bucketHeight),
                    endRow = Math.floor(bounds.max.y / grid.bucketHeight);
                return {
                    id: startCol + ',' + endCol + ',' + startRow + ',' + endRow,
                    startCol: startCol,
                    endCol: endCol,
                    startRow: startRow,
                    endRow: endRow
                }
            };

            var _getBucketId = function (column, row) {
                    return column + ',' + row;
                },
                i, row, col;

            var region = _getRegion(target);
            // var region = target.region;

            for (col = region.startCol; col <= region.endCol; col++) {
                for (row = region.startRow; row <= region.endRow; row++) {

                    var bucketId = _getBucketId(col, row),
                        bucket = engine.broadphase.buckets[bucketId];

                    // broad phase
                    if (bucket) {
                        for (i = 0; i < bucket.length; i++) {
                            var body = bucket[i];
                            if (body.id !== target.id) {
                                if (Matter.Detector.canCollide(target.collisionFilter, body.collisionFilter)) {
                                    // mid phase
                                    if (Matter.Bounds.overlaps(target.bounds, body.bounds)) {
                                        parts_scan:
                                            for (var j = target.parts.length > 1 ? 1 : 0; j < target.parts.length; j++) {
                                                var partA = target.parts[j];

                                                for (var k = body.parts.length > 1 ? 1 : 0; k < body.parts.length; k++) {
                                                    var partB = body.parts[k];

                                                    if ((partA === target && partB === body) || Bounds.overlaps(partA.bounds, partB.bounds)) {
                                                        // narrow phase
                                                        var collision = Matter.SAT.collides(partA, partB);
                                                        if (collision.collided) {
                                                            if (!result.includes(body)) {
                                                                result.push(body);
                                                            }
                                                            break parts_scan;
                                                        }
                                                    }
                                                }
                                            }
                                    }
                                }
                            }
                        }
                    }

                }
            }
            target.collisionFilter = oldFilter;
            return result;
        };

Looking at Matter.Query's 'point' and 'region' methods, I see that they do
not take advantage of the grid buckets.  Is there a reason?  I was
considering writing a mod (pull?) that calculated my colliding bodies.  My
solution so far was some monkey code, copying/pasting from matterjs.  I
just ran into why one shouldn't monkey code like this since it broke
between ver 11 and 12.  I know better.
On Sun, Sep 17, 2017 at 8:29 AM, Liam<EMAIL_ADDRESS>wrote:

Try this:
var collision = SAT.collides(bodyA, bodyB);
if (collision.collided) {
// do something
}
Where bodyA is your new body and bodyB is some other body to check, so
naturally you should loop this over every body that could be collided. For
instance those from Composite.allBodies(world).
Actually, this might be a nice addition to Matter.Query.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/liabru/matter-js/issues/478#issuecomment-330056691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKEOaZKJafzErsAO5E4RtTU2jPtbVOP2ks5sjTrTgaJpZM4PD56t
.

Grokking a bit more, I see that the Grid is an implementation of a
broadphase controller which has a contract.  I would propose a new
(optional?) method, "getBodies" or something taking a rectangular region
(or degeneratively, a point), returning an array of bodies.  This could be
used in a new Query routine.  The Query routine would check to see if the
broadphase controller implements getBodies, then use it, or fall back to
all bodies.
If this sounds interesting, I'll learn how to properly create a pull
request, matching coding styles and standards.
On Thu, Oct 5, 2017 at 10:16 AM, Craig Fransen<EMAIL_ADDRESS>wrote:

Looking at Matter.Query's 'point' and 'region' methods, I see that they do
not take advantage of the grid buckets.  Is there a reason?  I was
considering writing a mod (pull?) that calculated my colliding bodies.  My
solution so far was some monkey code, copying/pasting from matterjs.  I
just ran into why one shouldn't monkey code like this since it broke
between ver 11 and 12.  I know better.
On Sun, Sep 17, 2017 at 8:29 AM, Liam<EMAIL_ADDRESS>wrote:

Try this:
var collision = SAT.collides(bodyA, bodyB);
if (collision.collided) {
// do something
}
Where bodyA is your new body and bodyB is some other body to check, so
naturally you should loop this over every body that could be collided. For
instance those from Composite.allBodies(world).
Actually, this might be a nice addition to Matter.Query.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/liabru/matter-js/issues/478#issuecomment-330056691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKEOaZKJafzErsAO5E4RtTU2jPtbVOP2ks5sjTrTgaJpZM4PD56t
.

I spent today creating a prototype of a pull request which would implement my collidingBodies idea.  I want to make it efficient, so I want to leverage broadphase to narrow down the bodies to test.
I created a Grid.findBodies call to return all the bodies in buckets within a given bounds.  And then I wrote a routine in my own application that would loop through these bodies and return
identified collisions for all the parts of the target with all the parts of the bodies.
Although I'm happy to create a pull request, in studying your existing independent modules it is not clear where a routine such as mine would make sense.  Any module I choose seems to introduce a new unnatural dependency for that module.
So my question is: would such a routine make sense in matterjs?  Or should I just keep it in my codebase?
    /**
     * Given a bounds, returns contained bodies
     */
    Grid.findBodies = function (grid, bounds) {
        var i,
            row,
            col,
            region = _getRegion(grid, {bounds:bounds}),
            result = [];

        for (col = region.startCol; col <= region.endCol; col++) {
            for (row = region.startRow; row <= region.endRow; row++) {
                var bucketId = _getBucketId(col, row),
                    bucket = grid.buckets[bucketId];
                if (bucket) {
                    result.push.apply(result, bucket);
                }
            }
        }

        return result;
    };

And the routine in my code:

    self.collisions = function (target, filter) {
        var result = {},
            oldFilter = target.collisionFilter,
            i,
            grid = engine.broadphase,
            bodies = grid.controller && grid.controller.findBodies ? grid.controller.findBodies(grid, target.bounds) : engine.world.bodies;

        var makeResultKey = function (partA, partB) {
            return partA.id + ":" + partB.id;
        };

        target.collisionFilter = filter || FILTER_TILE;

        for (i = 0; i < bodies.length; i++) {
            var body = bodies[i];
            if (body.id !== target.id && (!target.ignoreId || target.ignoreId !== body.id)) {
                if (Matter.Detector.canCollide(target.collisionFilter, body.collisionFilter)) {
                    // mid phase
                    if (Matter.Bounds.overlaps(target.bounds, body.bounds)) {
                        for (var j = target.parts.length > 1 ? 1 : 0; j < target.parts.length; j++) {
                            var partA = target.parts[j];

                            for (var k = body.parts.length > 1 ? 1 : 0; k < body.parts.length; k++) {
                                var partB = body.parts[k];

                                if ((partA === target && partB === body) || Matter.Bounds.overlaps(partA.bounds, partB.bounds)) {
                                    // narrow phase
                                    var collision = Matter.SAT.collides(partA, partB);
                                    if (collision.collided) {
                                        var resultKey = makeResultKey(partA, partB);
                                        if (!result[resultKey]) {
                                            result[resultKey] = {target: partA, part: partB};
                                        }
                                    }
                                }
                            }
                        }
                    }
                }
            }
        }

        target.collisionFilter = oldFilter;
        return result;
    };

Can you put this in a fiddle giving an example of it working? Then I can get my head around it better!

Hey so I managed to check for collisions by using the Bounds.overlaps function. See example below:
....
var Bounds = Matter.Bounds;
....
function checkIfSpaceOccupied(cx, cy, approximateRange) {
var newBounds = {
min: {
x: cx - approximateRange,
y: cy - approximateRange
},
max: {
x: cx + approximateRange,
y: cy + approximateRange
}
}
for(var j = 0; j < worldObjects.length; j++) {
if (Bounds.overlaps(worldObjects[j].bounds, newBounds)) {
return true;
}
}
return false;
}
....
This example is not perfect as it is intended to be used with circular objects, but you guys get the idea.


Mix-up of return codes when using GetWorkingDirectory

I got strange behavior when trying to upload binary files to my ftp.  EnableThreadSafeDataConnections is false in my case and I did all FTP operations only in single thread. The GetWorkingDirectory() throw the FluentFTP.FtpCommandException with "550 Could not get file size." Wireshark shows that PWD returns previous error code from SIZE command:
...
3554	59.206258	FTP	61	Request: CWD /
3555	59.247468	FTP	91	Response: 250 Directory successfully changed.
3556	59.254597	FTP	62	Request: TYPE I
3557	59.296293	FTP	85	Response: 200 Switching to Binary mode.
3559	59.302661	FTP	XXX	Request: SIZE /abc/asd.xyz
3562	59.343603	FTP	84	Response: 550 Could not get file size.
3563	59.349279	FTP	60	Request: EPSV
3565	59.391072	FTP	103	Response: 229 Entering Extended Passive Mode (|||13061|).
3570	59.437461	FTP	XXX	Request: STOR /abc/asd.xyz
3572	59.478450	FTP	76	Response: 150 Ok to send data.
34674	76.445044	FTP	78	Response: 226 Transfer complete.
34675	76.447271	FTP	XXX	Request: SIZE /abc/asd.xyz
34677	76.487917	FTP	68	Response:<PHONE_NUMBER>2
34678	76.487985	FTP	YYY	Request: SIZE /abc/qwe.xyz
34682	76.529395	FTP	84	Response: 550 Could not get file size.
34683	76.529455	FTP	59	Request: PWD
34685	76.571388	FTP	63	Response: 257 "/"
; FtpCommandException with 550 error was caught here during GetWorkingDirectory() call

Please let me know if you need more information. It's 100% reproducible in my environment.
P.S. Everything is good when EnableThreadSafeDataConnections  is true.

You don't need wireshark. Just enable logging. See this FAQ entry.

I probably found the bug:

Good find. Can you fix it? And please prefer using high level API where possible.

I think you have to call GetReply() like so:
using (var stream = (FtpDataStream) myFtpClient.OpenWrite(file))
 action(stream);
GetReply()
using (var stream = myFtpClient.OpenWrite(file))
 action(stream);
GetReply()

Does this work for you?

Is this still an issue? The Dispose calls were recently fixed...


_DEFAULT_SOURCE should be used when _BSD_SOURCE

The compiler complains:
/usr/include/features.h:184:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"

Solution: https://stackoverflow.com/a/29201732

Fine with me.
I don't get these warning though. What's your setup?

The syslog-ng project uses libnet, and when you compile syslog-ng on ubuntu bionic, the following errors appear.

On which platform?

@koeppea I tried only on x86_64.


switch linting from pylint to ruff

pylint feature parity is tracked here https://github.com/astral-sh/ruff/issues/970.
the biggest missing feature set seems to be lack of docstring linting.
out of the unimplemented errors, the ones I recognize are:

function-redefined
import-error
no-member
too-many-function-args

warnings I recognize:

arguments-differ
attribute-defined-outside-init
missing docstring (like 6 of them)
pointless-string-statement (I use this as in-script documentation lol)
redefined-outer-name

on hold until ruff supports docstrings

Implemented since my last review:

function-redefined
missing-class-docstring / C0115 (D101)
missing-function-docstring / C0116 (D103)
missing-module-docstring / C0114 (D100)

Still not implemented

import-error
no-member
too-many-function-args
arguments-differ
attribute-defined-outside-init
redefined-outer-name

If we don't think the unimplemented ones above (or any I missed) I'd be happy switching to ruff from pylint @dpaiton @slundqui

I think we still want

import-error
no-member
arguments-differ (warning)
redefined-outer-name (warning)

IMO the other two are nice-to-have but not required.


Don't wrap _BaseParameter get and set

This breaks multi and array parameters because in unconditionally calls _save_val
Among other issues this resulted in a ~1Gb snapshot because all array parameters were suddenly stored in the snapshot
There are other solutions but I think it's fair not to wrap the getters and setters unconditionally

Isn't this why we have snapshot_value?
On Wed, Oct 18, 2017, 7:50 PM Jens Hedegaard Nielsen <
<EMAIL_ADDRESS>wrote:

This breaks multi and array parameters because in unconditionally calls
_save_val
Among other issues this resulted in a ~1Gb snapshot because all array
parameters were suddenly stored in the snapshot
There are other solutions but I think it's fair not to wrap the getters
and setters unconditionally
You can view, comment on, or merge this pull request online at:
https://github.com/QCoDeS/Qcodes/pull/797
Commit Summary

Don't wrap _BaseParameter get and set

File Changes

M qcodes/instrument/parameter.py
https://github.com/QCoDeS/Qcodes/pull/797/files#diff-0 (23)

Patch Links:

https://github.com/QCoDeS/Qcodes/pull/797.patch
https://github.com/QCoDeS/Qcodes/pull/797.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QCoDeS/Qcodes/pull/797, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGgLHTFK_5TvP26QTnr95uaVEvYqAd1sks5stbvIgaJpZM4P9Xei
.

I have implemented that as an alternative in #800

We'll close this in favour of #800.


fix(deploy): gh-pages checkout initial branch on error

If github-pages:deploy fails due to 'No changes found' or fails pushing to git repo, it then attempts to checkout the initial branch.
Closes #3030

Thanks for fixing this @taylorjb !


Provided offset not always honored when creating receiver

Expected Behavior
When calling hub.Receive() with eventhub.ReceiveWithStartingOffset(offset) as an option, the receiver starts reading from the provided offset.
Actual Behavior
If a receiver was previously created and closed within the same eventhub.Hub client for the same consumer group + partition, the next call to hub.Receive() will start from wherever that receiver stopped.
This seems to stem from the fact that when creating a new receiver, the options are applied first and then the last stored checkpoint is retrieved, which overrides the checkpoint provided in the option:
https://github.com/Azure/azure-event-hubs-go/blob/9898ba65784f054a43e4b18c84b5abe5fe8217b1/receiver.go#L146-L156
I'm not sure if this is intentional behavior, but it feels like a bug. Two reasonable fixes would either be to apply the options after fetching the stored checkpoint or have a check to not use the stored checkpoint if an option specified a checkpoint already.
Environment

OS: MacOS Catalina, Alpine Linux (in Docker)
Go version: 1.15.0
Version of Library: 3.3.0

Thanks for the feedback, looking into this and your proposed change.

Fixed in v3.3.1.


Build Errors Following Tutorial

Problem encountered on https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/generate-code
Operating System: windows
When I tried to run the MyMLApp.ConsoleApp there were 7 build errors. CS0579.
These were in MyMLAppML.Model.AssemblyInfo.cs file.
[assembly: System.Reflection.AssemblyCompanyAttribute("MyMLAppML.Model")]
[assembly: System.Reflection.AssemblyConfigurationAttribute("Debug")]
[assembly: System.Reflection.AssemblyFileVersionAttribute("<IP_ADDRESS>")]
[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0")]
[assembly: System.Reflection.AssemblyProductAttribute("MyMLAppML.Model")]
[assembly: System.Reflection.AssemblyTitleAttribute("MyMLAppML.Model")]
[assembly: System.Reflection.AssemblyVersionAttribute("<IP_ADDRESS>")]
This is the output from the Build.
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(14,12,14,54): error CS0579: Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(15,12,15,60): error CS0579: Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(16,12,16,58): error CS0579: Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(17,12,17,67): error CS0579: Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(18,12,18,54): error CS0579: Duplicate 'System.Reflection.AssemblyProductAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(19,12,19,52): error CS0579: Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute
1>MyMLAppML.Model\obj\Debug\netstandard2.0\MyMLAppML.Model.AssemblyInfo.cs(20,12,20,54): error CS0579: Duplicate 'System.Reflection.AssemblyVersionAttribute' attribute
Thanks,
Scott

This is resolved in the lastest version of Model Builder - released last Thursday. Can you upgrade and try again?

Resolving due to lack of activity. I believe this issue has been resolved in the latest version. If you still hit this issue .. please re-open!
Thanks for reporting!


Build break due to Google code obsolescence

~/s $ export GOPATH=$PWD
~/s $ go get github.com/otoolep/syslog-gollector
warning: code.google.com is shutting down; import path code.google.com/p/log4go will stop working
package code.google.com/p/snappy-go/snappy: unable to detect version control system for code.google.com/ path
~/s $ go install github.com/otoolep/syslog-gollector
src/github.com/otoolep/sarama/snappy.go:5:2: cannot find package "code.google.com/p/snappy-go/snappy" in any of:
        /home/philip/.gvm/gos/go1.5/src/code.google.com/p/snappy-go/snappy (from $GOROOT)
        /home/philip/s/src/code.google.com/p/snappy-go/snappy (from $GOPATH)
~/s $ ls
src

Fixed at https://github.com/otoolep/syslog-gollector/commit/784e6971b887cc3883800b604e9b37688f0c811c


Add create flags to control weather deployments should be created

Summary
This PR adds create flags to each deployment to control if a deployment should be created.
Use Case
In our use case, we are trying to deploy multiple operators within our cluster and have them scoped within its own namespace (see https://github.com/external-secrets/external-secrets/pull/800 for more details).

In order to do so, we need to first deploy external-secrets with only CRDs (i.e. Stores and ExternalSecrets) which would be used by the consequential deployments of external-secrets in each namespace.
We currently work around it by setting replicaCount to 0 but it would create some dangling resources in the Kube which is a bit dirty.
Adding create flags to each deployment will help enable the usage of multiple operators.

Yes, I believe this might indeed be needed, as you cannot have more than one webhook/cert controller deployment, but you indeed can have multiple ESO controllers =)

/ok-to-test sha=3502ab0a94df9f26df94cc893b2d3a61f18dc4f7

/approve

/merge


Enable bitcode for ios native libraries

Fixes #16839
@jtattermusch

Thanks for the contribution! I'll get that tested.

Started an adhoc run of package build: https://sponge.corp.google.com/invocation?id=bdb704c2-0123-4793-ad21-c3edf9169836&searchFor=

The adhoc build of unity package with grpc_csharp_ext bitcode embedded is here: https://storage.googleapis.com/grpc-testing-kokoro-prod/test_result_public/prod/grpc/core/master/windows/grpc_build_packages/8035/20190829-061342/github/grpc/artifacts/grpc_unity_package.2.24.0-dev.zip
@koshelevpavel  can you test if that works for you?

The adhoc build of unity package with grpc_csharp_ext bitcode embedded is here: https://storage.googleapis.com/grpc-testing-kokoro-prod/test_result_public/prod/grpc/core/master/windows/grpc_build_packages/8035/20190829-061342/github/grpc/artifacts/grpc_unity_package.2.24.0-dev.zip
@koshelevpavel can you test if that works for you?

Yes! It works for me. Thank you so much.


[BUG] Unable to attach claimed volume - no error given

Describe the bug
When deploying a persistent volume, a persistent volume claim and a pod using the claim, everything works as expected. If the pod is stopped, the claim persists. In this stopped state, however, it's not possible to attach to the volume by using the UI. The option to attach is there, but it doesn't do anything. When the claim is removed, however, the attachment works as expected.
To me, this seems to be expected behavior. The bug here is that A: the attach option is available when it perhaps shouldn't be and B: there's no error, log or notification to show the user that this is a problem.
To solve, either disable the option to attach via the UI when a volume is claimed, or notify the user that it cannot be done.
To Reproduce
Steps to reproduce the behavior:

Create a persistent volume, persistent volume claim and pod using the claim
Delete the pod
Via the UI, try to attach the volume to a node
See that nothing happens
Delete the persistent volume claim
Via the UI, try to attach the volume to a node
See that it works as expected

Expected behavior
Either the option to attach should not be given, or a notification should be shown to let the user know it's not possible to attach to a claimed volume.
Environment:

Longhorn version: v1.1.1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: microk8s, v1.21

If I've understood things correctly and this is indeed expected behavior, I'd like to ask a related question as well.
Postgres will not start in a directory which is not empty. If I deploy a volume and claim alongside Postgres, mkfs will leave the lost+found directory in the volume. One would think that by stopping the container, attaching the volume to a node and then cleaning it up prior to deploy the pod could work. But since it's not possible to attach a claimed volume, that seems like a no go. If I remove the claim to attach to the volume, I cannot reuse the volume. I suppose I could create a backup image of an empty volume and restore from it when I deploy Postgres. This, however, seems like a bit of a workaround. Another workaround would be running rm -rf lost+found before starting Postgres, but that seems as a bit of an hack as well.
What is the recommended approach here? I'd like to make the approach as code-defined as possible, meaning I'd rather not first create the volume and claim using the UI.

Longhorn does not manage how application from workload write directory/file to storage.  For lost+found that create by file system, it should be able to manage in the deployment manifest lifecycle: pre/post.
For PV to be reused after manually removed PVC, it is required to clean up ClaimRef of PV. Otherwise, the existing PV cannot be reused.
For PGDATA, it needs to change deployment manifest to appropriate path where data is stored. e.g.,

          volumeMounts:
            - name: pgdata
              mountPath: /postgres

@AlexGustafsson Are you able to resolve the issue?  Perhaps we can close it the ticket?

@cclhsu I’ll go ahead and close it. Thank you for the help.


Replay refactor

This pull request refactors the replay system to only support the new replay format (plain-text hex representing transmitted packets).
Major changes

SD encoding logic all removed as it is no longer necessary

This also includes the telemetry-parser utility. It is still available in the v0 release.
Any SD logic in the old data block file is still there

Replay doesn't really work with speed controls anymore (just reads packets constantly until file ends). This will need to be solved as an issue. I have left this unresolved in cases a new design could be explored where replays are just an RN2483 emulation
Recording is no longer implemented. This may even be left out in favor of using the log files recorded onboard the rocket, since there will be no missed packets/noise

There are also some small changes where Mission objects no longer have "epochs" as there is less metadata on mission files now. Length is measured in number of packets. Old mission files deleted, etc.
The telemetry replay play command works as intended with no errors, so this functionality is complete enough to be merged. Issues will be opened for resolving any other refactor side effects.

Closes #76


Game Component Draft

Draft of some game Component (Bomb, Character, PowerUp) + Camera

@EternalRat  You should resolve conversations when the issue is fixed
I thought you still had issues until I looked commit by commit changes

This branch is stale, I based the Movement branch on commits from here so they will be on the same PR.


Added a BEM-style active class.

Sort of addresses #76 but I added a BEM class and left in the older 'active' classes for compatibility. This should be paired with a breaking change that removes the older classes at some point.
What do you think?

I'm really sorry, I completely missed this PR. Reviewing it tonight and I'll get back to you with any feedback.

Tested and working. Thanks again, especially for your patience. Releasing as a patch.

Merged locally due to conflicts. Thanks again @pixelbandito


[PYTHON][RABIT] calling rabit.init multiple times exits the process

Environment info
Operating System: macOS 10.12.6
Compiler: gcc
Package used (python/R/jvm/C++): python
xgboost version used: 0.6
If installing from source, please provide

The commit hash (git rev-parse HEAD) 78c4188cec31425f708d238160ea3afb67a7250a

Logs will be helpful (If logs are large, please upload as attachment).

If you are using python package, please provide

The python version and distribution: 0.6, source

Steps to reproduce
In [1]: import xgboost as xgb
In [2]: xgb.rabit.init()

In [3]: xgb.rabit.init()
rabit::Init is already called in this thread

(and the process exits)

Would it be possible to avoid this, say by storing a global or threadlocal variable? It seems like https://github.com/dmlc/rabit/blob/a764d45cfb438cc9f15cf47ce586c02ff2c65d0f/python/rabit.py#L46-L52 intends to do something like that, but even then, the init will still continue to run, since it doesn't check the result and continues unconditionally.
I'm happy to submit a patch for this, but I'm not sure whether to make it in the rabit repo or here. My local copy picks up the version of rabit in xgboost/python-package/xgboost/rabit.py, so I've made the issue here.

Was this fixed in rabit?

This issue was closed due to the current triaging. We try to aggressive close issues from now on so opened issues can get attended to. I went ahead and re-opened it.

please send a PR to the rabit repo


运行一段时间会出现玩家进不去

Description
这样，服务器重启后就可以进了，但运行一段时间又会这样
Reproduction Steps
运行一段时间就会出现
Expected Behaviour
暂无
Server Details
1.20.1
LuckPerms Version
5.4.137
Logs and Configs
No response
Extra Details
No response

If you are a server admin, please check the console for any errors

Please provide your full `logs/latest.log file by using a paste services such as https://pastes.dev
And follow the issue template next time, in English preferably. You should also use our discord for support.


Pipfile should specify Python version

To reduce friction and the possibility of error when running pipenv install on a project that already has a Pipfile, the Pipfile should specify the Python version. This is already a feature in bundler, where you can specify the Ruby version with the ruby keyword.

you can require a version with pipfile
[requires]
python_version = "2.7"

Currently, you can check these PEP 508 specifiers with $ pipenv check.

Awesome, thanks!


Blog on Ortelius Non-Functional Requirements

The architecture teams work on non-functional requirements should be added as a blog, and added to the documentation.

Two Blogs have been submitted.
https://ortelius.io/blog/2024/02/28/what-are-non-functional-requirements-and-why-do-they-matter/
https://ortelius.io/blog/2024/02/29/2024-ortelius-non-functional-requirements/


Windows 11 Using HTML, CSS & JavaScript

Project title
Windows 11 Using HTML, CSS & JavaScript
Project Description
Hi @khushi-purwar, I would love to create Windows 11 lookalike using HTML, CSS, and JavaScript. Please assign me to this issue so that I can start working.
Thank You
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript

@khushi-purwar please assign me with this issue. I am a participant in GSSOC'22.
Thank You

@mishramuskaan24 you can start working on it.


enable cuda build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

#119

The CUDA builds but the MPI+cuda failed due to No space left on device

@conda-forge-admin, please rerender

@mattwthompson This working fine when tested locally. Shall we merge this PR?

@mattwthompson I think we could potentially test cpptraj.cuda. However, I don't know how to test this only when there is cuda. I wonder if I can have some of your help? Thank you.

I think it can be tucked away under a conditional like already happens for MPI: https://github.com/conda-forge/ambertools-feedstock/blob/bc93c747c80f8592d002ea0aa5ac321a82e9fe6f/recipe/run_test.sh#L50-L56

@conda-forge-admin, please rerender

@mattwthompson Ok, I have added a which and a lld test for cpptraj.cuda, which seems to pass.

@conda-forge-admin, please restart ci

@conda-forge-admin, please rerender

@conda-forge-admin, please restart ci

@mattwthompson Shall we merge this before working on 24? All the builds are passing and I have test for cpptraj.cuda.

It's probably fine but I'd like somebody from the Amber community to chime in

@njzjz Do you mind give this PR a review? Thanks.

You can re-configure the build process to store artifacts if they're not already there (I haven't checked), re-render, and then on the next build they're be available to download somewhere on the Azure pages that are linked in "CI" from this PR. Then you can install those as local conda packages
https://conda-forge.org/docs/maintainer/conda_forge_yml/#azure
Everything can be done locally (there's a build_locally.py file somewhere and/or information in the docs https://conda-forge.org/docs/maintainer/) but given the complexity of this feedstock I would worry there's a risk of false positives compared to what happens in automation

@dacase Building the linux version is quite easy, you just find a linux machine. clone the repo, run build_locally.py and select the relevant option. Then upload the .conda file to your local conda channel and you can then install it with conda.
In our company, we use this branch to build amber, where I change the source to build from local tar.gz file. Then upload the .conda to company conda channel and deploy in our production environment where pmemd.cuda.mpi works as expected.

@xiki-tempula could you merge the main branch into this once more? I don't want to accidentally revert #147
After that I'll merge tomorrow morning if nobody else got to it by then (or objects)


Inconsistent code logic for Model.build

In this function Model.build, the code logic seems buggy. It says that it does not accept dict as the type of input_shape, and reject the dict type here.
But then it has further code to check for the dict type, which makes me wonder that the purpose is to actually allow the usage of dict type...
I post this issue because I want to use dict type for the input_shape in my project. Right now, I have to override this function in my subclassed model and transform dict to list in a hard-coded order.

It says that it does not accept dict as the type of input_shape, and reject the dict type here.

It seems to me that dict is in valid_types
https://github.com/tensorflow/tensorflow/blob/d02bdf70273341cb41adc6f6f177b045dca1e470/tensorflow/python/keras/engine/training.py#L358-L359

Sorry, as @bhack pointed out, the problem has been fixed in the newest version.
I actually encountered this problem in version 2.3.0 here:
https://github.com/tensorflow/tensorflow/blob/5681c179eff80bce00e526303950b67b23cad14c/tensorflow/python/keras/engine/training.py#L377-L378


Title: Covid-19 X-Ray Image Classification

Is your proposal related to a problem? Please describe.
Description :- The Coronavirus Disease 2019 (COVID-19) has brought a worldwide threat to the living society. The whole world was putting incredible efforts to fight against the spread of this deadly disease. Meanwhile, hundreds of machine-learning experts volunteer their time and expertise to help medical researchers in this fight.
Aim :- One of the areas where machine learning can help is detecting the COVID-19 cases from chest X-ray images. The task is a simple classification problem where given an input chest X-ray image, the machine learning-based model must detect whether the subject of study has been infected or not.
Dataset I'll use :- https://www.kaggle.com/datasets/pranavraikokte/covid19-image-dataset
Solution I propose :-
1.) Using 5 different available network architectures such as Xception , DenseNet121 , VGG16 etc. to do catagorical classification for chest X-ray to detect COVID19 symptoms .
2.) use data augmentation techniques to improve the accuarcy of models.
3.) Comparing performance and accuracy of models using accuracy score ,loss and accuracy graph , confusion matrix for better understanding.
4.) Perfroming EDA (data analysis) for dataset to understand the structure of data.
5.) Using README file for describing the work I've performed.
Kindly assign this issue to me @Kushal997-das  and lable it as level-3 if possible as I'm training and testing dataset for 5 different models which is resource and time consuming and also making doucumentation about which works better > I will also be doing EDA analysis for the dataset.
I want to add this project in advance ml/data science repo
Add any other context or screenshots about the proposal request here.
No response

@Kushal997-das kindly assign this issue to me please.

@aaradhyasinghgaur, I'm assigning this to you, but please ensure that this project doesn't already exist in the repository.


Improve React Text Mask

@browniefed This is basically what you went through last night with some slight adjustments.
I eliminated textMaskState key and made it like it was before (things stored with setState). It works the same way. Just simpler.
I got rid of resetState. If the user wants to reset state they can do ref.maskedInput.setState(ref.maskedInput.getInitialState()).
Other than that, it's the same.
I tested it with controlled and uncontrolled. Seems to work with both.

Coolio 👍

@browniefed Updated! I'm not sure you're gonna like this, but it works perfectly! 😆
Also, I'm doing like you told me before, using key property to force a reset in the website.
And I removed the tests that you deleted in your branch.

Yes you are right, forceUpdate and assigning stuff in render? This all like SUPER anti-react haha.
This is all WAY too complicated, all to avoid a simple conformToMask call in getInitialState

https://github.com/msafi/text-mask/pull/61 is my proposition. We basically add one line in componentWillReceiveProps that sets the next conformed value. That's all

Decided to not do it this way.


Example code for framework7-vue swipeable tabs from official demo is not working

Framework7 version: [3.6.0]
Vue.js version: [2.5.17]
Platform and Target: [Android 8 Chrome browser]
Live Link: https://framework7.io/vue/tabs.html#swipeable-tabs

Describe the bug
The official demo of Swipeable Tabs for framework7-vue is not working. I copied exactly the same code from the example code and tested in my project, the swipe feature is really not working, neither on Android browser nor Google Chrome on my Mac. Please help to check the issue!
To Reproduce
Steps to reproduce the behavior:

Go to 'https://framework7.io/vue/tabs.html'
Scroll down to 'Swipeable Tabs' demo
Try to drag the screen of mobile simulator to the right or left, nothing happens.

Expected behavior
The content should be switched upon swiping.
Actual Behavior
Nothing happens.
Additional context
The demo from https://framework7.io/docs/tabs.html#swipeable-tabs works as expected.

After investigation, It seems swiper.$wrapperEl is now an empty list after bump from 3.5.2 to 3.6.
Which cause the window.getComputedStyle to crash.

@mmis1000 What can I do to fix the incorrect DOM generation? Or if I have to wait until next release?

You need to either wait for next release or use framework7-core directly(Which is error prone), i guess

@mmis1000 Thanks for your investigation, I just updated the title.

The required fix for this would be
Change this To
    const classes = Utils.classNames(className, Mixins.colorClasses(props), {
      'tabs-animated-wrap': animated,
      'tabs-swipeable-wrap': swipeable
    });

    const tabsClasses = Utils.classNames({
      'tabs': true,
      'tabs-routable': routable
    });

And it should give us the correct html structure

@mmis

@mmis1000 Tried just now, it works!


Remove shots

Remove shots from the coherence fitter

Summary
Details and comments

https://github.com/Qiskit/qiskit-ignis/issues/74


Fix typo in README

Hi there, interesting project! Found a typo while reading thru your README.
This PR fixes that typo, as there is no such thing as a most optimal solution. There is only one optimal solution.
Cheers!

Thanks!


Support for translation modules

Flutter apps typically segregate Intl.message calls in a class, roughly like this:
import 'package:intl/intl.dart';
import 'l10n/messages_all.dart';

class MyLocalizations {
  static Future<MyLocalizations> load(String localeName) async {
    await initializeMessages(localeName);
    Intl.defaultLocale = localeName;
    return new MyLocalizations();
  }

  String get title {
    return Intl.message(
      'Hello World',
      name: 'title',
      desc: 'Title for my application',
    );
  }
}

In a large app that's been factored into modules, this can be unwieldy because all of the app's Intl.message lookups must be included in a single class. It would be preferable to have one class like MyLocalizations for each module.
The generate_from_arb app would need an option that generated an initializeMessages() method for a specific module.
An Intl.message module parameter would make it possible for the intl package's message lookup logic to distinguish among modules. If the app's message names were globally unique, it would not be necessary to specify this parameter.

I'm assuming that the case here is that each individual component has its own messages and there's no sharing.
I think a reasonable approach for that would be something like the following.
messages_all.dart could include a class Intl which subclasses the regular Intl.
Users would not import intl.dart at all, or if they did, would hide the Intl class.
The version in messages_all.dart would do its own initialization which would return some kind of message lookup object or token. Intl.message calls made through that library would implicitly pass along the token. The biggest negative of this is that the user imports need to change - error detection if you do the wrong thing would be important. The other is that you have a large number of errors if you haven't generated the messages_all.dart file at all. Currently you just have an undefined initializeMessages. With this you'd have every reference to Intl as undefined. However, it's probably not unreasonable to require people to run the initialization step first.
I did a sketch of this, and it doesn't look like it would be too bad to implement, though I haven't done the actual lookup part yet.

Closing in favor of #9 .


Add Pagination to Ticket API

Implement pagination in the GET /api/Tickets route to limit results.

Kindly assign this issue to me.
I shall add a query parameter in /api/Tickets to limit the number of results fetched from DB and sent.
By mongoose's Query.limit(no) function, the required number of results can be fetched.

Hi @MadhavDhall,
the implementation looks good so far. In addition to this, we'll need to ensure that the response includes either a hasNext parameter or a totalPages parameter (or both, depending on your implementation), while implementing this one, please ensure that we do not query the entire database, to maintain efficiency.
it would also be helpful if we could add a new environment variable that controls the number of objects per page in the pagination. we'd be leaving the choice of nomenclature for the variable to you. please ensure that a default value is also hardcoded for objects per page in case the env var is not set, so we can maintain compatibility with old users.
if everything is clear, feel free to go ahead and open a PR.

Ok sir I am clear with the implementation
@AyushDharDubey kindly assign me the issue.


[red-knot] Narrowing - Not operator

Summary
After #13918 has landed, narrowing constraint negation became easy, so adding support for not operator.
Test Plan
I added a new mdtest file for not expression, but maybe we should spread it over the other test files (by adding not cases to each one of them)? I'll be happy to hear your preference around that :)

I added a new mdtest file for not expression, but maybe we should spread it over the other test files (by adding not cases to each one of them)? I'll be happy to hear your preference around that :)

I like what you've done here. I think in general any feature that makes sense to make a PR to add, probably makes sense to have a dedicated file to test as well. Which of course isn't incompatible with perhaps also having it occasionally show up in tests of other features, too, but not in a "must add it everywhere" way.


feat: vote delegation

Simple all-or-nothing vote delegation. Users may register a delegate who can act on their behalf until explicitly revoked. It does not do anything fancy and required only a minimal intervention so I think this is a good addition to the reference implementation.
Users can only register one delegate at a time. Delegation is directly linked, so one cannot make delegation chains. (Which I think is desirable, as the user never chose to elect the third party delegate.)
@radicleart consider it a preamble the delegation concepts you are working on.

I am thinking about ways in which we can make it so that the delegate does not have to send in a vote per delegatee. I created a "vote-many" equivalent but still do not like the amount of data to be posted. Perhaps a third sub token edg-token-delegated can solve it. Any suggestions welcome. I'm trying to keep the code succinct and clean.

For background there's a suggestion for such a mechanism here - Proposal 2: New EDG Delegation Tokens
Also feature/delegate-voting has an implementation that tracks the delegated portion of edg using maps.

@radicleart how about some sort of delegation mechanism for the reference repository?


Address 3 issues: baud rate change, flash reading, instantiation with port

This PR adds 3 changes that made the code usable in TeddyCloud, a toniebox server implementation.
Reading flash memory
the function read_flash() allows reading back the flash
Baud rate fix
changing the baud rate did not resynchronize properly. added sync and retries.
this way 921600 baud connection works always. before it worked 1 out of 30 connection attempts.
Instantiation using WebSerial port as well as Transport
simplify caller's code by directly using WebSerial port object if specified.
esploader = new ESPLoader({
  port: port,
  baudrate: 921600,
  romBaudrate: 115200
});

interesting failures...
ah i see. it is complaing due to formatting issues?
got it.

did update the code, but didn't run it yet in our project (https://github.com/toniebox-reverse-engineering/teddycloud)
will do the functional checks in 1-2 days

Thanks for the PR @g3gg0 looks great !
I've tested locally with esp32 wrover kit and works good. You can test the lint locally with npm run lint and after this will merge the PR.

Closing this PR since I merged with fixes in 04e337db44c5249016342b477a1827e6409fc31e

Thanks. Don't forget to tag the release on GitHub too.

I found a small bug in the type which I reported here https://github.com/espressif/esptool-js/commit/04e337db44c5249016342b477a1827e6409fc31e#r130045791


Update VMWare to VMware

Update VMWare to VMware
https://github.com/kubearmor/KubeArmor/blob/main/getting-started/support_matrix.md

/assign

Hello @ShubhamTatvamasi I would like to work on this issue can you please assign it to me

Hello @ShubhamTatvamasi I would like to work on this issue can you please assign it to me

Sure