Launch licensed V2

In the V2 branch there's been quite a bit of cleanup, refactoring and new or changed functionality.
Changes made in v2 branch

sources now have a base class, giving a more definitive structure for ease in developing new sources
the inheritance between the Dependency and License classes is broken.  Dependency now inherits from Licensee::Projects::FSProject and contains a license
the License class, which represents the dependency data that gets serialized/deserialized on disk, has been renamed to DependencyRecord.
cached records are now stored entirely in YAML as with a .dep.yml extension
dependencies now have a number of required fields, denoted in the constructor by keyword arguments
a new reporting infrastructure has been added to provide a way to shape licensed output differently for different scenarios.  direct reporting to the UI from anywhere in the code is removed

To do

[x] gracefully catch and handle Licensed::Shell::Error from reporters.  see if it's possible to continue execution of licensed when finding dependency data fails
[x] Each command follows the same pattern at this point.  Investigate whether it makes sense to define a base class for the pattern which the individual sources can override.
[x] Create migrator for v1 -> v2 configuration and license files
[x] prepare for v2 launch - update version, put notification in readme

released!


Regression in 7.4 from 7.3.3

Expected Behavior
When using com.github.ben-manes.versions plugin on a project with kotlin dependencies, the dependency versions should resolve correctly.
Current Behavior
The dependencies fail to determine the correct version. See https://github.com/ben-manes/gradle-versions-plugin/issues/471#issuecomment-1058830284
Context
Stopped working 7.4, was working in 7.3.3.
This is impacting the ability to generate accurate dependency version reports.
Steps to Reproduce
Sample gradle.build:
plugins {
  id 'com.github.ben-manes.versions' version '0.42.0'
  id 'java-library'
}

repositories {
  mavenCentral()
}

dependencies {
  api 'org.jetbrains.kotlin:kotlin-script-runtime:1.1.0'
}

Your Environment
Tested in Window 11, and in debian based CI container. Using gradle wrapper. JDK 17.

This is a consequence of the addition of extra consumable configurations like mainSourceElements and testResultsElementsForTest which are designed to be consumed leniently only as the requested variant may not always exist, especially for published libraries.
And combined with the fact that the versions plugin attempts to resolve them directly is what causes the issue. These configurations are explicitly marked as canBeResolved=false and so should not be resolved that way.

We believe this issue is no longer relevant. Please file a new issue if necessary.


home-manager: unstable-2024-04-23 -> 0-unstable-2024-04-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for home-manager is: A Nix-based user environment configurator
meta.homepage for home-manager is: https://nix-community.github.io/home-manager/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-04-29 in filename of file in /nix/store/hsgm5yfw44jizjv1fbkrk9svgw6pc34r-home-manager-0-unstable-2024-04-29

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

home-manager

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hsgm5yfw44jizjv1fbkrk9svgw6pc34r-home-manager-0-unstable-2024-04-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A home-manager https://github.com/r-ryantm/nixpkgs/archive/5ccd11ee4faa6827edeeb64ce1170fc657d443ac.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5ccd11ee4faa6827edeeb64ce1170fc657d443ac#home-manager

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hsgm5yfw44jizjv1fbkrk9svgw6pc34r-home-manager-0-unstable-2024-04-29
ls -la /nix/store/hsgm5yfw44jizjv1fbkrk9svgw6pc34r-home-manager-0-unstable-2024-04-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

home-manager

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


LLM policies UI schema

What does this PR do?

Adds UI Schema for LLM policies
Type of change

[x] New feature (non-breaking change which adds functionality)

How should this be tested?

[ ] Existing unit tests

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code and corrected any misspellings
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@pi1814 should remove heroicons from package.json


Dead code elimination doest removes throw after return.

Consider this code.
function a() {
    return true;
    throw Error('Not called!');
}

throw can be safely removed, but it isn't. Configuration default (compilation_level: 'SIMPLE').
BTW, throw after throw also not removed
function a() {
    return 1;
    throw Error('Not called 1');
    throw Error('Not called 2');
}

Compiler leaves both throws in code in that case.
Version: v20170124
Built on: 2017-01-27 11:44

If you're interested in sending a PR, this is the relevant file: https://github.com/google/closure-compiler/blob/master/src/com/google/javascript/jscomp/UnreachableCodeElimination.java


Add outline to all child Renderers from where it's applied

First of all - thanks for the great library.
Almost every time I've used this library I've found myself intuitively wanting to apply the Outline component to a parent object and have it apply automatically to all children. Usually I have one gameobject where I conceptually turn on/off the outline and expect everything within to be outlined, and going through turning it on/off for each renderer is a real hassle.
I would be interested to hear your opinion on that and have attached the code for how I prefer to use this effect. There are some issues with this PR, but I wanted to start the discussion about whether this was worthwhile or if I've missed something before I put the work into polishing this.
Outstanding issues with this PR:

Breaks back compatibility - might want to default to the old behaviour and have this as an option
Wasn't sure what was going on with the skinnedmeshrenderer etc, will need to fix that back up for this to be a viable PR

Just noticed a bug - if the list of children changes after the fact then they won't get highlighted. I've fixed it locally, if you're interested in this as a feature, I'll update the PR

Thank you for the contribution, and sure if you could upload the fix that would be great!


[DNM] test new open ffmast fix

@ijpulidos do you remember which test(s) we disabled because of this bug?

Yes, I'll make the changes in this branch/PR such that we run the tests that were failing with Openmm8. Thanks!

Do we want to merge this in so we can keep these tests running? Part of me is thinking that it could be good to keep these tests running, even if it is using an unreleased beta of the openeye-toolkit.

I think it could be worth it to have this in a separate flow (yet another one haha). Is that a reasonable way to do it?

We could add it to the matrix (but just do it for one python version and on linux). I am trying to think of the risks of just keeping it as is.

I don't see any immediate risks with this. I agree with adding it to the matrix (single python+linux).


New Contribution

Contributor: [contributor information - Optional]
SSH Public key: [contributor SSH public key (if you don't have one, submit the issue to receive instructions)"- Required]
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC3nBFyITuqI+3INjcAFfQz/tczz97h5VRWh0lLTlxAU


Refactored the site footer

There are no visual change for the footer, I've just extracted it into a separate component and removed margin top from it. Because of the absence of margin, I needed to add this margin on all pages so that pages do not glue to the footer.
This PR is more of a preparation for a footer redesign PR. Here is how it looks with this PR:

I also removed special thanks to Tighten, but I get put it back if you want. I just think that instead of listing all contributors in the footer, we can make a separate section on home page and fetch them from github, and show them like in small bubbles or something. But that's a discussion for a different issue.

Yeah I agree, we need a contributors page :) Made an issue for it: #168
I'll try to work on this tomorrow or the day after. Thanks for this PR as well!


Reloading default HighThroughputExecutor after parsl.clear() results in KeyError: 'block_id' exception

Describe the bug
Thanks for the great work on Parsl - it's an awesome tool! I noticed when attempting to load a HighThroughputExecutor configuration after using parsl.clear() an exception occurs which states: KeyError: 'block_id'. This doesn't seem to happen when using ThreadPoolExecutor. I'm unsure if this is expected behavior so I wanted to raise a bug just in case it helps diagnose or address this issue.
To Reproduce
Run the following Python snippet:
import parsl
from parsl.config import Config
from parsl.executors import HighThroughputExecutor

local_htex = Config(
    executors=[HighThroughputExecutor()],
)
parsl.load(local_htex)
parsl.clear()
parsl.load(local_htex)

Expected behavior
I'd expect something like what is witnessed with the ThreadPoolExecutor from the following example. If this isn't possible or is unreasonable to expect, I'd expect documentation or an upfront message from the logs about workarounds.
import parsl
from parsl.config import Config
from parsl.executors import ThreadPoolExecutor

local_threaded = Config(
    executors=[ThreadPoolExecutor()],
)
parsl.load(local_threaded)
parsl.clear()
parsl.load(local_threaded)

Environment

OS: MacOS
Python: 3.9
Parsl: 2023.08.21

Distributed Environment

Where are you running the Parsl script from ? Laptop/Workstation
Where do you need the workers to run ? Same as Parsl script

one thing in your example that sticks out to me is that you can't use the same Config object twice.
In the case of the thread pool executor, this probably doesn't matter, but it's likely to be more of a problem with htex.
There's a style for re-loading "the same" config that is used in (for example) the test suite and some applications that I work on that that looks something like this:
def fresh_config():
    return Config(executors=[HighThroughputExecutor()])

parsl.load(fresh_config())
parsl.clear()
parsl.load(fresh_config())

Probably we should make this more enforced - it wasn't part of the initial design of how Config was meant to work, but it's turned out since then that's a property of Config objects (and the subobjects contained inside a Config).
Can you try something like the above and see how things go?

I see in your comment on the cytotable issue https://github.com/cytomining/CytoTable/issues/90#issuecomment-1688981416 that you have that sort of behaviour as a recommended change - for a user to generate a new for loop.
Either that, or (I'm not sure how your code is organised for this) make it so a DFK can be initialised outside of the loop and not reloaded in each iteration in that loop.
I've found it a bit easier to understand why things work that way by thinking of a Config not as "here is our configuration file style specification", but "here is a bundle of the actual instantiated components that will be started and terminated by parsl.load()".

so if you want to say "we have a DFK loaded right now, and someone just gave me a config object ... is it the same config object? and if not, do a parsl shutdown/restart with the new config" then I would say you won't be able to compare any better than simple python object identity, using the is operator.
For the example in CytoTable issue 90
for plate_folder in sqlite_dir.iterdir():
    output_path = pathlib.Path(f"{output_dir}/{plate_folder.stem}_converted.parquet")
    # merge single cells and output as parquet file
    convert(
        source_path=str(plate_folder),
        dest_path=str(output_path),
        dest_datatype=dest_datatype,
        metadata=["image"],
        compartments=["nuclei"],
        identifying_columns=["ImageNumber"],
        joins=preset_join,
        parsl_config=Config(
            executors=[HighThroughputExecutor()],
        ),
        chunk_size=10000,
    )

probably for that to work, the user should create one Config object outside of the for loop and put it in a variable and pass that variable as parsl_config=my_single_config, if they want to use one single config for all of the parsl.
so then the cytotable code can compare the parsl_config just passed in with the config object of the currently active parsl and switch configs if the user has supplied a new one on a subsequent call.
If you avoid shutting down and restarting parsl each time, I think you'll also get some speedup from not paying the startup and shutdown costs of parsl for each loop iteration - depending on circumstances that might be significant, or might not.
However, this style feels a bit weird to me and I'd kinda encourage you to think about if you can also initialise parsl outside such a loop - i guess mostly it depends on how much you expect your users to be changing configs as a loop progresses.

Many thanks @benclifford for the recommendations here! I'll move forward with using Parsl as you described.


MSID: 87930 Version: 1 DOI: 2<IP_ADDRESS>1418

"msas": "Cell Biology", "Physics of Living Systems"
"msid": "87930"
"preprintDoi": "10.1101/2<IP_ADDRESS>1418"
"Reviewed Preprint posted": "2023-07-04"
"Sent for peer review": "2023-04-17"
"Posted to bioRxiv": "2023-03-20" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1418v2")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87930)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87930/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: https://github.com/elifesciences/enhanced-preprints-data/pull/116
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1418)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/87930/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87930)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87930

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87930

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87930/v1/87930-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87930)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Author emails need fixing

Fix in https://github.com/elifesciences/enhanced-preprints-biorxiv-xslt/pull/54


References wrong run with choices parameters

Hi, maybe I am doing something wrong but in my settings it is referencing the wrong run when running test on some trained models with several choices.
In my guild.yml I have some flags like below for train and test:
flags:
  flag1:
    choices:["a", "b"]
  flag2:
    choices: ["x", "y"]

I run train with guild run foo:train flag1="[a, b]" flag2="[x, y]" and it will correctly start 4 runs (one for each combination). But when I run test with guild run foo:test flag1="[a, b]" flag2="[x, y]" it references always the last train run for each combination I want to test.
I am running guild version: guild 0.7.0.post1
Thanks for guild.ai and your help!

Thanks a lot for your fast response. I have created a new operation but it cannot resolve the required operation from the train step.
prepare:
  main: guild.pass
train:
  main: guild.pass
  requires:
    - operation: prepare
  flags:
    a: null
    b: null
test:
  main: guild.pass
  requires:
    - operation: prepare
    - operation: train
  flags:
    a: null
    b: null
train-test:
  # tried also without requires
  requires:
    - operation: prepare
  flags:
    a: null
    b: null
  steps:
    - train a=${a} b=${b}
    - test a=${a} b=${b}

Running foo:prepare runs fine
Running foo:train a=1 b=3 runs fine
Running foo:train-test a=1 b=3 complains it cannot find required resource prepare
Full message:
You are about to run foo:train-test
  a: 1
  prepare: 5240ad11686e4e6783ca4313abaad95c
  b: 3
Continue? (Y/n)
Resolving prepare dependency
Using run 5240ad11686e4e6783ca4313abaad95c for prepare resource
INFO: [guild] running train: foo:train a=1 b=3
WARNING: cannot find a suitable run for required resource 'prepare'
Resolving prepare dependency
guild: run failed because a dependency was not met: could not resolve 'operation:prepare' in prepare resource: no suitable run for prepare

It finds the prepare run but somehow it is lost when it starts train.

Include isolate-runs: no as an attribute for test-train. By default Guild limits run resolution for a pipeline to only runs generate by that pipeline. You can relax this with isolate-runs.

Thanks a lot that solved the issue for me!


Fix barrows reward percentage calculation

rewardPercent incorporate Barrows brother's increase in max points. percentage format to 1 decimal place. Now with barrows kills, rewardPercent displays true percentage.
Fixes #12009

This is fixed in 807a22172f.


meta/redis: support redis connection pool config to avoid connection …

…explosion

Codecov Report
Patch coverage has no change and project coverage change: -31.64 :warning:

Comparison is base (83258be) 56.11% compared to head (b2bde74) 24.48%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #3584       +/-   ##
===========================================
- Coverage   56.11%   24.48%   -31.64%
===========================================
  Files         149       24      -125
  Lines       36994    14398    -22596
===========================================
- Hits        20760     3525    -17235
+ Misses      13955    10489     -3466
+ Partials     2279      384     -1895

Impacted Files
Coverage Δ

pkg/meta/config.go
10.41% <ø> (-38.20%)
:arrow_down:

pkg/meta/redis.go
0.11% <0.00%> (-66.01%)
:arrow_down:

... and 144 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

y, you are right. I will close pr and request.


Make sure we rewind streams

Guzzle and socket client rewinds streams. We should as well.
See discussion: https://github.com/php-http/message/pull/72

Thank you for merging.


Hybrid Preferred/Manual OR Getting stuck on picking the last Mission

Occasionally the Auto Grinding will get stuck on repeating the last mission, this most often occurs when it is the first time I am doing the mission likely because of the new Previous on the banner.
But it also happens on other occasions.
If I turn it off and on again the problem resolves itself, this is more than fine the vast majority of days, but during Half Offs/Lotteries/Appling it becomes a problem as I leave for 25 minutes come back and find it only did one mission.
If it could automatically turn off after each mission, I could set up another Macro to turn it back on afterwards.  Manual/First isn't an option as it's getting stuck picking the mission, not the Support List which is never a problem.
I'd vastly prefer to keep preferred as well as having it always picking MLB Support CE's is extremely useful.
Where in the code would I look to change to make it auto turn off after each mission?

I myself using first would also stuck due to slow emulator/slow android. (We use flat fixed wait() for now)
Unfortunately we don't have a proper logging function for now, so anything wait() too short could be THE problem.
3 main loops: https://github.com/29988122/Fate-Grand-Order_Lua/blob/eee2f96ad4c58c42446f189f66b1f7c9e61e17c8/regular.lua#L222
It could be in https://github.com/29988122/Fate-Grand-Order_Lua/blob/eee2f96ad4c58c42446f189f66b1f7c9e61e17c8/regular.lua#L76
or in https://github.com/29988122/Fate-Grand-Order_Lua/blob/eee2f96ad4c58c42446f189f66b1f7c9e61e17c8/regular.lua#L101
or in https://github.com/29988122/Fate-Grand-Order_Lua/blob/master/modules/battle.lua

For the time being, I can only recommend you to try to increase some of the wait() in those codes.
Ankulua itself cannot be trigger restart within the code.

Sorry for the delay I didn't notice the notification, I'll try modifying the numbers and see what fixes it.

I tried 82 to see if that would change anything by changing it from 1.5 to 100 but there wasn't any change unfortunately.

@Rajvir8 There has been a change that should have fixed this issue for you now! Please post here whether or not it is still causing you issues!
For reference, the change is that we added Support menu as a validator/actor, thus if it is in the Support menu, it will follow the script as appropriate for the Support menu, rather than wait a set amount of time before trying to do it.

Thanks for your hard work guys, I've updated to the newest version and will try it out, I can't be sure if it immediately fixed the problem as it only occurred sometimes.  But if it goes a week or so without the issue popping up again I'll make sure to mention that it's fully fixed.

@Rajvir8 There was an issue with the latest version regarding Support selection where it would crash. I just implemented a fix that I hope solves the issue, so please try the most recent one.

@TryBane I noticed that it failed the moment I put it in Preferred mode and swapped back to my Older Version while trying to figure out the issue.
Glad to hear you fixed the crashing issue and I've reupdated to the newest version and tried it out, the preferred mode is currently working again and everything seems like it's working fine in the newest version at the moment.


package github.com/micro/go-micro/v2: cannot find package "github.com/micro/go-micro/v2"

go get github.com/micro/go-micro/v2
package github.com/micro/go-micro/v2: cannot find package "github.com/micro/go-micro/v2" in any of:
/usr/local/go/src/github.com/micro/go-micro/v2 (from $GOROOT)
/Users/tomey/go/src/github.com/micro/go-micro/v2 (from $GOPATH)
Why can't I download this module?

you need to use go 1.14 or enable go modules


cargo backend issues when trying to update a package

Have some "cargo:<package_name>": "latest" in my config. When trying to mise upgrade they will fail like this:
mise Error getting latest version for cargo:<package>: cargo is not installed. Please install it in order to install <package>
obs.I have rust: "latest" in my config
edit: just noticed it is actually happening even on install... maybe some regression?

This looks similar to #1999 and #2000 where dependencies are not (yet) on the PATH. I assume you don't have shims on the path either? My guess is that it would work with shims enabled but not yet without.

I'm having a similar issue with the recently released version:
~ $ eval "$(~/.local/bin/mise activate zsh)"

mise failed to resolve version of cargo:fd-find from ~/.config/mise/config.toml: cargo is not installed. Please install it in order to install fd-find
mise failed to resolve version of cargo:starship from ~/.config/mise/config.toml: cargo is not installed. Please install it in order to install starship
mise failed to resolve version of cargo:eza from ~/.config/mise/config.toml: cargo is not installed. Please install it in order to install eza
~ $ mise --version
2024.5.5 linux-x64 (7e8dab5 2024-05-12)


feat(pod): add default network policy

Kubernetes has functionality to set the default behavior of network policy to disable all egress and ingress connections of pods. Updating our default behavior in this PR.
Resolves https://github.com/cdk8s-team/cdk8s-plus/issues/891

Question
I was initially trying to do this with the help of Namespaces. But I see we do not create this resource explicitly in our workflow and just use the string instead. Having the default network policy initialized when a namespace was created would help to have this policy work for each pod within that namespace.
The problem with doing this currently is,

If we have multiple resources(like deployment, job, etc) using the same name for the namespace. Then if we add logic to create a namespace in each of these resources, it would duplicate namespace in the manifest, due to multiple instances of it. I am not sure if there is a single place where the other resources can keep track of an already created namespace.
I did not find any place where we can create a default network policy for default namespace.

The solution I could think of was to create a Namespace instance and pass it to the resources instead of the string in metadata. Let me know what you think?

FYI there's now a v25 branch, I'd consider changing the target to v25 and adding the backport-to-k8s-24/main label.

💚 All backports created successfully

Status
Branch
Result

✅
k8s-22/main

✅
k8s-23/main

✅
k8s-24/main

Questions ?
Please refer to the Backport tool documentation


Remove pixiden icons; switch to font-awesome that we've already imported

reduces our dependencies on dead code, and reduces our use of bad import patterns. Also reduces our bundled file-size by about 25%, which is pretty neat.
TODO: everything in the issue desc, #165

closing since we're deprecating this frontend anyways


Using the flatten method in the BFF class, preserving area.

Hi,
How is the following method:
    // computes automatic flattening with minimal area distortion
    //    -boundaryData stores either the target angles at boundary vertices (if
    //     givenScaleFactors is false) -OR- the target scale factors (if givenScaleFactors
    //     is true)
    // (resulting flattening is stored in Corner::uv for each corner of this->mesh)
    void flatten(DenseMatrix& boundaryData, bool givenScaleFactors);

The kind of flattening I'm looking for is the one that reduces area distorsion. So I would load for example an .obj file, store it into a Mesh data structure (the one provided by your tool which is an HalfEdge data structure), later instantiate an BFF object. Now I'm stuck in figuring out how to use the flatten method, can you please guide me through it maybe with some pseudocode?
Regards

Yes, you should call the flatten with boundaryData initialized to 0 and givenScaleFactors set to true once you've initialized a BFF object. That should give you a map with minimal area distortion.

I suppose, but I might be wrong, the size of boundaryData would be num_vertices*num_vertices. Is it correct?

boundaryData is a vector of size #(boundary vertices). Here's an example of how to initialize boundaryData:
https://github.com/GeometryCollective/boundary-first-flattening/blob/23d8448a817f5175ebffd79f233076444b3a8d5e/viewer/src/Viewer.cpp#L1455

Thank you, very last question. After the flattening, where will the result be stored?

No worries, feel free to ask more questions :). The flattening is stored here:
https://github.com/GeometryCollective/boundary-first-flattening/blob/23d8448a817f5175ebffd79f233076444b3a8d5e/mesh/include/Corner.h#L14

Hi I'm trying to set up a simple flattening, for the moment I have this main
#include <Bff.h>
#include <MeshIO.h>

int main(int argc, char** argv) {

	std::ifstream ifs("./test_mesh.obj");
	std::stringstream ss_content;
	std::string content;
	std::istringstream iss_content;

	if(ifs) {
		std::cout << "Reading file!" << std::endl;
		ss_content << ifs.rdbuf();
		content = ss_content.str();
		iss_content = std::istringstream(content);
	}

	ifs.close();

	Mesh test_mesh;
	MeshIO::read(iss_content,test_mesh);

	return 0;

}```

How can I easily extract the boundary of the mesh and initialize properly a BFF object? (mainly how to get the boundary, since you've already explained the other bit).

Thank you

Hi, Is the following snippet correct to create a BFF object? For some reason after the I get a segmentation fault when I try to instantiate one object.
#include <Bff.h>
#include <MeshIO.h>

int main(int argc, char** argv) {

	std::ifstream ifs("./test_mesh.obj");
	std::stringstream ss_content;
	std::string content;
	std::istringstream iss_content;

	if(ifs) {
		std::cout << "Reading file!" << std::endl;
		ss_content << ifs.rdbuf();
		content = ss_content.str();
		iss_content = std::istringstream(content);
	}

	ifs.close();

	std::cout << "Mesh read!" << std::endl;

	Mesh test_mesh;

	std::cout << "Object mesh created" << std::endl;

	MeshIO::read(iss_content,test_mesh);

	std::cout << "Content obj used to initialize the mesh" << std::endl;

	BFF flattening_module = BFF(test_mesh);

	return 0;

}

I'm not quite sure. Try initializing the BFF object like "BFF flattening_module(test_mesh)" though I'm not sure if it'll solve the problem.

Nope, that does not work. Is there any way I can check if the loaded mesh is valid?

Closed surfaces (such as a cube) must be cut before flattening them - the BFF class expects a surface with boundary as input. Take a look at the Cutter & Viewer classes to cut through closed surfaces.

Ok, I've sorted out for now (basically at some points some of my wrappers are used hence it crashed, of course).
Out of curiosity what exactly are the boundary conditions you suggested? i.e. what do they represent?

They represent "no scaling" along the boundary: the length of each piece of the flattened boundary curve will be the same as the original boundary curve.  This condition in turn implies that the scale distortion over the interior domain is as small as it possibly could be.  So, it provides a good default choice for flattening: zero angle distortion, and minimal area distortion.


Documentation for scPredict states wrong newData format?

Hi,
I was implementing scPred in a shiny app today and was going over the documentation for the scPredict function. It states there:
newData | A matrix object with cells as rows and genes (loci) as columns
But it actually takes the inverse, cells as columns and genes as rows. This is also how it is shown in your tutorial, the train and test data are both in the format: columns = cells, rows = genes.
I just wanted to make sure that I have this correct and it might be worth updating the manual for scPredict to avoid confusion!
Thanks again for a very nice package!

Hi @FloWuenne, thank you so much for reporting this issue!
This has been solved in commit e3e8eb3.


repositories have disappeared

I was briefly able to make portus work. But after a couple of days, the repositories from the docker registry have disappeared. Portus refuses to list any repos in the registry.
docker login refuses to authenticate. Most of the time, I get this message:
Error response from daemon: no successful auth challenge for https://my.registry:5000/v2/ - errors: [token auth attempt to https://my.registry.com:5000/v2/ realm "https://portus.mydomain.com/v2/token" failed with status: 401 Unauthorized]
Occasionally I get the correct portus url:
Error response from daemon: no successful auth challenge for https://my.registry:5000/v2/ - errors: [token auth attempt for registry https://my.registry:5000/v2/: https://portus.mydomain.com/v2/token?account=XXX&service=my.registry%3A5000 request failed with status: 401 Unauthorized]
It should be noted that this url works when opened in a browser: I get to authenticate and can get a token.
The registry has not been changed since last time portus worked, except for being restarted.
The only change I made is on the portus server, when I ran "zypper update".

The only change I made is on the portus server, when I ran "zypper update"

It has happened to me sometimes on openSUSE that when I update with zypper, then the config for the registry gets replaced by the default one. Maybe this is your case ?

Did anyone find any more detail on this?  I am seeing the same issue, have not yet found the culprit.

@mstad could you tell me which versions of each program are you using ? (docker, distribution, Portus, etc). What kind of setup are you using ? Could you paste the logs whenever that happens ? It would be better if you have the log_level set to debug (see how to do that in the final section of this)
I'm asking all these questions because I'm not able to reproduce this so I'm basically blind when trying to fix this issue.

Closing since no further information was given. Please re-open with more details if you can still reproduce this on latest master. Thanks for reporting 👍


fix: UI bugs in provisioning

Description
Various fixes for UI bugs in provisioning
Task Item
fixes #6887 : alias link added and Link on click fixed with blank target
fixes #6888 : Fixed scrolling in provisioning modal to only scroll on detail view as opposed to whole modal
fixes #6789 : increased size of publish confirm modal to support larger comment text field
fixes #6886 : Updating copy and back button in config resource modal
fixes #6889: Updating copy and adding button in dialog footer for import existing resource modal
fixes #7132: string standardization
fixes #7133: disable modal exit while luis and qna are in mid provisioning
fixes #7126: remove semi colen in luis modal

Coverage decreased (-6.0e-05%) to 50.527% when pulling a2ac7e5c2426295736ae67357a221dadb83c6aec on pavolum/bugBashFixes into 8095853c6567de9473e3f136ee818d64ee2a651f on main.


Update binaries/ ARM support

This PR updates most TkDnD binaries from 2.9.4, pulling them from the TkDnD release. ARM binaries were pulled from tkinterdnd2-universal. (tkinterdnd2-universal is now defunct but the ARM binaries were built on TkDnD 2.9.3. I have not found a means to build them myself, and they are not normally compiled by the TkDnD maintainer.)
Added Win-x86 support, because I have seen this requested elsewhere (albeit from 2022) and because the TkDnD maintainer builds them.
Added ChangeLog.
Added support for additional architectures in other files.

Merging branch.
No significant logic was changed. Changes included known working changes from other repositories and is consistent with the logic of the original.


Documentation updates for training

realted to #463
Description:
Go over CUQIpy documentation and make light updates to help improve the documentation (e.g. fixes of typos, equations not rendered correctly) and identify larger documentation update tasks that are necessary
Definition of done:

[ ] Light update (as described above) is done, reviewed, and merged
[ ] Bigger and necessary documentation update tasks are identified and corresponding issues are created and assigned
[ ] The possibility of fixing errors related to documentation that appear when CUQIpy is installed on a Windows machine is investigated (@chaozg reported this issue).
[x] #488
[x] Add experimental mcmc to main API page

Note:

Hi @jakobsj , the DoDs are ready for your review 😄

@chaozg looks good, maybe with the addition in item no 2 that new issues created are linked from this issue.

Thanks @jakobsj , just updated item 2 according to your suggestion to "...corresponding issues are created, assigned and linked from this issue."


[$250] BUG: When a new message arrives while drafting a message in the compose field, field gets cleared

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open ND and login as account A
Start composing a message to any user Account B
Send a message from the account B

Expected Result:
User should continue typing the message in the compose field
Actual Result:
Compose field gets cleared
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.2.16-4
Reproducible in staging?: Need reproduction
Reproducible in production?: Need reproduction
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/196316973-f79ec345-80f2-4eea-be97-05137a35e57a.mp4
Expensify/Expensify Issue URL:
Issue reported by: @conorpendergrast
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1665165533707169
View all open jobs on GitHub

Upwork job is here

Going OOO next week so re-assigning

Waiting for proposals!

Can't seem to reproduce this, @Justicea83 can you give it one more try?

I can no longer reproduce this on my version of main, I vote we close this and see if it's reported again.

Cool, agreed, closing.


Create file _posts/0000-01-02-ChristainBedford.md

Experimenting with first commit

Merge change to line 5 "Textism!"


Breakpoint: trigger classification store only

Type of change: Functional relaxation.
Explanation:
It seems cleaner and simpler to consider CMOs as Stores for both Fence and Breakpoint matching.

Incorporated the intent of this pull request (hopefully...) into the draft spec #34
Though I did modify this somewhat....

Ahh, I recognize those old familiar keywords IMPLEMENTATION DEFINED.  :)
I realize that I myself have asked for IMPLEMENTATION DEFINED allowances to reduce the scope of what hardware supports, so I'll grant this here, because I assume you also have a specific implementation that you're trying to fit this onto.
But, I caution that debuggers should not rely on this behavior, and I wonder whether it's worth the additional complexity for them to support this varying hardware behavior.  It's not a big deal here, but a minor additional option multiplied by a long-lived and widely-used architecture, (as we hope RISC-V will be) results in a potentially meaningful software complexity cost.
I'm not aware of any ISAs that match cache ops as loads, nor implementations that send them down the load pipe, so I guess... why?

I'm open to dropping the load condition for management ops. I had added it at one point, because someone requested it, but why is just a faded memory now.
Let's see if we get any feedback one way or another....

Note that I punted final description of the trigger behavior to the debug architecture, but I retained "recommendations" for what the debug spec should define.
I did remove the imp-def statement allowing management ops to be handled as loads.


Update Acorn config for 1.4.1

Might as well include updates made post-1.4.0 installation to facilitate Acorn installation.

After this, we only need the bufr version update in spack-stack and then we are done with 1.4.1 I think.

Well, I accidentally pushed the bufr update to the same branch, so, I'm just gonna include it in this PR...

Can you also update it in https://github.com/JCSDA/spack-stack/blob/release/1.4.1/configs/containers/README.md (two places in that file) after the CI tests passed, please? No need to rerun CI again for README changes. Thanks!

Yep no problem. Should 1.4.0 go to 1.4.1 as well?


TLDex does not appear to respect block list

In the holodex TL chat pane, I have some usernames that are set to be blocked but they still appear in the translation pane because it also picks up verified accounts (that aren't translations either, just chat comments). I don't want to block all of the verified messages obviously, just ones from specific accounts.

Seems like loading from history was not filtering blocked accounts, but new messages were always blocked. If you were seeing blocked accounts show up on new messages, then we should re open this issue.

Yes you're correct then, it was 'loading from history' that wasnt respecting it as far as I can see.


pytest: make loadgroup the default

loadgroup falls back to load which was the default before https://github.com/commaai/openpilot/pull/30441 was merged. loadscope was only needed for test_models because setUpClass was so slow (downloading and mainly decompressing log), it was faster to not run that set up function each time in a new process for some process number configurations.
loadscope groups all the test cases from each class into a separate process, rather than splitting each test case up into new processes which will be slower for the majority of test classes (test_car_interfaces.py for example).

I think we are going to want this elsewhere too, what do you think of this decorator?
def xdist_group_property(property):
    """Mark a class based on a property of that class"""
    def decorator(cls):
        return pytest.mark.xdist_group(name=getattr(cls, property))(cls)
    return decorator

@xdist_group_property('car_model')
class TestCarModel(TestCarModelBase):

there will also be quite a few unittests that are going to want to be grouped

That only marks TestCarModel (the base class that is skipped) in this case since parameterized creates the classes dynamically.

That only marks TestCarModel (the base class that is skipped) in this case since parameterized creates the classes dynamically.

Hmm, does this currently work? I don't think so, because setup is only run on the workers so I think it would be too late to distribute them

Yeah, we'd need some sort of callback ability, but sadly class_name_func just calls the base class.

perhaps its better to handle this within conftest, which will have the class already expanded we can group it properly https://github.com/commaai/openpilot/pull/30466

If it works as expected, great


homework1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
add db diagram
What did you learn from the changes you have made?
modeling
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
better tool could create better diagram
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
tool
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

HW2: new score 8/8, well done
Yes, "AS" can be optional, sorry for the confusion

HW5: 5/8 INSERT Q2 INSERT INTO product_units (product_id, product_name, product_size, product_category_id, product_qty_type, snapshot_timestamp) SELECT product_id, product_name, product_size, product_category_id, product_qty_type, CURRENT_TIMESTAMP FROM product AS p WHERE product_id = 7
Ans: This question doesn't specify to use SELECT so I am free to use anything.

DELETE Q1 WITH older_record AS (SELECT product_id ,MIN(snapshot_timestamp) AS snapshot_timestamp FROM product_units WHERE product_id = 7) DELETE FROM product_units WHERE (product_id = (SELECT product_id FROM older_record ) AND snapshot_timestamp = (SELECT snapshot_timestamp FROM older_record ))
Ans: This question has to be more specific.

UPDATE Q1 ALTER TABLE product_units ADD current_quantity INT; UPDATE product_units SET current_quantity = ( SELECT current_quantity FROM ( SELECT p.product_id, COALESCE(quantity,0) as current_quantity FROM product_units p LEFT JOIN ( SELECT * ,ROW_NUMBER() OVER( PARTITION BY vi.product_id ORDER BY market_date DESC) AS rn FROM vendor_inventory vi ) vi ON p.product_id = vi.product_id WHERE rn = 1 OR rn IS NULL ) p WHERE product_units.product_id = p.product_id);


tiles info needs to be added to XML schema

[100%] Generating arch.merged.lint.html
...
github/SymbiFlow/symbiflow-arch-defs-v2x/build/xc7/archs/artix7/devices/xc7a50t-basys3-roi-virt/arch.unique_pack.xml:331: element tiles: Schemas validity error : Element 'tiles': This element is not expected.

Now that we have <tile> tags, should <pb_type> still have <fc> or <pinlocations> tags?

FYI - @acomodi I'm just fixing up the schema now...

Related pull request on VtR at https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/559

FYI - @Laksen

This is also happening if you run the ./.github/travis/script.sh on current head (26687ddc283a255ad804453d1f61e8f71e6f533a).
tansell@tansell:~/github/SymbiFlow/symbiflow-arch-defs$ ./.github/travis/script.sh
....
[ 50%] Built target file_xc7_archs_zynq7_tiles_slicem_slicem.pb_type.xml
[ 50%] Built target file_xc7_archs_zynq7_tiles_slicem_slicem.model.xml
[ 50%] Built target file_xc7_archs_zynq7_devices_xc7z010-zybo-roi-virt_arch.xml
[ 50%] Built target file_xc7_archs_zynq7_devices_xc7z010-zybo-roi-virt_arch.merged.xml
Scanning dependencies of target zynq7_xc7z010-zybo-roi-virt_arch_lint
[ 50%] Generating arch.merged.lint.html
/usr/local/google/home/tansell/github/SymbiFlow/symbiflow-arch-defs/build/xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/arch.unique_pack.xml:331: element tiles: Schemas validity error : Element 'tiles': This element is not expected.
/usr/local/google/home/tansell/github/SymbiFlow/symbiflow-arch-defs/build/xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/arch.unique_pack.xml fails to validate
xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/CMakeFiles/zynq7_xc7z010-zybo-roi-virt_arch_lint.dir/build.make:62: recipe for target 'xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/arch.merged.lint.html' failed
make[3]: *** [xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/arch.merged.lint.html] Error 3
make[3]: *** Deleting file 'xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/arch.merged.lint.html'
CMakeFiles/Makefile2:59508: recipe for target 'xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/CMakeFiles/zynq7_xc7z010-zybo-roi-virt_arch_lint.dir/all' failed
make[2]: *** [xc7/archs/zynq7/devices/xc7z010-zybo-roi-virt/CMakeFiles/zynq7_xc7z010-zybo-roi-virt_arch_lint.dir/all] Error 2
CMakeFiles/Makefile2:1732: recipe for target 'CMakeFiles/all_xml_lint.dir/rule' failed
make[1]: *** [CMakeFiles/all_xml_lint.dir/rule] Error 2
Makefile:760: recipe for target 'all_xml_lint' failed
make: *** [all_xml_lint] Error 2


Can't use cuda

i have NVIDIA GeForce GTX 1060 but in device there is only cpu
🤖🧠> system-info imaginairy_version:            13.2.0 imaginairy_path:               C:\Users\New\AppData\Local\Programs\Python\Python310\lib\site-packages\imaginairy python_version:                3.10.0 python_installation_path:      C:\Users\New\AppData\Local\Programs\Python\Python310\python.exe device:                        cpu torch_version:                 1.13.1+cpu platform:                      win32 hardware_description:          Windows-10-10.0.22621-SP0 ram_gb:                        7.96 🤖🧠>

The torch version you have installed says its for 1.13.1+cpu.  I'm not sure how exactly to install a different version but you'll need to do that.


Rewrite "How to create a capability" section

Consistent naming and titles
Get rid of "capability" and other terms – depends on #74
Keep linear readability in mind
Consider covering #58

Open questions:

Should we design it as Tutorial or Guides

Perhaps a tutorial covering all steps with particular integration in mind would be the best start

refer to up-to-date testing best practices, i.e. using https://github.com/superfaceai/testing

Closing as relates to the older version of Superface. Thanks all.


Fixing the meridiem for 24:00

24:00 is midnight and should be consider 12:00 am.  Changed the condition to determine which meridiem should be used. (H == 24 || H < 12)

Thanks for your contribution @devNoiseConsulting! I'll merge that in soon.
Just a question though, where did you happen to see 12 pm. for 24:00?
Was it when you resize an event until the very end of the day?

The app I'm working on is making a bunch of events from a schedule in our database. We are not creating or editing any events on the calendar. Just a week view with 30 minute time step.
Here's a sample of what one of the events we are creating:
{"start":"2019-11-04 23:00","end":"2019-11-04 24:00","content":"","title":"<a  title=\"Event 23:00-24:00\"  href=\"\/schedule\/###\/view>Event<a>","class":""},

Hi @devNoiseConsulting, thanks for your contribution. It is now published in version 2.14.0


Close an HTTP/1.1 connection after delay

Currently, if a ReponseHeaders, which contains "connection: close" headers, is sent, the server tries to close the connection immediately.
https://github.com/line/armeria/blob/b16bc8d926e3b4ebb07b86b66a09cd1126121574/core/src/main/java/com/linecorp/armeria/server/AbstractHttpResponseHandler.java#L94
This will make the sockets remain in the TIME_WAIT state.
We can probably avoid this by waiting a certain period of time so that clients do the active closing.
@trustin suggested waiting and closing the connection after writing an empty buffer:
ctx.writeAndFlush(Unpooled.EMPTY_BUFFER).addListener(CLOSE);

I'm pretty new to this kind of design/logic such as servers handling request and managing its connection.
Can you provide more context and guide how to 'wait for a certain period of time' without harming performance(blocking...etc..)
For example,  just invoking Thread.sleep(WAIT_TIME) looks crazy 😄 I believe there are more elegant way of handling and waiting from the view of server.

@echo304 Oops, I missed your comment and apologize for that. 😓
This issue has been assigned to a participant for our internal sprint.

Background
The initiator of a socket close incurs TIME_WAIT. For this reason, in the client-server networking model it is generally recommended that the client-side closes the connection first.
However, in Armeria there are two ways of closing a connection from the server-side.

By calling ServiceRequestContext#initiateConnectionShutdown

Server.builder()
    .service("/", (ctx, req) -> {
        if (req.headers().contains("should-close")) {
            ctx.initiateConnectionShutdown();
        }
        return HttpResponse.of(200);
    });

An InitiateConnectionShutdown event is sent over the channel pipeline which sets a flag

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/Http1RequestDecoder.java#L475

The flag is checked for each request/response completion, and the connection is closed if there are no in-flight requests

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/HttpServerHandler.java#L768-L786

By setting a Connection: close HTTP header

Server.builder()
      .service("/", (ctx, req) -> {
          return HttpResponse.builder()
                             .header(HttpHeaderNames.CONNECTION, "close")
                             .status(200)
                             .build();
      });

A flag is set depending on the header set

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/AbstractHttpResponseHandler.java#L153-L155

The channel is closed immediately after the response has been fully sent

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/AbstractHttpResponseHandler.java#L95-L99

Note that this only pertains to HTTP1 since HTTP2 has its own graceful shutdown mechanism:

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/Http2ServerConnectionHandler.java#L162

The above behavior can be observed from the following tests:

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/test/java/com/linecorp/armeria/server/HttpServerNoKeepAliveTest.java#L51
https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/test/java/com/linecorp/armeria/server/InitiateConnectionShutdownTest.java#L258

Handling this issue
I propose this issue be tackled in three steps:

A straightforward way to handle this issue is to add a delay to each location where channel#close occurs. Since an event loop is assigned to each channel, calling EventExecutor#schedule using the ServiceRequestContext#eventLoop with an arbitrary fixed delay should be good enough.

https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/HttpServerHandler.java#L783
https://github.com/line/armeria/blob/db3973d74e70e177b0849f201fdd96615f2f6292/core/src/main/java/com/linecorp/armeria/server/AbstractHttpResponseHandler.java#L98

We probably want to unify the logic. The previous Connection: close semantic doesn't need to close connections immediately since we will wait a certain time period anyways. We can refactor/simplify so that the two locations are handled by common logic
Instead of using an arbitrary fixed delay, we can introduce a value in Flags so that users can configure the location of how much time the server should wait.


Added Greek Language

Hello Paul, the language subtag el is included in the list and corresponds to the Greek Language. In case of any other concerns, do not hesitate to contact me.

According to the readme, you must add here in this list :

Import your file into the localize.ts file and add your language in the languages record.

const languages: Record<string, unknown> = {
   de,
   en,
   el,    // <= add el here
   fr,
   it,
   "pt-BR": pt_BR,
   sv,
   "zh-Hans": zh_Hans,
   nl,
   "zh-Hant": zh_Hant,
};


Refactor poly_reg_demo

[x] Rename prior to baseline
[x] Add a citation for ensemble+ agent
[x] Make systematic holes by x generator

Done.


python312Packages.aiovodafone: 0.6.1 -> 0.7.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.aiovodafone is: Library to control Vodafon Station
meta.homepage for python312Packages.aiovodafone is: https://github.com/chemelli74/aiovodafone
meta.changelog for python312Packages.aiovodafone is: https://github.com/chemelli74/aiovodafone/blob/v0.7.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.1 with grep in /nix/store/2aym5wvr1yr32m9fn0k66nqvpqjng9yx-python3.12-aiovodafone-0.7.1
found 0.7.1 in filename of file in /nix/store/2aym5wvr1yr32m9fn0k66nqvpqjng9yx-python3.12-aiovodafone-0.7.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.vodafone_station
python311Packages.aiovodafone
python312Packages.aiovodafone

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2aym5wvr1yr32m9fn0k66nqvpqjng9yx-python3.12-aiovodafone-0.7.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.aiovodafone https://github.com/r-ryantm/nixpkgs/archive/a119092084487121048c498c09dd74db27b77012.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a119092084487121048c498c09dd74db27b77012#python312Packages.aiovodafone

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2aym5wvr1yr32m9fn0k66nqvpqjng9yx-python3.12-aiovodafone-0.7.1
ls -la /nix/store/2aym5wvr1yr32m9fn0k66nqvpqjng9yx-python3.12-aiovodafone-0.7.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.vodafone_station
python311Packages.aiovodafone
python311Packages.aiovodafone.dist
python312Packages.aiovodafone
python312Packages.aiovodafone.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 352901 at a1190920 run on aarch64-darwin 1

:white_check_mark: 2 packages built:

python311Packages.aiovodafone
python312Packages.aiovodafone


FLSZB-110 Product Refresh

Merge FLSZB-110 and FLSZB-120 as 120 is not sold anymore
Use manufacturer "mlink" instead of marketing page
Merge compatible systems and fix EAN
Delete FLSZB-120 page

not sold doesn't mean it doesn't exist anymore. restore the old model for the PR to be merged


[aes, pre_syn, pre_sca] Fix Yosys synthesis and Alma formal security verification setups

This PR contains a couple of commits to re-enable Yosys synthesis for AES and Alma formal security verification.

Not sure if my setup is not working, but I get an error when running the pre_syn flow:
ERROR: Module \prim_sparse_fsm_flop_378FE_346F8' referenced in module \aes_cipher_control_fsm' in cell \u_state_regs' is not part of the design.`
It seems that the prim_spare_fsm modules are not getting properly renamed.

Not sure if my setup is not working, but I get an error when running the pre_syn flow: ERROR: Module "\prim_sparse_fsm_flop_378FE_346F8" referenced in module "\aes_cipher_control_fsm" in cell "\u_state_regs" is not part of the design. It seems that the prim_spare_fsm modules are not getting properly renamed.

Hm. This problem should actually be avoided by the following changes added in #9632:
https://github.com/vogelpi/opentitan/blob/498b600427af12133967708e3aeae2bc619258bf/hw/ip/aes/pre_syn/syn_yosys.sh#L114-L117
and
https://github.com/vogelpi/opentitan/blob/498b600427af12133967708e3aeae2bc619258bf/hw/ip/aes/pre_syn/syn_yosys.sh#L144-L146
Did you check out this PR here or maybe just cherry-pick onto an outdated master branch?

I checkout out this PR (gh pr checkout 9762) and the two changes in the file you mentioned are also in the script. I think Yosys is complaining as in the converted aes_cipher_control_fsm.v file there still is the prim_sparse_fsm with the suffix:
prim_sparse_fsm_flop_378FE_346F8 #(
  .StateEnumT_StateWidth(StateWidth),
  ..

Shouldn't this be prim_sparse_fsm_flop ? Adding something like this to line 143:
sed -i 's/prim_sparse_fsm_flop_.*/prim_sparse_fsm_flop \#(/g' $LR_SYNTH_OUT_DIR/generated/${module}.v
fixes this for me and the synthesis script is working for me.
Additionally, I also had to add this to line 147:
sed -i '/\.StateEnumT_StateWidth(.*/d' $LR_SYNTH_OUT_DIR/generated/${module}.v

Thanks for getting back Pascal. You are right, these suffixes should be removed (that's also the intention of the other patch).
It's strange that I don't see this. Most likely it's related to the specific sv2v (v0.0.7-17-g499bd58) and Yosys (0.9+4306 - git sha1 3931b3a03) version I am using.
I'll try out your suggested changes locally first and then push another commit to this PR.

Thanks Pirmin, now it works!
Yeah, I just recently updated to the latest version of Yosys (0.10+1 (git sha1 7a7df9a3)) as I needed some features from there.

Thanks for Pascal for having another look, and you both for approving this. Merging now.


Comprehensive particle mappings

net/minecraft/particle/Particle is now replaced by ParticleParameters. This is to avoid ambiguity with net/minecraft/client/particle/Particle. ParticleParameters contains the information necessary to spawn a Particle in the world. Most ParticleTypes use the default implementation which just contains the ParticleType, but there is an implementation that also contains an ItemStack (such as particles from eating) , and another that also contains a BlockState (such as particles from sprinting).
New particle classes and missing factory classes have been mapped. Almost all names are derived from the registry names of particles.

The ParticleParameters name is taken from the crash report element, which calls it "Parameters".

Should be good now


manifest: wurthelektronik: update revision for double promotion fix

Update wurtheletronik, this is needed for the double promotion fix
see: https://github.com/zephyrproject-rtos/zephyr/pull/57154

Hey together,
the pull request #62408 even brings the drivers to the most recent version, with more bugfixes and new sensors.

Hey together,
the pull request #62408 even brings the drivers to the most recent version, with more bugfixes and new sensors.

But that's been in review in September... I don't know when that is gonna come in 🤷 . This PR doesn't pull it up to a recent of a commit as that one though, this only pulls it up enough to bring in the double promotion fix.
This PR can go in a lot faster than the other one due to a lot less to review as this is blocking another PR, and #62408 can still easily come in when it's ready on top of this.

I agree. Thanks for contributing!


[mdbx::byte] better forgo char8_t and always use unsigned char

Currently mdbx::byte is defined as either char8_t or unsigned char. However, char8_t is much more narrow in scope by design and is intended only to help with UTF8 encoding: https://stackoverflow.com/a/57453713. I suggest to always define mdbx::byte as unsigned char.
P.S. In Silkworm we use uint8_t (= unsigned char) as our byte type; so making mdbx::byte always equal to unsigned char would allow us to use slice::byte_ptr() instead of slice::data() + cast.

This topic is somewhat confusing, but let me try to explain why libmdbx using char8_t as mdbx::byte.
Essentially I need just the unsigned char * restrict type in C99 terms, i.e. the non-aliasing pointer to unsigned char. However, C++ still doesn't have restrict keyword, but also a char-pointers may be aliased.
On the other hand, while/where uint8_t is defined/provided and CHAR_BIT = 8 the char8_t * actually act the same as the C99' unsigned char * restrict. Both the CHAR_BIT = 8 and uint8_t are prerequirements for libmdbx, so I don't expect any issues, including intentional injection of UB-errors by "extra strict" compilers.
At the same time, the approach of using char8_t has several advantages:

the `restrict' attribute is defined on level of the base type and is inherited by any derived pointer type;
some compilers treat FOO as an attribute of an instance of a type ( i.e. a variable, a specific pointer), but not a type attribute.

Nonetheless, I should think about switching to the uint8_t * __restrict__ for byte pointers.


Deambiguate stdin usage collision of set command and ask-passphrase option

I've noticed a problem: when the --ask-passphrase option is provided, of course the setting of the value fails, because the stdin is used as passphrase.
For example
echo "foo" | trousseau --ask-passphrase set bar

Fails, which is actually a normal and expected behavior. Don't know what to think about it yet.

In hindsight I realize this is more of a usage/shell related problem rather than a thing we should fix in trousseau.


Using the plugin with no config.json

EDIT: Submitted by mistake before writing a message.
I'm using NodeBB on Heroku and I need S3 for all the file uploads. I installed the plugin using npm and then pushed the directory back up to Heroku. I'm configuring everything as environment variables, so access key, secret key, host and bucket are all defined in the Heroku control panel. As I understand, path would be set by default to /.
At the moment I'm getting two errors, one on the console:
warn: [plugins/nodebb-plugin-s3-uploads-updated] Mapped path 's3 => /app/node_modules/nodebb-plugin-s3-uploads-updated/public' not found.

And one on the admin control panel:
Internal error.
Oops! Looks like something went wrong!
/api/admin/plugins/s3-uploads
Cannot find module './../../config.json'

This second one might be the issue here, as I have no config.json on the server. All variables for NodeBB configuration are also defined as environment variables.

As a clarification, the files are uploaded to S3 but I cannot see the plugin config options because of the config.json error.

it needs a config.json currently to determine your site url and a few other things


Install a CLI in the default deployment

Pull down a pinned version of the HistomicsTK CLI and install it into the system as part of standard deployment via the deploy_docker.py script.

Added in PR #332.  When not using docker, the cli_test.py script can be run manually to install a CLI and run some tests.


How to call lncli create and unlock from api

Hi following problem, I'm currently developing a lightning wallet, in which every user should get assigned his/her individual node. However I currently struggle to setup the authentication process when users first join the app. I can spin up a docker running a node for each usee individually however how would I do the lncli create as an api call for the user if I dont want to put it in the dockerfile? Also is the docker and api setup mad  in a way where I dont need to mess with the dockerfile at all in order to spin up a docker instane for each user. Could I simply use only api calls in order to change stuff individually for each user?
My docker spinup currently looks something like this:
sudo docker run -d
-v ~/Desktop/wallet_password:/root/.lit/wallet_password
-v ~/Desktop/lit.conf:/root/.lit/lit.conf
...
-p 8443:8443/tcp
-p 9735:9735/tcp
-p 10009:10009/tcp
lightninglabs/lightning-terminal:v0.12.2-alpha --enablerest
Also can I instanly pass a seedphrase while spinning it up or does it need to be done with an api call or lncli create call in the dockerfile?
In general is there anything else you recommend or I should look at anything else trying to create a individual dockernode for each user?

You could look into https://github.com/lightninglabs/lndinit, which should enable that.


how can I change another mp3 to play

`
package main
import (
"io/ioutil"
"time"
"github.com/hajimehoshi/oto"
"github.com/tosone/minimp3"
"log"
)
func players() error {
file, _ := ioutil.ReadFile("assets/mp3/test.mp3")
dec, data, _ := minimp3.DecodeFull(file)
player, _ := oto.NewPlayer(dec.SampleRate, dec.Channels, 2, 4000)
player.Write(data)

dec.Close()
player.Close()
return nil

}
func main() {
for i := 0; i < 3; i++ {
if err := players(); err != nil {
log.Fatal(err)
}
time.Sleep(time.Second * 5)
}
}`
when I run above code it got a error:
panic: oto: NewContext can be called only once

how can I solve this error, and I want to chenge another mp3 to play , is seems I cant close NewContext then create a new player

my test.mp3 is 2 second

my test.mp3 is 2 second

why I just play once then got error

why I just play once then got error

In your code, it looks like oto.NewPlayer is called multiple times. As you said, create a context by oto.NewContext and then call the context's NewPlayer instead.

thank you


BUG: pac auth create for GCC doesn't select right cloud

I am in version 1.32.8 and it seems like running pac auth create, doesn't select the right GCC cloud by default. Currently it defaults to 'Public'. I believe in past, it used to automatically select 'UsGov' when we used the command.

pac auth create without any arguments will always (and has always) targeted the Public cloud.
PAC can figure out the right cloud if you pass your organization's URL to the --environment command, but otherwise would need a --cloud argument to specify explicitly.


Primary screen icons not centering.

Hello,
Idk if this is a known issue for the latest version of TaskbarX, but seems like primary screen won't center for some reason. Using the Rainmeter version of TaskbarX.
No idea as to why this happens at all. I tried setting cpo to 1 in the config, and it doesn't seem to do it(refreshed loads of times. And that doesn't do it either.

I seem to have fixed the issue by going down to a lower version. I was running on version <IP_ADDRESS> and that seemed to be causing the problem, as version <IP_ADDRESS> works just fine. I wanted to see if there was a difference.

I have same problem. i just updated after a month (or two? i don't remember) but <IP_ADDRESS> only centers second display.
I also tried cpo=0 and playing with screen modes (extended, duplicate, etc.) and they didn't work.

I also tried TaskbarX with Configurator instead of Rainmeter Skin
The problem still exists.

I tried pre-release 1.7.1 to see if it is fixed. it wasn't.
then I Enabled "Show Console"
and this was the output

and everytime i open or close an app, this error appears again.

I tried pre-release 1.7.1 to see if it is fixed. it wasn't.
then I Enabled "Show Console"
and this was the output

and everytime i open or close an app, this error appears again.

To solve this issue, downgrade to <IP_ADDRESS>. Seems to fix it.


Adding bot to display coveralls data

A hackish bot to pull data from coveralls.io and display a report based on the passed in repo. I ended up using markdown, as I couldn't figure out how to use Hubot in coordination with the Mattermost upload API listed here: https://github.com/mattermost/platform/blob/master/api/file.go.
Additions

Added scripts/test-coverage.coffee to display markup coverage info.

Changes

Modifies package.json to add jsdom and markup packages.

Testing

Run cfpbot show test repos
Run cfpbot show test report grasshopper

Review

@contolini

Screenshots

Notes

There are probably a million approaches better than this one (i.e, going against the github api and using instanbul, coveralls.io webhook) but this was fun.

It would probably make sense to add the capability to summarize the table and display a visualization.

If there are many files then the table currently gets truncated.

Todos

Create a test coverage summary table.

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

…ndar

Very cool! I've tested it locally and it works well. Let's get it into prod so that we can do some user testing.
Buuuuut please git commit --amend and choose an emoji for your message per the very important contributing guidelines.

@contolini , I'm closing this, as I think the dashboard makes more sense.


stm32cube: cmake: Pure refactoring of build script

Reduce the code duplication in ext/hal/st/stm32cube/CMakeLists.txt by
using a foreach loop instead of copy-paste for each SoC.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6383   +/-   ##
=======================================
  Coverage   53.08%   53.08%
=======================================
  Files         430      430
  Lines       41040    41040
  Branches     7908     7908
=======================================
  Hits        21785    21785
  Misses      16032    16032
  Partials     3223     3223

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 c0985fa...a463326. Read the comment docs.


BLOB objects

I will reopen the request to add support for images saved as blob objects.
Not firefox and chrome either can download them directly - chrome has option to download such image but it doesn't work.
As i understand blob objects are a code which is required to run to show picture. Somehow browsers can display the image correctly so maybe can it be fetched from cache or sth like that?
There was some tip to get them in chrome with developer mode, but with much struggles i was able to get only few of them. With more than few pictures on site it is discouraging to use this method. With FX I couldn't get a single image.

URL?
Browser version?
It works fine with our own test case on Firefox Nightly 120.0a1
https://github.com/eight04/image-picka/blob/9a71160c25788978ba264ad34cf4e5cff24a919d/test/frame.html#L7

hello,
i've been using your extension for a while and it worked fine until today on this website :
https://www.japscan.lol/lecture-en-ligne/level-up-with-skills/39/1.html
nothing appear anymore they seem to have put blob objects ?
i tried to dl on firefox version 120.0.1

https://www.japscan.lol/lecture-en-ligne/level-up-with-skills/39/1.html

I got a 404 page:


[SMALLFIX] Update version for fuse dockerfile

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20602/
Test PASSed.


fix up some grammar

Update the README file to allow better readability

Thanks for the contribution @brmurphy!


Upgrade rake-compiler-dock

To support Ruby 2.7, new ruby-compiler-dock is needed. However, it changes the docker structure a bit, our build system should change accordingly. Previously, it had one docker image for everything but it changed to have one docker image per platform.
grpc_build_artifacts_multiplatform: passed

Some gems are missing with this PR. Artifacts for mingw32 and x86-linux are not built.
Ruby gem artifacts with this PR
grpc-1.27.0.dev-universal-darwin.gem
grpc-1.27.0.dev-x86_64-linux.gem
grpc-1.27.0.dev.gem
grpc-tools-1.27.0.dev.gem
Ruby gem artifacts previously
grpc-1.27.2-universal-darwin.gem
grpc-1.27.2-x64-mingw32.gem
grpc-1.27.2-x86-linux.gem
grpc-1.27.2-x86-mingw32.gem
grpc-1.27.2-x86_64-linux.gem
grpc-1.27.2.gem
grpc-tools-1.27.2.gem


Fix typo / grammatical error

Just 2 tiny fixes

Closing this. Please see https://github.com/Atyantik/react-pwa/pull/84


Can't run tensorflow multi-lingual sentence encoder

Description
When trying to run the multi-lingual version of the Universal Sentence Encoder there is a bug where an OP type SentencepieceOp is not registered
Expected Behavior
The model should run on the inputs provided
Error Message
(Paste the complete error message, including stack trace.)
2020-10-05 09:13:51.718367: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:303] SavedModel load for tags { serve }; Status: success: OK. Took 1933216 microseconds.
Exception in thread "main" org.tensorflow.exceptions.TensorFlowException: Op type not registered 'SentencepieceOp' in binary running on Humzas-MacBook-Pro.local. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) `tf.contrib.resampler` should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.
	at org.tensorflow.internal.c_api.AbstractTF_Status.throwExceptionIfNotOK(AbstractTF_Status.java:101)
	at org.tensorflow.SavedModelBundle.load(SavedModelBundle.java:206)
	at org.tensorflow.SavedModelBundle.access$000(SavedModelBundle.java:45)
	at org.tensorflow.SavedModelBundle$Loader.load(SavedModelBundle.java:50)
	at ai.djl.tensorflow.engine.TfModel.load(TfModel.java:95)
	at ai.djl.repository.zoo.BaseModelLoader.loadModel(BaseModelLoader.java:142)
	at ai.djl.repository.zoo.ModelZoo.loadModel(ModelZoo.java:162)
	at ai.securiti.privaci.detection.analyzer.topic.UniversalSentenceEncoder.predict(UniversalSentenceEncoder.java:85)
	at ai.securiti.privaci.detection.analyzer.topic.UniversalSentenceEncoder.main(UniversalSentenceEncoder.java:58)

How to Reproduce?
(If you developed your own code, please provide a short script that reproduces the error. For existing examples, please provide link.)
I am attaching a script which is modeled after this https://github.com/awslabs/djl/blob/master/examples/src/main/java/ai/djl/examples/inference/UniversalSentenceEncoder.java but replaces the modelUrl with "https://storage.googleapis.com/tfhub-modules/google/universal-sentence-encoder-multilingual/3.tar.gz" UniversalSentenceEncoder.java.zip
Steps to reproduce
(Paste the commands you ran that produced the error.)
I ran the attached script
What have you tried to solve it?

I looked up the error and it seems to be because operations in tensorflow_text aren't registered, I'm guessing those weren't implemented in DJL

Environment Info
Please run the command ./gradlew debugEnv from the root directory of DJL (if necessary, clone DJL first). It will output information about your system, environment, and installation that can help us debug your issue. Paste the output of the command below:
[INFO ] - ----------Environment Variables----------
[INFO ] - PATH: /Users/humzaiqbal/Downloads/apache-maven-3.6.0//bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/opt/python3/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/humzaiqbal/.local/bin:/Users/humzaiqbal/Downloads/apache-maven-3.6.0/bin:/Library/Java/JavaVirtualMachines/openjdk-11.0.1.jdk/Contents/Home/
[INFO ] - JAVA_HOME: /Library/Java/JavaVirtualMachines/openjdk-11.0.1.jdk/Contents/Home
[INFO ] - TERM: xterm-256color
[INFO ] - JAVA_MAIN_CLASS_5083: ai.djl.integration.util.DebugEnvironment
[INFO ] - LANG: en_US.UTF-8
[INFO ] - ITERM_PREV_PS1: \[\]\n\h:\W \u\n\$ \[\]
[INFO ] - LOGNAME: humzaiqbal
[INFO ] - XPC_SERVICE_NAME: 0
[INFO ] - PWD: /Users/humzaiqbal/Documents/djl
[INFO ] - TERM_PROGRAM_VERSION: 433
[INFO ] - JAVA_MAIN_CLASS_5033: org.gradle.wrapper.GradleWrapperMain
[INFO ] - SHELL: /bin/bash
[INFO ] - ITERM_ORIG_PS1: \n\h:\W \u\n\$
[INFO ] - TERM_PROGRAM: Apple_Terminal
[INFO ] - APP_NAME_5033: Gradle
[INFO ] - SECURITYSESSIONID: 186a7
[INFO ] - OLDPWD: /Users/humzaiqbal/Documents/djl
[INFO ] - USER: humzaiqbal
[INFO ] - APP_ICON_5033: /Users/humzaiqbal/Documents/djl/media/gradle.icns
[INFO ] - LaunchInstanceID: 91ACE051-8375-466D-8F2E-406BA163D4F6
[INFO ] - TMPDIR: /var/folders/kc/9h6dxv3s55zfnrh266jsgn2m0000gn/T/
[INFO ] - SSH_AUTH_SOCK: /private/tmp/com.apple.launchd.s1s1rKBXJj/Listeners
[INFO ] - XPC_FLAGS: 0x0
[INFO ] - TERM_SESSION_ID: 3DB58E3A-E7F7-4B0B-B4CC-C38F894CAC2C
[INFO ] - LC_ALL: en_US.UTF-8
[INFO ] - M2_HOME: /Users/humzaiqbal/Downloads/apache-maven-3.6.0/
[INFO ] - __CF_USER_TEXT_ENCODING: 0x1F5:0x0:0x0
[INFO ] - HOME: /Users/humzaiqbal
[INFO ] - SHLVL: 1
[INFO ] -
[INFO ] - ----------Hardware----------
[INFO ] - Available processors (cores): 12
[INFO ] - Byte Order: LITTLE_ENDIAN
[INFO ] - Free memory (bytes): 468419640
[INFO ] - Maximum memory (bytes):<PHONE_NUMBER>
[INFO ] - Total memory available to JVM (bytes): 536870912
[INFO ] - Heap committed: 536870912
[INFO ] - Heap nonCommitted: 38453248
[INFO ] - GPU Count: 0
[INFO ] - Default Device: cpu()
[INFO ] - GCC:
[INFO ] - Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
[INFO ] - Target: x86_64-apple-darwin19.6.0
[INFO ] - Thread model: posix
[INFO ] - InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Similar to https://github.com/tensorflow/hub/issues/463, it seems like this model depends on tensorflow text. Text is an expansion for Tensorflow that provides both native engine operators as well as some python code. We don't support Text right now, but I will change this issue to a feature request to support it

Great thanks, do you know if this is something that could be supported within a week or two or do you think more time would be required?

@roywei Can you take a quick look at TF Text?

Any news about solving this issue?

Just another ping in 2022 - any news?

Maybe it is possible to load the TF text with TensorFlow.loadLibrary(..) before loading the model. According to this closed issue from the tensorflow java repo, it should be possible now to load models using tensorflow-text ops.

Finally, it worked: I was able to load the multi-lingual model by loading the tensorflow_text .so files explicitly in front of loading the model:
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_constrained_sequence_op.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_fast_wordpiece_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_mst_ops.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_normalize_ops.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_regex_split_ops.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_sentence_breaking_ops.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_sentencepiece_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_split_merge_from_logits_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_split_merge_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_state_based_sentence_breaker_op.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_unicode_script_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_whitespace_tokenizer.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_whitespace_tokenizer_v2.so");
        TensorFlow.loadLibrary("/home/myName/.local/lib/python3.10/site-packages/tensorflow_text/python/ops/_wordpiece_tokenizer.so");

Maybe not all of the files has to be loaded, I will check that for me. Crucial was that the installed 'tensorflow_text' version was more or less the same than the tensorflow version used by DJL (shown with TensorFlow.version()). In my current case, the installed version under Linux/pip is '2.8.2', the DJL version is '2.8.0'.
I know this is a workaround, but maybe it helps someone, and maybe it helps enhancing DJL in this direction.

@reuschling
Really appreciate sharing this solution. We  can add this to our document.

@reuschling thanks again for this solution. I have updated the tensorflow documentation to detail this solution https://github.com/deepjavalibrary/djl/pull/1776. This solution will be very helpful for DJL TensorFlow users!


feat(message): add call field

Summary

Implements discord/discord-api-docs#6864 / #1193

This is a Code Change

[ ] I have tested my changes.
[x] I have updated the documentation to reflect the changes.
[x] I have run task pyright and fixed the relevant issues.

Forgot to mark this as a draft initially as it hasn't been merged by Discord yet


Make PR to merge ur_msgs back to upstream

Currently we use Denis' fork:
https://github.com/destogl/ur_msgs.git
We should get this merged back into https://github.com/ros-industrial/ur_msgs

https://github.com/ros-industrial/ur_msgs/pull/12

ur_msgs is actually on the upstream repo and released as binary packages by now.


OSD kiss ultra not working correctly

Hi all, I don't know if this is the place for my issue but I give it a try. I have received my new hdzero goggles and that are very nice. But I have some problems with the fc osd. I use kiss ultra fc and it is working but on the new goggles the screen is full of lines (so a -) the osd elements are showing but there rest of the screen of full. On the old farshark Rx this is not the case and the osd is working fine. Updated the kiss fc but no difference, updated the vtx aan goggles but still the same. If I disable the osd in the fc then the lines are gone. Is this a known issue?
Thanks in advance

yes this is right place! could you try creating an image somehow?

Yes tonight I will add an image, I will also try a second quad with kiss and see if it has the same problem.

Here a picture, strange this is that my other quad don't have this issue. Both use the kiss ultra and both on the whoop vtx with runcam V2. The one from the picture I updated the vtx and it reports ver 1.0.0 in the vtx menu. The other quad reports v37. To be clear the quad with shows the problems I updated it because of this issue but it didn't solve it. But why it reports ver 1.0.0 and the other 37 is a bit strange I think.

Kiss uses Ardupilot font (or simmilar, for me ardu one works), so You need to upload custom HD font with name ARDU_000.bmp. Instructions are under hdzero-osd-font-library

@nathanielakkermans can you verify if that is the case? fetch the ardu font here https://github.com/hd-zero/hdzero-osd-font-library and place it on the sdcard as described in the readme.

@nathanielakkermans can you verify if that is the case? fetch the ardu font here https://github.com/hd-zero/hdzero-osd-font-library and place it on the sdcard as described in the readme.

i'm sorry for the late replay. this did the trick! thank you for the solution. the strange thing is that one quad was working and the other had the strange osd lines. after the ardu font update the one with the lines was nice and fixt but i noticed that the other quad had a different font. so i checked the FC firmware and that one was running an old firmware 2.0.1 B23 (kiss ultra) and the other was running on 2.0.1 B43. so i guess that somewhere between these versions it changed witch osd it used. but all good now! thanks

Neat! an updated ARDU font was also merged into this repo recently. that should fix the issue without installing a custom font.


Allow any weak etag even if it doesn't match the pattern (412 should happen)

Fix https://github.com/Azure/Azurite/issues/1229
This is pretty low priority, but I wanted to start with an easy bug fix as I ramp up on this repository. This is only my 3rd PR 😄.

Good call. Done. There was another pre-existing table-only util that I moved too.

@XiaoningLiu - could this be merged? Or are there more changes I should do?


Enhance isType() documentation

Referring to this function: https://docs.influxdata.com/flux/v0.x/stdlib/types/istype/
Could we please add:

Some content that explains the purpose(s) of the function?
An example that shows how to exclude strings and other types of downsampling queries?

Added to Flux documentation in https://github.com/influxdata/flux/pull/4523. Will add to main docs site as well.


🐦 Please tweet about v0.40.0 release 🚀

Hi folks, could you please tweet about v0.40.0 ❔ So I'll can RT it 🙏

Hey! It should be tweeted after the weekend, when our social media person is back 🙂

🙆♂ i'm waiting for you.


release job in knative/build-pipeline is consistently failing

Expected Behavior
Release job succeeds
Actual Behavior
Release job is failing consistently in past 7 days
Steps to Reproduce the Problem
https://testgrid.knative.dev/knative-build-pipeline#release
Additional Info
This might be expected as build-pipeline is now moved out of knative

@bobcatfish can we simply remove them from our Prow and Testgrid instances, now that you guys have your own?

@bobcatfish can we simply remove them from our Prow and Testgrid instances, now that you folks have your own?

Yes we should remove.

/assign @chaodaig
Chao, please deploy the new configs once 563 merges and close this issue, thanks.

Both Prow and Testgrid configs deployed


#6 Append a resolver for "org.spark-packages" % "sbt-spark-package" % "0.2.2"

https://github.com/databricks/spark-package-cmd-tool/issues/6

thank you for merging it!

No problem. Actually, can we update the version to 0.2.3 in the other PR?
Thanks!
On Aug 28, 2015 4:09 PM, "Yu ISHIKAWA"<EMAIL_ADDRESS>wrote:

thank you for merging it!
—
Reply to this email directly or view it on GitHub
https://github.com/databricks/spark-package-cmd-tool/pull/7#issuecomment-135907998
.

Maybe, but I haven't checked updating the version will go well.


Issue with importing TimedJSONWebSignatureSerializer when updating db with Flask.

flask db upgrade
Usage: flask db upgrade [OPTIONS] [REVISION]
Try 'flask db upgrade --help' for help.

Error: While importing 'app', an ImportError was raised:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/flask/cli.py", line 218, in locate_app
    __import__(module_name)
  File "/Users/lostprogrammer/Documents/Documents/website/app.py", line 7, in <module>
    from models import db
  File "/Users/lostprogrammer/Documents/Documents/website/models.py", line 2, in <module>
    from itsdangerous import TimedJSONWebSignatureSerializer as Serializer
ImportError: cannot import name 'TimedJSONWebSignatureSerializer' from 'itsdangerous' (/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/itsdangerous/__init__.py)

I am getting this error when trying to update my database.  I am honestly unsure of the exact reason behind this.
Replicate the bug:

Using macOS Ventura
Python 3.9.10 with flask 2.2.2.
Setup a flask web server with a basic PostgreSQL database
Add the following line to the Python file:

from itsdangerous import TimedJSONWebSignatureSerializer as Serializer

Run flask db upgrade in said Python file

Expected behaviour:
From the many times I have used flask db upgrade and flask db migrate, this time I was not very lucky and received an odd error.
Environment:

Python version: Python 3.9.10
ItsDangerous version: 2.0.1
Flask version: 2.2.2

Duplicate of #294


Interval casting fixes update of cqm-models

Pull requests into cqm-execution require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
❗BEFORE MERGE ❗

[ ] AFTER https://github.com/projecttacoma/cqm-models/pull/118 is merged, update package.lock back to master and rebuild browser.js

Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/BONNIE-2033 https://jira.mitre.org/browse/BONNIE-2048
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

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

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   86.63%   86.63%
=======================================
  Files           6        6
  Lines         681      681
  Branches      203      203
=======================================
  Hits          590      590
  Misses         91       91

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 1ea2421...2068062. Read the comment docs.


Update vpn-gateway-about-vpngateways.md

The first paragraph is technically incorrect. Each virtual network can have up to two network gateways - one VPN Gateway and one ExpressRoute Gateway. The previous text said there can only be one gateway per virtual network.

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

Actually, the existing wording may be OK since it's talking about VPN gateways.