Fail to finetune on ucf101

Hi, I'm trying to finetune the pretrained model on ucf 101 but I only get 78% accuracy. I wonder have you tried similar settings?

I haven't tried running this code on ucf101, so I'm not sure what performance it should give. According to the paper, it should get to around 98% with two-stream finetuning. But the learning rate, batch size, and number of training iterations will all impact this, and I'm not sure what the right settings for ucf101 are.

@piergiaj Thanks for replying! I'd like to double check training configuration with you. According to charades_dataset.py, the image is normalized to [-1,1] and the image size is 224x224, the clip length is 64. Is that right?

Yes, that is the correct setting for training. For evaluation, using 256x256 with all the frames is important for improved performance.

Hi @ziqi-zhang , @piergiaj. I am trying to replicate the experiment of finetuning i3d trained on Kinetics, for ucf-101, as per the methods specified in the paper, but getting unsuccessful in achieving any significant accuracy (not even on training data) even after several iterations. Could you please give any guidance?
To simplify, I just used 10 classes from ucf-101,
extracted 64 contiguous frames from each video, from any (feasible) random begin point for each epoch,
randomly spatially cropped 224x224 from video resized to 256 for each epoch,
used Adam optimiser with initial learning rate(1e-4),
and mean subtarction and division by 255 from data.
I have a M2000 GPU.
I am using only RGB pipeline.

@piergiaj regarding your weights file rgb_imagenet.pt - is this i3d trained just on imagenet? or imagenet+kinetics? If it is the former, can you please let me know where can i find the weights for latter? Also, can you also please let me know what is the expected accuracy according to the i3d paper by using single stream i3d with your rgb_imagenet.pt weights only.

@ziqi-zhang could you finetune the model on ucf101 successfully? I want to know how the source of .json file for ucf101. Thank you.


Consider reverting change used to throttle requests to symbol provider API

The PR 1858 was created to work around an upstream issue (https://github.com/Microsoft/vscode/issues/51096#issuecomment-394764890).
However this upstream issue has since been resolved (https://github.com/Microsoft/vscode-python/pull/1858), hence we should consider reverting the PR https://github.com/Microsoft/vscode-python/pull/1858

Part of #2197

This has been resolved with https://github.com/Microsoft/vscode-python/pull/2456


fix(docs): use proper path for tutorial file in docs

running_code_in_the_editor.rst now lives in tutorials/plugins/running_code_in_the_editor.rst instead of tutorials/misc/...

Looks fine, but please leave the translation unchanged, translations are handled on Weblate and the copies here should be treated as read only.

translation file reverted

Thanks!


Script does not handle utf8 in intents

This is with Python 2.7, hard to see where the error occurs when using multithreading. I will try some decoding in load_data
File "assistant_cv.py", line 142, in <module>

  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 250, in map
    return self.map_async(func, iterable, chunksize).get()
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 554, in get
    raise self._value
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: ordinal not in range(128)

@havardthom good catch. Thanks for opening the issue.


docs: add project

Hi @transitive-bullshit,
Have been following this project for a couple of days now. Absolutely awesome following the fast pace journey. Kudos to you for maintaining and running this OSS project. Love it ❤
My docs contribution is an AI-Generated Cover Letter Service. Would love to be featured
https://sharehouse.app/ai
Cheers

Interesting use case && ShareHouse looks great — thanks!


Check for NULL when freeing the QUIC_TLS object

Free functions are expected to be tolerant of a NULL pointer being passed.
Fixes the problem in
https://github.com/openssl/openssl/pull/21668#issuecomment-1782718328

This pull request is ready to merge

Pushed.

Pushed.

To master and 3.2


Not all EOL Packages Being Picked up

What happened:
Hello again!
I have a container and or sbom of a container that has dotnet sdk 3.1 (which is eol) not being picked up by xeol.
ex from sbom
   "name": "dotnet-sdk-3.1",
   "version": "3.1.426-1.el8_7",
   "type": "rpm",
   "foundBy": "rpm-db-cataloger",

I am wondering if there is something not right with the support for rpm packages, the other error I got was
[0000]  WARN unknown package metadata type="DotnetPortableExecutableMetadata" for packageID="861efa353f20821b" form-lib=syft
What you expected to happen:
Should identify dotnet 3.1 as EOL
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Output of xeol version:  0.6.0,
Syft Version:         v0.83.1
OS (e.g: cat /etc/os-release or similar): macos

Hello! Does the SBOM you generate contain a PURL for the package dotnet-sdk-3.1, and if so, could you share the PURL?

Yup!
"purl": "pkg:rpm/rhel/dotnet-sdk-3.1@3.1.426-1.el8_7?arch=x86_64&upstream=dotnet3.1-3.1.426-1.el8_7.src.rpm&distro=rhel-8.7"

Ahh, a very interesting PURL from rpm.... which includes the version in the package name...
I added a PR to endoflife.date here to add the PURLs necessary for a match.

You very well may! EOL data fidelity is probably one of the biggest issues with xeol right now. There's unfortunately no single global source for all different variations of package PURLs.
At a high level: we ingest data from endoflife.date every 24 hours and throw it into a sqlite3 database which is stored in s3 and then downloaded by the CLI. Each endoflife.data product should have PURLs associated with it just like in the PR linked. The meat of the matching logic in xeol for PURLs is located here. Once you clone the repo, you can just run go run main.go <image> to test

Hi,
From google, "3.1.426-1.el8_7" may be provided from OS vendor/community.
If so, support period (EOL) will be defined by this page
https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle

If not so, support period (EOL) will be defined by this page
https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-and-net-core

Fortunatelly, Red Hat provides almost similar support period for dotnat as same as official support period.
But Red Hat sometimes provide long term support period -Full Life Application Streams-.
Then, I felt matching "purl: pkg:rpm/rhel/*" with "endoflife.date" will sometimes lead wrong judgement...

Ah, another edge case! Thanks for providing this information @witchcraze
The RHEL package EOLs is something that can't be supported by the endoflife.date data structure currently. I've been doing some thinking about a more extensible data format over here

The PR above has been merged in, so we should be able close this issue now. Please reopen if it's still not matching correctly.


getting error on npm install in windows

getting this error on npm install, not getting is this issue regarding hiredis or node-gyp

https://github.com/redis/hiredis/releases 0.5.0 —> 0.14.1 ?

@cclauss getting error as  No matching version found for<EMAIL_ADDRESS>

Please see edit above

@cclauss how to npm hiredis

https://github.com/NodeRedis/node-redis/blob/master/README.md#node-redis


Document the Request and Response Formats

We should document the request and response formats that Watchdog send to its consumers.

The formats follow the Watchdog PRD, but they could use copying over and reformatting into a document in this repo.
One change since the PRD was to add notes, error, and response to the callback request body


Google Cloud disk access has been denied, can you give a link to another web disk? Your pre-training model and data are not available for download

Google Cloud disk access has been denied, can you give a link to another web disk? Your pre-training model and data are not available for download

https://drive.google.com/drive/folders/0Bybnpq8dvwudVjBHNWNHUmVSV28?resourcekey=0-PIycD56YyYthmbURb4VKMg&usp=sharing


HLS: export both .ts and .m3u8 files in writeToStream

Version information

fluent-ffmpeg version: 2.1.2
ffmpeg version: 4
OS: --

Code to reproduce
//Input stream is .mp4
ffmpeg(inputStream).addOptions([
    '-profile:v main',
    '-c:a aac',
    '-ar 48000',
    '-b:a 192k',
    '-c:v h264',
    '-crf 20',
    '-g 48',
    '-keyint_min 48',
    '-sc_threshold 0',
    '-b:v 5300k',
    '-maxrate 5300k',
    '-bufsize 7500k',
    '-hls_time 4',
    `-hls_segment_filename %04d.ts`,
    '-hls_playlist_type vod',
    '-f hls'
]).writeToStream(outputStream, { end: true });

(note: if the problem only happens with some inputs, include a link to such an input file)
Expected results
I am looking to get both the hls_segments and the .m3u8 to export to the stream output.
Observed results
Only the .m3u8 gets sent properly to the stream output and the .ts files appear locally. When I try to have two .writeToStreams(), I get an error. Is this possible?
Checklist

[ * ] I have read the FAQ

[ ] I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)

[ ] I have included full stderr/stdout output from ffmpeg

Did you find solution?
I need same thing for converting and uploading .m3u8, .ts and .m3u8 playlist files on firebase storage. I only managed to upload .m3u8 files, can't find solution to upload .ts files, too.

Did you find solution?
I need same thing for converting and uploading .m3u8, .ts and .m3u8 playlist files on firebase storage. I only managed to upload .m3u8 files, can't find solution to upload .ts files, too.

I did not find a solution to upload both to a stream (I'm not sure it's possible here). I ended up downloading everything to a folder and then uploading everything together without a stream, and then deleting the temp files in the folder. I am also working with Firebase storage for my case.

Do you mind if you share your solution?

Did you find solution?
I need same thing for converting and uploading .m3u8, .ts and .m3u8 playlist files on firebase storage. I only managed to upload .m3u8 files, can't find solution to upload .ts files, too.

I did not find a solution to upload both to a stream (I'm not sure it's possible here). I ended up downloading everything to a folder and then uploading everything together without a stream, and then deleting the temp files in the folder. I am also working with Firebase storage for my case.

This solution is great but does not work with AWS Lambda & Large file because lambda only provide about 500MB tmp storage.
Is anyone know about solving this specific case(without tmp storage)?


ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound]

DECLARE
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kkpo_rcinfo_defstg:objnotfound],
[62781], [], [], [], [], [], [], [], [], [], []
ORA-06512: at line 12
ORA-06512: at line 5

Hi @Ketan-33,
It appears you have encountered an Oracle Database internal error.
This repository's focus is on the freely provided Sample Schemas and their associated scripts.
Please file a Service Request with Oracle Support or seek further help on forums.oracle.com
Thanks,


Deserialization improvements

Refactoring/rewriting of the deserialization:

Detection of the subtype is extracted to a separate deserializer with a newly introduced lookahead deserializer
SpecificObjectDeserializer rewritten to avoid buffering and to simplify the code

i dont like the LookaheadDecoder abstraction. I will try to find an alternative.

Ok

@dstepanov take a look. This approach avoids new API on Decoder, and it uses the existing decodeBuffer so in theory the jackson implementation can be based on TokenBuffer for performance at some point.
Also do you think the changes to JsonNodeDecoder still have value now that the new subtypes are gone? If not, we can revert them for easier review

I did a bit of benchmarking of the unwrapped scenario: 10% faster than the previous code.
Vs Jackson:
Benchmark                                                (stack)  Mode  Cnt    Score    Error  Units
JacksonBenchmark.decodeUnwrapped     JACKSON_DATABIND_INTROSPECTION  avgt   10  660.406 ± 11.924  ns/op
JacksonBenchmark.decodeUnwrapped                                         SERDE_JACKSON  avgt   10  554.094 ±  7.019  ns/op

@yawkat Looks fine. I think there are some improvements added to JsonNodeDecoder, you can copy those subclasses back into the decoder if you want.

@yawkat IMHO it would be better if DemuxingObjectDecoder was split into two implementations, one that caches and one that replays / delegates. Now it's hard to understand with all the states there.

Do you mean just moving the nested classes or actually weakening the API?

The best would be to have two implementation, the state can be passed as a map of string -> decoder

Ok let's keep it this way.


Unit tests failing during NixOS build

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
When updating the NixOS package from 0.2.1 to 0.2.4, one of tests fail during execution. Log is below:
test docker::shared::tests::directories::test_docker_in_docker ... ok
test docker::shared::tests::directories::test_host ... FAILED
test tests::toml::toml_check ... ok
test cross_toml::tests::merge ... ok

failures:

---- docker::shared::tests::directories::test_host stdout ----
Error: Permission denied (os error 13)

Location:
    src/docker/shared.rs:965:13
thread 'docker::shared::tests::directories::test_host' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: the test returned a termination value with a non-zero status code (1) which indicates a failure', /build/rustc-1.61.0-src/library/test/src/lib.rs:186:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    docker::shared::tests::directories::test_host

The affected code is:
https://github.com/cross-rs/cross/blob/6cd09b3eb28da7f4e21ee9e3ecee89a3d309c1dc/src/docker/shared.rs#L966-L983
What target(s) are you cross-compiling for?
No response
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[x] docker
[x] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.4
Example
No response
Additional information / notes
No response

can you run it with backtrace? RUST_BACKTRACE=1

What puzzles me is that RUST_BACKTRACE=full "fixes" the issue. Maybe it is due to concurrency?

Ok, got it reproduced. The way I was setting the environment variable was wrong. I got it reproduced using the RUST_BACKTRACE="full" option.
running 42 tests
test cli::tests::is_verbose_test ... ok
test config::tests::test_config::env_and_toml_default_target_then_use_env ... ok
test config::tests::test_config::env_target_and_toml_build_pre_build_then_use_env ... ok
test config::tests::test_config::env_and_toml_build_xargo_then_use_env ... ok
test config::tests::test_config::env_target_and_toml_build_xargo_then_use_toml ... ok
test config::tests::test_config::env_target_and_toml_target_xargo_target_then_use_env ... ok
test config::tests::test_config::no_env_and_no_toml_default_target_then_none ... ok
test config::tests::test_config::no_env_but_toml_default_target_then_use_toml ... ok
test config::tests::test_config::env_target_then_toml_target_then_env_build_then_toml_build ... ok
test config::tests::test_config::toml_build_passthrough ... ok
test config::tests::test_config::toml_target_passthrough ... ok
test config::tests::test_config::toml_build_passthrough_then_use_target_passthrough_both ... ok
test config::tests::test_config::volumes_use_toml_when_no_env ... ok
test config::tests::test_environment::build_and_target_set_returns_tuple ... ok
test config::tests::test_environment::parse_error_in_env ... ok
test config::tests::test_environment::target_build_var_name ... ok
test config::tests::test_environment::collect_passthrough ... ok
test config::tests::test_config::volumes_use_env_over_toml ... ok
test cross_toml::tests::parse_build_toml ... ok
test cross_toml::tests::parse_from_cargo_toml ... ok
test cross_toml::tests::parse_from_empty_cargo_toml ... ok
test cross_toml::tests::parse_mixed_toml ... ok
test cross_toml::tests::pre_build_script ... ok
test cross_toml::tests::parse_empty_toml ... ok
test cross_toml::tests::parse_target_toml ... ok
test docker::custom::tests::docker_tag_name_test ... ok
test docker::shared::tests::mount_finder::test_adjust_multiple_paths ... ok
test docker::shared::tests::mount_finder::test_longest_destination_path_wins ... ok
test docker::shared::tests::parse_docker_inspect::test_parse_container_root ... ok
test docker::shared::tests::mount_finder::test_default_finder_returns_original ... ok
test file::tests::as_posix ... ok
test docker::shared::tests::parse_docker_inspect::test_parse_empty_user_mounts ... ok
test file::tests::pretty_path_linux ... ok
test rustc::tests::hash_from_rustc ... ok
[cross] warning: using older rustc `1.0.0 (11111111 2022-01-01)` for the target. Current active rustc on the host is `rustc 1.2.0 (22222222 2022-02-02)`.
 > Update with `rustup update --force-non-host xxxx`
[cross] warning: using newer rustc `1.2.0 (22222222 2022-02-02)` for the target. Current active rustc on the host is `rustc 1.0.0 (11111111 2022-01-01)`.
 > Update with `rustup update`
[cross] warning: using rustc `1.0.0-nightly (22222222 2022-01-01)` for the target. Current active rustc on the host is `rustc 1.0.0-nightly (11111111 2022-01-01)`.
[cross] warning: using older rustc `1.0.0-nightly (11111111 2022-01-01)` for the target. Current active rustc on the host is `rustc 1.0.0-nightly (22222222 2022-02-02)`.
 > Update with `rustup update --force-non-host xxxx`
[cross] warning: using newer rustc `1.0.0-nightly (22222222 2022-02-02)` for the target. Current active rustc on the host is `rustc 1.0.0-nightly (11111111 2022-01-01)`.
 > Update with `rustup update`
test tests::target_mismatch ... ok
test docker::shared::tests::parse_docker_inspect::test_parse_missing_user_moutns ... ok
test docker::shared::tests::test_docker_userns ... ok
test docker::shared::tests::directories::test_docker_in_docker ... ok
test docker::shared::tests::test_docker_user_id ... ok
test tests::toml::toml_check ... ok
test docker::shared::tests::directories::test_host ... FAILED
test cross_toml::tests::merge ... ok

failures:

---- docker::shared::tests::directories::test_host stdout ----
Error: Permission denied (os error 13)

Location:
    src/docker/shared.rs:965:13
thread 'docker::shared::tests::directories::test_host' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: the test returned a termination value with a non-zero status code (1) which indicates a failure', /build/rustc-1.61.0-src/library/test/src/lib.rs:186:5
stack backtrace:
   0:     0x5555556cf9a1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h8a90a2dc0368e92a
   1:     0x5555555ca61c - core::fmt::write::h22e27476e719d048
   2:     0x5555556d6164 - std::io::Write::write_fmt::h6c6eeafbf5d0a5be
   3:     0x5555556e5e9a - std::panicking::default_hook::{{closure}}::h1efe1958ecadfc56
   4:     0x5555556e5af6 - std::panicking::default_hook::h421ef9590936ba8a
   5:     0x5555556e68e2 - std::panicking::rust_panic_with_hook::h6e5c670a80137632
   6:     0x5555556cfd72 - std::panicking::begin_panic_handler::{{closure}}::ha598c0022793c63e
   7:     0x5555556cfce6 - std::sys_common::backtrace::__rust_end_short_backtrace::h42cbca7399dc1d94
   8:     0x5555556e63d2 - rust_begin_unwind
   9:     0x5555555914a2 - core::panicking::panic_fmt::hae240fade5210bfd
  10:     0x5555555cac4c - core::panicking::assert_failed_inner::h1cd73df0f36cd7f5
  11:     0x555555591fea - core::panicking::assert_failed::h63255eec005ad009
  12:     0x55555563831e - core::ops::function::FnOnce::call_once::hffb2a9b8619e97af
  13:     0x5555555f3dc3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h8b4e642eab91d9c3
  14:     0x55555572118b - test::run_test_in_process::h5369f7a8f58fcca2
  15:     0x55555570eab4 - std::sys_common::backtrace::__rust_begin_short_backtrace::h8cde51eed9198402
  16:     0x555555707aa3 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hb623f7f70a1c1f4a
  17:     0x5555556efb45 - std::sys::unix::thread::Thread::new::thread_start::h902273841a4017f5
  18:     0x7ffff7d57ff2 - start_thread
  19:     0x7ffff7ddabfc - clone3
  20:                0x0 - <unknown>

failures:
    docker::shared::tests::directories::test_host

test result: FAILED. 41 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.17s

error: test failed, to rerun pass '--lib'
error: builder for '/nix/store/508s5vnm96zzyr133pgyfi60y6s6992q-cargo-cross-0.2.4.drv' failed with exit code 101;
       last 10 log lines:
       >   19:     0x7ffff7ddabfc - clone3
       >   20:                0x0 - <unknown>
       >
       >
       > failures:
       >     docker::shared::tests::directories::test_host
       >
       > test result: FAILED. 41 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.17s
       >
       > error: test failed, to rerun pass '--lib'
       For full logs, run 'nix log /nix/store/508s5vnm96zzyr133pgyfi60y6s6992q-cargo-cross-0.2.4.drv'.

can you comment out the lines until you find which check is failing? the backtrace is not helping at all (no line numbers :D )

So NixOS doesn't have access to the temp directory? And not really, but we could probably have it to the target directory. At least not until the path canonicalization is removed (but unfortunately, this can't be done for the CWD with how Rust works with this). This is because std::fs::canonicalize fails if the path doesn't exist on Windows, and we have logic that uses that. If #942 merges, this may not longer manifest however since it won't canonicalize even if cargo does. See the comment here:
fn get_cwd() -> Result<PathBuf> {
    // we need this directory to exist for Windows
    let path = temp::dir()?.join("Documents").join("package");
    fs::create_dir_all(&path)?;
    Ok(path)
}

There's like other parts that will fail if the CWD doesn't exist. We also need temp::dir() support for remote Docker, so this is a broader issue than just "tests failing", since users should have write access normally to their home directory.
I guess the better solution would be to allow users to control where the temp directory via an environment variable? We intentionally don't have it in the target directory, since most of this is supposed to persist cargo clean by design.

Can you provide echo $HOME?

The normal execution is fine. It runs in a invalid home. It returns:
Executing cargoCheckHook
++++ echo /homeless-shelter
/homeless-shelter

Can you provide echo $HOME?

The unittests work on my brother's NixOS install without issue. Mine work as root in a NixOS container (my brother is running as a normal user). I'm guessing the issue is with the data directory and having write access to it.

If your HOME is in fact /homeless-shelter, it's probably due to a like of write access there, in which case this behavior is intentional.

It does but not inside the nix-build environment. See: https://github.com/NixOS/nixpkgs/pull/181490
nix-build uses a sandbox and it aims to avoid writing to host whenever possible.

I think best solution is to just ignore that test for nix

It does but not inside the nix-build environment. See: NixOS/nixpkgs#181490
nix-build uses a sandbox and it aims to avoid writing to host whenever possible.

Ah my brother did mention this, that it is sandboxed during the actual nix-build but not running normally. I think we can just add an #[ignore] flag so it's only run if the ignored tests are run, so we can still test it on NixOS under non nix-build settings.

@otavio Is there an environment variable by any chance to determine if we're in a nix-build context?

@Alexhuszagh the #946 fixes it.

Perfect, can you try again with the new cfg_attr just in case? It should be the same logic, but that way we can run it on other OSes by default.

Didn't work.

Didn't work.

Ok I'll change it back. We can always update the CI to run it with the ignored flag and just keep cargo test to disable it by default.


Toggles state

Before sending out the link to the toggles page, wanted to add some state to let people know what state they're in.

i need to catch up on hooks, but looks good to me

Feel free to use this as a playground.


GH-81: Enable delete branch on merge

fix GH-81
https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Deletebranchonmerge

Add this snippet below so branches get auto-deleted upon PR merge to
your default branch:
Delete Branch on Merge
github:
  del_branch_on_merge: true

+1


Add k8s container logs collection

Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/2536

PTAL @dmitryax

@dmitryax any thoughts on what the implications of these change could be? Contrib is a much larger image, do we care about it?
The original idea for this chart was is to support only core collector functionality by default and provide users with an option to use the contrib collector for other use cases. I suppose that log collection components can be moved to the core collector build later, so I'm good with temporarily switching it to contrib.

@dmitryax any thoughts on what the implications of these change could be? Contrib is a much larger image, do we care about it?

The original idea for this chart was is to support only the core collector functionality by default and provide users with an option to use the contrib collector for other use cases. I suppose that log collection components can be moved to the core collector build later, so I'm good with temporarily switching it to contrib.

According to https://github.com/open-telemetry/opentelemetry-helm-charts/pull/36#discussion_r592389265 the filelog receiver will not be making it to core anytime soon.
I have a slight preference for sticking to the core image by default and just adding a sample values.yaml in the readme as how to achieve the container logging, but don't let that be a blocker!

Folks, I have applied all the code review remarks:

Switched to setting agentCollector.containerLogs.enabled to false by default,
Switched back to using core collector image in the chart,
Added docs on how to enable container log collection,
Added docs on the warning of looping logs from exporter back into receiver,
Changed file exporter in the example to otlphttp exporter, according to code review remarks.

Please take a look.

I have hopefully addressed all the comments. Are we ready to merge @tigrannajaryan?

Thanks @astencel-sumo


Fix bug with changing focus and apply changes from #157 to SplitButton page, Closes #200

Fix a bug where hitting control+b and similar commands will result in navigating the app with focus becoming nearly impossible
Description

Changed the event that was used since the previous event for text colorization would create an endless loop.
I also added the code that was introduced to the RichEditBox in #157 so that the same behavior does not occur in the SplitButton sample.
Motivation and Context

Closes #200
How Has This Been Tested?

Tested manually by starting application, visiting the RichEditBox on the SplitButton page and hitting control+b. After that I was able to successfully navigate to other commands using tab navigation.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Philosophical question for you both (@YuliKl @chingucoding) - this change introduces a bunch of codebehind to the sample, but this code isn't included in the sample code shown on the page. Should it be? Or is this just a bunch of "glue" to help make the sample work as expected?

Philosophical question for you both (@YuliKl @chingucoding) - this change introduces a bunch of codebehind to the sample, but this code isn't included in the sample code shown on the page. Should it be? Or is this just a bunch of "glue" to help make the sample work as expected?

I definitely think of the code as "glue". It has nothing to do with SplitButton per se, just makes the coloring scenario work better.

I agree with @YuliKl, most of the code is just "glue" to deal with the text changing its color.
One thing we might do is create an empty event listener function. In the sample, the SplitButton "uses" the myColorButton_Click function. Maybe we could add that function with a comment inside saying something like "Handling button click".
However I don't really think that it would be that helpful to just have a C# code block with an empty function. What do you think about that @stmoy and @YuliKl ?

However I don't really think that it would be that helpful to just have a C# code block with an empty function. What do you think about that @stmoy and @YuliKl ?

Agreed, I don't think it's super useful. I also agree with the overall direction as Yulia described. Net result: no changes needed.


Not receiving notifications

Now, this is far from the first reported case of this, and it's apparent that a lot of people are having issues with notifications. This is probably the second or third time I install this app, and it works okay, but I'm not receiving any notifications, making me have to check the app periodically to see if people have written anything.
This isn't something that I'm interested in continuing doing on a daily basis, so it would be nice if someone around here knows what's up.

Windows 10 Pro 1803
Microsoft Surface Laptop
No restrictive policies or settings in place

Thanks in advance

I need to know my code

@LordManhattan Did you ever get it fixed?


Update panels.md

See https://github.com/AdobeDocs/analytics.en/issues/125

@bryantabaird - I have made this change in the corporate repo and it should be published by EOD tomorrow. Thanks!


MSSQL vs BQ - Column validation - Custom Query with max, count fails

Column validation with custom query is not working for count, max etc
Command Used :
data-validation validate custom-query
--custom-query-type column
--source-query-file ss_cust_max_src.sql
--target-query-file ss_cust_max_tgt.sql
-sc MSSQL_CONN
-tc BQ_CONN
--bq-result-handler paras-sandbox-364713.data_validator.results
--max order_amount
data-validation validate custom-query
--custom-query-type column
--source-query-file ss_cust_max_src.sql
--target-query-file ss_cust_max_tgt.sql
-sc MSSQL_CONN
-tc BQ_CONN
--bq-result-handler paras-sandbox-364713.data_validator.results
--count custid
Source query (ss_cust_max_src.sql) : select custid,order_amount from tempdb.dbo.customer;
Target query (ss_cust_max_tgt.sql) : select custid,order_amount from paras-sandbox-364713.dlp.customer;
Error :
KeyError: <class 'decimal.Decimal'>

@madhu-jain I am facing similar issue. Have you found any solution?
The columns are originally stored in numeric/money in SQL server. I am trying to cast them in numeric(38,10) and then compare with BQ but end up with the same error. Table without numeric/money column works fine.

I feel the problem might be because of the mapping mentioned in _get_schema_using_query in /lib/python3.8/site-packages/third_party/ibis/ibis_mssql/client.py, there is no reference provide in type_map for decimal.Decimale and also, I was unable to find any reference for timestamp although it is already mentioned. Any idea how can I added reference to it?
@nehanene15 @sharangagarwal If you guys can take a look

@madhu-jain Add import decimal to import decimal lib and decimal.Decimal: 'Decimal',  in type_map in _get_schema_using_query funtion. it will work.

Closed with #771


first stab at isolating network tests (#263)

Updating CircleCI config files to run all tests, but not require network tests for building/publishing tagged releases. Bumping version middle-most.
@mlissner you will want to pull this code down to your machine and execute python -m unittest discover -s tests/network -v to make sure that all network tests work with your PACER config.  Go ahead and run tox and/or python setup.py test while you are at it.
When this branch is merged in, you will want to tag 1.24.00
(see #263)

@mlissner I guess we will see if Circle passes with these changes.
Regardless, I am out of pocket from now until Monday evening.

@mlissner, tests passed, but it skipped all the PACER tests that require credentials.  It does this on my machine, as I have no credentials set up, but should Circle have PACER_USERNAME and PACER_PASSWORD configured?  Has CI historically executed those tests?

Thanks @arderyp. Some of this (like the circleci configs) is a bit over my head, but it all seems to work nicely both in CircleCI and on my local machine, so I think we're in business.
I don't love the class-based file names. I might change that eventually to more normal names, but the allure of getting this landed was worth pulling it anyway. CircleCI is running now. Hopefully it'll work!

hmm @mlissner , I had a little more work to do lol, oh well.  Class names can change but must retain "test_" prefix

I figured not much risk I'd break the already broken. Let me know if you want help, otherwise, I'm just hoping to get a version released tomorrow, but I can still do that manually if need be.

let me poke around a little more tonight.  You can cut the release either way tomorrow.  Nothing is broken, we are just not executing PACER tests in Circle because, for some reason, the env variables aren't working... I still need to figure out why.

I think we are actually running them though. If you look at the latest workflows, they failed due to the network tests.

I think there is lots of confusion here, and its not helping that we are commenting both here and on #263.  Since this PR is closed, lets please stop commenting here.  Take it back over to #263


Feature: Collapsible Headings

It would be great to have collapsible headings (could be disabled by default), see for example the features showcased on https://bangle.dev/docs/examples/collapsible

https://github.com/facebook/lexical/issues/1841 and recently merged https://github.com/facebook/lexical/pull/2592 may be related.

Since it's already listed I'll close
This as a duplicate to keep single issue open for discussions (#1841)

@fantactuka https://github.com/facebook/lexical/issues/1841 is just a toogle and any place of the document. This issue is about collabopsible heading (h1, h2,...).
It is not the same thing.
Could we reopen this?

@fantactuka This is still closed. I think a collapsible heading can build on a collapsible node, but the feature is different. The goal of this issue to to automatically show the heading in collapse mode (or not if disabled). Any question you have to reopen this?


local-pv-provisioner ignore terminating PV

Please check the FAQ documentation before raising an issue

Describe the bug (required)
8026 I0404 12:24:12.213677       1 provisioner.go:356] volume pvc-eb0032a7-0349-47fb-a124-69210a1e8632 has been create on gke-snap-test-pool1-9a9e79fa-w2jb:/mnt/disks/raid0
8154 I0404 12:30:49.813325       1 provisioner.go:167] deleting volume pvc-eb0032a7-0349-47fb-a124-69210a1e8632 at gke-snap-test-pool1-9a9e79fa-w2jb:/mnt/disks/raid0
8279 I0404 12:33:54.018283       1 provisioner.go:356] volume pvc-03a69ec5-daa2-4580-972b-44faaf1143c6 has been create on gke-snap-test-pool1-9a9e79fa-w2jb:/mnt/disks/raid0
9007 I0404 14:05:49.880697       1 provisioner.go:356] volume pvc-43f6339a-90ef-4b63-8cff-8d99f97043bf has been create on gke-snap-test-pool1-9a9e79fa-w2jb:/mnt/disks/raid0

Your Environments (required)

OS: uname -a
Commit id (e.g. a3ffc7d8)

How To Reproduce(required)

delete PV manually
delete related PVC manually

Steps to reproduce the behavior:

Step 1
Step 2
Step 3

Expected behavior

Additional context

https://github.com/vesoft-inc/nebula-operator/issues/494


APOLLO "contamination" doesn't pertain to plant or animal organisms?

The definition and axioms for contamination process (aka biological contamination) forbid it occurring  a material entity that is not an organism.
"The process of existence without reproduction of a pathogen of a particular biological taxon in or on some material entity or the process of reproduction of a pathogen in or on a material entity that is not an organism."
Why limit biological contamination to non-organisms?  Contaminated food is what we of course are primarily interested, and that can include e-coli contaminated fenugreek seeds / plants etc.  Perhaps there is another word for this behaviour?
Also, what should we call the process after a food item has completed this contamination process, is contaminated, and pathogen reproduction occurs to bring the contaminant up to enough of an amount to potentially cause harm?  Food biological spoilage?
We're looking at creating a hierarchy of contamination and decontamination processes and artifacts in FoodOn or wherever people recommend.  Our hierarchy is (tentatively) at bottom of https://github.com/FoodOntology/foodon/issues/201

Happy to discuss and rework the definitions to accommodate. I don't think we intended to exclude food contamination.  Note that we did attempt to cover situations where organisms can be contaminated: "The process of existence without reproduction of a pathogen of a particular biological taxon in or on some material entity" which of course includes organism.  THe latter half of the definition is the only part of the definition that applies to non-organisms.


How to create subfolder?

Dim folder As TaskFolder
folder.createfolder("name")
gives me this error
'CreateFolder' is ambiguous because multiple kinds of members with this name exist in class 'Microsoft.Win32.TaskScheduler.TaskFolder'
edit: 1.6.2 and 1.5 gives this error, 1.4.2 no error
Originally posted: 2011-07-16T06:43:04

You've found a bug. I will fix this in 1.6.3. For now, to remove this error, you can just pass in the VB equivalent of (string)null as a second parameter.
Originally posted: 2011-07-16T22:13:46


[Bug]: AuthenticationError, RetryEror

Bug Description
index = GPTVectorStoreIndex.from_documents(
    document,
    storage_context=storage_context,
    service_context=service_context
)

or

index = GPTVectorStoreIndex.from_documents(
    [],
    storage_context=storage_context,
    service_context=service_context
)

query_engine = index.as_query_engine()
resposnse = query_engine.query()

Error:
AuthenticationError                       Traceback (most recent call last)

AuthenticationError: No API key provided. You can set your API key in code using 'openai.api_key = <API-KEY>', or you can set the environment variable OPENAI_API_KEY=<API-KEY>). If your API key is stored in a file, you can point the openai module at it with 'openai.api_key_path = <PATH>'. You can generate API keys in the OpenAI web interface. See https://platform.openai.com/account/api-keys for details, or email<EMAIL_ADDRESS>if you have any questions.

RetryError: RetryError[<Future at 0x7f6bdeb32b30 state=finished raised AuthenticationError>

Version
0.6.25, 0.6.25post1, 0.6.26 and 0.6.27
Steps to Reproduce
while indexing the document
Relevant Logs/Tracbacks
No response

Maybe duplicated of https://github.com/jerryjliu/llama_index/issues/6458

Not sure what the cause is yet. Will investigate. But closing as duplicate of https://github.com/jerryjliu/llama_index/issues/6458


problems with nginx-spdy-1.11.5+.patch when it is applied to nginx version 1.11.11

There is a problem with theis patch when it is applied to nginx version 1.11.11
[root@server nginx-1.11.11]# patch -p1 < ./nginx-spdy-1.11.5+.patch patching file auto/modules
Hunk #1 FAILED at 139.
Hunk #2 FAILED at 171.
Hunk #3 FAILED at 232.
Hunk #4 FAILED at 440.
4 out of 4 hunks FAILED -- saving rejects to file auto/modules.rej
patching file auto/options

Added new versions in #63

Can you please this one?
https://raw.githubusercontent.com/cujanovic/nginx-http2-spdy-patch/master/nginx-spdy-1.11.11%2B.patch

Excellent
The problem has been resolved
thank you very much

@cujanovic  I tried the patch with Nginx 1.12.0 .but it seems like the spdy is not working.


Add a hlint target to cabal file

Based on discussion at recent Haskell hacknight, making hlint a project dependency is not really the standard approach.  This issue will be closed.  Use stack to install hlint outside of any project to get it on the command line.


Add information about absence of "msg.sender"

@jonjove is this required prior to Meridian?

Not strictly required but probably helpful.

I see I just want to verify since I don't think the sprints have any space for extra work outside completed the critical issues required to run the demo at Meridian. If this is not critical to that I don't think we should focus our time on this.

Superseded by https://github.com/stellar/soroban-docs/issues/129


Adding support for view interactions as well as input, file, and mult…

Adding support for view interactions as well as input, file, and multi select block elements

@tsein-stripe I wonder why have you removed omitempty struct tag value from structs like publishViewRequest. Without this, views.publish requests fail with an empty hash (which is valid accordingly Slack API specs)?

@tsein-stripe I wonder why have you removed omitempty struct tag value from structs like publishViewRequest. Without this, views.publish requests fail with an empty hash (which is valid accordingly Slack API specs)?

Thanks! I fixed that with my last commit.

OK I've managed to test this internally and it's looking good! The removal of SingularBlockElement required some code changes, but that's understandable. We don't use all of these new elements, but the ones we do worked correctly, so LGTM.

@kanata2 Do you have any concerns or PR feedback, or can this be merged and PR's into slack-go/slack?

@kanata2 Is this ready to be merged in and PR'd to the upstream slack-go repo?

@tsein-stripe
What do you do with this? future tasks?
https://github.com/kanata2/slack/pull/1#discussion_r383692634

@kanata2 What do you think about the last change I submitted? Certainly all blocks will at the very least have a type/ID. I also included rich text as a block which will get mapped to the placeholder "UnknownBlock" type.
Again, I prefer having the UnknownBlock placeholder here so that it's fully transparent to the user that something came through from a Slack API response which this framework doesn't yet have an impl for -- rather than skipping and omitting the element (which could be confusing)

Looks good in terms of finding unsupported blocks without parsing failure.
You'll receive an error when you send json included marshalled UnknownBlock (e.g. {"type": "rich_text", "block_id": "hoge"}), so we need to handle this problem in next PR.

Thanks @kanata2 ! @dcelasun do you guys need anything else from me, or can you railroad these changes into the upstream repo? There should be no merge conflicts.

I figured out how to get this PR against the upstream repo -- I didn't know you could do that 🤦♂
https://github.com/slack-go/slack/pull/669

close this PR. New one is here!


Wrap table names

Addresses Issue #55
Also sneaks in PyCharm to .gitignore

Found a few additional spots not referenced in issue #55 and updated

Thanks @jzmiller1 !
I think that the _drop_trigger function might also need quotes, but I'm going to fix this in a follow up PR and add a test case around a table named "Order". I will also add you as a contributor in the README in this PR


[GMOD] GLIBC fix & updateonstart broken

Can't run ist because i get an Error while update check
ttt@mightful-noobs:~$ ./gmodserver start
[ .... ] Update gmod-server: Checking for update: SteamCMD/home/ttt/steamcmd/linux32/steamcmd: relocation error: /lib/i386-linux-gnu/librt.so.1: symbol __clock_nanosleep, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
[ FAIL ] Update gmod-server: Checking for update: SteamCMD: Not returning version info
[  OK  ] Update gmod-server: Checking for update: SteamCMD: Update available

Update available:
        Current build: 1214509
        Available build:

        https://steamdb.info/app/4020/

Applying update...
[  OK  ] Update gmod-server: SteamCMD
ERROR: ld.so: object '/usr/lib/coreutils/libstdbuf.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
/home/ttt/steamcmd/linux32/steamcmd: relocation error: /lib/i386-linux-gnu/librt.so.1: symbol __clock_nanosleep, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
[  OK  ] Alert gmod-server: Sending alert<EMAIL_ADDRESS>ttt@mightful-noobs:~$

I excluded my mailadress, but it is showen.
Maillog:
gmod-server received update

Distro Details
=================================
Distro: Ubuntu 14.04.5 LTS
Arch: x86_64
Kernel: 3.13.0-93-generic
Hostname: mightful-noobs.de
tmux: tmux 1.8
GLIBC: 2.19

Performance
=================================
Uptime: 0d, 1h, 34m
Avg Load: 0,00, 0,01, 0,05

Mem: total used free
Physical: 31G 9,7G 21G
Swap: 7,6G 0B 7,6G

Storage
=================================
Filesystem: /dev/sda4
Total: 221G
Used: 9,6G
Available: 201G
Serverfiles: 3,6G

Garry's Mod Server Details
=================================
Server name: [EU] Mightful Noobs | TTT | Whitelisted
Server IP: <IP_ADDRESS>:1337
Server password: ********
RCON password: ********
Game mode: terrortown
Tick rate: 66
Status: OFFLINE

gmod-server Logs
=================================

Script log
===================
/home/ttt/log/script/gmod-server-script.log
Aug 13 14:50:00 gmod-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2
Aug 13 14:56:45 gmod-server: UPDATE: INFO: Checking for update: Server logs
Aug 13 14:56:47 gmod-server: UPDATE: INFO: Checking for update: SteamCMD
Aug 13 14:56:50 gmod-server: UPDATE: FATAL: Checking for update: SteamCMD: Not returning version info
Aug 13 14:56:50 gmod-server: UPDATE: PASS: Checking for update: SteamCMD: Update available
Aug 13 14:56:55 gmod-server: UPDATE: INFO: Update available
Aug 13 14:56:55 gmod-server: UPDATE: INFO: Current build: 1214509
Aug 13 14:56:55 gmod-server: UPDATE: INFO: Available build:
Aug 13 14:56:55 gmod-server: UPDATE: INFO: 1214509 >
Aug 13 14:56:57 gmod-server: UPDATE: INFO: Starting SteamCMD
Aug 13 14:56:57 gmod-server: ALERT: INFO: Sending update alert
Aug 13 14:56:57 gmod-server: ALERT: INFO: Sending alert: *******
Aug 13 14:56:57 gmod-server: ALERT: PASS: Sending alert: ***********
Aug 13 14:56:57 gmod-server: UPDATE: PASS: command_update.sh exiting with code: 0
Aug 13 14:59:03 gmod-server: UPDATE: INFO: Checking for update: Server logs
Aug 13 14:59:05 gmod-server: UPDATE: INFO: Checking for update: SteamCMD
Aug 13 14:59:08 gmod-server: UPDATE: FATAL: Checking for update: SteamCMD: Not returning version info
Aug 13 14:59:08 gmod-server: UPDATE: PASS: Checking for update: SteamCMD: Update available
Aug 13 14:59:13 gmod-server: UPDATE: INFO: Update available
Aug 13 14:59:13 gmod-server: UPDATE: INFO: Current build: 1214509
Aug 13 14:59:13 gmod-server: UPDATE: INFO: Available build:
Aug 13 14:59:13 gmod-server: UPDATE: INFO: 1214509 >
Aug 13 14:59:14 gmod-server: UPDATE: INFO: Starting SteamCMD
Aug 13 14:59:15 gmod-server: ALERT: INFO: Sending update alert
Aug 13 14:59:15 gmod-server: ALERT: INFO: Sending alert: ***********

Console log
====================
/home/ttt/log/console/gmod-server-console.log (LOG FILE IS EMPTY)

Server log
===================
/home/ttt/serverfiles/garrysmod/logs (NO LOG FILES)

ping steamdb.info ?

PING steamdb.info (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=59 time=7.50 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=59 time=4.55 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=59 time=4.49 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=59 time=4.44 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=59 time=4.43 ms
64 bytes from <IP_ADDRESS>: icmp_seq=6 ttl=59 time=4.47 ms
64 bytes from <IP_ADDRESS>: icmp_seq=7 ttl=59 time=4.43 ms

I'll try a fresh install too. It's already installing, i'll see if i can reproduce on my Debian.

also tried to disable firewall, and turn off autoupdate, don't check anymore, and didn't start either
I'm using Ubuntu 14.04 64-Bit

OK, updateonstart is broken, at least if the server didn't start yet.
Disable updateonstart until it's fixed.
http://pastebin.com/c65WTPTW

Also, there are segfaults on a fresh install.
I suspect the glibc fix to be broken.
Auto detecting CPU
Using default binary: ./srcds_linux
Server will auto-restart if there is a crash.
./srcds_run: line 372: 13691 Segmentation fault      $HL_CMD
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Sat 13 Aug 15:22:35 CEST 2016: Server restart in 10 seconds
quit

OK, i disabled glibc fix for now until we fixed the fix (lol). https://github.com/dgibbs64/linuxgsm/commit/9e3148cb2b21ca528bf8090dd8c48a93066273c3#diff-261fcf3867f75d127d9098d6a56a7eb2
It seems to have fixed the updateonstart too.
You should now be able to install and start your server properly

run this to update your functions
./gmodserver uf
Start over
rm -R lgsm/lib
(if your server is empty) : rm -R serverfiles
./gmodserver install

Fixed

Works now, reloaded it complete, installed fresh, all fine now including the autoupdate.
Thanks

Allright :)


Simulation handles closing of netcdfoutputwriter

This pull request eliminates the need to have close(ncoutputwriter) at the end of the scripts. The closing is handled by the run! method of the Simulation type.
Resolves #650
Also fixes #651

Looks like GitLab CI just timed out, which is weird as builds have gotten faster but I restarted it.
Thinking I'll tag a patch release v0.24.2 once this PR has been merged as it improves existing scripts, if you're okay with this.
Also I edited your original post from "Addresses #650" to "Resolves #650". It has to be one of the accepted words for issues to be automatically closed: https://github.com/gitbucket/gitbucket/wiki/How-to-Close-Reference-issues-and-pull-request#closing-issues

@suyashbire1 Looks like NetCDF GPU tests are failing. Check out the GitLab CI build log: https://gitlab.com/JuliaGPU/Oceananigans-jl/-/jobs/454517749
Seems like we're getting a NetCDF error: Permission denied (NetCDF error code: 13) in write_grid_and_attributes. Not sure if has something to do with clobber vs. append but maybe giving different filenames for CPU and GPU will help? I.e. nc_filename = "dump_test_$(typeof(arch)).nc".


move ZwoEFW support to separate library

library created and published

https://github.com/AndreEbel/python-zwoasi/commit/c20214a917fdba024a2035f630b909fd8e52e7ae


prewrite_improve: abort Prewrite command after Rollback for the same txn

Hi,all,
This PR is for issue_1649. @disksing @zhangjinpeng1987  PTAL

PTAL @hhkbp2

Please update the PR's title with more details.

should add test in tests with raft engine.

Is it compatibility for the rolling update?

For this case In the rolling update, tikv should be updated before tidb. @siddontang

LGTM

@zhangjinpeng1987 @siddontang PTAL

Rest LGTM

PTAL @zhangjinpeng1987

LGTM @disksing PTAL again.

LGTM.


False positive when returning child classes instances

Hello. Thank you for the project.
There is a problem when you try to return an object of a child class.
Let us say I have the following project structure.
MyPackage/__init__.py - empty file
MyPackage/Dev.py:
class Developer:
    def __init__(self):
        pass

MyPackage/PyDev.py:
from .Dev import Developer

class PythonDeveloper(Developer):
    def __init__(self):
        super().__init__()
        pass

main.py:
from MyPackage.Dev import Developer
from MyPackage.PyDev import PythonDeveloper
import type_enforced

@type_enforced.Enforcer
def my_func(way) -> Developer:  # meant that Developer instance or any Developer's child class instance is returned
    if way == 1:
        return Developer()
    elif way == 2:
        return PythonDeveloper()

print(my_func(1))  # <- all ok
print(my_func(2))  # <- Unexpectedly get exception
pass

The exception message is:
TypeError: (my_func): Type mismatch for typed variable `return`. Expected one of the following `[<class 'MyPackage.Dev.Developer'>]` but got `<class 'MyPackage.PyDev.PythonDeveloper'>` instead.

Why it is expecting only the base class instance? Can this be fixed?

This is an interesting thought. Let me see what I can dig up here.

I was able to get a fix working by checking the instance MRO items instead of the type itself.  Another option is to take the passed type and work up the subclasses instead.
With that said, tests indicate that this will double type enforcement validation times. This will require some extra thought on my end.
As a fix for you now, you can add a simple helper method to work up the subclasses iteratively.
import type_enforced

def get_subclasses(obj):
    out = [obj]
    for i in obj.__subclasses__():
        out += get_subclasses(i)
    return out

class Developer:
    def __init__(self):
        pass

class PythonDeveloper(Developer):
    def __init__(self):
        super().__init__()
        pass

class SuperPythonDeveloper(PythonDeveloper):
    def __init__(self):
        super().__init__()
        pass

@type_enforced.Enforcer
def my_func(way) -> get_subclasses(Developer):  # meant that Developer instance or any Developer's child class instance is returned
    if way == 1:
        return Developer()
    elif way == 2:
        return PythonDeveloper()

print(my_func(1))  # <- all ok
print(my_func(2))  # <- No exception any more

Thanks,  I will use this workaround for now.

After more thought, it seems less likely that type_enforced should automatically check subclasses.
A good example is bool types, which are also int types. In this case if you say a variable has to be a bool, but you actually pass an an int like 5, it wouldn't raise an error but it really should.
I am thinking that I might add an importable helper function to do the same workaround I posted above so users can call it explicitly in cases that make sense to them.

So this would not be possible to just use the normal -> Developer instead of -> get_subclasses(Developer)?
Maybe you just make another decorator, or a parameter to your existing decorator, so that it behaves as expected in both cases? Like @type_enforced.Enforcer(subclasses=True)?

I am going to go ahead and close this out with: https://github.com/connor-makowski/type_enforced/pull/28
See the docs here: https://github.com/connor-makowski/type_enforced/blob/1141e6523b3fe34f5be900c543d8cd3815827479/README.md#validate-classes-with-inheritance

It is unfortunate that you have to edit the code of the functions along with decorator. But thanks for providing this function anyway.

I agree. To be honest, this might change in the next major version, but for backwards compatibility, I couldn't just modify the standard function. I do like the decorator modification, but then I would need to curry the decorator, which is possible and I have written the the code to do it, but it is additional overhead.


runAction (non streamed) + typing typing typing

This PR cleans up a and strictens a lot of types. It also introduce a non streamed runAction that should be preferred for Doc Tracker and Events over runApp (it's an observable wrapper on top of it) cc @fontanierh @PopDaph

@fontanierh unknown FTW
cc @philipperolet @Uzay-G for impact on chat and gens


CallAgentMethod?

I feel like calling agent's method quickly in a tree is really missing for convenience.
For now, we could make custom task that just calls agent's needed method (which needs creating new files), use CallMethod (for which we need to specify a node, which is redundant if it's always the agent), maybe make set/get property and use SetAgentProperty?
Everything needs extra steps, CallAgentMethod could simplify it and just call method directly on agent (behavior like CallMethod, minus node property, always the agent)
No? Maybe I'm missing some existing functionality that already works quick like that? 👀

I think just defaulting CallMethod to agent would suffice without adding additional tasks to the core.

@limbonaut hmm, ok, I actually just now noticed something. Here is the explanation.
There is one workflow which I use myself (and I bet some other people too) and looks like it won't work.
If I design/create new enemy type (adding needed rays, areas, colliders, etc.), I usually don't save them as new scenes instantly. Instead, I just work in current level scene. Because it's much quicker to iterate and adjust things, rather than jumping between 2 scenes (and because for now you can't easily resave/apply changes to instantiated scenes in Godot). So imagine, I added new behavior for this new enemy and now I want a few more of the same enemies to test. So I quickly duplicate this node and just move them around in this level scene (later I can delete these extra nodes quickly too and continue to work on the first one)
Now all the tasks that use node paths like CallMethod and all Animations states, won't work correctly.
Obviously the paths won't be updated on duplication and they all will be pointing to that first original enemy node.
While SetAgentProperty and CheckAgentProperty will still work because they are bounded to agent.
So this workflow is not possible, right? Is there a way to set paths in those tasks relative to agent node and not started from root node?
Also if you think CallAgentMethod would be redundant, then why there are CheckAgentProperty/SetAgentProperty, why not just make CheckProperty/SetProperty instead, which again can be linked to any node and agent itself, and which will broaden their use cases?
I think it's either they are grouped around Agent and Scene (and have doubles, like CallMethod and CallAgentMethod, which maybe is not great, I agree), or they all global scene-based where you can call methods/check properties of other nodes or agent. And also if you want you could specify in the task properties that path is relative to agent somehow (maybe checkbox "Relative to agent?") and then described workflow could work? 🤔

Is there a way to set paths in those tasks relative to agent node and not started from root node?

I didn't find a way to instruct inspector editor for NodePaths to edit the said path relative to anything else but scene root. Not to mention, that NodePath editor is not even accessible in GDExtension. So whichever scene is currently edited, its root is used by NodePath editor, even if that scene is unrelated to BT :shrug: . Thus, we're stuck with scene root.

So this workflow is not possible, right?

Depends. You can use BlackboardPlan workflow to set paths relative to BTPlayer/BTState. Define a NodePath variable in the BT's blackboard plan, and assign its value in BTPlayer. That way, the path itself will be relative to BTPlayer. This is the recommended way of accessing scene objects. Relying on NodePath  in a BT, you create a coupling of that BT with a scene, which can become a problem, as you can see.

Also if you think CallAgentMethod would be redundant, then why there are CheckAgentProperty/SetAgentProperty, why not just make CheckProperty/SetProperty instead, which again can be linked to any node and agent itself, and which will broaden their use cases?

Because it's a relict of the past. I haven't got time for that just yet. Ideally, there should be only one SetProperty/CheckProperty task pair (to be implemented).  SetAgentProperty is going to be deprecated eventually. Especially, when variable to property binding gets fully done.

... and have doubles, like CallMethod and CallAgentMethod ...

Following this logic, I would also have to add CallVarMethod for objects on the Blackboard. In the end of the day, we are talking about a parameter to CallMethod. Doubling and trippling each task that needs access to something related to objects will add bloat to the plugin, and increase cognitive load while browsing the task palette, and will add maintenance for me in the long run. Parametrizing CallMethod in such a way, that object could be specified regardless of the source, seems to me a better idea. Especially, if it can be repeated for other similar tasks. That's the whole point of BBParam classes, they just need a way to handle agent better.

This would be a welcome addition IMO:


Multirun doesn't select the function for simulating the project

Reproducible example
In the multirun add strings

AAA (Should fail)
AAAA (Should pass)

Building the same machine in JFLAP gives those results but multirun says they both pass.
Also weird, AAAA doesn't pass in normal run since it jumps to the final node too fast (this is a separate issue it seems)
More investigation finds that this line is the problem
https://github.com/automatarium/automatarium/blob/56feb729b3b8a33f6d48101cc0480f8849322dc9/frontend/src/components/Sidepanel/Panels/TestingLab/TestingLab.js#L355
Since it means it always simulates multirun as an FSA (hence it ignores the stack requirement).
This logic error seems to appear in a few places. We should probably make a function simulateGraph that properly chooses how to simulate the project instead of all the if's that are currently being used

I wouldn't say it straight up doesn't work, I think more investigation is required into the specific issue but atm it seems like the testing lab trace does it correctly, and multi-run seems to ignore an empty stack (an entirely wrong string will still be rejected)

Yeah wrote the issue late and didn't investigate properly.
But think I've found the root issue, seems like easy enough to fix (fix will come soon, we're still getting all the initial documents finished before we start sprinting)


Suricata 7.0.3

Testing v0.2.1 of suricata_exporter against Suricata 7.0.3 produces this error:
panic: interface conversion: interface {} is nil, not map[string]interface {}
[](url)
goroutine 21 [running]:
main.handleWorkerThread(0x7f1620?, {0xc000147dc0, 0xa}, 0x7?)
	/home/runner/work/suricata_exporter/suricata_exporter/main.go:554 +0x10c5
main.produceMetrics(0xc00011e0c0?, 0xc0001322a0?)
	/home/runner/work/suricata_exporter/suricata_exporter/main.go:744 +0x278
main.(*suricataCollector).Collect(0xc00011d900, 0xc000094760?)
	/home/runner/work/suricata_exporter/suricata_exporter/main.go:791 +0x14f
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
	/home/runner/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/registry.go:448 +0x11a
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather
	/home/runner/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/registry.go:457 +0x4c5

Attached the dump-counters.json

Hello @vpiserchia - Does this happen for you also with non-bond interfaces, too?
I'm looking at dump-counters.json output you provided (thanks!) and it looks like the threads["W#01-bond"] has a single "30" key that then nests the actual thread data:
{
  "W#01-bond1": {
    "30": {
      "capture": {
        "kernel_packets": 247478455,
        "kernel_drops": 186199,
       ...
      },
      "tcp": {
        "syn": 916622,
        "synack": 803543,

Honestly, to me this looks like a bug with the Suricata stats. It's not even clear what the meaning of the "30" is and they shouldn't be changing their stats format in a patch release anyhow.
@jlucovsky @victorjulien could you take a peek what happened in 7.0.3 with the stats code that such a format is produced?

@awelzel thanks for you quick response.
Indeed this is linked to the use of bond interfaces. Without bond the Json structure changes completely to this one:
    "threads": {
      "W#01-bond1": {
        "capture": {
          "kernel_packets": 27888,
          "kernel_drops": 0,
          "errors": 0,
          "afpacket": {
            "busy_loop_avg": 0,
            "polls": 2554,
            "poll_signal": 0,
            "poll_timeout": 203,
            "poll_data": 2351,
            "poll_errors": 0,
            "send_errors": 0
          }
        },

and the suricata_exporter works correctly:
suricata_app_layer_flows_total{app="bittorrent-dht",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="dcerpc_tcp",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="dcerpc_udp",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="dhcp",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="dns_tcp",thread="W#01-bond1"} 2
suricata_app_layer_flows_total{app="dns_udp",thread="W#01-bond1"} 347
suricata_app_layer_flows_total{app="enip_tcp",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="enip_udp",thread="W#01-bond1"} 0
suricata_app_layer_flows_total{app="failed_tcp",thread="W#01-bond1"} 20
suricata_app_layer_flows_total{app="failed_udp",thread="W#01-bond1"} 15
suricata_app_layer_flows_total{app="ftp",thread="W#01-bond1"} 0

It is the bond interface name:

Ah. Thanks for checking. Suspect this is also an issue with prior Suricata versions? Or has that only started with 7.0.3? Do you know?
Anyhow, please report this to the Suricata team. suricata_exporter crashing is unfortunate, but it's just a signal that the stats produced by Suricata are a bit broken.

https://redmine.openinfosecfoundation.org/issues/6732

FYI there is no 7.0.3 yet.

@victorjulien of course you're totally right. I messed up here. it is the 7.0.2. Going to edit both the issues.

@vpiserchia - I'm closing this. Upcoming Suricata 7.0.4 should have this fixed. Thanks for the report.


Need to upgrade aiohttp dependency to 3.9.4

Use this query to search for the most popular feature requests.
Is your feature request related to a problem? Please describe.
To fix the vulnerability, we need to upgrade aiohttp to 3.9.4. However, botbuilder-integration-aiohttp 4.14.8 depends on aiohttp==3.8.5.
Describe the solution you'd like
Upgrade aiohttp to 3.9.4.

This happened via dependabot and have been merged with main.  Will be in the next release.


LU Decomposition

By extension, maybe assert that L, U and A are the same shape and that L and U have been initialised per expectation (zeros).

The pdfs are very handy

I guess the question I never asked: my not internalise the creation of L and U and then return them from the function as a pair of outputs?

i.e.
L = np.zeros_like(A, dtype=np.float64)
U = np.zeros_like(A, dtype=np.float64)
...
return L, U

Yea, will add in the shape assertions, nice one!

For the memory allocation, it's done mainly for performance (this is 1us vs scipy 20us for a small matrix), and calling it in a loop will actually materialise that gain. The main use case for this in fastats is probably going to be iterating over a high-dimensional matrix and using L, U to solve the equations. Only allocating the arrays once saves ~10-20% of runtime.
Having said that, I do agree with you though, perhaps we should add a wrapper function to give the option:
def lu(A):
    L, U = np.zeros_like(A), np.zeros_like(A)
    lu_inplace(A, L, U)
    return L, U

@rjenc29 - the latest commit adds the API you asked for - L, U = lu(A), which just wraps the old function (which has been renamed to lu_inplace).

That's just the ticket, nice one


Emoji Picker - Moving by arrow keys will eventually lose focus when reaching last row of emojis

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

Expected result
Focus isn't lost even after reaching the last emoji on the list.
Actual result
After reaching the last emoji on the list, the focus is not visible anymore.
Action Performed

Log in to expensify.cash
Navigate to a conversation
Click on the emoji icon
Use the arrow keys to reach the bottom of the list

Platform
Web ✔
Build: 1.0.36-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Images/Video
https://user-images.githubusercontent.com/44479856/116945606-15e5c500-ac46-11eb-9e65-ce28fcc1e469.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Reported while executing PR https://github.com/Expensify/Expensify.cash/pull/2532#issuecomment-831599293

Not sure why this was not labeled as external, doing that now.

Triggered auto assignment to @kevinksullivan (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

I think this issue needs to be retested as I made some changes recently to scroll Listener which could have affected it.

ok, @isagoico can you retest please to make sure it's still reproducible?

@kevinksullivan Eep! 4 days overdue now. Issues have feelings too...

@kevinksullivan Still overdue 6 days?! Let's take care of this!

@kevinksullivan 10 days overdue. I'm getting more depressed than Marvin.


Show original Archetype names in backtraces.

Since this information is now available in DWARF, LLDB can display the
correct names for archetypes when printing backtraces.
rdar://problem/48259889

test with https://github.com/apple/swift/pull/22954
@swift-ci test

test with https://github.com/apple/swift/pull/22954
@swift-ci test

test with https://github.com/apple/swift/pull/22954
@swift-ci test

Works for me. I'll open a separate PR to rename everything.

test with https://github.com/apple/swift/pull/22954
@swift-ci test

test with https://github.com/apple/swift/pull/22954
@swift-ci test

@swift-ci test and merge

@swift-ci test and merge


Better handling error when not available

Add callback for valid and error scenarios.
Allow user to refuse and then accept recording without issue
Allow users to set mic after they refuse the first time .
this code is tested and used there : https://github.com/riderx/capacitor-screen-recorder

@toupper can you please merge or add more people as maintainers to this project? :) thanks

@aehlke Thanks for the ping here! I added you as collaborator, there're some conflicts in this PR, would you like to fix them and merge this PR if you have time?

I can fix my own conflict ^^

I can fix my own conflict ^^

That would be awesome, thanks @riderx! Let me know when it's done so I can merge it :)

should be good

Awesome, thanks @riderx


⚠ Bofrost.nl has degraded performance

In 698ba23, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 974 ms

Resolved: Bofrost.nl performance has improved in 430e215.


Chained value converters can cause infinite loop (freeze)

Testing the PreBeta release I stumbled upon this. It totally freezes my chrome tab.
Just chained a filter and a sort value converter.
This should reproduce it: http://plnkr.co/edit/fFMsS1?p=preview
P.S.: Sorry if this is the wrong repo, I am not that deep into the internals yet.

Still looking into this.  Has to do with the sort value converter mutating the array with each toView call.  If you update the toView function to return array.slice(0).reverse(); instead of array.reverse(); you won't get stuck in the loop.

minimal repro:
export class App {
  filter = '';
  items = ['a', 'b', 'c'];
}

export class FilterValueConverter {
  toView(array, filter) {
    if (filter.length) {
      return array.filter(x => x.startsWith(filter));
    }
    return array;
  }
}

export class ReverseValueConverter {
  toView(array) {
    return array.reverse();
  }
}

<template>
  Filter: <input ref="input">

${item}

</template>

Thanks a lot for the fast response!
I think there is still a performance penalty in here.
The infinite loop is fixed, but I had the impression that it is way slower than before the PreBeta.  I added the slice(0) just for test and it is indeed faster (not as fast I would have hoped though). This is in my app, I have no plunk for that (yet).
Any ideas?

how many items are in your array?  Can you elaborate on what the perf issue is?  I believe in your example you had a throttle or debounce binding behavior on your filter input- is that what is making it seem slower?  Because the array filtering is delayed?

Thanks to the explanations about the array mutations and the usage of slice(0) I think I can live with my current implementation. The difference in my app was only the aurelia packages, the debounce was there before (own implementation, still is. Didn't convert to aurelia debounce there yet).
The performance difference between aurelia-mid-october and pre-beta were around 3 seconds for ~350 array items without any code changes. As in 3 instead of 0.x seconds. With slice(0) I would have to measure if there is even a real difference.. it "feels" slower.


null pointer dereference in squeeze

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 18.04.6
Mobile device
No response
Python version
Python 3.8.3
Bazel version
bazel 5.3.0
GCC/compiler version
gcc 7.5.0
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
A maliciously constructed squeeze operator model leads to op_context.output being empty, causing a null pointer dereference in the ResizeTensor function.
// squeeze.cc
TfLiteStatus Prepare(TfLiteContext* context, TfLiteNode* node) {
  SqueezeContext op_context(context, node);
      ...
  return context->ResizeTensor(context, op_context.output, output_dims);  // op_context.output is null
}

// subgraph.cc
TfLiteStatus Subgraph::ResizeTensor(TfLiteContext* context,
                                    TfLiteTensor* tensor,
                                    TfLiteIntArray* new_size) {
  if (tensor->data.raw != nullptr &&   // tensor is nullptr
      EqualArrayAndTfLiteIntArray(tensor->dims, new_size->size,
                                  new_size->data)) {

squeeze.zip
Standalone code to reproduce the issue
I use the benchmark tool built according to [this official guide](https://www.tensorflow.org/lite/guide/build_cmake#step_1_install_cmake_tool), as follows:
1. git clone https://github.com/tensorflow/tensorflow.git tensorflow_src
2. mkdir tflite_build && cd tflite_build
3. cmake ../tensorflow_src/tensorflow/lite
4. cmake --build . -j
5. cmake --build . -j -t benchmark_model

The benchmark is in the tools directory

When I use the benchmark tool for PoC validation, it causes the TensorFlow Lite inference process to be subjected to a DOS（coredump).

❯ ./benchmark_model --graph=../poc/squeeze.tflite
INFO: STARTING!
INFO: Log parameter values verbosely: [0]
INFO: Graph: [../poc/squeeze.tflite]
INFO: Loaded model ../poc/squeeze.tflite
ERROR: Invalid tensor index 1025 in inputs. The subgraph has 3 tensors

INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
[1]    25682 segmentation fault (core dumped)  ./benchmark_model --graph=../poc/squeeze.tflite

Relevant log output
No response

This issue originally reported by @SiriusHsh has been moved to this dedicated repository for LiteRT to enhance issue tracking and prioritization. To ensure continuity, we have created this new issue on your behalf.
We appreciate your understanding and look forward to your continued involvement.


Extraction half of frames

When I try to extract keyframes from a long video(about 30 min and more), it only works for half the length of the video and then stops:

I will be appreciate your help!

Could you provide debug logs to assist?  You can add -v debug -l BUG_REPORT.txt to create one.  Thanks.

Could you provide debug logs to assist? You can add -v debug -l BUG_REPORT.txt to create one. Thanks.

I started with debug, but it's still not clear for me to understand what happend:

But i figured out that my test video has ~50fps. Can the problem depends on huge fps?

Is that the same video?  If the framerate is 50 FPS, then 131833 frames represents 43 minutes [1] that PySceneDetect processed.  The progress bar bases the total # of frames on whatever the video container reports, which may not be accurate.  To confirm this, you can try re-encoding the video with ffmpeg and then process it again with PySceneDetect.
Are you seeing this problem on different videos or just a single input?  Have you tried another backend (e.g. --backend pyav)?
[1]  131833 frames / (50 frames/sec * 60 secs/min) = 43 minutes

Is that the same video? If the framerate is 50 FPS, then 131833 frames represents 43 minutes [1] that PySceneDetect processed. The progress bar bases the total # of frames on whatever the video container reports, which may not be accurate. To confirm this, you can try re-encoding the video with ffmpeg and then process it again with PySceneDetect.
Are you seeing this problem on different videos or just a single input? Have you tried another backend (e.g. --backend pyav)?
[1] 131833 frames / (50 frames/sec * 60 secs/min) = 43 minutes
Edit: To answer your question, the problem shouldn't depend on framerate as long as it is fixed.

I've tried 2 diffrent video(both 50 fps, ~1.5 hours). But it's always processes half of the frames.
I agree with your calculation. But when i save one image per scene and looking at last image, i see ~the middle frame of my vildeo.
I also used another backend(moviepy) and it works well(with all frames), but too slow compared to opencv(4-5 times slower).

Are you able to share a sample video with me that shows the issue?  That would be useful to help debug what the issue may be.  Thanks!


simplify ci cache

Codecov Report

Merging #11 (f7b5178) into master (ffffe13) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   96.32%   96.32%
=======================================
  Files          11       11
  Lines         381      381
=======================================
  Hits          367      367
  Misses          7        7
  Partials        7        7

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 ffffe13...f7b5178. Read the comment docs.


Windows support for bootloader

Adds windows support for the bootloader by fixing the USB and HID descriptors to proper values and adjusting end of scratchpad transfer detection.
Other than Linux, Windows will not allow any communication with a USB device that does not exactly follow the specs and matches USB descriptors.
The original USB descriptor advertises a wMaxPacketSize of 64 which is invalid for low speed USB devices, causing enumeration to fail on many host controllers. The maximum allowed for low speed devices is 8 Bytes.
The HID descriptor had a wrong Report Count and was missing a Report Size, resulting in an undefined or zero length of data it would accept.
Also added make_win.bat to build and flash the bootloader, as the make-file did not work properly for me on windows.
Fixes issues #21 and #24.

@cnlohr I tried the bootloader also on Debian Linux and minichlink uploads fine, but ends with errors when the chip is rebooted:
$ sudo ./minichlink -w neo_blue.bin flash -b
Found B003Fun Bootloader
Halting Boot Countdown
Interface Setup
Image written.
Booting
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe

I guess that's fine though?

Unless the device has support for USB, that is exactly what it should do.
This is AMAZING.  Thank you so much @xsrf

Any chance you could be interested to join our discord? https://discord.gg/JsK7Hhfeyt


Combined training from scratch

Hi, it's really a great work, and I have successfully trained the JBU upsampler. The high-resolution feature map looks great. I'm just wondering have you ever tried to train these upsampler and downsampler along with the model all from scratch? Will it boost the performance?

That's great news! What hyperparams have you used? I've tried on a custom dataset but I haven't been able to get a good performance yet

Got it, it seems there is a gap between the default hyper parameters and the one used in the paper but it's good to know that the default values worked for you.
Actually, I did use a pre-trained encoder and I was able to train it but it seems it doesn't work well for small objects, which is also mentioned in the paper

Hi, I encountered a "FileNotFoundError: [Errno 2] No such file or directory: '/pytorch-data\cocostuff\curated\train2017\Coco164kFull_Stuff_Coarse.txt'" error message while running the “train_jbu_upsampler.py” file. How did you resolve it? Where do I download the "Coco164kFull_Stuff_Coarse.txt" file? Or what is the way to add the dataset?


US 01.07.01

Issue:
As a doer, I want to see what habits I need to do today.
Risk:
Medium
Story Points:
3

finished


Source code for "Deep Factors for Forecasting"(DEEP-FACTOR)

Description

Hi, if there are source codes for paper "Deep Factors for Forecasting".  I want to implement the  DEEP FACTOR model mentioned in the pape for research purpose.

References

paper Deep Factors for Forecasting

Hello, do you want to discuss about the paper details by any chance?

Hi @lennonmwy,
sorry for the delay in answering. We will bring the DeepFactor model to GluonTS in the near future (hopefully weeks rather than months) and @lovvge and @dcmaddix are eager to get their hands on it.
For the time being, we have the Deep State Space model implementation coming in now: https://github.com/awslabs/gluon-ts/pull/229

Dear  Team,
Any progress on the issue( the DeepFactor model )?
Thanks!

There's a PR for this now: https://github.com/awslabs/gluon-ts/pull/259
There's still some work needed, to make the data loader more efficient for example, so that it becomes usable.

There's a PR for this now: #259
There's still some work needed, to make the data loader more efficient for example, so that it becomes usable.

Thanks!


Strip colour codes from the file output

in the log file output the colour codes exist, these should be stripped out by default. Only the console log output should include colour data.
e.g. below includes the colour codes.
2024-04-05-11:01:40,  [0;35mLOG    [0m, src/cunit/ut_cunit.c,    92 :  [0;32m---- start of test run ---- [0m

Fixed in https://github.com/rdkcentral/ut-core/pull/41


Remove Travis configuration that matches default

Trusty based container builds are the default as of August 2017 (docs). Additionally, start the .travis.yml with ---\n as suggested by yamllint.

LGTM. Merge when you're ready.

Awesome, thanks!


Avoid sleeping unnecessarily during tests

This timeout parameter is used (and set) by the cancel tests but not by all the other tests that use this class.

Coverage remained the same at 89.931% when pulling 5d2cf3210a5eef9dc9d0d43a7099b06f731def01 on speed-up-inner-tests into e17f9ed575479de4623ee5ca952ffe544bac91ab on master.

Coverage remained the same at 89.931% when pulling 5d2cf3210a5eef9dc9d0d43a7099b06f731def01 on speed-up-inner-tests into e17f9ed575479de4623ee5ca952ffe544bac91ab on master.

Before: 5m43s per branch
After: 1m24s per branch


[core] Add additional browsers for detection

Packages impacted by this PR

@azure/core-rest-pipeline
@typespec/ts-http-runtime

Issues associated with this PR
Describe the problem that is addressed by this PR
Adds Opera to the browsers list.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Chrome/Chromium on high dpi screen wrongly moves dragElement

On my test machine (Linux Debian with Chromium) with a high dpi monitor the dragged element is moved twice as fast compared to the mouse movement .
It appears that somehow the hi dpi settings aren't respected. It appears that some kind of padding is applied to the dragged element that is to big and grows with every mouse move.
This problem does not occur on Firefox on the same hidpi machine.
Exact version:
Version 46.0.2490.71 Built on Debian stretch/sid, running on Debian stretch/sid (64-bit)
I have tested in on the exact same Chromium browser on a computer with a normal DPI screen. No bugs there.

No ideas.

Duplicate: https://github.com/RubaXa/Sortable/issues/674


Added explicit compilers to spack spec

Added gadi intel compilers and paths

We may have to remove this commit in the future, if CD can work with a centralised Spack config.


Fix README.md typo

Thanks for the port of this great library.

Coverage remained the same at 99.465% when pulling 9f211a371f2e3b0d8267869c5d4d002b952fbb0e on pboyer:patch-1 into cff6aef5d2def34072053d0dfa1663afc599bbaa on Eronana:master.

Thanks!


fix: BYTES column reflection failure

While working on benchmarks I've notice an error with BYTES type reflection. Adding a test reproducing the failure, fixing the error.

LGTM. Were there no BYTES-specific tests in the test suite?

Yeah, I didn't find any, so added several myself.


Parse weburl to construct drive name for OneDrive

OneDrive drive names are always set to OneDrive. For users that have multiple drives, this makes it hard to distinguish
which drive items belong to.
This commit introduces logic where we parse the webURL to extract the underlying sharepoint document library name
and use that as the drive name for OneDrive.
For SP - this behavior is already implemented by the API - so we do not do this.

Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[ ] :green_heart: E2E

I'm working on a sharepoint integration test as well - currently only unit tests + onedrive integration coverage exists in this PR. Let's not block behind that though.

We're going to try something different


Broken floodlights can be used as indestructible barricades

Description
Broken floodlights cannot be attacked nor destroyed while also being able to be unanchored.
This allows them to be used as indestructible walls that xenos can't get past, allowing marines to sit forever in corners or rooms.
Screenshots
https://github.com/user-attachments/assets/883645f4-51be-4fae-8530-a4f66732e5c9

I love how I made sure to fix this and then it just didn't work 😀😀😀😀

Them being indestructible is intended behavior though, they shouldn't be able to be unanchored

Popping this here quickly
CM parity, they're not moveable for a reason and generally can't be fully destroyed but have lengthy repair time
They were made impossible to move specifically for parity (and because people abused it)

you cant unanchor flood lights anymore, so this is fixed i think


Update Sentry integration with new PHP/JS libs

@mlabarrere, I use Staging environment value as CI deploys only this env


[jpegd] Use correct mfxVideoParam in VideoVppJpegD3D9 initialization

The regression was introduced in bb9a4a08, mfxVideoParam in
mfx_UMC_FrameAllocator_D3D_Converter::InitMfx() is for decoder only,
it ignores VPP step.
Issue: MDP-57600

Could u please clarify what is

mfx_UMC_FrameAllocator_D3D_Converter::InitMfx() is for decoder only
?

On InitMfx() callchain, in VideoDECODEMJPEG::Init() (see mfx_mjpeg_dec_decode.cpp:249) mfxVideoParam updated with FrameInfo that matches output of jpegd, before vpp step.


[Enhancement] Deduplicate the partitionValues in the createPartition RPC to avoid unnecessary overhead for the FE

Why I'm doing:

partitionValues in createPartition RPC may have duplicate record, it will cost unnecessary overhead on FE.

What I'm doing:

Deduplicate partitionValues
use INFO replace VLOG after we deduplicate the log

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

Why not deduplicate it on the FE end?

Why not deduplicate it on the FE end?

a lot of rpc overhead

@mergify backport branch-3.2 branch-3.1


remove useless yamls

Description
    deleted:    config/manager/kustomization.yaml
    deleted:    config/manager/manager.yaml

these two files are used to generate a yaml file of deployment/service, it not needed in current project.
Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a.
Tests
will be covered by CI/CD

The image registry within the CI is being rebuilt, please hold the test until it's done


[1.10.2] Crash with transpo

Issue description:
Crashes when ticking transporter when TransitResponse.EMPTY is returned in InventoryUtils and getRejected is called without checking before if its empty
MultipartTransporter where the Responce is requested
https://github.com/aidancbrady/Mekanism/blob/1.10/src/main/java/mekanism/common/multipart/MultipartTransporter.java#L119
InventoryUtils whre an Empty Responce is returned
https://github.com/aidancbrady/Mekanism/blob/1.10/src/main/java/mekanism/common/util/InventoryUtils.java#L260
TransitResponce where the actual NPE happens
https://github.com/aidancbrady/Mekanism/blob/1.10/src/main/java/mekanism/common/content/transporter/TransitRequest.java#L151
Steps to reproduce:
Idk but the code/crashlog dosn't lie and it happens
Version (make sure you are on the latest version before reporting):
**Forge:Forge <IP_ADDRESS>6
**Mekanism:Mekanism-1.10.2-9.2.2.final  (yes i know not the newest but showed it in the current code)
**Other relevant version:MCMultiPart-1.4.0-universal
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
https://hastebin.com/aretojozic.scala

Picture of the setup (the chest is full, the bedrock is the block that caused the error)
It happens when you you got a loop with a chest and the pipes and the chest is actually full during one item got looped

I can confirm im getting reports of this issue to from a server network and im using the last mekanisn which is the final fix one

Please try with this build (or build from source) http://maven.thiakil.com/mekanism/MekanismAll-1.10.2-<IP_ADDRESS>4-thiakil.jar

@thiakil im unable to test as its a server running my pack that seems be getting the crash, otherwise i would test, hopefully @essem2 can test ASAP.

@thiakil could not really replicate it and the original case got fixed by replacing the pipe with a bedrock.
the code seems to work.
Notreally part of the crash but related:
Isn't it a performance leak if a pipe connected to its own chest always pump items in a loop?

I'd appreciate it if you could re-test the original crash conditions.

Isn't it a performance leak if a pipe connected to its own chest always pump items in a loop?

That's just user error, Most mods don't have any special handling for feeding to another side of the same block.

@thiakil the original case was on a server where i don't have enough permissions to modify the server so i rebuilt it in singleplayer

ok, does that setup crash with the build on curseforge?

nope

@thiakil @aidancbrady any chance a new version can be posted to curse as i really need the fix for this crash

Can you verify if it actually fixes anything?

@thiakil i can give me 10

@thiakil Ok it seems to work 99% of the time, i seem to get this in one of my test worlds https://pastebin.com/cRgXG7z6 after loading it up with version on curseforge and then it crashed i loaded it up with the custom version above and then i got that error each time, but when i used the backup of the world and straight loaded the crashing world with the custom version it worked fine everytime

Great, I can poke Aidan to see if he'll release one.
That new message is known about, it was fixed on 1.11 but not backported as 1.10 is on critical-fixes-only kinda updates. I've added it to 1.10 now

@thiakil Thanks, any eta on that release as im about to update my packs so dont know if i should wait for the build release....

@thiakil, check out 9.2.2.fix3 - on Curse right now :)

Yayyyy @aidancbrady


Font misalignment on intro to managing npm packages

For some reason, the font changes halfway down this introduction. The file is here. I don't see the problem at first glance. Probably just a spacing issue or something.

Hi @moT01 . It looks like the problem caused by HTML tags in the text. I removed them and it looks better. Please check PR.


RUM-7302: Align log levels for sr already enabled

What does this PR do?
Aligns the log levels with iOS for the error we output when a user tries to enable session replay twice (either on the same core or on different cores) - "Session Replay is already enabled"
Motivation
On iOS they output an error to the user and debug to the telemetry.
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 69.75%. Comparing base (ff6002f) to head (8a6a881).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2399      +/-   ##
===========================================
- Coverage    69.82%   69.75%   -0.07%
===========================================
  Files          763      763
  Lines        28360    28363       +3
  Branches      4763     4761       -2
===========================================
- Hits         19801    19782      -19
- Misses        7246     7258      +12
- Partials      1313     1323      +10

Files with missing lines
Coverage Δ

...com/datadog/android/sessionreplay/SessionReplay.kt
72.09% <100.00%> (+2.86%)
:arrow_up:

... and 31 files with indirect coverage changes


DONATIONS

before launching we need an easy way for people to donate. Very similar to the top up button in the wallet area.
If someone has donated, we could wait 6 months etc before asking again
Should also have on website at point of download


No catching pokemons and jump

Expected Behavior
Actual Behavior

Steps to Reproduce
Config
{
"auth_service": "google",
"username": "",
"password": "",
"gmapkey": "",
"max_steps": 10,
"mode": "all",
"walk": 4.16,
"debug": false,
"test": false,
"initial_transfer": 0,
"location_cache": true,
"distance_unit": "km",
"item_filter": "201",
"evolve_all": "NONE",
"cp_min": 300,
"use_lucky_egg": false,
"evolve_captured": false,
"catch": {
"any": {"catch_above_cp": 10, "catch_above_iv": 0.1, "logic": "or"}
},
"release": {
"any": {"release_below_cp": 1000, "release_below_iv": 0.8, "logic": "or"},
"Rattata": { "always_release" : false },
"Pidgey": { "always_release" : false },
"Weedle": { "always_release" : false }
}
}
Other Information
OS:
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here)

I confirm this bug,  walk around and  catch noting.

The Bot is NOT jumping around (look at the destinations). The log messages are a bit confusing. Switch to newest dev which fixes those messages. The fact that the bot is not catching pokemon while farming is known and the bugfix is already in the works.

Not catching any Pokemon bug: https://github.com/PokemonGoF/PokemonGo-Bot/issues/821

Clean up your old clone.

As mentioned by @bstpierr this is a duplicate.


Setup staging nodes that are updated nightly

Description
Setup nodes on MainNet and Pyrmont that are updated nightly to provide early feedback.

Actually pretty straight forward.  Look at the way besu does it in the system-tools repo playbooks/roles/development-node

Done.


feat: Retry endpoint calls by default for specific response status co…

…des, with MAX_RETRIES

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 97.79%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
177

Relevant Lines:
181

💛  - Coveralls