Add sjb/ prefix for sjb files and scripts

Since we move to multibranch directory we have add the sjb/ prefix for the files and scripts that we are using from that directory.
@stevekuznetsov I guess more fixes will be needed ,but now aware of any yet. Thoughts ?
@bbguimaraes @jupierce fyi

@jhadvig i think i handled this in a commit

closing this one since @stevekuznetsov fixed the issue in https://github.com/openshift/aos-cd-jobs/commit/e380644c18207c8c92ffb3a89bc4d44c59e92a7c


BSO leaderboards missing thousands separators

🐛 Bug Report
Type +lb skills, see thousands separators.
Type =lb skills, see no thousands separators.
Reading leaderboards without thousand separators is very annoying especially since the numbers aren't aligned.

This has been fixed recently, I don't know exactly which commit fixed it 🤷

Apparently this is only fixed for XP and GP. KC leaderboards are still missing them.


Possibility to change the download URL when it expires

Hello, i would like to use this library into my project, but i have one problem.
I have download URL with expiration time, and when user pause download, expiration time is over, and user want to resume download, fetcher give me STATUS_ERROR, that is fine.
My ask is: is there any possibility to change download URL to continue download file with different download link?
Because for now i can't continue download, i need to remove request and starts again, losing proviously dowloaded part of the file.

@MaciekZ-NHM This is a very interesting scenario. It is possible to implement this in Fetch. I would have to find/test for the best way to implement this feature and to also test for the effects this can have on the library. Let me circle back back in a day.

Thank you for the quick answer, I'll wait ;)

@MaciekZ-NHM Still looking into this. I will keep this thread updated

@MaciekZ-NHM Version 1.1.1 has been pushed and contains a new method fetch.updateUrlForRequest(id,url). This will allow you to update the url of a download request that has been enqueued. If a url expires and the download cannot continue, The request status will be set to Fetch.STATUS_ERROR and fetch listeners will be alerted. After updating a request's url, it status will automatically be set to Fetch.STATUS_QUEUED and fetch will try to continue the download.


[TASK] Fix cypress pipeline provision VM network connection failure after migrate the host machine.

What's the test to develop? Please describe
After we migrated the original cypress test ansible host machine hp-205 to the new SLC lab environment.
And rebuild the staging Jenkins with the cypress test pipeline job.
When trigger the harvester-cypress-test job to start provisioning pxe_server, rancher and Harvester vm instance on the host machine.
On the test execution console: http://<IP_ADDRESS>/job/harvester-cypress-test/21/console
We found it would failed at the stage, it would failed when trying to upgrade all packages on the pxe_server vm.
TASK [configure_pxe_server : Upgrage all packages] *****************************
    fatal: [pxe_server]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: "}

For further investigation I try to access the pxe_server and test the outbound connectivity.
vagrant@cypress-rancher:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4094ms

vagrant@cypress-rancher:~$ sudo apt update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 1976 (python3)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to lock directory /var/lib/apt/lists/

It would likely the provisioned vm instance can't access to the internet which cause the failure
Prerequisite and dependency of test

Staging Jenkins is ready
The harvester-cypress-test pipeline job is well configured on the Staging Jenkins

Describe the items of the test development
Fix the network connectivity issue when the cypress pipeline provision all required vm instance

[ ] pxe_server
[ ] rancher
[ ] Harvester cluster

Ensure all the cypress test vm instance can correctly retrieve external IP address

[ ] pxe_server
[ ] rancher
[ ] Harvester cluster

Test cypress pipeline

[ ] Ensure the cypress pipeline job can execute well to execute the cypress testing script

After create a new cypress host on another bare-metal machine.
And set the vlan and bridge network interface, then set the bridge interface to get DHCP IP address.
The original network issue of lost network connection on the pxe_server VM have been resolved.

After investigation and several trials, we solve this issue on OpenSUSE Leap 15.6 host machine by

Remove the vagrant 2.2.18 from the zypper install (bind along with the vagrant-libvirt 0.10.2)
Manually add the vagrant 2.4.3$ wget https://releases.hashicorp.com/vagrant/2.4.3/vagrant-2.4.3-1.x86_64.rpm
$ sudo zypper install ./vagrant-2.4.3-1.x86_64.rpm

Then we need to upgrade the ruby version from built-in v2.5.9 to v3.2
We can use rvm to install and configure ruby 3.2 https://rvm.io/
Now we can install the vagrant-libvirtvagrant plugin install vagrant-libvirt

It would need to install libvirt

sudo zypper install libvirt-devel

We can install vagrant-libvirt 0.12.2 with vagrant 2.4.3 well

After the update, then we can correctly bring up the Rancher server vm

I will continue to investigate the configuration failure while install k3s version

TASK [configure_rancher_server : Install k3s] **********************************
fatal: [rancher]: FAILED! => {"changed": true, "cmd": "/tmp/rancher-server-k6kebbhv/install.sh", "delta": "0:00:00.400855", "end": "2024-12-06 17:19:16.110366", "msg": "non-zero return code", "rc": 1, "start": "2024-12-06 17:19:15.709511", "stderr": "[ERROR]  Download failed", "stderr_lines": ["[ERROR]  Download failed"], "stdout": "[INFO]  Using None as release\n[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/None/sha256sum-amd64.txt", "stdout_lines": ["[INFO]  Using None as release", "[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/None/sha256sum-amd64.txt"]}

After specify the correct eth1 bridge device of the cypress_vm host machine.
Then restart the Cypress pipeline, now it could be able to provision all the cypress test environment machines correctly including:

The pxe_server vm

The rancher server vm

Three nodes Harvester cluster vms
TASK [install_harvester_cypress : Wait for Harvester node to get ready] ********
FAILED - RETRYING: [cypress_vm]: Wait for Harvester node to get ready (30 retries left).
FAILED - RETRYING: [cypress_vm]: Wait for Harvester node to get ready (29 retries left).
FAILED - RETRYING: [cypress_vm]: Wait for Harvester node to get ready (28 retries left).
FAILED - RETRYING: [cypress_vm]: Wait for Harvester node to get ready (27 retries left).
ok: [cypress_vm]

TASK [cypress_tests : Confirm Rancher IP] **************************************
ok: [cypress_vm] =>
  rancher_ip_address: <IP_ADDRESS>

TASK [cypress_tests : Confirm Harvester VIP] ***********************************
ok: [cypress_vm] =>
  harvester_vip: <IP_ADDRESS>

TASK [cypress_tests : Register temporary directory path variable] **************
ok: [cypress_vm -> cypress_test(<IP_ADDRESS>)]

Then the pipeline execution failed at stage cypress_tests : Build docker image from tests/cypress
TASK [cypress_tests : Build docker image from tests/cypress] *******************
fatal: [cypress_vm -> cypress_test(<IP_ADDRESS>)]: FAILED! => changed=false
  msg: 'Error connecting: Error while fetching server API version: Not supported URL scheme http+docker'

Possible two changes that fixed the failure.

Downgrade the pip request library to 0.31.1 according to the stack overflow document
Specify the DOCKER_HOST: "unix:///var/run/docker.sock" in the ansible script of roles/cypress_tests/tasks/main.yml

Now the pipeline can proceed to use community.docker to create image -> create container and start the cypress test suite execution

Now the cypress pipeline could be able to complete the cypress script execution, cleanup the provisioned vagrant VMs and delete the workspace folder
It's the first time for the cypress pipeline to PASS the execution after migrated to the new Lab environment.
http://<IP_ADDRESS>/job/harvester-cypress-test/48/console

Next we need to check and fix the following test report activities:

Generate test report
Create a copy on the local workspace folder
Configure the pipeline to well connected to the new minio endpoint
Upload the test report to minio bucket
Set up the cypress web view on the minio endpoint
Set up web service for displaying cypress test report dashboard.


ft2fea-feature file dumper

I'm proposing to add a feature file generator to fontTools that I just wrote for a font project of mine.
The tool is in an early state so this could be a living Pull-Request until it's sufficient for you.
This PR has two parts: the fea-rendering library ft2fea.py and a command line tool ft2feaCLI.py.
I decided to add the CLI so that I can use the fea-generator while I'm completing it. Otherwise I had to come up with another way to silence output that I don't need in my build process.
The tool outputs GDEF, GPOS and GSUB. However, I only implemented the GPOS Lookup Types 4, 5 and 6 (MarkToBase, MarkToLigature, MarkToMark) yet.
The command line tool features a  query api that makes it possible to export just selected parts of the fea and honors dependency relations (like a Lookupflag that requires a defined Mark Attachment Class from GDEF) .
Sample output of $ ft2feaCLI.py fontfile.otf > dumped.fea
The help output of the tool:
$ ./ft2feaCLI.py -h
usage: ft2feaCLI.py [-h] [-r, --request [REQUEST]]
                    [-w, --whitelist [WHITELIST]]
                    [-b, --blacklist [BLACKLIST]] [-m, --mute [MUTE]]
                    FONT-PATH

Generate an OpenType Feature file (fea) from an otf/ttf font.

positional arguments:
  FONT-PATH             A ttf or otf OpenType font file.

optional arguments:
  -h, --help            show this help message and exit
  -r, --request [REQUEST]
                        Select the fea contents to export. Default: "**"
  -w, --whitelist [WHITELIST]
                        Whitelist fea contents.
  -b, --blacklist [BLACKLIST]
                        Blacklist fea contents.
  -m, --mute [MUTE]     Mute the printed output of fea contents.

The --request, --whitelist, --blacklist and --mute options; all take
as argument the same type of selector definition, which specifies the
the members of each set. See "The Selector Specification" below.

-r, --request
      Define the items that should be exported. If no request is
      defined (default) all items are requested (like: -r "**").
      If an empty request is defined (like: -r "") no item is requested.
      Items that are not directly requested are marked as "Maybe"
      which means that they are exported if they are a dependency
      of other items.
      E.g.: Lookups are dependencies of features. In order to export
      a feature, the lookups of the feature will be exported as well.
      If all of its lookups are are filtered (by --whitelist
      or --blacklist) the feature will not be exported even if it
      was requested.
      Similarly, LookupFlags of lookups can make a lookup dependent
      on the GDEF items "markAttachClasses" (Flag: MarkAttachmentType)
      and/or "markGlyphSets" (Flag: UseMarkFilteringSet) and some
      Lookup Types can themselves be dependent on other Lookups in
      the same table (GDEF or GPOS).
      NOTE: These Lookup Types are not yet implemented.

-w, --whitelist
      If a whitelist is present only items that are selected
      by the whitelist are allowed for output. This also means that
      this can block other not directly blocked items from output,
      if their dependencies are blocked.
      (default is like: -w "**")

-b, --blacklist
      If a blacklist is present only items that are *NOT* selected
      by the blacklist are allowed for output. his also means that
      this can block other not directly blocked items from output,
      if their dependencies are blocked.

-m, --mute
      While --whitelist and --blacklist try to keep the fea output
      valid when blocking other items (by taking care of dependencies)
      mute is not that careful. Mute allows to select items to not
      being printed, while dependent items will still be outputted.
      This is useful e.g. in a build process if all lookups of a
      feature should be used, but the features itself and thus the
      application of it are predefined somewhere else.
      E.g.: -r "GPOS feature mkmk" -m "GPOS feature mkmk" will output
      only the lookups used by the mkmk feature and if needed some
      class definitions of the GDEF table for Lookup-Flags. But
      the feature definition "feature mkmk { ... } mkmk;" will be
      omitted.
      Another scenario may be the inspection of the dependencies of an item
      while shutting of other noise.

The Selector Specification
==========================

A "selector" is made up of one or more single selectors, separated by
semicolons: "single-selector;single-selector;single-selector;

A "single-selector" is made up of one or more "selector-parts", separated
by whitespace: "part1 part2 part3". These parts represent a parent-child
like hierarchy: part3 is contained in part2 and part2 is contained in
part1.

A "selector-part" is made up of one ore more "selector-tags", separated
by the pipe "|" symbol:  "tag1|tag2|tag3". Each part of a tag represents
an alternative (logical OR) on the hierarchy level of the "selector-part"

Selector-Tags
-------------

"*" and "**" are wildcard tags.

"*" selects all items on the current hierarchy level. Thus it's not
    needed to have further tags separated with "|" in the same selector-part
"**" selects all items on the current hierarchy level and on all hierarchy
     levels below. Thus after a "**" it's not needed to add any further
     parts to select deeper levels. A single-selector ends after the
     first "**"

### Available tags and their hierarchy level (by indentation)

  languagesystem
  GDEF
      glyphClassDef
      attachList
      ligCaretList
      markAttachClasses
      markGlyphSets
  GSUB and GPOS
      script
          DFLT latn arab ... [script tags]
      language
          DEU dflt ARA URD ... [language tags]
      feature
          mkm mark calt dlig liga init medi ... [feature tags]
      lookup
          gpos1 gsub2 ... [see 'Lookup Type Selector Tags' below]// gpos1

 ### Lookup Type Selector Tags:
 from: https://www.microsoft.com/typography/otspec/gpos.htm

     gpos1: Single adjustment (GPOS Lookup-Type 1)
     gpos2: Pair adjustment
     gpos3: Cursive attachment
     gpos4: MarkToBase attachment
     gpos5: MarkToLigature attachment
     gpos6: MarkToMark attachment
     gpos7: Context positioning
     gpos8: Chained Context positioning
     gpos9: Extension positioning
     gsub1: Single
     gsub2: Multiple
     gsub3: Alternate
     gsub4: Ligature
     gsub5: Context
     gsub6: Chaining Context
     gsub7: Extension Substitution
     gsub8: Reverse chaining context single

EXAMPLES
========

$ fea2ft path/to/font.otf > features.fea
    Export all features of font.otf and save them to the file features.fea

$ fea2ft -r "GPOS" path/to/font.otf
    export just the GPOS table and GDEF dependencies if there.

$ ft2fea -r "GPOS feature mkmk|mark" path/to/font.otf
    export the mkmk and mark feature of the GPOS table (if available)

$ ft2fea -r "* script DFLT" path/to/font.otf
    export everything registered under the DFLT script

$ ft2fea -r "languagesystem" path/to/font.otf
    Print all languagesystem definitions for the font.
    NOTE: control over "languagesystem" is very limited at the moment.
    It is is not used as a dependency of script and language, thus all
    languagesystem definitions are either printed or not.

$ ft2fea -r "GSUB feature medi" -m "GDEF; GSUB feature *" path/to/font.otf
    export the lookups used by the medi feature of GSUB

$ ft2fea -r "GPOS lookup gpos4|gpos5|gpos6" path/to/font.otf
    export only the lookups of type MarkToBase (gpos4) or
    MarkToLigature (gpos5) or MarkToMark(gpos6)

$ ft2fea -r "* * gpos4|gpos5|gpos6" path/to/font.otf
    export only the lookups of type MarkToBase (gpos4) or
    MarkToLigature (gpos5) or MarkToMark(gpos6). Note, nothing but
    "GPOS ligature" as children named like "gpos4", thus the wildcards
    do just fine.

$ ft2fea -request "GPOS|GSUB feature *" \
            -whitelist "GPOS|GSUB; GPOS|GSUB **" \
            -mute "* feature *"  \
            path/to/font.otf
    Select features of GPOS or GSUB but filter dependencies that are not
    in GPOS or GSUB, i.e. lookups depending on class definitions in GDEF.
    Mute the feature blocks, so that only the lookups are exported.

Cool!
You have a typo ("mkm " instead of "mkmk " in the usage string). Other than that, splendid stuff!

Thanks Lasse!
We definitely have plans to do this.  My personal preference is to finish otlLib's build stuff, then add unbuild, and then add this feature to feaLib that would interface with unbuilt stuff rather than the internal tables directly.  But that definitely is not a requirement per se.

Hey, this is great! Thank you for sharing this here, Lasse :)
As @behdad anticipated in https://github.com/behdad/fonttools/issues/468#issuecomment-172837672, we are indeed planning to add support for writing OTL tables to feature files in various formats (fea, vtp, mti). Behdad proposed to define an API for "unbuilding" otData-defined objects to a set of Python primitive types (tuples, dict, set, etc.), i.e. the reverse of what otlLib.builder does. With that in place, then it would be easier to conceive writers outputting this data in various formats, including .FEA.
Anyway, yours seems to go in the same direction. I look forward to seeing more of it!

This is great, Lasse! My only concern is the lack of testing. Without unit tests, the codebase is hard to maintain.
OK to wait a week or so? Then I should have the unbuild() part done.

Thank you all for the feedback.

interface with unbuilt stuff rather than the internal tables directly

The unbuild plans sound good to me. I wouldn't mind to switch.

Without unit tests, the codebase is hard to maintain.

I agree. That can be done though.

OK to wait a week or so? Then I should have the unbuild() part done.

I'm not in a hurry. In fact I would suggest to keep the PR open for a while and let it evolve. Adding tests, using unbuild, that's fine for me. After all you are the maintainers of fontTools, so you should decide what goes into it.
I needed that thing right now, that's why it exists now, And I'll probably add some more lookups and some of the TODO's at the top of ft2feaCLI.py as I need it.
With some more distance and a bit of spare time I think I'd review the implementation of the filtering/query code in the CLI (ExportAggregator), because that's rather at the edge of "keep it simple", it has probably too much implicit knowledge about the behavior of the printing functions of ft2fea. Maybe the structure returned by unbuild can act as a intermediary format, that is then filtered, or a structure representing a fea-file could be created explicitly (containing otLib objects or unbuild data) , traversing and printing that would be trivial and simplify the printing functions, because the getStatus stuff could be removed.

This is mostly superseded by #776 and #779.
Thanks Lasse anyway!
Dunno, maybe your your console script could be adapted to work with Martin's implementation.
Maybe a main entry point for the ast module?
Let's think about it.

Can't ft2fea be used for dumping binary fonts feature to an FEA file, which fea2fea (the other PR) can't?

Ah true, I confused the two things.. 😐
Sorry!
So yeah, we still need to finish that unbuilding bit.

Still would be nice if we can generate AST from binary and use AST writer.  That way changing whitespace and other things will be uniformly applied to both kinds of output.

This code is "just" a snippet, and while it would be great to have it integrated more solidly into fonttools, it's seems that no movement is being made into that direction. I'd rather have this code actually be in Snippets/ than that it sits to rust here in this PR.

...although it currently doesn't run on Python 3, which is a bummer:
Traceback (most recent call last):
  File "ft2feaCLI.py", line 669, in <module>
    main()
  File "ft2feaCLI.py", line 638, in main
    aggregator.validate()
  File "ft2feaCLI.py", line 388, in validate
    self.validateCommonGTable(self.font[tableTag], required)
  File "ft2feaCLI.py", line 92, in wrapper
    registered = self.registry.get(key, None)
TypeError: unhashable type: 'table_G_P_O_S_'

Can someone take this on and do the proper implementation please?

@graphicore can you bring this up to date so it runs on Python 3 and drop it into Snippets? If not we'll have to close this.


Clicking on filtered run leads to displaying all runs again

Describe the Bug with repro steps
Customer can repro but we cannot.

Go to overview blade to filter runs with custom time range, and it brings up runs happened during this time range
Click on a run in the filtered result, the expectation is it will open the run. However, instead it opens a page which shows all runs again.

We do have HAR trace and the trace shows step 2 calls this URL.
https://management.azure.com/subscriptions/xxxxxxx/resourceGroups/xxxxxxx/providers/Microsoft.Logic/workflows/xxxxxxx/runs?api-version=2016-10-01&_=1698817148217
So it seems like the URL is not set up correctly, though having no idea what<PHONE_NUMBER>217 in the url is.
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response
AB#25784156

Best I can guess, This likely due to an issue with fetching the run data. The way this works is the clicking the run opens the all runs blade(which is how the run list on the side works that everyone seems to like) and the all runs blade fetches the data for the specific run and opens the run view. If the run data can’t be fetched for some reason it’ll never make it tot hat step.
not much I can do to diagnose this further without at the network trace and console logs. Can you send those to me directly @xuehongg ?

Found the issue and fixed that and a couple other issues here: https://msazure.visualstudio.com/One/_git/AzureUX-LogicAppsPortal/pullrequest/9170024?_a=files


Bedrock formatting error

when running streamlit app, got bedrock claude format error.
ValueError: Error raised by bedrock service: An error occurred (ValidationException) when calling the InvokeModel operation: Invalid prompt: prompt must start with " Human:" turn, prompt must end with " Assistant:" turn

python and langchain version, updated to the latest to resolve it.


Bugs in v 0.3.3

Hi
Ive seen two bugs in this version, first one is when u set the match length by number for example 30 it will set on short length and after u finish the match and hit rematch it will be 30. Then u change to 20 it will be 30 at first and after hitting rematch it will be 20.
Second bug is for the name of two new game modes, at first their name is ok, but after playing some matches or changing modifiers i dont know which , both their names change to free for all.
And Thanks for the mod. Its amazing

Thank you for the feedback! I have identified the source of the first bug (match length is set before StartMatch). I will include this fix in v0.3.4.
I was unable to replicate the name glitch or find any reason that would happen. If it happens again, make a note of what steps you followed to trigger it.
Glad you like the mod.

A fix for the match length issue is included in v0.3.4.

Thank u for the fixes and updates.
Is there a way to unlock all hats in game?
Also dynamic camera option isnt showing up in modifiers

Hi, I just added a bit of information about debug mode in the mod README.md. You can unlock the hats by pressing F1 to unlock debug mode, then H to unlock all hats, then Page Down to save.
Dynamic camera option is not yet a feature ported from wq13sk's mod.


Precision or accuracy?

Thank you for your awesome code. Prec1 and Prec5 are calculated using the function accuracy, which is said to "compute the precision@k for the specified values of k", but the way it's calculated suggests that it's an accuracy measure.
Is it precision or accuracy? I thought it's not exactly the same in ML terminology, especially if you consider a per-class precision.

Yes, it's accuracy, never changed the naming from an old version of the original pytorch training example that I started this from. I have this change on a list of small fixes to push through, once I'm done a few bigger tasks. Also have a distributed Precision, Recall, F-score (w/ macro/micro avgs) meter to add in that change set.

Hello @rwightman any update on when you would be adding Precision, Recall, and F1 score to metrics?

Hello @rwightman any update on when you would be adding Precision, Recall, and F1 score to metrics?


freetube: fix icon

Motivation for this change
Freetube's icon was previously placed in $out/share/application/hicolor/scalable, however an icon should be placed in $out/share/application/hicolor/scalable/apps in order to work. With this PR, it's in the correct location.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/779

@ofborg eval


More descriptive comment on build: false

This part of appveyor.yml is not easy to understand for someone not very familiar with Appveyor:
# disable automatic builds
build: false

It sounds like it turns off automatically building new commits to the project. Which it doesn't.
If the following comment is correct I would say it describes the setting in a clearer way:
# We build in the test stage, so disable Appveyor's build stage.
build: false

Can you submit a PR for this?

Sure!


typo: occurences -> occurrences

@shortpatti might be a good idea to trim the old branches in this repo https://github.com/MicrosoftDocs/windows-itpro-docs/branches/all 😉

Thanks for reminding me :)  I'm on it.


[projmgr,cbuildgen] support options (optimize, debug, warnings)

Contributed by STMicroelectronics
Signed-off-by: Tarek BOCHKATI<EMAIL_ADDRESS>

@brondani we still have to propagate this to CMakeLists.txt and manage it in .cmake files

@brondani I have added more commits to propagate the options to CMakeLists.txt
now I working on supporting these options on IAR.cmake

@brondani there was a bug on tools/projmgr/schemas/common.schema.json related to WarningsType
I will come back with another fix for codecov

@tarek-bochkati  can you please ensure that the open conversations above get closed commenting how these comments have been addressed or if case they have not been addressed, why this is.

@brondani could you please give some hints on how to fix the buildmgr-cov ?

@brondani could you please give some hints on how to fix the buildmgr-cov ?

@tarek-bochkati in the codecov report you can see the new lines that are not being covered by tests and probably causing the coverage to decrease. For example lines 895 - 904 in CbuildModel.cpp are shown as not being covered by tests.

@brondani is it possible to run codecov locally, so I can detect coverage regressions before pushing to github ?

@brondani is it possible to run codecov locally, so I can detect coverage regressions before pushing to github ?

Please take a look here:
https://github.com/Open-CMSIS-Pack/devtools/blob/main/.github/workflows/buildmgr.yml#L478-L493
@soumeh01 Could you please add to the devtools documentation how to generate the coverage report locally? Thanks!

as mentioned by @brondani , this change is too huge
decision is to split it into multiple PRs : we started with #478

summary:

#478 : merged
#479 : merged
#480 : merged
#484 : under review


Check if the downloaded file are already present in the TS map notebook

If this notebook https://github.com/cositools/cosipy/blob/main/docs/tutorials/ts_map/Parallel_TS_map_computation_DC2.ipynb
is executed multiple times it tries to download the files each time and show errors.
The zipped response file is deleted so the code downloads it again even if the unzipped file is present.

Thanks, @NicoloParmiggiani
I'm working on the SC tutorial and I added this:
from pathlib import Path
import shutil

data_dir = Path("") # Current directory by default. Modify if you want a different path

response_path = data_dir/"SMEXv12.Continuum.HEALPixO3_10bins_log_flat.binnedimaging.imagingresponse.nonsparse_nside8.area.good_chunks_unzip.h5"

# download response file ~839.62 MB
if not response_path.exists():

    response_path_zip = str(response_path) + '.zip'
    fetch_wasabi_file("COSI-SMEX/DC2/Responses/SMEXv12.Continuum.HEALPixO3_10bins_log_flat.binnedimaging.imagingresponse.nonsparse_nside8.area.good_chunks_unzip.h5.zip",response_path_zip)

    # unzip the response file
    shutil.unpack_archive(response_path_zip)

    # delete the zipped response to save space
    os.remove(response_path_zip)

@Yong2Sheng Can you do the same for the tutorial @NicoloParmiggiani mentioned, please?

Hi @israelmcmc and @NicoloParmiggiani, Thank you for bring it up! This is a good ideal, I will add this script to the downloading cell.

This is fixed in a commit in #150

#150 closed this.


Support FillProto for QuotaRequest.

Use two special attributes "quota.name" and "quota.amount" to pass info to protobuf QuotaRequest.

Jenkins job mixerclient/presubmit passed

Not yet.  I am about to it.   This is for istio/proxy to call it.

Jenkins job proxy/mixerclient-pr passed

Jenkins job proxy/mixerclient-pr passed


Using a soft font causes the Atlas engine to crash

Windows Terminal version
1.18.1421.0
Windows build number
10.0.19045.2913
Other Software
No response
Steps to reproduce

Make sure the Atlas engine is activated in the Advanced profile settings.
Open a bash shell.
Execute printf "\eP0;1;1;4;2;1{B~~~~~~~~/~~~~~~~~\e\\"

Expected Behavior
Most characters output at this point should be reverse question marks, except for ! which should map to a solid block.
Actual Behavior
The terminal crashes. This is caused by a null pointer reference when accessing the fontFaceEntry.fontFace field in BackendD3D::_initializeFontFaceEntry.
https://github.com/microsoft/terminal/blob/c589784b54d46187289651fa6c04c49fe05826aa/src/renderer/atlas/BackendD3D.cpp#L1158
Just based on a brief scan of the code, I got the impression that it's expected for the fontFace to be null when you have a soft font, so it may just be that this method hasn't allowed for that case. This appears to be a regression introduced in PR #15343.

Ah dang I didn't test it again after the PR. 😟 Sorry for breaking it, and thank you so much for noticing it!

FYI the link I distributed in some other comments (click) is a build that also contains the PR that fixes this. If you're eager to test it out, you could consider installing that build. 🙂

I've patched my local build with the changes in your PR and it's working great now. Thanks!


gradle 3.3 - Unable to add dependency

compile 'com.github.irshulx:laser-native-editor:2.0.3'
Error:(50, 13) Failed to resolve: com.github.irshulx:laser-native-editor:2.0.3

same problem here

Hello,
I'm facing same issue.
Can anyone guide in case if you have resolved the issue at your end.
--
Thanks,
Abhijit

same here

I have added it now locally. As implemented in the sample project

sorry for leaving it unattended for so long, fixed on the commit 964d37d.


feat: add optimizer with desired file size, add exceptions with context

I don't understand what is being done here. PRs should have a description, updated readme and updated tests that follow code style of the rest of the package.


enhancement : Jenkins Plugin Upgrade

Testing done

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes
- [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

I just did some changes to the pom removing all the unnecessary stuff and that builds without any problem locally
You have no tests so I removed almost all the test dependencies
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.jenkins-ci.plugins</groupId>
		<artifactId>plugin</artifactId>
		<version>4.80</version>
		<relativePath />
	</parent>
	<groupId>io.jenkins.plugins</groupId>
	<artifactId>leapwork</artifactId>
	<version>${revision}${changelist}</version>
	<packaging>hpi</packaging>
	<properties>
		<revision>4.0.10</revision>
		<changelist>-SNAPSHOT</changelist>
		<gitHubRepo>jenkinsci/leapwork-plugin</gitHubRepo>
		<!-- Baseline Jenkins version you use to build the plugin. Users must have
			this version or newer to run. -->
		<jenkins.version>2.440.1</jenkins.version>
		<gitHubRepo>jenkinsci/leapwork-plugin</gitHubRepo>
	</properties>
	<name>Leapwork</name>
	<url>https://github.com/${gitHubRepo}</url>

	<dependencyManagement>
		<dependencies>
			<dependency>
				<!-- Pick up common dependencies for the selected LTS line: https://github.com/jenkinsci/bom#usage -->
				<groupId>io.jenkins.tools.bom</groupId>
				<artifactId>bom-2.440.x</artifactId>
				<version>2815.vf5d6f093b_23e</version>
				<scope>import</scope>
				<type>pom</type>
			</dependency>
		</dependencies>
	</dependencyManagement>
	<dependencies>
		<dependency>
			<groupId>com.ning</groupId>
			<artifactId>async-http-client</artifactId>
			<version>1.9.40</version>
		</dependency>
		<dependency>
			<groupId>io.jenkins.plugins</groupId>
			<artifactId>gson-api</artifactId>
		</dependency>
		<dependency>
			<groupId>jakarta.xml.bind</groupId>
			<artifactId>jakarta.xml.bind-api</artifactId>
			<version>3.0.1</version>
		</dependency>
		<dependency>
			<groupId>com.sun.xml.bind</groupId>
			<artifactId>jaxb-impl</artifactId>
			<version>3.0.0</version>
			<scope>runtime</scope>
		</dependency>
		<dependency>
			<groupId>org.slf4j</groupId>
			<artifactId>slf4j-nop</artifactId>
			<version>1.7.32</version>
			<scope>test</scope>
		</dependency>
	</dependencies>

	<licenses>
		<license>
			<name>MIT License</name>
			<url>https://opensource.org/licenses/MIT</url>
		</license>
	</licenses>
	<!-- If you want this to appear on the plugin site page: -->
	<developers>
		<developer>

			<name>Leapwork DevOps</name>
<EMAIL_ADDRESS>		</developer>
	</developers>

	<scm>
		<connection>scm:git:https://github.com/${gitHubRepo}</connection>
		<developerConnection>scm:git:git@github.com:${gitHubRepo}.git</developerConnection>
		<url>https://github.com/${gitHubRepo}</url>
		<tag>leapwork-4.0.5</tag>
	</scm>

	<repositories>
		<repository>
			<id>mulesoft-releases</id>
			<name>MuleSoft Repository</name>
			<url>http://repository.mulesoft.org/releases/</url>
			<layout>default</layout>
		</repository>
		<repository>
			<id>repo.jenkins-ci.org</id>
			<url>https://repo.jenkins-ci.org/public/</url>
		</repository>
	</repositories>
	<pluginRepositories>
		<pluginRepository>
			<id>repo.jenkins-ci.org</id>
			<url>https://repo.jenkins-ci.org/public/</url>
		</pluginRepository>
	</pluginRepositories>
</project>

your build fails on ci.jenkins.io because it is built with java8. But you need this to run with java11.
You should first adjust the Jenkinsfile in a separate PR and merge it and then this PR should start working fine
buildPlugin(
  useContainerAgent: true,
  configurations: [
    [platform: 'linux', jdk: 11]
])

you will need to do the change to the Jenkinsfile in a separate PR and merge it first.
ci.jenkins.io is always taking the Jenkinsfile from the main branch to avoid that someone can just open a PR with a Jenkinsfile that tries to do harmful things. Once this is merged, revert to the pom.xml that I provided and this PR will build successfully.

Will raise separate PR for the same


Corrected bug that put the UTI instead of mimeType in retrieved assets

This pull request corrects a bug  found in RCTAssetsLibraryRequestHandler which used the asset UTI as the mimeType.
The code for finding the mimeType is based on the implementation used in RCTImageLoader and RCTImageUtils.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@yedidyak updated the pull request.

@yedidyak updated the pull request.

@yedidyak updated the pull request.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


NPM install fails on 1.3.0

I think there is something wrong with the newest version of the package in NPM:
npm install
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v5.4.1
npm ERR! npm  v3.8.0
npm ERR! path C:\Code\xxx\node_modules\cpx\bin\index.js
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Code\xxx\node_modules\cpx\bin\index.js'
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Code\xxx\node_modules\cpx\bin\index.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
When I change the version to 1.2.1 in package.json, everything seems to be ok.

ugha, sorry I'll fix ASAP

I published a fixed version.
Thank you.

Yup, seems to work now, thank you for very fast reaction!


Failure of scenario_test_runner

I installed scenario simulator v2 and autoware.universe on Ubuntu 22.04 with ROS2 humble.
All the installation and build procedures are successful.
When I started the scenario_test_runner. It seems failed: no Autoware and RVIZ2 appeared.
Only the logging info kept showing up and I cannot get the results as shown in the instruction video or docs.

@ZiweiSong96
It appears that the communication that should take place after launching Autoware is not taking place.
If possible, could you please provide error logs for other parts of the system?

It seems the simulator stucked at somewhere, I can only see the node or service "not ready". Besides, an information "Shutting down Autoware" appeared.

Actually these are all the error logs. They repeat one by one

It seems, you are trying to follow this instruction is it right?
https://tier4.github.io/AWSIM/GettingStarted/UsingOpenSCENARIO/

@mackierx111 Do you know something about this problem?

Hi, @ZiweiSong96 , may I ask do you have any solution for this issue? I have the same problem.

Hi, @Lkaho @ZiweiSong96, sorry to bother but i encounter same error, did you guys find a way to solve this problem?

Hi, @ZiweiSong96 , may I ask do you have any solution for this issue? I have the same problem.

Sure, I still work on Autoware related project.

Hi, @Lkaho @ZiweiSong96, sorry to bother but i encounter same error, did you guys find a way to solve this problem?

Actually I did not solve this question, so I turned to AWSIM and try to make some adjustment on the Unity 3D project to make some complex traffic scenarios.


Logitech Options app (macOS) stops working

When Karabiner Elements is running (0.90.92 macOS) the Logitech Options (aka Logi Options) stops working (due to a conflict?).
In particular, these functions fail:

on screen popup when pressing the Caps Lock key
battery indicator
bluetooth connection indicator
any setting (as far as I can see)
In other words, nothing works anymore in the Logitech Options app.

Furthermore, Karabiner Elements swaps Fn/Media-keys.

I am also having this issue.

might be because logitech options is confused about which keyboard it should be working on.
just for addition, logitech flow's automatic keyboard switching will fail if karabiner is on. It works when switching keyboard from win10 to macosx, but will fail to switch back to win10. Works again when I turn karabiner off.


First version of tauto

It seems to be complete now. Just some cleaning and use cases?

(there is one admitted lemma ``ìnversion_rel```, but it is not important)
Ideally, we need to be able to define a tactic tauto_tac out of quote, reify and tauto but I am not sure it can be done in MetaCoq.
@SimonBoulier do you think it can be done ?

Yes, it will be easy to prove inversion_Rel, exactly as we proved it in pcuic.

@tabareau Does your latest commit mean we should close this?


Links overwriting browser url

Consider following flow:
-Click on OAuth lock icon.
For above flow, the browser url is changed with #auth. Is there a way to avoid this? If not, is it possible to override this behavior?

use update-route='false'


Fix recursive retreiver notebooks

The recursive retriever docs were kind of broken, and missing outputs

@jerryjliu good catch


Block websites from blocking PiP

it's annoying and user-hostile.

Could you provide some example sites?

https://github.com/w3c/picture-in-picture/issues/178
https://w3c.github.io/picture-in-picture/#exit-pip

I mean what websites are blocking PiP functionality for you? I wanted to investigate the method they used to block it. There at least two methods. One method used by websites like Youtube TV is through sending a Feature-Policy header. If the website you have a problem with is using the same method. You could try using my extension to unblock it.
https://github.com/polywock/pipUnblocker

Sorry for dodging the question. AnimeLab blocks PiP.

I looked into AnimeLab's code. I found two workarounds. The first, use Firefox for AnimeLab. The API they use to block it is not available in Firefox.  The second, use the following bookmark before clicking on the PiP icon.
window.addEventListener("enterpictureinpicture", e => {
    e.stopImmediatePropagation()
}, {capture: true, passive: true})

window.addEventListener("leavepictureinpicture", e => {
    e.stopImmediatePropagation()
}, {capture: true, passive: true})

Your bookmarklet works! :D

https://github.com/polywock/pipUnblocker removes picture-in-picture feature policy from HTTP headers
All is left is removing the disablePictureInPicture HTMLVideoElement attribute.
From there, any website could be forced into Picture-in-Picture mode, even it explicitly told browser it wasn't compatible.

@beaufortfrancois, that's technically true, but AnimeLab walls of PiP functionality as a paid feature. To enforce it, they listen to the enterpictureinpicture event and forcefully exit using document.exitPictureInPicture(). I provided OP with a bookmarklet to block the event propagation. This issue can be closed.

@polywock do you think you could merge your bookmarklet and extension and make it automatic? :) sorry if that's not possible or too complicated. I don't really understand how it works.
i really don't know if websites should really have permission to exit PiP without a user gesture. I can't think of any use cases other than to be user-hostile. it's probably a w3c suggestion or wherever web standards are made though, hence why i made that other issue which got closed.
i was hoping that Google's PiP extension would add your unblocker. I installed it because I want to make any media go into PiP. If I cared about what websites intended, I wouldn't be using it at all.

@Poopooracoocoo, here's an extension version. You'll have to load it yourself. Publishing extensions is a pain. I stopped using a VPN, so I cannot test it on AnimeLab (not available in my country). Let me know if there any issues.
https://github.com/polywock/pipEventBlocker

Are there any plans to make this extension more intrusive? Like bypass disablePictureInPicture and other stuff?
I wrote myself this bookmarklet that also searches for all the videos inside all iframes.
https://gist.github.com/iamandrewluca/71b57cb2d905ab06429c481251db9833


403 causes panic

This was 100% a permission issue on my end but a 403 download code shouldn't cause a panic in the code.
PS C:\Users\Clayton Burlison\Desktop\cpe-chef-repo> C:\ProgramData\gorilla\bin\gorilla.exe -v
Retrieving manifest: unity_prd
Manifest Url: https://example.com/gorilla_repo/manifests/company_prd.yaml
panic: Unable to retrieve manifest:company_prdcompany_prd.yaml : Download status code: 403

goroutine 1 [running]:
log.Panic(0xc000067d40, 0x3, 0x3)
        /usr/local/go/src/log/log.go:326 +0xc7
github.com/1dustindavis/gorilla/pkg/gorillalog.Error(0xc000067d40, 0x3, 0x3)
        /ext-go/1/src/github.com/1dustindavis/gorilla/pkg/gorillalog/gorillalog.go:78 +0x5f
github.com/1dustindavis/gorilla/pkg/manifest.Get(0xc000067f68, 0x2, 0x2)
        /ext-go/1/src/github.com/1dustindavis/gorilla/pkg/manifest/manifest.go:68 +0x7b4
main.main()
        /ext-go/1/src/github.com/1dustindavis/gorilla/cmd/gorilla/main.go:25 +0xd0

Whatever does that double manifest name to come up should also be fixed. I saw that as well.
Thanks,
Erik Gomez

From: Clayton Burlison<EMAIL_ADDRESS>Sent: Tuesday, March 12, 2019 11:54:35 AM
To: 1dustindavis/gorilla
Cc: Subscribed
Subject: [1dustindavis/gorilla] 403 causes panic (#65)
This was 100% a permission issue on my end but a 403 download code shouldn't cause a panic in the code.
PS C:\Users\Clayton Burlison\Desktop\cpe-chef-repo> C:\ProgramData\gorilla\bin\gorilla.exe -v
Retrieving manifest: unity_prd
Manifest Url: https://example.com/gorilla_repo/manifests/company_prd.yaml
panic: Unable to retrieve manifest:company_prdcompany_prd.yaml : Download status code: 403
goroutine 1 [running]:
log.Panic(0xc000067d40, 0x3, 0x3)
/usr/local/go/src/log/log.go:326 +0xc7
github.com/1dustindavis/gorilla/pkg/gorillalog.Error(0xc000067d40, 0x3, 0x3)
/ext-go/1/src/github.com/1dustindavis/gorilla/pkg/gorillalog/gorillalog.go:78 +0x5f
github.com/1dustindavis/gorilla/pkg/manifest.Get(0xc000067f68, 0x2, 0x2)
/ext-go/1/src/github.com/1dustindavis/gorilla/pkg/manifest/manifest.go:68 +0x7b4
main.main()
/ext-go/1/src/github.com/1dustindavis/gorilla/cmd/gorilla/main.go:25 +0xd0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/1dustindavis/gorilla/issues/65, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFa_GNLQMEOK6mmqRvXlVyhzW-ESE2bhks5vV9vLgaJpZM4brZTS.

Thanks for the issue!
This should be pretty easy to fix as we are getting the right error, we just aren’t exiting gracefully.


Add lane below/above breaks layout

Describe the Bug
When i choose the option "add lane above" or "add lane below" in a diagram with multiplex lane, the layout get broken.
I tried an old version "3.1.0" and this don't happen.

Steps to Reproduce

Create a new diagram
Add three lanes
Create a flow
On the second lane, click "add lane below

Expected Behavior
The links should stay connected as below:

Environment

OS: Windows 10
Camunda Modeler Version: 3.7.0 Windows 64 bit

I can reproduce this issue:

Test diagram: space-test.bpmn.

Will be fixed with next release.

Can this one be closed?

👍


Author and onboard new Devfiles

Background
Currently all the devfiles hosted on the public registry registry.devfile.io/  are either maintained by the community or the runtime team themselves in the repo https://github.com/devfile/registry
It would be nice if we could onboard a few more stacks to the registry.
Work
We can take a look at the current popular frameworks in the market and identify which ones should be onboarded to the devfile registry.
To test out these devfiles, you can use the odo tool to author your devfile stacks. We can provide more than the rudimentary build and run options. Odo has the option to debug and test applications as well.
Tip: We can take a look at the Che Devfile 1.0 Registry  to onboard a few stacks

Checklist

[ ] Golang
[ ] Nodejs React
[ ] Nodejs Angular
[ ] Php Laravel


Only Add/Remove Roles if Missing/Existing in Role Synchronizer.

https://github.com/MitchTalmadge/StudyBot/commit/0b5a38fd82f9649f235f29c0dfa165531073501e


hello, i have a desktop and laptop, and i want to move my MysteriumVPN over to my laptop, but how do i log into my account on the windows appliction?, i only see 2 options which are "Go Back" And "Top Up Wallet"

when i try to click go back it says starting daemon but it keeps doing it i tried restarting the app,repairing the supervisor but with no success here is the logs
renderer.log
main.log
mysterium-node.log
myst_supervisor.log

also im on windows 11


integrate in smarthome

hi, can you make it so that you can query the temperatures? i would like to integrate that into iobroker. with mqtt or something like that. Thanks

A bit late to the party.. but I did exactly that the other day. I've got a working implementation here (it uploads to influxDB but you should be able to change it for MTTQ easily).


DazToUnreal Bridge 2<IP_ADDRESS> (Update DazBridge Library, UI/UX update, DTU update, bugfixes, Merge with latest David-Vodhanel changes)

Quality Assurance Review

Prior Behavior Preserved: All automated unit-tests and test-cases complete successfully.  Manual export of G8F/M, V8.1, with hair, clothing, Environments, Animations complete successfully. [PASSED]
New Features: New User Help Text appears correctly. Embedded Installers complete successfully.  [PASSED]
Output Validation: DTU, FBX, PNG file formats validated with automated tests. [PASSED]

Known Issue:

Building Blueprint based Unreal Project completes with "Success" message, however, executable does not run (tested with Unreal 4.27, 5.0, Windows 11).

The above issue is existing behavior which is confirmed with prior releases back to April 2021.  Since this is not a regression or new failure introduced by changes of this merger, I will proceed with merger and address this as an open issue needing bugfix in the immediate future.


Will installing this on Pi overwrite my current Pi-Hole installation?

Hello,
Will installing this on Pi overwrite my current Pi-Hole installation?
Enjoy your videos and saw this great tool. Don't want to break my current DNS wide Pi-Hole configurations.
If this will lose my current configuration any chance you can point to an article on how to back-up Pi-Hole configurations and put them in your installation?

@FifthCloud - Backups/restores in Pi-hole are pretty easy: you use the 'Teleporter' thing in Settings and save off a config zip, then import it on another Pi-hole instance.
But if you want this setup to not install Pi-hole so you can use your existing install, just set pihole_enable: false in your config.yml before running the playbook.

Will do! Thanks!


Findings not shown with Version 1.1.0

I've installed the Plugin Version 1.1.0

on IntelliJ IDEA Ultimate 2022.2.1 on MacOS Monterey 12.5.1 and tfsec v1.27.6
and get an empty findings list

Running the tfsec command in the cli finds plenty of issues though.

I just installed the plugin and encountered this as well. It looks like the results are actually there (I can click the ">" and expand them). It appears that there is some UI issue, as if I mouse over the line shown below the "High" category in the screenshot above, my mouse changes to a vertical drag cursor but I'm unable to actually adjust it.

We have the same exact issue with my colleagues. MacOS Monterey 12.5.1, IntelliJ IDEA 2022.1.3 (Ultimate Edition)
Build #IU-221.5921.22, built on June 21, 2022, Runtime version: 11.0.15+10-b2043.56 aarch64

Ran into the same problem. I found the section that shows High in the above image is scrollable. All the details are there; however, the UI is 1 row high instead of taking up the entire tool window space.

Any updates to this? This really anoying bug prevents us from using the plugin.


Webhook API Version Error

After upgrading to version v1beta2-1.3.0-3.1.1 with webhook enabled on Kubernetes 1.19, we get this error when operator starts:
main.go:209] MutatingWebhookConfiguration.admissionregistration.k8s.io "spark-operator-webhook-config" is invalid: [webhooks[0].sideEffects: Required value: must specify one of None, NoneOnDryRun, webhooks[0].admissionReviewVersions: Required value: must specify one of v1, v1beta1]

i have the same issue
also the default version ("when you dont specify any tag") v1beta2-1.3.1-3.1.1 seems to be missing
can anyone guide me to any temporary patch?
i need hooks so that i can mount production environment configmaps on my spark jobs

i have the same issue
also the default version ("when you dont specify any tag") v1beta2-1.3.1-3.1.1 seems to be missing
can anyone guide me to any temporary patch?
i need hooks so that i can mount production environment configmaps on my spark jobs

the isssu has been resolved and merged in to the repository
for those of you who have the same issue as me, just clone the repository and build your custom image untill the official release is made.

 For those of us who doesn't know how to build the custom imge, do you have any guidance on this?

@sadatnfs Since then, there have been a few images released to github registry, you can see them here: https://github.com/googlecloudplatform/spark-on-k8s-operator/pkgs/container/spark-operator.

i was able to resolve the issue by using below options while installing the helm chart:
--set image.tag=v1beta2-1.3.2-3.1.1 --set image.repository=ghcr.io/googlecloudplatform/spark-operator

i just helm installed v1beta2-1.3.3-3.1.1, but i don't see webhooks created, any idea why?

@yevsh webhooks are not enabled by default (seehttps://github.com/GoogleCloudPlatform/spark-on-k8s-operator/blob/e91821634deab861f56d5105b186b52749843272/charts/spark-operator-chart/values.yaml#L79), did you enable it at install time? Any logs from the operator?

i have the same issue.
install spark operator with webhook(kubectl apply -f spark-operator-with-webhook.yaml ) successfully with image version v1beta2-1.2.0-3.0.0, but upgrade to image version v1beta2-1.3.0-3.1.1, we get this error when operator starts:
I0209 06:13:22.008517      10 main.go:145] Starting the Spark Operator
I0209 06:13:22.009263      10 webhook.go:219] Starting the Spark admission webhook server
I0209 06:13:22.020432      10 webhook.go:415] Creating a MutatingWebhookConfiguration for the Spark pod admission webhook
F0209 06:13:22.024687      10 main.go:209] MutatingWebhookConfiguration.admissionregistration.k8s.io "spark-webhook-config" is invalid: [webhooks[0].sideEffects: Required value: must specify one of None, NoneOnDryRun, webhooks[0].admissionReviewVersions: Required value: must specify one of v1, v1beta1]

oh i see, we use the source code of spark-operator-chart-1.1.15, but  the issue has been resolved after that.
(issue: Resolves an error when deploying the webhook where the k8s api indicated that the webhook config was invalid because of missing SideEffects, and AdmissionReviewVersions (#1413))


upload raw collectl data to s3 after the run finishes

Hey Brad, I think this will save collectl data in S3 after a run finishes, but I haven't had a chance to try it. Can you take a look and let me know if it looks good?

Gonna table this for now given the open questions we talked about. We can always revisit at some point in the future.


useLazyFetch does not behave like useLazyAsyncData

Environment

Operating System: Darwin
Node Version:     v19.5.0
Nuxt Version:     3.2.3
Nitro Version:    2.2.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, runtimeConfig, content, image, googleFonts
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
The following code fetches search results. It's automatically refreshed when the searchquery ref is changed.
const navSearchAPICall = useLazyAsyncData(
    'searchWorking',
    () => $fetch('/api/search', {
        params: {
            query: searchquery.value
        }
    }),
    {
        server: false,
        watch: [searchquery]
    }
)

This works as expected. But the following code, wich should behave the same according to the documentation, does not work. The request is refreshed when the searchquery ref changes, but the query parameters stay the same.
const searchAPICall = useLazyFetch('/api/search', {
        key: 'searchNotWorking',
        params: {
            query: searchquery.value
        },
        server: false,
        watch: [searchquery]
    }
)

Describe the bug
As described in the reproduction, when using useLazyAsyncData, the request is refreshed with updated query parameters according to the searchquery ref.
But when using useLazyFetch, the request is refreshed but sent with unchanged query parameters.
Additional context
No response
Logs
No response

You should pass the ref directly, or it will be 'frozen' at the moment you call useLazyFetch, and unable to update:
const searchAPICall = useLazyFetch('/api/search', {
        key: 'searchNotWorking',
        params: {
            query: searchquery
        },
        server: false,
        watch: [searchquery]
    }
)

Thank you.


How to add UIView inside tooltip

Hi!
I want to know how could I add an UIView inside the EasyTipView, instead of only adding a single text. I have created an UIView and I want to add it in the tooltip.

version 2.0.4


style reset password page

How do I get to the reset password page?

The code for it is in app/views/devise/passwords/edit.html.erb


#2698. Configure custom comparator defining repeatable migrations order.

I would like to control the order of repeatable migrations.
In order to do that I suggest a new configuration parameter repeatableMigrationComparator, fully qualified class name of custom Comparator to determine the order of repeatable migrations.
By default repeatable migrations are ordered by description. Which means as before if not set.
This doesn't brake the main idea that versioned migrations are always applied before repeatable. The custom Comparator implementation controls only repeatable migration order.
I have found that it might close #2698 .

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

Thanks for the contribution. We are planning to do something like this, however the change would be quite a fundamental extension to the way Flyway works. We'd like to solve the problem in a more general way - for instance, to help with versioned migrations too (e.g. interleaving with repeatables).
There's a fair bit we need to consider, so we're holding off until V7 at the earliest. We'll keep this PR open as a reference.

Closing as we will be tackling the problem of custom migration ordering differently


118-improve-stringly-typed-firebase-collection-names

Created file Constants.swift for the FirestoreCollection enum. Fixed all Stringly typed Firestore Calls in ViewModels.
What it Does

Closes #118
Describe what your change does
Creates file Constants.swift housing enum FirestoreCollection. Replaces all tryingly-typed firestorm calls in DashboardViewModel and SettingsViewModel

How I Tested

Add a list of steps to show the functionality of your feature
For example:
Run the application
Tap the (+) button
Created Event to make a new Event
Clicked on Settings
Created a new Vehicle

Oh I messed this up.

Trying to reopen issue. GitHub shakes fist


panic: unaligned 64-bit atomic operation

Current Behavior
I encountered a runtime panic when running the hostd Docker container on my Raspberry Pi (aarch64).
Here's a little snippet of the log:
goroutine 51 [running]:
runtime/internal/atomic.panicUnaligned()
	runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Store64(0x2c9010c, 0x3e)
	runtime/internal/atomic/atomic_arm.s:291 +0x14
go.sia.tech/hostd/wallet.(*SingleAddressWallet).ProcessConsensusChange(0x2c900e0, {{0xc4, 0x5, 0x69, 0x84, 0xbf, 0x96, 0x84, 0x32, 0xaf, ...}, ...})
	go.sia.tech/hostd/wallet/wallet.go:698 +0xba4
go.sia.tech/siad/modules/consensus.(*ConsensusSet).managedInitializeSubscribe.func2(0x2d28180)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:212 +0x19c
gitlab.com/NebulousLabs/bolt.(*DB).View(0x29003c0, 0x284ad2c)
	gitlab.com/NebulousLabs/bolt@v1.4.4/db.go:730 +0xa4
go.sia.tech/siad/modules/consensus.(*ConsensusSet).managedInitializeSubscribe(0x28c8a80, {0x10e9308, 0x2c900e0}, {0xef, 0xea, 0xf7, 0xe9, 0x3b, 0x5f, 0xf4, ...}, ...)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:200 +0x33c
go.sia.tech/siad/modules/consensus.(*ConsensusSet).ConsensusSetSubscribe(0x28c8a80, {0x10e9308, 0x2c900e0}, {0xef, 0xea, 0xf7, 0xe9, 0x3b, 0x5f, 0xf4, ...}, ...)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:256 +0xec
go.sia.tech/hostd/chain.(*Manager).Subscribe(0x2dba000, {0x10e9308, 0x2c900e0}, {0xef, 0xea, 0xf7, 0xe9, 0x3b, 0x5f, 0xf4, ...}, ...)
	go.sia.tech/hostd/chain/manager.go:133 +0x5c
go.sia.tech/hostd/wallet.NewSingleAddressWallet.func1()
	go.sia.tech/hostd/wallet/wallet.go:767 +0x7c
created by go.sia.tech/hostd/wallet.NewSingleAddressWallet
	go.sia.tech/hostd/wallet/wallet.go:765 +0x720
2023/06/18 11:15:34 hostd v0.1.0-alpha.3-32-g0be24c2
2023/06/18 11:15:34 Network Zen Testnet
{"level":"info","ts":1687086934.2192411,"logger":"stdlog","caller":"hostd/main.go:50","msg":"Using HOSTD_ZEN_API_PASSWORD environment variable."}
{"level":"info","ts":1687086934.220021,"logger":"stdlog","caller":"hostd/main.go:69","msg":"Using HOSTD_ZEN_SEED environment variable."}
panic: unaligned 64-bit atomic operation

Expected Behavior
Work? 📈 😅
Steps to Reproduce
Just build from the scratch and try to start the container 🤷♂
git clone https://github.com/SiaFoundation/hostd.git && cd hostd

docker build -t zen_hostd -f docker/Dockerfile.testnet .

docker run -d --name hostd -e HOSTD_ZEN_API_PASSWORD='PASS' -e HOSTD_ZEN_SEED='SEED' -p localhost:9880:9880/tcp -p :9881:9881/tcp zen_hostd

Version
hostd v0.1.0-alpha.3-32-g0be24c2
What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?
Raspberry Pi OS | aarch64
Anything else?
No response

I can't recreate this on a fresh install of Raspberry Pi OS (64-bit). Are you sure you installed the 64-bit version? Looking at Raspberry Pi Imager, the default option is 32-bit.

Yeap, absolutely. In addition, the same Raspberry Pi is also carrying a renterd container, which works like clockwork.
I'm very impressed that you managed to do that. I spent a few days trying to exclude all the reasons why this might be happening. I can see the container starting up and hostd launching for about 5 seconds and if I take action quickly I'll be lucky enough to even be able to log in and enter the UI but then it crash.

For the sake of the experiment's purity, I even tried running hostd on mainnet, although I understood that the result would likely be the same, and indeed it was.
2023/06/18 12:56:53 hostd v0.1.0-alpha.3-32-g0be24c2
2023/06/18 12:56:53 Network Mainnet
{"level":"info","ts":1687093013.470032,"logger":"stdlog","caller":"hostd/main.go:50","msg":"Using HOSTD_API_PASSWORD environment variable."}
{"level":"info","ts":1687093013.4703264,"logger":"stdlog","caller":"hostd/main.go:69","msg":"Using HOSTD_SEED environment variable."}
panic: unaligned 64-bit atomic operation

goroutine 69 [running]:
runtime/internal/atomic.panicUnaligned()
	runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Store64(0x350e56c, 0x0)
	runtime/internal/atomic/atomic_arm.s:291 +0x14
go.sia.tech/hostd/wallet.(*SingleAddressWallet).ProcessConsensusChange(0x350e540, {{0x89, 0xea, 0xd7, 0xf6, 0x71, 0x80, 0xa2, 0x8f, 0x5b, ...}, ...})
	go.sia.tech/hostd/wallet/wallet.go:698 +0xba4
go.sia.tech/siad/modules/consensus.(*ConsensusSet).managedInitializeSubscribe.func2(0x30c6600)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:212 +0x19c
gitlab.com/NebulousLabs/bolt.(*DB).View(0x31143c0, 0x30f3d2c)
	gitlab.com/NebulousLabs/bolt@v1.4.4/db.go:730 +0xa4
go.sia.tech/siad/modules/consensus.(*ConsensusSet).managedInitializeSubscribe(0x30d0a80, {0x10edae8, 0x350e540}, {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:200 +0x33c
go.sia.tech/siad/modules/consensus.(*ConsensusSet).ConsensusSetSubscribe(0x30d0a80, {0x10edae8, 0x350e540}, {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...)
	go.sia.tech/siad@v1.5.10-0.20230228235644-3059c0b930ca/modules/consensus/subscribe.go:256 +0xec
go.sia.tech/hostd/chain.(*Manager).Subscribe(0x3194000, {0x10edae8, 0x350e540}, {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...)
	go.sia.tech/hostd/chain/manager.go:133 +0x5c
go.sia.tech/hostd/wallet.NewSingleAddressWallet.func1()
	go.sia.tech/hostd/wallet/wallet.go:767 +0x7c
created by go.sia.tech/hostd/wallet.NewSingleAddressWallet
	go.sia.tech/hostd/wallet/wallet.go:765 +0x720

What’s the output of sudo getconf LONG_BIT. Did you build the renterd container manually or pull the existing one?

Manually. When I first tried to pull the existing one, it also did not work. And by the way, if I'm not mistaken, the same thing happened with renterd. And only when I did it manually, renterd started to work. It has been working for about a month now, I update and use it almost every day and everything works fine.

Very odd. I can fix the alignment, but I can't recreate this issue on a fresh install of Raspberry Pi OS (64-bit). I can build the container, start it, fully sync, and access the UI. Does pulling the ghcr.io/siafoundation/hostd:master image result in the same panic or a different one?

Okay, here it is. Now I remember what was the error for renterd. That's exactly why I do this manually. Having seen that the renterd container has been working fine for a long period of time, I decided to do the same trick with hostd, but you already know the result. Can you please tell me, are you able to pull the ghcr.io/siafoundation/hostd:master image? My pupils will dilate even more if you confirm this 😵💫
And YES. Binary works just fine 👌

Can you please tell me, did you build it from scratch or you able to pull the ghcr.io/siafoundation/hostd:master

I can build it from scratch or pull the image. How did you install Docker? It seems like your Docker is trying to pull the 32-bit image, which we don't support.

#89 will fix the crash. However, I'd still recommend that you figure out why your Docker install is trying to grab the 32-bit image at some point.

That's exactly what I'm doing right now 🫡 Your question about Docker put me in the mindset that I had installed the wrong version of Docker and I managed to find this command `docker version --format '{{.Server.Arch}}'

If I'm right, for a 64-bit Docker, the architecture returned will be amd64 or aarch64. But for a 32-bit installation, it will  be: 386 or arm. Presently, I will engage in the task of uninstalling and reinstalling Docker. I will be boundlessly joyful if this succeeds, yet concurrently saddened by my own lack of attentiveness 😔

No comments 😑 Only, thank you.


babel-cli installed globally required by npm compile scripts?

Should the babel-cli package be installed globally to support the following npm scripts, before running the build scripts for the first time?
"compile:dev": "babel src -d dist --watch & babel themes/current/src -d themes/current/dist --watch",
"compile": "babel src -d dist --quiet",

No, babel-cli is local package.
You don't need any global package.


Include config files from conf.d

I need it to extend nginx configuration after setting environment variables

Can you do the PR versus branch 1.11.10-alpine instead of master? Master is really old, but we're not sure whether it's in use anywhere so didn't dare to overwrite it.

If you issue the PR from a branch inside this repo you can verify the build at https://hub.docker.com/r/travix/nginx/builds/ works. I wouldn't want it to be merged and then discover it's broken, because all of our k8s hosted applications use it.

Thank you, @JorritSalverda.
I created branch 1.11.14-alpine with my changes from 1.11.10-alpine. I am not sure about merging it to 1.11.10-alpine.
Let's override master and see if something breaks! =))


Soundex and diff - or usage for diacritical signs

How is it possible to include a "soundex" search and "diff" usage for tokens in lunr?
Perhaps anyone who implemented it till yet?
I wan't to find names like "Music" for "Mušič", wich is nearby it.
Or are there other possibilities to find even diacritical signs with latin1?
Code for soundex here: http://rosettacode.org/wiki/Soundex

It should be straightforward to add soundex processing to lunr, you will need to package an implementation of the soundex algorithm as a pipeline function.
A pipeline function is a simple transformation on a given token, so for a soundex it would simply return the soundex of a token.
// define a soundex pipeline function
lunr.soundex = function (token) {
  return soundex(token)
}

// register it with lunr.Pipeline, this allows you to still serialise the index
lunr.Pipeline.registerFunction(lunr.soundex, 'soundex')

With the function defined you can add it to an indexes pipeline, you probably want to remove the built in stemmer, as I doubt stemming and soundex work well together, though YMMV.
idx.pipeline.after(lunr.stemmer, lunr.soundex)
idx.pipeline.remove(lunr.stemmer)

The soundex function will then be used when indexing documents, and when searching for documents.
Let me know how you get along with this, and whether you need any help. I'm not super familiar with the implementation of the soundex algorithm, but I think it would be a cool add-on for lunr.
Closing as this isn't something that will live in lunr core, but feel free to re-open if you have any questions etc.

Ok, the soundex function can be found here http://rosettacode.org/wiki/Soundex#JavaScript
The diff calculates a similarity for 0 match and till 4 no match.
`var diff = function(a,b) {
var alength = a.length;
var res = 0
for (var i=0; i<a.length; i++) {
    if (a.charAt(i) == b.charAt(i)) {
        res++;
    }
}

return res

}
console.log(diff(soundex('Alex'), soundex('Alexander')))
`
So like @atamon hacked here https://github.com/olivernn/lunr.js/issues/70#issuecomment-187962132 for FuzzySearch, there is an "score" for similarity.
He used only one field "title" in his index. But how to search for multiple fields with soundex? Or a Fuzzy Search like @atamon used.
Can it a be a feature to directly say, a specific field in the index has a "soundex" or one a "fuzzy" or other?

Currently it is not possible, or easy, to change the way that matching of words in the index is implemented, I'm working on a new version of lunr that may make it easier to extend this, but it doesn't exist yet.
Untill it does, I think you can probably get quite far by just storing the soundex of words in the index, and using the existing term matching. The difference would be that instead of matching on stemmed words, it would be matching on the result of applying the soundex algorithm on the words.


ci: update notify-release action permissions

Fixes https://github.com/nearform/hub-draft-issues/issues/226.

Codecov Report

Merging #101 (7151445) into master (241af66) will not change coverage.
The diff coverage is n/a.

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##            master      #101   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           39        39
=========================================
  Hits            39        39

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


Documentation updates for creating a custom appLayout

I tried creating a custom MyLayout.js as per the tutorial/documentation but there's really not enough information there to make a working Layout that one can actually customize (though it is a tremendous start).
Here's what I ran into (please feel free to incorporate these into the docs if there isn't a better way) :

You can't instantiate a second injectTapEventPlugin(); I don't know where the "other one" is

I commented out the references to it but do not know what the consequences of this are

The references to './Menu' and './Notification' prevent it from compiling (that's not where those are)

trying to import them from 'admin-on-rest' does not work
Neither does importing them from the src directory using '/admin-on-rest/src/mui/layout/Notification'
I eventually found using lib as in '/admin-on-rest/lib/mui/layout/Notification' works

It'd be nice if there was a quick blurb somewhere on either taking pieces of the library local; or importing your customizations into the main framework

Copying the Notification and Menu sources locally takes more massaging

I was never able to make import Notification from './Notification'; work
For Notification the offending lines are:

import { hideNotification as hideNotificationAction } from '../../actions/notificationActions' ;
import translate from '../../i18n/translate';
Nothing I did seemed to satisfy both the compiler and the runtime to get a working Layout

With Menu, it only has the line import translate from '../../i18n/translate';

I used import translate from 'admin-on-rest/lib/i18n/translate';

The import List, ListItem from 'material-ui/List'; != import List, ListItem from 'admin-on-rest/lib/mui'

It was not clear to me for a long time that these aren't the same thing or even compatible with each other
Given that Material-UI seems to be the larger framework it'd be great if AOR could either:

Rename the AOR.List / ListItem components  to RestList / RestListItem
Alias them when showing examples: import List as RestList, ListItem as RestListItem ...
Consistently reference them through a dot qualifier like AOR.List somehow
Or less desirable, clearly document on the <List /> page this is a condition to be aware of

Thanks!  :)
After clearing up those issues I had a custom layout where I could make changes to the './Menu.js' in the projects ./src folder and see them reflected when the app rendered.

The sample code I was commenting on came from the AdminResource docs on creating a custom appLayout; not the CustomApp docs.  Thanks for the quick commit though.


update(policies): setup for policy hub

Description

setup for policy hub

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@ajithsimons

Please be aware of the license header years! If you create a new file, just put the current year in it. For other (modified) files you can either have 1 year (creation year) (e.g. 2024) or a 2 year range (creation year and last modification year) with commas separated (e.g. 2019,2024)

Asked team to update Thanks.


p2p: provide a separate metric for failed requests

When handling the requests, distinguish completed requests from failed
Motivation
Failed requests (e.g. due to i/o deadline exceeded errors) are currently counted as "completed", which is not entirely correct
Changes
Added spacemesh_server_requests{protocol="...",state="failed"} metric.
Test Plan
Query metrics on a node

bors merge


chore(test): update test files

:tada: This PR is included in version 2.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


specify encryption for --sse option

When running stax, it outputs an error stating that an invalid choice was made when running S3 commands with the AWS CLI. On further inspection, the commands look something like the following:
if ! aws s3 cp --sse "$template_path" "s3://$template_s3" > /dev/null; then
    #...
fi

It seems as though --sse is taking the filepath as an argument, which of course is not valid.
I decided to solve this by letting the user decide what encryption scheme to use. The docs do say that --sse with no arguments defaults to AES256, but I figured it would be nice to make this configurable.

I should add I tested running stax on Ubuntu 15.10 and AWS CLI 1.9.15 and 1.10.0 and stax fails to run when you don't specify the encryption scheme (as is currently the case).

This is great, thanks for the code update! I have not been working within AWS recently, so I have let this project go a bit, so I really appreciate the effort. Also, love your Snorlax avatar!

Happy to be of help :) Snorlax is greatest, isn't it?
I actually have another PR lined up but I wanted to build it off this one (it makes another change to the stax config file). Will send it along shortly.


Documentation reference error:  map.txt and "40.1" both link to "05.3" instead of "05.4"

Steps to reproduce
Read either 40.1 or map.txt and it states that mapping is introduced in "05.3".  It is introduced in "05.4".
Expected behaviour
The links are changed to 05.4.
Version of Vim
8.1
Environment
Ubuntu 20.4
Logs and stack traces
No response

diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 479f447..fb07a52 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -6,7 +6,7 @@

 Key mapping, abbreviations and user-defined commands.

-This subject is introduced in sections |05.3|, |24.7| and |40.1| of the user
+This subject is introduced in sections |05.4|, |24.7| and |40.1| of the user
 manual.

 1. Key mapping			|key-mapping|
diff --git a/runtime/doc/usr_40.txt b/runtime/doc/usr_40.txt
index 21c09b4..658fb69 100644
--- a/runtime/doc/usr_40.txt
+++ b/runtime/doc/usr_40.txt
@@ -20,7 +20,7 @@ Table of contents: |usr_toc.txt|
 ==============================================================================
 *40.1*	Key mapping

-A simple mapping was explained in section |05.3|.  The principle is that one
+A simple mapping was explained in section |05.4|.  The principle is that one
 sequence of key strokes is translated into another sequence of key strokes.

    The simplest form is that one key is mapped to a sequence of keys.  Since

I'll include the correction, thanks for reporting.


[Alert] Add new component

I am happy to contribute this component.  I am making this issue to determine interest and discuss the scope of the component.
This issue is to track the development in an Alert component.  This component provides contextual feedback messages for typical user actions.

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

This is distinct from a snackbar as mentioned in https://github.com/mui-org/material-ui/issues/15513.

Summary 💡
This component provides contextual feedback messages when you need a persistent static container which is closable by user actions or when you need to show alert messages to users.
Examples 🌈
Many libraries have implementations of this:

AntD's Alert Component
Bootstrap's Alert
reactstrap's Alert Component
Evergreen's Alert Component
PrimeReact's Alert Component
Elemental UI's Alert Component
react-bootstrap's Alert Component
Weaveworks UI Components' Alert Component
Zendesk Gardens' Alert Component
Bootstrap View's Alert Component

Motivation 🔦
As with the examples above, I have used such a component before in 3 of the above mentioned solutions and find it missing in material-ui.

@dimitropoulos This would be great! I have kept a small list of implementation I have seen over the last few months: https://trello.com/c/hMM2R1uh/1893-alert-component.

Great!  Then I'll start scoping out the API and features we would want to target.  Thankfully there's a good deal to draw on!  Once we agree on the general approach for things I will get started on the code.

(@oliviertassinari would you mind assigning this issue to me?)

@dimitropoulos Great, I have searched a bit some for more benchmark sources:

for the accessibility part, I would recommend having a look at https://www.w3.org/TR/wai-aria-practices/#alert and https://ui.reach.tech/alert if not enough.
for the API part, I would recommend having a look at https://chakra-ui.com/alert, https://sancho-ui.com/components/alert/, https://auth0-cosmos.now.sh/docs/#/component/alert, https://react-bootstrap.github.io/components/alerts
for the feature part, I would recommend having a look at  https://ant.design/components/alert/, https://orbit.kiwi/components/alert-message/, https://evergreen.segment.com/components/alert
for the UI part, I would recommend having a look at https://developers.google.com/web/tools/workbox/guides/using-bundlers, https://vuetifyjs.com/en/components/alerts#alerts, https://dribbble.com/shots/6472915-Flash-Message-Daily-UI-Challenge-011/attachments, https://dribbble.com/shots/7874860-Alerts-UI-design

Hi, I just wanted to ask if @dimitropoulos are you still working on it, or I could give it a go?

Note that the banner component in the Material Design specification is very close to this use case, I think that it's more important to have a solid Alert, but it could be interested to have some sort of an extended support for this component.

I have some work I did on it, but never pushed it up.  @r3dm1ke would you like to work on it together?  I'll push what I had now.  It took me quite a long time to figure out just how to get the basic moving pieces into the codebase to have a place to start.

@dimitropoulos That would be awesome, I am just not sure how to work together on the same pull request at the same time. Perhaps we need to split it into two based on what you have already completed (like api/tests/docs etc.)? @oliviertassinari do you have any insights?

see: https://github.com/mui-org/material-ui/pull/18702
I basically did a lot of the gruntwork associated with just getting the minimal set of things included.  I'd be more than happy for you to pick it up and do whatever you wish from here if you'd be alright with me chipping in a few commits as you go.  It was much more work than I was anticipating to get the above commit just because of a lack of familiarity with the codebase.  That said, I'd really like to get to a point where I can contribute valuable features (such as this) to this project, so if you could lead the way, it would give me a better idea of how development on this project works in practice.
Either way: I'm totally cool with whatever.  :)

Also, you're in Toronto and I'm in Michigan, so perhaps our timezones line up well enough to do some pair programming on it some night if you want :)

see: #18702
I basically did a lot of the gruntwork associated with just getting the minimal set of things included. I'd be more than happy for you to pick it up and do whatever you wish from here if you'd be alright with me chipping in a few commits as you go. It was much more work than I was anticipating to get the above commit just because of a lack of familiarity with the codebase. That said, I'd really like to get to a point where I can contribute valuable features (such as this) to this project, so if you could lead the way, it would give me a better idea of how development on this project works in practice.
Either way: I'm totally cool with whatever. :)

I am actually not that experienced myself 😅. I have looked through your changes, could you give we write access to your fork of the repo so we can continue from there?

oh my apologies! I assumed that you could already write to it!  I'll do that real quick :)

I've just sent both of you invites.  I thought the way it worked was that if you have write access on the main repo that you would have access on the fork, but I think that was skewed by my usage of github within a private organization where this holds true.

I've just sent both of you invites. I thought the way it worked was that if you have write access on the main repo that you would have access on the fork, but I think that was skewed by my usage of github within a private organization where this holds true.

Thank you! I did not have write access to the main repo though. Could you send me your email address so we do not clutter this issue?

@dimitropoulos Thanks for the invitation, I think that the simplest would be to iterate on a single place: dimitropoulos:alert-component. It's already great to see the infrastructure work required to implement such Alert components done :). I can imagine that it was challenging, well done!
I will have a look at the benchmarked components and make a proposal (from a "product" perspective), it's great to have multiple 👀 challenging it. Once we agree on the deliverable, you should be able to move forward and see the next steps more clearly :).

It's already great to see the infrastructure work required to implement such Alert components done

I've wondered occasionally if we should automate it, but then convince myself that there can only be so many more new components. \Now I'm not so sure! :)

I would propose the following API, something close to the DOM nodes like we have with the list, it makes composition and style override easier:

<Alert>
  <AlertIcon />
  <AlertTitle>
    Sorry, results couldn't be loaded
  </AlertTitle>
  <AlertClose />
  <AlertDescription>
    There was an error while processing your request. Refresh your page for loading results.
  </AlertDescription>
  <AlertActions>
    <Button>
      Refresh
    </Button>
    <Button component="a"<EMAIL_ADDRESS>      Contact support
    </Button>
  </AlertActions>
</Alert>

https://orbit.kiwi/components/alert-message/

We might be able to use CSS grid for positioning the elements, the challenge is to make sure it's supported with the older version of the spec IE 11 implements.
It's probably a good opportunity to introduce the success, info, and danger colors in the theme's palette.
I would propose we implement the 4 different states with a color prop.
We might be able to have a banner variant: https://material.io/components/banners/#.
I'm wondering if we shouldn't support these variants https://dribbble.com/shots/7874860-Alerts-UI-design/attachments/486141?mode=media, with the one labeled as "Secondary Alerts", the second one as the default. We could call it text, have outlined and filled (the first one)

It's probably a good opportunity to introduce the success, info, and danger colors in the theme's palette.

👍 🎉 🚀

  <AlertClose />

I was wondering should we allow multiple close icons and an ability to override its appearance and/or behavior? There may be a use case when user can either close or snooze the alert. But that may belong in <AlertActions />. What do you think?

@r3dm1ke Without more information, I don't think that we should allow more than one close icon. I think that developers should be able to customize the look of the icon button, or not even render it if needed.

I think that @mbrookes has made a brilliant connection at https://github.com/mui-org/material-ui/issues/18750#issuecomment-563028653.
What if we were enabling people to use the Snackbar to render the Alert (as a possible use case)?
We have a customization example with the Snackbar that we could actually make the filled variant of the Alert (it almost has the same design as previously proposed).

@oliviertassinari my gut reaction is that this could be great: but on thinking about it for a second I'm less confident because the actual UI behavior of a snackbar (also called toast) is so different (it's fixed position, dismissable with an animation, etc.).  That said... I'm not deeply aware of how this project is structured.
Just to say it out loud: it seems to me that it's actually the Alert component that's the parent component.  I understand it's strange to think about it this way because the Snackbar has been implemented first, but consider that the Snackbar is actually an extension of the functionality of the Alert in a lot of ways.  Perhaps part of the work for creating Alert is also to change Snackbar to use the Alert implementation under the hood.  This is good because it could mean simply refactoring a lot of that Snackbar code into Alert and consuming it while also freeing up Alert usecases as described in this issue.

@dimitropoulos @oliviertassinari I actually think that <Snackbar><Alert>...</Alert></Snackbar> makes a lot of sense. Alert component provides styling to display messages of various natures (the success, info, danger etc) and it can appear, well, pretty much everywhere. For example, at the top of the screen, in a form, in a chat, in a widget of a dashboard, and at the edge of the sceen as well. So it would probably be perfect for people that want the Alert appearance but Snackbar behavior to use them together. But I do not think we should build any positioning constraints into the Alert component so as to allow users to render where they please. What do you guys think?

Yeah, that sounds good to me.  As far as the API is concerned I'm open minded but not sure.  Consider how the Avatar component, based pretty much entirely on the Chip component, doesn't exactly (via its API) call attention to the fact that it uses Chip under the hood.  It basically just feels like a bespoke component.  Perhaps we should do the same with Snackbar.  At the same time... It could be cool to isolate that Snackbar behavior and give the user the ability to put whatever they want in a Snackbar, kinda like how a Modal/Dialog works.

From my perspective, the main purpose of the Snackbar component is to handle the complexity of displaying toasts on the screen. So it includes position, animation, stacking, imperative API. It could come unstyled.
I very much agree with the presentation draw by @r3dm1ke.
@dimitropoulos I don't understand your point regarding the Chip and the Avatar.

@oliviertassinari I think I misunderstood how to use the Snackbar.  I thought it was a ready-made component that comes with styles and all that.
My point was that when you use Avatar you don't do: <Avatar><Chip {...someOptions /></Avatar>, rather, you instead just do <Avatar {...someOptions} />.  The UX of the API is such that you don't have to be even aware that under the hood, Avatar is really just a nice wrapper for Chip.
Similarly, we may want to do the same here.  Instead of doing <Snackbar><Alert {...someOptions}</Snackbar> we may be better off with an API that looks like <Snackbar {...someOptions} />.  But... now that I see that Snackbar doesn't work that way, I'll just default to whatever you all think is best.

OK, thanks for the clarification. But notice that the Avatar isn't a wrapper for the Chip component. However, you can provide an Avatar to the Chip component. I think that it would be great to keep the API declarative, close to the underlying DOM node.

doh
Well now.. not sure how I got that impression.  Sorry for the confusion :|

No problem :)

I drafted out a proposed API for the root Alert component, tell me what you think:

color: 'default' | 'primary' | 'secondary' | 'error' - color of the alert, pulling from the theme
variant: 'text' | 'outlined' | 'filled' | 'banner' - variants from here and here
raised: bool - not sure about this one, but we could provide a styling similar to that in Card
size: 'small' | 'medium' | 'large' - control the margin within the Alert simular to the size prop in Table
component: elementType - component to use to render the Alert
classes, className, children

I am not sure though, should we have an open prop, like one in Dialog? Because both of them have a Close component, so should we add an ability to control the visibility of the alert with a prop?

I would really like if we saw the addition of success, info, danger or the like for this.  Perhaps we start small with the initial feature and just allow it to be a very restricted set of colors (of course people can always override in the meantime) and then spin off some separate issues/work for introducing the other colors to the palette.
I, for one (and maybe for all), have had quite a few times where I've wished the palette had a danger color or an info color.

I fully agree, but that big of a feature (add new colors to the theme palette and update the color prop on all components that use it) probably belongs to a separate issue. @oliviertassinari how do we proceed on this?

then spin off some separate issues/work for introducing the other colors to the palette.

Yep! that's what I'm trying to say.  Start with as few colors as possible for Alert at first (maybe literally only one?) and then add the other colors when the palette improvements land.

@r3dm1ke I think there's a consensus that we can add these static colours to the theme ahead of any dynamic theme improvements (https://github.com/mui-org/material-ui/issues/18094#issuecomment-562785773 and elsewhere).
If they are added as part of this PR, then the work to add them to other components (where appropriate) can be handled separately, and probably incrementally.

@r3dm1ke

+1 for adding success, info, and warning.
I would encourage to wait for a compelling use case before adding the component prop.
I'm not sure about the size prop. I would encourage to wait for a compelling use case too.
By raised, is this a reference to the elevation prop of the Paper component? It sounds good, I think that we can base the Alert component on the Paper (so no need for raised, we would get elevation)

@oliviertassinari @dimitropoulos
raised was a reference to the prop with the same name of the Card component, and I think it just supplies elevation to the Paper under the hood, so they are interchangeable. It indeed makes sense to use Paper to base the Alert on, so it would not be hard to implement the elevation prop.
I just pushed a commit that adds warning, info and success colors to the palette, tell me what you guys think. I am no designer, so the specific colors I chose may not be ideal 😅, but it should be easy to change it.

I think it would be best to do the changes to the palette in another, separate, PR with a separate issue.  I was trying to say before that it might be best to implement Alerts (for now) with just one color (primary?) or maybe two (primary + secondary?) to keep it as simple as possible while we nail down the main functionality.  I imagine there are other concerns and such that will come up when expanding the palette and therefore it seems prudent to me for other people to be able to weigh in on that feature as it stands.
Great head start on the palette stuff, though!

I think it would be best to do the changes to the palette in another, separate, PR with a separate issue.

@dimitropoulos This sounds safer 👍.

Ok, sounds reasonable, I just misunderstood. Then I will revert the last commit and save it for later

@r3dm1ke (and anyone else interested) the conversation about theme palette colors is happening here https://github.com/mui-org/material-ui/issues/13875#issuecomment-446414932


FireAllInRangeExcept

How do I FireAllInRangeExcept on BridgeNet2?

You can't, it's not supported.
It ultimately didn't fit the scope of bridgenet2


fix: remove volume name from docker mount path

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/2428
What is the new behavior?
Removes C: from docker path on windows.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

9 of 10 (90.0%)  changed or added relevant lines in 3 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 60.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/utils/deno.go
7
8
87.5%

Files with Coverage Reduction
New Missed Lines
%

internal/debug/postgres.go
3
64.86%

internal/gen/keys/keys.go
5
11.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
6885

Relevant Lines:
11420

💛  - Coveralls


[Engine-1.21] Parser improvements, allow config values to be used with etcd-snapshot

Backport of 2 PRs:
https://github.com/k3s-io/k3s/pull/4383
https://github.com/k3s-io/k3s/pull/4464
Linked Issues
https://github.com/k3s-io/k3s/issues/4476

User-Facing Change

Flags in config.yaml can now be used by etcd-snapshot

Further Comments

Codecov Report

Merging #4477 (76f27e3) into engine-1.21 (8f82ae0) will increase coverage by 0.63%.
The diff coverage is 76.92%.

@@               Coverage Diff               @@
##           engine-1.21    #4477      +/-   ##
===============================================
+ Coverage        11.24%   11.87%   +0.63%
===============================================
  Files              133      133
  Lines             9232     8950     -282
===============================================
+ Hits              1038     1063      +25
+ Misses            7969     7658     -311
- Partials           225      229       +4

Flag
Coverage Δ

inttests
0.68% <0.00%> (+0.02%)
:arrow_up:

unittests
11.53% <76.92%> (+0.62%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/cli/cmds/server.go
0.00% <0.00%> (ø)

pkg/configfilearg/parser.go
75.00% <78.37%> (+2.02%)
:arrow_up:

pkg/configfilearg/defaultparser.go
15.38% <100.00%> (-23.51%)
:arrow_down:

Continue to review full report at Codecov.

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