LGC2 screen randomly turns on.

I recently updated to v1.8 from v1.7.
But during the middle of the night I noticed the screen came out of stand-by on it's own and was displaying the built-in screen saver images that auto activates when there is no detected input.
This happened two nights in a row, so I uninstalled v1.8 and went back to v1.7 and it has not happened since.
A bug maybe?

Hi, no I just manually switch between inputs as required.
But I can certainly install v1.8 again and enable logging, no problem. 👍

I recently updated to v1.8 from v1.7.
But during the middle of the night I noticed the screen came out of stand-by on it's own and was displaying the built-in screen saver images that auto activates when there is no detected input.
This happened two nights in a row, so I uninstalled v1.8 and went back to v1.7 and it has not happened since.
A bug maybe?

Hi there.  Thank you @JPersson77 for this great software.   Unfortunately I am seeing this issue also.  There have been no changes that I'm aware of outside of some LG automatic updates in the last few days.
I am a new user with v1.8 so I'm unable to compare behaviors with 1.7 however my LG C2 is constantly turning itself on in the last few days.    EG  I turn off the TV & shut my PC down and the TV will turn back on.
I've enabled logging in case it can help.
Thanks!

Hi - I was having a similar issue but after enabling logging I found my TV had changed IP addresses.  Unsure if this helps.
Thanks!

@ryanmoses thanks too!
@P00NtANG any feedback wrt this issue?

I have seen this twice in the last 2 days, found the TV on with no signal input and playing the built-in images

Hi @hsuanguo can you please enable logging and see if you can capture the issue so I can have a look. Not sure from your or @P00NtANG s description if the PC was on at the time etc.

Hi @hsuanguo can you please enable logging and see if you can capture the issue so I can have a look. Not sure from your or @P00NtANG s description if the PC was on at the time etc.

Sure, I'll enable it and if it captures the failure again I'll update it here.

@ryanmoses thanks too!
@P00NtANG any feedback wrt this issue?

Hi @JPersson77
Sorry for the delay - I have been meaning to get back to you.
I still have some odd behavior where the TV will power off or on unexpectedly but I feel like it's a problem with windows 11 monitor topology rather than LG TV companion.
 OLED was the primary display. However turning off the other monitors caused my OLED to shut down also.  Windows was pretty confused about the monitor situation when I tried to turn it back on  (main display switched several times and swapped to the wrong monitor).
I've got logging switched on and I think this is the log of the issue I describe above.  Note I did not change my monitor topology at all during this time.
The last entry in the log is PC shutdown.
Tue 21:12:57 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:12:57 > IPC, windows monitor topology was changed.
Tue 21:12:57 > Device1, spawning DisplayPowerOnThread().
Tue 21:12:57 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:12:57 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:12:57 > Device1, established contact: Display is ON.
Tue 21:12:58 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:12:58 > IPC, windows monitor topology was changed.
Tue 21:12:58 > Device1, spawning DisplayPowerOnThread().
Tue 21:12:58 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:12:58 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:12:58 > Device1, established contact: Display is ON.
Tue 21:12:59 > Device1, repeating WOL broadcast ended
Tue 21:13:00 > Device1, repeating WOL broadcast ended
Tue 21:34:28 > IPC, windows monitor topology was changed.
Tue 21:34:28 > Device1, spawning DisplayPowerOffThread().
Tue 21:34:28 > Device1, established contact: Device is OFF.
Tue 21:34:29 > IPC, windows monitor topology was changed.
Tue 21:34:29 > Device1, spawning DisplayPowerOffThread().
Tue 21:34:29 > Device1, established contact: Device is OFF.
Tue 21:34:52 > IPC, windows monitor topology was changed.
Tue 21:34:52 > Device1, spawning DisplayPowerOffThread().
Tue 21:34:52 > Device1, established contact: Device is OFF.
Tue 21:35:09 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:35:09 > IPC, windows monitor topology was changed.
Tue 21:35:09 > Device1, spawning DisplayPowerOnThread().
Tue 21:35:09 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:35:09 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:35:10 > Device1, established contact: Display is ON.
Tue 21:35:11 > Device1, repeating WOL broadcast ended
Tue 21:35:17 > IPC, windows monitor topology was changed.
Tue 21:35:17 > Device1, spawning DisplayPowerOffThread().
Tue 21:35:17 > Device1, established contact: Device is OFF.
Tue 21:35:18 > IPC, windows monitor topology was changed.
Tue 21:35:18 > Device1, spawning DisplayPowerOffThread().
Tue 21:35:18 > Device1, established contact: Device is OFF.
Tue 21:35:20 > IPC, windows monitor topology was changed.
Tue 21:35:20 > Device1, spawning DisplayPowerOffThread().
Tue 21:35:20 > Device1, established contact: Device is OFF.
Tue 21:35:21 > IPC, windows monitor topology was changed.
Tue 21:35:21 > Device1, spawning DisplayPowerOffThread().
Tue 21:35:21 > Device1, established contact: Device is OFF.
Tue 21:35:23 > IPC, windows monitor topology was changed.
Tue 21:35:23 > Device1, spawning DisplayPowerOffThread().
Tue 21:35:23 > Device1, established contact: Device is OFF.
Tue 21:35:31 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:35:31 > IPC, windows monitor topology was changed.
Tue 21:35:31 > Device1, spawning DisplayPowerOnThread().
Tue 21:35:31 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:35:31 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:35:31 > Device1, established contact: Display is ON.
Tue 21:35:33 > Device1, repeating WOL broadcast ended
Tue 21:35:42 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:35:42 > IPC, windows monitor topology was changed.
Tue 21:35:42 > Device1, spawning DisplayPowerOnThread().
Tue 21:35:42 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:35:42 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:35:42 > Device1, established contact: Display is ON.
Tue 21:35:44 > Device1, repeating WOL broadcast ended
Tue 21:35:51 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:35:51 > IPC, windows monitor topology was changed.
Tue 21:35:51 > Device1, spawning DisplayPowerOnThread().
Tue 21:35:51 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:35:51 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:35:51 > Device1, established contact: Display is ON.
Tue 21:35:53 > Device1, repeating WOL broadcast ended
Tue 21:36:00 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:36:00 > IPC, windows monitor topology was changed.
Tue 21:36:00 > Device1, spawning DisplayPowerOnThread().
Tue 21:36:00 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:36:00 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:36:00 > Device1, established contact: Display is ON.
Tue 21:36:02 > Device1, repeating WOL broadcast ended
Tue 21:36:09 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:36:09 > IPC, windows monitor topology was changed.
Tue 21:36:09 > Device1, spawning DisplayPowerOnThread().
Tue 21:36:09 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:36:09 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:36:09 > Device1, established contact: Display is ON.
Tue 21:36:11 > Device1, repeating WOL broadcast ended
Tue 21:36:18 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:36:18 > IPC, windows monitor topology was changed.
Tue 21:36:18 > Device1, spawning DisplayPowerOnThread().
Tue 21:36:18 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:36:18 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:36:18 > Device1, established contact: Display is ON.
Tue 21:36:19 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:36:19 > IPC, windows monitor topology was changed.
Tue 21:36:19 > Device1, spawning DisplayPowerOnThread().
Tue 21:36:19 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 21:36:19 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 21:36:19 > Device1, established contact: Display is ON.
Tue 21:36:20 > Device1, repeating WOL broadcast ended
Tue 21:36:21 > Device1, repeating WOL broadcast ended
Tue 22:24:47 > IPC, Device1 - enabled in windows monitor topology.
Tue 22:24:47 > IPC, windows monitor topology was changed.
Tue 22:24:47 > Device1, spawning DisplayPowerOnThread().
Tue 22:24:47 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 22:24:47 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 22:24:47 > Device1, established contact: Display is ON.
Tue 22:24:49 > Device1, repeating WOL broadcast ended
Tue 22:24:52 > IPC, Device1 - enabled in windows monitor topology.
Tue 22:24:52 > IPC, windows monitor topology was changed.
Tue 22:24:52 > Device1, spawning DisplayPowerOnThread().
Tue 22:24:52 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 22:24:52 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 22:24:52 > Device1, established contact: Display is ON.
Tue 22:24:54 > Device1, repeating WOL broadcast ended
Tue 22:26:50 > IPC, Device1 - enabled in windows monitor topology.
Tue 22:26:50 > IPC, windows monitor topology was changed.
Tue 22:26:50 > Device1, spawning DisplayPowerOnThread().
Tue 22:26:50 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 22:26:50 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 22:26:50 > Device1, established contact: Display is ON.
Tue 22:26:51 > IPC, Device1 - enabled in windows monitor topology.
Tue 22:26:51 > IPC, windows monitor topology was changed.
Tue 22:26:51 > Device1, spawning DisplayPowerOnThread().
Tue 22:26:51 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 22:26:51 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 22:26:51 > Device1, established contact: Display is ON.
Tue 22:26:52 > Device1, repeating WOL broadcast ended
Tue 22:26:53 > Device1, repeating WOL broadcast ended
Tue 23:32:07 > IPC, Device1 - enabled in windows monitor topology.
Tue 23:32:07 > IPC, windows monitor topology was changed.
Tue 23:32:07 > Device1, spawning DisplayPowerOnThread().
Tue 23:32:07 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 23:32:07 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 23:32:07 > Device1, established contact: Display is ON.
Tue 23:32:09 > Device1, repeating WOL broadcast ended
Tue 23:32:12 > IPC, Device1 - enabled in windows monitor topology.
Tue 23:32:12 > IPC, windows monitor topology was changed.
Tue 23:32:12 > Device1, spawning DisplayPowerOnThread().
Tue 23:32:12 > Device1, repeating WOL broadcast started to MAC: 80:5B:65:7D:E3:FA using IP address: <IP_ADDRESS>
Tue 23:32:12 > GetBestRoute2() selected interface index 13 LUID<PHONE_NUMBER>518336 route protocol 2
Tue 23:32:12 > Device1, established contact: Display is ON.
Tue 23:32:14 > Device1, repeating WOL broadcast ended
Tue 23:52:10 > Event subscription callback: system shut down detected.
Tue 23:52:18 > ** System is shutting down.
Tue 23:52:18 > Device1, spawning DisplayPowerOffThread().
Tue 23:52:18 > Device1, established contact: Device is OFF.
Tue 23:52:18 > The service terminated.

Hi @ryanmoses, I'm not sure this is the same issue as @P00NtANG  reports (need more info there) but let's assume it might be. Since I don't have the beginning of your log I will assume there is only one WebOS-device/OLED, Device1.
Your log looks quite normal in the sense that the app does what it is supposed to. So a couple of questions:

I notice that at some points the topology seem to change in very rapid succession, two events within a second. Not sure why but maybe you recognise this and can explain what happened there? The app and display seem to be processing it fine though
can you try and verify that the actual topology as set in windows is what is actually being logged? I e whenever the OLED is set to enabled in the windows options you should see two lines like this in the log:

Tue 21:12:57 > IPC, Device1 - enabled in windows monitor topology.
Tue 21:12:57 > IPC, windows monitor topology was changed.

and then when the OLED is set as inactive in the topology there should be only this message in the log:
Tue 21:34:28 > IPC, windows monitor topology was changed.
In other words, what we must ultimately try to determine is if any of the above events in your log noted as 'IPC, windows monitor topology was changed' are erroneous. So that even though there was not an actual change in the windows topology the app still received a windows message that the topology was changed. I mean that your error could potentially pop up, if the app is registering events which are not truly user initiated. So please help me more to get a grip on the issue :)

Oh, and also. Are you using a 2022 model OLED, C2, G2 etc or an earlier model? Do you have "Always Ready" enabled if so?

Oh, and also. Are you using a 2022 model OLED, (C2, G2 etc) or an earlier model? Do you have "Always Ready" enabled if so?

Hi @JPersson77 - Thanks for your reply.
I am using a 2022 LG C2 and "always ready" is currently disabled.  I have tried with this both enabled/disabled.  And yes there is only Device1.
I spotted those frequent topoIogy changes in the log as well but note I didn't change the topology at all during that time.
And as mentioned I'm getting the feeling my windows 11 installation is pretty confused about the topology and it may not be anything to do with LG TV companion.     It's an upgrade of an old Windows 10 installation and likely has a few cobwebs.
I think if you don't spot any smoking guns in the log it may be best to leave this with me.   I will reinstall windows at some point and connect my TV via cable rather than WIfi - Presumably things will settle down after that and if not I can get in touch with you again.

Hi, I'm surprised it works at all without "Always Ready" enabled. I've noted it as requirement for using this feature as my testing indicated that the nVidia control panel could not properly enable the OLED display otherwise.
Anyway, yes I think there might be an issue here since you have logged received windows messages indicating topology changes even though you did not actually change the topology. I'll think about it a bit more :)

Hi, I'm surprised it works at all without "Always Ready" enabled. I've noted it as requirement for using this feature as my testing indicated that the nVidia control panel could not properly enable the OLED display otherwise.
Anyway, yes I think there might be an issue here since the app have logged received windows messages indicating topology changes even though you did not actually change the topology. I'll think about it a bit more :)

I am using C2 2022 and can confirm my "Always Ready" is disabled as well, and LGTV Companion works just fine most of the time, just experienced 2 times that TV was not off so far...

That's interesting. are you using an AMD or Intel GPU possibly? Can you also confirm you have the "windows topology" feature enabled, well just for clarity?

PS I created a discord server if you care to have a more direct discussion on the potential issue  https://discord.gg/7KkTPrP3fq

There is a development build v1.8.5 available on discord. This is a bugfix build with some changes to the power on/off logic that may resolve some issues noted in this thread. If you download and install this build please provide feedback on any observed changes in ability to keep power state between PC and display in sync and the specific fixes noted below.

bugfix for reported issues with random power on/off potentially related to wm_displaychange message handling in the v1.8 topology feature
made clear that change of GPU and / or adding displays may invalidate the topology configuration.
Implemented detection for invalidated topology configuration which will show windows notification and log message urging user to reconfigure.
added mechanism for identifying invalid pairing keys
more help texts was added to all configuration options in the UI

https://discord.gg/7KkTPrP3fq

I just saw the built-in screen saver again (13:59)
Sat 10:18:24 > ** System requests displays OFF.
Sat 10:18:24 > Device1, spawning DisplayPowerOffThread().
Sat 10:18:24 > Device1, HDMI4 input active.
Sat 10:18:24 > Device1, established contact: Device is OFF.
Sat 10:43:58 > ** System requests displays ON.
Sat 10:43:58 > Device1, spawning DisplayPowerOnThread().
Sat 10:43:58 > Device1, repeating WOL broadcast started to MAC: ******************** using IP address: *********
Sat 10:43:58 > GetBestRoute2() selected interface index 28 LUID ********************** route protocol 2
Sat 10:44:00 > GetBestRoute2() selected interface index 28 LUID ********************** route protocol 2
Sat 10:44:01 > Device1, established contact: Display is ON.
Sat 10:44:02 > Device1, repeating WOL broadcast ended

But there is no logging information at all, the last one was 3 hours ago().
By the way, I am using nvidia GPU, what is windows topology feature? I don't see in the UI?

Hi @hsuanguo
If there is nothing in the log for what happened at 13.59 I doubt the issue you are seeing have to do with the app.
But can you clarify please so I understand. From your earlier note here I assume the PC was on at 13.59 and I also read that the PC was at this time idle and displays were off.  Then all of a sudden the display wakes up and since there is no output from the PC the built in screensaver is playing. Can you confirm this is the issue you are experiencing?
But if the excerpt of the log you pasted above is the last part of the log (I think that is what you write) I don't see that the app has turned off the screen when the PC became idle.
Consider if there is anything else waking the screen? Consoles or other devices using CEC? Another installation of lgtv companion on another computer which is configured to control this device? Cat stepping on remote? :)
The topology feature is new in version 1.8.0. It's not specific to any brand of GPU. The option can be found in the general options at the bottom. Previous versions only synced power state of all displays with the power state of the PC. This new feaature additionally syncs enabled/disabled state in the monitor configuration with the display power state. I e so that if you have multiple monitors connected to your PC and then disable an OLED in your monitor configuration the corresponding OLED device will now also power off. So that the OLED behave like a PC-monitor in this respect too.

Hi @JPersson77
Yes, the PC was idle and there was no display output from the PC, I am not sure if the screen ever went off then woke up, what happened was, I left my pc for a while, when I came back to it, I saw the TV is on with built-in screen saver.
I have no other device that controls the TV, neither did I(nor anything, anyone) use the remote.
Then I moved the mouse, then the pc woke up, worked as usual.

Log.txt
config.json.txt
Thank you very much, really appreciate on your quick response.
Please find the uploaded file above.
It just happened again(20:00) I guess, the TV was off just now, but I can't wake it up from PC, instead I have to use the remote.
I suppose it went to screen saver first, then turned itself off after a period. Again, there is no log in the log file.
I do see LGTVsvc.exe is running, and I can control manually with test function.
PC is desktop, GPU is RTX 3090. Windows 11 21H2, pc is configured to turn screen off after 10 minutes, no sleep at all.
Hope those information helps.

I have installed 1.8.5 I'll let you guys know if it makes differences

Thanks, looking at the log I see nothing that  immediately stands out.
But I do notice that at the times you noted the issue, 13.59 and 20.00, the log shows several hours of system being in the ON-state. I assume this means that you were mostly using the PC and the 10 minutes screen saver never kicked in.
So here's another thought. Can you have a look at what value you have set for the display auto power off, i e this setting: et Settings->General->OLED Care->Device Self-Care->Energy Saving->Auto Power off. I think there is a potential for seeing your issue if you have this option set to 2 hours for example.
So, hypothetically, what could happen is this: say you've been using the PC for close to two hours or something and just as you step out for a quick break the TV is automatically powering off itself. The app does not know this as windows does not know this. So this can lead to you coming back to screen that is powered off which you cannot wake with the mouse because windows beleives the screen is already on and does not send the "wake up"- message that the app operates on. There would also be nothing in the log, like what is observed. And here is an interesting thing - depending on other settings there is a fringe case in v1.8 and earlier where the app tell the screen to power off but it will instead cause it to wake up. So, again hypothetically, if your display powered off automatically on its own accord due to the above setting, then followed shortly thereafter by windows going into idle and shutting down display outputs the app would tell the display to shut down, but instead accidentally waking it up and thus showing the screen saver images you described.
If you have the displays' own auto-power off set to two hours consider increasing it to 8 hours or something and maybe consider using the idle detection of the app instead set to 5 minutes or something like that.
The issue about accidentally waking up the screen when it should be powered off was fixed in v1.8.5 by querying the TV for the status before issuing the command. Thus adding a small roundtrip delay depending on the LAN to the power off which I hope should not matter.
Let me know how it goes

It just happened again with 1.8.5, so must be something with my system configuration. Do you know if there is a way that I can check the system log if there was a screen off event?
I do have the TV auto power off set to 4 hours, but I am pretty sure this is not the case because this time I just used the remote 20 mins ago(and switched back to PC screen) before I saw the screen saver again.......

Hi, ok I thought we had nailed it :)
One thing though, I suspect the auto power off will power off your TV after 4 hours irrespective of whether you have used the remote or not. So maybe not discount it yet. However with the fix in v1.8.5 I would expect the display to be off but not possible to wake with the mouse if the theory was correct.
Interesting question about the system log (event log). This tool will show you when PC started/went to sleep: https://www.nirsoft.net/utils/computer_turned_on_times.html . I don't think however there is a straightforward way of reading display on/off event in the the event log. I just now used this tool https://www.nirsoft.net/utils/full_event_log_view.html which presents event log items flattened so it's easy to see/filter/search what events occured at a specific time. Maybe you can find something? The closest I can see  from a brief look is that message 1660 and 1661 related to windows audio seem to occur in parallell with display on/off (on this system)

Hi @hsuanguo any feedback wrt the above? Still the same?

OK thanks for feedback and pointing out the screensaver. I will try to see if I can replicate

OK thanks for feedback and pointing out the screensaver. I will try to see if I can replicate

OK, I think now I have a better understanding on what happned:

Windows settings:  screen saver on (1min), screen off (10 mins)

Procedure:

First, windows will trigger screen saver after 1min afk.
Then, a few minutes later(< 10min), GPU will stop ouput signal, from the TV, it will detect no signal input, so TV built-in screen saver will start. I don't really no if this is expected windows behaviour, but I am not aware of any settings regarding this.
If I wait a bit longer the TV will be turned off and I can see > ** System requests displays OFF. in logger.

So I think from LGTVCompanion side, everything works just fine as it should be.
Sorry for all the confusions,  and thanks for all the help and sugguestions you provided!

Thanks for helping out too!
I think that is an unexpected behavior you have observed! I would expect GPU to cut signal as a result of OS requesting it to, so a bit surprising that it would do that <10mins. Not sure why and I cannot recreate at the moment on my system. nor does google give me any more info. I think build 1.8.5 and later will help somewhat with the issue since it will avoid potentially powering on the screen inadvertently.
If you should come to think of anything more related to this please let me know

Closing this issue since there was no potential fix to the app identified (apart from what was implemented in v1.8.5). Feel free to reopen if you should come to think of anything more related to this


Repr for Recipe and Step

We used to have nicer custom reprs for each Step and Recipe, but these were dropped in the refactor. Now that we're going for scikit-learn compatibility, it would be nice if our repr would match their conventions. We could accomplish this by subclassing Recipe from BaseEstimator, but currently we don't have sklearn as a required dependency (since we want to support non-sklearn workflows as well too). My guess is there's a way we can have a repr that follows sklearn's conventions here without relying on sklearn itself for an implementation.

Goal
How does sklearn represent subpipelines? We should basically use the same representation for a recipe.
>>> from sklearn.feature_selection import SelectKBest
>>> from sklearn.pipeline import Pipeline
>>> from sklearn.svm import SVC
>>> import ibis_ml as ml
>>>
>>> imputer = ml.ImputeMean(ml.numeric())
>>> scaler = ml.ScaleStandard(ml.numeric())
>>> rec = ml.Recipe(imputer, scaler)
>>> pipe = Pipeline([("rec", rec), ("svc", SVC())])
>>> pipe
Pipeline(steps=[('rec', <ibis_ml.core.Recipe object at 0x164f28df0>),
                ('svc', SVC())])
>>> subpipe = Pipeline(steps=[('select', SelectKBest(k=2)), ("svc", SVC())])
>>> pipe = Pipeline([("rec", rec), ("sub", subpipe)])
>>> pipe
Pipeline(steps=[('rec', <ibis_ml.core.Recipe object at 0x164f28df0>),
                ('sub',
                 Pipeline(steps=[('select', SelectKBest(k=2)),
                                 ('svc', SVC())]))])

Considerations:

We will probably need to give steps a name.
_EstimatorPrettyPrinter IS NOT straightforward: https://github.com/scikit-learn/scikit-learn/blob/main/sklearn/utils/_pprint.py#L116


Add other examples

Hi! I used to keep a YouTube playlist with videos related to Cylc (will search for that), and also some bookmarks. I'll search for that later, but I searched some that I remembered. Maybe some of these would be interesting for this list?

eWaterCycle (interesting that they have CWL and Cylc, although I think it was Cylc executing CWL workflows): https://blog.esciencecenter.nl/fairifying-ewatercycle-8a61cf93b81c?gi=e0614a00fb4f & https://github.com/eWaterCycle/ewatercycle-forecast
Commercial solution with Cylc & PBS by Altair - https://www.altair.com.es/newsroom/articles/cylc-altairs-pbs-professional-power-weather-modeling-at-australias-bureau-of-meteorology/
Some model optimisation with Cylc https://gmd.copernicus.org/articles/11/2153/2018/

And found this one now while searching for the ewatercycle (couldn't recall the name of the project, only that it was dutch and hydrology-related): https://www.waternz.org.nz/Article?Action=View&Article_id=2699

Ha! Found the playlist. I haven't updated it in a while, so there might be more interesting material out there :+1:
https://www.youtube.com/playlist?list=PLxlfTM52ynRZZ7rtLkoKANWiIFn92d6je

More about Altair's PBS + Cylc "Weather Solution":

https://altair.com/weather-climate
https://web.altair.com/en/cylc-weather-solution


Create lauder.txt

It's a school in Hungary. https://www.lauder.hu/wp/

@NumerX Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


SFTP support

Hi. It would be great to see SFTP support in Files UWP.
Currently, there is only three options to use SFTP in Windows:

WinSCP - an old app that is not very comfortable to use. (there is also MobaXterm, but it just works even slower)
Apps that create a virtual network drive. As they integrate with Windows Explorer, this is not a bad option, but path that Explorer uses is not Unix-style, so you can't just copy path to some file and paste it in terminal. (for ex. Z:\etc\nginx instead of /etc/nginx)
Total Commander and Far Manager SFTP plugins (which is not modern and more for old-school users)

Files UWP can take it advantages and get users who are looking for a modern SFTP client on Windows.
I've seen SFTP packages on nuget, so it might not be that difficult to implement

Merging with #1342.


exponential performance degradation with repeat-count

https://github.com/kobotoolbox/enketo-express/issues/806
Looks like DOM searches cause this and should be avoidable.

Also look into whether the presence of a (slow) geowidget in the repeat has anything to do with this.

Two main culprits:
a. $clone.trigger( 'addrepeat', [ repeatIndex, byCountUpdate ] ) and what handles this event
b. geo widget

Didn't find a quick win (or anything that is clearly wrong)


Deployment Microsoft Azure - Move data storage docs from ACI to "Microsoft Azure"

Summary
Move documentation how to store Kong metadata in Microsoft Azure from "Running Kong on Azure Container Instances" to "Microsoft Azure".
Relates to #1045

Checklist:

[X] Documentation
[X] Spellchecked my updates
[x] Ready to be merged

Looks like we'll need to add a logo for Bitnami and the formatting is broken:
https://deploy-preview-1049--inspiring-goldwasser-3966ac.netlify.com/hub/bitnami/microsoft_azure/
Will have a look after holidays.

I've updated some URLs and made some minor corrections. LMK what you think @tomkerkhove thanks

:shipit:

Awesome, thanks guys!


Issue connecting awsIotClient

Hello,
I am getting bellow error while connecting client.

Code:
String clientEndpoint = "a2b6lf8kaverg8-ats.iot.us-west-2.amazonaws.com";
String clientId = "A1234567890BCDEFG";
String certificateFile = "/MQTT/Certificates/6e21837395-certificate.pem.crt";
String privateKeyFile = "/MQTT/Certificates/6e21837395-private.pem.key";
if (awsIotClient == null && certificateFile != null && privateKeyFile != null) {
String algorithm = "RSA";
Util.SampleUtil.KeyStorePasswordPair pair = Util.SampleUtil.getKeyStorePasswordPair(certificateFile, privateKeyFile, algorithm);
awsIotClient = new AWSIotMqttClient(clientEndpoint, clientId, pair.keyStore, pair.keyPassword);
try {
awsIotClient.connect();
System.out.println("Connection Successful!");
} catch (AWSIotException e) {
e.printStackTrace();
}

I have not added any client from AWS Console. Rather this code is acting as client to connect to aws IOT.

Created certificate, but no policy. Not sure, do i require to create it or its okay to be without policy.

Error:
Nov 27, 2018 1:15:23 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
Connection lost (32109) - java.io.EOFException
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:146)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:267)
at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:65)
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:107)
... 1 more
Nov 27, 2018 1:15:23 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Nov 27, 2018 1:15:23 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: A1234567890BCDEFG
Nov 27, 2018 1:15:26 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried

I had a lot of issue with this also.
This is my working code maybe it might help.
String certificateFile = "certificate.pem.crt";
String privateKeyFile = "private.pem.key";
SampleUtil.KeyStorePasswordPair keyStorePair = SampleUtil.getKeyStorePasswordPair(certificateFile, privateKeyFile);
AWSIotMqttClient client = new AWSIotMqttClient(clientEndpoint, clientId, keyStorePair.keyStore, keyStorePair.keyPassword);


Knowledge transfer of Tableau

Knowledge transfer for tableau part to be given to Darshana

@niharikaavasthi and @Xu221b help in understanding tableau processes

Done


Docker push using remote api result 'is already in progress"

I have tag a image to local registry:
docker tag 590fa59c6dc3 <IP_ADDRESS>:80/jhzhang-test
Then i using docker remote API to push the image (api version: v1.11),

First time, it return after about several seconds, response is null.
Try push again, this time response is:

HTTP/1.1 500 Internal Server Error Content-Type: text/plain; charset=utf-8 Date: Fri, 01 Aug 2014 08:47:53 GMT Content-Length: 57 push <IP_ADDRESS>:80/jhzhang-test is already in progress

Try again after a while, result is:

HTTP/1.1 200 OK Content-Type: application/json Date: Fri, 01 Aug 2014 08:54:06 GMT Transfer-Encoding: chunked {"status":"The push refers to a repository [<IP_ADDRESS>:80/jhzhang-test] (len: 1)"} {"status":"Sending image list"} {"status":"Pushing repository <IP_ADDRESS>:80/jhzhang-test (1 tags)"} {"status":"Image 511136ea3c5a already pushed, skipping"} {"status":"Image b74728ce6435 already pushed, skipping"} {"status":"Image 3aa646e4f1d2 already pushed, skipping"} {"status":"Image 3460b1ba3f7d already pushed, skipping"} {"status":"Image 3933d6efb2a6 already pushed, skipping"} {"status":"Image e3288b42529a already pushed, skipping"} {"status":"Image c499ff5e8c87 already pushed, skipping"} {"status":"Image c529b1552e5a already pushed, skipping"} {"status":"Image d61b194a01f5 already pushed, skipping"} {"status":"Image 641283160ec4 already pushed, skipping"} {"status":"Image 42f3351dd9a3 already pushed, skipping"} {"status":"Image 95fea9b65ee9 already pushed, skipping"} {"status":"Image 976600925f6e already pushed, skipping"} {"status":"Image 9080f765ea3d already pushed, skipping"} {"status":"Image caf00af1e6bd already pushed, skipping"} {"status":"Image 590fa59c6dc3 already pushed, skipping"} {"status":"Pushing tag for rev [590fa59c6dc3] on {http://<IP_ADDRESS>:80/v1/repositories/jhzhang-test/tags/latest}"}

closing as failure to give more info but please ping me if you come back with the requested information


Vim9: can't use heredoc in nested functions

The following code doesn't compile:
def F(): string
    def G(): string
        perl <<EOF
        print "";
EOF
    return ''
    enddef
    return G()
enddef
defcompile

vim complains "missing heredoc end marker: EOF<00>".
What's more, for similar code:
def F(): string
    def G(): string
        perl <<EOF
EOF
    return ''
    enddef
    return G()
enddef
defcompile

vim complains "missing heredoc end marker: EOF<00>EOF".
vim version: 8.2.4922

Unrelated to the current issue, but I've noticed that the highlighting of the perl heredoc was wrong:

So, I fixed it in the vim9-syntax plugin:

Inside the g:vim9_syntax dictionary, the fenced_languages key must be assigned a list containing the 'perl' string.  For example:
vim9script
g:vim9_syntax = {
    builtin_functions: true,
    data_types: true,
    fenced_languages: ['perl'],
    errors: {
        event_wrong_case: true,
        octal_missing_o_prefix: true,
        range_missing_space: true,
        range_missing_specifier: true,
        strict_whitespace: true,
    }
}


add operation to transform Unix timestamp to UTC iso string

Can you include something in the spec so that the end user can specify a format string if they want non-ISO codes?


[TUTORIALS] Fixed minor typo in tutorial on low memory dropout

I'll merge this PR this time, but please note that minor typo related PRs are low priority.
From the contribution guide:

Please refrain from submitting low-effort pull requests (PR) -- such as minor formatting/typo fixes -- solely for the purpose of appearing in the commit history. Maintainers have limited bandwidth, and may decline to review such work.

@Jokeren Thanks! Sorry I hadn't read this guide, in hindsight I should've but this was such a minor thing that I just went straight to raise a PR and left. Will keep it in mind in the future 😄


load_and_construct(ed) object not triggering load after construction (Boost incompatibility)

During the migration of a project relying on boost::serialisation to cereal (thanks! it's making my liking life SO much easier) I noticed the following incompatibility between the two.
If you have some structure or classes that have a non-default constructor, when they are serialised they are correctly serialised, but when they are loaded_and_constructed they will not call the load method.  This behaviour is not documented anywhere.
I found an extremely ugly workaround: adding a new non-default constructor with an extra Archive& argument that performs everything the load function would do.
Boost::serialisation correctly calls load after having constructed the object.
#include <iostream>
#include <sstream>
#include <memory>

#include <cereal/access.hpp>
#include <cereal/archives/json.hpp>
#include <cereal/types/memory.hpp>

struct TextMessage {
  TextMessage(std::uint16_t length, std::uint16_t type)
    : length_{length}, type_{type} {
  }

  std::uint16_t length_;
  std::uint16_t type_;
  std::uint16_t extradata_;

  template<typename Archive>
  void save(Archive &ar) const {
    ar(length_, type_, extradata_);
  }

  template<typename Archive>
  void load(Archive &ar) {
    ar(extradata_);
  }

  template<typename Archive>
  static void load_and_construct(
      Archive &ar,
      cereal::construct<TextMessage> &construct) {
    std::uint16_t length;
    std::uint16_t type;

    ar(length, type);
    construct(length, type);
  }
};

int main() {
  std::stringstream ss;

  {
    cereal::JSONOutputArchive oarchive{ss};
    std::unique_ptr<TextMessage> kMessageToSerialize{
        new TextMessage{13, 1043}};

    kMessageToSerialize->extradata_ = 13456;

    oarchive(kMessageToSerialize);
    std::cout << "kMessageToSerialize->extradata_ = " << kMessageToSerialize->extradata_ << std::endl;
  }

  {
    cereal::JSONInputArchive iarchive{ss};
    std::unique_ptr<TextMessage> deserialized_message{nullptr};
    iarchive(deserialized_message);
    std::cout << "deserialized_message->extradata_ = " << deserialized_message->extradata_ << std::endl;
  }
  return 0;
}

I guess it should be made more explicit that load_and_construct effectively replaces load for types without a default constructor. It is not desired that you would be forcing a call to load afterwards. If this is the default behavior of boost in this situation we'll have to add a note to the transition guide.
The desired cereal way of doing things would be for our load_and_construct to look like:
  template<typename Archive>
  static void load_and_construct(
      Archive &ar,
      cereal::construct<TextMessage> &construct) {
    std::uint16_t length;
    std::uint16_t type;

    ar(length, type);
    construct(length, type);
    ar(construct.extradata_)
  }

See the doxygen on construct for more info.


[spaceship] get current build_number from AppVersion 🚀🤘

return build_number on AppVersion.
as supposed to be required here: https://github.com/fastlane/fastlane/issues/6770
if this one is merged - i ll add a custom action to retrieve the current build number.
adds method current_build_number to appVersion class.
e.g.:
app = Spaceship::Tunes::Application.find("krone.at-fivexfive")
[2] pry(main)> version = app.live_version.current_build_number
=> "7"
[3] pry(main)> version = app.edit_version.current_build_number
=> "14"

This looks great - I left one question 👍

Sweet, thanks! 🚀

my first spaceship PR ! feels good 💯  thx


Angle brackets in shortcodes break formatting

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!
I have the following shortcode:
              {
                name: "rimg",
                label: "Custom Image (rimg)",
                match: {
                  start: "{{<",
                  end: ">}}"
                },
                fields: [
                  {
                    name: "caption",
                    label: "caption",
                    type: "string",
                    ui: {
                      component: "textarea"
                    }
                  }
                ]
              },

If I type html into the value, E.g:
gregre

The value that is output is: {{< rimg href="d" caption="}} (note the missing end ". The value stops at >)
Reproduction
Ask James for private access if needed
Steps to reproduce

Use the shortcode above.
Add html to the shortcode value
Save
Check broken markdown in editor

System Info
System:
    OS: macOS 12.5.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 5.20 GB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.18.0 - ~/.nvm/versions/node/v16.18.0/bin/node
    Yarn: 1.22.19 - ~/Documents/forestry/smashing-magazine/node_modules/.bin/yarn
    npm: 9.1.2 - ~/.nvm/versions/node/v16.18.0/bin/npm
  Browsers:
    Chrome: 109.0.5414.87
    Firefox: 88.0.1
    Safari: 15.6.1
  npmPackages:
    @tinacms/auth: 1.0.2 => 1.0.2
    @tinacms/cli: use_db_status_to_check_client_info => 0.0.0-20230120125152
    tinacms: use_db_status_to_check_client_info => 0.0.0-20230120125152

Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug.

This is now handled with the markdown parser.


Fixes and improvements. [3]

Part 1. Language updates and additions.

Added some missed variables in "default" language. Update "en" and "ru" language.
Add "sitemap" link menu in "_config.yml".

Part 2. Descriptions in posts & pages.

Add meta descriptions on posts, if it was defined in post.md.
Add meta descriptions on pages, if it was defined in page.md.
Add titles on pages.

Usage:
example-post.md / example-page.md
---
title: About
description: Description about this site.
---

Descriptions on posts and pages will looks like that:

And like that:

It's important part of SEO and must be a vision on that parameter.
Titles on defined pages (tags, categories) looks like that:

Titles on custom pages (404, about) looks like that:

Part 3. Custom layout code.
As we know, theme Next allow to rewrite or add:

Custom css-styles (next/source/css/_custom/custom.styl).
Custom variables (next/source/css/_variables/custom.styl).

It's very good and important implementation for use your own individual blog style and make pulls/merges in global project throw git.
But 1 thing was wrong: before that time, u can't do your custom layout styles (div, span, counters, any scripts). So, i just added custom layout files in layout dir and u can add any html code there. And if file(s) will empty, code will not add.
Usage:
Simply add your html code in themes/next/layout/_custom/sidebar.swig, for example:
<div class="custom-code motion element" style="margin-top: 20px; padding-top: 18px; border-top: 1px dotted #ccc;">

<iframe id="ytplayer" type="text/html" width="215" height="auto" src="https://www.youtube.com/embed/A1Qb4zfurA8" frameborder="0"/>

</div>

In sidebar i use custom vision counter codes, like Yandex.
Custom layout files:

themes/next/layout/_custom/sidebar.swig
themes/next/layout/_custom/header.swig

Also, live demo is always on my site.

Great! Awesome enhancements~
Thanks @ivan-nginx

@iissnan actually, i need more time for remaking descriptions on posts, and i will do it some later.
And, yep, thank's u too for that great template. I was see that u working now for sticky block styles, called jeet, and this is really good and will make all blocks (specailly sidebar) fully responsive.


Authentik is not returning back to netbird when adding peers

I''m running a self hosting Netbird instance with Authentik as IDP backend. Traefik is running as reverse proxy with my own domain. I''m using Docker with the Traefik example file in this repo.
Ports in the self hosting guide are open in the Router.
Both are running at the same machine. The web interface is running fine now. However, i have problems when adding peers.
Log-in with Authentik is working fine. After that, Authentik is returning back to an URL like https://authentik.mydomain.com/device?code=XXXXXX with a white page.
Because the web interface is working (adding DNS, routes etc.) i don't how to troubleshoot.
Running a docker container with a setup key will add the peer to the web interface, but it's not coming online. Also, the "last seen" field is not updated.
To Reproduce
Steps to reproduce the behavior:

Open a Netbird client like the android App
Change the Url to the correct server and log-in with Authentik
https://authentik.mydomain.com/device?code=XXXXXX) with a white page is shown.
The following error is shown in the Management container:
### 2023-07-05T16:22:51+02:00 WARN management/server/grpcserver.go:322: failed logging in peer R7Z6hJvUc6+dCLF3Y3U7rpfreXIwhPEqygmEPFrpEXs=

Expected behavior
A new page with Netbird must be shown to complete the steps.
NetBird status -d output:
If applicable, add the output of the netbird status -d command
Coming soon this afternoon!
Screenshots
Coming soon this Afternoon!
Additional context
Coming soon this afternoon!
I will upload the files needed like the compose file and logs this afternoon. I'm so close to getting Netbird running and I''m really excited  to fix this problem!
Thanks in advance so far.

@bcmmbaga This is similar to #1015.
@Akruidenberg can you share your authentik version for us to check the doc steps against it?

It seems that the issue you're experiencing is due to the lack of a default device auth flow configured in authentik. To resolve this, you can follow these steps:

Go to the authentik admin interface
-On the left menu, click on System and then select Tenants
If you haven't set a custom tenant, choose authentik-default and click the edit button
Scroll down toDefault flowsand update the Device code flow to use the default-authenticator-static-setup (default-authenticator-static-setup) flow
Click on Update, and then you can try the client login again with netbird.

Please let us know if this resolves the issue.

Sorry for my late reaction! Problem is fixed. Thank you for your support.


react-svg  android compatibility

When I build react-svg for android , it throws error. Do we have any alternative for android? Please help My code is below
import ReactSVG from 'react-svg';

@gitpayal looks like your code sample is incomplete, can you paste the rest please? What error are you seeing, can you attach some details of that too?

Thanks Tanem for the reply. Following are my app specifications :->
"react": "^15.4.1",
"react-native": "^0.42.3",
"react-svg": "^2.1.21"
I am using the below code for showing sag images as icon in my app 👍
import ReactSVG from 'react-svg';

This code works in safari iOS but gives error in android(v 7.0) application while building app.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mergeDebugResources'.

/home/payalverma/Projects/caro-mobile/android/app/src/main/res/drawable-mdpi/public_img_svgs_settings.svg: Error: The file name must end with .xml or .png

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

BUILD FAILED
Total time: 24.182 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html
let me know if you can help me with the same

Thanks for the info. As you said re building the app, this looks like an issue with your setup, but it's not something I'm familiar with.
At this stage it doesn't look like a ReactSVG issue to me, but running a quick google search throws up a few links that might help, for example this one on stack overflow.
I'll leave this issue open for now though in case you want to let me know how you got on, good luck :+1:

Closing this issue as it doesn't look related to this project.


Update for new pymt release

This PR includes a few minor changes to help pymt_roms work with the new pymt release, v1.3.2. This includes:

Updating meta/Roms/parameters.yaml to work with the latest model_metadata, v0.8.2.
Using miniforge in the test CI workflow. (This will eventually get updated in the babelizer.) Also running the workflow with Python 3.11.

@mdpiper Thanks very much for updating the pymt_roms!

@gantian127 Thank you for accepting my pull request!


Optimize build system and output file structures

Exported contents are now scoped all under the dist directory
vanilla section of the package can be used independently same as react one.

import { createStates, createMachine } from "timsy" // ✅ okay
import { createStates, createMachine } from "timsy/vanilla" // ✅ okay
import { useMachine } from "timsy" // ✅ okay
import { useMachine } from  from "timsy/vanilla" // ❌ not okay

Boost the build process via

Using esbuild
Turn off heavy source-map
Using concurrently for parallelization

Add MIT LICENSE based on package.json fields

Delete extra source map from the source code

NOTE: they will remain on the git history

fix typos
eliminate package side effects in the production

Altering JSON attributes in the final published package.

Preventing unwanted publish for the main package, allow publish only in dist dir

yarn build
cd dist
# If you need to double-check what will be in the final publish package
npx npm-packlist
# publish via np or npm itself
npm publish

This is AMAZING! 😄 Thanks so much for taking the time and effort! I only have a single change suggestion and that is to change vanilla to core. I guess this is a bit subjective, but in my experience core is a more common name for "the core functionality" of a utility 😄  Again, this is super nice! 👍

I'm a vanilla lover😅, but sure I will change that to core

vanilla has been changed to core

import { createStates, createMachine } from "timsy" // ✅ okay
import { createStates, createMachine } from "timsy/core" // ✅ okay
import { useMachine } from "timsy" // ✅ okay
import { useMachine } from  from "timsy/core" // ❌ not okay

husky-pre push has been set to executable


BUG: cwt_morlet decim

closes https://github.com/mne-tools/mne-python/issues/3187

Coverage decreased (-0.001%) to 90.819% when pulling 5fc4898c0b0a50445151de020093ea7c2f25386d on kingjr:bug_cwtmorlet_decim into 4bf30daf575bdaf3c6155ce552d171a5bf3b3e72 on mne-tools:master.

Coverage increased (+0.003%) to 90.822% when pulling c3746c9ac1ba83eb3ad1c2747fa86db9ee4cd146 on kingjr:bug_cwtmorlet_decim into 4bf30daf575bdaf3c6155ce552d171a5bf3b3e72 on mne-tools:master.

Coverage decreased (-0.006%) to 90.813% when pulling c3746c9ac1ba83eb3ad1c2747fa86db9ee4cd146 on kingjr:bug_cwtmorlet_decim into 4bf30daf575bdaf3c6155ce552d171a5bf3b3e72 on mne-tools:master.

Thanks @kingjr


Fix #222 : Migrate to sound null safety

Does it work with  null safe i am not used to Github .
its the only package left for to migrate is it safe to migrate without changing  this package to null safe

Does it work with null safe i am not used to Github .
its the only package left for to migrate is it safe to migrate without changing this package to null safe

Nope you have to use null safety package
in you pubspec.yaml use it like this :
flutter_datetime_picker:
  git:
    url: https://github.com/figengungor/flutter_datetime_picker.git

Does it work with null safe i am not used to Github .
its the only package left for to migrate is it safe to migrate without changing this package to null safe

Nope you have to use null safety package
in you pubspec.yaml use it like this :
  flutter_datetime_picker:
    git:
      url: https://github.com/figengungor/flutter_datetime_picker.git

Thank you sir

When I try to "Cancel" or pressing outside the Date/Time picker bottom sheet it will cause an exception error.
I think "?" should be added to return types so it will not cause the said error:
// original code from flutter_datetime_picker.dart
static Future<DateTime> showDatePicker(
static Future<DateTime> showTimePicker(

// with changes
static Future<DateTime?> showDatePicker(
static Future<DateTime?> showTimePicker(

Thanks @kalmigs. Fixed it.


Remove exception stacktraces from unit tests (oracle#466)

Specify surefire and failsafe redirectTestOutputToFile=true configuration properties in top-level parent pom.xml to suppress unit test exceptions

@tomas-langer Are you okay with this change ? @barchetta FYI

If we keep the -e switch, this may be sufficient solution. Let's try it and if it hinders troubleshooting, we would have to come back and do the hard work (e.g. removing stacktraces that are expected).


Support Scrolling within Floating Overlay

Hi - thanks for building a great widget. Are you still supporting this?
I am building for flutter web app - and the floating overlay uses the Positioned widget which means that a scrollable widget as a child does not scroll unless all the constructors for the positioned widget are set.
https://stackoverflow.com/questions/59936098/listview-not-scrolling-in-positioned-widget
I have forked the repo and updated the _Reposition class to set the right and bottom properties of the Positioned constructor to 0 (see below) - although this means that the overlay cannot be scaled from the right or bottom anymore.
  @override
  Widget build(BuildContext context) {
    return StreamBuilder<Offset>(
      initialData: offsetController.state,
      stream: offsetController.stream,
      builder: (context, snapshot) {
        final position = snapshot.data!;
        return Positioned(
          top: position.dy,
          left: position.dx,
          bottom: 0,
          right: 0,
          child: child,
        );
      },
    );
  }

Any suggestions for how to set the right and bottom properties correctly in the _Reposition class so that the overlay will still scale from all 4 sides? I think the solution maybe to pass in the _Side.bottom and _Side.right from the get _entryProcesWidgets call in the floating_overlay_controller?
Many Thanks
Alistair

Hi! Thank you for the compliment! I'm still supporting this even with less time available.
I see why the gesture detectors would conflict if you tried to scroll inside the floating overlay. We could think of a flag inside the controller that would disable some or all of the gesture detection from the floating widget.
This way you could create a pin or some other button to indicate that the floating widget is fixed to that position/scale.
About what you did to solve that, I get the size from the widget after the first frame, maybe filling the width and height do the same as filling the bottom and right parameters? Since it could then internally create a Rect, I would have to test it anyways.
If you are willing to try and implement this, I would gladly accept a PR from your fork.

I found a solution! The issue was with the Overlay builder and the _Reposition object. I will submitt a PR tomorrow. Still need to fix getting the bottom right offset passed to the FloatingOverlayOffset.. but getting closer

Great work! Waiting for your PR!
About the rebuilding, that's something I'm trying to solve, I think it has something to do with getting the size of the child widget, but if you have any insight let me know!


Bounded type parameters are unbounded in generated code

interface Foo { }

@FreeBuilder
interface BuildableType<T extends Foo> {
    T getT();
    class Builder<T extends Foo> extends BuildableType_Builder<T> {}
}

Generates the following code:
@Generated("org.inferred.freebuilder.processor.CodeGenerator")
abstract class BuildableType_Builder<T> {
    ...
}

Even though the type parameter T in BuildableType is bounded, the type T in the generated code is unbounded. The generated builder does not work because the type argument T in the builder is not within the bounds of the type-variable T in BuildableType.

This should now be fixed in 1.10.3.


Module/discussion backend

Significant update

create shared store to replicate core functionality between modules more easily
refactor and build out discussion store
bind discussion store to list and create pages
modify discussion create page to better bind to editor as field value
create placeholder discussion view page and bind to store
add basic functionality to handle post comments

Apologies in advance, a lot of work required to build discussions back-end in a sensible way and integrate for testing into existing templates. But should have most desired functionality

Ok, stopping adding commits now (!)


volume metadata got reset - while trying to mount same volume from another docker host (was attached to volume earlier from docker host1)

container got detached  volume metadata got reset (was attached to volume earlier from docker host1) while trying to mount same volume from another docker host.
We are not able to attach the container to the same volume again. After restarting the docker service this problem is no longer reproducible.
Testcase steps:
1. VM1: create volume abc1> list volume > docker volume inspect abc1
2. VM2: list volume > docker volume inspect abc1
3. VM1: start container by mounting to abc1 > write some data > leave it attached/running
4. VM2: docker volume inspect abc1 (it should be in attached state)
5. ESX: make sure vmdkops_admin output is in sync with volume inspect
6. VM2: start container by mounting to abc1 > expect an error (docker: Error response from daemon: VolumeDriver.Mount: Failed to add disk 'scsi1:0'. disk /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/abc1.vmdk already attached to VM=422f7a41-10e5-0937-30ad-bd9bffa54565.)
7. VM2: docker volume inspect abc1 (make sure output stays the same as before)
8. ESX: make sure vmdkops_admin output is in sync with volume inspect
9. VM1: exit/detach container > docker volume inspect abc1
10. ESX: make sure vmdkops_admin output is in sync with volume inspect
11. VM2: docker volume inspect abc1
12. VM1/VM2: perform cleanup (rm container/volume)

Test is failing at step 7 and following are the observations
Observations:
1. attached container got detached when trying to attach from another docker host
2. Admin CLI fails to say whether volume is attached or not
3. docker volume inspect doesn't show following "status" information
"Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Fri Mar  3 22:20:16 2017",
            "created by VM": "vmFolderPhoton",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "detached"
        },

on VM2:
root@photon-xVmYMbyTn [ ~ ]# docker volume inspect abc1@sharedVmfs-0
[
    {
        "Name": "abc1@sharedVmfs-0",
        "Driver": "vsphere",
        "Mountpoint": "/mnt/vmdk/abc1@sharedVmfs-0",
        "Labels": {},
        "Scope": "global"
    }
]

On ESX:
[root@sc-rdops-vm10-dhcp-36-198:/vmfs/volumes/58b7316d-693a1616-8e5a-020015a5722b] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM   Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  --------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
abc1    sharedVmfs-0  vmFolderPhoton  Fri Mar  3 22:20:16 2017  detached                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent
abc     sharedVmfs-0  vmFldrRP        Fri Mar  3 22:35:43 2017  detached                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

[root@sc-rdops-vm10-dhcp-36-198:/vmfs/volumes/58b7316d-693a1616-8e5a-020015a5722b/dockvols/11111111-1111-1111-1111-111111111111] cat abc1-6de5a7cf7dec3c88.vmfd
{"status": "detached", "created": "Fri Mar  3 22:20:16 2017", "volOpts": {"diskformat": "thin", "fstype": "ext4"}, "attachedVMUuid": null, "created-by": "vmFolderPhoton"}

Test is failing at step 7 and following are the observations
Observations:

attached container got detached when trying to attach from another docker host
Admin CLI fails to say whether volume is attached or not
docker volume inspect doesn't show following "status" information

"Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Fri Mar  3 22:20:16 2017",
            "created by VM": "vmFolderPhoton",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "detached"
        },

@shuklanirdesh82 Can you please upload both plugin and vmdkops logs?

@shuklanirdesh82
Are you sure both VMs are on same ESX?

attached container got detached when trying to attach from another docker host

What does this mean? This can't happen.  Are you able to read/access files in container on VM1?

Admin CLI fails to say whether volume is attached or not

If both VMs are on same ESX then this should not happen. If VMs are on different host then it may reset metadata.

docker volume inspect doesn't show following "status" information

What version of Docker you are running in this VM? Note that additional status info in "inspect" is available only for Docker 1.12 and above.
BTW, I couldn't repro this on my setup.

Testcase steps:

VM1: create volume abc1> list volume > docker volume inspect abc1

root@photon-xVmYMbyTn [ ~ ]# docker volume create --driver=vsphere --name=abc1
abc1
root@photon-xVmYMbyTn [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vsphere             abc1@sharedVmfs-0
root@photon-xVmYMbyTn [ ~ ]# docker volume inspect abc1@sharedVmfs-0
[
    {
        "Name": "abc1@sharedVmfs-0",
        "Driver": "vsphere",
        "Mountpoint": "/mnt/vmdk/abc1@sharedVmfs-0",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "capacity": {
                "allocated": "13MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Sat Mar  4 09:26:00 2017",
            "created by VM": "photon-VM0.3",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "detached"
        },
        "Labels": {},
        "Scope": "global"
    }
]

VM2: list volume > docker volume inspect abc1

root@photon-xVmYMbyTn [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vsphere             abc1@sharedVmfs-0
root@photon-xVmYMbyTn [ ~ ]# docker volume inspect abc1@sharedVmfs-0
[
    {
        "Name": "abc1@sharedVmfs-0",
        "Driver": "vsphere",
        "Mountpoint": "/mnt/vmdk/abc1@sharedVmfs-0",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "capacity": {
                "allocated": "13MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Sat Mar  4 09:26:00 2017",
            "created by VM": "photon-VM0.3",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "detached"
        },
        "Labels": {},
        "Scope": "global"
    }
]

VM1: start container by mounting to abc1 > write some data > leave it attached/running

root@photon-xVmYMbyTn [ ~ ]# docker run -it -v abc1@sharedVmfs-0:/vol1 --name cnt_abc busybox
/ #

VM2: docker volume inspect abc1 (it should be in attached state)

root@photon-xVmYMbyTn [ ~ ]# docker volume inspect abc1@sharedVmfs-0
[
    {
        "Name": "abc1@sharedVmfs-0",
        "Driver": "vsphere",
        "Mountpoint": "/mnt/vmdk/abc1@sharedVmfs-0",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Sat Mar  4 09:26:00 2017",
            "created by VM": "photon-VM0.3",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "attached"
        },
        "Labels": {},
        "Scope": "global"
    }
]

ESX: make sure vmdkops_admin output is in sync with volume inspect

on ESX1:
[root@sc-rdops-vm10-dhcp-36-198:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)            Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  ------------------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
abc1    sharedVmfs-0  photon-VM0.3   Sat Mar  4 09:26:00 2017  564d70fe-a78a-cbf8-6faf-50da48997c64  N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

on ESX2:

[root@sc-rdops-vm10-dhcp-34-44:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
abc1    sharedVmfs-0  photon-VM0.3   Sat Mar  4 09:26:00 2017  photon-VM0.3                N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

VM2: start container by mounting to abc1 > expect an error (docker: Error response from daemon: VolumeDriver.Mount: Failed to add disk 'scsi1:0'. disk /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/abc1.vmdk already attached to VM=422f7a41-10e5-0937-30ad-bd9bffa54565.)

root@photon-xVmYMbyTn [ ~ ]# docker run -it -v abc1@sharedVmfs-0:/vol1 --name cnt_abc_213 busybox
docker: Error response from daemon: VolumeDriver.Mount: Failed to add disk 'scsi1:0'. disk /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/abc1.vmdk already attached to VM=564d70fe-a78a-cbf8-6faf-50da48997c64.

VM2: docker volume inspect abc1 (make sure output stays the same as before)

root@photon-xVmYMbyTn [ ~ ]# docker volume inspect abc1@sharedVmfs-0
[
    {
        "Name": "abc1@sharedVmfs-0",
        "Driver": "vsphere",
        "Mountpoint": "/mnt/vmdk/abc1@sharedVmfs-0",
        "Labels": {},
        "Scope": "global"
    }
]

ESX: make sure vmdkops_admin output is in sync with volume inspect

[root@sc-rdops-vm10-dhcp-36-198:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
abc1    sharedVmfs-0  photon-VM0.3   Sat Mar  4 09:26:00 2017  detached                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

@pdhamdhere

BTW, I couldn't repro this on my setup.

After restarting docker service, able to attach volume back; so changing the title saying "metadata is getting reset"

This test is not supported for the current level of the service. At least not yet, till the service can use a correct way to figure that a volume is really attached and in use (thru VC perhaps). On the other ESX host it will not find the VM and will simply leave the VMDK attached to the VM but set the meta-data (in KV) to DETACHED. But this is just the meta-data, the VMDK is still attached to the VM on the other host.
Admin CLI status in last step is correct. We need to see the service logs why the Get is reporting no status data.

@shuklanirdesh82 can we get the service logs for this test.

@govint docker-volume-service and vmdkops service logs are uploaded in comment#3

Volume metadata getting reset if VM tries to claim volume which is already-in-use is known issue. This will be resolved once we have integration with Property Collector on Hostd #369


syscall: missing SYS_GETSOCKOPT in zsysnum_linux_386.go

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.7.5
What operating system and processor architecture are you using (go env)?
Darwin/amd64
What did you do?
If possible, provide a recipe for reproducing the error.
GOOS=linux GOARCH=386 go doc syscall.SYS_GETSOCKOPT

What did you expect to see?
List of defined constants containing SYS_GETSOCKOPT.
What did you see instead?
doc: no symbol SYS_GETSOCKOPT in package syscall

working as intended because there isn't a getsockopt syscall on linux/386.
Long answer:
linux/386 multiplexes all socket syscalls into a one syscall (probably
because there aren't enough registers to pass the arguments.)
https://golang.org/src/syscall/syscall_linux_386.go#L183

Thanks a lot for the explanation. In that case, how to implement Getsockopt* for structs not implemented in syscall or unix?  The following code works on linux_amd64. I'd like to know a way to do that on linux_386 as well.
// Call getorigdst() from linux/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
func getorigdst(fd uintptr) (*syscall.RawSockaddrInet4, error) {
	const SO_ORIGINAL_DST = 80 // from linux/include/uapi/linux/netfilter_ipv4.h
	raw := syscall.RawSockaddrInet4{}
	siz := unsafe.Sizeof(raw)
	if _, _, errno := syscall.Syscall6(syscall.SYS_GETSOCKOPT, fd, syscall.IPPROTO_IP, SO_ORIGINAL_DST, uintptr(unsafe.Pointer(&raw)), uintptr(unsafe.Pointer(&siz)), 0); errno != 0 {
		return nil, errno
	}
	return raw, nil
}

Questions are best directed to a forum, rather than the issue tracker; see https://golang.org/wiki/Questions.
On 386 GNU/Linux you'll need to call something along the lines of Syscall6(syscall.SYS_SOCKETCALL, 15, /* socko pt arguments */).

Thanks a lot for the pointer! :)


Sensor calibration

Hello,
Found this on Tindie and am extremely interested as this is something that I've wanted to build myself.
As I was looking at the sensor documentation to figure out what I would have todo to make it myself (was looking at the SCD41) I saw that there was an api for set_sensor_altitude (datasheet section 3.6.3) and set_ambient_pressure (section 3.6.5) each which calibrates the sensor so that it can perform higher accuracy measurements.
Is this something that is taken into account?
I was looking at the board and didn't see any pressure measurement sensors, for my project I was planning on using BMP384 to get this information... if this is something thats taken into account I would just buy yours on Tindie :)

Hey @crener thanks for reaching out. I take the sensor altitude into account here https://github.com/davidkreidler/OpenCO2_Sensor/blob/main/OpenCO2_Sensor.ino#L200 .
By default, it is set to 50 m above NN (because I'm from Berlin). This can be simply changed by you in the code and programmed into the sensor.
Air pressure is am interesting additional point! I I would highly encourage you to build a DIY version with a esp32 development board, a Waveshare 1.54" display, a SCD41 dev board and an air pressure sensor to find out potential benefits of this additional measurement.
In general the accuracy of the SCD40  is ±(50 ppm + 5% MV) @400-2000 ppm wich is more than enough to determine indoor air Quality (when to open a window). The Open CO2 Sensor also uses automatic self calibration by default to prevent potential long term drift. For this the Sensor needs ambient air exposure once peer week to automatically calibrate itself.
It would also be possible to by the Open CO2 Sensor on Tindie and add an external pressure sensor to the i2c bus here:

I hope this helps!

I think if it's noticeable people who use this in a tall building might have issues if the floor they are in is more than X meters above the ground (assuming that the setting is changed in their OpenCO2 unit).
Easy test might be to put two next to each other one with a 50m setting and another with 250m and see if the values are the same over the course of a day? I don't have any hardware on hand to build this (more of a software guy) so would take me a while to get an answer...

Related article: https://gaslab.com/blogs/articles/altitude-compensation-co2-sensors
So it seems like a sensor calibrated at sea level (0m altitude) would display about 1% CO2 too much per additional 100m of altitude.

Hmm interesting read, for me that level of accuracy is fine with the default  but would make this unsuitable for people in mountains who aren't comfortable changing code and compiling to get a better base configuration for their location.
If you live in the Alps your village could be 1500m in elevation which would make all readings quite inaccurate.
Though i don't think anyone expects absolute accuracy from something like this, maybe the buttons on the back could be repurposed for some basic configuration?

Thanks for jumping on this discussion. The Building measurement idea would be defeated be the accuracy of the scd40 Sensor itself ±(50 ppm + 5% MV). At a 200m Height difference the difference would be 2% according to ThomasWaldmanns commend.
If you live in the Alps the automatic self calibration (ASC) of the SCD40 Sensor by Sensirion (a Swiss company) would do a great job in slowly adjusting to the Height. It needs to be exposed to ambient air.  This mode is enabled by default on my OpenCO2 Sensor.
From the Datasheet:
"Field Calibration
To realize high initial and long-term accuracy, the SCD4x includes two field calibration features. [...] Automatic self-calibration (ASC) ensures highest long-term stability of the SCD4x without the need of manual action steps from the user. The automatic selfcalibration algorithm assumes that the sensor is exposed to the atmospheric CO2 concentration of 400 ppm at least once per
week."

Is there a way to calibrate to 430ppm instead of 400ppm?

@ThomasWaldmann currently the calibration via the Menu ->Calibrate is defining the Environment to have 420ppm
https://github.com/davidkreidler/OpenCO2_Sensor/blob/v4.4/OpenCO2_Sensor.ino#L435
It can be changed there and then flashed onto the OpenCO2 Sensor.
For the automatic self calibration I sadly don't have the insides to know what the target is.

Interesting that it is 420, my devices showed 400 after the calibration process with v4.4 (that's why I asked). Thanks for the pointer to where it can be adjusted.


Branch coverage is zero

Bug
Upon using SqlCover with tSqlT, the line coverage is found but the branch coverage is zero
Using the way mentioned in this link
https://the.agilesql.club/2016/04/sqlcover-code-coverage-for-sql-server-t-sql/

Hi @ronniekapoor I need a bit more to go on, if you can give me an example of what you mean then please re-open this!
ed


RenderTexture not clearing correctly on CanvasRenderer

I am using pixi 2.0, have a DisplayObject container with a number of Sprites in it that are moving, I then render the DisplayObjectContainer to texture and it doesnt seem to clear the previous frame correctly whether i call clear or pass clear through the render call. This is currently only happening on CanvasRenderer, Webgl seems fine. I have literally reproduced this using your example11 but instead of rendering the stage to texture i render the displayobject with the bunnies to texture forcing CanvasRenderer.

any suggestion on this issue on v4?

@tywang2006 do you have something that I can just copy&paste into http://pixijs.github.io/pixi-examples-v2/#/basics/basic.js and see that its not working properly? Not old v2 code, but new one?
We'll fix that issue anyway, but the time spent on it will depend on how much information you give us.

i will try to make an example in fiddler

You don't need fiddler or that. You can just edit some example and then paste code here. That way we'll be able to test it on different versions of pixi

PIXI.loader.add('../assets/icons/icons.json').load(onAssetLoaded); function onAssetLoaded(loader:any, resource:any):void {     let renderer:any = new PIXI.CanvasRenderer(600, 600);     renderer.backgroundColor = 0x000000;     window.document.body.appendChild(renderer.view);     var sprite = new PIXI.Sprite(PIXI.Texture.fromFrame('icon0'));     var spriteNew = new PIXI.Sprite();     spriteNew.texture = PIXI.RenderTexture.create(sprite.width, sprite.height);     var stage = new PIXI.Container();     stage.addChild(spriteNew);     function render() {         spriteNew.x+=1;         sprite.x+=0.1;         renderer.render(sprite,spriteNew.texture);         renderer.render(stage);         requestAnimationFrame(render);     }     render(); }
if you use WebGLRenderer, it works,but chosen CanvasRenderer will cause issue. thanks

PIXI.loader.add('../assets/icons/icons.json').load(onAssetLoaded);
function onAssetLoaded(loader:any, resource:any):void {
let renderer:any = new PIXI.CanvasRenderer(600, 600);
renderer.backgroundColor = 0x000000;
window.document.body.appendChild(renderer.view);
var sprite = new PIXI.Sprite(PIXI.Texture.fromFrame('icon0'));
var spriteNew = new PIXI.Sprite();
spriteNew.texture = PIXI.RenderTexture.create(sprite.width, sprite.height);
var stage = new PIXI.Container();
stage.addChild(spriteNew);
function render() {
spriteNew.x+=1;
sprite.x+=0.1;
renderer.render(sprite,spriteNew.texture);
renderer.render(stage);
requestAnimationFrame(render);
}
render();
}

it is typescript

+1 updating render texture persists sprites in PIXI canvas mode with transparent background. Sprites persist when removed from the stage and when opacity set to 0.

If this issue persists in v4, and someone can supply a pen that shows it against the latest dev build, I'll reopen it.

I've had similar problems getting a RenderTexture to update a child texture on the fly using canvas. Works great in WebGL. Here is some code you can paste into the pixijs example pages located here
Toggle the disabledWebGl variable and see what happens in canvas; the old texture does not get removed. This result is actually better than what I've been working with. Whenever I try to swap out a texture in a RenderTexture in canvas nothing happens. It doesn't even add the texture i'm trying to swap in. Anyways here is the code.
var disabledWebGl = true;
var app = new PIXI.Application(800, 600, {backgroundColor : 0x1099bb}, disabledWebGl);
document.body.appendChild(app.view);
var woodTexture = PIXI.Texture.fromImage('required/assets/button.png');
var bunnyTexture = PIXI.Texture.fromImage('required/assets/basics/bunny.png');
var sprites = [];
var container = new PIXI.Container();
for (var i = 0; i < 2; i++) {
var bunny = new PIXI.Sprite(woodTexture);
bunny.x = 60 * i;
bunny.y = 60 * i;
container.addChild(bunny);
sprites.push(bunny);
}
var brt = new PIXI.BaseRenderTexture(300, 300, PIXI.SCALE_MODES.LINEAR, 1);
var rt = new PIXI.RenderTexture(brt);
var spriteHolder = new PIXI.Sprite(rt);
spriteHolder.x = 100;
spriteHolder.y = 100;
app.stage.addChild(spriteHolder);
app.ticker.add(function() {
app.renderer.render(container, rt);
sprites[0].texture = bunnyTexture;
});

https://github.com/pixijs/pixi.js/blob/dev/src/core/renderers/canvas/CanvasRenderer.js#L223
// else {
// TODO: implement background for CanvasRenderTarget or RenderTexture?
// }

So, who wants to implement it?

I thought this may have been an old closed issue so I added this one https://github.com/pixijs/pixi.js/issues/4085
It seems to behave differently on 5.0 alpha than it does on the current version I am using (4.2 I believe). 5.0 simply doesn't show anything while 4.2 does refresh the modified texture.

That's because 5,0 broke the canvas renderer completely.


improvement: added tooltip style prop to tooltop exit button

Added tooltip style props for lightbox component on the exit button
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots:
Before (If applicable):

After:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@bfbiggs changed, thank you

@holsted it passes on lightbox


Remove usage of jax.core and jax.interpreters

Those were internal APIs and will be deprecated / removed.
jax.core.Primitive should use jax.extend.core.Primitive
There is also an isinstance check for jax.core.Tracer which may require some more thought on how to replace the logic.
I can help with this work in collaboration with Jax team.

Relevant info:

https://jax.readthedocs.io/en/latest/api_compatibility.html
https://jax.readthedocs.io/en/latest/jax.extend.html\


Add tests for the

The <Style> component could use a little love. It was never something I used or really did anything with, so I don't have a really good grasp of the code.
cc @knowbody @alexlande

Have quite a few now, this can be closed.


docs(config): fix typo in comment of default config file

Description

This PR changes the comment of the header field in the default cliff.toml config, from # template for the changelog footer to # template for the changelog header.
Motivation and Context

That field is for headers so footer in the comment seems to be a typo.
How Has This Been Tested?

As a change to comments, no tests are required.
Screenshots / Logs (if applicable)
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (no code change)
[ ] Refactor (refactoring production code)
[ ] Other

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.
[ ] I have formatted the code with rustfmt.
[x] I checked the lints with clippy.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.40%. Comparing base (35dc1e4) to head (c67c432).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #776   +/-   ##
=======================================
  Coverage   36.40%   36.40%
=======================================
  Files          20       20
  Lines        1522     1522
=======================================
  Hits          554      554
  Misses        968      968

Flag
Coverage Δ

unit-tests
36.40% <ø> (ø)

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

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


Fix returning 'expires_at' in milliseconds timestamps

Don't merge it yet.

Current Status:
Now the serverRegisterServer should work and revoke the token when its not valid anymore.
NOTE: I've noticed very very minor problem. When the authorization server creates the token and passes it, the time it takes is approximately 350ms, that cause for delay in the assessment of the expiration time of the token for the serverRegisterServer (because the expiration time of token is only number of seconds the token is valid for, not precised time, and therefore the serverRegisterServer inferring by itself to add the expiration time given for token to the current time it got the token).
In conclusion, the serverRegisterServer got confused by thinking the token is valid with more seconds than it should be.
Luckily for us, we talking about 1~3 seconds delay, which not caused any special effect on the client side (the user simply can refresh the page or clicks many times at accordion and everything comes back to normal).
So the last step to avoid the delay is to make refactoring and optimization of the authorization server operations.


readme update for osx kvm install

update to readme file to note that kvm install and the zsh shell are not compatible.

Actually, zsh is now supported with the latest kvm, we'll have updates to the Home repo shortly for this!


Add firenvim

Instead of adding it separately for each browser, thought it looked cleaner this way. Feel free to shuffle it around as you see fit.

Wow Firenvim looks nice. Thank you for the contribution!


curl command will include content to avoid error

Description of the change: Sample curl command failed with an error that a content block is missing - fixed.
Reason for the change: Curl command on the current page results in an error
{"errors":[{"message":"Unless a valid template_id is provided, the content parameter is required. There must be at least one defined content block. We typically suggest both text/plain and text/html blocks are included, but only one block is required.","field":"content","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.content"}]}

Link to original source:

Closes #

great catch!!

Hello @gohelh-adsk,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Very cool, thanks @ksigler7 and @thinkingserious


Generated results

When I execute the plugin, only one page of the pdf is generated, and "extracting markdown text from pdf files" message remains constant.

Could you post an example of the PDFs you're processing? This might be fixed now if you update; if not, I can try to reproduce it.


chrome locking up

After installing today, I noticed that dozens of sites were freezing. I disabled this extension then everything worked normal.
OSX High Sierra 10.13.3
Chrome 63.0.3239.132 (Official Build) (64-bit)
Here's one url that was locking up in particular:  https://bootstrap.build/app

I have as similar problem as @crobinson42 has. I guess extension freezes all sites which use React library

I had this same problem. For me the only site I had trouble on was http://www.buildkite.com, which unfortunately is extremely important since it's our CI. I wish Chrome had a way to disable/enable extensions by host, so I could only run react-scope on localhost.

Killed Facebook for me. And Sentry.

And CodeSandbox
It crashes chrome tab even when devtools are closed.


[Feature Request]: Install asdf plugins using .tool-versions

Requested Feature
I have a .tool-versions file in my repo that defines all versions I'd like to use. It would be great if I can use asdf-package to install those plugins and use the versions from .tool-versions, i.e. the same as running asdf install in the repo.
Specifying the versions in devcontainer.json too makes it harder to ensure I use the same versions everywhere.

It seems that https://github.com/iloveitaly/asdf-devcontainer has the capability to support the .tool-versions file.

This project is not associated with the devcontainer project and appears to have been abandoned https://github.com/devcontainers-contrib/features/issues/628 . The official project has removed all devcontainer-contrib features from their listing. https://github.com/devcontainers/devcontainers.github.io/issues/451. There is a fork that is being worked on to update and maintain the features https://github.com/devcontainers-extra/features


0.13.22

If I use the netflix application in the xbox one or from the pc, I do not add the episodes seen. But since kodi no, is it normal?

In version 0.13.22 if I start to see a new series, it is not added to continue watching, I have to look for it again.

I have experienced the same on a Raspberry Pi3

I'm experiencing the same since 13.18 on windows 10, (now 14beta) I've always thought it was not implemented feature.

in the 0.13.21 if that worked the 2 options.


[controller][server] TopicManager refactoring and performance improvements

TopicManager Refactoring and Performance Improvements
Currently, we have three components that work together to fetch topic metadata,
such as endOffset and the timestamp of the last produced message. These
components are TopicManager, PartitionOffsetFetcher, and
CachedPubSubMetadataGetter. We create one TopicManager instance per broker
address/region, which is shared by all the components in the system.
PartitionOffsetFetcher is a part of the topic manager. There is one instance of
CachedPubSubMetadataGetter per StoreIngestionTask, which makes use of
TopicManager and PartitionOffsetFetcher to retrieve topic metadata.
PartitionOffsetFetcher uses pubsub admin and consumer clients to fetch offsets on
behalf of components like CachedPubSubMetadataGetter and other components. Each
PartitionOffsetFetcher has just one instance of a consumer, which is protected
with a consumer mutex since consumers are not thread-safe. This means that
PartitionOffsetFetcher can handle only one request at a time. The consumer mutex
is coarse-grained, which means it holds the lock even when making calls with the
admin client, which is unnecessary since admin clients are thread-safe.
Also, when the mutex is held for topics that do not exist or have metadata fetching
issues, we perform retries while holding the mutex. This results in the mutex being
held for a relatively longer time when there is an issue with one topic, directly
causing delays for other requests waiting for the lock. We have often observed high
contention on this mutex, leading to several issues.
The CachedPubSubMetadataGetter fetches offsets asynchronously using
TopicManager/PartitionOffsetFetcher, and caches them in a local cache. These
asynchronous requests are initiated when an entry is either not in the cache or
when it is stale. Currently, these asynchronous requests are served by the ForkJoin
common thread pool.
When there is an issue like a non-existent topic, we see high contention on the
consumer mutex, as discussed earlier. This results in ForkJoin threads being
blocked on the consumer lock for longer periods. When all the ForkJoin common
thread pools get blocked, other components in the system that rely on them are
starved, which affects their functionality.
To enhance the resiliency of TopicManager in the face of failures, this PR
introduces the following high-level changes:

Admin operations during metadata fetch are now performed without holding any lock.
This prevents bad topics from acquiring the consumer in the first place and reduces
the chances of contention when getting the consumer.

A configurable fetcher consumer pool is introduced for each topic manager. This
allows us to process requests with other consumers even if one is busy.

We have discontinued the use of the ForkJoin common thread pool for submitting
async fetch offset requests. Instead, dedicated fetcher thread pools are used for this purpose.

Miscellaneous

This commit introduced the following configs:

pubsub.topic.manager.metadata.fetcher.consumer.pool.size  - A config to specify number of PubSub consumer clients to use per topic manager (default: 2)
pubsub.topic.manager.metadata.fetcher.thread.pool.size -  Controls the size of per TM thread-pool used for get offset async requests (default: 2).

The TopicManagerRepository.SSLPropertiesSupplier has been extracted into PubSubPropertiesSupplier.
The CachedPubSubMetadataGetter and PartitionOffsetFetcher have been merged to form TopicManagerMetadataFetcher.
The method getOffsetLagFor in AggKafkaConsumerService has been renamed to getConsumerLagBasedOnMetrics.
The method getPartitionOffsetLag in ActiveActiveStoreIngestionTask has been renamed to getPartitionOffsetLagBasedOnMetrics.
TopicManagerContext has been created/extracted from TopicManagerRepository.builder() to pass the required dependencies for TopicManagerRepository.

How was this PR tested?

CI, frankenwar testing
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Thanks a lot @FelixGV, @lluwm, and @gaojieliu for the review, discussions, and help in improving this PR. 🙏 🚀


show-hint--select event is not fired?

editor.on('select',function(){....});
Does the select event of show-hint supposed to be used like this? It never fired.

This event is fired on your completion object (the thing returned from your hint function), not on the editor instance.


Copy the two CUDA files we need on bots so we can build it by default.

Currently all of the CUDA compiler and runtime code is only built on one bot and only on postsubmit. That makes it effectively an experimental feature and prone to incidental breakage. To enable the CUDA codepath to be supported by the broader team and community we must have at least presubmits compiling it. This will reduce the number of postsubmit detected build issues that are happening ~1-2 times a week.
nvidia has a supported install path that is much smaller than the normal install methods and platform agnostic via https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#tarball-zipfile-overview
The cuda.h file we need for the runtime is in here (include/cuda.h):
https://developer.download.nvidia.com/compute/cuda/redist/cuda_cudart/linux-x86_64/
The libdevice.10.bc file we need for the compiler is here (nvvm/libdevice/libdevice.10.bc):
https://developer.download.nvidia.com/compute/cuda/redist/cuda_nvcc/linux-x86_64/
The entirety of these together is ~37MB, vs the 3.5GB normal toolkit install. As neither of these two files are platform dependent every build configuration should have them available and we should be building with CUDA on by default. The bots can extract these and then we can point cmake at the paths by setting CUDAToolkit_INCLUDE_DIRS and IREE_CUDA_LIBDEVICE_PATH ourselves.
Update: nvidia recommends just setting CUDAToolkit_ROOT to the extraction path, then FindCUDAToolkit should (in theory) work (example here). That may be easiest, as all we need to do is:
mkdir cuda_toolkit
cd cuda_toolkit/
wget -q0- https://developer.download.nvidia.com/compute/cuda/redist/cuda_cudart/linux-x86_64/cuda_cudart-linux-x86_64-11.6.55-archive.tar.xz | tar -xf
wget -q0- https://developer.download.nvidia.com/compute/cuda/redist/cuda_nvcc/linux-x86_64/cuda_nvcc-linux-x86_64-11.6.124-archive.tar.xz | tar -xf
...
cmake ... -DCUDAToolkit_ROOT=cuda_toolkit/

This is a good find -- I had looked for something like this previously and not found it.
I'm going to try to login later today to do some work and watching docker images build seems like the right kind of post sickness reentry task :)

that sounds good - we already have the LIBDEVICE cmake variable anyway