Prevent local copies of DocTableInfo to return outdated partitions/indices

Summary of the changes / Why this improves CrateDB
Fixes the insert failure of https://github.com/crate/crate/issues/15880
Checklist

[ ] Added an entry in the latest docs/appendices/release-notes/<x.y.0>.rst for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in the latest docs/appendices/release-notes/<x.y.0>.rst
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Added 5.6 label as we have 5.6.5 opened


Store Assets Relative to Content (Bundles)

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Currently, the Media Library is a single folder where every image is dumped. This doesn't allow assets to be organized, managed, and deleted properly.
What is the expected behavior?
There is work going on to add subfolders (see #1046) and provide further improvements to the Media Library (see #1321).
But I think we should go a step further than that and allow assets to be stored relative to its content (it's been asked for in various comments to media library issues). The paradigm for such asset handling is different, but I belive it is a very reasonable way to organize the content.
The Hugo SSG has been moving more and more towards this way of organizing its content and calls this Page Bundles (see Hugo Content Management with Page Bundles and Content Organization).
content/
├── posts
│   ├── my-post-1
│   │   ├── index.md
│   │   └── post-image.jpg
│   ├── my-post-2
│   │   ├── index.md
│   │   └── post-image.jpg
│   ├── _index.md
│   └── overview-image.jpg

In this example, there are two page bundles, one for /posts/my-post-1 and one for /posts/my-post-2. They each have their own assets stored in the same folder.
Then there is also a bundle for the overview site for posts (Hugo calls it a Branch Bundle).
Reason for Bundles

Entire content for one page with its assets is stored in one folder. It is obvious which assets (images and also other resources) belong to a page.
SSG's generally determine output placement based on the location of source files. So, we can just reference assets with a simple relative path or just the filename instead of using /assets/some-unique-filename.jpg or /assets/some/duplicated/path/to/image.jpg.
The markdown content with relative images is rendered in the GitHub ui.
Content editors don't need to browse through lots of unrelated assets.
Assets can be optimized (sized/cropped) for its specific content.
Assets can safely be deleted if a page is deleted. In a central assets folder we are never sure if some image is still referenced by some content.
In my mind, images for a blog post are an integral part of the content. So, bundling it into one folder just makes sense.
Content is also portable: I can zip markdown and images together and they work independent from the entire website.
This might also improve an editorial workflow as the reviewer can focus on reviewing one folder containing everything related to the content.

Also see initial discussion in https://github.com/netlify/netlify-cms/issues/325.

+1

would love that to, i'm not yet using netlify cms but am considering it. as i'm managing my assets in an assets directory relative to the post it's not easy to migrate.
and by the, to prevent duplicate assets for internationalized content i'm also storing all language versions in the same directory having one shared assets folder
would love to use this structure with netlify cms 👍

Content editors don't need to browse through lots of unrelated assets

I would like to underline this. For people that uses Apps for markdown editing this is important. Usually these Apps can render images if they are in the same directory as .md file or with absolute path, which is not useful for later deployment. If the CMS supported this feature it means we can work on our posts in the same way from our local machines and from the CMS. ❤

I want this functionality and would like to lend a hand 😁

@arturogh that would be awesome - happy to support you in your efforts, too 👍🏼👍🏼
Sent with GitHawk

Great! This is a feature I'd really want too so I'd be happy to help in any way 😄

Do you guys have any design assets for Netlify CMS I could leverage? Someone working on the technical, backend side of this?
Also, a short 5-10 min chat would be great :).

Really sorry...I still want to work on this but life got crazy. I'd like to help with design and front end possibly at some point.

Any update on this, for me this feature is critical for any medium size site.

Probably our next priority after we finish OSS Docs (#2093).
Sent with GitHawk

Meant to add this after the last community meeting - here's the approach we discussed:

allow the collection slug to contain a slash
everything before the slash is processed as a directory name with variables

collections:
  - name: posts
    label: Posts
    create: true
    folder: content/posts
    slug: "{{title}}/index.md"
    fields:
      - { name: title, label: Title }
      - { name: body, label: Body, widget: markdown }

This approach only allows a single directory level to be created dynamically per entry, which should be sufficient.
Thoughts? Use cases this wouldn't work for?

I believe that would work for our use case on web.dev :)

@erquhart Awesome. Looking forward to that!
In your exampe you are using the {{title}} as a directory name. This is great as a default when a new post is created. But what happens when you later want to change the directory name (independently from the title)? Is there a way to do that in the CMS?
I'm asking this question because in a setup with bundles, the directory name is very important. One shouldn't customize the resulting slug via a slug entry in the frontmatter since SSGs will only apply that to the generated html file but not assets inside the directory. Thus all relative paths inside the markdown would fail.
Also, I wouldn't want to store the slug in the frontmatter anyways. This would be unnecessary duplication since that information is already in the directory or filename. And if you change one and not the other, things get very confusing in the repo.

Ah that's a good point. We often have posts whose title does not exactly
march their slugified directory name.
On Thu, Jun 20, 2019, 1:50 PM Marco Jakob<EMAIL_ADDRESS>wrote:

@erquhart https://github.com/erquhart Awesome. Looking forward to that!
In your exampe you are using the {{title}} as a directory name. This is
great as a default when a new post is created. But what happens when you
later want to change the directory name (independently from the title)? Is
there a way to do that in the CMS?
I'm asking this question because in a setup with bundles, the directory
name is very important. One shouldn't customize the resulting slug via a
slug entry in the frontmatter since SSGs will only apply that to the
generated html file but not assets inside the directory. Thus all relative
paths inside the markdown would fail.
Also, I wouldn't want to store the slug in the frontmatter anyways. This
would be unnecessary duplication since that information is already in the
directory or filename. And if you change one and not the other, things get
very confusing in the repo.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/netlify/netlify-cms/issues/1472?email_source=notifications&email_token=AAIEKDLUCQSFJGO3A3TQAYTP3PUPZA5CNFSM4FHSVJTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGSISA#issuecomment-504177736,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIEKDMZBIZPWBJAUCRCHYDP3PUPZANCNFSM4FHSVJTA
.

The requirement to change a slug after initial entry creation is of broader scope than this issue, covered under #445. Let me know if I missed what you were trying to communicate.

Yes, #445 should cover the case of changing the slug. We would just need to make sure that anything we do with sluggification must also work with folder names and not just with file names.

For sure, this issue will be addressed before that one 👍

This is looking fine to create folder per post as is a needed first step, so thank you @erquhart.
To make this really useful we want to use this folder for assets/images.
Can we add an image widget using that folder eg.
fields:
- label: "Featured Image"
  name: "thumbnail"
  widget: "image"
  config:
    media_folder: "."

(the media_folder property is at least not documented today so I guess it has to be developed)
What about medias in the body/markdown widget using the current folder. How can we achieve that?
Still, thank you for your work, I really like netlify-cms :)

@jballe initially you won't need to configure, we'll likely implement so that all images are stored with the entry you're editing, including those in markdown. Netlify CMS already has some internal asset proxying to facilitate this. We should have a switch on the media library for global vs. entry, but that will probably come later.

Super, @erquhart! I agree that if you want to create a folder per post then you probably also want to store assets in that folder. However I can imagine that for some fields I want to reference the global medias, but a candidate for a later step :+1:

I'm just checking in to see if there's been any movement on this?  Is it available yet to use?

This is the very next thing we're working on. Stay tuned.

Looking forward to hear more about this!

__yes!
--

a
http://dojo4.com/team/ara-t-howard
https://www.instagram.com/drawohara
i sometimes check email once or twice per week so if you're really after
me come by, call, or text.

On Thu, Sep 5, 2019 at 3:34 PM Shawn Erquhart<EMAIL_ADDRESS>wrote:

This is the very next thing we're working on. Stay tuned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/netlify/netlify-cms/issues/1472?email_source=notifications&email_token=AAABPTQDU5FH23WUIQRTUX3QIF3NJA5CNFSM4FHSVJTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6A4JMQ#issuecomment-528598194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABPTQOAXFAJEZ7VGFW673QIF3NJANCNFSM4FHSVJTA
.

Oh, I am looking forward for this one too, highly needed!

@mazdak78 Already in beta it seems https://www.netlifycms.org/docs/beta-features/#relative-image-paths 🎉

@mazdak78 Already in beta it seems https://www.netlifycms.org/docs/beta-features/#relative-image-paths 🎉

@CanRau : Oh, thanks, but I was mostly referring to feature about slug: "{{title}}/index.md" mentioned by @erquhart on Jun 19. :)

@erquhart Thank you for a super useful product! Question: are you guys working on the slug: "{{title}}/index.md" feature you mentioned on Jun 19, referred to by @mazdak78 above? If so, is there a rough ETA? -- I am getting started on a big project right now and we are making content organization decisions, and this feature would make it so much easier to have a cleaner set up!

@jimmyangel https://github.com/netlify/netlify-cms/issues/513

Meant to add this after the last community meeting - here's the approach we discussed:
* allow the collection `slug` to contain a slash

* everything before the slash is processed as a directory name with variables

collections:
  - name: posts
    label: Posts
    create: true
    folder: content/posts
    slug: "{{title}}/index.md"
    fields:
      - { name: title, label: Title }
      - { name: body, label: Body, widget: markdown }

This approach only allows a single directory level to be created dynamically per entry, which should be sufficient.
Thoughts? Use cases this wouldn't work for?

Hi @erquhart, do you have an ETA for this feature? Thanks.

What about images? Can they be stored in the same location, i.e., content/posts/{{title}}

Hi everyone !
Does anyone know if this feature is implemented? This is the only thing preventing us from using Netlify CMS in our project... and the documentation is not clear on what the option media_folder_relative: true allows to do.
Thanks for the help :)

It’s in progress, watch here for updates
Sent with GitHawk

Latest code on master branch (not published yet to beta) lets you do:
slug: 'index'
path: '{{title}}/{{slug}}'

to save a file under title/index.md for example.
Next step will be to store images with the content.

Thanks a ton for implementing this feature!

ficaria muito melhor mesmo para gerenciarmos as postagens

Hi, I think the doc could be updated right?

https://www.netlifycms.org/docs/gatsby/#get-to-know-gatsby

Good catch @Ir1d! removing that part will also require updating the config.yml yaml to support the starter directory structure. Do you mind opening an issue for that?

hi what would happen if title has space will the folder be created with spaces or hyphen?

@nidhi-wgl, sanitisation is still applied but only to template variables.

@erezrokah This is still listed under beta features in the docs. Is that the case or should this be moved to the permanent docs?

@erezrokah This is still listed under beta features in the docs. Is that the case or should this be moved to the permanent docs?

Yes we should. Opened a new issue to track this https://github.com/netlify/netlify-cms/issues/4608

Hi! Just found this issue. Is there any progress on uploading images to bundle paths?

Hi @BasixKOR this is supported via https://www.netlifycms.org/docs/beta-features/#folder-collections-media-and-public-folder


Bump PyO3 version and support Stable Rust

This commit updates retworkx to use the latest version of PyO3 which
enables support for compiling with stable rust (rustc >= 1.39). While
updating the PyO3 version supported this takes the opportunity to update
all the documentation and CI builds to rely on stable rust instead of
nightly. The nightly step was always an extra manual step that detracted
from the contribution process and prevented use in environments where
rustup wasn't allowed to be used.

This is on hold until rust-numpy releases it's new version which uses PyO3 0.11.0. Until rust numpy updates this won't work because there would be a version mismatch between the PyO3 API used by retworkx and rust-numpy

Once #90 and this merge that should be it for the 0.4.0  release.

Also before this merges I will push up a DNM test commit to verify the wheel builds still work with the new version of cibuidlwheel. I'm not expecting any issues, but we should verify it before release just to be sure.

Any possibility for switching to maturin for building too (instead of setuptools-rust)? https://github.com/PyO3/maturin
Maturin is under active development, while setuptools-rust seems stagnant.

Any possibility for switching to maturin for building too (instead of setuptools-rust)? https://github.com/PyO3/maturin
Maturin is under active development, while setuptools-rust seems stagnant.

@drewrisinger there aren't any current plans to switch. Was there a particular reason you were looking to switch over to maturin, or just that it is a more active project?
Back when we started retworkx maturin (then called pyo3-pack) was missing a lot of features, most importantly sdist support, so it wasn't viable. Those have been mostly addressed (although not completely) and the main advantage it really provides over setuptools-rust now is that it allows for building the python packages without having to create boilerplate config files in the repo. But, that work has already been done so there isn't really a reason to remove it. Also, in my experience having the setup.py and other files in repo ends up working in more environments (especially those with older pip versions).

@mtreinish thanks for the response. I was mostly just wondering for re-packaging this for NixOS. I have at least one or two examples of using maturin, and none with setuptools-rust due to its reliance on the Rust Nightly toolchain , though I think that is changing with the latest pyo3.
I have no objections, and that makes sense about the existing system working. 👍

Coverage increased (+0.01%) to 88.781% when pulling e6706bf8e81bdf3c01d1f6f6d6547f0d4c05849c on mtreinish:stable-rust into 9c4085fc9216c02fa87191a024960893f59fe965 on Qiskit:master.

Wheel builds all succeeded. The azure jobs which are macOS and windows have them in the artifacts store: https://dev.azure.com/qiskit-ci/retworkx/_build/results?buildId=16278&view=artifacts&type=publishedArtifacts (the travis jobs don't host anywhere). I'll revert the DNM test commit now and this should be good to merge.


Drop eventuals in favor of Tokio watch + timers for disputes

Subissue for #333
This is a larger refactor that will update multiple parts of the code.
I suggest you start with dispute manager which is the smallest Eventual in the code.
https://github.com/graphprotocol/indexer-rs/blob/main/common/src/attestations/dispute_manager.rs
After this, we can have more PRs for  attestation_signers, allocation and escrow_account.
Originally posted by @gusinacio in https://github.com/graphprotocol/indexer-rs/issues/333#issuecomment-2402390838

Hey @taslimmuhammed, I'm creating subissues for each of the eventuals

ok👍


The unicode format codes that require IRQL passive in dbgprint

The unicode format codes that is mentioned should be the following list:
(%C, %S, %lc, %ls, %wc, %ws, and %wZ). In this page, only two is mentioned.

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

ID: fdd9c906-0122-7c0f-e9bf-61021e1d8fde
Version Independent ID: 475e8ab8-c62a-91f3-831a-f0cfc46315a5
Content: DbgPrint function (wdm.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdm/nf-wdm-dbgprint.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @barrygolden
Microsoft Alias: bagold

@bradhodge - Thanks for this PR and I agree that the list was partial and not complete. I updated the topic to list out all of the unicode strings, which I think is a bit more clear. So thanks for filing this issue, and helping to improve the Windows developer docs.


DBZ-8393 ExtractNewRecordState transform: move processing of headers after envelope has been checked

This is to avoid NPE for non-envelope rerords.

@harveyyue @gunnarmorling @jpechane
There seems to be a change in the logic here since version 2.4.0, which causes a NPE when processing headers for non-envelope records.
My fix makes sure the headers get processed only after non-envelope records have been filtered out.

Strange, a test is failing in ona of the jobs:
ExtractNewDocumentStateTestIT.shouldFlattenTransformRecordForInsertEvent:1267 NullPointer Cannot invoke "java.util.List.size()" because the return value of "io.debezium.embedded.AbstractConnectorTest$SourceRecords.recordsForTopic(String)" is null
But it is passing locally in my dev env.. is this some flaky test that might pass if re-run?

@martinvlk I'll re-run it later to make sure.

Still failing. But honestly, I don't see how my fix could have affected this part of the code.

@martinvlk Could you please rabe on the latest main?
@vjuranek I noticed error in the log
2024-11-12T11:48:12.5835586Z java.lang.IllegalStateException: Cannot stop engine while tasks are starting, this may lead to leaked resource. Wait for the tasks to be fully started.
2024-11-12T11:48:12.5837435Z 	at io.debezium.embedded.async.AsyncEmbeddedEngine.close(AsyncEmbeddedEngine.java:246)
2024-11-12T11:48:12.5838968Z 	at io.debezium.embedded.async.TestingAsyncEmbeddedEngine.close(TestingAsyncEmbeddedEngine.java:34)
2024-11-12T11:48:12.5840576Z 	at io.debezium.embedded.AbstractConnectorTest.stopConnector(AbstractConnectorTest.java:167)
2024-11-12T11:48:12.5842108Z 	at io.debezium.embedded.AbstractConnectorTest.stopConnector(AbstractConnectorTest.java:152)
2024-11-12T11:48:12.5843726Z 	at io.debezium.connector.mongodb.AbstractMongoConnectorIT.afterEach(AbstractMongoConnectorIT.java:76)
2024-11-12T11:48:12.5845862Z 	at io.debezium.connector.mongodb.transforms.AbstractExtractNewDocumentStateTestIT.afterEach(AbstractExtractNewDocumentStateTestIT.java:88)
2024-11-12T11:48:12.5848899Z 	at io.debezium.connector.mongodb.transforms.AbstractExtractNewDocumentStateTestIT.restartConnectorWithoutEmittingTombstones(AbstractExtractNewDocumentStateTestIT.java:94)
2024-11-12T11:48:12.5851868Z 	at io.debezium.connector.mongodb.transforms.ExtractNewDocumentStateTestIT.shouldRewriteDeleteMessage(ExtractNewDocumentStateTestIT.java:1004)

is it possible that this relates to some of the test issues you fixed recently?

Merged the latest changes from main, let's see.

The check seem to be very flaky... can I do anything to help here?

@vjuranek I noticed error in the log
2024-11-12T11:48:12.5835586Z java.lang.IllegalStateException: Cannot stop engine while tasks are starting, this may lead to leaked resource. Wait for the tasks to be fully started.
2024-11-12T11:48:12.5837435Z 	at io.debezium.embedded.async.AsyncEmbeddedEngine.close(AsyncEmbeddedEngine.java:246)
2024-11-12T11:48:12.5838968Z 	at io.debezium.embedded.async.TestingAsyncEmbeddedEngine.close(TestingAsyncEmbeddedEngine.java:34)
2024-11-12T11:48:12.5840576Z 	at io.debezium.embedded.AbstractConnectorTest.stopConnector(AbstractConnectorTest.java:167)
2024-11-12T11:48:12.5842108Z 	at io.debezium.embedded.AbstractConnectorTest.stopConnector(AbstractConnectorTest.java:152)
2024-11-12T11:48:12.5843726Z 	at io.debezium.connector.mongodb.AbstractMongoConnectorIT.afterEach(AbstractMongoConnectorIT.java:76)
2024-11-12T11:48:12.5845862Z 	at io.debezium.connector.mongodb.transforms.AbstractExtractNewDocumentStateTestIT.afterEach(AbstractExtractNewDocumentStateTestIT.java:88)
2024-11-12T11:48:12.5848899Z 	at io.debezium.connector.mongodb.transforms.AbstractExtractNewDocumentStateTestIT.restartConnectorWithoutEmittingTombstones(AbstractExtractNewDocumentStateTestIT.java:94)
2024-11-12T11:48:12.5851868Z 	at io.debezium.connector.mongodb.transforms.ExtractNewDocumentStateTestIT.shouldRewriteDeleteMessage(ExtractNewDocumentStateTestIT.java:1004)

is it possible that this relates to some of the test issues you fixed recently?

yes, exactly this issues was fixed in DBZ-8397

Remaning test failures seem to be random unrelated failures, I re-run the jobs.
@martinvlk unfortunately yes, our testsuite is not that stable as we would like it to be, PRs to improve it would be always welcome:-)

Excellent, thanks!
Do you want me to do a cherrypick to the  release branch for 2.7.4, or you do that yourselves?
I assume 3.0.2 gets released from master?

@martinvlk And it is merged, thanks a lot! I'll try to apply it to 2.7 and only in case of the need of larger change I'll ask you for another PR.


PyArray2 into faer to simplify python interfaces to rust routines using faer

Currently my pyO3 bindings that call some rust routines that use faer look something like:
use numpy::{IntoPyArray, PyArray2, PyReadonlyArray2};
use pyo3::{exceptions::PyRuntimeError, pymodule, types::PyModule, PyResult, Python};
use faer::{prelude::*}
// ...

#[pymodule]
fn rust_lib<'py>(_py: Python<'py>, m: &'py PyModule)
    -> PyResult<()>
{
   #[pyfn(m)]
    fn rpca<'py>(py: Python<'py>, a_py: PyReadonlyArray2<'py, f64>, n_rank: usize, n_iters: usize, n_oversamples: usize)
        -> &'py PyArray2<f64>
    {
        let a_ndarray = a_py.as_array();
        let a_faer = a_ndarray.view().into_faer();
        // ... faer-rs math
        ndarray_result.into_pyarray(py)
    }
}

I'm unsure if I am using the best approach.
Desired Solution:
// ...

   #[pyfn(m)]
    fn rpca<'py>(py: Python<'py>, a_py: PyReadonlyArray2<'py, f64>, n_rank: usize, n_iters: usize, n_oversamples: usize)
        -> &'py PyArray2<f64>
    {
        let a_faer = a_py.into_faer();
        // ... faer-rs math
        faer_result.into_pyarray(py)
    }

I would be interested as well in something like this but I think it is something more to do with how this implemented in the crate used for type conversion from and to Numpy arrays.
As stated in the introduction to their docs this is something that has been somehow implemented for the nalgebra crate by implementing the ToPyArray trait. I guess something similar could probably be done for faer.


Rudimentary non-production distributed Python API

Functionality meant to validate that distributed execution with collectives is working correctly.
This should be thrown away if we have a proper implementation.

@sogartar I think there has been updates to TOM, could you rebase and push again?

@nithinsubbiah I change the PR target branch for the purpose of doing the code review without interruptions.


Increase characters slots amount to 30

Short description

Increase characters slots amount to 30
Why we need to add this

Because i ran out of slots and its pretty cheap
Media (Video/Screenshots)

Checks

[x] I do not require assistance to complete the PR.
[x] Before posting/requesting review of a PR, I have verified that the changes work.
[x] I have added screenshots/videos of the changes, or this PR does not change in-game mechanics.
[x] I affirm that my changes are licensed under the Starlight Fork License and grant permission for use in this repository under its conditions.

Changelog
:cl: Miracula

tweak: Increase characters slots amount to 30

it already 30

it already 30

yes, it is, and its not working

this pr fixes that


Make developers an admin on registration

Add this new variable to the hackathon variables file pls.

It already exists but I've set the default to [] if that's what you were looking for?

Also, note that being an admin doesn't make you an organizer immediately or a director.

Thanks! My intention here was to give developers the flexibility to modify their role manually (allowing them to test whatever) by using the admin panel.


Checkbox is Broken for Screen Reader Users

Description
When a screen reader, such as NVDA, arrows over the checbox, it says "Checkbox state blank". When tabbing to the checkbox, the screen reader says "blank".
This is due to the checkbox having role="presentation". Someone needs to urgently look at all the basic vaadin components, both button and checkbox are broken to the point of unusability for screen reader users.
Why not just use the native component and style it to be what it should be and just call it a day? Add the aria when needed, and leave the rest for the framework and browser to handle.
Expected outcome
Checkbox should be announced when it's arrowed over, without the blank at the end, and the label should be read. "Checkbox state label". When you tab, the same message should read.
Actual outcome
The screen reader adds a blank to the end of the message when arrowing, and says "blank" when tabbing. It also may say nothing wen tabbing or arrowing.
Live Demo
https://vaadin.com/components/vaadin-checkbox/html-examples
Steps to reproduce

Using NVDA 2020.2, visit the examples site
Hit "3" to jump to the "Basic Usage" heading.
Hit tab once. NVDA will not read anything. Sometimes NVDA does ignore the role=presentation, because it is getting too many conflicting commands, so that checkbox reads maybe 10% of the time. The next checkboxes under Basic usage with checkbox group never read. Just keep tabbing. Every single checkbox should read on the page.

Browsers Affected

[X] Chrome
[X] Firefox
[?] Safari
[X] Edge
[?] iOS Safari
[?] Android Chrome

Reminder to also check VoiceOver.


Wrong length of message on RT interface

Trying to use this package with the following setup:
Client machine: Ubuntu 14.04.4
ROS version: Indigo
Robot: UR10
URControl/Polyscope version: 3.2.19293
The output of running the driver is below:
$ roslaunch ur_modern_driver ur10_bringup.launch robot_ip:=<IP_ADDRESS>
... logging to /home/yamokosk/.ros/log/66a35286-0639-11e6-b7a3-989096c96b47/roslaunch-beast-6486.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://beast:38766/

SUMMARY
========

PARAMETERS
 * /robot_description: <?xml version="1....
 * /rosdistro: indigo
 * /rosversion: 1.11.16
 * /ur_driver/base_frame: base_link
 * /ur_driver/max_payload: 10.0
 * /ur_driver/max_velocity: 10.0
 * /ur_driver/min_payload: 0.0
 * /ur_driver/prefix:
 * /ur_driver/robot_ip_address: <IP_ADDRESS>
 * /ur_driver/servoj_time: 0.008
 * /ur_driver/tool_frame: tool0_controller

NODES
  /
    robot_state_publisher (robot_state_publisher/robot_state_publisher)
    ur_driver (ur_modern_driver/ur_driver)

ROS_MASTER_URI=http://<IP_ADDRESS>:11311

core service [/rosout] found
process[robot_state_publisher-1]: started with pid [6344]
process[ur_driver-2]: started with pid [6345]
[DEBUG] [1461090622.377862880]: Max velocity accepted by ur_driver: 10.000000 [rad/s]
[DEBUG] [1461090622.383396234]: Min payload set to: 0.000000 [kg]
[DEBUG] [1461090622.389380645]: Max payload set to: 10.000000 [kg]
[DEBUG] [1461090622.389424038]: Bounds for set_payload service calls: [0.000000, 10.000000]
[DEBUG] [1461090622.394952805]: Servoj_time set to: 0.008000 [sec]
[DEBUG] [1461090622.399890538]: Base frame set to: base_link
[DEBUG] [1461090622.407237390]: Tool frame set to: tool0_controller
[DEBUG] [1461090622.407281113]: Acquire firmware version: Connecting...
[DEBUG] [1461090622.410286155]: Acquire firmware version: Got connection
[DEBUG] [1461090622.926672201]: Firmware version detected: 3.2019293
[DEBUG] [1461090622.926762164]: Switching to secondary interface for masterboard data: Connecting...
[DEBUG] [1461090622.928908912]: Secondary interface: Got connection
[DEBUG] [1461090622.929007812]: Realtime port: Connecting...
[DEBUG] [1461090622.931536234]: Listening on <IP_ADDRESS>:50001

[DEBUG] [1461090622.931606611]: Realtime port: Got connection
[DEBUG] [1461090623.047969153]: The action server for this driver has been started
Wrong length of message on RT interface: -1077783229
Wrong length of message on RT interface: -1078231040
Wrong length of message on RT interface: 0
Wrong length of message on RT interface: -1077783229
Wrong length of message on RT interface: 0
^C[ur_driver-2] killing on exit
[robot_state_publisher-1] killing on exit
ur_driver: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' iled.
shutting down processing monitor...
... shutting down processing monitor complete
done

Looking at the code, I don't think this is a "3.2 version" (#17) problem as it looks like the code accounts for that version. Or maybe I am wrong?

False alarm. I guess there are simply a few corrupt packages flying around.


Patch the downloaded flatbuffer code to make compatible with TFLM.

See http://b/173239141 for more details.
The modified lines flexbuffers.h as a result of this patching are:
#if 1
          // TODO(b/173239141): Patched via micro/tools/make/flexbuffers_download.sh
          // Introduce a segfault for an unsupported code path for TFLM.
          return *(static_cast<double*>(nullptr));
#else
          // This is the original code
          double d;
          flatbuffers::StringToNumber(AsString().c_str(), &d);
          return d;
#endif

Once the current PR is merged, we should be able to revert https://github.com/tensorflow/tensorflow/pull/43566/commits/18ec320a50bb491e28d9a7f129fdc02ed50d0b3e and then merge https://github.com/tensorflow/tensorflow/pull/43566


synthetic.conf mount points not supported

Describe the bug
Create a symbolic link using /etc/synthetic.conf. For example:
# create a symbolic link named "baz" at / which points to "Users/me/baz"
baz	Users/me/baz

baz and Users/me/baz must be separated by a tab character and the host must be rebooted. Bind mount baz and list its contents:
docker run -it --rm -v /baz:/baz alpine ls /baz

Output:
mac       machines

To Reproduce
See above.
Expected behavior
List contents of baz.
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.7.0
Commit: c5439c5612cdb5febbbc69169a4f3b11cdada6c2 (v1.7.0)
System info:
macOS: 14.6.1 (23G93)
CPU: arm64, 8 cores
CPU model: Apple M1 Pro
Model: MacBookPro18,3
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-09-02T15-31-38.204902Z.zip

Screenshots and additional context (optional)
No response

Can't reproduce with baz	Users/me/baz. What's your real link location and target?


No listen scope cover replies to uploaded images in Slack

BotKit version: 0.5.5
Operating system version: N/A
I'm working with Botkit integrated with Slack, and I've noticed none of my triggers are firing when they happen in a conversation within an uploaded image.
Steps to reproduce:

Setup controller.hears on the scope 'ambient'.
Upload an image to a channel.
Reply to the image with something that should fire the trigger from step 1.

Is this a known issues? Is there an event I need to listen to in addition to this?
Thanks!

Tried adding file_comment_added as well, from slack's events list, no luck.

Hmm it might not be receiving the message as a normal message. It is likely
emitting a file_comment_added event.
Add a controller.on to check for that.
Not sure how file comments are threaded off the top of my head, it might be
a different api call to comment on a file, vs messaging a channel id.
On Mon, Jul 17, 2017 at 7:13 AM Tiago<EMAIL_ADDRESS>wrote:

Tried adding file_comment_added as well, from slack's events list, no luck.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/928#issuecomment-315727219, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMUR22p80vV6haXIDXrx1klyrU7L7astks5sO0HPgaJpZM4OZ1Ee
.

@jonchurch do you know where the listen-scope in botkit's controller.hears actually comes from? What do these kind of parameters match against, where in the framework? 'ambient,direct_message,direct_mention,mention'
I wonder if there's some kind of hardcoding that may be extendable to also allow reactions to file_comment_added events from slack, or if I explicitly have to leverage controller.on. Ideally I'd like to treat file comments similar to standard messages, in that matching controller.hears functions trigger in the scopes defined therein (e.g mention vs ambient).


Idea: Linting support for docker-compose.yml files

It would make it a lot simpler to author Dockerfile and docker-compose.yml files if you could view actionable linting errors from within VS Code. For example, Docker Compose includes JSON schema files for its various formats (e.g. v2.0) that document how to determine whether a compose file is valid or not.

I've investigated this and ultimately the conclusion I've reached is that without just straight-up copying the functionality of the YAML extension, I could not do as good of a job as they've already done. So rather than try to implement this, I'm going to close this issue, since with #122 it is now much more user-friendly to have both the YAML and Docker extensions' language services for compose working side-by-side.

Anyone on this ticket that needs this should be able to get something decent with Red Hat's YAML extension. You can use something like the following in your settings.json file.
{
"yaml.schemas": {
"https://raw.githubusercontent.com/docker/cli/master/cli/compose/schema/data/config_schema_v3.8.json": "docker-compose.yml"
}
}

there is no such file on GitHub so which file we should use now? or does any other extension support it?

I'm still able to access that file, what error do you see?

I am getting an error that could not load the file


VSCode 1.57 hangs on linux with a message "Select a language to get started. Start typing to dismiss, or don't show this again."

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.57
OS Version: Linux 4.1.12-<IP_ADDRESS>.el7uek.x86_64 #2 SMP x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:

Downloaded Visual Studio Code 1.57 tar file (.tar.gz 64 bit) from https://code.visualstudio.com/download
Extracted the tar: tar -xf
Used  bin/code binary

/gifPlease

Here's a screenshot

@SrikrishnanS you cannot click into the editor and start typing or use anything from the application?

Hi,
I encountered the same issue on Linux CentOS 7.4 64 bits.

Virtual machine VMWare
[team@localhost Documents]$ uname -r
3.10.0-693.el7.x86_64
I think this issue is easy to reproduce on a CentOS 7 VM.
In the past I had no problem installing VS Code on various Linux systems.
Best Regards.

The linux issue can be solved by running code --no-sandbox

Running "code" with --no-sandbox argument did not solved the problem, but as mentioned before, previous versions tagged "el7" are working correctly (i.e. keyboard responsive) on CentOS 7.

@SrikrishnanS you cannot click into the editor and start typing or use anything from the application?

Yes, I can't click or work with vscode.

Can you see if it still reproduces when disabling the GPU support in VSCode? You can do that by running VSCode from the command line like this: code --disable-gpu
If that helps, you can permanently configure this option via:

Command Palette search for "Configure Runtime Arguments"
Set disable-hardware-acceleration: true
Restart

--no-sandbox didn't work:
Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium.
--disable-gpu didn't work either, had no effect - window still frozen.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Past the earlier screen, but freezes with a different home screen now

Anything special about your setup? What Linux distro is this?

Hi @bpasero,
I installed your nightly insider builds as mentioned.
Running code-insiders --no-sandbox --verbose gave me the stack trace in attachment.
code_stack.txt

Thanks, this seems like the culprit:
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/share/code-insiders/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node)
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1185:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:982:32)
    at Module._load (internal/modules/cjs/loader.js:823:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12684)
    at Module.require (internal/modules/cjs/loader.js:1006:19)
    at v (/usr/share/code-insiders/resources/app/out/vs/loader.js:4:698)

I let Deepak continue the investigation, I think there maybe duplicates.

@bpasero @deepak1556
OS:  Linux 4.1.12-<IP_ADDRESS>.el7uek.x86_64 x86_64
System:  Red Hat Enterprise Linux Server release 7.4 (Maipo)
KDE:  4.14.8

Merging this to #115784
This is a known issue that versions higher that 1.52 don't work on RHEL 7 systems, there is workaround to install newer gcc toolchain mentioned in the linked issue until we work on a fix.

When will a fix be available?


Project proposal: <<please, update the title>>

Decision
Include
Justification
Good shit!
Repo URL
https://github.com/karol-brejna-i/test-actions
Alternative project name
karol-brejna-i/test-actions
What is the project type?
Collection
What is the project license?
Apache-2.0
Connect IQ Store URL
No response
Tested in the simulator?
No response
Tested on an actual device?
No response
Quality of the code?

[ ] Clean code
[X] Good README/docs

Description of the project
Booga Oooga
Additional info
none

🛒


Updated chacha20poly1305 to version 0.10

Hello! Did an update to latest chacha20poly1305 crate. Thanks for the great work and hope this is helpful!

This is great. Thank you!


not cool

I can’t find the details for donating, pls fix it (I have to pass all tests)

Specially for my biggest fans https://boosty.to/quicklybly


Datefield

Would love to have a nice date field option for mobile

Agreed! Will look into that this weekend...


notify_user_groups without owner still notifies owner group

I have a deploy-to-bitrise-io build step setup as follows to not send emails to the owner, but the owner is still getting build email notifications:
    -<EMAIL_ADDRESS>        inputs:
        - notify_user_groups: testers, developers, admins

Is this a bug, or do I have my config setup incorrectly?

The config seems to be good, we'll check what the issue can be. Thanks for reporting!

@lhildenST , are that emails build status emails or artifact generations email?
It looks like artifact generation emails (triggered by deploy-to-bitrise-io step) are sent to correct groups.
You can control build status emails on your app's settings page, but there you can not apply settings per groups...

@godrei The owner is receiving "Build [success] email"

this is a build status email and not triggered by this step. you can control this type of emails on app's settings page.

@godrei Makes sense, my misunderstanding.  Please remove the "bug" label on this issue then.  I will close.
Note: I just gave 3 votes to https://bitrise.uservoice.com/forums/235233-general/suggestions/11650665-allow-per-user-notification-settings.


Translate values in select

This is  a feature request.
Description
Can we add a meta "translation" to select input fields (equal to VueDatatable)?

You should pass the translated options from the backend / frontend.
Are you familiar with Enso's Enum class ?

Look into LaravelEnso\Helpers\app\Classes\Enum. and see the methods.
And then take a look at LaravelEnso\TutorialManager\app\Enums\Placement and it's use in TutorialForm

@mauthi, can we close this?

Thx, did not have time to take a look on it, but I think I can manage my needs with Enum.


Add failedImagesDirectory property on FBSnapshotTestController

Usecase:
We setup IMAGE_DIFF_DIR to be in our repo, so when any test fails on simulator we can find diff images in repo. But when you run tests on real device and it fails, device don't have write access to project folder.
Our solution:
Add ability to specify failedImageDirectory in runtime, so for real devices we can set it to some temporary folder.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Denis Bogomolov:x: ManWithBearDenis Bogomolov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Would be happy to merge this, however this suffers from the same issue I saw when I tried to do this in:
https://github.com/facebookarchive/ios-snapshot-test-case/pull/214
FBSnapshotTestController isn't exposed to FBSnapshotTestCase, so subclasses can't set this property.
As I mentioned in that issue, it is possible to do this but you have to refactor a decent amount of the library to make that setting like the reference images directory.

Hm. Maybe I missing something, but from my side it's not so bad:

We don't use FBSnapshotTestCase at all. Instead we have own abstraction around FBSnapshotTestController, so it's possible for us setup this property.
Easiest solution I see is to add - (void)setFailedImagesDirectory:(NSString*) path; to FBSnapshotTestCase, which has ability to pass new path to controller.

Right. If you don't use FBSnapshotTestCase, you can just make a FBSnapshotTestController and use it directly (we have a similar setup for Swift snapshot tests).
But in the case of this library, this doesn't make sense to merge unless people can use it.
I'm happy to do this though, because it's not just a case of exposing it via FBSnapshotTestCase as I mentioned in the other issue; it's actually a more widespread change to make.

Implemented in #44

Published in version 4.0.0.


Create 8.6 D-cut Branch

Application D-cut for MAS 8.6 is September 10th, which means that PAL should likely d-cut a week before then so that applications can perform a merge of a stable PAL before d-cut.

closed by the linked PR


Feature/api key field userprofile

Hey @nizyev and @brylie. Check this out. The main issue was #68 (explanation in the comment) in addition to #69.


How do I count the number of occurrence of a selected segment?

I'd like to count how many times does occur the element L11 in the provided document.
How do I do that? Is there a built-in method for it?
Thanks
ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*SM*4405197800*999999999*20111219*1747*2100*X*004010
ST*204*0001
B2**XXXX**9999955559**PP
B2A*04
L11*NONPRIMARY*OK
MS3*XXXX*B**M
NTE**FROZEN GOODS SET TO -10d F
N1*PF*XYZ CORP*9*9995555500000
N3*31875 SOLON RD
N4*SOLON*OH*44139
N7**NONE*********FF****5300
S5*1*CL*27800*L*2444*CA*1016*E
L11*9999001947*DO
L11*9999670098*CR
L11*9999001866*DO
L11*9999669887*CR

I don't think this is an "issue" of stupidedi.  You probably want to ask this question in places like Stackoverflow.
Anyway, to find occurrence, just use a String method scan
lines = IO.read('my_edi_file.txt', 'r')
lines.scan(/L11\*/).size    # this should yield 5

Yes, StateMachine#count should do what you want.
You'll need to be very precise about where the L11 segments are in the document. This is because in general, the same segment can be used in different contexts (within different loops, with different qualifier elements, etc) to mean different things.
In your example, it seems there are two places L11 can appear. Presumably they mean different things. Here's some code for illustration:
def count(isa)
  isa.iterate(:GS) do |gs|
    gs.iterate(:ST) do |st|
      pp ["ST->L11", st.count(:L11)] #=> in your example, 1

      st.iterate(:S5) do |s5|
        pp ["ST->S5->L11", s5.count(:L11)] #=> in your example, 4
      end
    end
  end
end

cursor = parser.first
while cursor.defined?
  cursor.tap do |isa|
    count(isa)
    cursor = isa.find(:ISA)
  end
end

Also, in an upcoming release, you will be able to access the tokenizer directly without having to parse the document. That will make it much easier to write something like this. On the other hand, the tokenizer is kind of low-level and doesn't know about data types, loops, tables, etc -- it's just presents a sequence of SegmentTok instances.
Regarding @lkfken's advice, that can work in some circumstances and fail in others. For instance, it could work if your files always have the same delimiters and the substring "L11*" never occurs where it isn't expected (like in another segment GS*L11*0~). But the danger is if those assumptions are wrong, you won't really know because there is no error detection.

Closing this but feel free to re-open if your question wasn't answered.


Crash when moving to the next chapter while reading a manga

Steps to reproduce

Read manga until the last page
Swipe to go to next chapter
Crashed

Expected behavior
Moving to the next chapter
Actual behavior
It crashed
Crash logs
neko_crash_logs.txt
Neko version
<IP_ADDRESS>
Android version
Android 12
Device
Redmi Note 9
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

2.12.10


I dont see any example for consuming the event once its published to eventhub and gets subscribed. Similar to EventGridPublisherClient , do we have EventGridSubcriberClient ?

I dont see any example for consuming the event once its published to eventhub and gets subscribed. Similar to EventGridPublisherClient , do we have EventGridSubcriberClient ?

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

ID: 4f8e9a64-2685-ab50-7477-bc9c643d02ae
Version Independent ID: f30a0808-9a94-9bb2-ca1b-b88b453d07de
Content: Azure Event Grid subscriptions through portal - Azure Event Grid
Content Source: articles/event-grid/subscribe-through-portal.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

@bhupendergiri
Thanks for your feedback! We will investigate and update as appropriate.

If you are looking for specific examples of how to consume events from eventhub,  then you will have to refer to the event hub documentation.
https://learn.microsoft.com/en-us/azure/event-grid/handler-event-hubs#event-hub
The above document talks about the schema and delivery property. If you need to know how to consume the event from eventhub then there are multiple ways to do it and eventhub documents calls it out.
Unfortunately there is no EventGridSubcriberClient available.

I have gone through the above documents already. I know there is no EventGridSubcriberClient  available and is not my need actually. I am looking for any sample code (java) whether its EventGridSubcriberClient or EventGridConsumerClient . I did see publisher client and it worked for me but unfortunately I dont see any Java EventGridConsumerClient which can read events from event Hub (type of subscription handler). Can you please advise on that part.

@bhupendergiri , Please refer to the Eventhub documentation below. You can use the Eventprocessorclient
https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-java-get-started-send#receive-events

I have gone through and its with StorageAccount? Is it necessary to have
storageAccount to consume events?. I dont think so. Can you please recheck.
Thanks & Regards
Bhupender Giri
On Mon, Dec 12, 2022 at 11:51 PM Mughundhan_R-MSFT @.***>
wrote:

@bhupendergiri https://github.com/bhupendergiri , Please refer to the
Eventhub documentation below. You can use the Eventprocessorclient
https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-java-get-started-send#receive-events
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/102544#issuecomment-1347745142,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOGOSUBJ3JRNGVLZ7FJSLDWM76GFANCNFSM6AAAAAASZZZKZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

You would need Storage account as it is used for checkpoints. If you dont have checkpoint store, there is a possibility of duplicate processing.

But when i read the docs, i can have any kind of event handlers ( based on
what is the subscription / type which can be Azure functions, event hub,
storage queues ) ??
https://learn.microsoft.com/en-us/azure/event-grid/event-handlers
Like I said earlier, I am able to publish the event using Event Grid Topic
endpoint. I have an event subscription with an end point as Event hub and
not the Storage queue. Now, I dont see any useful documentation to consume
this event back  ( i have subscribed using even hub endpoint)
Can you  please help and point to right documentation (in case I am missing
anything)
Thanks & Regards
Bhupender Giri
On Tue, Dec 13, 2022 at 12:06 AM Mughundhan_R-MSFT @.***>
wrote:

You would need Storage account as it is used for checkpoints. If you dont
have checkpoint store, there is a possibility of duplicate processing.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/102544#issuecomment-1347754015,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOGOSWX4BQQIGZR7SAGYFLWM7753ANCNFSM6AAAAAASZZZKZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

You can have any kind of event handler as a subscriber (Functions,webhook,eventhub). In your case, you need an Eventhub as an event handler. For eventhub, you will have to use the Eventprocessorclient to process the event. This Eventprocessorclient has a dependency on Storage account which is used as checkpoint store. So the subscriber is still Eventhub and not Storage account. Just that the Eventhub has a dependency on Storage account. Providing the same documentation again for reference  https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-java-get-started-send#receive-events

Thank you for the clarification. I will update once I try and see the
outcome
On Tue, Dec 13, 2022 at 1:14 AM Mughundhan_R-MSFT @.***>
wrote:

You can have any kind of event handler as a subscriber
(Functions,webhook,eventhub). In your case, you need an Eventhub as an
event handler. For eventhub, you will have to use the Eventprocessorclient
to process the event. This Eventprocessorclient has a dependency on Storage
account which is used as checkpoint store. So the subscriber is still
Eventhub and not Storage account. Just that the Eventhub has a dependency
on Storage account. Providing the same documentation again for reference
https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-java-get-started-send#receive-events
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/102544#issuecomment-1347800343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOGOSVR7RR4M3QH2MRNLA3WNAH2ZANCNFSM6AAAAAASZZZKZM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Thanks & Regards
Bhupender Giri


Modified RUN1 to load balance

Subroutine RUN1  of GEOS_CICE4ColumnPhysGridComp is modified to for load balancing similar to what was previously done for subroutine CICECORE in subroutine RUN2.

FWIW, these changes provide a slight speed up:
All runs are for 1 month with cas.
Ocean Model | NCPUS | mean wallclock time before update (number of simulations) | mean wallclock time after update (number of simulations)  |
MOM5            |   1440  |  145 min  (1) | 136 min (2) |
MOM6            |   1440  |  193 min  (3) | 196 min (1) |  **there was a variability of > 20 min in my runs before update.


Change "hover effect on Nav bar"

If we change hover effect on nav bar. like, when we hover on that icon than background of particular icon will gets change

I would like to work on this issue @QAZIMAAZARSHAD , Please assign me

@ankitmishra067 this issue is already open, see issue number https://github.com/QAZIMAAZARSHAD/Movie-Streaming-Website/issues/33.
Before opening any new issue please always make sure that no other similar issue is already open.


zypper command in README.rst is wrong

I noticed that the command to install py2pack in the README.rst is incorrect. On both Tumbleweed as well as Leap (15.2):
> sudo zypper install python-py2pack
[sudo] password for root:
Loading repository data...
Reading installed packages...
Package 'python-py2pack' not found.
Resolving package dependencies...
Nothing to do.

A simple search shows:
> zypper se py2pack
Loading repository data...
Reading installed packages...

S | Name               | Summary                                                                  | Type
--+--------------------+--------------------------------------------------------------------------+--------
  | python-py2pack-doc | Documentation for python-py2pack                                         | package
  | python36-py2pack   | Script for generating distribution packages from Python packages on PyPI | package
  | python38-py2pack   | Script for generating distribution packages from Python packages on PyPI | package
  | python39-py2pack   | Script for generating distribution packages from Python packages on PyPI | package

The file should give users the correct zypper command to install the package.

Just to give you the workaround, the correct package name is now python3-py2pack


feat: Implemented average pooling 2d.

The supported args cannot be tuple right now. This is WIP. Will extend
it to support tuple arguments.
Addresses: issue #160

Thank you. I will improve about arguments.

I support tuple arguments
https://github.com/pfnet-research/chainer-compiler/pull/163


jschardet license

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

Repro steps.

The log given by the failure.

Desired functionality.
The jschardet library that Angular CLI has a dependency on has an LGPL license. In my organization, libraries with LGPL licenses can't be used in production applications. As a result, when our application was scanned by cybersecurity, it failed.
It would be desirable for all Angular CLI libraries to have licenses that are less restrictive (for example, MIT).
Mention any other details that might be useful.

We do limit the licenses we use, and test for them in https://github.com/angular/angular-cli/blob/master/scripts/test-licenses.js. As far as I know jschardet is the only LGPL one we have.
If you can find way around that library that doesn't really change the CLI functionality I'm happy to review a PR.


Issue when I use table_to_sheet. I have: ERROR Error: Bad range (0): A1:A0

I'm using angular 6 and I'm trying to export my  to excel but when the code try to write the file my app present this error:  ERROR Error: Bad range (0): A1:A0
I'm using this line:
const ws: XLSX.WorkSheet=XLSX.utils.table_to_sheet(this.table.nativeElement);
But if I send a simple json with XLSX.utils.json_to_sheet my app works great. The trouble if that my JSON contains crude data.

I had exactly the same issue, follow the next steps, maybe could work.

Pay attention to div table wrapper, MUST to be:

 <mat-table>....</mat-table>

Then change
<mat-header-row *matHeaderRowDef ......>...</mat-header-row>

...

2.1 Then change the next row def
<mat-row *matRowDef...></mat-row>

PD: If you lost some styles add this:
 tr.mat-header-row, tr.mat-row {
   display: flex;
}
Hope this can help you.

@NicoleObando @geo-dev-cr can you share an example table triggering this issue?

Another:
https://stackoverflow.com/questions/50970632/how-to-export-excel-file-from-angular-material-5-mat-table-angular-material-tab/51157054
Changing from "mat-header-row" to "tr mat-header-row" breaks styles and formatting for me, even when the "display: flex" lines are added to the stylesheet.

For me it worked without changing the <mat-table to <table mat-table. My styling was the same after that using Angular 7.

It works for me but can anyone tell how to hide one of the columns to export.
In my table, there is also an edit button with this method edit section also added to an excel sheet.
Please Suggest.

Hi devs, I have found the solution by using the native angular components.
HTML
<mat-table #TABLE></mat-table>;
TS
@ViewChild('TABLE') table: any;
download()
this.table._elementRef.nativeElement
It is just the way to initialize our viewChild from ElementRef to any our DOM reference and then access the native element.
Based on: https://github.com/angular/material2/issues/3922#issuecomment-292137996
Hope it helps!

I'm using angular 5 and I'm trying to export my to excel but when the code try to write the file my app present this Error: Uncaught (in promise): Error: Bad range (0): A1:c4
i am using this line:=
XLSX.utils.book_append_sheet(wb, ws, ws_name);
XLSX.writeFile(wb, rajan+ '.xlsx');

Is there a way to make xslx able to interpret the Angular 5+ format (mat-table)?
Reverting to the old HTML table creates a lot of styling issues.

A) use the same underlying data source and lift to a worksheet using json_to_sheet
B) use nativeElement to extract the table DOM element and lift to a worksheet using table_to_sheet


[WIP] Don't require SLE11 media/repos anymore

Cloud 6 will be based on SLE12 so SLE11 media and repositories are
no longer needed.

@vuntz has already worked on this one https://github.com/crowbar/crowbar/pull/2125

oh. need to look at the current PRs before I start trying to fix things...

@toabctl anyways @vuntz  is on vacation now :( so maybe https://github.com/crowbar/crowbar/pull/2125 won't be updated...

@toabctl anyways @vuntz is on vacation now :( so maybe #2125 won't be updated...

@MaximilianMeister I closed #2125 in favor of this one. Reviews welcome :)

+1

LGTM codewise
is it tested?

@MaximilianMeister see jenkins log..


React error with child React Web Components

Warning: Attempted to synchronously unmount a root while React was already rendering. React cannot finish unmounting the root until the current render has completed, which may lead to a race condition.
This error occurs when I try to add a react web component as a child of another web component, and it does not matter if it's the same component or another one. for example, these both cause the error:

      <stepper-component title="Stepper Button-Child test">
        <button-element label="DEMO BUTTON"></button-element>
      </stepper-component>

      <stepper-component title="Stepper Self-Child test">
        <stepper-component title="Child Stepper"></stepper-component>
      </stepper-component>

I'm using React 18.2.0
NOTE: I did try to use slots, but there was no change in the behaviour, so in this example I am just using {children} in the react component

@zerico007 - thank you for the suggestion, however setting the shadow root on or off does not resolve the issue.
this appears to be an order of operations issue that has to do with rendering

hmm can you share the implementation details for your components so I can poke around?

and are you using slots?

@zerico007 - Using slots or not just helps with controlling the location of the content, if it were regular HTML that would be fine, but here I am illustrating the issue with a child web component.
I have modified the sandbox demo to illustrate the issue, note that the component should be rendered twice, once as a parent and once as a child.
https://codesandbox.io/s/example-mui-button-forked-z68inn?file=/public/index.html

this implementation won't work without using slots. see my implementation below.
https://codesandbox.io/s/example-mui-button-forked-wj5e0h

@zerico007 - very interesting.
I see now that I had the slot name wrong in my local test, and it is working after fixing that bit.
Can I ask why does a slot behave differently than children?
It is worth noting that though this does work, it is not ideal since it breaks regular DOM principals

children is a React principle. To get the same implementation with web components, the slot HTML tag has to be used. it is a native HTML tag that can also be used when creating templates in HMTL. It's also how Vue allows you to insert "children" into a component since Vue components are created using a template.

that is a very big deviation from W3C DOM spec, which is very important that this is clear for all that use this. I would suggest adding this near the top of the WIKI, along with including a working sandbox example.
see: https://www.w3schools.com/jsref/prop_element_children.asp
Thank you for all your help, I'm happy that there is a way around this limitation.

slots are a part of the web component technology suite and standard. you can access the children of a slot using slot.assignedNodes() or slot.assignedElements(). Creating a custom web component or a template that will render children, requires using slots. You can read more here

@zerico007 - oh thank you for that, I didn't know that it was part of the base web component spec, I thought it was a react thing. Learn something new every day. cheers!


Stuck in setup

So i installed uptime-kuma on my server and started it. When i did so, it showed me in the console "No user, need setup" so i went  to /setup on the website. I entered my credentials for the admin user and clicked on create. Now i am stuck on this screen, the create button is pale and i can't click it and nothing is happening

I got stuch here too.. @Kevin-Konradi  how did you able to solve this error

I didn't

@hkpanchani @Kevin-Konradi Are you guys using caprover to deploy?
Basically, I solved it allowing the use of websockets on my app.  Basically, I solved it allowing the use of websockets on my app. If you are using nginx as your webserver, you should add this to your location / {} config:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_http_version 1.1;

Hope it helps.

Are you running fine on Caprover? I'm getting responsetimes that are REALLY slow - 1300ms to the same datacanter, as opposed to 20ms from my home. Tried old versions and new and it's the same. I even added code you provided but no luck. From the VPS shell I get 200ms, from the Uptime Kuma container I get 200ms, but from within the Up[time Kuma panel I get 1300ms.


Consider using a single file-naming scheme and test grouping methodology

Currently, while browsing the test repository, i find it difficult to navigate to tests i expect to exist, and/or not to exist, as the file naming scheme (and test grouping) seems to be all over the place.
I think it'll be worth it (for organisational purposes) to organise files and scope tests such that someone new coming into the repository can find their way and discover related tests better.

Some current complaints and notes are that some files seem to inherit sytest's vague naming scheme (apidoc, federation, etc.), some simply document and test MSCs, and some restrict themselves to very narrow scopes (account_change_password_pushers_test.go)

Indeed, there is no consistent mandated way to name test files. There's a few constraints you need to consider:

Up until 12 days ago it was not possible to skip an individual test based on the homeserver, you had to skip an entire file using Go build tags. This is likely why there are some hyper-specific filenames as they are for certain failing tests.
Early in development I copied the sytest file naming scheme to more easily aid in test discovery: if you were comfortable with where tests were in sytest then you'd be comfortable in Complement too. This starts to fall apart when there are Complement-only tests.
MSCs in particular are optional which need to be opted in via build tags, so they have to be in their own file.
Directories are special due to the way the Complement test runner works (it just uses go test). Each directory is a package which is run concurrently by default by go test. Complement has some limitations (currently) around concurrent tests, in that you cannot current run multiple mock federation servers at once as it always binds to the same port: 8448 so running tests concurrently would get "port in use" errors. This is why there is a csapi directory which does not test federation at all, and then an "everything else" /tests directory. This isn't great but is something I am aware of.

From https://github.com/matrix-org/complement/pull/289;

As of this PR, it will now (in theory) be possible to scale out tests indefinitely as we no longer have any central point/resource which all tests rely on. This should make it possible to split /tests into more packages which make sense from a Matrix PoV.


'az devops team list' and 'az devops project list' throwing error

ps-demo is a project that i have deleted.  in fact, i've deleted and recreated it several times and have been messing with service principals/organizations/etc while learning how to automate my azure environment via the CLI.
Command Name
az devops team list Extension Name: azure-devops. Version: 0.8.0.
Errors:
:open_mouth:

TF200016: The following project does not exist: ps-demo. Verify that the name of the project is correct and that the project exists on the specified Azure DevOps Server.  Operation returned an invalid status code of 404.Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 326, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 384, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 375, in _run_job
    cmd_copy.exception_handler(ex)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/exception_handler.py", line 26, in azure_devops_exception_handler
    reraise(*sys.exc_info())
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 354, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 145, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/__init__.py", line 451, in default_command_handler
    return op(**command_args)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/team/team.py", line 63, in get_teams
    project=project)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 320, in resolve_instance_and_project
    detect=detect, organization=organization, project=project, project_required=project_required)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 301, in resolve_instance_project_and_repo
    git_info = get_vsts_info_from_current_remote_url()
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 352, in get_vsts_info_from_current_remote_url
    info = VstsGitUrlInfo(get_remote_url(VstsGitUrlInfo.is_vsts_url_candidate))
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/vsts_git_url_info.py", line 42, in __init__
    vsts_info = self.get_vsts_info(remote_url)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/dev/common/vsts_git_url_info.py", line 94, in get_vsts_info
    return GitClient.get_vsts_info_by_remote_url(uri, credentials=credentials)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/v5_0/git/git_client.py", line 33, in get_vsts_info_by_remote_url
    response = git_client._send_request(request, headers)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/client.py", line 51, in _send_request
    self._handle_error(request, response)
  File "/Users/buckfactor/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/client.py", line 253, in _handle_error
    status_code=response.status_code))
azext_devops.devops_sdk.exceptions.AzureDevOpsClientRequestError: TF200016: The following project does not exist: ps-demo. Verify that the name of the project is correct and that the project exists on the specified Azure DevOps Server.  Operation returned an invalid status code of 404.

To Reproduce:
Steps to reproduce the behavior. Note: Command arguments have been redacted.

az devops team list
or
az devops project list

Expected Behavior
a list of teams/projects.
Environment Summary
Darwin-18.5.0-x86_64-i386-64bit
Python 3.7.3
Shell: bash

azure-cli                         2.0.62 *

Extensions:
azure-devops                       0.8.0

Python location '/usr/local/Cellar/azure-cli/2.0.62/libexec/bin/python'
Extensions directory '/Users/buckfactor/.azure/cliextensions'

Python (Darwin) 3.7.3 (default, Mar 27 2019, 09:23:15)
[Clang 10.0.1 (clang-1<IP_ADDRESS>)]

Additional Context
i have been creating and deleting projects fairly often the last few days.  i imagine this is cached somewhere along the way where it shouldn't be?

@stlbucket : can you please run your command with --debug option and share the logs?
I suspect that you are running your commands from a git repo which is hosted in Azure DevOps and --detect option is sending the response to an incorrect organization..
--debug logs will contain the urls.
cc: @snankani

@stlbucket If you are still facing this issue, please help us with the debug logs so we can debug the issue.
Lets us know if what Gaurav suggested above was really the issue in your case (unexpected detect project and organization from git repository).

I am closing the issue as a case of mis-configuration.
If you feel the need of changing something to help improve the experience please share with us by filing a new issue.
Preferably in  our extension repo


[Darwin] Issue 26012 - MTRDevice should stream subscription reports

Fixes #26012
This PR makes the MTRDevice.mm's SubscriptionCallback reports attributes immediately without waiting for OnReportEnd.
This does mean that the MTRDeviceDelegate will be getting individual callbacks for each attribute and event, and so I have filed a separate issue for optimizing that part: https://github.com/project-chip/connectedhomeip/issues/29357

Fast-tracking platform-specific change with platform owner review.


Add some means for support.

If this application goes live customers will require a means of contacting support.

An email will do well.
Please hold until I figure where to put it.

Implemented


allow adding a RBD mirror to already deployed cluster

Add a tox scenario that adds a new RBD mirror node as a part of already
deployed Ceph cluster and deploys RBD mirror there.
Signed-off-by: Rishabh Dave<EMAIL_ADDRESS>

Testing this PR locally went fine for me; attaching the logs -
dev-centos-non_container-add_rbdmirrors-SUCCEEDED.log
dev-centos-container-add_rbdmirrors-SUCCEEDED.log

@guits
Should I go ahead and add "Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1677431" to the commit message? BZ #1677431 requests scale-up/down playbooks for MGR, RGW and RBD-Mirror which is too broad for a single PR.

jenkins test dev-centos-non_container-add_rbdmirrors

jenkins test dev-centos-non_container-add_rbdmirrors

jenkins test dev-centos-non_container-add_rbdmirrors

jenkins test dev-centos-container-add_rbdmirrors

jenkins test dev-centos-non_container-add_rbdmirrors

jenkins test dev-centos-non_container-add_rbdmirrors

jenkins test dev-centos-container-add_rbdmirrors

jenkins test pipeline

jenkins test dev-centos-container-all_daemons

ceph-ansible-prs-dev-centos-container-all_daemons

jenkins test dev-centos-container-all_daemons

jenkins test dev-centos-non_container-all_daemons

jenkins test dev-centos-container-all_daemons

jenkins test dev-ubuntu-non_container-all_daemons


Work in progress (wip): updating tests

[ ] Feature
[ ] Fix
[x] Enhancement

Brief

Migrated from npm to pnpm
Installed hardhat
Configured hardhat.config.ts
Added more scripts to package.json
Updated tests
Created a GitHub Action for testing

Description
This branch tries to improve the deployment and testing environment by setting and using hardhat and rewriting the tests.
Requirements :
:warning: Requires installing pnpm:
npm install pnpm

Then installing dependencies:
pnpm install

@mtoub is your intention to first adjust the dev framework before incorporating the diamond structure ?

@mtoub is your intention to first adjust the dev framework before incorporating the diamond structure ?

@guenoledc the idea is to integrate hardhat, refactor the testing code, and maybe discuss some improvement of this implementation to tackle the TODO's that you've mentioned in the solidity code. I suggest that we keep this base implementation in this repo as a reference and share the new Diamond-based so-bond implementation in another repo. We can then, use the same testing scripts for testing the so-bond implementation. What do you think?

@mtoub
I see. But can I challenge a bit
You need to rework all test scripts and therefore how do we secure that the new tests are good enough.
I was more thinking testing the diamond impl with the old testing scheme, then construct the hardhat refactoring.
As discussed with Zak, it would be good to be able to do a end to end test with our internal software with the Diamond impl.
But either way both stages should be done.
Your thoughts?

@mtoub I have been doing some reading on hardhat and I have found implication for us (CACIB) to use this framework because it implies significant adjustments in our software since we base our solution on the combined.json file generated by the solc --combined-json option. Hardhat does not seem to compile and generate this output format.
Of course we could have both at the same time (hardhat + pure solc compilations).
I have never used hardhat before so it is going to take me a bit of time to get used to it ... any suggestion to speed up the learning process ?

I look into the hardhat plugins and seems pretty simple to generate the desired combine.json file from the artifacts.
so I have created the following plugin. Need to test it in my conventional software though. But for information for now.

task("combined-json", "Generates a combined JSON file for all contracts", async (_, hre) => {
  console.log("Generating combined JSON file for all contracts...");
  const fqns = await hre.artifacts.getAllFullyQualifiedNames();

  if (fqns.length == 0) {
    console.log("No artifacts found. Please compile contracts first.");
    return;
  }

  // will receive an array of the different compiler versions used
  const versions: string[] = [];
  // will receive the JSON data for the combined.json file to be produced.
  // the structure of the file is:
  // - contracts:
  //  - <contract_fully_qualified_name>
  //    - abi
  //    - bin
  //    - bin-runtime
  // - version
  const combined: any = {contracts: {}};

  for (const fqn of fqns) {
    // skip the combined.json file itself
    if (fqn == ":combined") continue;
    // process the fqn of the smart contract compiled
    const bi = await hre.artifacts.getBuildInfo(fqn)
    if (bi && !versions.includes(bi.solcLongVersion)) {
      versions.push(bi.solcLongVersion);
    }
    const artifact = await hre.artifacts.readArtifact(fqn);
    combined.contracts[fqn] = {
      abi: artifact.abi,
      bin: artifact.bytecode == "0x" ? "" : artifact.bytecode,
      "bin-runtime": artifact.deployedBytecode == "0x" ? "" : artifact.deployedBytecode
    };
  }
  combined.version = versions.join(";");

  const fs = require("fs");
  const path = require("path");
  const location = path.join(hre.config.paths.artifacts, "combined.json");
  console.log("Generating", location)
  fs.writeFileSync(location, JSON.stringify(combined));
  console.log("Attention, other hardhat command may delete de combined.json file. Please, check it after running a command.");

})

@guenoledc I have adapted and added the combined-json task in to the hardhat.config.ts file:
task("combined-json", "Generates a combined JSON file for all contracts")
  .addParam("output", "The output file name for the combined JSON file")
  .setAction(async (taskArgs, hre) => {
    console.log("Generating combined JSON file for all contracts...");
    const fqns = await hre.artifacts.getAllFullyQualifiedNames();

    if (fqns.length == 0) {
      console.log("No artifacts found. Please compile contracts first.");
      return;
    }

    // will receive an array of the different compiler versions used
    const versions: string[] = []; //[taskArgs.version];
    // will receive the JSON data for the combined.json file to be produced.
    // the structure of the file is:
    // - contracts:
    //  - <contract_fully_qualified_name>
    //    - abi
    //    - bin
    //    - bin-runtime
    // - version
    const combined: any = { contracts: {} };

    for (const fqn of fqns) {
      // skip the combined.json file itself
      if (fqn == ":combined") continue;
      // process the fqn of the smart contract compiled
      const bi = await hre.artifacts.getBuildInfo(fqn);
      if (bi && !versions.includes(bi.solcLongVersion)) {
        versions.push(bi.solcLongVersion);
      }
      const artifact = await hre.artifacts.readArtifact(fqn);
      combined.contracts[fqn] = {
        abi: artifact.abi,
        bin: stripHexPrefix(artifact.bytecode),
        "bin-runtime": stripHexPrefix(artifact.deployedBytecode),
      };
    }
    combined.version = versions.join(";");

    const fs = require("fs");
    const path = require("path");
    // use the output file name provided as a parameter
    const location = path.join(process.cwd(), taskArgs.output);
    console.log("Generating", location);
    fs.writeFileSync(location, JSON.stringify(combined), { flag: "w" });
    console.log(
      "Attention, other hardhat command may delete de combined.json file. Please, check it after running a command.",
    );
  });

I had to remove the 0x from the bin and bin-runtime to match the solc --combined-json format. I have also added an output parameter to specify where the hardhat generated combined.json file is stored to avoid overwriting the solc one.
I have ran the hardhat combined-json against solc --combined-json (check scripts in package.json), the results are stored in contract-artifacts/hardhat/combined.json and contract-artifacts/solc/combined.json, respectively.
I used the linux diff command to check the difference between the two files and stored that in combined-diff.txt (N.B. prettier should be used to format the json files before running the diff command). It seems that both files have the same structure and produce the same abis, the only differences are the bytecodes which due the compiler and optimizer configuration in both solc and hardhat. I'll try to match the solidity versions and optimizer options to make the two files match.

Thanks
It would be good to match the bytecode indeed because I tested the last compilation on the previous tests and it failed. I didn't yet had time to identify why it failed.

Hi @mtoub ,
So, I have resolved the original testing . it was coming from all the register.grantXXXRole that now consumes 116k gas instead of less than 100k gas before.  This is probably because of the use of AccessControlEnumerable.sol instead of AccessControl.sol. Not a big deal then.
So, now I feal we should try to replicate the so-bonds implementation with your Diamond impl. What do you think?
If we merge this branch we will replace the unit testing that are not completed yet with hardhat.

@mtoub I have merged your pull request into this branch.
I think we can manage to keep both tests. For the remaining test I'll try finishing them tonight.
As per the diamond implementation I'll keep pushing to finalize it so that we can test it ASAP.

@mtoub , I think it is a good idea to keep both tests set for the moment.
I will make a proposal to have both without making it too messy in the folders

@guenoledc Great, I guess we can just create subfolders test/solc and test/hardhat same as we did with the contracts-artifacts. We'll see if we can keep some common utils function shared between the two.

@mtoub
I wonder whether we should have 3 different repos.

One to keep the current impl
One with both tests solutions and
One repo for the diamond impl.

This way the various impl can be tested with any test solution
Of course this is a multi repo approach and one can prefer a mono repo approach with sub folders.
Do you have a preference ?

Merging into a side branch to import into the refactoring branch

@mtoub
I wonder whether we should have 3 different repos.

One to keep the current impl
One with both tests solutions and
One repo for the diamond impl.

This way the various impl can be tested with any test solution
Of course this is a multi repo approach and one can prefer a mono repo approach with sub folders.
Do you have a preference ?

@guenoledc having a monorepo doesn't sound do bad actually, that way we'll have everything in one place instead of confusing people and having the code scattered over multiple repos.
@ymaghzaz do you think Turborepo can do the trick?

@mtoub @ymaghzaz
I have started to refacto into a mono repo
When I have a 1st working setup i'll explain


Pagination#canAdvance and Pagination#canBack always true

Is there an existing issue for this?

[X] I have searched the existing issues

🐛 Describe the bug
Hello I have an Kotlin extension function looking like this:
    @JvmStatic
    fun RenderContext.pagination(state: State<Pagination>, fallBack: ViewItems = ViewItems.MENU_PLACEHOLDER) {

        "NP".forEach { layoutSlot(it, fallBack.get()) }

        layoutSlot('N', ViewItems.NEXT_PAGE.get()).displayIf { c -> state.get(c).canAdvance() }
            .updateOnStateChange(state)
            .onClick { context ->
                val pagination = state.get(context)
                pagination.advance()
                CustomSounds.MENU_CLICK.playSound(this.player)
            }
        layoutSlot('P').displayIf { c -> state.get(c).canBack() }
            .updateOnStateChange(state)
            .onClick { context ->
                val pagination = state.get(context)
                pagination.back()
                CustomSounds.MENU_CLICK.playSound(this.player)
            }
    }

It adds next and Previous buttons to a layout, my issue is here that they are always added, no matter of there is just 1 or 50 Items in the Pennington.
This Problem only exists with all computedPagintons
✔ Expected behavior
Well, that the items are not displayed if there is no next or previous site.
👣 Steps to Reproduce
No response
💻 Platform

[X] Bukkit
[ ] Sponge
[ ] Other

⭐ Server Version
Paper version 1.21.1-122-master@4430e96 (2024-10-12T21:18:42Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
📚 Library Version
3.0.11
✍ Additional context
No response

Do it this way until this is fixed:
render.layoutSlot('<', back)
. updateOnStateChange(paginationState)
.displayIf(() -> pagination.currentPageIndex() != 0)
.onClick(pagination::back);
render.layoutSlot('>', next)
. updateOnStateChange(paginationState)
.displayIf(() -> pagination.currentPageIndex() < pagination.lastPageIndex())
.onClick(pagination::advance);


New PSR update

https://www.coingecko.com/api  (include some of these)
More medians
-nonCrypto prices (e.g. interest Rates, s&p 500, etc.)

Also update GDAX feed to Coinbase Pro as it's currently results in a redirect.


[WIP]: Highlevel tutorial for beginner

This is a high-level tutorial for beginners. The notebook aims at providing a tour of Qcodes in a succinct manner. The idea is to briefly walk through all the important concept and provide links to other documents/example notebooks for the details.
To do:

[ ] Write section on 'Monitor'. Umit please take care of this as I have no knowledge on this part.  @gatebuilder
[ ] Put more details on parameter section. Quickly refer to different kind of parameters and provides links to example notebook.
[ ] Beautify the figure, once the review is received.
[ ] Link the example notebook in the docs. Currently, it is not linked to the Qcodes documentation.

@mention one core developer
Sorry, the commit history does not make any sense.
@gatebuilder
@WilliamHPNielsen
@astafan8
@jenshnielsen
@Dominik-Vogel

This is a great start :) I left a few small suggestions here and there.


Extension fields missing from GIMBAL_DEVICE_ATTITUDE_STATUS_DATA

On both 0.12.1 and 0.13.1, I do not get access to the fields gimbal_device_id or camera_device_id which are extension fields, even when using the emit-extensions feature.

There was a bug in 0.13.x that the feature was not properly set on the mavlink-bindgen crate when using the mavlink crate. This was fixed with #248 and it should work now on master. You will have to use a git dependency for now until it gets released to crates.io.
Unsure why it doesn't work for 0.12.

Nevermind.
This currently depends on an older version of the MAVLink message definitions that do not have that extension field yet. Therefore it does not get generated.
https://github.com/mavlink/mavlink/blob/d6d86d3f0c90a67c275d6833931f7c712b858dba/message_definitions/v1.0/common.xml#L7013

Alright, closing since already fixed then


BUG set BUILD env var

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] 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.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

cc @isuruf

@conda-forge-admin, rerender

ok @isuruf - this should be ready to merge!


The meaning of command

$ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program […params…]
$ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program @@
I wonder what […params…] and @@ mean. Isn't input in testcase_dir? I can't understand what inputs from stdin and files mean.

I suppose you read this in https://github.com/google/AFL/blob/master/README.md#6-fuzzing-binaries
The [..params..] is a placeholder to describe how programs are usually invoked. Let's say you want to fuzz sha1sum program. You'd typically use it as sha1sum <path_to_file_to_calculate_hash_for>, or you may use additional options of that program, e.g. sha1sum -z <path_to_file_to_calculate_hash_for>. So, either only <path_to_file_to_calculate_hash_for> or a sequence of multiple parameters such as -z <path_to_file_to_calculate_hash_for> would be the [..params..] part.
If you want to fuzz sha1sum program by passing testcases as files, you'd need to invoke AFL with the following command line sha1sum -z @@. That way, AFL will replace @@ with a path to a fuzzing testcases it generated for the target program.


It doesn't seem to be explained anywhere in the doc.
Thanks.

Hi @1093919186. ScikitJS does not have implemented neural network, I guess.
For saving and loading a trained "transformer" you can use toJson() and fromJson() methods.
`
// Initialize One-Hot-Encoder (whatever)
let OHE = new scikitjs.OneHotEncoder();
// Fit stage
OHE.fit(yourData);
// Save
let savedOHE = OHE.toJson()
// ...
// Your amazing code
// ...
// Load stage
// First initialize a new OHE
let newOHE = new scikitjs.OneHotEncoder();
// Then use .fromJson() method
newOHE  = newOHE.fromJson(savedOHE);
`

Hi Alvgoro, I’m grateful for your sharing. By learning the source code, I have found this implementation method. There is another issue here issue, do you have a solution?
Thanks again.


Tilemaps are broken in GWT

http://libgdx.badlogicgames.com:8080/job/demo-superjumper/808/console

Yep. :(
People always forget to add new classes to the GWT module.


Add type annotation to new regrid code

Addresses #1457
Description:
This PR is to address one of requirements in issue #1457: update docstrings to use type annotation format. Tom@tgtg did most of the work for this PR a while ago, and I added some latest changes.
I used " mypy --follow-import=skip  --ignore-missing-imports  ./improver/regrid/*.py", and there remain some errors. I checked one by one, and these errors are not real problems. They should be able to skip using (#type ignore), but I did not do that way so that reviewer can double-check them.
There is another change in this branch: simplify the ecef_coords function in idw.py. It has no impact to the results as both unit test and acceptance passed OK.
Testing:

[Y] Ran tests and they passed OK

CLA

[ ] If a new developer, signed up to CLA

@dmentipl  I have fixed sphinx/flake8-related issues in PR #1510. As you suggested,  I removed "#type ignore" which was added for skipping the mypy-reported errors, and so the mypy errors remain. Would you please review this PR? Thanks, Julian

Hi Daniel, @dmentipl   Thank you very much for reviewing this PR. The guidance information you attached is very useful. I have followed your suggestions and made changes accordingly.
kind regards, Julian

@dmentipl  Thank you for raising new issues. I fixed them yesterday, and pushed the commit (0972043). Somehow, it did not turn up in github.  I did a bit change and push another commit (Tom suggested). Both commits turn up now. kind regards, Julian


Allow downstream code to choose between running from RAM or Flash

This commit parameterizes the linker script to use the memory region
TARGET. This region can be defined in a downstream memory.x as follows:
MEMORY { ... }
REGION_ALIAS("TARGET", FLASH); /* or RAM */

Apart from RAM and FLASH, other memory regions could be used, e.g. in order to produce a bootloader. Because the entire process is orchestrated by the downstream crate's build.rs, it can be adjusted programmatically, without rebuilding any of the dependencies.

It is unfortunately not possible to undefine or redefine a region alias, so tutorials, etc, will have to be changed.

Thanks for the PR, @whitequark.

in order to produce a bootloader.

I'd love to support such setups with cortex-m-rt. But I'd like to see sketched
out how a bootloader would hook to this before landing this PR. I'm not familiar
with bootloader internals but the simplest way I can think of how it would work
is this:

Bootloader boots from Flash in the normal way.
set VTOR to 0x2000_0000
call the entry point of the program loaded in RAM. So something like
(0x2000_0004 as fn() -> !)()

But then I don't see how the program loaded in RAM would respect the 'initial
value for the stack pointer' stored in 0x2000_0000.
Then there's the question of whether this is flexible enough to support existing
bootloaders like the stm32 one.
And if there are only two options for the REGION_ALIAS argument (FLASH and
RAM) there perhaps this could be just a Cargo feature to switch between those
two.

It is unfortunately not possible to undefine or redefine a region alias, so tutorials, etc, will have to be changed.

This seems fine since we have semver and documentation. Blog posts should pin to specific versions for reproducibility in any case.

I'd love to support such setups with cortex-m-rt. But I'd like to see sketched
out how a bootloader would hook to this before landing this PR.

I want to mention that bootloaders are not the main motivation for this PR. Mostly, I did it for debugging (I wasn't sure if it was openocd that's broken or flashing), and because from prior experience with stlink v1, flashing could take a long time, whereas loading to RAM was always extremely quick (this is not true on TM4C, but I imagine some STM32 users would be happier).
Anyway...

But then I don't see how the program loaded in RAM would respect the 'initial
value for the stack pointer' stored in 0x2000_0000.

... the bootloader could simply use a two-instruction trampoline that sets SP and PC. We could provide it as a part of cortex_m::asm, for that matter.

And if there are only two options for the REGION_ALIAS argument (FLASH and
RAM) there perhaps this could be just a Cargo feature to switch between those
two.

I have initially thought about such design, and eventually opted against it. Here are my reasons:

The build process becomes quite a bit more complicated. The cortex-m-rt linker script is hardcoded in the .cargo/config of the downstream crate. Changing to change the build configuration is highly undesirable as it is effortful to do right and it causes a rebuild of every dependency. So, we have to, instead of copying link.x as it is, adjust it in the build script. This makes cortex-m-rt harder to understand.
The features are not a particularly good mechanism to express this. If we have two features, ram and flash, then half of the possible combinations is meaningless.
Most importantly, there's no reason there should be just two memory areas. The uC you've mentioned in the quickstart post has two RAM areas; I know there are uCs that have discontiguous flash; even on uCs with contiguous flash, it is a perfectly valid desire to split it manually, such as to add a bootloader or selectable firmware.

My REGION_ALIAS method has none of the issues above and requires only minimal changes to cortex-m-rt.

Then there's the question of whether this is flexible enough to support existing
bootloaders like the stm32 one.

I'm not sure what you are referring to.

... the bootloader could simply use a two-instruction trampoline that sets SP and PC.

With just that changes to the vector table in the source wouldn't carry over, right? The uC would still be using the vector table at 0x0 / Flash.

The cortex-m-rt linker script is hardcoded in the .cargo/config of the downstream crate.

This is not entirely correct. .cargo/config must always be in the top crate / Cargo configuration. (Cargo ignores the .cargo/config of dependencies). The linker script name is hardcoded to link.x if you are using cortex-m-rt so there's no need to ever change the linker script settings in .cargo/config.

Changing to change the build configuration is highly undesirable as it is effortful to do right and it causes a rebuild of every dependency.

I don't see how it would cause a full rebuild. cortex-m-rt can always be used as a direct dependency of the application crate and that's how I think it should be used (but I can't foresee all the possible use cases). In that case, changing a Cargo feature in cortex-m-rt only causes that crate to be rebuilt, not the entire dependency graph.

The features are not a particularly good mechanism to express this.

I was thinking of just a single feature then we'd have two possibilities.

Most importantly, there's no reason there should be just two memory areas

I know.

I know there are uCs that have discontiguous flash; even on uCs with contiguous flash, it is a perfectly valid desire to split it manually, such as to add a bootloader or selectable firmware.

Which is why it'd like to see such use cases sketched out to make sure the changes proposed here support those use cases.
So, in my mind, we either make the linker script flexible enough to support elaborated memory layouts or we just support a few simpler memory layouts (what we have right now for deploys, and everything on RAM for development) and tell users how to plug their own linker script for more elaborated setups ("disable the 'linker-script' feature in cortex-m-rt, use this build script that copies link.x over, start from this link.x file)

With just that changes to the vector table in the source wouldn't carry over, right? The uC would still be using the vector table at 0x0 / Flash.

Sure, you've mentioned updating VTOR already which is why I did not repeat it.

This is not entirely correct. .cargo/config must always be in the top crate / Cargo configuration.

Yeah, that's what I meant by "downstream crate", bad phrasing.
Anyway. I would still like to have this ability, but I cannot justify the effort to make this PR much more generic, and I do not like the Cargo feature suggestion enough to work on it, so I am going to close it for now.