Elixir: Missing syntax highlight in modules and atoms

You can see the issue on the screenshot below:

I've done this workaround on my current settings. But I'm not sure if they should be in this repo or somewhere else though since scopes come from vscode-elixir-ls
  "editor.tokenColorCustomizations": {
    "[Nord]": {
      "types": "#8FBCBB",
      "textMateRules": [
        {
         "name": "Elixir: module attributes",
         "scope": "variable.other.readwrite.module.elixir",
         "settings": {
           "foreground": "#D8DEE9",
           "fontStyle": "bold"
         }
        },
        {
         "name": "Elixir: atoms",
         "scope": "constant.other.symbol.elixir",
         "settings": {
           "foreground": "#D8DEE9",
           "fontStyle": "bold"
         }
        },
        {
         "name": "Elixir: modules",
         "scope": "variable.other.constant.elixir",
         "settings": {
           "foreground": "#8FBCBB",
         }
        },
      ]
    }
  }

Then got this result:

+1 for this.
The workaround works like a charm, thanks @feliperenan ! Still, It would be better to have it out of the box, anyway.

Hi @feliperenan :wave:, thanks for your contribution :+1:
Adding explicit support for popular language extensions that provide enhanced highlighting compared to the bundled/builtin syntax extensions is totally fine, but I guess we should use the origin extensions instead of the fork you've linked to ensure to cover most users.
I've added it to the backlog, but feel free to submit a PR if you like :smile:

@arcticicestudio thanks for the reply. I didn't realize I linked a file from a fork :see_no_evil: . Anyway, I double checked and there is no change from the original repository. :raised_hands:
Also, I took the opportunity to send the pull-request and I would appreciate your reviews :pray:. Please, let me know if there is something to improve there :wink:
Thanks :wave:


[OTHER] Add TypeScript Or Use Only JavaScript

What would you like to share?
There is an important question if you would like to use ts in the project or not. Some configurations of ESlint and so on depends on this question . In my opinion, it is confusing that the project uses both.
Additional information
Pros of using TypeScript:

Improve Code Quality and Refactoring
Enhanced Productivity with Codebase Documentation

Cons of using TypeScript:

It consumes development time
Some big libraries and frameworks started remove it from the source code for example : Svelte, Turbo 8 . So the future of typescript for this days is unclear.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@kabir0x23


Reuse emits deprecation warnings

Describe the bug
Running reuse lint emits deprecation warnings for many files:
$ reuse --version
reuse 3.0.2
$ reuse lint
...
some/path/lib/python3.11/site-packages/reuse/project.py:286: PendingDeprecationWarning: Copyright and licensing information for '.github/actions/free-disk-space/action.yml' has been found in both '.github/actions/free-disk-space/action.yml' and in the DEP5 file located at '.reuse/dep5'. The information for these two sources has been aggregated. In the future this behaviour will change, and you will need to explicitly enable aggregation. See <https://github.com/fsfe/reuse-tool/issues/779>. You need do nothing yet. Run with `--suppress-deprecation` to hide this warning.
...

The warnings can also been seen on api.reuse.software:

To Reproduce
Run reuse lint using version 3.0.2
Expected behavior
No warnings emitted.
Possible workaround
Add the argument --suppress-deprecation to suppress the warning: reuse --suppress-deprecation lint.
Proposed fix

Move away from dep5 file, adopt REUSE.toml. dep5 will be deprecated as of REUSE 3.1.0 anyway.

Move away from dep5 file, adopt REUSE.toml. dep5 will be deprecated as of REUSE 3.1.0 anyway.

I agree that's the way forward. @carmenbianca did ping me about giving that alpha release and REUSE.toml a try, but I did not find the time to do that yet.
Anyway, I believe we should not fully migrate to it while it's still in alpha. And I do not regard those deprecation warnings as severe, esp. as mostly the REUSE check runs on CI only. So to me this is rather low priority.

Not reproducible anymore with reuse 4.0.3 on latest main, probably due to https://github.com/oss-review-toolkit/ort/pull/9075.


Use the latest agent tag in the packer hash

The current packer build doesn't detect a new buildkite agent being available. This adds the latest agent release tag to the packer hash, so when there's a new tag we'll get a new AMI built and an updated stack JSON.

Thanks @toolmantim 👌


struct task_struct is not recognized

Hi bpftrace maintainers,
The following code is test.bt,     "bpftrace test.bt pid" doesn't work.
It looks like that curtask is a unknown type, I don't know why.
#!/usr/bin/bpftrace

#include <linux/nsproxy.h>
#include <linux/pid_namespace.h>

tracepoint:syscalls:sys_enter_openat
/((struct task_struct *)curtask)->nsproxy->pid_ns_for_children->ns.inum == $1/
{
        printf("%s      %s\n", comm, str(args->filename));
}

error info

bpftrace --info

version

version 0.8 is an old version (the latest version is version 0.13). Can you try to upgrade bpftrace? (You can download the latest version's binary here: https://github.com/iovisor/bpftrace/releases/tag/v0.13.0)

Thanks for your answer, I will try the latest version.

@mmisono The latest version is ok, thank you!


Implement sc_internal_compiler_set_entry_point for WASM

Currently unimplemented!(), which blocks gfx-backend-gl from running the example.

:+1: yeah once the GL backend stabilizes a bit I was planning to do a pass through wasm to make the surface API work there


README example fails do build on windows with MS-MPI

I have attempted to build the example code in the README on windows. MS-MPI and LLVM/libclang are installed an their path variables set. I get the following error on the custom build command:
PS D:\Programming\Git\mspi-tests> cargo build
   Compiling mpi-sys v0.2.1
error: failed to run custom build command for `mpi-sys v0.2.1`

Caused by:
  process didn't exit successfully: `D:\Programming\Git\mspi-tests\target\debug\build\mpi-sys-1b6f4601ab826597\build-script-build` (exit code: 101)
  --- stdout
  cargo:rustc-cfg=msmpi
  OPT_LEVEL = Some("0")
  TARGET = Some("x86_64-pc-windows-msvc")
  HOST = Some("x86_64-pc-windows-msvc")
  cargo:rerun-if-env-changed=CC_x86_64-pc-windows-msvc
  CC_x86_64-pc-windows-msvc = None
  cargo:rerun-if-env-changed=CC_x86_64_pc_windows_msvc
  CC_x86_64_pc_windows_msvc = None
  cargo:rerun-if-env-changed=HOST_CC
  HOST_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
  DEBUG = Some("true")
  cargo:rerun-if-env-changed=CFLAGS_x86_64-pc-windows-msvc
  CFLAGS_x86_64-pc-windows-msvc = None
  cargo:rerun-if-env-changed=CFLAGS_x86_64_pc_windows_msvc
  CFLAGS_x86_64_pc_windows_msvc = None
  cargo:rerun-if-env-changed=HOST_CFLAGS
  HOST_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
  rsmpi.c
  cargo:rerun-if-env-changed=AR_x86_64-pc-windows-msvc
  AR_x86_64-pc-windows-msvc = None
  cargo:rerun-if-env-changed=AR_x86_64_pc_windows_msvc
  AR_x86_64_pc_windows_msvc = None
  cargo:rerun-if-env-changed=HOST_AR
  HOST_AR = None
  cargo:rerun-if-env-changed=AR
  AR = None
  cargo:rerun-if-env-changed=ARFLAGS_x86_64-pc-windows-msvc
  ARFLAGS_x86_64-pc-windows-msvc = None
  cargo:rerun-if-env-changed=ARFLAGS_x86_64_pc_windows_msvc
  ARFLAGS_x86_64_pc_windows_msvc = None
  cargo:rerun-if-env-changed=HOST_ARFLAGS
  HOST_ARFLAGS = None
  cargo:rerun-if-env-changed=ARFLAGS
  ARFLAGS = None
  cargo:rustc-link-search=native=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\atlmfc\lib\x64
  cargo:rustc-link-lib=static=rsmpi
  cargo:rustc-link-search=native=D:\Programming\Git\mspi-tests\target\debug\build\mpi-sys-b247709d622bce4e\out
  cargo:rustc-link-search=native=C:\Program Files (x86)\Microsoft SDKs\MPI\Lib\x64\
  cargo:rustc-link-lib=msmpi

  --- stderr
  thread 'main' panicked at C:\Users\...\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bindgen-0.68.1\ir\context.rs:553:15:
  libclang error; possible causes include:
  - Invalid flag syntax
  - Unrecognized flags
  - Invalid flag arguments
  - File I/O errors
  - Host vs. target architecture mismatch
  If you encounter an error missing from this list, please file an issue or a PR!
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I have not touched any code, so I don't know how to interpret the possible errors listed. I apologize if I have overlooked something, but this appears like a crate issue to me.

It looks like an environment problem. Can you compare what you're trying with what is tested in CI? Let us know how we can improve the instructions.
https://github.com/rsmpi/rsmpi/blob/main/.github/workflows/test.yaml#L59-L66
(I don't run on Windows so I'm not exposed to the quirks, but I do intend for it to be supported and rely on CI.)

I have tried cloning the rsmpi repository and running the tests with cargo test --features complex,derive (which I assume was meant by trying the CI tests). I have verified that MS-MPI is fully installed and all crates are updated. The build fails with the exact same issue, the log is identical except for the file locations.

Something must be different between your configuration and the Windows CI where rsmpi is tested. The error is coming from bindgen. I'd recommend seeing if you can run cargo test in the bindgen repo, and if not, reporting in their issues or discussions. https://github.com/rust-lang/rust-bindgen/discussions

I finally found the cause of this! It seems to have been a strange problem with bindgen:
bindgen needs libclang which I had installed via LLVM. To use libclang the LIBCLANG_PATH environment variable needs to be set according to the bindgen docs (and it was for me, to the correct location of "C:\Program Files\LLVM\bin" ). This doesn't seem to enough for bindgen though, and the build failed with a cryptic error.
The example builds successfully after adding the environment variable CLANG_PATH="C:\Program Files\LLVM\bin\clang.exe" which explicitly defines the location of clang.

If this is something we can document or otherwise make more robust, feel free to open a PR to update the docs.
Once the MPI ABI is widely available, we'll be able to drop the dependency on bindgen. I've been involved in that process for a while and it will take some time to make it into distributions. For Windows in particular, it'll depend on MS-MPI adding support. MS-MPI currently only claims compliance with MPI-2.2 (2009) and a subset of MPI-3.1 (2015) so I can't estimate how long it'll take to deploy the ABI (which is still working its way through standardization).


More windows polish

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Don't show extract into variable assist for unit expressions

Reproduction:
fn main() {
    let mut i = 3;
    $0if i >= 0 {
        i += 1;
    } else {
        i -= 1;
    }$0
}

Select the snippet of code between the $0's.
The extract into variable assist shows up, pushing down the more useful extract into function assist.
The resulting output of selecting the extract into variable assist is valid but with the extracted variable having the unit type:

fn main() {
    let mut i = 3;
    let var_name = if i >= 0 {
        i += 1;
    } else {
        i -= 1;
    };
    var_name
}

Fix:

Don't show the extract into variable assist for unit expressions. I could not think of any scenarios where such a variable extraction would be desired.

bors r+


Cleaned up some stuff

btw, @Eoghanmc22 I set the domain to terrain.str1ke.codes. I’ll leave it like that until you set up the edu pack


fix: npm package version reporting

Overview

Fixing the version reported by the agent when using the npm package. The version the NPM package reports on BAM calls should match the version that is reported by other installation methods.
Related Issue(s)

https://issues.newrelic.com/browse/NEWRELIC-8150
Testing

Run the full build and use the local test server to verify the version on the BAM calls.

Is the env.js file useless/unused then?

No, the env.js file is the default. If a consumer of the NPM package imports from the agent src directory, that is the constants they will get.

No. We cant import node globals in env.js. It will break the customer's app.

No. We cant import node globals in env.js. It will break the customer's app.

But if they import from src then, wouldn't they face the same issue? If so, is that just unavoidable?

Correct. We cannot fix this issue for customers that import from the src directory. They will have to wait until we sync the version numbers.


Version 2.0 Roadmap

This issue is for tracking the development progress of version 2.0 which is being done in the next branch. Discussion and suggestions are welcomed.
Progress

[x] C Rewrite
[x] LZ4 support
[ ] Streaming API
[ ] CLI rewrite
[ ] Documentation rewrite
[ ] Finalize archive file format (version 1)

After v2.0 has been released, 1.0 versions will be considered to be completely obsolete. v2.0 will feature no backwards compatibility with v1.0 (and with archive format version 0)
Why?

Version 1.0 was written in a time when I didn't know much about actually writing good code in C/C++.
The current C++ API is absolutely ridiculous to use and is specifically engineered for a very specific use case.
Example: It only supports the use of C++ streams for both reading and writing, and consequently, archives could only be read from a file.
Bad file format design which leads to extensive usage of heap memory, which needed to be resized frequently while reading, due to the fact that sizing information provided in the file was insufficient.
I want it to be usable in both C and C++ projects (and steer away from C++ if possible).
I want it to be less pretentious; I claimed zstd to be the best compression algorithm around and refused to look at any other ones. v2.0 will (hopefully) bring more compression methods to the table, with each of them having a specific advantage for something else (with speed still being the main focus).

Streaming: read streaming added in a9b6a7414bc8a0fd42eb773eb129f1f4c1b71aa9


Error in example notebook dataset_for_ui_example.ipynb

Hi,
This is in relation to https://github.com/openjournals/joss-reviews/issues/6392
I'm listing the first errors that popped up as I progressed through the cells in each notebook. These errors may perhaps also be a hardware issue as I'm running the notebooks on a laptop with non-CUDA GPU. Also please see #19
dataset_for_ui... : Cell 3

...
OSError: Cannot save file into a non-existent directory: '..\..\data\annotated_videos'

Hello - closing this since we're tracking the overall issue here: https://github.com/mrilikecoding/StreamPoseML/issues/19


Build in a mock chroot first

Build the RPMs in a mock using a simple script so that ansible-osbuild
can focus fully on deployment rather than compiling RPMs.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

I guess in the future we could pull these RPM's from somewhere so we don't have to even rebuild, right?

That would be super nice. ;)

@teg So using osbuild-composer's latest tag breaks something in the images.
 fatal: [localhost]: FAILED! => changed=true
   cmd:
   - /usr/libexec/tests/osbuild-composer/osbuild-image-tests
   - -test.v
   - /usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json
   delta: '0:07:26.709095'
   end: '2020-05-21 12:30:02.224952'
   msg: non-zero return code
   rc: 1
   start: '2020-05-21 12:22:35.515857'
   stderr: ''
   stderr_lines: <omitted>
   stdout: |-
     === RUN   TestImages
     === RUN   TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json
     === PAUSE TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json
     === CONT  TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json
     === RUN   TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json/image_info
     === RUN   TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json/boot
     --- FAIL: TestImages (0.02s)
         --- FAIL: TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json (446.69s)
             --- PASS: TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json/image_info (21.24s)
             --- FAIL: TestImages//usr/share/tests/osbuild-composer/cases/rhel_8.2-x86_64-vmdk-boot.json/boot (201.55s)
                 main_test.go:181: ssh test failure, 20 attempts were made
     FAIL
   stdout_lines: <omitted>

Using osbuild-composer master seems to make everything okay.

Hm, the test-case has not been changed (apart from the renam) since v12, so that is sad/unexpected. Could it be a flake?

@teg Just restarted the job. Let's see. https://osbuildci.cloud.paas.psi.redhat.com/blue/organizations/jenkins/osbuild%2Fosbuild/detail/PR-413/4/pipeline

@teg same issue :(

"Nothing changed" I said. I lie! Missed this one:
commit c0ad652db58059e0e99eb7253b6ba85f25bead3f
Refs: v12-6-gc0ad652
Author:     Ondřej Budai<EMAIL_ADDRESS>AuthorDate: Mon May 4 12:46:09 2020 +0200
Commit:     Major Hayden<EMAIL_ADDRESS>CommitDate: Fri May 15 08:01:53 2020 -0500

    test/images: fix running the tests on rhel

    RHEL 8 doesn't have qemu-system-x86_64 in PATH. Instead, it is in
    /usr/libexec/qemu-kvm. This commit fixes that by detecting the host
    distro and choosing the right binary.

Seems important. I guess we keep running tests against master until the next release?

Oh burn, I missed that one!


For basemap search (zoom < 7) - search coordinates and Basemap POI

Description
How to reproduce

Open https://test.osmand.net/map/search/
Try to search for 26°04.650′ N, 119°17.509′ E

Actual result

Loading...

Expected result

Support all coordinates format that present on the Android / iOS app

Environment
9.11.24

To implement: It should be very quick search using LocationParser before full search on server side
Why it doesn't work if LocationParser is embedded inside full search itself.

Basemap section has POI available for search - large cities, towns ...

Review

[ ] Add possibility to search city on zoom levels > 7. Currently is it hard to find Berlin on 10 zoom level over Tokyo


Upgrade pulumi-terraform-bridge to v3.61.0

This PR was generated via $ upgrade-provider pulumi/pulumi-gcp --kind bridge.

Upgrading pulumi-terraform-bridge from v3.60.1 to v3.61.0.
Upgrading pulumi-terraform-bridge/pf from v0.16.1 to v3.61.0.

This is failing in Python, taking a quick look:
 TestAccWebserver/webserver-py-old (6m15.5s)


Update to dry-validation 0.8.0

I haven't updated all rules to the new syntax, but basically in places where you have blocks w/o disjunctions you can just do value(:some_predicate?) and when it must be filled use filled(:some_predicate?) and when it can be nil do maybe(:some_predicate?)
Fixes #824

 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.

one more thing - rubygems is having some issues with index caching, so it doesn't see latest dry-logic when bundling, it works with --full-index option but it's of course dead slow to bundle like that.

Awesome! Thanks!

Rubygems dependency cache issues seems to be fixed now \o/. @solnic could you rebase and resolve conflicts in Gemfile? We had to made patch release yesterday with hard dependencies. Also could you sign the CLA, we'll love to include this in our next release.

@nevalla cla signed, branch rebased, the build's green 🎉

LGTM!


1.20.1 ETA?

You probably get this question asked a lot, but is there any ETA for 1.20.1?  Minecraft is quite literally unplayable without this for me :)

The mod should work on 1.20.1, which version did you try it with?

My bad, I had previously downloaded this mod via Modrinth (with ATLauncher), and at the time I suppose there was no "official" 1.20.1 release on the page.  Downloaded from here and manually installed, everything worked great.  Sorry for confusion!


Adds support for both quotes in the TS side

TypeScript uses both ' and " in the output, so only one of the contribution changes were being applied - re discussion in #2111

:+1: Yes, it was the minified version. Terser was converting ' to " and I only really tested the dev built, since I never had problems in the past with the minified one.


The functionality provided by this repo could be implemented through git-scripts.

These commands could easily be implemented as git-scripts, integrating natively with git as git <command>.
You can create a git-script by creating an executable file named git-<command>, and placing it in the user's PATH.
For example, git-back might be a shell script:
git-back
#!/usr/bin/env sh

git checkout HEAD~

...and then as long as git-back is executable and in the user's PATH, the user can run it via git back.
IMO this provides a much nicer interface to extensions you think are useful when using git. You can peruse my own git-scripts in bddenhartog/git-extensions if you're at all confused about the implementation.

@captainsafia I'm not sure why this was closed without a response. Requiring the use of a second command altogether, like giddy, seems like extra work that only serves to complicate things for the user. You can still use the node package ecosystem to distribute your (hopefully POSIX) scripts; heck, you can even keep node as the interpreter, meaning you don't need to change much.
Effectively, all that you need to do to port your giddy tool to direct git extensions is abstract the code for them out into individual files named git-*, and ensure they are all added to the bin object in your package.json. I certainly don't mean to step on your toes here, but rather suggest a way to offer a better user experience for the handy functionality you've provided to the community.


Ongoing Sync Permissions

I received an error when trying to limit the sql account's security per ongoing sync section in this document: An unexpected error occurred when applying batch file....Failed to execute the command 'BulkInsertCommand' for table [my custom table]....
It worked when I followed advice to add ALTER TABLE here ...did I do something wrong or should the section for ongoing sync add ALTER TABLE to its list of required permissions?  Thank you.

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

ID: 062e2bfa-d9dc-c992-f5cc-f8149fe637d2
Version Independent ID: 5d931071-aed4-5c28-5036-95a1e5098aee
Content: Best practices for Azure SQL Data Sync - Azure SQL Database
Content Source: articles/azure-sql/database/sql-data-sync-best-practices.md
Service: sql-database
Sub-service: data-movement
GitHub Login: @stevestein
Microsoft Alias: sstein

@tx5westmt Thank you for reaching out.
We are actively investigating and will get back to you soon.

@tx5westmt In looking into this, can you recall the exact changes you made? The document states the following For Ongoing Sync in the Database accounts with least required privileges section:
Select/ Insert/ Update/Delete on tables that are selected for syncing, and on sync metadata and tracking tables;
Execute permission on stored procedures created by the service;
Execute permission on user-defined table types.
Is it possible that you tightened things down too much? Or, in a particularly controlled exercise, determined that the above specific permissions are either not clear or not accurate?

@Mike-Ubezzi-MSFT  Below are the steps I performed to isloate the issue to my table selected for syncing. After more testing it looks like it only happens on 'upload' data inserts from member to hub:

hub is azure sql; member is on premise sql 2014; bi-directional sync enabled
Gave account db_owner on metadata table to remove that from equation
GRANT SELECT, INSERT, UPDATE, DELETE ON SCHEMA::DataSync (to cover tracking tables)
GRANT EXECUTE ON SCHEMA::DataSync (stored procs created by service)
GRANT EXECUTE ON TYPE::DataSync.[myTable_dss_....(guid)] (just to confirm this wasn't it)
GRANT SELECT, INSERT, UPDATE, DELETE ON OBJECT::dbo.[myTable] (only testing on 1 table)
At this point, sync is successful per azure sync log on no changes and 'download' changes from hub -> member
However, adding a row in member table for 'upload' fails (dropped a screen shot picture in here)

The link I referenced above led me to try adding ALTER on my table which worked and allows the inserted record into the hub. I am not a DBA so not sure if I missed something or if this was something related to Azure sql/trigger permissions?

@tx5westmt Greatly appreciate the detailed feedback. This is incredibly helpful information. I will have the documentation team review this article and make updates based upon your feedback and careful analysis of each directional sync scenario.

@stevestein @CarlRabeler Would on-going sync permissions slightly differ in a bi-direction sync scenario where the upload (Member -> Hub) sync permissions differ slightly than the download (Hub -> Member) scenario? If so, is there a need to explicitly detail this?

@tx5westmt  - thanks for the feedback.
We have an internal work item (1780954) to update the collection of data sync articles. Unfortunately, we currently don't have an estimated time of completion for this.
Thanks
#please-close


Update CSSmin.php

Fixed Int size css in normalize_int($size)

Thanks! Please submit bugs to https://github.com/tubalmartin/YUI-CSS-compressor-PHP-port. I'm open to updating our copy in the 2.x branch, but there won't be more 2.x releases unless a security issue is found.


Allow commas in URLs

aloha @Garfield-fr .. long time no see :)

aloha @lsmith77 your welcome :+1: See you soon ;)


[EAGLE-838] Resolve defunct process in hadoop jmx script by kill -9

https://issues.apache.org/jira/browse/EAGLE-838

Resolve defunct process in hadoop jmx script by kill -9
Support configurable log file path
Improve JMX reader to multiple-threading

LGTM
Jenkins previously failed build seems has passed now.


Parsing error while calling an array getter twice

Bug
When a function that returns an array is called twice in a parallel loop, an error occurs at the second function call:
NameError: Array "__g_<ARRAY_NAME>_0" not found in outer scope or closure
Calling the function once, or accessing the array directly multiple times do not cause any error.
To Reproduce
The following code causes a DaCe error on lines quads1 = get_quads() / quads1 = get_quads_alt():
import dace
import numpy as np

NB_CELLS = 100
NB_QUADS = 20
QUADS = np.empty((NB_QUADS, 4), dtype=np.int32)

def get_quads():
    return QUADS

def get_quads_alt():
    return QUADS

@dace.program
def call_getter_twice():
    """
    Call the array getter twice per iteration
    [ERR] NameError: Array "__g_QUADS_0" not found in outer scope or closure
    """
    start_index = 0
    for j_cells in dace.map[start_index:NB_CELLS]:
        j_id0 = j_cells
        quads0 = get_quads()
        nodes_of_cell_j0 = quads0[j_id0]
        # ...Computation...

        j_id1 = j_cells
        # quads1 = get_quads()   # <- Error is caused by this function call...
        quads1 = get_quads_alt() # <- ...or alternatively by this one
        nodes_of_cell_j1 = quads1[j_id1]
        # ...Computation...

if __name__ == '__main__':
    call_getter_twice() # Error

Expected behavior
No DaCe error is thrown. Same result as accessing the array directly, without a function call (quads0 = QUADS, quads1 = QUADS).
Desktop:

OS: Ubuntu 22.04
DaCe 0.14.2

Motivation
Our aim is to generate DaCe code from a higher-level domain-specific language. Even though calling the same getter twice may be pointless, such code is expected to be valid.
Our current generator initializes multiple variables before their usage in next loop. At the moment, these variables cannot be reused among subsequent loops. For that reason, the same getter can be called multiple times, as shown in the following code snippet:
for j_cells in dace.map[start_index:self._nbCells]:
  j_id = j_cells

  # Loop #0 - Initialization
  reduction0 = dace.ndarray((2), dtype=dace.float64)
  reduction0.fill(0.0)
  nodes_of_cell_j0 = get_quads(j_id) # <- First call to get_quads()
  nb_nodes_of_cell_j0 = nodes_of_cell_j0.size

  # Loop #0 - Loop Construct
  for r_nodes_of_cell_j0 in range(nb_nodes_of_cell_j):
    r_id0 = nodes_of_cell_j0[r_nodes_of_cell_j]
    reduction0 = ...

  # Loop #1 - Initialization
  reduction1 = 0.0
  nodes_of_cell_j1 = get_quads(j_id)  # <- Second call to get_quads()
  nb_nodes_of_cell_j1 = nodes_of_cell_j1.size

  # Loop #1 - Loop Construct
  for rNodesOfCellJ in range(nbNodesOfCellJ):
    r_id1 = nodesOfCellJ[rNodesOfCellJ]
    reduction1 = ...

Thank you for reporting and for the short reproducer. It's probably an error in the internal mapping of QUADS inside the dace python parser. It is correct to only feed it in as one argument (since the array will be shared across the two calls), hence the _0.
Does it also happen if you just call get_quads twice rather than get_quads_alt?

It is a more complicated issue because, in the above code, the return values of the methods are views to the global QUADS. We do not support returning views from DaCe programs, but we make a copy, which may yield different semantics than expected.

Does it also happen if you just call get_quads twice rather than get_quads_alt?

Thanks for your quick reply. I confirm the same error occurs when get_quads is called twice.

@rd-cea We are in the process of fixing the reported error. A potential follow-up issue concerns what is returned from get_quads and get_quads_alt. In CPython, these methods will return a reference to the global array QUADS. In other words, if you write to quads0 in your example program above, then the changes will be immediately seen in QUADS and quads1. However, DaCe does not support returning such references (through the return statements). Instead, it will return copies, and QUADS, quads0, and quads1 will be different objects. If this will be an issue, please let us know, so we can discuss a workaround for your use case.

@rd-cea We have now merged the fix into the master branch. Could you try it with your code?


[Feature]: Cache HLS/m3u8

Description

Currently, caching is only supported for URLs that end in a .mp4, .m4v, or .mov extension

It would be VERY nice to have caching for m3u8 videos. It is very important for me and probably for many others too.
Why it is needed ?
This will allow small developers (like me!) to save bandwidth and lower costs of serving videos with m3u8 format.
Possible implementation
No response
Code sample
No response

To be follow up in: https://github.com/TheWidlarzGroup/react-native-video/issues/3712


Separate sync and backup notification types (successes separated from failures)

Describe your suggested feature
I have syncing enabled with Syncyomi, syncing automatically every time the app is opened, a chapter is opened or read, and every thirty minutes. Each time one of these occurs, a notification is shown.
Since a sync has never failed, I don't know if it would appear in a separate notification channel, but I assume it doesn't, given the name of the channel (simply, "Progress"). This means I cannot disable notifications for sync successes, without also being unaware of when a sync fails.
Presumably, this also applies to backups and restores, given that syncs are in the same notification category; I don't want to give up the ability to know when a backup fails in order to disable the constant "Syncing library complete" notification.
To go further, this should then also apply to backup and restores, having backup successes and failures be separate notification channels.
Other details
Related: https://github.com/jobobby04/TachiyomiSY/issues/1152
Maybe related: https://github.com/jobobby04/TachiyomiSY/issues/1280
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.11.0.
[X] I will fill out all of the requested information in this form.

Came here to suggest this feature request. My phone basically has a persistent Syncyomi notification with how often it happens. I also dont want to completely disable all Syncyomi notifications in case there is a failure.
IMO, the notification categories should be as such:

Backup and restore

Allow notifications
Complete
Errors
Progress

Sync

Allow notifications
Complete
Errors
Progress

I have very little experience with Android dev, but it seems it should be a relatively simple change.

A few additions to app/src/main/java/eu/kanade/tachiyomi/data/notification/Notifications.kt for the new group and channels.
Then some changes to app/src/main/java/eu/kanade/tachiyomi/data/sync/SyncNotifier.kt to use the new channels/group.
And if a new channel is created for backup errors, an update to app/src/main/java/eu/kanade/tachiyomi/data/backup/BackupNotifier.kt


Fixed #25397 -- Documented class-based view context variable clash with context processors.

Documented context possible shadowing of context
processor variables by default implementation of get_context_data.
PS. Previous PR https://github.com/django/django/pull/5451 auto-closed because I made some error in
in my fork.

merged in 494b7986a3e5996d857b085f188a630d1504d9ca, thanks!


VSCode not launching when FONTCONFIG_FILE env variable is set

VSCode Version:
1.28.2
7f3ce96ff4729c91352ae6def877e59c561f4850
x64
OS Version: Manjaro Linux KDE x64, kernel 4.19.0-1

Steps to Reproduce:

Set the FONTCONFIG_FILE to any value (it can be empty, it can point to existing or non-existing file - the result is the same) and run vscode: env FONTCONFIG_FILE="" code --verbose
VScode window does not appear and application exits. The output is:

[20538:1022/082947.661071:ERROR:sandbox_linux.cc(344)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 8:29:47 AM] Starting VS Code
[main 8:29:47 AM] from: /opt/visual-studio-code/resources/app
[main 8:29:47 AM] args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  add: false,
  a: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  'open-url': false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': true,
  disableExtensions: true,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false,
  issue: false,
  'skip-getting-started': false,
  'skip-release-notes': false,
  'sticky-quickopen': false,
  'disable-restore-windows': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-crash-reporter': false,
  'skip-add-to-recently-opened': false,
  status: false,
  s: false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  trace: false }
[main 8:29:47 AM] Resolving machine identifier...
[main 8:29:47 AM] Resolved machine identifier: <CUT>
[main 8:29:47 AM] update#setState idle
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.
[main 8:29:48 AM] windowsManager#open

Does this issue occur when all extensions are disabled?: Yes

How did you install vscode?

I've installed it from AUR package visual-studio-code-bin. You can see the PKGBUILD here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=visual-studio-code-bin
This is basically an automated installation script which downloads the official Linux build and unpacks it to the filesystem.

This issue originates from electron, you can check if it repros on the latest release and create an issue here if you want https://github.com/electron/electron


Improve support for running robusta locally

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: aantn:x: Robusta RunnerRobusta Runner seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

one more comment.
Because you ran the runner locally, it changed your git user to "Robusta Runner"
Now, parts of the commits are registered under the "Robusta Runner" which didn't sign the CLA...


Rename package to allow running through npx

npx @xata.io/xata-codegen

@gimenete Before merging we should deprecate old package and publish current version. I've cancelled the current build so the action does not attempt to publish the new one yet (approval on the rename).


[New Feature_WebApp] - Setup Linting

Is your feature request related to a problem? Please describe.
We can setup linting so that the code is well-organized and readable. Also, this will help us to maintain the code style throughout the codebase.
Describe the solution you'd like
This can be achieved using prettier, husky and eslint.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Go ahead !


Implement config updates

In case package was updated and old config is already in the application, we need to:

Add new keys from package config to application config.
Comment-out keys that aren't present.
Probably report on the differences?

English: A decision on the update configuration packages.
Version 1. Copy the additional configs to the subfolder /config/yii-debug/readonly - these will be the original default configs. On composer update, we make a diff between the new default configs and the current configs from readonly folder. And then array_merge($diff, $edited_config)
Version 2. Before updating the packages, copy the current default configs somewhere in the runtime folder or save in memory. Then we do as in the first version.

English: A decision on the update configuration packages.
Version 1. Copy the additional configs to the subfolder /config/yii-debug/readonly - these will be the original default configs. On composer update, we make a diff between the new default configs and the current configs from readonly folder. And then array_merge($diff, $edited_config)
Version 2. Before updating the packages, copy the current default configs somewhere in the runtime folder or save in memory. Then we do as in the first version.


[WIP] Add type annotations and mypy compliance

:squid: Ready for review, but watch for sea monsters (my first WB PR)
Ticket
https://openscience.atlassian.net/browse/SVCS-340
Purpose

Add type annotations to assist with debugging (core classes and some, but not all, providers)
Provide an option (currently not on by default) to use mypy, a linter for gradual type hinting- catches weird usages of methods

Notes for reviewers
Many of these types are a "best guess" and subject to evolve in the future. Python types are informational only and do not affect runtime, but tools such as mypy (and pycharm!) support automatic linting to catch errors during development.
I am new to waterbutler. If there is a better type to use, let me know. The ignore settings in mypy may be too aggressive and are worth revisiting in the future.
Specific rules that we ignore
Mypy does not appear to support selective ignoring of certain rules. Therefore, ignore statements are scattered throughout the code more than I would wish. See notes and rationale:

Mypy doesn't seem to do very well with functions that can return more than one type of thing. (so basically every call to metadata gets ignored) See:
https://github.com/python/mypy/issues/1693

This could be resolved using dependent types / @overload, if we some day refactor so that files and folders are represented via different classes.

Method call signatures or return types are not consistent with parent classes. We routinely violate the Liskov substitution principle, of necessity as there is no uniform abstraction for all providers. See: https://github.com/python/mypy/issues/1237

There are a lot of ignores for this. It's terrible; I'm sorry.

Summary of changes

Add type annotations to code
Update docstrings
Update method signatures that did not reflect the common usages across all subclasses

Testing notes
In theory this is a pure developer facing change. One or two minor changes were made to method call signatures.
Recommend watching for any new errors during common operations. I have done light manual testing consisting of uploads/downloads/renames/cross provider moves (osf storage to google drive).

Initial manual testing. Merge conflicts with googledrive refactor; will update and revalidate before next week.

Coverage increased (+0.4%) to 75.6% when pulling e3fc18303e7326cf3b2caa95b8728c113c7a6ed7 on abought:feature/svcs340-waterbutlerpath into 753bdd2434b757d889aae6d9b6e9c9c3a650e9dc on CenterForOpenScience:develop.

Merge conflicts resolved and basic retesting done. Let me know if there are additional checks requested!


Enable the feature to set height of x axis

The height of x axis can be set manually by this option
http://c3js.org/reference.html#axis-x-height
It would be enough to add these lines of code within 'chartAxisX' directive
var height = attrs.axisHeight;
if (height) {
		axis.height = parseInt(height)};
}

at view side could be for example as follow:
<chart-axis-x axis-position="outer-center" axis-height="85"></chart-axis-x>

Fixed by the pull request, thanks


values.yaml are stale for Crossplane

What happened?
The default values.yaml in the UXP helm chart is stale with respect to Crossplane. For instance, the securityContext fields on release-1.2 do not match those for v1.2.1 in Crossplane.
How can we reproduce it?
Deploy UXP and check the runAsUser / runAsGroup fields.
What environment did it happen in?
Universal Crossplane version: v1.2.1-up.3
Kubernetes version (kubectl version): v1.21.0 (v1.21.0)

When creating the release for OLM, please clear out the runAsUser and runAsGroup related to securityContextCrossplane and securityContextRBACManager

@muvaf I wonder if we could implement some hooks in olm-bundle to support any operations like this?

@BigSammich We can do it but could you elaborate on why you need them cleared out in OLM?

@muvaf Openshift likes to assign "random" UID / GID in a range and some clusters enforce that policy, more info here.

@hasheddan thanks for the info! I opened https://github.com/upbound/universal-crossplane/issues/116 to track it.


disk information in settings

Description
This PR adds an entry to the settings view that shows the disk usage of the disk that docker is making use of.

Checklist

[X] I have manually tested the application to make sure the changes don’t cause any downstream issues, which includes making sure ./orchest status --ext is not reporting failures when Orchest is running.

@iannbing  @ricklamers Can this be merged?

LGTM. Minor point: there should be some spacing between the text below the bar. We could just add a "push-up" class.

Great job! :rocket:

Updated look


Release of Pre-trained models

Request for Release of Pretrained NLLB-LLM2Vec Model
Hello Team,
Could you please release the pretrained NLLB-LLM2Vec  models mentioned in your paper on "Self-Distillation for Model Stacking Unlocks Cross-Lingual NLU in 200+ Languages"? It would greatly benefit the community by facilitating further research.
Thank you for your contributions.
Best regards,
Arkadeep Acharya

Hi Arkadeep,
Thanks a lot for your interest in our work!
Yes, I very much plan on making the models available. :)
I am currently working on refining Stage 1, such that Stage 2 won't be necessary.
My sincere hope is that I can then release a single pre-trained model which can easily be fine-tuned on any downstream task without task distillation for maximum performance.
In any case, I will make the self-supervised adapted model (S1) available asap.
Cheers,
Fabian

Thanks Fabian!
Looking forward to the model release!

As a quick update. Sharing the model on Hugging Face hub is surprisingly hard, since it has to be quantized and LoRAfied correctly prior to loading the weights. transformers, peft, bitsandbytes don't play that easily nicely together when setting up an AutoModel.from_pretrained the conventional way. Unfortunately, none of this is really well documented.
Between having been sick and working on the more general model, I haven't yet had sufficient time how to best upload the model in a way that it is most easily used, i.e.
from transformers import AutoModel
model = AutoModel.from_pretrained("fdschmidt/nllb-llm2vec-v0.1")

I might have to package it more generally as an nn.Module (cf. https://huggingface.co/docs/hub/models-uploading#upload-a-pytorch-model-using-huggingfacehub). I'll be on vacation next week but will try to squeeze it in.

Hey Fabian!
I know you are probably busy building some exciting stuff but have you had the chance to upload the weights? Even a link to S3 or Google drive is much appreciated.
Thanks

Hi there,
I'm actually while writing trying to iron out the very last issues of an initial release of NLLB-LLM2Vec on Llama 3.1 8B.
That release will support seamless
AutoModel.from_pretrained("fdschmidt93/...")
AutoModelForSequenceClassification.from_pretrained("fdschmidt93/...")
AutoModelForTokenClassification.from_pretrained("fdschmidt93/...")

Unfortunately wrapping true custom models onto the Huggingface Hub is simply a bad developer experience (undocumented and unusual behavior, plus stuff like https://github.com/huggingface/transformers/pull/33844).
Anyhow, that release should ideally be close in performance of S1+S2 while only doing S1+FT (if that's unclear, please refer to the paper).
I'm on the case.

https://huggingface.co/fdschmidt93/NLLB-LLM2Vec-Meta-Llama-31-8B-Instruct-mntp-unsup-simcse
Here is the model with usage instructions on the README. The model doesn't have that much mileage on it yet, so I'd kindly ask you to report any issues you run into it quickly and I'll fix them ASAP :)

@fdschmidt93 Thanks a lot!

Hi @fdschmidt93, Can you please clarify if this is a stage-1 trained model or if the model has gone through both Stage-1 and stage-2 training?

Hi @ArkadeepAcharya
As stated on the readme of the model, this version has yet to be fine tuned for a downstream task. Hence, the model has only been trained for stage 1. It nevertheless should notably perform better than stage 1 in the paper as it has been trained

for much longer
with token alignment
with a least squares initialized up projection that improves convergence speed and fit
merged LoRAs -- which strongly helps in few shot tasks like NusaX

I unfortunately won't be releasing stage 2 models as I will not be finetuning models per task due to lack of time and compute.
There would be an argument to do something like GritLM (cf. Paper) and then do distillation to have a single model for 'all tasks', but I don't have the capacity (GPUs, time) to do that. I invested a lot of time in improving the self-supervised stage as much as possible.
NLLB-LLM2Vec should be used if you need sequence level embeddings for less resourced languages that industry-level models (samples, supervision, etc.) like NVEmbed, GritLM, E5, BGE don't cover. Or in actually academic settings where you want to be more sure that the task has not leaked (albeit instruction finetuning of Llama itself may have leakage).


Refactoring index, and fixing python "se3ToXYZQuat "

Switch index depending on architecture ( std::size_t now).
Cleaning multiple warning for Clang
Travis now compiles with Clang and passes
Added License
Fixing pythons utils method " se3ToXYZQuat"

I think this pull request needs some commit simplifications before being accepted. Indeed commits d1d76e1 and 843ea35 have been written in opposite directions.
We also need to choose between int type and long type according to the architecture (cf. Eigen).

The switch of index has been done in three steps because the naive change of int to size_t involved errors. But i can squash these commits together.

I really think it is better in this way.
In the same way, it is better to use a global Model::Index rather than size_t in 40f3fc6. And don't hesitate to use typedef to avoid long expression (e.g. Index instead of simple Model::Index).


Add support for OPTIONS requests.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@85f2715). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head b3d18eb differs from pull request most recent head aaa7768. Consider uploading reports for the commit aaa7768 to get more accurate results

@@            Coverage Diff             @@
##             develop     #126   +/-   ##
==========================================
  Coverage           ?   88.61%
==========================================
  Files              ?       82
  Lines              ?     1317
  Branches           ?      122
==========================================
  Hits               ?     1167
  Misses             ?      148
  Partials           ?        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 85f2715...aaa7768. Read the comment docs.


Login Popup sometimes does not open

https://github.com/aws/amazon-connect-streams/blob/2802651ab46452485bcb178d8d324aaffa4019ba/src/util.js#L413
connect.PopupManager.prototype.open = function(url, name) {
    var then = this._getLastOpenedTimestamp(name);
    var now = new Date().getTime();
    var win = null;
    if (now - then > ONE_DAY_MILLIS) {
       win = window.open('', name);
       if (win.location !== url) {
          win = window.open(url, name);
       }
       this._setLastOpenedTimestamp(name, now);
    }

According to the code above. The login popup only opens if one day has passed since the last popup. This seems to create isssues as sometimes the user is not logged in but it won't popup the login window because 1 day has not passed yet since the last popup. Somehow, I don't see this issue mentioned by anyone so may be I am doing something wrong here.
The following is the only code that I have for now.
var ccpUrl = "https://" + instanceAlias + ".awsapps.com/connect/ccp-v2";
connect.core.initCCP(containerDiv, {
        ccpUrl: ccpUrl,
        loginPopup: true,
        loginPopupAutoClose: true,
        softphone: {
            allowFramedSoftphone: true
        }
    });

I was wondering if the check if (now - then > ONE_DAY_MILLIS) { is really required?

Have also experienced this issue.

I don't understand this one day, neither.
I was clearing this with the following snippet:
connect.core.getPopupManager().clear(connect.MasterTopics.LOGIN_POPUP);

We clear the timer on ACK_TIMEOUT and ACKNOWLEDGE events, and you can manually clear it by calling connect.core.getPopupManager().clear(connect.MasterTopics.LOGIN_POPUP) as @hfahlbusch mentioned. By default if the CCP does not ACK for 10 seconds that will trigger a cleanup call.


Proxy working only for text, voice and media failed in proxy transport

Test with 4 different servers , with serval users with different connectivity . only Text can transfer , other types of media failed or user cannot download sent one .

Hello
Yes, this restriction has been applied by WhatsApp. Maybe in the future it will be fixed

Again: A new fake advertisement by WhatsApp

@slawlor  can you confirm this is limitation by Meta ?

Again: A new fake advertisement by WhatsApp

The media are good at publishing fake headlines. This feature is not an advanced feature

Yes it's a limitation, we currently only support the main chat functionality. It's stated in the "About" on the project on the repository home page.

Yes it's a limitation, we currently only support the main chat functionality. It's stated in the "About" on the project on the repository home page.

Dear friend, I am the manager of an organization that helps the people of Iran to have access to the free internet.
In less than twenty minutes, the server will be identified and blocked by Iran's firewall.
This is not a good idea
I think you are only looking to create fake news rather than helping people


Download images alongside markdown files save images to same name

Download URL: https://mp.weixin.qq.com/s/q_a0_qXpui-SkIdQv-E49A

if not enable option "Download images alongside markdown files", download markdown file's images would be something in markdown file like:
![Image](https://mmbiz.qpic.cn/mmbiz_gif/0UdhCqGulicdW4XSJpnW7ZAoZGPRNe4icfibylabw3GfUTtKRHo3v2TwxBCcrSnwzV4wN8LiaQ5oib4hJKa3sMeYnXA/640?wx_fmt=gif&tp=webp&wxfrom=5&wx_lazy=1)
![Image](https://mmbiz.qpic.cn/mmbiz_jpg/0UdhCqGulicdW4XSJpnW7ZAoZGPRNe4icf9FscoN4ueNV9ApDbV2pmKGPSTB59R9LWtTliblfQoGlcpgRAO9VXmSA/640?wx_fmt=jpeg&tp=webp&wxfrom=5&wx_lazy=1&wx_co=1)

if enable option "Download images alongside markdown files", then those images would point to same name:
![Image](_resources/%E5%B9%BC%E5%84%BF%E5%9B%AD%E8%BF%91%E8%A7%86%E9%98%B2%E6%8E%A7%E6%89%8B%E5%86%8C/640)
![Image](_resources/%E5%B9%BC%E5%84%BF%E5%9B%AD%E8%BF%91%E8%A7%86%E9%98%B2%E6%8E%A7%E6%89%8B%E5%86%8C/640)

Hope it could be solved as bug or new feature, Thank you.

Ah, I see what's happening here.  If you look at the URLs, the file name for both is "640". So I'll need to append a number to make the filename unique. In this situation, you'd likely end up with 640 and 640(1) (or maybe 640.1).
🤔 I might also want to see if the file is missing the extension, and if it is like these are, try and ascertain the correct extension and append that.

Ah, I see what's happening here.  If you look at the URLs, the file name for both is "640". So I'll need to append a number to make the filename unique. In this situation, you'd likely end up with 640 and 640(1) (or maybe 640.1).
🤔 I might also want to see if the file is missing the extension, and if it is like these are, try and ascertain the correct extension and append that.


Command error:   Error in Fid_info[1, "DECIM"] : subscript out of bounds

I am getting the Group Delay Correction error when trying to process the dataset MTBLS9131(metabolights)
Command error:
Error in Fid_info[1, "DECIM"] : subscript out of bounds
Calls:
Execution halted
I have DECIM defined as 24 in all data folders.

Are there any outputs from previous steps, namely load_fids and raw_fids_visualisation? How manifest.csv and metadata looks like? There error most likely indicates that there are no data after loading raw fids.

You can try. I simply replaced the folders in your testthat/data/ folders with different datasets (from MTBLS9131) and even named them in the same way (500 etc.), keeping your metadata. Of course, it does not make any sense in scientific terms, but I wanted to test the workflow on different signals.
MTBLS9131.zip

After downloading the raw data directly via FTP using the command:
wget -r -np -nH --cut-dirs=5 ftp://ftp.ebi.ac.uk/pub/databases/metabolights/studies/public/MTBLS9131/ and then making a little modifications to the metadata.csv, manifest.csv, and params.yml files based on the information provided in UPEC_metadata.xlsx everything seems to work just fine. It is crucial to ensure that only two groups are kept for comparison in metadata. If the pipeline is executed with three groups, it will run successfully until the univariate analysis, where an error will appear indicating that there are more than two groups to compare. I am also including all files (only inputs as full results are still in process of generating
NASQQ_MTBLS9131.zip
) in .zip archives in here.

Here are the results from the spectral processing. Aside from three samples that likely needed manual flipping after FT and some adjustment of baseline correction parameters, everything looks fine. The folder containing all results exceeds 600MB, so I am unable to upload it here.
Spectrum_data_N_stacked.pdf

It took 2 hours, but the results have been fully generated. Additionally, treated samples are clearly distinguished from the negative controls, suggesting that everything proceeded as expected (see next screenshot of PCA)

One outlier was detected in the univariate module. This sample exhibited strong water signal during spectral processing stage, resulting in poor FT and phasing. This outlier is also evident in the PC1 vs PC2 plot and on the heatmap (sample 30), where distinct clusters for the treatment and control groups are clearly visible as well.

After downloading the raw data directly via FTP using the command: wget -r -np -nH --cut-dirs=5 ftp://ftp.ebi.ac.uk/pub/databases/metabolights/studies/public/MTBLS9131/ and then making a little modifications to the metadata.csv, manifest.csv, and params.yml files based on the information provided in UPEC_metadata.xlsx everything seems to work just fine. It is crucial to ensure that only two groups are kept for comparison in metadata. If the pipeline is executed with three groups, it will run successfully until the univariate analysis, where an error will appear indicating that there are more than two groups to compare. I am also including all files (only inputs as full results are still in process of generating NASQQ_MTBLS9131.zip ) in .zip archives in here.

Hi,
I downloaded your files and run the program. It crashes on Solven t Suppression:
Nextflow 24.04.1 is available - Please consider updating your version to it
N E X T F L O W  ~  version 23.10.1
Launching ./main.nf [gigantic_carson] DSL2 - revision: eee0efc519
        .--:--:---.\
      {}  : {}   :                           __  _  __   __  ____
      ||__"_||   :                          |  || ||  \ /  || __ \
     /        \  `={}_                      | N \ A| S   Q || Q_| \
    |   NASQQ  |  (   )                     |_| \_||_| V |_||_| \_|
    |  v1.0.0  |  (   )
    |    ____  |  (   )    Nextflow Automatization and Standarization for Qualitative and Quantitative
    |   |    | |  (   )             1H 1D NMR metabolomics data preparation and analysis
    |___|____|_|  (   )                   =======================================
    |          |  (   )                   input from     : manifest.csv
   /|    ||    |\ (   )                   output to      : output/outdir_review
  | |    ||    | |(   )                   ------
  | |____||____| |(   )                   run as         : nextflow run ./main.nf -c ./nextflow.config -profile standard -params-file params.yml
  |   _________  |(   )                   started at     : 2024-05-27T09:09:47.060396+02:00
  |  |   | |   | |(   )                   launchdir at   : /workspace1/Dropbox/Krzysztof/revisions/GIGAScience/nasqq-main
  |__|   |_|   |_|(___)

[-        ] process > SPECTRAL_PREPROCESSING:LOAD... -
[-        ] process > SPECTRAL_PREPROCESSING:RAW_... -
executor >  local (1)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [  0%] 0 of 1
[-        ] process > SPECTRAL_PREPROCESSING:RAW_... -
executor >  local (3)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [  0%] 0 of 1
executor >  local (4)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [  0%] 0 of 1
executor >  local (4)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [  0%] 0 of 1
[7a/38d866] process > SPECTRAL_PREPROCESSING:GROU... [100%] 1 of 1 ✔
[bf/ee4e0f] process > SPECTRAL_PREPROCESSING:SOLV... [ 50%] 1 of 2, failed: 1...
executor >  local (5)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [100%] 1 of 1 ✔
[7a/38d866] process > SPECTRAL_PREPROCESSING:GROU... [100%] 1 of 1 ✔
executor >  local (5)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [100%] 1 of 1 ✔
[7a/38d866] process > SPECTRAL_PREPROCESSING:GROU... [100%] 1 of 1 ✔
[78/152663] process > SPECTRAL_PREPROCESSING:SOLV... [ 50%] 1 of 2, failed: 1...
[-        ] process > SPECTRAL_PREPROCESSING:APOD... -
[-        ] process > SPECTRAL_PREPROCESSING:ZERO... -
[-        ] process > SPECTRAL_PREPROCESSING:FOUR... -
[-        ] process > SPECTRAL_PREPROCESSING:ZERO... -
[-        ] process > SPECTRAL_PREPROCESSING:INTE... -
[-        ] process > SPECTRAL_PREPROCESSING:BASE... -
[-        ] process > SPECTRAL_PREPROCESSING:NEGA... -
[-        ] process > SPECTRAL_PREPROCESSING:WARPING -
[-        ] process > SPECTRAL_PREPROCESSING:WIND... -
[-        ] process > SPECTRAL_PREPROCESSING:BUCK... -
[-        ] process > SPECTRAL_PREPROCESSING:NORM... -
[-        ] process > METABOLITES_QUANTIFICATION     -
[-        ] process > ADD_METADATA                   -
[-        ] process > COMBINE_DATASET_BATCHES        -
[-        ] process > DATA_ANALYSIS:FEATURES_PROC... -
[-        ] process > DATA_ANALYSIS:EXPLORATORY_D... -
[-        ] process > DATA_ANALYSIS:UNIVARIATE_AN... -
[-        ] process > DATA_ANALYSIS:MULTIVARIATE_... -
[-        ] process > PATHWAY_ANALYSIS_MULTIVARIATE  -
[-        ] process > PATHWAY_ANALYSIS_UNIVARIATE    -
ERROR ~ Error executing process > 'SPECTRAL_PREPROCESSING:SOLVENT_SUPPRESSION (review)'
Caused by:
Process SPECTRAL_PREPROCESSING:SOLVENT_SUPPRESSION (review) terminated with an error exit status (1)
Command executed:
solvent_suppresion.R --id "review" --fid_gdc "review_grouped_FIDdata_GDC.rds" --raw_rds "review_selected_fid_list.rds"
executor >  local (5)
[ff/701c1d] process > SPECTRAL_PREPROCESSING:LOAD... [100%] 1 of 1 ✔
[42/1372e0] process > SPECTRAL_PREPROCESSING:RAW_... [100%] 1 of 1 ✔
[7a/38d866] process > SPECTRAL_PREPROCESSING:GROU... [100%] 1 of 1 ✔
[78/152663] process > SPECTRAL_PREPROCESSING:SOLV... [100%] 2 of 2, failed: 2...
[-        ] process > SPECTRAL_PREPROCESSING:APOD... -
[-        ] process > SPECTRAL_PREPROCESSING:ZERO... -
[-        ] process > SPECTRAL_PREPROCESSING:FOUR... -
[-        ] process > SPECTRAL_PREPROCESSING:ZERO... -
[-        ] process > SPECTRAL_PREPROCESSING:INTE... -
[-        ] process > SPECTRAL_PREPROCESSING:BASE... -
[-        ] process > SPECTRAL_PREPROCESSING:NEGA... -
[-        ] process > SPECTRAL_PREPROCESSING:WARPING -
[-        ] process > SPECTRAL_PREPROCESSING:WIND... -
[-        ] process > SPECTRAL_PREPROCESSING:BUCK... -
[-        ] process > SPECTRAL_PREPROCESSING:NORM... -
[-        ] process > METABOLITES_QUANTIFICATION     -
[-        ] process > ADD_METADATA                   -
[-        ] process > COMBINE_DATASET_BATCHES        -
[-        ] process > DATA_ANALYSIS:FEATURES_PROC... -
[-        ] process > DATA_ANALYSIS:EXPLORATORY_D... -
[-        ] process > DATA_ANALYSIS:UNIVARIATE_AN... -
[-        ] process > DATA_ANALYSIS:MULTIVARIATE_... -
[-        ] process > PATHWAY_ANALYSIS_MULTIVARIATE  -
[-        ] process > PATHWAY_ANALYSIS_UNIVARIATE    -
ERROR ~ Error executing process > 'SPECTRAL_PREPROCESSING:SOLVENT_SUPPRESSION (review)'
Caused by:
Process SPECTRAL_PREPROCESSING:SOLVENT_SUPPRESSION (review) terminated with an error exit status (1)
Command executed:
solvent_suppresion.R --id "review" --fid_gdc "review_grouped_FIDdata_GDC.rds" --raw_rds "review_selected_fid_list.rds"
Command exit status:
1
Command output:
(empty)
Command error:
Error in difsm(y = FidRe, lambda = lambda.ss) :
NA/NaN/Inf in foreign function call (arg 2)
Calls:  -> difsm
Execution halted
Work dir:
/workspace1/Dropbox/Krzysztof/revisions/GIGAScience/nasqq-main/output/workdir_review/78/152663b306185410eeb3b2107a352a
Tip: view the complete command output by changing to the process work dir and entering the command cat .command.out
-- Check '.nextflow.log' file for details

Firstly, I edited the archive with the uploaded files on Sunday because it had a typo in params.yml. Do you have the most recent version of it?
Secondly, apart from the errors from Nextflow, please provide:

The .nextflow.log.{number of execution} file (each time you execute pipeline in the same directory it adds subsequent number, so it might be .nextflow.log.1).
The outcomes of the last two processes:

For the process that crashed, I need the list of the working directory and the files .command.out and .command.err.
For the previous successfully executed process, I need the .rds files so that I can load them and see what’s going on.

I need to have a look on the input files (manifest.csv, params.yml, metadata.csv) maybe there are some typo.

Hi,
I took the input files from your zip linked in this thread (https://github.com/ardigen/nasqq/files/15443973/NASQQ_MTBLS9131.zip)
But the params.yml from the zip file has been modified on Friday, 17∶11∶38. Is it the right one?

Oh, I edited params.yml on Friday and metadata.csv on Saturday, my bad. Those files seem to be fine. Please provide the following from points 1-3.

these are the files generated/modified today
files.zip

Okay, those files seem to be fine if the path /workspace1/Dropbox/Krzysztof/revisions/GIGAScience/nasqq-main is an absolute path. If not, I recommend using either an absolute path or a relative path starting from the directory where all input files are located. Now, the most crucial files I need are review_grouped_FIDdata_GDC.rds from the 7a/38d866 workdir and review_selected_fid_list.rds from the ff/701c1d workdir (it is shorten name, it is much longer but Nextflow shows only this during execution).

Anyways, after resolving these issues, adding a "Debugging" section to the README might be a good idea to speed up the process of resolving potential bugs as it not so straightforward, especially for somebody without experience in Nextflow pipelines.

These files are in different locations, not in 7a and ff. Here is the full workdir:
https://www.dropbox.com/scl/fi/n6t5j1ycmtchicfcvebor/workdir_review.zip?rlkey=p2z8w1eiz7yfzzkyioy5r3yqe&dl=0

Can you please remove entire workdir, all .nextflow.log(s) and run pipeline one more time? I see that it crashed on two samples 3 and 33, and I am trying to figure out why.

The same, crashes on Solvent suppression
https://www.dropbox.com/scl/fo/smq6itb1q55cv7ypxt7qk/AF9cipZEKKWQiQxZoUpj954?rlkey=kzyrxu0votlc415qbv375aar5&dl=0

So far, it seems like FIDs that you have in your directory are completely different then mine, either preprocessed by pipeline or even using manual function in R. Below few examples:

And that is one from yours output:

Can you please start from scratch? Here are the steps:

Clone the repository of the nasqq pipeline to a new location. Remove all remnants of previous executions or change the execution location.
Create a new folder inside the nasqq directory, for example, review.
Navigate to this new review folder.
Download the raw files from Metabolights via FTP.
Copy manifest.csv, params.yml, run.sh, and metadata.csv into the review directory.
Adjust the paths in these files to absolute paths.
Run run.sh.

That's super strange, I did it one more time as I described above and it's running correctly...

it seems to be ok now, but crashed on warping, because I did not adjust the number of CPUs... I will let you know soon

OK, completed successfully, thanks!


fix(iOS 16): avoid SpringBoard crash trying to foreground the app.

This change fixes the sendToHome method for iOS 16.0 and above, which were introduced along with Xcode 14, as addressed in https://github.com/wix/Detox/issues/3531.
The original bug was reproduced locally with Xcode 14 and Xcode 14.1 beta 2 (I checked if anything has changed between those versions) along with iOS 16 and iOS 16.1. Also, the fix was tested on the same Xcode versions and iOS Simulators.
SpringBoard is not directly accessible by Simctl on iOS 16.0 and above, therefore we launch and terminate the Settings app instead. This sends the currently open app to the background and brings the home screen to the foreground.
In spite of the fact that this isn't an ideal solution, I haven't found another direct method of doing it, so this is probably the only practical option.

@asafkorem
Hello sir. I'm not a pro ios developer. I'm only junior and trying learn the swift language for 6 months. Anyway, I upgraded my xcode the last version and now I'm seeing "  the operation couldn't be completed. xpc error " and simulator is down. I don't know this is the same problem that you wrote here but I just want to help you with this bad error. Thanks

@umutcanbostancii what is your Detox version?


[BulletPhysics][Suggestion][CS/CZ] Keep ragdoll instead of ClCorpse message

In CS 1.6 and CZ, after a player dies and the animation finishes, it is rendered invisible and a ClCorpse( https://wiki.alliedmods.net/Half-life_1_game_events#ClCorpse ) message is sent to players, basically spawning a client-sided entity at a certain origin with the player model and the last frame of the death animation that was played.
If you can find a method to somehow hook this and keep the ragdoll instead it would be awesome.
Thank you :)
https://user-images.githubusercontent.com/3608544/174457658-30e14a53-8ba9-4d99-811d-4bbc30231071.mp4

Counter-Strike never sends client index (aka entity index) of dead player to client in ClCorpse event
MESSAGE_BEGIN(MSG_ALL, gmsgSendCorpse);
	WRITE_STRING(pModel);
	WRITE_LONG(pev->origin.x * 128);
	WRITE_LONG(pev->origin.y * 128);
	WRITE_LONG(pev->origin.z * 128);
	WRITE_COORD(pev->angles.x);
	WRITE_COORD(pev->angles.y);
	WRITE_COORD(pev->angles.z);
	WRITE_LONG((pev->animtime - gpGlobals->time) * 100);
	WRITE_BYTE(pev->sequence);
	WRITE_BYTE(pev->body);
	MESSAGE_END();

it will be quite tough to know who owns the corpse

An update has been pushed in commit 52c9f9905d9f2c1ca6a6900de361cc80e2ed0a90 to find out who owns the corpse with some tricky method.
the ClCorpse message now works fine with ragdolls in most situations. (probably not works with VIP CT)
and I made some changes to gign's constraints, it loooks better now than it was

Will test it out, but notice that the rigid body spheres still clip through eachother and the body looks "compressed".
Also, if you have time, can you please explain your method of how you did the ClCorpse support in summary?

Will test it out, but notice that the rigid body spheres still clip through eachother and the body looks "compressed". Also, if you have time, can you please explain your method of how you did the ClCorpse support in summary?

The positions, angles model names and sequences are saved for dead players, which were compared while creating tempentity from ClCorpse.

Tested. The ragdoll still turns into a static ClCorpse and the following errors are thrown:
https://user-images.githubusercontent.com/3608544/174492901-33aa7d55-4ecb-4c5c-b171-704c77595cea.mp4

Tested. The ragdoll still turns into a static ClCorpse and the following errors are thrown:
https://user-images.githubusercontent.com/3608544/174492954-70e0dc14-e10f-460d-b9e4-5fe3e95b1613.mp4

Also, just want to say amazing job. The ragdolls even fade away and get removed by the engine when cl_corpsestay expires, exactly like the ClCorpse entity. Thank you.


Refactor RM - Title Count query to use derived tables

Axel is working on refactoring the RM - Title Count query to use derived tables

-refactoring is done
-some concerns about performance, Axel to working with Nassib on this


Missed Publishers.ZIP

Apple documentation: https://developer.apple.com/documentation/combine/publishers/zip

This is a work in progress: #109

Sorry, I not noticed.


MI 4.2.0 - SAML integration support

Problem
This git issue is related to https://github.com/wso2-enterprise/wso2-apim-internal/issues/1678.
MI 4.2.0 has not been properly tested for SAML related use cases. As a result, multiple issues are observed when implemented SAML 2.0 integrations. The said issues are documented in the above ticket.
Solution
Improve MI 4.2.0 to support SAML related use cases.
Affected Component
MI
Version
4.2.0-Beta
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Hi @sarindufit
I have debugged the SAML flow with MI 4.2.0 pre-beta pack and the following points were observed

According to the stack trace [2023-01-25 14:25:45,020] ERROR {NativeWorkerPool} - Uncaught exception java.lang.NoClassDefFoundError: org/apache/xml/security/exceptions/XMLSecurityException  org/apache/xml/security/exceptions package is not visible to the custom mediator with saml implementation
We have packed this class as a bundle as  <bundleDef>org.wso2.santuario.orbit:xmlsec</bundleDef> in org.wso2.micro.integrator.identity.xacml.mediator.feature
When debugging our orbit bundle for opensaml/3.3.1.wso2v7 we can see that xmlsec dependency is used but not packed.
After adding it as an embedded dependency the SAML scenario worked as expected
Please test by adding the jar inside /wso2mi-4.2.0-alpha/wso2/components/plugins/opensaml_3.3.1.wso2v7.jar

patch.zip

Hi Rosen,
Please note that I can confirm that the below issue is now resolved.
[2023-01-25 14:25:45,020] ERROR {NativeWorkerPool} - Uncaught exception java.lang.NoClassDefFoundError: org/apache/xml/security/exceptions/XMLSecurityException

However, the execution flow now results in the below error. Note that the ws-security header is not sent out to the backend. I have attached the wire log for your reference.
[2023-02-01 12:48:40,186] ERROR {org.apache.synapse.core.axis2.Axis2Sender} - {proxy:ch_suva_wsx_monitoring_platform_sap_crm_saml_v1} Unexpected error during sending message out. Error in signature with X509Token org.apache.axis2.AxisFault: Error in signature with X509Token
	at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
	at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
	at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:206)
	at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:188)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:675)
	at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:86)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:591)
	at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:423)
	at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:79)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:261)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:472)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:188)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.apache.rampart.RampartException: Error in signature with X509Token
	at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:789)
	at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:457)
	at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
	at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
	at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
	... 20 more
Caused by: org.apache.ws.security.WSSecurityException: Signature creation failed (Cannot setup signature data structure); nested exception is:
	org.apache.xml.security.transforms.TransformationException: Unknown transformation. No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
Original Exception was org.apache.xml.security.transforms.InvalidTransformException: Unknown transformation. No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
	at org.apache.ws.security.message.WSSecSignature.addReferencesToSign(WSSecSignature.java:640)
	at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:779)
	... 24 more
Caused by: org.apache.xml.security.transforms.TransformationException: Unknown transformation. No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
Original Exception was org.apache.xml.security.transforms.InvalidTransformException: Unknown transformation. No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
	at org.apache.xml.security.transforms.Transforms.addTransform(Transforms.java:197)
	at org.apache.ws.security.message.WSSecSignature.addReferencesToSign(WSSecSignature.java:561)
	... 25 more
Caused by: org.apache.xml.security.transforms.InvalidTransformException: Unknown transformation. No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform
	at org.apache.xml.security.transforms.Transform.initializeTransform(Transform.java:336)
	at org.apache.xml.security.transforms.Transform.<init>(Transform.java:117)
	at org.apache.xml.security.transforms.Transforms.addTransform(Transforms.java:193)
	... 26 more

When I tested the same implementation with wso2mi-4.1.0, this issue is not apparent. Therefore, I believe mi 4.2.0 still needs further changes to the SAML integration flow
Thanks,
Sarindu.

wso2carbon.log

Hi Rosen,
As per your request, I'm attaching the artifacts which you can use to test this issue. Please copy the jar file to the lib directory and the car file to the carbonapps directory.
Upon deployment, you can use the below WSDL to create a SOAP request in SOAP UI.
http://localhost:8290/services/ch_suva_wsx_monitoring_platform_sap_crm_saml_v1?wsdl
artifacts.zip
Thanks,
Sarindu.

Hi All,
I have debugged the use case with SAML headers and SOAP requests. The following points were discovered during the debugging.

The said security fix for the opensaml orbit bundle had issues. We have migrated opensaml_3.3.1.wso2v4 old mi 4.1.0 to
opensaml_3.3.1.wso2v7 in new mi 4.2.0. inside the orbit bundle, there were several dependency updates due to security vulnerabilities.
By further analyzing the opensaml orbit bundles I noticed that the base opensaml update was not causing the issue, but the dependency version limitation of xml.security package causes the class not to find the issue.
That fix was also done for a security fix from the IAM team. Along the way, we folked the xmlsec from apache and ported the security fix, hence we were using the forked version of xmlsec.
When foking the xmlsec from apache we used the xmlsec version 1.5.6 instead of the 1.5.4 we had originally with the mi 4.1.0
This minor version update causes the

 Caused by: org.apache.xml.security.transforms.InvalidTransformException: Unknown transformation.
 No handler installed for URI http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security
-1.0#STR-Transform

error and was able to get it resolved once I downgrade the xmlsec version to 1.5.4.

Hence we can fix this problem by downgrading the xmlsec base version for the forked wso2-xmlsec repo.
We also need to release a new opensaml orbit bundle by increasing the lower version range for the xmlsec library.

We will update the progress of this ticket.
Adding @GDLMadushanka as he has done the initial folk for the xml-sec and currently doing the base version change.


Avoid duplicate enum value of LIST_STYLE_TYPE

Summary
This PR fixes the following bugs

[x] Avoid duplicate values in LIST_STYLE_TYPE enum

The LIST_STYLE_TYPE enum has duplicate values GURMUKHI and HEBREW like below.
https://github.com/niklasvh/html2canvas/blob/6020386bbeed60ad68e675fdcaa6220e292fd35a/src/css/property-descriptors/list-style-type.ts#L26-L29
And it makes Deno runtime (in my Fresh project) show duplicate-case warning for below codes.
https://github.com/niklasvh/html2canvas/blob/6020386bbeed60ad68e675fdcaa6220e292fd35a/src/css/types/functions/counter.ts#L461-L464

Can be tested in @cantoo/html2canvas


Support multiple kinds of value parsers

i.e. an aeson parser

Also just investigate ReadP to remove the dependency on megaparsec https://hackage.haskell.org/package/base-<IP_ADDRESS>/docs/Text-ParserCombinators-ReadP.html


Add padding in button to make it look better

I see if we can add bit padding to he left and right of the Send Message it'd be a nice idea..

PLease assign me this task to work on

I'd like to work upon this issue if this hasn't been done yet.Pls assign it to me

@muhammedanaskhan What are the updates??

Am not working on this unfortunately, sorry for it please assign to anyone else interested.

I would like to work upon this issue!

Kindly revert!

Ok @bhoomikhurana, i have assigned this issue to you.


Add link to the roadmap to ddev Readme.md

Also includes an update to the project overview verbiage and context as to why we use a roadmap, what it means, etc. Relates to issue Update readme to include a link to the roadmap and a stronger introduction..
The Problem:
An end-user visiting the project page probably doesn't realize there is a roadmap as well as the expectations around it, how to submit feature requests/issues, etc.
The Fix:
Update the readme to link to the current wiki and provide context as to what it means and how to contribute to its future.
The Test:
NA
Automation Overview:
NA
Related Issue Link(s):
#212
Release/Deployment notes:
NA

Thanks, @rfay! I'll take the feedback and modify the 2nd paragraph of the roadmap to simplify.

Added small tweaks. The main goal is achieved and any future spelling/grammar items can be addressed in subsequent PRs (probably without needing an issue). Plus, @tannerjfco is in the process of reorganizing the docs and this might cause things to change further.


EventHandler equivalent through Wasm

What would you like to be added:
EventHandler equivalent to notify updates to resources from host to wasm guest.
Why is this needed:
In current design, we passed nodes and pods to every wasm guest in every scheduling cycle.
But, actually no need to pass nodes and pods every time since not all objects get changed between each scheduling cycle.
We can always store every pod/node to all wasm guests' memory, and keep them up-to-date. Then, every wasm guest just needs to refer to those objects when needed, instead of getting them from host in every scheduling cycle, which requires overhead to marshall/unmarshall the objects.
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

/remove-lifecycle stale
/lifecycle frozen


Improve the reproducibility instructions

In preparation for the ICSE 2021 artifact track, we should improve our instructions for deploying and using the programmatic interfaces for CodeShovel.

[x] Update README.md

[x] Simplify file to make it easier to understand options for using CodeShovel
[x] Add docker-compose instructions for web service
[x] Verify docker-compose instructions for web service instructions work
[x] Add curl instructions for REST interface
[x] Verify curl instructions work
[x] Update command line instructions
[x] Verify command line instructions work

[x] Extract development instructions to Development.md
[x] Add a docker-compose.yml so this repo contains everything needed to package the web service.

Thanks for all your help with the docker bits @braxtonhall !

Thanks for all your help with the docker bits @braxtonhall !


"SliderHorizontalThumbHeight" was not found with InnerLoop for ColorPicker

Describe the bug

Message:
Exception thrown at 0x00007FFCC4B43EAC in MUXControlsTestApp.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x0000007FD5CFA518.

StackTrace:
 	KernelBase.dll!00007ffcc4b43eac()	Unknown
 	vcruntime140d_app.dll!00007ffca2698337()	Unknown
> 	Microsoft.UI.Xaml.dll!winrt::throw_hresult(const winrt::hresult result) Line 4808	C++
 	Microsoft.UI.Xaml.dll!winrt::check_hresult(const winrt::hresult result) Line 4854	C++
 	Microsoft.UI.Xaml.dll!winrt::impl::consume_Windows_UI_Xaml_IFrameworkElementOverrides<winrt::Windows::UI::Xaml::IFrameworkElementOverrides>::MeasureOverride(const winrt::Windows::Foundation::Size & availableSize) Line 1814	C++
 	Microsoft.UI.Xaml.dll!winrt::Windows::UI::Xaml::IFrameworkElementOverridesT<ColorPicker>::MeasureOverride(const winrt::Windows::Foundation::Size & availableSize) Line 13559	C++
	Microsoft.UI.Xaml.dll!winrt::impl::produce<ColorPicker,winrt::Windows::UI::Xaml::IFrameworkElementOverrides>::MeasureOverride(winrt::Windows::Foundation::Size availableSize, winrt::Windows::Foundation::Size * result) Line 7682	C++

Errors in Output window just before crash:
Exception thrown at 0x00007FFCC4B43EAC (KernelBase.dll) in MUXControlsTestApp.exe: WinRT originate error - 0x80004005 : 'Cannot find a Resource with the Name/Key SliderHorizontalThumbHeight'.
Exception thrown at 0x00007FFCC4B43EAC (KernelBase.dll) in MUXControlsTestApp.exe: WinRT originate error - 0x802B000A : 'Cannot find a Resource with the Name/Key SliderHorizontalThumbHeight [Line: 88 Position: 160]'.
Exception thrown at 0x00007FFCC4B43EAC in MUXControlsTestApp.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x0000007FD5CFA518.

Steps to reproduce the bug

Steps to reproduce the behavior:

Clone latest master
Enable InnerLoop with single
<FeatureColorPickerEnabled>true</FeatureColorPickerEnabled>
Build and run with mixed debug mode
Open color picker page

Expected behavior
No crash and working ColorPicker
Version Info
Latest master https://github.com/microsoft/microsoft-ui-xaml/commit/3834f4d238b98abf5857120387eee3a2e3da0aa4

Windows 10 version
Saw the problem?

Insider Build (20152)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context
Everything works after I added to ColorPicker style resources from below:
<Thickness x:Key="SliderTopHeaderMargin">0,0,0,4</Thickness>
    <x:Double x:Key="SliderPreContentMargin">15</x:Double>
    <x:Double x:Key="SliderPostContentMargin">15</x:Double>
    <x:Double x:Key="SliderHorizontalHeight">32</x:Double>
    <x:Double x:Key="SliderVerticalWidth">32</x:Double>
    <x:Double x:Key="SliderThumbCornerRadius">10</x:Double>
    <x:Double x:Key="SliderHorizontalThumbWidth">20</x:Double>
    <x:Double x:Key="SliderHorizontalThumbHeight">20</x:Double>
    <x:Double x:Key="SliderVerticalThumbWidth">20</x:Double>
    <x:Double x:Key="SliderVerticalThumbHeight">20</x:Double>

I also tried to make Slider as dependency for ColorPicker in FeatureArea.props, but it does nothing for me. I am new to this codebase, so I don't know how InnerLoop works internaly.

Adding
    <FeatureSliderEnabled>productOnly</FeatureSliderEnabled>

to either the innerloop file or the section @StephenLPeters linked fixes the crash. Since in the long run we should add that to this section anyway (as it fixes this issue), would you maybe like to contribute a fix for this @maxkatz6 ?

@chingucoding
I created PR https://github.com/microsoft/microsoft-ui-xaml/pull/2833


Does webpack 2.1-beta not support a profiler?

I can find documentation anywhere and it seems my usual --profile flag doesn't work any more.

Should still work?

I am facing a simialr problem, this is the output I get.
{
  "errors": [],
  "warnings": [
    "./~/jsondiffpatch/src/main.js\n48:20 Critical dependency: the request of a dependency is an expression",
    "./~/jsondiffpatch/src/main.js\n53:19 Critical dependency: the request of a dependency is an expression"
  ]
}

any update?

looks like a problem with the stats options. You didn't pass any option to the stats option, did you?

command used
webpack --config internals/webpack/webpack.prod.babel.js --profile --json > stats.json

based off https://github.com/mxstbr/react-boilerplate

https://github.com/mxstbr/react-boilerplate/blob/master/internals/webpack/webpack.base.babel.js#L85
stats: false
this disables all stat info.

it is set to false while displaying stats ... this is run on 2.1.0-beta.15
on 2.1.0-beta.22 stats.json is blank. not sure where to go from here.


XLA: specify num_partitions in xla_cpu_runtime_ParallelForkJoin

I am interested in the LLVM IR obtained by launching a Tensorflow test program with the --xla_dump_ir_to flag. In particular, I would like XLA to create a certain number of copies of a function that can run in parallel on multiple CPUs.
(I know this sounds like a support question rather than an issue, but nobody could answer me on StackOverflow until now, so I figured that maybe what I am looking for is a feature that still does not exist)
I have a test program that includes these lines
with tf.device("device:XLA_CPU:0"):
       y = tf.nn.conv2d(X, weights_tensor, strides=[1, 1, 1, 1], padding='SAME')
    sess.run(tf.global_variables_initializer())
And in the output .ll files XLA generates a call to
call void @__xla_cpu_runtime_ParallelForkJoin(i8* %6, i8* %run_options, i8** null, i8** %buffer_table, i64* %prof_counters, i32 56, i64* getelementptr inbounds ([224 x i64], [224 x i64]* @parallel_convolution_parallel_dimension_partitions, i32 0, i32 0), i32 2, i8* bitcast (void (i8*, i8*, i8**, i8**, i64*, i64*)* @parallel_convolution to i8*))
which is a good starting point.
But now I want to specify how many copies of that function I want. What I have tried up to now is to use these options
config = tf.ConfigProto()
config.device_count={"CPU": 5}
config.intra_op_parallelism_threads=5
config.inter_op_parallelism_threads=5
and they still lead to the same call, with the num_partitions argument set to 56 (number of CPUs on my machine).
Moreover, a different test program with
with tf.device("device:XLA_CPU:0"):
                y=tf.layers.max_pooling2d(inputs=x, pool_size=[3, 3], strides=3)
        sess.run(y,{x: reshaped_input_array})
does not generate any call to xla_cpu_runtime_ParallelForkJoin at all.
Is it possible to force XLA in any way to produce parallel copies of a function, and to specify how many copies?
System information

OS Platform and Distribution: Linux 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
TensorFlow installed from: source
TensorFlow version: 1.13.1
Python version: 2.7.16
Bazel version: 0.21.0
GCC version: 8.3.0

@jlebar

Is it possible to force XLA in any way to produce parallel copies of a function, and to specify how many copies?

No, exactly how XLA generates LLVM IR for a particular op is an implementation detail.
If you're interested in contributing patches to add this feature<EMAIL_ADDRESS>would be a place to start the discussion.

Is it possible to force XLA in any way to produce parallel copies of a function, and to specify how many copies?

No, exactly how XLA generates LLVM IR for a particular op is an implementation detail.
If you're interested in contributing patches to add this feature<EMAIL_ADDRESS>would be a place to start the discussion.

Is it possible to force XLA in any way to produce parallel copies of a function, and to specify how many copies?

No, exactly how XLA generates LLVM IR for a particular op is an implementation detail.
If you're interested in contributing patches to add this feature<EMAIL_ADDRESS>would be a place to start the discussion.


Release version 0.7.0

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

Comparison is base (f9f7dd4) 36.66% compared to head (d4d2845) 36.69%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #320      +/-   ##
==========================================
+ Coverage   36.66%   36.69%   +0.03%
==========================================
  Files          94       94
  Lines        6240     6240
==========================================
+ Hits         2288     2290       +2
+ Misses       3952     3950       -2

Files
Coverage Δ

...gorithms/linfa-preprocessing/src/linear_scaling.rs
45.28% <ø> (ø)

...ms/linfa-preprocessing/src/tf_idf_vectorization.rs
38.88% <ø> (ø)

algorithms/linfa-preprocessing/src/whitening.rs
51.02% <ø> (ø)

... and 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@YuhanLiin I just saw your message on the Zulip about stepping away from your maintainership of Linfa after this release. I just wanted to say thank you for all your hard work on this project over the past years; I've learned a lot from seeing your approach to code and open source, and have deeply appreciated your participation. Best of luck in your next endeavors!

Yeah it's been a great experience working on Linfa with all of you. I want to give a shoutout to @quietlychris and @bytesnake in particular for helping with maintenance. Thank you for everything.


explorerDenyList / explorerAllowList not working [bug]

Link to minimal reproducible example
<Web3Modal         projectId={projectId}         ethereumClient={ethereumClient}         explorerAllowList={[           "4622a2b2d6af1c9844944291e5e7351a6aa24cd7b23099efac1b2fd875da31a0",         ]}       />
Summary
explorerDenyList / explorerAllowList options method in web3Modal does not work, in both V1 and V2
List of related npm package versions
"@wagmi/core": "^0.10.6",
"@web3modal/ethereum": "^2.2.2",
"@web3modal/react": "^2.2.2",
"ethers": "^5.7.2",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-scripts": "5.0.1",
"wagmi": "^0.12.6",

Hey 👋
Just tried to reproduce in this example https://github.com/WalletConnect/web3modal/blob/V2/laboratory/src/pages/v1Base.tsx
Seems to be working. What issue are you facing on your end?
https://user-images.githubusercontent.com/3154053/228553009-51b025b3-9a60-4c9a-b6f2-652ebe60e653.mov

c57ca95b47569778a828d19178114f4db188b89b763c899ba0be274e97267d96, metamask does not seem to work


mxbai-embed-large embedding not consistent with original paper

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Error Message and Stack Trace (if applicable)
No response
Description
THe test is not working well.
It works with ollama directly but not with ollama under Langchain.
Also, it works well with Llamafile under Langchain.
The issue seems to be the same than here :  https://github.com/ollama/ollama/issues/4207
Why is it not fixed with langchain?
System Info
System Information

OS:  Darwin
OS Version:  Darwin Kernel Version 23.5.0: Wed May  1 20:13:18 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6030
Python Version:  3.10.4 (main, Mar 31 2022, 03:37:37) [Clang 12.0.0 ]

Package Information

langchain_core: 0.2.20
langchain: 0.2.8
langchain_community: 0.2.7
langsmith: 0.1.88
langchain_chroma: 0.1.1
langchain_text_splitters: 0.2.2

ollama : 0.2.1
Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langgraph
langserve

Actually, the issue is that by default langchain add an option : embed_instruction  embed_instruction: str = "passage: "
And it kills everything with 'mxbai-embed-large'.
So to pass the test we need to add this when declaring model :
ollama_emb = OllamaEmbeddings(model="mxbai-embed-large", embed_instruction="")

I don't know if it is a good example to be actually accurate.
What do you think that we need to use?
I am going to try


ArtifactDataWriter should set appropriate file metadata

ArtifactDataWriter should set appropriate file metadata/attributes when saving files to the tar archive (e.g., owner, permissions, etc.). I'm not sure exactly what those should be; see TarInfo for the possible file attributes that can be set.

Perhaps a pseudo qiime user with 777 as permissions? We definitely don't want to leak system information in these artifacts.

What about 666 for files and 777 for directories? 777 makes sense for
executable files.
I can see benefit in 444 for some files...
On Mar 8, 2016 10:21 AM, "Evan Bolyen"<EMAIL_ADDRESS>wrote:

Perhaps a pseudo qiime user with 777 as permissions? We definitely don't
want to leak system information in these artifacts.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiime2/issues/14#issuecomment-193899521.

I'm not 100% sure we need to worry about this in qiime2. Should this be handled by the tools using qiime2?

This is QIIME 2's responsibility because it defines and implements the .qtf format, and we don't want to leak system information in artifacts. Note that we're talking about file permissions for files that are added to the tar archive.

Closing as new .qza/.qzv archive format is ZIP64-based which doesn't have file metadata like this to set.


WIP: Normal calculation

Merging this now and leaving the two remaining tasks from #262 for separate PRs.


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

package.json

chore(deps): add ^3.10.0 remove ^3.9.0 (devDependencies.ava)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question: If clearable is true, selectorIcon is not shown. How to keep both?

I want to show selectorIcon when nothing selected, then if user select something use clearable icon.

In my opinion it does not make sense to keep both, either the select is not yet filled, its a bit weird UX to have both icons, but whats your use case exactly? I can accept a PR if you are willing to drop it :p

Could you please tell me what are the steps of your installation process? Mine has no style.#103