The generative coverage model and germline CNV caller

It is finally here :-) I broke the PR into 3 separate commits. The first two commits are minimal (docs + update to the existing classes). The last commit is major but may still be reviewed in compartments (see the commit message).
Regarding the failing tests: most of them are on purpose. The failing Spark tests of the germline caller are due to an issue in GATK engine (see https://github.com/broadinstitute/gatk/issues/2337). I'm working on a fix.

Thanks for issuing this, @mbabadi!  I got saddled with putting together a couple of talks, and @davidbenjamin and @asmirnov239 are out this week, but we will get to reviewing it ASAP.
However, I see that some tests are failing---can you go ahead and throw a @Test(enabled = false) and TODOs on these in the meantime?

@mbabadi @samuelklee I'm done.

You should test that.  I almost never try to parallelize steam.  Also,
could it cause issues when running in spark?
On Apr 14, 2017 22:37, "Mehrtash Babadi"<EMAIL_ADDRESS>wrote:

@mbabadi commented on this pull request.
In src/main/java/org/broadinstitute/hellbender/utils/hmm/segmentation/
HiddenMarkovModelPostProcessor.java
https://github.com/broadinstitute/gatk-protected/pull/857#discussion_r111656546
:

@@ -308,8 +309,9 @@ private void performSegmentation() {
*/
private Map<String, List<HiddenStateSegment<S, T>>> calculateBestPathSegments() {
final Map<String, List<HiddenStateSegment<S, T>>> allSegments = new LinkedHashMap<>(sampleNames.size());

   IntStream.range(0, numSamples)

   IntStream.range(0, numSamples).parallel()

@LeeTL1220 https://github.com/LeeTL1220 any reason why not? parallel
streams make a ForkJoinPool with an adaptively chosen number of threads.
If the system has multiple cores, they will be all used. #GreatSpeedup
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/gatk-protected/pull/857#discussion_r111656546,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACDXk90Brd-xv4N4goHiQTYb3tkyjoVZks5rwC1rgaJpZM4LilC_
.

OK @mbabadi!  I left some remarks, but I think I am generally OK with all of your responses.  Let's try to avoid that unicorn in the future...

Congrats @mbabadi, this is huge!


Update Lottie Codegen doc

Remove gui for lottiegen since we're removing this feature shortly

Docs Build status updates of commit cdecaab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/animations/lottie-scenarios/getting_started_codegen.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@sohchatt this is still in 6.0, eh?  So master is correct, when we push next update to package and refresh docs from master it'll disappear?
Or do you want to modify the existing live page?  If so, you need to do this change off the live branch as per readme.

I just used the docs.microsoft edit UI on the live page. Does that not work?

@sohchatt you just need to switch to the live branch first:


merge from arlac77/template-arlac77-github,arlac77/template-esm-only,arlac77/template-node-component

package.json

chore(deps): add ^3.11.0 remove ^3.10.1 (devDependencies.ava)

:tada: This PR is included in version 3.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


M3u8::Playlist.read("path/to/file") fails silently

Had a few minutes of head scratching when I tried calling M3u8::Playlist.read with a path before I realized I needed an IO object. Calling read with a path doesn't throw an error and returns a playlist regardless
irb(main):002:0> M3u8::Playlist.read("~/Desktop/long_hls")
=> #<M3u8::Playlist:0x007fb77388de20 @version=nil, @sequence=0, @cache=nil, @target=10, @type=nil, @iframes_only=false, @independent_segments=false, @items=[]>

Good catch, I agree that the reader should raise an error if the first line does not contain the #EXTM3U tag.

Fixed in v0.8.0


index out of bounds: the len is 10 but the index is<PHONE_NUMBER>3709551615

https://github.com/fltk-rs/fl2rust/blob/62e26384b84fb7a782fd4a30093cfb9c611bdec0/src/gen.rs#L177
I think it shoule be
for i in 1..props.len() {
// since you use props[i - 1]

Hi
Do you have a reproducer which invokes this?

I've pushed a fix which uses optionals and wrapping sub.

@MoAlyousef it is still happenening unless I modify to 0 to 1 again.
I have tried both using a manual version fl2rust in.fl > out.rs as well as manually editing my installed version and deleting my deps to rebuild the changes.
This is by far the most intricate FLUID file I have ever used with the program, it is 1247 lines, otherwise I'd post it here.
If the 0 should work (like it used to) it seems there is likely some item I am using you did not include, or something along those lines.

Though, if you just want me to post it anyhow I can :smile:

Does it also happen with the latest changes?
If you could upload it or send it privately, it would provide a good test case.

I've tried the latest changes on uhambo.fl and it seems to work correctly. Can you try again?

Were you able to verify the latest release?

This does indeed fix it! Thanks so much I will close this!


[BUG] v112 to v120 upgrade observed error in post-drain

Describe the bug

[Wed May 31 14:26:00 UTC 2023] Running "upgrade_node.sh post-drain" errors, will retry after 10 minutes (0 retries)...
+++ PRETTY_NAME='Harvester v1.1.2'
+++ ID=sle-micro-rancher
+++ ID_LIKE=suse
+++ ANSI_COLOR='0;32'
+++ CPE_NAME=cpe:/o:suse:sle-micro-rancher:5.3
+++ VARIANT=Harvester
+++ VARIANT_ID=Harvester-20230420
+++ GRUB_ENTRY_NAME='Harvester v1.1.2'
++ echo Harvester v1.1.2
+ CURRENT_OS_VERSION='Harvester v1.1.2'
+ '[' 'Harvester 984295f-dirty' = 'Harvester v1.1.2' ']'
+ '[' -n '' ']'
++ mktemp -p /host/usr/local/upgrade_tmp
+ tmp_rootfs_squashfs=/host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj
+ download_file http://upgrade-repo-hvst-upgrade-h6v4z.harvester-system/harvester-iso/rootfs.squashfs /host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj
+ local url=http://upgrade-repo-hvst-upgrade-h6v4z.harvester-system/harvester-iso/rootfs.squashfs
+ local output=/host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj
+ echo 'Downloading the file from "http://upgrade-repo-hvst-upgrade-h6v4z.harvester-system/harvester-iso/rootfs.squashfs" to "/host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj"...'
+ local i=0
+ [[ 0 -lt 100 ]]

Downloading the file from "http://upgrade-repo-hvst-upgrade-h6v4z.harvester-system/harvester-iso/rootfs.squashfs" to "/host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj"...
+ curl -sSfL http://upgrade-repo-hvst-upgrade-h6v4z.harvester-system/harvester-iso/rootfs.squashfs -o /host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj
+ break

++ mktemp -d -p /host/tmp
+ tmp_rootfs_mount=/host/tmp/tmp.x7BLf5ytTi
+ mount /host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj /host/tmp/tmp.x7BLf5ytTi
+ new_elemental_cli=/usr/local/bin/elemental_cli/elemental
+ target_elemental_cli=/host/usr/bin/elemental
++ date +%Y%m%d%H%M%S
+ elemental_upgrade_log=/usr/local/upgrade_tmp/elemental-upgrade-20230531142550.log
+ local ret=0

+ mount --bind /usr/local/bin/elemental_cli/elemental /host/usr/bin/elemental
+ chroot /host elemental upgrade --logfile /usr/local/upgrade_tmp/elemental-upgrade-20230531142550.log --directory /tmp/tmp.x7BLf5ytTi
Flag --directory has been deprecated, 'directory' is deprecated please use 'system' instead

INFO[2023-05-31T14:25:50Z] Starting elemental version v0.1.1
INFO[2023-05-31T14:25:50Z] Upgrade called
INFO[2023-05-31T14:25:50Z] Applying 'before-upgrade' hook
INFO[2023-05-31T14:25:50Z] Running before-upgrade hook
INFO[2023-05-31T14:25:50Z] deploying image /tmp/tmp.x7BLf5ytTi to /run/initramfs/cos-state/cOS/transition.img
INFO[2023-05-31T14:25:50Z] Creating file system image /run/initramfs/cos-state/cOS/transition.img
INFO[2023-05-31T14:25:50Z] Copying /tmp/tmp.x7BLf5ytTi source...

ERRO[2023-05-31T14:25:59Z] Failed deploying image to file '/run/initramfs/cos-state/cOS/transition.img': exit status 23: rsync: [sender] read errors mapping "/tmp/tmp.x7BLf5ytTi/ascii
.pf2": Input/output error (5)
rsync: [sender] read errors mapping "/tmp/tmp.x7BLf5ytTi/euro.pf2": Input/output error (5)

rsync: [sender] read errors mapping "/tmp/tmp.x7BLf5ytTi/grub-mkconfig_lib": Input/output error (5)
rsync: [sender] read errors mapping "/tmp/tmp.x7BLf5ytTi/unicode.pf2": Input/output error (5)
WARNING: ascii.pf2 failed verification -- update discarded (will try again).

harv31:/home/rancher # kk get pods -A | grep upgrade
cattle-system               apply-system-agent-upgrader-on-harv32-with-b02cb3c166f31a-h4q8z   0/1     Completed   0               15m
cattle-system               system-upgrade-controller-65bcf49944-zbq7v                        1/1     Running     0               4m35s

harvester-system            hvst-upgrade-h6v4z-apply-manifests-fgt8k                          0/1     Completed   0               16m
harvester-system            hvst-upgrade-h6v4z-post-drain-harv31-w655c                        1/1     Running     0               3m13s  ----keep waiting

harvester-system            hvst-upgrade-h6v4z-upgradelog-downloader-555cfdc5dc-5b22q         1/1     Running     0               11m
harvester-system            hvst-upgrade-h6v4z-upgradelog-infra-fluentbit-gbm6v               1/1     Running     0               5m52s
harvester-system            hvst-upgrade-h6v4z-upgradelog-infra-fluentbit-vddlj               1/1     Running     0               3m3s
harvester-system            hvst-upgrade-h6v4z-upgradelog-infra-fluentd-0                     2/2     Running     0               5m52s
harvester-system            virt-launcher-upgrade-repo-hvst-upgrade-h6v4z-h6q5h               1/1     Running     0               30m

To Reproduce
Steps to reproduce the behavior:

v1.1.2 2-node cluster, upgrade to v1.2.0

Expected behavior

Support bundle

Environment

Harvester ISO version:  v1.2.0
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): KVM VM based 2-node Harvester cluster

Additional context
Add any other context about the problem here.
Observed in test of PR: https://github.com/harvester/harvester/pull/3380

@bk201 @starbops  any idea of this post-drain failure ? thanks.

I guess the root cause could be the same as #4020 because we usually see an "input/output error" indicating something is wrong with the storage device. Those files are under /tmp/tmp.x7BLf5ytTi, which is bind-mounted and rooted under the host's /usr/local:
mount /host/usr/local/upgrade_tmp/tmp.Cn3b2PEXTj /host/tmp/tmp.x7BLf5ytTi


Cleanup of core module

Adds a lot of . to ends of sentences
Removes some outdated methods from EOPatches
Restructures utilities into their own subfolder
Other minor things

Codecov Report

Merging #371 (5f06307) into develop-v1.0 (f06c41e) will increase coverage by 0.11%.
The diff coverage is 69.23%.

@@               Coverage Diff                @@
##           develop-v1.0     #371      +/-   ##
================================================
+ Coverage         81.83%   81.94%   +0.11%
================================================
  Files                54       55       +1
  Lines              5377     5339      -38
================================================
- Hits               4400     4375      -25
+ Misses              977      964      -13

Impacted Files
Coverage Δ

core/eolearn/core/eoworkflow.py
96.77% <ø> (ø)

core/eolearn/core/exceptions.py
100.00% <ø> (ø)

core/eolearn/core/utilities/filesystem.py
96.42% <0.00%> (ø)

visualization/eolearn/visualization/eopatch.py
0.00% <0.00%> (ø)

core/eolearn/core/eonode.py
94.23% <25.00%> (ø)

core/eolearn/core/utilities/feature_parser.py
89.83% <50.00%> (ø)

core/eolearn/core/utilities/other.py
57.83% <57.83%> (ø)

core/eolearn/core/eodata.py
90.68% <66.66%> (+0.72%)
:arrow_up:

core/eolearn/core/constants.py
98.63% <100.00%> (+0.01%)
:arrow_up:

core/eolearn/core/core_tasks.py
98.10% <100.00%> (+0.61%)
:arrow_up:

... and 15 more

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 f06c41e...5f06307. Read the comment docs.


Nesting the doc according to yaml's nesting

Hello,
autoyaml seems to be an nice extension to document yaml files inside sphinx.
Unfortunately in the current version the generated doc is 'flat'. It would greatly enhance readability if it would be possible to 'nest' the documentation following yaml's file nesting.

Hi,
currently YAML:
###
# Level 1 variable description
variable:
  ###
  # Level 2 variable description
  subvar:
    ###
    # Level 3 variable description
    subsubvar: "test"

would render as:
variable

   Level 1 variable description

subvar

   Level 2 variable description

subsubvar

   Level 3 variable description

I assume your idea is to render it like:
variable

   Level 1 variable description

   subvar

      Level 2 variable description

      subsubvar

         Level 3 variable description

Am I right?

Exactly.
Certainly, there should be a nesting limit as more than 3 levels it might become unreadable.

Hi. I like the idea. Most of my configs are nested. 3 should be a good default. But having the option to configure it if 1-2 more levels are needed would be awesome.

Hi. I like the idea. Most of my configs are nested. 3 should be a good default. But having the option to configure it if 1-2 more levels are needed would be awesome.

Release 0.6.0 has been published with support for nested keys. By default only root level comments will be parsed, but you can inspect nested mappings by changing autoyaml_level configuration variable.


Fix active sync instantiation

@calvinjia PTAL, this fixes active sync instantiation

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/3781/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.0 please.


chore(deps): update sigstore/cosign-installer action to v3

This PR contains the following updates:

Package
Type
Update
Change

sigstore/cosign-installer
action
major
v2.8.1 -> v3.0.1

Release Notes

sigstore/cosign-installer
v3.0.1
Compare Source
What's Changed

make cosign v2.0.0 default version by @developer-guy in https://github.com/sigstore/cosign-installer/pull/109

Full Changelog: https://github.com/sigstore/cosign-installer/compare/v3.0.0...v3.0.1
v3.0.0
Compare Source
Breaking change
Cosign v2 has some breaking changes. Please check those: https://blog.sigstore.dev/cosign-2-0-released/
What's Changed

test: add logs when downloading the public keys by @hectorj2f in https://github.com/sigstore/cosign-installer/pull/106
Add support to install v2 and any other cosign release candidate by @hectorj2f in https://github.com/sigstore/cosign-installer/pull/105
v2.0.0 release by @sabre1041 in https://github.com/sigstore/cosign-installer/pull/108

New Contributors

@hectorj2f made their first contribution in https://github.com/sigstore/cosign-installer/pull/106
@sabre1041 made their first contribution in https://github.com/sigstore/cosign-installer/pull/108

Full Changelog: https://github.com/sigstore/cosign-installer/compare/v2...v3.0.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This is probably going to break stuff...
Not until I publish a release in this repo though. Sorry, future me.


Reduce type conversion on Timeflake::as_u128(...)

Description
Seems there's no reason to convert timestamp as u64 than convert to u128.
Since the ret is u128.
Also tested this with cargo test.
Changes.

Remove 2 times of type conversion on code.

Story
Found above issue while port to 64bit sized version.

Thanks for pointing my mistake, patch looks good.


Getting Parceler to execute on a lib project and the app itself?

I have a project that uses a shared library project. The library is where the majority of the Parcelables live. I've migrated to Parceler, so far so good :)
We also have some code in the app project that I'd like to use Parceler on as well.
Everything compiles and runs, but it appears that the Parcels aren't being generated for the classes in the App project though:
01-02 11:04:20.060  26765-26765/com.etsy.android.soe.alpha E/AndroidRuntime﹕ FATAL EXCEPTION: main
org.parceler.ParcelerRuntimeException: Unable to create ParcelableFactory for foo.bar.AClass
at org.parceler.Parcels$ParcelCodeRepository.get(Parcels.java:198)
at org.parceler.Parcels.wrap(Parcels.java:85)
at org.parceler.Parcels.wrap(Parcels.java:69)
...
I've tried having the provided statement in either gradle files, that seems to determine which project will have Parcels generated... I can't have it in both, I get a dex error.
Any idea what I'm doing wrong?

That's strange.  Can you verify a Parcelable wrapper is generated for your AClass in your library?  Like: AClass$$Parcelable

The library Parcelable wrappers are generated, but there are none in the App Project itself,
AClass$$Parcelable doesn't exist.

What Parcelable wrappers are generated?  It sounds like a wrapper for AClass isn't generated.

With POJOS annotated with @Parcel in both the Library Project and the App Project:

If I have the compile/provided statements only in the Library's build.gradle, compilation succeeds. $$Parcel wrappers are generated for all the Library POJOs. But none of the POJOs in the App project.
I'll see exceptions like this upon calling Parcels.wrap on App Project POJOS:
org.parceler.ParcelerRuntimeException: Unable to create ParcelableFactory for   com.android.lib.models.LibPojo

If I move the "provided" statement  to the App Project, compilation succeeds. $$Parcel wrappers are only generated for the App project POJOS, but not the Library POJOS. I'll see the same exception above whenever the Parcels.wrap/unwrap is used on a Lib POJO

If I add the compile/provided statements to the build.gradle to both the App Project and the library project I get a dex error:

Error:Gradle: Execution failed for task ':dexAlphaDebug'.

com.android.ide.common.internal.LoggedErrorException: Failed to run command:
/Users/sbirksted/development/android-sdk-macosx/build-tools/21.1.1/dx -JXmx2g --dex --no-optimize --output /MyProject/build/intermediates/dex/alpha/debug --input-list=/MyProject/build/intermediates/tmp/dex/alpha/debug/inputList.txt
Error Code:
2
Output:
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define Lorg/parceler/Parceler$$Parcels$1;
at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
at com.android.dx.command.dexer.Main.runMonoDex(Main.java:302)
at com.android.dx.command.dexer.Main.run(Main.java:245)
at com.android.dx.command.dexer.Main.main(Main.java:214)
at com.android.dx.command.Main.main(Main.java:106)

Not sure if this is something to do with our setup or Parceler.

Is your library an .aar?  I'm not sure if this is any different than a .jar
dependency in terms of class lookup.  Parceler will resort to a
getClass() call if it can't find the parceler factory in the
Parceler$Parcels mapping.
On Jan 7, 2015 10:11 AM, "bjornlate"<EMAIL_ADDRESS>wrote:

With POJOS annotated with @Parcel https://github.com/Parcel in both the
Library Project and the App Project:

If I have the compile/provided statements only in the Library's
build.gradle, compilation succeeds. $$Parcel wrappers are generated for all
the Library POJOs. But none of the POJOs in the App project.
I'll see exceptions like this upon calling Parcels.wrap on App Project
POJOS:
org.parceler.ParcelerRuntimeException: Unable to create
ParcelableFactory for com.android.lib.models.LibPojo
2.
If I move the "provided" statement to the App Project, compilation
succeeds. $$Parcel wrappers are only generated for the App project POJOS,
but not the Library POJOS. I'll see the same exception above whenever the
Parcels.wrap/unwrap is used on a Lib POJO
3.
If I add the compile/provided statements to the build.gradle to both
the App Project and the library project I get a dex error:
Error:Gradle: Execution failed for task ':dexAlphaDebug'.
com.android.ide.common.internal.LoggedErrorException: Failed to run
command:
/Users/sbirksted/development/android-sdk-macosx/build-tools/21.1.1/dx
-JXmx2g --dex --no-optimize --output
/MyProject/build/intermediates/dex/alpha/debug
--input-list=/MyProject/build/intermediates/tmp/dex/alpha/debug/inputList.txt
Error Code:
2
Output:
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define
Lorg/parceler/Parceler$$Parcels$1;
at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
at com.android.dx.command.dexer.Main.runMonoDex(Main.java:302)
at com.android.dx.command.dexer.Main.run(Main.java:245)
at com.android.dx.command.dexer.Main.main(Main.java:214)
at com.android.dx.command.Main.main(Main.java:106)
Not sure if this is something to do with our setup or Parceler.
—
Reply to this email directly or view it on GitHub
https://github.com/johncarl81/parceler/issues/63#issuecomment-69054832.

putting the provided statement in a gradle file seems to trigger annotation processing.
The catch here is the Parceler$$Parcels.java output result needs to be the union of both projects.
Right now its either the classes in the App Project:
public Parceler$$Parcels() {
    map$$0 .put(ChildOfBaseObject.class, new Parceler$$Parcels.ChildOfBaseObject$$Parcelable$$0());
    map$$0 .put(ChildOfChildOfBaseObject.class, new Parceler$$Parcels.ChildOfChildOfBaseObject$$Parcelable$$0());
}

Or the classes in the Lib project.
public Parceler$$Parcels() {
    map$$0 .put(BaseObject.class, new Parceler$$Parcels.BaseObject$$Parcelable$$0());
}

But what I need is this:
public Parceler$$Parcels() {
    map$$0 .put(BaseObject.class, new Parceler$$Parcels.BaseObject$$Parcelable$$0());
    map$$0 .put(ChildOfBaseObject.class, new Parceler$$Parcels.ChildOfBaseObject$$Parcelable$$0());
    map$$0 .put(ChildOfChildOfBaseObject.class, new Parceler$$Parcels.ChildOfChildOfBaseObject$$Parcelable$$0());
}

I uploaded the test project, if you care to check it out and reproduce the issue
https://github.com/bjornlate/parceler-library-project-test
The processor could output a file of all the annotated classes it adds to the Parceler$$Parcels constructor.
If the processor is run again in the project it would check for existence of that file, then add put statements for each class listed in the file...

Great!  I will take a look this evening.

@bjornlate I was able to make your project work by removing the parceler annotation processor from the library class and simply referencing the BaseObject class from the android project via @ParcelClass(BaseObject.class).  I've issued a PR to you with this change so you can review.

Thanks @johncarl81 I'll check it out

@bjornlate, did this work for you?

@bjornlate, feel free to reopen if this is still an issue.

Just for history's sake: there was a change (https://github.com/johncarl81/parceler/commit/235e74596aad1d65c88fb74bcb069d57cb2fc39d) in Parceler 1.1.2 which doesn't generate Parceler$$Parcels any more, instead it only uses this logic to resolve the generated code:
private static String buildParcelableImplName(Class clazz) {
    return clazz.getName() + "$$" + "Parcelable";
}


Revert broken release

Revert "[maven-release-plugin] prepare for next development iteration"
Revert "[maven-release-plugin] prepare release v1.36.1"

What does this PR do?
Checklist

[x] This is something else

[ ] I have updated CHANGELOG.asciidoc

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-04-11T12:15:49.123+0000

Duration: 14 min 28 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Eastern European locations unicode cause a crash.

Some locations cause the following crash.
Traceback (most recent call last):
File "./elodie.py", line 345, in
main()
File "C:\Python27\lib\site-packages\click\core.py", line 716, in call
return self.main(*args, **kwargs)
File "C:\Python27\lib\site-packages\click\core.py", line 696, in main
rv = self.invoke(ctx)
File "C:\Python27\lib\site-packages\click\core.py", line 1060, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "C:\Python27\lib\site-packages\click\core.py", line 889, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Python27\lib\site-packages\click\core.py", line 534, in invoke
return callback(*args, **kwargs)
File "./elodie.py", line 115, in _import
trash, allow_duplicates)
File "./elodie.py", line 66, in import_file
print('%s -> %s' % (_file, dest_path))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u015b' in position 88: ordinal not in range(128)
Location.json
[{"lat": 49.7838611111111, "name": {"default": "Przemy\u015bl", "city": "Przemy\u015bl", "state": "podkarpackie", "country": "Polska"}, "long": 22.7677916666667}]

Thanks for reporting. Could you email the photo to jaisen (at) github username (dot) come?

Sent!
Thanks for all the help.

Hi, I have the same bug - cant process pictures - getting the same error message as OP.
Traceback (most recent call last):   File "./elodie.py", line 345, in <module>     main()   File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 716, in __call__     return self.main(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 696, in main     rv = self.invoke(ctx)   File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 1060, in invoke     return _process_result(sub_ctx.command.invoke(sub_ctx))   File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 889, in invoke     return ctx.invoke(self.callback, **ctx.params)   File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 534, in invoke     return callback(*args, **kwargs)   File "./elodie.py", line 115, in _import     trash, allow_duplicates)   File "./elodie.py", line 64, in import_file     media, allowDuplicate=allow_duplicates, move=False)   File "/root/elodie/elodie/filesystem.py", line 376, in process_file     self.create_directory(dest_directory)   File "/root/elodie/elodie/filesystem.py", line 45, in create_directory     if os.path.exists(directory_path):   File "/usr/lib/python2.7/genericpath.py", line 26, in exists     os.stat(path) UnicodeEncodeError: 'ascii' codec can't encode character u'\u0144' in position 32: ordinal not in range(128)
Can You help please!
kind regards,
Piotr

I get the same error except in the end it's like that
return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: 'charmap' codec can't encode characters in position 34-38: character maps to

Had the same problem with Python 2.7 on Win 10. Switching to Python 3.6 environment solved it.
Looks like the problem is on line 63 of elodie.py, FILESYSTEM.process_file, when it creates the dest_path with unicode characters.

Had the same problem with Python 2.7 on Win 10. Switching to Python 3.6 environment solved it.
Looks like the problem is on line 63 of elodie.py, FILESYSTEM.process_file, when it creates the dest_path with unicode characters.

Could you please share how you switched to Python 3.6? Installing it does not seem to be enough. I tried to run it on a system without Python2 and create a symlink but it wont run.

Could you please share how you switched to Python 3.6? Installing it does not seem to be enough. I tried to run it on a system without Python2 and create a symlink but it wont run.

I've meant that I've installed elodie and ran it with a separate python3 installation, instead of running it with python2.
What is the error you are getting? Did you do pip3 install -r requirements.txt on the cloned repository before running it?

Thanks @the-lay
Another thing I had to do was change "python" in the Elodie.py to "python3" and works fine.


CXXCBC-25: keep scope and collection separate in document_id

I decided to do it because I want to control construction, and hide fields from direct modification into "private" section. Also it helped during refactoring :) as compiler complained more.

So document_id is immutable.  I see :)


Enabled Site Multilanguage with Json or another format for I18n

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code
// If relevant, paste all of your challenge code in here

Screenshot

@pcimagenca the .json files do have areas that allow internationalization. Are you having issues changing the language settings? I'm not understanding your issue.

Closing as stale. Please feel free to reopen with a detailed description of the issue. Thanks and happy coding!


Update colour scheme to match UI mockup

Changed colours for relevant components.
Colour scheme:
Base Colour: #171923
Even Person Card: #252838
Odd Person Card: #32374d

Codecov Report
Base: 65.08% // Head: 65.08% // No change to project coverage :thumbsup:

Coverage data is based on head (aa08504) compared to base (7474b24).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #91   +/-   ##
=========================================
  Coverage     65.08%   65.08%
  Complexity      463      463
=========================================
  Files           100      100
  Lines          1521     1521
  Branches        165      165
=========================================
  Hits            990      990
  Misses          492      492
  Partials         39       39

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

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


Clarify how to use Union Function in CQD

The method to use the "Union function" described here https://docs.microsoft.com/en-us/skypeforbusiness/management-tools/call-quality-dashboard/use#what-does-union-do is not clear. By putting 1 piece of common text into multiple filter fields, thereby you force an "or" to happen on those sets vs the default of each filter in the list being an "and" type.
For example, if I want to have a filter for classified poor, or rated poor, I would put 1 piece of matching text in both of those filters in the Union field of the filter.

@StainlessSteele Hi! Thanks for submitting feedback. Could you please link the article you would like this content to be included on? Thanks.

This page https://docs.microsoft.com/en-us/skypeforbusiness/management-tools/call-quality-dashboard/use#what-does-union-do However, the content there should also be merged and updated here https://docs.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard

@StainlessSteele Thank for reaching out. The second article was updated in the interim recently, please confirm.

@StainlessSteele We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

here you will find more information
https://youtu.be/2CiBBmnnEaQ?t=1309
Minute 21:49


Testing: flaky test

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

Used for investigating the flaky test, done now


translucent render

When I use SpriteRendererAuthoriing and there is a translucent part in the texture, the translucent part cannot be displayed. How can I solve this problem?

Hi! I guess you would need to rewrite shader a bit, because whole project aiming pure performance and translucent is evil in terms  of performance.


how to auto load Entities?

I have a polymorphic model commentable
how do I represent commentable ?
class Comment < Base
      expose :sender, using: API::Entities::User
      expose :commentable // how to auto load entity with model Post, Article, or anything else?
      expose :content
end

use const_get
expose :notifiable

def notifiable
    API::Entities.const_get(object.notifiable_type).
                        represent(object.notifiable, serializable: true)
end

Is this something we want in the README? Feel free to contribute.


Add 8_Puzzle Game

8_Puzzle Game
PR Description 📜
An interactive 8-puzzle game built with HTML, CSS, and JavaScript. The objective of the game is to arrange the tiles in numerical order by sliding them into the empty space.
Fixes #4637

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @katarianikita2003 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit , please review

Thank you  @katarianikita2003 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


"This overload of nonzero is deprecated"

🐛 Bug

A change in torch\nn\functional might have change usability of the nonzero function used in fasterrcnn_resnet50_fpn. This produces a warning and slows down processing.
To Reproduce
Steps to reproduce the behavior:

torchvision.models.detection.fasterrcnn_resnet50_fpn(pretrained=True)

Produces the following message
C:\ProgramData\Anaconda3\lib\site-packages\torch\nn\functional.py:2854: UserWarning: The default behavior for interpolate/upsample with float scale_factor will change in 1.6.0 to align with other frameworks/libraries, and use scale_factor directly, instead of relying on the computed output size. If you wish to keep the old behavior, please set recompute_scale_factor=True. See the documentation of nn.Upsample for details.
warnings.warn("The default behavior for interpolate/upsample with float scale_factor will change "
..\torch\csrc\utils\python_arg_parser.cpp:756: UserWarning: This overload of nonzero is deprecated:
nonzero(Tensor input, *, Tensor out)
Consider using one of the following signatures instead:
nonzero(Tensor input, *, bool as_tuple)
Expected behavior

The warning is not expected and there is a considerable slowdown compared with previous iterations. I cannot quantify this properly but I have noticed that a task that took +- 5 minutes now takes more than 10.
Environment
Please copy and paste the output from our
environment collection script
(or fill out the checklist below manually).
You can get the script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

PyTorch / torchvision Version (e.g., 1.0 / 0.4.0): pytorch 1.5.0   torchvision 0.5.0
OS (e.g., Linux): Windows
How you installed PyTorch / torchvision (conda, pip, source): conda
Build command you used (if compiling from source): conda install pytorch==1.5.0 torchvision==0.5.0 cudatoolkit=10.0 -c pytorch
Python version:3.7
CUDA/cuDNN version: py3.7_cuda102_cudnn7_0
GPU models and configuration:nvidia GeForce GTX 1050
Any other relevant information:

Additional context

Thanks for opening the issue!
I would be surprised that the warning would account for such a large slowdown, but changing the code to use the non-deprecated codepaths sounds good to me.
A PR fixing this would be awesome!

Facing the same issue with torchvision.models.detection.keypointrcnn_resnet50_fpn pretrained network. Processing speed is reduced greatly because of the changes in torch.nn.functional

I runned collect_env.py and get printed output.
Now, what should I copy and where should I paste it?

@sykimm copy and paste on github the output of collect_env.py, although I'm not sure if the slowdown is due to the nonzero warning or the Upsample warning

@fmassa I'm new to this but I'm keen on contributing and perhaps being able to fix this issue. Having checked repository and the warning, would simply setting  recompute_sclae_factor = True in the forward function help?

@java-abhinav07 yes, it would help, but one would need to verify that it doesn't change the behavior of the code so that old models still give the same result

@fmassa I'll try it locally and get back

Managed to remove recompute_scale_factor warning. However, the TAT is still high possibly because I'm still getting the overload of nonzero warning. Will create a PR once that's fixed, any suggestions for where the problem might be with this?
_
> /pytorch/torch/csrc/utils/python_arg_parser.cpp:756: UserWarning: This overload of nonzero is deprecated:
>         nonzero(Tensor input, *, Tensor out)
> Consider using one of the following signatures instead:
>         nonzero(Tensor input, *, bool as_tuple)

_

So seems like the overhead is in nonzero, could you try to see if you could first send a PR changing the nonzero behavior to be the non-deprecated one?

Yes, will fix it asap and send in a PR. Albeit, I did take a quick look and it seems like torch.nonzero has been used at multiple places, having changed the same at a couple of instances the time (for my application) was reduced by 0.5s.

https://github.com/pytorch/vision/pull/2314
@fmassa Kindly review the PR. This fixes the non-zero depreciation warning issue, thanks! and sorry about the delay

Fixed by https://github.com/pytorch/vision/pull/2705

ValueError: All bounding boxes should have positive height and width. Found invaid box [500.728515625,<PHONE_NUMBER>882812,<PHONE_NUMBER>5,<PHONE_NUMBER>470703] for target at index 0.
i am getting this error using detecto for object detection

@kashf99 this is the same as https://github.com/pytorch/vision/issues/2740.

@java-abhinav07 Thanks for helping to improve the code. Did you already fix the recompute_scale_factor warning?

@java-abhinav07 Thanks for helping to improve the code. Did you already fix the recompute_scale_factor warning?


Deadlock when the right conditions are met

Hey @alexandru, I finally managed to reproduce that weird bug I mentioned. Looks like it requires you to block a Task inside of another Task, where the inner Task uses onErrorHandleWith and both are run on the same scheduler. Changing any of those conditions seems to fix the problem.
...I have no idea what's going on here, but hopefully you'll have a better idea. The repo where it's reproduced is linked at the bottom of this comment, the good stuff is in Main.scala
https://github.com/Diagoras/monix-bug-example

Thanks @Diagoras, will take a look.


Add 0.5.0 of IDL

Addresses #215

Only a single version statement can appear per/file. This was stated in the spec, but not enforced by the loader. Allowing only a single version statement per/file makes models simpler to parse and removes confusion if multiple statements appear.
Metadata must be defined after a version (if any) and before a namespace statement (if any). This change makes metadata appear in models more consistently and makes it easier to implement parsers.
Only a single namespace can appear per IDL file. Allowing only a single namespace makes models easier to parse and more consistent.
Use statements must appear after a namespace statement. This was the only way examples were presented in the spec, but it wasn't explicitly called out or enforced by the parser. This makes it much easier to understand the semantics of the use statement and makes it easier to implement parsers.

These changes are implemented in a backward compatible way. If a version of 0.4.0 is specified in a model explicitly, then none of the above constraints are enforced. If no version is set and any of the above constraints are violated, then a warning is emitted noting that the violation will not be allowed in future versions of Smithy. If a version of 0.5.0 is explicitly set, then the above violations will cause an ERROR and fail a model build.

Squashed and merged into add-0_5_0-format


Added Django 1.10 support

Seems like the only thing needed is more test cases. Please correct me if I'm wrong.

Changes Unknown when pulling f2b6dab1cb514768f173782b94d0fa650a9bca70 on ovidner:master into ** on st4lk:master**.

Changes Unknown when pulling 5e132e081c07bdff7ace7daaa785f46ce90b6751 on ovidner:master into ** on st4lk:master**.

Django 1.7 is no longer supported by DRF and fails tests, so I dumped it from the list of supported Django versions and changed the README accordingly.

Changes Unknown when pulling 7e189aac7be6254c1bfc575fad8faf99223b3bf7 on ovidner:master into ** on st4lk:master**.

Thanks!

Finally uploaded to pypi v1.0.0


How to build mocha with webpack

For some reason I need to bundle mocha with webpack.
I see browser section in mocha package.json so it looks like webpack should exclude node specific require's.
But when i try var mocha = require('mocha') I'm getting warnings:
WARNING in ./~/mocha/lib/mocha.js
Critical dependencies:
151:20-37 the request of a dependency is an expression
183:17-30 the request of a dependency is an expression
220:26-39 the request of a dependency is an expression
 @ ./~/mocha/lib/mocha.js 151:20-37 183:17-30 220:26-39

WARNING in ./~/mocha/lib/interfaces/bdd.js.orig
Module parse failed: /Users/vitalets/projects/autotester/node_modules/mocha/lib/interfaces/bdd.js.orig Unexpected token (93:0)

and errors:
ERROR in ./~/mocha/~/growl/lib/growl.js
Module not found: Error: Cannot resolve module 'fs' in /Users/vitalets/projects/autotester/node_modules/mocha/node_modules/growl/lib
 @ ./~/mocha/~/growl/lib/growl.js 8:9-22

Can anybody help to fix this?
How to correctly use browser-entry.js?
thanks!

For some reason I need to bundle mocha with webpack

Can we start there? What is that reason and could whatever you want to achieve be done without? The amount of scope creep webpack adds, like having to bundle your test runner seems like the real issue to me here

If you're using mocha in Node, then you don't need to bundle.  (More on this if you need it)
If you're using mocha in the browser for browser tests, then I'd recommend doing something like this:
// webpack.config.js
plugins: [
  ...
  entry: ["./test/all.js"],
  new HtmlWebpackPlugin({
    cache: true,
    filename: "test/index.html",
    showErrors: true,
    template: "./test/support/index.html",
    title: "Mocha Browser Tests",
  }),
  ...
],

// test/all.js
const context = require.context(
  "../src",       // Root directory
  true,           // Recursive
  /.+\.test\.js$/ // Test pattern
);

// Require each within build
context.keys().forEach(context);

<!DOCTYPE html>

    <meta charset="utf-8">
    <title><%= htmlWebpackPlugin.options.title %></title>

    <link<EMAIL_ADDRESS>rel="stylesheet" />

@Munter

For some reason I need to bundle mocha with webpack

Can we start there? What is that reason and could whatever you want to achieve be done without? The amount of scope creep webpack adds, like having to bundle your test runner seems like the real issue to me here

I'm building chrome extension that allows to run tests with mocha.
I achieved it without bundling mocha via manually re-loading it as script tag every time I need.
But my intention was to bundle it as all other files in project.
@ericclemmons
Thanks for HtmlWebpackPlugin, will have a look on it.
Anyway, guys, could you shortly explain for what reason there is browser-entry.js and how you use it?

@vitalets That's the entry point for Browserify.  It's used when building the browser version of mocha (./mocha.js; not ./lib/mocha.js). It's also used if you are attempting to bundle Mocha itself (via Browserify), because it's in the browser field of package.json.
Webpack may not respect the browser field in package.json; if it doesn't, you could try to point it at this file instead of index.js.  But there's likely Browserify-specific stuff tangled up in there, and you might also find some conditional require statements that Webpack won't like.
Regardless, the entry point should be browser-entry.js and not index.js if you are attempting to bundle yourself (though it's still unclear to me why anyone would really need to do this).  Otherwise, ./mocha.js is already built for the browser.
I'm going to close this, as I don't think there's anything to be done here, but feel free to ask more questions here or in Gitter.

@boneskull thanks for explanation!
AFAIK webpack supports browser field in package.json but when I tried where are some other errors with conditional requires as you said.
Will contact you in gitter if needed!

@vitalets webpack only supports using the browser field in as an alias of main, not the full browser object as defined in the spec. https://github.com/webpack/webpack/issues/151#issuecomment-464551484
browserify supports the spec, hence why builds work fine using that.

I struggled with some of the same issues expressed on this thread, so here's my solution just in case it helps someone else.
My requirements were that I could run the tests using karma but I also had a webpage that allowed me to run the mocha tests in a browser.
I did manage to get something working using an html page based on the html that @ericclemmons posted. However, I was pretty unhappy with my approach because all my other modules were being bundled nicely with webpack, but then I had a few files that were sitting outside of that, and I was using things like the webpack copy plugin to move mocha.js to the right place in the build and it all looked wrong.
So, I wanted to load mocha using webpack so it was managed in the same way as all my other modules (I think that's a fairly normal thing to want, despite some of the comments on this thread). It would be straightforward to shim mocha using exports-loader if you only wanted to run in a browser, but karma-mocha provides its own version of mocha which will conflict with the version pulled in using webpack if you do this. I did finally get it working by:

Importing mocha/browser-entry instead of plain mocha
Importing the mocha js and css in a 'mocha-wrapper' module which also called mocha.setup
Importing this wrapper module conditionally, only if the describe function is not in global scope already (if yes, then we're running with karma so no need to load mocha ourselves; if no, we're running in the webpage so load mocha using webpack in the normal way)

@tstibbs - Would you mind posting a link to your working project somewhere?

@tstibbs - Would you mind posting a link to your working project somewhere?

@rafikhan You'll have to have a dig around, but the following should be most of what you need:
https://github.com/tstibbs/geo-bagging/blob/master/ui/test/suite/mocha-wrapper.js
https://github.com/tstibbs/geo-bagging/blob/master/ui/test/suite/suite.js#L8
https://github.com/tstibbs/geo-bagging/blob/master/ui/webpack.config.cjs#L185
(to be clear I'm not saying my approach is right or even valid, I'm just saying it appears to be working for me - on a small personal project with just a handful of tests)

Applying directly @aovchinn's solution still displayed in console the error:
Critical dependency: the request of a dependency is an expression

However I was successful using import "script-loader!mocha/mocha-es2018" (after adding the "script-loader" npm dependency).


Deno KV API - Transactions - example incorrect "check"

<EMAIL_ADDRESS>
Along with these actions, key+versionstamp pairs are provided as a condition for the transaction's success.

...
  const senderKey = ["account", sender];
  const receiverKey = ["account", receiver];
...
    if (senderRes.value === null) throw new Error(`Account ${sender} not found`);
    if (receiverRes.value === null) throw new Error(`Account ${receiver} not found`);
...
    res = await kv.atomic()
      .check(senderKey) // Ensure the sender's balance hasn't changed.
      .check(receiverKey) // Ensure the receiver's balance hasn't changed.
      .set(senderKey, newSenderBalance) // Update the sender's balance.
      .set(receiverKey, newReceiverBalance) // Update the receiver's balance.
      .commit();

Those keys do not have a timestamp - the timestamp would have to be the result of a query.
Should the check lines be the following?
      .check(senderRes) // Ensure the sender's balance hasn't changed.
      .check(receiverRes) // Ensure the receiver's balance hasn't changed.

Thanks for reporting. This has been fixed in #632 (ref. https://deno.com/manual@main/runtime/kv/transactions ) (The fix will be released soon)


Request: support --max-concurrency=auto

There is a pytest plugin for running tests concurrently using multiprocessing. That plugin supports automagically inferring the number of parallel processes to spawn: pytest -n auto.
I know promptfoo supports concurrency using --max-concurrency (defaulted as of 0.55.0 to 4).

What type of concurrency does promptfoo use? Is it multiprocessing?
Can we support --max-concurrency=auto, and do basic machine-tailored inference for an optimal amount of concurrency?

Evals are I/O bound with respect to the LLM APIs, so in practice it is not
desirable to set it based on your number of CPUs but instead your
network, rate limits, etc.  The concurrency uses node's event loop as
opposed to multiprocessing.
On Mon, Apr 29, 2024 at 10:55 PM James Braza @.***>
wrote:

There is a pytest plugin for running tests concurrently using
multiprocessing. That plugin supports automagically inferring the number of
parallel processes to spawn: pytest -n auto.
I know promptfoo supports concurrency using --max-concurrency (defaulted
as of 0.55.0 to 4).

What type of concurrency does promptfoo use? Is it multiprocessing?
Can we support --max-concurrency=auto, and do basic machine-tailored
inference for an optimal amount of concurrency?

—
Reply to this email directly, view it on GitHub
https://github.com/promptfoo/promptfoo/issues/737, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLYJUAEETTZI6FWRGSS2DY74W4FAVCNFSM6AAAAABG7SRGKKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TANJWGU3DCNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Okay I see. So I guess it's not really feasible to auto-infer a concurrency count.
I will open a docs PR to at least add that the concurrency is managed via a single process event loop


refine problem

When I train the model using python main.py , it works well.
But when I try to refine the model, using  python main.py --refine --lr 1e-5 --reload --previous_dir
it reports error：
Traceback (most recent call last):
File "main.py", line 225, in
loss = train(opt, actions, train_dataloader, model, optimizer_all, epoch)
File "main.py", line 23, in train
return step('train', opt, actions, train_loader, model, optimizer, epoch)
File "main.py", line 94, in step
loss.backward()
File "D:\Anaconda\envs\pose\lib\site-packages\torch_tensor.py", line 307, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "D:\Anaconda\envs\pose\lib\site-packages\torch\autograd_init_.py", line 156, in backward
allow_unreachable=True, accumulate_grad=True)  # allow_unreachable flag
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [64, 1024]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead. Hint: the backtrace further above shows the operation that failed to compute its gradient. The variable in question was changed in there or anywhere later. Good luck!
I can't fine the problem, I almostly use with torch.autograd.set_detect_anomaly(True): , but still can't find the crux.

See https://github.com/Vegetebird/StridedTransformer-Pose3D/issues/19#issuecomment-1276159365

See #19 (comment)

Thank you! Using torch==1.7.1 could avoid this problem, and  "nn.Relu(inplace=True)" couldn't.


KCP admin can create resources in workspaces that don't exist

Describe the bug
The KCP admin can create resources in workspaces that don't exist. It might be good to have some guardrails against it even for the admin, or at least an entry in the log.
To Reproduce
Steps to reproduce the behavior:

Modify the kubeconfig to point to an org:workspace that doesn't have a corresponding workspace resource.
Create any resource in the non-existent workspace.

Expected behavior
The resource creation should be denied or the circumstance logged since it's not within the context of an existing workspace.

Starting a slack thread that we can summarize back here, but roughly:

If we allow admins to create resources outside workspaces, we need a way for admins to clean up mistakes
We may want to support precreating resources in a workspace via this mechanism, but we DEFINITELY don't want to leave resources from previous workspaces around when new workspaces are created

More chat here https://kubernetes.slack.com/archives/C021U8WSAFK/p1646758726804289

I think this situation is by design and I don't think we want to invest in changing this. System:masters group membership is required to bypass workspace authorization. This is basically what root is in Linux. Ability to shoot yourself into the foot is part of that role.
In the future, we will have org admins and kcp admins as organizational roles (think of a role for service provider setup). These won't be system:masters, but would intentionally switch to some shard admin role to the privileged operations described in this issue. In other words: "admins are not admins" is something we will see much more than in Kube. I.e. the described danger won't be real in practice for normal administration of kcp.

+1 for closing if nobody objects.


Reference image feature

Hello I am blown away by how production worthy your tool can be!
Only thing I'd like is a image to texture feature instead of text to texture.
Is this already possible if not do you have plans for this?

Yes, you can achieve image-to-material by using methods such as the IP-Adapter, which is quite easy to implement. However, further testing is required to ensure stability.

Yes, you can achieve image-to-material by using methods such as the IP-Adapter, which is quite easy to implement. However, further testing is required to ensure stability.

Hi , how to use IP-Adapter to merge your project ,can u give some ideas

basic sd model is loaded in the method configure(self) in dreammat_guidance.py，you can load ip-adapter or other diffusers supported adapters like lora here


processStaking and processRedemption fallback

for v0.9.1 we put a fallback to execute processStaking and processRedemption by Registrar in advance of separating the signature confirmation from the transaction formulation.
addresses #8
for forcing cost

[x] processStaking by Registrar
[x] processRedemption by Registrar
[x] unit test processStaking
[ ] processRedemption

@jasonklein this needs to applied for processRedemption still


problem mapping JSON with nested arrays into RDF

New issue based on discussion in #18
@asotona said:

The root cause is in inability of the JSONPath to traverse to "parent" node. Maybe you can help me, however I don't see a way to use CARML (and also any other RML utilising JSONPath) to map JSON with nested arrays into RDF.
I see no way to map it from top to down nor from bottom up, where there is an array between parent and child objects. Maybe we can close this issue and create another one or change the subject.

@asotona could you provide an example JSON snippet and the RDF you wish to have created?


Build cmake with FT4222

Hi,
I want to use this library with FT4222, so I had to add FTDI4222=ON USBPLAT=ON.
What is command line please ?
I try  cmake .. -DFTDI4222=ON -DUSBPLAT=ON but it don't found library for FT4222
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Performing Test HAS_C__Wall
-- Performing Test HAS_C__Wall - Success
-- Performing Test HAS_C__Werror_main
-- Performing Test HAS_C__Werror_main - Success
-- Performing Test HAS_C__Wformat
-- Performing Test HAS_C__Wformat - Success
-- Performing Test HAS_C__Wmain
-- Performing Test HAS_C__Wmain - Success
-- Performing Test HAS_C__Wuninitialized
-- Performing Test HAS_C__Wuninitialized - Success
-- Performing Test HAS_C__Winit_self
-- Performing Test HAS_C__Winit_self - Success
-- Performing Test HAS_C__Werror_implicit
-- Performing Test HAS_C__Werror_implicit - Success
-- Performing Test HAS_C__Werror_missing_parameter_type
-- Performing Test HAS_C__Werror_missing_parameter_type - Success
-- Performing Test HAS_CXX__Wall
-- Performing Test HAS_CXX__Wall - Success
-- Performing Test HAS_CXX__Werror_main
-- Performing Test HAS_CXX__Werror_main - Success
-- Performing Test HAS_CXX__Wformat
-- Performing Test HAS_CXX__Wformat - Success
-- Performing Test HAS_CXX__Wmain
-- Performing Test HAS_CXX__Wmain - Success
-- Performing Test HAS_CXX__Wuninitialized
-- Performing Test HAS_CXX__Wuninitialized - Success
-- Performing Test HAS_CXX__Winit_self
-- Performing Test HAS_CXX__Winit_self - Success
-- Performing Test HAS_CXX__Wnon_virtual_dtor
-- Performing Test HAS_CXX__Wnon_virtual_dtor - Success
-- Performing Test HAS_CXX__Woverloaded_virtual
-- Performing Test HAS_CXX__Woverloaded_virtual - Success
-- Performing Test HAS_CXX__Wreorder
-- Performing Test HAS_CXX__Wreorder - Success
CMake Warning at CMakeLists.txt:93 (message):

Install git to compile a production libmraa!

-- INFO - libmraa Version v1.5.1
-- INFO - cmake Version 3.5.1
-- INFO - Target arch is x86_64
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.12", minimum required is "2.7")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable exact version "2.7.12")
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.5.2", minimum required is "3")
-- Could NOT find PythonLibs (missing:  PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS) (Required is exact version "3.5.2")
-- INFO - Adding onewire backend support
-- INFO - Adding support for platform ALL
-- INFO - Adding support for all platforms
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
INFO - Adding x86 platforms
-- INFO - Adding USB platforms
CMake Error at src/CMakeLists.txt:146 (message):
Enabled FTDI4222 support but library not found
INFO - FTDI4222
-- Found SWIG: /usr/bin/swig3.0 (found version "3.0.8")
PYTHON2 attempting to build!
-- Found Nodejs: /usr/bin/nodejs
INFO - Node version is 4.2.6
INFO - Node using v8 <IP_ADDRESS>
-- INFO - swig Version 3.0.8
-- INFO - CXX compiler Version GNU 5.4.0
-- INFO - Using V8 version > 3 so requiring C++11 compiler
-- INFO - install NODE modules to /usr/include/nodejs/lib/node_modules/mraa/
-- Configuring incomplete, errors occurred!
See also "/home/teosit/mraa-master/build/CMakeFiles/CMakeOutput.log".
See also "/home/teosit/mraa-master/build/CMakeFiles/CMakeError.log".
Thank you.

If you read here: https://github.com/intel-iot-devkit/mraa/blob/master/docs/ftdi_ft4222.md did you install the library from ftdi?

Libft4222 was not installed correctly, it work now thank you. But now when I test this program :
int
main(int argc, char** argv)
{
mraa_init();
//! [Interesting]
printf("MRAA Version: %s\n\n", mraa_get_version() );
mraa_spi_context spi;
spi = mraa_spi_init(0);
mraa_spi_mode(spi, MRAA_SPI_MODE0);
if (spi == NULL) {
printf("Initialization of spi failed, check syslog for details, exit...\n");
exit(1);
}
printf("SPI initialised successfully\n");

mraa_spi_frequency(spi, 10000);
mraa_spi_lsbmode(spi, 0);
uint8_t data[1] = { 0x03 };
uint8_t* recv;

recv = mraa_spi_write_buf(spi, data, 1);
printf("Writing -%i", data[0]);
printf("RECIVED-%i-\n", recv[0]);
usleep(100000);

mraa_spi_stop(spi);

}
And in my syslog :
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: libmraa version v1.5.1 initialised by user 'root' with EUID 0
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: Platform not supported, not initialising
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: libft4222.so not found, skipping
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: libmraa initialised for platform 'Unknown platform' of type 98
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: spi: no spi buses defined in platform
Nov 16 09:51:28 teo-System-Product-Name libmraa[7252]: spi: mode: context is invalid

Ok so that indicates mraa didn't manage to dlopen libft42222.so as done here: src/usb/ftdi_ft4222.c:121:    void *func = dlsym(libft4222_lib, symbol);
Where is libft4222.so on your system and has ldconfig been refreshed?

libft4222.so is on /usr/local/lib. I have juste made : sudo ldconfig and now in my syslog :
Nov 16 10:15:58 teo-System-Product-Name libmraa[8883]: libmraa version v1.5.1
initialised by user 'root' with EUID 0
Nov 16 10:15:58 teo-System-Product-Name libmraa[8883]: Platform not supported, not initialising
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT_GetDeviceInfoList returned 2 devices
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: mraa_ftdi_ft4222_init completed successfully
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT4222_GetVersion 42220200 01030178
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT4222_I2CMaster_Read failed for address 0x20. Code 50
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT4222_I2CMaster_Write failed address 0x27
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT4222_I2CMaster_Read failed for address 0x27. Code 50
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: FT4222_I2CMaster_Read failed for address 0x70. Code 50
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: libmraa initialised for platform 'Unknown platform + FTDI FT4222' of type 98
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: spi: no spi buses defined in platform
Nov 16 10:16:01 teo-System-Product-Name libmraa[8883]: spi: mode: context is invalid

ok well that looks much better. Uhm unfortunately SPI functionality isn't implemented in mraa for the FT4222 yet see docs/ftdi_ft4222.md. @whbruce do you have it stashed in a WIP branch or was it never done?
You may have to implement that part if you want to use it with mraa, although most of the ground work is already there so it shouldn't be too hard. We'd obviously welcome the contribution :)

I never had SPI connected sensors to test so didn't add support. Maybe @Propanu did some work on this?

Unfortunately I never added SPI support for the same reason: we had no need for SPI sensors for the demos that use the FT4222 expander.

Closing as probably a feature request at this point ;-) Sorry!


chore(main): release 0.24.0

:robot: I have created a release beep boop
0.24.0 (2023-03-22)
Features

chart: better lines (64ee6df)
settings: update default durations (22b019a)

Tests

settings: add test for DurationToSecondsString (42f3508)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/ecg_monitor/releases/tag/v0.24.0 :sunflower:


YouTube download failing with when time-continue is specified

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2019.07.14
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
[tom@tom-linux Music]$ youtube-dl -v -x --audio-format mp3 https://www.youtube.com/watch?time_continue=130&v=IYzlVDlE72
[3] 19781
[2]   Exit 1                  youtube-dl https://www.youtube.com/watch?time_continue=130
[tom@tom-linux Music]$ [debug] System config: ['--prefer-free-formats']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-x', '--audio-format', 'mp3', 'https://www.youtube.com/watch?time_continue=130']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.06.21
[debug] Python version 3.7.3 (CPython) - Linux-5.1.16-300.fc30.x86_64-x86_64-with-fedora-30-Thirty
[debug] exe versions: ffmpeg 4.1.3, ffprobe 4.1.3
[debug] Proxy map: {}
[generic] watch?time_continue=130: Requesting header
[redirect] Following redirect to https://www.youtube.com/
[generic] www.youtube: Requesting header
WARNING: Falling back on generic information extractor.
[generic] www.youtube: Downloading webpage
[generic] www.youtube: Extracting information
ERROR: Unsupported URL: https://www.youtube.com/
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/youtube_dl/YoutubeDL.py", line 795, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.7/site-packages/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.7/site-packages/youtube_dl/extractor/generic.py", line 3316, in _real_extract
    raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: https://www.youtube.com/

Description
When I download an url copied from genius.com (lyrics site), there is a time_continue argument specified. This argument causes youtube-dl to crash and produce weird errors. I expected youtube-dl to just use the v key instead of the first one.

https://github.com/ytdl-org/youtube-dl#video-url-contains-an-ampersand-and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command


Add metrics for Edgex to enhance the system monitor

Metrics and Log are two basic parts of a stable system. For enhancing the EdgeX's stability we should consider to monitor it in the future. The monitor would need to be provided metrics. So we should introduce the metrics infrastructure for it.
There are a few scenario where we could add metrics:

device data import count / rate;
support notification count / schedule count (trigger count)
export data count / rate;
....

Although, metrics and log sometimes can match the same goal(provide information to calculate/aggregate/analysis). But they are different, here is a good article described the difference between them.
I find a popular go metrics package : go-metrics, which can write metrics into InfluxDB. And using this (we can also implement a logger to write log into InfluxDB), we could integrate the metrics with InfluxDB's full technology stack (monitor, dashboard, storage, computing).
What's your idea? @jpwhitemn and @drasko

@yanghua good point here.
In Mainfllux we use metrics (and logs of course) for every service, something like this: https://github.com/mainflux/mainflux/blob/master/http/api/metrics.go, and those are then exported to Prometheus. We are using go-kit metrics because we are using go-kit in Mainfux, but go-metrics looks like a nice package and a good candidate for EdgeX.

@jpwhitemn if this idea been accepted, I will try to contribute a input plugin to Telegraf (The plugin-driven server agent for collecting & reporting metrics) for EdgeX. This work will promote EdgeX's connectivity with other ecosystem and make EdgeX easy to monitor.

Closing this issue per further discussion via Core WG and System Mgmt WG. There are several actionable items here which can be re-added to the issues list once we have decided on directions via the working groups.


fix: filter null args

closes #744

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


Universal Package task should store version number in env variable

Universal Packages can be uploaded without a predetermined version number, so save this information in an environment variable prior to completion

@zjrunner this change looks good to me - did you want to merge it or shall I?


Include table indexes in table_info (SQLDatabase)

Adds an optional flag to include table indexes in the table_info string that is passed to the prompt.
Haven't tested it much, but it seems to help nudge the model in choosing more optimal queries.
Can be particularly useful when paired with #2345

LGTM! Specially if its optional and defaults to False, it won't be impacting prompt size for most users 🙂


Error 500 on a specific page

https://vgmdb.info/album/82849
I wonder why.

Thanks for the report! The information panel seems to now have tr rows without any td cells, which the parsing logic failed at.

Thanks for the report! The information panel seems to now have tr rows without any td cells, which the parsing logic failed at.


how to get NSDate for Yesterday @ 9pm ?

The most simple way in UTC region is working directly with NSDate:
var date = NSDate(fromDate: (NSDate()-1.days), hour: 9, minute: 0, second: 0)


CONNECTION FAILURE
47964245314304:error:1417D0FC:SSL routines:tls_process_client_hello:unknown protocol:ssl/statem/statem_srvr.c:956:
write:errno=0

I don't know how to locate the problematic test case.
Probably near  "../test/recipes/70-test_sslextension.t ....."
The cipher list is 3 bytes long, thus rlistlen=3 is not a multiple of num=2
rlist = [0x00 0x00 0x2F]
Although this is a fatal error (with non-zero return code),
make test prints at the end:
All tests successful.
Files=90, Tests=479, 329 wallclock secs ( 2.94 usr  0.50 sys + 186.48 cusr 152.72 csys = 342.64 CPU)
Result: PASS
make[1]: Leaving directory `/home/ed/OPC/openssl'

It's also in the travis logs, but only in the 1.1.0-stable branch.

So there are several issues here:

SSL_get0_raw_cipherlist() doesn't seem to be consistent. It now always return TLS_CIPHER_LEN (== 2) even when there was a SSLv2 compatible client hello doing SSLv3+. In SSLv2 the cipher list was 3 bytes but in SSLv3 it's 2 bytes. The raw list that is actually returned has the 3 byte list like send in the client hello. So we either need to revert the commit (and probably some others) that made it always say there are 2 bytes per cipher, or actually return a list that has 2 byte ciphers.
We don't get this error in the master branch while the code that has the problem is just the same. So we might have lost test coverage somehow.
The test aborted, but we said everything is ok, which defeats the purpose of actually letting travis check this. I wonder which return code asan generates in that case.

I only use gcc not clang.
In gcc the application terminates with exit code 1 when that kind of error
happens the server should terminate immediately.
I think the return code is simply thrown away here:
    if ($self->serverconnects == 0) {
        die "serverpid is zero\n" if $self->serverpid == 0;
        print "Waiting for server process to close: "
              .$self->serverpid."\n";
        waitpid( $self->serverpid, 0);
    }

It would also be 1 if a memory leak happens, although that is only checked when
the application terminates normally.
You can change the exit code with ASAN_OPTIONS="exitcode=123" for instance.
I see the same error happening in master too.
Just use "make test V=1", why are you not seeing this?

Oh, that is the difference:
1.1.0 branch is built with these options:
export CONFIG_OPTS="no-asm enable-asan enable-rc5 enable-md2"
but master is built with slightly different options:
export CONFIG_OPTS="no-asm enable-asan enable-rc5 enable-md2 no-shared -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION"
the no-shared skips a few test cases...

SSL_get0_raw_cipherlist() doesn't seem to be consistent. It now always return TLS_CIPHER_LEN (== 2) even when there was a SSLv2 compatible client hello doing SSLv3+. In SSLv2 the cipher list was 3 bytes but in SSLv3 it's 2 bytes. The raw list that is actually returned has the 3 byte list like send in the client hello. So we either need to revert the commit (and probably some others) that made it always say there are 2 bytes per cipher, or actually return a list that has 2 byte ciphers.

The commit that caused it to always return 2 is not the source of the problem and reverting it will not solve the issue. Prior to 1.1.0 it asked the SSL_METHOD what the size of its ciphersuite encoding was. The SSLv2 method would return 3, and everything else would return 2. So, even in 1.0.2, if you have negotiated SSLv3+ with an SSLv2 compat ClientHello then SSL_get0_raw_cipherlist() will still return 2!!
The difference in 1.0.2 (that means it doesn't crash) is that version negotiation works completely differently. In 1.0.2 there is an initial stage on the front of the state machine which works out which SSL_METHOD needs to be used. If it receives a pure SSLv2 ClientHello it starts the SSLv2 method and if it receives an SSLv3+ ClientHello it uses an SSLv3+ method. However, if it receives an SSLv2 compat ClientHello but wants to use SSLv3+ then it constructs a "fake" SSLv3+ format ClientHello and then lets the SSLv3+ method handle it. It is the raw ciphersuite list from the "fake" ClientHello that gets stored away, so when you call SSL_get0_raw_cipherlist() in this scenario you're not actually getting the raw list at all - you are getting the "fake" list which has had all the SSLv2 ciphersuites removed from it and it has been converted into SSLv3+ format. Therefore the value of 2 for the length of a cipher is still correct.
In 1.1.0 things works completely differently and we no longer create a "fake" SSLv3+ ClientHello. We process the SSLv2 compat ClientHello directly. That means when you call SSL_get0_raw_cipherlist() you really do get the raw cipherlist in whatever format we received it in.
I think the correct solution here is to pre-process the list to convert it into SSLv3+ format before we save it away.

Fix for this in #2280.


Can “buildGraph”functions return pyg format?

Now buildGraph function return networkx format. Can I modify it to return in Pyg format?

Yes you can do it using the from_networkx function of the pyg library.
Here an example in a previous work.

Yes, but it's too slow.

该邮件从移动设备发送
--------------原始邮件--------------
发件人："KevinHoarau @.>;
发送时间：2023年12月26日(星期二) 下午4:00
收件人："KevinHoarau/BML" @.>;
抄送："赖俊宇 @.>;"Author @.>;
主题：Re: [KevinHoarau/BML] Can “buildGraph”functions return pyg format? (Issue #6)
Yes you can do it using the from_networkx function of the pyg library.
Here an example in a previous work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The example is slow because it is single-threaded, however, if you use from_networkx in the BML's transformation then it could be parallelized. But maybe you already tried, and it is still too slow.


ReversingLabs A1000 v2: Feature - Add new actions

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Testing of all the changes has been performed (for bug fixes / features)
[x] The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
[x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[x] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[x] Verify all checks are passing.
[x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[x] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the manual_readme_content.md.
[x] If this is a new connector or you are adding new actions

[x] Please document in the manual_readme_content.md all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the manual_readme_content.md.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Added new actions:

Advanced Search Local
Advanced Search TiCloud
Get User Tags
Create User Tags
Delete User Tags
Set Sample Classification
Delete Sample Classification
YARA Get Rulesets
YARA Get Ruleset Text
YARA Get Matches
YARA Create Or Update Ruleset
YARA Delete Ruleset
YARA Enable Or Disable Ruleset
YARA Get Synchronization Time
YARA Set Ruleset Synchronization Time
YARA Start Or Stop Local Retro Scan
YARA Manage Cloud Retro Scan
YARA Status Retro Scan Local
YARA Status Retro Scan Cloud
List Containers For Hash
Delete Sample
Download Extracted Files
Reanalyze Local Samples

Bug fixes:

Fixed advanced_search view render by marshalling TiCloud data format into A1000 data format
Fixed typos on custom views

Enhancements:

ReversingLabsSDK dependency updated to 2.5.6
Expandex actions parameter list with missing parameters for actions:

detonate_file
detonate_file_from_url
network_ip_to_domain
network_urls_from_ip
network_files_from_ip

Added charts for actions to enhance UX and data readability
Added contextual action popup for most actions with custom views:

domain_reputation
get_classification
get_summary_report
get_titanium_core_report
ip_reputation
network_files_from_ip
submit_url
url_reputation

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

@ishans-crest
@mishalp-crest
This merge request was closed but the latter pipeline failed due to a header missing header in unreleased.md.
Could you help with getting these changes published?
Link to failed pipeline.


[Sandbox] k0s

Application contact emails
<EMAIL_ADDRESS><EMAIL_ADDRESS>Project Summary
k0s is a CNCF-certified lightweight, Kubernetes distribution with zero dependencies and zero opinion.
Project Description
k0s is a fully conformant, CNCF-certified Kubernetes distribution that offers a zero-dependency, statically compiled, vanilla Kubernetes experience. Designed to run anywhere—from bare metal to cloud environments—k0s provides a minimal footprint with a low attack surface. It enforces a strong separation between controllers and workers, enhancing security and operational efficiency.
k0s aligns with the CNCF mission by fostering an open-source, vendor-neutral Kubernetes distribution that emphasizes choice and flexibility within the cloud-native ecosystem. By providing diversity of choice, k0s encourages innovation and collaboration, strengthening the Kubernetes community.
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/k0sproject
Project repo URL in scope of application
https://github.com/k0sproject/k0s
Additional repos in scope of the application
https://github.com/k0sproject/k0sctl
Website URL
https://k0sproject.io/
Roadmap
https://github.com/k0sproject/k0s/milestones
Roadmap context
In our monthly office hours and community channels, we openly discuss roadmap items, gathering input and prioritizing items through collaborative discussions. Our approach is strongly oriented towards fostering a thriving ecosystem, and we actively seek opportunities for interoperability with CNCF projects and other open-source initiatives. This commitment helps us better address the interests and needs of our community.
We are working towards a more formal roadmap.
Contributing Guide
https://github.com/k0sproject/k0s/blob/main/docs/contributors/overview.md
Code of Conduct (CoC)
https://github.com/k0sproject/k0s/blob/main/CODE_OF_CONDUCT.md
Adopters
We are updating this in real time.
https://github.com/k0sproject/k0s/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
https://mirantis.com
Maintainers file
https://github.com/k0sproject/k0s/blob/main/MAINTAINERS.md
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
k0s seeks to apply to CNCF in order to find a vendor-neutral home.  The k0s community has seen significant adoption and has matured rapidly, recently adding additional non-Mirantis maintainers from Replicated.com.  With over 7,500 weekly active clusters in the wild that average over 300+ days in age, we believe the time is right to become an official project of the CNCF.
We want to demonstrate our commitment to managing expansion in an open-source manner and ensure neutral governance for our growing community of users and contributors. The CNCF platform will serve as an additional catalyst for community adoption and encourage contributions from developers. Additionally, being a part of CNCF allows k0s to learn from other projects and actively contribute back to the cloud-native community, aligning with the maintainer's ethos.
k0s wants to establish itself as a clear alternative k8s distribution for those who want an ultra lightweight, secure, vanilla distribution that supports all x86 and ARM platforms.
Benefit to the Landscape
The CNCF ecosystem would benefit from having additional conformant k8s distributions, especially ones with a specific niche, such as k0s: lightweight, no opinion, works anywhere and on any platform.
Key Features Include:

Different installation methods: single-node, multi-node, airgap and Docker
Automatic lifecycle management with k0sctl: upgrade, backup and restore
Modest system requirements (1 vCPU, 1 GB RAM)
Vanilla upstream Kubernetes (with no changes)
Available as a single binary with no external runtime dependencies besides the kernel
Flexible deployment options with control plane isolation as default
Scalable from a single node to large, high-available clusters
Supports custom Container Network Interface (CNI) plugins (Kube-Router is the default, Calico is offered as preconfigured alternative)
Supports custom Container Runtime Interface (CRI) plugins (containerd is the default)
Supports all Kubernetes storage options with Container Storage Interface (CSI)
Supports a variety of datastore backends: etcd (default for multi-node clusters), SQLite (default for single node clusters), MySQL, and PostgreSQL
Supports x86-64, ARM64 and ARMv7
Konnectivity service, CoreDNS, Metrics Server

Cloud Native 'Fit'
k0s is about as cloud-native as you can get, given it is basically the purest and simplest form of a k8s distribution.
Cloud Native 'Integration'
Nothing besides core Kubernetes.
Cloud Native Overlap
There is some overlap with k3s, but ultimately, we believe there is a enough difference in approach to allow both distributions in the Kubernetes ecosystem.
Here are some different perspectives from around the web for this year, comparing k0s and k3s:

<EMAIL_ADDRESS>https://shipyard.build/blog/k0s-k3s-k8s/
https://www.nops.io/blog/k0s-vs-k3s-vs-k8s/

Perhaps more importantly, here are a couple of k0s users explaining why they preferred k0s over k3s:

https://github.com/k0sproject/k0s/issues/3248#issuecomment-1649672501
https://github.com/k0sproject/k0s/issues/3248#issuecomment-1780158625

Similar projects
k3s
Landscape
Yes, k0s is listed in the landscape.
Business Product or Service to Project separation
Some Mirantis products do leverage k0s, but the project is maintained completely separately from our products and has been since inception.  Originally Mirantis products used other k8s distributions, but recently migrated to k0s.  A close inspection of GitHub issues will show you that there is a clear firewall between k0s and our enterprise products.  Putting k0s into the CNCF will further help maintain it's independence.
Project presentations
Runtime TAG in 2021:
https://www.youtube.com/watch?v=5Hja-cGXZ5Q&ab_channel=CNCFTAGRuntime
Edge/IoT WG in 2022:
https://youtu.be/L5jWfM6kn5M?t=1695
Project champions
TBD
Additional information
We collect anonymous usage data.  Attached is a screenshot of our k0s dashboard with some detailed statistics showing our accelerated growth over the past year.
k0s Dashboard.pdf

As a representative of Replicated, I'd like to express our support for the k0s project's application to join the CNCF as a sandbox project.

At Replicated, we have carefully evaluated and selected k0s for our needs, and it has become an integral part of our technology stack.

During our selection process, we reviewed several available projects. What truly sets k0s apart is its commitment to a zero-ops approach. While there are other easy-to-install distributions like k3s, k0s uniquely defines installing, upgrading, and maintaining the cluster as core features within its scope. The built-in Autopilot feature is a prime example of this philosophy, demonstrating a distinctive approach to handling upgrades that's integrated directly into the distribution. This aligns perfectly with our goals of simplifying Kubernetes operations for our users.

We have already implemented k0s in production environments and are seeing great results. Our intention is to continue expanding its use within our infrastructure. We would be delighted to see k0s become part of the CNCF, as we believe this would ensure its continued growth as an open-source community project.

Given our positive experience with k0s and its unique features, we strongly support its inclusion in the CNCF and look forward to its continued development and adoption within the wider community.

Do you have a list of third party dependencies for k0s?

@caniszczyk I'm not sure what you mean here by 3rd party dependencies?
As for any Golang project, our Golang dependencies are managed via go modules: https://github.com/k0sproject/k0s/blob/main/go.mod
The components we embed as binaries are: runc, containerd, Kubernetes (api-server, controller-manages, scheduler, kubelet), kine, etcd, iptables and keepalived
All the embedded bins are statically compiled so we can run them on all Linux OSes and thus have no separate builds or packaging for each distro. The versions for these embedded bins are declared at https://github.com/k0sproject/k0s/blob/main/embedded-bins/Makefile.variables
We also produce SBOM for all the releases: https://github.com/k0sproject/k0s/releases/download/v1.30.4%2Bk0s.0/spdx.json
As for Kubernetes itself, it still has some "3rd party" dependencies, i.e. it does call some tools on the host like mount for example.

@jnummelin this is exactly what I need, essentially we need the runtime dependencies and their associated licenses to ensure they are compliant with CNCF's IP Policy: https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md

ok, I've checked the dependency data (attached in CSV format). All the golang modules adhere to the CNCF policy. Some of the embedded binaries, iptables and keepalived, are GPLv2, but IMO they go into this category from the policy:
It is either (A) stored unmodified in a designated third-party folder, or (B) not stored in the CNCF project repository and instead retrieved at installation or build time from the upstream third party repository or package repository

In this case we get the sources for those components directly from upstream repos, build them and "just" include the binary.
k0s dependencies - Sheet1.csv

Per @jnummelin:
On Oct 27th k0s crossed another threshold in adoption.  We crossed the threshold of seeing 400k unique[^1] clusters throughout the telemetry collection period starting March 2021.  Couldn't be more proud of the k0s team for making k0s what is is today and the dedication to make it better every day.
Onwards and upwards!
[^1]: We determine unique clusters based on kube-system UUID as k8s uses type 4 UUIDs which makes them globally unique, or at least the chance for collisions is extremely low.

Replicated recently shared a YouTube video with more details on their use case as well as additional k0s proof points.
https://youtu.be/95LhxbmH-t0?si=4ScS3jDQBRErX1MP

@randybias and team, thanks for your submission! I have a couple of questions:

Has there been organized efforts to broaden the set of folks who are regular committers? (looking at https://github.com/k0sproject/k0s/graphs/contributors?from=12%2F16%2F2023)
Has there been examples of good back-and-forth between k0s and its upstream (k8s) on issues that matter to your end users?

thanks!


Bluetooth: BAP: Broadcast: Add checks for length before merging BIS cfg

Before merging the BIS specific codec configuration with the subgroup codec configuration, we should ensure that the BIS data is not empty, as that would trigger an error from bt_audio_data_parse.

For some reason retriggering CI didn't pass the tests, so had to rebase


Implement "stage_file_with_retry" for robust file staging

Job creation involves staging multiple files (artifacts, pipeline proto, job file, template). While artifact staging has retry logic, these other types do not, leading to potential job failures due to transient service issues.
This commit introduces stage_file_with_retry, a new function with built-in retry logic.  Several stage_file calls in apiclient.py have been replaced with this new function.
Internal bug id: 384579652.

Run Prism_Python PreCommit 3.9


Question about ollama + qwen

Can Spring AI support the Qwen large language model?
And can spring-ai-ollama-spring-boot-starter support function calling?

For the first one, it supports Qwen. For the second one, it does not yet support ollama's function call.

Which Maven package can I use?

Does Spring AI support the Qwen large language model?

Spring AI supports Ollama, so you just have to use the Ollama starter package.

Does spring-ai-ollama-spring-boot-starter support function calling?

Spring AI does [1][2][3], but Ollama doesn't officially support function calling yet [4][5], so naturally spring-ai-ollama-spring-boot-starter doesn't have it baked-in. By the way, neither vLLM nor SGLang do [4].

[1] https://github.com/spring-projects/spring-ai/discussions/193
[2] https://www.devturtleblog.com/sring-ai-function-calling-tutorial/
[3] https://spring.io/blog/2024/03/06/function-calling-in-java-and-spring-ai-using-the-latest-mistral-ai-api
[4] https://github.com/QwenLM/Qwen2/issues/378 (https://github.com/QwenLM/Qwen2/issues/378#issuecomment-2097355347)
[5] https://github.com/ollama/ollama/issues/3137
[6] https://github.com/QwenLM/Qwen2/blob/d439e04e84ebe3734dea4e9769e17f380a8c72b8/README.md?plain=1#L192

spring cloud alibaba ai for qwen
目前无法支持。因为 ollama 的 api 不支持 tools 和 tools_choice 字段。但是可以参考以下文档自己实现。（不推荐但是可用，以下两种方式都可以实现ollama的function call。）
langchain ollama function call
qwen agent funciton call

@zzllkk2003, Ollama added (partial) function calling support last week and Spring AI just provided support for it: https://docs.spring.io/spring-ai/reference/api/chat/ollama-chat.html#_function_calling
But of it to work the underling models must support function calling. I'm not sure qwen2 supports it? Can you point me to a model that does?
Just tried with qwen2 and got:
{"error":"qwen2 does not support tools"}

For this to work we need a qwen/qwen2 model that has been trained for function calling?

Llama 3.1-8B、70B、405B is a new state-of-the-art model and  support Tools.but Spring AI does support function calling ，It would be great if the next step could support function calling

For this to work we need a qwen/qwen2 model that has been trained for function calling?

@tzolov tzolov  please see at here
https://qwen.readthedocs.io/en/latest/framework/function_call.html

@SpiritCloude you can call the llama models with spring ai and function calling.

I've tried function calling with the following models:

Qwen2 - 7B
Qwen 2.5 - 7B
Llama 3.1 - 8B
Llama 3.2 - 3B
Llama 3.3 - 70B

They all work as expected.


Implement "format(s)" command-line argument

Issue https://github.com/rolandsz/Mi-Fit-and-Zepp-workout-exporter/issues/1 showed that non-essential features depending on untested third-party code can easily break the core functionality of the application. Users should be able to opt-in for extra functionalities (like conversion to .gpx), so at least they can dump their data in raw .json format.
Acceptance criteria:

Introduce a new argument in the ArgumentParser such as format or formats
Make sure the value of this argument is validated so it can only take values "json" or "gpx" (See https://docs.python.org/3/library/argparse.html#choices)
Make sure it can handle multiple values such as "json,gpx" (See https://docs.python.org/3/library/argparse.html#nargs)
Refactor the Scraper class so it converts & exports workouts in the user-specified format(s)

Nice to have:

Write unit tests for AC 4

Implemented in 8a17e3caed12f8bae3ebf10631d58d1dcd4246e7


nextcloud: use certificate chain instead of individual cert

Exactly the solution proposed by @peteromero in #166
I have attributed @peteromero as a co-author of the commit.
Closes #166

Thanks, @jotoho


Fix StringIndexOutOfBoundsException in NamespaceResources#pathIsFromNamespace

Motivation
The NamespaceResources#pathIsFromNamespace throws StringIndexOutOfBoundsException when path is  "/admin/policies".
PS. It happens in some test case, I am not sure it will appear in running broker.
Modifications
Check the path starts with BASE_POLICIES_PATH + "/" first.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:
NamespaceResourcesTest
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[x] no-need-doc

Simple bug fix.

/pulsarbot run-failure-checks


Marking other HTML elements as "non-drop targets"?

First off, thanks for this awesome library!
I'm having an issue with autoscroll. Because I have a fixed toolbar at the top of my page, when a user drags a sortable item up to the top of the page, it won't scroll because (I assume) it thinks the user might want to drop the item on the toolbar.
Is there a way for me to mark HTML elements as non-drop targets, so SortableJS ignores these? The only hack I can think of (not ideal) is to detect when an item is dragging, and then globally set all fixed elements with pointer-events: none.

https://github.com/SortableJS/Sortable/issues/1582