1.15 distroless base

Please provide a description of this PR:
Update base distroless image since there is a fixed CVE

@sergii-ssh: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sergii-ssh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

integ-pilot_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

integ-pilot_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot

analyze-tests_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test analyze-tests

lint_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test lint

integ-operator-controller_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

integ-pilot_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot

analyze-tests_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test analyze-tests

lint_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test lint

integ-operator-controller_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-operator-controller

integ-security_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

integ-pilot_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot

analyze-tests_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test analyze-tests

lint_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test lint

integ-operator-controller_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-operator-controller

integ-security_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security

integ-security-multicluster_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sergii-ssh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-basic-arm64

integ-security-istiodremote_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-istiodremote

integ-helm_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-helm

integ-pilot_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot

analyze-tests_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test analyze-tests

lint_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test lint

integ-operator-controller_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-operator-controller

integ-security_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security

integ-security-multicluster_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-security-multicluster

integ-pilot-istiodremote-mc_istio
0344d9ec58f2495bdb3be9a7e2e9c5a0f8a53fe5
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Looks like this is based against the wrong branch. Normally, we would take the PR against the main branch and cherry-pick it to the other branches.

thanks Eric. I've closed it


⚠ AGEG website (redirect) has degraded performance

In 73ad30d, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2309 ms

Resolved: AGEG website (redirect) performance has improved in eb9e551.


Upload Meeting 20240123 document

What type of PR is this?

documentation

What this PR does / why we need it:

Upload 2024/01/23 meeting document

Sorry for the delay
Which issue(s) this PR fixes:

NA

Special notes for reviewers:
Changelog input
Additional documentation

Hi @GillesInnov35, Hi @fernandopradocabrillo ,
Could you approve this PR please.
BR
Toshi

Thank you for your approval.  I have just merged this PR.  Sorry for the dealy.
BR
Toshi


Rancher 2.5.9 Monitoring. 1 day after install Cluster Metrics shows Failed to load graph

My Environment:
Rancher 2.5.9, Docker install, Cluster created with Rancher.
Yesterday, I installed monitoring on my new cluster according the the instructions here:
https://rancher.com/docs/rancher/v2.5/en/monitoring-alerting/#enable-monitoring.
Not sure if its relevant, but I did not do the section for Enable Monitoring for use with SSL. (The instructions say to create a secret and "Add the ca, cert, and key files to the secret".  I don't know where to find these files.  I am using Lets Encrypt for my Rancher Certificate (outside Ranchers) and AWS ACM for my load balancer certificates) LE does give me cert and key files, but these are going to change every couple of months so using them as a secret does not make sense.
Current Issues:
From the Monitoring Overview page I can bring up Grafana but I see this error on all the graphs: Unknown error during query transaction. Please check js console logs.  This was working yesterday.

From Cluster Explorer, Cluster Dashboaard, Cluster Metric does not load.  Error is Failed to load graph. This never worked.

Nodes View:
Node CPU and RAM are not populated:

If i click on a node there is no info in the CPU and Memory section.

I see this in my event log:

Not sure what to do at this point.

Closing as stale - I believe this has been fixed, but please re-open if still an issue.


Address design/copy comments for NP

Task/Issue URL: https://app.asana.com/0/0/1205258659015741/f
Description
See asana task
Steps to test this PR
QA optional (see asana task)

Current dependencies on/for this PR:

develop

PR #3457   👈

This comment was auto-generated by Graphite.


.NET Core 3.1 Web API or Blazor Server app

I'm trying to get a .NET Core 3.1 web app running with CoreRT.
I'm starting with the Web API project template before attempting to move to the Blazor Server template.
The first thing I had to do was to solve this exception:

System.Reflection.MissingMetadataException: 'System.Text.Json.JsonPropertyInfoNotNullable<WebApplication1.WeatherForecast,System.DateTime,System.DateTime,System.DateTime>' is missing metadata.

Which I did by adding an rd.xml file as follows:
<?xml version="1.0" encoding="utf-8" ?>
<Directives>
  <Application>
    <Assembly Name="System.Text.Json" Dynamic="Required All" />
  </Application>
</Directives>

The web server now gets up and running at least.
However, requests to the Web API project template /weatherforecast endpoint all just fail, with Chrome reporting localhost didn’t send any data. ERR_EMPTY_RESPONSE.
Also, the compiler is still outputting a huge amount of these warnings - all for System.Text.Json:
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.<>m__Finally1() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.System.Collections.Generic.IEnumerable<TDeclaredProperty>.GetEnumerator() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.System.Collections.IEnumerable.GetEnumerator() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.System.IDisposable.Dispose() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.MoveNext() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.System.Collections.Generic.IEnumerator<TDeclaredProperty>.get_Current() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
EXEC : warning : ignoring debug info for [System.Text.Json]System.Text.Json.JsonPropertyInfoCommon`4+<CreateGenericTDeclaredPropertyIEnumerable>d__28<int8,int8,int8,int8>.System.Collections.IEnumerator.get_Current() [C:\Data\Code\repos\Owned\Bakk\WebApplication1\WebApplication1.csproj]
...

Any thoughts on moving forward with this?
Is it likely to be feasible to get a fairly complex .NET Core 3.1 Blazor web application running with CoreRT at this time? The current 2.1 Web API sample mentions the risk of adding unsupported features and that some functionality might not yet be supported in CoreRT, but I couldn't find any specifics about unsupported features/scenarios elsewhere in the documentation - other than the problem of reflection causing unlinked dependencies.

The current implementation of System.Text.Json serializer is very unfriendly to full AOT compilation due to heavy reflection use. You can always make it work by adding more hints to the linker, but I do not think it is worth the pain. The System.Text.Json is not planning to fix this anytime soon (tracked by https://github.com/dotnet/runtime/issues/1568).
If you would like to use full AOT to compile your app, I would recommend switching to Json serializer that has AOT friendly option, e.g. [Utf8Json with pre-code generation] (https://github.com/neuecc/Utf8Json/#pre-code-generationunityxamarin-supports).
Or not use json serializer at all and directly read/write your json payloads using json reader/writer.

@space-alien what are you looking to gain from AOT compilation with CoreRT for your server side blazor application?

@davidfowl It's for a cross-platform desktop app that would run as a service, with a Blazor UI.

And CoreRT is to get you a small binary output or is there more? How small is acceptable?

I'm turning to AOT for:

Smallest possible binaries. This is important for distribution and for delivering automatic updates. I also expect binary size to have some psychological bearing on the perceived efficiency of the software, although this is not something I can afford to fixate on.
Fast startup time, minimising resource usage. This becomes even more important if users run the app on sign in, rather than as a service.
Perhaps, some additional resistance to decompilation.

In terms of what binary size would be acceptable, I don't have numbers at this stage, but I can say that the preview trimming feature in .NET Core 3 is not yet delivering a viable size reduction for my project.
To illustrate, a Console App template is trimmed to 26,077KB (single file, ReadyToRun) - with a stream of RUNREADYTORUNCOMPILER warnings being emitted. CoreRT, with the most aggressive optimisations, reduces that by 96% to 1,062KB.
And even on a fast system, there is a noticeable lag running the larger trimmed binary (~0.8s before seeing "Hello World" on the first run, with a subtle smaller lag on all subsequent runs), compared to the CoreRT output, which runs instantly every time.
I'm really quite struck by the evident potential of efficient AOT compilation.

Thanks for that response @space-alien!

@davidfowl It's for a cross-platform desktop app that would run as a service, with a Blazor UI.

You mentioned that it would run as a service but then you also mention this:

Fast startup time, minimising resource usage. This becomes even more important if users run the app on sign in, rather than as a service.

How much does startup time matter in this case? Isn't the app going to boot up once and then be running for a long time?

Smallest possible binaries. This is important for distribution and for delivering automatic updates. I also expect binary size to have some psychological bearing on the perceived efficiency of the software, although this is not something I can afford to fixate on.

In terms of what binary size would be acceptable, I don't have numbers at this stage, but I can say that the preview trimming feature in .NET Core 3 is not yet delivering a viable size reduction for my project.

Do you have a feel good number where size no longer matters?

To illustrate, a Console App template is trimmed to 26,077KB (single file, ReadyToRun) - with a stream of RUNREADYTORUNCOMPILER warnings being emitted. CoreRT, with the most aggressive optimisations, reduces that by 96% to 1,062KB.

Have you tried running the IL Linker? It can be much smaller than 26MB.

And even on a fast system, there is a noticeable lag running the larger trimmed binary (~0.8s before seeing "Hello World" on the first run, with a subtle smaller lag on all subsequent runs), compared to the CoreRT output, which runs instantly every time.

The current single file implementation on CoreCLR self extracts on first run which causes that horrible lag. I'm not sure it matters for your scenario but that's something that's going to get fixed with .NET 5.

I'm really quite struck by the evident potential of efficient AOT compilation.

This is great! I'd love to see if you get things working with AOT (Just FYI there are lots of warts in higher level frameworks because they weren't designed to be AOT friendly). If you get this app working, please share what the rd.xml looks like and the workarounds you had to put in place.


Fixing the aspect ration warping of the prod login page

@aevo98765 This looks good to me, can you please cherry-pick it to release-1.0 branch as well.


Your requirements could not be resolved to an installable set of packages

`composer require raiym/instagram-php-scraper phpfastcache/phpfastcache
Using version ^0.12.0 for raiym/instagram-php-scraper
Using version ^9.0 for phpfastcache/phpfastcache
./composer.json has been created
Running composer update raiym/instagram-php-scraper phpfastcache/phpfastcache
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires raiym/instagram-php-scraper ^0.12.0 -> satisfiable by raiym/instagram-php-scraper[v0.12.0].
- Root composer.json requires phpfastcache/phpfastcache ^9.0 -> satisfiable by phpfastcache/phpfastcache[9.0.0].
- phpfastcache/phpfastcache 9.0.0 requires psr/simple-cache ^2.0||^3.0 -> satisfiable by psr/simple-cache[2.0.0, 3.0.0].
- You can only install one version of a package, so only one of these can be installed: psr/simple-cache[1.0.0, 1.0.1, 2.0.0, 3.0.0].
- raiym/instagram-php-scraper v0.12.0 requires psr/simple-cache ~1.0 -> satisfiable by psr/simple-cache[1.0.0, 1.0.1].
- Conclusion: don't install psr/simple-cache 1.0.1 (conflict analysis result)
You can also try re-running composer require with an explicit version constraint, e.g. "composer require raiym/instagram-php-scraper:*" to figure out if any version is installable, or "composer require raiym/instagram-php-scraper:^2.1" if you know which you need.
Installation failed, deleting ./composer.json.`

Same error

https://github.com/postaddictme/instagram-php-scraper/pull/986


Remove react

The project still contains many react references and dependencies, but react isn't used (anymore). They also cause several security warnings of outdated dependencies.

Fixed by #12


Fix broken uart module

These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later
uart module for ESP32 is broken. This PR fixes it.

In the current code, uart:open/1,2 takes uart0, uart1 or uart2 as peripheral option. However, Nif takes either one of UART0, UART1 or UART2. This PR corrects the behaviour of uart:open to match that of Nif.
The Nif of uart module does not send a reply parsable by port:call, which stops the process from executing further codes. This PR fixes that by using port_send_reply function.

The Nif of uart module does not send a reply parsable by port:call, which stops the process from executing further codes.

I noticed that there was another problem on my device which prevents me from processing UART. So this statement might be false. Actually I read the old code twice and cannot find problems. It seems I have to reword the commit comment and CHANGELOG.md so that my commit is just a refactor.

Thank you for this! We just discovered this bug and were discussing it in our Telegram chat, which I would encourage you to join:
https://t.me/atomvm
The core developers and many community members are frequently active there, and we would welcome having you join our conversations.

Thank you for info about Telegram community. I already joined, but I seldom use Telegram, so I didn't noticed this PR is mentioned there.
If there is someone who wants to talk to me there, please don't hesitate to mention me. I'm there with the same username (@aiotter).

Thank you for your review. The current code is already tested, in other words, the commits in the PR are cherry-picked from the branch I build AtomVM from and I'm using it in my daily development.
I'll check your review, correct the code ,reword the commit comment, test it on my device and let you know then.

Tested and it worked. Now it's ready to be merged.


Update docker packages

Thanks for the pull request, @stvstnfrd! I've created OSPR-3307 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.

@stvstnfrd Thank you for your contribution. @ormsbee Is this something you could review?

Ping :)

Thanks for the pull request, @stvstnfrd! I've created OSPR-3514 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.

@natabene If @ormsbee isn't able to look at this, can you find another reviewer please?
Maybe @jmbowman ?

@jmbowman Would you review this?

@stvstnfrd 🎉 Your pull request was merged!
Please take a moment to answer a two question survey so we can improve your experience in the future.


Fix IP not displaying

May require plugin. Removed skin for now.

When rewriting skin, see http://docs.rainmeter.net/manual/plugins/wifistatus and http://docs.rainmeter.net/manual/plugins/sysinfo for examples on how to do this. Probably requires the proper plugins, though.


Update config to include connect

This PR adds connect to the redux example. I thought since it has the import statement, it should also have the call to connect.
Story
I did a dumb copy paste when i came here to see how to add the redux plugin.
Then, i spent several dozens of minutes to figure out why reactotron didn't connect #285
This could hopefully save other people those precious minutes.

Oops, Thank you!  Ya, that was my bad.


Alias Missing - Inc_volume

Either the aliases inc and dec_volume are not done by now or the documentation is pointing to the wrong alias.
Invalid rpc command alias 'inc_volume' has been mapped to 'misc.empty_rpc_call()'

@ChisSoc I think this is due to the move to Pulseaudio. Or did we forget to change it on the WebApp @pabera ?

@maedball which version did you install?

I just did a pull, so latest ;-).
all other aliases are working i am currently trying to change it away from alias to rpc, but since i am still working at the same time i havent gone far by now ;-p
volume:
    Type: RotaryEncoder
    Pins: [6, 12]
    FunctionCW: {volume.ctrl.change_volume, kwargs: {step: 1}}
    FunctionCCW:  {alias: dec_volume,kwargs: {step: 1}}
    action_after_increments: 2

It looks like i have it working, and it is just a documentation thing.
volume:
    Type: RotaryEncoder
    Pins: [6, 12]
    FunctionCW: {alias: change_volume, kwargs: {step: 5}}
    FunctionCCW:  {alias: change_volume, kwargs: {step: -5}}
    action_after_increments: 2

It looks like i have it working, and it is just a documentation thing.

The template needs to be changed as well.

It looks like i have it working, and it is just a documentation thing.

@maedball: Great that you could figure it out yourself. Do you mind referring to the documentation that requires an update? :-)

Just saw this #1730 .. 👍

I am really bad in using Github so hope all is fine and it helps some ppl ;-)
By the way really nice and understandable structure. I wouldn't have figured it out without the well designed documents and structure! Now back to testing, next step gpio rfid reader...

It looks like i have it working, and it is just a documentation thing.

The template needs to be changed as well.

Sorry i just saw that comment, to what template are you referring?

This one :)
https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/future3/develop/resources/default-settings/gpio.example.yaml


toggled between visible and invisible

allows user to toggle visible and invisible of different labels
Example

Usage example
https://github.com/timqian/star-history/issues/62

If no one is assigned or working I wouldn't mind giving it a go

@bikingbadger Glad to hear that. I think no one is working on this~

Thanks @timqian
It's actually something that I was looking when using the chart.

I've managed to catch the click on the actual rectangle of the legend.
What do you think is the best way to change the dataset of the graph or fire a function on the Line class to change the underlying data.
I had an idea of adding a parameter to the dataset like this:
datasets: [{
      label: 'Plan',
      data: [30, 70, 200, 300, 500, 800, 1500, 2900, 5000, 8000],
      hidden: false,
    }

That way the a function of the class can just toggle the hidden value and a user can setup the table with datasets hidden but shown in the legend.
I've pretty new to SVG's and getting around Classes so hope I'm not asking silly questions although I think the method of hwo to show or hide the series could be used commonly between the various charts by way of extending a parent Chart class

@bikingbadger
“a user can setup the table with datasets hidden but shown in the legend”, this sounds interesting to me, but I am not sure if this feature is necessary, I don't see this option in other more mature chart libs likechart.js or echarts


s3 backend: copy fails for some source keys

Using the S3 backend, Copy fails if the source key includes URL-encoded escape sequences like %2f. This is due to a bug in a dependency, which I've reported. In the meantime, a fix is to URL-encode the source key in Copy. (the S3 API expects the source key to be URL-encoded).

fix with new S3 backend (#83) that doesn't use go-cloud.


add validation on multi_zone destination creation, include zone configs in list and show destination output

Coverage decreased (-0.06%) to 54.711% when pulling 14c3c4d1cbf7d0a581ce5909c63e73fb21cf109d on multi_zone_dest_check into<PHONE_NUMBER>ffe956ac57c49f4d6995f723799452 on master.

@venkat1109 I noticed an existing bug in updateDestination and fixed it in this PR. Could you take another look?

Coverage increased (+0.08%) to 54.844% when pulling ef1382aa8fde106fafcf2cee1a689d4d3b40ec89 on multi_zone_dest_check into<PHONE_NUMBER>ffe956ac57c49f4d6995f723799452 on master.

Coverage decreased (-0.3%) to 54.76% when pulling 2e9e97a16aff9c5bb480d4989b7f13e509ab6a77 on multi_zone_dest_check into 5eefb79554ab2952c96cd22267b03a6bcbe4fe44 on master.

Looks good to me !

Coverage decreased (-0.01%) to 54.754% when pulling 301748c784ccf90f1bfea0659500e57941a300f7 on multi_zone_dest_check into 389c4b53271a79777be63962050883470d0e5ffe on master.

Coverage increased (+0.05%) to 54.814% when pulling 301748c784ccf90f1bfea0659500e57941a300f7 on multi_zone_dest_check into 389c4b53271a79777be63962050883470d0e5ffe on master.


warning C4457: declaration of 'mousePos' hides function parameter

The warning is reported on MS VS Community 16.8.2 in https://github.com/eliasdaler/imgui-sfml/blob/5ab660a13bc997225587eea88755f22f999f7ba9/imgui-SFML.cpp#L397

Compiled with /W4 and /WX (https://docs.microsoft.com/en-us/cpp/build/reference/compiler-option-warning-level?view=msvc-160)

Fixed by #143


Add builtin filter function

 Comment by aisk
Thursday Sep 07, 2017 at 16:32 GMT

@trotterdylan Updated!


Update README.md

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/test image-build

Codecov Report

Merging #10 (6ba7ef2) into master (171b52d) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
+ Coverage   52.69%   52.72%   +0.02%
==========================================
  Files         298      298
  Lines       21726    21726
==========================================
+ Hits        11448    11454       +6
+ Misses       9051     9048       -3
+ Partials     1227     1224       -3

Impacted Files
Coverage Δ

pkg/ddc/goosefs/metadata.go
64.28% <0.00%> (+3.29%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

/retest

/lgtm

/approve


ROS# to connect to real robots

Hi Martin, good job on the ros sharp and the examples you are providing. I have managed to get everything working properly and i found your tutorials very easy to understand and accurate to follow.
I was wondering if you would be interested to provide some additional information as to how to actually connect a real life robot and teleoperate using unity, or perhaps make a tutorial for us about it. Lets say a generic ROS supported robot like NAO or Pioneer 3AT.
How easy is to actually move away from the gazeebo simulation to the real world? Is is as simple as installing rosbridge libraries you are providing in the tutorial pages and then roslaunch rosbridge_server rosbridge_websocket.launch?
I believe that a general tutorial demonstrating how to use your library for other robots and in reality would be very beneficial for us robot enthousiasts.
Thank you again for your hard work

Hi @skouicy :

Is is as simple as installing rosbridge libraries you are providing in the tutorial pages and then roslaunch rosbridge_server rosbridge_websocket.launch?

Yes!
Looking at the interfaces from the Unity / Windows side, there is no difference between communicating with a virtual or real robot. We are communicating with a ROS system via rosbridge_suite and Websocket connection. For ROS# I see nothing new to explain or document here.
The nice thing about the virtual Turtlebot 2 example is that everybody can get it running with nothing but one PC and free software.
For simplicity / learnability / maintainability we should focus on explaining only things relevant to ROS#, and as little as possible about connected systems (other robots, ROS, Unity, Visual Studio, C#, JSON, VR/AR Glasses, Rendering, ...). For those topics there is (and will be) better documentation around elsewere already.
Have fun!

Hi @MartinBischoff and thanks for your reply.
I can understand why you dont want to get into the discussion of introducing instructions for connecting robots etc, as this will shift away the point of this wiki.
However, considering that this framework may be sought by people who are perhaps interested in doing such projects, would it be possible to at least provide more information how you have connected the turtlebot 2 as per your youtube video: https://www.youtube.com/watch?v=OytzagQirrk&feature=youtu.be
For instance, as there is no need for a gazeebo implementation etc as indicated on your wiki site, what is the configuration and commands you have issued to the turtlebox in order to get it working?
i.e. install rosbridge server on the robot: $ sudo apt-get install ros-kinetic-rosbridge-server
Do we need the joy_to_twist script? and if so where to place it etc.
I believe that this would be of great benefit to everyone, as we can study your example and configure it accordingly to other robots.
Looking forward to your reply.


Column ordering does not seem to work

It could just be me, but I can't get the column-ordering to work.
I have changed config.yml and added:
tables:
    #columns: []
    columns: ['Level', 'XP', 'Total Kills', 'Death Count']

These are the display names, but I have also tried the objective name (if I understand this correctly).  E.g:
> scoreboard objectives add deathCount deathCount "Death Count"
And then use deathCount in the config:
    columns: ['level', 'XP', 'totalKills', 'deathCount']

But it always displays them in alphabetical order:

Another little issue there is that it would be nice if empty columns could show up.  It was very confusing when I started setting up this plugin that I did not see anything.

I think you are missing a - like so:
tables:
  - # (some comments are here probably)
    columns: ['Level', 'XP', 'Total Kills', 'Death Count']

That - is what makes tables a list of "objects" with columns instead of a single "object" with columns.
For the columns, you cannot enter the scoreboard objective name, that is only possible in objectives.
Thanks for the empty column suggestion! That sounds like a good idea to reduce confusion and I'll add it in the next release.

Ah, thanks.  I cleaned up the file a bit and missed that it was supposed to be a list.
Works perfectly with the added "-"


switched to jobs syntax for CI

I expect people will use this repo as an example to follow. Switching to newer syntax for the YAML.

Thanks!


Can't add Human Player to Match

Hi Team,
I am a firtstime UCP user so maybe the solution is easier than worth your time. So appolagies in advance :)
But for some reason I cant seem to add myself "Human" to matches (or even appear in the first place).
Below screenshots of the lobbies. Tried reinstalling the patch or look for options in the General Menu, but no luck. (and couldn't seem to find the issue in a previous thread)
Thanks in advance for your help and looking forward trying a more advanced game experience!
SinglePlayer Lobby

Crusade Lobby

Did you by any chance activate the option "Spectator Mode enabled" which literally removes you from the game?

Did you by any chance activate the option "Spectator Mode enabled" which literally removes you from the game?

You were 100% correct! Thank you very much for lending me your brainpower... thought I was losing my mind for some time.
Have a great rest of the week and also a good 2021 :)

See, it's the god damn simple things in life that can have the largest impact...
You were 100% correct! Thank you very much for lending me your brainpower... thought I was losing my mind for some time.
Have a great rest of the week and also a good 2021 :)

you might want to close the issue ;)

you might want to close the issue ;)


Add an option to ignore input when the cursor is in the center of the screen.

I would like an option to ignore mouse input events when the cursor is in the middle of the screen. When I play a game, the cursor locks to the center of the screen and it messes with the heatmaps. Could you please add an option to ignore those inputs?

Interesting problem. So there are mouse events recorded during the game, but they're all positioned in screen center?

Yeah, all the heatmap shows is a red dot in the center of the screen. I assume that becuase of how many data points it has at that one position, the rest of the points from normal mouse movement are hidden in the heatmap becuase they are much less concentrated.

Out of curiosity, can you send a screenshot of your heatmap page?
I suppose I can add a generic option, to specify regions of interest or disinterest for mouse events in the configuration file, e.g.
# Ignore mouse events from center of screen
MouseRegionsOfDisinterest = [[0.49, 0.49, 0.2, 0.2]]

How about an application block list? When an application on that list is running then capturing of certain inputs could be deactivated.
That could even have additional benefits outside of this issue.

@shenef An application block list might be even better, indeed. Identified by the executable name or full path.
I will look into it.

@AIP21 @shenef
Assuming you've been using Windows, can you check out this pre-release version: https://erki.lap.ee/stuff/inputscope_1.8.dev6_x64.exe?
There are now application-specific stats as well, and applications can be blacklisted or whitelisted in configuration file, as:
# Path can be absolute or relative like "C:\Python\python.exe" or "python.exe",
# and can contain wildcards like "python*".
ProgramBlacklist = {executable path: [] if all inputs else [input or event type, ]}
ProgramWhitelist = {executable path: [] if all inputs else [input or event type, ]}

e.g.
# Monitor all inputs from Notepad only
ProgramWhitelist = {"notepad.exe": []}

or
# Ignore keypress events from command prompts, and all mouse events from Paint.
ProgramBlacklist = {"cmd.exe": ["keys"], "mspaint.exe": ["mouse"]}

@AIP21 @shenef Comments?

Yes sorry for the late response. It works perfectly for my purposes. I just added the games I wanted ignored and now the new data is much easier to see. Thank you!
This is very specific but would there be a way for me to remove old points that are in the center of the screen? Because my old data is still not visible due to all the old data in the center of the screen.

Excellent. I will release an official new version presently.

This is very specific but would there be a way for me to remove old points that are in the center of the screen?

History can be deleted from the tray menu: right-click on the tray icon, go to "Clear events history", and choose which time period and input to clear.

That's great, thank you. I'm marking this as closed, but feel free to reopen it if needs be.

v1.8 released.

thx, i haven't gotten to actually test the test build but will report back if I encounter any issues with this new release.


Optimizable Nodes

We have a few nodes that should be Optimizable - Fisher Vector, GMM, PCA. Useful for the VOC Pipeline.

Removing from milestone 0.3.0. Delaying until we get a chance to set up proper PCA cost modeling.

Closed by #257


feat(plus): service.addDeployment()

Introduce service.addDeployment() which associates a deployment to a service. The method deployment.expose() now just delegates the work to this method.
Additionally, the logic that added the selector label to the deployment was moved from deployment._toKube() into service.addDeployment() and combined with the logic that installed the selector on the service (which is much more natural).
BREAKING CHANGE: deployment.expose() now takes port as a positional argument (before: deployment.expose({ port }), now: deployment.expose(port)).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

I dont want to get hung up on this now, but i'm taking a mental note to revisit the addDeployment name :)

Yes I am not in love with this name


Decide on build tool

Some of us have default to using Make, but should we really?

Pro: Make is familiar to many of us
Con: Make is awful

Another possible option is to use straightforward bash scripts. We need to plug our build process into Prow, anyway, so it shouldn't matter if it's make test or test.sh.

Personally I prefer make. It's well known and well understood. I don't think it's so bad.

I agree that make is well known and it is used by many people. if you know what it does/doesn't it is not that bad.

Thanks @tliron . Personally I have no preference.  But  make is more ubiquitous and we have our repos and build system to work with it  . Is there any strong reason to change it?

Makefile is not much used in the Go world.
I think it could be a barrier of entry, another new language for potential contributers to learn.

In my opinion it makes little difference whether one uses (ba)sh script or Makefile as they are basically the same, though Makefile tab usage as delimiters occasionally causes some confusion. Another con for make is that an image in which prow job will run has to have make installed and if we're not using any make features, only just execute shell commands with parameters then I'd say we're better with simple shell script.
Bazel which seems what cool kids are using these days can do a lot of magic including reproducible builds or build docker images by itself, but it's enormous and because of otherwise nifty features of caching and sandboxing, one-off builds (which all CI code check jobs are, as pods get discarded after job finishes) take a lot of time. Also at build/test time it's depending on external repos (for example to pull go build templates). Literal 'hello world' takes around 20 seconds to build compared with less than one sec for 'go build'
bazel build //...  0.03s user 0.04s system 0% cpu 20.110 total
go build             0.29s user 0.35s system 78% cpu 0.814 total

Mage seems to be another popular solution, it's basically make but you write your build 'script' in go which is a pro. If we're considering barrier of entry, then with mage it's only GO that one would have to deal with.
So I guess the main question is what advanced features during the build process we need to justify anything more than putting together few commands in shell script.

K8s started with Bazel (because it's an OSS version of an internal Google tool), and ended up ripping it out. Which was a huge effort. It's great for the right use case but I don't see an advantage for us.
I wouldn't want to go with anything other than make or bash - a new tool like mage means we all need to learn something new. Make has been around for > 30 years and is pretty well established, I imagine 99%+ of people developing on Linux have used it...

In my opinion Make is overkill for any Go project. The go compilation process is so straightforward (single command does all) that we don't need any of Make's sophisticated (and complex) task management and optimization.
For that reason I'm in favor of just having bash scripts. We can establish some best practices and uniformity to those. (We would have to do the same for Make, too, should we want to continue using it.)


Create a Login and Register Page

Create a login and register page.
Fields: username, email, password for user registration
user login: username and password
If you can, add validations and errors
Planning to create a page where users could  share stories about adopting a pet, etc

Hi, Please assign this issue to me! I am new to open source. looking to make contribution!

alright go for it


fix: html in callouts

Fixes CX-76

🧰 Changes
This fixes rendering html in callouts. The regex to trim the blockquote leaders >  was also trimming the ending bracket of the html tags.
🧬 QA & Testing

Broken on production.
Working in this PR app.

This PR was released!
🚀 Changes included in v6.26.2-next.1

This PR was released!
🚀 Changes included in v6.26.2


Error: Unparseable b-file line for ID 'A000521': -1 1

When asking the backend to call sequence A000521, the b-file has a term for index -1, which seems to cause the backend to choke up.  To replicate, ask for http://<IP_ADDRESS>:5000/api/get_oeis_values/A000521/50 and you will get the error that is the title of this issue.

Need to bump this in priority, as it hit again in testing https://github.com/numberscope/frontscope/pull/230


Add ed25519 to x25519 to nsec.experimental

Still working out how to take Key instances.

Forgot to mention this is from #32, thanks @p3root

Thanks a lot for your pull request! (We're moving slowly, but we're moving 😀)
I've made a few changes in<PHONE_NUMBER>6ead37f53f0523ff654cd804083894 to avoid exporting/importing. Let me know if that works for you.

:+1:


Copy files from a Python project skeleton (to enable CI etc.)

Maybe copy over the relevant files from perfcapture which, in turn, is based on https://github.com/jaraco/skeleton

Hmm, on second thoughts, maybe zarr-benchmark shouldn't be a Python package. Instead, users would pip install perfcapture (once perfcapture is on PyPI!) and run perfcapture against the "benchmark recipes" in zarr-benchmark.


Fixes 96: Add bulk create

Works in practice, but can't get tests to work yet because of some weird db transaction errors. Gonna make a draft PR in case I need help fixing :)
I'll update this description with more stuff once I fix that.

https://issues.redhat.com/browse/HMSCONTENT-96

The changes I made to the tests to delete the data from the 3 tables in my
rh repo load pr will probably solve the transaction errors.  The order of
deletion was wrong
On Tue, Jul 12, 2022, 4:40 PM rverdile @.***> wrote:

Works in practice, but can't get tests to work yet because of some weird
db transaction errors. Gonna make a draft PR in case I need help fixing :)
I'll update this description with more stuff once I fix that.
You can view, comment on, or merge this pull request online at:
https://github.com/content-services/content-sources-backend/pull/50
Commit Summary

6ec5a05
https://github.com/content-services/content-sources-backend/pull/50/commits/6ec5a0582788eb95408c660fe5ad236f93531474
Fixes 96: Add bulk create

File Changes
(7 files
https://github.com/content-services/content-sources-backend/pull/50/files
)

M pkg/dao/error.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-aab5a6ff6e60a8adb3c68abe7a6e5f77894b49722ac6e6e00ed31a54baa75fd6
(6)
M pkg/dao/interfaces.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-2890cf291694326df603760e3664720654eedef0b24b2a2db407c6d1c8c4da9f
(1)
M pkg/dao/repository.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-4613b72907d5407f2d396f8946b7744d5e95d1d8c57545a7fbcf4fecace55a82
(107)
M pkg/dao/repository_test.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-d117c6646c5fd3154993cd1578e3335cd07dc6260dfd2fb36841c3ca400da1ce
(39)
M pkg/dao/suite_test.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-3765cee86bf193a9d472329749d34f6c068829023e610e7da26837e441a703a1
(4)
M pkg/handler/repositories.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-5ea0664036ce68d4fb37e1a290f05df4868fb8b9cdff39f03d0e4fad2e9e0375
(45)
M pkg/handler/repository_test.go
https://github.com/content-services/content-sources-backend/pull/50/files#diff-a8dd18992b56849843b60650d1e482fa51dd8f739a6fab75fd3591b6e18fd603
(10)

Patch Links:

https://github.com/content-services/content-sources-backend/pull/50.patch
https://github.com/content-services/content-sources-backend/pull/50.diff
—
Reply to this email directly, view it on GitHub
https://github.com/content-services/content-sources-backend/pull/50, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADAORNRILUCRWTUIN6UV4DVTXJ3DANCNFSM53MJNGQQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I fixed that here too. I think it has something to do with there being a transaction both in the test and in the dao layer.

ahh, maybe try nested transactions? https://gorm.io/docs/transactions.html#Nested-Transactions

One thing to note, is the card describes a response that looks like this:
{ "RepoName": {"error": "Error Found"}, "2nd repo name": {"error":nil}}
but the current pr doesn't follow that.  You might wanna check with @Andrewgdewar as he and i discussed this previously.
We could also return the repo that was created as part of it within that structure:
{ "RepoName": {"error": "Error encountered", "repository": nil},
"2nd repo name": {"error":nil, "repository": {"uuid":"abcd"...}}}

Also, should it be an array?
[
  {  "repoName1":
   {
       "error": "error1",
        "repo": nil
    }
  },
  {  "repoName2":
   {
       "error": nil,
        "repo": {repo...}
    }
  },
]

And to clarify, this would also return the successful repos on error? Not just the ones that errored?

repo names are supposed to be unique, so i think just  just one big hash where the name is the key is fine, you may want to preemptively make sure that no duplicates are passed in though and reject the request outright.  IDK @Andrewgdewar your thoughts?

Built and pushed image for 5f7208ad3d802c4c0fd34681b31421766e388de4

ignore the push this doesn't work yet

https://issues.redhat.com/browse/14702687

Built and pushed image for 7da566d8d8890af896b360f3324501eda3e47610

should be all updated now

Built and pushed image for 0c4064ad456845d0a94b94c5ee732a7357ca3fc4

Built and pushed image for 910fca4a69f1b209e4991d9ec263cab7d437d295

Built and pushed image for 0b2b0940b480543cda033bb27cd468d521fd0913


adding did:web

Overview
This implements the creation of did:web's into the ssi-service
Description
Input:
PUT
http://localhost:8080/v1/dids/web
{
"keyType":"Ed25519",
"didWebId":"did:web:tbd.website"
}
Output:
{
    "did": {
        "@context": "https://www.w3.org/ns/did/v1",
        "id": "did:web:tbd.website",
        "verificationMethod": [
            {
                "id": "did:web:tbd.website#owner",
                "type": "Ed25519VerificationKey2018",
                "controller": "did:web:tbd.website",
                "publicKeyBase58": "4HyjANoMdhpp952YPb4wALydQRQ7BmsXHmBdwq4YSyiR"
            }
        ],
        "authentication": [
            [
                "did:web:tbd.website#owner"
            ]
        ],
        "assertionMethod": [
            [
                "did:web:tbd.website#owner"
            ]
        ]
    },
    "privateKeyBase58": "3mG6UhpXKZxeg7BwQZNpgEYiJUMkeDYATrHoLAbQDsiqeQEYwXxer7Stw6gVGdHwjPMxAmxUosrhnxPAWLBjcoqB",
    "keyType": "Ed25519"
}

Codecov Report

Merging #191 (1de03ca) into main (c25553b) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   24.98%   24.98%
=======================================
  Files          21       21
  Lines        1781     1781
=======================================
  Hits          445      445
  Misses       1264     1264
  Partials       72       72

Impacted Files
Coverage Δ

config/config.go
11.57% <0.00%> (ø)

pkg/server/router/did.go
7.92% <0.00%> (ø)

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

Yup I'll make new integ test and also plug up the resolution part too


Increase test coverage to 0.98

Before V0.8.0 we want to make sure out test coverage is at least 0.98
Required steps:

merge TPU testing #1246 #2094
prepare the infrastructure to run TPPU tests

not sure to get this done for v0.8, rather v0.9


Cannot brew update or upgrade: Error: homebrew-cask is a shallow clone.

Bug report

[* ] ran brew update and can still reproduce the problem?
[* ] ran brew doctor, fixed all issues and can still reproduce the problem?
[* ] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
I tried to run brew update and brew upgrade as usual to update the packages on my machine. Instead, I got the error below informing me that homebrow-core is a shallow clone (that's a good thing right?) and that I should unshallow it. Seemed a bit odd to me, as I thought the point of a shallow clone was to save a bunch of disk space, but I ran the command anyway. After running the suggested command to unshallow, the error remains on subsequent tries. So perhaps the issue is unrelated to the "shallowness" of the repo.
What happened (include command output)

Command output

$ brew update
Error: homebrew-core is a shallow clone. To brew update first run:
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow
$ git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow
remote: Enumerating objects: 848801, done.
remote: Counting objects: 100% (848798/848798), done.
remote: Compressing objects: 100% (272589/272589), done.
remote: Total 843685 (delta 574218), reused 837687 (delta 568229), pack-reused 0
Receiving objects: 100% (843685/843685), 331.47 MiB | 10.81 MiB/s, done.
Resolving deltas: 100% (574218/574218), completed with 4347 local objects.
From https://github.com/Homebrew/homebrew-core
55b17bad99..536b616fc3 master     -> origin/master
$ brew upgrade
Error: homebrew-cask is a shallow clone. To brew update first run:
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch --unshallow

What you expected to happen
Brew update and upgrade to update and upgrade, respectively.
Step-by-step reproduction instructions (by running brew commands)
brew update

Output of brew config and brew doctor commands
Brew Config:

HOMEBREW_VERSION: 2.6.0-68-g5ad9496
ORIGIN: https://github.com/Homebrew/brew
HEAD: 5ad949672f1fd9ce900e1196a0ad2c020f869480
Last commit: 26 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 55b17bad998d4b72411754fe69d68b7f3b4d1292
Core tap last commit: 25 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: nvim
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 12.0 build 1200
Git: 2.24.3 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.0.1-x86_64
CLT: <IP_ADDRESS>.1.1604076827
Xcode: 12.2

Brew Doctor:

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed kegs have no formulae!
This means they were either deleted or installed with `brew diy`.
You should find replacements for the following formulae:
  python@2

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/python2.7/greenlet/greenlet.h
  /usr/local/include/python3.7m/greenlet/greenlet.h
  /usr/local/include/python3.8/greenlet/greenlet.h

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  python@2

Warning: Homebrew's sbin was not found in your PATH but you have installed
formulae that put executables in /usr/local/sbin.
Consider setting the PATH for example like so:
  echo 'set -g fish_user_paths "/usr/local/sbin" $fish_user_paths' >> ~/.config/fish/config.fish

Error: homebrew-cask is a shallow clone. To brew update first run:
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch --unshallow

Please do this.

Please do this.

I did? It's pretty clear in my bug report. But I'll post it here again:
$ brew update

Error: homebrew-core is a shallow clone. To brew update first run:

git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow

$ git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow

remote: Enumerating objects: 848801, done.

remote: Counting objects: 100% (848798/848798), done.

remote: Compressing objects: 100% (272589/272589), done.

remote: Total 843685 (delta 574218), reused 837687 (delta 568229), pack-reused 0

Receiving objects: 100% (843685/843685), 331.47 MiB | 10.81 MiB/s, done.

Resolving deltas: 100% (574218/574218), completed with 4347 local objects.

From https://github.com/Homebrew/homebrew-core

55b17bad99..536b616fc3 master     -> origin/master

$ brew upgrade

Error: homebrew-cask is a shallow clone. To brew update first run:

git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch --unshallow

No, what you ran was git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow. Not the same command.

 I didn't notice that the repo was different the second time around.
Closing now as it seems to be working. Any thoughts on why I had to unshallow these repos? Seems a bit annoying since they are huge.

GitHub has requested this.

Ouch. Alright, thanks!

I've opened https://github.com/Homebrew/brew/pull/9447 to improve the message here.

Error: homebrew-core is a shallow clone. To brew update first run:
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow
This restriction has been made on GitHub's request because updating shallow
clones is an extremely expensive operation due to the tree layout and traffic of
Homebrew/homebrew-core. We don't do this for you automatically to avoid
repeatedly performing an expensive unshallow operation in CI systems (which
should instead be fixed to not use shallow clones). Sorry for the inconvenience!
having same issue, I tried running seperatly
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core"
fetch --unshallow
not working, I am unable to figure out the mistake I might be doing.

@niraj28 Run the below and then try again
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch --unshallow

git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" fetch --unshallow
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask" fetch --unshallow
now working fine.


Add AMQP listener mode utility

Pass --amqp option with exchange/queue parameters to listen continuously on exchange
Optional tool.  Take it or leave it.
@RackHD/corecommitters @zyoung51 @uppalk1 @tannoa2 @geoff-reid @keedya

*** BUILD #472 ***
Test Name: test_node_workflows_del_active
Error Details: (500)
Reason: Internal Server Error
HTTP response headers: HTTPHeaderDict({'Content-Length': '55', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"37-XhzFbw00G2hLTZBPq5najA"', 'Date': 'Tue, 03 May 2016 19:52:46 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"Failed to cancel 5729018c0ee9c2ee9914a02a"}

-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', BadStatusLine("''",))': /api/1.1/nodes
urllib3.connectionpool: INFO: Starting new HTTP connection (11): localhost
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/v1_1/nodes_tests.py", line 384, in test_node_workflows_del_active
    raise e
'(500)\nReason: Internal Server Error\nHTTP response headers: HTTPHeaderDict({\'Content-Length\': \'55\', \'X-Powered-By\': \'Express\', \'Connection\': \'keep-alive\', \'ETag\': \'W/"37-XhzFbw00G2hLTZBPq5najA"\', \'Date\': \'Tue, 03 May 2016 19:52:46 GMT\', \'Access-Control-Allow-Origin\': \'*\', \'Content-Type\': \'application/json; charset=utf-8\'})\nHTTP response body: {"message":"Failed to cancel 5729018c0ee9c2ee9914a02a"}\n\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by \'ProtocolError(\'Connection aborted.\', BadStatusLine("\'\'",))\': /api/1.1/nodes\nurllib3.connectionpool: INFO: Starting new HTTP connection (11): localhost\n--------------------- >> end captured logging << ---------------------'

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/session_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/RackHD/build/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: teardown
Error Details: 'X-Auth-Token'
-------------------- >> begin captured logging << --------------------
modules.redfish_auth: INFO: auth already disabled.
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/account_service_tests.py", line 38, in teardown
    Auth.disable()
  File "/home/jenkins/workspace/RackHD/build/test/modules/redfish_auth.py", line 67, in disable
    del config.api_client.default_headers['X-Auth-Token']
"'X-Auth-Token'\n-------------------- >> begin captured logging << --------------------\nmodules.redfish_auth: INFO: auth already disabled.\n--------------------- >> end captured logging << ---------------------"

Test Name: pollers_data_get
Error Details: Condition was True.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/v2_0/pollers_tests.py", line 158, in pollers_data_get
    assert_false(poller.get('lastFinished', False))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
AssertionError: Condition was True.

test this please

*** BUILD #474 ***
Test Name: test_node_workflows_del_active
Error Details: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Content-Length': '78', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"4e-Q3AUUEwY3oGiRq2sWimtjA"', 'Date': 'Tue, 03 May 2016 20:47:07 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"TaskCancellationError: Failed to cancel 57290e49fbed7c74a30f55bb"}

Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/v2_0/nodes_tests.py", line 348, in test_node_workflows_del_active
    raise e
ApiException: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Content-Length': '78', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"4e-Q3AUUEwY3oGiRq2sWimtjA"', 'Date': 'Tue, 03 May 2016 20:47:07 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"TaskCancellationError: Failed to cancel 57290e49fbed7c74a30f55bb"}

Should optional utilities/tools be in the on-tools repo?  +1 from me either way.

@zyoung51 probably, but since it reuses classes defined in test I just made it an option.

@jlongever yeah we have a similar utility at https://github.com/RackHD/on-tools/blob/master/dev_tools/sniff.js, though there seems to be a bit more functionality here. Might be worth a README mention if you're going to add this?
👍

+1 This tool will be useful

👍 looks great, thinking maybe we should kill the tooling in on-tools/dev_tools/sniff.js - especially where this could be leveraged to get better insight into the system for testing, which I suspect is some of the desire/drive here (at least that's my guess based on it being in tests - was that part of the intent @jlongever ?)

@heckj tbh I didn't put too much thought into it,  this was something I used while testing out new poller alerts and figured it would be useful under the integration test framework.  Same with the  --httpd option as well,  was used for validating Redfish EventService webhook functionality.


How Machine Learning is Revolutionizing the Agricultural Industry

this closes #4374
Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[ ] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[ ] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[ ] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #issue-number

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Okay, i will make the changes

@srishilesh, I did the revision, kindly review

@Ann-tech348
Thanks for making the changes.
Let's wait for this article to get plagiarism checked.
Thanks.

@section-engineering-education/content-moderator-team
Can we have this PR plagiarism checked?

Is this in reference to the author?

"Can we have this PR plagiarism checked?"
Is this in reference to the author please?

"Can we have this PR plagiarism checked?" Is this in reference to the author please?

No. It isn't.
The content moderators will be running a plagiarism check to see if the score is less than 10%.

@section-engineering-education/content-moderator-team
Can we have this PR plagiarism checked?

@hectorkambow
Can we have this PR plagiarism checked?
I have pinged the CMs as well, couldn't find any response.

@lalith1403 @Bayler @collins-a
Need your help here.
If you find time, can you guys have a quick look at this article? Do you think any other topics must be added? Or how this article could be improved?
I'm a little doubtful content-wise, since these information aren't backed by enough data, supporting it. Most of the points addresses the question of "What?", but not "How?" or "Why?".
Your thoughts would definitely help me in deciding whether to ask the author to rework on this.
cc. @hectorkambow

@lalith1403 @Bayler @collins-a
Need your help here.
If you find time, can you guys have a quick look at this article? Do you think any other topics must be added? Or how this article could be improved?
I'm a little doubtful content-wise, since these information aren't backed by enough data, supporting it. Most of the points addresses the question of "What?", but not "How?" or "Why?".
Your thoughts would definitely help me in deciding whether to ask the author to rework on this.
cc. @hectorkambow

Hey @srishilesh, I do agree with you, it's a little light on the how. Let me go ahead and highlight a couple of areas.

Plagiarism check done.

@collins-a Thanks for your suggestion. It was really helpful.
Let's give author sometime to make these changes.

cc. @Ann-tech348 We'll be closing this PR. Feel free to open a new PR, and mention me when the changes are done.
As mentioned in the suggestions, it would be great if you focus on the "how" part more. Explain some algo's in detail.
Feel free to ping me in case of any questions. Thanks.

@Ann-tech348
Do we have any updates on this?
Just wanted to check if you need any help.

I am till working on it and will respond within the week. thanks

@srishilesh , i am unable to update the document since cant locate the folder on the visualstudio code, kindly help

@srishilesh , i am unable to update the document since cant locate the folder on the visualstudio code, kindly help

@Ann-tech348
I'm sorry, which document?
Probably, let's connect via slack.

I meant @srishilesh you open this PR so that I can finish this revisions

@collins-a Thanks for your suggestion. It was really helpful.
Let's give author sometime to make these changes.

cc. @Ann-tech348 We'll be closing this PR. Feel free to open a new PR, and mention me when the changes are done.
As mentioned in the suggestions, it would be great if you focus on the "how" part more. Explain some algo's in detail.
Feel free to ping me in case of any questions. Thanks.

@Ann-tech348
As I had mentioned previously, you would have to open a new PR. Until then you can make those revisions in your forked repository.
If we reopen this PR for you to make changes, it would be unfair to other contributors.
Ensure that your PR must be ready to be published.


Duplicate dependencies: resolves #8

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Include legacy scripts in review app legacy mode

This PR includes the GOV.UK Template and frontend toolkit scripts on the page in the legacy mode.
Specifically, it

Includes GOVUK.modules.start() which initiates any scripts with start(). However, the modules (apart from auto-track-event.js for which this is needed) use init() so they have to be instantiated separately.
Doesn't include Selection buttons which are deprecated.
Doesn't include any of the tracking scripts from Frontend Toolkit as it seems unlikely these will conflict with GOV.UK Frontend which doesn't include any tracking scripts.
Includes auto-track-event.js as this seems "special", being incldued in the /modules folder instead of /analytics.

I've tested the modules to work on the pages but haven't included the markup in this PR. We could consider adding them to some pages if we thought this was useful.
This can also now be used to reproduce https://github.com/alphagov/govuk-frontend/issues/1270 by going to /full-page-examples/announcements and clicking on mobile Menu button.
Includes latest package-lock (see https://github.com/alphagov/govuk-frontend/pull/1377)
Fixes https://github.com/alphagov/govuk-frontend/issues/1360

Merged in Hanna's absence.


Intercept navigationDelegate, onLoaded...

Hi,
I would like to replace the current WebView with this to support for both mobile and web.
However, I find no way to handle the events such as navigationDelegate, onLoaded...
May I know how to do that?
Basically, I need to make sure this is work seamlessly as WebView before going further for web improvement.
Thanks!

Hi, a working navigationDelegate is a little bit tricky to implement, I'll try to look into it ASAP.
The onLoaded callback is available as two separate onPageStarted and onPageFinished callbacks, like in the mobile version.

Done #26
navigationDelegate only works for SourceType.urlBypass for now. This may change soon.
You can use onPageStarted and onPageFinished to get the next url, just like on mobile.
You can get the package from github until I publish a new version on pub.dev.
Closing this.


feat: new command to edit secrets mapping file and populate environment specific data

/test all

Not this PR contains a breaking changes
jx-gitops extsecrets renamed to jx-gitops secretsmapping
and in a secrets-mapping.yaml
spec.defaultBackendType is now spec.defaults.backendType

/lgtm


Docs: update screenshot path for npm

Fix:

update screenshot path from media/screenshot.gif to https://raw.githubusercontent.com/SamVerschueren/listr/master/media/screenshot.gif

The gif is not visible on the npm website. I added the absolut path to the img tag, so the gif is also displayed on the npm website, not only on github.

This should already have been fixed by npm: https://github.com/npm/marky-markdown/issues/320 Not sure why it's not working, but package authors shouldn't be forced to work around their continued brokenness.

If I get this right, you need to specify the right path for repositoryin the package.json. npm docs
I guess this could be the problem in this repo.
Right now its:
"repository": "SamVerschueren/listr",

Should be:
"repository" : {
  "type" : "git",
  "url" : "https://github.com/SamVerschueren/listr.git"
}

Then it's still not working correctly because the docs indicate that the shorthand version I use here (and in every other repository) is valid as well. They know that my project is located on GitHub, hence the project link on the npm package page.

Okay, that is true.
I run the tests from npm/marky-markdown with "repository": "name/repo", "repository": "github:name/repo", "repository": "https://github.com/name/repo" and
"repository": {
  "type": "git",
  "url": "https://github.com/name/repo"
}

the relative to absolut path conversion is only working for the last type.
But since this is a problem with npm/marky-markdown this PR is not relevant.

Care to create a new issue over there and link it here? I will definitely upvote it.

I will as soon as I get to a computer.


React-select Auto Suggest component grows out of screen

React-select Auto suggest component grows out of screen

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
The auto suggest input field should work like a regular textfield.
Current Behavior
The textfiled grows out of screen.
Steps to Reproduce
Here is the codesandbox:
Link:

https://codesandbox.io/s/ly87zo23kl

Tech
Version

Material-UI
v3.3.1

React
16.6.0

Browser
Google chrome

@tanmoy12 I'm sorry, I don't understand, what's the issue? It seems to be fine on the codesandbox.

Please keep typing into the textbox

@tanmoy12 The fix should be as simple as adding overflow: hidden in https://github.com/mui-org/material-ui/blob/926e76dc206a9607f30ade0de22f39b1fd375937/docs/src/pages/demos/autocomplete/IntegrationReactSelect.js#L66-L71. Do you want to give it a try :)?


add push functionality on incoming requests

@brokenprogrammer
This should be merged after #18
This PR simplifies the code by replacing expressjs with uWebsockets.js as well as adds functionality to push incoming requests to the browser client

@brokenprogrammer
Your comment does not appear here for some weird reason, but to answer your question that you told me offline:
uwebosckets handles HTTP requests as well: example

merging with previous comment


issue when teleporting to new world and hitting right away

it makes ToutEnGucci Disconnect
here is how it happens: https://youtu.be/7-GmInsbgd4

Just to be clear, ToutEnGucci is not attacking you here, is that correct?

Just to be clear, ToutEnGucci is not attacking you here, is that correct?

that is correct


dms: avatar in header doesn't render correctly

We seem to squish the avatar in the channel header.

looks like 24x24?


Fix the content-type for AASA

The content-type for the AASA file is incorrect which prevents deeplinking from working properly.
We are using the aws cli to deploy the build files into the s3 bucket, but if a content-type is not specified during this operation, it attempts to guess the correct mime type and it happens to be wrong for this file.
The fix here is to copy the file over itself during the deploy with the correct content-type header.
Details
Explained above
Fixed Issues

https://github.com/Expensify/Expensify/issues/266451
Tests
Since I have access to the bucket directly, I used the AWS CLI locally and ran the commands to check what it's set to now, updated it, then checked again.
❯ aws s3api head-object --bucket expensify-cash --key .well-known/apple-app-site-association
{
    "AcceptRanges": "bytes",
    "LastModified": "2023-03-06T15:21:48+00:00",
    "ContentLength": 1882,
    "ETag": "\"cf128e3c63ff747d0dc2448796e58744\"",
    "VersionId": "AEjHTa_2cV1EWNQ9W4ktuvci4sQwKZxl",
    "ContentType": "binary/octet-stream",
    "ServerSideEncryption": "AES256",
    "Metadata": {}
}

~ 6s
❯ aws s3 cp --content-type 'application/json' --metadata-directive REPLACE s3://expensify-cash/.well-known/apple-app-site-association s3://expensify-cash/.well-known/apple-app-site-association
copy: s3://expensify-cash/.well-known/apple-app-site-association to s3://expensify-cash/.well-known/apple-app-site-association

~ 12s
❯ aws s3api head-object --bucket expensify-cash --key .well-known/apple-app-site-association
{
    "AcceptRanges": "bytes",
    "LastModified": "2023-03-07T14:26:44+00:00",
    "ContentLength": 1882,
    "ETag": "\"cf128e3c63ff747d0dc2448796e58744\"",
    "VersionId": "nDTrPy3pUU_nUDl.QXor29JLhrxZkJrl",
    "ContentType": "application/json",
    "ServerSideEncryption": "AES256",
    "Metadata": {}
}

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@bondydaa Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/marcochavezf in version: 1.2.80-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/roryabraham in version: 1.2.80-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Stop at a specific row

Hello,
I know, it's not an issue but I don't know where to ask for features :-)
Is there a possibility to add an option and stop at a specific row with reading?
Thanks and kind regards,
Matthias

Hello,
how to read only a certain number of rows ?


Unable to install

I've added the line: pod 'MMLanScan' but when i try to install i've this error:
[!] Unable to find a specification for MMLanScan
How can i fix ?
Thanks

Solved, i don't why but with pod update the first time doesn't work, with the second works.


Grant permissions to people with spaces in their name? (NukkitX)

I can't grant my friend permissions because it thinks that it's a separate arguement in the command, doesn't work with quote symbols, or declaring a symbol with /lp user user\ name

Because you cannot have a space in a mc name
https://namemc.com/name/squirtle fanboy
Your "friend" is either full of crap, pulling your leg or your running a cracked server.

Bedrock clients allow spaces in usernames

The error message you're getting actually has nothing to do with the username.
parent friend isn't a command. Perhaps you meant parent add friend?

But the command /lp user "squirtle fanboy" permission set nukkit.* true doesn't work either.

Set allow-invalid-usernames to true in your config and restart the server. Luck's commit above will make thay default for new installations.


i have a function that lets me toggle opacity . I put it in bindings.lua but nothing happens when i press Ctrl+Alt+O . is there anything wrong with that code?

{
key = "O",
mods = mod.SUPER_REV,
-- toggling opacity
action = wezterm.action_callback(function(window, _)
local overrides = window:get_config_overrides() or {}
if overrides.window_background_opacity == 1.0 then
overrides.window_background_opacity = 0.9
else
overrides.window_background_opacity = 1.0
end
window:set_config_overrides(overrides)
end),
},

nvm , i found out a way to toggle it in nvim