Issue with Disabling Camera

Title: Issue with Disabling Camera
Description:
I am experiencing an issue where the camera fails to disable when the Button_Released event is triggered in my application. The camera is initially set to be disabled, and it successfully enables on a button press but does not disable again on button release. The event is being triggered successfully but the camera remains active.
Environment:
I just tried on Android 13
Here is a simplified version of the relevant code:
XAML:
<Button Text="Camera" VerticalOptions="Center" HorizontalOptions="Center" Pressed="Button_Pressed" Released="Button_Released"/>
<scanner:CameraView x:Name="Camera" CameraEnabled="False" CaptureQuality="Highest" HeightRequest="185"></scanner:CameraView>

C# Code-Behind:
private void Button_Pressed(object sender, EventArgs e)
{
    Camera.CameraEnabled = true;
}

private void Button_Released(object sender, EventArgs e)
{
    Camera.CameraEnabled = false;
}

Expected Behavior:
The camera should be disabled when the button is released.
Actual Behavior:
The camera remains enabled even after the button is released.
Steps to Reproduce:
Start the application.
Press the Camera button to enable the camera.
Release the Camera button.
The camera should disable on step 3, but it remains active.
Please let me know if you need any further details or if there is any additional information I can provide to help resolve this issue.

This issue also happened with MVVM,

Actually, the problem occurs in scenarios where there is an attempt to change the CameraEnabled property from True to False. In my debugging, I noticed that the HandleCameraEnabled method in CameraManager is not being triggered after this change when using MVVM. When not using MVVM, it is triggered but has no effect.
To work around this, I used a DataTrigger in XAML that reinitializes the CameraView when CameraInitialized is True. This ensures that the camera is completely reset and not merely disabled, which helps to address the issue where the camera remains active despite the CameraEnabled property being set to False. This method might be particularly necessary on specific platforms like Android, where this behavior has been noted. Here's the modified XAML code for the workaround:
<ContentView>
    <ContentView.Triggers>
        <DataTrigger TargetType="ContentView" Binding="{Binding CameraInitialized}" Value="True">
            <Setter Property="Content">
                <Setter.Value>
                    <scanner:CameraView x:Name="Camera" CameraEnabled="{Binding IsCameraEnabled}" CaptureQuality="Highest" VerticalOptions="FillAndExpand" HorizontalOptions="FillAndExpand"/>
                </Setter.Value>
            </Setter>
        </DataTrigger>
    </ContentView.Triggers>
</ContentView>

This solution ensures that the CameraView component is correctly updated, effectively managing the camera's enabled state as intended.

FWIW, I have two ways how scanning can be performed - either manual or automatic. While the manual mode is active, users must keep the Scan-button pressed.
I implemented this using the PauseScanning property.
The CameraEnabled property is only used within the page's OnAppearing and OnDisappearing events (otherwise all MVVM).
No problems here. I do think that this is the way it's supposed to work.

Thank for answering, Olaf-R. I understand the purpose of PauseScanning property. However, my concern is specifically with controlling the camera's power state directly to manage battery consumption. We considered enabling and disabling the camera—not just pausing scanning—to save battery when the camera is not in use. Furthermore, we are using Views, so when the View changes the camera still active, what is a big problem for us.
Is there no built-in capability to toggle the CameraEnabled property on and off dynamically outside of the page lifecycle events? It seems somewhat limiting to have the CameraEnabled property only effective during the lifecycle of the component.
Thanks again for your input.

Hello all and thank you for your feedback.
I managed to test one scenario this morning (ContentPage, code behind, basic Button_Pressed and Button_released events, Oneplus 7 PRO, Android 12) and both setting Enabled to true and false started and stopped the camera successfully.
One thing to remember is that CameraView will retain the last frame when camera is disabled, but it will be frozen.
So far I haven't tried MVVM and ContentVIew.
Can you create a some basic MAUI project that expresses this bug and upload it here so I can download it and try to replicate it.

You are right. Sorry for the inconvinience. The problem is actually only appearing when using MVVM.
Hope this sample code helps to reproduce the problem.
BarcodeScanningTest.zip

Should be fixed in 1.5.1


.yaml file missing

While running the script for Diffusion Model, it gives error saying "No such file or directory: '/home/........./PVDM/configs/latent-diffusion/ucf101-ldm-kl-3_res128.yaml'. This error pops up when I give this argument "--first_model 'results/first_stage_main_gan_UCF101_42/model_last.pth' " from the diffusion model script. Does it means the "ucf101-ldm-kl-3_res128.yaml " is missing from the configs/latent-diffusion file ? Help in this matter will be really appreciated.

Please see this issue: https://github.com/sihyun-yu/PVDM/issues/21#issue-1673492540


Auto Pause: Total disaster.

Today I had a total crash with a novice while I was teaching him how to fly the PX4!
Why?? Just because he could not understand nor he could learn that in order to PAUSE his flight he has to
FIRST: switch to MISSION
and then
SECOND: to switch Auto Pause
it is just overwhelming for the pilot to think of this combination, especially in dare situation when you most likely need Auto Pause. It is against all the rules in a real airplane cockpit as well.
It is crazzzzyyyy!
It is like having your phone ringing in a meeting and then in order to MUTE it you have to first hit home button and then hold volume down for 2 seconds.
Or it is like if you are in the car listening to music CD and have your phone ringing first hit on the Radio Button and then hit CD pause in order to Pause your CD.
Now I have to make an input mixer setting in the Horus in order to do it with just one button, given all the processing power I have in the Pixhawk. Is it hard to make it function like RTL?
This becomes the N1 reason for crashes of novice for the last 6 months I experience. Nobody wants to fly PX4 at the club already. And it is hard for me to persuade them to start using it again with such public crashes and disaster in front of all people and humiliation for me!
It is non sense, period.
 If this is the case excuse me for the rant.

That interpretation is wrong. Putting it into HOLD should be all it takes to make it either loiter at the default loiter radius or hover in spot when in multi rotor mode.
I suggest you try in the simulator first.

Exactly what I had in mind @Lorenz and exactly my point. Because I'm talking about Airplanes now (I had to clarify) Auto Pause should do Loiter in our situation, in order for my student to have a brake from his plane uncontrollable dive (not because plane falure) and has his hands stop shaking from the overwhelming situation. So Auto Pause means Pause the flight (and FC take control of it) until I have time to explain to him the situation, why it happened, and most importantly to have my student pass the Adrenalin rush.
That is how I understand Auto Pause (ex. Loiter).
Experienced users dont use Auto Pause except if we are in mission and we have to Loiter for some time to change the mission or do some other stuff.

@tubeme This comes from the fact that the modes are set-up in a hierarchical way and pause is nested in mission. I agree that it might be confusing if you don't know this fact, and if it's not already captured in your RC switch setup.

Hi @julianoes @LorenzMeier
As far as I understand this is the current hierarchy of the flight modes taken from the source:
uint8 NAVIGATION_STATE_MANUAL = 0		# Manual mode
uint8 NAVIGATION_STATE_ALTCTL = 1		# Altitude control mode
uint8 NAVIGATION_STATE_POSCTL = 2		# Position control mode
uint8 NAVIGATION_STATE_AUTO_MISSION = 3		# Auto mission mode
uint8 NAVIGATION_STATE_AUTO_LOITER = 4		# Auto loiter mode
uint8 NAVIGATION_STATE_AUTO_RTL = 5		# Auto return to launch mode
uint8 NAVIGATION_STATE_AUTO_RCRECOVER = 6	# RC recover mode
uint8 NAVIGATION_STATE_AUTO_RTGS = 7		# Auto return to groundstation on data link loss
uint8 NAVIGATION_STATE_AUTO_LANDENGFAIL = 8 	# Auto land on engine failure
uint8 NAVIGATION_STATE_AUTO_LANDGPSFAIL = 9	# Auto land on gps failure (e.g. open loop loiter down)
uint8 NAVIGATION_STATE_ACRO = 10		# Acro mode
uint8 NAVIGATION_STATE_UNUSED = 11		# Free slot
uint8 NAVIGATION_STATE_DESCEND = 12		# Descend mode (no position control)
uint8 NAVIGATION_STATE_TERMINATION = 13		# Termination mode
uint8 NAVIGATION_STATE_OFFBOARD = 14
uint8 NAVIGATION_STATE_STAB = 15		# Stabilized mode
uint8 NAVIGATION_STATE_RATTITUDE = 16		# Rattitude (aka "flip") mode
uint8 NAVIGATION_STATE_AUTO_TAKEOFF = 17	# Takeoff
uint8 NAVIGATION_STATE_AUTO_LAND = 18		# Land
uint8 NAVIGATION_STATE_AUTO_FOLLOW_TARGET = 19	# Auto Follow
uint8 NAVIGATION_STATE_MAX = 20
This in its term means to me that from hierarchy stand point the RTL is lower in the hierarchy than the Mission and again is part of the autonomous modes as Loiter is, in other words RTL is also a sub mode of Mission if use Mission to denote autonomous modes, and can be activated from ALL modes (Manual, Acro etc) even without a GPS lock, which is very very good in design perspective. Without a GPS lock the RTL could do open loiter or land as far as I understand.
2-3 years ago RTL did not function this way and could not be activated from the Manual modes and without a GPS lock and I'm glad that after zillion of discussions on this topic things changed for good and PX4 became more reliable and robust as a flight controller. As I always like to think, the devil is in the details. And sometimes small details can make a difference between successful product or unsuccessful one.
There is something I noticed in the Flight Mode setup page in QGC. With the RTL switch enabled I see the Return monitor slider go to enable state the Return go yellow (ie activates) and I get the message "Reject Auto Return to Land" because I'm using bench test mock up I have for work and the mock up is in landed state. A minor detail here is that it is not correct English sentence! "Reject RTL" means that I have to reject the RTL but in reality it is that the RTL is rejected by the FC although I want to enable it. So the correct sentence should read "RTL rejected" and a good detail should be to have a second sentence to clarify why it is rejected. So it might read "RTL rejected, no GPS lock" or "RTL rejected, Aircraft is landed" etc.
When I flip the Pause/Hold switch I notice there are two sliders go to enable state: 1. Hold monitor slider and 2. Mission monitor slider at the same time. Which is logical if we want to anble the Loiter with just one (Hold) switch (this is exactly what I do in my Horus input mixer to make it work). Despite the Mission monitor slider and Hold monitor slider go to on state with the flip of Pause(Hold) switch neither Mission lights up in yellow nor Hold lights up in yellow nor i get any message from QGC that something is rejected.
Compared to this Hold switch behavior when I'm on the bench and I activate Mission with the main switch I see the Mission monitor slider go to on state, the Mission lights up in yellow and I get "Reject Auto Mission" message in QGC, of course consistent behaviour because I have no mission in the controller and I'm on the ground (If don't have mission in the PX4 and I'm in the air, the PX4 goes in Loiter state). Again minor detail is that "Reject Auto Mission" is not correct sentence. It should read Auto Mission Rejected" (by the FC) and again clarification why it is rejected could be added as a second sentence.
This to me is a totally inconsistent behavior for the Pause/Hold switch however i look at it.
And finally it is not a good idea to have a 2 different labels for the same thing because it might be hard to explain and setup by the user.
In the setup we refer to Loiter as Hold and we setup a Hold switch, but during flight we put a status and we receive a message as "Auto Pause Activated" in QGC. Either we use Hold or we use Auto Pause or just Pause to denote the Loiter in the setup and in the message the QGC gives. Probably HOLD is the better term.

@julianoes Thanks for correcting the spelling mistake!

I want to make my last pointer here.
I liked the Pixhawk and PX4 fundamental idea with the ROS almost since the beggining because it could easily scale up in terms of HW and SW development. Also I percieve it as a PROFESSIONAL controller given the extensive features.
I can point you to at least 3 cases of real airplane crashes with huge loss of life and damages on the ground due to bad signaling and confusing messaging in the cockpit.
And also there is famous emblematic A380 emergency situation with 50+ major system failures due to engine blow up. The messaging in the cockpit was so consistent, the procedures were so consistent with the messaging that the flight finished on the runway, the pilots managed to land it in this dare situation without a single life lost and without single people injury.
2 years ago we started scaling up, and we had flown a 2.5m - 3.4m IC engine airplanes at 10-20 kilos weight, with 1-3 kilos payload and about 5-10 kilos of gasoline.
Now we are moving towards 3.6m - 4.6m wingspan airplanes IC engine, 20-45 kilos weight and about 10-30 kilos gasoline with huge lipo batteries. So my point is that PX4 is not a toy/hobby controller anymore and with this scale we can really do damage and even kill people on the ground if we don't pay attention to the details!
I noticed today that @LorenzMeier added a PR https://github.com/PX4/Firmware/pull/6731 which a very very good thing and we have to be aware what could happen if we are not cautious.

It sounds like the confusion here is the "old/advanced" flight mode switch configuration which is a hierarchy. That nav state numbering isn't a hierarchy and has more to do with when things were added.
Have you tried the new "simple" flight mode config in QGC? Single channel for mode selection, separate dedicated switch for RTL, kill, etc.

@tubeme I agree with your concerns. And thanks for pointing out multiple places where the feedback to the ground station is confusing or wrong. We should fix that.
For the mode switching, we probably need to go over these RC configurations again and check for cases like this. And maybe it's time to deprecate some "old/advanced" flight mode switch configuration if that's the issue. What do you think @dagar.

Hey @dagar and @julianoes I don't like the new single switch setup because it is even more overwhelming for the novice than the multiple switch. Also I don't have the flexibility to setup the thing i want it my way with the single switch. Both ways are good on their own. I use the PX4 since version 0.5 which was about the summer 2014. I spent almost everyday with the controller and I still sometimes find myself in a maze. Imagine what is happening with a new user.
My interest and your interest in this open source project is to make as many people as we can use it. And there are certain qualities that PX4 should have in order to catch the fish. The simple example is the iPhone. I use smart phones since HTC P3300 windows phone which was avail way before Apple stepped in. The revolution for smart phones started with the iPhone because it was the easiest to use and with the best user experience created at that time. Despite Google stepped in with a lot of muscle they still are following in terms of sales. And now the iPhone is lacking a lot of features that Android has, and they are kind of dumb phones for me, but they still are holding their position as #1 smart phone in net worth.
Since the beginning of 2015 I want a single feature that will tremendously simplify the emergency response of the PX4. And that is setup a single emergency 3 pos switch. low position -regular flight, mid position - Hold or Auto Pause, high position - RTL. I cannot do this even today and finally I had a real crash with a real novice person in front of huge audience.I saw a lot of eye rolling and smiles. Of course If I had it in my hands I would most likely have the reflex to turn on the Loiter in time. But usually I leave my Loiter switch on during take off, and then in an emergency I flip the main mode switch to mission and voala I have Loiter with a single switch. This is a work around and not a good practice. I have this practice with time and got accustomed to it. I tell you something interesting. The guy that fly the most PX4 in our tests (he flies almost every day!) did not use loiter in many months. He has a 2-3 thousand hours on PX4 but three weeks ago he called me with a shocking question. "Hey Man, how do I go in Loiter? I could not turn it on at the field and I needed it to test some batteries."
Now I understand that nesting is different than indexing the modes in my example. But @julianoes has a great Idea that there should be some revision to what is going on in the nesting.
It is a simple idea, make the RTL and Hold in one emergency separate group on their own. Make both work from all modes + use the Hold with a higher priority than Mission in order to be able to Hold / Auto Pause the mission execution as well. This will nail it totally.
In this emergency mode group in the future we can include a certain other emergency modes regarding the collision avoidance like in the #6731. Like if we approach / sense  a commercial plane dive down to safe alt and activate loiter or rtl. This group should have the highest priority above all modes.

Sorry I don't want to sound like a wining dude but I want to make my final pointer and will never get in this topic.
The hardest thing to sell is the free thing!!!
I spent most of my career in TV and Advertising Production so in the TV business you sell FREE content.
From the user / viewer stand point the decision making on what to buy is a matter of 2-3 second. Then they hit the next channel on the remote and you loose in the TV business money, here in the FC we loose dedicated time.
We have to fight other open source free flight control software with the PX4. And even in our case it is a matter of 20 minutes until they install Mission Planner and flash APM. APM to me is a competition! despite we are kind in one group. Also there are at least 2 other very nice and decent open source fc software.
We are so advanced in many many areas, but at the same time so un-punctual on some details.

@tubeme your idea is to have a dedicated switch that's OFF - RTL - LOITER for use in emergencies right?
In an emergency why would you need RTL and Loiter/Hold on the same switch. Wouldn't either do?
How is the simple switch config more overwhelming? You have a single channel for selecting modes. Then you have a set of switches that override. What's missing?
If you want more slots in your mode config you can mix switches together. I simply use the GCS to select modes and try to keep the transmitter simple. Most users only use a small set of modes.
Let's try to break this down into something specific, concise, and actionable. As far as the firmware is concerned, my interest is improving the new config, as I don't like the old style, either in configuration, usage, or how it's implemented in software.

... finally I had a real crash with a real novice person in front of huge audience.
Sorry to hear that, and I do understand your pain.

And that is setup a single emergency 3 pos switch. low position -regular flight, mid position - Hold or Auto Pause, high position - RTL

This should be doable with the "new single switch setup" I believe. The setup should be in a way that whatever you envision / or think is really simple and powerful, should be possible.

@tubeme We're changing the nested switch setup, however, adding to Julian's point: A setup with more than 3 modes is already way too confusing.
The way that normal products are built is to have 3 modes on hardware switches, an RTL switch and the rest of the modes on the screen / tablet.
Typical setup would be:

POSCTL
MISSION
RTL

or with two switches:

POSCTL
MISSION
HOLD

And RTL on/off
In theory you don't even need the mission switch. Just set it to mission using the tablet after uploading it and use the main mode switch to re-take manual control when needed.
We have stopped using the complex mode switching a long time ago and only use the single mode switch exclusively within the core dev team. Everything else is just too consuming and all the other flight modes can be enabled using the tablet.
That is also how most products, e.g. the ones from DJI handle the more advanced modes. You enable them on the screen and you can bail out any time using a HW switch.

@LorenzMeier Good points!
I really haven't tried the single mode switch extensively. And that is due to the fact that until very recently a month ago it was not possible to take off and land in Pos or Alt ctl. I will definetely dig immediately in your proposed setup. There are also still some problems with landing in PosCtl, actually the land detection for the MC and VTOL, so it is pretty dangerous for me at this point to not have the option of Manual.
This way Lorenz is a very good way of setting up things and is something that I wanted long time ago giving exactly examples in previous discussions with DJI. Also don't forget that I might not want to use tablet and just fly, or as in my case use Professional ground station with a second person dedicated to it. So it is not a good idea for the pilot to rely solely on the presumption that he has to use tablet or phone for flying. So in my opinion there should be some rethinking. Or at least I have to wait for the final idea to fully develop. As a professional controller we have to be aware that there are a lot of scenarios and vehicles for use.
Your examples of setup are exactly how DJI is doing it. and it holds true for VTOL's as well. But I have another problem with this setup and it is with the airplanes.
If we are in Pos or Alt control how do we take of from hand or from airstrip? I did not tried this with FW and I don't have idea what will happen when by default I'm in Pos Ctl? Is it going to allow me to arm? And once I arm is it going to spin the prop trying to achieve min airspeed while in my hand. I have three very nasty cuts to my hands and fingers (one involved going to a hospital) with somehow inconsistent behavior of PX4 in FW (given I use master untested versions). Of course I had cuts from DJI as well and other controllers.
Can I assign switch for take off and landing in FW?
@LorenzMeier when the master speaks, everybody obeys :) but please I have points in what I wrote so we have to be right on the details. And if the single mode switch is the way to go we have to remove the old fashioned setup from QGC and not give the option for it.

@dagar I will dig deeper in the single mode switch. I really have not tried it extensively and I will do it in the coming days.
Thanks @dagar @LorenzMeier

@dagar @LorenzMeier
I don't have a 6 pos switch (i have a rotary 6pos knob which is not good for flight modes), and I could not setup take off and landing for FW with the simple switch. The rest is OK. I will fly it tomorrow this way. May be we could have two simple switches what do you think?
Also there should be some more options for Kill switch for the IC engines.
In two weeks we are flying a 4m IC engine airplane, and I have to make the kill switch setup in Horus, otherwise we could not stop the engine. The problem with IC engines is that the throttle is servo, and each engine - servo combination has its own sweet spot for the engine shut down. This concern the IC Helicopters as well.
There is no way to setup Flaps with the single setup page. For professional use it is a good idea to have the option to control the flap extension with a rotary knob as well or at least as a parameter. But this is optional. For the flaps it is a must to have the time it takes for full extension as parameter as well! The flap extension and timing is very important for airstrip landing.

We use the 6-pos option with just 3 active / loaded positions. The others remain unassigned.
Your feedback is really good and appreciated. We want to put a particular focus on usability issues in the next weeks so please keep it coming. I am completely aware how important it is.

Although I'm always arguing for the old style switching, I have to admit that my use case is really tuning an airframe where I'm going through all the modes and also switch directly between different modes. The options Lorenz explained really make a lot of sense for the typical usage. At least with the changed priority in #6764 it should be one step more flexible, also in combination with the single channel switching.

@AndreasAntener I have the same use case as you. When building and testing new frames etc. I prefer to have all modes and options at my disposal.
But I think we have to rethink a little bit more the whole system setup options. I'm rendering some thoughts for the last two days and have some ideas.
@LorenzMeier Your proposed setup is actually a corner case because it is the best one, but for MC. Just tree modes + some additional switches for certain things as transition kill and RTL. A lot like DJI.
Actually for MC I even don't need the Hold mode! it is just not necessary because it equals PosCtl with centered sticks.
Here is another thought i have. DJI already got the niche of one button control for novice users. I use this metaphor taken from the iPhone. The revolution of iPhone was the single button. But in their case they rely on the software developers to implement a back button functionality. It was horrible  in the beginning, now they got it right with time (I still hate it so I use HTC). They introduced 2 other functions with time to this one button. Double click bringing a task management, and now they made it as a fingerprint reader.
DJI got this lane on the highway, given they sell their drones in Apple stores. Of course because you cannot do more with less they moved most of their control to the iPhone or iPad.
Where is the problem? Energy. iPhones and Tablets have limited amount of energy, so cleverly DJI hooked the iPhone or Tablet to their RC with cable for two reasons - 1. energy 2. feed the digital pipeline to the phone or tablet ie Control, Telemetry, Video. This is a very nice and well engineered concept but for now it is limited to MC and pretty short range flights given the pipeline is at 2.4ghz. We cannot compete with them on this. So what are our options? Give more power and functionality for a little bit more advance users.
If we create a smarter system with more powerful feature set we can always mimic some simple setup options for the novice i.e. the new setup interface and only 3 modes.
I think the PX4 should have a two flavors in it. One is the powerful professional set and one is the simple use case set.
The thing that boggles my mind is the planes and VTOL. The planes definitely need more modes and options to fly than the MC. This holds true for VTOLs. VTOL is actually a plane! which has the option to take off and land in MC and it does not need all the things related to take off and landing like flaps and landing gear etc. If you make the VTOL with characteristics of a MC then you loose performance.
So our worst case scenario in terms of complexity is the plane. We have to keep the complexity for the plane but at the same time give the options for simplifications if you don't need complexity or if you fly MC. We cannot just remove the old style of setup. We could make it look and feel like the new style but with more buttons.
I don't feel comfortable having to rely on Tablet or Phone for flight! The 500mw telemetry drains my tablet for 30 minutes. We already have 1:30min flight times with the electric VTOL and about 2 hours with electric small planes. For the IC engines we can reach 5-6 hours and we rely on PC ground station.
We cannot create one size fits all solution and we have to concentrate on the main group of people using our product or the prospect buyers we want to get.
So the main questions that we have to ask ourselves are:
Who is buying Pixhawk?
What for?
How do they control it?
In my opinion the real standard set is Taranis or Futaba with Pixhawk because the sbus standard. Or some of the OpenTX alternatives and flavors. And of course some Spectrums. And majority of this users fly APM. Only the more adventurous one go to PX4 and try the QGC and that is pretty logical. This pattern is the same for US and Bulgaria the places where we have information. At both places PX4 does not have a good reputation because  - It is too hard to setup and tune!!! This implies that our users are a little bit more advanced users. So we have to bear in mind this fact. Taranis created X7 which will give a good budget option and we definitely can fight this tendency with pure marketing strategies.
If we agree that Taranis is the standard and the Airplane is the worst case scenario in terms of complexity and we cannot rely on tablet for now for pure FPV flying we have the following switches for control:
6 - 3 Pos switches
2 - 2 Pos switches
2 - rotary knobs
2 - levers
And from experience I grouped 4 main groups of functionality in different combinations. Not necessary all at once. Depends on the setup.
Flight group - Flight modes, Transition switch.
Take Off and Landing group - Take off, Flaps, Landing gear, Parachute, Landing
Emergency group - RTL, Hold - for FW and VTOL (Loiter), Engine Kill - IC or electric
Video Cam or Instrument control - Pitch, Roll, Yaw, Rec, Cam Switch.
That is for the modes and switches.
So I chose Android as an option because of the back button.
So the real question is 1 button vs. 3 Buttons, iPhone vs. Android.
How do we give as much power to the user with least amount of buttons, but definitely not one. If they want one then fine use the simple switch setup. But most likely they will want more than one, because the main user group is the advanced one. I have no answer to this question yet. I just give you some thoughts out loud.
This is off topic but we have to see all the use cases in order to sort out all the options and the best trends for development.
I think that there is still a lot of business for the OSD! I know a lot of people that want to just fly without PCs, GSs or tablets - advanced hobbyists. They fly one of the most popular OSD FCs. The Vector. Because it has the best OSD. This is if we start to make a specialized small hobby versions of the Pixhawk PX4 products.
 It is called PlayUAVOSD. It is an abandoned Open Source project (because the creator just had other things to do and abandoned it) with a VERY VERY powerful hardware base (ARM ST32F405). Then another guy Tobias made a fork of it but he again is not dedicating time to it. It looks perfect and is not bound to the ugly Fonts of MinimOSD. It visualizes the mission, has a 2 Cam input and you can switch 3 views that are totally configurable. In the future if there are some volunteers  we can make our own fork and polish the thing. Still lacking some visuals like icons etc. Somebody made corrections for PX4 mode names so it is in sync with PX4. I'm not a dev so I could not do it.

If we create a tailored version toward TV and Film production which includes modes that combine flying patterns + cam patterns we will kill the competition ! I can help a lot in this direction.

Here is an idea:
We don't have a simple or complex setup switch page. We have just one that looks like the simple switch. And it looks like the current simple switch setup page. We have 3 types of switches 6 pos, 3 pos, 2 pos and a slider. We make this 4 templates for switches. 3 of these templates look like the current 6 pos switch but with 6, 3 and 4 positions (drop downs). And the slider template is just 1 drop down.
So in reality when we have all the switches OFF we are in the default mode and default switch setup.
The minimum setup could be for MC
1 - 3pos template with three 3 drop downs (this will have label MODE SWITCH) by default the 3 modes could be Position, Stabilized, Mission)
1 - 3pos template with 1 empty (OFF) position + 2 drop down. The last drop down will have RTL by default (label could read EMERGENCY SWITCH)
Then a + button. Once you hit a + you will be given the choice to add a 6,3,2Pos switch or Slider. Then it will add the template for a switch and you will choose a channel for the switch as well with position 1 empty (OFF state) (in the additional switches you will have always position 1 as empty (OFF))
This way I can add as many switches as I want and dedicate whatever modes or functionality as I want. So we go from simple to complex depending on my needs.
For VTOL the default should be the same as MC but with the exception of one additional mandatory default switch.
1 - 3pos template with three drop downs (this will have label MODE SWITCH) by default the 3 modes could be Position, Stabilized, Mission)
1 - 3pos template with 1 empty (OFF) position + 2 drop down. The last drop down will have RTL by default, here by default we could add the Hold (Loiter) as a mid position drop down (label could read EMERGENCY SWITCH)
1 - 2 pos template with 1. MC; 2. FW here you have no choice with drop downs (label could read TRANSITION SWITCH)
then again a + button so I could add mode switches and program them as I like.
For the FW we have the same as VTOL but with a little different modes order:
1 - 3pos template with three drop downs (this will have label MODE SWITCH) by default the 3 modes could be  Stabilized, Position, Mission)
1 - 3pos template with 1 empty position (OFF) + 2 drop down. The last drop down will have RTL by default, and  Hold (Loiter) as a mid position drop down (label could read EMERGENCY SWITCH)
That is it. Simple, elegant and scalable . Going from simple to complex.

If you like my idea i have another suggestion.
It is very impractical and I never used it (even when I was novice to PX4) to calibrate and assign switches in the calibration page. I proffered to do it in the Parameters, when there was no switch setup page.
Just remove the calibration of buttons and sliders from the calibration page. Usually at this stage you don't know yet what are the options and assignments etc. so omit this step here. This will make the calibration page more simple and straight forward.
And then add a simple button on the switch template which reads "Calibrate switch". If you see there are some inconsistencies or miss alignment then hit "Calibrate Switch" Click, Click, OK - boom you are done. simple on the spot. There might be only one or two switches that have problems... No need to calibrate all the switches.

@tubeme Wow that a lot of reading for one to do :).
Trying to step back a bit. I'm going to ignore Android vs. iPhone and focus on the current RC gear that is out there right now and we need to live with. While autonomy is generally increasing, RC use and switch complexity will go down.
What problem are we facing?

Users with different RC hardware, software, and configuration (1 switch to 1 channel, n switches mixed to 1 channel, etc.)
Different flight modes,  emergency modes, special features like kill switches, flaps, etc.
Users with vastly different wishes (fixedwing tuning requiring all the modes, multicopter flying in POCTL plus RTL, POSCTL and all the mission functionality, ...)

There is no way we can come up with a switch model or hierarchical representation ever which captures all of these options! So what can we do?
What can we do?
Well, we have to offer the possible settings and let the user combine his wishes with his RC setup. That's also what the "new setup" tried to accomplish. The setup in QGroundControl needs to be very simple so that a user is aware of what the settings are and can verify it works (and will work when he/she needs it). If there any inconsistencies or conflicts, they need to be detected right then!
What do we have now?
Looking at the current two implementation, I see the following problems:
(Old) switch setup:

The hierarchy is not appearant which can lead to the case that we're discussing here. However, some hierarchy is needed because otherwise the precedence is not given and you don't know if the mode switch or the "loiter/hold/pause" switch is more important (or intuitive, or safe?).

(New) single switch setup:

The flight modes are set in 6 discrete steps. Why 6? It's tedious to get this matching.
What is the precedence of the "Switch Settings" in relation to the flight mode? It is not appearant from the UI in QGroundControl. Why is it a single switch setup if there are additional (mode) switches like "Offboard" and "Return"? It boils down to be the same as the multi switch setup just with 6 instead of 3 options for the mode switch.

The exact problem that we're discussing in this thread is that there are different views and implementations of what the hierarchy should be right now:

My was always that the hierarchy should be by levels of autonomy, meaning that loiter and RTL should only be available in AUTO. Back in the days I was reluctant to have RTL to have precedence over everything! Why? Because it is actually inconsistent with e.g. loiter (which is what you ran into). This being said, I do understand that this is confusing to a user and therefore not something to continue having the future!

Your view is (as I understand it), that emergency switches should always have precedence. Sounds good, so what should happen if you engage both RTL and Pause? Should it pause the RTL or RTL the pause? What about LAND?
What if you issue RTL in QGC and have a switch in Pause? With QGC in the loop it gets even more confusing.
Also note that emergency switches conflict with the manual override which always has precedence anyway, at least for fixedwing.

What could we do?

Have Pause and Land to have precedence over the reset, except RTL which is suggested by @tubeme, @AndreasAntener and check and test that for edge cases.
Or I have one crazy idea: Remove all hierarchy and just listen to the last switch that has been changed or the last command issued by QGC?

@julianoes :) Sorry I just carried away a little...
I understand your point about nesting in the current implementation. And yes it is logical that the RTL and Hold should be part of auto modes from development stand point.
But from user stand point everybody is thinking in a different way. And everybody has its preferences and different needs about mode and functionality priority from pilot / user stand point. So it is a good idea to have e dynamic setup and prioritize the setup to their liking.
I thought about your idea to listen to the last command. It is not crazy and I like it. My worry is that it will be very complicated to develop and there might be some other problems but I like it a lot.
Also while I agree that with the increase of autonomy we will reduce the flight mode options in terms of basic modes. But we will increase the scenario flying options. So pretty much the complexity of RC switches will be the same. Just the switching will move from basic mode flying to scenario flying. Like we added Take Off and Landing and Follow. We will add in the feature things like go here do this and that and we will still need the rc switches to cover this scenarios. We are still far away from the point where we will not need RC. This holds true especially for professional use. Some special professional users are very conservative in their procedures and they are very slow in adapting the new ways of doing things. So the RC is here to stay for a while.

BTW rethinking the modes now, it is a good point you have about what has the priority QGC or the RC??
And then if I have connected Joystick in the QGC what has the priority?? QGC RC or the Joystick??
Given this your idea about what is last has the priority sounds pretty good to me. You touch the Joystick it has the priority. You touch the screen QGC has the priority. You move the Joystick it takes control.

Something about the Emergency. Now we are thinking about only two options for emergency. Hold and RTL. But in the future we can add other emergency scenarios. Like go to Reserve Airport. Go to data link loss Loiter spot 1 etc. We have a collision emergency do this and that. So we have to prepare the system to accommodate all this emergency scenarios and give the user the flexibility to prioritize this options as well.

My basic idea in two words is go from flight modes priority and nesting to control and switch priority.

Hi People,
this quiet a lot to read and understand. My current concern with this matter is the following. I'm one of the specialists having a 3 & 2 Pos Switch mixed together to one RC Channel in order to get 6 Positions. This allows to skip some of the discrete steps. As they are currently all freely assignable in the single Channel Mode Assignment, I assumed this should not cause any Problem. With my setup it is i.e. possible to switch directly from PosCTRL to Pause/Loiter. I was working with this setup since FW 1.2 and have never had any trouble with it - but I did not use Loiter much.


extend/ENV/super: avoid adding llvm to HOMEBREW_LIBRARY_PATHS

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This leads to undesired linkage with LLVM's libunwind (because it
shadows the system's libunwind).
See, for example, Homebrew/homebrew-core#169354.

Does this still work OK for things that link to libLLVM/libclang?

Haven't tested, but I'd be shocked if it didn't for nearly all of them. Will test a bit.

Makes sense yeah

Yea, seems to not break things (tried castxml and nvc). But perhaps it doesn't go far enough -- maybe what we want to do is set  LIBUNWIND_INSTALL_LIBRARY_DIR to something like lib/"unwind" (or perhaps lib/"system", in analogy to Apple's /usr/lib/system/libunwind.dylib) to make sure we're not linking to it unless we really mean to.

I agree. You should only need LLVM libunwind if you absolutely need it - not by default. Like how we did with libc++, which might itself be what uses LLVM libunwind.

Cool. Let's do that. At that stage, though, it makes me wonder if LLVM needs to be keg-only anymore. (All remaining libs in the lib directory don't shadow something OS-provided, IIRC)

it makes me wonder if LLVM needs to be keg-only anymore

The executables will shadow system clang which we don't want.


Incorrect codegen for types with embedded constants

In test PutReferencedConstant the codegen expects the caller to pass a value for RefColorConstant.ColorConstant even though it's defined as a constant in the swagger.  For comparison, see the C# codegen which properly defines ColorConstant as read-only and doesn't require it as a param to PutReferencedConstant.

This issue should be staled, closing


Repository standardisation - Part 2 - Shell & Tools

Please give Nixago (a Nix community project seamlessly integrated into Standard) for the formatters via Numtide's excellent treefmt (also seamlessly integrated) a try: https://github.com/input-output-hk/cardano-world/blob/master/nix/automation/nixago.nix#L8-L33

I'm not in favour of nixago. Dynamically generating config files is a worse UX for many people. I use Nix a lot and even I am often outside a nix-shell.

I'd be happy to use treefmt if we can work it in nicely though.

You can copy or link files, so it's also strictly useful outside of a shell, if you copy.
It's a nice tool, at some point you may probably want to try it out.
Not really strong opinions here. So if you prefer not to use it, that's fine. 😊


:zip.unzip/2 now returns directory name too in Erlang 27.1

The changelog only mentions this about :zip.list_dir/2, but I am seeing the effect for :zip.unzip/2 too.
So here:
https://github.com/crbelaus/bun/blob/75aa6556ee45775b6134ee836b6d2f29da42ea3e/lib/bun.ex#L208-L212
Before download_path was say [~c"/tmp/bun-linux-x64/bun"], now its [~c"/tmp/bun-linux-x64/", ~c"/tmp/bun-linux-x64/bun"]. This is now failing in File.cp! later (as an aside, it's not because it got wrong type, but apparently for anything that expects chardata but is given something else, elixir attempts implicit conversion which for list means joining everything which produces nonsense path here, this just happened to be not a problem with one element list).
Another arm in the case pattern should fix it in backward compatible way I guess, lmk if you want me to create PR.

Thanks for the heads up @natrys. This should be fixed on #26


Triggering the chain-preserving bug (from Zuma) causes the game to grant insane bonuses

Triggering the known chain preserving bug (matching 2 spheres of the same color to a valid match in quick succession to save a chain bonus) causes the game to grant ~Combo x10:

Fixed in e364a78c819f78df796b653a065e292f234725c4 (?)


fix: handle undefined in insert and update sql statements

Test default values in a record for all column types
If any result in something other than null, it may be difficult to query for
e.g. if the user creates a record for employee but omits several fields, what do those fields populate with?


Improve file organization

Add a DOCS folder, both to relocate some existing materials and as a place to build new docs on topics such as our tech stack (see #330)
Add a TESTS folder

To be discussed further…

What was the TESTS folder for?

This process is underway. We now have DOCS and TESTS folders. (The purpose of the latter is to put some separation between the actual schema and the tests that we use to validate JSON files against it.)

A couple of questions regarding this issue:

PROTOCOLS  - should they go to the DOCS folder?  - should we make a folder for it inside the DOCS folder, or better in the root folder?
CHANGELOG - also to DOCS? It´s in the SCHEMA folder now
CONTRIBUTIONS - also to DOCS?


Refactor xIisHandler to eliminate the need for hard coding handler data

Please reference the proposed schema below.  The idea is to allow the new resource to accept parameterized input that will be leveraged to create web handlers that include those hard coded in the current resource, as well as those not hard coded.  I'm working on this update, but wanted to get feedback on the proposed schema.
[ClassVersion("1.0.0")]
class HandlerObject
{
  [Required, Description('Specifies the physical path to the handler')] string Path;
  [Required, Description('Specifies the HTTP verbs that are handled by the new handler'), ValueMap{'GET','HEAD','POST','DEBUG'}, Values{'GET','HEAD','POST','DEBUG'}] string Verb[];
  [Write, Description('Specifies the location for which the cmdlet returns handler information')] string Location;
  [Write, Description('Specifies the modules used for the handler')] string Modules;
  [Write, Description('Specifies preconditions for the new handler')] string PreCondition;
  [Write, Description('Specifies the user rights that are required for the new handler'), ValueMap{'Execute','None','Read','Write'}, Values{'Execute','None','Read','Write'}] string RequiredAccess;
  [Write, Description('Specifies the resource type this handler runs')] string ResourceType;
  [Write, Description('Specifies in MB the ASP response buffer limit')] uint32 ResponseBufferLimit;
  [Write, Description('Specifies the script processor that runs for the module')] string ScriptProcessor;
  [Write, Description('Specifies the managed type of the new module')] string Type;
  [Write, Description('Specifies whether the handler processes full path information in a URI')] boolean AllowPathInfo;
};

[ClassVersion("1.0.0"), FriendlyName("xIisHandler")]
class MSFT_xIisHandler : OMI_BaseResource
{
  [Key, Description('Specifies the name of the new request handler')] string Name;
  [Required, Description('Specifies whether the handler will be installed on the system'), ValueMap{"Present", "Absent"}, Values{"Present", "Absent"}] string Ensure;
  [Read, Description('The handler object properties'), EmbeddedInstance('HandlerObject')] string HandlerObject[]
}

Looks very promising!
Only thing I can see directly is

HandlerObject probably should be named xWebApplicationHandlerInformation, or just xWebApplicationHandler.
Ensure could default to $true and then it doesn't need to be Required, but Write.
Property HandlerObject should probably be renamed to Handler (singular, it can be one or more), and it should have the type qualifier Write?

Labeling this as a breaking change, and help wanted. Let me know if you are working on this, then a label this as 'in progress'.

@boscoedash the change you are proposing in https://github.com/PowerShell/xWebAdministration/pull/360 will add a new resource for this instead? Will your proposal deprecate the resource xIisHandler?

@nehrua Can you see if the resource proposed in PR #360 works as you intended (with the exceptions that it's a new resource).

@johlju The resource proposed in PR #360 works and I intended.  I worked with boscoedash and contributed to its development.  The resource in #360 is intended to deprecate xIisHandler, as it should be able to handle handlers hardcoded in the xIisHandler as well as many others.  Sorry for the confusion.

@nehrua No worries! Great collaboration! 😃 Then we should deprecate xIisHandler in PR #360 as well.


need to report which file failed; weird typedef problem

currently when it fails on an assert it doesn't tell you which source file failed.  it would be nice to know.

converting libzfs, it chokes on /usr/include/libspl/sys/frame.h (to find the problem I had to grep for the offending typedef).
typedefs should only have 1 member, not 2
Cursor(TypedefDecl, "gregset_t", Type(Typedef, "gregset_t"))
[Cursor(TypeRef, "greg_t", Type(Typedef, "greg_t")), Cursor(IntegerLiteral, "", Type(Int, "int"))]

Here is the offending code:
#if defined(_LP64) || defined(_I32LPx)
typedef long    greg_t;
#else
typedef int     greg_t;
#endif
Bizarrely, it chokes even if I hack the source by doing:
FIXME
#define _LP64 1
just before the code.
`
laeeth@sheldrake> C_INCLUDE_PATH=/usr/include/libspl:/usr/include/libzfs /tank2/develop/include/bin/include libzfs.h /tank2/develop/include/libzfs/libzfs.di
typedefs should only have 1 member, not 2
Cursor(TypedefDecl, "gregset_t", Type(Typedef, "gregset_t"))
[Cursor(TypeRef, "greg_t", Type(Typedef, "greg_t")), Cursor(IntegerLiteral, "", Type(Int, "int"))]
`
If I hack the include D code by doing the following then it continues on its merry way and appears to finish.  The resulting D source doesn't compile yet, but that's probably for other reasons.
You might want to have a treat errors as warnings command-line switch, because in the general case it's more than  occasionally much better to do most of the job than just fail.  Maybe you could add // FIXME: message to the resulting source.
source/include/translation/typedef_.d
`
if(!(children.length == 1 ||
       (children.length == 0 && typedef_.type.kind == Type.Kind.Typedef)))
{
        import std.stdio:writeln;
       writeln(text("typedefs should only have 1 member, not ", children.length, "\n", typedef_, "\n", children));
}

`

These are two issues. Please open a different Github issue for each problem. I'm closing this and opening two.

@Laeeth See #13 and #14


Collect width and height for SVG

1. Why is this change necessary?
Shopping worlds and other components need width and height for correct calculations like image mapping.
2. What does this change do, exactly?
Add to supported type image also type vector with extension svg. Svg is most common supported vector format in browsers. Svg is XML based and has different ways to add width and height. Directly width and height attribute or viewbox (second and third value).
3. Describe each step to reproduce the issue or behaviour.
Add a shopping world banner and try to add an SVG with a image map.
4. Please link to the relevant issues (if any).
Is closed
5. Which documentation changes (if any) need to be made because of this PR?
SVG support is improved for example in shopping world. This allows modern light weight vector images for highDPI displays with less traffic and no need thumbnails.
6. Checklist

[ ] I have written tests and verified that they fail without my change -
-> No existing tests for migrateMeta

[x] I have squashed any insignificant commits

[x] This change has comments for package types, values, functions, and non-obvious lines of code

[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21675
Please use this issue to track the state of your pull request.

@soebbing any chance for 5.5?

@xf- I'd like to do that, but it will have to be after 5.5.0, sorry :(

Hi @xf-, thank you for your contribution! 💙
Sorry it took us so long. 😭


Description for colors

It would be helpful to have a description for the color headings (Region, Base, Primary) to better explain their function. A "more information" button could be an example.

I'll look into that! In the meantime you can check out the brief descriptions on our blog post here in the "How to use" section.


fix upsert /id generation

Packages impacted by this PR
@azure/cosmos
Issues associated with this PR
#21383
Describe the problem that is addressed by this PR
Upsert operation was failing when partition key of container is /id and id is missing in the object body. This fix generates the uuid before extracting partition key from the body, similar to create operation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A
Are there test cases added in this PR? (If not, why?)
N/A
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


refactor build.sh script.

Refactor & Debug build.sh script:

Let platforms, ABIs, release/debug targets case insensitive:

./build.sh -p Android Debug

Above cmd will do nothing, because Android & Debug are case sensitive. So let those keywords case insensitive maybe a good idea.

Add error msg to remind the developer:

./build.sh -p android
./build.sh -p andr
./build.sh -p android bug
./build.sh -p android -q arm debug

Above error cmds will not has hints to remind the developer, so I add error msg to cover: missing targets, invalidate platform, invalidate target, invalidate ABI.

Let ISSUE_DESKTOP_BUILD as false

This var can be false, I just need to rearrange the build orders at the end of the script, and the only dependency is run_tests, I add build the desktop Debug target manually inside run_tests.

Debug Android samples build

./build.sh -p android -k sample-gltf-viewer debug

The above cmd will fail, the backtrace told me the cmd was not found in out/release/filament/bin/?, but I'm running the debug build, and the cause is missing property com.google.android.filament.tools-dir, so the groovy plugin filament/android/buildSrc/src/main/groovy/FilamentPlugin.groovy will use the default config one.
                def filamentToolsPath = providers
                        .gradleProperty("com.google.android.filament.tools-dir")
                        .forUseAtConfigurationTime().get()

I don't understand where it config the forUseAtConfigurationTime(), but the value is out/release/filament/.
So config -Pcom.google.android.filament.tools-dir will resolve this bug.

use pushd & popd to replace cd

I don't really understand the benefit of allowing case insensitivity.
But I think giving an error when necessary flags like debug or release is not specified is a good idea. But probably we just need a more general approach to validating the arguments.

I don't really understand the benefit of allowing case insensitivity.
But I think giving an error when necessary flags like debug or release is not specified is a good idea. But probably we just need a more general approach to validating the arguments.

Oh, there are duplicated codes to check the debug & release for platforms (desktop, android, ios, webgl).
So, I add a function to reduce the duplication:
function check_debug_release_build {
    if [[ "${ISSUE_DEBUG_BUILD}" == "true" || "${ISSUE_RELEASE_BUILD}" == "true" ]]; then
        "$@";
    else
        echo "You must declare a debug or release target for $@ builds."
        echo ""
        exit 1
    fi
}


Sponsorship pipeline & documented process

We need to set up a private pipeline and process for handling different stages of sponsorship and negotiation, as welll as renewals for the sponsorship.
Process must be documented.
To keep overview of progress - handled by project coordinator who is going to be responsible for that.

I believe it is the easiest to have a private github repository with each issue dedicated to a specific donor, plus labels indicating the status of the donor - e.g. in talks, donating, stopped, etc, plus the donation level label, plus whatever else like "waiting for the donor" vs "waiting for us to reply".  On top of it, github issues will allow users to subscribe to specific or all issue changes, plus the entire history is more permanent than in a google doc.  Search would be far easier to do (simply use label:.... to filter), and it would be possible to have an agreed public statement in the readme if needed (e.g. these are our current donors) type of thing.

My suggestion is to use Hubspot.com for free - and use Deals kamban in there.
This means we could also log emails - get Companies and Contacts properly logged in CMS - without any work at all.

HubSpot is used

Please document the process - so if you go for on holidays people can jump instead of you :-). This is still missing.

https://github.com/maplibre/maplibre/wiki/Sponsorship-Pipeline


Create a Beta v1 of the API

We currently have preliminary work to version the API and overall improve the best practices of API format. In order to make this new version of the API production ready, several things need to be updated:

Document the new API (preferably by OpenAPI spec)
Update the manager to use this new API
Update the frontend to use this new API
Update the authorization policy plugin in the backend to use this new API

While this work is being done, it would probably be good to create a feature flag, default to off, that can be used to turn on the new API.

1 and 4 Completed for v1.8.0.
Created #491 for the manager moving to v1
and #492 for the frontend moving to v1


Uninitialized string offset

When using isLocationOnEdge on several decoded polylines, I am getting error on some encoded polylines: Uninitialized string offset: 156 in PolyUtil.php on line 313, which points to a decoding function. I have escaped all the backslashes from encoded polyline at the time of creating in Javascript, but I am not aware if some characters should be escaped also in PHP.
Encoded polyline, which produces the error is:
polyline_error.txt

Hi @jaska120 ,
Please can you show how you making the call ?
The isLocationOnEdge method only available for Directions API.
Here how this method to be invoked within this package:
$response = \GoogleMaps::load('directions')
            ->setParam([
                'origin'          => 'place_id:ChIJ685WIFYViEgRHlHvBbiD5nE',
                'destination'     => 'place_id:ChIJA01I-8YVhkgRGJb0fW4UX7Y',
            ])
           ->isLocationOnEdge(55.86483,-4.25161);

    dd( $response  );  // true

Regards,
Alexander

I am making the call to database where are user previously inserted encoded polylines and point is user defined point to which the query is made against.
$distance = 1000; //meters
$startpoint = array('lat' => 61.487002, 'lng' => 23.790636);
$endpoint = array('lat' => 60.215399, 'lng' => 24.943364);

while($row = $result->fetch_assoc()) {
	$encoded = $row["encodedpolyline"];
	$polyline = \GeometryLibrary\PolyUtil::decode($encoded);

	$startboolean = \GeometryLibrary\PolyUtil::isLocationOnEdge($startpoint,$polyline,$distance);
	$endboolean = \GeometryLibrary\PolyUtil::isLocationOnEdge($endpoint,$polyline,$distance);

        if ($startboolean and $endboolean) {
		//var_dump($encoded);
	        //var_dump($startboolean);
	       //var_dump($endboolean);
	       $data[] = $row;
	}
}

$data array is being JSON encoded and sent to client via Ajax call and it returns correctly except the error occurs with the last polyline. In this example I have provided $startpoint and $endpoint arrays hardcoded but those are the coordinates with which user would face error.
Please find attached txt document for encoded polylines SQL queried from $row["encodedpolyline"]. The problem occurs only with the last polyline and the functions works if I delete that from database so I guess it has something do with the format of encoding.
example_encoded_polylines.txt

Hi Alexander,
My bad, there was still a problem with escaping backslashes and your code is working normally.
Thanks,
Jaska

Hi @jaska120 ,
Thank you for your update, glad to hear that issue has been resolved.
Regards,
Alexander


[BUG] CategoryName not appearing in Application Insights trace

Library name and version
Azure.Monitor.OpenTelemetry.AspNetCore 1.2.0
Describe the bug
I'm running an ASP.NET Core site with Open Telemetry configure to use Azure Monitor:
        builder.Services.AddOpenTelemetry().UseAzureMonitor(options =>
            {
                options.ConnectionString = connectionSetting.ApplicationInsightsConnectionString;
                options.EnableLiveMetrics = false;
            })
            .WithMetrics(providerBuilder => providerBuilder
                .AddMeter("Microsoft.AspNetCore.Hosting")
                .AddMeter("Microsoft.AspNetCore.Server.Kestrel"))
            .WithTracing(providerBuilder =>
            {
                providerBuilder.AddSqlClientInstrumentation(options =>
                {
                    options.SetDbStatementForText = true;
                });
                providerBuilder.AddSource(activitySource.Name);
            });

But the CategoryName is not coming through to the Trace entries in Application Insights.

I've confirmed with a Console Exporter that it seems to be included:
LogRecord.Timestamp:               2024-07-09T14:36:13.7590899Z
LogRecord.TraceId:                 5db02af065203a913b074ef34ecb022a
LogRecord.SpanId:                  b0869753585a3222
LogRecord.TraceFlags:              Recorded
LogRecord.CategoryName:            MyLoggerName
LogRecord.Severity:                Debug
LogRecord.SeverityText:            Debug
LogRecord.FormattedMessage:        Using GetCurrentSiteHandler to handle request
LogRecord.Body:                    Using {0} to handle request
LogRecord.Attributes (Key:Value):
    0: GetCurrentSiteHandler
    OriginalFormat (a.k.a Body): Using {0} to handle request
LogRecord.ScopeValues (Key:Value):
[Scope.0]:SpanId: b0869753585a3222
[Scope.0]:TraceId: 5db02af065203a913b074ef34ecb022a
[Scope.0]:ParentId:<PHONE_NUMBER>000000
[Scope.1]:ConnectionId: 0HN504HTTDB38
[Scope.2]:RequestId: 0HN504HTTDB38:00000001
[Scope.2]:RequestPath: MyRequestPath

Resource associated with LogRecord:
telemetry.distro.name: Azure.Monitor.OpenTelemetry.AspNetCore
telemetry.sdk.name: opentelemetry
telemetry.sdk.language: dotnet
telemetry.sdk.version: 1.9.0
service.name: unknown_service:Cbh.Operations.Saturn.SiteHost

Expected behavior
The CategoryName property would be available in Application Insights
Actual behavior
The property is not included.
Reproduction Steps
See description.
Environment
.NET SDK:
 Version:           8.0.302
 Commit:            ef14e02af8
 Workload version:  8.0.300-manifests.00e64df5
 MSBuild version:   17.10.4+10fbfbf2e

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.302\

Host:
  Version:      8.0.6
  Architecture: x64
  Commit:       3b8b000a0e

.NET SDKs installed:
  8.0.206 [C:\Program Files\dotnet\sdk]
  8.0.302 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Thanks for sharing the feedback. This is indeed a limitation, but lets use https://github.com/Azure/azure-sdk-for-net/issues/44746 for tracking.
Closing as duplicate.


Typo fixed

There was a small typo at home.html for account page link
Corrected that..

There was a small typo at home.html for account page link
Corrected that..

Thanks for fixing it , merging it


Deploying to Heroku not currently working

Screenshot from the deploy process:

It's interesting as it's a squash migration that seems to conflict with the migration that it contains.

Indeed it fails on Heroku but seems to work fine with a local sqlite database :open_mouth:

It fails locally when used with Python 3.

Thanks, fixed now.

Related ticket in Django: https://code.djangoproject.com/ticket/25906


user12986714: Watch<PHONE_NUMBER>2

user12986714 requests the watch of the watch_number<PHONE_NUMBER>2. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Eliah Kagan in Charcoal HQ

Appeared in https://metasmoke.erwaysoftware.com/post/253234.


yewtube: init at 2.9.0, replace mps-youtube

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[x] Fits CONTRIBUTING.md.

cc @k0ral @odi (can't request a review for some reason). would you like to be added to the maintainer list for yewtube?

cc @k0ral @odi (can't request a review for some reason).

maybe because I am not part of the NixOS github organization?

would you like to be added to the maintainer list for yewtube?

no its not necessary for me to be on the maintainer list of yewtube

would you like to be added to the maintainer list for yewtube?

Gladly, thank you :) .

maybe because I am not part of the NixOS github organization?

That's probably it. I think you should both request to be added here, so you can get pinged by ofborg

would you like to be added to the maintainer list for yewtube?

Gladly, thank you :) .

Great! I just added you

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1673

Ping


Enable side-by-side private assembly

This PR enables side-by-side private assembly.
I know patching the ruby source is out of the RubyInstaller's policy.
But, since this is packaging issue, I chose committing to the RubyInstaller
rather than reporting to the Ruby official repository.
With this PR, I changed the common dlls' install path to under
the bin/RubyInstaller.MRI.RubyAssembly directory
so that the PATH setting to the ruby.exe does not affect other applications
that use same name dlls.
Hope this makes RubyInstaller's ruby more stable and easy to update
the toolchain.

[Done   ] ruby*, check*
[Not yet] ruby*:package:installer

[Done  ] ruby*:package:installer

This looks interesting. I will look at this more when I get a chance.

This is solved in RI2. See: https://github.com/oneclick/rubyinstaller2/commit/b2bd6303206e278cb42e304bdb2525625a6dac46


python312Packages.plugwise: 1.4.0 -> 1.4.1

Diff: https://github.com/plugwise/python-plugwise/compare/refs/tags/v1.4.0...v1.4.1
Changelog: https://github.com/plugwise/python-plugwise/releases/tag/v1.4.1
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 344040 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.plugwise
python311Packages.plugwise
python311Packages.plugwise.dist
python312Packages.plugwise
python312Packages.plugwise.dist


Unable to horizonatally center pagination

Is there a way to center the pagination?  I'm currently unable to do so because of these hidden list items.

This requires further investigation.  Just looking at just your screenshot, it looks like that's margin?

It's actually an <li> with width set to 0.  UI Bootstrap has a lot of these that aren't completely removed from the DOM.

Sorry to bother you.  Turns out I actually had margin being set on them globally.


[Package Request]: New package: Microsoft.Promptflow version 1.7.0

How can we help?
I would like help so I can submit the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
pr: https://github.com/microsoft/winget-pkgs/pull/148162/files
Download Page Url: https://promptflowartifact.blob.core.windows.net/msi-installer/promptflow-1.7.0.msi
Publisher: Microsoft Corporation
Package Name: Microsoft Promptflow
Description: Prompt flow is a suite of development tools designed to streamline the end-to-end development cycle of LLM-based AI applications, from ideation, prototyping, testing, evaluation to production deployment and monitoring. It makes prompt engineering much easier and enables you to build LLM apps with production quality.
Package Version: 1.7.0
Installer URL:  https://promptflowartifact.blob.core.windows.net/msi-installer/promptflow-1.7.0.msi

Close with reason: Resolved by PR;

#148162


perf(combine-api,dispatch-service): speed up use of COMBINE API by dispatch service

Addresses part of #4283

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


There should be a similar page for Antivirus on Windows Server 2019.

Especially the 'Windows Defender Antivirus' feature on Windows 2019, there is no more sub-feature, the 2 sub-features below are merged to have a single one.
. Windows Defender
. GUI for Windows Defender

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

ID: 6d1dee2b-d86a-0019-f689-81483fab31f5
Version Independent ID: 02722ca2-1dde-aafb-22e3-67259c4ece37
Content: Windows Defender Antivirus on Windows Server 2016
Content Source: windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-on-windows-server-2016.md
Product: w10
Technology: windows
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@denisebmsft Would you be able to shed light on this matter? Any plans to release the 2019 version of the article? Thank you.

I'm having trouble with Ansible for this feature in the 2019 server. Confirming the details about 2019 version would be helpful.

@e0i, @huuducle, and @shivakakarla, I'm looking into this, and will post an update as a new comment here.

Hello! The article has been updated, so I am going to close this issue for now. Please let us know if you run into any issues!


tests: build error

https://travis-ci.org/inveniosoftware/invenio-oauth2server/jobs/378447598

Apparently, Flask docs for v0.11 are no longer there. Docs for v0.12 are good though... So updating the docs' conf.py should be enough to fix the build.
The question is, do we also update the setup.py dependency as well? Doing so might possibly break other invenio packages that depend on invenio-oauth2server and have a minimum version of 0.11.1, causing a conflict with this module...
This though is probably related to the bigger issue of syncing common dependencies (i.e. flask, six, wtforms, etc) between all invenio modules. Also, Flask 1.0 is out, so maybe it makes sense to plan an upgrade campaign at some point and address these issues then...


Give a higher score to matches at the beginning of a path component?

Previously: Stable sorting?
Besides https://github.com/thoughtbot/pick.vim, my most common use case is a fuzzy project finder that sorts by most recent. However once I start typing, the original sort order appears to be lost.
I think the unstable sort probably makes sense as a default for performance reasons, but perhaps a stable sort option would be appropriate?

Hey, @sharplet! Thanks for your feedback.
What version of Pick are you running? From 1.3.0, the sorting should be stable.

You know, I'm on 1.3.0, so perhaps stability isn't the problem!
Here's an example that didn't quite match my expectation:

After typing the query li, the first result is "CLIKit", instead of something that starts with "li", "liftoff".
Note that selecta exhibits the same behaviour:

I see what you mean. The reason this happens is because the algorithm scores higher the shorter the total string is compared to the matching substring.
I'm not sure how we could improve the algorithm for this use case but I'd be happy to hear any suggestions! Pull requests are of course also very welcome.

I think for the algorithm to follow my intuition, it would have to become aware of path components, and favour matches anchored to the beginning of a path component.
I took a dive into the source, but I think a PR is probably beyond me at this point (without some serious hand-holding).

Yes, something like that might work!
I'd be happy to answer all your questions and also to pair on this if we can find a time that works for both of us.
In the meantime, should we rename this issue or close it in favor of a future PR?

I went ahead and renamed the issue for now. It would be cool if we could take a look at this at some time.

I'll go ahead and close this issue for now.
If anyone would like to take a stab at something like this, I think it's important to consider the fact that pick is also used to search for other things than file names. An alternative scoring algorithm would therefore have to be sufficiently general in order to be possible to merge.


Documentation: add Introduction section

how to display snippets
how to display settings
how to add snippet
how to add setting

Description + screenshot + keyword combination for Linux, Windows, and Mac.

@rodionos What exactly do you mean by settings? The plugin configuration?

Added with #139 #136


[bug] Updater - Tauri API error: Invalid cross-device link (os error 18)

Describe the bug
During the installUpdate() call, I receive the error "Tauri API error: Invalid cross-device link (os error 18)". I'm using a statically hosted update file following the Update File JSON Format. I have the updater dialog set to false. I'm trying to update an AppImage.
I found another "Invalid cross-device link" error in an unrelated python project.

Reproduction
No response
Expected behavior
No response
Platform and versions
Environment
  › OS: Manjaro 21.3.1 X64
  › Node.js: 16.15.1
  › npm: 8.5.5
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.0.0
  › @tauri-apps/api [NPM]: 1.0.1
  › tauri [RUST]: 1.0.0,
  › tauri-build [RUST]: 1.0.0,
  › tao [RUST]: 0.11.2,
  › wry [RUST]: 0.18.3,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../public
  › devPath: http://localhost:8080/
  › framework: Svelte
  › bundler: Rollup

App directory structure
  ├─ .git
  ├─ src-tauri
  ├─ public
  ├─ scripts
  ├─ .github
  ├─ .aws-sam
  ├─ src
  └─ node_modules

Stack trace
No response
Additional context
No response

Thanks @lucasfernog. Looking forward to seeing this reflected in the npm package.

This is still happening for macos with tauri v1.2.1


Hotkey F1 doesn't work for PHP

When pressing F1 in PHP file nothing happens.

I''m seeing this too. The error showing in the console is
Traceback (most recent call last):
  File "/opt/sublime_text/sublime_plugin.py", line 1088, in run_
    return self.run(edit)
  File "/home/rodney/.config/sublime-text-3/Packages/Zeal/zeal.py", line 128, in run
    self.handler = ZealNameInputHandler(matched_docsets, text, self.clear_handler)
TypeError: __init__() takes 3 positional arguments but 4 were give

I think the line
self.handler = ZealNameInputHandler(matched_docsets, text, self.clear_handler)
should be
self.handler = ZealNameInputHandler(matched_docsets, text, on_offer=self.clear_handler)
but when I make that change I get the error
Traceback (most recent call last):
  File "/opt/sublime_text/sublime_plugin.py", line 1082, in run_
    return self.run(edit, **args)
TypeError: run() got an unexpected keyword argument 'zeal_name'

which is where I had to stop looking into this.

Thanks for the report. I released 2.0.2 with the fix from my fork at https://github.com/SublimeText/Zeal.

Thanks for the report. I released 2.0.2 with the fix from my fork at https://github.com/SublimeText/Zeal.

v2.0.2 seems to be working again thanks, this issue is good to close

v2.0.2 seems to be working again thanks, this issue is good to close


incremental backup

Is your feature request related to a problem? Please describe.
Hi, dear. I‘m working on some periodic forms. Now, I have to create a task to complete the dump operation. It cost a lot of time to export data because of a quite large amount. Could you provide an incremental way to export it?
Describe the solution you'd like
An incremental backup method can only need to back up files that have been added or modified compared to the previous one。
Describe alternatives you've considered
differential backup?

Thx!!!!

Hello @paul-yangmy,
If you're talking about database backup, then this feature may not be available by the database you're using.
What's the database you're referring to?

Hi, yes. Did we have the database incremental backup? I used mysql.

Thanks for the response.
Looks like that MySQL indeed supports such feature.
We currently don't support that.


⚠ Bofrost.at has degraded performance

In 83469fe, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1571 ms

Resolved: Bofrost.at performance has improved in 5ac8e61 after 9 minutes.


Seamless teleport

Teleporter which continues your movement seamlessly. If you jump to a teleport trigger from the side, your jump movement should be applied to the teleport destination. I'm not exactly sure how this should be handled since teleports where you enter from top/bottom might be a bit weird.

This is basically how teleporters that keep speed work, not sure what the idea here is tbh, closing.


 Ich brauche Kuhfleisch aber ich habe Angst reinzugehn. Kannst
du 5 Kühe töten?
finish-message: Danke! Hier ist eine kleine Belohnung für dich!
stages:
ordered:
'1':
mobs-to-kill:
- Cow
mob-amounts:
- 5
locations-to-kill:
- world 43.0 80.0 371.0
kill-location-radii:
- 40
kill-location-names:
- Kuhfarm
'2':
npc-ids-to-talk-to:
- 123
rewards:
items:
- ==: org.bukkit.inventory.ItemStack
v: 2227
type: EMERALD
quest-points: 1
options:
allow-commands: true
allow-quitting: true
use-dungeonsxl-plugin: false
use-parties-plugin: true
share-progress-level: 1
require-same-quest: true**

When you say "in chat" what are you doing to trigger the message? Taking the quest? Running a command?
Also, please use a website like Pastebin to share your quest. Usually I'd close the ticket for failing to do that, but I know you're a longtime user, so please just edit your post.

Yes when taking the quest

Thanks for the clarification. Fix will be available in the next SpigotMC release.


Commands endpoint

To summarize, there are multiple changes happening:

Wwagger Command API has changed, because there was a problem with python client generation.

We needed to remove the oneOf field from Commands and instead parse everything into the generic Command that contains all fields
Each of the commands still exists in the swagger definition, so we can take advantage of the validation functions

We needed to differentiate between zero valued fields and missing fields, therefore, the nullable: true was added. As a result, the Go struct fields are now pointers so their presence can be checked easily with comparing with nil.
Basic implementation of all commands. Some checks might still be missing


move to new repo

Why is it stage?

Because that's what @jasonthomas told me :)

We still want to reference the old one in the docs/README.rst?

And requirements/docker.txt?

got those two in that commit ^

Cool. r+


Remove outdated LDAPS requirement

LDAPS is no longer required

Please see https://github.com/prestosql/presto/pull/3644


dependencies warning with Spyder5

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

Install Spyder5

What is the expected output? What do you see instead?
I get a warning about missing dependencies: spyder_kernels >=2.0.1,2.1.0 : 2.0.1 (NOK)
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

I have the same issue after installing Spyder 5.0.0, also rtree >=0.8.3 : None (NOK)

I have same issue, on both Mac and windows. Spyder 5.0 started fine one time on windows, but failed 2nd time. On mac the issue is persistent, but I have yet to understand the impact.
"I get a warning about missing dependencies: spyder_kernels >=2.0.1,2.1.0 : 2.0.1 (NOK)"
if I were to try to resolve, how/where?

I get the same message even if

I installed those kernels with pip
I updated conda
I installed those kernels with conda

Hey all, thanks for reporting. This is a duplicate of issue #15091 and it'll be fixed in our next version (5.0.1), to be released shortly.
In the meantime, please ignore that message, it's a false alarm.


Markdown not rendered in herocard

In the sample 01.a.getting-started-full-bundle when i type "herocard", the markdown is not rendered.

I'm having the same issue in my webchat component while using the latest version of the CDN.
https://cdn.botframework.com/botframework-webchat/master/webchat-es5.js

This bug has been fixed and will be available in our next release later this month. If you need these changes immediately, please see our documentation on pointing to our MyGet feed for latest bits.
https://github.com/microsoft/BotFramework-WebChat/issues/2062

I'm still having the issue while using
https://cdn.botframework.com/botframework-webchat/master/webchat-es5.js
Am I missing something ?

The Web Chat Development Team no longer updates the master CDN. Please use latest instead.


Update Storybook theme and add v9 preview

Questions
Answers

Description?
Update storybook configuration and add PrestaShop v9.0.0 option in storybook themes

Type?
new feature

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company
@PrestaShopCorp

How to test?
Run storybook and check if v9 theme is applied when selected

Selected theme PrestaShop v9.0.0 in Storybook UI :

Hello @tblivet!
This is your first pull request on autoupgrade repository of the PrestaShop project.
Thank you, and welcome to this Open Source community!


Add Build information

This is the current notes I have on how to get this building locally, leaving as draft until I'm done with my testing in case I encounter any additional notes

This is already documented under https://github.com/Level/classic-level#supported-platforms via the node-gyp link which documents the prerequisites for every platform:

In that case you'll need a valid node-gyp installation.


educloud issues

a running tally of issues that need to be addressed for educloud users

users need to allow pop ups from educloud

we have decided not to use educloud due to ongoing issues with educloud


SubscribeCallback() is not being called in pub-sub-sample program

Hi All,
I have compiled the SDK on my Ubuntu VM and tried to run the pub-sub-sample program. I was expecting to see both the published and subscribed messages on the hardcoded topic but looks like it can publish the messages but nothing happens on the subscription. Below is the output:
[INFO] Wed Mar  4 18:58:55 2020
:680 [OpenSSL Wrapper] [140023712573248] [ConnectTCPSocket:L234] : resolved avkkmno6cibmr-ats.iot.us-west-2.amazonaws.com to <IP_ADDRESS>
[INFO] Wed Mar  4 18:58:56 2020
:58 [Network Read] [140023677699840] [HandleConnack:L228] : Network Connect Response. Success : SDK Code 0.

******************************Entering Publish with no queuing delay unless queue is full!!**************************
Publish Payload : Hello from SDK : 1
Publish Packet Id : 3
Publish Payload : Hello from SDK : 2
Publish Packet Id : 4
Publish Payload : Hello from SDK : 3
Publish Packet Id : 5
Publish Payload : Hello from SDK : 4
Publish Packet Id : 6
Publish Payload : Hello from SDK : 5
Publish Packet Id : 7
Success : SDK Code 0.
Waiting!!! 1
Waiting!!! 2
Waiting!!! 3
Waiting!!! 4
Waiting!!! 5
Waiting!!! 6
Waiting!!! 7
Waiting!!! 8
Waiting!!! 9
Waiting!!! 10
Waiting!!! 11
Waiting!!! 12
Waiting!!! 13
Waiting!!! 14
Waiting!!! 15
Waiting!!! 16
Waiting!!! 17
Waiting!!! 18
Waiting!!! 19
Waiting!!! 20
Waiting!!! 21
Waiting!!! 22
Waiting!!! 23
Waiting!!! 24
Waiting!!! 25
Waiting!!! 26
Waiting!!! 27
Waiting!!! 28
Waiting!!! 29
Waiting!!! 30
Waiting!!! 31
Waiting!!! 32
Waiting!!! 33
Waiting!!! 34
Waiting!!! 35
Waiting!!! 36
Waiting!!! 37
Waiting!!! 38
Waiting!!! 39
Waiting!!! 40
Waiting!!! 41
Waiting!!! 42
Waiting!!! 43
Waiting!!! 44
Waiting!!! 45
Waiting!!! 46
Waiting!!! 47
Waiting!!! 48
Waiting!!! 49
Waiting!!! 50
Waiting!!! 51
Waiting!!! 52
Waiting!!! 53
Waiting!!! 54
Waiting!!! 55
Waiting!!! 56
Waiting!!! 57
Waiting!!! 58
Waiting!!! 59
Waiting!!! 60
Waiting!!! 61
Waiting!!! 62
Waiting!!! 63
Waiting!!! 64
Waiting!!! 65
Waiting!!! 66
Waiting!!! 67
Waiting!!! 68
Waiting!!! 69
Waiting!!! 70
Waiting!!! 71
Waiting!!! 72
Waiting!!! 73
Waiting!!! 74
Waiting!!! 75
Waiting!!! 76
Waiting!!! 77
Waiting!!! 78
Waiting!!! 79
Waiting!!! 80
Waiting!!! 81
Waiting!!! 82
Waiting!!! 83
Waiting!!! 84
Waiting!!! 85
Waiting!!! 86
Waiting!!! 87
Waiting!!! 88
Waiting!!! 89
Waiting!!! 90
Waiting!!! 91
Waiting!!! 92
Waiting!!! 93
Waiting!!! 94
Waiting!!! 95
Waiting!!! 96
Waiting!!! 97
Waiting!!! 98
Waiting!!! 99
Waiting!!! 100

*************************Results**************************
Pending published messages : 5
Total published messages : 5
Exiting Sample!!!!
Exiting Thread MQTT Keep alive Action!!
Successfully Exited Thread MQTT Keep alive Action!!
Exiting Thread TLS Read Action Runner!!
Successfully Exited Thread TLS Read Action Runner!!
Exiting Thread Outbound Action Processing!!
Successfully Exited Thread Outbound Action Processing!!

Any help would be great! Please let me know if any additional information is required.

Resolved the issue. I had to update the policy for iot:* and after that, I was able to see the subscription messages. But, this is strange because I had iot:Subscribe present on the policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "iot:*",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iot:Connect",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iot:Subscribe",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iot:Publish",
      "Resource": "*"
    }
  ]
}

Closing the issue but if anyone can please shed light on this policy puzzle :)


Updated dependencies to their latest stable version.

Updated dependencies to their latest stable version.

And then this one 😁


Unable to compile hello-world example

I get the following errors (rust 1.34.1):
error[E0658]: The attribute `inherit` is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
 --> src/lib.rs:5:3
  |
5 | #[inherit(Node)]
  |   ^^^^^^^

error[E0658]: The attribute `methods` is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
  --> src/lib.rs:10:3
   |
10 | #[methods]
   |   ^^^^^^^

error[E0658]: The attribute `export` is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
  --> src/lib.rs:21:5
   |
21 |   #[export]
   |     ^^^^^^

error: cannot find derive macro `NativeClass` in this scope
 --> src/lib.rs:4:10
  |
4 | #[derive(NativeClass)]
  |          ^^^^^^^^^^^

error[E0061]: this function takes 1 parameter but 0 parameters were supplied
  --> src/lib.rs:31:10
   |
31 |   handle.add_class::<HelloWorld>();
   |          ^^^^^^^^^ expected 1 parameter

error[E0277]: the trait bound `HelloWorld: gdnative_core::class::NativeClass` is not satisfied
  --> src/lib.rs:31:10
   |
31 |   handle.add_class::<HelloWorld>();
   |          ^^^^^^^^^ the trait `gdnative_core::class::NativeClass` is not implemented for `HelloWorld`

error: aborting due to 6 previous errors

You don't seem to be using qualified names for the macros, did you add a use gdnative::*; or #[macro_use] extern crate gdnative; to your file?

There seems to be something wrong with the crates.io entry for this crate.
I had this issue too, after I replaced gdnative = "0.5.0" in the dependencies with
[depencdencies.gdnative]
git = "git://github.com/GodotNativeTools/godot-rust"

and replaced
#[derive(NativeClass)] > #[derive(gdnative::NativeClass)]
#[inherit(Node)] > #[inherit(gdnative::Node)]
#[methods] > #[gdnative::methods]
(edition 2018 BTW)
it worked

Yes, the newest version with the procedural macros is not on crates.io yet. It has to be a git (or path) dependency for now.

Thanks @T0mstone. I'll give that a try.

Closing this issue since it works, although it really should mention in the readme that you need the github version of godot-rust.

I also think the readme should have some kind of warning about this, and also links to a version of the examples which works with the package published on crate.io.

This appears to still be a thing? I also had to switch to the Git version in order to build the code that's in the README.md, which is confusing. If the README.md instructions are going to sometimes not work between releases, maybe don't even include them? Or maybe them super generic, like showing how to install the Git version or crate.io version, and then tell users to run cargo doc to get more information?

In the readme, this:
[dependencies]
gdnative = "0.5.0"

should probably be replaced with this:
[dependencies]
gdnative = { git = "git://github.com/GodotNativeTools/godot-rust" }

Thanks @karroffel


[question]Confusion about tab

Summary:
I have deleted the style tab from ‘src/app/(app)/_layout.tsx’，but still display the style tab.  i don't know why

Steps to reproduce:
Expected behavior:
Hide the deleted tabs
Additional notes:
Tasks

[ ] Task 1
[ ] Task 2
[ ] Task 3

my fault


Initializes combo boxes and buttons as soon as FXML is loaded

Contains
Initializes the top buttons and ChangeListeners for the combo boxes as soon as application.fxml gets loaded. This makes the UI responsive before filling it with the package details.
Fixes #473.
How to test

Start the launcher normally.
Observe the package selected by default. Do not select another!
If it's not installed, Download button is shown and Delete button is disabled.
Otherwise, Start button is shown and Delete button is enabled.
Now install or remove the package and restart the launcher.
Check if the condition in step 3 is still satisfied.

For example, when Terasology-2291 is installed, it should look like:

And when not installed, it should look like:

Hooray Jenkins reported success with all tests good!


Using exec to launch consul-template, in order to take PID 1.

This tiny modification makes consul-template takes PID 1 over the initial bash process, which allow a better signal management (docker stop/kill will be forwarded to consul-template wich will andle it nicely and stop the "runner" - aka haproxy).
Without this, the docker stop signal (SIGTERM) is not forwarded to consul-template by bash, and the process is killed (SIGKILL) by docker after 10 seconds (default timeout), which is not really clean.

@eesprit I've checked your changes locally (with updates towards master) and it looks ok. @stevendborrelli 👍

@eesprit @stevendborrelli Change is present in master so there's no need for this PR anymore.


Warning in the console

I have this kind of warning:
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0

And the build don't works with OpenJDK 1.9 (9.0)

And the build don't works with OpenJDK 1.9 (9.0)

You might want to create a separate issue for that.

For me it's the same issue because it seam that the warning becomes an error ...

Ok, I see. I guess we have to update the Gradle scripts and update some of our build files:
https://github.com/mapfish/mapfish-print/search?utf8=✓&q=512M

+1 :-)

I guess this is not an issue anymore. I cannot find MaxPermSize anywhere

Thanks :-)


getAll() returns empty array

Contacts.getAll((err, contacts) => {
      if(err === 'denied'){
          alert("getAll denied")
       }
       else {
                alert (JSON.stringify(Contacts));    // alerts {"myProp":"Hello"};
        }
 })

output - {} (empty array)
there are contacts in andoid phone

this is very confusing. you have contacts and Contacts mismatching case.
And having contacts value be {"myProp":"Hello"} is impossible, it must be you testing things out.
Please review your code.

contacts retrieved after changing Contacts to contacts in alert


⚠ Bofrost.at has degraded performance

In 8607c54, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1597 ms

Resolved: Bofrost.at performance has improved in fbdb931.


Invalid model export for flat cubes

If cube is flatten into a plane (which is common in Minecraft models), the exported model often doesn't look as it should. It's probably related to the code that detects the rotation of the cube.

Fixed with commit 1c63818fca72dba9cbc25cdb7ff64909062914e7


add helpers for algebra type aliases and values

Change-Id: I910bef70b98f249bf26d8b43968da431615fb8d3

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (I5ec06fbe2c5353c05b68d99a9a523015f9e54c8b@29399ae). Learn more about missing BASE report.

Additional details and impacted files
@@                             Coverage Diff                              @@
##             I5ec06fbe2c5353c05b68d99a9a523015f9e54c8b      #52   +/-   ##
============================================================================
  Coverage                                             ?   97.67%
============================================================================
  Files                                                ?       19
  Lines                                                ?      172
  Branches                                             ?        4
============================================================================
  Hits                                                 ?      168
  Misses                                               ?        0
  Partials                                             ?        4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.