File greater than 5GB will cause error

Describe the bug
Hi, I was trying to transfer 4 identical large files (2GB each) from my iPad Pro to PC, and I always got this error message before the last file was transferred.
Error
DioException [unknown]: null
Error: PathNotFoundException: Cannot open file, path = '/private/var/mobile/Containers/Data/Application/F113BB37-75C7-43CE-9CAE-BB34854ED218/tmp/org.localsend.localsendApp-Inbox/ Test.mp4' (OS Error: No such file or directory, errno = 2)
Expected behavior
Being able to transfer file more than 5GB at once
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
iPad Pro M1, iOS 17.2
Windows 11
Additional context
No response

Can you select a folder (with only that file). Does this work?

I just tested it. Sending a folder(1171 files, 20.6G) from Android 13 to windows 10 x64 is available, but when sending another folder(2413 files, 21.2G), the app crashed.

so is there any solution???

I am experiencing the same issue. When I transfer multiple files with a total size of 7.9 GB from my MBP to Windows, the application on Windows crashes. However, there is no problem when transferring small batches.

@ch1lam Regarding Windows, there is a bug in the newest update (1.15.0): #1506

An update on my end. My phone died (Android 12) and I recently purchased an Android 14 phone. Tested with a 6.4 GB file and it worked just fine with Localsend v1.15.1.

I believe that the device that sends the files needs as much RAM as the biggest file, while the receiving device can receive files with unlimited size.

so is there any solution???

Updating the app in both the devices solved this problem for me.

This should be fixed in the latest update now (1.15.2)

Hi, I'm using v1.15.3 on iPhone (14 Pro) and iMac (Intel based / Sonoma), and transferring a single 5.6GB video file from the iPhone to the Mac causes the iPhone app to crash.


Use bootstrap for documentation pages

Is your feature request related to a problem? Please describe.
The CSS within the docs folder is of no use to the package, and only contributes to its total size.
Describe the solution you'd like
Using a bootstrap CDN on documentation pages could eliminate the need for extra CSS.
Describe alternatives you've considered
May consider tailwind too.

This is implemented in v3.4.1.
Closing this.


Filetype plugins seem unnecessarily opinionated with regards to expandtab

I prefer to use spaces over tabs so I set expandtab in my vim config. I have also changed the Godot editor settings to use spaces instead of tabs. However the filetype plugins of vim-godot override this with set noexpandtab. I understand the reasoning is probably just trying to make this plugin work with the default settings of the Godot editor, but vim by default does not set expandtab anyway. So if you use the default Godot settings and the default vim settings, there is no conflict. If I change the Godot setting, then in my opinion it's my job to also change vim's to match, not for the plugin to assume I use the default. So as it is, I either have to override vim-godot in the after directory, so I have to set expandtab twice in two different places, or I have to reach into the plugin itself and modify it. Neither of which are ideal when there's no reason for the plugin to do it in the first place. Or is there a reason I'm not seeing?
Thoughts?

I don't have strong preferences myself as I don't see a problem setting my own preference in my after directory.
So in the beginning expandtab wasn't there and I just had after/godot.vim file with my settings, including set noexpandtab.
Then a new contributor find out that gdscript guidelines suggest to use tabs over spaces and thus by default gdscript uses tabs, the same way python uses spaces, makefiles tabs etc (no matter if you have set expandtab in your vimrc)


emmet-language-server

For omni completion when writing html and emmet, emmet-language-server is a great help. Here is an example config for getting it to work.
call LspAddServer([#{name: 'emmet',
                 \   filetype: 'html',
                 \   path: '/usr/local/node_modules/.bin/emmet-language-server',
                 \   args: ['--stdio'],
                 \ }])

Thanks.  I have updated the wiki with the above sample code for adding the emmet language server.

@yegappan do you mind making multiple-server configuring (for same ft) with features switches (true or false) work again? or it was not working ever, but seems it was mergered be part of our lsp code base already, so perhaps need to make it work (though seems high complexity).
// for now seems only first configured server's features counted.
// supposed nothing impacted for now, just I found it was failed, so jump in to give you a message, take your time anyway.
--
shane.xb.qian

I tested enabling few features in one language server and other features in another language server with two language servers registered for the same filetype.  From the logs, I can see that this works properly.  Do you have the list of steps to reproduce the problem?  Which language servers are you using?  Which features did you try enabling and disabling in the language servers?

you can try pylsp with hover/completion/signature features disabled (false) while pyright with these enabled (true),
you can see hover etc always from pylsp (and disabled) which pyright not really took over the features functionality.
// or here if two for html, it should be same case.
// though i do not recommend this, since it would raise complexity of code and functionality much, but there already.

I tried to reproduce this issue with both the pylsp and pyright language servers registered for python files.  I disabled the hover/completion/signature features for pylsp and enabled for the pyright server.  From the debug logs, I can see that these features are handled by the pyright language server and not by the pylsp server.
I also tried to reproduce this issue with the typescript-language-server and the deno server for typescript files.  I couldn't reproduce this issue.
Can you enable the debug logs for both the language servers and run the ":LspHover" command and see which server is handling the request?  Can you also show how you are registering the language servers?

um, how you can get that debug log? it should be failed immediately when feature check:
Error: Language server for "python" file type supporting "hover" feature is not found
// not much specially, except features option
// 'features': { 'hover': v:false } for pylsp
// 'features': { 'hover': v:true }  for pyright
--
shane.xb.qian

Can you attach the complete call to the LspAddServer() function to register the pylsp and pyright servers with all the arguments?

same like in the wiki, nothing specially except features option.
// according to basic ps cmd, pyright did not even start, but only pylsp, but since it disabled hover feature, so none!
a.k.a :
Error: Language server for "python" file type supporting "hover" feature is not found this err was a correct prompt.
--
shane.xb.qian

if still no clue to you, then let it be..
// it does not bother me actually :smile: and i did not recommended this feature too.
// but just felt like a similar ticket at this repo startup or https://github.com/yegappan/lsp/issues/98 this one.
--
shane.xb.qian

Can you try to reproduce the issue with the latest plugin version?

Can you try to reproduce the issue with the latest plugin version?

i think your latest commits (some mins ago) was not necessary or didnot help something:
1, or even worse, since it mixed to use 'augroup' and 'aupat' in this repo, make more confused much;
2, these buf/feature check etc seems would not make something different, eventually err prompt if no
3, specially i have no confident to verify all your change(these commits) i donot see it was bug fix
IMO:
a, that inlay hints #357 my pr worked, but just i guess was a vim bug to make 'once' be failed.
b, this multiple-servers features seems rare and conner case let it be is ok!  <---
i guess it was init timing issue, it would be failed in some specific case
but mainly it should be worked as you said, just vim9 had some tiny diff..
c, if you have time, #338 maybe more valuable
// though not only py env dyn change issue,
// e.g go.mod (and/or its import pkg) changed, seems re-effect the changes seems do was an issue,
// 'lspserver restart' seems not help some.
// i was observing as well, no clue so far.
--
shane.xb.qian


install tls support into conduit

tried to fix #9 , but encountered a bug in a dependent library,
have to wait for the fix patch to be merged

don't wait for upstream merging, instead use a local fix instead


why is output(w_opt) a zero matrix? can someone assist me here. because optimal value of the objective function is correct but output matrix is printed as a 2x3 zero matrix yet it shouldnot be a zero matrix.Thanks

import cvxpy as cp
import numpy as np
Define problem parameters
I = 3  # Number of users
J = 2  # Number of antennas
P_max_t = 20  # Maximum transmit power
Gamma_th = 5.0  # Interference threshold
g = np.random.rand(I, J)  # Channel gain matrix
eta = np.random.rand(I, 1)  # Weighting factor for each user (reshaped to column vector)
xi = np.random.rand(I, 1)  # Satisfaction level for each user (reshaped to column vector)
Define optimization variables
w = cp.Variable((J, I), complex=True)
z = cp.Variable((I, 1))
Define optimization objective
objective = cp.Maximize(cp.sum(cp.multiply(eta, cp.multiply(xi, cp.log(z)))))
Define constraints for z
z_constraints = [z[i] >= 1 + cp.abs(g[i, :] @ w[:, i])**2 for i in range(I)]
Define optimization constraints
constraints = [
cp.sum_squares(cp.norm(w, axis=0)) <= P_max_t,
cp.sum([cp.sum_squares(cp.multiply(g[i, :][:, np.newaxis], w[:, np.arange(I) != i])) for i in range(I)]) <= Gamma_th,
] + z_constraints
Solve optimization problem
problem = cp.Problem(objective, constraints)
problem.solve()
problem.solve(solver=cp.SCS)
Extract optimal solution
w_opt = w.value
print("Optimal value:", objective.value)
print(w_opt)

Hi, @balexx2! If it's not too much trouble, please ask these kinds of questions on GitHub Discussions or our Discord. It seems off-topic for GitHub Issues, so I'll be closing it for now.


Don't infer return type in function/method blocks

A spiritual ancestor of #748 and #215. Fixes #151 in case incompatible return types are actually reachable (which seemed to be the issue, given the title). #1133 follow-up.
Resolves #1092 and resolves #1093 because we no longer infer the return type for function blocks. Fixes #483.
Not sure about the generic stuff, please check :^)
I don't know how to put a commit description without commit linter complaining, so I'll just paste it here:

This refers to functions as well as methods that are not fat-arrow.
Parser and a couple of tests needed to be updated in some cases, to specify the return type.
When the return type is not specified for not-fat-arrow functions, it is set to void.

Might have fixed that for methods too. I'll test a little bit and push when I'm done

Hello!
One or more of the commit messages in this PR do not match the Jakt code submission policy, please check the lint_commits CI job for more details on which commits were flagged and why.
Please do not close this PR and open another, instead modify your commit message(s) with git commit --amend and force push those changes to update this PR.

@jntrnr I've added some comments and deleted some debug variables / checks that I forgot about (oops...). Sorry for the mess, it must have been a pain to understand the changes.
I've also added one fixme, because even after this PR we still don't check properly the type of make_memo() in
/tests/typechecker/generic_across_scopes.jakt. The tests itself is unfortunately way above my head and I don't know what the exact problem is.
If the PR gets merged I'll probably add an issue for that

we still don't check properly the type of make_memo()

That has an explicit return type, and is correctly typechecked on main - what fails?

we still don't check properly the type of make_memo()

That has an explicit return type, and is correctly typechecked on main - what fails?

Nah, it doesn't fail the test itself, but when you change
function make_memo<R, S>() throws -> Memo<R, S> {
    let value: [R:S] = [:]
    return Memo(value)
}

to... for example this:
function make_memo<R, S>() throws -> Memo<R, S> {
    let value: [R:S] = [:]
    return ""
}

It doesn't complain and generates invalid cpp code (even on main)

Pushed up the changes. If I remove the or .get_type(checked_expr.type()) is TypeVariable on line 3824 in the early return, the only failing test now is generic_across_scopes.jakt with the error
----- ./tests/typechecker/generic_across_scopes.jakt:28:13
 27 |         if memo!.value.contains(x) {
 28 |             return memo!.value[x]
                  ^- Type mismatch: expected ‘i64’, but got ‘V’
 29 |         }
-----

It might not even be related to the is TypeVariable early return
Am I dumb or this error is getting swallowed? This does not print any Jakt errors and gets past the codegen stage, where invalid C++ is emitted

You learn something everyday

Not sure if this is the way, but I set ignore_errors to false before checking for type compatibility in typecheck_return() and after the check I restore its value. Thanks to this, we properly error when the return type of make_memo is wrong.
I've added a test case for it as well.
I don't think there are any other known issues.

The first pass over generic functions should ignore errors - that's expected
The second specialised pass (on call) should not be ignoring it though

So is there a bug somewhere? It seems to be set to true both times we call typecheck_return for make_memo

There seems to be a bug for sure.
function make_memo<R, S>() throws -> Memo<R, S> {
    let x: String = 32
    let value: [R:S] = [:]
    return Memo(value)
}

Assigning i64 to String gives us...
root@CloverLaptop:/home/jakt# ./build/jakt ./tests/typechecker/generic_across_scopes.jakt
internal error: Garbage statement in codegen
Aborted

We don't really typecheck functions like make_memo at all currently, so I'll remove the hack with setting .ignore_errors = false, I don't think it would work in all cases regardless.


Update cross-compile docker image: contrib/Dockerfile

Fixes docker image's cross compile issues for arm-unknown-linux-gnueabihf.
Not sure if changes are desirable upstream, but fixed this for myself and thought that others might find it useful.
error: failed to run custom build command for `aws-lc-sys v0.21.2`

Caused by:
  process didn't exit successfully: `/build/release/build/aws-lc-sys-d28a1b34df617185/build-script-main` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX
  cargo:rerun-if-env-changed=AWS_LC_SYS_INTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_CFLAGS
  cargo:rerun-if-env-changed=AWS_LC_SYS_PREBUILT_NASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_C_STD
  cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER
  cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
  cargo:rerun-if-env-changed=CMAKE

  --- stderr
  Missing dependency: cmake
  thread 'main' panicked at /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/builder/main.rs:315:40:
  called `Result::unwrap()` on an `Err` value: "Required build dependency is missing. Halting build."
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
...
cargo:warning=Generating bindings - external bindgen. Platform: arm-unknown-linux-gnueabihf
...
 --- stderr
  Consider installing the bindgen-cli: `cargo install --force --locked bindgen-cli`
  See our User Guide for more information about bindgen:https://aws.github.io/aws-lc-rs/index.html
  Failure invoking external bindgen! External bindgen command failed.
  thread 'main' panicked at /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/builder/main.rs:559:5:

Thanks. More people have reported problems with this, so I this should be a good step.

I'm trying to cross-compile for armhf (Raspberry Pi Zero 2W running 32-bit Bullseye). While I can now compile using vulkoingim's new Dockerfile (thanks for that!), it looks like the new binary requires version 2.32 of libc, presumably because the container now uses Bookworm as the build environment. Is there any way around this? I tried downgrading the Dockerfile to Bullseye (just replacing Bookworm with Bullseye in the relevant lines as well as removing the armel packages). The environment builds without errors, but when I compile, I get this error, which is similar to but a bit different from the original issue that the new file addressed:
The following warnings were emitted during compilation:

warning: CMAKE environment variable set: cmake
warning: Generating bindings - external bindgen. Platform: arm-unknown-linux-gnueabihf

error: failed to run custom build command for `aws-lc-sys v0.21.2`

Caused by:
  process didn't exit successfully: `/build/release/build/aws-lc-sys-7ed2ad5b4505cda7/build-script-main` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX
  cargo:rerun-if-env-changed=AWS_LC_SYS_INTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_CFLAGS
  cargo:rerun-if-env-changed=AWS_LC_SYS_PREBUILT_NASM
  cargo:rerun-if-env-changed=AWS_LC_SYS_C_STD
  cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER
  cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
  cargo:rerun-if-env-changed=CMAKE
  cargo:rerun-if-env-changed=CMAKE
  cargo:warning=CMAKE environment variable set: cmake
  cargo:warning=Generating bindings - external bindgen. Platform: arm-unknown-linux-gnueabihf
  cargo:rerun-if-env-changed=AWS_LC_SYS_INCLUDES

  --- stderr
  Failure invoking external bindgen!

  bindgen-PARAMS: --prefix-link-name aws_lc_0_21_2_ --allowlist-file .*(/|\\)openssl((/|\\)[^/\\]+)+\.h --allowlist-file .*(/|\\)rust_wrapper\.h --rustified-enum point_conversion_form_t --default-macro-constant-type signed --with-derive-default --with-derive-partialeq --with-derive-eq --raw-line
  // Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
  // SPDX-License-Identifier: Apache-2.0 OR ISC
   --generate functions,types,vars,methods,constructors,destructors /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/include/rust_wrapper.h --rust-target 1.59 --output /build/arm-unknown-linux-gnueabihf/release/build/aws-lc-sys-2f43f036e7a1cb23/out/bindings.rs --formatter rustfmt -- -I /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/include -I /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/aws-lc/include
  bindgen-STDOUT:
  bindgen-STDERR: /usr/include/stdint.h:26:10: fatal error: 'bits/libc-header-start.h' file not found
  panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bindgen-cli-0.70.1/main.rs:45:36:
  Unable to generate bindings: ClangDiagnostic("/usr/include/stdint.h:26:10: fatal error: 'bits/libc-header-start.h' file not found\n")

  thread 'main' panicked at /build/cache/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.21.2/builder/main.rs:559:5:
  aws-lc-sys build failed. Please enable the 'bindgen' feature on aws-lc-rs or aws-lc-sys.For more information, see the aws-lc-rs User Guide: https://aws.github.io/aws-lc-rs/index.html

Apologies if I'm missing something stupidly obvious; I'm relatively now to Rust cross-compilation, so definitely possible I'm just being a doofus.

I'm trying to cross-compile for armhf (Raspberry Pi Zero 2W running 32-bit Bullseye). While I can now compile using vulkoingim's new Dockerfile (thanks for that!), it looks like the new binary requires version 2.32 of libc, presumably because the container now uses Bookworm as the build environment. Is there any way around this? I tried downgrading the Dockerfile to Bullseye (just replacing Bookworm with Bullseye in the relevant lines as well as removing the armel packages). The environment builds without errors, but when I compile, I get this error, which is similar to but a bit different from the original issue that the new file addressed:
...
Apologies if I'm missing something stupidly obvious; I'm entirely new to Rust cross-compilation, so definitely possible I'm just being a doofus.

I'm also running a 32-bit OS, but it does have a more recent libc.
I went straight for bookworm, as I just brute forced my way through updating the deps 😅  I just tried with bullseye and got it to compile with:
RUN apt-get install -y gcc-arm-linux-gnueabihf libc6-dev-armhf-cross
ENV CPATH=/usr/arm-linux-gnueabihf/include

docker run -v /tmp/librespot-build:/build librespot-cross cargo build --release --target arm-unknown-linux-gnueabihf --no-default-features --features alsa-backend

Can you try and see if that would work?

 Thank you so much; that worked perfectly. Adding in those dependencies was all I needed, and it runs like a charm on my Zero 2 now. I merged in #1359 and am now off to see if that fixes that keepalive issue for me (probably will, since it seems like it fixed it for everyone else).
Thanks again!


ModuleNotFoundError with newest versions of pynitrokey and spsdk

Hello, I get this error when trying to run nitropy.
Python version: 3.8.12
OS: OpenSUSE Tumbleweed
pynitrokey==0.4.13
spsdk==1.6.0
$ nitropy
Traceback (most recent call last):
  File "/home/a/python/nitrokey/bin/nitropy", line 5, in <module>
    from pynitrokey.cli import nitropy
  File "/home/a/python/nitrokey/lib/python3.8/site-packages/pynitrokey/cli/__init__.py", line 20, in <module>
    from pynitrokey.cli.nk3 import nk3
  File "/home/a/python/nitrokey/lib/python3.8/site-packages/pynitrokey/cli/nk3/__init__.py", line 21, in <module>
    from pynitrokey.nk3 import list as list_nk3
  File "/home/a/python/nitrokey/lib/python3.8/site-packages/pynitrokey/nk3/__init__.py", line 13, in <module>
    from .bootloader import Nitrokey3Bootloader
  File "/home/a/python/nitrokey/lib/python3.8/site-packages/pynitrokey/nk3/bootloader.py", line 18, in <module>
    from spsdk.sbfile.images import BootImageV21
ModuleNotFoundError: No module named 'spsdk.sbfile.images'

When changing bootloader.py line 18 to:
from spsdk.sbfile.sb2.images import BootImageV21
it works:
$ nitropy
Usage: nitropy [OPTIONS] COMMAND [ARGS]...

Options:
  --help  Show this message and exit.

Commands:
  fido2    Interact with Nitrokey FIDO2 keys, see subcommands.
  ls       List Nitrokey keys (in firmware or bootloader mode)
  nethsm   Interact with NetHSM, see subcommands.
  nk3      Interact with Nitrokey 3, see subcommands.
  pro      Interact with Nitrokey Pro keys, see subcommands.
  start    Interact with 'Nitrokey Start' keys, see subcommands.
  storage  (experimental) 'Nitrokey Storage' keys, see subcommands.
  version  Version of pynitrokey library and tool.

Hi!
Indeed, we need to make a new release yet adjusted to spsdk 1.6.0. I am just working on it. For a quick workaround you can downgrade spsdk to 1.5.0, like:
python3 -m pip install -U spsdk==1.5.0

Details:

https://github.com/Nitrokey/pynitrokey/pull/180#issuecomment-1031209339

OK thanks. Wow, github didnt show me the PR.

New release 0.4.15 is already available on PIP. To update:
python3 -m pip install -U --user pynitrokey

Please reopen in case it would not work for you. Closing as done.

Can confirm it is fixed with 0.4.15. Thanks for the pretty fast reply!

Great! Thank you for retesting!


added links to training and GitHub directions to create an account

Per Chan's request in the Transition document, I've added a link to Josh's overview. Because we've had questions about it, I've added a link to the GitHub directions for creating a GitHub account.
The style of this section is somewhat conversational, I've kept that going. If it seems too informal I can change it.

@elisabethpatterson, this is just my opinion, but I think this update should be a note.  Also, please add something to indicate that NOAA.gov users can view the file linked.  Perhaps "NOAA.gov users that need help getting started, please ..."

I have no objection to either suggestion, and will make the updates when
I'm back in working order.
On Mon, Jul 22, 2024 at 3:09 PM Seth Underwood @.***>
wrote:

@elisabethpatterson https://github.com/elisabethpatterson, this is just
my opinion, but I think this update should be a note. Also, please add
something to indicate that NOAA.gov users can view the file linked. Perhaps
"NOAA.gov users that need help getting started, please ..."
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-RDHPCS/noaa-rdhpcs.github.io/pull/132#issuecomment-2243635436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4T5JWYN3JQHUGS2XLOJID3ZNVKHVAVCNFSM6AAAAABLAS7GXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBTGYZTKNBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

This will close #82 and #141


GC pods using background propagation

Summary
Any reason to GC pods in the foreground?
Use Cases
When would you use this?

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I don't think this gives the benefit I expect. I expect it will be better to have more Groutines deleting pods in parallel.


Add SkiaSharp.Views.Forms.WPF Directory.Package.props

I know nothing about Directory.Package.props but got a compile error on SkiaSharp.Views.Forms.WPF and since it was missing from Directory.Package.props I added it there.

This was the error:
NU1010	The PackageReference items SkiaSharp.Views.Forms.WPF do not have corresponding PackageVersion

This is the correct solution when this error occours


Add whitespace control to "Permissions required for GitHub Apps"

Why:
Permissions required for GitHub Apps contains several endpoint lists, but some are displayed dense and others widely spaced. This is caused by unintentional blank lines in the list markup, namely by version conditions using {% if %} blocks without whitespace control.
What's being changed:

Add whitespace control, e.g. {% if -%} (note the hyphen)
Simplify logic for Permission on "security events" section
Minor consistency changes (- for list items instead of *), no blank lines between items

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).

Thanks so much for opening a PR with this fix @Simran-B! I'll get it triaged for review ⚡

I'll do another pass to revert some whitespace control again where it breaks the layout or is unnecessary (at the end of lists).


lag while new update

Issue Type: Bug
IDE starts to lag or hang whenever there is a new update arrives in the background or any notification arrives.
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 6.3.9600

The same problem

OK let me know.

again its happening,lagging every-time switching tab or opening new file., see attached snapshot of process explorer.

Can you perhaps do the following when it happens again:

Run Developer: Toggle Developer Tools
Switch to the Performance tab
Run a performance recording for ~10 seconds without touching anything

Send me that recording. Thanks!


rspec not working: encoding

  1) Isobib::IsoBibliography fetch hits of page
     Failure/Error: while resp.body !~ /<strong/ && n < 10

     ArgumentError:
       invalid byte sequence in US-ASCII
     # ./lib/isobib/scrapper.rb:183:in `=~'
     # ./lib/isobib/scrapper.rb:183:in `!~'
     # ./lib/isobib/scrapper.rb:183:in `get_page'
     # ./lib/isobib/scrapper.rb:57:in `parse_page'
     # ./lib/isobib/hit.rb:22:in `fetch'
     # ./lib/isobib/workers_pool.rb:18:in `block (2 levels) in worker'

— which is why I'd introduced
        resp = Net::HTTP.get_response(uri).encode("UTF-8")

Closing: duplicates #26


Feature request: modify hydra on-the-fly

Hi,
I'd like to have the possibility to modify the hydra on-the-fly
Use case: Bind a hydra to the snippets and modify it when the lexer changes.
When I'm working on a Lua file, I'd like my Lua snippets to appear on the hydra and when I work on Python, I'd like to see my Python snippets appearing...
events.connect(events.LEXER_LOADED, function(lang)
-- (Re)create my_lang_snippets hydra
   hydra.rebind({key='ctrl+S', help='snippets', action=my_lang_snippets})
end)

I already know how to create the snippets hydra ;-)

That would be a good feature to have. I'll work on it.

A quick hack to reload the hydra...
works for me (TM) ... but could be nicer (TM)
Best, /PA
On Sun, 10 Jul 2022 at 14:17, Amy de Buitléir @.***>
wrote:

That would be a good feature to have. I'll work on it.
—
Reply to this email directly, view it on GitHub
https://github.com/mhwombat/textadept-hydra/issues/5#issuecomment-1179717727,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZKU4F32JCZXW2LLDYHJADVTK5ODANCNFSM53ESISBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

Screencast_11-07-22_10:29:55.webm
A small proof of concept... I'm hacked viciously ;_) to change the hydra when I change lexer.

I'm pushing a new version of hydra to the repo. It's a first step toward a nicer way to change hydra bindings on-the-fly, but I still have a few things to do to support that properly.
The downside is that in order to use the new version, you will have to make a small modification to your init.lua. Where you have something like...
local word_hydra = {
  { key='left', help='prev', action=buffer.word_left, persistent=true },
  { key='right', help='next', action=buffer.word_right, persistent=true },
}

hydra.keys = {
  { key='ctrl+w', help="word", action=word_hydra },
}

...you need to change it to...
local word_hydra = hydra.create({
  { key='left', help='prev', action=buffer.word_left, persistent=true },
  { key='right', help='next', action=buffer.word_right, persistent=true },
})

hydra.keys = hydra.create({
  { key='ctrl+w', help="word", action=word_hydra },
})

@snoopy please see the comment above if you'd like to try the latest version.

I just pushed a new version of hydra to the repo. In your example, something like this should work.
hydra.bind(hydra.keys, {key='ctrl+S', help='snippets', action=my_lang_snippets})

See https://github.com/mhwombat/textadept-hydra#modifying-key-bindings-on-the-fly for more information. Let me know if this meets your needs; if so, I will close the issue.

Cool, thanks a ton!
Changed everything to 'official' :-) and the demo video is still valid..
Really cool to access snippets without interacting with the tools menu.
Best, /PA
On Tue, 12 Jul 2022 at 18:21, Amy de Buitléir @.***>
wrote:

I just pushed a new version of hydra to the repo. In your example,
something like this should work.
hydra.bind(hydra.keys, {key='ctrl+S', help='snippets', action=my_lang_snippets})
See
https://github.com/mhwombat/textadept-hydra#modifying-key-bindings-on-the-fly
for more information. Let me know if this meets your needs; if so, I will
close the issue.
—
Reply to this email directly, view it on GitHub
https://github.com/mhwombat/textadept-hydra/issues/5#issuecomment-1181978401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZKU4CRYPWMEKC2NF5MNTLVTWLO5ANCNFSM53ESISBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet


[BUG] automation docs broken when file trigger is used

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
table for steps look fine when no trigger or schedule is used
but when file trigger is specified it does not have the line break shown here on line 17:

Expected Behavior
add another line break after file trigger section
Steps To Reproduce

Go to '...'
Click on '....'
Run '...'
See error...

Version
4.0.0
Environment

OS:
Node:
npm:

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

also there might be line breaks in the step description that break the table...


Use fixed-size integers

Hi,
I tried to use the DW1000 with the esp8266.
The esp is a 32bit arm which is different to 8bit atmel (Arduino). So I had to use fixed sized integers (stdint.h) to avoid different behaviour on the different architectures.
Sadly I did not got it stable working on the esp. (seems to be related on the SPI clock generator of the spi). But I want to share my code with you, I tested some functions and it worked so far.
Main changes of PR:

integers to fixed sized integers
a lot of todos for the classes and code
reading of OTP.

Best Rotzbua

@Rotzbua I have the DWM1000 working with the ESP8266. I think your suspicion is correct about the SPI clock. By trial an error, I more-or-less accidentally came across a combination of settings that work pretty reliably. First, I changed _fastSPI to 20 MHz. Then, I had to tweak the code in DW1000::select() because there was something it didn't like about calling enableClock(XTI_CLOCK) before manageLDE(). I wouldn't call my solution production-ready, but I'm happy to share and maybe together we come up with something more stable. What's the best way to share my code? Should I open a pull request?

@aacton Hi, I will not work with the esp8266/dw1000 now and in the future. My solution now uses a Sparkfun Pro Micro with<EMAIL_ADDRESS>and I will focus on that combination.
About the SPI speed problem I read something at the elector-magazine (I thing it was the German edition). They programmed a "tuner"-script which runs until the esp8266 has a stable and well known spi speed.

Great, many thanks! Cheers!

In the interest of closing this loop: Regarding my previous comment about issues with the ESP8266, after much investigation, I traced the issue back to the way the registers were being written when changing clock speed. Using _fastSPI of 20MHz in conjuction with pull request #131 (now merged) fixes the issues.


v1.6.1

Release 1.6.1

Codecov Report

Merging #146 (72eb62c) into main (04725c3) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #146   +/-   ##
=======================================
  Coverage   98.49%   98.49%
=======================================
  Files          27       27
  Lines        2124     2124
=======================================
  Hits         2092     2092
  Misses         32       32

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


Include debug mode for showing changes slurp will make to the database

We should have a debug option in this script that allows for the script to instead of just making the changes to slurm, instead prints what it would do instead.

Closed after realizing the slurm_helper_ldap_compare.py script should accomplish the same task.


apply itself for igo files

Is there anyway for gosublime to pretend that an igo file is a go file and apply itself?

What's the scope name of an igo file? You can find it by opening the Sublime Text console and running view.scope_name(0).

'text.plain '

Is that inside a igo file? I'd expect it to be using a custom syntax definition of some sort.
What's an igo file anyway?

https://github.com/rocketlaunchr/igo

If you or someone else created a syntax definition for it, I'd be willing to add a special-case if possible. But I don't think that'd be enough because it seems like it uses a different syntax that would fail when GoSublime uses the official go tools on it.


Make compatible with Jython 2.7.0

I'm going to be adding some new inheritance styles this weekend. When I do, I'll update the import statement to be compatible with Jython. I'll let you know when the new release is complete (it will be available via pip as well)

@gappleto97
Version 2.1.0 is out. I hope this jives with Jython 2.7!


Crash from CoUninitialize/OleUninitialize

I was trying to use this library from Qt application and there's a conflict between QWindows plugin that also initializes/uninitializes Ole (for QSystemTrayIcon). The result of the conflict is that CoUninitialize() is called twice and second time it raises an exception (which causes an application).
I don't have a very good solution except to provide a way not to call CoUninitialize() in destructor.

There is a separate issue where different users provide alternative solutions. As you mentioned, there is no clear solution, specially if you use the provided singleton. See #44 for more details.


how to place a call with asterisk

Hello guys!
Can some, please, clarify/help with workflow on the following script:
Let's assume I have RTP stream on a local device, and what I'm trying to accomplish is to place a call from asterisk (I've got sip identity with credentials) using drachtio-srf and use that RTP stream as an audio for the initiated call.
I'm assuming I should you UAC from srf instance, and I'm building local SDP for it but the call seems to be dropping
my test code (which is not working) is
let uac = srf.createUAC(`sip:${requstedPhone}@${asteriskHost}`, {
    noAck: true,
    headers: {
        From: `sip:${myAsteriskIdUser}@${asteriskHost}`,
        "User-Agent": "drachtio-srf",
    },
    auth: {
        username: myAsteriskIdUser,
        password: myAsteriskIdPass,
    },
}).then(async (obj) => {
    console.log(`received sdp offer ${obj.sdp} from B party`);
    // get local rtp stream meta
    let ip, port, pType;
    // SDP to send back to the peer
    let sdp =
        "v=0\r\n" +
        "o=sip2ab " + new Date().getTime() + " 1 IN IP4 <IP_ADDRESS>\r\n" +
        "s=-\r\n" +
        "t=0 0\r\n" +
        "m=audio " + port + " RTP/AVP " + pType + "\r\n" +
        "c=IN IP4 " + ip + "\r\n" +
        "a=rtpmap:" + pType + " opus/48000/2\r\n" +
        "a=fmtp:" + pType + " maxplaybackrate=48000;stereo=1\r\n";
    return obj.ack(sdp);
}).then((dialog) => {
    dialog.on("destroy", async () => {
        console.log("called party ended call");
    });
});

thank you in advance!

now I'm thinking I'm doing it wrong (obviously, as it's now working :-) )
as I wan't to be able to place a call to my phone number from asterisk using my sip id/credentials
so there in no such thing
sip:${requstedPhone}@${asteriskHost}

That code looks correct to me at first glance.  Are you saying it is working now?  If so please close the issue, it not please provide sip traces

Nope it's not working :(
I'll get you a sip trace for sure
meanwhile I've added some logging to my code, and getting that after I've got dialog in my hand and destroy handler is called
'CSeq: 24347 BYE\r\n' +
'Reason: Q.850;cause=44\r\n' +


[build] - Centralize around a single build system: CMake

          Since I Introduced this PR over six months ago, I've learned a lot more about the state of embedded development toolchains and build systems, primarily from my work managing such for the [Deluge Community Firmware](https://github.com/SynthstromAudible/DelugeFirmware) project. In that time, my overall outlook w.r.t. the management of dependencies (such as the CMSIS ones here) and build systems in the Daisy project has changed, and it boils down to a few key points:

Maintaining two build systems is a hassle and can lead to problems. Make and CMake ultimately accomplish the same thing, but CMake offers far more flexibility in terms of project organization and integration into other projects as a library. From what I understand the CMake system is newer, and is potentially a migration target, but (much like with the GPIO/Pin situation) currently in an awkward middle state.

Submodules are not the greatest way to do dependency management. CMake now has a very nice built-in dependency download and integration system called FetchContent that is well suited for problems like this: downloading weird out-of-source build components and integrating them without polluting the version control system. I've used this in a very similar situation for downloading and integrating AVR Dx devicepacks into a project's AVR-GCC toolchain, for example.

In the long run migrating the current build system to more idiomatic CMake is probably a good path forward, and will reduce a lot of issues with other kinds of integrations such as alternate toolchains (I've had a Clang-support PR waiting in the wings for a while now). However in the short term I think submodules are an acceptable stopgap solution for the dependency version problem, even if it requires an additional VCS step in the form of git submodule update.
I also kind of just want to see this PR merged so I can work on others, haha 😅
Originally posted by @stellar-aria in https://github.com/electro-smith/libDaisy/issues/582#issuecomment-1863483649

I like the idea of centralizing around a single build system a lot.
The primary concern I have is that it may appear more complex to the user for their application build files.
For example, a current minimal Makefile for an application may look like:
# Project Name
TARGET = Blink

# Sources
CPP_SOURCES = main.cpp

LIBDAISY_DIR = ../libs/libDaisy
DAISYSP_DIR = ../libs/DaisySP

# (optional) Includes FatFS source files within project.
#USE_FATFS = 1

# Core location, and generic Makefile.
SYSTEM_FILES_DIR = $(LIBDAISY_DIR)/core
include $(SYSTEM_FILES_DIR)/Makefile

A similarly simple CMakeLists.txt may be possible, but the ones I've had to write when experimenting with the build system end up being a bit longer:
project(Blink)
cmake_minimum_required(VERSION 3.19)

set(FIRMWARE_NAME Blink)

set(FIRMWARE_SOURCES
    src/main.cpp
)

# include libDaisy
set(LIBDAISY_DIR ../libs/libDaisy)
add_subdirectory(${LIBDAISY_DIR} libDaisy)

# include DaisySP
set(DAISYSP_DIR ../libs/DaisySP)
add_subdirectory(${DAISYSP_DIR} DaisySP)

# linker script
get_filename_component(LIBDAISY_DIR_ABS "${LIBDAISY_DIR}"
                       REALPATH BASE_DIR "${CMAKE_SOURCE_DIR}")
set(LINKER_SCRIPT ${LIBDAISY_DIR_ABS}/core/STM32H750IB_flash.lds)

# firmware binary image
add_executable(${FIRMWARE_NAME} ${FIRMWARE_SOURCES})

target_link_libraries(${FIRMWARE_NAME}
  PRIVATE
  daisy
  DaisySP
)

set_target_properties(${FIRMWARE_NAME} PROPERTIES
    CXX_STANDARD 17
    CXX_STANDARD_REQUIRED YES
    SUFFIX ".elf"
    LINK_DEPENDS ${LINKER_SCRIPT}
)

target_link_options(${FIRMWARE_NAME} PUBLIC
    -T ${LINKER_SCRIPT}
    -Wl,-Map=${FIRMWARE_NAME}.map,--cref
    -Wl,--check-sections
    -Wl,--unresolved-symbols=report-all
    -Wl,--warn-common
    -Wl,--warn-section-align
    -Wl,--print-memory-usage
)

add_custom_command(TARGET ${FIRMWARE_NAME} POST_BUILD
    COMMAND ${CMAKE_OBJCOPY}
    ARGS -O ihex
    -S ${FIRMWARE_NAME}.elf
    ${FIRMWARE_NAME}.hex
    BYPRODUCTS
    ${FIRMWARE_NAME}.hex
    COMMENT "Generating HEX image"
VERBATIM)

add_custom_command(TARGET ${FIRMWARE_NAME} POST_BUILD
    COMMAND ${CMAKE_OBJCOPY}
    ARGS -O binary
    -S ${FIRMWARE_NAME}.elf
    ${FIRMWARE_NAME}.bin
    BYPRODUCTS
    ${FIRMWARE_NAME}.bin
    COMMENT "Generating binary image"
VERBATIM)

There could be a similar way to the core/Makefile we import for the Make system that would work well for reducing/simplifying this.
It's also possible that a well commented template project (similar to what you might see when building a project with JUCE (e.g. # PUT YOUR PROJECT NAME HERE, etc. ) may provide an easy enough transition.
Definitely open to thoughts, as well as any other things that are missing, worth discussing!

yeah the core/Makefile style system is what I went with in my cmake-improvements branch:
cmake/DaisyProject.cmake:
set(DAISY_STORAGE flash CACHE STRING "Select the storage destination of the executable.")

if(DEFINED CUSTOM_LINKER_SCRIPT)
    set(LINKER_SCRIPT ${CUSTOM_LINKER_SCRIPT})
else()
    cmake_path(SET LINKER_SCRIPT NORMALIZE ${CMAKE_CURRENT_LIST_DIR}/../core/STM32H750IB_${DAISY_STORAGE}.lds)
endif()

add_executable(${FIRMWARE_NAME} ${FIRMWARE_SOURCES})

target_link_libraries(${FIRMWARE_NAME}
    PRIVATE
    daisy
    ${DAISYSP_LIB}
)

set_target_properties(${FIRMWARE_NAME} PROPERTIES
    CXX_STANDARD 17
    CXX_STANDARD_REQUIRED YES
    SUFFIX ".elf"
    LINK_DEPENDS ${LINKER_SCRIPT}
)

target_link_options(${FIRMWARE_NAME} PUBLIC
    LINKER:-T,${LINKER_SCRIPT}
    $<$<CONFIG:DEBUG>:LINKER:-Map=${FIRMWARE_NAME}.map>
    $<$<CONFIG:DEBUG>:LINKER:--cref>
    LINKER:--gc-sections
    LINKER:--check-sections
    LINKER:--unresolved-symbols=report-all
    LINKER:--warn-common
    $<$<CXX_COMPILER_ID:GNU>:LINKER:--warn-section-align>

    # Currently a GSoC project to port this to LLD
    $<$<CXX_COMPILER_ID:GNU>:LINKER:--print-memory-usage>
)

add_custom_command(TARGET ${FIRMWARE_NAME} POST_BUILD
    COMMAND ${CMAKE_OBJCOPY} -O ihex -S ${FIRMWARE_NAME}.elf ${FIRMWARE_NAME}.hex
    BYPRODUCTS ${FIRMWARE_NAME}.hex
    COMMENT "Generating HEX image"
    VERBATIM
)

option(DAISY_GENERATE_BIN "Sets whether or not to generate a raw binary image using objcopy (warning this is a very large file, as it is a representation of the *full memory space*.)")

if(DAISY_GENERATE_BIN)
    add_custom_command(TARGET ${FIRMWARE_NAME} POST_BUILD
        COMMAND ${CMAKE_OBJCOPY} -O binary -S ${FIRMWARE_NAME}.elf ${FIRMWARE_NAME}.bin
        BYPRODUCTS ${FIRMWARE_NAME}.bin
        COMMENT "Generating binary image"
        VERBATIM
    )
endif(DAISY_GENERATE_BIN)

and then subsequent projects can just use this like so:
# Only required if not a subdir of another project
#cmake_minimum_required(VERSION 3.20)
#project(PROJECT_NAME_HERE)

set(FIRMWARE_NAME examples_Encoder)
set(FIRMWARE_SOURCES Encoder.cpp)
include(DaisyProject)


Fix #2068 Add support for java.time.Duration

Add static method for converting a java.time.Duration into an Ehcache
Duration
Add methods on the Expirations utility taking java.time.Duration
parameters

This will not get merged, going with the approach in #2166


Semver debug

Fixes #122

+1 thanks for changing this, makes output much apb much cleaner.
[dwhatley@precision-t apb]$ ./apb registry add
WARN Didn't find config file, creating one.
Getting specs for registry: [docker]
INFO == REGISTRY CX ==
INFO Name: docker
INFO Type: dockerhub
INFO Url: docker.io
[...]
INFO adapter::imageToSpec -> Image docker.io/ansibleplaybookbundle/mediawiki-apb:latest runtime is 2
INFO adapter::imageToSpec -> Image docker.io/ansibleplaybookbundle/dynamic-apb:latest runtime is 2
INFO Validating specs...
WARN Spec [ rhpam-apb ] failed validation for the following reason: [ Spec [rhpam-apb] failed version validation ]. It will not be made available.
WARN Spec [ import-vm-disk-apb ] failed validation for the following reason: [ Spec [import-vm-disk-apb] failed version validation ]. It will not be made available.
WARN Spec [ mongodb-apb ] failed validation for the following reason: [ Spec [mongodb-apb] failed version validation ]. It will not be made available.
WARN 3 specs of 43 discovered specs failed validation from registry: docker.io
INFO Registry docker has 40 bundles available from 72 images scanned
 BUNDLE                    IMAGE                                                                   REGISTRY
 --------------------- -+- ------------------------------------------------------------------- -+- --------
 nginx-apb              |  docker.io/ansibleplaybookbundle/nginx-apb:latest                     |  docker
 windowsvm-apb          |  docker.io/ansibleplaybookbundle/windows-apb:latest                   |  docker
[...]


Send Accept request header to support content negotiation

Would be great to set Accept header value from command line (currently it is /) to support content negotiation.

Merge request has #13 been created

After some thought I'm going to remove this option in 3.0.0 and instead add a -h / --header option to allow overriding any header.

Fine for me, thanks!


Release scripts

Lacking documentation but already ready for a first review I'd say.
This PR not only adds scripts to prepare artifacts for release but also contain a few other additions/improvements (contained in their respective commits):

Proper use of bin and lib directories (this one affects documentation and deployment scripts)
The test script now understands the feature flags and passes them on to the build script (not the most sophisticated solution as these flags need to be updated twice if changed)
OpenBLAS compatibility is improved to support a wider range of x86_64 processors). The max threads property is taken from the machine where the release is created (so atm it's set to 112 cores). This is open for debate if we should provide a fixed value there and what this value should be. According to the OpenBLAS documentation this setting affects internal structures.

The full pipeline is untested as I copy the created files back to my computer for signing (don't have gpg agent forwarding set up).
For the final merge some things like DAPHNE_REPO_URL need to be changed of course.
At them moment I use these scripts like this:

Create the artifacts: time ./release.sh --version 0.1-testing-rc04 --githash `git rev-parse --short HEAD`
Copy back to my machine: rsync -havP <hostname>:./code/daphne-eu/daphne/build/daphne-0.1*rc04*.* .
Signing and checksumming: ~/code/daphne/prototype/release.sh --artifact ./daphne-0.1-testing-rc04-bin.tgz --gpgkey B28F8F4D

The release.sh script will call pack.sh which will call build.sh and test.sh. Only if testing completes successfully, the artifact, a gzipped tar archive (format open for discussion) is created. The command after --githash fetches the git hash of the current commit. The script checks out this git hash and restores the current commit after successful completion. This is a bit of a shortcoming as you have to issue a manual git checkout - if the script fails and terminates early.
Note to self: don't write all the documentation in the PR description :-P

Thanks @corepointer! Overall, it looks very good to me. Not only the release-related scripts, but also the other improvements.
Things we need to finalize before the merge:

Currently, the built executables and libraries reside in different locations in a build from source (/build/...) and in a release (/bin/... and /lib/...). At least the locations of the executables are used many times thorughout the documentation, deployment scripts, and source code. I highly recommend using the same locations in both cases. I personally like the /bin/ and /lib/ approach. Why don't we adopt that generally? I think we would just need to (1) adapt the CMakeLists.txts, and (2) the --clean in build.sh.
Depending on how we resolve the first point, we need to update all occurrences of the old paths thoughout the code base.

Optional improvements:

Likewise, the user configuration file UserConfig.json resides in different locations. I recommend generally moving it from /src/api/cli/UserConfig.json to /UserConfig.json (even in the normal repo).
pack.sh and release.sh both have a variable unknown_options, but it doesn't seem to have an effect.

Please let me know if/which of those points you'd like to address, or if I shall try it.

Thx for the review @pdamme !
Writing this message while the test suite runs before I push changes ;-)

Adjusted bin/lib output. Also redirected the test executables to the bin directory btw.
The unknown_options thing is a copy&paste error from build.sh. I pulled over the printing of these from build.sh now.

Suggestions:

For UserConfig.json I recommend a conf directory. Or even etc? :-D
We could move all the shell scripts (it has grown to quite a number) to a directory as well while we're at it. Maybe even to bin (I know, they're not binary but still ;-) )
What about an env.sh that sets up PATH, LD_LIBRARY_PATH and DAPHNE_ROOT (and potentially other stuff) ?
In the style of SystemDS builtin functions, we could wrap our algorithms in a function body and use a default import from DAPHNE_ROOT/scripts/{algorithms,builtins}. That would boost usability imho.
At them moment I adjusted the output of libs and executables to what we need. In the long run we should make proper use of cmake install and package features. But that is more a v0.2 thing ;-)

Sounds very good. In general, I would not over-engineer things right now (we want to be done at some point...). We will see what we really need later. So:

For UserConfig.json, I'm fine with both individual file or conf-directory (I just don't know what else we will ever put there...).
Moving shell scripts: IMHO: simple in theory, might need adjustments in various places (missing them could cause errors), no clear benefit, and not directly related to release automation. So I suggest leaving that for later.
env.sh: IMHO also not required right now :)
Wrapping DaphneDSL scripts in functions for (re)usability: definitely! But not now, please. Preparing a simple-to-use library of high-level ML and other primitives in DaphneDSL is on our agenda, but it's a task of its own and should be done thoroughly.
Thanks and agreeing :)

Finally, I think the release scripts are good as they are (with the points above addressed), for now. We can still improve them for the next releases.

Thanks for finalizing it. Good point about the config dir, we can do that after the release :) .


(actions): add unit test

Based on https://github.com/operator-framework/catalogd/pull/29#pullrequestreview-1380089352 && https://github.com/operator-framework/catalogd/pull/29#discussion_r1163317618 are we okay with just adding the unit test workflow or should we supersede this PR with a new PR that implements the matrix style workflow?

My opinion is that we should go ahead and add the unit test action right now. Once #34 is in we'll be in a position to write some test cases for the CatalogSource reconciler that should be useful even when we're making the switch for the child resources/moving to aggregated api etc etc. Also feels like the right time to get at least the initial set of tests written down. So we can add the action, and then discuss the "matrix style tests"
I'll also need more clarification about the meaning of "matrix style tests", unless that means "rename sanity.yaml to test.yaml and add the unit test job to that file", in which I'm happy to do that in this PR


term request: Soil Nitrate

Hello the Bioscales project is in need of the term:
Soil Nitrate

We will measure this on both bulk soil and porewater samples. I will be expressed for soils a mg NO3 per kilogram of soil (dry weight), for porewater as mg NO3 per liter


Link back to Jira issue in comments

I would like to add an extra comment in DevOps with an custom text, including a link to the original Jira issue. Is this possible?

Or via the Hyperlink Type: https://docs.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference?view=azure-devops#hyperlink-type

@jerone  Thanks for the suggestion! We will look into this. At this time we don't support that unfortunately but you can either add a link in the comment which will be migrated or a custom field containing the jira link with custom text.

We are going to migrate Jira this sprint, so I started to look into creating an extra comment with a ping back to the Jira isue, but I couldn't find the code to create the Jira url. I don't want to manually add a comment to 700 issues :smile:


Fix race condition in test case test_compile_details (#4033)

Pull request opened by the merge tool on behalf of #4033

Pull request rejected by merge tool. The tests for this branch did not succeed.

Merged into branches iso5 in 29c595da550b20bd8ed87433052e9549d6778999


using for loop instead of forEach in element classlists

using a forEach loop does not allow us to return early from iterating all the elements in the classlist. We need to use the good old for loop to do so. This bug broke all css blocking.
The prepare script allows us to pull from github as a npm dep without having to commit the bundled result.

Thanks! @IMFIL Could you resolve the conflict so I can merge this?

Manually picked in master branch


post the compiled extension

Can you attach the compiled package to releases?
Currently
gyp ERR! node -v v16.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     <https://github.com/nodejs/node-gyp/issues>
Build failed with error code: 7

Sorry, main source files of NodeJS old but dist folder latest compiled code
But whatsapp change self code soo our extention code not worked
Don't ask for countinue this repo


⚠ PrivateHD has degraded performance

In 822d2d7, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1971 ms

Resolved: PrivateHD performance has improved in af3fe93.


Create FAQ page

Task Description
Create FAQ page based on the wireframes
Technical Considerations
Use TailwindCSS, follow accessibility rules, and semantic HTML. Make it responsive!
Additional Considerations

Completed!


Ensure native notebooks can be used without Python or Python extension

For #1074
Separate test where Python extension is not installed.

Need to fix the failing test.


Can't search

Hey,
I am trying to search but I can't find any course.

Udemy changed their videos. They are DRM now. Very doubtful there is anyway now to download them.


PojoQueryBuilderImpl wrapQueries

In many of the methods for building queries for POJOs there is a check to see if wrapQueries is set to true before it prefixes path information, creates container queries, etc.  ThepojoPropertyPath() method:
https://github.com/marklogic/java-client-api/blob/develop/src/main/java/com/marklogic/client/impl/PojoQueryBuilderImpl.java#L53
does not do a similar check.  Would something like this:
    private StructuredQueryBuilder.PathIndex pojoPropertyPath(String pojoProperty) {
        if (wrapQueries) {
            return pathIndex(classWrapper + "/" + pojoProperty);
        } else {
            return pathIndex("/" + pojoProperty);
        }
    }

be more appropriate to honor that wrapQueries state, or are there things that would break or other reasons it should not be implemented this way?

Perhaps there's something that needs to be done here, but I'll be surprised if that's it.  The wrapQueries check is only in effect after you've called containerQueryBuilder (because you want to do the equivalent of an cts:element-query in XQuery).
Any chance you could share the query you're doing and the scenario that's not working?  I can create one, but it would be easier if we're looking at the same thing.

Let me clarify further that the expected path range indexes are the ones you'll see from using the annotation @PathIndexProprty and running GenerateIndexConfig.  In all cases the path will be classWrapper/pojoProperty because that's how the data is in the doc (every POJO property is nested in a class wrapper).  So classWrapper is not optional like wrapQueries is.
Perhaps all you need to do is add the annotation, run GenerateIndexConfig and see what the expected path range index is?

It wasn't necessarily a matter of something "not working", exactly.  I think I see where I have not thought this through fully.  We "extended" the POJO repository so we could do some custom settings to the object mapper (one of which was to not have the class wrapper) for some interoperability issues we were having between some Node.js stuff and Java stuff.  In that we instantiate an extension of PojoQueryBuilderImpl (yeah, I know) that sets wrapQueries to false and has a pojoPropertyPath method like that above so it doesn't prefix the path.  We just put documents in a "Person" collection as opposed to a "com.bubba.Person" collection, and the JSON document is "simple" JSON without the wrappers.
If we were doing it "right" we wouldn't "see" the PojoQueryBuilderImpl.class at all and setting the wrapQueries to false wouldn't even be an option.
Your suggesting on running GenerateIndexConfig is probably a good one so I can better understand how it all works.  I have never used the containerQueryBuilder before so I should look more into that.  The more I understand how everything "should" work the more "extensions" I can get rid of.  This sounds like more I need to learn instead of you updating something at the moment.
Maybe I have more a question of "what are the downsides of not having the classWrapper prefix on everything, and if there are no major downsides is it worth allowing configuring a PojoRepository such that things are not wrapped?"  We have been doing it like that for the last couple years without issue but we don't have 100s of Java/MarkLogic apps so we are probably just lucky.  I can see how having a "com.bubba.Person" and "com.lubba.Person" might lead to some issues since they both are treated as "Person" with our "hacks".
Thanks for your time, by the way, Sam.

Given these classes
`package lds.stack.examples.marklogic.model;
import com.marklogic.client.pojo.annotation.Id;
import com.marklogic.client.pojo.annotation.PathIndexProperty;
import java.util.List;
import java.util.UUID;
public class Event {
@Id
public String id;
@PathIndexProperty(scalarType = PathIndexProperty.ScalarType.STRING)
public String name;
public List rooms;
public Event() {
    this.id = UUID.randomUUID().toString();
}

public Event(String name, List<Room> rooms) {
    this();
    this.name = name;
    this.rooms = rooms;
}

public String getName() {
    return name;
}

public void setName(String name) {
    this.name = name;
}

public List<Room> getRooms() {
    return rooms;
}

public void setRooms(List<Room> rooms) {
    this.rooms = rooms;
}

}
`
package lds.stack.examples.marklogic.model;
public class Room {
public String name;
public Type type;
public Room() {
}

public Room(String name, Type type) {
    this.name = name;
    this.type = type;
}

public String getName() {
    return name;
}

public void setName(String name) {
    this.name = name;
}

public Type getType() {
    return type;
}

public void setType(Type type) {
    this.type = type;
}

}
`
`
package lds.stack.examples.marklogic.model;
import com.marklogic.client.pojo.annotation.PathIndexProperty;
public class Type {
@PathIndexProperty(scalarType = PathIndexProperty.ScalarType.STRING)
public String name;
public Type() {
}

public Type(String name) {
    this.name = name;
}

public String getName() {
    return name;
}

public void setName(String name) {
    this.name = name;
}

}
`
I get the following indexes generated:
 {       "path-expression" : "lds.stack.examples.marklogic.model.Event/name",       "scalar-type" : "string",       "collation" : "http://marklogic.com/collation/",       "range-value-positions" : "false",       "invalid-values" : "ignore"     },     {       "path-expression" : "lds.stack.examples.marklogic.model.Type/name",       "scalar-type" : "string",       "collation" : "http://marklogic.com/collation/",       "range-value-positions" : "false",       "invalid-values" : "ignore"     }
I was trying to use containerQueryBuilder() to do a range query on the Type.name, is that possible?  It was getting choked up on the fact that rooms was a java.util.List.  Maybe I did it wrong?  Is it possible if my rooms was just a room:
qb.containerQueryBuilder("room", Room.class).containerQueryBuilder("type", Type.class)
...or is the only way to use qb.range(qb.pathIndex(....))

I don't see a way to do that.
I tried this:
PojoQueryBuilder<Event> qb = eventRepo.getQueryBuilder();
PojoQueryBuilder<Room> roomQueryBuilder = qb.containerQueryBuilder("rooms", Room.class);
PojoQueryBuilder<ArrayList> typeQueryBuilder = roomQueryBuilder.containerQueryBuilder("type", ArrayList.class);
PojoQueryBuilder<Type> typeQueryBuilder = roomQueryBuilder.containerQueryBuilder("type", Type.class);

And I get the error:
Exception in thread "main" java.lang.IllegalArgumentException: property type not found, getType not found, and setType not found in class java.util.List
        at com.marklogic.client.impl.PojoQueryBuilderImpl.getType(PojoQueryBuilderImpl.java:319)
        at com.marklogic.client.impl.PojoQueryBuilderImpl.containerQueryBuilder(PojoQueryBuilderImpl.java:70)
        at LdsPojos.main(LdsPojos.java:25)

Because, of course, ArrayList doesn't have a getType method.  But it seems reasonable to me that we could support a Collection of Pojos.  Would it be helpful if we file an RFE for that?
Again, in the short-term, the work-around is to use JacksonDatabindHandle that should provide a more open-ended feature set.

You could probably do a term query or a word query, however, using roomQueryBuilder.  Perhaps you could even get away with a value query instead of a range query.  Should I see if I could make that work?  Or is that not going to meet your needs?

I don't know how much this helps, but here's how to do it using JacksonDatabindHandle:
// do this before you create your DatabaseClient
DatabaseClientFactory.getHandleRegistry().register( JacksonDatabindHandle.newFactory(LdsEvent.class) );
...

ArrayList<Room> rooms = new ArrayList<>();
rooms.add(new Room("room_a", new Type("type_a")));
Event event = new Event("event_a", rooms);
client.newDocumentManager().writeAs(event.id, event);

StructuredQueryBuilder qb = new StructuredQueryBuilder();
StructuredQueryDefinition query = qb.containerQuery(qb.jsonProperty("rooms"),
  qb.range(qb.pathIndex("type/name"), "xs:string", "http://marklogic.com/collation/", Operator.EQ, "type_a"));
DocumentPage docs = client.newDocumentManager().search(query, 1);
for ( DocumentRecord doc : docs ) {
  Event matchingEvent = doc.getContentAs(Event.class);
  System.out.println(matchingEvent);
}

So the registration of the class allows the getContentAs to work? Am I understanding that correctly?

Most POJOs I have designed have some sort of collection in it, that is just how it has worked out.  As I have never used the containerQueryBuilder() function I haven't had an issue, but I can see how supporting more complicated JSON models would be useful.  Then again, if people aren't complaining it may not be worth it, and I am fine without it at the moment because most of the queries I do are value queries and I can do container queries and value queries and that mostly works fine.
What would be most useful for us is a little more configurability on how the JSON is stored in the database.  For us, just the ability to "turn off" the class wrappers was all we really needed, but we kind of had to "hack" to get it to work.  Being able to get at the object mapper inside the PojoRepository and having that used throughout, plus the ability to turn off "wrapQueries" is what we need.  Maybe in general this exposing more configuration would expose a bunch of problems and that might be why it might not be an option.  That is the main question I wanted to ask, the "wrapQueries" one I started with was just a step towards this.

Thanks, @malteseduck.  I'll create the RFE for supporting collections with containerQueryBuilder.  I think it's a good enhancement.
By "wrapQueries" what I think you mean is turn off JsonTypeInfo.As.WRAPPER_OBJECT.  In PojoQueryBuilderImpl "wrapQueries" actually refers to container queries, so it's not related to the persisted class wrappers.
For testing purposes, you can access the ObjectMapper using
((PojoRepositoryImpl) pojoRepository).getObjectMapper()

we didn't expose that because it starts you down a path that could easily break things.  For example: removing the persisted class wrappers might break things.  We need those if we're going to do any kind of simple containerQueries (containerQueryBuilder) or range queries on nested types.  You've been fine without it since you haven't done containerQueries or range queries on nested types.
Your scenario is the perfect example where you have two nested classes with the property "name".  We use the class wraper to create path range indexes that are class-specific, so you can query Type/name or Room/name not just any "name" property at any level.  Of course, if you always nest only one way (no Room or Type objects inside any other objects), you could create full-path range indexes like /rooms/type/name, but we didn't see a way to fit that type of path range index into PojoQueryBuilder as it is now, so we stuck with container queries and versitile path indexes like Type/name.
In any case, when you ask the question of whether or not you can tweak the persisted structure, you're headed down a path that's better served by JacksonDatabindHandle in combination with JSONDocumentManager and StructuredQueryBuidler than by PojoRepository.  Does that make sense?

Sorry, I missed one of your questions:

So the registration of the class allows the writeAs/getContentAs to work? Am I understanding that correctly?

Yes, you understood that correctly, when it comes to POJOs.  There are many types pre-registered for you (byte[], Document, File, InputSource, InputStream, JsonNode, JsonParser, Reader, Source, String, XMLEventReader, XMLStreamReader), see HandleFactoryRegistryImpl.registerDefaults.  But to register your own POJOs you'll need to pass the return value of JacksonDatabindHandle or JAXBHandle newFactory methods to DatabaseClientFactory.getHandleRegistry().register().

Your explanation makes sense, I can see where opening things up could break things or cause a lot of support issues with people breaking themselves.  We had used the ((PojoRepositoryImpl) pojoRepository).getObjectMapper() to update the wrap, and had created some classes that we used to work around alot of the class wrappers and such in range queries, etc.  I was trying to take advantage of all the good things you had with PojoRepository and PojoQueryBuilder but we may have ended up with something more complicated than just using the JacksonDatabindHandle and such as you suggest.  I will look more into using that approach.  Thanks


Update Package.swift to use upToNextMajor

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] 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)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@kevinlind can we just merge this into main directly since there are unreleased changes on dev?

@sbenedicadb Yes, good catch. Let me rebase my changes from main.

@sbenedicadb As the rebase changes the commit history from what is in this PR, I'll need to close and create a new one.


Fix potential infinite loop condition in test suite

I was doing some testing with js-xlsx's test suite and ran into a test that was hanging.  The problem was cmparr()'s for-loop condition.  Switching from != to < fixed the hung test and caused it to error correctly. Thought I'd drop the fix here in-case it's useful to js-xlsx.

Good catch! Out of curiosity, what platform triggered the error?

I made some custom changes to the js-xlsx test suite in relation to a TypeScript project I was working that has some special excel import/export requirements.
The issue doesn't occur in a clean clone of the js-xlsx repository, just related to some custom changes I made that happened to uncover this.


Changing relative depth estimation model

Hi! Is it possible to switch models that estimate relative depth. It is known, that currently zoedepth uses midas. But I would like to use other models that also evaluate depth in relative aspect, such as Marigold. How to do it?

@Renat2001 Did you solve this ? if yes, how ?

Actually, no, I did not. But I found an interesting workaround: there is a model that predicts focus length and other distortion parameters so that I can use it to recover refined point cloud from MiDaS (or Marigold) relative depth output.

@Renat2001 Can I use it to recover relative depth maps for my rgb images ?


feat: add snowflake oauth access token support

https://docs.snowflake.com/en/developer-guide/python-connector/python-connector-connect#connecting-with-oauth

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ModSecurity-Nginx compilation issue

After compilation of modsecurity, I downloaded nginx tar file and compiled it into ModSecurity-Nginx folder as suggested in this documentation. I'm using this command ./configure --add-module=/path/your/modsecurity-for-nginx and its giving me an error saying
" checking for modsecurity library in ... not found ./configure error : ngx_http_modsecurity_module requires the MODSECURITY LIBRARY, but we cannot find modsecurity there."  Am i missing something here?

Hi @vishaalgc
Did you had the chance to get ModSecurity installed before tried to compile the nginx connector?


Remove unnecessary plugin for next versions in the package build

Description

Remove unnecessary plugin for next versions in the package build
Fix the building of packages with branches with /

Issues Resolved

https://github.com/wazuh/wazuh-dashboard/issues/401

Screenshot
ARM deb

Test
ARM
DEB
https://github.com/wazuh/wazuh-dashboard/actions/runs/12484705833
RPM
https://github.com/wazuh/wazuh-dashboard/actions/runs/12484708968
x86
DEB
https://github.com/wazuh/wazuh-dashboard/actions/runs/12484704855
RPM
https://github.com/wazuh/wazuh-dashboard/actions/runs/12484707657
Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[x] Commits are signed per the DCO using --signoff

Test 2024/12/26 🟢
OS: centos8
Vagrantfile
Vagrant.configure("2") do |config|
  if ENV["VAGRANT_WSL"]
    config.ssh.insert_key = false
  end
  config.vm.box = "centos/8"
  config.vm.network "private_network", ip: "<IP_ADDRESS>"
  config.vm.provider "virtualbox" do |pmv|
    pmv.memory = 4096
    pmv.cpus = 2
    pmv.name = "Centos8"
  end
  ssh_pub_source = ENV["WZ_SSH_PUB_KEY_PATH"]
  if ssh_pub_source
    config.vm.provision "file", source: ssh_pub_source, destination: "~/.ssh/me.pub"
    config.vm.provision "shell", inline: <<-SHELL
        cat /home/vagrant/.ssh/me.pub >> /home/vagrant/.ssh/authorized_keys
        mkdir -p /root/.ssh/
        cat /home/vagrant/.ssh/me.pub >> /root/.ssh/authorized_keys
      SHELL
  end
  # https://stackoverflow.com/a/71309215
  config.vm.provision "shell", inline: <<-SHELL
      cd /etc/yum.repos.d/
      sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*
      sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*
      sudo yum upgrade -y
    SHELL
end

Wazuh indexer: Build [ "deb", "rpm" ] Wazuh Indexer on [ "x64" ]
Wazuh dashboard: Build [ "rpm" ] on [ "x86_64" ]
[root@vbox vagrant]# systemctl status wazuh-indexer
● wazuh-indexer.service - wazuh-indexer
   Loaded: loaded (/usr/lib/systemd/system/wazuh-indexer.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2024-12-26 18:23:07 UTC; 13min ago
     Docs: https://documentation.wazuh.com
 Main PID: 3527 (java)
    Tasks: 84 (limit: 24920)
   Memory: 1.3G
   CGroup: /system.slice/wazuh-indexer.service
           └─3527 /usr/share/wazuh-indexer/jdk/bin/java -Xshare:auto -Dopensearch.networkaddress.cache.ttl=60 -Dopensearch.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.a>

Dec 26 18:22:50 vbox systemd-entrypoint[3527]: WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.OpenSearch (file:/usr/share/wazuh-indexer/lib/opensearch-2.18.0.jar)
Dec 26 18:22:50 vbox systemd-entrypoint[3527]: WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.OpenSearch
Dec 26 18:22:50 vbox systemd-entrypoint[3527]: WARNING: System::setSecurityManager will be removed in a future release
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: Dec 26, 2024 6:22:51 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: WARNING: COMPAT locale provider will be removed in a future release
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: WARNING: A terminally deprecated method in java.lang.System has been called
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.Security (file:/usr/share/wazuh-indexer/lib/opensearch-2.18.0.jar)
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.Security
Dec 26 18:22:51 vbox systemd-entrypoint[3527]: WARNING: System::setSecurityManager will be removed in a future release
Dec 26 18:23:07 vbox systemd[1]: Started wazuh-indexer.
[root@vbox vagrant]# systemctl status wazuh-dashboard
● wazuh-dashboard.service - wazuh-dashboard
   Loaded: loaded (/etc/systemd/system/wazuh-dashboard.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2024-12-26 18:36:49 UTC; 16s ago
 Main PID: 4049 (node)
    Tasks: 11 (limit: 24920)
   Memory: 241.9M
   CGroup: /system.slice/wazuh-dashboard.service
           └─4049 /usr/share/wazuh-dashboard/node/bin/node /usr/share/wazuh-dashboard/src/cli/dist

Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["error","opensearch","data"],"pid":4049,"message":"[version_conflict_engine_exception]:>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","index-pattern:alerts"],"pid":4049,"messa>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:metaFields"],"pid":4049,"message>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:metaFields"],"pid":4049,"message>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:timeline:max_buckets"],"pid":404>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:timeline:max_buckets"],"pid":404>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:timepicker:timeDefaults"],"pid":>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","plugins","wazuhCore","initialization","setting:timepicker:timeDefaults"],"pid":>
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["listening","info"],"pid":4049,"message":"Server running at https://<IP_ADDRESS>:443"}
Dec 26 18:36:56 vbox opensearch-dashboards[4049]: {"type":"log","@timestamp":"2024-12-26T18:36:56Z","tags":["info","http","server","OpenSearchDashboards"],"pid":4049,"message":"http server runnin>


Build agent script block does not run properly

The whole code block is at Configure your build agent, and in the part where the python unit tests are run the script runs two different lines, resulting in a permissions issue. I would recommend changing it to how it looks further below at Test library code using Databricks Connect or change the newline marker "|" to ">" so it runs the script as just one line.

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

ID: 56b86f59-7a22-90c6-9aa6-652b85975612
Version Independent ID: b333ab7b-847b-7129-9b62-4b9b934747d7
Content: Continuous integration and delivery on Azure Databricks using Azure DevOps - Azure Databricks
Content Source: databricks/dev-tools/ci-cd/ci-cd-azure-devops.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@mssaperla / @leifbro Could you please validate customer feedback and enhance document as appropriate? Thank you.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7170) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close

#please-close


Exclude unused platform-specific tkdnd files in pyinstaller hook

The tkdnd folder contains pre-compiled files for Windows, Linux and macOS. But TkinterDnD.py only loads one of them according to current platform. I modified the pyinstaller hook to exclude the unused platform-specific tkdnd files so the bundled app's size can be slightly reduced.

Afaik this can be done for the setup.cfg also (PyPi build)

Sorry for the long period since your submission of this PR.
Thanks for the improvement suggestion. I have reviewed this and determined that it works as expected.


Error while running the FP Nokia SR-Linux README example

I'm trying to run the example provided in the README file with a Nokia SRL, with the following minor changes to  topologies/kne/nokia_srl.textproto file

Added type line below name "type: NOKIA_SRL"
Changed image file location to: "ghcr.io/nokia/srlinux:latest"

go test -v feature/system/tests/*.go -kne-config $PWD/topologies/kne/testbed.kne.yml -testbed $PWD/topologies/dut.testbed
*** Reserving the testbed...
F0726 17:17:17.165291 2470725 ondatra.go:53] error executing command /home/opetre/go/bin/kne_cli topology reset /home/opetre/featureprofiles/topologies/kne/nokia_srl.textproto dut --push: time="2022-07-26T17:17:17Z" level=info msg="Creating manager for: nokia-srl"
time="2022-07-26T17:17:17Z" level=info msg="Trying in-cluster configuration"
time="2022-07-26T17:17:17Z" level=info msg="Falling back to kubeconfig: "/home/opetre/.kube/config""
time="2022-07-26T17:17:17Z" level=info msg="Adding Node: dut:NOKIA:NOKIA_SRL"
Error: node dut is not resettable and --skip not set
: exit status 1
FAIL    command-line-arguments  0.417s
FAIL

Hi @octpetre
It seems like ondatra framework is expecting to reset the dut but the dut does not allow this. As the message suggest, you can set the --skip flag to the function. I've done so by editing the file in my go/mod, usually found in<EMAIL_ADDRESS>(be mindful that you may not have the same version of ondatra as I do, usually the latest one pulled should be OK).
You can then change the reset config Line to include "--skip". Example post-change below.
_, err := kneCmdFn(d.cfg, "topology", "reset", d.cfg.TopoPath, d.Name(), "--push", "--skip")
That being said, you might still get stuck running the test around this part:
go test -v feature/system/tests/*.go -kne-config /home/user/openconfig/featureprofiles/topologies/kne/testbed.kne.yml -testbed /home/user/openconfig/featureprofiles/topologies/dut.testbed

*** Reserving the testbed...

********************************************************************************

  Testbed Reservation Complete
  ID: 4e5e8447-2256-4b92-a0b4-1f7e4eebfd87

    dut:              dut

********************************************************************************

=== RUN   TestMotdBanner
    banner_test.go:31: Need working implementation to validate against
--- SKIP: TestMotdBanner (0.00s)
=== RUN   TestLoginBanner
    banner_test.go:82: Need working implementation to validate against
--- SKIP: TestLoginBanner (0.00s)
=== RUN   TestHostname
=== RUN   TestHostname/15_Letters
<Stuck here>

Hi @Hobbydos
What would be the SRL Cli command(s) to reset the config manually?

@bortok  I think you might be looking for load factory / commit now

Hi @bortok,
I've raised PR-182/KNE to implement the resetter in SRL.

Hello all,
I tried @Hobbydos suggested workaround with changing the ondatra knebind.go file and also the kne version from the PR-182/KNE source forked repo. In both cases the ondatra reservation did go through, however the test got stuck at the exact "TestHostname/15_Letters" function.
Further troubleshooting...the config on the cli before and after reset is the same.
The issue also happens when running these OTG tests feature/interface/staticarp/otg_tests/static_arp_test and feature/bgp/policybase/otg_tests/route_installation_test/ as they get stuck whenever oc DUT interaction phase.

SR Linux Resetter has been added in https://github.com/openconfig/kne/pull/187
so this issue is hopefully resolved


Deep dive teleprompter rename

I keep getting confused when I search for information on optimizers and can't find it since some sections are still named teleprompters. I just went ahead and refactored the deep dive section. I hope you don't mind!

Hi @tom-doerr , thanks for this change! This has been long overdue but we will also need to do this refactoring within the repository to align with Optimizers overall. @okhat is this a good time to make this transition?

If it's basically just renaming teleprompt to optimize and adding deprecation warnings if someone continues to use teleprompt I could try to add it to the PR

Adding deprecation warnings while keeping it functional seems straightforward.
dspy/teleprompt/teleprompt.py would become:
import warnings
warnings.warn(
    "The 'teleprompt' module has been renamed to 'optimize'. Please update your imports.",
    DeprecationWarning
)
from dspy.optimize.optimize import *

Would be happy to help out with refactoring.

Ah okay, LabeledFewShot is probably also not an optimizer


In MSSQL: Incorrect syntax near the keyword 'rule'.

In MSSQL Rule is a reserved keyword.
If there is a column with a reserved name it is necessary that the sql use square brackets to make it explicit that you mean the object named "rule" it.
Use [rule] instead of rule.

There's various ways to tell Hibernate to use quoted identifiers, the easiest one being to quote the column name using backticks in the @Column annotation.
I suggest you check the Hibernate documentation.


diffusive compute pathway uses old DA vars

The dataframes usgs_df_sub and lastobs_df_sub are computed with the same function as the MC pathways, but the actual call differs. That may be fine, but if not, then...
here: https://github.com/NOAA-OWP/t-route/blob/70e32677509b3e767e1eeeb48be9bb1a76b15a41/src/python_routing_v02/troute/routing/compute.py#L722
... consider adding something like the following:
np.array(da_positions_list, dtype="int32"),
lastobs_df_sub.get("last_obs_discharge", pd.Series(index=lastobs_df_sub.index, name="Null")).values.astype("float32"),
lastobs_df_sub.get("time_since_lastobs", pd.Series(index=lastobs_df_sub.index, name="Null")).values.astype("float32"),

Should be addressed by #358
Additional work will be needed to actually use the DA values somehow.


Multiple schedule settings for a JDBC river in feeder mode

Hello,
I would like to be able to specify multiple schedule settings (per SQL statement, per index) within single feeder process.
Currently I can only specify a single schedule setting for the whole feeder process:

{
"elasticsearch" {///es cluster settings},
"schedule":"///schedule settings",
"type": "jdbc",
"jdbc": [{
///first set of queries
},{
///second set of queries
}]
}

It would be much more convenient to start single feeder process doing all things instead of multiple.

I'm hitting this limitation too! Multiple rivers seems like an ok solution. What confused me for some time is that the schedule property works within a single jdbc object but only works on the root when multiple jdbc objects are defined.


Support for offline dictionaries or instant definitions

Is your feature request related to a problem? Please describe.
Hello! I'm exploring Lute coming from Vocab Tracker, and one thing I miss is instant translations/definitions.
As I understand it, in Lute, there are no pre-filled definitions, and you have to copy-paste your own definitions from an external dictionary. In my use case, I simply determine how well I know a word's meaning, and assign it a level. I do not intend to bother with assigning data to each word within Lute itself.
However, when you click on a word, loading an online dictionary for each new word can take a second or two (on my connection, at least), and that's enough to break my immersion when reading.
Describe the solution you'd like
Allow installing an offline .tsv dictionary (such as the ones used by LinguaCafe), to provide instant definitions for selected words, while in the meantime also loading the embedded online dictionary (if so configured).
Describe alternatives you've considered
I'm not sure what solution Vocab Tracker uses to be so efficient, but that! I think it uses some translator service, but whatever it is, it loads meanings instantly when selecting words or even phrases.
Additional context
That's all! Thank you!

Hi @sabretou , thanks very much for the issue and your notes.  This has been requested before, but your detail helps, so I've copied the information here to the older issue (#228), and I'll close this one as a duplicate.  Cheers!

Hi @sabretou - could you give some detail for the questions I asked in #228?  Cheers!


Enhancement: allow spo listitem list to retrieve all items in a list

The spo listitem list can be used to return items in a list.
Currently, this command returns a 100 items by default (which is the REST API default), except when using the pageSize and  pageNumber options, with these you can maximize the amount returned to max 500 per request. But there's always just one request. If I want to retrieve all items in a list I'd have to build a script to follow each skiptoken.
As an enhancement I'd like to be able to retrieve all items using just the single m365 command.
We could go two ways:

Get all items by default
Get x items by default (like it is now) and adding an --all option to get more. Additionally, we'd have to update the documentation to say that the pageSize option defaults to 100.

Ideas?

I think we should retrieve all items by default.
Also noticed we should maybe add a remark that some filter queries won't work anymore when the list exceeds 5k items.

I should also look into how can page can page the data using camlQuery... not sure if that endpoint has skiptoken implementation.

Normally it does yes 😊

I'm not seeing a skiptoken implementation unfortunately.

Any comments before I pick this up @pnp/cli-for-microsoft-365-maintainers?


Invalid Directory causing Cloning issue

After the recent PR, you merged:

PR #1821

The Contributor has again broken the codebase cloning due to improper directory path naming:

The space in the Folder name is failing the cloning process:

@pankaj-bind Please do resolve the issue at your convinience


RuntimeError: This event loop is already running

I have installed twint using  pip install twint and trying to run simple program to scrape tweets.
c = twint.Config()
c.Search = "advertisement"
c.Min_likes = 5

twint.run.Search(c)

and got an error in colab.
RuntimeError                              Traceback (most recent call last)

<ipython-input-4-f28f8e9aab1e> in <module>()
----> 1 twint.run.Search(c)

3 frames

/usr/local/lib/python3.7/dist-packages/twint/run.py in Search(config, callback)
    325     config.Profile = False
    326     config.Profile_full = False
--> 327     run(config, callback)
    328     if config.Pandas_au:
    329         storage.panda._autoget("tweet")

/usr/local/lib/python3.7/dist-packages/twint/run.py in run(config, callback)
    224         raise
    225
--> 226     get_event_loop().run_until_complete(Twint(config).main(callback))
    227
    228 def Favorites(config):

/usr/lib/python3.7/asyncio/base_events.py in run_until_complete(self, future)
    561         """
    562         self._check_closed()
--> 563         self._check_runnung()
    564
    565         new_task = not futures.isfuture(future)

/usr/lib/python3.7/asyncio/base_events.py in _check_runnung(self)
    521     def _check_runnung(self):
    522         if self.is_running():
--> 523             raise RuntimeError('This event loop is already running')
    524         if events._get_running_loop() is not None:
    525             raise RuntimeError(

RuntimeError: This event loop is already running

try using this before your code. Worked for me.
import nest_asyncio
nest_asyncio.apply()

It seems that the pypi version of twint is broken see  #786 (comment)
Best solution would be to do the following steps:

git clone https://github.com/twintproject/twint.git
cd twint
python3 -m pip install -r requirement.txt
python3 -m pip install .

After this your could should be working (tested locally and it worked)

Try this, it worked for me:
pip install nest_asyncio
import nest_asyncio
nest_asyncio.apply()

Nest asyncio worked for me, thanks !


fix(usage-statistics): ensure editor id

Which issue does this PR address?
This makes sure we do not send events with missing installation to E.T., to not rubbish our usage statistics data.
It also fixes the root cause of the missing installation id:

start plugin with disabled configuration
enable on runtime
editor id is missing due to missing early configuration

Closes #1965
Closes #2076
Acceptance Criteria

[ ] Corresponds to the concept
[ ] Corresponds to the design

Definition of Done

[ ] corresponds to the design principles
[ ] corresponds to the code standards
[ ] passes Continuous Integration checks
[ ] available as feature branch on GitHub

[ ] contains the cleaned up commit history
[ ] commit messages satisfy our commit message guidelines
[ ] a single commit closes the issue via Closes #issuenr

It also makes sure we track those cases with Sentry, to, maybe someday, find the actual root cause (cf. #1965)

So far I was also not able to reproduce in which cases the editor id might be empty. I could think that the .editorId file couldn't be read, due to permissions. In these cases, we maybe can't do anything against it.

I've found a more likely case when editor ID is not included. You just need to enable usage statistics on runtime. Have a look at the test case: https://github.com/camunda/camunda-modeler/pull/2116/commits/4e35043a663eb7c8669065afffd321f03fc6d5a7

Thanks a lot 👏 I'll update the PR accordingly.

I updated the PR to set the editor as early as possible, so we ensure it's set no matter you enable the plugin during runtime.

As a side note, I've tested this with removed permissions on config.json and the app is then kinda unusable, but till now we haven't received any feedback regarding this. So I'd say that permissions problems are a bleeding-edge case ;)

Makes sense. Let's assume that users are able to write their own user-data directory.


fix: github, npm 멀티 배포

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


TRT-1193: Revert "IR-373: remove node-ca daemon"

Reverts openshift/cluster-image-registry-operator#867
I think Hypershift conformance is breaking on this https://issues.redhat.com/browse/TRT-1193 blocking nightlies
https://testgrid.k8s.io/redhat-hypershift#4.14-aws-ovn-conformance&width=20
Images failing to pull from the local registry during conformance tests.
registry pod logs show lots of remote error: tls: bad certificate where there were none before.

/payload-job periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance

@csrwng found that this in the likely cause https://github.com/openshift/machine-config-operator/pull/3770/
Hypershift does not run the MCO and thus nothing is laying down certs for the registry.

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-aws-ovn
/override ci/prow/e2e-aws-ovn-image-registry
/override ci/prow/e2e-aws-ovn-upgrade
/override ci/prow/e2e-hypershift
/override

/label approved
/lgtm

/label approved
/label jira/valid-bug

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-aws-ovn-upgrade


Upgrade Bootstrap

Oops, looks like our Bootstrap version is almost two years old!
3.3.6 is the latest as of March 2016.
Bootstrap 4 is still in alpha and likely won't be released for a while so upgrading to a new 3.x release is worth it in my opinion.

Agreed, but we need to take a good look at the changelog ^^-


BUG: In the navbar the toggle button, google logo etc arr not organized properly.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @anuragverma108 Please assign this issue to me.

Assigned!
Make sure to attach before & after screenshots in your PR. Also, star the repo before working on it. While creating your PR, ensure you pull all existing changes beforehand to avoid conflicts.
Happy open-source contributing!