Add smart_passive collector

Commit adds smart_passive collector which collects metrics from pre-scraped
data. The reason for doing it this way:
1] take away logic, which is often complicated, how to actually get SMART data
2] SMART data reusability. Often, more than just one monitoring tool is using
SMART data, eg. Diamond and Nagios. This way, you query your disks only once
instead of N times.

This repo has moved to https://github.com/python-diamond/Diamond
Please open a new pull request there if this issue is not resolved with the current code there.
Thanks!


DlgQuickPlayer: The song length is misrepresented on the slider

The slider max doesn't reflect the song length. When playing back a song, the slider is at the end while the song is only half-way through.

Replaced by #63, closing.


run spell-check over description and guidance in data.tsv

Please report any issues regarding misspellings in the submission-schema repo. Closing.


Promisify Download to Catch HTTP Errors

Dunno if this is fine but I noticed HTTP errors weren't being caught by try catch https://github.com/Corsace/Corsace/blob/c1d12e85ecd8f38150b3c8b913d29e94743af577/DiscordBot/commands/tournaments/mappool/download.ts#L117
https://github.com/Corsace/Corsace/blob/c1d12e85ecd8f38150b3c8b913d29e94743af577/Server/utils/download.ts

Actually fixed it.


Fix token usage with jump forward

close #173
This PR fixes the incorrect token usage when jump forward is enabled. Specifically, we introduce a new field orig_prompt_tokens, which will be set when the first jump forward happens so that we could know the original number of prompt tokens. When returning a response (a chunk in streaming or a complete response), we use the following equations to correct the token usage:
completion_tokens = curr_prompt_token - orig_prompt_tokens + completion_tokens
prompt_tokens = orig_prompt_tokens

@comaniac Hi, I suggest initializing the orig_prompt_tokens when constructing the Req so that we can simplify the code.

Thanks that makes sense. Meanwhile, can you add some comments back to explain why we need to calculate the token usage in this way?


Improve the initial onboarding animation

Description
Today, the animation needs to complete first in order for the user to see the text/instructions.
We have to change this in such a way that the text shows up immediately, and then in the background, the animation plays.

Done with: https://github.com/kumahq/kuma-gui/pull/325


Add changelog

Add a changelog sub-page listing all relevant changes.
Optimally, figure out a way to populate it automatically - maybe just download the commit list to a DB and then allow an admin to delete/modify the list to clean it up?

It would be good if it prompted the user before auto-deleting from the list.

I'm not sure if I follow. If you mean auto-deleting games when deleted in Playnite, then that's the idea behind Sharenite, to keep everything in sync. There's no way to add, delete and modify games in Sharenite and any edit like that would be overwritten with a full Playnite sync anyway.


[Feature request]  remember last items

Greetings,
In the PR that I made I recalled that some elements remained saved, now in the latest release those elements reset. Could it be possible to have those elements remain whenever the plugin is reopened.
I don't recall how to cache them or what is causing them to reset but resetting the output each time along with other parameters is more annoying as our use case require to only need to change 1 or two element between each export.
Thanks again,

Do you remember which elements? I didn't see these changes in PR. I'll
revise it as soon as possible.
Em qui., 8 de out. de 2020 às 12:20, Alex<EMAIL_ADDRESS>escreveu:

Greetings,
In the PR that I made I recalled that some elements remained saved, now in
the latest release those elements reset. Could it be possible to have those
elements remain whenever the plugin is reopened.
I don't recall how to cache them or what is causing them to reset but
resetting the output each time along with other parameters is more annoying
as our use case require to only need to change 1 or two element between
each export.
Thanks again,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sandroklippel/qgis_gee_data_catalog/issues/3, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBSMEHUQRCFC24YFYDGOSTSJXKE5ANCNFSM4SI4XYJQ
.

I'm not sure how it happened. I've looked at your fixes and nothing stands out. An option to remember the last directory would be to store the variable in the plugin instance and not the dialog instance. Just by changing https://github.com/sandroklippel/qgis_gee_data_catalog/blob/6e5d89240ebb68d0f16620542c2aabf59e1a09a2/qgis_gee_data_catalog_dialog_base.py#L90 and adding a check if the folder variable is set before providing the default.
Or maybe it was a thing I changed and I opted to don't remember it as users had no way to 'reset' the variable (but any invalid folder would cause a temporary output to be created).
I can do a PR and some tests if you don't want or hhave the time to do so. I may have enough time during the weekend.

Sorry, it was my fault. Just comment out line 431 in
qgis_gee_data_catalog.py
Em qui., 8 de out. de 2020 às 18:17, Alex<EMAIL_ADDRESS>escreveu:

I'm not sure how it happened. I've looked at your fixes and nothing stands
out. An option to remember the last directory would be to store the
variable in the plugin instance and not the dialog instance. Just by
changing
https://github.com/sandroklippel/qgis_gee_data_catalog/blob/6e5d89240ebb68d0f16620542c2aabf59e1a09a2/qgis_gee_data_catalog_dialog_base.py#L90
and adding a check if the folder variable is set before providing the
default.
Or maybe it was a thing I changed and I opted to don't remember it as
users had no way to 'reset' the variable (but any invalid folder would
cause a temporary output to be created).
I can do a PR and some tests if you don't want or hhave the time to do so.
I may have enough time during the weekend.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sandroklippel/qgis_gee_data_catalog/issues/3#issuecomment-705828392,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBSMEGUKJU7YTH23WMXHJTSJYT5XANCNFSM4SI4XYJQ
.

I just commited the fix. If you can do some testing, maybe we can release a minor version after the weekend.

Excellent, thanks! We'll try to do some testing today.

Did a quick test, all seemed fine, the last folder string remained and the output was constant. Thanks again Sandro!

Issue fixed, version 0.4.1 released.

Thanks Sandro for the great support!


MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '10'. Its new value: '9'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '9'. Its new value: '8'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '8'. Its new value: '7'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '7'. Its new value: '6'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '6'. Its new value: '5'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '5'. Its new value: '4'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '4'. Its new value: '3'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '3'. Its new value: '2'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '2'. Its new value: '1'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '1'. Its new value: '0'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT property. Its current value is '502'. Its new value: '501'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT64 property. Its current value is '502'. Its new value: '501'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '0'. Its new value: '14'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '14'. Its new value: '13'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '13'. Its new value: '12'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '12'. Its new value: '11'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '11'. Its new value: '10'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '10'. Its new value: '9'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '9'. Its new value: '8'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '8'. Its new value: '7'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '7'. Its new value: '6'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '6'. Its new value: '5'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '5'. Its new value: '4'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '4'. Its new value: '3'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '3'. Its new value: '2'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '2'. Its new value: '1'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '1'. Its new value: '0'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT property. Its current value is '501'. Its new value: '500'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT64 property. Its current value is '501'. Its new value: '500'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '0'. Its new value: '14'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '14'. Its new value: '13'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '13'. Its new value: '12'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '12'. Its new value: '11'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '11'. Its new value: '10'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '10'. Its new value: '9'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '9'. Its new value: '8'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '8'. Its new value: '7'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '7'. Its new value: '6'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '6'. Its new value: '5'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '5'. Its new value: '4'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '4'. Its new value: '3'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '3'. Its new value: '2'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '2'. Its new value: '1'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '1'. Its new value: '0'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT property. Its current value is '500'. Its new value: '400'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT64 property. Its current value is '500'. Its new value: '400'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '0'. Its new value: '14'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '14'. Its new value: '13'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '13'. Its new value: '12'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '12'. Its new value: '11'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '11'. Its new value: '10'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '10'. Its new value: '9'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '9'. Its new value: '8'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '8'. Its new value: '7'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '7'. Its new value: '6'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '6'. Its new value: '5'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '5'. Its new value: '4'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '4'. Its new value: '3'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '3'. Its new value: '2'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '2'. Its new value: '1'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying ServicePackLevel property. Its current value is '1'. Its new value: '0'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT property. Its current value is '400'. Its new value: '603'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Modifying VersionNT64 property. Its current value is '400'. Its new value: '603'.
MSI (s) (C8:24) [00:15:14:143]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (C8:24) [00:15:14:143]: Doing action: INSTALL
Action start 0:15:14: INSTALL.
MSI (s) (C8:24) [00:15:14:159]: Running ExecuteSequence
MSI (s) (C8:24) [00:15:14:159]: Doing action: FindRelatedProducts
MSI (s) (C8:24) [00:15:14:159]: FindRelatedProducts: could not read ASSIGNMENTTYPE info for product '{27276DC1-66AA-4B16-918D-5AB1EEDF09C6}'.  Skipping...
MSI (s) (C8:24) [00:15:14:159]: FindRelatedProducts: could not read ASSIGNMENTTYPE info for product '{27276DC1-66AA-4B16-918D-5AB1EEDF09C6}'.  Skipping...
MSI (s) (C8:24) [00:15:14:159]: FindRelatedProducts: could not read ASSIGNMENTTYPE info for product '{27276DC1-66AA-4B16-918D-5AB1EEDF09C6}'.  Skipping...
Action start 0:15:14: FindRelatedProducts.
MSI (s) (C8:24) [00:15:14:159]: Doing action: CheckEmulatorInstance
Action ended 0:15:14: FindRelatedProducts. Return value 1.
MSI (s) (C8:24) [00:15:14:159]: Creating MSIHANDLE (50) of type 790542 for thread 4900
MSI (s) (C8:2C) [00:15:14:159]: Invoking remote custom action. DLL: H:\WINDOWS\Installer\MSI1A21.tmp, Entrypoint: CheckEmulatorInstance
MSI (s) (C8:A8) [00:15:14:159]: Generating random cookie.
MSI (s) (C8:A8) [00:15:14:221]: Created Custom Action Server with PID 6940 (0x1B1C).
MSI (s) (C8:28) [00:15:14:237]: Running as a service.
MSI (s) (C8:28) [00:15:14:253]: Hello, I'm your 64bit Impersonated custom action server.
MSI (s) (C8:2C) [00:15:14:253]: Closing MSIHANDLE (50) of type 790542 for thread 4900
Action start 0:15:14: CheckEmulatorInstance.
MSI (s) (C8:24) [00:15:14:268]: Doing action: CheckProc
Action ended 0:15:14: CheckEmulatorInstance. Return value 1.
MSI (s) (C8:24) [00:15:14:268]: Creating MSIHANDLE (51) of type 790542 for thread 4900
MSI (s) (C8:88) [00:15:14:268]: Invoking remote custom action. DLL: H:\WINDOWS\Installer\MSI1A90.tmp, Entrypoint: CheckProc
MSI (s) (C8!D4) [00:15:14:284]: PROPERTY CHANGE: Adding VT_ENABLED property. Its value is '1'.
MSI (s) (C8!D4) [00:15:14:284]: PROPERTY CHANGE: Adding NX_ENABLED property. Its value is '1'.
MSI (s) (C8:88) [00:15:14:284]: Closing MSIHANDLE (51) of type 790542 for thread 4900
Action start 0:15:14: CheckProc.
MSI (s) (C8:24) [00:15:14:284]: Doing action: SetProcFlags
Action ended 0:15:14: CheckProc. Return value 1.
MSI (s) (C8:24) [00:15:14:284]: Creating MSIHANDLE (52) of type 790542 for thread 4900
MSI (s) (C8:94) [00:15:14:284]: Invoking remote custom action. DLL: H:\WINDOWS\Installer\MSI1AA0.tmp, Entrypoint: SetProcFlags
MSI (s) (C8!10) [00:15:14:300]: PROPERTY CHANGE: Adding TOTALMEMSIZEMB property. Its value is '8087'.
MSI (s) (C8!10) [00:15:14:300]: PROPERTY CHANGE: Adding DEFMEMSIZE property. Its value is '2.0'.
MSI (s) (C8!10) [00:15:14:300]: PROPERTY CHANGE: Adding DEFMEMSIZEUNIT property. Its value is 'GB'.
MSI (s) (C8!10) [00:15:14:300]: PROPERTY CHANGE: Modifying TOTALMEMSIZE property. Its current value is '0'. Its new value: '5.9'.
MSI (s) (C8!10) [00:15:14:300]: PROPERTY CHANGE: Adding TOTALMEMSIZEUNIT property. Its value is 'GB'.
MSI (s) (C8:94) [00:15:14:300]: Closing MSIHANDLE (52) of type 790542 for thread 4900
Action start 0:15:14: SetProcFlags.
MSI (s) (C8:24) [00:15:14:300]: Doing action: CheckMemSizeValue_SilentInstall
Action ended 0:15:14: SetProcFlags. Return value 1.
MSI (s) (C8:24) [00:15:14:300]: Creating MSIHANDLE (53) of type 790542 for thread 4900
MSI (s) (C8:0C) [00:15:14:300]: Invoking remote custom action. DLL: H:\WINDOWS\Installer\MSI1AB1.tmp, Entrypoint: CheckMemSizeValue_SilentInstall
MSI (s) (C8!2C) [00:15:14:315]: Creating MSIHANDLE (54) of type 790531 for thread 8236
MSI (s) (C8!2C) [00:15:14:315]: Creating MSIHANDLE (55) of type 790531 for thread 8236
MSI (s) (C8!2C) [00:15:14:315]: Creating MSIHANDLE (56) of type 790531 for thread 8236
MSI (s) (C8!2C) [00:15:14:315]: Closing MSIHANDLE (56) of type 790531 for thread 8236
Action start 0:15:14: CheckMemSizeValue_SilentInstall.
MSI (s) (C8!2C) [00:15:14:315]: Closing MSIHANDLE (55) of type 790531 for thread 8236
MSI (s) (C8!2C) [00:15:14:315]: PROPERTY CHANGE: Adding MAXMEMSIZE_VALID property. Its value is '1'.
MSI (s) (C8!2C) [00:15:14:315]: Closing MSIHANDLE (54) of type 790531 for thread 8236
MSI (s) (C8:0C) [00:15:14:315]: Closing MSIHANDLE (53) of type 790542 for thread 4900
CheckMemSizeValue: used no-limit value type
MSI (s) (C8:24) [00:15:14:315]: Doing action: SetDefaultErrorTitle
Action ended 0:15:14: CheckMemSizeValue_SilentInstall. Return value 1.
MSI (s) (C8:24) [00:15:14:315]: PROPERTY CHANGE: Modifying ERRORMESSAGETITLE property. Its current value is 'Error message title'. Its new value: 'Intel® Hardware Accelerated Execution Manager Setup'.
Action start 0:15:14: SetDefaultErrorTitle.
MSI (s) (C8:24) [00:15:14:315]: Doing action: SetErrorDialog
Action ended 0:15:14: SetDefaultErrorTitle. Return value 1.
MSI (s) (C8:24) [00:15:14:315]: PROPERTY CHANGE: Modifying ErrorDialog property. Its current value is 'ErrorDlg'. Its new value: 'CustomErrorDlg'.
Action start 0:15:14: SetErrorDialog.
MSI (s) (C8:24) [00:15:14:315]: Doing action: LaunchConditions
Action ended 0:15:14: SetErrorDialog. Return value 1.
Action start 0:15:14: LaunchConditions.
MSI (s) (C8:24) [00:15:14:315]: Doing action: UseShellToProcessDriver
Action ended 0:15:14: LaunchConditions. Return value 1.
Action start 0:15:14: UseShellToProcessDriver.
MSI (s) (C8:24) [00:15:14:315]: Doing action: ValidateProductID
Action ended 0:15:14: UseShellToProcessDriver. Return value 1.
Action start 0:15:14: ValidateProductID.
MSI (s) (C8:24) [00:15:14:315]: Doing action: CostInitialize
Action ended 0:15:14: ValidateProductID. Return value 1.
MSI (s) (C8:24) [00:15:14:315]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (s) (C8:24) [00:15:14:315]: Baseline: Sorting baselines for {741289DC-136A-49C3-B1F5-3ED030A7792A}.
MSI (s) (C8:24) [00:15:14:315]: Baseline: New baseline 7.4.1 from transaction.
MSI (s) (C8:24) [00:15:14:315]: Baseline: Sorted order Native: Order 0.
MSI (s) (C8:24) [00:15:14:315]: Baseline Data Table:
MSI (s) (C8:24) [00:15:14:315]: ProductCode: {741289DC-136A-49C3-B1F5-3ED030A7792A} Version: 7.4.1 Attributes: 0 PatchId: Native BaselineId: -2147483648 Order: 0
MSI (s) (C8:24) [00:15:14:315]: Baseline File Table:
Action start 0:15:14: CostInitialize.
MSI (s) (C8:24) [00:15:14:315]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'L:'.
MSI (s) (C8:24) [00:15:14:315]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
 Return value 1.
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: MsiAssembly
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: Class
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: Extension
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: TypeLib
Action start 0:15:14: FileCost.
MSI (s) (C8:24) [00:15:14:331]: Doing action: CostFinalize
Action ended 0:15:14: FileCost. Return value 1.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: Patch
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: Condition
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'L:'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding IntelFolder property. Its value is 'H:\Program Files (x86)\Intel'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding DownloadFolder property. Its value is 'H:\Program Files (x86)\Intel\Download'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding HAXMFolder property. Its value is 'H:\Program Files (x86)\Intel\Download\HAXM'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding IntelHaxmFolder property. Its value is 'H:\Program Files (x86)\Intel\Download\HAXM\1.0.1'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding SysFolder property. Its value is 'H:\WINDOWS\system32'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding Intel64Folder property. Its value is 'H:\Program Files\Intel'.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Adding HAXM property. Its value is 'H:\Program Files\Intel\HAXM'.
MSI (s) (C8:24) [00:15:14:331]: Target path resolution complete. Dumping Directory table...
 Its value is '1'.
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: MsiAssembly
MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT MsiAssembly.Attributes, MsiAssembly.File_Application, MsiAssembly.File_Manifest,  Component.KeyPath FROM MsiAssembly, Component WHERE  MsiAssembly.Component_ = Component.Component AND MsiAssembly.Component_ = ?
Action start 0:15:14: CostFinalize.
MSI (s) (C8:24) [00:15:14:331]: Doing action: SetHaxmFolder
Action ended 0:15:14: CostFinalize. Return value 1.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Modifying IntelHaxmFolder property. Its current value is 'H:\Program Files (x86)\Intel\Download\HAXM\1.0.1'. Its new value: 'H:\Program Files (x86)\Intel\Download\HAXM\7.4.1'.
Action start 0:15:14: SetHaxmFolder.
MSI (s) (C8:24) [00:15:14:331]: Doing action: MigrateFeatureStates
Action ended 0:15:14: SetHaxmFolder. Return value 1.
Action start 0:15:14: MigrateFeatureStates.
MSI (s) (C8:24) [00:15:14:331]: Doing action: InstallValidate
Action ended 0:15:14: MigrateFeatureStates. Return value 0.
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is 'd53a292ed0656546a679e290752fa82e'.

MSI (s) (C8:24) [00:15:14:331]: Note: 1: 2205 2:  3: _RemoveFilePath
MSI (s) (C8:24) [00:15:14:331]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
 Return value 1.
MSI (s) (C8:24) [00:15:14:346]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C8:24) [00:15:14:346]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C8:24) [00:15:14:346]: BeginTransaction: Locking Server
MSI (s) (C8:24) [00:15:14:346]: Note: 1: 2203 2: H:\WINDOWS\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C8:24) [00:15:14:346]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C8:24) [00:15:14:346]: Note: 1: 2203 2: H:\WINDOWS\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C8:24) [00:15:14:346]: Server not locked: locking for product {741289DC-136A-49C3-B1F5-3ED030A7792A}
MSI (s) (C8:24) [00:15:14:346]: Note: 1: 2203 2: H:\WINDOWS\Installer\inprogressinstallinfo.ipi 3: -2147287037
Action start 0:15:14: InstallInitialize.
DEBUG: Error 2203:  Database: H:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147287037
MSI (s) (C8:24) [00:15:14:346]: Product: Intel® Hardware Accelerated Execution Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2203. The arguments are: H:\WINDOWS\Installer\inprogressinstallinfo.ipi, -2147287037,
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2203. The arguments are: H:\WINDOWS\Installer\inprogressinstallinfo.ipi, -2147287037,
Action ended 0:15:14: InstallInitialize. Return value 3.
Action ended 0:15:14: INSTALL. Return value 3.
Property(S): Description = Intel Hardware Accelerated Execution Manager
Property(S): UpgradeCode = {DB78ECC5-A91B-41F4-949C-E30AFB4387CB}
Property(S): WIXUI_EXITDIALOGOPTIONALCHECKBOX = 0
Property(S): CUSTOMMEMSIZEUNIT = 1
Property(S): HAXM = H:\Program Files\Intel\HAXM
Property(S): WixUIRMOption = UseRM
Property(S): MEMSIZETYPE = 1
Property(S): CUSTOMMEMSIZE = 0
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): ARPNOREPAIR = 1
Property(S): ERRORMESSAGETITLE = Intel® Hardware Accelerated Execution Manager Setup
Property(S): ErrorDialog = CustomErrorDlg
Property(S): SysFolder = H:\WINDOWS\system32
Property(S): IntelHaxmFolder = H:\Program Files (x86)\Intel\Download\HAXM\7.4.1
Property(S): ProgramFilesFolder = H:\Program Files (x86)
Property(S): TARGETDIR = L:
Property(S): System64Folder = H:\WINDOWS\system32
Property(S): Intel64Folder = H:\Program Files\Intel
Property(S): ProgramFiles64Folder = H:\Program Files
Property(S): Intel = 6
Property(S): HAXMFolder = H:\Program Files (x86)\Intel\Download\HAXM
Property(S): DownloadFolder = H:\Program Files (x86)\Intel\Download
Property(S): IntelFolder = H:\Program Files (x86)\Intel
Property(S): NOTCHECKVTENABLE = 1
Property(S): TOTALMEMSIZE = 5.9
Property(S): MAXMEMSIZE = 0
Property(S): DescriptionR = Intel® Hardware Accelerated Execution Manager
Property(S): Acronim = Intel HAXM
Property(S): AcronimR = Intel® HAXM
Property(S): VT_Not_Support = This computer does not support Intel Virtualization Technology (VT-x) or it is being exclusively used by Hyper-V. HAXM cannot be installed.
Please ensure Hyper-V is disabled in Windows Features, or refer to the Intel HAXM documentation for more information.
Property(S): XD_Not_Support = This computer does not support Intel Execute Disable Bit (XD) or it is disabled in the BIOS. HAXM cannot be installed.
Please refer to the Intel HAXM documentation for more information.
Property(S): WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT = Launch Intel HAXM &Documentation
Property(S): ARPPRODUCTICON = arp_icon
Property(S): Manufacturer = Intel Corporation
Property(S): ProductCode = {741289DC-136A-49C3-B1F5-3ED030A7792A}
Property(S): ProductLanguage = 0
Property(S): ProductName = Intel® Hardware Accelerated Execution Manager
Property(S): ProductVersion = 7.4.1
Property(S): DefaultUIFont = WixUI_Font_Normal
Property(S): WixUI_Mode = Mondo
Property(S): SecureCustomProperties = ERRORMESSAGETITLE;HAXM_SHELL;MAXMEMSIZE;OLDERFOUND;WIX_DOWNGRADE_DETECTED;WIX_UPGRADE_DETECTED
Property(S): MsiLogFileLocation = L:\haxm-windows_v7_4_1\log-ld.txt
Property(S): PackageCode = {2509FF36-0259-450A-9022-7B87F7327793}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): CURRENTDIRECTORY = H:\Users\lewes\AppData\Local\Temp\intel\HAXM\7.4.1\silent
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 8552
Property(S): MsiSystemRebootPending = 1
Property(S): VersionDatabase = 200
Property(S): VersionMsi = 5.00
Property(S): VersionNT = 603
Property(S): ACTION = INSTALL
Property(S): VersionNT64 = 603
Property(S): WindowsBuild = 9600
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = H:\WINDOWS
Property(S): WindowsVolume = H:
Property(S): SystemFolder = H:\WINDOWS\SysWOW64
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = H:\Users\lewes\AppData\Local\Temp
Property(S): CommonFilesFolder = H:\Program Files (x86)\Common Files
Property(S): CommonFiles64Folder = H:\Program Files\Common Files
Property(S): AppDataFolder = H:\Users\lewes\AppData\Roaming
Property(S): FavoritesFolder = H:\Users\lewes\Favorites
Property(S): NetHoodFolder = H:\Users\lewes\AppData\Roaming\Microsoft\Windows\Network Shortcuts
Property(S): PersonalFolder = J:\我的文档system
Property(S): PrintHoodFolder = H:\Users\lewes\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
Property(S): RecentFolder = H:\Users\lewes\AppData\Roaming\Microsoft\Windows\Recent
Property(S): SendToFolder = H:\Users\lewes\AppData\Roaming\Microsoft\Windows\SendTo
Property(S): TemplateFolder = H:\ProgramData\Microsoft\Windows\Templates
Property(S): CommonAppDataFolder = H:\ProgramData
Property(S): LocalAppDataFolder = H:\Users\lewes\AppData\Local
Property(S): MyPicturesFolder = H:\Users\lewes\Pictures
Property(S): AdminToolsFolder = H:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
Property(S): StartupFolder = H:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
Property(S): ProgramMenuFolder = H:\ProgramData\Microsoft\Windows\Start Menu\Programs
Property(S): StartMenuFolder = H:\ProgramData\Microsoft\Windows\Start Menu
Property(S): DesktopFolder = H:\Users\Public\Desktop
Property(S): FontsFolder = H:\WINDOWS\Fonts
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): PhysicalMemory = 8087
Property(S): VirtualMemory = 5113
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = lewes
Property(S): UserSID = S-1-5-21-4114302665-3708693206-1991511074-1001
Property(S): UserLanguageID = 2052
Property(S): ComputerName = DESKTOP-LEWES
Property(S): SystemLanguageID = 2052
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 23
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 0:15:14
Property(S): Date = 2019/2/6
Property(S): MsiNetAssemblySupport = 4.6.1038.0
Property(S): MsiWin32AssemblySupport = 6.3.10586.0
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): Privileged = 1
Property(S): USERNAME = lewes
Property(S): DATABASE = H:\WINDOWS\Installer\ae4a9.msi
Property(S): OriginalDatabase = H:\Users\lewes\AppData\Local\Temp\intel\HAXM\7.4.1\silent\hax64.msi
Property(S): UILevel = 2
Property(S): VT_ENABLED = 1
Property(S): NX_ENABLED = 1
Property(S): TOTALMEMSIZEMB = 8087
Property(S): DEFMEMSIZE = 2.0
Property(S): DEFMEMSIZEUNIT = GB
Property(S): TOTALMEMSIZEUNIT = GB
Property(S): MAXMEMSIZE_VALID = 1
Property(S): ROOTDRIVE = L:
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): INSTALLLEVEL = 1
MSI (s) (C8:24) [00:15:14:362]: Windows Installer 已安装产品。产品名称: Intel® Hardware Accelerated Execution Manager。产品版本: 7.4.1。产品语言: 0。制造商: Intel Corporation。安装成功或错误状态: 1603。
MSI (s) (C8:24) [00:15:14:362]: Closing MSIHANDLE (49) of type 790542 for thread 4900
MSI (s) (C8:24) [00:15:14:362]: Deferring clean up of packages/files, if any exist
MSI (s) (C8:24) [00:15:14:362]: MainEngineThread is returning 1603
MSI (s) (C8:38) [00:15:14:362]: RESTART MANAGER: Session closed.
MSI (s) (C8:38) [00:15:14:362]: No System Restore sequence number for this installation.
=== Logging stopped: 2/6  0:15:14 ===
MSI (s) (C8:38) [00:15:14:378]: User policy value 'DisableRollback' is 0
MSI (s) (C8:38) [00:15:14:378]: Machine policy value 'DisableRollback' is 0
MSI (s) (C8:38) [00:15:14:378]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C8:38) [00:15:14:378]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C8:38) [00:15:14:378]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C8:38) [00:15:14:378]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (C8:38) [00:15:14:378]: Destroying RemoteAPI object.
MSI (s) (C8:A8) [00:15:14:378]: Custom Action Manager thread ending.
MSI (c) (68:68) [00:15:14:378]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (68:68) [00:15:14:378]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/6  0:15:14 ===

problem solved
cause by : "system environment parameter - path - temp path " has been modified.
reset to this can fix this problem.
TEMP：%SystemRoot%\TEMP
TMP： %SystemRoot%\TEMP

problem solved
cause by : "system environment parameter - path - temp path " has been modified.
reset to this can fix this problem.
TEMP：%SystemRoot%\TEMP
TMP： %SystemRoot%\TEMP


Event listener memory leak?

Following the given Event Listener example, the used memory is constantly growing.
Steps to repeat:

Run event listener example from link.
Use "psrecord" (or similiar tools) and attach to the started process above and capture the memory consumption
Within the Sonos App, trigger some events (Play, Pause, another title etc)
After each event, the used memory grows constantly
The option "soco.config.CACHE_ENABLED = False" has no effect to this issue

Thanks for your great work,
Stefan

Can anyone confirm the memory leak of the event listener? This issue might be worth fixing for release 0.17 too.

Second, I can see that @aschwith tagged this as the potential source of an error in https://github.com/smarthomeNG/smarthome/issues/312, but it then in that thread seems to be exonerated. So my questions is if that problem was the reason @pfischi measured this to begin with. I.e. if this has caused a real world problem.

Hi @KennethNielsen, thanks for getting back to us. Actually, @pfischi and myself have been working on the same smarthomeNG project which uses the SoCo framework to control Sonos devices. I am not sure if @pfischi is still online but I can confirm that unfortunately the memory leak still exists with with SoCo 0.17.
We were testing similar to the way that you suggested. @pfischi described how we reproduce it.
Is there a maximum size for the event queues or will the keep on increasing forever? I will try to add the debug output as you suggested to see if the queues are emptied properly.
Also, I wonder if you or someone else here in the SoCo community can confirm the memory leak in the environment they are using?

@KennethNielsen can you recommend a suitable debug output to monitor the event queue? Thanks a lot.

@aschwith ok, let's do one thing at a time. First of, can I get you to clarify whether I read that smarthomeNG thread correctly in that the bug described there was not related to SoCo? I would like to first determine whether a bug has been observed in the wild, or only in a synthetic test.

Second, can you please post the test code you use. That is always a good starting point. I aware that as @pfischi mentioned, it is probably close to the code in the event module docstring, but it be nice with the exact code so that we are sure we are talking about the same thing.
I hope you are ok with doing a little bit of the leg work on this one, as my time to spend on SoCo is unfortunately not too much.

Hi @KennethNielsen , yes I can confirm that the smarthomeNG thread was not related to SoCo at the end. However, the memory leak is observable for everyone who uses SmarthomeNG in combination with the enabled Sonos plugin which is based on SoCo.
I am able to reproduce the memory leak issue within the smarthomeNG environment. @pfischi was able to reproduce the same issue with the SoCo minimal exampe code from the event listener. Therefore, it should be straight forward in the community to confirm. I started to add debug outputs attached to the event queue to monitor if the number of events increases but could not observe anything special so far. Any suggestion or confirmation of the memory leak is highly appreciated.

Ok. So I have tried to reproduce this within SoCo and I have been unable to reproduce any serious memory leak. When I write serious it is because I find i difficult to figure out what I should have observed. Keep in mind that this is not like memory profiling a C-program, where you are certain that every single increase in memory used is something allocated by the programmer. Python, I assume, does a bunch of advanced optimizations with pro-allocation and such that means that it is not possibly to directly track and increase in memory consumption to the creation of a new object.
A further difficulty is that memory on my system is allocated in 4k pages and the event XML is maybe a few hundred bytes and maybe the same for he XML objects and so on. Bottom line is that you need to be able to create quite a few events to easily see an effect and I was simply not able to. I subscribed to all the event subscriptions and tried to script interaction like play and pause and play list changes, but all in all it didn't amount to that many events.
The bottom line from testing is that I ran a test program over about 12 hours, which is a slightly expanded version of the events example, and I was able to observe only a small increase in total memory footprint, that is small enough that I'm not convinced it doesn't just come from Python caching something before it eventually clears it up. The test data was:
#events  Memory/kb
1051     25352
1619     25372
1722     26260

and I will post the test script at the end of this post.
Ok. So I will close this issue now. Feel free to re-open if you still think there is a problem in SoCo itself. But in order for me to spend more time on it I would need the following:

The exact code used posted
Steps to reproduce with details. It was really nice of @pfischi to post steps to reproduce, but I was unable to use some of them e.g. I was unable to figure out how to change units in psrecord from MB to KB.
Example output that shows the leak

The script used was:

from time import sleep

from threading import Thread

from pprint import pprint
from queue import Empty
from soco.discovery import by_name
from soco import events
from soco.events import event_listener

device = by_name("Køkken")

subs = []
for service in (device.avTransport, device.contentDirectory,
                device.deviceProperties, device.renderingControl,
                device.zoneGroupTopology, device.alarmClock,
                device.systemProperties,
                device.musicServices):
    subs.append(service.subscribe())

def switch():
    last = 1
    while True:
        sleep(0.1)
        last = (last + 1) % 2
        device.play_from_queue(last)
        device.volume = last + 1

Thread(target=switch, daemon=True).start()

event_num = 0
wait = 0.01
while True:
    size = 0
    try:
        for sub in subs:
            try:
                event = sub.events.get(timeout=wait)
                event_num += 1
                pprint(event.variables)
            except Empty:
                pass
            #pprint(event.variables)
            size += sub.events.qsize()

    except KeyboardInterrupt:
        for sub in subs:
            sub.unsubscribe()
        event_listener.stop()
        break

    print("Events", event_num, "Q size", size)


[Sheet] Click event handlers are triggered by pressing Sheet.Trigger

Describe the bug
Basically I want to execute functions inside the sheet overlay but what happens is they get executed immediately.
In my example code i have buttons but they do not execute the function when pressed, but are executed immediately when pressing the sheet trigger.
ER: Events are not triggered
AR: Events are triggered.
Reproduction
https://stackblitz.com/edit/github-qu3ne7-fqgmgx?file=src%2Froutes%2F%2Blayout.svelte
If that doesn't work or the link expires
<script>
	import '../app.pcss';
	import * as Sheet from '$lib/components/ui/sheet/';
</script>
<Sheet.Root>
		<Sheet.Trigger>Open</Sheet.Trigger>
		<Sheet.Content>
			<Sheet.Header>
				<Sheet.Title>Are you sure absolutely sure?</Sheet.Title>
				<Sheet.Description>
					This action cannot be undone. This will permanently delete your account and remove your
					data from our servers.
				</Sheet.Description>
				<button onclick={alert("alerted")}>Alert me</button>

			</Sheet.Header>

		</Sheet.Content>
	</Sheet.Root>
<slot />

Logs
N/A

System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 5600 6-Core Processor
    Memory: 42.46 GB / 63.92 GB
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.1.4 - ~\AppData\Roaming\npm\pnpm.CMD
    bun: 1.1.0 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527

Severity
annoyance

You are using svelte 4 in that stackblitz. In Svelte 4 you need to use on:click not onclick

Sorry I cannot replicate this on stackblitz on svelte 5, :((
However I can replicate in on my private repo.
Here is my package json if it might help
{
"name": "frontend",
"version": "0.0.1",
"private": true,
"scripts": {
"dev": "vite dev",
"build": "vite build",
"preview": "vite preview",
"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
"lint": "prettier --check . && eslint .",
"format": "prettier --write ."
},
"devDependencies": {
"@sveltejs/adapter-node": "^5.2.6",
"@sveltejs/kit": "^2.5.27",
"@sveltejs/vite-plugin-svelte": "^4.0.0",
"@tailwindcss/typography": "^0.5.14",
"@types/eslint": "^9.6.0",
"autoprefixer": "^10.4.20",
"bits-ui": "^1.0.0-next.39",
"clsx": "^2.1.1",
"eslint": "^9.0.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-svelte": "^2.45.1",
"formsnap": "^1.0.1",
"globals": "^15.0.0",
"lucide-svelte": "^0.452.0",
"mode-watcher": "^0.4.1",
"prettier": "^3.1.1",
"prettier-plugin-svelte": "^3.2.6",
"prettier-plugin-tailwindcss": "^0.6.5",
"svelte": "^5.0.0",
"svelte-check": "^4.0.0",
"svelte-sonner": "^0.3.28",
"sveltekit-superforms": "^2.20.0",
"tailwind-merge": "^2.5.4",
"tailwind-variants": "^0.2.1",
"tailwindcss": "^3.4.9",
"typescript": "^5.5.0",
"typescript-eslint": "^8.0.0",
"vite": "^5.4.4",
"zod": "^3.23.8"
},
"type": "module",
"dependencies": {
"dotenv": "^16.4.5",
"pocketbase": "^0.22.0-rc2"
},
"optionalDependencies": {
"@rollup/rollup-linux-x64-gnu": "^4.24.0"
}
}

I even tried reinstalling my node modules.

It doesn't help, unfortunately. Once you provide a reproduction with Svelte 5 I can reopen this issue, but gonna close it until then.

Must be a bug in svelte or one of my old packages!
I deleted my package-lock.json and reinstalled everything now everything works perfectly.
Let me know you need a repro for that so I can create one.

Awesome!

Here is a short video of the error!
It's actually weird that I can only reproduce it at the moment when using touch/taps!
Repro link:  https://stackblitz.com/~/github.com/Inovvia/shadcn-repro-sheet
https://github.com/user-attachments/assets/69ca4560-e313-4675-8dc3-9e1bb37c5f29


Merge 1.2.x into master

Issue
NA
Description
Merge 1.2.x into master

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.3.3-merge-1-2-into-master-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 1.3.3 :tada:
The release is available on:

1.3.3
GitHub release

Your semantic-release bot :package::rocket:


Update images to fix CVEs

Before I can promote a docker image to production, it need to pass a security scan with no medium or high vulns. In the case of dynatrace/oneagent:latest - it trips with:

name
version
CVE
level
solution

openssl
1.1.1a-r1
CVE-2019-0190
medium

openssl
1.1.1a-r1
CVE-2019-1543
medium
Upgrade package openssl to version 1.1.1b-r1 or above.

It appears this image is built with Alpine 3.9
sh-4.4# cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.9.2
PRETTY_NAME="Alpine Linux v3.9"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"
sh-4.4# openssl version
OpenSSL 1.1.1a  20 Nov 2018

I think this is fixed simply with a rebuild using the latest alpine 3.9.3 base image since that openssl version should now be 1.1.1b-r1
dynatrace/dynatrace-oneagent-operator:v0.3.0:

name
version
CVE
level
solution

busybox
1.28.4-r3
CVE-2018-20679
medium

This should be a quick fix by upgrading Alpine to 3.9 (.3) in your Dockerfile  as that should contain a patched - 1.29.3-r10 version of busybox.

Thank you for reporting that issue. We will take care!

@jimangel I will forward your finding internally, as this is a different container image. You are referring to the actual OneAgent container image. This repo is just for the operator.
But definitely something we have to tackle.

Fixed with #103 and #104 respectively.


[ALLUXIO-2521]Add presto onalluxio doc

https://alluxio.atlassian.net/browse/ALLUXIO-2521

I will finish the en doc tomorrow.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13088/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13102/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13106/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.file.FileSystemMasterIntegrationTest.concurrentCreate
Test FAILed.

Merged build finished. Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13116/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13119/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13120/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13156/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13213/
Test PASSed.

Merged build finished. Test PASSed.

After use the profile of -Pspark and -Ppresto , and the guava's class file still in the client jar, my method is wrong? Can anybody explain it?

@gjhkael after talking to you, I updated the solution to exclude gauva. Please checkout my comment. And feel free to test whether that helps

@apc999  thanks for your help. After recompile alluxio project with -Ppresto, the presto works.

@gpang this issues resolved.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13484/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13503/
Test PASSed.

Merged build finished. Test PASSed.

Hi
The alluxio jar with dependencies break a lot of presto dependencies not just guava

@gpang  PTAL after the latest update?

LGTM

@gjhkael thanks for adding this useful tutorial!


JsonApiObject always enables version information

In spring-hateoas-jsonapi:2.0.0, the one-argument constructor for JsonApiObject(boolean) disregards the value of the showVersion parameter, and always sets the showVersion value to true when calling the four-argument constructor.
The effect is that jsonApiConfiguration.withJsonApiObject(new JsonApiObject(false)) results in the version information being added. As a workaround, jsonApiConfiguration.withJsonApiObject(null) can be used to remove the version information, e.g. with the purpose of overriding the configuration for unit testing.

thx for reporting this, I'll have a look at it.

fix will be in the next release.


Feature Request.  Class constructor (shallow and deep)

I would like a deep and shallow class copy constructor.  E.G.
@DeepClassCopyConstructor
class Car {
   String license;
   String model;
   Engine engine;

  Car (Car c){
      this.license = c.license;
      this.model = c.model;
      this.engine = new Engine(c.engine);
  }

}

@ShallowClassCopyConstructor
class Car {
   String license;
   String model;
   Engine engine;

  Car (Car c){
      this.license = c.license;
      this.model = c.model;
      this.engine = c.engine;
  }

}

There's no way for us to know that, to make a deep copy of engine we'd have to call new Engine(c.engine), and there's also no way for us to know that, for example, java.math.BigInteger is immutable and therefore does not need a deep copy, unless we hardcode every immutable type as a big list in lombok someplace. This is hard for java.* and utterly impossible for the entire greater java ecosystem.
That makes this feature request impossible to implement.

Actually can you just do a new Integer(c.id)
Sent from my iPad
On Nov 5, 2018, at 2:36 PM, Reinier Zwitserloot <notifications<EMAIL_ADDRESS>wrote:
There's no way for us to know that, to make a deep copy of engine we'd have to call new Engine(c.engine), and there's also no way for us to know that, for example, java.math.BigInteger is immutable and therefore does not need a deep copy, unless we hardcode every immutable type as a big list in lombok someplace. This is hard for java.* and utterly impossible for the entire greater java ecosystem.
That makes this feature request impossible to implement.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rzwitserloot/lombok/issues/1913#issuecomment-436061464, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVoxz8aKVflKYSnhdsbTwVhyT2tPtS6ks5usL1RgaJpZM4XxTQo.


SelectBox: Electron select labeling. Workaround for #60929

Electron 2.x incorrectly exposes select as role=menuItem

Screen readers do not read aria-label

Remove "title" attribute on select , avoids duplicate reading

Explicit role should not be required under Electron 3

Thanks for the PR🍻


Support custom base url

This PR adds support for custom base url. You can pass custom base url when OpenAISwift creating.
Change point

add baseURL in OpenAISwift
update baseURL setting in  prepareRequest

have the same here too https://github.com/adamrushy/OpenAISwift/pull/81


Create Pool Fee restriction

copy/paste from telegram @ashachaf
"... (if fee is greater than 3% we  should indicate this will not work in the interface or restrict the fee to be between 0-3% only)."

Fee is actually capped at 5%, Yudi says it can remain here too so lets limit at 5%

changed to 5%.


The add-on description starts with a blank line

In the NVDA's store included in alpha versions, planned for NVDA 2023.2, add-on descriptions are read in a multiline edit box. When pressing tab to focus this field, it's confusing the fact that NVDA doesn't start reading, since it seems that no description is included until down arrow is pressed to explore the multiline control.
I can make a PR in some days to fix this, unless you disagree.

Sorry for being slow on replying. I don't see where the newline is sneaking in. The description is in NVDA-addon/buildVars.py and is:
    "addon_description": _("""MathCAT is a replacement for MathPlayer which has been discontinued.
        It provides speech and braille support, and also supports MathPlayer's three modes of navigation.
        The speech quality is not quite as good as MathPlayer's speech yet,
        but the braille support is much better and includes both Nemeth and UEB Technical.
        Translations to Indonesian, Spanish, and Vietnamese exist and other translations are in progress."""),

I would appreciate it if you could fix this since I don't see where the problem lies.
FYI: here's a build of the latest MathCAT that I hope to release in a day or two.

Hello, I created a PR and fixed this, no worries. We'll also provide tests for spanish translation when possible.
Thanks for your attention.

Fixed via PR  #47


Ref #8 - Add tx pair to ordered list when adding it to the wallet

See https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L907

This pull request is now managed with CodeReviewHub. Refresh.

:shipit:

@FornaxA Travis doesn't like it, but seems unrelated to this change?


Simplest possible usecase: Bundle CSS - how?

So the docs really improved when starting with webpack. I got everything JS related working pretty fast and the config is straightforward 👍 .
However when I start to get into CSS, everything is confusing again.
I got a folder:
src/css/ with two files in it:
a.css and b.css.
Now I want them bundled to dist/bundle.css.
I followed these docs but CSS is simply ignored.
I would expect to name an output dir and an entry file, just like with JS.
This is my full config:
const ExtractTextPlugin = require("extract-text-webpack-plugin");
const path = require('path');

module.exports = {
  watch: true,
  devtool: "cheap-eval-source-map",
  entry: './src/js/L.PM.js',
  output: {
    filename: 'leaflet.pm.min.js',
    path: path.resolve(__dirname, 'dist')
  },
  module: {
    rules: [
      {
        test: /\.css$/,
        use: ExtractTextPlugin.extract({
          fallback: "style-loader",
          use: "css-loader"
        })
      }
    ]
  },
  plugins: [
    new ExtractTextPlugin("leaflet.pm.css"),
  ]
};

seems like I have to import my CSS into my JavaScript files to make it work...?
This isn't mentioned anywhere where:
https://webpack.js.org/plugins/extract-text-webpack-plugin/#usage-example-with-css
I import my CSS files into JavaScript so Webpack takes the CSS out again and puts it into a separate file?
This doesn't really make sense. Am I doing this correctly?

I import my CSS files into JavaScript so Webpack takes the CSS out again and puts it into a separate file?

@codeofsumit Yep 😛 , webpack is JS Module Bundler  and doesn't understand CSS 'natively' (that why you need a 'loader' css => module.exports = ${css} ), it builds a dependency graph by walking the import/require() statements and ETWP will gather the chunks and extracted them into one separate file per Instance
const ExtractTextPlugin = require('extract-text-webpack-plugin')

const extractCSS = new ExtractTextPlugin({ filename: 'css.bundle.css' })
const extractSASS = new ExtractTextPlugin({ filename: 'sass.bundle.css' })

const config = {
   module: {
     rules: [
       {
          test: /\.css$/,
          use: extractCSS.extract({ // Instance 1
            fallback: 'style-loader',
            use: [ 'css-loader' ]
          })
       },
       {
          test: /\.scss$/,
          use: extractSASS.extract({ // Instance 2
            fallback: 'style-loader',
            use: [ 'css-loader', 'sass-loader' ]
          })
       }
     ]
   },
   plugins: [
      extractCSS // Instance 1
      extractSASS // Instance 2
   ]
}

I showing you this example, bc ETWP doesn't work per entry, it's alsways a combo of a loader rule and a plugin Instance regradless of how many entries you have 😛

This doesn't really make sense. Am I doing this correctly?

It makes sense when you need the CSS ({String}) during build time (e.g CSS Modules) or to rewrite url() with the correct assets paths in case you load them via webpack.
component.css
.app {
  display: flex;
  background: url('./image.png')
  /* => background: url(require('path/to/image.png')) */
}

component.js
import style from './style.css'
import image from './image.png'

// style.app === '362fzewvf'
const Component = () => render(<div class=`${style.app}`>
)

It doesn't make sense if you are using e.g Bootstrap and you don't need the CSS at build time, then just use a CDN or add a
<link href="path/to/lib">

manually 😛

thanks for the detailed explanation @michael-ciniawsky - I'll send a PR with what I think would've helped me. Your post definitely did!

codeofsumit: did the solution provide by michael-ciniawsky worked for you ?? Can you share the code.
I am also trapped into the same problem that I also want to bundle some how or the other  'cssBundle' with the package. its 2 days now :(

@qasimraza1979 Solved your issue?

@michael-ciniawsky  This worked for me. Thanks. I was doing some silly mistake.

I also was able to make it work.
Here is my code

package.json => NPM
add these to dependencies

"extract-text-webpack-plugin"

and this is you want to minify extracted CSS
'optimize-css-assets-webpack-plugin'

NPM scripts for starting webpack in different modes

"scripts": {
    "webpack-production": "cross-env NODE_ENV=production webpack --env.prod=true",
    "passive-WebpackCompile": "webpack  --display-reasons --config webpack.config.js",
  }

Now

webpack.config.js => top of the file

const ExtractTextPlugin = require("extract-text-webpack-plugin");
const OptimizeCssAssetsPlugin = require('optimize-css-assets-webpack-plugin'); //if want to minify CSS in prod

webpack.config.js => isProd variable

module.exports = function (env) {
    //shell level constants
    const nodeEnv = env && env.prod ? 'production' : 'development';
    const isProd = nodeEnv === 'production';

    //...
}

webpack.config.js => inside module

        module: {
            rules: [
                {
                    test: /\.css$/,
                    // exclude: /node_modules/,
                    use:
                        ExtractTextPlugin.extract({
                            fallback: 'style-loader',
                            use: [{
                                loader: 'css-loader',
                                options: {
                                    sourceMap: !isProd,
                                    // sourceMap: toString(!isProd),
                                    // minimize: isProd
                                }
                            }, {
                                loader: 'sass-loader',
                                options: {
                                    sourceMap: !isProd
                                }
                            }]

                        })

                },
            ],
            loaders: [
                {
                    test: /\.css$/,
                    loader: ExtractTextPlugin.extract(
                        'style-loader',
                        'css-loader'
                    )
                }
            ]
        },

Also added this plugin for CSS minification in PROD

webpack.config.js => add this in plugins, when in production

//minify extracted CSS, works with text extractor
            new OptimizeCssAssetsPlugin({
                assetNameRegExp: /\.optimize\.css$/g,
                cssProcessor: require('cssnano'),
                cssProcessorOptions: { discardComments: { removeAll: true } },
                canPrint: true
            }),

I hope this helps

What is the syntax for referencing the CSS files in TypeScript?


Sum totals description needs breaking out into it's own section

The following statement
The sum of kubernetes online endpoints and managed online endpoints under each subscription cannot exceed 50. Similarly, the sum of kubernetes online deployments and managed online deployments under each subscription cannot exceed 200.
is under the section on kubernetes here https://learn.microsoft.com/en-us/azure/machine-learning/how-to-manage-quotas?view=azureml-api-2#azure-machine-learning-kubernetes-online-endpoints
This should be in it's own section or heading please. We use Managed Online Endpoints and would have missed this information on first pass as it only exists as a statement under the kubernetes section.
Any clearer description of limits in this regard welcome
Thanks

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

ID: 8ea6aa65-3cbb-83d5-0f16-23b58c52cb88
Version Independent ID: 91fa8a56-cde6-06e2-b1bb-d521a7819c30
Content: Manage resources and quotas - Azure Machine Learning
Content Source: articles/machine-learning/how-to-manage-quotas.md
Service: machine-learning
Sub-service: core
GitHub Login: @SimranArora904
Microsoft Alias: siarora

@neilmca-inc
Thanks for your feedback! We will investigate and update as appropriate.

@neilmca-inc
One of our consumers voiced a very similar worry. When our team is finished, we'll update as soon as possible.
#https://github.com/MicrosoftDocs/azure-docs/issues/108069
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)

@Naveenommi-MSFT Thanks. What ideas am I submitting to another site?

Hi @neilmca-inc
You can make your suggestions on the link I shared above if you have any future update requests.

@neilmca-inc
We are going to close this thread if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


JSONata - Issue reading multiple Dashboard Variables

Hi,
We are having this a global variable (multi value variable),  and we are not able to read the actual position of the variable. We are been forced to set the index of the array statically:
Panel Url request: http://localhost:3000/d/h5tWCggVz/app?orgId=1&var-cluster_zone=k8&var-environment_value=int&var-environment_value=nft&editview=templating
Multivalued variable-> environment_value with values (int, nft)
In the JSONata field we can only access to the the values using the array index ($environment_value[0] or $environment_value[1]). We should be able to access to the current value using ${environment_value} or $environment_value.
Do you have any suggestion about how to access to the actual parameter without the need to set the index in the array?
`(
$searchEnvironment :=  function($cluster, $envirovement) {(
$status := $lookup($.teamDashboards, $cluster).applications[*].environments[name = $envirovement];
)};
$r := $searchEnvironment($cluster_zone[0], $environment_value[0]).canaryStatus ;
)`

Quoting the documentation Dashboard variables are available as JSONata variables, e.g. $instanceName. Since dashboard variables can have multiple values, the JSONata variable is always an array. If your variable contains a single value, you can use $instanceName[0] to index the first value in the array.
Given Dashboards variables are an array, if we are using the variable in a Dashboard Row to loop over the values of a variables, how can we know which index of the array we are in? can we access to the actual iterator? or can we just use the actuakl value accessing to the variables (as in JsonPath) using the variable reference like: ${environment_value}

Quoting the documentation [Dashboard variables](https://grafana.com/docs/grafana/latest/variables/) are available as JSONata variables, e.g. $instanceName. Since dashboard variables can have multiple values, the JSONata variable is always an array. If your variable contains a single value, you can use $instanceName[0] to index the first value in the array.
Given Dashboards variables are an array, if we are using the variable in a Dashboard Row to loop over the values of a variables, how can we know which index of the array we are in? can we access to the actual iterator? or can we just use the actuakl value accessing to the variables (as in JsonPath) using the variable reference like: ${environment_value}

I am also facing same issue.

I put a comment with the same problem in another issue. However, this one is exactly my issue.

hi, as some limitations were applied to jsonata in plugin-version v1.3.5 ( see https://github.com/grafana/grafana-json-datasource/blob/main/CHANGELOG.md#v135---2023-04-05 ) for more info, could you try with the current grafana and plugin version, and see if the problem is still actual? thank you!


Add high level job object wrapper and jobcontainers package

Add high level job object wrapper.
Add extra job object bindings for stats usage.
Add jobProcess type to be used with job object wrapper.
Add functions to get a user/service token.

Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

I'm going to move the unit tests to /test/functional today. Forgot they were package local

I'm going to move the unit tests to /test/functional today. Forgot they were package local

Ehh actually.. I'd have to make the wrapper public so I'll wait for feedback on this.

@kevpar @katiewasnothere @ambarve If anyone has time tomorrow, could you give this a glance

@kevpar Addressed feedback. I removed the jobcontainers package from this PR entirely, I'll add the entirety of the package in the next PR. For your suggestion to fix GetQueuedCompletionStatus in x/sys/windows I will send a PR and see where that gets.

@kevpar Addressed all feedback (I think :P )

One small fix about using Broadcast vs Signal but otherwise LGTM!

@kevpar If you have some time to do a last sweep :)


Build failures don't output anything if the project file doesn't exist

14:01:45 INF] Executing application from  /Users/ryan/github.com/dotnet/tye/samples/single-project/tye.yaml
[14:01:45 INF] Dashboard running on http://<IP_ADDRESS>:55862
[14:01:50 INF] Building project /Users/ryan/github.com/dotnet/tye/samples/single-project/tye.yaml/test-project/test-project.csproj
[14:01:50 INF] Building /Users/ryan/github.com/dotnet/tye/samples/single-project/tye.yaml/test-project/test-project.csproj failed with exit code 1:
[14:02:11 INF] Shutting down...

I introduced a bug that lead to the project full path being computed teh wrongly. It doesn't give you a good error message.

This should be fixed.

Why was this closed? Is there a PR to link?

https://github.com/dotnet/tye/pull/152


Adding option to force install GTest.

Also making it force install GTest 1.10 by default on jenkins CI.  Looks like we're grabbing an older version of Gtest there, causing CI failures.

Can you provide an example of CI having the wrong version of gtest? We might need to fix something in CI if that's the case

Can you provide an example of CI having the wrong version of gtest? We might need to fix something in CI if that's the case

If you take a look at any of the CI failures since the HIP on Windows commit in the develop branch (where I added the requirement for Gtest 1.10 and added a find_package check beforehand to Dependencies.cmake), you should be able to see that most if not all of them are failing during compilation.  All of which are failing due to Gtest in some shape or form.  From my experience those messages are consistent with older version of gtest being found.

All below is from Eiden:```
Failure is likely cause by I think moving
include(cmake/Dependencies.cmake)
before
set(AMDGPU_TARGETS "${DEFAULT_AMDGPU_TARGETS}" CACHE STRING "List of specific machine types for library to target")
sets AMDGPU_TARGETS prematurely because dependencies.cmake does find_package(rocprim) which causes find_package(hip) which sets AMDGPU_TARGETS
I think something is broken in rocThrust compilation in CI. It hasn't been targeting the right device targets since this commit https://github.com/ROCmSoftwarePlatform/rocThrust/commit/22fda4adfced5be5addec35b16050d7ffc99a67e
Last passing
http://math-ci.rocm.amd.com/blue/organizations/jenkins/compute-rocm-dkms-no-npi-hipclang%2Fprecheckin%2FrocThrust/detail/develop/134/pipeline/210/#step-225-log-172
Device targets : gfx803;gfx900:xnack-;gfx906:xnack-;gfx908:xnack-;gfx90a:xnack-;gfx90a:xnack+;gfx1030
First fail
http://math-ci.rocm.amd.com/blue/organizations/jenkins/compute-rocm-dkms-no-npi-hipclang%2Fprecheckin%2FrocThrust/detail/develop/135/pipeline/217
Device targets : gfx900;gfx906;gfx908

Upon further investigation, the root cause is not because of an older version of GTest being installed, but a combination of trying to build a test executable with no test case (device_delete) and using GTest static library.
Adding the test case back (even if it is empty) fixed the issue locally for me.  And linking to Gtest as a shared library also seems to avoid the problem.

The title of the PR was likely incorrect.


Update mobile view drawer menu

Description
Add language switch
Add I18n
Screenshots
No response
Additional information
No response

Meaning like this? That the language switch is inside the drawer below?

closed due to #271


Add email notification when cancel a recurring contribution

Coverage increased (+0.08%) to 81.062% when pulling d3a73cfadeb1537871f416155ec2ce3b3229400b on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.

Coverage increased (+0.07%) to 81.049% when pulling 1265b06ab432d0a492ee07d0627b66837ce58b5e on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.

Coverage increased (+0.07%) to 81.049% when pulling fb2c65e80a24210fc261024722d49850d2d726e6 on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.

Coverage increased (+0.1%) to 81.073% when pulling 5f153703ef7ea1999cc8f195d66e023f81ab2884 on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.

Coverage increased (+0.1%) to 81.073% when pulling 60c1a68c2b4496d50201421122df6332f978cd9b on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.

Coverage increased (+0.1%) to 81.073% when pulling e1a9a4e310908f3220132245b0eb2ea3460f8428 on feat/cancel-recurring-contribution into 861d8de6052f8301a3b9b2fb1b1b8ad57e9233a0 on master.


Collection annotated with @PathVariable is parsed as semicolon separated value

Describe the bug
FeignClient parses collection from method argument as string value where elements are separated by semicolon, but I think it should be a comma separated value instead.
Sample
Let's say we have some feign client
@FeignClient(name = "some-entity-target-service", url = "http://localhost:8081/api/v0/some_entity/")
public interface SomeEntityFeignClient {...}
with method like this
@GetMapping("{ids}")
ResponseEntity<Collection<SomeEntity>> getByIds(@PathVariable Set<String> ids);
Style from guideline gives the same result
@RequestMapping(method = RequestMethod.GET, path = "{ids}")
ResponseEntity<Collection<SomeEntity>> getByIds(@PathVariable("ids") Set<Integer> ids);
Logs show request that feign sends

GET http://localhost:8081/api/v0/some_entity/1;2 HTTP/1.1
But as for me it should be
GET http://localhost:8081/api/v0/some_entity/1,2 HTTP/1.1

What version are you using? #260 added something similar but for matrix parameters.

@spencergibb I've pulled spring boot project from spring initializr version 2.2.2.
It has
 <dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-openfeign-core</artifactId>
<version>2.2.1.RELEASE</version>
<scope>compile</scope>
</dependency>
And
  <dependency>
<groupId>io.github.openfeign</groupId>
<artifactId>feign-core</artifactId>
<version>10.4.0</version>
<scope>compile</scope>
</dependency>
If I missing something, you may see list of dependencies and its versions here

I'm not a developer of this library, but as far as I understand spring-cloud-openfeign is not responsible for doing this.
Expanding URI parameters is feign's burden.
Maybe you should consider moving your issue there?
I hope this helps! Good luck trying to fix this!

@IlyasYOY maybe, idk
Let someone reject this issue this comment like yours and I'll do the same for feign directly

Hi, @AndrewPanov I have just tested your example on Hoxton.SR3, and I'm getting  /ids/1,2,3 as expected.
Please provide a minimal, complete, verifiable example that reproduces the issue.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Hi. @AndrewPanov problem fixed on release 2.2.2.RELEASE.

org.springframework.cloud
spring-cloud-starter-openfeign
2.2.2.RELEASE

Hi. @AndrewPanov problem fixed on release: 2.2.2.RELEASE.
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-openfeign</artifactId>
<version>2.2.2.RELEASE</version>
</dependency>

Hi @AndrewPanov, please upgrade to Hoxton.SR3 and verify.

@lashen, @OlgaMaciaszek thanks for reply


[question] How to achieve maximum GPU utilization with TensoRT-LLM lib using openai-server.py

Hello,
Thank you for creating openai-server.py. It has been very helpful in avoiding the need to use vLLM or other OpenAI-like proxies.
I need to deploy several LLMs and embedding models. After reviewing the code for openai-server.py, I noticed that it currently handles only a single model. I am planning to use Triton for inference and manage GPU utilization through Triton.
How would you recommend managing GPU resources through TensorRT-LLM? Is there a way to use multiple LLMs with openai-server.py? Additionally, is there a planned implementation for an API to support Triton-hosted models?
Thanks in advance for your help!

Hi, thanks for using and helping to improve our library.

Can you please explain how you are going to "manage GPU utilization through Triton"?
TRT-LLM has a runtime argument to manage how much free memory should be used for KV Cache, I am not quite sure how you are going to manage GPU utilization, but this argument could be one option. Currently, we do not include it as an openai server argument, but it will not take much effort to add.
For serving multiple models with openai server, I am afraid that we do not have an elegant way to do this at this point. But you can still try to use multiple processes to run multiple server instances (and control their memory fraction carefully), then direct requests to their model.
"an API to support Triton-hosted models", for this question, do you mean implementing openai api in triton?


Why are you removing dependencies on upgrade?

Script
nginx-proxy-manager
Describe the bug
https://github.com/ej52/proxmox-scripts/blob/main/lxc/nginx-proxy-manager/install/alpine.sh#L64
You are removing dependencies on upgrade, just to install them again later. It would make more sense to just leave them installed. Is there a specific reason they need to be removed and then added again?

Apologies, I did miss read the issue.
I added that bit of code as a way to remove any old dependencies that may have been installed with older installs of NPM using the script. As it would cause conflicts with NPM changes.
eg. NPM started using pip certbot package instead of apk package.
When the script finishes or exits unexpectedly, trapexit is called to cleanup and remove all the DEVDEPS to keep the proxmox container lightweight.

--cleanup flag added in the latest PR, by default it will leave all the dev dependencies, unless the flag is set.


Timeout?

Is there a way to set (or add) a timeout on a connection. We are sending millions of emails via MailGun, and occasionally our message pump (which simply drains a redis list with prepared content), hangs in the call to message().send. It just never calls the callback. It's intermittent, we can send 100k emails or millions and then it pops up. My thoughts are that something went wrong the connection and it needs to timeout, or a callback is being missed somewhere in mailgun-js and node goes idle (our status monitor for example keeps running). Any ideas?

Hello,
Hmm that does sound strange. Are you using a proxy? Are there attachments? Can you post some sample code / pseudo code on how you are using the library just so I understand the context? Are emails sent asynchronously in parallel? or synchronously in a series. If parallel, how many at a time?
I think a timeout option is possible. We can just use the normal http(s) Request setTimeout option.
https://nodejs.org/api/http.html#http_request_settimeout_timeout_callback
I am thinking that the timeout from http will result with err in the callback from mailgun library.
so for example something like:
var mailgun = require('mailgun-js')({
  apiKey: api_key,
  domain: mydomain,
  timeout: 60000 // 1 minute timeout
});

var data = {
  //...
};

mailgun.messages().send(data, function (err, body) {
  if(err) {
    console.log(err); // in case of timeout err will be defined with some kind of timeout message and passed back in the callback
  }
  console.log(body);
});

Any thoughts? Does this sound sensible?

I am sending up to 8 at a time, the code is simple. There is a function that waits on blpop from redis, when it pops, it takes the content and pushes it to message.send(). When message.send returns, it calls itself using setimmediate to unroll any stack.
At startup I call the function 8 times, which basically puts 8 calls waiting on blpop.
It's an odd one, it can run for weeks and send millions of emails, or like in the last few days stop 3 times. It's now running smoothly again, which makes me think it's a "hung" connection.
I'm thinking the timeout as you specified would be perfect just to catch anything along these lines, and you are correct, request does have a timeout option, so if you can use that, it makes perfect sense.
Thank you for looking into this, and we really enjoy this module, it great.
Seth


cant set default label on logger for uncaught exceptions

Please tell us about your environment:

winston 3.2.1?

[ ] winston@2
[X ] winston@3

_node -v outputs: v10.15.3
Operating System? (Windows)
Language? (TypeScript X.X)

What is the problem?
I want to set the label of the logger for uncaught exceptions
example output (I'm spitting the value of label from the format function)
label: gde-proxy_proxy.ts_onRequest
2019-07-11 19:42:55.55 [gde-proxy_proxy.ts_onRequest] debug: incoming message for GET /_api/info
  meta: {"app":"gde-proxy - development","env":"development","method":"GET","url":"/_api/info","headers":{"host":"localhost:8080","user-agent":"curl/7.46.0","accept":"*/*"}}

label: undefined
2019-07-11 19:42:55.55 [] error: uncaughtException: error from isapicall
Error: error from isapicall

this is my format function:
    format.printf(({ timestamp, message, service, label, level, ...meta }) => {
      console.log('label:', label)
      return `${timestamp} [${label || ''}] ${level}: ${message} ${logMeta(meta)}\n`
    })

these are my console options:
  console: {
    level: config.console_log_level || 'verbose',
    handleExceptions: true,
    label: DEFAULT_LABEL,
    // json: true,
    colorize: true,
  },

And this is how I create my log:
const logger: Logger = createLogger({
  level: config.log_level || 'info',
  format: getFormat(),
  transports: [new transports.Console(options.console)]
})

I don't know where the logger that handles uncaught errors is created...
What do you expect to happen instead?
Show the default label when logging and uncaught error

As per the current version & version 3.2.1 of Winston the only valid configuration value that you're applying to the Console Transport is level. Documentation regarding these valid options can be found here: latest v3.2.1
With that being said the defaultMeta logger configuration (example here) is likely what you want to use for this behavior. Unfortunately we don't have good documentation around Default Metadata configuration for a given logger but that should be changing in the near future.


Plotly Offline Option

Firstly, this is a suggestion, rather than an issue, as such.
Secondly, Plotly has recently released their offline API for R and Python and has open sourced the core JavaScript library.   This offline option is important for those working in the finance industry, since it removes security issues associated with sending data to a 3rd party for plotting.  I don't know what would be involved with regards modifying XPlot to offer a Plotly offline option, but I do think that it would solve the problem mentioned above and with that, potentially create a wider audience for XPlot and FsLab.

The latest version on NuGet supports plotly.js and removes the API round trip. The FsLab integration isn't up do date yet, I'm testing the new version and fixing the JSON schema mappings on the go.

Hi there,
Thanks for this, that's good news.  Also, thank you for your work on this
part of the XPlot library as well as the others.
Regards,
Russell
On Sun, Jan 10, 2016 at 4:34 PM, Taha Hachana<EMAIL_ADDRESS>wrote:

The latest version on NuGet https://www.nuget.org/packages/XPlot.Plotly/
supports plotly.js and removes the API round trip. The FsLab integration
isn't up do date yet, I'm testing the new version
https://github.com/TahaHachana/XPlot/tree/master/src/XPlot.Plotly/Tests
and fixing the JSON schema mappings on the go.
—
Reply to this email directly or view it on GitHub
https://github.com/TahaHachana/XPlot/issues/26#issuecomment-170353563.

--
Russell

I might have just updated the FsLab integration, though I have not done any proper testing!

Hi All,
Cool, thanks Tomas.  I have a small project in mind, which I’d like to try, hopefully in the next few months if time permits.  It essentially revolves around reporting and I’d like to pull a few things together with it, namely Fs Lab for the literate programming angle (ie. easy HTML rendering), the SQL Command type provider for painless SQL server access, a proprietary library for market data access and XPlot for charting.  The idea is to see if we can use this set of tools to develop high quality reports / analytics using a scripting paradigm.
At this point, I think we have all the required pieces in place to be able to do this in F#.
Russell
From: Tomas Petricek<EMAIL_ADDRESS>Sent: Wednesday, 13 January 2016 3:52 AM
To: TahaHachana/XPlot<EMAIL_ADDRESS>Cc: RussellPolitzky<EMAIL_ADDRESS>Subject: Re: [XPlot] Plotly Offline Option (#26)
I might have just updated the FsLab integration, though I have not done any proper testing!
—
Reply to this email directly or view it on GitHub https://github.com/TahaHachana/XPlot/issues/26#issuecomment-171127723 .  https://github.com/notifications/beacon/AAitMehDE_GyXW4J11SQo7t_zPyxcnboks5pZaUogaJpZM4HBqpj.gif

Hi,
I’ve done a little testing.  Off line charts seem to be fine in FSI but weren’t working in the journal output.
I’ve added a few lines to the formatter to ensure that the plotly library is loaded once.
I’ve sent a pull request for the fix.
Regards,
Russell
From: Tomas Petricek<EMAIL_ADDRESS>Sent: Wednesday, 13 January 2016 3:52 AM
To: TahaHachana/XPlot<EMAIL_ADDRESS>Cc: RussellPolitzky<EMAIL_ADDRESS>Subject: Re: [XPlot] Plotly Offline Option (#26)
I might have just updated the FsLab integration, though I have not done any proper testing!
—
Reply to this email directly or view it on GitHub https://github.com/TahaHachana/XPlot/issues/26#issuecomment-171127723 .  https://github.com/notifications/beacon/AAitMehDE_GyXW4J11SQo7t_zPyxcnboks5pZaUogaJpZM4HBqpj.gif

Thanks for the contribution


don't copy all layers in DrawTiled()

Started using this library to load a 10,000 tile map, and performance tanked. Largest contributor was copying all the layers in DrawTiled(). Switching to a reference cut cpu usage 50%.

omg thank you

You’re welcome. Thank you for writing the library in the first place.


Proximal, proximal conjugate and inline computation

In our generic Function class, we have two methods the proximal and the proximal_conjugate.
The default proximal method does not compute anything. On the other hand, the proximal_conjugate is computed using the proximal method (Moreau decomposition)
For example, in the L2NormSquared implementation in order to compute the proximal_conjugate it is sufficient to define a proximal method, since this will call the parent proximal_conjugate method of the Function class.
In the future, if we want to define another function and use the proximal and proximal_conjugate methods, we need only to define its proximal method.
If for some reason there is an proximal_conjugate implementation in a function class, this will be called directly and will not go to the parent class. The implementation here is correct.
However, there is an example where all this fails due to inline operation. See #914. This is related to SPDHG and this line. Basically input and output are the same causing problems in this line. Because, out, x and out  again are the same objects.  If we use an L2NormSquared, SPDHG will diverge due to this error. However, if a ScaledFunction is used, e.g., 5 * L2NormSquared then the proximal_conjugate of the ScaledFunction is used. Due to this proximal_conjugate implementation of the ScaledFucntion, the input and output are different objects and SPDHG will work. However this function is not needed since ScaledFunction is a child class of the Function class and the proximal method is sufficient.
I believe that this inline problem is very important and most probably there are other cases where this is appeared without knowing, maybe in the gradient method.

I suppose that #916 is one step in removing the proximal_conjugate from functions where there is no specific implementation of it?
Can you make sure every function we have has this checked?

[ ] ScaledFunction
[ ] SumFunction
[ ] SumFunction
[ ] SumScalarFunction
[ ] ConstantFunction
[ ] TranslateFunction
[ ] OperatorCompositionFunction
[ ] L1Norm
[ ] L2NormSquared
[ ] MixedL21Norm
[ ] TotalVariation
[ ] LeastSquares
[ ] KullbackLeibler
[ ] Rosenbrok

However, there is an example where all this fails due to inline operation. See #914. This is related to SPDHG and this line. Basically input and output are the same causing problems in this line. Because, out, x and out again are the same objects. If we use an L2NormSquared, SPDHG will diverge due to this error. However, if a ScaledFunction is used, e.g., 5 * L2NormSquared then the proximal_conjugate of the ScaledFunction is used. Due to this proximal_conjugate implementation of the ScaledFucntion, the input and output are different objects and SPDHG will work. However this function is not needed since ScaledFunction is a child class of the Function class and the proximal method is sufficient.
I believe that this inline problem is very important and most probably there are other cases where this is appeared without knowing, maybe in the gradient method.

This has nothing to do with the proximal_conjugate simplification you are talking about in this issue. I believe #914 is a different bug and I agree that this needs addressing ASAP.

Any progress here?


Clarify instructions for QGIS download for OSX / Mac to bypass notarization issue

Description
When installing QGIS on a Mac / OSX / MacOS you have to bypass the notarisation issue by using Control-Click and choose open on the menu. This is what we have on the page currently:
https://qgis.org/en/site/forusers/download.html

When working with novice users it often confuses them. I understand that QGIS is looking to notarise the installer to completely bypass the issue and I am not sure what the current status of this is.
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/218
https://github.com/qgis/QGIS/issues/32167
In the mean time, I suggest updating the text on the website. I am working with a client who needed to install QGIS on a Mac, and got confused. I explained what need to be done, and asked them what changes they suggested to clarify this.
He suggested this:

"Were it me, I’d probably format it slightly differently (I’m drawn to the big green button and not to the stuff below it, personally). Quick mock-up below of what would probably made me read it, with some slight change on the focus of the wording.
Hope this is useful; apologies if this is a bit OTT but I did a big UX project on exactly this sort of thing for a holiday rental business previously, so it’s sort of ingrained in me!"
Can we make these changes? What do you think?
Best wishes,
Nick.

Please see also https://lists.osgeo.org/pipermail/qgis-user/2023-November/053612.html

Latest changes

https://github.com/qgis/QGIS-Website/commit/5ba991c56d58bf401489c2b8c3484c7354b9c930

Also, how about tweaking the text slightly. I'm trying to put the most important stuff first:
On first launch, please control-click on the icon and choose Open from the context menu, after which a confirmation dialog is shown and you need to click the Open button. This is needed because QGIS is not yet notarized as required by macOS security rules. macOS High Sierra (10.13) or newer is required.

Another related issue report: https://github.com/qgis/QGIS/issues/55663.


Server side rendering: being able to trigger the search server side

Feature request
What is the current behavior?
Currently when rendering a react-instantsearch page with next it doesn't send a page with results already fetched from Algolia.
What is the expected behavior?
It would be great if this could be achieved without any configuration. Otherwise, it would be enough to provide a guide that explains how to do it (and change the API or the internals to make it possible, if needed).

@bobylito what is the status on that ? Is there any work in progress ? maybe an API design ? Thanks!

React InstantSearch has been moved here: https://github.com/algolia/react-instantsearch
This issue has either been rewritten or placed inside our backlog.


Do not copy text to clipboard after selecting

This behaviour was introduced in https://github.com/LukeSmithxyz/st/commit/683341140065b3096ee9e7e3e3b042f9c52230a6
Resolves: #177

@LukeSmithxyz I just noticed that you merged you merged a master branch from a fork. That means the fork can keep making changes without you having to approve for as long as he wants to.
This is a bad. PRs should always be from a branch not master.
I don't know exactly how to fix it, since you already merged, but would be best to reset to previous commit.
https://blog.jasonmeridth.com/posts/do-not-issue-pull-requests-from-your-master-branch/

That's not how Github works (that's not even what that site says).
The issue is that if he would've commit other things (before I merged it), those commits would appear in this PR and there'd be a high chance of me rejecting them because obviously they're not part of the fix.
But if I accept a PR from a master branch, that doesn't mean that new commits continue to merge after I select to merge the original commit.

Ah gotcha. That makes more sense. I stand corrected.
On Sat, Apr 4, 2020, 3:05 PM Luke Smith<EMAIL_ADDRESS>wrote:

That's not how Github works (that's not even what that site says).
The issue is that if he would've commit other things (before I merged it),
those commits would appear in this PR and there'd be a high chance of me
rejecting them because obviously they're not part of the fix.
But if I accept a PR from a master branch, that doesn't mean that new
commits continue to merge after I select to merge the original commit.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LukeSmithxyz/st/pull/183#issuecomment-609082288, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOKIUUFAY5YS2NZ5QQLCZTRK6HJ7ANCNFSM4LYYIZEQ
.


installing nstore

suggestion : can you tell why not step.js is included in your git. need to install seperately.
where i can find the pattern module.

The dependencies are specified in the package.json.  Either install nstore from npm or download nstore from github and then npm install from the nstore directory.


Remove mpich from host/run dependency of intel-fortran-rt

Intel Fortran supports CoArray feature which requires Intel MPI, and won't work correctly with MPICH.
There is no reason for that dependency. If a Python package is written in Fortran using Coarrays, and compiled using Intel Fortran compiler, the author of that package must specify run-time dependency on Intel MPI manually.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

conda-forge-admin, please rerender


Doesn't work with Safari, or am I missing something?

No idea.

Looks like no pollyfill required now as Safari supports Intersection Observer. Curious if you can use requestAnimationFrame with this library as we might wrap in FastDOM

I tested sal.js on Safari 12.1 and I can confirm it works. As you can see in Can I use.

Curious if you can use requestAnimationFrame with this library as we might wrap in FastDOM

@Mapiac can you elaborate more on that?


Replace macro with TypedDictionaryArray in comparison kernels

Which issue does this PR close?

Closes #2513.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

dict eq string          time:   [509.02 µs 509.31 µs 509.70 µs]
                        change: [-7.5163% -7.4216% -7.3388%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 100 measurements (10.00%)


Performance drop with fancyzones at 0.17

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.778]
PowerToys version: 0.17
PowerToy module for which you are reporting the bug (if applicable): FancyZones

After upgrading from 0.16.1 to 0.17 there is a noticeable performance drop in using fancyzones and also whole explorer seems slowed down. I now installed 0.16.0 and everything is nicely fluent. No other changes in configuration were made.

Can you provide the rest of the bug report? The repro steps, expected, and actual would be handy here, thanks!

Well there's no repro steps, I've just upgraded and noticed the performance issues.
Expected behavior is no performance issues and actual is that there is performance issues.
But maybe helps that it is most noticeable when I want to "move" - assign a window to a zone, it takes more time than before to show zones, and everything starts lagging, windows move slower and after I release the window it takes also some more time to hide zones and display windows normally (full opacity). So basically everything works as it should be way more slower.

@mariusrak So repro steps seem to be:

Start PowerToys, with FancyZones enabled
Drag a File Explorer window and hold shift/non-primary mouse button to activate zone overlay
Observe zone population hitches, takes ~a second to appear
Drag window to zone, observe window move is slow

I can't repro this but can you verify that's correct? Are you seeing the slowdown every time? Can you reproduce with all windows or only specific apps?

It happens with every window, not only file explorer window. Otherwise it's correct.

@mariusrak
have you tried turning off the transparency for the dragged window? Does it make any difference?

@enricogior
It makes a huge difference.  I have a triple monitor setup with UHD 620 and the performance just plummeted (I can see in Task Manager that GPU is overloaded when I move a windows around and try to assign in to a zone). However, after I turned off transparency and "show zones on all monitors", performance got back to an acceptable level.

@AntonIlinykh
in 0.18 we have a fix for the perfs issue with "show zones on all monitors", for the transparency, we call a Windows API, I suspect it's a video driver issue.

Sorry, seems like the problem is also in 0.16 when FZ is enabled for all monitors. But there is different behavio in 0.16 than in 0.17.
0.16 - zones overlay is slowly gaining opacity and after random time it assign window to zone.
0.17 - everything starts lagging and stuttering
I'll report after I try 0.18

We've done a bunch of improvements, do we still feel this is an issue?

I don't see any performance issues at all ... because it doesn't work :D The zones are highlighted but the windows do not snap in anymore.

I still see a huge frame drop when using fanzy zones with opacity turned on or off in version 0.72.0

After playing with various settings, I found that unchecking "Show zones on all monitors while dragging a window" gave the best performance improvements.