Power Virtual Agents - Per User license not available in Admin portal

In 'power-virtual-agents/requirements-licensing.md',
under section 'Buy tenant and per user licenses', it says
'Search for and select the subscriptions you want to purchase'.
However, the Admin portal 'store' doesn't have the license mentioned later as 'Power Virtual Agents user license'. Only the tenant license is available.

Hi, you will need to use the non-preview version of the admin portal. I've updated the documentation accordingly.


discussing rule AEM-20 "ResourceResolver can be closed using try-with-resources"

I think that the current implementation displays quite a lot of false positives, which diminish the value of this rule right now.
Look at this example (https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/4b3da3f5fdf0b59049b966bea9306d24c87d0293/bundle/src/main/java/com/adobe/acs/commons/audit_log_search/impl/AuditLogSearchServlet.java#L64)
protected final void doGet(SlingHttpServletRequest request, SlingHttpServletResponse response)
            throws ServletException, IOException {
[...]
ResourceResolver resolver = request.getResourceResolver();
[...]

This line is pointed out with this rule.
But actually it does not apply here, as this is a simple assignment, and no ResourecResolver has been opened here. When you close the RR as suggested (by whatever means) you are doing wrong. Because you did not open the RR here, but you just did an assignment to a local variable.
This rule as it is today is not helpful, because blindly following the rules will cause developers to introduce functional issues in their code.
Instead only methods, which clearly open a new RR should be considered. Given the number of patterns out there, which are used for it, the rules are likely to get much more complex. Consider these patterns:
ResourceResolver rr = resourceResolverFactory.login[...];

and
ResourceResolver rr = HelperService.getNewResourceResolver();

and
ResourceResolver getNewResourceResolver() {
  [...]
  ResourceResolver rr = resourceResolverFactory.login[...]
  return rr;
}

I would be great if you could point any issue clearly; even if that means, that we cannot detect all possible situations where a RR will remains unclosed.

Hi @joerghoh, I agree that the rule is somewhat troublesome for a number of reasons, some of which I've described in https://github.com/Cognifide/AEM-Rules-for-SonarQube/issues/188
I'm of a mind to get rid of it. If other rules pertaining to Autocloseable resources fail to pick up Sling-specific examples, we can revisit bringing the rule back and make sure to use the examples you provided as unit tests to avoid false positives arising.


Done: Add a ruler

🚀 Feature
Add a ruler to measure distance in world space.

Motivation
There were a lot of requests to implement this and I said that I can do this in the community meeting. For me, this is also useful in napari. Now, there is a working implementation :smiley: and I want to share my design suggestion.
@tlambert03, @sofroniewn

Pitch
The ruler lives on the scale bar overlay. I use the interaction box overlay and transform the scale bar in the world space in order to measure the distances there. Now, the interaction box is no longer only correlated with the active layer, but can also be correlated with overlay objects like the scale bar, how I did it. The ruler can be activated when the scale bar is activated and a key is pressed.
See the attached video.
https://user-images.githubusercontent.com/83079938/156732507-bfc39a2c-e281-4285-813f-7ce7e76aa1b6.mp4

Alternatives

Additional context

Love it!
❤

Wow this is so cool @MBPhys!! I like how you're re-using the scale bar. I wonder though would people ever like multiple rulers? Or would people ever like to have both a ruler and a scale bar? I'm not sure. I think this is a fine place to start, but very curious what others think, cc @napari/core-devs? I think a PR would be great though - this will be very useful for a lot of folks!!

I agree that a ruler would be amazing, but I don't think resizing and rotating the scalebar is a good approach. I'm sure what everyone really wants is to be able to click and drag from x to y and get the distance, without having to fight with handles and stuff. I would instead suggest to reuse the measurement logic from the scale bar, but recreate a new overlay.
Also, a reminder that there were attempts like #3763 to unify overlays as things that live in canvas space, and a changes like this are going against that. That's not a problem per se (happy to drop that idea if this makes more sense!), I just wanted to connect the discussions :)
Another thing worth thiking about is a ruler in 3D that lives in scene space (cc @kevinyamauchi @alisterburt).

I'm sure what everyone really wants is to be able to click and drag from x to y and get the distance, without having to fight with handles and stuff. I would instead suggest to reuse the measurement logic from the scale bar, but recreate a new overlay.

Good point, click and drag would be good to have too - maybe nice to also allow resizing afterwards, so maybe best to have the ruler be its own overlay and have both click and drag and an interaction box. Regardless, it would be nice to pick up #3763 again and get that merge

If I had my druthers this would be part of Shapes layer tools--more intuitive for me anyways. A ruler icon as an option on the line? Could indicate with a corner like Adobe tools.

wow! super cool @MBPhys :)
I think overall I agree with @brisvag, I would prefer if this was a separate entity from the scale bar - with click and drag to define then with a handle on each end for manipulation.
Starting with 2D is great and this will allow us to add 3D later. @brisvag is right that we don't have a obvious place to put 'things which live in scene space' right now. @psobolewskiPhD I like where you're coming from - a potential intermediate solution could be to add a context menu when we right click on a line which shows the length of the line in both data and world coordinates (with units from scale bar if set), would be curious if others like/dislike this idea!

a potential intermediate solution could be to add a context menu when we right click on a line which shows the length of the line in both data and world coordinates (with units from scale bar if set), would be curious if others like/dislike this idea!

Anything that gets use closer!
I think there are things a user (like me) can want:

to be able to quickly get the size of an object they are viewing. I confess I do this a lot, usually by zooming and repositioning so the scale bar is over my object of interest. Then I eye ball it. 🤣
to be able to indicate the size/distance visually on the image with a text label (optional). This is related to the above. One could also tweak the line ends to make them more ruler like, etc.
to be able to repeatedly measure the length/diameter of objects. Draw -> measure -> Draw -> measure, so on. There's an example that's a skeleton for that and this may be better for a plugin/widget.

Thanks for your fast feedback :smiley:
I agree with you, @brisvag, to add the option of drawing a ruler from point x to point y, additionally and create an independent overlay object for the ruler.
Furthermore, I think unifying the overlays is a good idea, too. This looks like a lot of work:) If you want I can help, @brisvag? How I understand the overlays, there are objects they live in world space like the interaction box or canvas space like the scale bar. But I think a ruler or an interaction box makes more sense in world space for me because they interact with them, or? Maybe a good approach could be to have the choice, but this is already the case,
https://github.com/napari/napari/blob/6ce1968d0924b3b104c3fe3ec7595fd17215a92b/napari/_qt/qt_viewer.py#L386-L414
the parent self.view for canvas space or self.view.scene for world space. There is just a linear transformation between them to compare the systems. If I am wrong, please correct me, @sofroniewn @brisvag?
@alisterburt @psobolewskiPhD
This is a good point to make a ruler on the top of a line shape object as additional property for the object. This can be
extended to a rectangle and so on, too. I love the idea @alisterburt, because it is light, too.
Nonetheless, my idea behind this was to have a ruler, which looks like a ruler and is fully independent of the layer interaction, just lives on the viewer in the world space for each 2D perspective and you do not need new buttons and icons. This implementation works for nd layers like the interaction box but is not yet supported for the 3D view like the interaction box. This is the case for drawing objects like lines for shape layers, too. This to add could be the next big step, but I think is not so easy and need a discussion previously that there are not going against and be consistent.
What do you think?
Another idea would be to have measurements like a ruler independent of overlays as an individual measurement layer? From my side, there is the question in which direction napari should go in the future? In the direction of imageJ with a lot of built-in stuff for instance or in the direction of a light fast viewer as it is now? For elementary measurements, I think there are a lot of opportunities like adding, cropping, and so on. This is a question, which the napari community has to answer :smile: In my opinion napari is a beautiful light viewer in python and the very good plugin system provides required stuff on top selecting individually by users so that they are not flooded with icons/buttons/options, which they do not need at all for their usage.

the parent self.view for canvas space or self.view.scene for world space. There is just a linear transformation between them to compare the systems. If I am wrong, please correct me, @sofroniewn @brisvag?

Yes i think that is right

Nonetheless, my idea behind this was to have a ruler, which looks like a ruler and is fully independent of the layer interaction, just lives on the viewer in the world space for each 2D perspective and you do not need new buttons and icons.

I think it is nice to have the separate ruler as people shouldn't be forced to add a shapes layer just to measure something - but we might also want to make is super easy to add a text box to each line with its length and a text box to each polygon with its area - that would be a fun feature

In my opinion napari is a beautiful light viewer in python and the very good plugin system provides required stuff on top selecting individually by users so that they are not flooded with icons/buttons/options, which they do not need at all for their usage.

yeah - i do like that simplicity too. i'm curious what others think here too

Hi, I have a question about how you can resize the scaler size; how do you employ an interaction box? thanks.

@jinxsfe this is a really old issue, and the "interaction box" no longer exists in that form, I don't think you could make this work.
Actually, this reminds me that this ruler tool is a great candidate for the new overlays system, and should be relatively easy to implement...


TiledTileMapReader not found

Hi I have a problem to run and execute one of the examples.
When I try to run the "diddy-examples-master/src/Tile/" example I get an
"Error : Type 'TiledTileMapReader' not found"
I use the current diddy module from https://github.com/swoolcock/diddy
Do I need something else to run the example?

It works now. I add "Import diddy.tile.diddyreader" and change "Extends TiledTileMapReader" to "Extends DiddyTiledTileMapReader".


Please check if the wording is right

Hi team,
Please check if the wording of MSDN Dev/Test subscription below is right.
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/direct-ea-administration#msdn-subscription-transfer
MSDN subscription transfer
When your transfer an MSDN subscription to an EA enrollment it's automatically converted to an MSDN Dev/Test subscription. After conversion, the subscription loses any existing monetary credit. So, we recommended that you use all your credit before you transfer it to your Enterprise Agreement.
If they are correct, what does "MSDN Dev/Test subscription." exactly mean?
I wonder if it should say "Enterprise Dev/Test subscription," if you mean MS-AZR-0148P
Enterprise Dev/Test subscription.
There is another section stating about MS-AZR-0148P
Enterprise Dev/Test subscription as below,
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/direct-ea-administration#to-set-up-the-enterprise-devtest-offer
When a user is added as an account owner, any Azure subscriptions associated with the user that is based on either the pay-as-you-go Dev/Test offer or the monthly credit offers for Visual Studio subscribers get converted to the EA Dev/Test offer. Subscriptions based on other offer types, such as pay-as-you-go, associated with the account owner get converted to Microsoft Azure Enterprise offers.
So, both of those 2 sections are stating about the same EA dev/Test offer?
Your clarification will be appreciated,
Thank you.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f83c18d8-14be-4262-035f-0caa6e2cf3b2
Version Independent ID: 17274f5d-d9fa-fdc3-2f72-e421be13cd00
Content: EA Billing administration on the Azure portal - Microsoft Cost Management
Content Source: articles/cost-management-billing/manage/direct-ea-administration.md
Service: cost-management-billing
Sub-service: enterprise
GitHub Login: @bandersmsft
Microsoft Alias: banders

@v-sashig
Thanks for your feedback! We will investigate and update as appropriate.

@bandersmsft Please review the question.

@v-sashig Thanks for raising this issue. I've updated the article for clarity. Mentions of MSDN Dev/Test were changed to Enterprise Dev/Test (ms-azr-0148p) and mentions of EA Dev/Test to Enterprise Dev/Test (ms-azr-0148p) for clarity.
#please-close


Crazy callback wrappers

I may have gone overboard with the safe callbacks because I wanted to replace all our manually made callbacks and we weren't super consistent (hence the front and back binding). Most use-cases are gonna be very simple however, something like the socket code
I also bumped to clang 15.0.2 while I was at it
made handle_function auto-cast entities so we don't have to manually lua["cast_entity"](ent) all the time

Still have to test, hopefully sometime today.

@Dregu for your async http stuff you can use this simply as make_safe_cb<void(std::string_view)>(std::move(lua_cb)) to get a thread-safe callback.


Add support for streaming Zarr stores for hosted datasets

Is your feature request related to a problem? Please describe.
Lots of geospatial data is stored in the Zarr format. This format works well for n-dimensional data and coordinates, and can have good compression. Unfortunately, HF datasets doesn't support streaming in data in Zarr format as far as I can tell. Zarr stores are designed to be easily streamed in from cloud storage, especially with xarray and fsspec. Since geospatial data tends to be very large, and on the order of TBs of data or 10's of TBs of data for a single dataset, it can be difficult to store the dataset locally for users. Just adding Zarr stores with HF git doesn't work well (see https://github.com/huggingface/datasets/issues/3823) as Zarr splits the data into lots of small chunks for fast loading, and that doesn't work well with git. I've somewhat gotten around that issue by tarring each Zarr store and uploading them as a single file, which seems to be working (see https://huggingface.co/datasets/openclimatefix/gfs-reforecast for example data files, although the script isn't written yet). This does mean that streaming doesn't quite work though. On the other hand, in https://huggingface.co/datasets/openclimatefix/eumetsat_uk_hrv we stream in a Zarr store from a public GCP bucket quite easily.
Describe the solution you'd like
A way to upload Zarr stores for hosted datasets so that we can stream it with xarray and fsspec.
Describe alternatives you've considered
Tarring each Zarr store individually and just extracting them in the dataset script -> Downside this is a lot of data that probably doesn't fit locally for a lot of potential users.
Pre-prepare examples in a format like Parquet -> Would use a lot more storage, and a lot less flexibility, in the eumetsat_uk_hrv, we use the one Zarr store for multiple different configurations.

Hi @jacobbieker, thanks for your request and study of possible alternatives.
We are very interested in finding a way to make datasets useful to you.
Looking at the Zarr docs, I saw that among its storage alternatives, there is the ZIP file format: https://zarr.readthedocs.io/en/stable/api/storage.html#zarr.storage.ZipStore
This might be convenient for many reasons:

On the one hand, we avoid the Git issue with huge number of small files: chunks files are compressed into a single ZIP file
On the other hand, the ZIP file format is specially suited for streaming data because it allows random access to its component files (i.e. it supports random access to its chunks)

Anyway, I think that a Python loading script will be necessary: you need to implement additional logic to select certain chunks (based on date or other criteria).
Please, let me know if this makes sense to you.

Ah okay, I missed the option of zip files for zarr, I'll try that with our repos and see if it works! Thanks a lot!

Hi,
Yes, it seems to! I got it working for https://huggingface.co/datasets/openclimatefix/mrms thanks for the help!

On behalf of the Zarr developers, let me say THANK YOU for working to support Zarr on HF! 🙏  Zarr is a 100% open-source and community driven project (fiscally sponsored by NumFocus). We see it as an ideal format for ML training datasets, particularly in scientific domains.
I think the solution of zipping the Zarr file is a great way to balance the constraints of Git LFS with the structure of Zarr.
It would be amazing to get something on the Hugging Face Datasets Docs about how to best work with Zarr. Let me know if there's a way I could help with that effort.

Also just noting here that I was able to lazily open @jacobbieker's dataset over the internet from HF hub 🚀 !
import xarray as xr
url = "https://huggingface.co/datasets/openclimatefix/mrms/resolve/main/data/2016_001.zarr.zip"
zip_url = 'zip:///::' + url
ds = xr.open_dataset(zip_url, engine='zarr', chunks={})

However, I wasn't able to get streaming working using the Datasets api:
from datasets import load_dataset
ds = load_dataset("openclimatefix/mrms", streaming=True, split='train')
item = next(iter(ds))

FileNotFoundError traceback
```
No config specified, defaulting to: mrms/2021
zip://::https://huggingface.co/datasets/openclimatefix/mrms/resolve/main/data/2016_001.zarr.zip
data/2016_001.zarr.zip
zip://2016_001.zarr.zip::https://huggingface.co/datasets/openclimatefix/mrms/resolve/main/data/2016_001.zarr.zip
---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
Input In [1], in ()
      1 from datasets import load_dataset
      2 ds = load_dataset("openclimatefix/mrms", streaming=True, split='train')
----> 3 item = next(iter(ds))
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/datasets/iterable_dataset.py:497, in IterableDataset.iter(self)
496 def iter(self):
--> 497     for key, example in self._iter():
498         if self.features:
499             # we encode the example for ClassLabel feature types for example
500             encoded_example = self.features.encode_example(example)
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/datasets/iterable_dataset.py:494, in IterableDataset._iter(self)
492 else:
493     ex_iterable = self._ex_iterable
--> 494 yield from ex_iterable
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/datasets/iterable_dataset.py:87, in ExamplesIterable.iter(self)
86 def iter(self):
---> 87     yield from self.generate_examples_fn(**self.kwargs)
File ~/.cache/huggingface/modules/datasets_modules/datasets/openclimatefix--mrms/2a6f697014d7eb3caf586ca137d47ca38785ae2fe36248611b021f8248b59936/mrms.py:150, in MRMS._generate_examples(self, filepath, split)
147 filepath = "https://huggingface.co/datasets/openclimatefix/mrms/resolve/main/data/2016_001.zarr.zip style="color:rgb(175,0,0)">"
148 # TODO: This method handles input defined in _split_generators to yield (key, example) tuples from the dataset.
149 # The key is for legacy reasons (tfds) and is not important in itself, but must be unique for each example.
--> 150 with zarr.storage.FSStore(fsspec.open("zip::" + filepath, mode='r'), mode='r') as store:
151     data = xr.open_zarr(store)
152     for key, row in enumerate(data["time"].values):
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/zarr/storage.py:1120, in FSStore.init(self, url, normalize_keys, key_separator, mode, exceptions, dimension_separator, **storage_options)
1117 import fsspec
1118 self.normalize_keys = normalize_keys
-> 1120 protocol, _ = fsspec.core.split_protocol(url)
1121 # set auto_mkdir to True for local file system
1122 if protocol in (None, "file") and not storage_options.get("auto_mkdir"):
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/core.py:514, in split_protocol(urlpath)
512 def split_protocol(urlpath):
513     """Return protocol, path pair"""
--> 514     urlpath = stringify_path(urlpath)
515     if "://" in urlpath:
516         protocol, path = urlpath.split("://", 1)
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/utils.py:315, in stringify_path(filepath)
313     return filepath
314 elif hasattr(filepath, "fspath"):
--> 315     return filepath.fspath()
316 elif isinstance(filepath, pathlib.Path):
317     return str(filepath)
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/core.py:98, in OpenFile.fspath(self)
96 def fspath(self):
97     # may raise if cannot be resolved to local file
---> 98     return self.open().fspath()
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/core.py:140, in OpenFile.open(self)
132 def open(self):
133     """Materialise this as a real open file without context
134
135     The file should be explicitly closed to avoid enclosed file
(...)
138     been deleted; but a with-context is better style.
139     """
--> 140     out = self.enter()
141     closer = out.close
142     fobjects = self.fobjects.copy()[:-1]
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/core.py:103, in OpenFile.enter(self)
100 def enter(self):
101     mode = self.mode.replace("t", "").replace("b", "") + "b"
--> 103     f = self.fs.open(self.path, mode=mode)
105     self.fobjects = [f]
107     if self.compression is not None:
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/spec.py:1009, in AbstractFileSystem.open(self, path, mode, block_size, cache_options, compression, **kwargs)
1007 else:
1008     ac = kwargs.pop("autocommit", not self._intrans)
-> 1009     f = self._open(
1010         path,
1011         mode=mode,
1012         block_size=block_size,
1013         autocommit=ac,
1014         cache_options=cache_options,
1015         **kwargs,
1016     )
1017     if compression is not None:
1018         from fsspec.compression import compr
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/implementations/zip.py:96, in ZipFileSystem._open(self, path, mode, block_size, autocommit, cache_options, **kwargs)
94 if mode != "rb":
95     raise NotImplementedError
---> 96 info = self.info(path)
97 out = self.zip.open(path, "r")
98 out.size = info["size"]
File /opt/miniconda3/envs/hugginface/lib/python3.9/site-packages/fsspec/archive.py:42, in AbstractArchiveFileSystem.info(self, path, **kwargs)
40     return self.dir_cache[path + "/"]
41 else:
---> 42     raise FileNotFoundError(path)
FileNotFoundError:
</details>

Is this a bug? Or am I just doing it wrong...

I'm still messing around with that dataset, so the data might have moved. I currently have each year of MRMS precipitation rate data as it's own zarr, but as they are quite large (on order of 100GB each) I'm working to split them into single days, and as such they are still being moved around, I was just trying to get a proof of concept working originally.

I've mostly finished rearranging the data now and uploading some more, so this works now:
import datasets
ds = datasets.load_dataset("openclimatefix/mrms", streaming=True, split="train")
item = next(iter(ds))
print(item.keys())
print(item["timestamp"])

The MRMS data now goes most of 2016-2022, with quite a few gaps I'm working on filling in

Hi @albertvillanova, I noticed there is now the HFFileSystem, where the docs show an example of writing a Zarr store directly to the Hub, and no mention of having too many files. Is there still the restriction on lots of files in datasets? It would be more convenient to be able to have the geospatial data in one large Zarr store, rather than in multiple smaller ones, but happy to continue using zipped Zarrs if thats the recommended way.

Hi @jacobbieker.
Thanks for coming back to this pending issue.
In fact, we are now using the fsspec API in our HFFileSystem, which was not the case when you created this issue.
On the other hand, I am not sure of the current limitations, both in terms of the number of files or performance when loading.
I think it would be best to try a POC again and discuss any issues that arise and whether we can fix them on our end (both datasets  and the Hub).
We would really like to support the Zarr format 100% and that the Hub is really convenient for your use case. So do not hesitate to report any problem.


check osdp close file status (according prototype function comments)

could be usefull if any error during file closing

I conciously chose to ignore this error, here is my reasoning:

this close failure is a local issue, the OSDP peer does not need to know about it.
all bytes of the file has been sent to the peer and the peer has probably closed it's FD already so don't make sense to ask it to discard the contents due to this issue.

On the other hand, we can have the log message. What do you think?


A hefty BIG rewrite

Admittedly, this is a tough commitment that'll drain all my time and energy doing this tedious process; frankly, it has taken a lot of work to rewrite the entire codebase, and here's the reason why:

To clean up to coincide with both the desktop and the web client, most of the commits have been focused mainly on the web client and I want it to lean more on both sides
Refactor all the imports to shift the new paradigm of importing components and shared files

In addition, I might also rework the landing page to make up for all of the rewrite work as well

Whoops, my bad


Enable audio reply

#73

Hi, thanks. I will check it out
Could you please check and add this to the send_sticker and reply_sticker as well?

Hi @ArielS1, thanks for the PR!
Is this got checked and worked? in the facebook docs appear that some messages cannot be sent as replies

Hi @ArielS1, thanks for the PR! Is this got checked and worked? in the facebook docs appear that some messages cannot be sent as replies

I tested the send_audio and reply_audio and it works for sure
I also copy pasted the same logic for stickers, few minutes ago


docs: clean up the troubleshooting for mac users section

The problem related to the zkevm-bridge-ui on macOS and WSL has been solved by #63.
This PR cleans up the Troubleshooting documentation. Now mac users only need to have Docker Engine version 4.27 or higher to run the zk-prover.

Adding @kmurphypolygon as a reviewer


motor - run until stalled

Hi, will the package eventually support motors stopping when stalled, similar to the pybricks functionality? Or is this not possible with the HAT? Is there a way to implement this with the current python-build-hat library?
Thank you!

My scenario is: having the motor move and once the motor reaches an obstruction and stalls, the motor stops.
This reduces the need for combining a motor with a sensor that detects when the motor has stopped.
Since the HAT has only 4 LEGO ports, this reduces the number of LEGO devices needed for motion control.
Alternatively we're looking at combining two LEGO HATS through a stack board, but there are pin address collisions. So we're also looking at ways to combine two HATS with the ability to multiplex between them.
Thanks again!

  I went and looked at pybricks and their code is amazingly complicated (and excellently documented) and has the benefit of working directly on the motor and its signals.  All this is to say I wouldn't get your hopes up, but I'm not done poking at it.

Hi, will the package eventually support motors stopping when stalled, similar to the pybricks functionality? Or is this not possible with the HAT?

Pybricks developer here.
We define stalled as "unable to reach target speed or position given the available feedback torque". The torque and speed thresholds are configurable. Using the internal motor control state, this can get very responsive.
On that note, would there be any interest in a fully open source firmware for the Build Hat?
I've seen a few of such requests here and on the Raspberry Pi forums. It could potentially solve most motor and sensor related problems, and perhaps improve the hat's responsiveness quite a bit.
It's certainly possible technically, and we'd be happy to chat about it with the Raspberry Pi Foundation. I don't know if we should open an issue here (@chrisruk ? ) but we can also be reached via email<EMAIL_ADDRESS>or on GitHub.

I would say there's not enough political capital in online discussions with the Raspberry Pi Foundation to get any meaningful action on the firmware, as no reason for the closed source has been even offered, despite the chip being produced by the Foundation itself.  The Pybricks team may have enough, if the issue of BuiltHAT being not well suited for precision robot applications due to firmware limitations was raised in their own official channels.
I do like the BuildHAT, but I can't even get it to replace EV3Dev in some projects I have due to the imprecision in motor control.

Thanks for your response! But crucially, this approach doesn't require the original firmware source to be be disclosed.
Pybricks already has open source drivers for all LEGO motors and sensors. These drivers could be adapted to run on this architecture. They can run without MicroPython on top as this would not be needed in this application.
The Build Hat seems like it has a lot of potential just waiting to be unlocked :)

The firmware is signed, so looping in Pybricks to run on the RP2040 would be a significant development structure change, if I understand you correctly.
If the firmware were open sourced, which seems to require external pressure on the Foundation to do so, then improved and adapted drivers could at least be formally entertained as options.

I've come here as I have recently obtained a RPi 3 B and, being an AFOL who enjoys motorising builds, immediatly considered a build HAT. However, having read this thread, and others, I'll give it a miss. Consider:
Pyricks on the Technic Hub works.
Pybricks on the EV3 works.
EV3Basic on the EV3 works.
Arduino (with hacked wiring) works.
So many alternatives work as intended. Why put up with h'ware and s'ware that does not work.
So much good open source software out there that I have gained great pleasure, satisfation and knowledge from. Why this attitude by RPi Foundation?


Add missing canonicalization to LLVMCPUVectorLowering

I found that some canonicalization between the three stages of LLVMCPUVectorLowering are not happening. This patch adds the canonicalization stages that we have between them.
(This is another indicator that we have to split this pass into multiple ones :))

It's difficult to know which canonicalization pattern is missing. I added them all to see if that fixed https://github.com/openxla/iree/issues/13004 but that doesn't seem to be the case :(
At the very least, there are some canonicalization patterns from vector.transpose that are not happening between the concat and the transpose lowering and that is regressing masking.


cawbird: 1.0.1 -> 1.0.2

Motivation for this change
fixes some TLS connection issues
please backport to release-19.09
Things done

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

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

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

@GrahamcOfBorg build cawbird

backported in 5d430d1641166fa2b3b2dace5bf3bf3f83f88a44


Values derived from useColorMode() can be stale when rendering in prod mode

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
The value returned by the useColorMode hook from @docusaurus/theme-common seems to have a strange behavior when:

Building for production and/or using React in prod mode (npm run build && npm run serve).
window.localStorage.theme is 'dark' while the themeConfig.colorMode.defaultMode value is 'light', or window.localStorage.theme  is 'light' while the themeConfig.colorMode.defaultMode value is 'dark'.

Then trying to use the colorMode value set the value of DOM attributes ends up generating a DOM with incorrect attribute values:
import { useColorMode } from "@docusaurus/theme-common";
import React from "react";

export default function ColorModeTest() {
  const { colorMode } = useColorMode();
  return (

{colorMode}

  );
}

In the conditions described above, if the themeConfig.colorMode.defaultMode value is 'light' and the localStorage.theme value is 'dark':

The generated HTML will be:
light

The hydrated DOM will be:
dark

This is particularly troublesome when you have UI components that support both dark and light themes and rely on HTML attributes to set the correct color theme on the component itself (e.g. in order to display a light component in a dark context for visual emphasis).
Reproducible demo
https://github.com/fvsch/docusaurus-use-color-mode-stale-value
Steps to reproduce

Check out https://github.com/fvsch/docusaurus-use-color-mode-stale-value
Install dependencies, build for prod and serve that build: npm install && npm run build && npm run serve
The home page of the demo should be using a light theme.
Click the theme switching button on the top right to switch to the dark theme.
Reload the page.

Expected behavior
The values derived from the colorMode, whether they're text nodes or attribute nodes, should be in sync and reflect the localStorage.theme value.
In the last step, the visual result should be:

Actual behavior
Attribute values that are derived from the colorMode value seem to be outdated.
In the last step, the visual result is:

Your environment

Public source code: https://github.com/fvsch/docusaurus-use-color-mode-stale-value/blob/main/src/components/ColorModeTest/index.js
Public site URL: n.a. (but currently affects https://developer.stackblitz.com/ too)
Docusaurus version used: 2.0.1
React version used: 17.0.2
Environment name and version (e.g. Chrome 89, Node.js 16.4): all browsers tested (Firefox, Chrome and Safari); Node 16.17.0.
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS 12.5, probably happens on Linux too (happens when building our site on CI); haven't tried on Windows but I don't expect a difference here.

Self-service

[ ] I'd be willing to fix this bug myself.

Agree there is likely a React hydration problem.
const getInitialColorMode = (defaultMode: ColorMode | undefined): ColorMode =>
  ExecutionEnvironment.canUseDOM
    ? coerceToColorMode(document.documentElement.getAttribute('data-theme'))
    : coerceToColorMode(defaultMode);

  const [colorMode, setColorModeState] = useState(
    getInitialColorMode(defaultMode),
  );

Again related blog post: https://www.joshwcomeau.com/react/the-perils-of-rehydration/
Afaik it has been claimed in a clearer way more recently by the React core team that the SSR/CSR must 100% match. React 18 introduces a onRecoverableError callback which usually notice you of hydration mismatches, and in this React 18 POC PR (https://github.com/facebook/docusaurus/pull/7855) I noticed we had some.
In this case I think we can't technically init our React state with the correct value, but instead should always init it to the default color mode, and then trigger a new re-render to fix it after hydration.
const [colorMode, setColorModeState] = useState(defaultMode);

useLayoutEffect(() => {
  coerceToColorMode(document.documentElement.getAttribute('data-theme'))
},[])

This should fix the SSR/CSR mismatch, but this is a bit annoying unfortunately, as it will mean some components will render first with the wrong colorMode and then eventually re-render with the right one

any status update or timeline on this? seems to be an important one. I have an logo with a font color that I need to change dynamically on the current color theme, and currently this bug means I need to keep the theme switcher toggle disabled for now. Thanks!

I'll probably fix this as part of the React 18 upgrade, as we'll be able to see hydration error messages that I would have to fix one by one to complete this migration.
Note you might not need useColorMode, you can also use html[data-theme="dark" CSS selectors and we also have a ThemedImage component.

Is there any ETA on that? Still broken on 3.0.1

@sszczep this is likely not something we can actually fix.
I suggested in https://github.com/facebook/docusaurus/issues/7986#issuecomment-1291989001 to use CSS media queries for styling instead.
If you have another use-case that can't be solved with CSS, please explain why and I'll try to provide a workaround.

@sszczep this is likely not something we can actually fix. Due to how React hydration works, the first value returned by this hook is likely not the actual effective color mode your page is rendered in.
I suggested in https://github.com/facebook/docusaurus/issues/7986#issuecomment-1291989001 to use CSS media queries for styling instead.
If you have another use-case that can't be solved with CSS, please explain why and I'll try to provide a workaround.

I need to pass current color mode to Material UI Theme Provider. Can't use CSS variables unfortunately. If you have a workaround that would be great. Cheers

There is no good workaround IMHO.
You might be fine with the following, but use at your own risks, and be aware it is likely to create issues down the line.
const isDarkMode = document.documentElement.getAttribute('data-theme') === "dark";

Please also understand that Docusaurus doesn't have good support for "legacy CSS-in-JS libs" (StyledComponents, Emotion, JSS, MUI...), that require collecting styles during the rendering process (see also https://github.com/facebook/docusaurus/issues/3236).
So I'd simply recommend not using MUI in the first place, unless you clearly understand the tradeoff you make and the risk of having flashes of unstyled content.

Flashes don't really bother me so it shouldn't be an issue. I'll give it a shot. Thanks

Turns out that with MUI v5.6.0 they released a support for CSS theme variables. I successfully incorporated CssVarsProvider with Docusaurus theming system. They are now synced without any further gimmicks and shouldn't cause issues in the future. As described here it has some drawbacks (bigger code size, polluting stylesheets with vars) but it is definitely better than dealing with FOUC.
@slorber I also tested your recommendation, worked fine with MutationObserver, but the flicker was worse than I initially anticipated.
If anyone is interested, here is the code:
src/theme/Layout/MuiThemeProvider.tsx
import React from "react";

import {
  Experimental_CssVarsProvider as CssVarsProvider,
  experimental_extendTheme as extendTheme,
} from "@mui/material/styles";

const theme = extendTheme({
  // custom theming overrides...
});

export default function MuiThemeProvider({
  children,
}: React.PropsWithChildren) {
  return (
    <CssVarsProvider
      theme={theme}
      attribute="data-theme"
      colorSchemeStorageKey="theme"
      modeStorageKey="theme"
    >
      {children}
    </CssVarsProvider>
  );
}

src/theme/Layout/index.tsx
import React from "react";

import Layout from "@theme-original/Layout";
import { Props } from "@theme/Layout";

import MuiThemeProvider from "./MuiThemeProvider";

export default function LayoutWrapper({ children, ...props }: Props) {
  return (
    <Layout {...props}>
      <MuiThemeProvider>
        {children}
      </MuiThemeProvider>
    </Layout>
  );
}

Once again, thanks for guiding me into that direction.

I'll probably fix this as part of the React 18 upgrade, as we'll be able to see hydration error messages that I would have to fix one by one to complete this migration.
Note you might not need useColorMode, you can also use html[data-theme="dark" CSS selectors and we also have a ThemedImage component: https://docusaurus.io/docs/markdown-features/assets#themed-images

I had the same problem and "ThemedImage" helped

@LeonnardoVerol which problem, and can you create a https://docusaurus.new repro please so that we see this problem in action?

@LeonnardoVerol which problem, and can you create a https://docusaurus.new repro please so that we see this problem in action?

It was like the original post... I was using "colorMode" to swap 2 images.
Docusaurus would swap correctly the images on light/dark toggle but fail to swap the images in some other situations. (E.g: on page refresh)
Replacing that logic for "ThemedImage" solved my problem.

any status update or timeline on this? seems to be an important one. I have an logo with a font color that I need to change dynamically on the current color theme, and currently this bug means I need to keep the theme switcher toggle disabled for now. Thanks!

There seems to be a hacky way to temporarily overcome this problem, which is by wrapping the base component in another component that delays the rendering using useEffect, so that the obtained value will be the correct one. But it might not be suitable for all use cases. For mine, it happened to be a theme switcher toggle as well so it worked… at least for now.
const visibilityReducer = () => true

function SomeComponent() {
  const [visible, setVisibilityTrue] = useReducer(visibilityReducer, false)
  useEffect(setVisibilityTrue, [setVisibilityTrue])
  return visible ? <SomeComponentBase /> : null
}

Also, this seems to be quite an old issue and I see some PRs were merged above. My @docusaurus/core and @docusaurus/preset-classic are both v3.4.0, but I am encountering this issue also, not sure if this is normal? Thought of opening a new issue at first, but changed my mind thinking it might be a better idea to continue in this thread for now.

it's also happen in 3.4,  use ThemedImage and tailwind instead of useColorMode, it's work!


MCUXpresso SDK FreeRTOS updates.

List of NXP MCUX SDK modifications.

Task aware debugging support:
- freertos_task_c_additions.h
- add portARCH_NAME to CM33 portmacro.h
GCC -flto optimization support
- vTaskSwitchContext attribute used in task.h
Enable definition of configCPU_CLOCK_HZ by variable instead of constant.
- add external variable declaration to port.c (extern uint32_t SystemCoreClock;)
Add alternative memory alocator adapted for newlib.
- heap_useNewlib.c
Replace configOVERRIDE_DEFAULT_TICK_CONFIGURATION in RVDS ports.
- use generic solution attribute((weak))
Tickless for CM0
- add external declaration of vPortSuppressTicksAndSleep into CM0 portmacro.h
Checklist:

Updates are rebased to master branch just for purpose of further discussion.

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi David - thanks for this contribution.  This is going to take some time to go through - below just starting with a high level:

freertos_task_c_additions.h

Although this header file was originally added at NXP's request, it is now generally available for all users, and is often mentioned in the support forums when people want to add code into the tasks.c file without modifying the code.  That makes the file very much project specific rather than part of the kernel code - analogous to the FreeRTOSConfig.h file which would not be stored in a directory that is in the include path of all projects that use the kernel.  Your submission also includes what I think is NXP specific code - if some of that code is generally useful to all users then perhaps we can add it directly into the .c file to leave the header file available for all users.

add portARCH_NAME to CM33 portmacro.h

I think this changes have already been done, but not synch'ed with Git yet.  Let me know if anything is missing:
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/portable/ARMv8M/non_secure/portable/GCC/ARM_CM33_NTZ/portmacro.h#l90 ... etc.

GCC -flto optimization support
vTaskSwitchContext attribute used in task.h

We have already done this too so it will be available here in the next sync (see portDONT_DISCARD):
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/include/task.h#l2307
We do not allow any compiler or third party library specifics into the kernel code, hence we do not check for GCC inline using the pre-processor, but use a macro that is then defined in the compiler specific portmacro.h file.
which also means....

Enable definition of configCPU_CLOCK_HZ by variable instead of constant.
add external variable declaration to port.c (extern uint32_t SystemCoreClock;)

....I'm afraid we cannot include SystemCoreClock either, although I can't actually see where you use the variable that is externed.  If it relies on the variable being in the build then it will break the build for many thousands of developers, if it doesn't rely on SystemCoreClock being defined then the definition is redundant for those users.
What is the use case here?  Maybe we can find another way of achieving it?  I'm assuming you cannot just have the extern in FreeRTOSConfig.h, or #define configCPU_CLOCK_HZ to SystemCoreClock.

Add alternative memory alocator adapted for newlib.
heap_useNewlib.c

Will look in more detail.

Replace configOVERRIDE_DEFAULT_TICK_CONFIGURATION in RVDS ports.
use generic solution attribute((weak))

Weak attribute was not available at the time the code was written.  If there are no backward compatibility issues for users this would seem to be a simple change.

Tickless for CM0
add external declaration of vPortSuppressTicksAndSleep into CM0 portmacro.h

Enough people have done their own version of this that I agree it should be in the official distribution.

Updates to some of my comments from my previous reply:

add portARCH_NAME to CM33 portmacro.h

I think this changes have already been done, but not synch'ed with Git yet. Let me know if anything is missing:
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/portable/ARMv8M/non_secure/portable/GCC/ARM_CM33_NTZ/portmacro.h#l90 ... etc.

GCC -flto optimization support
vTaskSwitchContext attribute used in task.h

We have already done this too so it will be available here in the next sync (see portDONT_DISCARD):
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/include/task.h#l2307

These have now been merged into the Github repo.

....I'm afraid we cannot include SystemCoreClock either, although I can't actually see where you use the variable that is externed. If it relies on the variable being in the build then it will break the build for many thousands of developers, if it doesn't rely on SystemCoreClock being defined then the definition is redundant for those users.
What is the use case here? Maybe we can find another way of achieving it? I'm assuming you cannot just have the extern in FreeRTOSConfig.h, or #define configCPU_CLOCK_HZ to SystemCoreClock.

Would be interested in your reply to the above to see what we can do here.

Add alternative memory alocator adapted for newlib.
heap_useNewlib.c

Will look in more detail.

This is similar to heap_3 already, which could be used with newlib, but doesn't provide sbrk() or configLINKER_HEAP_BASE_SYMBOL.  There are some application/environment/compiler specifics here so options would be either for you to provide this file yourself (as per the task c additions header file) or for this to be provided as a utlity c file in a similar way to the sprintf_stdarg c file.
Additionally - the setjmp/xJmpBuf suggestions - which I seem to have neglected to comment on previously.  These changes are isolated to a single compiler which allows us to make and test the changes without fear of breaking somebody else's builds, however I'm interested in the use case as most users will not have anything to return to.  Please let me know.

/bot run checks

Hello DavidJurajdaNXP,
Is this PR up to date ? Can you please resolve conflicts  ? Coding style checks are failing as well, we'll try to get back to you on that once conflicts are resolved.
Thanks.

Hi all,
@abhidixi11
Pull Request is not ready for merge. It is only resource for broader discussion.
It is not planned to merge it directly.
@RichardBarry
I have removed following requirements from pull request:
- freertos_tasks_c_additions.h
- heap_useNewlib.c
- extern uint32_t SystemCoreClock in port.c
- Scheduler ending support
Explanation:
Will be covered on NXP side in CMSIS pack vendor extension for FreeRTOS
- freertos_tasks_c_additions.h
- heap_useNewlib.c
Could be covered in FreeRTOSConfig.h
- extern uint32_t SystemCoreClock in port.c
Scheduler ending functionality is required for gcov coverage tests enablement, but it could be stripped from official support.
- Scheduler ending support
Remaining requirements to discuss are:
- vPortSuppressTicksAndSleep support for CM0
- configOVERRIDE_DEFAULT_TICK_CONFIGURATION -> attribute((weak)) in RVDS
Regards,
David

Hi all,
@RichardBarry
Remaining requirements to discuss are:
- vPortSuppressTicksAndSleep support for CM0
- configOVERRIDE_DEFAULT_TICK_CONFIGURATION -> attribute((weak)) in RVDS
I have removed following requirements from pull request:
- freertos_tasks_c_additions.h
- heap_useNewlib.c
- extern uint32_t SystemCoreClock in port.c
- Scheduler ending support
Explanation:
Will be covered on NXP side in CMSIS pack vendor extension for FreeRTOS
- freertos_tasks_c_additions.h
- heap_useNewlib.c
Could be covered in FreeRTOSConfig.h
- extern uint32_t SystemCoreClock in port.c
Scheduler ending functionality is required for gcov coverage tests enablement, but it could be stripped from official support.
- Scheduler ending support
@abhidixi11
Pull Request is not ready for merge. It is only resource for broader discussion.
It is not planned to merge it directly.
Regards,
David

@DavidJurajdaNXP
I got the hardware and I'm in the middle of testing my two PRs linked above. Since it has been a while (apologize..), could you confirm we should be able to fully resolve this thread once: 1, tickless is supported in CM0 port(s); 2, weak linkage is updated in CM3 and CM4 ports?

Hi @yuhui-zheng,
CM0 and CM4 tickless support is most important for us. We would like to add tickless support also for CM33, but let's start with CM0 and CM4. Should I prepare isolated pull request? Do you need any reference or package?
Tickless support list should also include RVDS week unification:
3. Replace configOVERRIDE_DEFAULT_TICK_CONFIGURATION in RVDS ports.
- use generic solution attribute((weak))
We would like to cover also inconsistency in API prvSetupTimerInterrupt/vPortSetupTimerInterrupt.
Feel free to contact me anytime here or via email.
Regards,
David

Thanks @DavidJurajdaNXP. I think I'll be fine without additional PR or reference for now.
In regards to tickless --

I'll merge tickless for GCC/Keil/IAR CM0 into kernel repository, and it'll be included in future releases.

For CM4 are you looking for tickless in MPU or non-MPU port? I believe CM4 non-MPU port already supports tickless. Linking below:
GCC/CM_4F (non-MPU) --
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/portable/GCC/ARM_CM4F/port.c#l511
Keil/CM_4F (non-MPU) --
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/portable/RVDS/ARM_CM4F/port.c#l524
IAR/CM_4F (non-MPU) --
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Source/portable/IAR/ARM_CM4F/port.c#l387

CM33 is also on track by another colleague, I believe.

In regards to weak linkage --

I'll merge the update along with tickless into kernel directory.

Seems we've got you covered for this thread. Will keep this PR open for one more week.
Regards,
Yuki

@DavidJurajdaNXP  I'm closing this thread now. Things are currently under review (see below reference links if interested), and will be merged to upstream shortly.

M0 tickles:
https://github.com/yuhui-zheng/FreeRTOS/tree/LPC51U68_M0+_Xpresso
(Could try out demo projects under ./FreeRTOS/Demo/CORTEX_M0+_LPC51U68_LPCXpresso/, GCC/Keil/IAR projects could be found there.)
M3/M4 weak linkage:
https://github.com/yuhui-zheng/FreeRTOS/tree/CORTEX_M3_4_Keil_weak_linkage


message with attachments

I was trying to use the chat.postMessage method you have and your API is slightly different than slacks
wondering if you only support text messages? I tried adding an attachment inside options but doesn't seem to render.
https://api.slack.com/methods/chat.postMessage

Good catch.  I'll see if I can fix that today.

note that the way attachments are handled, they need to be JSON.stringify'd
https://github.com/slackhq/node-slack-client/issues/12
this took some time to figure out a way back!

+1 i need this one, i may be doing a PR of this

Well I've had the same problem for a while now, and decided to fix it : #5
Btw, I added the support for icon_emoji in the options.
What do you think @krishamoud, can you merge it?

Closed with https://github.com/krishamoud/meteor-slack-api/pull/5


Is it impossible to save pptx with images as blobs?

Hi,
Is it impossible to save pptx with images as blobs?
pptx.save(ppt_name, function(blob){console.log(blob);},'blob');
When I execute the code, the logs are as follows.

(it prints not Blob, but pptx Filename)
but when I execute the code without 'slide.addImage(...)',
Browser print 'blob' logs well.

Thanks-!

https://stackoverflow.com/questions/57193128/cant-save-pptx-with-image-in-blob-format-pptxgenjs?noredirect=1#comment100895635_57193128
I solved it-


Wrap the form inside the component

TypeError: document.querySelector(...).parentElement.submit is not a function
    at VueComponent.<anonymous> (StripeCheckout.vue:165)
    at Array.<anonymous> (vue.js:661)
    at nextTickHandler (vue.js:608)
    at <anonymous>
handleError @ vue.js:529
(anonymous) @ vue.js:663
nextTickHandler @ vue.js:608

i'm sorry but i got the same error and i don't understand why...
my form is inside the component..
I'm using NUXT maybe because of it?
Any idea to make it work?
thanks a lot for help


It doesn't work I put the key in and get an error

I'm in 0.11.1 mcpe I have a Samsung galaxy s4 and I get an authentication error when I put the security key in

Are you running the server on Android, if so see #11

Yes I am using Android but I didn't understand how that helped I put key in like it says and I get an error

Further discussion should go to #11


topo sort of context entries is impossible

unlike scope entries, context entries are nameless, so there's no way to resolve reference hierarchies
related note: telescope is supposed to be a list of named types, but there's a field clash between "name" in the context of a scope entry and in the context of a scope reference

The related note is a good catch, now fixed by not using "name" for everything, instead:

"refName" holding the identifier of a ScopeReference
"boundName" holding the bound variable name of a Pi

Note that you cannot properly build a dependency tree out of those strings/names, these are not unique in contrast to the scope that has fully-qualified names (+ unique numeric identifiers), so you have to really use the DeBruijn indices to actually calculate which context entry a local variable refers to, c.f. Test.ContextShadowing{.agda/.json} for a detailed example.


add amplify pull docs

Issue #, if available: fixes #3125
Description of changes:
added amplify pull references in README and amplify help.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #3126 into master will increase coverage by 0.44%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3126      +/-   ##
==========================================
+ Coverage   63.13%   63.57%   +0.44%
==========================================
  Files         223      220       -3
  Lines       11179    11101      -78
  Branches     2317     2161     -156
==========================================
  Hits         7058     7058
+ Misses       3807     3733      -74
+ Partials      314      310       -4

Impacted Files
Coverage Δ

packages/amplify-cli/src/context-extensions.ts
25.69% <0%> (ø)
:arrow_up:

...lify-graphql-types-generator/src/compiler/index.ts
90.32% <0%> (ø)
:arrow_up:

...y-graphql-types-generator/src/compiler/legacyIR.ts
96.72% <0%> (ø)
:arrow_up:

...fy-appsync-simulator/src/schema/directives/auth.ts

...c-simulator/src/schema/directives/aws-subscribe.ts

...s/amplify-appsync-simulator/src/type-definition.ts

...ync-simulator/src/velocity/util/transform/index.ts

.../amplify-appsync-simulator/src/mqtt-server/util.ts

...s/amplify-appsync-simulator/src/resolvers/index.ts

...y-appsync-simulator/src/schema/directives/index.ts
0% <0%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


Timepicker: DST issue

On the fall day of DST the time picker can't go forward past 2 AM
http://plnkr.co/edit/f1kiq5J89eOhBLgtstRT?p=preview

I'm not seeing this - can you give me the exact steps you are taking to see the issue?

Ah, I think this might happen, if the day to switch back from DST in your time zone differs from mine (2016-10-30). Please change $scope.mytime accordingly.

Got it, finally was able to reproduce in the Pacific timezone: http://plnkr.co/edit/aJSWySs4N458sERn7yum?p=preview
This is an interesting bug. We likely need to add a check in the increment method in the timepicker & special timezone handling - the decrement one seems to work properly.

I really want to know hot to use arrowkeys in Timepicker.

Closing in favor of #5957 as this will result in a complete rewrite of the widget, addressing all the outstanding issues.


whether \bar is too long?

as the title says
\bar {H} is rendered as

and this is created by https://www.codecogs.com/latex/eqneditor.php, well I think it is too short on the other hand

The rendered output in MathJax viewer is ok IMO.


Using socket.io-redis but there is nothing in my redis database

Sails version: 0.12.1
Node version: 4.2.4
NPM version: 3.5.2
Operating system: Windows 10

I have moved sockets to use socket.io-redis as opposed to memory because I need to deploy a Sails application (that is currently running in Windows) on Heroku.  I have disabled "polling" and can see my clients all connecting with "websocket" so there should be no sticky session issues.  My worry is that although everything seems to be working fine in a test environment, I cannot actually see any data in Redis that looks relevant to sockets.  I admit I don't know what it might look like anyway, but I have other redis dependencies (busmq and redis-sessions) that are working fine and I can see the data in the database.  Should I see evidence of socket.io-redis activity in the redis db?  What would it look like?  Perhaps I am just misunderstanding what happens under the covers.

OK

Should I see evidence of socket.io-redis activity in the redis db? What would it look like? Perhaps I am just misunderstanding what happens under the covers.

I've been there-- it can be confusing at first.  It's not actually storing anything in Redis-- it's using Redis's built in message queuing to deliver messages.  The actual room membership is stored in the memory of the individual Node processes-- this is why we had to implement an additional layer in Sails (used to be known as the "admin bus") in order to support .join() and .leave() in a multi-node environment (was part of the 0.12 release-- previously, join and leave would only work for a single Node server and not across the entire cluster).
Hope that helps!  Sounds like you're doing everything right to me. 👍

Ok - many thanks for the clarification

I've been wondering this for the last couple days and trying to find it, so thanks for asking kpturner and for the clarification mikermcneil. I found it confusing too.
The config/sockets.js file says:

One of the big challenges of scaling an application is that these sorts
of clustered deployments cannot share memory

so I was expecting redis to be used for shared memory.
Just after that, it says:

However that means that all room/pubsub/socket processing and shared memory has to be offloaded to a shared, remote messaging queue (usually Redis)

The remote message queue part is key!
I'd recommend adding a statement like When working with sockets, Sails only needs Redis for the sake of its messaging queue. No data is stored in Redis., perhaps after the phrase "Luckily, Socket.io (and consequently Sails.js) apps support Redis for sockets by default."
@mikermcneil Can you confirm, does this mean that each server has a copy of ALL socket session data, even if it's only connected to a subset of those sockets?

I stumbled on to this issue cause I couldn't figure out why there was no data being saved in redis. Additional documentation would be very helpful.
@tylercollier Been wondering that myself as well. @mikermcneil Can you confirm tylers last question?


No, but really. This is what I sent the pull request for the first time. Honestly. I don't know what you're talking about.

Merged! Thanks for contributing :)

Merged! Thanks for contributing :)

No problem! Thanks for making it easier to get up and running!
On Thu, Dec 31, 2015, 11:19 PM Charlton Trezevant<EMAIL_ADDRESS>wrote:

Merged! Thanks for contributing :)
—
Reply to this email directly or view it on GitHub
https://github.com/ctrezevant/eliteshell/pull/5#issuecomment-168281186.

No problem! Thanks for making it easier to get up and running!
On Thu, Dec 31, 2015, 11:19 PM Charlton Trezevant<EMAIL_ADDRESS>wrote:

Merged! Thanks for contributing :)
—
Reply to this email directly or view it on GitHub
https://github.com/ctrezevant/eliteshell/pull/5#issuecomment-168281186.


FMOscillator Bug Fixes

Fixing a slew of control processing bugs that snuck in during refactoring.

Looks good! Thanks for the fix!


erigon: 2022.10.01 -> 2.29.0

Description of changes
erigon update https://github.com/ledgerwatch/erigon/releases/tag/v2.29.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[X] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I'm going to merge this since I don't think there will be too much interest.
Happy to respond to feedback should there be any.


Fix docs and run as part of travis build

Looks more consistent to me. :shipit:

LGTM

@kionka the sbt unidoc plugin is run as part of our release process


Godot Window Scales akward

Godot version
3.4.stable
System information
Ubuntu
Issue description
Godot scales at maximized mode very  just look at the picture..
Steps to reproduce
Install Godot on Ubuntu an make it Fullscreen...
Minimal reproduction project
No response

Duplicate of https://github.com/godotengine/godot/issues/31133. As a workaround, set the editor display scale to 75% in the Editor Settings or decrease the main font size to 12.


Max width NaN fix

This PR is related to issues described in #387
When a cell's maxWidth is NaN, the calculated style.maxWidth is "NaNpx". React won't update the DOM's style when given this value, resulting in incorrectly sized columns.
This PR ensures the maxWidth style is properly handled when maxWidth is NaN.
Note this PR also will add a button to the Controlled Component story to allow the user to reset the controlled state.

Nicely done :)

Cheers - awesome work on React Table. It's getting us much further than any other React-based grid out there.

Good to hear!
On Tue, Aug 1, 2017 at 9:29 PM ldstein<EMAIL_ADDRESS>wrote:

Cheers - awesome work on React Table. It's getting us much further than
any other React-based grid out there.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-table/pull/415#issuecomment-319557653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCXJMvqovHruqn2TtMWTG8qFbLagZks5sT-0HgaJpZM4OqjTi
.


Update flash_attn on pypi

Hello and thanks for all your hard work!  When you get a moment, would you be able to push 2.6.3 to pypi?  It seems to be stuck at 2.6.2.
Thank you!

Wheels are still building by github actions

Thank you!


added a gradient boosting algo from sklearn for the dataset

Gradient boosting is a machine learning technique for regression, classification and other tasks, which produces a prediction model in the form of an ensemble of weak prediction models, typically decision trees.

Nice, this should be good addition to the repository!


Cleanup CI warning

Most of the warnings are about using old macOS version it the matrix - we can just clean it, but can't fix it (we can but don't want to)

Superseded by https://github.com/valkey-io/valkey-glide/issues/2365


Fix environment particles.

You should also really update your references for this project. I did on my end just to compile it...but you really should in the project as well.

Thank you very much!


HALON-570: fix possible possible ignorance of the new drive.

Created by: qnikst

HALON-570: fix possible possible ignorance of the new drive.

In HALON-570 issued Smart request for the old drive instead
of a new drive, because drive candidate that was created in
HPI rule was never actualized. This happened because HPI
rule incorrectly decided that drive was powered on instead
of beign inserted.
Currently sspl:monitor-status-hpi rule doesn't check if drive
was changed or not, when decide what happen with disk.
That may lead to a problems when halon could make incorrect
decisions. The problematic case is:
0. Drive fails, marked as removed, etc.

SSPL-LL sends HPI event for some reason -> this leads to the
drop of the DriveRemoved status
SSPL-LL sends HPI event about new drive, beceuse there is
no drive removed status, halon decide that it's a repower.

The fix is to make halon aware if it was a new drive or not.
It seems it's not easy to fix 1. as HPI message is the only
source for drive insertion event, this means that if
monitor-drivemanager and hpi messages will be unordered, then
halon will miss drive insertion.

HALON-570: do not loose StorageDevice links when updating.

Mark device as present when it's a new drive.

Previously we did not do this.

Remove device identifiers from old disk.

Identifiers get added to the new disk by attachStorageDeviceReplacement,
so should be removed from the old disk before merge.

Add device path when not present.

Previously wasn't added in this branch, meaning replacement
drive didn't have the right path.

HALON-570: set correct path on drive-manager request.

When drive-manager request arrive halon find disk in the slot.
Previously halon attached path information to that drive, but
instead halon should check if there is a replacement for that
drives and attach path there.
When HPI event about new drive arrives HALON should not insert
id in enclosure field to candidate, otherwise drive-manager rule
may decide that disk is already inserted in the slot.
attachStorageDeviceReplacement can be called multiple times,
in such case no new replacement drive is created, instead we
just attach new identifier to that device.

HALON-570: update confd only when disk path is known.

Don't test that new SN is the same as old SN.

Closing as an obsolete


feat: update response and error handling

This commit updates response and error handling to bring them into conformance with error handling standards and practices.
I'll update the examples and the README files once this is merged and I can release a new version of the SDK.
Fixes #93

@pgautier404 this looks really nice at first glance!  There's more here than I will be able to take in today.  One thing that would be really helpful is if you could file a second PR that is just a "draft" PR that would show how the example code will change to correspond to these changes.
I'd like to have some combination of @bruuuuuuuce , @eaddingtonwhite , and @poppoerika take a look at the new API and see how it will feel, maybe even pull it down and kick the tires a bit.  But being able to show what the diff of the example code will look like I think will go a long way towards helping folks evaluate UX.

@pgautier404 this looks really nice at first glance! There's more here than I will be able to take in today. One thing that would be really helpful is if you could file a second PR that is just a "draft" PR that would show how the example code will change to correspond to these changes.
I'd like to have some combination of @bruuuuuuuce , @eaddingtonwhite , and @poppoerika take a look at the new API and see how it will feel, maybe even pull it down and kick the tires a bit. But being able to show what the diff of the example code will look like I think will go a long way towards helping folks evaluate UX.

Good idea: https://github.com/momentohq/client-sdk-javascript/pull/132.

@eaddingtonwhite is there anything here you think is a blocker or should we fast-follow the rest?


Allow the use of the association names for bindings

Currently there are two ways to specify the bindings when using Ecto.Query functions:

Positional binding
where(query, [x, y], ...

Named binding
join(query, ..., as: :some_name, ... # must be known at compile time

It would be nice to have an option so that one can specify the association names as the bindings:
where(query, [:posts, :comments], ...
I think the reason that Ecto currently doesn't allow that, is because an association can be joined multiple times. But in that case, it can simply be a documented known limit for that functionality, and someone willing to join an association multiple times would need to use the positional or named binding only.
The reason why I come up with this, is because it is not trivial to build dynamic composable queries with bindings based on position. The named binding was introduced, but the :as needs to be specified at compile time.

So I implemented this in master and I got failures in some apps because they were already setting that association to something else, and the conflict lead to failures. So unfortunately there is no way we can introduce this behaviour without breaking changes, sorry.


[NON CODE] Write a Socialmedia or Blog Post related to this repo

🚀 Feature Request
Is your feature request related to a problem? Please describe.

NON CODE CONTRIBUTION

Describe the solution you'd like

Hacktober 2022 allows to contribute with non code issues. Feel free to write a social media post or blog post. Link your posting in the comment section of this issue.

Describe alternatives you've considered

Additional context

@Gismo1337 Kindly assign me this issue.

@utkarsh006 Link published blogs here and i add them to https://github.com/Gismo1337/vue-cookie-consent-banner/wiki/Blogs for the hacktoberfest team to check valid contribute.

@Gismo1337 Kindly visit through my article. Hope you love it 😄
LINK TO THE ARTICLE

@Gismo1337 Kindly visit through my article. Hope you love it 😄
LINK TO THE ARTICLE

I do not see any commitment to this repo?!

@Gismo1337 Should I give your repo link in my article as a commitment ?

@Gismo1337 Means the above article is not valid?

@utkarsh006 What did you expect from writing this blogpost without any relation to this repo? May you can get in touch with the orga of hacktoberfest to talk about? Without any relation to this repo it's not qualified for us.

@Gismo1337 Buddy I am just asking that whether I include the link to this issue or repo in my article? If you're not clear with this, do make me that.


Monterey app not exiting properly

Intention

I'm submitting a bug report
Environment

Operating System: Ubuntu 16.04.2 LTS

Node Version: 6.5.0

NPM Version: 3.10.6

Monterey Version: 0.4.7-428

Description
Current behavior:
The monterey app keeps running even when closed by the close button.  The main window closes, but the application never completely exits until I press Ctrl-C in the terminal.
Expected/desired behavior:
The monterey processes should exit all by themselves.

@melbit-dannyw Thanks for your report. At the moment, it will not be acted upon - until we reassemble our development team.


[bug]: Board thumbnails not refreshing

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
RTX2080
GPU VRAM
8GB
Version number
3.7.0
Browser
Chrome latest
Python dependencies
No response
What happened
After deleting the top most image in one of the boards, the board thumbnail remains stuck on the now none existent image.
What you expected to happen
The board thumb to refresh onto the next available image in the board.
This also doesnt update after a full browser refresh, engine refresh, transient files clean. Nothing seems to reset it except creating a new image.
How to reproduce the problem
Create a board
Create some images
Delete the latest
Check the board thumbnail.
Additional context
No response
Discord username
No response

Hello! One year has passed since this bug report was opened. Have you installed the latest version of Invoke? Currently we are at version 5.4.3! Is the problem still persistent?
In the negative, and if there is no further feedback from the users, I would recommend to dismiss this bug report.


Various improvements

Thanks for contributing your project,
may I suggest some improvements?

Complete Unit test, and move the test class to a dedicated source tree (as per Maven best practice)
Add security tests
Configure JAXB plugin to add equals() and hashCode() to generated classes
Better exception handling
Fixed typo in class name
XML generation improvements, with proper name spaces so that the generated TCX can be parsed by other tools/services

Thanks for considering

Hey! Thanks for contribution! to be honest i didnt except this ;D


Can't work with DashsSope's OpenAI compatible mode API.

Bug description
There were two principal issues:

The DashScope API URL is https://dashscope.aliyuncs.com/compatible-mode. Simply replacing the OpenAI URL with this can cause the path to be lost. As a temporary fix, update both the base URL and the path:

url=https://dashscope.aliyuncs.com/
path=/compatible-mode/v1/chat/completions

The DashsSope's OpenAI compatible mode API is not fully compatible with the OpenAI API; its top_b parameter requires a value within the range (0.0, 1.0), whereas aicommit2 uses 1 as the default value.

aicommit2 version
v2.0.1
Environment
System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 91.25 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.local/share/mise/installs/node/20/bin/node
    npm: 10.5.0 - ~/.local/share/mise/installs/node/20/bin/npm
    pnpm: 9.7.0 - ~/.local/share/mise/installs/node/20/bin/pnpm
    bun: 1.1.12 - /opt/homebrew/bin/bun

Can you contribute a fix?

[X] I’m interested in opening a pull request for this issue.

@zybzzc Thank you for sharing the issue. I noticed that OpenAI's top_p parameter is a problem for you.
I don't know much about dashscope, so I can't think of an appropriate idea.
If url includes dashscope, should I remove the top_p parameter?

@zybzzc Regarding the first issue, the behavior you're observing is intentional. That's the right way to set it up.
For the second issue, I've added the OPENAI.topP option. If you set topP to 0, it will not be included in the request. Please see this
aicommit2 config set OPENAI.topP=0

@tak-bro Thank you! It works fine.


Errors in logs when scoping a go dynamic executable

We see the following in scope logs at the default log level:
Scope: readdir(pid:84578): [2022-03-16T14:46:33.330-0400] ERROR: get_file_size:open
Scope: readdir(pid:84578): [2022-03-16T14:46:33.330-0400] ERROR:unmap_all: file size

...when scoping this test application:
package main

import (
	"log"
	"os"
)

func main() {
	// Call syscall.Readdir
	_, err := os.ReadDir(".")
	if err != nil {
		log.Fatal(err)
	}
}

QA INSTRUCTIONS
(To run from source):
checkout this branch
make build CMD="make all" && make image
docker VERSION_ID is dev-x86_64
Part 1
Do:
docker run --rm -it cribl/scope:<VERSION_ID>
apt update && apt install -y golang curl
curl https://pastebin.com/raw/R8P7ZFuD -o test_app.go
go build test_app.go
file test_app
scope test_app
scope logs

Expect:

test_app is a statically-linked executable
No errors in the logs


Corrected parameter name in example 3

Docs Build status updates of commit 25a131f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azps-5.8.0/Az.Accounts/Get-AzAccessToken.md
:white_check_mark:Succeeded
View (azps-5.8.0)

azps-5.9.0/Az.Accounts/Get-AzAccessToken.md
:white_check_mark:Succeeded
View (azps-5.9.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Missing source mapping for automatically generated semi-colons

Describe the bug
The generated source maps do not include a mapping for automatically generated semi-colons. This results in source map libraries (e.g. source-map) to fail to map generated code back to the original code.
You may see the behavior in this visualization:

Input code
a()//?

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": false,
      "decorators": false,
      "dynamicImport": false
    }
  },
  "sourceMaps": true
}

Playground link
No response
Expected behavior
Source map would include a mapping for the automatically generated semi-colon back to the original code.
Actual behavior
No source map is generated for the semicolon
Version
<EMAIL_ADDRESS>Additional context
No response

Many thanks for the fast turn around on the issues that I raised yesterday. Over the coming weeks, we're looking to create a more comprehensive set of source mapping tests against swc for our products. We're hoping to do it in a way that we can share with you that you if that would be useful to you.

I tried fixing this, but I don't know what should semicolon point.

In the example above, in the parsed code (AST), the semi-colon is technically the end of the ExpressionStatement.
I'm not sure how swc internals work and whether this is possible, but is it possible to handle the same way as a multi-line comment?
Multi-line comment transform includes a mapping for the semi-colon:
a()/*?*/

to:
a() /*?*/ ;

//# sourceMappingURL=a.spec.js.map

I've also provided examples of Babel and TypeScript doing the same if that helps you identify how it should work:

Babel
TypeScript


Home page revisioning

According to ChatGPT:

The purpose of a homepage is to serve as the main entry point or initial landing page for a website. It typically provides an overview and introduction to the website's content, organization, and navigation options. The homepage often showcases key features, highlights important information or updates, and directs users to other relevant sections or pages within the website. Its goal is to provide a clear and engaging starting point for visitors, helping them navigate and discover the desired content or services the website offers.

We are missing all of the above :). This means @juliavdkris and @yustarandomname we are rewriting the home page to be more precise for new users. The new home page should include:

[ ] A short introduction about the purpose of the application (Both educational and game aspects) (Julia)
[ ] Ask Jonas if he still wants to be included on the website
[ ] Title image should include a turbine
[ ] Change to "Start Game" button

Include link to repo on the homescreen


Update mkdocs.yml

Updated Microsoft Flow to Power Automate reflecting product name changes

changed 'Microsoft Flow' to 'Power Automate'
moved all 'Power Automate cmds right after the 'Power Apps' cmds
renamed 'PowerApps' to 'Power Apps' as this is the product name

Closes #2259

Awesome job with the rename! Thank you so much! 👏


Uncaught TypeError: _laravelEcho2.default.channel is not a function

any idea ?

Instead Echo.channel try window.Echo.channel

@sugeng that fixed it , thanx but now i dont know how to view the data, there is no examples and the official doc have only for pusher , have u came by any tutorials using redis & echo ?


log densensitation in tiflash

Feature Request
Is your feature request related to a problem? Please describe:

Describe the feature you'd like:

In https://github.com/pingcap/tiflash/issues/1277, we introduce security.redact_info_log to replace the rowkey by ? in the tiflash logging.
TiDB introduce a "marker" mode for redact https://github.com/pingcap/tidb/issues/51306 since v8.1
Mark sensitive data with ‹..›. when security.redact_info_log=marker. Note that ‹ is not "less" < but U+2039. If the raw data contains ‹, ‹ will be escaped to ‹‹, similar to ›. This is a new feature:

TiFlash will produce logs with sensitive data marked with ‹..›
Cloud or OP users could desensitive logs on their own by tidb-server sub commands or whatever.

It is basically because that users want the original log, and we (primarily tech supports) should only see desensitived logs.
Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

[] client-c: https://github.com/tikv/client-c/pull/184
[] tiflash: https://github.com/pingcap/tiflash/pull/9136
[] docs update: https://github.com/pingcap/docs-cn/pull/17627


Unable to run flutter apps

FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Failed to install the following Android SDK packages as some licences have not been accepted.
build-tools;28.0.3 Android SDK Build-Tools 28.0.3
platforms;android-29 Android SDK Platform 29
To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

Using Android SDK: C:\Users\jhaym\AppData\Local\Android\sdk

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2m 7s
Exception: Gradle task assembleDebug failed with exit code 1

It seems Docs on --licenses is missing. accept the license before build.
Have a look on this branch of stack overflow.
for windows:
%ANDROID_HOME%/tools/bin/sdkmanager --licenses
Mac OS:
export JAVA_HOME=/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home
yes | ~/Library/Android/sdk/tools/bin/sdkmanager --licenses

I hope your issue is clear.
Thankyou.

@jhaymesdev
As the error log says:
Failed to install the following Android SDK packages as some licences have not been accepted. build-tools;28.0.3 Android SDK Build-Tools 28.0.3 platforms;android-29 Android SDK Platform 29 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
Please follow the leads mentioned in the error and install the components and then try again to see if it works.

It seems Docs on --licenses is missing. accept the license before build.
Have a look on this branch of stack overflow.
for windows:
%ANDROID_HOME%/tools/bin/sdkmanager --licenses
Mac OS:
export JAVA_HOME=/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home
yes | ~/Library/Android/sdk/tools/bin/sdkmanager --licenses

I hope your issue is clear.
Thankyou.

It seems Docs on --licenses is missing. accept the license before build.
Have a look on this branch of stack overflow.
for windows:
%ANDROID_HOME%/tools/bin/sdkmanager --licenses
Mac OS:
export JAVA_HOME=/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home
yes | ~/Library/Android/sdk/tools/bin/sdkmanager --licenses

I hope your issue is clear.
Thankyou.

@darshankawar and @swebreza

@swebreza and @darshankawar thank you so much I really appreciate your help you both are live savers. Big thank you again

It seems Docs on --licenses is missing. accept the license before build.
Have a look on this branch of stack overflow.
for windows:
%ANDROID_HOME%/tools/bin/sdkmanager --licenses
Mac OS:
export JAVA_HOME=/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home
yes | ~/Library/Android/sdk/tools/bin/sdkmanager --licenses

I hope your issue is clear.
Thankyou.

It seems Docs on --licenses is missing. accept the license before build.
Have a look on this branch of stack overflow.
for windows:
%ANDROID_HOME%/tools/bin/sdkmanager --licenses
Mac OS:
export JAVA_HOME=/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home
yes | ~/Library/Android/sdk/tools/bin/sdkmanager --licenses

I hope your issue is clear.
Thankyou.

Thank you so much @swebreza and @darshankawar for your help this was so helpful it's running fine now. Thank you so much you are both life savers .Thank you soo much

@jhaymesdev
Given your last comment, I am going ahead and closing this as resolved.
Thanks.


How should I save keypoints in npy format?

How should I save keypoints in npy format?

Hi, thank you for the interest.
Do you mean np.save()?

Where to print keypoints and how to export MP4 video files to 3D NPY format to save keypoints

您好，感谢您的关注。
你的意思是np.save()?
I want to convert the video like this and save it as Npy:

The file should contain an array with shape 15 x 2 x length.
The first dimension (15) corresponds the 15 body joint defined here.
The second dimension (2) corresponds to x and y coordinates.
The third dimension (length) is the temporal dimension.

Hi, is this #10 related to this issue ?

嗨，这个#10与这个问题有关吗？

Ok, thanks. I'll try it. I'd like to convert video to https://github.com/yzhq97/transmomo.pytorch is required in the input skeleton sequences .npy file


14.1 Importing icons -- Importing Issue and Solution

I complied the application guideines to complete the installation and downloading Icons8App. However, I have met an extracting error and have had the following solution.
Installation
$ pip install plyvel
$ pip install svglib,
$ sudo apt install p7zip-full
Download Icons8App
And download the from the weblink of https://icons8.com/app. Icons8App_for_Mac_OS.dmg is saved in the Downloads file.
Issue -- Open Errors: 1
During executing the command $ 7z x Icons8.app, it shows Open Errors: 1. Please see the details as follows.
$ cd Downloads
~/Downloads$ 7z x Icons8App_for_Mac_OS.dmg
~/Downloads/Icons8 v5.7.2$ 7z x Icons8.app
Would you like to replace the existing file:
Path:     ./__TEXT__text
Size:     318885 bytes (312 KiB)
Modified: 2019-12-25 18:18:20
with the file from archive:
Path:     __TEXT__text
Size:     68631 bytes (68 KiB)
? (Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? N
After random choosing the above-mentioned option, it shows the error.
Archives: 295
OK archives: 34
Can't open as archive: 260
Archives with Errors: 1
Open Errors: 1
After analyzing the error, I know that some files have redundant content. It is the source of the error.
Solution:
It is necessary to change to the absolute path to extract the file of  icons-db4. It avoids the extracting error.
$ cd Downloads
~/Downloads$ 7z x Icons8App_for_Mac_OS.dmg
~/Downloads$ cd Icons8\ v5.7.2
~/Downloads/Icons8 v5.7.2$ cd Icons8.app/Contents/Resources
~/Downloads/Icons8 v5.7.2/Icons8.app/Contents/Resources$ tar -xvf icons.tar.gz
c/
icons-db4/000006.log
icons-db4/LOCK
icons-db4/000005.ldb
icons-db4/CURRENT
icons-db4/LOG
icons-db4/MANIFEST-000004
icons-db4/LOG.old
After executing the above-mentioned commands, it show a success. After running the example application, it generates icons (directory: home/user/icons)in the home directory. The icons file holder includes index.json that will be used in ### 14.2 Icon Autoencoding.
Notes:
In the In [6] sectionl, it shows the message as follows.
Can't handle color: url(#LP0GfCD4bXLuDCmAsJT~Ia)
I do not know how to solve the issue.

Hi,
Thanks for all your detailed notes. I think most of it springs from running this on tensorflow 2.0. The mundane truths is that my local machine with my GPU so far only runs upto 1.14 and so that is what I have been going through. DId you want to make sure this all works on 2.0 or would it work for you to just use the versions from requirements.txt?
Thanks!

Never mind.

Anyway, it is the issue that I met. I have solved it for your information. Cheers!


Add ingress/egress default deny tests for CNP

Currently we only have tests for KNP default deny. We should add coverage for CNP default deny as well.

See cilium/test/k8sT/manifests/knp-default-deny-egress.yaml and knp-default-deny-ingress.yaml


[release-0.17] Auto-update dependencies

Produced via:
./hack/update-deps.sh --upgrade && ./hack/update-codegen.sh
/assign ZhiminXiang tcnghia
/cc ZhiminXiang tcnghia

/hold
I am not sure if we want to cause a release just because of a vendor change in test-infra
cc @nak3 @ZhiminXiang

If this is the only for test-infra update, I think we should close this one.


[Support] config issue

Hello, I am trying to get Checkrr running but running into this issue that it is not binding to a real port. I have tried config with and without the webserver section.
Docker-Compose:
  checkrr:
    container_name: checkrr
    image: aetaric/checkrr:latest
    volumes:
      - $DOCKER_PATH/checkrr/config/checkrr.yaml:/etc/checkrr.yaml
      - $DOCKER_PATH/checkrr/config/checkrr.db:/checkrr.db
      - drivepool:/media
    ports:
      - 8585:8585
    restart: unless-stopped
    labels:
      autoheal: $AUTOHEAL_RESTART

$DOCKER_PATH~=/mnt/A6C117D287988134/docker
drivepool is a Mount to NAS
Config File
checkrr:
  checkpath:
    - "/Anime/"
    - "/Anime Movies/"
    - "/Documentary/"
    - "/Movies/"
    - "/Movies 4k/"
    - "/Reality_TV/"
    - "/Standup/"
    - "/TV Shows/"
    - "/TV Shows 4K/"
  database: ./checkrr.db
  debug: true
  csvfile: ./badfiles.csv
  logfile: ./checkrr.log
  logjson: false
  cron: "@daily"
  ignorehidden: true
  webserver:
    port: 8585
    tls: false
    baseurl: "/"
    trustedproxies:
      - <IP_ADDRESS>

            _|                               _|

   _|_|_|   _|_|_|       _|_|       _|_|_|   _|  _|     _|  _|_|   _|  _|_|

 _|         _|    _|   _|_|_|_|   _|         _|_|       _|_|       _|_|

 _|         _|    _|   _|         _|         _|  _|     _|         _|

   _|_|_|   _|    _|     _|_|_|     _|_|_|   _|    _|   _|         _|

Checkrr version 3.4.0

 Commit: f7f3f46a56bf2d014aa5b0a7c9bf6e1a5fc132c5

 Built On: 2024-10-09T21:07:59Z

 Built By: goreleaser

time="2024-10-11T14:40:28Z" level=info msg="Using config file: /etc/checkrr.yaml"

[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

 - using env:	export GIN_MODE=release

 - using code:	gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /api/files/bad            --> github.com/aetaric/checkrr/webserver.getBadFiles (4 handlers)

[GIN-debug] POST   /api/files/bad            --> github.com/aetaric/checkrr/webserver.deleteBadFiles (4 handlers)

[GIN-debug] GET    /api/stats/current        --> github.com/aetaric/checkrr/webserver.getCurrentStats (4 handlers)

[GIN-debug] GET    /api/stats/historical     --> github.com/aetaric/checkrr/webserver.getHistoricalStats (4 handlers)

[GIN-debug] GET    /api/schedule             --> github.com/aetaric/checkrr/webserver.getSchedule (4 handlers)

[GIN-debug] POST   /api/run                  --> github.com/aetaric/checkrr/webserver.runCheckrr (4 handlers)

[GIN-debug] Listening and serving HTTP on :0

Not really sure what is wrong, if I could get some inpuit that would be very helpful. Project looks great.

I would also suggest you not use the logfile directive or the csvfile directive at all inside docker as the files will be stuck inside the container unless you mount the files to a file on the host.
It would be best to use one of the notification services to get bad files reported to you instead of the csv and just use docker logs checkrr for the logs as you did to get the output to diagnose the port issue.

Thanks, for the help. I'll try all this. I am planning on hooking up Discord to my personal server once I get stuff running.

Webserver working now. Thanks for the help. I'll close this ticket


KeyError reading yaml file

yaml file:
mylist:
  - 1
  - 2
  - 3

with open("config/aa.yaml","rb")as f:
     data.load(f,'yaml')

---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
Input In [21], in <module>
      1 with open("config/aa.yaml","rb")as f:
----> 2      data.load(f,'yaml')

File ~/anaconda3/envs/py3/lib/python3.9/site-packages/tablib/core.py:414, in Dataset.load(self, in_stream, format, **kwargs)
    411 if not import_set:
    412     raise UnsupportedFormat(f'Format {format} cannot be imported.')
--> 414 fmt.import_set(self, stream, **kwargs)
    415 return self

File ~/anaconda3/envs/py3/lib/python3.9/site-packages/tablib/formats/_yaml.py:32, in YAMLFormat.import_set(cls, dset, in_stream)
     29 """Returns dataset from YAML stream."""
     31 dset.wipe()
---> 32 dset.dict = yaml.safe_load(in_stream)

File ~/anaconda3/envs/py3/lib/python3.9/site-packages/tablib/core.py:341, in Dataset._set_dict(self, pickle)
    338     return
    340 # if list of rows
--> 341 if isinstance(pickle[0], list):
    342     self.wipe()
    343     for row in pickle:

KeyError: 0

Please can you give a complete, minimal, self-contained Python script which reproduces your problem?
Tips here: https://stackoverflow.com/help/minimal-reproducible-example

tablib expects a yaml content structured with headers, like:
- {first_name: John, gpa: 90, last_name: Adams}
- {first_name: George, gpa: 67, last_name: Washington}

The docs could be more explicit and the error message in case of failure, too.

I have the same issue. Minimal code for reproduction:
props.yaml:
title: Voice of Miki Vanoušek

And the python code:
import tablib
with open('props.yaml', 'r') as f:
    podcast_properties = tablib.Dataset().load(f)


Merge pull request #103 from oasis-open/master

Please generate the read-the-docs and review them, in addition to reviewing the code

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@75e8b00). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #104   +/-   ##
=========================================
  Coverage          ?   72.29%
=========================================
  Files             ?       12
  Lines             ?     3162
  Branches          ?        0
=========================================
  Hits              ?     2286
  Misses            ?      876
  Partials          ?        0

Continue to review full report at Codecov.

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

@emmanvg and @gtback:
I'm not exactly sure what happened.  I tried to separate the doc and code commits, and got into a heap of trouble.  Actually, I think I inadvertently committed these changes to the master branch already :-(.
Anyway - the code commit is 7a9633d and the doc commits are https://github.com/oasis-open/cti-stix-elevator/commit/242ea744f1aed5c17ad2526e43073355979f33ed, and https://github.com/oasis-open/cti-stix-elevator/commit/3f7da73735f3dfae4988dffbac5906864507ff50
I guess the best way to review the docs is to run "make html" and review the local files?
Also, @gtback - do we just update the read-the-docs site by hand once this PR is merged in?

Somehow git got confused; the only changes in this PR are to setup.py, and aren't changes we want (I don't think).
@rpiazza, ReadTheDocs should detect any commits to the master branch (via a webhook) and rebuild the documentation automatically.

@gtback I think we do need these changes. Look at the setup file in master https://github.com/oasis-open/cti-stix-elevator/blob/master/setup.py. It has duplicate entry_points and install_requires

Good catch @emmanvg ! I didn't realize it was duplicated.