Our end goal is to modernise and make our behaviour around specificity and nesting spec-compliant, which will benefit the majority of our users.

As such, I think we can remove barriers that'll hamper us in achieving this for our next major release, including removing options that may no longer be relevant.

I suggest we remove the `ignoreSelectors` option (and related tests) as part of URL It may well be that everyone's use case is covered by:

If not, a person can open a new issue with their use case, and we'll decide on the most modern way to cater to it.

We've typically avoided broad ignore options like `ignoreSelectors` because of these types of problems. We've had better success with more focused ignore options like:

- `ignorePseudoClasses`
- `ignoreContextFunctionalPseudoClasses`

We can reach for similar options to cater to specific use cases.


I agree with replacing `ignoreSelectors` with more specific options. 👍🏼

Perhaps, I assume that CSS Modules selectors like `:global` or `:local` might be used in most use cases of `ignoreSelectors`. As we can regard them as *functional pseudo classes*, providing `ignoreFunctionalPseudoClasses` instead of `ignoreSelectors` makes sense to me in order to keep compatibility as much as possible.

E.g.

json
{
 "selector-max-specificity": ["0,2,0", {"ignoreFunctionalPseudoClasses": [":global", ":local"]}]
}

css
.foo .bar.baz {} /* '0,3,0' => reported */

:global(.foo) .bar.baz {} /* '0,2,0' => not reported */

So, I suggest the following steps:

1. Deprecate `ignoreSelectors` with the next *minor* version (16.x.0)
2. Add `ignoreFunctionalPseudoClasses` with the next *minor* version (16.x.0)
3. Remove `ignoreSelectors` with the next *major* version (17.0.0)


Thanks for getting back @drewid
Any chance this shows the values returned? Due to the backingStore, the properties may not show as the serializer will pick out only changed values after the response.

cs
result.BackingStore.InitializationCompleted = false;
var jsonString = KiotaJsonSerializer.SerializeAsString(result);


Thanks for raising this @drewid

The API will only return a limited number of properties by default and thus the $select parameter is required to fetch those properties.
With regards to displaying the results, the models used by the SDK should be serialized as pointed at here due to the custom serialization.

Any chance you can confirm this resolves it?


I will look into things further but if more work/serialization is needed then core graph documentation and examples needs to be seriously updated as it is very wrong.


A get should never just return changed values and that is not implied anywhere in the docs.


I will dig further but this is a royal mess.

- A default query should return all values.
- A select should return just those mentioned and not the slew being returned


I was able to run smoothly after setting the parameter 'ulimit -n 1000000', thanks!


I can look at this later today, I thought this worked when I tested it but I might be wrong.

Could you please send me a list of mods that you are using? It is very likely that another mod is overwriting the seed that you set


I read that this issue was not included in the previous release as mentioned in this comment , just wanted to ask whether we have an update on this or not.


Any progress on this? The first image comparison with TT4 might have not illustrated the issue very much because the difference was subtle. The extent of the disturbance depends on the design of the theme, and this example might illustrate the issue better The left is how it should be and the right is the current status.

Screenshot 2024-01-29 at 13 47 04


I am far from an expert in how those properties are handled in Gutenberg, but maybe changing the `prevent_override` to `false` solves the problem: link.

prevent_override => false

I've tested that and, making that change, it seems to work for my case:
* If I have a theme.json with sizes with the same slug as the default ones ("small", "medium", "large"...) the value from the theme takes precedence over the default value in Gutenberg.
* If I remove the `fontSizes` from the theme, they still appear now with the values provided by Gutenberg.

Is that what we want? If that should be the solution I can work on a pull request.


@kmranjo @sarahmhgov I think we are holding on this feature for a while now. I'm going to close this ticket.


@SantosGuillamot Thanks for taking a look! I've also been working on this and commented in the PR that caused the issue (#56661). It'll be helpful if you can review when I get it working.


Great to hear you are working on that 🙂

Oh, that's a pity. I can test whatever the solution is, although I'm not gonna be available until tomorrow.


@andrueastman Thank you for the magical code snippet regarding the BackingStore - I have no idea why that magically makes things work in making the serialization honor the select list (or at least properly trim the fields).

What is misleading though is that **the query still returns "every" field**, including the selected fields requested. The KiotaJsonSerializer is being applied after the fact and I can see the query is returning all the fields when doing a basic serialization of the result. This is remarkably misleading and incredibly wasteful. What has been implemented is not a select parameter, it's actually a "make sure to include these fields" parameter.

The information related to KiotaJsonSerializer and v5 breaking change regarding BackingStore needs a "lot" more information publicly. Is not listed anywhere in the normal docs and examples that I can see.

In essence, the standard described ways of doing QueryParameters.Select do not work without it (at least narrowing it down). It does include the fields selected, but also includes every other field.


I measured the voltage between sensor terminals to 6.6 VDC without sensors connected and 5.2 VDC with sensors. The current drain was 32 mAh.
6.6/.032 - (6.6-5.2)/0.032 = 162,5 Ohms
Tested with a 150 Ohm resistor, which resulted in 4.98 VDC across the terminals - didn't work!
I will see if I can find a resistor to get closer to the 5.2 V target and test again...


@jacobpoder

A resistor is not going to work. The GDO provides a voltage on the line and the sensors clamp the line to ground at at certain frequency for a certain duration (I can't remember the values, would have to put the oscilloscope on the wire again to look). Anyway, that's why you measure a lower voltage with the sensors on, but it's not a DC voltage, it's a square signal.

You could emulate it with a microcontroller and a transitor to clamp the line to ground for `x` ms every `y` ms.


@mariusmuja Sounds like the PWM used to detect faulty bulbs in my car... IIRC my multimeter does have a mode to detect duty cycle, so I guess I can try that...


Sounds reasonable.

In the meantime

shouldn't hinder that plan.
@romainmenke Either emend, remove or replace the 6 tests that are affected; we can discuss the details in the PR.

The documentation update could be skipped since we are planning to replace it.


Is strange that regular serialization does not work and only works with KiotaJsonSerializer. This is not documented anywhere obvious.


@Boyuan-Yu About one point having a longer description than another when 2 are in the same row, the designer says that we should have the point component fill the row, and pull down the Select as Lead button.

You can choose to take this on - but it's probably changes to the point component, or we can make a separate issue out of it and deal with it later.

Basically do you think this is an quick change or a hard one?

<img width="1353" alt="image" src=" URL


Sure

BepInEx-BepInExPack-5.4.2100
RugbugRedfern-Skinwalkers-4.0.1
CapyCat-Solos_Ring_Compass-1.0.3
AlexCodesGames-AdditionalSuits-2.0.0
x753-More_Suits-1.4.1
Verity-TooManySuits-1.0.5
x753-Mimics-2.3.2
anormaltwig-LateCompany-1.0.10
notnotnotswipez-MoreCompany-1.7.6
tinyhoot-ShipLoot-1.0.0
thomas-AlwaysShowClock-1.0.0
TheFluff-FairAI-1.3.2
Rune580-LethalCompany_InputUtils-0.6.1
Renegades-FlashlightToggle-1.5.0
Renegades-WalkieUse-1.5.0
2018-LC_API-3.4.5
EliteMasterEric-Coroner-1.5.3
CapyCat-Solos_Bodycams-1.0.5
MoreLethal-Pinger-3.2.0
boxofbiscuits97-QuotaRollover-2.3.0
Bobbie-MetalRecharging-1.0.0
Coomfy-CoomfyDungeon-1.0.12
amnsoft-EmployeeAssignments-1.1.0
Evaisa-HookGenPatcher-0.0.5
Evaisa-LethalLib-0.14.0
MegaPiggy-BuyableShotgun-1.0.4
MegaPiggy-BuyableShotgunShells-1.0.5
matsuura-HealthMetrics-1.0.2
Toskan4134-LethalRegeneration-1.2.0
Stoneman-LethalProgression-1.3.2
JunLethalCompany-GamblingMachineAtTheCompany-1.3.5
MikeMediaStudios-MikesTweaks-2.0.2
MoonJuice-BuyRateSettings-1.3.1
Sligili-HDLethalCompany-1.5.6
akechii-DiscountAlert-2.3.0
Ozone-Runtime_Netcode_Patcher-0.2.5
AlexCodesGames-AdditionalContentFramework-1.0.3
HomelessGinger-MaskedEnemyOverhaul-3.1.1
ATK-LaterNights-0.9.1
Ozone-BepInUtils-1.2.1
Ozone-Glow_Steps-1.1.2
Pooble-LCBetterSaves-1.7.3
CTMods-KarmaForBeingAnnoying-1.1.0
zerouni-CustomRadio-0.1.1
rafl-CustomBoomboxMusicFixed-1.0.2
Mom_Llama-Lethal_Company_Enhancer-0.1.10
sunnobunno-YippeeMod-1.2.3
Azim-HoarderBud-1.0.10
blink9803-AutoFlyToCompany-1.0.1
darksnakex-NoCorpseHigherQuota-2.5.0
IntegrityChaos-Diversity-1.1.10
Suskitech-AlwaysHearActiveWalkies-1.4.4
FlipMods-TooManyEmotes-1.8.3
AllToasters-SpectateEnemies-2.2.1
Blorb-WeatherMultipliers-1.1.0
Sv_Matt-HideModList-1.0.1
PortableNavi-BetterInverseTeleporter-1.0.2
no00ob-LCSoundTool-1.5.0
Clementinise-CustomSounds-2.3.2
SkrimpGang-AAAAAGHH-1.0.1
darmuh-ghostCodes-1.5.1
F4ilS4fe-MaskTheDead-1.0.5
Dev1A3-ScannableCodes-1.0.2
ButteryStancakes-AccurateStaminaDisplay-1.1.2
OE_Tweaks-Possessed_Masks-2.0.2
extraes-LethalLoudnessMeter-1.0.2
ZG-ScalingStartCredits-1.0.6
Electric131-IsThisTheWayICame-1.1.4
SoraYuki-ShowAmmoCount-1.1.0
MaxWasUnavailable-MoonOfTheDay-1.0.4
Sligili-More_Emotes-1.3.3
Rattenbonkers-Teleporter_Cooldown_Reset-1.0.1
TwinDimensionalProductions-CoilHeadStare-1.0.3
FlipMods-ObjectVolumeController-1.0.4
eXish-Batteries-1.0.4
AgentRev-ShootableMouthDogs-1.0.1
CyanBlob-Motion_Tracker-1.0.0
ScruffyRules-BatteryText-1.0.0
CTMods-ChatCommands-1.1.7
FlooflesDEV-LCSeedPicker-1.2.1


I could try it on a very basic modpack (just the seedpicker installed) to see if that changes anything, too


I have found the conflicting mod: it is MaxWasUnavailable-MoonOfTheDay-1.0.4

When that mod is disabled in my modpack, that seedpicker works as intended. When it is enabled, the seedpicker is ignored


one more advantage of the data.table syntax/API for arrow (R package)? I naively URL


Thanks for confirming @drewid . Since this is related to the discussion in URL We will close this and follow this up there


Thanks for the feedback here @drewid

Just to clarify, what is indeed happening is that API is indeed only returns the fields selected(This can be confirmed using the Graph Explorer ).
However, the model properties will by default read as null by a serializer if they have not been set due to the proxy mechanism used by the backing store. The `KiotaJsonSerializer` is built for this and can be used to get back the Json received or to be sent out by a given execution call.

This indeed should be better documented, and we've created URL to update the v5 documentation here.


I don't know what the problem is, but this is very unlikely to be a Ren'Py problem. Other than positioning the window where you last place it, Ren'Py is working the same way regardless of monitor. I'd suggest reporting this issue to Nvidia to see if they can help as all.


Noting that while the front end is better/fixed, the font sizes in the editor (Typography > Size) are still being hijacked by core sizes. In other words, the screenshots from my comment above are still in an issue.

cc: @annezazu for visibility and @iamtakashi to confirm if seeing the same thing.


To re-iterate, these were just taken with/without Gutenberg 17.6.0-rc.3 active.

**Gutenberg not active:**

image

**Gutenberg active:**

image


Just reopening if this is still an ongoing issue and not fully corrected with the latest change.


@bgardner - Just to help me understand the current issue:

From what I'm seeing in your latest screenshots is that the core sizes are listed above yours. If that is the only problem, there's a separate issue for that: URL

Or is it that your custom sizes are not working still?


This should work as a quick fix for disabling the default font sizes, but I'm pretty sure the CSS for them won't be printed either:

php
add_filter('wp_theme_json_data_default', function($theme_json) {
 $data = [
 'version' => 2,
 'settings' => [
 'typography' => [
 'fontSizes' => []
 ]
 ]
 ];

 return $theme_json->update_with($data);
});


@juniorthejunior Have you tried completely uninstalling the Nvidia Drivers, downloading the latest from Nvidia, restarting Windows, and Reinstalling the Drivers? Going into Device Manager, right-click on the video card(s), click on uninstall, and click the checkbox that Asks if you want to Delete Drivers. It will probably be something Nvidia will ask to see if it is a problem with their drivers, or if it is a problem with your currently installed drivers.

One thing about "updating drivers", it may not ALWAYS put the newest version of everything. There could be a lingering issue that could cause odd behaviors.

Additionally, they also may ask you if this happens in another profile (Username). Corrupted (or starting to corrupt) profiles can cause wide range of weird issues. It will help both them and you determine if it is system-wide or just account-wide.

Just two things to check that I did not see in your lists because I do not know how quick Nvidia is with responding to support requests.


@justintadlock I see that this exists: URL

The problem is that in the editor, where there are font sizes names common with core/default themes and my Frost/Powder themes (Small, Medium, Large, and Extra Large in this case) the drop down menu shows the core values and not my theme values. With the revert in URL the issue is no longer on the front end out of the box—just when text is given any of those sizes listed above (in which case it becomes a front end problem.)

In English: if a theme declares font sizes that are identical to the ones in core, core should defer altogether (front end, back end, site editor) to the theme.


@justintadlock Can confirm the filter above is working perfectly and as expected. CSS is printed and Small, Medium, Large, and Extra Large sizes show correct values in the Typography > Font Size menu in post editor as well as correctly on the front end when chosen.


We can't expect theme developers to add this filter as a long term solution.


@carolinan Agreed. I was merely confirming it worked to see if it helped inform a permanent fix in core.


Hi - I have this exact same issue, also have no sensors, and with the black wire disconnect, close command doesn't work.

If needed, my logs are at URL

Also, happy to provide any additional logging if it will help?

Is there an interim solution, where the "toggle" command could be sent in place of "close"?

Thnx


For me I have turned off every style, but with Gutenberg 6.4.3 (since 6.4.0 iirc) font size is back

`theme.json`:

json
{
 "$schema": " URL
 "version": 2,
 "settings": {
 "appearanceTools": false,
 "typography": {
 "defaultFontSizes": false,
 "customFontSize": false,
 "lineHeight": false,
 "dropCap": false,
 "fluid": false,
 "fontStyle": false,
 "fontWeight": false,
 "letterSpacing": false,
 "textDecoration": false,
 "textTransform": false,
 "fontFamilies": [],
 "fontSizes": []
 }
 },

The font size control is back, making the whole "Styles" tab appear:

image


Thanks for the suggestions. Followed the steps - deleted via Device Manager, restarted, installed 551.23 (the latest), restarted - and the problem still persists. I also repeated the process except uninstalling the driver using DDU (a third-party "deep uninstaller" of sorts), and that made no difference either.

Also made a new Windows account/profile, downloaded and ran Ren'Py 8.2.0 and the results were the same there as well.

I'll have to put together a report to NVIDIA at some point in the future, though at least for the time being, I am disabling this feature entirely in my project, since I personally would not want a player to encounter it and have them have to deal with it (however rare it might be; if it's happened to me, it'll happen to someone else), especially for a mostly QoL feature.


Since this issue has been reopened, I will also change the project board status from "Done" to "ToDo".


I was able to build on virtualbox based ubuntu 22.04. It needs openscenegraph 3.4.1 and osgearth 2.9.0. Follow directions on URL for Linux build but use GL2 instead of GL3:

git clone URL
cd OpenSceneGraph
git checkout OpenSceneGraph-3.4.1 # ==> this is new
mkdir build && cd build
cmake .. -DOPENGL_PROFILE=GL2 -DOSG_GL_CONTEXT_VERSION=4.6 # GL2 instead of GL3
make -j8
sudo make install
cd ..
git clone URL
cd draco
mkdir build && cd build
cmake .. -DCMAKE_CXX_FLAGS=-fPIC
make -j8
sudo make install
cd ..
git clone URL
cd osgearth
git checkout osgearth-2.9 # ==> this is new
mkdir build && cd build
cmake .. -DOSGEARTH_ENABLE_FASTDXT=OFF
make -j8
sudo make install

Then in config.user of omnetpp, change `WITH_OSGEARTH=no` to `WITH_OSGEARTH=yes` and build omnetpp using `./configure` and `make`.


Yes @kyl416 , I saw #657 . This entry has now been closed with the result that everything is working again. This is also the case, with the exception of the DAZN channels. Maybe @matthuisman no longer wants to support this because of the topic described?

Greetings Weri


That sounds great!

What do you think about do a PR do create a new dockfile for Ubuntu 22.04?


Quick one @Rotfuks, URL do you think we need both of the issues still? I guess the other is more about a whitepaper than the research, but did want to point out...


Hmm good point @loujaybee - that ticket still seems to be pretty valid for what we're doing there. And I even commented there, so I should know it! :laughing:

This one was the outcome of a discussion around the next steps for the initiative and how to formalise and make the work more transparent in the scope of our working group.
The other ticket sure has way more text to go through - but it also with that has all the context and the action items that we're listing here. What do you think @mluskind, should we keep this "smaller" epic here or use the original whitepaper one?


Just talked to @mluskind, yes makes sense to close this as a duplicate and put some effort in the original ticket where people might already watch for updates. Thanks for the heads up!
And sorry @abangser for closing it while you just labeled it :heart: :laughing:


So I used the latest language pack from official update site (pls see the screenshot),
image

the unpacked .jar already contains required fix
image


thats not the case. the dazn channels are there. its just they need to switch to v2 hls manifest


Looks like GitHub Actions now has free M1 runners. That should make it easier to get builds running: URL


Ah ok @matthuisman , where can this setting be made? Or does your addon need to be adapted for this?

Greetings Weri


By the way, the build is successful but when running any showcase, I get an error "simulations stopping with assert currentTimes.simTime <= simTime()". I have created a separate issue for this.


@ddfridley It should be a quick fix. Let me see what I can do.


I agree that it's confusing, and seems to leave the compiler as a guide to where to use the discards because it's not readily apparent where and why they are used. Maybe at best it's a preferable alternative to `#pragma warning disable CS4014` and at worst, it's confusing without a comment in the code to explain the purpose?


I forgot to mention earlier - that due to the issues with the esphome firmware, I have been running the MQTT version. MQTT appears to work with cover.close in home assistant. Unsure if the command "close" actually uses toggle internally or not, but sending the cover.close command from home assistant does close the garage door via MQTT. Unsure if that means that the GDO is receiving a close command correctly or not, as MQTT may be received and simply toggle.

May not be useful information but in case, I thought I would comment.


Hello Everyone!
I would like to work on this issue as part of the LFX Mentorship.


I have almost the same problem, but with a strange twist. IF i connect the black wire then my problem is exactly like the one described earlier, aka. everything else works except "CLOSE". If I disconnect the black wire as is instructed (I don't have obstruction sensors) also OPEN function stops working! However "TOGGLE" still works.


As for the people trying to emulate obstruction sensor, it is surprisingly difficult, I tried with manually adjustable electronics circuit without success.

With a microchip controlled oscillation it works... for a time. It seems I have a bug in control software and it eventually somehow goes off sync because it stops working. I haven't continued with this as it seems to be really difficult to emulate the obstruction sensors and was hoping for an easier and more reliable solution with ratgdo :)


Hi @xmulligan! I'm Abhay. First and foremost, the project is thriving. I have successfully applied to the mentorship program and completed all the pre-tasks. I am eagerly awaiting the opportunity to work with you, learn more about the projects, and delve into interesting challenges.


Docs are correct, `color=tomato` will only show in the editor log (since it's RichTextLabel and support all colors), but won't show in the OS terminal.


I was working on implementing arbitrary color code conversion to truecolor ANSI escape codes, but I couldn't get it to work yet.


Oh okay I wasn't aware that this was related to the terminal! The fact about bbcode to ansi conversion is only mentioned a bunch of lines below so I thought that it applied to the Godot output.


Hello, thanks for using the project, and sorry for the slow response!

This 'currentTimes.simTime <= simTime()' error happens when the "RealTimeScheduler" can't keep up with real time. The scheduler is the OMNeT++ class responsible for dispatching events in the correct timings, the RealTimeScheduler provided by INED dispatches these messages to try to keep the simulation synched with real time. When the simulation is too slow (could be too many vehicles, computer resources, overhead from the virtual machine, etc.) the scheduler raises these exceptions.

An easy workaround is to simply remove the RealTimeScheduler, it should be on your .ini file with the key "scheduler-class". Removing this loses you the guarantee that your simulation will be synched with real time. You can still get pretty good results by manually controlling the simulation speed to approximate real time. If being precisely in synch with real time isn't one of your requirements, I would highly suggest this solution. If you do want to keep things synchronized, I'm afraid you will have to opt for a lighter simulated scenario

I was never able to figure out the exact mechanism that causes this assertion to fail. I highly suspect it's some implementation detail of the RealTimeScheduler class that I just never figured out. If I ever do, I will make sure to include a patched version of the class with the simulator. If you find a solution or the root-problem, please share it with us!

Also, I made a new .ova file to use with the new version of the simulator, that should help you with the setup if you are having trouble with that: URL


@klonikar hello! I am also having trouble setting up GrADyS-SIM with OMNeT++ 6 on Windows. While I haven't quite figured out the root cause yet, I have created a new .ova virtual machine image in case you want to use it: URL

I saw that you also got the same idea as me of setting the simulator up on a Linux virtual machine, that's great! If you have any trouble, try the .ova image above and see if that helps.

Also, replied to you on your other issue about the SITL integration.


Thanks for opening this for discussion @cshintov . To summarize, wander currently has 2 levels of drill-down: 1) jobs and 2) allocations and tasks combined in one table. This proposal would change that to 3 levels: 1) jobs, 2) allocations and 3) tasks, more similar to the web ui's model.

I'm interested in getting more data before proceeding with this change, as I personally see the 2 level model as an advantage, but am open to shifting to 3 level if there's broader support.

Ah, that's super annoying behavior! Broke it out into a bug issue here: URL

If you run wander with `--filter-with-context=false` or the equivalent env var/config option, it will only show matching rows

If you want to extract out the alloc restart functionality and PR just that against `next` right now in a separate PR, we should be able to get that merged quickly regardless of the outcome of this drill-down discussion!


@coderigo @classabbyamp @qwo @viniciusartur @Antse @sheridanvk @ghthor @yuankaiyu @hoppel @chuckyz @foozmeat @neomantra @bbarg @dbalan @beakman @moyiz ,

You've all contributed to or opened issues in wander before. Assuming you are or were users of it, what do you think of this proposal:


@cshintov this should be fixed in `next` (`go install github.com/robinovitch61/wander@next`) now. Mind giving it a shot when you get the chance and letting me know if there is any other undesirable behavior?


Thanks. I will try out your .ova VM, though now I also have a virtualbox VM where gradys is built. I kind of gave up widows, and went ahead with VM. I think the first root cause is that the Makemake is not generating a proper Makefile to build the gradys related sources into obj files. When I hand modified the Makefile to build it, I am getting several "undefined symbol" errors for symbols in inet lib as well for winsock lib.

ld.lld: error: undefined symbol: inet::ClockUserModuleMixin ::exponential(inet::ClockTime, int) const
ld.lld: error: undefined symbol: __declspec(dllimport) WSAStartup
ld.lld: error: undefined symbol: __declspec(dllimport) socket

We need to add more `-l` options to the linker cmd line. But not sure how to fix the issue for building gradys sources.

I also have a linux machine where the build works fine but I get the simTime error.


Thanks for responding. I will try out the removing the RealTimeScheduler. At this time, real timeness is not a strict requirement for me. I do not know why is it not able to keep up with real time even when trying it on a quite powerful linux machine and the default ini file **showcases/sitl/simple_simulation/omnetpp.ini** config **SimpleSitl** config which has `*.numUAVs = 2`.
If I find a workaround/solution, I will certainly share.

Do I need to replace the RealTimeScheduler with something else or simply remove/comment the line?


Wanted to add my support for this request. Often I will be switching between the data wrangler view & my jupyter notebook and it is frustrating to have to close the bottom and side panel. Awesome extension though, thanks for the extension!


The simulations are working now after commenting out the RealTimeSimulator line. Among the 4 sitl showcases (gradys-simulations -> showcases -> sitl), 3 are working. The simple_simulation (SimpleSitl of ini file) starts but the vehicle does not move. I changed the waypoints file also but there is no movement. I think the logic in DroneMobilityMav::readWaypointsFromFile in DroneMobilityMav.cc may have something to do with it. Your if-else statements are processing GOTO, TAKEOFF, RETURN_LAUNCH commands but the file has only GOTO and REVERSE commands. In this function, you are not calling queueMessage like you do in MAVLinkFileMobility::readMissionFromFile and MAVLinkFileMobility::startMission.

The file mission.waypoints for file_mobility_simulation has more command types.

I am not that familiar with omnet++ so I could not dig further.


Can provide an update on the domain block weight limits? As of now we still have `MAXIMUM_BLOCK_WEIGHT: Weight = Weight::from_parts(u64::MAX, u64::MAX)` and without an actual limit it can't be guaranteed that a fraud proof will fit into the conensus chain block size limit.


Hi there! I am Rudraksh, the project on Cilium governance documentation looks pretty interesting to me. While considering the points mentioned by @xmulligan @joestringer & @aanm. I performed a data analysis on the repos under Cilium project using Pandas. I came up with some figures with Cilium as:

image

I am looking forward to leveraging it further, to get more details about the individual projects which can help while defining lifecycle. While I found the Falco project repo lifecycle structure to be an excellent reference, I understand that we may need to make certain adjustments in the context of Cilium. I also came across CNCF governance templates which has been incredibly helpful in learning about governance in open source.

In the latest, review of Cilium governance the essence of contributor ladder was one of the major feedback/reviews by TOC, is this an aspect we should prioritize in the context of the Cilium governance project?


I'm personally a fan of the existing drill down levels, though I haven't run into a case as the OP where it is hindering any of my workflows.

My question to the @cshintov. If you could group/sort by the alloc ID in the combined view, would that improve your workflow? That's an additional sorting mode, where the current sorting mode is based on the task name only.


I think the original issue caused by URL which was resolved when we reverted in #58456.

The original issue ( URL is still open, as is this other one about duplicate font sizes: URL

I think these two issues cover all the currently known bugs, so I'll close this one in favour of them.


I have removed this from the Polish board is it's too big to go into 6.5.


This is likely due to what I do here

I set the seed override to false when you're not at a MoonOfTheDay moon.

Looking at their code (which they mention is heavily inspired by MoonOfTheDay), they seem to touch that variable at the same time. So it'd be down to whichever mod loads first, as that one will be overridden iirc.

I think they can fix it by adding a soft dependency to MoonOfTheDay, which should cause their mod to be loaded after mine. Alternatively, they can set their patch to run last.


Crossposting from the issue on my end:

 URL

Should be an easy fix if you set your patch priority to run last @FlooflesDev


@tomasz-c OK, good point!

Here is what the app currently does:

The first time a watch tries to connect, the app will pair with the watch automatically.
From then on, it will only pair with the same watch until you press the "FORGET" button.
If you try to connect another watch, it will fail.
You can test this by resetting your watch to factory default and trying to connect. This will fail because the Bluetooth ID of the watch changes when reset, equivalent to connecting a new watch. To connect the watch, you must press the "FORGET" button. (Prior to version 11.9, I have gone back and forth allowing all watches to auto-connect because some people have requested auto-syncing multiple watches, but now only one watch can connect until "FORGET" is pressed).

Now, the only way somebody else can connect to the watch is if they are running the app and have not yet paired it with a watch. This can happen when the watch auto-syncs, and they are nearby, like on a bus (a very rare event, I can only hope this app is popular enough for random people to run it on the same bus). In this case, they will not be able to see the Google reminders in the app, but it is possible to send their reminders to your watch, which is, of course, a problem.

Auto-pair is generally a good feature. The app can connect to watches ad-hoc, even if they are not in the supported list. People like this feature, and I would like to keep it.

To address the rare possibility of sending the wrong reminders, I will arrange the app not to send reminders if this is the first time they have connected to this watch.


@tomasz-c The scenario you described in your comment is kind of expected behavior though. If watch A was previously connected to this app, it simply connected to this app again and got reminders from it. The same reminders will show up in the official app.

If you really wanted only watch B to connect to this app, pair it, and do not press the "FORGET" button. Watch A will not connect to the app. This is what should happen in version 11.9 and later of this app. Let me know if this is not what you see.

Generally, I recommend running only one app, not both.


That's because the mqtt version only uses toggle commands.

If you click close, and the door is already closed, the mqtt firmware won't send any wireline command at all (and vice versa with open).

The ESPHome version sends a command no matter what and lets the GDO decide if it should ignore it depending on the state. The problem here is that ROW openers which have optional obstruction sensors (they are mandatory in NA) ignore the explicit close command if no sensor is connected.


I thought that may be the case. Interestingly chamberlain make a point of saying the obstruction sensor is optional in nz, and it has an obstruction reverse feature built in if the GDO senses an obstruction. It is really effective.

@PaulWieland Is it likely to work around it in firmware? I am holding off getting the obstruction sensor, but if you think it is a while odd or very hard to do/a compromise functionality wise, I will order them in from the US. Ones available in nz are super expensive. :)

Thanks I advance!


Get-PnPUserProfileProperty works with -ClientSecret but not working with -Thumbprint. Getting Access Denied.


The advantage of using a close command vs a toggle command is that the result is a closed door even if ratgdo has the incorrect door state. The disadvantage is that some (all?) GDOs ignore it if no obstruction sensors are connected.

We could add a feature flag allowing the user to select the behaviour they want.


Better documentation will be great because it is 100% not intuitive and not at all clear.


I did some tests with my two watches, GW-B5600 and GAB-2100, and the app worked as expected for me (with some small display issues, which I will fix in the next release). Basically, if the watch is already paired, another watch cannot connect unless the "FORGET" button is pressed. I made a video to ensure we are on the same page:

Watch Connection Video

If you actually connect and are able to get to the TIME screen without forgetting, there may be some problem saving to the LocalStorage of your phone, since the paired watch info is stored there. I'm hoping that this is just a display issue, as shown in the video.

Regards


I too like the current drill-down levels, I don't know that layering it one
extra level adds much from when I've used it as by the time I get to a job
things tend to easily fit on one screen without paginating and it's obvious
which alloc belongs to which task.

On Tue, Feb 6, 2024 at 3:14 AM Will Owens ***@***.***> wrote:


Ya, this could work if combined with `--filter-with-context=false`, **but still more work - more key presses and brain cycles**.


Is the ratgdo hardware capable of controlling the 6v output of the obstruction pin-out, or is it just passthrough? I noticed that there is a loop function to check the high-low transformation on the obstruction signal which could possibly be also used to emulate the high-low transition every 6.5 ms?


@Thlamz your OVA is ubuntu 20.04 and all the simulations are working with RealTimeScheduler enabled. Can you briefly describe your changes?

I see that your omnet++ is also built with OSG, OSGEarth but map imagery is not visible. Possibly that makes a difference as CPU does not have to render it.

Even the **SimpleSitl** is working (I only changed the paths to point to ArduCopter.elf and param files): The two quad vehicles properly go to sensor[0] and sensor[1] and return.

The only differences I see are ubuntu 20.04, python 3.8 instead of 3.11 and the git branch th-fixes instead of main... Even after shifting to main branch, SimpleSitl works. I am not clear why does it fail in my environment.


I fixed the issue with the latest PowerShell module on Powershell 7.2 with the command "Sync-PnPSharePointUserProfilesFromAzureActiveDirectory" all information is well documented: URL

The service principal needs to have the following rights:
Graph API:
[User.Read.All]

Sharepoint API
[User.Read.All]
[Sites.FullControl.All]

Which will look like:
 " -AppRole "User.Read.All" -BuiltInType MicrosoftGraph`
`Add-PnPAzureADServicePrincipalAppRole -Principal " " -AppRole "Sites.FullControl.All" -BuiltInType SharePointOnline`
`Add-PnPAzureADServicePrincipalAppRole -Principal " " -AppRole "User.Read.All" -BuiltInType SharePointOnline`

Then also grant the permissions in Sharepoint:
App permission:
`
`
I suspect that this rights package will help in granting rights also for Set-PnPUserProfileProperty, but I started using the latest module because it adds support for using System managed identities and User Managed Identities which I'm using in combination with a automation account to sync the attributes from Azure AD to SharePoint.

The script looks like this:

Connect-PnPOnline tentantname-admin.sharepoint.com -ManagedIdentity -UserAssignedManagedIdentityClientId "Service principal ObjectID"

$users = Get-PnPAzureADUser -select "OnPremisesSamAccountName"

Sync-PnPSharePointUserProfilesFromAzureActiveDirectory -UserProfilePropertyMapping @{"UserName"="OnPremisesSamAccountName";"CellPhone"="MobilePhone"} -Users $users -Folder "Documents"

Disconnect-PnPOnline


@jakoblell We are aware of this. We will prioritse this change soon and post a follow-up pr with proper extrinsics limits. Thank you!


@klonikar I only changed configuration and build stuff. The main things I remember:
- Some of the paths set in Paths and Symbols were absolute and invalid on my machine, so I changed them to the proper ones
- I added the -lpython3.8 flag to get the python integration to work.
- Changed the protocol path for all modules that used the python integration
- Changed the .elf and param file paths for all modules that used the SITL integration
- The python sample in the showcases folder was completely broken, it's still a bit broken but at least it opens now, the python files were completely missing in the repository

You can see the full changes on PR #33. It's still being reviewed, which is why I didn't merge it yet.

I chose Ubuntu 20.04 because I always had trouble installing OSG on Ubuntu 22.04, which I think you yourself described here: URL

The map imagery really is not visible, even though I saw no visible errors. I am sure that with this same installation using python 5.6.2 the map imagery used to show. Since it was only visual I didn't investigate further, assumed it was just an incompatibility between OMNeT 6 and the OSG libraries. Your comment that it worked on Ubuntu 22.04 left me curious, I'll try to investigate further.


@klonikar fixed it and reuploaded the images! You can download the new one here. In case you don't want to redownload the image, the fix was very simple, just set the environment variable MESA_GL_VERSION_OVERRIDE=3.3.


That was quick 👍
I wasn't really complaining about the imagery not there... Rather, I thought the SimpleSitl worked because imagery was not there!! Thanks.


Thanks for the detailed reply. There is nothing in the PR that will solve the problem for SimpleSITL and also the RealTimeScheduler... Its only some added python files and change to use python 3.8 which is default for ubuntu 20.04.

This leaves me to wonder why does it work in your OVA but not in my real ubuntu 20.04 machine or the 22.04 OVA.


Yes, I also have problems with cloudflare and the DNS proxy, I had to remove it and expose the public IP.
I have a pfsense firewall with HA proxy with ACLs and I have thus secured my infrastructure.Even Alexa doesn't work for me with the proxy active, I haven't figured out why yet but the HA app doesn't work for me either!
Indeed, if you know how to solve the problem with Alexa and the HA app, maybe we can find the root cause of the problem also for sending data from Legrand!


Although I understand why the Web GUI is that way, I find myself jumping a lot between the Alloc/Task windows in the Web GUI. And very often I want to check out the `alloc` files but that's not directly available from the `task` so you have to jump around, etc. But then for an alloc you often need some minor task info and need to pop into the task page.

So I like how `wander` does it currently, but I don't have as many allocs/tasks as OP.

I thus appreciate that one drills down from Allocs into a Task; but I'd still want the current display at the Alloc level.

The power of TUI is that you can get to the where you want very easily -- enter/escape into a Task view is consistent with this. That said, if a filter/sort helps achieve the same, then that might be simpler.

Is there any particular content/UX in a Task pane that would be different than the Alloc-focused pane? In OPs example, they look identical.


I wish I could help you but I have no way to expose Homeassistant other than with the Cloudflare tunnel because I'm behind a 5G connection with double NAT and I have no other way to publish externally. I have Alexa but not configured in Homeassistant, for now I let it work on its own. The strange thing is that the Companion APP works correctly, wouldn't it be necessary to also put the ports (MQTT?) used by the thermostats in the tunnel?


It doesn't use mqtt, the data arrives via http post on a ha webhook


@tomasz-c Here are a few things to try:
- Make sure you have all permissions for the app enabled, especially read/write permissions.
- Try using a different phone with the two watches. This will eliminate the posibility that the problem is related to the phone setting/Android version.
- Regards


I will check it and let you know.
Currently, I have recorded a video of how the application behaves on my smartphone, so I am sharing it:
 URL

I will check it and let you know. Currently, I have recorded a video of how the application behaves on my smartphone, so I am sharing it:

The application is launched immediately after clearing the data.
0:03 - information about the program, with visible version,
0:13 - GST-B500 pairing
0:23 - disconnected
0:32 - MSG-B100 pairing
0:43 - disconnected
0:50 - GST-B500 pairing
0:56 - disconnected

I didn't use FORGET here.
This is Android 14, tested on the v12.0 app from Fdroid and Google Play.
By the way. If you release a new official version, would it be possible to include on GitHub the apk there in addition to the source code, as other projects do? This would allow to test new versions quickly.

Regards


Hello @yrodiere

We haven't set anything specific for that parameter, so we just use the default.

We detected the issue when running our Quarkus app on OpenShift.
We have a batch with a long transaction that inserts records in a database.
Of course we expect that either all the records or none are inserted.

When a redeploy is done in OpenShift while this batch is running, we end up having partial data.

When running the standard `mvn quarkus-dev` + CTRL-C locally, we could not replicate this issue.
When pressing CTRL-C the process is terminated and the prompt is shown instantly.

When running the quarkus:dev via java.exe + CTRL-C locally, we were able to replicate the issue.
When pressing CTRL-C it takes a while before the process is terminated and the prompt is shown.

This led us to the conclusion that the shutdown method is somehow involved.
When the issue occurs it seems that the connection is explicitly closed, causing Oracle to commit on close.
When the application is instantly terminated there is no issue since Oracle does no commit when the connection is lost.


This is a great idea. What if we sorted such that the "all tasks for job" page's first rows were the first task in each allocation, eg

Alloc A Task 1
Alloc B Task 1
Alloc C Task 1
Alloc A Task 2
...

And pressing "t" on one of these rows brings you to a "tasks only for this allocation" page. Do you think this is a nice middleground @cshintov ?


On Android 10 with your application, this situation does not occur, the second watch does not pair, it has ERR.
After restarting the application, I can pair the second watch without using FORGET, but this is probably intentional.

On Android 14, there is no read/write access (data access) in the permission settings, so you can't grant it even manually. On Android 10 this is possible. So I guess you had a good idea to check it out.
I don't know which Android version you are using, maybe it's due to a change: URL


Hi @matthuisman I noticed that after a certain time the stream from DAZN Darts x PlutoTV simply stops and ends up back in the Kodi main menu. It is irrelevant which Kodi version is used. Is this due to the addon or Inputstream.adaptive?
Greetings Weri
kodi_plutlo_omega.log


OK, thanks for helping thack this issue. I will look into getting it to work with Adroid 14, and aslo making other small fixes. Should take a couple of days.


So, looks like the Android Version is not causing the problem. I ran the app with an Android 14 emulator (Pixel 3a API 34), and I can read and write from local storage.
Which phone make and model are you using?


@scruffian I'm a bit confused by this last comment. Can you clarify? I've added it to the 6.5 board to be safe as it's clearly impacting theme authors and seems important to get fixed. Ideally, this is resolved for 6.5 but I definitely want to understand more if/why that might not be feasible.


I'm experiencing the same issue. In my case, I have a page that calls `parent()` and an invalidate call in the layout that redirects to `/login` when an auth check fails. Previously that worked just fine, but now it gets stuck showing the same page, but loaded with `/login`'s page data.


I think this is the reason why I want a focused view, and others don't. At small numbers (without many sidecars) it doesn't matter much.

Ya, the above proposal might work, but I don't think it's needed, because without `filter with context` there's already a middle ground.

But if the majority of users are fine with the current view, it's OK.

Besides, I can maintain my own version for my use case; that's the beauty and purpose of open source, isn't it?


@Thlamz I think I found out the reason for RealTimeScheduler not working. When I changed the build type to debug (for both gradys-simulations and inet4.5) in your OVA VM, I always get the simTime() error. When I change it back to release build, I dont get it.

Then I created a brand new ubuntu 20.04 VM, installed all the required packages as given in omnet++ InstallGuide.pdf, including osg, osgearth. Changed the configure.user to enable osgearth, built the osgearth, inet4.5 in release mode... finally built the gradys-simulations in release mode and launched SimpleSitl.

I will close this issue unless you have something to add.

image


We put in a fix for this, but it ended up creating worse bugs, so we took it out again. We are still working on a fix, but it's going to take longer than we have before the cut off. I hope it will make it into a Gutenberg release soon :)


@klonikar Nothing to add! OMNeT does tend to run much slower in debug mode, so what you said makes complete sense.


I agree with @carolinan on this, it is inconvenient to ask to touch two places to configure the theme but at the same time I think it is nice to give the opportunity to confiugure the theme dynamically.

I've seen some options line `blockGap` accepting three values, `false`, `true`, `null` triggering different results. Could be the same for the collections, something like `false` deactivate the feature, `[]|{}` empty object add nothing more. Indeed we cannot pass an empty collection to signaling the theme we want any option because it would make difficult to address the cases where someone might want to edit the value via a filter giving dynamic data which might be empty or not while at the same time they want to keep the current theme / core configuration.


We can't expect theme developers to add this filter as a long term solution.

I agree with @carolinan on this, it is inconvenient to ask to touch two places to configure the theme but at the same time I think it is nice to give the opportunity to confiugure the theme dynamically.

I've seen some options line blockGap accepting three values, false, true, null triggering different results. Could be the same for the collections, something like false deactivate the feature, []|{} empty object add nothing more. Indeed we cannot pass an empty collection to signaling the theme we want any option because it would make difficult to address the cases where someone might want to edit the value via a filter giving dynamic data which might be empty or not while at the same time they want to keep the current theme / core configuration.

### Update
Sorry, I've not took into account the theme override the core configuration, disabling via the same option wouldn't work because there'll be no way to add more options. (edited)


| Besides, I can maintain my own version for my use case; that's the beauty and purpose of open source, isn't it?

The other beauty is that the openness allows us to have broader awareness so that we can all be more powerful together. I certainly want large Nomad installations to exist and operate well, even though I don't have a large one myself...

If you do experiment with your idea and make a PR or fork, please note it on this issue =)


Sweet, thanks all for the discussion here. Sounds like `--filter-with-context=false` is a good enough middle ground for now. I'd be happy to add the "t for allocation-specific tasks" implementation here if desired in the future, but will close this issue for now as it seems like no one needs it yet. Anyone feel free to reopen or open a new issue referencing this one if you want to.


@annezazu To clarify some more, we want to fix this issue by adding a `defaultFontSizes` option in theme.json which matches how many other presets work. And we _thought_ we had it working in #56661.

Unfortunately, the behavior of having that setting either enabled or disabled is different from the current implementation (merging default options with theme options). This is the "worse bug" that @scruffian mentioned—old themes looked different after the change. To fix that issue, we need to bump the theme.json version so old (theme.json v2) themes can continue to work as they currently do and new (theme.json v3) themes can start using the new defaults.

Increasing a theme.json version isn't a small change. And this is the first time that we're changing a default value, so there's no precedent set for how to do it. We want to get it right because there's two other options that could be updated the same way.

You can see my progress in #58409. The change already seemed big enough that we didn't want to rush it for 6.5.


I'm using OnePlus 6 running crDroid which is based on LineageOS.

I checked the application in App Manager and there are two permissions with data access and the status "revoked", even though in the application settings I have the status "No permissions denied":

Screenshot_20240207-180348_Permission controller
Screenshot_20240207-173557_App Manager

I added permissions manually via adb:

adb shell pm grant org.avmedia.gshockGoogleSync android.permission.READ_EXTERNAL_STORAGE
adb shell pm grant org.avmedia.gshockGoogleSync android.permission.WRITE_EXTERNAL_STORAGE

They appeared in App Manager (granted):

Screenshot_20240207-173557_App Manager

But it didn't help and the application works the same.

Unfortunately, I cannot check it on another smartphone with Android 14.
I understand that since I have an unofficial Android installation, there may be a problem here somewhere, but overall crDroid works very well for me and I haven't had any problems with it.

So we'll probably have to stop looking for the cause until someone else is able to confirm it on stock Android 14.

Regards


Right now, the shadcn has a specific folder to install their components, so u gotta adapt your folder structure to receive shadcn components without any problem, in the shadcn installation u can remake your folder structure just pressing "y" on a step.
But to solve your doubt you should visit URL


OK, np.
I noticed that in your "TIME" screen, the tempearure is formatted incorrecly, simething like "24 st C" as opposed to "24°C. I'm using localization and have not hardcoded this simbol. Maybe you know if this is specific to the Polish language on Android. I could not find anything related to thes issue on the internet.


@neomantra

I had first raised the PR and then opened the issue 🙂
You can find it here: #126


Yes, that's a shortcut. Anyone would understand it, but it's not commonly used and looks a bit strange. Maybe someone uses it in some literary (non-technical) texts. I think it would be better to use °C. I have no idea why Android shows it this way for the Polish language. In Android battery settings and in the weather on the screen, the temperature is given as °C. So it looks like Android itself is not using its interpretation.


Is there any movement on this? This is a fairly serious regression, and is preventing us from moving to SK v2.

I did create a simple GitHub project that demonstrates the problem, if that helps... URL


Glad to hear that you loved Kerala. Seems like you are fond of India. Your profile pic, the handle, etc! 🙏


Thanks for the feedback here @drewid. We'll close this for now and track this via URL


Hi, we also have this exact issue. First observed in our Kubernetes-based test environment, where Kubernetes sends a SIGTERM to the Quarkus app, after which a partial transaction got committed to the Oracle DB.

I can reliably reproduce it using Quarkus dev mode and pressing `CTRL+C` or `q` during a large transaction with 100k+ inserts to multiple tables. Then, some thousands of table entries are visible, but not all.

Using the workaround from @segersb above ( URL almost, but not quite, fixes the issue. The call to rollback happens without throwing an exception, but a SINGLE table entry is still inserted anyway.

One thing I've noted is that "Arjuna" also tries to rollback the transaction, but fails because the connection was already closed:

`[co.ar.at.jta] (database-worker-saving-entities-1) ARJUNA016045: attempted rollback of (io.agroal.narayana.LocalXAResource@5158e0b4) failed with exception code XAException.XAER_RMERR: javax.transaction.xa.XAException: Error trying to transactionRollback local transaction: ORA-17008: Closed connection
`

I'd be very happy if Quarkus could reliably rollback all open transactions BEFORE closing the connections.
We're currently using Quarkus 3.6.8, graceful shutdown timeout not enabled.


After a short checkin with @mluskind and looking at the plan of the couple of new issues we're creating here we decided it would be a better approach to use this as a dedicated ticket for the now streamlined effort that we're aiming for in this research and close the other here linked epic with the outcome of forming the initial platform-as-a-product research group and setting the topic and scope of the research we will conduct within the scope of this epic here now. Soooo, reopening it :)


Hi @ivu-mawi,

Thanks for your input!

Does your project maybe have multiple datasources?
I'm hoping that might explain why the workaround is not fully working on your end.
It was specifically made for our use case with only the default datasource:
`DataSource dataSource = (DataSource) dataSources.getDataSource(" ");`

If not I'm a bit worried we'll also encounter issues in our projects.


Hi, also thanks for reporting this and the workaround.

I'm afraid we also use a single, default datasource.

The single inserted entry doesn't always occur. But I'm guessing it only doesn't occur when I press `CTRL+C` too quickly before hibernate has decided to actually send statements to the driver or something.


I think my workaround now will be to simply `Thread.sleep` in a method that `@Observes ShutdownEvent` and only returns when all currently active transactions have finished. (We have some code that wraps all relevant transactions, so I'll keep a counter there and sleep until it reaches zero.)

This might mean waiting too long, so Kubernetes will SIGKILL our app. But this leaves no chance to properly close the oracle connections, and even Oracle does a rollback then in my tests, same as `CTRL+C` on Windows as you mentioned.

But I don't know how this would interact with any other ShutdownEvent Observers, if we had any. Would this delay the other ones, preventing their graceful shutdown until SIGKILL happens? Not a good solution in that case.


That's a creative workaround!

Normally you should be able to use @Priority annotation to make sure other shutdown listeners go first.
We used that in the past for startup listeners, so I guess it will also work for shutdown.

SIGKILL always worked for me as well because Oracle only commits when connections are closed properly.
I guess a shutdown listener that sleeps forever could also work, effectively forcing kube/oc to kill the pods.

Another approach might be to combine the Quarkus property `quarkus.shutdown.timeout` and the kube property `terminationGracePeriodSeconds`
`quarkus.shutdown.timeout=30S` would make sure Quarkus does not start closing connections after 30S to be sure
`terminationGracePeriodSeconds: 0` would cause kube to kill the pods


I'm going to say that we have solved the original proposal - all the data is being served by our API + `hackathon.json` + OpenGraph meta-tags. We are still far from the Ultimate Mechanism (which, today, probably means getting your event to stand out in GPT results), and there are some great further ideas in this ticket - but I would say that we have ensured that hackathons powered by Dribdat have decent SEO.

See also #379


@segersb Agroal 2.3 adds `onConnectionCreate` / `onConnectionDestroy` methods to `AgroalPoolInterceptor`.

This will support you use case (if Agroal prevents the rollback, you'll need to unwrap the connection and call `rollback` on the raw connection).

This methods run on Agroal housekeeping thread and therefore should not be abused.


@tomasz-c I have updated the app to use DataStore instead of SharedPreferences. I think this will address the problem you are experincing on your Android 14 phone, and also is the recommenerd method to use now. You might want to give it a try, and let me know how it goes

I have placed the APK on my Google Drive, since I have not figured out how to build an APK on GitHub. The code for the APK is in branch "pairing", if you like to build it from source. (If you are familiar with creating APK's on GitHub, feel free to contribute)

This branch also fixes a number of display issues, as well as closing the loophole of getting the incorrect reminders for unpaired watches.

I will do some more testing as well, and if there are not issues, I will merge to main and create another relase.

Cheers,
Ivo


Iae pessoal, tudo certo ?, estava com o mesmo problema
Solução:: desinstalei, apaguei os arquivos adicionais e reinstalei

funcionou de boas


Thank you very much. I'd like to test it, but I can't download this file from Google Drive, is it marked as private?


OK, try again to download. here is the link:
 URL

On Sun, Feb 11, 2024 at 9:37 AM Tomasz C. ***@***.***> wrote:


Thank you for opening this, the way you've laid out the work to be done and linked other issues is quite helpful!


I was hoping that Harmony had a function like that, but I had some trouble finding it until now. Thanks for the help and for letting me loosely copy your mod :) (extremely new to Unity modding).
I fixed the issue in v1.2.2 of the mod.


Fixed the issue on my end:

 URL

Feel free to close this issue, thanks for the help!


It works! Now on Android 14 without using 'FORGET' the second watch is unable to pair, it displays 'ERR'.

When it comes to building Android applications, I have no experience. I thought you could just attach an APK file you built yourself, e.g. the one for Google Play. But I read the article and it looks like it's not that easy:
 URL

Thank you for this change in the program. It will be useful in the future when more users will have newer Androids.


Ok, great! Did you notice if your selected actions were preserved after the
update?

I have created a new version 12.1 on playstote and on f-droid. I know it
takes a while to appear on f-droid.

About the APK creation on GitHub, I had it working at one time, but the
signature was not updated properly, so people had to remove the app before
installing it. I simply have to spend the time to write the correct yml
script for GitHub, and I not overly excited about administration work.

On Sun, Feb 11, 2024, 2:13 PM Tomasz C. ***@***.***> wrote:


Yes, I noticed a problem, I edited the previous comment, you probably already replied and didn't see it. Please take a look at them.


No, should not have to use FORGET to connect the same watch. Is this behavior only on your Android 14 phone? BTW, I don't think it is the Android version, but the os distribution.

The app 12.1 should be coming on the playstote soon, maybe try it and see any difference


Strange, I'll try with more phones. Seems like the new settings are not saved. I think the os you're using is super secure.

Can you try this:
- Select some actions in the action screen.
- go to the time screen
- disconnect and restart the app
- see if the newly selected actions are still selected.
This will tell is if you are able to save your preference


Or maybe it has something to do with encryption. Can you put a phone number
in the action screen, restart the app, and see if the number appears the
same?

Thanks

On Sun, Feb 11, 2024, 2:29 PM Tomasz C. ***@***.***> wrote:


I did some tests:
- there is no entry in the application. phone and settings are remembered after restart,
- I built version 12.1, I don't know if I did it correctly, but I got app-debug.apk, it works and presents itself as 12.1, but this version works the same as the previous one,
- the most important observation - if I pair the watch in the Android system settings, I can reconnect without using 'FORGET', both after disconnecting the watch and restarting the application. So after pairing in the system, everything in the application seems to work correctly (I haven't tested automatic time synchronization yet)

I hope that such pairing in the system was not always required and I did not know about it. But probably not, because previously the app connected to all watches every time without pairing in the system.

I forgot to mention that I have Android without Gapps (I did not install it), so I do not have GSF (Google Services Framework), but this application in the Google Play store does not show that it is dependent on GSF.

Conclusion:
- currently (after pairing in the system) the application seems to work as expected, I will let you know if the watch synchronizes automatically,
- this action is fine for me, it doesn't bother me that I have to pair the watch in the system, unless there are some negative consequences that I don't know about,

Thank you for these changes to the application.
Regards.


OK, will leave it for now. I think it is some permissions related to BT for your device.

In the future, I will try ti install crDroid 14 on one of my phones and see if I can reproduce it.

I will leave this issue open in case somebody else want to chime in.

Thanks for all the feedback


They need to run on macOS 14 though. If you choose a `macos-14` runner, it will automatically run on M1, while `macos-11/12/13` runners are provisioned on Intel. Also many paths are different due to homebrew installing under `/opt/` instead of `/usr/local` on ARM. I guess we'll either have to create a new action or put a lot of conditionals into the existing one.


@kirk-patton closing this for now. Feel free to re-open with more details about the issue and steps to reproduce it. Thanks!


@ashutosh-narkar the details were hidden as they had been provided as part of the comment included in the template. I edited the issue to unhide that.


@kirk-patton I would recommend using the latest version of OPA and try to repro with that. Also it would help if you could share the policy, input etc. There were some issues around OPA returning a "nil" response in an older version which we fixed. Not sure if you're seeing the same issue but using the latest OPA version would help to figure that out.


Hi Andrea, I did a test: within the integration, by selecting system options, I disabled and enabled polling for updates. The two thermostats took the correct values at that time. This means that they can communicate correctly with the Legrand cloud via Cloudflare tunnel. I don't understand why it doesn't do it automatically...


It seems we're keeping this on the WordPress 6.5 Editor Task board intentionally in the No Status column in hopes that it'll be addressed for 6.5. It does seem like a critical issue for many builders. I see it as In Progress on the Automattic team Ignite's project board. @ajlende do you have any updates on this, please?


This isn't going to make it to 6.5 as stated above :( I left it for a bit to see if we could make progress since, as you noted, it's an important issue but it's not going to happen 24 hours before beta 1. Punting now.


Automatic time synchronization does not work. I waited for the watch to want to update, then it was visible that it was connecting and after a short while it displayed ERR. Connecting (bottom left button) and triggering actions (bottom right button) work properly, e.g. sending time to the watch.
I have no more ideas why it doesn't work for me. I will wait until you or someone else has access to Android 14. Not necessarily crDroid, just information that it works properly on any Android 14 is enough, then I will know that it is definitely something on my side.


@justintadlock So you're saying that the font sizes will be broken in the site editor for any theme that uses slugs similar to core?


Yes.

This has been an issue for several major releases and no one has a fix for it yet that doesn't break other things. Given the complexity of the issue, it's unlikely to be fixed in time for 6.5. Of course, if any contributor has time for a PR to fix in the next 24 hours, that could change. I'm sure plenty of folks would be willing to test.


@justintadlock This issue has not existed (at least what I am experiencing URL until recently. The current version 6.4.3 is not experiencing this issue, and if ignored, this will become a major disaster for users of these themes. I am not sure at this point if anyone understands the severity of it, and I will glad Zoom you (or @annezazu) or whomever to show exactly what is happening.


@bgardner - This specific ticket was created for Wordpress 6.2.2 and Gutenberg 16.1.0, so I want to make sure it's clear we're talking about punting something that's been understood to be an ongoing thing.

Not sure if #57889 should be reopened at the moment, especially if it's a new issue introduced since WP 6.4. In that case, it should definitely be addressed for 6.5. Anyway, pinging some folks to see what we can get done. :)


@justintadlock I understand. The original issue that was created ( URL was created at 6.4.2, and that is where I chimed in. It has since been closed, but the problem still exists. I think it needs to be re-opened (again) and made a priority for 6.5.


I don't even have the official app on this phone. But it was running on another phone nearby. I will check synchronization if there is no official application nearby and let you know.
Thank you for your suggestion.


Because this issue touches all of my themes, Ollie by Mike McAlister, even @ndiego's personal theme. Not to mention the (possible) 100's of themes that are using theme sizes/slugs similar to core.


You're right! I set the watch to an hour just before the update, and if there was no other phone with the official application nearby, the synchronization worked :)
Thank you for the idea. I thought that if each watch is paired with its application on separate phones, there will be no conflict.


Circling back to ack that I Zoomed with @annezazu and @ajlende to walk through what I reported in URL More to come.


What has happened is that the watch is sending a signal that it is trying
to connect, and the app running on the phones nearby see this request and
they try to connect to the watch. The first phone that replies to the watch
wins. The watch will only talk to this phone from that point on. In your
case, the phone that was not paired got in first, and that connection
failed. The watch displayed ERR.

On Mon, Feb 12, 2024 at 5:01 PM Tomasz C. ***@***.***> wrote:


Let's not create a new action, let's add branches and what not to deploy-macosx, yes. From what I understand GCC isn't available at all on Apple Silicon, so we can skip all that, and no need to worry about /usr/local paths there.


We have released an updated version that includes the above reflections. Thank you for your patience!


Hi all, thought I would provide a quick update. I have bought and installed some sensors (many thanks @Rossaluss for the recommendation). Now they are installed and everything works reasonably well with the esphome ratgdo firmware and ROW garage door opener.

I did notice one thing: When I close the door (through the close command) on either Home Assistant with cover.close or through the web interface on the device, the light flashes 4 times (roughly 4 seconds) then starts to close. There is no obstruction or issue. It appears that the firmware counts this as it's close time so a door close command is about 4-5seconds longer than it really is. that means if I try to set the door to say, 50%, it doesn't go too far down as it includes the first 4 seconds or so of flashing light. Looking at the logs, it appears to start closing at around 70-65% closed according to the learnt time.

Is that expected behavior? I didn't see anything obvious in the manual. Will do some further investigation.

Thanks all for the support. I am glad I have it working now, shame the obstruction sensors were needed, however I will look to mount them properly to get the use out of them, currently just looking at each other on the roof to get things going.

(side note: If anyone buys the Amazon linked ones above, you need to reverse the wires based on the instructions. instructions are terrible and the wires are not very long, so you will need to buy additional connecting wiring. Mounting kit seems good too. Pretty happy considering the cheap price)


This might be made worse by building all the applets in parallel. Maybe limiting the amount of parallel jobs to one would help? `CARGO_BUILD_JOBS=1`


If you don't wait for the data to arrive from Legrand but you make the query it's different, it's one thing to do get on their servers and another to receive posts on your HA's webhooks


I tried to describe the problem we still see in this thread. Sorry, if it wasn't clear.


Try:

1. Go to Cloudflare’s dashboard on their website, Zero Trust > Access > Tunnels. Select your tunnel. (This is where the Tunnel ID comes from for the Cloudflare Tunnel Token above.)

2. Check that everything is correct. The public hostname and service target ( URL must be right. Verify that remote access to that domain still works.

3. Go to Cloudflare’s dashboard, Zero Trust > Access > Access Groups. Create a new group, named whatever you like. I used “Google Assistant IPs”.

4. Under Group Configuration > Include, selector IP ranges, add the following ranges.

| Geography | Region | IP V4 ranges |
|--------------------|-------------------------------|---------------------|
| Australia | Australia East | 20.37.194.0/24 |
| |Australia South East | 20.42.226.0/24 |
| Brazil | Brazil South | 191.235.226.0/24 |
| Canada | Central Canada | 52.228.82.0/24 |
| Asia Pacific | Southeast Asia (Singapore) | 20.195.68.0/24 |
| India | South India | 20.41.194.0/24 |
| | Central India | 20.204.197.192/26 |
| United States | Central United States | 20.37.158.0/23 |
| | West Central United States | 52.150.138.0/24 |
| | East United States | 20.42.5.0/24 |
| | East 2 United States | 20.41.6.0/23 |
| | North United States | 40.80.187.0/24 |
| | South United States | 40.119.10.0/24 |
| | West United States | 40.82.252.0/24 |
| | West 2 United States | 20.42.134.0/23 |
| | West 3 United States | 20.125.155.0/24 |
| Europe | Western Europe | 40.74.28.0/23 |
| | North Europe | 20.166.41.0/24 |
| United Kingdom | United Kingdom South | 51.104.26.0/24 |

It would be a good idea to also ask Legrand support a question to find out which regions they have the services distributed in, otherwise I'm afraid you'll have to open all those subnets.
Here you will find the link to the AZURE page, I hope it can help you.


Ciao Andrea, I traced with my firewall the domain my smarther(s) contact from inside my lan to Legrand cloud. Could be helpful in your opinion?


@andrea-mattioli what I have to ask exactly to Legrand forum?


Thanks, `@Priority` works!

I agree with the rest.

I'll stick with my "dynamic" delay, because it allows a normal graceful shutdown if no transactions are running, or very short transactions, which I expect is the much more likely scenario for our app. So the SIGKILL from Kubernetes would only be a rare last resort kind of thing, if someone happens to trigger a restart during one of those rare long transactions.

Still, would be much nicer if Quarkus rolls back before close of course :)


Make a test by adding all the subnets, if it works then write to Legrand and ask which ones you need to implement and remove the rest!

Also you can try make a POST (use internet connection):

import requests
import json

def send_post_request(url, payload):
 headers = {'Content-Type': 'application/json'}
 try:
 response = requests.post(url, data=json.dumps(payload), headers=headers)
 if response.status_code == 200:
 print("POST request successful!")
 print("Response:")
 print(response.json())
 else:
 print("POST request failed with status code:", response.status_code)
 print("Response:")
 print(response.text)
 except Exception as e:
 print("An error occurred:", e)

# payload JSON
payload = {
 "key1": "value1",
 "key2": "value2"
}

# URL
url = " URL

# POST
send_post_request(url, payload)

You can find the correct endpoint url via Legrand API or via my old integration URL


Is there any solution looking to come from this at all? By all appearances, the package camerawesome has managed to turn front camera mirroring into a toggle-able feature. Just curious if there's any similar solutions in the works for the main camera plugin. Recording any video (or image) content with text or other similar content is not really doable right now. At least not without doing video processing after the fact


@abelsiqueira @suvayu Maybe this is a good candidate for a wiki? 🙃


Have we decided what use we'll be moving to the wiki? We have 6 places for prose right now:

- README.md
- README.dev.md
- CONTRIBUTING
- Docs = Website
- Issues
- Discussions

So it might be useful to redefine some things to give use to the wiki. Also, it is a good time to bring up URL since it relates to documentation and purpose.


@barreiro
Thanks, that would already be a much better solution than what we have now!

Is that something that Quarkus would implement by default?
It doesn't seem right that transactions are not safe by default when using Oracle.


Ciao Andrea, I've added all the subnets to cloudflare tunnel and now seems to work. Meanwhile I've made a post in Legrand forum asking for the correct subnet. You'll find it in forum.


Here is a good example how fullscreen code blocks are done on dev.to
 URL

 URL


Great it helped!

Interestingly the doc for using `quarkus.shutdown.timeout` says: "Setting this timeout will incur a small performance penalty, as it requires active requests to be tracked." I guess they have a similar code to yours to track the open transactions.

If you still have issues, you could also play with the values of those properties.
`terminationGracePeriodSeconds` can be set to maybe 30 second or so while `quarkus.shutdown.timeout` could be set to a minute.
In a "normal" redeploy Quarkus should be able to shut down within the grace period op kube.


[Triage] As part of this, we should ensure the artifacts are identical as much as possible between the partner and GH releases.


What is the status of this?
I tried to summarize the problem in order to make it more clear.

The Equinox Platform just bundles a bunch of components which can be also individually used and consumed from maven central. The Equinox Platform has a version number but each bundled component has its own version number (and a maven group/artifact id). The latest version of the Equinox Platform is 4.30, see here for a list of contained components are their version.

CVE-2021-41033 states that all Equinox versions
 org.eclipse.platform
 org.eclipse.osgi
 3.18.0

For an outsider it is hard to determine if your used component suffers from a CVE which just states which Equinox Platform version is affected. In this specific case i think that the OSGi Framework was not vulnerable because of CVE-2021-41033.
The problem was in P2, according to this issue.

However i think this a general problem and lets assume that the OSGi Framework was affected.
CVE-2021-41033 was fixed in Equinox Platform >= 4.21, which contains Equinox OSGi Framework in version 3.17, see here.
So using Equinox OSGi Framework in version 3.17 and above should be fine, but OWASP complains because it mixes up the Equinox Platform version with the Equinox OSGi Framework version.

I think this is general problem and might affect other parts of the Equinox Platform as well like (Equinox CM, Equinox Console, etc..) and it would be nice if we could work out a solution for this.


The eclipse maintainer stated that this is indeed a false positive
and that the mentioned artifact (Equinox OSGi Framework) was never affected by CVE-2021-41033, see here.

So please add this as a false positive, thanks in advance.


Hi, thanks for your detailed report. I personally do not use conan but I have a little project where I smoketest asio-grpc with conan. Using default setting with MSVC it builds static libraries for me, for you it seems like you have selected shared libraries (at least for protobuf) and now tries to link with both `libprotobuf-lite` and regular `libprotobuf`. I tried to reproduce that without luck.

Here is the `conanfile.txt` that I used for the reproduction:

[requires]
asio-grpc/2.9.2

[generators]
CMakeDeps
CMakeToolchain

[layout]
cmake_layout

[options]
protobuf/*:shared=True

After running the conan install command, I do

cmake --build --preset conan-release


This is because `control` by default, for historical reasons, performs an eager synthesis of the control operation, so the scaling is fairly naturally super-linear (for arbitrary controlled gates). The solution for the simple representation of the objects is to use the modern form that @alexanderivrii has been getting in place, where controls, inverses and gate powers are represented as modifier tags on the gate, and only realised at synthesis time. In your example, setting `annotated=True` in the `control` call will make this script work in linear time of `N`.

That said, when it actually comes to synthesising the gates through `transpile`, you're still almost certainly going to see the super-linear blow up. Our arbitrary-control syntheses probably aren't the best they can be yet, but I think the general case is still going to scale quite a lot with the number of controls.


Just as an immediate copy-pastable example of the above:

python
from qiskit import QuantumCircuit

N = 100
sub_qc = QuantumCircuit(1)
sub_qc.x(0)

out = QuantumCircuit(N)
out.compose(sub_qc,range(sub_qc.num_qubits), inplace=True)

for kk in range(N-1):
 sub_qc = sub_qc.control(annotated=True)
 out.compose(sub_qc,range(sub_qc.num_qubits), inplace=True)


Fwiw, slightly better form for this would be to do:

python
from qiskit import QuantumCircuit

N = 100
sub_qc = QuantumCircuit(1)
sub_qc.x(0)
sub = sub_qc.to_gate()

out = QuantumCircuit(N)
out.append(sub, range(sub.num_qubits))

for kk in range(N-1):
 sub = sub.control(annotated=True)
 out.append(sub, range(sub.num_qubits))

`compose` is a circuit-inlining method, where a circuit represents a program. A single object in a circuit is a `Gate` (if unitary) or `Instruction` (if not), and that's the base blocking structure of the object and how it's pulled through the transpiler. Using the native block structure like that (rather than inlining things with `compose`) will be / should be better for performance longer term, especially as our things like synthesis of these gate annotations improves, because the tranpsiler will be able to retain the abstract/logical structure of the circuit for more longer, and do operations on large-scale abstract components, rather than a flattened structure caused by over-use of `compose`. `compose` is of course better when you _want_ the structures to be merged / inlined, but I don't think this particular example is one of those.


Ok thanks. I am trying to benchmark various aspects of Qiskit, and this one broke things, where as other frameworks can handle the controlled circuit.

Is there anyway for an user to find out what `annotated=True` does in the control? I cannot seem to find it. Also, if it prevents blow-up, why is it not on by default?


It's not on by default because that would have been a major breaking API change, and we're not confident that it's as well supported through the entire stack as the current form yet. It will become the default once it and its synthesis have matured a little more - I'd imagine changing the default of `control` will be one of the API breaks of Qiskit 2.0.

For example, at the moment, the multiple `control` form of annotated gate isn't merging the controlled modifiers into one, nor do the transpiler passes that synthesise the annotated forms of the gates, so we'll still effectively be doing the same looped calls you were underneath. That's not super hard to fix of course, just an indication of the newness of the feature in Qiskit.

What are you meaning by "any way for a user to find out what it does?"? It's a modifier, so it doesn't really _do_ anything (in the sense of the eager synthesis of `ControlledGate`) does on the spot. How it gets synthesised to actual hardware depends (in theory, not yet in practice) on the basis gates and coupling constraints of the hardware, which isn't defined at the point of creating an abstract circuit, but would happen during compilation.


Yeah, no I answered my own question when I tried to change the basis on the circuit and it just kept running.

It also modifies the circuit drawing, which is not too important, but unexpected.


Ah, for methods different than `GET` the header to access a different schema is `Content-Profile` instead of `Accept-Profile`. Does this work for you:

bash
curl --location ' URL
--header 'Content-Profile: pmg'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer (token containing the db_admin role)
--data '[
{
"name": "weird-wallaby-93"
}
]'


I should add that I went through all the reproduction steps above, but instead of using the `pmg` schema I used a different schema (one that I've been using for a little longer) and this problem did NOT manifest. So it seems to be something connected to the `pmg` schema. Could be a permissions issue, but I've checked everything I can think of permissions-wise. And I still believe if it's a permissions issue it should manifest as a 403 with an error body.


@laurenceisla YES! That fixed it. But the weird thing is the other POST requests I have in Postman against tables in a different schema ('industrial'), worked with the Accept-Profile header, which is quite strange. Thank you so much!


Thank you so much @Tradias for your quick response!
Further, I moved to CMake instead, and still face a last bit of problems as stated below in getting my feet wet on this package:

I followed the below instructions of the README.md, and it was **successful** in installing the library.
Though I do not understand the significance of "lib" folder inside the install directory is filled with many cmake files. Maybe that got anything to with my problem, not sure...

image

In stage 2, where I wanted to integrate the library to my target. Here is the snippet of **CMakeLists.txt** that builds my target linking asio-grpc:

set (CMAKE_PREFIX_PATH C:/Users/Downloads/asio-grpc/install)
find_package(asio-grpc)

## ...

add_executable(WT hello-world-server.cpp ${HEADERS} ${SOURCES} )

##...

# Specify include directories if your project has header files in multiple directories.
target_include_directories(WT
 PRIVATE
 #asio-grpc
 ${CMAKE_PREFIX_PATH}/include
 ${CMAKE_SOURCE_DIR}/helper

 #...
)

target_link_libraries(WT
 PUBLIC

 asio-grpc::asio-grpc
 Boost::headers

 #..
)

After configuring my CMakeLists.txt, when I **build** it, I get the below error:

C:\thavi\CPP_WS\asio-grpc-experiment\helper\awaitable_server_rpc.hpp(24,41): error C2039: 'use_awaitable_t': is not a member of 'boost::asio' [C:\TH
ARMA\CPP_WS\asio-grpc-experiment\build64\WT.vcxproj]
C:/thavi/vcpkg/installed/x64-windows/include\boost/asio/ssl/stream.hpp(39,11): message : see declaration of 'boost::asio' [C:\thavi\CPP_WS\mt5\manager\mt5_ib_to
olstandalone\build64\WT.vcxproj]
C:\thavi\CPP_WS\asio-grpc-experiment\helper\awaitable_server_rpc.hpp(24): error C2061: syntax error: identifier 'use_awaitable_t' [C:\thavi\CPP_WS\
asio-grpc-experiment\build64\WT.vcxproj]
C:\thavi\CPP_WS\asio-grpc-experiment\helper\awaitable_server_rpc.hpp(24,60): error C2039: 'as_default_on_t': is not a member of '`global namespace''
 [C:\thavi\CPP_WS\asio-grpc-experiment\build64\WT.vcxproj]
C:\thavi\CPP_WS\asio-grpc-experiment\hello-world-server.cpp(16,1): fatal error C1083: Cannot open include file: 'helloworld/helloworld.grpc.pb.h':
No such file or directory [C:\thavi\CPP_WS\asio-grpc-experiment\build64\WT.vcxproj]

Primarily the issue is about missing "use_awaitable_t"... not clear if my verion of Boost::asio (1.75) is missing it perhaps?
Maybe you can take a look at my environment (snapshot below):

image

**Other general question**:
Since it is a header-only library, why do we need to link "asio-grpc::asio-grpc". Sorry for the basic question.

Thanks for your help in advance!

Thanks,
Tharma


In the long run I highly recommend using a package manager. At work and personally I use vcpkg.

I assume in your CMake you forgot to add:

cmake
target_compile_features(WT PRIVATE cxx_std_20)

Specifying a target in `target_link_libraries` is CMake's magic way of propagating any kind of build requirements to your target. This includes: libraries to link, directories to include, pre-processor definitions, compile features/flags, .... In the case of asio-grpc that would be linking with `gRPC::grpc++`, enabling compile feature `cxx_std_17` and adding pre-processor definition `AGRPC_BOOST_ASIO`. In general it is a good idea to specify all direct dependencies in a `target_link_libraries` call, regardless of whether they are header-only or compiled.

Also at some point you will have to generate source code from `.proto` files. You can do so using asio-grpc's helper function:

cmake
asio_grpc_protobuf_generate(
 GENERATE_GRPC
 TARGET WT
 IMPORT_DIRS "${CMAKE_CURRENT_SOURCE_DIR}"
 PROTOS "${CMAKE_CURRENT_SOURCE_DIR}/proto/helloworld/helloworld.proto")


Thank you so much! I had a valuable learning experience with this cmake function, target_compile_features. Additionally, I proceeded with "vcpkg" as you suggested, and I must say, I found it to be incredibly user-friendly.

Regarding the linking errors, you were absolutely correct! When I replaced cxx_std_17 with cxx_std_20 in the code below, the issues were resolved:

target_compile_features(WT PRIVATE cxx_std_20)

With that, I could "configure" (`cmake . -B ./build`) without any error.
But when I "build" (` cmake --build ./build --config Release` or `cmake --build ./build --config Debug` ),
**I face just these two errors** (details below):

C:/Users/thavi/Downloads/asio-grpc/install/include\agrpc/detail/register_awaitable_rpc_handler.hpp(58,15): error C2672: 'co_spawn':
no matching overloaded function found

C:\thavi\build\generated\helloworld\helloworld.pb.cc(43,80): error C2127: 'helloworld::_HelloReply
_default_instance_': illegal initialization of 'constinit' entity with a non-constant expression

I was wondering if you could provide guidance on this as well? Thanks for your help, in advance.

Thanks,
Tharma


Here is a complete minimal gRPC helloworld example: URL

The `register_awaitable_rpc_handler.hpp` error seems to be a Boost 1.75 specific thing where asio forgot to add type traits for `executor_with_default` of `asio::use_awaitable_t` and misdetects MSVC's `decltype` capabilities. Nothing I can do on my side but if you use the example above that won't be an issue (because it will use Boost 1.83).

The protobuf error is this one URL and was fixed in a later protobuf release. Again, none issue if you use my example.


I can't imagine a person in this world who likes to take a selfie without mirror mode on the camera. However, this package does not allow you to do that, even though this feature was requested in 2019. I understand that Flutter is a huge project and requires prioritizing. But, my question is: Should it be a priority to run Flutter even on a washing machine, when you still can't take a proper selfie on an iPhone? 🤷🏼♂


Continuing with Jake's example, here are a few thoughts on the following synthesis step:

An expression of the form `sub.control(annotated=True) ... .control(annotated=True)` would actually combine all of the control modifiers into a single list, that is create an "annotated operation" whose "base operation" is `sub` and whose modifiers are the list `[ControlModifier(1), ..., ControlModifier(1)]`.

For `N=10`, synthesizing this directly is very slow, but we do have a new transpiler pass `OptimizeAnnotated` in Qiskit 1.0 that canonicalizes the modifiers, that is replaces the list of modifiers by a single control modifier with multiple controls. We are still investigating how to best integrate it into the transpiler flow, so it's now on by default, but one would use this along the following lines:

from qiskit.transpiler.passes import OptimizeAnnotated
basis_gates = ['cx', 'id', 'u']
out = OptimizeAnnotated(basis_gates=basis_gates)(out)

The pass is recursive, descending into the definitions of custom gates, and it needs basis gates and equivalence library to know which definitions to examine and which to skip.

For `N=10`, the optimized circuit `out` is now susceptible to transpilation (i.e. to either `transpile` or to `HighLevelSynthesis`). However the approach still does not scale to much larger values of `N`. If I recall correctly (not too sure about this), our default algorithm for synthesizing multiply-controlled gates without ancilla qubits produces exponentially many gates.

One could do a bit better by replacing the code

sub_qc = QuantumCircuit(1)
sub_qc.x(0)
sub = sub_qc.to_gate()

by

sub = XGate()

in which case the synthesis algorithm would treat the annotated `sub` essentially as a `MCX`-gate, producing half as many gates and somewhat decreasing runtime, but unfortunately the default synthesis algorithm ("McxGrey") for MCX-gates without ancillas still produces exponentially many gates.


OK, let us establish a baseline for the problem. Let me ask you a few things first:

What is the version of the app? You can find the version by pressing the (i) in the top-right of the initial screen.
Is this a new behavior? Was it working before, or is this something you have experienced before?
Please make sure the official app is not running on your phone or on phones in the proximity of the watch.
Please make sure this app is not running on a phone in the proximity of the watch.
Does the app work on another phone you might have?
Do you have multiple watches?
I will look into the issue once I understand the situation better. Thanks for reporting this.


A simple thing to try is to go the Android setting, and clear "Storage and Cahe" and see if this fixes the promle. In v12.1, we cahnged the way we store local data, this might be effecting it.


Doing 1 did prevent an OOM but the compile took over 40min to complete, I did try 4 jobs however that still hit an OOM


If all else fails, somebody reported that they had to pair the watch manually once from the Android settings, and then it started working. We have tested the app with Android 14, so I assumed that this is something specific to their crDroid OS. It seems that some versions of Android 14 have extra security features that don't allow automatic pairing, or there is a bug in the OS. We are still investigating.

If you try to pair manually, go to Settings, select Bluetooth -> Pair new device, then long-press the lower-left button of the watch, and it will appear in the list of devices. Just pair it then

here is the link

Please let me know how it goes.


Just keeping some notes about this issue for future reference.

Location of DataStore data file:
/data/data/org.avmedia.gshockGoogleSync/files/datastore/CASIO_GOOGLE_SYNC_STORAGE.preferences_pb

Simmilar issue found here:
 URL


Just keeping some notes here for future reference:

Location of DataStore data file:
/data/data/org.avmedia.gshockGoogleSync/files/datastore/CASIO_GOOGLE_SYNC_STORAGE.preferences_pb

Simmilar issue found here:
 URL


Are you sure you are using the latest github version on master, I made a fix last Friday for token refresh, just updated my test HA from 2024.2.0 to 2024.2.2 and that didn't gave a probem, see URL for the fix. Do you have that?


ah I have a21d8cc, will pull the latest master, thanks

image


**[SOLUTION:]**

did that app works as expected now
(cleared cache b4 for good measure)

-----

1. new user
2. no official app installed, no other phones in vicinity
3. "
4. n/a
5. no

-----

same behavior as pressing 'forget' in app

-----

stock pixel rom, however custom linux-stable based kernel
(5.10.197-Kirisakura_Raviantah_2.1.0), magisk 26.4, lsposed 1.9.2; if that matters


Great, thanks for the feedback! I'll add this solution to a troubleshooting section.
I'll continue to investigate why this is the case.i can only assume this is a new security feature to prevent apps from maliciously connecting via Bluetooth without the user's knowledge. It does not effect all Android 14 phones, so I'm not sure what is the difference.

I would be really curious how the official app behaves with your phone, but if you have not installed it before, I understand you might be reluctant to compromise your privacy.

Thanks again for reporting this.


Just tried both the 'classic' g shock connected and newer casio watches app and both work as expected. Once paired in app the watch and app reconnect without hiccup. Deleted the watch pairing from my phones bluetooth settings beforehand.
So I'm guessing it's bug specific to your app.


Ok, I'll look into it. Thanks.

On Sun, Feb 18, 2024, 12:14 PM Lexvox ***@***.***> wrote:


Sounds like you have some good technical skills. Could you help me narrow down the problem?
I suspect it has something to do with the app storage. After connection, the Bluetooth (BT) ID of the watch is stored in the DataStore of the app. Next time, the app will reuse the same ID to connect to the watch until you clear the storage or press "FORGET".

Could you try the following:

1. Unpair the watch and clear storage from Android settings.
2. Set up ADB on your PC. Put your phone in "developer" mode and connect it to the PC via USB.
3. Run the following to see the content of the app's data:

adb shell
run-as org.avmedia.gshockGoogleSync
cat /data/data/org.avmedia.gshockGoogleSync/files/datastore/CASIO_GOOGLE_SYNC_STORAGE.preferences_pb

You should see "File not found".
4. Connect the watch to the phone for the first time. Run the above commands again. This time you should see something like:

LastDeviceName*CASIO GA-B2100
LastDeviceAddress*F6:A1:42:57:7A:07

LastDeviceAddress is what holds the ID of the watch. Let me know if you see it.

Thanks


Update: I tried compiling cosmic-applets on my desktop (i7-13700k, 32GiB of ram) and maxed out the ram on the same step. The CPU seems to not max out, but the ram certainly does.


1. cleared app, deleted pairing from phones bt setting
2. looked up the file (nonexistent)
3. after connecting (in app) it holds my watches id just like in ur xample,
4. disconnected watch
5. wont reconnect as before,
6. without clearing the app or forgetting the watch in app I connected the watch through my phones bt settings and when I switched back to the app the interface was already up displaying the info as expected

also cleared and reconnected twice just to see if the phone changed the id for some reason (it didn't)


@siddharthadevops Hi, it's not about taking a photo not in selfie mode, it's about taking a video, as camera plugin serve both of this...
Taking a video in mirror mode is not the problem, but saving it in mirror mode it is, if you have something in background like a car, a brand name, it's all reversed... what would be great is to choose it, like in iOS / Swift


that's not a good idea. Translations will get dangerously out-of-sync.


True, it makes sense.

But, take Arch Wiki as example, it has multilingual support, and on the top of the translated page there is a notice about the last time this page is updated, and also a link to the original language.

If we could implement such warning/notification, will you feel it better?


Possibly the same problem as URL ?

Compiling all applets in parallel takes quite the toll on ram usage, building them one-by-one should be much easier.


Diataxis was a great read!
I agree we're spreading out a bit, but this is something that doesn't seem to really belong in an issue... Maybe it can go into the docs? Right now it's pretty dev-related, but eventually might be useful to the user.