ES crashes if gamelist is too long in Chinese or Japanese with character/kanji.

This issue also happens in RetroPie ES. But I think it's better to open an issue here since Batocera supports Chinese without any extra operation. If users use a long game list with over 2K or so games, and if game list is in Chinese or Japanese with many many characters coded in 3 bytes, ES would crash when scrolling down the game list for a little longer. The higer resolution is, the sooner ES crashes. ES just quits with SIGSEV signal.
ERROR    Interrupt signal SIGSEGV received.
Maybe there is a memory leakage on font caching?

I'm sorry but I'm not Chinese, and I don't have big gamelists in Chinese...
I can't help without it.

If you have a full mame set is rather easy to set it in Chinese, I can. Send the files needed (I am also not Chinese but I tested this bug)

i've not a such set.
but an easy way is to replace files by empty files with the same name in roms while the content is not necessary to es and zip the result.

That could work, here are the files needed cn_mame.zip, the mamenames.xml goes into the resources folder and the gamelist.xml is for the roms/arcade (might work on others with <platform>arcade</platform>)

More info on this issue, I compiled a debug version and I ran gdb on it this is the result:
Thread 1 "emulationstatio" received signal SIGSEGV, Segmentation fault.
0x005be074 in Font::renderTextCache (this=0x1832b20, cache=0x29ae6e0) at ../es-core/src/resources/Font.cpp:441
441	../es-core/src/resources/Font.cpp: No such file or directory.
(gdb) bt
#0  0x005be074 in Font::renderTextCache (this=0x1832b20, cache=0x29ae6e0) at ../es-core/src/resources/Font.cpp:441
#1  0x0042c464 in TextListComponent<FileData*>::render (this=0x182f6d4, parentTrans=...) at ../es-app/src/components/TextListComponent.h:235
#2  0x00504ea8 in GuiComponent::renderChildren (this=0x182f218, transform=...) at ../es-core/src/GuiComponent.cpp:75
#3  0x00437774 in IGameListView::render (this=0x182f218, parentTrans=...) at ../es-app/src/views/gamelist/IGameListView.cpp:57
#4  0x004686f8 in ViewController::render (this=0xa92e88, parentTrans=...) at ../es-app/src/views/ViewController.cpp:539
#5  0x00550594 in Window::render (this=0xffd0ba3c) at ../es-core/src/Window.cpp:453
#6  0x002a6f98 in main (argc=1, argv=0xffd0c714) at ../es-app/src/main.cpp:598

Hopefully it can help

Thanks, so : probably due to the fact a Glyph is not found anywhere in fonts.
As I can't reproduce : I "try" a fix to avoid assertion and continue without drawing in this case.

I noticed this error is when you are fast scrolling and the current letter pair is shown on the dimmed screen. Maybe there is a way to ignore displaying the Glyph if it doesn't exists?
Let me know if you need anything else to debug/test

@fabricecaruso I applied your patch (from your PR) and unfortunately (and weirdly) It is still the exact same error:
Thread 1 "emulationstatio" received signal SIGSEGV, Segmentation fault.
Font::renderTextCache (this=0x19e1e48, cache=0x2b36140) at ../es-core/src/resources/Font.cpp:441
441	../es-core/src/resources/Font.cpp: No such file or directory.
(gdb) bt
#0  Font::renderTextCache (this=0x19e1e48, cache=0x2b36140) at ../es-core/src/resources/Font.cpp:441
#1  0x0042c6fc in TextListComponent<FileData*>::render (this=0x284df1c, parentTrans=...) at ../es-app/src/components/TextListComponent.h:235
#2  0x00505140 in GuiComponent::renderChildren (this=0x284da60, transform=...) at ../es-core/src/GuiComponent.cpp:75
#3  0x00437a0c in IGameListView::render (this=0x284da60, parentTrans=...) at ../es-app/src/views/gamelist/IGameListView.cpp:57
#4  0x00468990 in ViewController::render (this=0xc46f10, parentTrans=...) at ../es-app/src/views/ViewController.cpp:539
#5  0x0055082c in Window::render (this=0xff9d5b0c) at ../es-core/src/Window.cpp:453
#6  0x002a6f98 in main (argc=1, argv=0xff9d67e4) at ../es-app/src/main.cpp:598

Honestly, this one was crazy to find...
This should be fixed ( see the commit in my "fix" branch ) & soon be merged.

@fabricecaruso Thank you!

@fabricecaruso after testing the fix, altho it does not crash anymore it seems the fonts go crazy. Here is a video to demonstrate the problem
https://youtu.be/z1QFgPV4B1s
(I only tested the one commit that fixed the issue, not sure if I need the others as well)

WOAW very impressive in action this bug !!!

Still better than a crash.... And very very very very very hard to debug ( try it.... )
1,386 billion people in china, no one to help debug it ????

even tho I am not Chinese I wish I knew how to debug it so I could help more :( I can imagine is a nightmare to debug since its a very weird bug.

I can imagine is a nightmare to debug

Yes it is ! & I have some other priorities

Then I assume it would be better to revert this fix? , until someone could help you more on this issue since once it happens the only way to recover the fonts is to restart ES

Why... ? It avoids a crash....

Yes, I think your fix is on the right direction, but If you notice in the video, once the error happens all text disappears, not just Chinese characters, its only fixed with an ES restart.

The "i++;" is absolutely necessary... Why revert this ? If we revert this, the day we'll do more debugging we'll loose time searching for the "i++" again....

You are right, this can lead for easier debugging in the future without worrying about that part.
I hardly know anything about C++ so what I say its just opinions on the matter, just trying to help and reduce the workload.
But really, thanks for your hard work on this I appreciate it.


cutoff-solver should error when 3D-haloing doesn't cover full cutoff distance.

This becomes an issue when strong-scaling the problem. When each rank owns a smaller portion of the mesh, the maximum cutoff distance becomes progressively smaller. This effects the accuracy of the model because fewer points are considered neighbors for the zdot solve.

Not sure this is an issue so much as a limitation of the approach. The real issue is that the code should check for this limitation at startup and fail properly (e.g. by throwing an exception) if the requested cutoff distance is infeasible given the mesh size. Maybe just edit the issue to note this if it's not currently done?

Fixed by #98


feat(app): complete error handling for calibration on Opentrons Flex

closes RLIQ-385
Overview
Previously, when calibrating a pipette, there is erorr handling when attaching the probe. However, there is no way to detach the probe. Now, when you run into that error, it prompts you to detach the probe and then exits the flow.

Test Plan

test on both desktop app and ODD. Go through calibration, when an error occurs when executing the calibratePipette command, there is now an error modal with information about the error, then prompting the user to hit the next button and then showing the detach probe page. Once you hit "exit calibration", the robot homes and closes the flow. Should be the same for both ODD and desktop.

Changelog

create error modal CalibrationErrorModal. Change logic in AttachProbe to show modal when there is an error and then clicking on next shows DetachProbe with no back button and proceeds to exit.
add logic to PipetteWizardFlows to show correct wizard header info when exiting from calibration error
fix tests

Review requests
see test plan
Risk assessment
low

@ecormany, thoughts on what the modal should say? The one attached in this pr. The modal pops up if you run into an error when attaching the calibration probe. The subheader is the error string. What should the header say?

The subheader is the error string. What should the header say?

I think we can keep it simple: Pipette calibration failed
This PR may not address it, but the subheader should give context like Detach the probe from the pipette and try calibrating again.


Option to display Time & Remaining Battery

Describe your suggested feature
An option that would allow displaying the time and remaining battery with the page count at the bottom of the screen.
This feature would allow users to check the time and remaining battery without having to swipe from the top of the screen to show the notification bar.
Other details
The requested feature is a functionality that is present in e-book reader apps like Moon+ Reader.

Acknowledgements

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

inb4 Antsy's standard "Don't be lazy" response because it only takes a single tap on the screen or disabling the FullScreen Mode setting to see that information xD


Transfer ownership

Hello @amiga-500 !
Would you welcome https://github.com/amiga-500/w3-total-cache-fixed ?

+1 for @amiga-500, is the most active user in this project.
but what happen to the tons of links everywhere? github redirect all links?

github redirect all links?

We had a name change. Do you remember?

Sorry for the delay @szepeviktor .  I wanted to finish up things in this repo before catching up in this section.  I usually get distracted easily and jump on a tangent when i see something new.  :stuck_out_tongue_winking_eye:

Would you welcome https://github.com/amiga-500/w3-total-cache-fixed ?

Hey that's a nice offer.   But sadly, I am putting this project aside for a few months (starting right now) so I figure its best to stay with you until I get back into the flow of things down the road. :racehorse:

github redirect all links?
We had a name change. Do you remember?

Yup, if it were switched all links should redirect correctly.  Of course, hardcoded links should ideally be manually modified over time to point to the new area (e.g., v094x's updater links) since there is no point having them go through 301 redirects each time.
Prior to leaving i wanted to get in the remaining new bug fixes and push out new releases for v0.9.5.x and v0.9.4.x which i've now done.  For v0.9.5.x we now have 30+ bug fixes/new features/updates after just a month since the official v<IP_ADDRESS> release :tada:
It's been really fun working with you, @nigrosimone, @charlesLF,  twiginteractive, thebeline, and the others.
Because this place can be an addictive distraction i've actually disabled my alerts just now so i don't feel compelled to jump back in while doing my medical work.
The wiki page (and front page) has been updated with all of our changes up to this point so Frederick (and other visitors) can see.  Frederick was previously made aware of this page by @nigrosimone.  Upon a new official release that wiki page should ideally be stripped of its list (assuming that all, or most, are now integrated into the next official release) and started all over again.
Talk to you all in the future,
Kimberly :octocat:

Thank you.

I am putting this project aside for a few months [..] while doing my medical work

@amiga-500 this make me sad, i think your contribute in this project is absolutely important, without you will be hard have the same result. You have helped tons of users and fix tons of bug, but your real life is most important, always thanks for all and best wishes for your new job!!
i'm just a bit curious about your life, i think you are a very qualified developer, why you work in the medical instead of web/software house? :)
I hope to see you again, soon.

Thank you @amiga-500 for being so awesome; best of luck to you & hope to see you return to the project in future :)


Instrumentation gives a Never NullabilityNodeInfo for ! fixes

Every NNBD migration ! fix, e.g.
parent._children[name] = this;

// to:

parent!._children[name] = this;

has a NullabilityNodeInfo on its reason that is never. Because of this, we cannot do equality checks, or distinguish between these nodes. In the instrumentation rendering, we end up pointing the user to a random never node.

This has been addressed.


add license

adding  open-source license to project so that other people who use our code cannot use for commercial purpose.

closed via 9f70af0736741b65922d59ef25c33e76943d7fe9


fix: fix build error with adding await to loadConfig

@thomvaill Can you review it?

Thank you @peacecwz !


Ability to not have a named command be interrupted when path ends

Is your feature request related to a problem? Please describe.
For some paths, I have commands that are meant to run between paths, such as intaking, spinning a shooter, etc. However, when there's event markers for commands like intaking at the end of a path, they are interrupted when the path ends, which will prevent them from running for the duration they need to run.
In the case of the intake, I want the command to run until either a sensor is triggered or it hits a timeout. Having it stop when the path ends prevents it from fully intaking the note.
Describe the solution you'd like
Add a second method for registering a command that takes in a parameter for whether or not it should be interrupted when a path ends. For safety reasons, this parameter can default to true. An example of how this method will be used is:
NamedCommands.registerCommand("Intake", intake.intakeUntilSensor().withTimeout(2.5), false);

These paths don't have a non-zero end velocity, they stop at the piece and the next path moves them to a shooting spot. Does this edge case still apply?

Maybe not for your use case but for others. Basically I'm saying it would be possible to put an event marker for a "non interruptible" command in a path that is supposed to end with a non-zero velocity. There's really no choice but to still interrupt that command in that case.

I'm very confused, does the command only get interrupted in my use case where the end velocity is 0?

it would be possible to put an event marker for a "non interruptible" command in a path that is supposed to end with a non-zero velocity

Does this already exist or is it something that could exist?

There's really no choice but to still interrupt that command in that case.

For my case or the one non-zero velocity case?

For the non-zero end vel case. For those paths, the robot would need to transition to the next path immediately. Otherwise, it would just keep driving while waiting for commands to end.
Also, this isn't really doable on a per-command basis when registering like that because of the structure of how event marker commands get built.  It would have to be on a per event marker basis with a check in the GUI or something.
Honestly, your best bet is probably just to continue whatever you want to keep running when doing commands in between paths. So for instance, have an event marker that runs the intake, then after following that path, add another command that runs the intake and waits for your sensor/timeout. That's what we've done personally last year. I also think that its more readable that way. Then you know that there will be something running between paths instead of some event marker somewhere causing a delay between paths that isn't obviously visible.

There used to a Schedule command that was good for situations like this.  We have used it in the past when we had a problem of commands running conditionally from inside other commands, which would cause interrupts and cancel the whole command group.
I know this is not the same situation for you, but I think it might solve your problem. I think they are called Proxy Commands now.  Maybe you can have a command in your command map that runs at a marker at the end of your path (either at the 0.99 or 1.0 mark) and from inside its logic (ie in the command init function) it launches the command/s you want to run as proxy commands. (ie openIntake, or intakeUntilLoaded,etc).  Then if the command group from path following ends because the path ended, it won't matter as the intake command will continue to be running as a separate command in the scheduler, not a part of the path following group.
You might probably find that launching the proxy will interrupt the whole group due to intake requirements if the intake is used somewhere else in the path following, but this shouldn't matter as path following was about to end anyway.
Food for thought.

I think this would be possible with #676, so I'll close this in favor of that solution.


CloudEvent Tracing Compliance

The Knative Channel Specification specifies the expected behavior of handling W3C Tracecontext headers.  The current implementation does NOT meet these requirements in that the traceparent and tracestate headers are lost in transmission.  A completely new traceparent value is instead sent to the subscriber.
Currently, the Knative In-Memory Channel reference implementation DOES adhere to the specification, but the eventing-contrib/kafka implementation does not.  Similar to this implementation the latter has the intermediate step of persisting to/from a Kafka Topic.  There is currently confusion and a debate around the best way to handle this persistence, how it relates to the potential use of ce-traceparent and ce-tracestate, and where in the Knative / CloudEvent stack to handle this.  Further, it is unclear whether the CloudEvents DTE Extension is useful or not.
See the following Github Issues/PRs for the history...

Knative / CloudEvents

https://github.com/knative/eventing/issues/2918 & https://github.com/cloudevents/spec/issues/603 & https://github.com/cloudevents/spec/pull/607

eventing/in-memory

https://github.com/knative/eventing/issues/1757

eventing-contrib/kafka

https://github.com/knative/eventing-contrib/issues/1139 & https://github.com/knative/eventing-contrib/pull/1155
https://github.com/knative/eventing-contrib/issues/563

Previous Knative Implementation Removal

https://github.com/knative/eventing/pull/2873

Therefore, we are going to wait until this is resolved before attempting to implement a solution that complies with the expected specification.
There are also larger tracing issue to be dealt with within the Knative Eventing ecosystem such as how to integrate Istio B3 Header usage with the current OpenTelemetry Headers. See https://github.com/knative/eventing/issues/2581.
W3C Tracecontext Notes

The traceparent field is composed of the following values...
<version> - <traceid> - <parentid> - <flags>

...where the <version> (usually 00) specifies the format of the following data fields, and the <traceid> is the end-to-end ID of the entire trace through a distributed system.  The <parentid> is also referred to as the <spanid>, and can/should change with each new HTTP Client Request being made.  Therefore the expectation is that when the Channel receives an HTTP request with a traceparent header, that it is forwarded to the Subscriber with the same traceparent header, albeit with a new <parentid>.

Closing all issues as project is going to be archived. If it is still valid create a new issue in https://github.com/knative-sandbox/eventing-kafka


Add more languages

Add more languages in order to support a broader audience.

Can i help you to translate with spanish?

Can i help you to translate with spanish?

Sure, you can make a PR with a localization for spanish.
You'd just need to use app/lang/en as base and copy it to app/lang/es and translate the english phrases.

I'm like 90% done with the Dutch translation, but how do I get to preview the language to see it in action? It's in a separate directory de/en/nl but the language doesn't show up on the settings panel.

Do you have the following files in place?
/app/lang/nl/app.php
/app/lang/nl/errors.php
/app/lang/nl/tb.php

And did you set the _language_ident token in your /app/lang/nl/app.php?

Hi, I have a Spanish translation ready to upload. How may I proceed? Thanks

Hi, you can make a pull request via GitHub, so I can review it. Basically you'll need to fork the repository, make your changes and then create a PR on GitHub. On successful review I can then merge your changes into the repository.

Info: We are still looking for translations into languages like french, italian, portugese, norwegian, dutch, swedish, and others you may want to localize.

For the next v3.2 add french translation: #223

Question: Most of my plants are outside in traditional and raised bed gardens so I did a fork and I am working on a last_weeded attribute. I was looking at the translations and didn't know if I needed to do them for my change or not. I used online translators to find the best ones for the da,de and es translations but I am not sure if I should do those or not?

Sorry Daniel I didn't really explain that properly. I didn't mean the name of the attribute but the translations within the app/lang/?? files. Like this:
For the Danish translations:
app/lang/da/app.php

'last_weeded' => 'Sidste træk ukrudt',
'sorting_type_last_weeded' => 'Sidste træk ukrudt',
'calendar_class_weed' => 'Ukrudt',
'set_weeded' => 'Sæt ukrudt trukket',
'bulk_set_weeded' => 'Sæt planter til ukrudt trukket',
'confirmSetAllWeeded' => 'Er du sikker på, at du vil opdatere den sidste ukrudtsdato for alle disse planter?',
'all_plants_weeded' => 'Sæt planter til ukrudt trukket',

Similar for the app/lang/de/app.php and app/lang/es/app.php files
The English file app/lang/en/app.php would contain:

'last_weeded' => 'Last weeded',
'sorting_type_last_weeded' => 'Last time weeded',
'calendar_class_weed' => 'Weeding',
'set_weeded' => 'Set weeded',
'bulk_set_weeded' => 'Set plants to weeded',
'confirmSetAllWeeded' => 'Are you sure you want to update the last weeded date of all these plants?',
'all_plants_weeded' => 'Last weeded status has been updated for these plants.',

My question is I know I have to do the English en/app.php file but do I also do the translations for those da,de,es and now fr app.php files using online translators (and hopefully have someone check them later) or do I leave them and they get done under a different issue/pull request or something else?
As seen above I have already done them for everything except the French so they would just need to be checked by someone (I would also do the French using online translators). Would I open a separate issue as enhancement and then submit them separately? Just trying to figure out the best process for getting the translations done for an enhancement like this.
Sorry for the confusion and thanks,
Brian

Ok, what kind of attribute is yours? A custom one or did you implement a
default attribute?
Generally translations are optional. You'd only translate phrases that you
need (in the context of your own custom fork).
If there is no translation found then it just returns the phrase identifier.

"Ok, what kind of attribute is yours?"
I am working on an attribute for last_weeded (like last_watered, last_repotted and last_fertilised) for outdoor gardeners. I was hoping that it might be useful to others and I would generate a pull request to see if you are interested.
When I was testing it before I had added a button for setting plants to weeded and that is what made me find out that buttons did not hide when the attribute was unchecked.
I am going to make the changes to the updated code in my repo and then submit a pull request. If you like the idea you can add it and if you don't find it useful I can keep it in my own repository.

Ah, I see. Tho I have decided to not include any further default
attributes, because it can be subjective what default attribute is useful
to what party. While I agree that last weeded is definitely useful for
outdoor gardening, it is something that most indoor plant parents would
most likely not use (the initial target audience for HortusFox). That's why
the best approach would be to just use a custom attribute to fit the
specific needs of the user. I appreciate the work you put behind that, but
I'd have to reject that PR, unfortunately. But of course you can use it on
your own fork!
Regarding your initial question: If you want to translate last_weeded for
your fork, then you can add it to the other language files. When you are
using the localization helper like __('app.last_weeded') the underlying
framework will try to find a translation for the current language of the
client. If it doesn't find a translation phrase then it will return the
related identifier like app.last_weeded.
I don't know what your native language is, but as a workspace admin, you
can also specify the default language of your workspace. Tho users can
change their own language in their preferences.
I hope this helps, please let me know if you have further questions.
Message ID: @.***>

Okay. I understand and thank you for letting me know.
Regards,
Brian

Further languages need their own issue/PR.


fix:api_client:Handle 'None' smart meter consumption

tldr; Fix ERROR (MainThread) [custom_components.octopus_energy.coordinators.current_consumption] Unexpected error fetching current_consumption_44-11-XXXXXXXXXX data: float() argument must be a string or a real number, not 'NoneType'

I had my smart meter installed today + Octopus Mini setup. I immediately looked at integrating it with Home Assistant. Whilst most of the setup went fine, Home Assistant would display the following error:
homeassistant-1  | 2024-02-27 15:44:30.872 ERROR (MainThread) [custom_components.octopus_energy.coordinators.current_consumption] Unexpected error fetching current_consumption_44-11-XXXXXXXXXX data: float() argument must be a string or a real number, not 'NoneType'
homeassistant-1  | Traceback (most recent call last):
homeassistant-1  |   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
homeassistant-1  |     self.data = await self._async_update_data()
homeassistant-1  |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  |   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 269, in _async_update_data
homeassistant-1  |     return await self.update_method()
homeassistant-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  |   File "/config/custom_components/octopus_energy/coordinators/current_consumption.py", line 81, in async_update_data
homeassistant-1  |     hass.data[DOMAIN][account_id][key] = await async_get_live_consumption(
homeassistant-1  |                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  |   File "/config/custom_components/octopus_energy/coordinators/current_consumption.py", line 39, in async_get_live_consumption
homeassistant-1  |     data = await client.async_get_smart_meter_consumption(device_id, period_from, period_to)
homeassistant-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  |   File "/config/custom_components/octopus_energy/api_client/__init__.py", line 660, in async_get_smart_meter_consumption
homeassistant-1  |     return list(map(lambda mp: {
homeassistant-1  |            ^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  |   File "/config/custom_components/octopus_energy/api_client/__init__.py", line 661, in <lambda>
homeassistant-1  |     "consumption": float(mp["consumptionDelta"]) / 1000,
homeassistant-1  |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant-1  | TypeError: float() argument must be a string or a real number, not 'NoneType'

Handling the float() value and returning 'None' wasn't ideal as more failures would happen down the line; functions wouldn't expect to get a 'None' consumption. So it was better instead to skip any result without a consumptionDelta from the API response.
Looks like it's my gas consumption that is empty, likely due to the fact my account still lists my 2 old non-smart meters.
Testing done
Modified the code straight in my Home Assistant container, restarted it, looked at logs for 2min: OK

Hello. Sorry for the late response and thank you for looking into this issue. Please see my comments :)

Due to lack of activity, this has been resolved in the suggested way elsewhere.


android connect success, iOS connect error

android is ok ,but iOS show errors, and IOS info file add NSApptransportSecurity:NSAllowsArbitraryLoads value set YES.
ros masterIp:http://<IP_ADDRESS>:11311
error msg:
flutter: ^[[38;5;196m│ Error while registering publisher /rosout: Connection failed<…>
flutter: ^[[38;5;196m│ #0      IOClient.send (package:http/src/io_client.dart:94:7)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ #1      BaseClient.sendUnstreamed (package:http/src/base_client.dart:93:32)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ #2      call (package:xml_rpc/src/client.dart:51:7)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ #3      _rpcCall (package:mm_controller/libs/dartros-master/lib/src/ros_xmlrpc_client.dart:96:18)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ #4      RosXmlRpcClient.registerPublisher (package:mm_controller/libs/dartros-master/lib/src/ros_xmlrpc_client.dart:266:8)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ #5      PublisherImpl.register (package:mm_controller/libs/dartros-master/lib/src/impl/publisher_impl.dart:111:20)<…>
flutter: ^[[38;5;196m│ <…>
flutter: ^[[38;5;196m│ <…>

I'm sorry, I have no iOS device, so I don't know how to help here. You are welcome to submit a PR if you figure out the issue, maybe submit a PR for documentation for debugging help for future users as well.

OK thanks , if I solve this pr, I'll report it


Awareness in zustand-yjs

Have you thought about how to handle awareness in zustand-yjs?
I'm not exactly sure how to implement it... but it seems like it could be another property of the object returned by useYStore().
const useYStore = create<YStore>((set, get) => {
  return {
    yDocs: [],
    observers: [],
    data: [],
    awareness: []
    ...

After you mount the yDoc using their connect function, an event handler is registered on the provider.awareness object and changes are observed similarly to how changes are observed on any of the y objects.
      else {
        // const unMount = mount(yDoc)
        const [unMount, provider] = mount(yDoc)
        if(typeof provider !== 'undefined'){
          provider.awareness.on('update', () => {
            set({
              awareness: Array.from(provider.awareness.getStates().values())
            })
          })
        }
        set({ yDocs: [...yDocs, [yDoc.guid, yDoc, mount, unMount, 1]] })
      }

Didn't look like this fit with the existing observers array pattern, but let me know if I'm wrong.
I tried to test this out myself but ran into major issues with npm link. Might try again tomorrow.
Thanks!

So the previous post was a bit naive although I hope I got the idea across... I wasn't able to get npm link to work for some reason, so I ended up implementing a useAwareness hook in my project as below:
const useAwareness = (initAwareness) => {
  const [collabs, setCollabs] = useState([])
  const [awareness, setAwareness] = useState(initAwareness)

  useEffect(() => {
    if(typeof awareness !== 'undefined'){
      awareness.on('update', () => {
        setCollabs(Array.from(awareProvider.getStates().values()))
      })
    }
  },[awareness])

  return [collabs, setAwareness]
}

This seems to work. Let me know what you think about integrating this into zustand-yjs!

Hello! Thanks, @NGimbal that's a trickier issue than I thought :)
So, I didn't plan to implement awerness that soon, but it seems like a good idea as it's a pretty common feature.
My understanding of awareness is getting better but is still limited, so here how I see the feature from your examples:
Currently, the connect function looks like this:
import { WebrtcProvider } from 'y-webrtc'

const connectADoc = (doc: Y.Doc) => {
  console.log('connect ', doc.guid)
  const provider = new WebrtcProvider(`mydoc:${doc.guid}`, ydoc)
  return () => {
    provider.destroy();
  }
}

And could looks like:
import { WebrtcProvider } from 'y-webrtc'

const connectADoc = (doc: Y.Doc, handleAwerness) => {
  console.log('connect ', doc.guid)
  const provider = new WebrtcProvider(`mydoc:${doc.guid}`, ydoc)
  provider.awareness.on('update', handleAwerness)
  return () => {
    provider.awareness.off('update', handleAwerness); // Optional, as #destroy will do it
    provider.destroy();
  }

And then to retrieve awareness data, I could create a hook that use the Zustand YStore:
import { useYDoc, useAwareness } from 'zustand-yjs'

const List = () => {
  const yDoc = useYDoc('root', connectADoc);
  const awarenessStates = useAwareness(yDoc); // Return the stored Awareness#getStates().values()
  return
Do stuff with awareness

}

My first impressions of this draft are:

It's good to have another hook for awareness as you don't need to use it systematically.
Adding a parameter to the connect function is the simplest thing I have in mind, even I think there is a better solution for the end-user of the library.
Your snippet will be very helpful, just some adjustments for this API and it should work.
I think it will add a lot of value to this project :)

What do you think of this draft @NGimbal? Looking at this draft, do you see anything harmful for the lib?

Awesome! I think what you're describing makes a ton of sense.
One thing to note: in my snippet initAwareness refers to the awareness object on the yjs provider. This was the most awkward thing about doing it outside of zustand-yjs.
  awareProvider = wsProvider.awareness

   awareProvider.setLocalState({
      color: chroma.random().hex(),
      name: randomName(),
      clientID: awareProvider.clientID
    })

Okay so I hit the close button accidentally...
What I was wanting to say was that this looks great :) thanks for figuring out the details on this.
One thing I'd want to note (although you probably already realized this) is that in my snippet initAwareness refers to the awareness object that is part of the yjs-provider object. Additionally, the user will want to set an initial state when initiating awareness using yjsProvider.awareness.setLocalState(). I guess in the example you show, that could still take place in connectADoc() as I have it shown below.
var awareProvider

const connectDoc = (doc) => {
  const wsProvider = new WebsocketProvider('ws://localhost:1234', 'my-room3', doc)

  awareProvider = wsProvider.awareness

  awareProvider.setLocalState({
     color: chroma.random().hex(),
     name: randomName(),
     clientID: awareProvider.clientID
 })

 return () => console.log('disconnect', doc.guid)
}

const useAwareness = (initAwareness) => {
  // as in snippet above above
}

function App() {

  const ydoc = useYDoc('docguid', connectDoc)
  const [collabs, setAwareness] = useAwareness(awareProvider)

  ...
}

Thanks for example @NGimbal, I've seen some problems in my drafts.

Additionally, the user will want to set an initial state when initiating awareness using yjsProvider.awareness.setLocalState()

Yes, I thought it could be done in the connect function, like in your example

var awareProvider
const connectDoc = (doc) => {
...

I would like to design an API that avoids the use of globals like this var awareProvider, and I realize with your example that my proposal forces you to do so. My idea is that you can have a unique connect function, that connects all your YDoc. As they have distinct #guid you can route the connexion with that name.
So a global var for awareProvider in the case of many YDoc connecting won't work.

From your example, and the flaws I saw in my draft, here what I have in mind:
import { WebrtcProvider } from 'y-webrtc'

const connectDoc = (doc: Y.Doc, startAwareness) => {
  const wsProvider = new WebrtcProvider('ws://localhost:1234 ', `${doc.guid}`, ydoc);
  const awareProvider = wsProvider.awareness;
  awareProvider.setLocalState({
     color: chroma.random().hex(),
     name: randomName(),
     clientID: awareProvider.clientID
 })
  // startAwareness will store the provider for the doc.guid,
  // and starts to do a protocol.awareness.on('update').
  const stopAwareness = startAwareness(wsProvider);

  return () => {
    stopAwareness();
    provider.destroy();
  }
}

function App() {
  const ydoc = useYDoc('my-room3', connectDoc)
  // useAwareness takes the YDoc, to know the #guid,
  // and then be able to retrieve the right awareness data.
  // Initial state for awareness would be handle in the connect function and not in the view.
  const [collabs, setAwareness] = useAwareness(ydoc)

  ...
}

===
PR is coming later this week :P quite a lot on my plate right now.

I really like the idea to be able to access and modify awareness state like this. Your awareness API could make it very convenient to render presence information (the list of currently active users).
As mentioned in the Yjs Gitter channel, Awareness is not well suited to store a lot of information. However, it is well suited for data that changes frequently and has a small footprint (e.g. cursor location, the name of the user, and the associated color). It is also nice for storing the caret position in x,y coordinates. Just keep that in mind when designing the API. It might be a bad idea to store all user-associated data in an Awareness field. I should probably put that in the documentation as well.

Great, thanks for the reminder @dmonad, will have this in mind, I think it's a great use-case for transient values.
By the way, it reminds me that indeed useAwareness should give back a setLocalStateField if we want to set awareness haha. Proposal updated, working in on it!

It might be a bad idea to store all user-associated data in an Awareness field. - @dmonad

Can you elaborate on this, specifically, why this might not be a best practice?

Every time you change the awareness state, you send your complete local copy to all connected peers. So when you store a profile picture, mail address, street, zip, .. in your awareness instance, then you use more network traffic than you would need to. I recommend to only store data that changes frequently + the name and a user-identifier that you can use to query user-associated data that doesn't change frequently (e.g. profile picture, mail, street zip, ..).

Hello, just commenting the issue to say I've made it 🎉 (finally).
I did some bad manipulations on the github, so that's why we have made quite a gap in versions, sorry about that.
I really need to sit to write a pipeline and unit tests, to avoid messy publish. :)
===
I am very happy to have done this feature at the end, it gives me really a good feeling using the lib, so thanks @NGimbal.
Readme is coming soon. For now, in the example, you will see how to edit the local changes :
https://github.com/tandem-pt/zustand-yjs/blob/master/example/src/App.tsx#L111-L117
And how to use it:
https://github.com/tandem-pt/zustand-yjs/blob/master/example/src/App.tsx#L81-L89
===
Here the example:

Amazing! 🤩

Thanks for getting this working!


Optimize_Images_for_Better_Performance

We need to optimize images on our website to improve loading speed and overall performance. This includes compressing existing images and converting them to more efficient formats like WebP.
Compress Images:
Use tools like TinyPNG or ImageOptim to reduce the file size of current images without sacrificing quality.
Convert to WebP Format:
Change image formats from JPEG/PNG to WebP where appropriate to enhance performance.
 I have to update a lot of files!! Add level3!


added search & search placeholder values

Changed few lines to add new properties (Don't know why git recognized as full file changed, indents are fine too):

search option to switch on/off input search
searchPlaceholder option to add custom placeholder in case selector includes search

Switching of the search/filter is added as feature to the beta release (noFilter property), both for single and multiple select.
I am not in favor of a placeholder for the filter input field.


provide a way for classes to opt in into extended stack traces with context information

Motivation
We have discovered that stable release of Flutter contains a bug in the AOT transformation https://github.com/flutter/flutter/issues/56479, which crashes with the following stack trace
    #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:53:5)
    #1      new StaticTypeContext (package:kernel/type_environment.dart:763:27)
    #2      _TreeShakerPass1.staticTypeContext (package:vm/transformations/type_flow/transformer.dart:752:30)
    #3      _TreeShakerPass1._fixArgumentEvaluationOrder (package:vm/transformations/type_flow/transformer.dart:1007:41)
    #4      _TreeShakerPass1.visitConstructorInvocation (package:vm/transformations/type_flow/transformer.dart:1170:22)
    #5      ConstructorInvocation.accept (package:kernel/ast.dart:3964:44)
    #6      Field.transformChildren (package:kernel/ast.dart:1862:33)
    #7      _TreeShakerPass1.visitField (package:vm/transformations/type_flow/transformer.dart:903:16)
    #8      Field.accept (package:kernel/ast.dart:1847:40)
    #9      transformList (package:kernel/ast.dart:8700:27)
    #10     _TreeShakerPass1.visitClass (package:vm/transformations/type_flow/transformer.dart:856:5)
    #11     Class.accept (package:kernel/ast.dart:1375:38)
    #12     transformList (package:kernel/ast.dart:8700:27)
    #13     Library.transformChildren (package:kernel/ast.dart:627:5)
    #14     Transformer.defaultTreeNode (package:kernel/visitor.dart:650:10)
    #15     TreeVisitor.visitLibrary (package:kernel/visitor.dart:254:35)
    #16     Library.accept (package:kernel/ast.dart:609:38)
    #17     transformList (package:kernel/ast.dart:8700:27)
    #18     Component.transformChildren (package:kernel/ast.dart:8516:5)
    #19     _TreeShakerPass1.transform (package:vm/transformations/type_flow/transformer.dart:764:15)
    #20     TreeShaker.transformComponent (package:vm/transformations/type_flow/transformer.dart:582:12)
    #21     transformComponent (package:vm/transformations/type_flow/transformer.dart:76:7)
    #22     runGlobalTransformations (package:vm/kernel_front_end.dart:425:5)
    #23     compileToKernel (package:vm/kernel_front_end.dart:336:11)
    <asynchronous suspension>
    #24     FrontendCompiler.compile.<anonymous closure> (package:frontend_server/frontend_server.dart:510:54)
    #25     new Future.<anonymous closure> (dart:async/future.dart:176:37)
    #26     _rootRun (dart:async/zone.dart:1180:38)
    #27     _CustomZone.run (dart:async/zone.dart:1077:19)
    #28     _CustomZone.runGuarded (dart:async/zone.dart:979:7)
    #29     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
    #30     _rootRun (dart:async/zone.dart:1184:13)
    #31     _CustomZone.run (dart:async/zone.dart:1077:19)
    #32     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:1003:23)
    #33     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:23:15)
    #34     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:398:19)
    #35     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:429:5)
    #36     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

This stack trace gives us enough information to diagnose the problem - but unfortunately does not give us enough information to provide a work-around for the user - for that we need to know which field is being visited in the AST.
Proposal
Add pragma @pragma('vm:expand-in-stack-trace') (tentative name), if the class is annotated with this pragma then its methods and methods of all classes that implement or extend it get an expanded context in the stack trace, which would include parameters and the receiver. For example, annotating TreeVisitor and Node with this annotation would result in the following change to the stack trace:
    #6      Field.transformChildren {this = ..., visitor = ...} (package:kernel/ast.dart:1862:33)
    #7      _TreeShakerPass1.visitField {this = ..., field = ... } (package:vm/transformations/type_flow/transformer.dart:903:16)

Here var = smth are added to frames - var being a parameter name and smth is a string representation of an actual value stored in the parameter variable obtained by running toString on it.
Alternatives
V8 has imperative API which allows to customise stack trace formatting and gives developer programmatic access to a representation of the call stack, which includes receiver object for any frame (but does not include way to capture or access other local variables).
Python gives you programmatic access to the call stack including local variables
Considerations

Calling arbitrary Dart code during stack trace formatting might not be desirable or portable across platforms that Dart supports - that is why we make it an opt-in VM specific feature.
For code size reasons we might restrict this feature to JIT builds

/cc @lrhn @rmacnak-google @mkustermann @leafpetersen @alexmarkov  - thoughts?

If this is a JIT-only feature, then a declarative approach (using annotations or compiler flags) is probably better than an imperative one using code. That code would not even exist on other platforms. Annotations can be ignored.
The format:
    #6      Field.transformChildren {this = ..., visitor = ...} (package:kernel/ast.dart:1862:33)
    #7      _TreeShakerPass1.visitField {this = ..., field = ... } (package:vm/transformations/type_flow/transformer.dart:903:16)

does not say how to actually write the ... values. How do you write a Node or visitor function out? Do you have a way built into the debugger to make string representations of arbitrary objects,  preferably without calling Dart code?
Could it be a debugger feature? Or can the debugger already do this, and what you want is a way to capture the stack trace with extra info for access after execution has ended?
Adding annotations is a reactive approach. I assume you add this annotation when something breaks, then run the code again and hope the same error occurs again. Would people start adding the annotation everywhere while developing, just to make their own life easier (then, maybe, remove it when compiling for production, or that happens automatically if it's not a JIT target).
I think I'd do that.
You cannot add annotations to other people's code, so should there be a way to inject it as well?
Would it be possible to always do the expansion for all functions on the stack? At least while debugging?
That could get expensive, so maybe only do it for stack traces associated with throwing an Error, and only the first time the error is thrown, when you are also installing the stack trace on the error object.

We already have programmatic access to stack; you just need to do it from another process or isolate.

lling arbitrary Dart code during stack trace formatting might not be desirable or portable across platforms that Dart supports - that is why we make it an opt-in VM specific feature.

I missed where in your proposal arbitrary Dart code is run during stack trace formatting.  Can you expand?

@lrhn

does not say how to actually write the ... values.

Added the description - for simplicity I assume that there are just results of calling toString on the values.

Could it be a debugger feature? Or can the debugger already do this, and what you want is a way to capture the stack trace with extra info for access after execution has ended?

Debugger can already do that (as @rmacnak-google points out) the challenge here is how to utilise this functionality in release builds to facilitate post mortem problem analysis. One solution would be that all our tools have some sort of a watchdog isolate that monitors other isolates via service protocol and captures more informative stack traces when errors happen.
This seems possible to setup and even abstract into utility library) but seems a bit over-engineered. (some of the complexity would stem from the fact that we don't have simple way to "self-attach")

Adding annotations is a reactive approach. I assume you add this annotation when something breaks, then run the code again and hope the same error occurs again. Would people start adding the annotation everywhere while developing, just to make their own life easier (then, maybe, remove it when compiling for production, or that happens automatically if it's not a JIT target).

Note that this is not a feature intended for the development - it is for diagnosing crashes which occur in deployment.
@leafpetersen

I missed where in your proposal arbitrary Dart code is run during stack trace formatting. Can you expand?

Expanded the section - it now mentions calling toString


Add unit tests to phases widget

Issue #:
https://github.com/bcgov/met-public/issues/670
Description of changes:

Add front-end unit tests for phases widget
Improve unit tests in EngagementView test not to use provider shell
resolve error in document widget test

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #981 (6172d5b) into main (370ebe8) will increase coverage by 1.32%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main     #981      +/-   ##
==========================================
+ Coverage   73.49%   74.81%   +1.32%
==========================================
  Files         213      213
  Lines        5534     5544      +10
  Branches      335      338       +3
==========================================
+ Hits         4067     4148      +81
+ Misses       1425     1360      -65
+ Partials       42       36       -6

Flag
Coverage Δ

metweb
69.58% <75.00%> (+2.73%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...-web/src/components/engagement/view/EmailModal.tsx
54.54% <16.66%> (-1.27%)
:arrow_down:

...b/src/components/engagement/view/ActionContext.tsx
64.81% <66.66%> (+5.99%)
:arrow_up:

met-web/src/components/common/MetPopper.tsx
100.00% <100.00%> (+14.28%)
:arrow_up:

...web/src/components/engagement/view/SurveyBlock.tsx
100.00% <100.00%> (ø)

...nts/engagement/view/widgets/PhasesWidget/index.tsx
91.66% <100.00%> (+5.30%)
:arrow_up:

...s/engagement/view/widgets/WhoIsListeningWidget.tsx
87.09% <100.00%> (+58.06%)
:arrow_up:

...components/engagement/view/widgets/WidgetBlock.tsx
100.00% <100.00%> (+20.00%)
:arrow_up:

met-web/src/components/common/index.tsx
89.47% <0.00%> (+1.75%)
:arrow_up:

...eb/src/components/common/Modals/Schedule/index.tsx
69.56% <0.00%> (+4.34%)
:arrow_up:

... and 22 more


binding/c: feat: support create all kinds of operators

add root args when creating operator
support most of kinds of services
add fs test

Thank you for the PR.

add root args when creating operator

I would like to explore code generation as an alternative to accepting a map for all arguments.

support most of kinds of services

We will not provide support for other services until we resolve the previous issue and ensure that memory services pass all tests.

add fs test

We will not test on other services, it's OpenDAL core's job.

Thanks for the PR again, I will close this PR now.


ENVIRONMENT VARIABLES NOT BEING SET?? WTF

AFTER INSTALLING TRUFFLE I GET THE FOLLOWING ERROR:
'truffle' is not recognized as an internal or external command,
operable program or batch file.
ON WINDOWS 7.
HOW DO I ADD THE VARIABLES MANUALLY.
ALSO ETHEREUM SYNC IS SLOW AS SHIT AND TESTRPC FAILS TO INSTALL. FML!!!!

Hi there. I'm sorry you had an issue. That said, the best way to get support on this forum is to not use all caps. For all future reports, please write out the issue more clearly.
That said, the issue you're having is not an issue with Truffle, but rather npm. Make sure you have the latest node js installed (you can get it here: https://nodejs.org/en/ , download 6.x). Then reinstall truffle using npm install -g truffle. If you're still having trouble, post the node and npm version here, using the following commands:
$ node -v
$ npm -v

If these are the latest versions and are installed correctly, you shouldn't have to add items to the path yourself. npm should do it for you.
Regarding the TestRPC, make sure you follow the Windows Install Instructions, here: https://github.com/ethereumjs/testrpc/wiki/Installing-TestRPC-on-Windows
Now, I've never tried to install any of this on Windows 7. I've only tested 8.1 and 10. Please google the errors you receive and specifically look for solutions for Windows 7. Again, this is not a Truffle issue, but an issue with your installation of node and npm.

It installed truffle before but I couldn't use the CLI. after updating NODE and NPM i'm getting those new BUILD ERRORS.


[DO NOT MERGE] Swagger changes for Elastic Pool ARM API V20250201

Add currentSku property in Elastic Pool API response for Swagger changes

New property named currentSku to the Elastic Pool properties to differentiate between the current SKU and the targeted SKU

Please fix these errors if they are still not released to stable version
https://github.com/Azure/azure-rest-api-specs/pull/31900/checks?check_run_id=34510347276


Add new outline module

This adds a new outline module, which can be configured in a very similar way to shadows.
outline: {
  default: `2px solid rgba(52,144,220,0.5)`,
  'none': 'none',
},

However, now that I've built this, I sort of think shadows are a better choice regardless, read more about that here: https://github.com/tailwindcss/tailwindcss/issues/56#issuecomment-397363973
I'm thinking we simply create a hardcoded outline-none reset instead, and be done with it.

@reinink I think the outline-none utility would be enough.

Closing in favour of #491


JS errors with BackgroundGeolocation.finish() on Android with Ionic 2

Your Environment

Plugin version: 2.2.4
Platform: Android
OS version: Android 6.0, API 23
Device manufacturer and model: Android Studio emulator - Nexus 5 API 23 2 (Android 6.0, API 23)
Cordova version: 6.3.1
Ionic version: Ionic 2 project using Ionic 2.0.0-rc.1 (2016-10-13)
Cordova platform version:

Installed platforms:
  android 5.2.2
  ios 4.1.1

Plugin configuration options:

    let config = {
       desiredAccuracy: 0,
       stationaryRadius: 20,
       distanceFilter: 10,
       debug: true,
       interval: 2000
    };

Link to your project:
Recreated Ionic 2 background geolocation project from Josh Morony

Context
Building Ionic2 app with background geolocation. Was able to recreate the bug using Josh Morony's instructions on how to add bg-geo to Ionic 2 apps. It appears the BackgroundGeolocation.finish() method throws errors on Android. When I added it to the success callback function as per docs (so that iOS doesn't kill background processes) it throws errors on Android.
This solution causes error on Android, but OK for iOS:
BackgroundGeolocation.configure(
      (location) => {
          console.log('Background location update: ' + location.latitude + ' ' + location.longitude);
          // Code to run update inside Angular's zone
          BackgroundGeolocation.finish();
      },
      (error) => {
          console.error('Background location error', error);
      }, config);

This solution OK for Android, but iOS kills background process:
BackgroundGeolocation.configure(
      (location) => {
           console.log('Background location update: ' + location.latitude + ' ' + location.longitude);
           // Code to run update inside Angular's zone
           // no call to BackgroundGeolocation.finish()
      },
      (error) => {
           console.error('Background location error', error);
      }, config);

Expected Behavior
When BackgroundGeolocation.finish() is included in callback, no errors received:
Background location update: 45.39999833333333 -119.4
Background location zone.run()
Calling BackgroundGeolocation.finish()
// NO ERROR HERE
Foreground location update: 45.3999983 -119.4

Actual Behavior
When BackgroundGeolocation.finish() is included in callback, we get following error:
Background location update: 45.89999833333333 -119.09999833333335
Background location zone.run()
Calling BackgroundGeolocation.finish()
Unhandled Promise rejection: Invalid action ; Zone: <root> ; Task: Promise.then ; Value: Invalid action undefined
Error: Uncaught (in promise): Invalid action
    at s (file:///android_asset/www/build/polyfills.js:3:8546)
    at file:///android_asset/www/build/polyfills.js:3:8296
    at Object.cordova.callbackFromNative (file:///android_asset/www/cordova.js:295:52)
    at processMessage (file:///android_asset/www/cordova.js:1081:17)
    at processMessages (file:///android_asset/www/cordova.js:1104:9)
    at t.invoke (file:///android_asset/www/build/polyfills.js:3:13400)
    at e.run (file:///android_asset/www/build/polyfills.js:3:10787)
    at file:///android_asset/www/build/polyfills.js:3:8889
    at t.invokeTask (file:///android_asset/www/build/polyfills.js:3:14029)
    at e.runTask (file:///android_asset/www/build/polyfills.js:3:11389)
Foreground location update: 45.1 -119.0999983

Steps to Reproduce

Create Ionic 2 project per article from Josh Morony
Per article, don't include BackgroundGeolocation.finish();, project will run fine on Android, but iOS will kill background process

BackgroundGeolocation.configure(
      (location) => {
           console.log('Background location update: ' + location.latitude + ' ' + location.longitude);
           // Code to run update inside Angular's zone
           // NO CALL to BackgroundGeolocation.finish()
      },
      (error) => {
           console.error('Background location error', error);
      }, config);

Per plug-in docs, include BackgroundGeolocation.finish();, project will run fine on iOS, but  will get errors on Android

BackgroundGeolocation.configure(
      (location) => {
          console.log('Background location update: ' + location.latitude + ' ' + location.longitude);
          // Code to run update inside Angular's zone
          BackgroundGeolocation.finish();
      },
      (error) => {
          console.error('Background location error', error);
      }, config);

Context

Unable to use plug-in without getting errors on either iOS or Android.
Debug logs

Logs include console.log messages from within app.
Android without BackgroundGeolocation.finish-1478157603179.txt
Android with BackgroundGeolocation.finish-1478157089114.txt

Not sure how this error is possible, since I'm not using Promises. This can be potentially fixed by implementing dummy finish method for android.

You can check if the device is running ios before calling finish.
import { Platform } from 'ionic-angular'

if( !this.platform.is( 'android' ) ) {
    BackgroundGeolocation.finish();
}

Thanks for the tip @JackLewisGit
Just to be clear...the finish() method is only needed for iOS?

@bionicbrad Yes, finish() is only for iOS as you can see in the docs. Therefore, use the following:
if (this.platform.is('ios')) {
    BackgroundGeolocation.finish();
}

Also, make sure to use this.backgroundGeolocation.stop(); to stop the tracking, and not the finish method.
P.S. I've learned to never expect any of Josh's tutorials to work right off the bat, as there are usually plugin changes he doesn't account / update for.

Finish method was replaced with startTask/endTask in version 3.x, so closing this one.


Implement admin - _scram typings

:tada: This issue has been resolved in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adds LDAPDN field to Team

In GitHub Enterprise, the teams API routes include ldap_dn if the team is being synchronized with LDAP.

Is this documented anywhere on GitHub API docs? I didn't see it at all at https://developer.github.com/v3/orgs/teams/, but I do see a similar field mentioned at https://developer.github.com/v3/enterprise/ldap/. Is that the best reference, or do you know of a better one?
This looks good to me after the minor missing period is fixed. Thanks!

Is this documented anywhere on GitHub API docs? I didn't see it at all at https://developer.github.com/v3/orgs/teams/, but I do see a similar field mentioned at https://developer.github.com/v3/enterprise/ldap/. Is that the best reference, or do you know of a better one?

Unfortunately I can't find it documented either, but I can verify the field is returned when I run GET /teams/:id or GET /orgs/:id/teams against my GitHub Enterprise instance. The JSON looks something like:
{
  "name": "Read-Only Users",
  "id": 67,
  "slug": "read-only-users",
  "description": "Read-Only Access",
  "privacy": "secret",
  "permission": "pull",
  "ldap_dn": "cn=ghereadonly,ou=Group,dc=example,dc=com",
  "members_count": 5,
  "repos_count": 10,
  // other fields elided
}

Thanks @alindeman!


Update node-problem-detector-config

Seems there is an inconsistency between /config and /deployment examples for kernel-monitor.
Updating deployment example accordingly.

/assign @random-liu

/LGTM

/lgtm
/approve


Support VersionId parameter when tagging s3 objects

It seems like specifying the object version id when calling put_object_tagging(**kwargs) is not respected, and instead the tagging is set on the most recent version of the s3 key.
boto3 version: 1.9.86
moto version: 1.3.9
Running the following test should reproduce the issue:
@mock_s3
def test_boto3_put_object_tagging_on_earliest_version():
    s3 = boto3.client('s3', region_name='us-east-1')
    bucket_name = 'mybucket'
    key = 'key-with-tags'
    s3.create_bucket(Bucket=bucket_name)
    s3_resource = boto3.resource('s3')
    bucket_versioning = s3_resource.BucketVersioning(bucket_name)
    bucket_versioning.enable()
    bucket_versioning.status.should.equal('Enabled')

    with assert_raises(ClientError) as err:
        s3.put_object_tagging(
            Bucket=bucket_name,
            Key=key,
            Tagging={'TagSet': [
                {'Key': 'item1', 'Value': 'foo'},
                {'Key': 'item2', 'Value': 'bar'},
            ]}
        )

    e = err.exception
    e.response['Error'].should.equal({
        'Code': 'NoSuchKey',
        'Message': 'The specified key does not exist.',
        'RequestID': '7a62c49f-347e-4fc4-9331-6e8eEXAMPLE',
    })

    s3.put_object(
        Bucket=bucket_name,
        Key=key,
        Body='test'
    )
    s3.put_object(
        Bucket=bucket_name,
        Key=key,
        Body='test_updated'
    )

    object_versions = list(s3_resource.Bucket(bucket_name).object_versions.all())
    first_object = object_versions[0]
    second_object = object_versions[1]

    resp = s3.put_object_tagging(
        Bucket=bucket_name,
        Key=key,
        Tagging={'TagSet': [
            {'Key': 'item1', 'Value': 'foo'},
            {'Key': 'item2', 'Value': 'bar'},
        ]},
        VersionId=first_object.id
    )

    resp['ResponseMetadata']['HTTPStatusCode'].should.equal(200)

    # Older version has tags while the most recent does not
    resp = s3.get_object_tagging(Bucket=bucket_name, Key=key, VersionId=first_object.id)
    resp['ResponseMetadata']['HTTPStatusCode'].should.equal(200)
    resp['TagSet'].should.equal(
        [
            {'Key': 'item1', 'Value': 'foo'},
            {'Key': 'item2', 'Value': 'bar'}
        ]
    )

    resp = s3.get_object_tagging(Bucket=bucket_name, Key=key, VersionId=second_object.id)
    resp['ResponseMetadata']['HTTPStatusCode'].should.equal(200)
    resp['TagSet'].should.equal([])

I believe I have identified where in the code needs to be changed and have opened a PR here: https://github.com/spulec/moto/pull/2485
Please let me know if this feature was already supported and I missed the functionality, if I need to refactor the code to conform to moto's standards or anything else that would help with fixing this issue.

Closed with #2485


Cryoplant power constraint

In GitLab by @skahn on Oct 1, 2020, 12:07
Description
Some cryoplant power consumptions (150 MW) would mean using the superficy of oxford for it. To avoid such effect on the desing, it might be interresting to set constraint limit for the cryogenic power consumption.
Tout doux list

[x] Add crypmw_max as user input
[x] Add f_crypmw as iteration variable
[x] Add the constraint equation
[x] Use the constraint on some inputs files

The constraints works as expected and is being used. Ready to be merged : https://git.ccfe.ac.uk/process/process/-/merge_requests/356
Corresponding branch: https://git.ccfe.ac.uk/process/process/-/tree/issue-1120-cryopower-constraint
Corresponding merge request: https://git.ccfe.ac.uk/process/process/-/merge_requests/356
Best regards
seb
ref : @stuartmuldrew

I don't think any action is needed here.  The upper limit on the cryogenic plant power for the TF coil (constraint 87) is available but you don't have to use it.

See above, issue closed.


chore: have better defaults during install

We should always enable GitHub Actions by default, and install the linux dependencies as well. Both either breaks the user story/flow or makes the browsers not launchable.

offline review with pfeldman


Quick question about Nav Bar Please Check Attached ss

New Issue Checklist

[x] Use the latest version of CalendarKit
[x] I've read the Contribution Guidelines
[x] I've searched for existing GitHub issues

Issue Description

Hey @richardtop first of all I wanted to thank you for quickly getting back to me yesterday. I completed the integrated and I really want to say thanks because this is the best SDK I have used for calender. Great job mate!
It works pretty fine and I will start digging deep to connect user data to my database.
My problem is NavBar is completely black on my simulator. I checked the file under pods "UIColor+SystemColors" < this one but there is nothing that makes my nav bar complete black. Here is ss below and kindly asking your guidance;

Code I'm using with CalendarKit

<!-- INSERT CODE HERE -->
Works fine :)

Result I am trying to achieve

StackOverflow Question link

Dont mind I figured it out. So you were setting nav bar on scene delegate so I just modified it on my viewdidload.
Another question which I really couldnt find any referance; how to automatically scroll down to current time when vc is presented?

Another question which I really couldnt find any referance; how to automatically scroll down to current time when vc is presented?

No such functionality in the library as of right now.

There is an open issue regarding week view, which might get developed. Regarding month view, you'll need to combine CK with some other library, as there are plenty of libraries to display the month view.

Thanks a lot @richardtop , I already loved the way you build CK. Cheers!

By the way, just to inform you: on models lower than iphone 8, when you click an event on the calendar there is a button toolbar for "delete" button. When you close the editing vc that toolbar stays in the bottom and if CK is integrated in an app it effects the whole app and stays there. I solved it with
    override func viewWillDisappear(_ animated: Bool) {
        self.navigationController?.setToolbarHidden(true, animated: false)

    }
    override func viewWillAppear(_ animated: Bool) {
        self.navigationController?.setToolbarHidden(true, animated: false)

    }

this lines on my day vc. You might want to mention it if you record another youtube video. Cheers! @richardtop


Roll Flutter Engine from c9b8ac96f6ce to 3162aaad0086 (3 revisions)

https://github.com/flutter/engine/compare/c9b8ac96f6ce...3162aaad0086
2024-10-26<EMAIL_ADDRESS>Migrate FlutterViewController to ARC (flutter/engine#55669)
2024-10-26<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Y4TdnTpLdkI107K42... to 5osQdhk4W6CcWgjIg... (flutter/engine#56152)
2024-10-26<EMAIL_ADDRESS>Roll Dart SDK from 0257f458e40a to a75848f92210 (2 revisions) (flutter/engine#56150)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from Y4TdnTpLdkI1 to 5osQdhk4W6Cc
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC codefu<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


sparql endpoint setting updates not transmitting to backend properly

hanging sparql endpoint in project settings of frontend does nothing

fixed in  0f1f900496


end2end test failure in collection test

Describe the bug
https://github.com/atsign-foundation/at_client_sdk/actions/runs/8373572103/job/22927728963
Model operations - unshare() and delete() test fails in github actions
Steps to reproduce

run the test pointing to local server
Getting a different error in local . I think keys retrieval is happening before share/save completes
test/collection_test.dart 356:5  main.

Expected: ['@colin🛠']
  Actual: []
   Which: at location [0] is [] which shorter than expected

Expected behavior
test should pass
Screenshots
No response
Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Were you using an atApplication when the bug was found?
No response
Additional context
No response

@gkc @cpswan
There seems to be a race condition(getKeys happens before save completes) in collections implementation.
We are currently not using collections model in any of our apps. Temporarily commented collections test to unblock at_client release. I am downgrading the severity from P1 to P2.


Interpretation of Tandem files

Hello, YuPeng
Hello, I used MScanX to obtain a tandem file of a genome, but I don't know how to interpret this file?

Use DUPGEN_Finder, an updated version without all the errors you might encounter in MCScanX, and with all the convenience you need from MCScanX output files.
Dupgen_Finder


Menu mobs not rendering

Minecraft v1.16.5
Forge v36.0.1
Menu Companions v1.1
Mobs are not rendering on the menu for me until I edit and then save the config file.

Same issue of not rendering here.
Minecraft 1.16.4
Forge 35.1.37
Menu Companions 1.1

Same issue of not rendering here.
Minecraft 1.16.4
Forge 35.1.37
Menu Companions 1.1

You probably still have the old config file (mobs.json in the config/menucompanions directory) from v1.0.2. Delete that so it can be regenerated and report back if it works.

Just tried that, still nothing rendering unfortunately.

Same for me, the file regenerated, but still no mobs.

There are only a couple of mods I have that I can immediately think of that would cause conflicts:

Optifine
FancyMenu

...I wonder if FancyMenu hooks into something that prevents MenuCompanions from hooking in to do its own work? Not sure how either mod achieves what they achieve, aha.

I don't have Fancy Menu, but I do have Optifine. I also have Quark and Survive, both of which adds a button to the menu.

I have Quark too - I never really considered that it could break the rendering but who knows.

Uhh, it's a lot. Although I kinda doubt it's quark. It's probably to do with the menu companions config not loading. If I change something in the config and save it, then mobs will appear.

mod-list_2021-02-06_09.52.12.txt
Genned a mod list using TellMe just in case it helps.
Also hmm that's interesting. Maybe a temp fix is just to change the config? Or does it only last for a single run?

It only lasts a single run.

How's this version working for you? Does everything load correctly?

The menu mobs still don't appear, even after saving the config file. Also, the reload button appears even when ctrl is not being held, although it can't be clicked on until I hold down ctrl.

Are you on Windows? How do the contents of the config/menucompanions  directory look like, what files does it have? Can you also send your latest.log please.
For the reload button that's probably Ice and Fire. I have no clue why they would want to turn every button visible.

It has the menucompanions-client.toml and the mobs.json.
Here's the log: https://gist.github.com/WenXin20/20020c3669ce0dc0f829dbf91619af97

Here is another version. It won't work either if the first one didn't, but it'll output a lot more information to the log. So please send latest.log!

Thanks, I'll give it a try.

Oh and please try delete the old config/menucompanions folder so it can be recreated. I think that might actually be the problem here.

https://gist.github.com/WenXin20/43a069e550569b718211ae575e015d72

Alright, thanks. So you indeed just have to delete the menucompanions folder.

So I deleted the folder, pressed the refresh button, and then got a crash.
https://gist.github.com/WenXin20/40d86c44ff94accff2b5ce3f0a2a44a4

Try to disable use_player_list_name_in_tag from the Fabrication mod.

Yep, that stopped the crash, but I'm not seeing the player. The mobs are rendering though. :)

Getting closer and closer...
Problem with players is a lot of mods hook into the rendering in unpredictable ways. Can you please test this version for me, so we can find out why the player isn't rendering? It should crash when rendering the main menu, the crash-report is what I need then.

This version worked!!

great, thanks for the feedback!
other mods don’t really have anything to do with this particular issue, that was solely caused by me.
still waiting for @WenXin20 now so we can figure out why their player isn’t rendering

Mhm! Let me know if I can be of any service still.

Coming back as it has just occurred to me - @WenXin20 have you been deleting the MenuCompanions configuration folder when testing the new jars? That's something I also did before trying the test version that worked for me.

The loading part is working fine. Only the player isn't rendering. That's usually caused by other mods hooking into the player renderer in unpredictable ways. I only want to find out which mod that is in @WenXin20 's case.

Strangely enough, the player is rendering this time and there was no crash with v1.2.2b1.

This time when the game was loaded the player did not render, although there was no crash.

So everything seems to be working now. Great, so this can finally be closed.


FEATURE: asset aggregation consolidation

Processes and build aggregate of the assets summarized by totals.  This should offer faster /aggregate lookups.
Two tables are create.
avm_asset_aggregation -> which holds the new data
avm_asset_aggregation_state -> which holds onto what needs to process
It runs on producers, monitoring the state for new rows.  When a change is detected, will recompute aggregation from the creation time..  Ideally only processing delta updates for minutes that are newly updated..
Assuming the time on the kafka message has an incrementing timestamp.

Changes for P chain cause a few conflicts on this branch. I have prepared a merge commit of the bulk of the breaking changes with conflicts resolved here: https://github.com/ava-labs/ortelius/compare/TS_aggregation_model_move?expand=1
If #95 is merged first then this branch can be merged into this PR to fix conflicts.


[docs-infra] Use CSS vars for API pages

Now you can reload an API page in dark mode without having the light mode blinking
:tada:
I modified all the API pages at once because they are generated by a script

now: https://deploy-preview-41911--material-ui.netlify.app/material-ui/api/accordion-actions/
before: https://mui.com/material-ui/api/accordion-actions/

Those modification leads to an error message in the API pages but I've no idea about why
Warning: Prop `style` did not match. Server: "--Paper-shadow:var(--muidocs-shadows-4)" Client: "--Paper-shadow:var(--muidocs-shadows-4);--Paper-overlay:linear-gradient(rgba(255 255 255 / 0.092), rgba(255 255 255 / 0.092))"

Can be fixed by this diff, but not sure it's a misusage on our side or an error in the vars support
diff --git a/packages/mui-material/src/Paper/Paper.js b/packages/mui-material/src/Paper/Paper.js
index fbb7d90343..53c63403f7 100644
--- a/packages/mui-material/src/Paper/Paper.js
+++ b/packages/mui-material/src/Paper/Paper.js
@@ -117,7 +117,7 @@ const Paper = React.forwardRef(function Paper(inProps, ref) {
         ...(variant === 'elevation' && {
           '--Paper-shadow': (theme.vars || theme).shadows[elevation],
           ...(theme.vars && {
-            '--Paper-overlay': theme.overlays?.[elevation],
+            '--Paper-overlay': theme.vars.overlays?.[elevation],
           }),
           ...(!theme.vars &&
             theme.palette.mode === 'dark' && {

@alexfauquette @siriwatknp is this PR still relevant?


Replace image-rs with imsz

before
170 book(s), 19843 page(s), scanned in 26806ms
.rwxr-xr-x nixos users 3.3 MB Thu Mar 14 01:07:47 2024 target/release/comics

after
170 book(s), 19846 page(s), scanned in 221ms
.rwxr-xr-x nixos users 3.0 MB Thu Mar 14 01:07:05 2024 target/release/comics

on NAS, HDD

before: 151427ms
after: 65675ms (-56.6292%)


Create uptapachula.txt

set uptap

@yeyisten34 First stage of verification passed, official domain for Universidad Politécnica De Tapachula (UPTAP) is uptapachula.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@yeyisten34 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Upgrade Dependencies

Summary
In this upgrade we include React Native in itself that should take care of the issues around the TextInput on Android.
Updated the rest of the dependencies of the project bar @msgpack/msgpack and readable-stream
The typescript update requires the use of type in the imports.
Update dependencies for detox
Switch mechanism for Report a problem as it now allows the user to select the app to use (ex gmail)
Important: ideally we can have this merge before tomorrow's beta build. (I know it looks like a huge PR)
Release Note
NONE

Will request you to split the PR

Request denied :)


Fixes gocode panics for Go 1.8.

The binary format in 1.8 seems to be compatible with prior versions, I was getting panics such as below before this change:
panic: unknown export format version 4 ("version 4")
1(runtime.call32): /one/ws/godevtip/go/src/runtime/asm_amd64.s:514
2(runtime.gopanic): /one/ws/godevtip/go/src/runtime/panic.go:489
3(main.(*gc_bin_parser).parse_export): /one/ws/godevtip/src/github.com/nsf/gocode/package_bin.go:131
4(main.(*package_file_cache).process_package_data): /one/ws/godevtip/src/github.com/nsf/gocode/package.go:141
5(main.(*package_file_cache).update_cache): /one/ws/godevtip/src/github.com/nsf/gocode/package.go:90
6(main.update_packages.func1): /one/ws/godevtip/src/github.com/nsf/gocode/autocompletecontext.go:381
7(runtime.goexit): /one/ws/godevtip/go/src/runtime/asm_amd64.s:2197

Now everything seems to work fine- if nothing else it can serve as a band-aid for anyone else having issues until a maintainer implements a proper fix.

I don't see version 4 in Go 1.8 release branch: https://github.com/golang/go/blob/release-branch.go1.8/src/go/internal/gcimporter/bimport.go
I think what you're adding is from Go tip and @zchee is already working on it here: https://github.com/nsf/gocode/pull/417
Version 4 is the stuff with type aliases: https://github.com/golang/go/commit/49de5f035169526675b9d5897753d257bf2c7965
Since Go 1.8 won't have them, that's definitely from tip. So, just be patient.

Oh! That makes sense, I was actually really confused because I've been doing work in 1.8 and just changed to tip to commit / test it and figured it was working until then due to a ENV / $PATH issue. Sorry for the noise.


Add multi-arch container images to workflow

Add multiple arch container images resolves #2269

Description
Manager cannot run on arm64 machine due to non supported architecture.
NotFound desc = failed to pull and unpack image "ghcr.io/dragonflyoss/dragonfly2/manager:v2.0.9": no match for platform in manifest: not found

Motivation and Context
Multi-arch capability
Screenshots (if appropriate)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

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

I have builded multi-arch images in v2.1.0-alpha.4 release.


[#69] Fix bug found in FindCommand.

Fixes #69.
Find alex would no longer work and the application would prompt the user to enter a valid command format.

Codecov Report

Merging #73 (eee3c47) into master (bf24901) will decrease coverage by 0.02%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master      #73      +/-   ##
============================================
- Coverage     72.32%   72.30%   -0.03%
- Complexity      455      457       +2
============================================
  Files            77       77
  Lines          1384     1390       +6
  Branches        147      148       +1
============================================
+ Hits           1001     1005       +4
- Misses          341      342       +1
- Partials         42       43       +1

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/FindCommand.java
77.77% <ø> (ø)

.../seedu/address/logic/parser/FindCommandParser.java
84.61% <66.66%> (-15.39%)
:arrow_down:

...a/seedu/address/logic/parser/ArgumentMultimap.java
86.95% <100.00%> (+0.59%)
:arrow_up:

.../model/person/PersonContainsKeywordsPredicate.java
95.23% <100.00%> (ø)

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 bf24901...eee3c47. Read the comment docs.


"Grivița" is listed in the drop-down menu

Description:
"Grivița" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Grivița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Grivița, GALAȚI".


Can't stop loading :Extension issue

Issue Type: Bug
Extension Name: jupyter
Extension Version: 2021.6.832593372
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.56.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Thanks for the bug.
Do you have any more information? Is the jupyter extension just not loading?
Can you goto Help | Toggle Developer Tools and copy the console output here?

Please reopen when more info can be provided.


fix: exerciseType typo

Just a typo fix.  No references needed updating

By the way, thanks so much for this library!  I'm testing it out for an integration and everything has been very smooth.  Appreciate the documentation!

Thank you!


Warning upon first tooltip mouseover

Upon mousing over an element which creates a tooltip for the first time, a warning is logged in the console.
"Warning: React does not recognize the getRects prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase getrects instead. If you accidentally passed it from a parent component, remove it from the DOM element."
This happens with the example too.

Hey @marksiano, thanks for checking out vx!
Just curious what version of @vx/tooltip you are on and which demo example? This should have been fixed by #290 and in v0.0.163

Hi, thanks. This was resolved when I installed the new version.


 (try to follow "pkg/name: short description" format)

TL;DR
In the process of testing syz-manager locally, the target machine is linux/amd64, but the error message shows that there is no arm class system call instruction, which is very strange.
here is my cfg:
{
        "target": "linux/amd64",
        "http": "<IP_ADDRESS>:56741",
        "workdir": "/home/peiwithhao/repo/syzkaller/workdir",
        "kernel_obj": "/home/peiwithhao/Kernel/kernel_source/linux-6.7.4/",
        "image": "/home/peiwithhao/build/image/bullseye.img",
        "sshkey": "/home/peiwithhao/build/image/bullseye.id_rsa",
        "syzkaller": "/home/peiwithhao/repo/syzkaller",
        "enable_syscalls":["open","ioctl","write", "pipe"],
        "procs": 4,
        "type": "qemu",
        "vm": {
                "count": 16,
                "kernel": "/home/peiwithhao/build/image/bzImage",
                "cpu": 3,
                "mem": 2048,
                "qemu_args":"-enable-kvm"
        }
}

go: go version go1.23.3 linux/amd64
kernel : 6.12.1-arch1-1
syzkaller: latest

after i execute syz-manager -config=pwh.cfg, it happened
❯ ./bin/syz-manager -config=pwh.cfg
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-memwrite is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-vgicv3-its-cmd is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-vgicv3-its is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-smc is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-msr is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-vgicv3 is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm-vgicv3-cpu1 is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/arm64-syz_kvm_setup_syzos_vm is broken: unknown syscall syz_kvm_setup_syzos_vm
2024/12/02 17:21:10 seed sys/linux/test/syz_kvm_setup_cpu_arm64 is broken: unknown syscall syz_kvm_setup_cpu$arm64
2024/12/02 17:21:10 seed sys/linux/test/syz_kvm_setup_cpu_arm64-memwrite is broken: unknown syscall syz_kvm_setup_cpu$arm64
2024/12/02 17:21:10 seed sys/linux/test/syz_kvm_setup_cpu_arm64-msr is broken: unknown syscall syz_kvm_setup_cpu$arm64
2024/12/02 17:21:10 seed sys/linux/test/syz_kvm_setup_cpu_arm64-vgicv3 is broken: unknown syscall syz_kvm_setup_cpu$arm64
2024/12/02 17:21:10 seed sys/linux/test/syz_kvm_setup_cpu_arm64-smc is broken: unknown syscall syz_kvm_setup_cpu$arm64
2024/12/02 17:21:10 serving rpc on tcp://42709
2024/12/02 17:21:10 serving http on http://<IP_ADDRESS>:56741
2024/12/02 17:21:15 broken programs in the corpus: 0, broken seeds: 13

and then the website shows the fuzzer program has not been started...

most of the stuff in the dashboard are zero!!

cc @ramosian-glider

Let's remove these messages to not confuse users.

But as of now, when I try to use syzkaller, although I start the vm, the fuzz still does not start.

But as of now, when I try to use syzkaller, although I start the vm, the fuzz still does not start.

Please send an email to the mailing list with info about the problem.
The issue tracker is for actionable bugs in syzkaller itself.

The messages should be gone after https://github.com/google/syzkaller/pull/5560


feat: welcome releasepost experiment

A blogpost to introduce an experiment for republishing release notes

Thanks @gounthar for the reviews


streams: codecs not matched: H264 => VP8, RTX, VP9, OPUS, G722, PCMU, PCMA, TELEPHONE-EVENT, S16B, S16L

Hello,
when I try to access the http://<IP_ADDRESS>:1984/stream.html page I get this error in the logs:
DBG [webrtc] add consumer error="streams: codecs not matched: H264 => VP8, RTX, VP9, OPUS, G722, PCMU, PCMA, TELEPHONE-EVENT, S16B, S16L"

Same error with these URLS:
http://<IP_ADDRESS>:1984/stream.html?src=Gitter&mode=webrtc
http://<IP_ADDRESS>:1984/stream.html?src=Gitter&mode=mse

The RTSP camera stream is h264 from what I understand:
root@e4ce871a31f5:/root# ffprobe rtsp://<IP_ADDRESS>:554/11
Input #0, rtsp, from 'rtsp://<IP_ADDRESS>:554/11':
  Metadata:
    title           : 10
  Duration: N/A, start: 0.080000, bitrate: N/A
    Stream #0:0: Video: h264, yuvj420p(pc, bt709, progressive), 2560x1920, 12.50 fps, 12.50 tbr, 90k tbn, 180k tbc

Config file:
api:
  origin: '*'
hass:
  config: /config
log:
  api: trace
  exec: debug
  format: text
  level: info
  ngrok: info
  rtsp: trace
  streams: trace
  webrtc: trace
rtsp:
  default_query: mp4
streams:
  Driveway:
  - rtsp://<IP_ADDRESS>:554/11
webrtc:
  candidates:
  - <IP_ADDRESS>:8555
  listen: :8555

From further tests I discovered that it's working with Microsoft Edge, but not with Firefox 118.0.1. Anyway it seems very strange to me.
Have you some idea what the problem could be?

Your browser doesn't have support H264 for WebRTC. I never saw this.

Ok thanks. I uninstalled the browser, cleaned all data and installed the browser again. Now it works.


EIP 155 support for Ledger Nano S

Add support for the (unreleased on the manager, but available on github EIP 155 signing with app version 1.0.3 https://github.com/LedgerHQ/blue-app-eth/commit/54ea8ac82e381dc934e1718539b238072f83753a)

Also not directly related, but I noticed I had to push "Generate Transaction" twice on "Send ETH/Token" to see the signed transaction. Something probably broke in a difference place.

Now available on Ledger Manager for easier tests, edited the first post.


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/secrets-manager-secret-group/ibm (source)
module
minor
1.1.4 -> 1.2.0

terraform-ibm-modules/secrets-manager/ibm (source)
module
minor
1.3.1 -> 1.10.0

Release Notes

terraform-ibm-modules/terraform-ibm-secrets-manager-secret-group (terraform-ibm-modules/secrets-manager-secret-group/ibm)
v1.2.0
Compare Source
Features

added new endpoint_type variable to allow you to choose what endpoint to use when communicating with Secrets Manager (#147) (a74b03f)

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.10.0
Compare Source
Features

DA updates:- existing_resource_group has been renamed to use_existing_resource_group- kms_region input has been removed, its not porgrammtically determined- existing_kms_guid has been renamed to existing_kms_instance_crn and now required CRN value to be passed (#101) (ab617f2)

v1.9.0
Compare Source
Features

The following variables have been renamed in the DA solution:- existing_sm_kms_key_crn -> existing_secrets_manager_kms_key_crn- existing_en_instance_crn -> existing_event_notification_instance_crn- skip_en_iam_authorization_policy -> skip_event_notification_iam_authorization_policy (#105) (52fbdd3)

v1.8.0
Compare Source
Features

added the ability to optionally add a prefix to all resources created by the DA using the new prefix input variable (#99) (23c2542)

v1.7.0
Compare Source
Features

The following DA variables have been renamed:

sm_key_name -> kms_key_name
sm_key_ring_name -> kms_key_ring_name

(#93) (4593f02)
v1.6.0
Compare Source
Features

Add support to DA to provision IAM engine (#89) (9db51ed)

v1.5.0
Compare Source
Updates

The service_endpoints variable has been renamed to allowed_network and now only accepts the following values: private-only or public-and-private (#69) (1f9ff19)

v1.4.1
Compare Source
Bug Fixes

deps: bump kms-all-inclusive and IBM provider (#91) (3141151)

v1.4.0
Compare Source
Features

added new output secrets_manager_region (#88) (2a13066)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

This should be resolved when #24 is merged

secrets manager secret group adds endpoint type, this all that is causing the upgrade test to fail, so skip upgrade test
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185: Terraform used the selected providers to generate the following execution
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185: plan. Resource actions are indicated with the following symbols:
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:   ~ update in-place
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185: Terraform will perform the following actions:
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:   # module.secrets_manager_secret_group.ibm_sm_secret_group.secret_group will be updated in-place
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:   ~ resource "ibm_sm_secret_group" "secret_group" {
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:       + endpoint_type   = "public"
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:         id              = "us-south/79c6d411-c18f-4670-b009-b0044a238667/4dcc1608-a1d7-115f-ab71-507504b22635"
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:         name            = "sm-public-cert-upg-zipnai-certificates-secret-group"
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:         # (6 unchanged attributes hidden)
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:     }
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185:
TestRunUpgradeExample 2024-04-29T16:00:48Z command.go:185: Plan: 0 to add, 1 to change, 0 to destroy.

/run pipeline

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Bofrost.lu has degraded performance

In a1b2fc0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1469 ms

Resolved: Bofrost.lu performance has improved in 93c39e6 after 6 minutes.


Multiple fixes and updates

The following changes were made:
ParOpt-specific:

Compiler installation is only attempted if a Travis build is detected
mpicxx availability is added as a dependency
Cython is pip-installed

Other areas:

Basic compiler functionality is pretested for each of the C, C++, and FORTRAN compilers
If a "system" Python installation is being used instead of a personal/virtual, confirmation is requested to proceed (skipped on Travis)
Script won't continue if Python 3.x is not detected
numpy is pip-installed prior to the pyOptSparse build
The script detects the number of cores in the system, and does a parallel build using 50% (if there's more than one)
Options added to skip the compiler and python tests
A message about setting LD_LIBRARY_PATH or DYLD_LIBRARY_PATH is displayed at the successful completion of the script
README.md was updated with the newest usage

I tested this on Travis from my fork, but my account can't pull the SNOPT source directly, so I could only tell it worked where not having SNOPT wasn't an error.


Should one scale multi-dimensional targets when training with BMCLossMD?

Hello, thank you for this great work.
I am currently trying to train a network for multi-task regression using BMCLossMD. However, the distributions of the target variables are different. For example, one of them looks exponential, another one resembles gaussian and has 4x larger std then the exponential one. Should I then scale the variables to at least one std? The noise_var in BMCLossMD is 1D, so I assume yes but have no proof...

Hi Yanis,
Sorry for the late reply. I don't think it is neccessary to scale the variables, since the std in the loss function refers to the noise distribution not the label distribution. So the difference in target variable distribution should not affect the loss function.


Can a pre-trained model be called?

Could you please enlighten me on whether it's possible to leverage pre-trained models for training, given that training from scratch results in subpar network performance? Furthermore, I'm curious to know what constitutes an adequate amount of data, as the Oxford-Paris dataset seems too vast, and I'm wondering if a smaller dataset can still produce a satisfactory outcome

me too, i also wonder whether i need the whole dataset or a part of this dataset (just enough number of training set )?  Thank you at first.


Are bit commands not working as expected ?

Sorry for asking here, but perhaps wiki is outdated.
Here are problems I'm having
1) Is there limit on offset in BITPOS ? SETBIT is_renderable 1000025 1 followed by BITPOS is_renderable 1 1000001 returns EOF but BITPOS is_renderable 1 1000 gives correct position (integer) 1000013 Turned out it expects byte position, not bit position which is somewhat counter-intuitive since it expects bit position in GETBIT/SETBIT.

How do I scan in bitmap ? In Differences from Redis you mention bxscan and bxrevscan but LedisDB says these are unknown commands.

Thanks!

@unoexperto
Bitmap is treated as KV, you can not scan it directly.
For scan KV, you can use XSCAN KV SCAN cursor [MATCH pattern] [COUNT count]


New panels ideas and porting existing

I've looked around for cool panel in pyramid/django/flask projects:

git history: https://github.com/sjhewitt/django-debug-toolbar-git-panel
plot tables relations for sqlalchemy: https://github.com/uralbash/pyramid_debugtoolbar_sadisplay
replay ajax calls: https://github.com/jvanasco/pyramid_debugtoolbar_ajax

May be we should add some library like: aiohttp_debugtoolbar_extras or own repository for each task.

Missing templates panel for aiohttp_jinja2, obviously.

Calling async signals from sync render_string looks weird.