x/tools/cmd/godoc: list packages in the correct order

https://github.com/golang/go/wiki/CodeReviewComments#imports says that "Imports are organized in groups, with blank lines between them. The standard library packages are in the first group.".
However godoc simply sorts imports in lexicographical order.
This makes it very hard to find the documentation of a standard package.
The order should be:

standard library packages
golang.org/x/ packages
other packages

godoc sorts imports within groups.
If you want to maintain groups, use golang.org/x/tools/cmd/goimports.

Sorry, but what do you mean with "use golang.org/x/tools/cmd/goimports".
I'm referring to the package index available at http://localhost:6060/pkg/.
As you can see from https://imagebin.ca/v/2c2N6BhjBUmp, finding documentation for a standard package is quite a pain, since all third party package are interleaved with standard packages.

I'm sorry, I misunderstood your comment.  I don't understand your reference to the CodeReviewComments wiki page, as that has nothing to do with what godoc displays.
You are suggesting that godoc should sort the packages it displays differently.

CC @griesemer

I added a reference to CodeReviewComments because Go programmers expect to see packages listed in a well defined order, and this order is not respected by godoc.
However the real problem is that godoc package listing seems to be specialized for https://golang.org/pkg/.
Packages are listed in a section named "Standard library".  The problem is that when godoc is executed on a local system, all installed packages are considered part of the standard library.
One possible solution is to add an additional section, that it is only visible when there are third-party packages installed on the system.


LC gets Invalid decimal error while making mediated transfer

Thanks for filing a bug report :-)
Steps to Reproduce
Scenario
LC(browser) <==> CLI <==> LC(browser2)

Make a few transfers from CLI to browser2
Make a few mediated transfers from LC(browser) to LC(browser2)
Make mediated transfers from LC(browser2) to LC(browser)

Expected Result

LC(browser2) node should be able to perform mediated transfers to LC(browser)

Actual Result

LC browser2 logs
raiden_0xF087038D9032dc5e419C62dF32e865C2d160db2e_2021-03-10T13_39_07.848Z.log
raiden_0xF087038D9032dc5e419C62dF32e865C2d160db2e_2021-03-10T13_11_03.035Z.log
CLI logs
node-5d3c71-mainnet-10thMarch2021.log
LC browser logs
Unfortunately logs are empty

We performed a test by deleting all the databases from all the three nodes and starting fresh.
This was an infrastructure issue where the CLI took 762138 ms to sync. And after the sync the lightclient was able to make transfers both sides.
This might be because of our ethereum nodes which were slow to sync during that time.
2021-03-11T14:58:27.553Z [info] => action     {
  type: 'raiden/synced',
  payload: { tookMs: 762138, initialBlock: 10095771, currentBlock: 12017904 }
}


[MM-41281] Change crt tour trigger condition and save onBoarding auto tour status in preferences

Summary
Change CRT tour trigger condition and save onBoarding auto tour status in preferences
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-41281
Related Pull Requests
Webapp: https://github.com/mattermost/mattermost-webapp/pull/9289
Release Note
NONE

Thanks Ashish. I removed the QA deferred label as I'd like to have @jgilliam17 test this to ensure there are no issues with this conflicting with the regular onboarding tutorial.

/update-branch

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/109343

Thanks @AshishDhama
Tested, looks good to merge - pending E2E report.

CRT tour triggers only once for each user; Tour does not interfere with onboarding tutorial

/cherry-pick cloud

Cherry pick is scheduled.

/cherry-pick release-6.4

Cherry pick is scheduled.


re-introduce and rename cwd-proposal-multiple

This reintegrates Jake's changes from here: https://github.com/DA0-DA0/dao-contracts/pull/480/files#, updates with the latest deposit and renaming changes

Codecov Report
Base: 91.11% // Head: 91.07% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (4954cfe) compared to base (9e801cc).
Patch coverage: 81.50% of modified lines in pull request are covered.

:exclamation: Current head 4954cfe differs from pull request most recent head ef4ac40. Consider uploading reports for the commit ef4ac40 to get more accurate results

Additional details and impacted files
@@                Coverage Diff                @@
##           zeke/renaming     #499      +/-   ##
=================================================
- Coverage          91.11%   91.07%   -0.04%
=================================================
  Files                 33       37       +4
  Lines               3015     3565     +550
=================================================
+ Hits                2747     3247     +500
- Misses               268      318      +50

Impacted Files
Coverage Δ

...cts/proposal/cwd-proposal-multiple/src/proposal.rs
90.47% <ø> (ø)

...cts/proposal/cwd-proposal-multiple/src/contract.rs
90.38% <77.47%> (ø)

packages/cwd-voting/src/multiple_choice.rs
94.44% <90.47%> (ø)

...e-propose/cwd-pre-propose-multiple/src/contract.rs
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


updated animations

pls merge to updated-animation so thath playsound branch can be deleted

Playsound-Branch is now deleted


Template parameter Pre-CTS

Test the compatibility of current design with template parameter. Player is expected to parse pre-transformed arguments and emit player module.
If the current design cannot achieve the expected result, consider a new approach for such requirement.
A live test demo can be found here.

Not possible due to AST pre-transform completed by MediaWiki.


Latest plugin update killed my Kumo access through Homebridge

After installing the latest update, my accessories do not appear on Homebridge nor Homekit anymore. Reverting to previous version does not remedy the issue.
EDIT: reverting to .18 got my accessories back but had to install new child bridge

Can you post your logs? There’s not much to go on here.

It killed mine also - homebridge-kumo v1.8.21
[1/22/2022, 2:59:25 PM] ---
[1/22/2022, 2:59:25 PM] ====================
[1/22/2022, 2:59:25 PM] ERROR LOADING PLUGIN homebridge-kumo:
[1/22/2022, 2:59:25 PM] Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/lib/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js from /usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js not supported.
Instead change the require of /usr/lib/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js in /usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js to a dynamic import() which is available in all CommonJS modules.
at Object. (/usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js:6:18)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/kumo-api.js:7:41)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/platform.js:4:20)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/index.js:3:20)
at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:135:108)
at PluginManager.initializeInstalledPlugins (/usr/lib/node_modules/homebridge/lib/pluginManager.js:64:30)
at async Server.start (/usr/lib/node_modules/homebridge/lib/server.js:106:9)
[1/22/2022, 2:59:25 PM] ====================

Ok. I'm running Node.js Version 16.13.0, NPM 8.1.0, and Homebridge 1.4.0. Working fine here. I'll need to dig further.

Here is mine Looks identical)
[1/22/2022, 12:16:22 PM] ====================
[1/22/2022, 12:16:22 PM] ERROR LOADING PLUGIN homebridge-kumo:
[1/22/2022, 12:16:22 PM] Error [ERR_REQUIRE_ESM]: require() of ES Module /homebridge/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js from /homebridge/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js not supported.
Instead change the require of /homebridge/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js in /homebridge/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js to a dynamic import() which is available in all CommonJS modules.
at Object. (/homebridge/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js:6:18)
at Object. (/homebridge/node_modules/homebridge-kumo/dist/kumo-api.js:7:41)
at Object. (/homebridge/node_modules/homebridge-kumo/dist/platform.js:4:20)
at Object. (/homebridge/node_modules/homebridge-kumo/dist/index.js:3:20)
at Plugin.load (/usr/local/lib/node_modules/homebridge/lib/plugin.js:135:108)
at PluginManager.initializeInstalledPlugins (/usr/local/lib/node_modules/homebridge/lib/pluginManager.js:64:30)
at async Server.start (/usr/local/lib/node_modules/homebridge/lib/server.js:106:9)
[1/22/2022, 12:16:22 PM] ====================
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Saturday, January 22, 2022 at 15:03
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
It killed mine also - homebridge-kumo v1.8.21
[1/22/2022, 2:59:25 PM] ---
[1/22/2022, 2:59:25 PM] ====================
[1/22/2022, 2:59:25 PM] ERROR LOADING PLUGIN homebridge-kumo:
[1/22/2022, 2:59:25 PM] Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/lib/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js from /usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js not supported.
Instead change the require of /usr/lib/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js in /usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js to a dynamic import() which is available in all CommonJS modules.
at Object. (/usr/lib/node_modules/homebridge-kumo/node_modules/fetch-timeout/src/index.js:6:18)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/kumo-api.js:7:41)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/platform.js:4:20)
at Object. (/usr/lib/node_modules/homebridge-kumo/dist/index.js:3:20)
at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:135:108)
at PluginManager.initializeInstalledPlugins (/usr/lib/node_modules/homebridge/lib/pluginManager.js:64:30)
at async Server.start (/usr/lib/node_modules/homebridge/lib/server.js:106:9)
[1/22/2022, 2:59:25 PM] ====================
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks for looking into this. I am running
On HB version 1.4.0.
Also, Mitsubishi recently updated their iOS KUMO app, don't know if that could do anything.
Up To Date
From: Fraser Sim @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Saturday, January 22, 2022 at 16:34
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
Ok. I'm running Node.js Version 16.13.0, NPM 8.1.0, and Homebridge 1.4.0. Working fine here. I'll need to dig further.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Please try v1.8.22 which should take care of it. The bump in the version number to node-fetch caused this bug (not sure why it didn't affect my build). It is working now with the latest version (v3) of node-fetch.

Looks Good!   Thanks for taking care of this so quickly.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loaded homebridge-kumo v1.8.22 child bridge successfully
[1/23/2022, 8:42:05 AM] Loaded 3 cached accessories from cachedAccessories.0EF2A5C67892.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Living Room
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Den
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Bedroom
[1/23/2022, 8:42:05 AM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-kumo) is running on port 50703.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Kumo API: Successfully connected to the Kumo API.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Den
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P00x1F. Label: Bedroom
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Number of devices found: 3
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Completed login.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Restoring existing accessory from cache: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Living Room" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Den
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Den" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Bedroom
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Bedroom" as ductless unit.

Thank you very much for fixing this so quickly.
Working here again, too with 1.8.22
I did find this in the logs
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (PowerSwitch): set Active to true.
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Heater/Cooler): set Active from 0 to 1
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Fan): set Swing to 0.
[1/23/2022, 11:38:36 AM] [homebridge-kumo] queryDevice_Direct error: Time out on local IP connection..
[1/23/2022, 11:38:36 AM] [homebridge-kumo] Kumo API: Failed to send command directly to device (Serial: 9X34P008S100090F).
Looks like an automation was trying to run but failed. I’m sure this is unrelated to the previous issue but I thought I might mention it. Should I turn Direct Access off?
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Sunday, January 23, 2022 at 08:44
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
Looks Good! Thanks for taking care of this so quickly.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loaded homebridge-kumo v1.8.22 child bridge successfully
[1/23/2022, 8:42:05 AM] Loaded 3 cached accessories from cachedAccessories.0EF2A5C67892.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Living Room
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Den
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Bedroom
[1/23/2022, 8:42:05 AM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-kumo) is running on port 50703.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Kumo API: Successfully connected to the Kumo API.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Den
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P00x1F. Label: Bedroom
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Number of devices found: 3
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Completed login.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Restoring existing accessory from cache: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Living Room" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Den
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Den" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Bedroom
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Bedroom" as ductless unit.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I am seeing similar errors but my automations are running not sure if it’s just defaulting to cloud API.
 - David St. Hubbins
On Jan 23, 2022, 11:50 AM -0500, HaWi @.***>, wrote:

Thank you very much for fixing this so quickly.
Working here again, too with 1.8.22
I did find this in the logs
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (PowerSwitch): set Active to true.
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Heater/Cooler): set Active from 0 to 1
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Fan): set Swing to 0.
[1/23/2022, 11:38:36 AM] [homebridge-kumo] queryDevice_Direct error: Time out on local IP connection..
[1/23/2022, 11:38:36 AM] [homebridge-kumo] Kumo API: Failed to send command directly to device (Serial: 9X34P008S100090F).
Looks like an automation was trying to run but failed. I’m sure this is unrelated to the previous issue but I thought I might mention it. Should I turn Direct Access off?
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Sunday, January 23, 2022 at 08:44
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
Looks Good! Thanks for taking care of this so quickly.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loaded homebridge-kumo v1.8.22 child bridge successfully
[1/23/2022, 8:42:05 AM] Loaded 3 cached accessories from cachedAccessories.0EF2A5C67892.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Living Room
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Den
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Bedroom
[1/23/2022, 8:42:05 AM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-kumo) is running on port 50703.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Kumo API: Successfully connected to the Kumo API.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Den
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P00x1F. Label: Bedroom
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Number of devices found: 3
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Completed login.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Restoring existing accessory from cache: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Living Room" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Den
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Den" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Bedroom
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Bedroom" as ductless unit.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>

I checked and the appliance was already running, so the error may be generated by the fact that the appliance didn't turn on because it was already on.
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Sunday, January 23, 2022 at 11:52
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
I am seeing similar errors but my automations are running not sure if it’s just defaulting to cloud API.
 - David St. Hubbins
On Jan 23, 2022, 11:50 AM -0500, HaWi @.***>, wrote:

Thank you very much for fixing this so quickly.
Working here again, too with 1.8.22
I did find this in the logs
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (PowerSwitch): set Active to true.
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Heater/Cooler): set Active from 0 to 1
[1/23/2022, 11:38:34 AM] [homebridge-kumo] Dining Room (Fan): set Swing to 0.
[1/23/2022, 11:38:36 AM] [homebridge-kumo] queryDevice_Direct error: Time out on local IP connection..
[1/23/2022, 11:38:36 AM] [homebridge-kumo] Kumo API: Failed to send command directly to device (Serial: 9X34P008S100090F).
Looks like an automation was trying to run but failed. I’m sure this is unrelated to the previous issue but I thought I might mention it. Should I turn Direct Access off?
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Sunday, January 23, 2022 at 08:44
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
Looks Good! Thanks for taking care of this so quickly.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loaded homebridge-kumo v1.8.22 child bridge successfully
[1/23/2022, 8:42:05 AM] Loaded 3 cached accessories from cachedAccessories.0EF2A5C67892.
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Living Room
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Den
[1/23/2022, 8:42:05 AM] [homebridge-kumo] Loading accessory from cache: Bedroom
[1/23/2022, 8:42:05 AM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-kumo) is running on port 50703.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Kumo API: Successfully connected to the Kumo API.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P008xF. Label: Den
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Found device. Serial: 1834P00x1F. Label: Bedroom
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Number of devices found: 3
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Completed login.
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Restoring existing accessory from cache: Living Room
[1/23/2022, 8:42:06 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Living Room" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Den
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Den" as ductless unit.
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Restoring existing accessory from cache: Bedroom
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Using Kumo Cloud API for device control
[1/23/2022, 8:42:07 AM] [homebridge-kumo] Initializing "Bedroom" as ductless unit.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I checked and the appliance was already running, so the error may be generated by the fact that the appliance didn't turn on because it was already on.
Mine are running today as well - Good call.
Maybe I will add some logic if they are already powered on not to run.

Thank you, I don't think it’s critical, though.
From: FTI76 @.>
Reply-To: fjs21/homebridge-kumo @.>
Date: Sunday, January 23, 2022 at 13:53
To: fjs21/homebridge-kumo @.>
Cc: Hans Winkler @.>, Author @.***>
Subject: Re: [fjs21/homebridge-kumo] Latest plugin update killed my Kumo access through Homebridge (Issue #55)
I checked and the appliance was already running, so the error may be generated by the fact that the appliance didn't turn on because it was already on.
Mine are running today as well - Good call.
Maybe I will add some logic if they are already powered on not to run.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Enhance AbstractFileAsert#hasSameBinaryContentAs

I just found that the AbstractFileAssert#hasSameBinaryContentAs(File) method does the following.

Loads whole bytes of the expected file into memory(an array).
And compares byte by byte from two input streams,

one from the actual file
and the other is the in-memory cached byte array (from the expected file)

We can(should) do like this.

Pre-verify those files' sizes for a fast-fail manner, since comparing bytes from two different-sized files is meaningless.
Compare two binary sequences (as is), without reading all bytes (from the expected file)

        assertThat(decrypted)
                .hasSize(plain.length())        // not required when it's covered by the hasSameBinaryContentsAs
                .hasSameBinaryContentAs(plain); // should be more memory-friendly!

The AbstractPathAssert#hasSameBinaryCotentAs(Path) seems have the same problem.

Fair point, I completely agree


Support for parameter set selection by parameter value.

A common pattern with native binaries is to have a first parameter indicating some general command, and the rest of the commandline is options to that first command.
Like
p4 opened ...
git commit -a --amend

#pattern
exe command flag1 option2=1

Today, this is something that I find cumbersome to express in PowerShell, since the allowed verbs are often a mismatch with the command, and we have no nice way to match parameter sets with the value of a parameter. (It can be done with dynamic parameters, but that quickly becomes unwieldy and seems like an abuse of the feature).
I'd like to start a discussion to see if we can come up with a better way.
An initial suggestion is to allow an enum  or string parameter at the first position with a Parameter flag (here: ParameterSetSelector)be the selector of the parameter set.
enum SubCommandTypes {
    SomeSubCommand
   AnotherSubCommand
}

function Start-MainCommand {
    param(
        [Parameter(ParameterSetSelector=$true, Mandatory=$true)]
        [SubCommandTypes ] $Command
        ,
        [Parmameter(ParametersetName="SomeSubCommand")]
        [int] $Count
        ,
        [Parmameter(ParametersetName="AnotherSubCommand")]
        [int] $Size
    )
}
# or
function Start-MainCommand {
    param(
        [Parameter(ParameterSetSelector=$true, Mandatory=$true)]
        [ValidateSet("SomeSubCommand", "AnotherSubCommand")]
        [string] $Command
        ,
        [Parmameter(ParametersetName="SomeSubCommand")]
        [int] $Count
        ,
        [Parmameter(ParametersetName="AnotherSubCommand")]
        [int] $Size
    )
}

Thoughts?

@powercode Thanks for opening the discussion! I've waited a long time for this.
I think we should start with trying to formalize the description (notation, terms).
statement := command [parameterset]

parameterset := parametersetParameterList

parametersetParameterList := parametersetParameter parametersetParameterList

parametersetParameter  := Parameter [SubParameterlist]

SubParameterlist := parametersetParameterList

Parameter := valueParameter | Switch

cc @PowerShell/area-language

I would take this a step further and suggest that the value of the property could be inspected as well. Something like:
[Parameter(ParameterSetSelector="MyParamSetName", ConditionalValue=$true)]
        [Switch] $Command

This way you would support Start-MainCommand -Command:$myFlag, otherwise you would resolve the wrong set for Start-MainCommand -Command:$false.

What would the effect be of having a callback to user code to determine parameter set?
We have a few different scenarios that PowerShell doesn't handle well, and this could potentially open up for handling the more difficult cases.
I'm thinking in the way of an attribute on Cmdlet, [ParameterSetResolver(typeof(MyResolver))].


feat(#minor): Updated euler-finance schema to 2.0.1

Deployment here:
https://okgraph.xyz/?q=jaimehgb%2Feuler
Updated the schema to 2.0.1, which is the addition of a few fields and counters, and account positions. All the position’s code I brought from AAVE subgraph, but let me know if I should have used a more recent reference.
When a market is created, I start tracking the Debt and Collateral tokens transfers to avoid position not found errors when withdrawing, repaying and liquidating. But they still come up from time to time.

@jaimehgb/@bye43 At this point we don't want to do this, but was there a reason we chose to go with the 2.0.1 schema over the 3.0.0 schema?

@jaimehgb / @bye43 At this point we don't want to do this, but was there a reason we chose to go with the 2.0.1 schema over the 3.0.0 schema?

When looking at both to see which one to go for I saw that from 1.7.0, the work needed for 2.0.1 was already part of the work for 3.0.0. Even if we go for 3.0.0 now, these additions will mostly remain the same.

@jaimehgb / @bye43 At this point we don't want to do this, but was there a reason we chose to go with the 2.0.1 schema over the 3.0.0 schema?

When looking at both to see which one to go for I saw that from 1.7.0, the work needed for 2.0.1 was already part of the work for 3.0.0. Even if we go for 3.0.0 now, these additions will mostly remain the same.

I suppose one benefit of skipping to 3.0.0 is to utilize Dylan's lending sdk.

I suppose one benefit of skipping to 3.0.0 is to utilize Dylan's lending sdk.

That is a good point indeed 🤔
But wouldn’t it have required an important refactor to the whole euler?

Also, I’m ignoring the Address lowercase lint warning for this one. Because we are using a couple of them as IDs for entities, and prefer not to mess up

unique users data looks good. this should be good to go, unless there is further code review.

One question about the need to search for open positions; otherwise looks good.
the other euler PR: https://github.com/messari/subgraphs/pull/2065 (to be merged soon)

Euler is dead, this work is not needed anymore


Not working on macOS 11.2.1

Following your instructions the command ./autogen.sh complete without errors.
The command ./configure, make and make install don't exist (command not found).
Any chance to have an update? Thanks

sounds like a watchman issue.


Memory not being released on destroying activity

I have observed that when activity is destroyed then all the instances of the library code are not finished and thus the memory taken by library code isn't released.
Could you please look into it.

Hey, how do you know this is happening?
Feel free to send a pull request.

I use your library as an item in my RecyclerView in an Activity.
Below is my LeakCanary info:
ApplicationLeak(className=com.abc.ArticleDetailActivity, leakTrace=
┬
├─ org.chromium.device.power_save_blocker.PowerSaveBlocker
│    Leaking: NO (a class is never leaking)
│    GC Root: Global variable in native code
│    ↓ static PowerSaveBlocker.b
│                              ~
├─ java.util.HashMap
│    Leaking: UNKNOWN
│    ↓ HashMap.table
│              ~~~~~
├─ java.util.HashMap$Node[]
│    Leaking: UNKNOWN
│    ↓ array HashMap$Node[].[0]
│                           ~~~
├─ java.util.HashMap$Node
│    Leaking: UNKNOWN
│    ↓ HashMap$Node.key
│                   ~~~
├─ com.pierfrancescosoffritti.androidyoutubeplayer.core.player.views.WebViewYouTubePlayer
│    Leaking: YES (View.mContext references a destroyed activity)
│    mContext instance of com.abc.ArticleDetailActivity with mDestroyed = true
│    View#mParent is null
│    View#mAttachInfo is null (view detached)
│    View.mWindowAttachCount = 2
│    ↓ WebViewYouTubePlayer.mContext
╰→ com.theepochtimes.news.features.articledetails.ArticleDetailActivity
     Leaking: YES (WebViewYouTubePlayer↑ is leaking and Activity#mDestroyed is true and ObjectWatcher was watching this)
     key = 4ee2961d-1584-4a7a-8eab-d2c91687a56a
     watchDurationMillis = 6575
     retainedDurationMillis = 1567
, retainedHeapByteSize=295071)

Hello,
This problem can be reproduced in Sample App.
After adding debugImplementation 'com.squareup.leakcanary:leakcanary-android:2.0-beta-3' into build.gradle of core-sample-app, launch "ayp API" and click "Fragment Example". Then press back key to go back to main page. You will see leakcanary reports the leak(refer to the attachment).

Thanks for the info. These days I don't have much time to work on the library, pull requests are welcome!

I use your library as an item in my RecyclerView in an Activity. Maybe you need to check the internal webview.
Below is my LeakCanary info:
ApplicationLeak(className=com.abc.ArticleDetailActivity, leakTrace=
┬
├─ org.chromium.device.power_save_blocker.PowerSaveBlocker
│ Leaking: NO (a class is never leaking)
│ GC Root: Global variable in native code
│ ↓ static PowerSaveBlocker.b
│ ~
├─ java.util.HashMap
│ Leaking: UNKNOWN
│ ↓ HashMap.table
│ ~~~~~
├─ java.util.HashMap$Node[]
│ Leaking: UNKNOWN
│ ↓ array HashMap$Node[].[0]
│ ~~~
├─ java.util.HashMap$Node
│ Leaking: UNKNOWN
│ ↓ HashMap$Node.key
│ ~~~
├─ com.pierfrancescosoffritti.androidyoutubeplayer.core.player.views.WebViewYouTubePlayer
│ Leaking: YES (View.mContext references a destroyed activity)
│ mContext instance of com.abc.ArticleDetailActivity with mDestroyed = true
│ View#mParent is null
│ View#mAttachInfo is null (view detached)
│ View.mWindowAttachCount = 2
│ ↓ WebViewYouTubePlayer.mContext
╰→ com.abc.ArticleDetailActivity
 Leaking: YES (WebViewYouTubePlayer↑ is leaking and Activity#mDestroyed is true and ObjectWatcher was watching this)
 key = 4ee2961d-1584-4a7a-8eab-d2c91687a56a
 watchDurationMillis = 6575
 retainedDurationMillis = 1567
, retainedHeapByteSize=295071)

same problem with me

how to resolve it?

I'm also seeing the same issue reported by Logcat on Android Studio. A workaround that seems to work is to override onStop in my fragment as follows
override fun onStop() {
        super.onStop()
        youtubePlayerView.release()
    }

I understand this is not the best option as I'm doing more than needed but at least it unregisters the networkListener
Proposed fix is to simply call context.unregisterReceiver(networkListener) in the onStop method of LegacyYoutubePlayerView ...
@PierfrancescoSoffritti I have created a PR for a proposed fix... this is my 1st PR ever to an open-source project so I hope I'm doing things right.
Regards,
Adam

This leak should be fixed in version 12.0.0 of the library.


Drop peers after failing to send messages to them

Description
I'm seeing ~200k/hr p2p warnings about "failed sending" messages from the managed testnet nodes (see screenshot below). This happens when a node tries to propagate a gossip message to a peer, and fails. I think this error is happening so often because nodes never drop peers after such an error. Ideally, a node should drop a peer--in the case of connection not found in cpool, probably right away, and replace it with a healthy peer.
Affected code

https://github.com/spacemeshos/go-spacemesh/blob/a3ba021480a2aa5ed9b88d9d2c1f62dbddf7c1f1/p2p/gossip/protocol.go#L145
This issue appears in commit hash: v0.1.29, a3ba021480a2aa5ed9b88d9d2c1f62dbddf7c1f1
Related files (optionally with line numbers):

So in the codebase if writer fails https://github.com/spacemeshos/go-spacemesh/blob/develop/p2p/net/conn.go#L285-L297 it will notify switch https://github.com/spacemeshos/go-spacemesh/blob/develop/p2p/switch.go#L217-L218 which will call Disconnect. We definitely don't need to add another disconnect in the protocol, as this mechanism already exists.
But there is probably something wrong with it, the code didn't change much between https://github.com/spacemeshos/go-spacemesh/commit/a3ba021480a2aa5ed9b88d9d2c1f62dbddf7c1f1 and current develop.

For reads there is similar code flow that will propagate notifications and close connection if reader failed.

I experimented with the change https://github.com/spacemeshos/go-spacemesh/pull/2490 on a devnet with 50 nodes. By disconnecting multiple peers periodically. "expired peer" log was consistently observed, but never "failed sending".
I assume that the issue is fixed. It is still possible that sometimes "failing sending" will be observed because peers are not updates synchronously when the connection is dropped, but it won't be at a reported rate.


Add unit test for bitcoin_merkle_root functions

We test bitcoin_merkle_root over in the blockdata::block module.
Although the bitcoin_merkle_root and bitcoin_merkle_root_inline
functions are almost identical there is enough index manipulation done
that it is not immediately obvious that the code is error free.
Add a unit test that verifies that the two functions return the same
resulting merkle root.
This was done in response to #394.

Also while useful, I think it'd be even better to somehow unify the two functions so same logic would always be guaranteed.

I don't think we can. If I understand correctly bitcoin_merkle_root_inline is a memory optimised version so we don't allocate each recursive loop. Its not possible to do this and still have an API that accepts an iterator.

ACK e04795093f06b31cb50f874a2ddd365757dbcac5


Return deepcopy of the object

https://github.com/rancher/rancher/issues/28863

https://github.com/rancher/rancher/issues/29047


Service Account does not have storage.buckets.get access to the Google Cloud Storage bucket

My setup can create database, network and K8S, but fails to create a bucket.
I have given roles/storage.admin to my service account.
gcloud projects add-iam-policy-binding $PROJECT_ID --member "serviceAccount:$SERVICE_ACCOUNT" --role="roles/storage.admin"

When  I apply https://raw.githubusercontent.com/crossplane/provider-gcp/master/examples/storage/bucket.yaml  I get the following issue complaining that the service account has not the needed permissions.
  Type     Reason                         Age                 From                                      Message
  ----     ------                         ----                ----                                      -------
  Warning  CannotObserveExternalResource  19s (x29 over 23m)  managed/bucket.storage.gcp.crossplane.io  cannot get GCP bucket attributes: googleapi: Error 403<EMAIL_ADDRESS>does not have storage.buckets.get access to the Google Cloud Storage bucket., forbidden

I have triple checked and tried a few time resetting my env, and don't see what I am missing.

oooh, That message was very confusing does not have storage.buckets.get access to the Google Cloud Storage bucket
Actually, the external-name was the issue
  annotations:
    crossplane.io/external-name: crossplane-example-bucket

crossplane-example-bucket was already existing, and a bucket name has to be globally unique.

Changing the external to a non existing one made it work.
Closing.


subscriber: fix busy loop in aggregator task

currently, there's an issue where the console-subscriber background
aggregator task busy-loops, using 100% CPU time. this is because it's
currently awaiting a recv call on the events channel on every
iteration of the aggregate loop...and events are generated when a task
is exited. this includes the aggregator task! so, when the aggregator
task has finished a poll, the subscriber sends an exit message...which
wakes the aggregator task back up.
this branch fixes the issue by changing the aggregator task to not
include new messages on the events channel in the select! that will
wake up the aggregator. instead, it allows messages to be buffered, and
drains all events in the channel whenever it's woken by something else.
to avoid losing events due to a full buffer, i've also added a "high
water line" where the TasksLayer will notify the aggregator task after
a send, if the channel is approaching its maximum capacity (with some
wiggle room). now, the aggregator is woken in the following cases:

the data flush interval has elapsed
a new client has subscribed
the event buffer is nearing capacity

and the buffer is drained before going back to sleep in all these cases.
this should avoid the busy loop and prevent the aggregator from
monopolizing CPU time.
we can probably also shrink the event buffer a bit now that we're always
woken when nearing capacity...

cc @LucioFranco let me know if this fixes the issue you're seeing?


Combine same-type same-filename outputs

Working on the new layout it occurs that sometimes scripts may output alternate types for the same file. The obvious example would be a script generating figures which might output both .png and .svg versions of the same plot.
I think it would be nice if a file of the same sort (e.g. image) is available with the same filename but different extension to group these together in a single visual item int the interface (with an precendence order determining which is displayed).
We could support toggling between the alternatives but the main thought would be to provide a download drop down that lists the two formats ("Download as .png" etc.)

:+1:
I'm for it. I would like to revisit the file detection and grouper though to see if we could make it more dynamic to user's needs. The idea is more like an admin interface to customize what is detected and add new detection routines (just simple regex stuff). We fetch these entries on app loading to avoid hitting the database everytime a file is checked.

Moving to the Wooey repo.


Misalignment of text inside a card in features section

Describe the bug
The text inside the card with title "Multi Bit Buses and components" in the features section of home page is not aligned properly with the left card.
To Reproduce
Steps to reproduce the behavior:

Go to 'circuitverse.org'
Scroll down to the Features section
See error

Expected behavior
The text should be properly aligned with the left card.
Screenshots

Are you working on this issue? (Yes/No)
Yes, I have fixed this issue, let me know if I should open a PR.

I'm currently working on this issue

yes @sakkshm26 i you have already fixed the issue , you can open a pr linking this issue .


Girlscript Summer of Code Introduction/Tracking

👋 Hi @GameSphere-MultiPlayer,
I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you :octocat:

[x] #6
[x] #7
[ ] #8
[x] #9
[x] #10

please assign this task i am good in web dev and done some projects

Can You please assign this issue to me

Hello Admin, I would like work on creating a Code of Conduct file for your repository that aligns with guidelines. Kindly assign this to me


@Schema.example only works for Strings

I'm using annotations 2.X. I've got this annotation for a class:
    public static class Foo {
        @Schema(example = "myExampleSessionId")
        @JsonProperty("session_id")
        private EntityId sessionId;

        @Schema(example = "myExampleString")
        private String myString;
    }

It renders to this JSON:
EntityId": {
"type": "object",
"properties": {
"bytes": {
"type": "array",
"items": {
"type": "string",
"format": "byte"
}
},
"created": {
"type": "integer",
"format": "int64"
}
}
},

Foo": {
"type": "object",
"properties": {
"session_id": {
"$ref": "#/components/schemas/EntityId"
},
"myString": {
"type": "string",
"example": "myExampleString"
}
}
}

Notice that there's no "example" parameter associated with "session_id." But the example for the String parameter worked fine.
What I would expect would be this:
Foo": {
"type": "object",
"properties": {
"session_id": {
"$ref": "#/components/schemas/EntityId",
"example": "myExampleSessionId"
},
"myString": {
"type": "string",
"example": "myExampleString"
}
}
}

Is this a bug, or is there something I need to do differently with my annotations?

Can't work that way, because that's not a valid definition. You can't add additional properties alongside a $ref.

The thing is, the properties aren't parsing within the ref, either. i.e. there's no "example" parameter inside the Foo object. Is there something I need to do to get those to parse correctly?

Or is there another way to define an example for a $ref?

Did you define the example inside EntityId?

I didn't. Will give that a try.

That worked! Thanks.

Great. Is there anything else or can we close the ticket?


[Feature Request] Support music file

Must not be passed to youtube_dl to process FilePath-like.

What music url means?
@AkiaCode

ex ) https://localhost:3000/muisc.mp3
@kijk2869

ex ) https://localhost:3000/muisc.mp3
@kijk2869

Already supported 😃

oh, okay

Local File Path is not supported.

sorry


Fix Yarn container log and livy submission log fetcher issues

java.lang.RuntimeException: /home/travis/.azure/azureProfile.json (No such file or directory)
	at com.microsoft.azure.spark.tools.http.AzureOAuthTokenFetcher.buildFromAzureCli(AzureOAuthTokenFetcher.java:41)

Codecov Report

Merging #16 into master will increase coverage by 4.1%.
The diff coverage is 82.83%.

@@            Coverage Diff             @@
##             master     #16     +/-   ##
==========================================
+ Coverage      62.7%   66.8%   +4.1%
+ Complexity      383     359     -24
==========================================
  Files            62      57      -5
  Lines          1606    1440    -166
  Branches         90      90
==========================================
- Hits           1007     962     -45
+ Misses          540     423    -117
+ Partials         59      55      -4

Impacted Files
Coverage Δ
Complexity Δ

...crosoft/azure/spark/tools/http/HttpObservable.java
74.79% <ø> (-1.63%)
38 <0> (-2)

.../tools/restapi/yarn/rm/apps/appid/AppResponse.java
100% <ø> (ø)
2 <0> (?)

...api/yarn/rm/apps/appid/appattempts/AppAttempt.java
30% <ø> (ø)
3 <0> (?)

...re/spark/tools/restapi/yarn/rm/apps/appid/App.java
10.81% <0%> (ø)
4 <0> (?)

...stapi/livy/batches/api/batchid/GetLogResponse.java
20% <0%> (-20%)
2 <1> (ø)

...zure/spark/tools/job/ArcadiaSparkBatchFactory.java
83.33% <100%> (+20.83%)
3 <1> (ø)
:arrow_down:

...m/microsoft/azure/spark/tools/utils/LaterInit.java
100% <100%> (ø)
13 <4> (+3)
:arrow_up:

...rm/apps/appid/appattempts/AppAttemptsResponse.java
100% <100%> (ø)
2 <0> (?)

...ft/azure/spark/tools/job/HdiSparkBatchFactory.java
83.33% <100%> (+44.87%)
3 <1> (ø)
:arrow_down:

.../spark/tools/processes/SparkJobLogInputStream.java
81.48% <100%> (+9.14%)
6 <1> (-7)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 001739f...b84b493. Read the comment docs.


Issue with k8s.io/de/docs/tasks/tools/install-minikube/

This is a Bug Report
Problem:
The command "brew cask install minikube" does not work anymore.
Proposed Solution:
Now it is only possible to install minikube with this command: "brew install minikube"
Page to Update:
https://kubernetes.io/de/docs/tasks/tools/install-minikube/

Thank you for reporting this @leifwenzel. Die deutsche Lokalisierung ist nicht aktuell / the German localization is outdated.
/language de
/kind cleanup
/priority backlog

/assign


Disambiguate Byte

There seems to be an ambiguity between Init.Byte and Strings.Byte in the stdlib that breaks MetaCoq's compilation on my computer.

Right, I didn’t notice even a warning, thanks !


WSA redirect to Windows apps

Added a "redirect to Windows apps" section to the WSA page describing how to launch Windows file/protocol handlers from Android apps. This includes WSA's implicit redirection and the new LAUNCH_URI intent action.
I also removed a description of WSA's software-backed file encryption since we removed that support due to userdata corruption issues and lack of real security without a hardware keystore.
I also added (TM) superscripts to all name drops of WSA in the documentation since we were doing that inconsistently. We don't use the (TM) superscript on any name drop of Android outside of the WSA name, so we should probably do that, but it wasn't clear if that was intentional since we consistently didn't do it.

Thanks for making these updates @kevinkieselbach! Merging them in - should be live within an hour.


fix(tools): load pfv4 fonts in demo

What I did

nice up the dev server demo, with some internal refactors
use PFv4 fonts in dev server
remove the site.tagPrefix option from same, move it to the root of the options objs
add a hamburger icon to pfe-icon (don't learn from the implementation here, we'll eventually replace it with something nicer)
fix/improve some component demos

Notes to reviewers
the dev server demos and the netlify dp demos should be visually equivalent, except for the main header

Not sure if this is really a blocking issue.  But when you click on a component demo from the nav, a new page loads, and focus returns to the top of the nav on the first nav item, not the top of the page itself.  I feel like this is most likely an accessibility error.   After page load I would assume focus is on the document, usually followed by a skip-nav link which could skip the header links (logo/github) and then place focus on the main navigation.  This gives the user the option to click a header link after page load.  There is also a visual style applied with :focus-visible which almost makes it look like an active page indicator.

@zeroedin I spun that out to a new issue, let's merge this to unblock the next two prs


Get previous route (yew router)

Question
does Yew Router provide to get the previous route like react-router-last-location?
I haven't seen anything in the documentation about it

No, the router does not keep track of the history. The state and history is handled by the Javascript History API which only allows access to the current state (that's also the reason why react-router-last-location has that big disclaimer "Last location != Previous browser history state").
You can however manually keep track of the previous route. To do this you can connect to the RouteAgent which will notify you whenever the route is changed.
You can then keep track of the current route and assign it to the previous route whenever the route changes.
Here's a complete example:
use std::mem;
use wasm_bindgen::prelude::*;
use yew::{html, Component, ComponentLink, Html, ShouldRender};
use yew_router::{
    agent::RouteAgentBridge, components::RouterButton, route::Route, service::RouteService, Switch,
};

#[derive(Debug, Switch, Clone)]
pub enum AppRoute {
    #[to = "/a/{anything}"]
    A(String),
    #[to = "/b/{anything}"]
    B(String),
    #[to = "/c"]
    C,
}

type AppRouterButton = RouterButton<AppRoute>;

pub enum Msg {
    UpdateRoute(Route<()>),
}

pub struct Model {
    _route_agent: RouteAgentBridge,
    route: Route,
    previous_route: Option<Route>,
}
impl Component for Model {
    type Message = Msg;
    type Properties = ();

    fn create(_: Self::Properties, link: ComponentLink<Self>) -> Self {
        let callback = link.callback(Msg::UpdateRoute);
        let route_agent = RouteAgentBridge::new(callback);

        let route = RouteService::new().get_route();

        Self {
            _route_agent: route_agent,
            route,
            previous_route: None,
        }
    }

    fn update(&mut self, msg: Self::Message) -> ShouldRender {
        match msg {
            Msg::UpdateRoute(route) => {
                let old_route = mem::replace(&mut self.route, route);
                self.previous_route = Some(old_route);
                true
            }
        }
    }

    fn change(&mut self, _: Self::Properties) -> ShouldRender {
        false
    }

    fn view(&self) -> Html {
        html! {

                    <AppRouterButton route=AppRoute::A("lorem".to_string())>{ "A" }</AppRouterButton>
                    <AppRouterButton route=AppRoute::B("hello".to_string())>{ "B" }</AppRouterButton>
                    <AppRouterButton route=AppRoute::C>{ "C" }</AppRouterButton>

                    { format!("current route: {:#?}", self.route) }

                    { format!("previous route: {:#?}", self.previous_route) }

        }
    }
}

#[wasm_bindgen(start)]
pub fn run_app() {
    yew::start_app::<Model>();
}

Note: This example only keeps track of the previous route, it does not store the entire history. If you need that functionality you need to store the routes in a vector.

I think that is what I need. Thanks a lot!


ggd-run.sh error when installing sacCer3 genome data: "can't open file '/bin/python': [Errno 2] No such file or directory"

Hello,
I'm getting the error from the title, when installing the sacCer3 genome data in a freshly created Bcbio install.
I'm guessing the sacCer3 ggd recipe needs fixing (https://github.com/chapmanb/cloudbiolinux/blob/master/ggd-recipes/sacCer3/seq.yaml). It was last modified in 2019, in order to fix a previous issue (https://github.com/bcbio/bcbio-nextgen/issues/2758).
Not sure why this error started happening now. Installing the genome data worked fine in bcbio v1.2.8.
Here's what I'm running now:
## install bcbio-nextgen
## online documentation: https://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html
cd ${HOME}
wget https://raw.githubusercontent.com/bcbio/bcbio-nextgen/master/scripts/bcbio_nextgen_install.py
python3 bcbio_nextgen_install.py ${HOME}/bcbio-nextgen-TEST --tooldir=${HOME}/bcbio-nextgen-TEST/tools --nodata --mamba
## add the locations to the bcbio-nextgen dependency executables to the system's $PATH variable
export PATH=${HOME}/bcbio-nextgen-TEST/anaconda/bin:${HOME}/bcbio-nextgen-TEST/tools/bin:$PATH

## download genome data for sacCer3
bcbio_nextgen.py upgrade -u skip --genomes sacCer3 --aligners bwa --aligners bowtie2 --aligners hisat2 --aligners star

And this is the stack trace:
Saccharomyces_cerevisiae.R64-1-1.dna.toplevel.fa.gz                    100%[==========================================================================================================================================================================>]   3.61M  4.54MB/s    in 0.8s

2022-05-18 10:03:14 (4.54 MB/s) - written to stdout [3786555]

/home/test/bcbio-nextgen-TEST/anaconda/envs/python2/bin/python: can't open file '/bin/python': [Errno 2] No such file or directory
Traceback (most recent call last):
  File "/home/test/bcbio-nextgen-TEST/anaconda/bin/bcbio_nextgen.py", line 228, in <module>
    install.upgrade_bcbio(kwargs["args"])
  File "/home/test/bcbio-nextgen-TEST/anaconda/lib/python3.7/site-packages/bcbio/install.py", line 109, in upgrade_bcbio
    upgrade_bcbio_data(args, REMOTES)
  File "/home/test/bcbio-nextgen-TEST/anaconda/lib/python3.7/site-packages/bcbio/install.py", line 361, in upgrade_bcbio_data
    args.cores, ["ggd", "s3", "raw"])
  File "/home/test/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 354, in install_data_local
    _prep_genomes(env, genomes, genome_indexes, ready_approaches, data_filedir)
  File "/home/test/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 480, in _prep_genomes
    retrieve_fn(env, manager, gid, idx)
  File "/home/test/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 875, in _install_with_ggd
    ggd.install_recipe(os.getcwd(), env.system_install, recipe_file, gid)
  File "/home/test/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/ggd.py", line 30, in install_recipe
    recipe["recipe"]["full"]["recipe_type"], system_install)
  File "/home/test/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/ggd.py", line 62, in _run_recipe
    subprocess.check_output(["bash", run_file])
  File "/home/test/bcbio-nextgen-TEST/anaconda/lib/python3.7/subprocess.py", line 411, in check_output
    **kwargs).stdout
  File "/home/test/bcbio-nextgen-TEST/anaconda/lib/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bash', '/home/test/bcbio-nextgen-TEST/genomes/Scerevisiae/sacCer3/txtmp/ggd-run.sh']' returned non-zero exit status 2.

Below is the content of the ggd-run.sh script:
test@server-bioinfo:~$ cat /home/test/bcbio-nextgen-TEST/genomes/Scerevisiae/sacCer3/txtmp/ggd-run.sh
#!/bin/bash
set -eu -o pipefail
export PATH=/home/test/bcbio-nextgen-TEST/tools/bin:$PATH
RELEASE=94
BUILD=sacCer3
url=ftp://ftp.ensembl.org/pub/release-$RELEASE/fasta/saccharomyces_cerevisiae/dna/Saccharomyces_cerevisiae.R64-1-1.dna.toplevel.fa.gz
mkdir -p seq
wget -O - --no-check-certificate https://gist.githubusercontent.com/chapmanb/a973558c2ec67a57eb4592c709ec0d09/raw/81d398fd7f3c901f89753d4f9f39c5a87d05a7fa/sacCer3.chrom.sizes | cut -f 1 > sacCer3.chrom.sizes
wget -c --no-check-certificate https://raw.githubusercontent.com/kwongj/sort-contigs/master/sort-contigs.py
wget --no-check-certificate -O - $url | gunzip -c | python -c 'import sys; [sys.stdout.write(">chr%s\n" % (l[1:].split()[0].replace("Mito", "M")) if l.startswith(">") else l) for l in sys.stdin]' > seq/$BUILD.fa.orig
`bcbio_conda env list | grep python2 | awk '{print $2"/bin/python"}'` sort-contigs.py seq/$BUILD.fa.orig --out seq/$BUILD.fa --fmt fasta --order sacCer3.chrom.sizes
samtools faidx seq/$BUILD.fa
picard -Xms1g -Xmx3g CreateSequenceDictionary REFERENCE=seq/$BUILD.fa OUTPUT=seq/$BUILD.dict SPECIES=$BUILD

Sure enough, there is no /bin/python on my system, there is only /bin/python3:
test@server-bioinfo:~$ ls -lh /bin/python
ls: cannot access '/bin/python': No such file or directory

test@server-bioinfo:~$ ls -lh /bin/python3
lrwxrwxrwx 1 root root 9 Mar 13  2020 /bin/python3 -> python3.8

@amizeranschi  please try again - I've made a fix

what is your
which python2
echo $PATH

python2 should be there if you have installed bcbio and added bcbio/anaconda/bin:bcbio/tools/bin to PATH

@naumenko-sa  In that case, it looks like the problem is there is no python2 in our $PATH, although we do have the 2 bcbio bin directories:
test@server-bioinfo:~$ echo $PATH
/home/test/bcbio_nextgen_maria/anaconda/bin:/home/test/bcbio_nextgen_maria/tools/bin:/home/test/bcbio_nextgen_maria/extra3/bin:/home/test/bcbio_nextgen_maria/extra_conda2/bin:/sbin:/bin:/usr/bin:/usr/local/bin:/snap/bin

test@server-bioinfo:~$ ls -lh /home/test/bcbio_nextgen_maria/anaconda/bin/python2*
ls: cannot access '/home/test/bcbio_nextgen_maria/anaconda/bin/python2*': No such file or directory

test@server-bioinfo:~$ ls -lh /home/test/bcbio_nextgen_maria/tools/bin/python2*
ls: cannot access '/home/test/bcbio_nextgen_maria/tools/bin/python2*': No such file or directory

Hi! I was able to install the genome by creating a symlink like this:
  ln -s /bcbio/install/path/anaconda/envs/python2/bin/python  /bcbio/install/path/tools/bin/python2

It is great that it has been solved, so we were able to install sacCer3 in the end?
cloudbiolinux when installing is making symlinks for envs into tools/bin:
https://github.com/chapmanb/cloudbiolinux/blob/master/cloudbio/package/conda.py#L124
If your installation did not finish successfully, other files could remain unlinked and some workflows may not be working.

@naumenko-sa
Thanks a lot for looking into this.

If your installation did not finish successfully, other files could remain unlinked and some workflows may not be working.

This is a very good point. What else should we be looking for in there? I can send you a list of the contents of our bcbio/tools/bin, in case this helps.
As far as we could see from the logs, the installation DID finish successfully, we didn't get any errors, but the python2 binary just didn't get linked into bcbio/bools/bin automatically, thus, we had to create it ourselves to solve the issue mentioned above.
Have you also tested this yourself, in a fresh install, and did you end up having python2 symlinked in bcbio/tools/bin?

@amizeranschi
You are right- python2 was not linked since it is not a package.
I added linking here - please give it a try
https://github.com/chapmanb/cloudbiolinux/blob/master/cloudbio/package/conda.py#L138

I just noticed now that I forgot to reply here. This issue is fixed.


⚠ WSINGRESOS - GENERICO has degraded performance

In 95b610d, WSINGRESOS - GENERICO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsGenericoPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 24973 ms

Resolved: WSINGRESOS - GENERICO performance has improved in 61468a7.


Adding legals mentions (Privacy policy | Terms of use)

Inspirations

https://remoteok.com
www.glassdoor.com/

Here is a possible draft:
Legals/Privacy Policy or Terms of Use for jobsika.cm
jobsika.cm is a website that allows people to anonymously rate their companies and share their salaries, as well as to post and apply for jobs in Cameroon. It is operated by the Open Source Software Cameroon (OSSCameroon) community, a non-profit organization that promotes open source software development and collaboration in Cameroon.
By using jobsika.cm, you agree to the following terms and conditions:
User Content
You are solely responsible for any content that you submit, post, or display on jobsika.cm, including ratings, reviews, salaries, comments, job applications, and any other information or materials. You represent and warrant that you have the right and authority to share such content and that it does not violate any laws, regulations, or third-party rights.
You grant jobsika.cm a non-exclusive, royalty-free, worldwide, perpetual, irrevocable, and sublicensable license to use, reproduce, modify, distribute, display, and perform your content for the purposes of providing and improving the website and its services.
You acknowledge and agree that jobsika.cm does not endorse, verify, or guarantee the accuracy, reliability, or quality of any user content. You also acknowledge and agree that jobsika.cm may remove, edit, or disable any user content at any time and for any reason at its sole discretion.
Job Posting and Application
If you are an employer or a recruiter who wants to post a job on jobsika.cm, you agree to the following:

You will provide accurate and complete information about the job opportunity, the company, and the application process.

You will not post any job that is illegal, fraudulent, discriminatory, abusive, offensive, or otherwise inappropriate.

You will not charge any fees or require any payment from job seekers for applying or accessing your job posting.

You will respect the privacy and confidentiality of job seekers and their personal information.

You will not use jobsika.cm for any purpose other than recruiting qualified candidates for your job opportunity.

If you are a job seeker who wants to apply for a job on jobsika.cm, you agree to the following:

You will provide accurate and truthful information about your qualifications, skills, experience, and availability.

You will not submit any false, misleading, or fraudulent information or documents.

You will not apply for any job that you are not qualified for or interested in.

You will not use jobsika.cm for any purpose other than finding suitable employment opportunities.

You acknowledge and agree that jobsika.cm does not guarantee or endorse any job posting or application on the website. You also acknowledge and agree that jobsika.cm is not involved in any aspect of the employment relationship between employers and job seekers. You are solely responsible for your interactions and communications with employers.

Privacy Policy
jobsika.cm respects your privacy and is committed to protecting your personal information. This privacy policy explains how we collect, use, share, and safeguard your personal information when you use our website.
Information We Collect
We collect two types of information from you: personal information and non-personal information.
Personal information is any information that can be used to identify you as an individual. We collect personal information from you when you voluntarily provide it to us. For example:

When you register an account on jobsika.cm

When you submit a rating or a review of a company

When you share your salary information

When you post or apply for a job

When you contact us for support or feedback

Non-personal information is any information that cannot be used to identify you as an individual. We collect non-personal information from you automatically when you use our website. For example:

Your IP address

Your browser type

Your device type

Your location

How We Use Your Information
We use your non-personal information for the following purposes:

To analyze and monitor our website performance and usage

To generate aggregate and anonymous statistics and reports

To conduct research and development

To improve our website and its services

How We Share Your Information
We do not sell, rent, or trade your personal information to any third parties without your consent. We may share your personal information with the following parties:
Our service providers, contractors, and partners who help us to operate and maintain our website and its services. They are bound by contractual obligations to protect your personal information and use it only for the purposes for which we disclose it to them.
Other users of the website, such as employers, recruiters, and job seekers, when you post or apply for a job.
Law enforcement, government authorities, or other third parties, when we believe it is necessary or appropriate to comply with legal obligations, protect our rights and interests, or prevent or investigate fraud, abuse, or illegal activity.
We may share your non-personal information with the following parties:
Our service providers, contractors, and partners who help us to analyze and improve our website and its services. They are bound by contractual obligations to protect your non-personal information and use it only for the purposes for which we disclose it to them.
Other users of the website, such as employers, recruiters, and job seekers, when we display aggregate and anonymous statistics and reports on the website.
Advertisers and advertising networks who deliver relevant content and advertisements to you on the website or on other platforms. They may use cookies and other similar technologies to collect non-personal information from you.
How We Protect Your Information
We take reasonable measures to protect your personal information from unauthorized access, use, disclosure, modification, or destruction. We use encryption, firewalls, passwords, and other security technologies to safeguard your personal information. However, we cannot guarantee that your personal information is completely secure or immune from cyberattacks or human errors.
How Long We Keep Your Information
We retain your personal information for as long as necessary to fulfill the purposes for which we collected it or as required by law. We may delete or anonymize your personal information when it is no longer needed or when we terminate our website and its services.
Your Rights and Choices
You have the following rights and choices regarding your personal information:

You have the right to request that your personal information or any content you uploaded on jobsika be deleted. All you need to do is email us at --- or send us a message on our social media.

You can opt-out of receiving promotional emails from us by clicking on the unsubscribe link in the email or contacting us at<EMAIL_ADDRESS>

Changes to This Policy
We may update this policy from time to time to reflect changes in our practices or applicable laws. We will notify you of any material changes by posting a notice on the website or sending you an email. Your continued use of the website after such notice constitutes your acceptance of the revised policy.
Contact Us
If you have any questions or concerns about this policy or our privacy practices, please contact us on our social media or write to us at:
Open Source Software Cameroon (OSSCameroon) BP 12345 Yaounde Cameroon

I need review here

Hallo @Theryx thanks for writing this. i have some points of ununderstanding:

do the users have credentials on jobsika.cm?
is it right ths users can contacts us for deleting his data?

No creds as far as I know


[fix](prepare statement) Not supported such prepared statement if prepare a forward master sql

Proposed changes

Use prepared protocol useServerPrepStmts=true and connect to follower FE
Use prepared statement to execute a ddl stmt such as drop database
follower FE forward this command to master FE, and it's not prepared protocol
then the client got the following exception:

java.sql.SQLNonTransientConnectionException: msg: Not supported such prepared statement
        at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
        at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
        at com.mysql.cj.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:633)
        at com.mysql.cj.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:417)
        at com.mysql.cj.jdbc.ClientPreparedStatement.execute(ClientPreparedStatement.java:371)

When  and connect to follower FE, it forward the sql to master FE and
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


"Failed to load script" error (gtag & hotjar)

📚 What are you trying to do?
I'm using nuxt-scripts to setup Google Analytics and Hotjar. Apparently everything is working as expected, and I can't reproduce any errors. Both on localhost and in production, when I access my application, the script loads and trigger events correctly in different browsers.
However, in production, Sentry is notifying me about this error, that is happening frequently (both gtag and hotjar).
When I access the same page that triggered the error, nothing wrong happens (and nothing is logged in sentry). Which makes me think it might be a specific error in a particular browser.

🔍 What have you tried?
This is an example of how I setup hotjar, creating a composable that exports a method to identify user. This method identifyHotjarUser() is called in a onMounted() hook on my home page. Gtag setup is following almost the same structure.
export const useHotjar = () => {
  function identifyHotjarUser () {
    const runtimeConfig = useRuntimeConfig()
    const { hotjar } = runtimeConfig.public.scripts

    const { hj, $script } = useScriptHotjar({
      id: Number(hotjar.id),
      sv: hotjar.sv
    })

    $script.then(() => {
      hj('identify', 'user-id', {
        name: 'user name',
        website: 'http://user-website.com',
      })
    })
  }

  return {
    identifyHotjarUser,
  };
}

ℹ Additional context
This is the frequency of errors in each browser and OS:

Examples of user agents from Chrome Mobile:
Mozilla/5.0 (Linux; Android 7.0; SM-G930V Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943)

Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

The issue is most likely related to the end user having a browser extension that is blocking these tracking scripts.
As far as I understand the error thrown won't have any logic side effects, besides the script itself not being loaded.

Sentry doesn't give me any details about the script request and the error. I can't even tell if it's affecting the end user in any way because I'm unable to reproduce the error.
I don't know what else I can try to reach a conclusion :disappointed:
I’m going to setup gtag and hotjar using useScript instead of useScriptGoogleAnalytics and useScriptHotjar, just to ensure there's nothing wrong with the registry scripts.`

Out of a total of 24,000 visits to my site, I have about 1,500 occurrences of the error, which came from approximately 500 different users. This reinforces my belief that it’s a user-specific browser error, which may be blocking these tracking scripts.
For now, I’ll assume that’s the case and close the issue. If I have any updates on the error, I’ll come back here.
Thanks for the help!


jQuery not available in server integration

When referencing jQuery during a server integration test I get
$ is not defined

Is it possible to have jQuery visibile? I think it's important to properly cover integration tests.

jQuery is a client only library. Can you give me an example how you would use it in a server integration test please. So that I can understand you use case.

Doing http requests to a remote service (OpenStack). Due to the request's nature, it has to be a server-side only operation (wrapped in a Meteor's Method). I'm using $.ajax().
... uhm. Now that you're making me double thinking about it, maybe I could (should?) use Meteor HTTP functions?

Yes, Meteor HTTP works on client and server side. $.ajax works only on the client side.
If your Meteor method is also included on the client side, then it will also run on the client. You can read more about it in the documentation http://docs.meteor.com/#/full/meteor_methods (see isSimulation).


feat(linter): add errcheck check an fix issues

Description of the change:

Enable errcheck check
Fix linter issues

Motivation
Closes: #2219

/hold
(it is done and OK to go, the hold is just for we prioritize orders reviews )

Also there's a typo in the PR title if you're going to use that for the commit message.
... check an fix issues should be ... check and fix issues.

Hi @hasbro17,
Really thank you for your great review :-)
Regards the :

Also there's a typo in the PR title if you're going to use that for the commit message.
... check an fix issues should be ... check and fix issues.

I will fix in the squash.


react/prop-types: allow ignoring by glob

example
{
  'react/prop-types': ['warn', { ignore: ["/_path$/", "className"] },
}

todo

[ ] add test

@a-x- are you interested in updating this PR?


Add possibility to give icon path for shortcuts

For some apps, the target linked in the shortcut does not contain the app icon. A third parameter in the shortcut array can now be used to specify the icon location.
Example:
    "shortcuts": [
        [
            "bin/idea.bat",
            "IntelliJ IDEA",
            "bin/idea.exe"
        ]
    ],

The documentation in the wiki should be amended if this gets accepted.

Related to #1320 #1319 #1378

Thanks for the links. I continued conversation at #1378


Brandont.dev

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[x] The domain is in the correct alphabetical order
[x] This site is not a ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: brandont.dev
  url: https://brandont.dev/
  size: 165
  last_checked: 2023-04-07

GTMetrix Report: https://gtmetrix.com/reports/brandont.dev/UHgT0tcH/

Thanks for adding your site!


fixing metadata.rb to not include path outside of the repo

Fixing metadata.rb

The main reason for this is to fix knife cookbook upload issue. On chef client 11 it fails due to metadata pointing at a dependencies outside of cookbook path.
/cc: @schisamo

I always upload the cookbook with Stove, so I don't experience this problem.


Add subsetting option to data access methods

Fixes #406
This PR adds the index option to the following methods on a field/fieldlist:

to_numpy()
to_array()
data()
to_latlon()
to_points()

With this the extracted values can be sliced on a per field level. E.g. if ds is a fieldlist we can write:
v = ds.to_numpy(flatten=True, index=slice(0, 3))

This is roughly equivalent to:
v = np.array([f.to_numpy(flatten=True)[:3] for f in ds])

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

Project coverage is 90.06%. Comparing base (4973af9) to head (99e47cb).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #407      +/-   ##
===========================================
+ Coverage    89.92%   90.06%   +0.14%
===========================================
  Files          120      120
  Lines         7764     7875     +111
  Branches       675      675
===========================================
+ Hits          6982     7093     +111
  Misses         651      651
  Partials       131      131

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

@iainrussell, if it is fine with you I merge and close this PR


Dist is not being commited to filesystem but generated

Seems even after revert, GH does build but the test fails?

#2826
https://github.com/kodadot/nft-gallery/issues/2826#issuecomment-1096606454
#2828

Seems everything is building here at 3049c4d (#2805)
https://github.com/kodadot/nft-gallery/pull/2805

Might this be related? https://github.com/nuxt/framework/issues/4119


Tweak Readme.md for readability

Wraps some type/method/property names in backticks for readability

Thank you.


✨[Feature Request]: Login page is not appearing good

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The login page absolutely needs improvement.
Use Case
It makes the web page more attractive to the users.
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

please assign it to me
Thank you

provide layout how you are thinking it should be

i would like to work on this !please assign it  to me.

@Anishkagupta04
This is my design


Podman doesn't always honor default rw permission for volumes in podman run

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

Description

Podman does not always honor the default of :rw  when mounting a volume with podman run --volume [...]. It turns out podman takes the last explicitly specified mount permission as the default.
The doc for podman run says "By default, the volumes are mounted read-write".
Steps to reproduce the issue:
$ sudo podman run --name rabbitmq_bootstrap -ti --user root --rm \
    --volume=/etc/hosts:/etc/hosts:ro \
    --volume=/var/lib/rabbitmq:/var/lib/rabbitmq \
    <IP_ADDRESS>:8787/tripleomaster/centos-binary-rabbitmq:current-tripleo \
    touch /var/lib/rabbitmq/foo
touch: cannot touch '/var/lib/rabbitmq/foo': Read-only file system

Describe the results you received:
It fails to write to /var/lib/rabbitmq even though the volume was mounted not supposed to be mounted read-only.
Describe the results you expected:
It should be able write to /var/lib/rabbitmq when mounting the volume with --volume=/var/lib/rabbitmq:/var/lib/rabbitmq
Additional information you deem important (e.g. issue happens only occasionally):
Some more tests show that podman uses the last explicitly set mount permission:
# WORKS
$ sudo podman run --name rabbitmq_bootstrap -ti --user root --rm \
    --volume=/var/lib/rabbitmq:/var/lib/rabbitmq \
    <IP_ADDRESS>:8787/tripleomaster/centos-binary-rabbitmq:current-tripleo \
    touch /var/lib/rabbitmq/foo

# WORKS
$ sudo podman run --name rabbitmq_bootstrap -ti --user root --rm \
    --volume=/etc/hosts:/etc/hosts:ro \
    --volume=/var/lib/rabbitmq:/var/lib/rabbitmq:rw \
    <IP_ADDRESS>:8787/tripleomaster/centos-binary-rabbitmq:current-tripleo \
    touch /var/lib/rabbitmq/foo

# FAILS
$ sudo podman run --name rabbitmq_bootstrap -ti --user root --rm \
    --volume=/etc/hosts:/etc/hosts:ro \
    --volume=/etc/resolv.conf:/etc/resolv.conf \
    --volume=/var/lib/rabbitmq:/var/lib/rabbitmq \
    <IP_ADDRESS>:8787/tripleomaster/centos-binary-rabbitmq:current-tripleo \
    touch /var/lib/rabbitmq/foo
touch: cannot touch '/var/lib/rabbitmq/foo': Read-only file system

# WORKS
$ sudo podman run --name rabbitmq_bootstrap -ti --user root --rm \
    --volume=/etc/hosts:/etc/hosts:ro \
    --volume=/etc/resolv.conf:/etc/resolv.conf:rw \
    --volume=/var/lib/rabbitmq:/var/lib/rabbitmq \
    <IP_ADDRESS>:8787/tripleomaster/centos-binary-rabbitmq:current-tripleo \
    touch /var/lib/rabbitmq/foo

Output of podman version:
$ podman version
Version:       0.6.1
Go Version:    go1.9.4
OS/Arch:       linux/amd64

Output of podman info:
$ sudo podman info
host:
  MemFree: 261070848
  MemTotal:<PHONE_NUMBER>
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 2
  hostname: openstack-controller-0
  kernel: 3.10.0-862.9.1.el7.x86_64
  os: linux
  uptime: 11h 17m 28.52s (Approximately 0.46 days)
insecure registries:
  registries:
  - <IP_ADDRESS>:8787
  - <IP_ADDRESS>:8787
registries:
  registries:
  - docker.io
  - registry.centos.org
  - registry.access.redhat.com
store:
  ContainerStore:
    number: 5
  GraphDriverName: overlay
  GraphOptions:
  - overlay.override_kernel_check=true
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
  ImageStore:
    number: 6
  RunRoot: /var/run/containers/storage

Additional environment details (AWS, VirtualBox, physical, etc.):

Sounds like a parsing issue - @umohnani8 PTAL

Thanks @mandre This should be an easy fix.

Fixed in #1142


Feature request: Upload components

It would be great if I could upload a single file as a component to a study in JATOS––my lab often has multiple people collaborating on a study and having to destroy/create the study anew for any code changes, or SSH into the remote node itself to make those changes, is something that is incredibly time consuming. I can't imagine it would be a ton of work to add

Actually, I think my workflow was just approaching JATOS the wrong way. Closing this


Open source the codemod that migrate from the old stylex syntax to the new stylex syntax

Describe the feature request
When stylex was first introduced at React Conf in 2019, its API looked like this:
const styles = stylex.create({
  red: {},
  blue: {}
});

<Button className={styles('red', blue && 'blue')} />

Upon its introduction, many projects attempted to replicate the concept, with the style9 doing an exceptional job.
Since then, stylex has evolved rapidly with significant changes to the API, while the community exploring ideas with projects like style9.
Since stylex is now open-sourced, I'm considering migrating my existing projects, which are currently powered by style9, to stylex. However, this transition would entail numerous modifications.
I understand that Facebook might use an internal codemod for this purpose. Is there any possibility of making it open-source?

@SukkaW Our internal codemods are based on Flow which is not really used outside of Meta and would likely not be useful. Also this particular transition happened a long time ago. I'll see if I can find something useful, but the chances of that are pretty low.


introduce text editor

Since last request I have removed coupling of TextCell and TextEditor. But I have left TextEditorCell to provide all necessary functionality to traits (TextNavigationTrait, TextNavigationTrait and CompletionSupport).

I would rename TextEditorCell to CellTextEditor. It's not a cell, it's a text editor for a cell.
In Completion Support I would try to get rid of editor == null branch. It's nice to do everything via TextEditor interface.
Overall good job. I merged it. Create a separate pull request for my comments.


Allow headers when making multi get requests + set headers when makin…

…g controller API calls
Instructions:

The PR has to be tagged with at least one of the following labels (*):

feature
bugfix
performance
ui
backward-incompat
release-notes (**)

Remove these instructions before publishing the PR.

(*) Other labels to consider:

testing
dependencies
docker
kubernetes
observability
security
code-style
extension-point
refactor
cleanup

(**) Use release-notes label for scenarios like:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

Codecov Report

Merging #9170 (1f66880) into master (0be79c9) will decrease coverage by 2.94%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #9170      +/-   ##
============================================
- Coverage     69.96%   67.02%   -2.95%
- Complexity     4756     4811      +55
============================================
  Files          1848     1377     -471
  Lines         97914    71556   -26358
  Branches      14747    11436    -3311
============================================
- Hits          68508    47960   -20548
+ Misses        24629    20130    -4499
+ Partials       4777     3466    -1311

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
67.02% <0.00%> (+0.08%)
:arrow_up:

unittests2
?

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

Impacted Files
Coverage Δ

.../org/apache/pinot/common/http/MultiGetRequest.java
90.90% <0.00%> (-9.10%)
:arrow_down:

...va/org/apache/pinot/core/routing/RoutingTable.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/pinot/common/config/NettyConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/common/metrics/MinionMeter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...g/apache/pinot/common/metrics/ControllerMeter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../apache/pinot/common/metrics/BrokerQueryPhase.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../apache/pinot/common/metrics/MinionQueryPhase.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ache/pinot/server/access/AccessControlFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/query/parser/QueryRewriter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...he/pinot/common/messages/SegmentReloadMessage.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 744 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


added questions

Thanks for review @xabbuh,  I will update the Set.  Also,  good luck if you are training for the certification: to me you are already a Symfony expert

Thank you @mickaelandrieu! :)


Eager fetching events

As mentioned by @bogus34 in #240 - looking into refining the model event cycle, triggering additional events during eager loads, etc.

@bendrucker It would be amazing to configure something like
var ModelB = bookshelf.Model.extends({
  fetchEager: ['other'],
  relatedBs: function() {
    return this.hasMany(ModelB)
  },
  other: function() {
    return this.belongsTo(ModelC);
  }
});

// without withRelated because always i want load other
new ModelB.forge({id: 1}).fetch().then(function(modelb) {
  modelb.related('other');
});

@rkmax @bendrucker is there any way currently that allows default eagerly fetched models like described above?

@tgriesser Curious if there is an obvious workaround for modifying queries that are fetched via withRelated. I've been able to get pretty far so far with the following, which adds a special column AS into the SQL to have the database translate a geographic point into something more readable. However, I just realized that the fetching and/or fetching:collection events are not fired for withRelated.
I'm not seeing an obvious way to accomplish this, even as a workaround, for withRelated so curious if there is a stop-gap I could use.
Example of my modification:
var onFetchAddCoordinateTranslation = function(model, columns, options) {
    var coordinatesToGeoJson = bookshelf.knex.raw('ST_AsGeoJSON(coordinates) as coordinates_geojson')
    var applyToCoordinates = _.some(columns, function(value) {
        return (value === 'account_addresses.*' || value === '*' || value === 'coordinates')
    })
    if (applyToCoordinates) columns.push(coordinatesToGeoJson)
}

bookshelf.Model.extend({
    initialize: function() {
        this.on('fetching', onFetchAddCoordinateTranslation)
        this.on('fetching:collection', onFetchAddCoordinateTranslation)
    }
})

My solution is somthin like this
initialize: function() {
                this.on('fetching', function(model, columns, options){
                    // Set default relation
                    if(!options.withRelated){
                        options.withRelated = [];
                    }
                    options.withRelated.push("other");
                });

                this.on('fetched', function(model, response, options){
                    // parse geo position to Object
                    model = geo.simpleParse({
                        data: model
                    });
                });
}

and the other model with postGIS
initialize: function() {
                this.on('fetching fetching:collection', function(model, columns, options){
                    if(columns){
                        columns.push(knex.raw("ST_AsGeoJSON(other.position) as position"));
                    } else {
                        options.query.select(knex.raw("ST_AsGeoJSON(other.position) as position"));
                    }
                });
}

@rhys-vdw I think this is resolved by my PR #1206

Resolved by #1206


Install Tailwind css in the project

HELLO TEAM!!!
I have successfully installed tailwind CSS in the project for better styling and developer experience

Hello @David-Lanzz
Great job completing this part of the task, its time to merge


opentabletdriver: add buildInputs

Description of changes

Should fix issue: #184652
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

CC @tewkanz.

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

1 package built:

opentabletdriver


Fix python code snippet. (Commit containers)

Proposed changes
Update engine/api/get-started.md.
An error occurred when executing python sample code (Commit containers).
Therefore, i fixed python sample code.

@mstanleyjones Thanks!


drawio: 15.7.3 -> 15.8.4

Motivation for this change
update drawio to the latest version
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

drawio

At first I got a core dump, however running it again worked :shrug: .


Support xterm.js' letterSpacing setting

terminal.integrated.letterSpacing should support integer (pixel) values

@rfgamaral you can test it out in tomorrow's Insiders:

Great, awesome job, thanks :)
I know it's a bit unrelated, but hard would it be to implement a similar setting on https://github.com/zeit/hyper?

@rfgamaral should be pretty easy, you would need to expose the xterm setting and then make sure that sizing still works correctly.

Thank you :)


Would be nice to have Material Theme'd Shrine

It might already be in the plans.  But I notice the Shrine we show in flutter_gallery is the only pre-Material-theming shrine.
This is not at all urgent.

FYI @willlarche

Known! It will be a port of the codelabs' final result and maybe some more.

Duplicate of #22722