Truncate node addresses

Instead of showing the full address of each thornode thor155fhk3zl2utx7msaynp5ag6epxpmjkrp7ytmr8 truncate the middle, e.g. like that: thor155fh...ytmr8
Then the buttons are not that big.

The buttons are as big as the Message above it.
But we could truncate it, cut the size of the buttons in half, and display them in pairs:
thorXX...XXX - thorXX...XXX
thorXX...XXX - thorXX...XXX
Add NODE   -  << BACK

Sounds good to put them in 2 columns beside each other.


illuminate/support of laravel/framework 6.16.0 not supported

Problem 1
    - Installation request for pwweb/artomator ^0.2.2@beta -> satisfiable by pwweb/artomator[v0.2.2-beta].
    - Conclusion: remove laravel/framework v6.16.0
    - Conclusion: don't install laravel/framework v6.16.0
    - pwweb/artomator v0.2.2-beta requires illuminate/support 6.0.* -> satisfiable by illuminate/support[v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4].
    - don't install illuminate/support v6.0.0|don't install laravel/framework v6.16.0
    - don't install illuminate/support v6.0.1|don't install laravel/framework v6.16.0
    - don't install illuminate/support v6.0.2|don't install laravel/framework v6.16.0
    - don't install illuminate/support v6.0.3|don't install laravel/framework v6.16.0
    - don't install illuminate/support v6.0.4|don't install laravel/framework v6.16.0
    - Installation request for laravel/framework (locked at v6.16.0, required as ^6.2) -> satisfiable by laravel/framework[v6.16.0].

Suggestion to have composer requirement ^6.0 for illuminate/support

Merged PR #21


Test-update

@cxwtool : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#hold-off

Closing this test PR


roundhouse missing assembly reference

Uninstall Log4Net Nuget as roundhouse.lib will install an older version.  Remove the reference to roundhouse.databases.sqlserver as this does not seem to actually be needed.  Then include roundhouse.lib nuget package.


use latest kiali

currently rio is using kiali v0.14  which is much older than latest https://github.com/kiali/kiali/releases/tag/v0.20.0      This needs to be updated.

duplicated of https://github.com/rancher/rio/issues/383


Channel or Stream Support from Client to Server?

I'm currently using SignalR Core in a project and it does a great job so far!
I currently have a little problem with data send from the client to the server, which exceeds the data limit.
I know that the limit can be adjusted, but it doesn't really solve my use case.
What I want to do is stream a variable list of items from the client to the server. If the list get's to large, I will have to split it into smaller chunks or set the transfer limit higher (which is risky, because I don't know how many items there will be).
A better solution would be to use the ChannelReader, just like it's currently used to stream data from the server but in the opposite direction.
Is it possible to add the support to stream data from the client to the server?
Or does the current architecture forbid it?
I'm currently using the C# client and server. So far I do not require the javascript client in my project.

This is something we're actively considering for the 3.0 release next year. See https://github.com/aspnet/SignalR/issues/2699 .
I'm going to close this issue just because we're already tracking this. Glad to hear this feature would be useful to you! Feel free to continue discussion on this thread or the referenced issue!


Fix test cases to close input streams

Would it be worthwhile to create an Abstract class with the method logContainsMessage() for our test classes to extend and use?

Yes. We can look into doing that in a future PR.


[Epic] Archive old k3s-io repos

Is your feature request related to a problem? Please describe.

k3s-io has 27 repos. Many of these are old and unused.
Describe the solution you'd like

We need to cleanup and arch these repositories.

We have archived all relevant repos, closing this issue


a misregistered package action-cable

Hi, guys.
I am trying to register a package action-cable for actioncable from Ruby on Rails. But the name action-cable is misregistered  to another package action-cable-react. And I cannot delete the name actioncable that I registered by mistake either.
$ bower search action-cable
Search results:

    action-cable-bower git://github.com/hardywu/action-cable.git
    actioncable git://github.com/hardywu/action-cable.git
    action-cable git://github.com/schneidmaster/action-cable.git
    action-cable-react git://github.com/schneidmaster/action-cable-react.git

$ bower unregister actioncable
? You are about to remove component "actioncable" from the bower registry (https://bower.herokuapp.com). It is generally considered bad behavior to remove versions of a library that others are depending on. Are you really sure? Yes
bower unregister    actioncabler to remove versions of a library that others are depending on.
Unregistering should work again, once that is resolved.

You should now be able to unregister packages as intended. :tada:

Thanks a lot.


ci/precommit: checkout with token

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
Did you make sure to update the docs?
[x] Did all existing and newly added tests pass locally?

What does this PR do?
debugging:
Started: bash /home/runner/work/_actions/actions-js/push/v1.4/start.sh
Push to branch ci/precommit
[ci/precommit d98cb32] pre-commit: running and fixing...
 1 file changed, 1 deletion(-)
To https://github.com/Lightning-AI/sphinx-theme.git
 ! [remote rejected] HEAD -> ci/precommit (refusing to allow a GitHub App to create or update workflow `.github/workflows/code-lint.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/Lightning-AI/sphinx-theme.git'
Error: Invalid status code: 1
    at ChildProcess.<anonymous> (/home/runner/work/_actions/actions-js/push/v1.4/start.js:9:[19](https://github.com/Lightning-AI/sphinx-theme/actions/runs/6894240260/job/18755592670?pr=98#step:6:20))
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  code: 1
}
Error: Invalid status code: 1
    at ChildProcess.<anonymous> (/home/runner/work/_actions/actions-js/push/v1.4/start.js:9:19)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:[30](https://github.com/Lightning-AI/sphinx-theme/actions/runs/6894240260/job/18755592670?pr=98#step:6:31)4:5)

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

:books: Documentation preview :books:: https://lit-utilities--194.org.readthedocs.build/en/194/

validated on another private repo:


scroll to top button is not consistent

Describe the bug
The scroll-to-top button does not consistently appear on all pages, or sometimes fails to function as expected.
To Reproduce
Steps to reproduce the behavior:

Navigate to any page where the scroll-to-top button should be visible.
Scroll down to trigger the button.
Observe whether the button appears and functions as expected.

Expected behavior
The scroll-to-top button should be present on all pages, appearing when the user scrolls down and smoothly returning to the top when clicked.
Screenshots

Additional context
This may require checking page layouts or scripts that handle the button’s visibility and functionality.

fixed

@ANSHIKA-26  but why there are two scroll to top buttons


[Fix-8050] When the task is forbidden the node will obviously display.

Purpose of the pull request
This PR will close #8050 .
This PR will close #8181  .

Brief change log

Verify this pull request

Manually verified the change by testing locally.

Codecov Report

Merging #8332 (e90a920) into dev (b75f67a) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

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

@@             Coverage Diff              @@
##                dev    #8332      +/-   ##
============================================
- Coverage     45.30%   45.28%   -0.03%
  Complexity     3994     3994
============================================
  Files           680      680
  Lines         26459    26463       +4
  Branches       2848     2849       +1
============================================
- Hits          11987    11983       -4
- Misses        13339    13347       +8
  Partials       1133     1133

Impacted Files
Coverage Δ

...duler/common/task/switchtask/SwitchParameters.java
0.00% <0.00%> (ø)

...olphinscheduler/rpc/remote/NettyClientHandler.java
41.86% <0.00%> (-9.31%)
:arrow_down:

Continue to review full report at Codecov.

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


Caddy Hangs Frequently

1. What version of Caddy are you running (caddy --version)?
0.9.4
2. What are you trying to do?
Run Caddy reliably
3. What is your entire Caddyfile?
can provide privately, hostnames will need to be obscured

4.  What did you expect to see?
A working web server!
6. What did you see instead (give full error messages and/or log)?
Caddy occasionally hangs, timing out when web requests are sent.
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
I'm not sure.  It's unpredictable so far.

Thanks for the report. Unfortunately this is entirely unactionable as-is, so I will be closing this.
Can't you even reveal how many sites are hosted on it, whether it's HTTP or HTTPS, what the output of curl -v or s_client is, anything?

Thanks for your help, @mholt.  I'd like to continue updating this issue if it persists, if you don't mind?  I'll wait for the update release.  Mind linking me to the issue for the deadlock?  I can do some debugging / stack tracing if you'd like.

Yep! If it's what I suspect (again, having no real grounds for it), it's a duplicate of this: https://github.com/mholt/caddy/issues/1157
Fixed in: https://github.com/mholt/caddy/pull/1366
If, after the update, your server continues to exhibit the same behavior or you are confident it is something different, feel free to re-open with more details. Enabling pprof and getting a stack trace of all the goroutines would be helpful as well.

Thanks again, @mholt!  I've deployed 0.9.5 and will report back with updates within two weeks.

So far so good, with one exception: this upgrade caused hosts with WebSocket configurations to continuously cycle connect/reconnect.  @mholt any insight into this?  I saw a mention of improved support in the release notes.
Configuration file looks something like this:
soundtrack.io:80 {
  redir https://soundtrack.io{uri}
}

*.soundtrack.io:80 {
  redir https://{hostonly}{uri}
}

soundtrack.io:443 {
  tls /FULL_PATH_OBSCURED/soundtrack.io.crt /FULL_PATH_OBSCURED/soundtrack.io.key
  proxy / localhost:13000 {
    websocket
    header_upstream Host soundtrack.io
  }
}

*.soundtrack.io:443  {
  tls /FULL_PATH_OBSCURED/soundtrack.io.crt /FULL_PATH_OBSCURED/soundtrack.io.key
  proxy / localhost:13000 {
    websocket
    header_upstream Host {hostonly}
  }
}

I've also tried with -http2=false as per some original documentation, to no avail.  Please advise!

The release notes very prominently describe the new timeouts: https://caddyserver.com/docs/timeouts
You should probably raise or disable them if you have long-lived connections, like websockets.
Glad it's working for you now!

So far.  It happens once a week or so, and we've restarted the instance since then.  We'll have to wait to be sure.
I have over 100 hosts, does timeout need to be added individually to each?

No, if you read the docs it says you can just set it once per listener.

I've read the docs; they are unclear.  Trying to add timeout to the top-level so that it applies to all hosts seems to break the config (Parse error: Unknown directive 'some.host'), and having to make configuration changes to every single host every time we upgrade is getting tedious.  Perhaps following the semantic versioning guide would be useful here with regards to mandating configuration changes.
I've changed the timeout for one host to 1m to test, but it seems the connections are still getting restarted.  Adding websocket to a host's configuration really should be sufficient, if we don't want WebSockets to be made available by default (which I believe they should be).  Are we sure the read/write timers are being calculated correctly?

I've read the docs; they are unclear. Trying to add timeout to the top-level so that it applies to all hosts seems to break the config

Yeah, you can't do that. :) It sounds like you might be new to Caddy. I suggest reading https://caddyserver.com/docs/caddyfile for information about how the Caddyfile syntax works.

Perhaps following the semantic versioning guide would be useful here with regards to mandating configuration changes.

We generally do, but shifted down a version number until we're 1.0. Until then, I'm not afraid to make breaking changes, and that's stated in the wiki. By 1.0, we should have a good definition of what breaking and non-breaking means.

Are we sure the read/write timers are being calculated correctly?

We use the Go standard library. See https://github.com/golang/go/issues/16100 for more information.

The trouble seems to be that the timer isn't incremented, even if data is sent over the WebSocket.  Results in the WebSocket being dropped consistently.  Is this the desired behavior?

Not sure -- Go is handling the timeouts for us. We just set the values on the http.Server. You can take the issue up at golang/go there if you think it is a bug (it might be -- or it just might be more complicated than it seems from the surface). That issue I linked to will get you started.


Add try / except to check if weekly stats have been pulled

The current way to update the weekly NFL stats (and from there, scoring) is to to do a POST on update-weekly-stats which can be called by cron.  All of the admin pages except this require superuser login.  Either find a way to do the POST with a login or add a try / except to make sure the stats aren't already there to avoid malicious actors.

Done and in the msf2-api branch:  7735738d0a13ea84fa02327f9c975e7af3410400

Done!  https://github.com/prcutler/nflpool/commit/fa6bd552b8e971f3d2cb406cd3b57354b84d1345


Various minor changes

Marker and polygon centered different in mobile after automatic zoom. This is because the infobox is open.
Update URL with coordinates after search result selection.
Differentiate between click and double click in leaflet.

Test den: https://forvaltningsportal.test.artsdatabanken.no/pr/forvaltningsportal_408


docs: documentation updates

Summary
Adds documentation for functions added / updated for the next release.

Type

[ ] Bugfix
[ ] Enhancement or Feature
[ ] Code Style or Formatting
[x] Documentation
[ ] Refactoring
[ ] Chore
[ ] Other
Please describe:

Breaking Changes?

[ ] Yes, there are breaking changes.
[x] No, there are no breaking changes.

Test and Documentation

[x] Tests have been completed.
[x] Documentation has been added or updated.

Issue References

Additional Information

Where do you want them?
Jared Burns
Technology Product Management 5 |  VMware Cloud Foundation (VCF)
Broadcom
office:<PHONE_NUMBER> |  mobile:<PHONE_NUMBER>
USA-SC Remote Location
@.***   |   broadcom.com
On Mon, Jan 15, 2024 at 09:16 Gary Blake @.***> wrote:

@.**** requested changes on this pull request.
In CHANGELOG.md
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452426660
:

-- Added Request-AslcmBundle cmdlet to download the VMware Aria Suite Lifecycle bundle in SDDC Manager.
-- Added New-AslcmDeployment cmdlet to perform the deployment of VMware Aria Suite Lifecycle using SDDC Manager.
-- Added Install-AslcmCertificate cmdlet to install a signed certificate for VMware Aria Suite Lifecycle using SDDC Manager.
+- Added Request-VrslcmBundle cmdlet to download the VMware Aria Suite Lifecycle bundle in SDDC Manager.
+- Added New-VrslcmDeployment cmdlet to perform the deployment of VMware Aria Suite Lifecycle using SDDC Manager.
+- Added Install-VrslcmCertificate cmdlet to install a signed certificate for VMware Aria Suite Lifecycle using SDDC Manager.

Please remove this change, the new functions have been created with Aslcm
name deliberately
In CHANGELOG.md
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452427018
:

-- Added Undo-AslcmDeployment cmdlet to remove VMware Aria Suite Lifecycle from SDDC Manager.
-- Added Export-AslcmJsonSpec cmdlet to generate a JSON specification file for VMware Aria Suite Lifecycle.
-- Added Invoke-AslcmDeployment cmdlet to perform an end-to-end install of VMware Aria Suite Lifecycle.
+- Added Undo-VrslcmDeployment cmdlet to remove VMware Aria Suite Lifecycle from SDDC Manager.
+- Added Export-VrslcmJsonSpec cmdlet to generate a JSON specification file for VMware Aria Suite Lifecycle.
+- Added Invoke-VrslcmDeployment cmdlet to perform an end-to-end install of VMware Aria Suite Lifecycle.

Please remove this change, the new functions have been created with Aslcm
name deliberately
In PowerValidatedSolutions.psd1
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452427451
:

@@ -11,7 +11,7 @@
RootModule = 'PowerValidatedSolutions.psm1'

 # Version number of this module.

ModuleVersion = '<IP_ADDRESS>9'

ModuleVersion = '<IP_ADDRESS>0'

This build number will need to be bumped again when this PR is ready to be
merged
On
docs/documentation/functions/workspace-one-access/Invoke-IamDeployment.md
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452428889
:
not sure why this file is listed under workspace one access, as IAM no
longer has WSA
On
docs/documentation/functions/workspace-one-access/Invoke-UndoIamDeployment.md
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452429093
:
not sure why this file is listed under workspace one access, as IAM no
longer has WSA
On docs/documentation/functions/workspace-one-access/Export-IamJsonSpec.md
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#discussion_r1452429592
:
not sure why this file is listed under workspace one access, as IAM no
longer has WSA
—
Reply to this email directly, view it on GitHub
https://github.com/vmware/power-validated-solutions-for-cloud-foundation/pull/468#pullrequestreview-1821767065,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOU6LLHQXYCQNNK7L4F25NLYOU23HAVCNFSM6AAAAABBY3DPT2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMRRG43DOMBWGU
.
You are receiving this because you authored the thread.Message ID:
<vmware/power-validated-solutions-for-cloud-foundation/pull/468/review/1821767065
@github.com>

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.


Fix unstable tests

At preset, we don't have unstable tests. All test problems are related to unstable and slow emulators.


Adding tests & URL namespaces.

Dropping Django 1.7 support in tox.ini.
Adding tests for section views.
This PR supersedes closed PR https://github.com/pinax/pinax-blog/pull/78.

@paltman Can this be merged?


fzy sorter is slow with large code base

I have 2 golang repos kubernetes with 20k+ files and kubeedge with 7k+ files.
git_files and find_files becomes quite slow once I set the sorters to fzy,  search result starts to show after I type 7,8 letters :
require('telescope').setup{
  defaults = {
    generic_sorter = require'telescope.sorters'.get_fzy_sorter,
    file_sorter = require'telescope.sorters'.get_fzy_sorter,
  }
}

Do we have any update here? I can add more details if needed, just let me know what is necessary.

Yeah, there is ongoing work in #215.

You can try this instead: https://github.com/nvim-telescope/telescope-fzy-native.nvim :) I hope it works for you!

You can try this instead: https://github.com/nvim-telescope/telescope-fzy-native.nvim :) I hope it works for you!

it works, even with 20k files in the git repo!


Kuberentes Deployment to OAM converter

Migrated from https://github.com/oam-dev/rudr/issues/347
Ideally, we can covert a given kubernetes deployment object to a OAM defined application component and the required traits. Then the users can enjoy the benefit of separate concerns and supplying orthogonal operational capabilities without changing the app definition.
This would be supported in migrate sub-command.

assign @Diddaa


Poll rate (rate limit)

About 1 month ago, I had problems with the car becoming unavailable in HA every evening, the same applies to access in the Skoda app. Connection was restored a little late at night, with a downtime of about 6 hours.
I thought at first that this was due to work on the servers, but when the problem did not stop I contacted Skoda who took the matter up with the factory. Was then told that access was closed due to backend protection due to a third party program.
Guess this is due to HA polling the skoda server too often. Is it possible to add a variable in configuration to set update frequency against server, or reduce this permanent?
I run the latest version of HA and Skoda connect. Both parts have been updated during this period without the problem having changed

Hi, you can configure the Polling Frequency in the integration settings (Settings -> Devices and Services -> Integrations -> Skoda Connect -> Configure).
Keep in mind there are many other third-party services. I suspect things like Tronity and Pump might have a larger userbase than HA and who knows how often they are hitting the Skoda API.
Either way, feel free to play around with the polling interval. I personally have it set to 30s.

Thanks for the reply dvx76. Mistake of me not checking configuration settings. Was sure I had checked there earlier.
It was at 60sec, set it to 120sec and I'll see if that prevents me from being blocked.
I don't know about Tronity and Pump, it's not something I use. I have only configured Skoda connect in HA and I occasionally use the Android app.

I am also seeing this error. It can be seen in the logs as:
'errors': [{'type': 'UNAVAILABLE_VCF_CAPABILITIES', 'description': 'Fetch VCF capabilities failed because of {UNKNOWN}'}]}
I've now changed my poll interval to 180 seconds to see if it works like that.
It seems that there is some kind of daily quota of requests. The request limit is lifted when they day changes at 00:00 UTC.

I think I have the same issue since quite some time, but I did not find the time to investigate it further.
When I go to bed the status of my car is automatically checked with a forced refresh. This used to work fine until, I suppose a few weeks or maybe months ago.
Every day in the evening the Skoda entities become unavailable. Every night at 2:00 am (00:00 UTC) the entities come available again. During the time the entities are unavailable the Skoda app doesn't connect either.
I have changed the poll interval from 60 to 120 seconds to see if it works.

I have the same issue with a CUPRA and the bad thing is I can't even use the official app. Setting to 120s and see how it changes.

Fixed for me using 120s pull
I also removed some data that are no longer pulled and this makes me think if this also count as single pull request (one for each data type) or is it just one pull with all the data in a single request.
Do you know?

Bottom line - the bug is to allow polls below 120 sec, additionally the issue should be mentioned in the documention.

I absolutely second this

What do you mean by the bug is to allow polls below 120 sec ?
As for documentation, I can add a note where Poll frequency is documented in the README.

I have the same problem, and got the same answer from Skoda support that @Stene79 got.
Will try to change the polling interval to 300 and see if that helps.
Also, please correct me if I'm wrong here, but disabling entities in the Skoda integrations will not affect anything as all data (instruments) are collected for every request anyway, right?

I have the same problem, and got the same answer from Skoda support that @Stene79 got.
Will try to change the polling interval to 300 and see if that helps.
Also, please correct me if I'm wrong here, but disabling entities in the Skoda integrations will not affect anything as all data (instruments) are collected for every request anyway, right?

120s is fine

Hi.
Is it possible to somehow collaborate with Skoda to have official integration? I don't know the details but isn't better to be subscribed to some data on server, so server can send when some information is changed? In that case we will not ask server for data refresh every two minutes or less, or I am getting this wrong?
I mean this HA integration is really nice to have, it works as additional alarm in case of car movement, it can notify if you forgot to close doors,windows etc.

What do you mean by the bug is to allow polls below 120 sec ?
As for documentation, I can add a note where Poll frequency is documented in the README.

I have to apologise - bug is not the correct wording. It should be enough do mentioned into the documention.
And 120 should be default - 120 sek means 720 calls (enough below 1000 what looks like the Skoda limit).

Hi.
Is it possible to somehow collaborate with Skoda to have official integration? I don't know the details but isn't better to be subscribed to some data on server, so server can send when some information is changed? In that case we will not ask server for data refresh every two minutes or less, or I am getting this wrong? I mean this HA integration is really nice to have, it works as additional alarm in case of car movement, it can notify if you forgot to close doors,windows etc.

I don't think that Skoda / VW will allow that - they have their own app. Look what happen with Mazda where Mazda do not allow to use the api for HA integration.

@tiefflieger666

And 120 should be default - 120 sek means 720 calls (enough below 1000 what looks like the Skoda limit).

Cool. I'm changing the doc in #219 and the default is being changed in #217

Is it possible to somehow collaborate with Skoda to have official integration?

The integration replicates how the Skoda App works. Which is pull-based. There is no push-based solution, even though that would definitely be nice.
I would be very reluctant to try and discuss this integration with Skoda/VW because at best I don't think they will be interested to collaborate with no financial incentive. At worst, the don't like this at all and can try to block us. Ideally someone with a good contact in VW/Skoda would create a backchannel.

Hi, just wanted to share my experience in case someone else is puzzled by the rate limiting behavior. I had the poll frequency at 60s (or was it even 30s) for some time and it worked fine, but few weeks ago every afternoon at the same time the inegration started reporting unavailable and came back alive at UTC 00:00. After increasing the poll frequency (having read about the problems both here and with VW, our other car is ID.3), it was again stable for some days with 120s, but now it changed again a few days ago.  Now the unavailability comes at 3PM UTC and as expected lasts until 12PM UTC. So it seem I have to increase the poll frequence again to at least 180s.
Why I wanted to share this is that it may not be enough to give any exact "safe" polling frequency. It would be nice to know how it works at the back end, why some clients are limited (seemingly) more than others. We do not have anything else polling the API except this integration, I assume the VW integration is working with a completely different back-end (although it could explain something if VAG was harmoninzing their e-services and rate limiting ip's with too frequent connections). The Skoda model in this case is -23 Superb iV.

I assume the VW integration is working with a completely different back-end (although it could explain something if VAG was harmoninzing their e-services and rate limiting ip's with too frequent connections).

I believe that it's the same backend for all VAG connected cars. Perhaps different for ID/Rnyaq but your Superb iV shares backend, and frontend, with the VW Passat GTE.

Looks like Skoda / VW changed the behavior / daily limit again after 23.10.2023. Before it was working 24 hrs with 120 sec, but after 23.10.2023 it becames unavaliable after aprox. 18,5 hours (between 21:15-21:30 GMT+2). What refers to a limit of 500 calls per day - or a poll rate of 180.
Have adapted it on my side to 150 (I know - it's not enough to cover the whole, but that would proof the hypothesis). Results will be visible on Wednesy (partly tomorrow, due the change was done at 8:00 GMT+1).
Will keep you updated.

I assume the VW integration is working with a completely different back-end (although it could explain something if VAG was harmoninzing their e-services and rate limiting ip's with too frequent connections).

I believe that it's the same backend for all VAG connected cars. Perhaps different for ID/Enyaq but your Superb iV shares backend, and frontend, with the VW Passat GTE.

Yes, that could be. Our other car is ID.3. It does not seem to suffer from similar rate limit. I think I've set it to 120s now and it works 24h.
I changed the poll frequence for Skoda Connect to 180s around noon today but still, at exactly 3PM UTC it stopped working.

My ID4 started becoming unavailable every other poll cycle. So they have definitely made changes to the frontend for ID/Enyaq as well. Though there does not seem to be a hard limit (yet what I've seen) for ID frontend.
The hardest rate limit is for the old API which is common for all PHEV+Combustion connected cars which makes sense since there's plenty more cars and users using it.

I got the information from Skoda that the limit should be around 20 - 25 calls per day!
Have not tested if this is true - but it is possible that they lowered the limit again.

It seems they did, yes.
Since a few weeks I'm getting mad at their official app far more often than before.
I can see the multiple 429 errors in logs :
Too many requests. Further requests can only be made after the end of next trip in order to protect your vehicles battery.
And
Failed to execute data refresh - Action rate limit reached. Start the car to reset the action limit
@dvx76 it would bé nice to remove the 900 poll refresh rate limit, I was at 90, and wanted to put 1800, but impossible. Used 900, but who knows how many times it will hold :)

Please raise a new issue (or better, submit a PR) to get the max poll frequency raised. Should be trivial.
25 calls a day is ridiculous, even for Skoda. Probably mentioned before the actual limit is obscure, probably updated regularly,  and definitely different for different models (and maybe also different locations). I've had poll frequency 60s for nearly 2 years with no issues.


Improve Profiling

This request involves two commits:

The first fixes a bug where it was impossible to profile without a callback.  The profiler code passes the callback parameter as null if it is not provided.  This broke the argument parsing code of the logger, resulting in the metadata being lost.

The second adds a new profiling function startTimer which fixes a fundamental async issue with the profiler.  See the commit for details.

I will accept this if you can add tests for the new .startTimer() method.

@indexzero Tests added.

Ok, thanks. I'll merge this in soon.

Cherry-picked. Thanks


Step Challenges:  Menu Button disappears on second step on Mobile

On devices which display the "Mobile" view, the Menu button disappears when you navigate to the second slide.  Going back to the first slide brings it back.
Confirmed on Chrome on a Galaxy Tab Pro and Galaxy S3.

I worked on identifying what this mysterious disappearance is. You will get a clear idea of what's happening when you do the following.

In developer tools, select any tab/mobile as model. I selected Apple iPhone.
I opened step-challenge
Click and Open the Menu
Navigate to second slide.
I am attaching a screenshot to show the result.

It is little bizarre to me. But these are my findings related to this issue.

I'm able to reproduce this only in Chrome. @hallaathrad another issue that you may want to take a look.

it does help a whole lot, @gasperno! I know exactly what is generating the issue.
Now let's see if we can fix it without breaking a nail!

@hallaathrad I am able to repro in Chrome on a Galaxy S6. The menu disappears forever unless I scroll the page and then release my finger.

yeah, it's something in the way jQuery refreshes, it seemed to be... going to work on this one after lunch, shouldn't be too complex to deal with.

@hallaathrad, is this issue still going on?  if not then we could close this issue.

@dwd2010 I believe it's still happening. haven't quite figured out how to solve it.
Please leave it open, I'll close it asap.

@hallaathrad, no problem. I did test that on the chrome on my iPhone. I dont see any problem.  oh well.  menu button didnt disappears on me.

@hallaathrad, I can't reproduce. Is anyone still having this issue?

@atjonathan I can still repro.

Is this reproducible on beta?


TMOS 14.1 and root password

Hi,
When an onboarding config includes achange of root password, I cannot retrieve the old password on a TMOS v14.1, even if I use the admin password as described in the documentation.
Which old password do I have to set in v14.1+ ?
JSON body request
{
"async": false,
"schemaVersion": "1.3.0",
"Common": {
"root": {
"userType": "root",
"newPassword": "NewTest4Issue!",
"oldPassword": "Test4Issue!",
"class": "User"
},
"dbvars": {
"systemauth.disablerootlogin": false,
"ui.advisory.enabled": true,
"ui.advisory.text": "POC_Public_cloud",
"class": "DbVariables",
"ui.advisory.color": "green"
},
"class": "Tenant",
"route_internal": {
"gw": "<IP_ADDRESS>",
"mtu": 1500,
"class": "Route",
"network": "<IP_ADDRESS>/8"
}
},
"class": "Device",
"label": "declarative_onboarding_for_ADC_in_HUB"
}
answer
{
"code": 422,
"status": "ERROR",
"message": "invalid config - rolled back",
"errors": [
"Old password is incorrect."
],
"declaration": {
"async": false,
"schemaVersion": "1.3.0",
"Common": {
"root": {
"userType": "root",
"class": "User"
},
"dbvars": {
"systemauth.disablerootlogin": false,
"ui.advisory.enabled": true,
"ui.advisory.text": "POC_Public_cloud",
"class": "DbVariables",
"ui.advisory.color": "green"
},
"class": "Tenant",
"route_internal": {
"gw": "<IP_ADDRESS>",
"mtu": 1500,
"class": "Route",
"network": "<IP_ADDRESS>/8"
}
},
"class": "Device",
"label": "declarative_onboarding_for_ADC_in_HUB"
}
}

The old password would be the one you setup right before you installed DO.

OK thank you
By default, root access is not activated, so I understand that the root password cannot be set initially with DO, am I correct ?

That is correct. Admin account must be setup prior to first DO declaration.

Thanks


Recommended to increase page layout to support the display of multiple pages at the same time.

As the title mentioned.

Hi @gagmeng,
It is actually possible to have multiple windows open at the same time.  But the issue is that all windows share the same data storage, including calculations, settings, variables, etc.  So if a change is made in one window, it also changes the other windows but the change is not visible until the other pages are refreshed/restarted.  Then the UI becomes confusing.  Therefore I have chosen to keep a single window.  I will close this as wontfix for now however I will keep looking into a solution which would allow this in a user friendly way in the future.
Thank you for the suggestion!


Bug report: Wrong modulo value for Fletcher 16 integer truncate operations

Describe the bug
Wrong Fletcher 16 values are returned.
To Reproduce
Just calculate any Fletcher 16 value

Go to 'Favorites'
Click on 'From Hex'
Click on 'Delimiter'
Select  'Space'
Scroll down to 'Hashing'
Click on 'Fletcher-16 Checksum'
Go to Input
Write 'AA BB CC DD EE' without quotes
The returned checksum is 55 00 and it should be FC 4A

Expected behaviour
Calculate the correct Fletcher-16 value
Additional context
Modulo operation values used for integer truncation are wrong, the file CyberChef/src/core/operations/Fletcher16Checksum.mjs  at line 41 has the following
        for (let i = 0; i < input.length; i++) { \             a = (a + input[i]) % 0xff;             b = (b + a) % 0xff;         }
Which should be corrected as
        for (let i = 0; i < input.length; i++) {             a = (a + input[i]) % 0x100;             b = (b + a) % 0x100;         }

While mod 256 (0x100) is used in some protocols, the "correct" value for modulo looks 255 (0xff).
See: Fletcher's checksum - Wikipedia


s3.Bucket websites property is pluralized but should not be

Looks like website is not marked as MaxItems = 1, even though it is in practice, so we should force this and/or update the TF provider.
        let bucket = new aws.s3.Bucket(name, {
            websites: [{
                indexDocument: "index.html",
            }],
        }, { parent: this});

Commit 2a4132e in the Terraform provider fixes this, so this should be resolved with the next update.

This was fixed a while back, I'll close this issue out.


VS code editer changes color when full screen and in Zen mod

Issue Type: Bug
I upgraded vscode today, and i found it changed color when full screen an at Zen mode. While it did not go wrong at the default window mod.
VS Code version: Code 1.24.1 (24f62626b222e9a8313213fb64b10d741a326288, 2018-06-13T17:51:32.889Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx   (8 x 1996)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
6.90GB (2.52GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

jupyter
don
1.1.4

latex-workshop
Jam
5.5.1

vscode-language-pack-zh-hans
MS-
1.24.3

python
ms-
2018.5.0

markdown-all-in-one
yzh
1.4.0

Can you repreoduce this with vscode insiders https://code.visualstudio.com/insiders/
If yes please post a screenshot and explain what is wrong
Also reproducable steps would help


Ability to make the server websocket traffic first. in standalone.py

Currently there is no way in standalone.py to have the
server initiate traffic (after handshake done). It would be very useful to have
that feature so that we can test server initiated traffic.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 9 Nov 2012 at 2:29

As tyoshino@ said, it is possible to do this. Closing as invalid.


lint-fmt: grant network access to opam pin

This happens in the case where ocamlformat is vendored.
If its opam file contains pin-depends, it needs network access to be installed.

Here's a build where this could benefit ocaml-ci: https://ci.ocamllabs.io/github/ocaml-ppx/ocamlformat/commit/928ca6a8b47318b78d99a1faa59349d65526f0c7/variant/(lint-fmt)

Here's a build where this could benefit ocaml-ci: https://ci.ocamllabs.io/github/ocaml-ppx/ocamlformat/commit/928ca6a8b47318b78d99a1faa59349d65526f0c7/variant/(lint-fmt)

I'm ok with this, but it seems like a bug in opam that opam pin add -n results in network traffic. The manual page says:
       -n, --no-action
           Just record the new pinning status, and don't prompt for
           (re)installation or removal of affected packages.

And fetching the remote sources seems like a pretty significant action. Maybe this just needs a revision to the manual page entry upstream in opam.

I'm ok with this, but it seems like a bug in opam that opam pin add -n results in network traffic. The manual page says:
       -n, --no-action
           Just record the new pinning status, and don't prompt for
           (re)installation or removal of affected packages.

And fetching the remote sources seems like a pretty significant action. Maybe this just needs a revision to the manual page entry upstream in opam.

That surprised me as well, but I think that's due to the recursive nature of pin-depends, but I'm not sure how to fix that with the current UI. What we're doing is:

opam pin add -n
opam depext
opam install --deps-only

If pin add does not access the network, then this network access would need to be "resolved" in opam depext and somehow written back to the switch state.

That surprised me as well, but I think that's due to the recursive nature of pin-depends, but I'm not sure how to fix that with the current UI. What we're doing is:

opam pin add -n
opam depext
opam install --deps-only

If pin add does not access the network, then this network access would need to be "resolved" in opam depext and somehow written back to the switch state.


Problems connecting chirpstack-gateway-bridge with DRAGINO LG308 Gateway

Hi,
I have recently changed to ChirpStack Private Server and installed this docker version. Seems to work pretty good. But my gateway isn't connecting, or at least in the Application Server it still says
Last seen: Never
When looking for the logs, docker-compose logs will show:
chirpstack-gateway-bridge_1      | time="2020-06-11T07:55:32Z" level=error msg="integration/mqtt: connection error" error="Network Error : dial tcp <IP_ADDRESS>:1883: connect: connection refused"

I followed this guide to install in the gateway: https://www.chirpstack.io/gateway-bridge/gateway/dragino/ to install

This is the configuration file on docker:
chirpstack-gateway-bridge.toml.txt
(I recently changed <IP_ADDRESS> to chirpstack-network-server as shown in the file)

And this the file on the gateway:
GTWFILE_chirpstack-gateway-bridge.toml.txt

(Maybe I'm missing sth?)
Any help is really useful.
Nicolas

@Rokscript08 as the issue does not look like a problem to report, I suggest to write this issue down into the Community Forum.  In there, you will find a lot people that may help you on this.
From what I see, it looks like your MQTT Broker in down. Double check that it's running.

Whoops my bad. Thank you.


Optimize conversion of primitive arrays to string

This PR improves speed of binding arrays in prepared statements
JMH Results:
BindTest.benchBindDoubleArray  thrpt   15  3745576.179 ± 389141.253  ops/s
BindTest.benchBindDoubleArray  thrpt   15  5544670.142 ± 138029.538  ops/s
+48%

BindTest.benchBindFloatArray   thrpt   15  4127465.414 ±  67650.486  ops/s
BindTest.benchBindFloatArray   thrpt   15  5684227.118 ±  77065.492  ops/s
+37%

BindTest.benchBindIntArray     thrpt   15  7047571.132 ± 143269.075  ops/s
BindTest.benchBindIntArray     thrpt   15  15777212.957 ± 944574.097  ops/s
+120%

BindTest.benchBindLongArray    thrpt   15  7000060.972 ±  78086.627  ops/s
BindTest.benchBindLongArray    thrpt   15  13688058.489 ± 507957.236  ops/s
+95%

BindTest.benchBindShortArray   thrpt   15  7293179.203 ±  80167.534  ops/s
BindTest.benchBindShortArray   thrpt   15  15914677.941 ± 237247.522  ops/s
+118%

 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.


wip: tweak the generated python bindings

The generated Python bindings are a lot more opinionated than the C api itself. At moment, I'm adjusting some of the hardcoded behavior; but this might evolve into a slightly more extensible interface for library-specific stuff.

By default, find_library does not know about the active Conda environment on OSX; hence the current use of it it makes it harder to deploy the produced shared library with conda. As a quick fix, I check this explicitly.

It would be nice if we could specify these parameters via an argument to the generated python bindings function. Then it would be easier to extend for these kinds of things at build-the-shared-library time.

It would be nice if we could specify these parameters via an argument to the generated python bindings function. Then it would be easier to extend for these kinds of things at build-the-shared-library time.

Yes, I agree. I'm experimenting with this a bit, although I think more broadly we should just make the definitions available for anybody to use (i.e. not necessarily wrap in opaque python-generator closure, but rather have define-library produce something that can be passed off to a custom python, ruby, whatever generator).

Yes, the way I wrote this really optimized for two goals:

No pollution of any global namespaces.
Expediency and minimal amount of code to function
There's not much extensibility, so the guts might/should get reworked to support library authors and custom configurations more.

This is a relatively modest change, and is fine for now (imo). In the longer run we will have our eye on more general mechanisms.


Jabauman @next npm updates

Summary:

The topic Installing Zowe CLI with Node.js 16 on Windows has not been published to the live docs site. We added Installing Zowe CLI with Node.js 16 on Windows to the TOC immediately after Setup > Installing Zowe CLI > Installing the ssh2 Package for Zowe CLI.

In the topic Installing Zowe CLI with Node.js 16 on Windows, added the following note after the second bullet:
Note: The TGZ bundle that we supply is designed to support offline installation (the computer is not connected to the Internet). We recently detected (and reported) an issue with NPM that prevents you from installing the TGZ bundle when the computer is not connected to the Internet. If you encountered this problem, we ask you to upvote the issue (NPM fails to globally install packages from TGZ bundle without Internet connection #4332).

https://github.com/zowe/docs-site/blob/jabauman-%40next-npm-updates/docs/user-guide/cli-install-cli-nodejs-windows.md

Added a note to Setup > Installing Zowe CLI > System requirements under Client side > Node.js bullet: Note: If you are installing Zowe CLI with Node.js 16 on a Windows operating system, see Installing Zowe CLI with Node.js 16 on Windows.

https://github.com/zowe/docs-site/blob/jabauman-%40next-npm-updates/docs/user-guide/systemrequirements-cli.md

In the topic: Install the Zowe CLI @next version > Prerequisites > added 3rd bullet: If you are installing Zowe CLI @next on a computer that is running a Windows operating system, see Installing Zowe CLI with Node.js 16 on Windows.

https://github.com/zowe/docs-site/blob/jabauman-%40next-npm-updates/docs/user-guide/cli-install-cli-next.md
@nannanli :  Ashley, at some point we need to merge these changes into the master branch. pleas dont merge until the PR gets its required approvals.
Thx!

@t1m0thyj is Node 16 the only prereq version of Node for the Zowe CLI @next version? If not, I think we want to use the same language as before:

Node.js: Install a currently supported Node.js LTS version. For an up-to-date list of supported LTS versions, see Nodejs.org.
Tip:  You might need to restart the command prompt after installing Node.js. Issue the command node --version to verify that Node.js is installed.
Note: If you are installing Zowe CLI with Node.js 16 on a Windows operating system, see Installing Zowe CLI with Node.js 16 on Windows.

@JamesBauman do you know why this PR changes 2k+ files?

@t1m0thyj is Node 16 the only prereq version of Node for the Zowe CLI @next version? If not, I think we want to use the same language as before:

Node.js: Install a currently supported Node.js LTS version. For an up-to-date list of supported LTS versions, see Nodejs.org.
Tip:  You might need to restart the command prompt after installing Node.js. Issue the command node --version to verify that Node.js is installed.
Note: If you are installing Zowe CLI with Node.js 16 on a Windows operating system, see Installing Zowe CLI with Node.js 16 on Windows.

Good point, the following bullet points make it look like Node.js 16 and npm 7/8 are prerequisites. But really the prerequisites have not changed for CLI vNext, we just want to add notes for Node.js 16 and npm7/8 users.

@MikeBauerCA  - i believe there are so many files because i specified to merge into the master branch...  perhaps i need to merge to staging and then from staging into master.  stay tuned i'll double check and verify....thx

Closing this PR....  Created https://github.com/zowe/docs-site/pull/2021/  to update the articles and sidebar


Investigate whether some CSS/JS modules can be removed easily

E.g. looks like we include semantic-ui CSS which is 600K uncompressed and 90K compressed. We likely don't use most of this stuff.

@marcinbodnar @Patrick1904 can you take a look and make rough estimate on how long it will take to get rid of semantic-ui?
I assume it should be possible to provide our internal shims for Grid, List, Form, Image and other commonly used components to avoid changing much code.

@vgrichina My rough estimate would be about 40-50h. We got rid of a lot of it since we last talk about it, but there are still some problematic elements.

@marcinbodnar so based on current state looks like following components are still used from semantic-ui-react:

[ ] Image
[ ] Button
[ ] List
[ ] Form
[ ] Segment
[ ] Grid
[ ] Header
[ ] Container
[ ] Divider
[ ] Popup
[ ] Modal
[ ] Responsive
[ ] Input

I think we need to determine which of these we want to re-implement in wallet (probably makes sense for most commonly used) and which to just remove altogether (makes sense for least commonly used).
I assume we already made a lot of progress since last discussion about this, right?

@marcinbodnar so based on current state looks like following components are still used from semantic-ui-react:

[ ]  Image
[ ]  Button
[ ]  List
[ ]  Form
[ ]  Segment
[ ]  Grid
[ ]  Header
[ ]  Container
[ ]  Divider
[ ]  Popup
[ ]  Modal
[ ]  Responsive
[ ]  Input

I think we need to determine which of these we want to re-implement in wallet (probably makes sense for most commonly used) and which to just remove altogether (makes sense for least commonly used).
I assume we already made a lot of progress since last discussion about this, right?

@vgrichina thanks for doing the audit. The Popup is the main component still missing. It'll take a few days to replace/remove the remaining semantic-ui-react stuff. I'll make sure to prioritize this better. @marcinbodnar we can coordinate async.

@Patrick1904 sure, at this moment I have a lot of things on my plate, that are a bit urgent. But I will have that in mind, I can handle it whenever there will be nothing more urgent.

@Patrick1904 sure, at this moment I have a lot of things on my plate, that are a bit urgent. But I will have that in mind, I can handle it whenever there will be nothing more urgent.

Yep totally I'll be able to handle most of this.

We made quite a lot of progress on this with the latest nav and dashboard redesign.
There are four main pages left that are built with semantic-ui:

https://wallet.testnet.near.org/full-access-keys
https://wallet.testnet.near.org/authorized-apps
https://wallet.testnet.near.org/sign
https://wallet.testnet.near.org/login

In addition, the current footer is built with semantic-ui, and could use a redesign anyway.
cc @corwinharrell

fixed by Replace semantic-ui modal/tooltip components #1525


[operations] Implement process_attester_slashing

https://github.com/lambdaclass/lambda_ethereum_consensus/blob/dd0a0523e6be2a21fa3f6a96d4466926307d236c/docs/specs/beacon-chain.md?plain=1#L2709-L2724
See Spec tests format: https://github.com/ethereum/consensus-specs/tree/dev/tests/formats/operations
Acceptance criteria:

Run corresponding spec tests

Hey may I get this one? also in the other issue I saw
https://github.com/lambdaclass/lambda_ethereum_consensus/issues/300#issuecomment-1766348829
seems like 2nd question remained unanswered could you answer that as well?

Hey may I get this one? also in the other issue I saw #300 (comment) seems like 2nd question remained unanswered could you answer that as well?

Question answered.

Must have missed it though may I get the issue 😄


Is it possible to use it in container which is not the html / body?

I would like to use the plugin with scrollable contant in a container. It shouldn't scroll the whole page, just the content of the container. Is there an optionfor it?

Not at the moment


[pa11y-ci] Add 'hideElements' rules to hide all pa11y errors

[x] Make the pa11y-ci job green by hiding them
[ ] Analyse the errors and fix them if possible
[x] Bump pa11y-ci from 2.4.2 to 3.0.0
[ ] Find a way to use the HTML reporter but still log the results in CLI

[ ] Check https://github.com/pa11y/pa11y-ci/commit/5c842cf1b9fe2867b70ff5354851d985be8d71c4 available since 3.0.0

[ ] See if we can use npx maybe, since Chromium is a huge download or see if we can cache puppeteer on CI

Context
Tried it first in this PR in my forked version of Bootstrap among other things — All check have passed.
There are still several TODO topics to tackle in https://github.com/twbs/bootstrap/pull/29315.
The target of this PR would be main-xmr-pa11y-ci.
I chose here to focus on having a green pa11y-ci job by hiding all elements reported as issues; it would help us to track the new issues that will be merged into main while trying to fix the current ones.
Indeed, pa11y-ci is a bit unstable at the moment and it becomes easier to check regression if you know that the job can be green (everything is OK) instead of having to analyze the red one that can be a regression or a crash...
I was thinking of the following process:
Fix existing issues

Done here Hide all the errors reported by pa11y-ci to have a green job.
For each hideElements rule, analyze it, define if it is a real issue and fill the table below with the analysis in the last column.
If the issue can be fixed, open a PR and write its reference in the table below.
When the issue is fixed / merged, remove the hideElements rule.

Handle new issues
After each rebase of the main-xmr-pa11y-ci, the pa11y-ci job would be executed by GitHub CI. If we observe new issues in the artifact: we should write a new hideElements rule and add a new line in the table below.
Pa11y issues tracker
Total without any hideElements: 568 errors
Legend

:stop_button: Analysis must be done
:hourglass: Work In Progress — A PR is probably being reviewed
:white_check_mark: Analysis done — Keep the hideElements rule
:heavy_check_mark: Analysis done — Removed the hideElements rule

Missing submit button in Algolia search form

:white_check_mark:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid

First detected in
/docs/5.1/about/overview

Path
(html > body > nav > div > form)

HTML element
<form class="bd-search position-relative me-auto"> <span class="algolia-aut...</form>

hideElements rule
.bd-search

Errors removed
99

Analysis
Algolia doesn't provide a type="submit" HTML element associated to the form so we probably cannot do anything about it and must keep this rule.

Insufficient contrast for text muted in the footer

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/about/overview/

Path
(html > body > footer > div > div > div:nth-child(1) > ul > li:nth-child(1))

HTML element

Designed and built with all the...

hideElements rule
footer > div > div > div:nth-child(1) > ul > li

Errors removed
306

Analysis
TODO

Insufficient contrast for "Bootstrap" in the footer

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/examples/blog/

Path
(html > body > footer > p:nth-child(1) > a:nth-child(1))

HTML element
Bootstrap

hideElements rule
footer > p > a

Errors removed
6

Analysis
TODO

Insufficient contrast for green text with gray background

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.3:1. Recommendation:  change background to #feffff.

First detected in
/docs/5.1/about/brand/

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(9) > div:nth-child(1) > strong)

HTML element
Correct

hideElements rule
div:nth-child(4) > main > div:nth-child(3) > div:nth-child(9) > div > strong

Errors removed
3

Analysis
TODO

Insufficient contrast for warning outline buttons on white background

:white_check_mark:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 1.63:1. Recommendation:  change text colour to #967100.

First detected in
/docs/5.1/components/buttons

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(17) > button:nth-child(5)) (but also number 6 and 7)

HTML element
<button type="button" class="btn btn-outline-warning">Warning</button>

hideElements rule
button.btn.btn-outline-warning, button.btn.btn-outline-info, button.btn.btn-outline-light

Errors removed
12

Analysis
A message is already displayed in the documentation to explain that Some of the button styles use a relatively light foreground color, and should only be used on a dark background in order to have sufficient contrast.

Insufficient contrast for outline search button in Examples > Carousel

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.4:1. Recommendation:  change background to #010509.

First detected in
/docs/5.1/examples/carousel/

Path
(#navbarCollapse > form > button)

HTML element
<button class="btn btn-outline-success" type="submit">Search</button>

hideElements rule
nav.navbar-dark.bg-dark button.btn.btn-outline-success

Errors removed
6

Analysis
TODO

Insufficient contrast for gray text with light gray background in Examples > Cheatsheet

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/cheatsheet/

Path
(html > body > aside > h2)

HTML element

On this page

hideElements rule
aside > h2

Errors removed
2

Analysis
TODO

Missing legend element in fieldset in Examples > Cheatsheet

:stop_button:

Error
Fieldset does not contain a legend element. All fieldsets should contain a legend element that describes a description of the field group.

First detected in
/docs/5.1/examples/cheatsheet/

Path
(#disabled-forms > div:nth-child(2) > div > form > fieldset)

HTML element
<fieldset disabled="" aria-label="Disabled fieldset example">
...</fieldset>

hideElements rule
fieldset *:not(legend) doesn't seem to work so #disabled-forms > div:nth-child(2) > div > form > fieldset

Errors removed
2

Analysis
TODO

Missing submit button in Example > Cheatsheet > Floating labels

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/examples/cheatsheet/

Path
(#floating-labels > div:nth-child(2) > div > form)

HTML element
<form> <div class="form-flo...</form>

hideElements rule
form:not(:has(> [type=submit])) doesn't work so #floating-labels > div:nth-child(2) > div > form

Errors removed
2

Analysis
TODO

Insufficient contrast for nav pills used in Examples > Cheatsheet > Scrollspy

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/examples/cheatsheet/

Path
(#navbar-example2 > ul > li:nth-child(2) > a)

HTML element
Second

hideElements rule
.navbar.navbar-light > .nav.nav-pills > li > a.nav-link

Errors removed
6

Analysis
Linked to another error in Components > Scrollspy

Insufficient contrast for green texts in Examples > Checkout

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.3:1. Recommendation:  change background to #feffff.

First detected in
/docs/5.1/examples/checkout/

Path
(html > body > div > main > div:nth-child(2) > div:nth-child(1) > ul > li:nth-child(4) > div > h6)

HTML element

Promo code

hideElements rule
.bg-light > .text-success

Errors removed
6

Analysis
TODO

Insufficient contrast for disabled dropdown item in Components > Dropdowns

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.07:1. Recommendation:  change text colour to #6f777f.

First detected in
/docs/5.1/components/dropdowns/

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(79) > ul > li:nth-child(2) > a)

HTML element
Disabled link

hideElements rule
ul.dropdown-menu > li > a.dropdown-item.disabled

Errors removed
1

Analysis
TODO

Insufficient color contrast for light links with light background in Helpers > Colored Links

:white_check_mark:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 1.63:1. Recommendation:  change text colour to #967100

First detected in
/docs/5.1/helpers/colored-links/

Path
(html > body > div:nth-child(4) > main > div:nth-child(2) > div:nth-child(2) > a:nth-child(5))

HTML element
Warning link (same thing for link-info and link-light) (see outline buttons)

hideElements rule
a.link-warning, a.link-info, a.link-light

Errors removed
3

Analysis
A message is already displayed in the documentation mentioning that Some of the link styles use a relatively light foreground color, and should only be used on a dark background in order to have sufficient contrast.

Insufficient contrast for search button with green outline in Components > Navbar

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.3:1. Recommendation:  change background to #feffff.

First detected in
/docs/5.1/components/navbar/

Path
(#navbarSupportedContent > form > button)

HTML element
<button class="btn btn-outline-success" type="submit">Search</button> (same for btn-outline-secondary and btn-outline-primary)

hideElements rule
nav.navbar.navbar-light.bg-light .btn.btn-outline-success, nav.navbar.navbar-light.bg-light .btn.btn-outline-secondary, nav.navbar.navbar-light .btn.btn-outline-primary

Errors removed
10

Analysis
TODO

Duplicate "constructor" id in Components / List Group

:white_check_mark:

Error
Duplicate id attribute value "constructor" found on the web page.

First detected in
/docs/5.1/components/list-group/

Path
(#constructor)

HTML element

constructor List Groups

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/list-groups/

Path
(html > body > div:nth-child(6) > label:nth-child(4) > span > small)

HTML element
 <svg class="bi me-1" w...

hideElements rule
label.bg-light .text-muted

Errors removed
1

Analysis
TODO

Insufficient contrast for nav pills used in Components > Scrollspy

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/components/scrollspy

Path
(#navbar-example3 > nav > nav:nth-child(2) > a:nth-child(1))

HTML element
Item 1-1

hideElements rule
nav.navbar-light.bg-light nav.nav.nav-pills > a.nav-link

Errors removed
6

Analysis
Linked to another error in Examples > Scrollspy

Insufficient contrast for text muted with light background in Examples > Dashboard

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/dashboard/

Path
(#sidebarMenu > div > h6 > span)

HTML element
Saved reports

hideElements rule
.sidebar.bg-light .text-muted

Errors removed
2

Analysis
TODO

Missing submit button in Forms > Floating Labels

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/forms/floating-labels/

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(7) > form)

HTML element
<form class="form-floating"> <input type="email" class="f...</form>

hideElements rule
form.form-floating

Errors removed
2

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/jumbotron/

Path
(html > body > main > div > div:nth-child(3) > div:nth-child(2) > div > button)

HTML element
<button class="btn btn-outline-secondary" type="button">Example button</button>

hideElements rule
.bg-light .btn.btn-outline-secondary

Errors removed
2

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/examples/navbars/

Path
(#navbarsExample02 > form) and other ids

HTML element
<form> <input class="form-c...</form>

hideElements rule
div[id^=navbarsExample] > form

Errors removed
10

Analysis
TODO

TODO: Add a title

:stop_button:

Error
Anchor element found with a valid href attribute, but no link content has been supplied.

First detected in
/docs/5.1/examples/headers/

Path
(html > body > main > div:nth-child(6) > header > a)

HTML element
 <svg class="bi me-2" w...

hideElements rule
main > header > div > div > a, main > div > header > a, main header > div > div > div > a

Errors removed
5

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This textinput element does not have a name available to an accessibility API. Valid names are: label element, title undefined, aria-label undefined, aria-labelledby undefined.  /// This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.

First detected in
/docs/5.1/examples/checkout/

Path
(html > body > div > main > div:nth-child(2) > div:nth-child(1) > form > div > input)

HTML element
<input type="text" class="form-control" placeholder="Promo code">

hideElements rule
input.form-control[placeholder='Promo code'], input.form-control[placeholder='رمز ترويجي']

Errors removed
4

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/checkout

Path
(html > body > div > main > div:nth-child(2) > div:nth-child(2) > form > div:nth-child(1) > div:nth-child(4) > label > span)

HTML element
(Optional)

hideElements rule
.bg-light form small.text-muted, .bg-light form span.text-muted

Errors removed
6

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/checkout/

Path
(html > body > div > footer > p)

HTML element

© 2017–2021 Company Name

hideElements rule
.bg-light footer.text-muted > p

Errors removed
2

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/examples/checkout

Path
(html > body > div > footer > ul > li:nth-child(1) > a)

HTML element
Privacy

hideElements rule
.bg-light footer > ul > li > a

Errors removed
6

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/examples/dropdowns

Path
(#dropdownFilter > div:nth-child(1) > form)

HTML element
<form class="p-2 mb-2 bg-light border-bottom"> <input type="search" cla...</form>

hideElements rule
#dropdownFilter > div > form

Errors removed
4

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This button element does not have a name available to an accessibility API. Valid names are: title undefined, element content, aria-label undefined, aria-labelledby undefined.

First detected in
/docs/5.1/examples/dropdowns

Path
(#dropdownCalendar > div > div > div:nth-child(1) > button:nth-child(1))

HTML element
<button class="btn cal-btn" type="button"> <svg class="bi" widt...</button> and other elements of #dropdownCalendar

hideElements rule
#dropdownCalendar > div > div > div > select, #dropdownCalendar > div > div > div > button

Errors removed
4

Analysis
TODO

TODO: Add a title

:stop_button:

Error
Anchor element found with a valid href attribute, but no link content has been supplied.

First detected in
/docs/5.1/examples/footers

Path
(html > body > div:nth-child(2) > footer > a) and different combination of  in footers

HTML element
 <svg class="bi me-2" wid...

hideElements rule
footer > p + a[href='/'], footer > div > a[href='/'], footer ul > li > a[href='#']

Errors removed
9

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/examples/footers

Path
(html > body > div:nth-child(10) > footer > div:nth-child(1) > div:nth-child(4) > form)

HTML element
<form>
Subscribe to our...</form>

hideElements rule
div:nth-child(10) > footer > div:nth-child(1) > div:nth-child(4) > form

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 1.63:1. Recommendation:  change text colour to #967100.

First detected in
/docs/5.1/examples/grid

Path
(html > body > main > div:nth-child(1) > p:nth-child(25))

HTML element

 No grid classes are nece...

hideElements rule
p.text-warning

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.29:1. Recommendation:  change text colour to #fff.

First detected in
/docs/5.1/examples/headers/

Path
(html > body > main > header:nth-child(8) > div > div > ul > li:nth-child(1) > a)

HTML element
Home

hideElements rule
header div.bg-dark a.text-secondary, header.bg-dark a.text-secondary

Errors removed
2

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/examples/headers/

Path
(html > body > main > header:nth-child(8) > div > div > form) and other header examples as well

HTML element
<form class="col-12 col-lg-auto mb-3 mb-lg-0 me-lg-3"> <input type="search"...</form>

hideElements rule
header:nth-child(8) > div > div form, header:nth-child(10) > div > div form, header:nth-child(12) > div > div form, header:nth-child(16) > div form, header:nth-child(18) > div > div form

Errors removed
5

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/heroes/

Path
(html > body > main > div:nth-child(8) > div > div:nth-child(2) > form > small)

HTML element
By clicking Sign up, you agree ...

hideElements rule
form.bg-light small.text-muted

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.29:1. Recommendation:  change text colour to #fff.

First detected in
/docs/5.1/examples/heroes/

Path
(html > body > main > div:nth-child(12) > div > div > p)

HTML element

Quickly design and customize re...

hideElements rule
div.bg-dark.text-secondary p

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/examples/navbars/

Path
(html > body > main > div:nth-child(12) > div > div > div > p:nth-child(2) > code)

HTML element
.container

hideElements rule
.bg-light code

Errors removed
6

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change background to #fff.

First detected in
/docs/5.1/exampless/navbars

Path
(html > body > main > div:nth-child(12) > div > div > div > p:nth-child(2) > a:nth-child(2))

HTML element
top

hideElements rule
.bg-light a

Errors removed
10

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.45:1. Recommendation:  change background to #fafbfc.

First detected in
/docs/5.1/examples/sticky-footer

Path
(html > body > footer > div > span)

HTML element
Place sticky footer content her...

hideElements rule
footer.bg-light span.text-muted

Errors removed
2

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/components/navbar

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(55) > nav > form) and another form + button

HTML element
<form class="container-fluid">
 ...</form>

hideElements rule
main > div:nth-child(3) > div:nth-child(55) > nav > form, main > div:nth-child(3) > div:nth-child(59) > nav > form, main > div:nth-child(3) > div:nth-child(133) > nav > div > button

Errors removed
3

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.27:1. Recommendation:  change text colour to #fff.

First detected in
/docs/5.1/utilities/opacity

Path
(html > body > div:nth-child(4) > main > div:nth-child(2) > div:nth-child(3) > div:nth-child(1)) but concerns the 4 examples

HTML element

100%

hideElements rule
.opacity-100.bg-primary.text-light, .opacity-75.bg-primary.text-light, .opacity-50.bg-primary.text-light, .opacity-25.bg-primary.text-light

Errors removed
4

Analysis
TODO

TODO: Add a title

:stop_button:

Error
Not all th elements in this table have a scope attribute. These cells should contain a scope attribute to identify their association with td elements

First detected in
/docs/5.1/examples/pricing

Path
(html > body > div > main > div:nth-child(3) > table)

HTML element
`  ...``

hideElements rule
main > div:nth-child(3) > table.table.text-center

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 4.3:1. Recommendation:  change background to #fbfbfb.

First detected in
/docs/5.1/examples/sign-in

Path
(html > body > main > form > p)

HTML element

© 2017–2021

hideElements rule
body > main > form > p.text-muted

Errors removed
1

Analysis
TODO

TODO: Add a title

:stop_button:

Error
This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

First detected in
/docs/5.1/components/toasts/

Path
(html > body > div:nth-child(4) > main > div:nth-child(3) > div:nth-child(49) > form)

HTML element
<form>
 <labe...</form>

hideElements rule
main > div:nth-child(3) > div:nth-child(49) > form

Errors removed
1

Analysis
TODO

@julien-deramond thanks for the PR! I'm going to rebase the base branch later so you will need to rebase this too. I'd say it'd be better if you proceeded with the fixes so that we get an idea of what needs to be fixed. Perhaps the footer contrast fixes could land separately on main, though.

@XhmikosR Yes, I was thinking this PR as a tracker:

If the error can't be or shouldn't be fixed, it stays in this PR in the hideElements list / rules.
If the error can be fixed, fix it into the main branch, rebase this branch, remove the rules from the hideElements
When all errors have been studied (fixed or hidden) this PR would be safe to merge (apart from the technical issues mentioned in your original PR and copied in this one's description).

I pushed another patch which attempts to make use of the new reporter option. It doesn't seem to work, though.

I tried another approach in https://github.com/julien-deramond/bootstrap/pull/4 with a reduced test case (simpler sitemap.xml).
In https://github.com/julien-deramond/bootstrap/runs/4410421235?check_suite_focus=true, we can see the CLI report and after that:
Run actions/upload-artifact@v2
With the provided path, there will be 2 files uploaded
Total size of all the files uploaded is 2431 bytes
Finished uploading artifact pa11y-ci-results. Reported size is 2431 bytes. There were 0 items that failed to upload
Artifact pa11y-ci-results has been successfully uploaded!

It seems that the HTML report is OK (contains 2 files). However I don't see the artifact, I can't download it anywhere.

Note to myself: modify this PR after the merge of https://github.com/twbs/bootstrap/pull/35894 which should fix some a11y errors found by pa11y.


Optimize Bypass Time for Loot-links Without Parameter r

Issue:
When dealing with loot-links that lack the r parameter (e.g., https://linksloot.net/s?dCQN), the bypass process typically takes around 60 seconds to complete. This delay negatively impacts the efficiency and user experience.
Objective:
Implement a solution to reduce the bypass time for loot-links without the r parameter, aiming to make the process faster and more efficient.
Steps to Reproduce:

Go to the link: https://linksloot.net/s?dCQN
Observe the time taken for the process to complete (approximately 60 seconds).
Expected Outcome: The bypass time should be significantly reduced, ideally to under 10 seconds.

Example loot-link without the r parameter: https://linksloot.net/s?dCQN
Version
Manifest-v3
What browser(s) are you seeing the problem on?
Chrome browsers (includes brave, edge, opera, etc)
What platform are you seeing the problem on?
Computer (Windows, Linux, MacOS)
Anything else?
No response

Can't reproduce this. Navigating to the link, it complains about adblock being enabled (even with extension disabled) then I get sent to a FF extension page as it should.

I only have to wait about 3-4 seconds on average before seeing the extension page.

This extension doesnt work on have of the sites for me


A valid company search does not always return reviews

There seems to be some variation in the base URL when searching for companies.  Sometimes and overview is returned and sometimes the base link to reviews is returned.  When an overview link is returned no reviews can be downloaded.

The latest release should have fixed this issue


chore(dependabot): Revert "chore: Add dependabot for github actions"

Reverts Betterment/charlatan#14
curious if reverting this will fix the issue with the lcov report. not sure why but i wanna try it.
/domain @btrautmann @CelticMajora
/no-platform

nanda? you still working?

nanda you still there?


4.23 Example not working  "LogPython: No module named 'TensorFlowComponent'"

I recently upgraded computers and am having trouble getting this working again.  I haven't change my specs all that much however this project used to work on my old computer and now it does not on my new one.
When I press play the level starts, doesn't throw any error messages, and lets me press the keyboard to change the numbers displayed.  It seems to skip entirely over the training portion and it no longer does anything when I press "F".  I noticed I was getting an error message in my output log, however I'm not sure how to correct it.  I understand python but am new to Unreal Engine.
Windows 10
Output Log below
LogTemp: Repeating last play command: Selected Viewport
LogBlueprintUserMessages: Early PlayInEditor Detection: Level '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel' has LevelScriptBlueprint '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist' with GeneratedClass '/Game/ExampleAssets/Maps/Mnist.Mnist_C' with ClassGeneratedBy '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist'
LogPlayLevel: PlayLevel: No blueprints needed recompiling
LogHMD: Initializing OVRPlugin session
LogHMD: Allocating Oculus 3296 x 1776 rendertarget swapchain
PIE: New page: PIE session: Mnist (May 12, 2021, 12:51:47 PM)
LogPlayLevel: Creating play world package: /Game/ExampleAssets/Maps/UEDPIE_0_Mnist
LogPlayLevel: PIE: StaticDuplicateObject took: (0.002097s)
LogAIModule: Creating AISystem for world Mnist
LogPlayLevel: PIE: World Init took: (0.000749s)
LogPlayLevel: PIE: Created PIE world by copying editor world from /Game/ExampleAssets/Maps/Mnist.Mnist to /Game/ExampleAssets/Maps/UEDPIE_0_Mnist.Mnist (0.002954s)
LogUObjectHash: Compacting FUObjectHashTables data took   1.17ms
LogInit: XAudio2 using 'Headphones (2- Rift S)' : 2 channels at 48 kHz using 16 bits per sample (channel mask 0x3)
LogInit: FAudioDevice initialized.
LogLoad: Game class is 'GameModeBase'
LogWorld: Bringing World /Game/ExampleAssets/Maps/UEDPIE_0_Mnist.Mnist up for play (max tick rate 0) at 2021.05.12-19.51.48
LogPython: Error: No module named 'TensorFlowComponent'
LogWorld: Bringing up level for play took: 0.001044
LogOnline: OSS: Creating online subsystem instance for: :Context_5
PIE: Play in editor start time for /Game/ExampleAssets/Maps/UEDPIE_0_Mnist 0.469
LogBlueprintUserMessages: Late PlayInEditor Detection: Level '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel' has LevelScriptBlueprint '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist' with GeneratedClass '/Game/ExampleAssets/Maps/Mnist.Mnist_C' with ClassGeneratedBy '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist'
SocketIOLog: SocketIO Connected with session: 0OyiC6LCh3RttJtxABOY
SocketIOLog: SocketIO 0OyiC6LCh3RttJtxABOY connected to namespace: /
LogBlueprintUserMessages: Early EndPlayMap Detection: Level '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel' has LevelScriptBlueprint '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist' with GeneratedClass '/Game/ExampleAssets/Maps/Mnist.Mnist_C' with ClassGeneratedBy '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist'
LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden
LogWorld: BeginTearingDown for /Game/ExampleAssets/Maps/UEDPIE_0_Mnist
LogWorld: UWorld::CleanupWorld for Mnist, bSessionEnded=true, bCleanupResources=true
LogPlayLevel: Display: Shutting down PIE online subsystems
LogBlueprintUserMessages: Late EndPlayMap Detection: Level '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel' has LevelScriptBlueprint '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist' with GeneratedClass '/Game/ExampleAssets/Maps/Mnist.Mnist_C' with ClassGeneratedBy '/Game/ExampleAssets/Maps/Mnist.Mnist:PersistentLevel.Mnist'
LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden
LogUObjectHash: Compacting FUObjectHashTables data took   1.03ms
LogPlayLevel: Display: Destroying online subsystem :Context_5
LogSlate: Took 0.000133 seconds to synchronously load lazily loaded font '../../../Engine/Content/Slate/Fonts/Roboto-Light.ttf' (167K)

Points to missing plugin content, did you download the release? (7zip) did you place it in a short root location (less than. 240 char total for binaries)

I modified the standard download name (TensorFlowExamples-ue4.23-v0.7.0-noplugins (1)) to something smaller and deleted my existing Plugin folder and re-added the release (7zip).  Those combination of steps got it working for me, thanks for the quick reply.


Correct attribution for unity model

i dont mean to be a bug a boo
but...
can You change the by GFourteen on the Unity model?
to:
Unity AI Lab
There are  a number of us in the Unity AI Lab that work on the Unity prompts
so just seems off that it sayd "by @GFourteen"
@thomash
im just the guy that writes the 3 cent check a day for the web domain:
https://blog.unityailab.com/unity.html

Sry, but you mentioned the wrong ThomasH. I have nothing to do with Unity or Unity AI


Parse Credentials from URL for Proxies that use auth

When using the plugin against a proxy Code Artifact that utilizes credentials for auth the plugin throws exception for parsing the url.
AttributeError

  'NoneType' object has no attribute 'groups'

  at /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/urllib3/util/url.py:370 in parse_url
      366│
      367│         if authority:
      368│             auth, _, host_port = authority.rpartition("@")
      369│             auth = auth or None
    → 370│             host, port = _HOST_PORT_RE.match(host_port).groups()
      371│             if auth and normalize_uri:
      372│                 auth = _encode_invalid_chars(auth, USERINFO_CHARS)
      373│             if port == "":
      374│                 port = None

The following error occurred when trying to handle this error:

  Stack trace:

  2  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/models.py:382 in prepare_url
      380│         # Support for unicode domain names and paths.
      381│         try:
    → 382│             scheme, auth, host, port, path, query, fragment = parse_url(url)
      383│         except LocationParseError as e:
      384│             raise InvalidURL(*e.args)

  1  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/urllib3/util/url.py:394 in parse_url
      392│
      393│     except (ValueError, AttributeError):
    → 394│         return six.raise_from(LocationParseError(source_url), None)
      395│
      396│     # For the sake of backwards compatibility we put empty

  LocationParseError

  Failed to parse: https://aws/@{}:amazon-{}.d.codeartifact.us-west-2.amazonaws.com/pypi/{}/

  at <string>:3 in raise_from
        1│

The following error occurred when trying to handle this error:

  Stack trace:

  16  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/application.py:329 in run
       327│
       328│             try:
     → 329│                 exit_code = self._run(io)
       330│             except Exception as e:
       331│                 if not self._catch_exceptions:

  15  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/console/application.py:185 in _run
       183│         self._load_plugins(io)
       184│
     → 185│         exit_code: int = super()._run(io)
       186│         return exit_code
       187│

  14  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/application.py:423 in _run
       421│             io.input.set_stream(stream)
       422│
     → 423│         exit_code = self._run_command(command, io)
       424│         self._running_command = None
       425│

  13  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/application.py:465 in _run_command
       463│
       464│         if error is not None:
     → 465│             raise error
       466│
       467│         return event.exit_code

  12  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/application.py:449 in _run_command
       447│
       448│             if event.command_should_run():
     → 449│                 exit_code = command.run(io)
       450│             else:
       451│                 exit_code = ConsoleCommandEvent.RETURN_CODE_DISABLED

  11  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/commands/base_command.py:119 in run
       117│         io.input.validate()
       118│
     → 119│         status_code = self.execute(io)
       120│
       121│         if status_code is None:

  10  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/cleo/commands/command.py:83 in execute
        81│
        82│         try:
     →  83│             return self.handle()
        84│         except KeyboardInterrupt:
        85│             return 1

   9  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/console/commands/publish.py:82 in handle
        80│         )
        81│
     →  82│         publisher.publish(
        83│             self.option("repository"),
        84│             self.option("username"),

   8  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/publishing/publisher.py:86 in publish
        84│         )
        85│
     →  86│         self._uploader.upload(
        87│             url,
        88│             cert=resolved_cert,

   7  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/publishing/uploader.py:125 in upload
       123│
       124│         try:
     → 125│             self._upload(session, url, dry_run, skip_existing)
       126│         finally:
       127│             session.close()

   6  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/publishing/uploader.py:216 in _upload
       214│             # TODO: Check existence
       215│
     → 216│             self._upload_file(session, url, file, dry_run, skip_existing)
       217│
       218│     def _upload_file(

   5  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/poetry/publishing/uploader.py:256 in _upload_file
       254│             try:
       255│                 if not dry_run:
     → 256│                     resp = session.post(
       257│                         url,
       258│                         data=monitor,

   4  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/sessions.py:590 in post
       588│         """
       589│
     → 590│         return self.request('POST', url, data=data, json=json, **kwargs)
       591│
       592│     def put(self, url, data=None, **kwargs):

   3  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/sessions.py:528 in request
       526│             hooks=hooks,
       527│         )
     → 528│         prep = self.prepare_request(req)
       529│
       530│         proxies = proxies or {}

   2  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/sessions.py:456 in prepare_request
       454│
       455│         p = PreparedRequest()
     → 456│         p.prepare(
       457│             method=request.method.upper(),
       458│             url=request.url,

   1  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/models.py:316 in prepare
       314│
       315│         self.prepare_method(method)
     → 316│         self.prepare_url(url, params)
       317│         self.prepare_headers(headers)
       318│         self.prepare_cookies(cookies)

  InvalidURL

  Failed to parse: https://aws/@{}:amazon-{}.d.codeartifact.us-west-2.amazonaws.com/pypi/{}/

  at /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/requests/models.py:384 in prepare_url
      380│         # Support for unicode domain names and paths.
      381│         try:
      382│             scheme, auth, host, port, path, query, fragment = parse_url(url)
      383│         except LocationParseError as e:
    → 384│             raise InvalidURL(*e.args)
      385│
      386│         if not scheme:
      387│             error = ("Invalid URL {0!r}: No schema supplied. Perhaps you meant http://{0}?")
      388│             error = error.format(to_native_string(url, 'utf8'))

Stack traces have sensitive information removed.

Should have a PR ready tomorrow. Just need to fix some typical mypy being mypy stuff.

Resolved by #9