[e2e]: nodejs push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6609443009
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Mon Oct 23 06:17:07 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6623081773
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Tue Oct 24 06:17:13 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6636498093
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Wed Oct 25 06:22:22 UTC 2023
Tests are passing now. Closing this issue.


VolumeSubpathEnvExpansion feature gate is enabled by default from v1.15

VolumeSubpathEnvExpansion feature gate is enabled by default from v1.15

/approve
@sftim Will you give the lgtm when this looks ready.

I'm at SREcon this week so might not be around that often.

/lgtm


Error in multithreading with wasm-pack and webassembly rust

Bug report

What is the current behavior?
When compiling https://github.com/iMplode-nZ/rust-webpack-multithreading-test via (p)npm watch using webpack 5.49.0 and the latest rust and the rust flags -Ctarget-feature=+atomics,+bulk-memory,+mutable-globals, I get this error:
webpack compiled with 1 error
ERROR in ./pkg/index_bg.wasm
Module parse failed: Unexpected section: 0xc
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
Error: Unexpected section: 0xc

If the current behavior is a bug, please provide the steps to reproduce.
Clone https://github.com/iMplode-nZ/rust-webpack-multithreading-test, npm install, npm serve.

What is the expected behavior?
It does not error.

Other relevant information:
webpack version:  5.49.0
Node.js version: 14.4.0
Operating System: Ubuntu 20.04 focal
Additional tools:
rustc 1.56.0-nightly (4e282795d 2021-07-31)
wasm-bindgen 0.2.75
wasm-pack 0.10.0

I'm putting this here as it seems more like a webpack bug than a wasm-pack/bindgen/rust bug.
See wasm-pack issue at https://github.com/rustwasm/wasm-pack/issues/1050

Same issue here
"Unexpected section: 0xc" throws in wasm-async, or more precisely it crashes in @webassemblyjs/wasm-parser. This is a minimal example to reproduce the error:
const { decode } = require("@webassemblyjs/wasm-parser");
const fs = require('fs');

decode(fs.readFileSync('file.wasm'), {
  ignoreCodeSection: true,
  ignoreDataSection: true,
  ignoreCustomNameSection: true,
})

example files to reproduce:
wasm_parse_bug.zip

@xtuc Can you look at this?

probably some target-feature not supported  by current @webassemblyjs/wasm-parser

I'm compiling with the following flags:
rustflags = [
    # Enabled unstable APIs from web_sys
    "--cfg=web_sys_unstable_apis",
    # Enables features which are required for shared-memory
    "-C", "target-feature=+atomics,+bulk-memory,+mutable-globals",
    # Enables the possibility to import memory into wasm.
    # Without --shared-memory it is not possible to use shared WebAssembly.Memory.
    "-C", "link-args=--shared-memory --import-memory",
]

If I import wasm via bindings generated by wasm_bindgen (wasm-bindgen --target web --out-dir web target/wasm32-unknown-unknown/debug/mapr.wasm) it works. The the bundle which was created by wasm-pack is improte dI get the above error.

Same issue here with rustflags = ["-C", "target-feature=+atomics,+bulk-memory,+mutable-globals"]. I tried both webassembly/async and webassembly/sync.

For me everything works now, if you want I could provide you with webpack/rust configs.

@maxammann Yes please.

.cargo/config.toml
[build]
target = "x86_64-unknown-linux-gnu"

[target.wasm32-unknown-unknown]
rustflags = [
    # Enabled unstable APIs from web_sys
    "--cfg=web_sys_unstable_apis",
    # Enables features which are required for shared-memory
    "-C", "target-feature=+atomics,+bulk-memory,+mutable-globals",
    # Enables the possibility to import memory into wasm.
    # Without --shared-memory it is not possible to use shared WebAssembly.Memory.
    "-C", "link-args=--shared-memory --import-memory",
]

A build script which does not use webpack. (get this working first!)
#!/bin/bash
set -e

webgl_flag=""

TEMP=$(getopt --long -o "g" "$@")
eval set -- "$TEMP"
while true; do
  case "$1" in
  -g)
    webgl_flag="web-webgl,"
    shift 2
    ;;
  *)
    break
    ;;
  esac
done

export RUSTUP_TOOLCHAIN=nightly-2022-02-26-x86_64-unknown-linux-gnu

rustup component add rust-src --toolchain nightly-2022-02-26-x86_64-unknown-linux-gnu

function plain_build() {
  cargo build --features "$webgl_flag" --target wasm32-unknown-unknown -Z build-std=std,panic_abort
  # TODO: Untested: --reference-types
  wasm-bindgen --target web --out-dir dist/mapr-pain-bindgen target/wasm32-unknown-unknown/debug/mapr.wasm
}

function wasm_pack_build() {
  ~/Downloads/wasm-pack-v0.10.1-x86_64-unknown-linux-musl/wasm-pack build . \
        --release --target web --out-dir dist/mapr -- \
        --features "$webgl_flag" -Z build-std=std,panic_abort
}

wasm_pack_build

My webpack config (not ready for copy&paste):
const path = require("path");
const webpack = require("webpack");
const CopyPlugin = require("copy-webpack-plugin");
const WasmPackPlugin = require("@wasm-tool/wasm-pack-plugin");

let dist = path.join(__dirname, 'dist/demo');
module.exports = (env) => ({
    mode: "development",
    entry: {
        index: "./index.ts",
        'service-worker': "./service-worker.ts",
    },
    experiments: {
        syncWebAssembly: true
    },
    performance: {
        maxEntrypointSize: 400000,
        maxAssetSize: 400000000,
    },
    output: {
        path: dist,
        filename: "[name].js"
    },
    devServer: {
        server: {
            type: 'http',
        },
        allowedHosts: 'all',
        host: '<IP_ADDRESS>',
        static: {
            directory: dist,
        },
        headers: {
            'Cross-Origin-Opener-Policy': 'same-origin',
            'Cross-Origin-Embedder-Policy': 'require-corp'
        },
    },
    module: {
        rules: [
            {
                test: /\.tsx?$/,
                use: 'ts-loader',
                exclude: /node_modules/,
            },
        ],
    },
    resolve: {
        extensions: ['.tsx', '.ts', '.js'],
    },
    plugins: [
        new webpack.DefinePlugin({
            WEBGL: !!env.webgl
        }),
        new CopyPlugin({
            patterns: [
                {from: "static", to: "."},
            ],
        }),
        new WasmPackPlugin({
            crateDirectory: path.resolve(__dirname, '../'),

            // Check https://rustwasm.github.io/wasm-pack/book/commands/build.html for
            // the available set of arguments.
            //
            // Optional space delimited arguments to appear before the wasm-pack
            // command. Default arguments are `--verbose`.
            //args: '--log-level warn',
            // Default arguments are `--typescript --target browser --mode normal`.
            extraArgs: `--target web -- ${env.webgl ? '--features web-webgl' : ''} -Z build-std=std,panic_abort`,

            // Optional array of absolute paths to directories, changes to which
            // will trigger the build.
            // watchDirectories: [
            //   path.resolve(__dirname, "another-crate/src")
            // ],

            // The same as the `--out-dir` option for `wasm-pack`
            outDir: path.resolve(__dirname, 'dist/libs/mapr'),

            // The same as the `--out-name` option for `wasm-pack`
            // outName: "index",

            // If defined, `forceWatch` will force activate/deactivate watch mode for
            // `.rs` files.
            //
            // The default (not set) aligns watch mode for `.rs` files to Webpack's
            // watch mode.
            // forceWatch: true,

            // If defined, `forceMode` will force the compilation mode for `wasm-pack`
            //
            // Possible values are `development` and `production`.
            //
            // the mode `development` makes `wasm-pack` build in `debug` mode.
            // the mode `production` makes `wasm-pack` build in `release` mode.
            // TODO: We always build a production build because a development build runs slow
            // TODO: The function which is slowing it down is TileProto::decode() which maps the tile proto struct
            // TODO: into our data structure. (Development: 15s, Production: 60ms)
            forceMode: "production",

            // Controls plugin output verbosity, either 'info' or 'error'.
            // Defaults to 'info'.
            // pluginLogLevel: 'info'
        }),
    ]
});

Having this issue too. Did other people manage to get it working?

Related: https://github.com/WebAssembly/binaryen/issues/3006

I don't think this issue still exists. At least I'm using WASM multithreaded successfully.

Can't be fixed here, please use extraArgs: "--target web" for WasmPackPlugin.
Used for test https://github.com/webpack/webpack/issues/14087#issue-982321260 and all works fine:
rustc --version
rustc 1.69.0 (84c898d65 2023-04-16)

[dependencies]
wasm-bindgen = { version = "0.2.84", features = ["serde-serialize"] }

--target web doesn't fix it for me, --target no-modules doesn't either

@wrightwriter Please avoid such comments, it will not allow to help you, provide infromation/reproducible example


Clipboard tooltip not disappearing

Hey , Noticed this small error of clipboard tooltip not immediately hiding once clipboard has been pressed .
For more clarification :

Would love to dive into it as to resolve this issue , if it seems legit :)

Good catch, I can confirm this bug. You're of course welcome to work on this.

Cool , Working on it 👍


should a keepalive be necessary?

In all my work with flannel, it certainly seems that the network between any two hosts will not function until there's a bidirectional flow of traffic between those two hosts.
(i.e:
from A ping B - fail
from B ping A - fail
from A & B simultaneously reciprocate ping -SUCCESS! :)
After (some period, not yet measured, but not very long time) of no traffic between A & B the become unreachable until the process is repeated.
I've written a keepalive unit-pair (dns announcer, and fping+dig script to handle this and keep the network running - but should this be necessary? In most situations, with a loaded network this wouldn't be noticed, but it does present a challenge to bootstrapping the cluster AFAICT.
The cluster is running in AWS VPC, all etcd machines are in the same AZ, same subnet, -- and this is on the current 522.2 beta.

from A ping B - fail
from B ping A - fail
from A & B simultaneously reciprocate ping -SUCCESS! :)
yes, i also have this problem. my docker cluster build in centos 7.0.1406 in openstack kvm.

@stormltf Can you run tcpdump via toolbox on both src and dest's flannel0 and also on eth0 (or whatever the real interface is called). I'm assuming you're using "udp" backend. On eth0, the encapsulated packets are sent over udp port 8285 so watch for those.
Also, if you configure it with vxlan backend, does it help?

when i using "udp" backend , i also have that problem.
when i use vxlan:
./etcdctl mk  /coreos.com/network/config  '{"Network":"<IP_ADDRESS>/16","Backend":[{"Type":"vxlan", "VNI": 1}] }'
then i run  flannel in three slave-machines.  all is well.
then i want to start docker  in these three machines.but two of them failed....
[root@vm-56-62 bin]# docker -d --bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
INFO[0000] [graphdriver] using prior storage driver "devicemapper"
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: bridge IPv4 (<IP_ADDRESS>) does not match requested configuration <IP_ADDRESS>

when i used "udp" backend ,  i  alse met that problem.
then  i use “vxlan” backend  and  VNI =1
i start two machines
A:  docker0:<IP_ADDRESS>      flannel.1: <IP_ADDRESS>
B:  docker0:<IP_ADDRESS>      flannel.1: <IP_ADDRESS>
from A PING B   fail
from B PING A fail
from A & B simultaneously reciprocate ping  fail     :(

I am having the same issue described by @guruvan, is there a solution/explanation for it?

Hi,
I've had this problem twice and have both found the problem.
The first time is using EC2 and the default safe group didn't open UDP ports. After open them, it works.
The second time is in our own cluster. The first net interface is bind to public IP and have firewall on it. The second interface is used to communication with other hosts in the cluster. Flanneld uses the first interface's IP by default, so it cannot communicate between hosts. After set the IP to use with -iface/--public-ip, it works.
The details of each time is different, but both reasons are hosts cannot communicate on the specify UDP port.
Hope this helps.

I think this issue is just caused by firewall ports not being opened. We already mention this in the docs. I'm not sure how else to progress this issue so closing.


rollback k8s client-go deps to v7.0.0

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

/lgtm pending E2E

/lgtm


Move to 2019 IMD for 2020 onwards

What problem would this feature solve? Please describe.
The 2019 IMD dataset has been published (Sep 2019, https://www.gov.uk/government/statistics/english-indices-of-deprivation-2019)
We should calculate IMD deciles with the most relevent data available.
We should also probably calculate 2010-2014 IMD deciles using the 2010 IMD datasets
Describe the solution you'd like
Allow multiple IMD rankings and deciles to be loaded for different years. We may have to move beyond relying on the data included in the postcode directory
Additional context
https://www.gov.uk/government/statistics/english-indices-of-deprivation-2019
https://www.gov.uk/government/statistics/english-indices-of-deprivation-2015
https://www.gov.uk/government/statistics/english-indices-of-deprivation-2010

@ox-baloo for thoughts

I think we should just use the 2019 IMD deciles retrospectively. My assumption is that not many of them have changed (though this is an interesting question). I think using multiple ones will confuse people reading the data. In the vast majority of cases I care about which areas currently have a low index of deprivation.

I think we should just use the 2019 IMD deciles retrospectively.

Done!


Very small typo in e2e script

Fixes a very small typo in the new e2e script :)

Thanks @SD-13 !
/lgtm
/approve


Triggered Execution / Watching Broken in 1.1.5 on Linux

[x] I've read the CONTRIBUTING guidelines

steps

Run a triggered execution command on Linux with sbt 1.1.5
Change a file

problem
Triggered execution doesn't run
expectation
Triggered execution should run
notes
sbt version: 1.1.5
jvm version: 1.8.0_171

@eatkins fancy triaging this?

I believe it's fixed by https://github.com/sbt/io/pull/150

Thanks @eatkins. Fix coming in sbt 1.1.6 (or 1.2.0 if we cut that instead), @jamesward. We've not yet discussed when that'll be though.

@dwijnand  @eed3si9n  User experience on linux is seriously hampered because of this. Could we please release this now? thanks

I think @eed3si9n might be releasing 1.1.6 soon (tm).

This seems to be fixed in 1.1.6. Thanks all!

Thanks - can confirm it works.


Rerender for R 3.4.0

If this could get a @conda-forge-admin, please rerender that would be great.

All set already.


Remove internal params in explain output

What does this change
Don't show internal params in output of explain
What issue does it fix
Closes #1091
Notes for the reviewer
Checklist

[x] Unit Tests
[x] Documentation (N/A)
[x] Schema (porter.yaml) (N/A)

@carolynvs You mentioned, porter inspect shows parameter list in issue. But I see porter inspect showing only image and invocation image list. So, I added necessary changes to explain command only

Oh great! At one point inspect was going to do more, and we changed it's scope. I wasn't sure if it was affected or not so thanks for checking.

/azp run porter-integration

I am looking into why the integration tests are failing, it does not appear to be related to your changes.

Your change is fine, verified manually locally. I believe that this is a problem with how the CI action is merging your change with master. I'm going to merge and then see how it lands on main. If there is a problem, I'll resolve any conflicts.


Adjust priority of Shutdown event in basic cluster

Problem
What is being fixed?  Examples:

Currently, the Shutdown event always get lost and never get a chance to be sent out to subscribers.
The priority of ShutDown event should be adjusted to CRITICAL as Startup event, since this is the event get logged right before the device shutdown, if we don't mark it as CRITICAL, it will not get sent out immediately as Urgent, and it will get lost during shut down since the event circular buffer is not in persistent memory.

Change overview
Adjust priority of Shutdown event in basic cluster
Testing
How was this tested? (at least one bullet point required)

Confirm the Shutdown event is logged as Urgent event from log.

This does not seem like the right fix. The right fix would be to flush out the event buffer on shutdown, no? Probably right after queuing the shutdown event....
That said, if that buffer does not fit in a single message we could still have a problem. So maybe we do need to make this event critical... but in that case that needs to be raised as a spec level issue (possibly in parallel with the code change).

We don't flush the event buffer on shutdown, only critical event get sent immediately, other event will be sent when we reach next reporting interval.
I already put a PR in spec side before this PR.
https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/4787

We don't flush the event buffer on shutdown

I know we don't.  I am saying we should, best-effort.  That's in addition to changing the event priority here.

flush out the event buffer on shutdown,

Acked. https://github.com/project-chip/connectedhomeip/issues/13008


[BEAM-6268] Ignore failed HadoopFormatIOCassandraTest

Temporary ignore this test (ports conflicts)

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


Pytorch should be a dependency with explicit version

C++ based extensions of pytorch should have specific dependency on pytorch, since pytorch's ABI is not stable. So pytorch version should be pinned during the build. This also goes for other extensions like

https://github.com/conda-forge/pytorch_scatter-feedstock
https://github.com/conda-forge/pytorch_cluster-feedstock
https://github.com/conda-forge/pytorch_spline_conv-feedstock
https://github.com/conda-forge/pytorch_geometric-feedstock

@cmpute how would I go about doing this?

Just pin the pytorch version used for these libraries would be fine

@cmpute do you know what level of pinning is required? down to the minor or bug-fix version?
With pinning, it would be good to add a variant file to build with multiple versions of pytorch.

@cmpute do you know what level of pinning is required? down to the minor or bug-fix version?
With pinning, it would be good to add a variant file to build with multiple versions of pytorch.
@rluria14 I'm happy to send a PR

At least minor version for my experience

I think the level of pinning should be at x.x.x (bug fix) given the below smalle tests:
# GPU
mamba create -n tmp_pyg_gpu -c conda-forge python=3.8 pytorch_geometric pytorch-gpu=1.10.2 cudatoolkit=11.1
mamba list -n tmp_pyg_gpu | grep 'pytorch\|cuda'
mamba run -n tmp_pyg_gpu python -c "import torch_geometric"  # -> WORK

# GPU (broken)
mamba create -n tmp_pyg_gpu -c conda-forge python=3.8 pytorch_geometric pytorch-gpu=1.10.0 cudatoolkit=11.1
mamba list -n tmp_pyg_gpu | grep 'pytorch\|cuda'
mamba run -n tmp_pyg_gpu python -c "import torch_geometric"  # -> FAIL

The error being:
ERROR conda.cli.main_run:execute(41): `conda run python -c import torch_geometric` failed. (See above for error)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_geometric/__init__.py", line 4, in <module>
    import torch_geometric.data
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_geometric/data/__init__.py", line 1, in <module>
    from .data import Data
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_geometric/data/data.py", line 9, in <module>
    from torch_sparse import SparseTensor
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_sparse/__init__.py", line 36, in <module>
    from .storage import SparseStorage  # noqa
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_sparse/storage.py", line 5, in <module>
    from torch_scatter import segment_csr, scatter_add
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_scatter/__init__.py", line 13, in <module>
    torch.ops.load_library(importlib.machinery.PathFinder().find_spec(
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch/_ops.py", line 110, in load_library
    ctypes.CDLL(path)
  File "/home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /home/hadim/local/conda/envs/tmp_pyg_gpu/lib/python3.8/site-packages/torch_scatter/_scatter_cuda.so: undefined symbol: _ZNK2at6Tensor6deviceEv

@AntoinePrv are you planning to merge #25?
@hmaarrfk is that ok for you to pin at x.x.x given the above example? or should we stick to x.x?

Honestly, we probably had alot of breakage with older versions of pytorch 1.10.2 is probably as old as I would go.
1.11.0 i hope is in better shape with pinnings.

Honestly, we probably had alot of breakage with older versions of pytorch 1.10.2 is probably as old as I would go.

Ok this is good to know. I will stick with >=1.10.2 then.
Should we still pin those libraries pytorch_xxx?

We recently added a conda-forge wide pytorch pinning. Newely rerendered recipes that depend on pytorch will receive it.
https://github.com/conda-forge/pytorch_sparse-feedstock/blob/main/.ci_support/linux_64_c_compiler_version10cuda_compiler_version11.1cxx_compiler_version10python3.8.____cpython.yaml#L28

No longer an issue, if it is let me know and we can re-open this issue


[Question] Can't run in Docker container

what's problem? Thanks

By using offical base image,I solve it. Thanks! @yury-s


#157 rethinking shortcuts

The major work is done, we might have to change some tool shortcuts around and check that there are no bad collisions...

Good point. There might actual be a way.

@MrTopom Should be addressed now.

Need to move the window shortcuts to CTRL + number...

Please review again! @MrTopom


Support for 8.X version of logtrail kibana

hi, I'm using logtrail and we find it very helpful. are you planning to release a new version of logtrail for kibana 8.x.

We are migrating to ECK Operator on K8s and we are missing the Logtrail on 8.7, there are some plan's for this?

the tail logs apps has a very experience, please support the new kibana versions


Relax dask-core upper bound

Since dask is using calver I think it's safe to remove the upper bound here
https://github.com/gjoseph92/geogif/blob/6fc66faebf5c6ed3d5e6fdcb1213e2ca3645e0fc/pyproject.toml#L12
Ran into this trying to keep geogif in an environment with newer dask versions
https://github.com/pangeo-data/pangeo-docker-images/pull/431#issuecomment-1416483271
Happy to submit the PR to fix @gjoseph92

Please do so, thanks for noticing @scottyhq

@scottyhq 0.1.4 is pushed to PyPI with your change


Loading from bad path crashes Python interpreter

Describe the bug
Loading from a bad path should give an exception but should not crash the Python interpreter.
To Reproduce
from phylotrackpy import systematics

syst = systematics.Systematics(lambda x: x)
syst.load_from_file("", "id")

Fixed in #100


Not working if build tool version is >=25

Overview

I'm working on a android project with Build Tool Version 25.0.2 and added dependency for Permission Dispatcher. When i am building the project, library is not generating any Permission Dispatcher classes at all corresponding to any Activity or Fragments which has annotation @RuntimePermissions.
It is working fine if Build tool version downgrades to <25.

@3niman Thx for your opening. Can you remember the error message?

This is very peculiar. I'm always on the latest build tools and haven't noticed any odd behavior. To add to @hotchemi's point, does compilation finish without errors, or do you have a stack trace for us?

@aurae Yes compilation finishes without any error, but no Dispatcher files generated.
Also i have tested with a project which is initially running on build tool version 24.0.3 and working fine. But when changed build tool version to 25.0.2 and Rebuild the project, all the generated Dispatcher file gone.
Rolled back the build tool version to 24.0.3 and its working fine.

@3niman Umm, it's kinda weird...

Do you use any other libraries that use annotation processing?
Can you give us a sample proj that can reproduce the problem?

I can confirm that it works fine with the latest build tools.

it is not working with annotationProcessor but with apt on Build Tool Version 25.0.2

using the old way as apt rather that annotationProcessor it works on Build Tool Version 25.0.2

I'm really inclined to say that the issue isn't with PermissionsDispatcher directly, but your specific setup. Do you have any other code-generating annotation processors in your project that stop working when using Build Tools 25.0.2 & the annotationProcessor configuration? If not, could you just add one and test it out, like ButterKnife or LoganSquare?

i already had ButterKnife and i used the annotationProcessor  instead of apt plugin and nothing was generated ..Build Tool Version 25.0.2

Guys. We need code. Please give us a minimum project that reproduce the issue.

Yes, we need a sample code to reproduce the problem.

I'm facing this too. Here is a test project in the permissions-dispatcher branch (it's not minimal though, sorry): https://github.com/vickychijwani/quill/tree/permissions-dispatcher. And you can see the build failure on CircleCI here: https://circleci.com/gh/vickychijwani/quill/173. Can this issue be re-opened please?
Other observations:

Changing build tools version to 24.x didn't seem to help, but I only tried once, quickly
Other libraries may be interfering with PermissionsDispatcher, these are the suspects:

Retrolambda + gradle-retrolambda (backports Java 8 lambdas to Java 7)
Realm (persistence library, uses annotations on model classes)
Hugo (Jake Wharton's method call logging library)
ButterKnife (view injection library)
Retrofit (HTTP interface generator)
Gson (JSON <=> POJ converter)

Thank you for reporting!  We will have a look into your sample code shortly, trying to reproduce the issue.

Update realm. I sent PR. This still has compile error because of realm version but at least PD generates PostEditFragmentPermissionsDispatcher
#219 It seems this report is correct. Realm v1.x is not working with PD.

wow weird...anyway thx @shiraji!
@vickychijwani can u check?

@3niman Did you use Realm alongside PD as well when you ran into this issue?

@hotchemi @shiraji Thanks for looking into this. I guess it's time for me to update Realm - I had been putting it off :smile:. Moving from Realm 1.x to 2.x will take me a few days, I'll report back once I'm done!

@hotchemi @shiraji so after upgrading Realm, MyFragmentPermissionsDispatcher is generated and seems to work... except the @OnPermissionDenied and @OnNeverAskAgain are never called. I tried debugging in the auto-generated class, and was surprised to find that Android doesn't call onRequestPermissionsResult if the user denies the request! I tested on Android 7.1.1 and 6.0 emulators.
I'm sure my code is somehow wrong but I can't quite figure out where 🤔 . Could you help me out by looking at the code in permissions-dispatcher branch?

Uh oh, I realized my mistake as soon as I posted. I forgot to call the delegate's onRequestPermissionsResult 😛. Silly me.

Everything works perfectly now 🎉. Final working commit is here. This issue can be closed if needed.

Happy to hear that, @vickychijwani! :)


code in textInputHandler run twice

Issue Description
Hi, when I print text in textInputHandler, it print twice in console log! what should I do ?
page.textInputHandler = { (item, text) in
print("value is (text)")
}

Hi, I just managed to reproduce the issue. I will investigate.

I have fixed this issue. It turns out there were some issues in the handling of the return key and action button. The fix will be available in the next release, thanks very much for reporting! 😄

The fix shipped in 2.0.0-beta.3.


fix: fixed verdict comparison in evolutions.py

The bug is located in the ragas.testset.Evolution class. The problem is that you are checking the ‘verdict’ field against a string value of ‘-1’, and you need to compare it against an int value of -1:

So I changed the verdict comparison from a string to an integer in the conditional check.

hey @MarkHmnv - firstly thanks a lot for adding the PR but that version of testset generation is going to be removed in the next version but still merging it in
in the meantime would love to get your opinion on the new one if you have time 🙂 . You're valuable feedback would be awesome!


Fix endless recursion exporting Padding widget

export() stucks on a padding widget as it passes itself into DynamicWidgetBuilder.export(...) instead of the child.

thanks


run breaks when the number of observations are less than PEs used

Description
When the number of observations are less than the number of PEs used to run experiments in soca-science the steps run.var/hofx fails. It hangs at the step GetValues<MODEL, OBS>::fillGeoVaLs
@travissluka mentioned that it could be because noaa19 has fewer obs than PEs, and something in fillGeoVaLs is trying to do an MPI reduce with all PEs but the PEs with 0 obs are skipping the MPI call
To Reproduce:
Run any DA or noDA experiment for<PHONE_NUMBER> using the sst_noaa19 obs from the R2D2 database located at /work/noaa/marine/marineda/r2d2/obs/jcsda_soca/ob/benchmark_v1 on orion. The experiment breaks at run.var/hofx step.
Output
output logs
On orion the log can be seen at /work/noaa/marine/kritib/runs/HAT10/1135x633x50/test_sstnoaa19/logs/2015092012/run.var

@kbhargava this is apparently what we were talking about today.
I'm hoping that https://github.com/JCSDA-internal/soca/issues/722 will fix this issue for us. Fingers crossed


Add --recursive mode to s3touch

Convenient way to s3touch all objects under a prefix.
cc @camillacaros @dnomadb @GretaCB @celoyd

super late here, but yay thanks for this :+1:


Typos

Changed some of the preference text.

Fixed the colver/cloud cover typo.
I also removed "includes current" from two of the settings, I don't think it would apply there since minutely is its own section and since hourly is its own section?
It made sense adding includes current for the forecast list since it counted the current forecast in that number of days as I've seen sometimes that the forecast list doesn't always show the current day? If the forecast list always shows the current day then it might not need to be specified.
Changed "if available" to "when available" since the minutely data (the precipitation section under Current forecast?) doesn't always show so when seems better.


URDF and teleop fixes

Merge in changes specific to the URDF in "vector_description" and support for teleop in simulation using "hlpr_gazebo"
URDF changes:

Actual mass and inertia values for the linear actuator (pulled from CAD files)
Added in an extra "dummy" link that allows for planning from the center of the gripper

Teleop changes:

Support for pan/tilt and linear actuator changes in the vector_ros->vector_teleop_full_system node

Do I have to run anything new for teleop? or just the normal remote_vector_teleop?

Nope - but you need to checkout the hlpr_simulator package from the HLP-R org (https://github.com/HLP-R/hlpr_simulator)
To launch you run
roslaunch hlpr_gazebo vector.launch
roslaunch vector_remote_teleop vector_remote_teleop.launch

I'm going to go ahead and pull this in since it is key to testing out some other changes. Can roll back if necessary.


Spotify Playlist Generator

Title and Issue number

Title :Spotify Playlist Generator
Issue No. : #501
Code Stack : react, html, css , spotify api
Close #501

Video (mandatory)

https://github.com/apu52/METAVERSE/assets/68018372/3f52c7be-c033-4404-8feb-d0f5d99869cf
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have updated the projectData.json file for my contribution
[X] I have added the img of my project in the assets/img section

Additional context (Mandatory )
Are you contributing under any Open-source programme?
CodePeak, KWOC

Please omit the unnecessary lines in the README.md & don't make 3 contributions in one single branch in your forked repo.

Removed the default lines from the readme.


Feat(et)

Codecov Report

Merging #88 (f1e1632) into main (519841f) will decrease coverage by 0.02%.
The diff coverage is 81.76%.

@@            Coverage Diff             @@
##             main      #88      +/-   ##
==========================================
- Coverage   84.52%   84.50%   -0.03%
==========================================
  Files          35       37       +2
  Lines        3741     3910     +169
==========================================
+ Hits         3162     3304     +142
- Misses        579      606      +27

Impacted Files
Coverage Δ

pynhm/hydrology/PRMSRunoff.py
81.61% <25.00%> (ø)

pynhm/base/budget.py
76.10% <76.10%> (ø)

pynhm/__init__.py
100.00% <100.00%> (ø)

pynhm/base/adapter.py
94.52% <100.00%> (+0.31%)
:arrow_up:

pynhm/hydrology/PRMSCanopy.py
80.60% <100.00%> (+0.11%)
:arrow_up:

pynhm/hydrology/PRMSEt.py
100.00% <100.00%> (ø)

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 519841f...f1e1632. Read the comment docs.


Cannot generate PGP key using Windows desktop app

Keybase GUI Version: 1.0.40-20180205105656+493a528
Select "Get a new PGP key", fill in the full name and some emails, then press "Let the math begin" (there is nothing indicating the generation progress, even no animated circle or a grayed-out button, only the CPU usage raised), after a few seconds the app let me input the passphrase of the keybase account, then I input the correct one, and the app shows a "disconnected" info.
Tried serval times, all resulting a "disconnected" problem.

I manually ran keybase pgp gen in the console and it worked. see #10448

This is fixed in an upcoming release

@artfulhacker I tried the command line method and gets a red error text - ERROR EOF, I don't know what's wrong?

Got the update, and finally there is a progress indicator.
But when I started to generate keys, it takes forever.

I'm in the same spot. Keybase seems stuck on generating the key.

Should be fixed, @NME1138 which version of the app are you on?

Current version. 1.0.45

Can you do keybase log send and we'll take a look? CC @zapu

Sent. I generated my own keys and imported them in, btw.


Logs are not sent in a .txt file

Expected Behavior
Logs sent should be attached to email in a .txt file.
Current Behavior
Logs are inserted into the body of the email. It also cuts off after about 40 lines text so the majority and most recent logs are not seen.

This seems to be an issue related to iOS.


Fix sonar issues

Fixed 30 sonar issues.

Fixed 18 issues: Math operands should be cast before assignment
Fixed 7 issues: Iterator.next() methods should throw NoSuchElementException
Fixed 1 issue: toString() should not return null
Fixed 2 issues: Non-thread-safe fields should not be static
Fixed 1 issue:  compareTo should not be overloaded
Fixed 1 issue: Externalizable classes should have no-arguments constructors

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fa3862a). Click here to learn what that means.
The diff coverage is 23.94%.

@@            Coverage Diff            @@
##             master    #1108   +/-   ##
=========================================
  Coverage          ?   25.05%
  Complexity        ?     6223
=========================================
  Files             ?     1440
  Lines             ?    87894
  Branches          ?    12292
=========================================
  Hits              ?    22024
  Misses            ?    63708
  Partials          ?     2162

Impacted Files
Coverage Δ
Complexity Δ

...ache/kylin/engine/mr/streaming/ColumnToRowJob.java
0% <ø> (ø)
0 <0> (?)

...kylin/common/persistence/RootPersistentEntity.java
18.6% <ø> (ø)
4 <0> (?)

.../kylin/stream/server/ReplicaSetLeaderSelector.java
0% <0%> (ø)
0 <0> (?)

.../java/org/apache/kylin/storage/StorageContext.java
30.1% <0%> (ø)
10 <0> (?)

...emcubing/RecordConsumeBlockingQueueController.java
75% <0%> (ø)
8 <0> (?)

...in/common/persistence/ExponentialBackoffRetry.java
42.85% <0%> (ø)
7 <0> (?)

...org/apache/kylin/gridtable/GTAggregateScanner.java
33.66% <0%> (ø)
12 <0> (?)

...che/kylin/storage/hbase/util/CubeMigrationCLI.java
0% <0%> (ø)
0 <0> (?)

.../org/apache/kylin/engine/mr/ByteArrayWritable.java
0% <0%> (ø)
0 <0> (?)

...org/apache/kylin/dimension/AbstractDateDimEnc.java
34.88% <0%> (ø)
6 <0> (?)

... and 19 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 fa3862a...777c33e. Read the comment docs.

retest this please

Pull Request Test Coverage Report for Build 5639

17 of 71 (23.94%)  changed or added relevant lines in 27 files are covered.
12 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.0003%) to 27.486%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-common/src/main/java/org/apache/kylin/common/persistence/ExponentialBackoffRetry.java
0
1
0.0%

core-common/src/main/java/org/apache/kylin/common/util/ByteArray.java
0
1
0.0%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/algorithm/BPUSCalculator.java
0
1
0.0%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/RecordConsumeBlockingQueueController.java
0
1
0.0%

core-cube/src/main/java/org/apache/kylin/gridtable/GTAggregateScanner.java
0
1
0.0%

core-metadata/src/main/java/org/apache/kylin/source/datagen/ColumnGenerator.java
0
1
0.0%

core-storage/src/main/java/org/apache/kylin/storage/StorageContext.java
0
1
0.0%

core-storage/src/main/java/org/apache/kylin/storage/gtrecord/SortedIteratorMergerWithLimit.java
0
1
0.0%

engine-mr/src/main/java/org/apache/kylin/engine/mr/BatchOptimizeJobCheckpointBuilder.java
0
1
0.0%

query/src/main/java/org/apache/kylin/query/relnode/OLAPProjectRel.java
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/RecordConsumeBlockingQueueController.java
1
85.71%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
2
68.46%

stream-coordinator/src/main/java/org/apache/kylin/stream/coordinator/Coordinator.java
2
26.37%

storage-hbase/src/main/java/org/apache/kylin/storage/hbase/util/CubeMigrationCLI.java
3
0%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
4
78.12%

Totals

Change from base Build 5638:
-0.0003%

Covered Lines:
24197

Relevant Lines:
88035

💛  - Coveralls


Update Performance Analyzer to support ElasticSearch version 7.3.2

Description of changes:

Updated the ES and OD versions in build.gradle
Updated the gradle version
Added release notes
Modified WhoAmIAction to extend ActionType and CollectMetricsTests based on changes in ES

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ktkrg Please  review

Please update the PR with a brief description of your changes.

@ktkrg Updated the PR.

@ktkrg @ditac Resolved the conflict in release-notes. Can you please review.


build models_pruning  for bug

Hi,
bazel-bin/$examples_dir/cifar10/cifar10_train --pruning_hparams=name=cifar10_pruning,begin_pruning_step=10000,end_pruning_step=100000,target_sparsity=0.9,sparsity_function_begin_step=10000,sparsity_function_end_step=100000
bash: bazel-bin/contrib/model_pruning/examples/cifar10/cifar10_train: No such file or directory
Thank you for your help!

ERROR: Skipping 'contrib/model_pruning/examples/cifar10:cifar10_{train,eval': no such target '//tensorflow/contrib/model_pruning/examples/cifar10:cifar10_{train,eval': target 'cifar10_{train,eval' not declared in package 'tensorflow/contrib/model_pruning/examples/cifar10' defined by /home/ai/tensorflow/tensorflow/contrib/model_pruning/examples/cifar10/BUILD
WARNING: Target pattern parsing failed.
ERROR: no such target '//tensorflow/contrib/model_pruning/examples/cifar10:cifar10_{train,eval': target 'cifar10_{train,eval' not declared in package 'tensorflow/contrib/model_pruning/examples/cifar10' defined by /home/ai/tensorflow/tensorflow/contrib/model_pruning/examples/cifar10/BUILD

I apologize, but I am having a hard time understanding what the problem is, where the problem is, and what version it affects. Please resubmit and pay attention to the issue template (https://github.com/tensorflow/tensorflow/issues/new). Please provide all the information it asks. Thank you.

It looks like you haven't used a template to create this issue. Please resubmit your issue using a template from here. We ask users to use the template because it reduces overall time to resolve a new issue by avoiding extra communication to get to the root of the issue. We will close this issue in lieu of the new one you will create from the template. Thank you for your cooperation.


Error when using * in installation

I tried to install abqpy with Install A Specific Version using * to match specific version.
pip install abqpy==2021.*.*

But it gave me the following error message.
ERROR: Could not find a version that satisfies the requirement abqpy==2021.*.* (from versions: 2016a0, 2016a1, 2016a2, 2016a3, 2016a4, 2016a5, 2016a6, 2016a7, 2016a8, 2016a10, 2016.0, 2016.1, 2016.1.1, 2016.1.2, 2016.2.0, 2016.2.1, 2016.2.2, 2016.2.3, 2016.2.4, 2016.2.5, 2016.2.6, 2017a5, 2017a6, 2017a7, 2017a8, 2017a10, 2017.0, 2017.1, 2017.1.1, 2017.1.2, 2017.2.0, 2017.2.1, 2017.2.2, 2017.2.3, 2017.2.4, 2017.2.5, 2017.2.6, 2018a6, 2018a7, 2018a8, 2018a9, 2018a10, 2018.0, 2018.1, 2018.1.1, 2018.1.2, 2018.2.0, 2018.2.1, 2018.2.2, 2018.2.3, 2018.2.4, 2018.2.5, 2018.2.6, 2019a7, 2019a8, 2019a9, 2019a10, 2019.0, 2019.1, 2019.1.1, 2019.1.2, 2019.2.0, 2019.2.1, 2019.2.2, 2019.2.3, 2019.2.4, 2019.2.5, 2019.2.6, 2020a8, 2020a9, 2020a10, 2020.0, 2020.1, 2020.1.1, 2020.1.2, 2020.2.0, 2020.2.1, 2020.2.2, 2020.2.3, 2020.2.4, 2020.2.5, 2020.2.6, 2021a9, 2021a10, 2021.0, 2021.1, 2021.1.1, 2021.1.2, 2021.2.0, 2021.2.1, 2021.2.2, 2021.2.3, 2021.2.4, 2021.2.5, 2021.2.6, 2022a10, 2022.0, 2022.1, 2022.1.1, 2022.1.2, 2022.2.0, 2022.2.1, 2022.2.2, 2022.2.3, 2022.2.4, 2022.2.5, 2022.2.6)
ERROR: No matching distribution found for abqpy==2021.*.*

Is that the correct way to use it, or am I doing something wrong?

How about using pip install abqpy==2021.*?

pip install abqpy==2021.* seems the right way, in the README.md, I suggest this, but I may make a mistake in the documentation.

If so, we need to change it every time we publish a new release, I found it annoying so I just leave it like this.

May be we can use a workflow like find and replace to change it before publishing.

How about using pip install abqpy==2021.*?

This is a strange behavior.

How about using pip install abqpy==2021.*?

Yes! That worked. BTW, in the documentation, it is suggesting an older version
pip install abqpy==2021.1.1

Maybe, there is a way to put the current version in this suggestion

I came up with a soution in #1107.


Flaky test: ProducerTest.testWaitForExclusiveProducer

example failure
FAILED TESTS (1/376):
     166 ms: ./pulsar-tests ProducerTest.testWaitForExclusiveProducer (try #1)

[ RUN      ] ProducerTest.testWaitForExclusiveProducer
2022-12-01 06:25:37.989 INFO  [140250769911488] ClientConnection:189 | [<none> -> pulsar://localhost:6650] Create ClientConnection, timeout=10000
2022-12-01 06:25:37.989 INFO  [140250769911488] ConnectionPool:97 | Created connection for pulsar://localhost:6650
2022-12-01 06:25:37.991 INFO  [140250766808640] ClientConnection:379 | [[::1]:37744 -> [::1]:6650] Connected to broker
2022-12-01 06:25:37.997 INFO  [140250766808640] HandlerBase:72 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-1] Getting connection from pool
2022-12-01 06:25:38.038 INFO  [140250766808640] ProducerImpl:190 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-1] Created producer on broker [[::1]:37744 -> [::1]:6650]
2022-12-01 06:25:38.043 INFO  [140250769911488] ProducerImpl:721 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-1] Closing producer for topic persistent://public/default/testWaitForExclusiveProducer1669875937
2022-12-01 06:25:38.044 INFO  [140250766808640] ProducerImpl:687 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-1] Closed producer 0
2022-12-01 06:25:38.045 INFO  [140250766808640] HandlerBase:72 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-2] Getting connection from pool
2022-12-01 06:25:38.053 INFO  [140250766808640] ProducerImpl:190 | [persistent://public/default/testWaitForExclusiveProducer1669875937, p-name-2] Created producer on broker [[::1]:37744 -> [::1]:6650]
/home/runner/work/pulsar-client-cpp/pulsar-client-cpp/tests/ProducerTest.cc:331: Failure
Expected equality of these values:
  ResultOk
    Which is: Ok
  producer2.send(MessageBuilder().setContent("content").build())
    Which is: ProducerNotInitialized

Another failure
[ RUN      ] ProducerTest.testWaitForExclusiveProducer

2023-03-24 08:16:50.796 INFO  [140716606979840] ClientConnection:183 | [<none> -> pulsar://localhost:6650] Create ClientConnection, timeout=10000
2023-03-24 08:16:50.796 INFO  [140716606979840] ConnectionPool:106 | Created connection for pulsar://localhost:6650
2023-03-24 08:16:50.799 INFO  [140716603856448] ClientConnection:381 | [[::1]:35688 -> [::1]:6650] Connected to broker
2023-03-24 08:16:50.800 INFO  [140716603856448] HandlerBase:72 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-1] Getting connection from pool
2023-03-24 08:16:50.807 INFO  [140716603856448] ProducerImpl:208 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-1] Created producer on broker [[::1]:35688 -> [::1]:6650]
2023-03-24 08:16:50.811 INFO  [140716606979840] ProducerImpl:755 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-1] Closing producer for topic 0x7ffb1c003ae0
2023-03-24 08:16:50.812 INFO  [140716603856448] HandlerBase:72 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-2] Getting connection from pool
2023-03-24 08:16:50.812 INFO  [140716603856448] ProducerImpl:719 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-1] Closed producer 0
2023-03-24 08:16:50.813 INFO  [140716603856448] ProducerImpl:208 | [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-2] Created producer on broker [[::1]:35688 -> [::1]:6650]
/home/runner/work/pulsar-client-cpp/pulsar-client-cpp/tests/ProducerTest.cc:332: Failure
Expected equality of these values:
  ResultOk
    Which is: Ok
  producer2.send(MessageBuilder().setContent("content").build())
    Which is: ProducerNotInitialized
2023-03-24 08:16:50.814 INFO  [140716606979840] ProducerImpl:709 | Producer - [persistent://public/default/testWaitForExclusiveProducer1679645810, p-name-1] , [batchMessageContainer = { BatchMessageContainer [size = 0] [bytes = 0] [maxSize = 1000] [maxBytes = 131072] [topicName = 0x7ffb1c003ae0] [numberOfBatchesSent_ = 2] [averageBatchSize_ = 0.5] }]


having problem with the import

having
 _sql-formatter<EMAIL_ADDRESS>TypeScript error in D:/works/web/dbo/node_modules/_sql-formatter@7.0.0@sql-formatter/lib/src/core/Params.d.ts(1,15):
',' expected.  TS1005

  > 1 | import { type Token } from './token';
      |               ^
    2 | export declare type ParamItems = {
    3 |     [k: string]: string;
    4 | };

Usage

How are you calling / using the library?

with react
import { format } from 'sql-formatter';
console.log(format(''));

    "typescript": "^4.0.3",

is it the reason that  my type script version too low ?

Yes, you'll need to updated to TS ^4.5

Yes, you'll need to update to TS ^4.5

I'll try, if it works i'll close this issue.
btw,  do you consider surpporting lower versions of typescript?


Add utils and common initial folders and reorganize code and plugins

This PR removes the dependency between template-coq and PCUIC and reorganize plugins in proper directories

This PR is still having some plugins and opam packages issues to be fixed

It is almost ready now, the only issue is that the nix compilation does not let me define opam package that contains several folders easily so I have done one package per folder to start with. The reason is that package and folder names are supposed to be inlined in several places in the scripts (e.g., touch ${pkgpath}/metacoq-config in default.nix.

We decide for now that having a correspondance between opam packages and folders is more robust (even if more verbose).


exception not displayed in console

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
OS Version: Windows_NT x64 10.0.14393
Extensions:

Extension
Author (truncated)
Version

debugger-for-chrome
msj
3.3.0

require('async_hooks').createHook({
  init: () => {
    process._rawDebug("you won't see mee");
    a.b = c; // crash
  }
}).enable();

Promise.resolve().then(()=>{
  console.log("me neither");
});

I'm writing code using async_hooks magic and it seems that process._rawDebug does not appear in the console anymore. Worst, if a crash happens in a hook then you won't have any indication that it happened. I spent 4 hours debugging this :(

Reproduces without extensions: Yes

process._rawDebug goes directly to stderr and skips the debug protocol. I don't recommend using that in general. But you can also check out the insiders build and set "outputCapture": "std".
https://github.com/Microsoft/vscode/issues/19750

It's not only that, the debugger does not catch the exceptions happening in hooks, the debugging session just exits without any indication that something has gone wrong.

Do you have the button checked to break on all exceptions? Does it work differently with chrome devtools?

Tried the sample code with chrome devtools and I get the same behavior. Node.js bug?

Thanks for trying that. Sounds like it could be a node bug, you can open an issue on https://github.com/nodejs/node


Add a comparison function to show what has changed on an object

Fixed by 740a11a, use MetatlasObject.show_diff


[BUG] RedHat 7.0 - fiftyone.core.service.DatabaseService failed to bind to port

System information

OS Platform and Distribution : Red Hat Enterprise Linux Workstation VERSION="7.5
FiftyOne installed from (pip or source): pip install fiftyone
FiftyOne version (run fiftyone --version): fiftyone v0.11.1, Voxel51, Inc.
Python version: Python 3.7.10 ( conda env)

Commands to reproduce

pip install fiftyone
Installed mongodb-org-server-4.4.6 system wide using dzdo account on RedHat because of import error RuntimeError: Could not find mongod >= 4.4
python
import fiftyone as fo

Describe the problem

Installed the fiftyone library on  Redhat 7 using pip in conda env
Installed mongodb-org-server-4.4.6 system wide using dzdo account ont RH because of import error RuntimeError: Could not find mongod >= 4.4
Mongodb  is running
 mongod --version db version v4.4.6 Build Info: {        "version": "4.4.6",        "gitVersion": "72e66213c2c3eab37d9358d5e78ad7f5c1d0d0d7",        "openSSLVersion": "OpenSSL 1.0.1e-fips 11 Feb 2013",        "modules": [],        "allocator": "tcmalloc",        "environment": {            "distmod": "rhel70",            "distarch": "x86_64",            "target_arch": "x86_64"  } }
When i import fiftyone in python i get the error fiftyone.core.service.ServiceListenTimeout: fiftyone.core.service.DatabaseService failed to bind to port

[/data_local/workspace/conda_amine] l0494241@xrai-frpau-132 ~ → python

Python 3.7.10 (default, Jun  4 2021, 14:48:32)

[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import fiftyone as fo
{"t":{"$date":"2021-07-02T09:17:38.359Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"/users/l0494241/~/.fiftyone/var/lib/mongo/log/mongo.log","newLogPath":"/users/l0494241/~/.fiftyone/var/lib/mongo/log/mongo.log.2021-07-02T09-17-38"}}
Subprocess ['/usr/bin/mongod', '--dbpath', '~/.fiftyone/var/lib/mongo', '--logpath', '~/.fiftyone/var/lib/mongo/log/mongo.log', '--port', '0', '--nounixsocket'] exited with error -6:
Uncaught exception
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/__init__.py", line 25, in <module>
    from fiftyone.__public__ import *
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/__public__.py", line 11, in <module>
    _database_service = fos.DatabaseService()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 203, in __init__
    super().__init__()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 81, in __init__
    self.start()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 293, in start
    food.set_default_port(self.port)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 283, in port
    return self._wait_for_child_port()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 180, in _wait_for_child_port
    return find_port()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 212, in call
    raise attempt.get()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/six.py", line 719, in reraise
    raise value
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 178, in find_port
    raise ServiceListenTimeout(etau.get_class_name(self), port)
**fiftyone.core.service.ServiceListenTimeout: fiftyone.core.service.DatabaseService failed to bind to port**`

Other info / logs
When looking at similar issues i tried to run the mongod from the env but got and error :
`[/data_local/workspace/conda_amine] l0494241@xrai-frpau-132 bin → /data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/db/bin/mongod --version
/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/db/bin/mongod: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory`

Also running directly the command  /usr/bin/mongod --dbpath /users/l0494241/.fiftyone/var/lib/mongo \ --logpath /users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log \ --port 0 --nounixsocket

gives a core dump error :
[/data_local/workspace/conda_amine] l0494241@xrai-frpau-132 ~ → /usr/bin/mongod --dbpath /users/l0494241/.fiftyone/var/lib/mongo \
> --logpath /users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log \
> --port 0 --nounixsocket
{"t":{"$date":"2021-07-02T12:14:54.579Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log","newLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log.2021-07-02T12-14-54"}}
**Aborted (core dumped)**

We also have a disk quota limit on our home ( /users/ID) where the .fiftyone directory is created, this may be the issue, how can i configure fiftyone to use other directory for sertup ?

Thanks for your help
Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently.
[ X ] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community.
[ ] No. I cannot contribute a bug fix at this time.

Hi @AmineDiro. I am unsure if we have had any successfully use fiftyone on RHEL. But it is something we can try to work out.
The first thing I would recommend is to clear your mongo data folder, and then try again with your system install of mongo.
rm -r /users/l0494241/.fiftyone/var/lib/mongo

Thanks a lot for your help,
i rm - rf  I am still having the same issue.
From my understanding the init calls __public__ which initalizes the DatabaseService class.
In the class we call  `DatabaseService.find_mongod()``which search for available mongod_path .
For me i debugged by printing the  mongod_path
mogod_path /data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/db/bin/mongod
mogod_path /usr/bin/mongod

Now after rerunning  i have this error  :
{"t":{"$date":"2021-07-02T16:17:00.976Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log","newLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log.2021-07-02T16-17-00"}}
Subprocess ['/usr/bin/mongod', '--dbpath', '/users/l0494241/.fiftyone/var/lib/mongo', '--logpath', '/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log'] exited with error 1:
}
  Frame: {"a":"55C41D55F94E","b":"55C41C598000","o":"FC794E","s":"_start","s+":"29"},"s":"_ZN5mongo8executor18NetworkInterfaceTLC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_14ConnectionPool7OptionsEPNS_14ServiceContextESt10unique_ptrINS0_21NetworkConnectionHookESt14default_deleteISD_EESC_INS_3rpc18EgressMetadataHookESE_ISI_EE","s+":"E88"}
  Frame: {"a":"55C41ECB47CD","b":"55C41C598000","o":"271C7CD","s":"_ZN5mongo8executor20makeNetworkInterfaceENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10unique_ptrINS0_21NetworkConnectionHookESt14default_deleteIS8_EES7_INS_3rpc18EgressMetadataHookES9_ISD_EENS0_14ConnectionPool7OptionsE","s+":"18D"}
  Frame: {"a":"55C41D563565","b":"55C41C598000","o":"FCB565","s":"_ZN5mongo12_GLOBAL__N_116setUpReplicationEPNS_14ServiceContextE","s+":"405"}
  Frame: {"a":"55C41D563FA2","b":"55C41C598000","o":"FCBFA2","s":"_ZN5mongo12_GLOBAL__N_111mongoDbMainEiPPcS2_","s+":"2C2"}
  Frame: {"a":"55C41D4D7029","b":"55C41C598000","o":"F3F029","s":"main","s+":"9"}
  Frame: {"a":"7F8F7D4463D5","b":"7F8F7D424000","o":"223D5","s":"__libc_start_main","s+":"F5"E.constprop.606","s+":"1EA"}
  Frame: {"a":"55C41F32AD4A","b":"55C41C598000","o":"2D92D4A","s":"_ZN5mongo15printStackTraceERSo","s+":"3A"}
  Frame: {"a":"55C41F2F3D4D","b":"55C41C598000","o":"2D5BD4D","s":"_ZN5mongo5logv214FileRotateSink7consumeERKN5boost3log12v2s_mt_posix11record_viewERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE","s+":"50D"}
  Frame: {"a":"55C41F30B4E3","b":"55C41C598000","o":"2D734E3","s":"_ZN5boost3log12v2s_mt_posix5sinks13unlocked_sinkIN5mongo5logv216CompositeBackendIJNS5_14FileRotateSinkENS5_10RamLogSinkES8_NS5_14UserAssertSinkEEEEE7consumeERKNS1_11record_viewE","s+":"213"}
  Frame: {"a":"55C41F440223","b":"55C41C598000","o":"2EA8223","s":"_ZN5boost3log12v2s_mt_posix4core16push_record_moveERNS1_6recordE","s+":"1D3"}
  Frame: {"a":"55C41F2FF3E2","b":"55C41C598000","o":"2D673E2","s":"_ZN5mongo5logv26detail9doLogImplEiRKNS0_11LogSeverityERKNS0_10LogOptionsENS_10StringDataERKNS0_26TypeErasedAttributeStorageE","s+":"682"}
  Frame: {"a":"55C41ECCE138","b":"55C41C598000","o":"2736138"plicationEPNS_14ServiceContextE","s+":"405"},{"a":"55C41D563FA2","b":"55C41C598000","o":"FCBFA2","s":"_ZN5mongo12_GLOBAL__N_111mongoDbMainEiPPcS2_","s+":"2C2"},{"a":"55C41D4D7029","b":"55C41C598000","o":"F3F029","s":"main","s+":"9"},{"a":"7F8F7D4463D5","b":"7F8F7D424000","o":"223D5","s":"__libc_start_main","s+":"F5"},{"a":"55C41D55F94E","b":"55C41C598000","o":"FC794E","s":"_start","s+":"29"}],"processInfo":{"mongodbVersion":"4.4.6","gitVersion":"72e66213c2c3eab37d9358d5e78ad7f5c1d0d0d7","compiledModules":[],"uname":{"sysname":"Linux","release":"3.10.0-862.14.4.el7.x86_64","version":"#1 SMP Fri Sep 21 09:07:21 UTC 2018","machine":"x86_64"},"somap":[{"b":"55C41C598000","elfType":3,"buildId":"312311B4128B98F2F0502772FB85CC572CDDD0A1"},{"b":"7F8F7D424000","path":"/lib64/libc.so.6","elfType":3,"buildId":"85EA0AE559B53AB60D8548242CEDD0E83F4816DA"}]}}

Also after reinstalling mongod-server i could not start the service :
● mongod.service - MongoDB Database Server
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2021-07-02 18:19:53 CEST; 4s ago
     Docs: https://docs.mongodb.org/manual
  Process: 26387 ExecStart=/usr/bin/mongod $OPTIONS (code=exited, status=14)
  Process: 26384 ExecStartPre=/usr/bin/chmod 0755 /var/run/mongodb (code=exited, status=0/SUCCESS)
  Process: 26380 ExecStartPre=/usr/bin/chown mongod:mongod /var/run/mongodb (code=exited, status=0/SUCCESS)
  Process: 26376 ExecStartPre=/usr/bin/mkdir -p /var/run/mongodb (code=exited, status=0/SUCCESS)
 Main PID: 15578 (code=exited, status=0/SUCCESS)

Jul 02 18:19:53 xrai-frpau-132 systemd[1]: Starting MongoDB Database Server...
Jul 02 18:19:53 xrai-frpau-132 mongod[26387]: about to fork child process, waiting until server is ready for connections.
Jul 02 18:19:53 xrai-frpau-132 mongod[26387]: forked process: 26390
Jul 02 18:19:53 xrai-frpau-132 mongod[26387]: ERROR: child process failed, exited with 14
Jul 02 18:19:53 xrai-frpau-132 mongod[26387]: To see additional information in this output, start without the "--fork" option.
Jul 02 18:19:53 xrai-frpau-132 systemd[1]: mongod.service: control process exited, code=exited status=14
Jul 02 18:19:53 xrai-frpau-132 systemd[1]: Failed to start MongoDB Database Server.
Jul 02 18:19:53 xrai-frpau-132 systemd[1]: Unit mongod.service entered failed state.
Jul 02 18:19:53 xrai-frpau-132 systemd[1]: mongod.service failed.

I am pretty stuck at this level , running mongod with --dbpath does not work either :/ .

Well , I found the issue with the mongod server not running it was a port issue, now i changed it to runn on 8889 , i also changed the value in command property of DatabaseService :
262     @property
263     def command(self):
264         args = [
265             DatabaseService.find_mongod(),
266             "--dbpath",
267             self.database_dir,
268             "--logpath",
269             os.path.join(self.database_dir, "log/mongo.log"),
270             "--port",
271             "8889",
272         ]

Now the mongod server is running 👍
-bash-4.2$ dzdo systemctl status mongod
● mongod.service - MongoDB Database Server
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2021-07-02 19:33:14 CEST; 9min ago
     Docs: https://docs.mongodb.org/manual
 Main PID: 1797 (mongod)
   CGroup: /system.slice/mongod.service
           └─1797 /usr/bin/mongod -f /etc/mongod.conf

Jul 02 19:33:12 xrai-frpau-132 systemd[1]: Starting MongoDB Database Server...
Jul 02 19:33:13 xrai-frpau-132 mongod[1794]: about to fork child process, waiting until server is ready for connections.
Jul 02 19:33:13 xrai-frpau-132 mongod[1794]: forked process: 1797
Jul 02 19:33:14 xrai-frpau-132 mongod[1794]: child process started successfully, parent exiting
Jul 02 19:33:14 xrai-frpau-132 systemd[1]: Started MongoDB Database Server.

But there is still the same issue when importing the the DatabaseService 😞 :
Python 3.7.10 (default, Jun  4 2021, 14:48:32)
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import fiftyone as fo
mogod_path /data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/db/bin/mongod
mogod_path /usr/bin/mongod
{"t":{"$date":"2021-07-02T17:39:48.743Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log","newLogPath":"/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log.2021-07-02T17-39-48"}}
Subprocess ['/usr/bin/mongod', '--dbpath', '/users/l0494241/.fiftyone/var/lib/mongo', '--logpath', '/users/l0494241/.fiftyone/var/lib/mongo/log/mongo.log', '--port', '8889', '--nounixsocket'] exited with error 1:
}
  Frame: {"a":"55737546E94E","b":"5573744A7000","o":"FC794E","s":"_start","s+":"29"},"s":"_ZN5mongo8executor18NetworkInterfaceTLC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_14ConnectionPool7OptionsEPNS_14ServiceContextESt10unique_ptrINS0_21NetworkConnectionHookESt14default_deleteISD_EESC_INS_3rpc18EgressMetadataHookESE_ISI_EE","s+":"E88"}
  Frame: {"a":"557376BC37CD","b":"5573744A7000","o":"271C7CD","s":"_ZN5mongo8executor20makeNetworkInterfaceENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt10unique_ptrINS0_21NetworkConnectionHookESt14default_deleteIS8_EES7_INS_3rpc18EgressMetadataHookES9_ISD_EENS0_14ConnectionPool7OptionsE","s+":"18D"}  Frame: {"a":"557375472565","b":"5573744A7000","o":"FCB565","s":"_ZN5mongo12_GLOBAL__N_116setUpReplicationEPNS_14ServiceContextE","s+":"405"}
  Frame: {"a":"557375472FA2","b":"5573744A7000","o":"FCBFA2","s":"_ZN5mongo12_GLOBAL__N_111mongoDbMainEiPPcS2_","s+":"2C2"}
  Frame: {"a":"5573753E6029","b":"5573744A7000","o":"F3F029","s":"main","s+":"9"}
  Frame: {"a":"7EFCED2E33D5","b":"7EFCED2C1000","o":"223D5","s":"__libc_start_main","s+":"F5"E.constprop.606","s+":"1EA"}
  Frame: {"a":"557377239D4A","b":"5573744A7000","o":"2D92D4A","s":"_ZN5mongo15printStackTraceERSo","s+":"3A"}
  Frame: {"a":"557377202D4D","b":"5573744A7000","o":"2D5BD4D","s":"_ZN5mongo5logv214FileRotateSink7consumeERKN5boost3log12v2s_mt_posix11record_viewERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE","s+":"50D"}
  Frame: {"a":"55737721A4E3","b":"5573744A7000","o":"2D734E3","s":"_ZN5boost3log12v2s_mt_posix5sinks13unlocked_sinkIN5mongo5logv216CompositeBackendIJNS5_14FileRotateSinkENS5_10RamLogSinkES8_NS5_14UserAssertSinkEEEEE7consumeERKNS1_11record_viewE","s+":"213"}
  Frame: {"a":"55737734F223","b":"5573744A7000","o":"2EA8223","s":"_ZN5boost3log12v2s_mt_posix4core16push_record_moveERNS1_6recordE","s+":"1D3"}
  Frame: {"a":"55737720E3E2","b":"5573744A7000","o":"2D673E2","s":"_ZN5mongo5logv26detail9doLogImplEiRKNS0_11LogSeverityERKNS0_10LogOptionsENS_10StringDataERKNS0_26TypeErasedAttributeStorageE","s+":"682"}
  Frame: {"a":"557376BDD138","b":"5573744A7000","o":"2736138"plicationEPNS_14ServiceContextE","s+":"405"},{"a":"557375472FA2","b":"5573744A7000","o":"FCBFA2","s":"_ZN5mongo12_GLOBAL__N_111mongoDbMainEiPPcS2_","s+":"2C2"},{"a":"5573753E6029","b":"5573744A7000","o":"F3F029","s":"main","s+":"9"},{"a":"7EFCED2E33D5","b":"7EFCED2C1000","o":"223D5","s":"__libc_start_main","s+":"F5"},{"a":"55737546E94E","b":"5573744A7000","o":"FC794E","s":"_start","s+":"29"}],"processInfo":{"mongodbVersion":"4.4.6","gitVersion":"72e66213c2c3eab37d9358d5e78ad7f5c1d0d0d7","compiledModules":[],"uname":{"sysname":"Linux","release":"3.10.0-862.14.4.el7.x86_64","version":"#1 SMP Fri Sep 21 09:07:21 UTC 2018","machine":"x86_64"},"somap":[{"b":"5573744A7000","elfType":3,"buildId":"312311B4128B98F2F0502772FB85CC572CDDD0A1"},{"b":"7EFCED2C1000","path":"/lib64/libc.so.6","elfType":3,"buildId":"85EA0AE559B53AB60D8548242CEDD0E83F4816DA"}]}}
  Frame: {"a":"55737723827A","b":"5573744A7000","o":"2D9127A","s":"_ZN5mongo18stack_trace_detail12_GLOBAL__N_119printStackTraceImplERKNS1_7OptionsEPNS_14StackTraceSinkUncaught exception
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/__init__.py", line 25, in <module>
    from fiftyone.__public__ import *
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/__public__.py", line 11, in <module>
    _database_service = fos.DatabaseService()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 203, in __init__
    super().__init__()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 81, in __init__
    self.start()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 293, in start
    food.set_default_port(self.port)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 283, in port
    return self._wait_for_child_port()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 180, in _wait_for_child_port
    return find_port()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 212, in call
    raise attempt.get()
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/six.py", line 719, in reraise
    raise value
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/data_local/workspace/conda_amine/lib/python3.7/site-packages/fiftyone/core/service.py", line 178, in find_port
    raise ServiceListenTimeout(etau.get_class_name(self), port)
fiftyone.core.service.ServiceListenTimeout: fiftyone.core.service.DatabaseService failed to bind to port

Hi @AmineDiro. Pardon the delay. I think what would be easiest until we can officially support RHEL (soon) is a quick patch that assumes you are running your own mongod service.
All you should need to do is replace this line with
import fiftyone.core.odm.database as food
food.set_default_port(27017) # change to your mongo service port
food.get_db_conn()

Again, you should replace or comment out the line starts that initializes the DatabaseService.

Hello thanks for the help again :smiley:
I would love to contribute to the support of RHEL (what would be the step to contribute on this ? )
i changes __public__ to :
 11  #_database_service = fos.DatabaseService()
 12  import fiftyone.core.odm.database as food
 13  food.set_default_port(8889) # change to your mongo service port
 14  food.get_db_conn()

Now everything is ok :
Python 3.7.10 (default, Jun  4 2021, 14:48:32)
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import fiftyone as fo
>>> dataset = fo.Dataset("test-dataset")
>>> print(dataset)
Name:        test-dataset
Media type:  None
Num samples: 0
Persistent:  False
Tags:        []
Sample fields:
    id:       fiftyone.core.fields.ObjectIdField
    filepath: fiftyone.core.fields.StringField
    tags:     fiftyone.core.fields.ListField(fiftyone.core.fields.StringField)
    metadata: fiftyone.core.fields.EmbeddedDocumentField(fiftyone.core.metadata.Metadata)
>>> print(fo.config)
{
    "database_dir": "/users/l0494241/.fiftyone/var/lib/mongo",
    "dataset_zoo_dir": "/users/l0494241/fiftyone",
    "dataset_zoo_manifest_paths": null,
    "default_app_port": 5151,
    "default_batch_size": null,
    "default_dataset_dir": "/users/l0494241/fiftyone",
    "default_image_ext": ".jpg",
    "default_ml_backend": "torch",
    "default_sequence_idx": "%06d",
    "default_video_ext": ".mp4",
    "desktop_app": false,
    "do_not_track": false,
    "model_zoo_dir": "/users/l0494241/fiftyone/__models__",
    "model_zoo_manifest_paths": null,
    "requirement_error_level": 0,
    "show_progress_bars": true
}

You'd need to add the download url option to the db package's setup.py. And add a new rhel package like debian9.
https://github.com/voxel51/fiftyone/blob/develop/package/db/setup.py
In the end, the changes should allow for the following build command:
FIFTYONE_DB_BUILD_LINUX_DISTRO=rhel python setup.py bdist_wheel --plat-name linux-x86_64

I should note that I was able to install and use fiftyone on a rhel 8 docker image, but I was not able to find a rhel 7 image. Perhaps I should check CentOS 7.

Great Thanks for the guidance. I'll start working on this. :+1:


import fails on cue eval within cue.mod/pkg

What version of CUE are you using (cue version)?

$ cue version
cue version 0.3.0-alpha4 darwin/amd64

Does this issue reproduce with the latest release?

Last stable release: yes
Last alpha release: yes

What did you do?
$ cat > repro.sh <<'EOF'
#!/bin/bash

set -e

# Create package to be imported
DIR_FOO=cue.mod/pkg/foo.com/foo
mkdir -p "$DIR_FOO"
echo 'package foo' > "$DIR_FOO"/foo.cue

# Create package from which to import
DIR_BAR=cue.mod/pkg/bar.com/bar
mkdir -p "$DIR_BAR"

# This works
echo -e 'import "foo.com/foo"\nfoo' | cue eval - >/dev/null && echo "Import from module root: OK"

# This doesn't work
cd $DIR_BAR && echo -e 'import "foo.com/foo"\nfoo' | cue eval - >/dev/null && echo "Import from within cue.mod/pkg/: OK"
EOF

$ bash repro.sh

What did you expect to see?
Import from module root: OK
Import from within cue.mod/pkg/: OK

What did you see instead?
Import from module root: OK
import failed: cannot find package "foo.com/foo":
    -:1:8

are you trying to navigate into the cue.mod dir and run typical cue commands, and expecting that it ought to work as if from a normal cue module with a mod dir and packages?
iirc, the way imports work is much like Go and (again) iirc only one layer of modules is imported, so that when you run the command in from within the cue mod dir, it would need essentially the same mod dir from wherever you are trying to run the command. That is to say cue is not walking back up the directory structure to find the correct root dir of your module which has the original cue.mod dir.
Does this sound about right?

Yes that’s exactly right. I expected a “git-like” behavior of walking back up to find the current cue.mod.
I often find myself in an interactive shell typing “cue eval” within the directory of the package I’m developing or testing. This is in the context of developing a standard library so there is no “primary” package at the root of the module. The cue.mod itself is the project.

On Oct 5, 2020, at 7:44 PM, Tony Worm<EMAIL_ADDRESS>wrote:

are you trying to navigate into the cue.mod dir and run typical cue commands, and expecting that it ought to work as if from a normal cue module with a mod dir and packages?
iirc, the way imports work is much like Go and (again) iirc only one layer of modules is imported, so that when you run the command in from within the cue mod dir, it would need essentially the same mod dir from wherever you are trying to run the command. That is to say cue is not walking back up the directory structure to find the correct root dir of your module which has the original cue.mod dir.
Does this sound about right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

This issue has been migrated to https://github.com/cue-lang/cue/issues/551.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


added cypress test for global setting menu

Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Closing this as it will added in
#6677 feat(ui): support slack Webhook integration on settings


Rotary_pos_emb Miss?

I have a question about the Rotary_pos_emb function in llama. I have not find this function in the code, and I can only guess that it has been implemented in _kernels.batch_decode( in the batch_decode function?
So if i want to find Rotary_pos_emb, I need to check flashinfer's code?

Correct. Position embedding is within the attention kernel. Punica just calls FlashInfer. https://github.com/punica-ai/punica/blob/591b59899f0a20760821785d06b331c8a2e5cb86/csrc/flashinfer_adapter/flashinfer_all.cu#L96

Thank you for your prompt answer!
btw, punica is a very rewarding job.

Thanks!


Add PriorityQueue constructor accepting array as argument

Hi!
This PR doesn't have a link to a Jira Issue as according to contribution guidelines I can either create a patch and attach it to an issue on Jira or open a pull request - let me know if I misunderstood things and have to create a Jira issue anyway.
Description
PriorityQueue class doesn't have a constructor accepting array/collection and I created one for the cases, when heap elements are known in advance to save some time on queue creation: O(N) (heapify) vs Nlog(N) (calling add() in loop).
Solution
JDK PriorityQueue has a constructor, accepting Collection and it internally uses heapify - this PR is basically adaptation of this method (index is not 0 but 1 based and no need to check comparator presence).
Tests
I added a test creating a queue filled by random elements with the new method and checking its validity. Also added a potential usage (just took randomly first usage of add) and it didn't cause any failures.
Tried to run benchmarks using https://github.com/mikemccand/luceneutil but
got an error
src/python/competition.py", line 302
    raise ValueError(f'mode must be "cpu" or "heap" but got: {mode}')

may I ask is there any detailed guide on running Lucene benchmarks?
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ ] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.

Maybe add a method called addAll(Collection) which would be smart enough to detect when it can use this accelerated addition instead of element-by-element addition? I'm not sure an additional constructor is needed here.

Maybe add a method called addAll(Collection) which would be smart enough to detect when it can use this accelerated addition instead of element-by-element addition? I'm not sure an additional constructor is needed here.

Good point with Collection, thanks. No need to convert list to array if we don't use it directly anyway (because of 1-index shift) - can rather copy from collection.
It's always possible to build a heap if elements are provided and comparable - in JDK they check what kind of collection is provided and take comparator from it - but here we have lessThan. My understanding is that user decides whether it's possible to use faster addition - one of use cases when add() are not interrupted by pop() or any other structure changing operations, i.e when we build first and only then do something.
I added a constructor as other option would be to use existing ones and then do smth like addAll(items) - but I wanted to avoid usage of default constructor, filling it with sentinel null objects. But I actually found an issue in my constructor - need to add maxSize >= ArrayUtil.MAX_ARRAY_LENGTH check there, thanks!
Would it it be fine if I keep the constructor but adjust it to copy directly from Collection and add a size check?

I wanted to avoid usage of default constructor, filling it with sentinel null objects

In all honesty, this is probably not something you can ever, ever notice when you compare the cost of building the heap with clearing a chunk of memory. And it makes the API simpler in my opinion. But sure, you can keep the constructor.

Fair point, I changed it to addAll. Also added a case to add into partially filled queue - just realized that you probably meant this use case and I misunderstood it.

I've added a proper issue number (https://issues.apache.org/jira/browse/LUCENE-10494) and tweaked minor details of the implementation (exception types thrown in addAll and add were different). I think it's good to go.

Thank you!

Thanks!


capture unable to recognize dag stream as interface

Elasticsearch version: 5.6
Moloch version: 1.0.0
OS name and version:centos 7
How was Moloch built/installed:easybutton install
I am trying to install moloch 1.0.0 with DAG functionality, I have referred to issue #681, but the fix they suggested doesn't seem to fix my issue, when I go through the entire setup process with their steps either it fails to recognize dag0:0 as a device and references one of the reader_pcap shared objects or it won't even execute the capture binary in dryrun, and complains that it can't locate my libdag shared objects. Has anyone figured out a sound method of building moloch 1.0.0 to support DAG interfaces? I seem to remember there may used to have been a with-dag option when running ./configure in the moloch directory when you untar the source code. Thanks in advance for any input.

Oh, I was getting daq and dag confused.  We have a daq reader https://github.com/aol/moloch/wiki/Settings#Reader_daq_Settings
Make sure you are linking against the dag libpcap file, and if it can find stuff when running try setting your LD_LIBRARY_PATH

How much would it break if i forced it to use libpcap-1.7.x instead of 1.8.1? I've tried building 1.8.1 --with-dag and then built moloch off of that but it always fails to recognize the interface.

Also, does the capture binary build completely off of libpcap.so?

It shouldn't break anything.  You just need to rebuild libpcap your self with dag and then make sure it all links.

what would be the easiest way to point moloch at my libpcap during the build process, seems like there are a lot of moving parts inside the easybutton script

Something like:

edit easybutton-build and change the libpcap build line to include the options you need
edit the capture/Makefile.in and add -ldag after the -lyaml
run easybutton-build

you could also just go build libpcap manually after running once with no mods

I tried doing the build normally, then go back and rebuild libpcap --with-dag and then running make install and make config, and it still doesn't recognize the interface

after rebuilding libpcap you have to rebuild moloch-capture since its using the static version of libpcap.  If you are I can't really help since I don't use dag.  you can do a nm moloch-capture | grep dag and make sure you see stuff, if you don't it probably hasn't actually linked against the dag library.

on the plus side i did get a ton of results from the nm command

I just chanced across this, so I expect the thread is cold. Did you contact Endace support?
Libpcap 1.8.1 has a bug building against the DAG libraries. You can either use libpcap 1.7.4, or Github master. Unfortunately we have been waiting a long time for a new stable libpcap release.
Does the libpcap 'findalldevstest' test program find the card?


Reading a list of CSV files will result in a blank line

Reading a list of CSV files will result in a blank line
funtion
xlsx.read(buffer, {
       type: 'binary',
       raw: true
}

Can you share what buffer actually is?  Is it a string?  when type is binary the input is expected to be a string whose character codes are between 0 and 255

Please follow up with some more details and we can reopen


Add analyze bundles example

Resolve #5329

Create analyze bundles example
Housekeeping old example with-webpack-bundle-analyzer
Modified both READEME.md

This PR looks incredible, thank you very much @echoulen 🙏


Error when submitting via AJAX

I'd really like AJAX form submission to work with your excellent plugin. But it doesn't.  Since it throws an error, I hope you don't mind that I'm submitting this as a new issue instead of the comments I posted on this closed issue.  I do hope it is an easy fix to get your plugin to work with AJAX.
Steps taken:

Download and install latest grav v 1.6.26
bin/gpm install form mailchimp
Add a page '/user/pages/03.contact/form.md'

'/user/pages/03.contact/form.md':
---
title: Contact

form:
   name: ajax-test-form
   template: form-messages
   action: '/contact'
   refresh_prevention: true

   fields:
      name:
         label: Your Email
         type: email

   buttons:
      submit:
         type: submit
         value: Submit

   process:
      mailchimp:
        lists: []
      message: 'Thank you for your submission!'
---

Submit form while recording network log in Chrome devtools.

Result: No form submission and no success message.  The browser console shows
POST https://mysite.com/contact 500 (Internal Server Error)  jquery-2.x.min.js:4
send @ jquery-2.x.min.js:4
ajax @ jquery-2.x.min.js:4
(anonymous) @ contact:287
dispatch @ jquery-2.x.min.js:3
r.handle @ jquery-2.x.min.js:3

I get this error under Network > Response:
{"error":{"type":"Error","message":"Class 'AaronHipple\\Grav\\Plugin\\MailChimp\\ErrorLoggingMailChimp' not found","file":"\/<PATH TO MY GRAV INSTALL>\/user\/plugins\/mailchimp\/mailchimp.php","line":128}}
I'd be grateful if the plugin can be made to work with AJAX.

Update: I'm a novice, and don't really know what composer is, but I discovered that installing the plugin via the grav gpm causes this issue. However, running composer update resolves the issue. Also, installing the plugin via composer results in no issue.

Any chance on fixing this issue please?


LOS, VRSSI and more insights statistics on NRNG_TAG/NRNG_NODE example

Hi!
I've been testing with the NRNG_TAG / NRNG_NODE examples and everything is working really good but I would need to add
statistics to debug and mitigate in case a Hard-NLOS is found. I've tried to modify the code in many ways together with amend paramers but can not find the way to get them correctly.
I've tried to amend this parameters:
NRNG_VERBOSE: 2
TWR_DS_EXT_NRNG_ENABLED: 1
RNG_VERBOSE: 2
RNG_STATS: 2
NRNG_STATS: 2
UWBCFG_DEF_RX_DIAG_EN: '"1"'

But seems like none of them work. I've also debugged and found out that all statistic values are always set to 0 so it seems like these amend parameters do not work properly.

That's what I ended up doing.
In nrng_encode.c I changed the json filling part to this: (you need to add these parameters in the json struct too)
uint16_t j=0;
for (uint16_t i=0; i < 16; i++){
    if (valid_mask & 1UL << i){
        uint16_t idx = BitIndex(nrng->slot_mask, 1UL << i, SLOT_POSITION);
        nrng_frame_t * frame = nrng->frames[(base + idx)%nrng->nframes];
        struct _twr_data_t * twr_data = (struct _twr_data_t * ) frame->payload;
        if (frame->code == UWB_DATA_CODE_SS_TWR_NRNG_FINAL && frame->seq_num == seq_num){
            json.rng[j] = (dpl_float64_t) uwb_rng_tof_to_meters(nrng_twr_to_tof_frames(nrng->dev_inst, frame, frame));
            json.ouid[j] = frame->dst_address;
            json.rssi[j] = twr_data->rssi;
            json.fppl[j] = twr_data->fppl;
            json.los[j] = uwb_estimate_los(nrng->dev_inst,json.rssi[j],json.fppl[j]);
            j++;
        }
    }
}

Originally, the twr_ss does not add the RSSI and FPPL data into the twr_data thus you need to modify the twr_nrng_ss.c too:
Within the case UWB_DATA_CODE_SS_TWR_NRNG_T1:
            frame->fppl = uwb_get_fppl(nrng->dev_inst);
            frame->rssi = uwb_get_rssi(nrng->dev_inst);

And you'll have the debugging data available!


add open telemetry endpoints for tracing

implement as something that could be in a module (example). determine later if can go into the core.

dupe #290


Fix Redux logo

The old logo used some GitHub token system that expired and the logo disappeared.

Thanks!


Live demo credentials not working

Hello guys,
I tried to take a look into the live demo but I couldn't login in and I get this error
The credentials you entered did not match our records. Try again?
Is it a known issue? Is-it possible for you fix it?
Thank you so much

Any update on this?

Looking into it

Thank you very much @ajitbohra

Any feedback on the demo login?

Perfect, thank you!


Incorrect code Snippet

The code snippet to query the service failure values is missing an extension:
sc qfailure ".NET Joke Service"
[SC] QueryServiceConfig2 SUCCESS

SERVICE_NAME: .NET Joke Service
        RESET_PERIOD (in seconds)    : 0
        REBOOT_MESSAGE               :
        COMMAND_LINE                 :
        FAILURE_ACTIONS              : RESTART -- Delay = 60000 milliseconds.
                                       RESTART -- Delay = 60000 milliseconds.
                                       RUN PROCESS -- Delay = 1000 milliseconds.'

Should be:
sc.exe qfailure ".NET Joke Service"

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

ID: ed148088-4550-2788-0756-390eab15e3f6
Version Independent ID: 64d5cdf8-e50f-0c89-7f16-82645ba6383e
Content: Create a Windows Service using BackgroundService - .NET
Content Source: docs/core/extensions/windows-service.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Hi 👋
Thank you so much for posting this issue. We really appreciate it.
The extension isn't needed, this has always been the case with executables that are part the PATH env var. I'm going to close this issue, unless you have any other questions or concerns.


Implemented mesh_surface_update_x_region functions

Fixes #67700 by implementing the mesh_surface_update_x_region functions.
Implementation partially taken from GLES3 version of mesh_surface_update_region from 3.x and from servers/rendering/rendering_rd/storage_rd/mesh_storage.cpp of master. Basically, binds buffer, set data, and unbind buffer.

Thank you! 🎉 Merged.


Fix/visualization flips

@parijatm
Selectively disable PEX (because it takes a long time on circuits with capacitors.)

This make unit tests work again.


Potentially replace unmaintained libraries ignored in audit.toml.

And revisit other ignores.
https://github.com/near/near-sdk-rs/blob/master/.cargo/audit.toml

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a process engineer and I have a high problem-solving capacity. I am currently co-founder and developer of my own startup.
How I plan on tackling this issue
My work can be divided into 3 stages:

Research new solutions from other updated libraries
Deploy locally to see its usage and avoid errors or problems.
Implement until the desired goal is achieved.

This is my first ODack I hope to contribute a lot, I am available to start immediately

@MPSxDev Go for it!

Research Outcome:
This is the research work carried out, first checking that the repositories are maintained and active, and then verifying the existence of documentation in docs.rs. Below I leave the points found in the audit.toml file
Atty: This is no longer maintained 2 years ago an alternative:

Use std.io.IsTerminal, introduced in Rust 1.70.0 which is part of The Rust Standard Library. Reference docs.rs

Wee_alloc: This has not been maintained for 3 years, a solution may be to implement

WasmTools is highly actively maintained. Reference docs.rs
As a direct replacement for wee_alloc, lol_alloc. Reference docs.rs

curve25519-dalek: Because it has vulnerabilities I found this alternative:

ed25519 Reference docs.rs

I look forward to your comments and any other requests that may be required.

We had a prior discussion about wee_alloc and decided to keep it: https://github.com/near/near-sdk-rs/pull/1151
atty, curve25519-dalek - they are not direct dependencies, right? Can we update any of direct dependencies to fix it?

In the case of atty, they themselves recommend using std.io.IsTerminal since it was incorporated into the Rust Standard Library. Ref IMG

curve25519-dalek appears to have vulnerabilities but using Scalar29::sub (32-bit) and Scalar52::sub which can be solved by adding a volatile read as an optimization barrier as stated in this report: RUSTEC Report

@MPSxDev near-sdk-rs does not directly depend on atty. Please, inspect the dependencies tree to identify which crates we need to update in order to upgrade/eliminate atty and curve25519-dalek. Once identified, we could make a decision whether we can contribute the fix to those dependencies as there is nothing near-sdk-rs can do about it directly.

After a thorough investigation of the packages that include the involved dependencies.
These include the atty dependency:

cargo-near 0.5.2
env_logger 0.9.3

These include ed25519-dalek:

near-crypto 0.23.0 and 0.20.1
near-cli-rs 0.7.8
near-vm-runner 0.20.1 and 0.23.0
slip10 0.4.3

These include curve25519-dalek:

near-crypto 0.23.0 and 0.20.1

Below are the affected packages used, including the current version and whether they continue to use these affected dependencies.

cargo-near: The current version is 0.6.4, last updated on 2024-07-22. It could migrate atty to std.io.IsTerminal, as recommended by atty.
env_logger: There is currently a new version 0.11.5 that does not use atty; it should be updated to this new version.
near-crypto: The current version is 0.23.0 but it is using the affected version of curve25519-dalek, which should be updated to version >=4.1.3. It is also using version 2.1.0 of ed25519-dalek.
near-cli-rs: The current version is 0.13.0 and uses version ed25519-dalek v2.
near-vm-runner: The current version is 0.23.0 and continues to use version 2.1.0 of ed25519-dalek.
slip10: This package is 3 years old and supports ed25519-dalek v1.
ed25519-dalek: The current version is v2.1.1 and should be updated to use curve25519-dalek v4.1.3, which fixes the vulnerability according to this Reference.

In summary, the following steps should be taken:

Migrate from atty to std.io.IsTerminal in cargo-near.
Update env_logger to the latest version.
For near-crypto, near-cli-rs, and near-vm-runner, use versions higher than v2 for ed25519-dalek, which according to rustec.org includes the patch for the vulnerability in versions >=2.
For all mentioned in point 4, since ed25519-dalek uses curve25519-dalek as a dependency, version >=4.1.3 should be used.

@MPSxDev Great summary! We definitely can act on the first two steps immediately. slip10 has been replaced with slipped10, and that should have been subsequently updated in the recent near-cli-rs and cargo-near releases. Can you give it a try upgrading the dependencies and authoring the atty PR to cargo-near as part of this issue?

Thank you very much. Yes, I can try to update this. If I have any questions, I will let you know.

This issue should be closed, I have already done the audit on the latest version and there is no presence of atty and the versions of other dependencies are already updated to versions without the vulnerability. @frol