Improve python version formatting 🐍 affects [pypi piwheels github]

After implementing the piwheels badge the other day I realised that I had just used renderVersionBadge() but our standard version formatter
https://github.com/badges/shields/blob/76a64a7896893bac4a1b52e683a0a542541b3bdb/services/color-formatters.js#L16-L20
isn't great for python packages because it will format something like 2.0.0rc1 or 2.0.0b2 as "stable".
Then I started pulling the thread and realised this problem actually also applies to some other python ecosystem badges.
so in this PR I have:

Added a pep440VersionColor() formatter function which uses https://github.com/renovatebot/pep440 to parse versions
Added the ability to pass renderVersionBadge() a custom formatter function as an optional param - this might be handy if we want to use a custom formatter for other package ecosystems.
Used this in the badges for pypi, piwheels and github-pipenv

Warnings

:warning:
This PR modified service code for pypi but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for piwheels but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for github but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against 59da3433547abf6602686a7afd76a12b8bbc75b2

I've rebased this to resolve the conflicts on package.json and package-lock.json as it was easier than doing it as a merge. No functional changes


wayland-protocols: 1.14 -> 1.15

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/wayland-protocols/versions.
These checks were done:

built on NixOS
0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 1.15 with grep in /nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15
directory tree listing: https://gist.github.com/ed6b2fe913e7aa8189e99f99b8d56511
du listing: https://gist.github.com/f55c3123eacd3a802f5007f3d8f49d3d

meta.description for wayland-protocols is: '"Wayland protocol extensions"'.
This build is cached with Cachix. To use the cache follow these instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout cac3ecea232d24e5a1413b86d058c5960b134f04 && nix-shell --pure -I nixpkgs=. -p wayland-protocols

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: wayland-protocols
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: wayland-protocols
Partial log (click to expand)
 /nix/store/kzkid23xcd26f19yh2kxi7v19m3ra315-coreutils-8.29/bin/install -c -m 644  unstable/text-input/text-input-unstable-v1.xml '/nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15/share/wayland-protocols/unstable/text-input'
 /nix/store/kzkid23xcd26f19yh2kxi7v19m3ra315-coreutils-8.29/bin/mkdir -p '/nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
 /nix/store/kzkid23xcd26f19yh2kxi7v19m3ra315-coreutils-8.29/bin/install -c -m 644  unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml '/nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
make[1]: Leaving directory '/build/wayland-protocols-1.15'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15
checking for references to /build in /nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15...
/nix/store/8bxhbp4dxhkf114igs0lg7y1xdb5cifm-wayland-protocols-1.15

Success on x86_64-linux (full log)
Attempted: wayland-protocols
Partial log (click to expand)
 /nix/store/n7qp8pffvcb5ff52l2nrc3g2wvxfrk75-coreutils-8.29/bin/install -c -m 644  unstable/text-input/text-input-unstable-v1.xml '/nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15/share/wayland-protocols/unstable/text-input'
 /nix/store/n7qp8pffvcb5ff52l2nrc3g2wvxfrk75-coreutils-8.29/bin/mkdir -p '/nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
 /nix/store/n7qp8pffvcb5ff52l2nrc3g2wvxfrk75-coreutils-8.29/bin/install -c -m 644  unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml '/nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
make[1]: Leaving directory '/build/wayland-protocols-1.15'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15
checking for references to /build in /nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15...
/nix/store/acbjqscvbj2a369m2cmx5waxpab9b3fp-wayland-protocols-1.15

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: wayland-protocols
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: wayland-protocols
Partial log (click to expand)
 /nix/store/l816bx8lgm0jwb7hzbc105h0fv097zry-coreutils-8.29/bin/install -c -m 644  unstable/text-input/text-input-unstable-v1.xml '/nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15/share/wayland-protocols/unstable/text-input'
 /nix/store/l816bx8lgm0jwb7hzbc105h0fv097zry-coreutils-8.29/bin/mkdir -p '/nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
 /nix/store/l816bx8lgm0jwb7hzbc105h0fv097zry-coreutils-8.29/bin/install -c -m 644  unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml '/nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
make[1]: Leaving directory '/build/wayland-protocols-1.15'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15
strip is /nix/store/90vmpr41dzsx350k5argycaf693hnl1l-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15
checking for references to /build in /nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15...
/nix/store/b4gybwvc4sfaw6kg2s2zdys14vmb19js-wayland-protocols-1.15

Success on aarch64-linux (full log)
Attempted: wayland-protocols
Partial log (click to expand)
 /nix/store/lqnf05qdjshwijs9dr3klzk31y4qkj2g-coreutils-8.29/bin/install -c -m 644  unstable/text-input/text-input-unstable-v1.xml '/nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15/share/wayland-protocols/unstable/text-input'
 /nix/store/lqnf05qdjshwijs9dr3klzk31y4qkj2g-coreutils-8.29/bin/mkdir -p '/nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
 /nix/store/lqnf05qdjshwijs9dr3klzk31y4qkj2g-coreutils-8.29/bin/install -c -m 644  unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml '/nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15/share/wayland-protocols/unstable/xwayland-keyboard-grab'
make[1]: Leaving directory '/build/wayland-protocols-1.15'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15
strip is /nix/store/7iyn7gn33i7xxjgmwf25k20246y6nd9d-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15
checking for references to /build in /nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15...
/nix/store/2rbqcp8ky1wv3rpqbmwqasn9s4gd673w-wayland-protocols-1.15

Changes:
https://lists.freedesktop.org/archives/wayland-devel/2018-July/038831.html


Service.addObserver(owner: closure:) Allows multiple observers for self

I was doing some testing of grabbing a resource, adding an observer and calling load in viewDidAppear. Within the closure I would print the 'event' and noticed after multiple calls to viewDidAppear the print statement was being called multiple times per an event.

override func viewDidAppear(animated: Bool) {
    super.viewDidAppear(animated)

    MyAPI.resource('/home').addObserver(owner: self, closure: {
        [weak self] resource, event in
        print(event)
    }
}

I dug around a bit and it appears that it might just be an issue with the ClosureObserver.

The problem is that Swift has no notion of closure identity or comparison: there’s no way for Siesta to know that you’re adding “the same” closure twice, because there’s no such thing as “the same” closure.
If you add an observer that’s an object, then Siesta will prevent dups. But otherwise, it’s up to you to make sure you don’t add redundant observers — by adding them in viewDidLoad instead of viewWillAppear, for example.

Prompted by this, I added some information about duplicate observers to the API docs. Thanks for the good question!
Also, an aside on the code you posted: in Swift, when the last arg is a closure, you can place it as a block after the method call. So instead of this:
MyAPI.resource('/home').addObserver(owner: self, closure: {
    [weak self] resource, event in
    print(event)
})

…you can do this:
MyAPI.resource('/home').addObserver(owner: self) {
    [weak self] resource, event in
    print(event)
}

You may already know that, but I though I’d mention it just in case.

That makes a lot of sense with Swift. I guess from the API of a Siesta Service class I made an assumption that 'self' would be the qualifier for adding an extra observer to that resource. Is there a use case to adding multiple 'self' owners to a specific resource?

The owners are about lifecycle, not uniqueness. When the owner goes away, the observer stops observing. When you want to remove observers, you do it by owner. There’s a detailed explanation in the docs.

Is there a use case to adding multiple 'self' owners to a specific resource?

Observers have owners, not resources, so I’m not quite sure what you mean by that. I’m guessing you mean, “Is there a use case for having multiple observers with the same owner?,” then sure; in fact, it’s quite common. For example, a view controller might might do this:
foo.addObserver(self)
bar.addObserver(self)
bar.addObserver(owner: self) {
    [weak barDisplayerWidget] in
    barDisplayerWidget?.refresh()
}

Here, the VC depends on two resources, so it observes both of them (as a self-owned observer). It also owns a barDisplayerWidget that wants to observer the second resource. All three observers are owned by self, so when the VC is deallocated, Siesta automatically stops sending events to all of them.
This also has the advantage that you can remove multiple observers at once:
for resource in [foo, bar] {
    resource.removeObservers(ownedBy: self)
}

…which is a common idiom when one VC wants to change which resource it’s observing. There’s an example of this in the sample project.

I understand now with that example. My pattern was to only have one observer per a resource per a controller. Having multiple closures available I can see being helpful. I will switch to using the just addObserver(self) for my current case and implementing ResourceObserver protocol.


README file Update

Codecov Report

Merging #50 (0eb14ab) into main (cdea35b) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main     #50   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          8       8
  Lines        529     529
=====================================
  Misses       529     529

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 cdea35b...0eb14ab. Read the comment docs.


Add Qonto extension

Description
This PR adds Qonto as a new Extension. 2 commands are available:

Search bank accounts
Search transactions

The user will enjoy the following features:

List bank accounts and transactions
Filter bank accounts and transactions
Show/copy IBAN
Download transactions as CSV
Setup datetime format (20/07/2022 or 07/20/2022 checkout preferences)
Setup currency format (1 000,00 €, €1,000.00 or 1.000,00 € checkout preferences)

To access Qonto data, the user must set up a login and secretKey provided on app.qonto.com > settings > Integrations > API Key. To use it without credentials, a demo mode option with fake data is available in the Extension preference (clic demo and write demo/demo as login/secretKey).
Screencast
https://user-images.githubusercontent.com/743358/231434827-d5a44887-b4d0-435d-b000-f1499ebbe9b9.mp4
Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

Hello @pernielsentikaer, I made the requested changes. Waiting for your review 🙂


[Question] Still active?

This looks incredible!
Just a couple of questions on the project itself:

Are you still actively developing this?
Are you using it any production applications?
Have you spoken to anyone at Microsoft regarding Reactor and their road to open-sourcing bits of it?

Thanks!

Yes, I am still actively developing Qactive. Currently, I'm experimenting with better graph serialization in a local branch, and the results are promising.
(Can't say)
Unfortunately not. I don't have any contact with MS. But I'm still very much interested in seeing what they've built! I hope that it goes OSS.

Awesome, thanks for your reply :)


"Variable assigned but never used" false positive in a script block passed to ForEach-Object

Steps to reproduce
(Initially reported in downstream repo, see https://github.com/ant-druha/intellij-powershell/issues/96, but with my adjustments to better demonstrate the behavior.)
(1..3) | ForEach-Object {
    $Hashes = "test"
} {
    $Hashes += "Some-String "
} {
    $Hashes
}

Expected behavior
There should be no warnings about the initial value of the $Hashes variable not being used in this code.
To demonstrate that it is in fact used, run the code, and you'll see output testSome-String Some-String Some-String: test value was used.
Actual behavior

The variable 'Hashes' is assigned but never used.PSScriptAnalyzer(PSUseDeclaredVarsMoreThanAssignments)

Environment data
While it was reported in intellij-powershell where we bundle v1.21.0, I was also able to reproduce the same in VSCode.

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.3.7
PSEdition                      Core
GitCommitId                    7.3.7
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.21.0

Additional Information
From a quick look, it may be related to #1472.

Duplicate with #1163?

I think it's a duplicate. Thank you!

Anyways, I think these rules have been oversimplified this issue were it could just be: don't warn if the concerned variable can be found back (anywhere) in the script (even this might not capture everything, which is better than a false-possitive)


Resource Approximations For All Space-Time Operators

For every operator, approximate how much compute and memory will be required on the target chip.


Install issues

Python: 3.x
OS: Raspbian Stretch
Kivy:
Kivy installation method: manual

Description
I have tried installing Kivy on two different RPi's. Used the manual method and tried compiling locally first. On one system I was able to compile but unable to run any of the demo programs.
Then I tried using the git+install...@master instruction and was able to get Kivy installed. However, on one system, when I try to run the demo programs, I get the following output:
[INFO   ] [Logger      ] Record log in /home/pi/.kivy/logs/kivy_19-02-08_3.txt
[INFO   ] [Logger      ] v1.11.0.dev0, git-775cd93, 20190208
[INFO   ] [Logger      ] v2.7.13 (default, Sept 26, 2018, 18:42:22)
[GCC <IP_ADDRESS>70516]
[INFO   ] [Logger      ] 184 symbols loaded
[INFO   ] [Logger      ] Providers: img_tex, img_dds, img_pil, img_gif (img_sdl2, img_ffpyplayer ignored)
[INFO   ] [Logger      ] Provider: egl_rpi
[INFO   ] [Logger      ] Using the "openGL ES 2" graphics system
[INFO   ] [Logger      ] Backend used (sdl2)
Segmentation fault
On the other RPi, I get the following:
Traceback (most recent call last):
File "main.py", line 15, in
from kivy.app import App
ImportError: No module named kivy.app
What did I do wrong?
Thanks,
pete

Duplicate of #6007

Pointing me to that other ticket only addresses one of the issues I had; what about the other?
Traceback (most recent call last):
File "main.py", line 15, in
from kivy.app import App
ImportError: No module named kivy.app

Thanks,
pete


FALCON-2204 Change mode for falcon_merge_pr.py to executable

This pull request changes the permissions to be executable.

Unrelated build failure. 👍

Looks good. :+1:


Update to Fontawesome 6.1.1

It'd be great to have an update to Font Awesome 6.1.1.
The reason is that they added a lot of new icons in 6.1.0 as described in their changelog. I'd love to be able to make use of those.
I'd be happy to make a pull request for it myself, but it's probably just as much work for you to review the PR as doing the whole thing yourself :).

Hi @eKIK!
Just released version 0.7.1 with FontAwesome 6.1.1
These new icons are amazing 👍


Anchorwave large chromosome error

Hello,
We are currently trying to run Anchorwave on the huge Axolotl genome (32 Gbp) and we are getting the following error:
Command:
anchorwave proali -t 19 -i GCF_000001405.39_GRCh38.p13_genomic.gff -as human_cds.fa -r GCF_000001405.39_GRCh38.p13_genomic.fna -ar human.sam -a axolotl.sam -s AmexG_v6_scaffolds_withMT-AJ584639_withUnplacedContigs.fa -y 0.4 -n hum_axo_anchors -R 1 -Q 1 -o human_vs_axolotl_alignment.maf -f human_vs_axolotl_alignment.f.maf

Error:
  SSE4.1 is enabled
  anchorwave: /Apps/anchorwave/src/service/TransferGffWithNucmerResult.cpp:427: void readSam(std::vector<AlignmentMatch>&, std::ifstream&, std::map<std::__cxx11::basic_string<char>, Transcript>&, int&, const double&, double&, std::set<std::__cxx11::basic_string<char> >&, int32_t&, int32_t&, int32_t&, int32_t&, int&, bool&, int&): Assertion `chromosomePosition==transcriptHashMap[elems[0]].getPEnd()' failed.
  .command.sh: line 2: 59509 Aborted                 anchorwave proali -t 19 -i GCF_000001405.39_GRCh38.p13_genomic.gff -as human_cds.fa -r GCF_000001405.39_GRCh38.p13_genomic.fna -ar human.sam -a axolotl.sam -s AmexG_v6_scaffolds_withMT-AJ584639_withUnplacedContigs.fa -y 0.4 -n hum_axo_anchors -R 1 -Q 1 -o human_vs_axolotl_alignment.maf -f human_vs_axolotl_alignment.f.maf

We suspect this is due to the chromosome coordinates exceeding the size of the declared variables, which is a common problem with this genome. Is there any chance you could fix this? We would be happy to help with any testing or anything that would help solve this issue!
Thank you!

Could you please share where could I found those input files please?

Sure! We are uploading the files and will send them to you by the end of the week. Thanks!!

Similar error but different cause.  This assertion can also fail when there is a slight overlap in the CDS coordinates such as in this example from GCF_000001405.26_GRCh38_genomic.gff:
790294:NC_000007.14     BestRefSeq      CDS     94663334        94664513        .       +       1       ID=cds26285;Parent=rna33791;Dbxref=GeneID:23089,Genbank:NP_001165908.1,HGNC:14005,MIM:609810;Name=NP_001165908.1;Note=isoform 3 is encoded by transcript variant 2;exception=ribosomal slippage;gbkey=CDS;gene=PEG10;product=retrotransposon-derived protein PEG10 isoform 3;protein_id=NP_001165908.1
790295:NC_000007.14     BestRefSeq      CDS     94664513        94665682        .       +       0       ID=cds26285;Parent=rna33791;Dbxref=GeneID:23089,Genbank:NP_001165908.1,HGNC:14005,MIM:609810;Name=NP_001165908.1;Note=isoform 3 is encoded by transcript variant 2;exception=ribosomal slippage;gbkey=CDS;gene=PEG10;product=retrotransposon-derived protein PEG10 isoform 3;protein_id=NP_001165908.1

This overlap of 1bp breaks your method of counting chromosome positions in TransferGffWithNucmerResult.cpp::readSam()  -- both function signatures.

Similar error but different cause. This assertion can also fail when there is a slight overlap in the CDS coordinates such as in this example from GCF_000001405.26_GRCh38_genomic.gff:
790294:NC_000007.14     BestRefSeq      CDS     94663334        94664513        .       +       1       ID=cds26285;Parent=rna33791;Dbxref=GeneID:23089,Genbank:NP_001165908.1,HGNC:14005,MIM:609810;Name=NP_001165908.1;Note=isoform 3 is encoded by transcript variant 2;exception=ribosomal slippage;gbkey=CDS;gene=PEG10;product=retrotransposon-derived protein PEG10 isoform 3;protein_id=NP_001165908.1
790295:NC_000007.14     BestRefSeq      CDS     94664513        94665682        .       +       0       ID=cds26285;Parent=rna33791;Dbxref=GeneID:23089,Genbank:NP_001165908.1,HGNC:14005,MIM:609810;Name=NP_001165908.1;Note=isoform 3 is encoded by transcript variant 2;exception=ribosomal slippage;gbkey=CDS;gene=PEG10;product=retrotransposon-derived protein PEG10 isoform 3;protein_id=NP_001165908.1

This overlap of 1bp breaks your method of counting chromosome positions in TransferGffWithNucmerResult.cpp::readSam() -- both function signatures.

Thanks. The above two lines indicate that the 94664513 bp belong to two CDSs at the same time, and the length of the intron is -1 bp.
From my point of view, this is a problem with the GFF file.

Agreed, however the world is a rough and tumble place.  Letting the user know the source of the issue (rather than a simple assert failure), would help them 1) identify the offending line(s) in the GFF file so they can remedy the situation, and 2) not incorrectly blame the issue on your tool.   Or, preferably you could report the problem as a warning and have a sensible default remedy coded ( disregard any overlap and treat as blunt ends, or remove/disqualify the overlapping CDS), that would allow your tool to run more robustly in a larger workflow.

Are there any updates on this issue? I am encountering a similar error when running proali -R1 -Q1
AVX2 is enabled
anchorwave_avx2: /opt/conda/conda-bld/anchorwave_1684247957463/work/src/service/TransferGffWithNucmerResult.cpp:432: void readSam(std::vector<AlignmentMatch>&,  std::ifstream&, std::map<std::__cxx11::basic_string<char>, Transcript>&, int&, const double&, double&, std::set<std::__cxx11::basic_string<char> >&, int32_t&,  int32_t&, int32_t&, int32_t&, int&, bool&, int&): Assertion `chromosomePosition == transcriptHashMap[elems[0]].getPEnd()' failed.

The parsing of GFF files is complex.
I was trying to find a programmer to help fix this, but I have not found one yet.
@jgroh For your problem, please DO use the CDS file generated from the anchorwave gff2seq command. The CDS fasta file downloaded or generated using other software/script would NOT work.


Accents/diacritics in Clearspeak

Stumbled across this when working with word problems:
<math>
  <mfrac>
    <mtext>Number of lattés sold</mtext>
    <mtext>Number of cafés</mtext>
  </mfrac>
</math>

With Clearspeak and SRE v3.2 this results in "Number of latt e acute s sold over Number of caf e acute s" -- note the accented letters break the word and explicitly describe the modified letter.  Mathspeak also splits the speech: "StartFraction Number of latt modifying above e with acute s sold Over Number of caf modifying above e with acute s EndFraction"
I tried using <mi> and <mi><mtext> in place of <mtext> above which change the results a bit but still expand out the accented letters.
I'm certainly open to other approaches for handling word problems in MathML (this example is a simplification for illustration), but suspect that diacritics will interrupt the resulting speech across the board.

Sorry, this one fell through the cracks. There was little time for SRE at the beginning of the year. The issue is due to SRE parsing the text in order to find and translate math symbols. This is done using a regexp for the particular locale. English does not contain characters with diacritics in that regexp (unlike French for example), hence SRE assumes that these letters are accented math characters and translates them accordingly.
Making a general change to the way text elements are treated would be difficult in that it would badly affect content that do not explicitly mark up single math characters in mtext elements as quite a number of publishers do.
If you have control over the content I could suggest using one of the attributes, like
'aria-label', 'exact-speech', 'alt' around the "latte" element.


Do the gs: files in the code still exist?

I am trying out the code in scifive_pretrain_base.ipynb.
I got
OSError: Unable to open file for all the gs: files in the code
'gs://t5_training/t5-data/config/pretrained_models_google_base_operative_config.gin'
gs://mindxhack/bio_sentence_piece_small.txt
I tried look them up using the google cloud storage browser and don't see these files.
The browser does find the model files like
gs://scifive/models/pubmed_pmc/base
So the question is whether this is working code as is. Do these dependent files still exist on the cloud?

Hi @bhomass , gs://mindxhack/bio_sentence_piece_small.txt should be any text file of your own to train a tokenzier model for model

thank you. What about gs://t5_training/t5-data/config/pretrained_models_google_base_operative_config.gin?


node client sdk: transaction security

We need ability to create secured transactions (sign with tcert) in the node.js client sdk. This is the code from fabric/core/crypto.  We should refactor this module to provide functions that allow the application to create secured transactions prior to sending to the peer.

This should be included in https://github.com/hyperledger/fabric/issues/1117

@binhn Binh, I think this can be closed.


Cloud Firestore crashes natively on DocumentReference.get()

This is an issue that comes up rarely, but consistently.
I make a CollectionReference, and get a DocumentReference from it, and then call .get() on the DocumentReference. Getting the CollectionReference and DocumentReference works just fine, but the app crashes natively when .get() is called. The DocumentReference points to a real document in the database. My code is as follows
CollectionReference usersCollection = _fireStore.collection(_usersCollection);
    print("Created users collection reference");
    DocumentReference userDoc = usersCollection.document(uid);
    print("Created user's document reference");
    DocumentSnapshot usr = await userDoc.get();
    print("Data retrieved");`
The debug output is
`flutter: Created users collection reference
flutter: Created user's document reference
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff23c7127e __exceptionPreprocess + 350
	1   libobjc.A.dylib                     0x00007fff513fbb20 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff23c70ff8 +[NSException raise:format:arguments:] + 88
	3   Foundation                          0x00007fff256e9c1a -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   Runner                              0x000000010d402bd4 _ZN8firebase9firestore4util16ObjcThrowHandlerENS1_13ExceptionTypeEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 356
	5   Runner                              0x000000010d402413 _ZN8firebase9firestore4util5ThrowENS1_13ExceptionTypeEPKcS4_iRKNSt3__<…>
Lost connection to device.

Output of flutter doctor:
`[✓] Flutter (Channel master, v1.15.4-pre.83, on Mac OS X 10.15.3 19D76, locale
en-US)
• Flutter version 1.15.4-pre.83 at /Users/OwenScott/devtools/flutter
• Framework revision ec9813a500 (2 days ago), 2020-02-16 19:15:52 -0800
• Engine revision d60f298d9e
• Dart version 2.8.0 (build 2.8.0-dev.9.0 edd64e6d5c)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /Users/OwenScott/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling
support)
• Platform android-29, build-tools 28.0.3
• Java binary at: /Applications/Android
Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.3.1, Build version 11C504
• CocoaPods version 1.9.0.beta.2
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 43.0.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
[✓] IntelliJ IDEA Community Edition (version 2019.3.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 43.0.3
• Dart plugin version 193.6494.35
[✓] VS Code (version 1.40.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.6.0
[✓] Connected device (1 available)
• iPhone 11 Pro Max • 4CE40E91-D69E-4A87-B150-A865C351FEB3 • ios •
com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)
• No issues found!
`

Note: I have discovered the steps to reproduce
Call .get() on a DocumentReference with an empty document id, ie
await Firestore.instance.collection("MyCollection").document("").get();
I understand why this happens and that this can simply be avoided by String validation before the .document() method is called, but it would still be better to return an error message natively and throw an exception at the Dart / Flutter level so that the app doesn't crash egregiously without any clear reason.

This was flagged in another issue and needs fixing/validation, however doing .document("") is invalid since you can't query an "empty" document.

Fixed via https://github.com/FirebaseExtended/flutterfire/pull/2913


Using MockHttp with AutoFixture AutoData

Hi,
I'm trying to use MockHttp with AutoFixture's AutoData attribute.
To test the library, I've created a test repo that contains only two tests:
public class Tests
{
    [Test, CustomAutoData]
    public async Task Basic_test(Uri testUri, string result)
    {
        var handler = new MockHttpMessageHandler();

        var sut = new TestService(handler.ToHttpClient());

        handler.When(HttpMethod.Get, testUri.ToString()).Respond(HttpStatusCode.OK, new StringContent(result));

        var actual = await sut.GetString(testUri);

        Assert.That(actual, Is.EqualTo(result));
    }

    [Test, CustomAutoData]
    public async Task Test_with_custom_autodata([Frozen] MockHttpMessageHandler handler, TestService sut, Uri testUri, string result)
    {
        handler.When(HttpMethod.Get, testUri.ToString()).Respond(HttpStatusCode.OK, new StringContent(result));

        var actual = await sut.GetString(testUri);

        Assert.That(actual, Is.EqualTo(result));
    }
}

public static IFixture CreateFixture()
{
    var fixture = new Fixture();

    fixture.Customize<HttpClient>(o => o.FromFactory((MockHttpMessageHandler handler) => handler.ToHttpClient()));

    return fixture;
}

This setup is not working as the second test fails due to a CancellationToken being on "ThrowIfCancellationRequested".
Changing the customizations as follow makes the second test working. Unfortunately this is not optimal because it makes the setup too dependent on the SUT constructor.
public static IFixture CreateFixture()
{
    var fixture = new Fixture();

    //fixture.Customize<HttpClient>(o => o.FromFactory((MockHttpMessageHandler handler) => handler.ToHttpClient()));

    fixture.Customize<TestService>(o => o.FromFactory((MockHttpMessageHandler handler) =>
    {
        var http = handler.ToHttpClient();

        return new TestService(http);
    }));

    return fixture;
}

This issue is mostly about a clarification about the "chain".
I was expecting:

TestService (default setup) to require a HttpClient
HttpClient use the provided customization based on FromFactory that requires a MockHttpMessageHandler
MockHttpMessageHandler to be newed up using the default setup

Thanks for your help!
I opened an issue on MockHttp here: https://github.com/richardszalay/mockhttp/issues/73

@Kralizek don't know if you still need help with this but it seems that you need a custom specimen builder.
I've made a small gist for you.
Basically you add that specimen builder and then instead of using the factory you customize your Fixture like this:
fixture.Customizations.Add(new HttpClientSpecimenBuilder());

Thanks for your help! I'll check it later this week :)

@aivascu do you mind if I put your specimen into a NuGet package?

@Kralizek not at all, as long as the package is open source and you credit my contribution.


dollar signs in source blocks

It seems asciidoctor-latex currently parses the content of a source block. The following example shows their interaction.
foo.adoc:
= Include Bug Demo

Testing $x$, $y$.

[source,perl]
----
print $_, $_;
----

EOF

The output for the source block is:
print pass:[\(_, \)]_;

This seems counterintuitive since we may expect that a source block to be processed only by a source highlighter. While we may expect the writer to alter the code in a source block to escape the dollar signs and thus this interaction may be acceptable, this interaction effectively prohibits the use of include, (e.g., include::bar.pl[]).

I agree this should not happen. This is the danger of using a preprocessor to process syntax. A preprocessor does not recognize the structure of the AsciiDoc document, so it's going to lead to these sorts of bugs. A tree processor is the right solution because it can choose which nodes in the tree to process.
(I'm considering other types of extensions that might offer more flexibility, but those are still just considerations).

Does this mean there is currently no safe method to use include with asciidoctor-latex? Thanks!


PlayStore DeepLink Issue

Some deep links may be failing because your web domains aren't associated with your app
This means that on Android 12 and above, your app can't accept traffic from some web URLs. To fix issues and make sure that users go directly to your app, go to the Deep links page.
Details:
https://play.google.com/console/u/1/developers/8548546370386799497/app/4973272515950350768/deeplinks?selectedVersionCode=215

[ ] Put assetlinks JSON file on sever
[ ] Fix  tag failed
Add a "/" to the beginning of the android:path attribute in the  tag. The attribute might also be android:pathPrefix or android:pathPattern.

Hi @seabornlee I independently did this work, it does require an update that I don't have permission to push to the
DMZ site (aw.app), I will get that actioned by the current owner(s).


fun situation for deinit

this is not real pr
@gmlwhdtjd
introduce fun situation of deinit 🤣, we can see from failed test case.
bug in UIKit??
I guess some code run in autorelease block, may be.

@gmlwhdtjd
ok deinit is not working well same code frame some state.

introduce our fun situation @ioskrew/ioskrew


Acyl-CoA (CHEBI:17984) has CAS regno 9029-97-4 for the transferase

Acyl-CoA (CHEBI:17984) has CAS regno 9029-97-4 (source KEGG), but according to CAS Common Chemistry, this CAS registration number is for the Acetyl-coenzyme A C-acyltransferase. See https://commonchemistry.cas.org/detail?ref=9029-97-4

CAS number now removed. Thanks


KO after tydom update

Hi,
I have a Tydom 2.0 working well since 2 years with homeassistant (alarm and covers). Thanks a lot fmartinou for this wonderful integration with HA.
After upgrading the TYDOM firmware from my smartphone app; nothing works with HA (alarm or covers) :-(
Try to reboot HA without success
This is my tydom 2.0 config

And the HA Addons log

For information, all works well with the smartphone app after the update.

After a host reboot, all is working well. Sorry


Reverse Words in a String -leetcode 151

@larissalages  I can add a solution to the leetcode problem 151- Reverse Words in a String (Medium).
please assign me this issue.

Can you please assign this issue to me ?


untrack()

Hi,
is there a recommended way to untrack()?
I have an effect that writes to a signal that I want to untrack after the first write so that it doesn't go in the way of the other signal writes that would otherwise re-trigger the effect. (the write happens in an effect which is necessary in that context, but due to the fact that it in an effect call, it is tracked and retriggers. It doesn't auto-retrigger because the signal is memoized but when other pieces of the code write to the value of the signal, this effect is triggered and overwrites again)
In Solid you have untrack() but here I just found one such function in the tests.
Thanks btw for the project, I started the same project 2 weeks ago because I had the same pain... and then found usignal :)
Best

Solved it with a peek() and conditional for the moment, but a way to untrack would be nicer:

const simplifiedExample = () => {

  const slugToCreate = useSignal('')

  const onInput = (event) => (slugToCreate.value = event.target.value)

  effect(async () => {
    if (slugToCreate.peek() === '') {
      slugToCreate.value = await getSlugToCreate()
    }
  })

return (<input
    type="text"
    value={slugToCreate.value}
    onInput={onInput}
    placeholder="Type here.."
    class="input input-bordered w-full max-w-xs"
  />)
}

beside the fact tat peek() is the solution to these and other cases where side-effects are not always desired (there is your untrack ... there's nothing to untrack if you don't track it in the first place), if the value is the same nothing happens to the signal or its chain of effects so I am having really hard time to understand what is it that you are trying to solve ... does the subscription bother you, even if the value is always the same? is the value not always the same but you want it to side-effect only the first time? In latter case, you have the solution, and there's nothing for me to do, so I can close it, I suppose, feel free to add more context in case it needs to be re-opened.

It was the latter case, but it's not so beautiful, because the solution to not get it tracked in the first place is not always applicable -- it is in this case, but there are so many other cases where you are running code in an effect and at some point in time you'd like to stop that tracking from happening. Imagine you didn't think of that before -- so you can now try and refactor your code with many conditionals to solve it -- but arguably, it would be a much better DX if you would just be able to call an untrack() at any time, and be fine with an easy escape. Maybe you want 3 calls in 20 seconds and then untrack. How do you solve such cases? With a lot more signals where you aggregate that state and then make it conditional. But thats a lot of code and complexity compared to a potential untrack() call. I don't know if thats easy to implement though.

Also relevant: adding an untrack() to a signal is footgun prone because signals can be passed along many components or function and untracking it somewhere might result into undesired behavior elsewhere ... if the untrack should be targeted only for the current effect you'll have bad/ugly performance due extra list of tracking effects attached to a signal ... using a conditional peek() is fine both for read and write operations which is why I believe you should not think what Solid does, as that's another world/pattern/solution based on tooling and AOT speculations, here I am following closer Preact signals but also I think if there's a solution, there's no need to bloat the library.

there are so many other cases where you are running code in an effect and at some point in time you'd like to stop that tracking from happening

name one ... 'cause I don't understand this use case to start with ... you either are interested in a signal, or you should just pass a state instead and handle that.

Also relevant: adding an untrack() to a signal is footgun prone because signals can be passed along many components or function and untracking it somewhere might result into undesired behavior elsewhere ... if the untrack should be targeted only for the current effect you'll have bad/ugly performance due extra list of tracking effects attached to a signal ... using a conditional peek() is fine both for read and write operations which is why I believe you should not think what Solid does, as that's another world/pattern/solution based on tooling and AOT speculations, here I am following closer Preact signals but also I think if there's a solution, there's no need to bloat the library.

Okay, I agree with you. The arguments here are probably to be valued more than a slight DX improvement for edgy cases. And tbh the Solid speculations and the compiler and all gave me many footguns when I reimplemented Next.js with Solid as its core. It's not public yet, but I'll soon publish it. I was recently thinking to just throw out Solid again, because I would gain the same results by just combining my JSX runtime (springtype) with a reactivity library (as I said, I was writing it but then I paused that because of reasons and now I found this lib of yours :)

more on my thoughts:
// solve one-off empty to not-empty
if (!(state.key = signal.peek()))
  state.key = signal.value;

// solve X amount of changes
if ((state.key = signal.peek()) < 3)
  state.key = signal.value;

Yep, that would do in most cases. Thank you for your time!

Maybe one last question: What are your thoughts on signal based state management using Proxies? I was thinking to extract and implement something like https://www.solidjs.com/docs/latest/api#createmutable -- I like the DX of it alot; it's intuitive and not too bad in performance for most real world use-cases

does that triggers updates on effects interested in just store.name when store.surname = 'changed' happens?

the case all effects are triggered when any change happens to the store:
const handler = {
  get: (target, name) => target.value[name],
  set(target, name, value) {
    if (target.peek()[name] !== value)
      target.value = {...target, [name]: value};
    return true;
  }
};

const creteMutable = target => new Proxy(signal(target), handler);

the case each store value, including accessors, are handled differently, could be handled as such (haven't tried it yet, but I think it's a way to make it work):
function createSignal([name, descriptor]) {
  const shrinked = {
    accessor: !descriptor.hasOwnProperty('value'),
    signal: signal({$: this})
  };
  if (shrinked.accessor) {
    shrinked.get = descriptor.get;
    shrinked.set = descriptor.set;
  }
  return [name, shrinked];
}

const handler = {
  get(map, name) {
    const descriptor = map.get(name);
    const {value: {$}} = descriptor.signal;
    return descriptor.accessor ?
      descriptor.get.call($) :
      $[name];
  },
  set(map, name, value) {
    const descriptor = map.get(name);
    const {accessor, signal} = descriptor;
    const $ = signal.peek();
    let changed = !accessor && (value !== $[name]);
    if (accessor) {
      batch(() => {
        const p = new Proxy($, {
          set($, name, value) {
            if ($[name] !== value) {
              changed = true;
              $[name] = value;
              map.get(name).signal.value = {$};
            }
          },
          valueOf: () => $
        });
        descriptor.set.call(p, value);
      });
    }
    else
      $[name] = value;
    if (changed)
      this.signal.value = {$};
  }
};

const creteMutable = target => new Proxy(
  new Map(
    Array.prototype.map.call(
      Object.entries(
        Object.getOwnPropertyDescriptors(target)
      ),
      createSignal,
      target
    )
  ),
  handler
);

Btw, I thought untrack was kinda permanent but it looks lik eit's exactly a peek() so my comment on undesired side effects might be misleading. Apologies for that.

Hi :) sry for the long delay, there was been quite a bunch of stuff going on irl...
Thank you, yeah, I realized that too and started playing with different reactive store ideas in my head and as PoCs
I ended up separating the concern of "obervation of change" on an object and the concern of "reactivity" and ended up building this:
https://github.com/jsheaven/observed
and on top that:
https://github.com/jsheaven/reactive
It's not perfect and couldn't be compared to the power and quality of usignal but yeah, it's a very simple "nano" approach with a different idea in mind -- opt-in reactivity, but still, "true" reactivity :)


docs: add reference to custom api clients from cli overview

fixes #4200
Signed-off-by: Marcos Lilljedahl<EMAIL_ADDRESS>

WDYT @jpadams? https://github.com/dagger/dagger/pull/4156#issuecomment-1358027732
Going for rebase & merge when all checks pass.


docs(readme): add testing requirements section

This is to be merged after #10.  The main purpose of submitting it right now is to ensure the lack of Cirrus CI concurrency at a repo-level.  The checks here should run at the same time as the checks currently running on #10 (there is expected slow-down due to user-level concurrency).

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


Erro Shadow atribute at Login

@rmurussi Can you please share error for which you created this PR?

This is already fix in this : https://github.com/codedthemes/mantis-free-react-admin-template/commit/ce3779e0a2192e3f2470f7e6933baa48d5732b9e


Add new tests to test SSE-S3 using a KMS

Test SSE-S3 with both combinations of environment variable MINIO_SSE_AUTO_ENCRYPTION {on  and off}

With auto encryption, all tests automatically test encryption for all operations. So all it requires is a mint-auto change.


fix(other): Push only after release is published

Signed-off-by: Ingo Bürk<EMAIL_ADDRESS>

This pull request relates to or closes the following issues:
I have verified that…

[x] the commits in this pull request follow the conventionalcommits pattern
[x] tests have been updated or added
[x] documentation has been updated to reflect the changes made

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #80   +/-   ##
=======================================
  Coverage   83.16%   83.16%
=======================================
  Files          23       23
  Lines         612      612
  Branches       90       90
=======================================
  Hits          509      509
  Misses         52       52
  Partials       51       51

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 5ff3d94...ecf709e. Read the comment docs.


CMake/Windows: definition of dllimport function not allowed openhmd-shared

This commit introduced DLL entry points in the function definitions
https://github.com/OpenHMD/OpenHMD/commit/34a57c35facf9489777d531618964a937d5f85c6
And this one added a couple more:
https://github.com/OpenHMD/OpenHMD/commit/039fb4d96e6a5dae96c16f8ba5008af03906dbda#diff-1d18002189189eaac845866819a755c6
Unless I am missing something this is triggering the following when building with CMake (generating for VS 2019):
Error	C2491	'ohmd_ctx_create': definition of dllimport function not allowed	openhmd-shared	\src\openhmd.c	21

Reverting the commits above fixes the issue.

cc @pH5 and @Wallbraker


docs: title && demo

Codecov Report

Merging #738 (23ce3a1) into release/0.16.0 (ecdbc62) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release/0.16.0     #738   +/-   ##
===============================================
  Coverage           57.14%   57.14%
===============================================
  Files                   1        1
  Lines                  70       70
  Branches               18       18
===============================================
  Hits                   40       40
  Misses                 30       30

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 ecdbc62...a826166. Read the comment docs.

Codecov Report

Merging #738 (23ce3a1) into release/0.16.0 (ecdbc62) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release/0.16.0     #738   +/-   ##
===============================================
  Coverage           57.14%   57.14%
===============================================
  Files                   1        1
  Lines                  70       70
  Branches               18       18
===============================================
  Hits                   40       40
  Misses                 30       30

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 ecdbc62...a826166. Read the comment docs.


Update Plugin Artifacts Links for v0.134.0

Automated changes by create-pull-request GitHub action

 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.


add ci CIFuzz Github action

What type of PR is this?
/kind feature
What this PR does / why we need it:
Add CIFuzz workflow action to have fuzzers build and run on each PR.
This is a service offered by OSS-Fuzz where OpenYurt already runs. CIFuzz can help detect regressions and catch fuzzing build issues early, and has a variety of features (see the URL above). In the current PR the fuzzers gets build on a pull request and will run for 300 seconds.
Does this PR introduce a user-facing change?

No

@DavidKorczynski Hi, openyurt has some sub projects, like openyurt and yurt-app-manager. Currently, only yurt-app-manager uses oss-fuzz, as show in https://github.com/google/oss-fuzz/blob/master/projects/openyurt/Dockerfile. So I think it's better   make a pr for https://github.com/openyurtio/yurt-app-manager.


Updated to Swift 2.0 Changes

Just stumbled upon this when I was using Alamofire with one of my Swift 2.0 projects, and thought I'd do a quick fork.

Looks like I missed the playground in the conversion. Thanks @terhechte!


site.request["parameters"] defined by an inheriting scraper is never used

A user of Juriscraper may want to use the defined interface through self.request. However, it does not behave as expected. I was trying to understand why the minn scraper had to redefine request_url_get, instead of just using self.request["parameters"], self.request["headers"] and self.request["verify"]. The explanation is below
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/opinions/united_states/state/minn.py#L43-L53

Somewhat confusingly, there are 2 "parameters" attributes defined on AbstractSite
self.parameters which is used only on POST requests as the data argument
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/AbstractSite.py#L68
self.request["parameters"] which, if defined explicitly in an inheriting Site, will never be used
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/AbstractSite.py#L48-L58
This is due to _download being called by _parse without a request_dict argument
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/AbstractSite.py#L139-L142
The effect of this, is that the existing self.request["parameters"] will always be deleted by process_request_parameters
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/AbstractSite.py#L322-L335
Since the default is always an empty dict
https://github.com/freelawproject/juriscraper/blob/6a645346dce8f4ab4173a9a196093df7aa2e9120/juriscraper/AbstractSite.py#L354-L359

Related to #1106 and #1064

Nice. Looks like you've got the fix figured out too, right? I'll put this on your backlog. Thank you.

while we are fixing things - @grossir do you think we should fix the data/parameters overlapping language?  have you noticed this?

this is something I've wanted to get to for a while.  thanks for tackling this.  this should make things much nicer


KAFKA-10199: Shutdown state updater on task manager shutdown

When the task manager is shutdown, the state updater should also
shutdown. After the shutdown of the state updater, the tasks
in its output queues should be closed.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Call for review: @wcarlson5 @lihaosky

Build failures are unrelated:
Build / JDK 11 and Scala 2.13 / kafka.api.TransactionsExpirationTest.testTransactionAfterProducerIdExpires(String).quorum=zk
Build / JDK 8 and Scala 2.12 / org.apache.kafka.clients.consumer.CooperativeStickyAssignorTest.testLargeAssignmentAndGroupWithNonEqualSubscription()
Build / JDK 8 and Scala 2.12 / org.apache.kafka.clients.consumer.StickyAssignorTest.testLargeAssignmentAndGroupWithNonEqualSubscription()
Build / JDK 8 and Scala 2.12 / kafka.api.PlaintextAdminIntegrationTest.testConsumerGroups(String).quorum=zk

@guozhangwang As discussed yesterday, I will merge this PR.


Drone environment variables in bot message

Hello guys, how i use environment variables in bot message?
Example, i want to show in message by error build at what steps is fails. Drone have environment, called - DRONE_FAILED_STEPS. How i use this ENV and other ENV`S on this plugin message part?
Or maybe your know other ways to output to a message failed steps?
Thanks is advance!

Hello, @suchimauz!
Try to use template_vars:
  - name: notify
    image: appleboy/drone-telegram
    settings:
      template_vars:
        steps: ${DRONE_FAILED_STEPS}
      message: >
        Steps: {{tpl.steps}}


Camera plugin - preview after photo - change text labels

is that possible to change the label information after take a photo? After take a photo i see the photo preview with two options, OK or Retry, this labels are modifieble?

Could you provide more details on this? Which platform are you referring to?


Add environment variable section to the configuration docs

While I was exploring the repository code, I noticed that there are some environment variables configuration available that are undocumented.
Using environment variables for configuration is extremely useful, specially when running Greenmask as a Job inside a cluster.
I also would like to suggest the addition of some other environment variables that could improve ease configuration:

Storage

TYPE - chose storage type, valid values are directory or s3
BUCKET_NAME
BUCKET_REGION - recently the possibility to set the region through the AWS_REGION environment variable was added, but adding this additional variable would align for a more cohesive env var naming
PATH - for directory storage, but this could also be used as prefix when using s3 storage

Other variables for storage would also be beneficial, but I believe that these would cover the majority of the users

@joao-zanutto  I will check possibility to implement the variables you mentioned and review your merge request tomorrow.
Feel free to share your experience I will highly appreciate any feedback provided.
Thank you so much!


Rate limiting

After only a few commands, i get the "Unusable response produced by ChatGPT, maybe its unavailable."
So then i try again but from the actual browser it says i can try again in 1 hour. Is there a way to bypass this ?
I want to use this as an API for my web app so anyone on there could try it and input a command but if its getting rate limited like this its not going to work,

I guess the rate limiting is the result of Cloudflare, and it can't be bypassed by nature.
https://support.cloudflare.com/hc/en-us/articles/115001635128-Configuring-Cloudflare-Rate-Limiting
ChatGPT is $100,000 per day. Highly recommend you read this article.
https://indianexpress.com/article/technology/tech-news-technology/chatgpt-interesting-things-to-know-8334991/
All we can to do is make a proper error message like 'Two many requests in 1 hour'

i think i've seen some other chatgpt wrappers bypass cloud flare though it has to be possible. And now for reason i'm getting this message after only 1 prompt, so this is unusual.

It looks you overused the wrapper. There is a daily limit per user. One solution would be to create multiple users using multiple ips. Another is to wait for the official api or use the gpt3 api

I have this problem, but just in https://chat.openai.com/api/auth/session
If use directly in browser work fine


Failing tests

What

ProductsAPITest > post product() FAILED
java.net.ConnectException at CoroutineDebugging.kt:46
Caused by: java.net.ConnectException at RealConnection.java:249
Caused by: java.net.ConnectException at Net.java:-2

ProductsAPITest > products by city paris not found() FAILED
retrofit2.HttpException at KotlinExtensions.kt:53
ProductsAPITest > product not found() FAILED
com.google.common.truth.ComparisonFailureWithFacts at ProductsAPITest.kt:129

fixed by @g123k , dexing still fails in the CI

Dexing is indeed KO for debug builds.
But the code, as is, is OK for releases builds.
The way to fix this is to migrate to Gradle 8, which requires a lot of work (GreenDAO is deprecated and we have to rewrite everything)


update for quarkus 3.0.0 (javax/jakarta)

Because I needed a local build that works with Quarkus 3.0.0.CR1 even for native image builds, I did a fork and quick fix of he quarkiverse/quarkus-logging-json extension. I needed the io.quarkiverse.loggingjson.providers.KeyValueStructuredArgument.kv.
Please note the disabled jacoco in the pom.xml because I struggled getting it working here.
Maybe you can consider to integrate these changes.

We would be willing to commit resources to maintain this extension if that is an option.  Another alternative is we can submit a fork of this as a new logging extension. As of right now, our upgrade is at a stand-still without this and we are also using an internal dependency.

Superseded by https://github.com/quarkiverse/quarkus-logging-json/pull/234


#310 changed 'optional' suffix rendering condition for disabled=False

Description
Fixed condition for displaying optional field label suffix for disabled=True fields.  (#310 issue)

Coverage increased (+12.6%) to 73.21% when pulling 2114960bbcb81bf11398a2a7257cb315f9b57dca on bugfix/310-optional-suffix-for-enabled-not-required-fields into 6afd8e6cb41526d0e7c4fb8e008bccf94644f01a on develop.


Fix grammar in kubernetes dashboard docs

Start a new sentence after a period.

Please sign CLA #31161 (comment)

Done: sorry for the delay, I had to check with my employer as to whether the individual or corporate CLA was more appropriate.

I signed the CNCF CLA.

Thank you!
/lgtm

/assign @jlbutler


[embedded] Conditionalize assert printing to debug assert config

See https://github.com/apple/swift/pull/72817. Turns out these are more codepaths that end up calling _assertionFailure, so let's conditionalize printing (in Embedded Swift) to the debug assert config directly inside_assertionFailure.

@swift-ci please test


Reverse height

Hello! I have a problem with method
private fun getTransitionHeight(): Float {
return Math.min(getBackLayout().height.toFloat(),height - peeckHeight)
}
So, for correct work user must insert in peeckHeight height of front layout. But if I want to dropdown depending of background content height I need to insert height to global top like here:
return Math.min(getBackLayout().height.toFloat(),peeckHeight)
I think it will be better if you do a parameter to make it optional. Thanks.

peeckHeight is not the height of front layout is the height of the header of front layout it means when we droopdown we  need to keep thats header of front layout visible
translation should be "height - peeckHeight"
so i m not sure why u want it like this
return Math.min(getBackLayout().height.toFloat(),peeckHeight)

Oh, I understood the idea of this element, thanks. But I have a non-standart task - make a short menu in background layer. Several elements ang very big empty space - I think it is not beautiful. So, a variant - pull back the height of background layer menu and make foreground layer disabled. But I will tell your opinion to our designer.

maybe because ur setting the height of backlayout to "match_parent"
if its the case you should change it to "wrap_content" and i think this will solve the problem of the big empty space
and about disabling the front layout i will work on it and i will informe you about any updates

Yes, I've already done this. But also I changed height - peeckHeight to height with peeckHeight value is background menu's height. And it works as I want. The problem cannot be solved only with changing "match_parent" to "wrap_content".
Okay, I will wait for your updates, thanks a lot. And my opinion: your version of Backdrop is the best between all I found today.

you can now use version v2.0
frontlayout will be disabled when backdroplayout is in open state


suggestion of vevo [Feature Request]

What is the purpose of your issue?

[ ] Bug
[ x] Feature Request
[ ] Question
[ ] Other

Description

example
when downloading closer by the chainsmokers, if i type the space correctly, if will be downloaded with the chainsmokers as artist
if not the youtube will kick in and chainsmokerVEVO will be the artist. i suggest a feature to combine these artists together.
Log

I don't get what you're aiming at. A little more information would help.

From what I understand, if for example the YouTube artist for a video is "ChainsmokersVEVO", you want to trim the "VEVO" part when applying metadata in a situation where the track isn't found in Spotify. However, almost all artists having a VEVO channel on YouTube also have a Spotfiy page. So, I'm not sure why this would be a problem since Chainsmokers is on Spotify and so the metadata gets taken from Spotify.

@ritiek you are right, i have since figured out exactly what you said. i am closing this idea. nice program


Problem connecting to Google Drive

Got this on the popup when trying to connect to my personal email account.

Could you confirm it's not happening again?

Looks very slow to me, but not sure if we can improve this

Sono this particular issue. Closing


Move to java17 as default

This is to gather details on moving to java17 as minimum requirement and start with the implementation.
The plan is to release this in 2.0.0.
Acceptance criteria:

java17 is the minimal java version for kotlin-faker:2.0.0
java8 is supported (via own artifact? kotlin-faker-jdk8?)

(optionally java11 should also be supported in a similar fashion?)

kotlin 2.0.0 (if released by then) is the minimal kotlin version for kotlin-faker:2.0.0

backwards compatibility with 1.[789].x is unclear at this point

Some useful documentation from gradle:

https://docs.gradle.org/current/userguide/feature_variants.html
https://docs.gradle.org/current/userguide/toolchains.html

OK, I'm not really sure this makes sense for a kotlin-based library. What benefits do we get from defaulting to java17 when the primary language is kotlin? I can't see any, at least until kotlin starts declaring "minimal supported java version".
At the same time, implementing this issue would require introduction of another artifact to make the lib compatible with java8.


Refactor model training method

Refactoring to pass the filenames in to the training method rather than through the constructor.
Updated UTs for this change

Fixes #90

Current coverage is 100% (diff: 100%)

Merging #93 into master will not change coverage

@@           master   #93   diff @@
===================================
  Files           1     1
  Lines         102   103     +1
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
+ Hits          102   103     +1
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 644254d...f35e502

@Jtfinlay thanks this is great! 👍
happy #hacktoberfest! 😸


Feature Request - Free stuck unit

Reminder of the idea we talked about on discord.
Since sometimes units get stuck on deployment, or very rarely on strange terrain features during gameplay.
An ability that moves a unit a very short distance horizontally could be useful. Ideally it would be set up to only be attractive to fix glitches not to use in ordinary play.
"we can give it fairly serious penalties for use. lose all evasion, give it a big cbill cost, only allow it to be used once or twice per mission, etc. could probably limit the range vertically as well... so you can use it to get off a weird ramp on an urban map or whatever, but not teleport to the top of a building."

@CargoVroom remind me... is this resolved by the CarefulManeuvers ability, or did you want like...an actual emergency teleport ability? Only a month ago and I've completely forgotten what we talked about -_-


StartGrabbing and StopGrabbing?

I've been making great use of the StartUsing and StopUsing functions (that are part of VRTK_Interactable Object) that are used in your example script "UseRotate". I'd love to be to address Grabbing the same way but I do not see StartGrabbing or StopGrabbing in the VRTK_Interactable Object script. Is it there somewhere and I'm just missing it?
I'm really just looking for a simple way for an object with VRTK_InteractableObject attached to know when it has been grabbed so that I can trigger other things in my scene.
Thanks!

NOTE: Any issue that does not follow the below template will be immediately closed and not re-opened until the template structure is adhered to.

Precheck

Do not use the issues tracker for help or support (try VRTK Slack channel, Stack Overflow, etc.)
For proposing a new feature, please check existing open and closed issues before creating a duplicate
For bugs, do a quick search and make sure the bug has not yet been reported
Finally, be excellent to each other, and party on dudes!

Environment

Source of VRTK (Unity Asset Store or Github)
Version of VRTK (Unity Asset Store/Github release number) (Github master commit hash)
Version of Unity3D (e.g. Unity 5.4.4f1)
Hardware used (e.g. Vive/Oculus)
SDK used (e.g. OpenVR/SteamVR/Oculus Utilities)

Steps to reproduce
Attempt to recreate the issue in a VRTK example scene and provide steps to reproduce in a clear text step by step list. Include code samples, errors and stacktraces if appropriate.

Do not upload custom projects with custom code to demonstrate the issue.

Expected behavior
Briefly describe what you expect should happen
Current behavior
Briefly describe what is actually happening

https://vrtoolkit.readme.io/docs/vrtk_interactableobject#section-grabbed-1


ISSUE-907 Test Mode: Deleting a topology source node after a test sou…

…rce node is configured throws exception

remove associated test source before removing topology source
remove associated test sink before removing topology sink

This closes #907
@shahsank3t Could you verify the patch to see it resolves #907?
@arunmahadevan Please review and comment. Thanks in advance!

+1


Adopt the IIS in-process hosting model - custom web.config

An additional upgrade step when adopting the IIS in-process hosting model: If you have a custom web.config that currently contains modules="AspNetCoreModule", this needs to be changed to "AspNetCoreModuleV2".

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 46a10a5c-bacc-1bcf-a7ae-499715e1bfdd
Version Independent ID: 1585163b-b1d7-eeb8-ebc6-adfc2730f393
Content: Migrate from ASP.NET Core 2.1 to 2.2
Content Source: aspnetcore/migration/21-to-22.md
Product: aspnet-core
GitHub Login: @scottaddie
Microsoft Alias: scaddie

Great idea @edwiles, and I'll include hostingModel="InProcess", too.

May as well do the 3.0 changes for the 2.2 to 3.0 migration doc while I'm at it.

Actually that's a question - if InProcess is present in the web csproj, do we need hostingModel="inProcess" in the custom web.config?

Here's the logic ...
https://github.com/aspnet/websdk/blob/06b8237d0c3d7cd712c3f9619afef541ad5502cd/src/ProjectSystem/Targets/netstandard1.0/Microsoft.NET.Sdk.Web.ProjectSystem.targets#L24
As you can see, it's only used there, so the answer is not really. If you have a custom web.config, then you can only set the hosting model attribute on the element and you don't need the project file entry. However, I would go ahead and set it myself ... just in case later the custom web.config is removed from the project. I would want the opt-in in-process behavior if the project ever went back to a non-custom web.config setup.
In the 2.1 to 2.2 migration topic, I think it best to:

Leave the project file property info for hosting model in its current section.
Have the custom web.config remarks in another section.
Not describe it further.

We're recommending to devs to go with in-process. Therefore, it's best to have both sections go that way.
WRT 3.0 ... In-process is by-default, so we can let devs remove the project file prop if they want to. WRT a custom web.config there, I assume that they already have a good 2.2 starting app configured however they want with or without the web.config. No changes are required.


CallBacks?

Hello is there any callback for the list view ? like on long press click on the list ? thank you.

@ziadkiwan The list view is an independent part, the JcPlayer library only care about the audio files and manipulating them. The lógic of list view is for the developer responsibility.

oh the application do not take care of creating the list too ? i need to create the adapter etc... ?

@joielechong yep 😃

oh okay got it thank you! you should mention that in the readme 👍

Thanks! I'll do it right now.


Is Pipeline Parallelism same as Parameter partitioning?

Thanks for the amazing DeepSpeed! I can train/finetune GPT2 1.5B on a single 2080Ti, with a few train code change.
Your new feature Pipeline Parallelism is very promising, is it the Parameter Partitioning in ZeRO paper?
If they are not the same, what are the Pros and Cons of Pipeline Parallelism and Parameter Partitioning?

Thanks for your interest in DeepSpeed!
Pipeline parallelism is not the same thing as ZeRO's parameter partitioning, though they accomplish similar goals. Pipeline parallelism also partitions a model (and gradients, and optimizer states) among GPUs. The tradeoff is that your model needs to have sufficient depth to be partitioned (i.e., it needs to have enough layers), and forward() must follow a specific format.
Pipeline parallelism is a big topic with several algorithms such as PipeDream and GPipe. DeepSpeed uses a different algorithm that trades off a batch size for the same convergence properties as traditional data parallelism. Our pipeline tutorial covers the specific algorithm that we use in DeepSpeed today. A schedule like PipeDream should be possible as well if the schedule was implemented.
ZeRO does not include parameter partitioning yet, but once released they can even be composed. Pipeline parallelism works with ZeRO stage 1 and 2 today (optimizer and gradient partitioning). ZeRO-3 (parameter partitioning) will be more simple to use because it does not require model modification, but introduces additional communication. Pipeline parallelism on the other hand may require some model modifications but typically improves communication overheads. We've seen some large speedups with pipeline parallelism on low-bandwidth networks.

Thanks for the detailed answer, I got it now.

@ShadenSmith is there an ETA by which y'all are planning to release Stage 3? I'd love to beta-test it if y'all have it on some other branch!

@ShadenSmith is there an ETA by which y'all are planning to release Stage 3? I'd love to beta-test it if y'all have it on some other branch!


How to get native event object in button click event handler?

pane.addButton({title: 'Save'}).on('click', e => {
  // if ctrlKey is pressed
  ?
  // else
 ///
});

I found the solution:
pane.addButton({title:'Save'}).element.on('click', e => {
 //...
});

Implemented in #591. You'll be able to access the native event object via e.native from the next version.
pane.addButton({title: 'Save'}).on('click', (ev) => {
  console.log(ev.native);
});

Released 4.0.3.


EE-21448 - SDK - Add input format enum support for translate operations

added here: https://github.com/RWS/languageweaver-sdk-samples/pull/18/files


'ExprArrayNameSpace' object has no attribute 'eval'

The error happens when following the MIMIC-IV tutorial at "Data Extraction & Pre-processing" step.
PYTHONPATH="$EFGPT_PATH:$PYTHONPATH" python \
        $EFGPT_PATH/scripts/build_dataset.py \
        --config-path=$(pwd)/configs \
        --config-name=mimiciv \
        "hydra.searchpath=[$EFGPT_PATH/configs]"

Omitting {'min_los': 3, 'min_admissions': 1} from config!
Empty new events dataframe of type VISIT!
Empty new events dataframe of type ICU_STAY!
Empty new events dataframe of type PROCEDURE!
Error executing job with overrides: []
Traceback (most recent call last):
  File "/mnt/shared_home/vlialin/documents/EventStreamGPT/scripts/build_dataset.py", line 349, in main
    ESD = Dataset(config=config, input_schema=dataset_schema)
  File "/mnt/shared_home/vlialin/documents/EventStreamGPT/EventStream/data/dataset_base.py", line 552, in __init__
    self._validate_and_set_initial_properties(subjects_df, events_df, dynamic_measurements_df)
  File "/mnt/shared_home/vlialin/documents/EventStreamGPT/EventStream/data/dataset_base.py", line 580, in _validate_and_set_initial_properties
    self._agg_by_time()
  File "/mnt/shared_home/vlialin/miniconda3/envs/clinicallm/lib/python3.10/site-packages/mixins/timeable.py", line 101, in wrapper_timing
    out = fn(self, *args, **kwargs)
  File "/mnt/shared_home/vlialin/documents/EventStreamGPT/EventStream/data/dataset_polars.py", line 639, in _agg_by_time
    .arr.eval(pl.col("").cast(pl.Utf8))
AttributeError: 'ExprArrayNameSpace' object has no attribute 'eval'

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.```

Thanks @Guitaricet. Just to close the loop on this here as well, this is related to the polars version -- they updated the namespace for nested arrays in 0.18. In https://github.com/mmcdermott/EventStreamGPT/commit/7f002b5642526812efc51361eb5c83f97f97451d I've pushed a change to this to dev.

@mmcdermott this also needs to be changed in the unit tests.


Separate C++ from C settings

Just add other settings to C++
C settings (as today):
  "doxdocgen.c.commentPrefix": " * ",
  "doxdocgen.c.firstLine": "/**",
  "doxdocgen.c.lastLine":  " */",
  "doxdocgen.c.triggerSequence": "/**",

C++ settings (new):
  "doxdocgen.cpp.commentPrefix": "/// ",
  "doxdocgen.cpp.firstLine": "///",
  "doxdocgen.cpp.lastLine":  "///",
  "doxdocgen.cpp.triggerSequence": "///",

Just to be clear.
You want to have different settings for C++ and C? Or do you want to rename them?

Different settings.
C++ comments are a lot better, but in ANSI C we cannot use them.
Best regards,
Ronny Sherer
On Fri, Jul 20, 2018 at 1:01 PM Christoph Schlosser <
<EMAIL_ADDRESS>wrote:

Just to be clear.
You want to have different settings for C++ and C? Or do you want to
rename them?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/christophschlosser/doxdocgen/issues/84#issuecomment-406553356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADmAgu20JO5nGlDuM3_1JLPQ0cEP2JF2ks5uIap2gaJpZM4VXnt5
.

Okay I'm still not sure I get your problem.
This is confusing to me:

C++ comments are a lot better, but in ANSI C we cannot use them.

Could you please post a whole usecase and tell me what you mean by this?

Closing this as there is no sufficient description.


isar_generator is incompatible with multipule packages.

Steps to Reproduce
installing the following packages:

dependencies:
freezed_annotation: ^0.14.1
isar: ^0.1.0
isar_flutter: ^0.1.0

dev_dependencies:
build_runner: ^1.12.2
freezed: ^0.14.1+1
isar_generator: ^0.1.0
json_serializable: ^4.0.2

Error sample
This is the error message i get:
Because every version of isar_generator depends on freezed_annotation ^0.12.0 and tdd_null_safe depends on freezed_annotation ^0.14.1, isar_generator is forbidden.

and if  change the dependencies version of [freezed, freezed_annotation, json_serializable] to any,
i get this error message:
Because every version of isar_generator depends on glob ^1.1.0 and build_runner >=1.11.2 depends on glob ^2.0.0, isar_generator is incompatible with build_runner >=1.11.2.

and finnaly if i change build_runner version to any, i get this error message:
Because every version of isar_generator depends on dartx ^0.5.0 which depends on crypto ^2.1.0, every version of isar_generator requires crypto ^2.1.0.

And because universal_io >=2.0.0 depends on crypto ^3.0.0, isar_generator is incompatible with universal_io >=2.0.0.

i learned about this database on hive's github issues, so i wanted to give it a try, but alas i got the same errors that hive currently has, i know that almost all the generator dependent packages are having a problem fixing the compatibility issues.. so good luck on fixing it, and i wish you all the best, the data base does look promising and i can't wait to start using it.
Version

Platform: Android,  Windows.
Flutter version: 2.0.3
Isar version: 0.1.0
Isar Generator version: 0.1.0

I'm almost finished with the new version. I will publish this weekend ✌

Great, thank you all for your efforts. 🙏

New version released 💪


[ldd-img] Addition of  IOF class

Issue Type
ENHANCEMENT request.
Describe the issue identified (if applicable)
There are no available attributes to describe image IOF parameters.
The Mars2020  Mastcam-Z  team would like the addition of attributes to describe reflectance (IOF) images. These attributes could be made into a class if that is better for general use.
iof_conversion_coefficient  - IOF Conversion coefficient (float_array)
iof_conversion_coefficient_std - 1-sigma standard deviation in IOF conversion coefficient (float_array)
Describe the solution you'd like
These attributes could go just after the  <Radiometric_Calibration> class,  or where ever you feel these are best located.
PDS4 IM Version
1.16
Need-by Date
Needed for the upcoming Mars2020 data release.
Additional context
Add any other context or examples products

@katecrombie Is this need imminent?
For any new IOF can we simply add "radiance factor" as a  radiometric_type?
https://github.com/pds-data-dictionaries/ldd-img/blob/9f9bfa9c619132f9a929cece2a761e60f40eae35/src/PDS4_IMG_IngestLDD.xml#L2931
And then add these two new attributes as optional under the Radiometric_Correction class: https://github.com/pds-data-dictionaries/ldd-img/blob/9f9bfa9c619132f9a929cece2a761e60f40eae35/src/PDS4_IMG_IngestLDD.xml#L6578
But you also list them as float_array? Are they really or just a single floating-point value? Arrays again is harder to support in XML and I would need an example.

@Trent, if this is easy to implement, soon would be good.
I like the "radiance factor"  as a radiometric_type solution.
The two new IOF attributes could be implemented the same way as responsivity and responsivity_std.  (no float arrays, it would be a single floating point value per attribute)

still need better radiance factor definition but implemented. Having wired "logs" directory issue. Hopefully it will clean itself up.


[pyspark] Don't stack for non feature columns

To close https://github.com/dmlc/xgboost/issues/9016. I did some benchmark tests, this PR can bring ~1x speed up. Please see the details https://github.com/dmlc/xgboost/issues/9016#issuecomment-1521451690

Hi @trivialfis @WeichenXu123, Please help to review this PR. Thx


Basic support for binding the camera viewport

We need to support setting the camera viewport explicitly to a binding, which will update the map. This has a number of thorny issues, which I'll attempt to spell out here. I'm sure I've missed some cases, so feedback welcome.
Methods of camera manipulation
There are three basic types of camera manipulation in MapLibre today.
Group one: direct manipulation of properties
This family of properties can be manipulated directly via a single family of method overloads. They can all be manipulated either separately or together currently. I assume we could do this via a single modifier with nullable arguments.

[ ] Center
[ ] Zoom level
[ ] Direction (degrees)

Group two: visibility specification
The second family can be specified by two modifiers: one sets a visible bbox and the other specifies a set of points. For the latter, it is probably useful to expose a higher-level API (maybe even make it the default behavior as in MapKit) to automatically fit all user-added overlays, annotation, etc. (We can make a task for this later if we decide to make that).

[ ] Visible coordinate bounds
[ ] Visible coordinates (with padding)

Group three: direct camera control
You can also construct an MGLMapCamera. As far as I'm aware, this is actually currently the only way to set pitch, which is a bit funky. We might want to have the others create cameras internally but additionally expose this. Opinions welcome.
Open questions
What's the best way to signify animation parameters? Can/should we be considering making this a bit more swift-y? Stick with the classic Obj-C-style animated parameter? Make animation opt-out? Something else?
How to handle user tracking? It's currently viewed as a separate parameter, but at a higher level, "track the user" is simply another camera mode. Half-baked idea literally off the top of my head, but I think the camera state might be best modeled as a sum type. We have the explicit parameters (center coord, zoom level, direction, and pitch) as one state. Visible coords and bounds are just convenience ways to construct this state. Then there's a separate state which is "follow the user at this zoom level, direction, and pitch."
Related to the above, we will need a way of handling user interaction. The user can of course "break" programmatic tracking of any sort, and this special case will need to be modeled, maybe with read-only observability with by the parent (the tracking status is internal @State that will be dependent on user interaction).

@ Archdoog I'm starting to write up some of the architectural/design questions now on GitHub and here's the first one :) I'd love your input on this when you get a chance.

Okay, so an MVP of sorts is actually very much within reach! I've pushed an example: https://github.com/stadiamaps/maplibre-swiftui-dsl-playground/blob/main/Sources/MapLibreSwiftUI/Examples/Camera.swift.
I'm pretty happy with the interface and bindings. I've also verified that it works both ways with a modified body like this:
    var body: some View {
        MapView(styleURL: styleURL, camera: $camera)
        .task {
            print("Before camera: \(camera)")
            try! await Task.sleep(for: .seconds(3))

            camera = MapView.Camera.centerAndZoom(switzerland, 6)
            print("After camera: \(camera)")

            try! await Task.sleep(for: .seconds(2))
            print("VERY after camera: \(camera)")
        }
    }

The output is
Before camera: centerAndZoom(__C.CLLocationCoordinate2D(latitude: 46.80111099999998, longitude: 8.226666999999992), Optional(4.0))
After camera: centerAndZoom(__C.CLLocationCoordinate2D(latitude: 46.801111, longitude: 8.226667), Optional(6.0))
VERY after camera: centerAndZoom(__C.CLLocationCoordinate2D(latitude: 46.80111099999998, longitude: 8.226666999999992), Optional(6.0))

That actually brings up an interesting quick which I'm surprised by, but I'm not sure it matters now. I'd expect the camera update to only occur after the animation as implemented.
The big unknown in still if we can do better with animations, or whether we should just stick what's already in MapLibre. In any case, that isn't a decision that needs to be made urgently.

Working on my implementation of a MapCamera enum, I've landed on this question a few times:

Should the MapCamera contain automation for user location?

With the original MapView, Apple's MapKit and more, the answer is typically kind of. Those apis allow you to set a user location following mode to effectively control the map camera indirectly. When this is running, the binding would just want updates from the MapView of the MapCamera every time a location update pan finishes. When to update the binding is definitely tricky depending on the reasoning of the current behavior/mode. Furthermore, The provider of the coordinate data may ideally want to update the location every 60th of a second, every second, or once in a while. The slower the frequency, the easier it is to just let the camera and animation do its thing. The 60th of a second may require a totally different mechanism (e.g. DisplayLink), but it's worth thinking on.
Without User Location
This simpler camera option detaches the MapCamera from a location provider. Using this ideology we could see a service updating the center location constantly with a refresh rate.
enum MapCamera {

    /// Center on a coordinate with default values
    case center(CLLocationCoordinate2D)

    /// Center on a cooridinate with a specific zoom and pitch
    case center(CLLocationCoordinate2D, Zoom, Pitch)

    /// Pass a specific camera object to display
    case camera(MGLMapCamera)

    /// Fit the camera exactly to a bounding box.
    case boundingBox(BoundingBox)

    /// Fit the camera to a bounding box with padding.
    case boundingBox(BoundingBox, EdgeInsets)
}

With User Location
With user location, we now have to assume the camera can be attached to the user location with a location provider. This can be done with the MapView itself by just toggling the follow user behavior as defined in the user tracking mode: https://maplibre.org/maplibre-native/ios/api/Classes/MGLMapView.html#/c:objc(cs)MGLMapView(py)userTrackingMode. The bonus here is, we can let the location provider update the location many times on the MapView before updating the external binding value.
enum MapCamera {

    /// Center on a coordinate with default values.
    case center(CLLocationCoordinate2D)

    /// Center on a cooridinate with a specific zoom and pitch.
    case center(CLLocationCoordinate2D, Zoom, Pitch)

    /// Pass a specific camera object to display.
    case camera(MGLMapCamera)

    /// Fit the camera exactly to a bounding box.
    case boundingBox(BoundingBox)

    /// Fit the camera to a bounding box with padding.
    case boundingBox(BoundingBox, EdgeInsets)

    /// Follow the user's location with a north map orientation.
    case followUser // or followLocation

    /// Follow the user's location and orient the map to their course of travel.
    case followUserWithCourse // or followLocationWithCourse

    // etc.
}

As a note, with the LocationProvider as a common tool to manipulate centering location data, we could rename User to Location, LocationProvider or similar. By default the MapView could contain its standard platform specific UserLocationProvider, but allow customization.
Extending This
It would be easy to consider extensions to this ideology that include common use cases like MapCamera.showcase(Route), MapCamera.showcase([Route]), etc. While an enum is nice, maybe another container is ideal to allow extending custom MapCamera's that contain logic based on the foundation.
Thinking Forward
The Basics
@State var mapCamera: MapCamera = .center(.init(45.5, 45.5), 10, 45)

var body: some View {
    MapView(styleURL: styleURL,
            camera: $mapCamera)
}

Injecting a custom location provider
This could be a good way to leverage a lot of functionality in an easy to understand manner:
@State var mapCamera: MapCamera = .followLocation

var body: some View {
    MapView(
        styleURL: styleURL,
        camera: $mapCamera
    )
    .locationProvider(navigationLocationProvider)
}

Animation
As it sits now, you want the Binding for map camera to update at the end of the animation process. This is fine so long as we can manipulate the animation or frame rate to fit the use case for navigation or another custom profile. This topic needs a lot more discussion, but I would love if for navigation we could give the MapView a location provider that provided a realistic user location value every frame and the MapView could just follow it, updating the binding at the end of each window of frames. Don't treat the example below as a real idea, just trying to illustrate the idea as inspiration, implenting this likely has many flaws.
@State var mapCamera: MapCamera = .followLocation

var body: some View {
    MapView(
        styleURL: styleURL,
        camera: $mapCamera
    )
    .locationProvider(navigationLocationProvider)
    .onCameraAnimation { eventUpdate in
        switch eventUpdate.status {

        case .ended:
            mapCamera = eventUpdate.mapView.camera
        default:
            break
        }
    }
    .cameraBindingUpdate(on: .ended)
    .cameraAnimation {
        // This would likely only "buffer" external mapCamera updates. Updates from gestures within the map would have to ignore this.
        CameraAnimation(
            ...
            // Lots to brainstorm here, but how to control the animation/flow between frequent and infrequent camera updates.
        )
    }
}

Animation needs a lot more thought, but it's something to think about in this context.


Move field parsing to Observer

Is your feature request related to a problem? Please describe.
We receive a proto object from vision/simulator that describes the field. We convert it to our own Field type which is easier to use. But what if our received object contains missing information? And what if the received data is inconsistent? Filtering needs to be applied to ensure we use correct Field information, but that is not done at the moment.
Describe the solution you'd like
I suggest moving the conversion from the AI code to Observer code, as this is exactly why Observer exists. After that, Observer can apply filtering to make sure we have a proper representation of the Field.
Additional context
I suggest waiting until this PR is merged so having a reference of a Field is a bit more simple.
To send the filtered Field from Observer to AI, a new proto object that matches our way of describing a Field is probably very convenient, so I also suggest doing that. (I would be very willing to fix that part!)

@Florisheinen1 Maybe a few points of discussion before I would start fixing this:
What to do in case we have not yet received a field from vision? There's basically 2 options:

Use a 'default field' with sensible sizes (e.g. the default division A sizes for example)
Do not pass a field at all/pass a null field.

I don't have a particularly strong opinion for either as I don't know enough about the AI, but I can imagine that in some situations having a field available is crucial. It also reduces the (mental) overhead of having to check if the field is present every time.

@Florisheinen1 Your opinion on this? You can also maybe make a PR drafting the field proto type already if you feel like doing so.

In my opinion we should use the last known field or pass a null field if nothing has been sent yet. Checking whether the field is present should be done anyway as not having a field does impact our winning chances. Also we would only have to check one time per game, since we can assume that the field will not change during the game.


Reduce risk of oauth token compromise by storing tokens in $XDG_RUNTIME_DIR

Related command
az login
Is your feature request related to a problem? Please describe.
On Linux Azure CLI stores oauth tokens unencrypted on disk.  This is understandable on headless Linux because headless Linux does not provide a standardized credential store.  However, storing oauth tokens unencrypted on disk remains a security concern.  This is particularly true for Azure CLI because it gives access to a wide range of Azure services.
What can be done ?
One simple improvement would be to store oauth tokens under directory $XDG_RUNTIME_DIR when this exists.
Many Linux distributions use systemd and create a user session when the user logs in or starts an SSH session.  When the user session is first started the system creates a tmpfs runtime filesystem and sets $XDG_RUNTIME_DIR to point to it.  When the user's last session ends the system deletes the user's runtime filesystem.  This is observed on both Ubuntu and Mariner (with systemd).
Storing oauth tokens under $XDG_RUNTIME_DIR would have two immediate benefits:

The runtime filesystem uses tmpfs so oauth tokens stored in $XDG_RUNTIME_DIR are not stored on disk.
The runtime filesystem is deleted when the user sessions terminate, so oauth tokens stored in $XDG_RUNTIME_DIR are deleted at the end of the user session.

Side effects of the proposed change:

Users who exit an SSH session and start a new SSH session need to re-authenticate.
Processes left running after the SSH session ends (e.g. using nohup or tmux) lose access to oauth tokens.

If these side effects are unacceptable we could allow users to override this behavior and store oauth tokens under $HOME rather than $XDG_RUNTIME_DIR (at the cost of persistent oauth tokens on disk).  For example, we use $AZURE_RUNTIME_DIR alongside the existing $AZURE_CONFIG_DIR to control where runtime information such as oauth tokens are stored.
Describe the solution you'd like
When storing unencrypted oauth tokens on Linux, check whether $XDG_RUNTIME_DIR is set and refers to a valid directory, and if so store oauth tokens under $XDG_RUNTIME_DIR rather than $HOME.
See also git-credential-manager issue 1595.  Note that Azure CLI gives access to git repositories in Azure DevOps (via az account get-access-token) so if Azure CLI is weaker than Git Credential Manager then it bypasses and undermines the security that Git Credential Manager provides.
Describe alternatives you've considered
Azure CLI could go further and secure oauth tokens using Gnome Keyring when available (as Git Credential Manager does).  However Gnome Keyring is really intended for use in Linux desktop, and headless Linux is used much more widely than Linux desktop.  Using $XDG_RUNTIME_DIR would improve both cases and should be relatively easy.  Using Gnome Keyring in the desktop case could be added later.
Additional context
None.

Thank you for opening this issue, we will look into it.


Add packagegroup-gdp-rvi to genivi-dev-platform image

Group rvi components into a 'rvi' packagegroup, and include this in the default GDP image. This approach will allow new components from rvi to be added once to this packagegroup. Including @leon-anavi as he brought rvi sota/core into GDP

@chbae do you have any preference here?

@tom--pollard
Why don't you change to commit message?
Others are fine to me.
Add packagegroup-gdp-rvi to genivi-dev-platform image
[GDP-159] meta-rvi yocto layer merging

@chbae I'm not sure what your point is with 3. ? And sure about the jira ticket inclusion, it could go in the body of the commit, however this is not really an issue

@tom--pollard
You are right. number 3 is just my recommendation because we didn't decide commit message rule. It's up to you. :)

Thanks for the feedback as always @chbae :)


What should we have in git repository

Just wanted to know what should / should not be inside our git repositories.
If we have cloned whole repo does the whole repo with both example clocks, original README.md, flutter_clock_helper directory have to be present in our own repo?

The answer is in the Getting Started guide on the contest page under Step 5.

Correct. See 5d:
"In your /flutter_clock folder, zip these two folders:

flutter_clock_helper (unedited)
_clock (your clock)"

To clarify, your git repo can have whatever you want in it. The zip you submit should have the minimum specified in the Getting Started guide.