text:
Handle version aliases within an lts directory

In combination with https://github.com/nodenv/nodenv-aliases/pull/25, this PR should allow for the ability to make and view aliases in the form of lts/*. This should increase the compatibility of auto-switching to nvm-style versions (e.g. lts/carbon).

@jasonkarns what are your thoughts on adding nvm-like aliases with this PR (along with https://github.com/nodenv/nodenv-aliases/pull/25)?

@jamesacarr i'm mostly 👍 . I'd like to get some tests added to cover the new feature.

What would your thoughts be on an approach that changed nodenv's handling of the lts/* version name, instead?
That is, instead of allowing/requiring lts codenames to be under an lts subdirectory, they were left as top level (ie NODENV_ROOT/versions/argon). And the nodenv-version-name command would translate lts/argon to just argon ? Have you already investigated that approach or have any idea of the feasibility on that side?

I did a little bit of testing of versions in subdirectories, and things seem to sorta work OOTB.
Given a nodenv installation that uses nodenv-aliases and a smattering of node versions, one could end up with versions like this: (versions culled for brevity)
nodenv versions
  system
  8
  8.9
  8.9.1
  8.15
  8.15.0
  10
  10.8
  10.8.0
  12
  12.0
  12.0.0

$ mkdir -p `nodenv root`/versions/lts
$ cd `nodenv root`/versions/lts
$ ln -s ../10 dubnium
$ nodenv shell lts/dubnium
$ node -v
v10.8.0

With this setup, ones .node-version file will successfully activate an lts/* alias.
The downside, as this PR addresses, is that the lts subdirectory is listed as a node version, rather than listing the individual versions within it.
Some thoughts and question:
How important is it for nodenv versions to have special handling for lts/ under versions/? What benefits does it offer, considering that current behavior "works" for the purpose of version activation and switching? What about the concern for scenarios where lts is intended to be an actual version and not a subdirectory? Are there other special subdirectories we would want to support this treatment in the future? How much of a concern is it, that we would essentially be reserving certain directory names that could not be used as version names?

Playing around with another option: using find to get all directories that contain a bin directory. (Only checks first 2 levels)
find -L $(nodenv root)/versions -maxdepth 3 -name bin |
  sed -e s:^"$(nodenv root)/versions/\(.*\)/bin":\\1:

Pros

doesn't make lts a magic string, so users could group nodes into any directory.
doesn't make lts a reserved name so a user could still use lts as a literal node version name. (this PR makes lts verboten)

Cons

requires invoking a utility (but versions isn't in critical path to invoking utilities so impact is low)
potential cross-platform issues with find (gnu vs bsd for instance)
somewhat brittle in that node installs must now contain a bin/ directory at their top level. (though this is already a practical requirement thanks to nodenv-which)

Related to: https://github.com/rbenv/rbenv/pull/1156 though we've specifically allowed / in version names when backporting that fix from rbenv

Any chance to see this merged?

I'm still 👍 to merge but tests are a pre-req.
ideally, i'd still prefer to refactor to something as mentioned here: https://github.com/nodenv/nodenv/pull/118#issuecomment-550406733 such that lts/ isn't a magic, hardcoded exception. But I'd merge as-is if tests are added.

@jamesacarr I added tests for this functionality in https://github.com/lumaxis/nodenv/commit/15e9eac5b442aa5fb4ccce111ed55c785fe8234c
Feel free to cherry-pick my commit into your branch so @jasonkarns can merge this 🙂
I've also started playing with the refactoring you suggested, @jasonkarns, but I'd like to move that to a separate PR preferrably.

@lumaxis you can also open a PR with jamesacarr:master has the base branch so the tests could be merged in directly via github. (Depending on how this PR was opened, I may be able to pull them in here myself.)

@jasonkarns Opened a separate PR against this repo instead since I'm not sure how active @jamesacarr is here

authors: jamesacarr jasonkarns lumaxis romansavrulin

repo: nodenv/nodenv


text:
[1.20.1-4.0.2] The configuration option "invulnerable" does not take full effect.

According to the description in custom-bingos.md, the "invulnerable" option allows the player to resist most damage and automatically restore the player's Hunger Value.
However, when I actually played the game, I found that this option did not seem to be fully effective, but only helped me to automatically restore my Hunger Value, and did not make me immune to any other damage.
Mod version : 4.0.2
The logs :
https://mclo.gs/QZXpsYH
The setting I use :
{
  "game": {
    "win_condition": "bongo.default",
    "invulnerable": true,
    "pvp": false,
    "friendly_fire": false,
    "time": "unlimited",
    "consume_items": false,
    "lock_task_on_death": false,
    "teleports_per_team": 0,
    "leaderboard": false,
    "lockout": false
  },
  "level": {
    "teleporter": "bongo.default",
    "teleport_radius": 10000
  },
  "equipment": {
    "inventory": [],
    "backpack": [
      {
        "item": "minecraft:stone_sword"
      },
      {
        "item": "minecraft:wooden_sword"
      }
    ],
    "emergency": [],
    "offhand": {
      "item": "minecraft:air",
      "count": 0
    },
    "head": {
      "item": "minecraft:air",
      "count": 0
    },
    "chest": {
      "item": "minecraft:air",
      "count": 0
    },
    "legs": {
      "item": "minecraft:air",
      "count": 0
    },
    "feet": {
      "item": "minecraft:air",
      "count": 0
    }
  }
}

Tested with only Bongo and LibX loaded and the issue still exists

Fixed in 1.20.1-4.0.3.

source: gharchive/issue

authors: Junnaturefox noeppi-noeppi

repo: noeppi-noeppi/Bongo

license_type: permissive

license_source: github-api


text:
network.data messages not shown

I thought it was my runtime but I just checked noflo-nodejs and I get the same result, network.begingroup  and network.endgroup both show in the debug panel when the edge is selected but the network.data is not, I tried this with the lastest noflo-ui stable release and master and I get the same result.
Is it a bug or do I need to do something for these to appear ?
Here is what the noflo-nodejs sent:
{
  "protocol": "network",
  "command": "begingroup",
  "payload": {
    "id": "filesystem/ReadFile_vb059() OUT -> IN core/Output_p8j8a()",
    "graph": "main",
    "src": {
      "node": "filesystem/ReadFile_vb059",
      "port": "out"
    },
    "tgt": {
      "node": "core/Output_p8j8a",
      "port": "in"
    },
    "group": "/tmp/flo.txt"
  }
}

{
  "protocol": "network",
  "command": "data",
  "payload": {
    "id": "filesystem/ReadFile_vb059() OUT -> IN core/Output_p8j8a()",
    "graph": "main",
    "src": {
      "node": "filesystem/ReadFile_vb059",
      "port": "out"
    },
    "tgt": {
      "node": "core/Output_p8j8a",
      "port": "in"
    },
    "data": "yo\n"
  }
}

{
  "protocol": "network",
  "command": "endgroup",
  "payload": {
    "id": "filesystem/ReadFile_vb059() OUT -> IN core/Output_p8j8a()",
    "graph": "main",
    "src": {
      "node": "filesystem/ReadFile_vb059",
      "port": "out"
    },
    "tgt": {
      "node": "core/Output_p8j8a",
      "port": "in"
    },
    "group": "/tmp/flo.txt"
  }
}

And what I see is:
</tmp/flo.txt>
<//tmp/flo.txt>

Can confirm, not seeing data packets:

With noflo/noflo-runtime#88 we now get packet data as expected

That needs to be merged, released, and we need to bump the dep in noflo-ui

Fixed in 0.12.2

thanks :)
I tried to look at it but this project is really daunting, there are so many different libraries...

authors: bergie schmurfy

repo: noflo/noflo-ui

license: mit

license_source: bigquery


text:
LuaPushable does not impl for Vec

The custom completion list function require a type Function<(String, String, usize), Vec<String>>: https://docs.rs/nvim-oxi/latest/nvim_oxi/types/enum.CommandComplete.html#variant.CustomList. However the trait LuaPushable doesn't implemented for Vec, so I can't create a new function that have return type Result<Vec<T>>.
121 |     let completion = Function::from_fn(generate_completion);
    |                      ^^^^^^^^^^^^^^^^^ the trait `LuaPushable` is not implemented for `Vec<std::string::String>`

My function signature: fn generate_completion(arguments: (String, String, usize)) -> Result<Vec<String>>
Build with rev=e5c34c7, which is currently the HEAD of the git repo.

done 86280aa35bc919334d227bc722c7ca92a3279cec

license: MIT


text:
chore: allow omitting the --name flag in nargo init

Problem
Resolves #3007
Additional Context
PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

cc @TomAFrench, should be good for re-review(?)

source: gharchive/pull-request

repo: noir-lang/noir


text:
chore: include durations of tracing spans in log output

Description
Problem*
Resolves
Summary*
This PR updates the filter on span events so that we get the duration of the span being printed.
Example output:
2024-03-27T17:18:17.207634Z TRACE check_crate{crate_id=Root(1) deny_warnings=false disable_macros=false}: noirc_driver: new
2024-03-27T17:18:17.238046Z TRACE check_crate{crate_id=Root(1) deny_warnings=false disable_macros=false}: noirc_driver: close time.busy=30.4ms time.idle=39.3µs
2024-03-27T17:18:17.238075Z TRACE compile_no_check{function_name="main"}: noirc_driver: new
2024-03-27T17:18:17.238081Z TRACE compile_no_check{function_name="main"}:monomorphize: noirc_frontend::monomorphization: new
2024-03-27T17:18:17.238180Z TRACE compile_no_check{function_name="main"}:monomorphize: noirc_frontend::monomorphization: close time.busy=95.5µs time.idle=3.56µs
2024-03-27T17:18:17.238217Z TRACE compile_no_check{function_name="main"}:create_circuit: noirc_evaluator::ssa: new
2024-03-27T17:18:17.238234Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation: noirc_evaluator::ssa: new
2024-03-27T17:18:17.238458Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:defunctionalize: noirc_evaluator::ssa::opt::defunctionalize: new
2024-03-27T17:18:17.238476Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:defunctionalize: noirc_evaluator::ssa::opt::defunctionalize: close time.busy=12.5µs time.idle=6.24µs
2024-03-27T17:18:17.238482Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:remove_paired_rc: noirc_evaluator::ssa::opt::rc: new
2024-03-27T17:18:17.238499Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:remove_paired_rc: noirc_evaluator::ssa::opt::rc: close time.busy=7.51µs time.idle=9.60µs
2024-03-27T17:18:17.238504Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:inline_functions: noirc_evaluator::ssa::opt::inlining: new
2024-03-27T17:18:17.238572Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:inline_functions: noirc_evaluator::ssa::opt::inlining: close time.busy=64.0µs time.idle=3.42µs
2024-03-27T17:18:17.238578Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:mem2reg: noirc_evaluator::ssa::opt::mem2reg: new
2024-03-27T17:18:17.238668Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:mem2reg: noirc_evaluator::ssa::opt::mem2reg: close time.busy=83.6µs time.idle=5.48µs
2024-03-27T17:18:17.238675Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:evaluate_assert_constant: noirc_evaluator::ssa::opt::assert_constant: new
2024-03-27T17:18:17.238682Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:evaluate_assert_constant: noirc_evaluator::ssa::opt::assert_constant: close time.busy=3.01µs time.idle=4.07µs
2024-03-27T17:18:17.238688Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:unroll_loops: noirc_evaluator::ssa::opt::unrolling: new
2024-03-27T17:18:17.387314Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:unroll_loops: noirc_evaluator::ssa::opt::unrolling: close time.busy=149ms time.idle=5.25µs
2024-03-27T17:18:17.387343Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:simplify_cfg: noirc_evaluator::ssa::opt::simplify_cfg: new
2024-03-27T17:18:17.393664Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:simplify_cfg: noirc_evaluator::ssa::opt::simplify_cfg: close time.busy=6.31ms time.idle=6.11µs
2024-03-27T17:18:17.393681Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:flatten_cfg: noirc_evaluator::ssa::opt::flatten_cfg: new
2024-03-27T17:18:22.881528Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:flatten_cfg: noirc_evaluator::ssa::opt::flatten_cfg: close time.busy=5.49s time.idle=9.78µs
2024-03-27T17:18:22.881558Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:remove_bit_shifts: noirc_evaluator::ssa::opt::remove_bit_shifts: new
2024-03-27T17:18:22.939961Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:remove_bit_shifts: noirc_evaluator::ssa::opt::remove_bit_shifts: close time.busy=58.4ms time.idle=7.86µs
2024-03-27T17:18:22.939994Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:mem2reg: noirc_evaluator::ssa::opt::mem2reg: new
2024-03-27T17:18:39.127772Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:mem2reg: noirc_evaluator::ssa::opt::mem2reg: close time.busy=16.2s time.idle=7.82µs
2024-03-27T17:18:39.127802Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:fold_constants: noirc_evaluator::ssa::opt::constant_folding: new
2024-03-27T17:18:42.247447Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:fold_constants: noirc_evaluator::ssa::opt::constant_folding: close time.busy=3.12s time.idle=6.51µs
2024-03-27T17:18:42.247480Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:fold_constants_using_constraints: noirc_evaluator::ssa::opt::constant_folding: new
2024-03-27T17:18:46.333707Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:fold_constants_using_constraints: noirc_evaluator::ssa::opt::constant_folding: close time.busy=4.09s time.idle=10.1µs
2024-03-27T17:18:46.333739Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:dead_instruction_elimination: noirc_evaluator::ssa::opt::die: new
2024-03-27T17:18:47.352043Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation:dead_instruction_elimination: noirc_evaluator::ssa::opt::die: close time.busy=1.02s time.idle=8.20µs
2024-03-27T17:18:47.366309Z TRACE compile_no_check{function_name="main"}:create_circuit:find_last_array_uses: noirc_evaluator::ssa::opt::array_use: new
2024-03-27T17:18:47.371971Z TRACE compile_no_check{function_name="main"}:create_circuit:find_last_array_uses: noirc_evaluator::ssa::opt::array_use: close time.busy=5.64ms time.idle=18.0µs
2024-03-27T17:18:47.371988Z TRACE compile_no_check{function_name="main"}:create_circuit:into_acir: noirc_evaluator::ssa::acir_gen: new
2024-03-27T17:18:54.310129Z TRACE compile_no_check{function_name="main"}:create_circuit:into_acir: noirc_evaluator::ssa::acir_gen: close time.busy=6.94s time.idle=8.21µs
2024-03-27T17:18:54.310156Z TRACE compile_no_check{function_name="main"}:create_circuit:ssa_generation: noirc_evaluator::ssa: close time.busy=30.1s time.idle=6.94s
2024-03-27T17:18:54.311567Z TRACE compile_no_check{function_name="main"}:create_circuit:optimize_acir: acvm::compiler::optimizers: new
2024-03-27T17:18:54.311580Z  INFO compile_no_check{function_name="main"}:create_circuit:optimize_acir: acvm::compiler::optimizers: Number of opcodes before: 8323
2024-03-27T17:18:54.312564Z  INFO compile_no_check{function_name="main"}:create_circuit:optimize_acir: acvm::compiler::optimizers: Number of opcodes after: 8323
2024-03-27T17:18:54.312571Z TRACE compile_no_check{function_name="main"}:create_circuit:optimize_acir: acvm::compiler::optimizers: close time.busy=995µs time.idle=9.56µs
2024-03-27T17:18:54.313322Z TRACE compile_no_check{function_name="main"}:create_circuit:update_acir: noirc_errors::debug_info: new
2024-03-27T17:18:54.314192Z TRACE compile_no_check{function_name="main"}:create_circuit:update_acir: noirc_errors::debug_info: close time.busy=863µs time.idle=6.04µs
2024-03-27T17:18:54.314446Z TRACE compile_no_check{function_name="main"}:create_circuit: noirc_evaluator::ssa: close time.busy=37.1s time.idle=4.23µs
2024-03-27T17:18:54.315015Z TRACE compile_no_check{function_name="main"}: noirc_driver: close time.busy=37.1s time.idle=4.54µs
2024-03-27T17:18:54.320236Z TRACE optimize_acir: acvm::compiler::optimizers: new
2024-03-27T17:18:54.320252Z  INFO optimize_acir: acvm::compiler::optimizers: Number of opcodes before: 8323
2024-03-27T17:18:54.321141Z  INFO optimize_acir: acvm::compiler::optimizers: Number of opcodes after: 8323
2024-03-27T17:18:54.321147Z TRACE optimize_acir: acvm::compiler::optimizers: close time.busy=902µs time.idle=9.38µs
2024-03-27T17:18:54.321156Z TRACE transform_acir{expression_width=Bounded { width: 3 }}: acvm::compiler::transformers: new
2024-03-27T17:18:54.322544Z TRACE transform_acir{expression_width=Bounded { width: 3 }}: acvm::compiler::transformers: close time.busy=1.38ms time.idle=4.58µs
2024-03-27T17:18:54.323134Z TRACE update_acir: noirc_errors::debug_info: new
2024-03-27T17:18:54.323928Z TRACE update_acir: noirc_errors::debug_info: close time.busy=789µs time.idle=5.42µs

Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Does anyone use these traces? I find them completely unreadable

I find them pretty useful plus it allows us to keep in logging without affecting the user or having lots of boolean flags exposed to the CLI. The filtering could be improved however.

authors: TomAFrench jfecher


text:
Update to Noir v0.31.0

### Prerequisite
- [ ] https://github.com/noir-lang/noir/pull/5072
- [ ] https://github.com/noir-lang/noir/pull/5061

Following https://github.com/noir-lang/noir/pull/5072, proving and verification workflow would no longer rely on NoirJS but proving backends' JS packages (e.g. bb.js) instead.
The PR includes updates to the https://noir-lang.org/docs/tutorials/noirjs_app/ doc page.
As this repo is linked and used as the basis of that doc page, we should update this as a part of the doc page update.

This should go along with updating the corresponding docs page

authors: Savio-Sou critesjosh

repo: noir-lang/tiny-noirjs-app


text:
🛑 mastodonczech.cz is down

In b7873e0, mastodonczech.cz (https://mastodonczech.cz/nodeinfo/2.0) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodonczech.cz is back up in 69d1f6f.

repo: nolog-it/mastodon-uptime


text:
Update LanguageServer submodule to v1.0.0 and SymbolServer to v1.0.1

This will at least allow the LanguageServer to work with Julia 1.3

Works for me, thank you! How did you pick the submodule versions? They are almost all different from the latest tags/master from julia-vscode/julia-vscode.

I just used the [deps] in Project.toml for LanguageServer#v1.0.0.
Are you sure you set (setq lsp-julia-default-environment "~/.julia/environments/v1.0")? I was able to get it to work with Julia v1.0.5 (current LTS).

I unset lsp-julia-default-environmnet. I will have to try again then.

Whoops, my mistake! The reason this was working on Julia v1.0 was due to the following (monkey-) patch for Julia v1.4.
diff --git a/src/symbols.jl b/src/symbols.jl
index f74f85c..1b2dc1a 100644
--- a/src/symbols.jl
+++ b/src/symbols.jl
@@ -212,7 +212,7 @@ function cache_package(c::Pkg.Types.Context, uuid::UUID, depot::Dict, env_path =
         if path(pe) isa String
             env_path = path(pe)
             Pkg.API.activate(env_path)
-        elseif !is_stdlib(c, uuid) && ((Pkg.API.dir(pe_name) isa String) && !isempty(Pkg.API.dir(pe_name)))
+        elseif ((Pkg.API.dir(pe_name) isa String) && !isempty(Pkg.API.dir(pe_name)))
             env_path = Pkg.API.dir(pe_name)
             Pkg.API.activate(env_path)
         end

Perhaps we can compile backports and fixes until LanguageServer.jl is running properly on v2.0.0?

Feel free to do it, I currently don't have the capacity to do anything more complex than the current lsp-julia.

authors: AlexLewandowski gdkrmr

repo: non-Jedi/lsp-julia


text:
Crash with my modpack

https://pastebin.com/rMkkSXxH

Yeah looks like some sort of compatibility issue, doesn't look like Ender Trigon is doing anything wrong. What other mods do you have installed?

Ok, I'll try to list the latest mods I added as much as I can(I have about 418 mods):
recipes library
dynamical compass
forbidden arcanus
charms
skill cloaks
epic knights
totw modded
travelers backpack
philips ruins
alchemy lib
chemy lib
aeroblender
sculkhorde
alchemistry
ancient manuscripts
recruits

I don't think I'll be able to diagnose the problem with that amount of mods lol. You'll have to go through them and figure out the culprit. I'd recommend looking for mods that may modify the Ender Dragon in any form/capacity.

Hi, so from other sources it turns out there's something genuinely wrong with Ender Trigon itself, specifically for the 1.19.4 version.
According to some other people I mentioned this problem to, it has a very breaking change to the vanilla code.
Something about it wanting to make the dragon fight creation method private when it's not because you can't reduce methods' visibility
this isn't a compatibility error

I meant to get back to you on CurseForge but I forgot, this is a more appropriate place anyway
This is the method in question:

That method is directly from the normal ender dragon, and is private. This is the mixin overwrite the mod uses:

This method copies the visiblity of the vanilla one. If I'm not mistaken I shouldn't be reducing the visiblity of the method at all
What is interesting however is the forge bot flags that method as being public, so I could very well be reducing the visibility (something could've changed on either Minecraft's end of Forge's) without my knowing

Have you tried running Ender Trigon by itself to see if the issue persists?

Ok so I tried to use Ender Trigon by itself and it did work. I then decided to put the mods from my modpack one by one until I reach a point where it doesn't work again. This log is the result, can you please figure out some stuff? Thank you.
https://pastebin.com/JTe15bG0

What was the mod that you put in that caused this crash report?

Based on my testing it seemed to be a mod called Cloud Rider, which btw is a mod that depends on Geckolib.

Interesting. I'd report the issue to them then, since there shouldn't be anything wrong on my end (unless if there is something on my end, which could totally be the case)


text:
升级到 0.15.3 版本后, 打包报错

降到 0.15.2 版本后解决

`

kml_admin@1.0.0 build
vite build

vite:config bundled config file loaded in 180.19ms +0ms
vite:config using resolved config: {
vite:config   build: {
vite:config     target: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
vite:config     cssTarget: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
vite:config     outDir: 'dist',
vite:config     assetsDir: 'assets',
vite:config     assetsInlineLimit: 4096,
vite:config     cssCodeSplit: true,
vite:config     sourcemap: false,
vite:config     rollupOptions: {},
vite:config     minify: 'esbuild',
vite:config     terserOptions: {},
vite:config     write: true,
vite:config     emptyOutDir: null,
vite:config     copyPublicDir: true,
vite:config     manifest: false,
vite:config     lib: false,
vite:config     ssr: false,
vite:config     ssrManifest: false,
vite:config     ssrEmitAssets: false,
vite:config     reportCompressedSize: true,
vite:config     chunkSizeWarningLimit: 1024,
vite:config     watch: null,
vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] },
vite:config     modulePreload: { polyfill: true },
vite:config     cssMinify: true
vite:config   },
vite:config   resolve: {
vite:config     mainFields: [ 'module', 'jsnext:main', 'jsnext' ],
vite:config     browserField: true,
vite:config     conditions: [],
vite:config     extensions: [
vite:config       '.mjs',  '.js',
vite:config       '.mts',  '.ts',
vite:config       '.jsx',  '.tsx',
vite:config       '.json'
vite:config     ],
vite:config     dedupe: [ 'vue' ],
vite:config     preserveSymlinks: false,
vite:config     alias: [
vite:config       [Object], [Object],
vite:config       [Object], [Object],
vite:config       [Object], [Object],
vite:config       [Object], [Object],
vite:config       [Object], [Object],
vite:config       [Object], [Object],
vite:config       [Object], [Object]
vite:config     ]
vite:config   },
vite:config   css: { preprocessorOptions: { scss: [Object] } },
vite:config   plugins: [
vite:config     'vite:build-metadata',
vite:config     'vite:watch-package-data',
vite:config     'vite:pre-alias',
vite:config     'alias',
vite:config     'vite:modulepreload-polyfill',
vite:config     'vite:resolve',
vite:config     'vite:html-inline-proxy',
vite:config     'vite:css',
vite:config     'vite:esbuild',
vite:config     'vite:json',
vite:config     'vite:wasm-helper',
vite:config     'vite:worker',
vite:config     'vite:asset',
vite:config     'vite:vue',
vite:config     'vite:vue-jsx',
vite:config     'vite-plugin-cdn2:presetModule',
vite:config     'vite:wasm-fallback',
vite:config     'vite:define',
vite:config     'vite:css-post',
vite:config     'vite:build-html',
vite:config     'vite:worker-import-meta-url',
vite:config     'vite:asset-import-meta-url',
vite:config     'vite:force-systemjs-wrap-complete',
vite:config     'commonjs',
vite:config     'vite:data-uri',
vite:config     'vite:dynamic-import-vars',
vite:config     'vite:import-glob',
vite:config     'vite-plugin-cdn2:transform',
vite:config     'vite:build-import-analysis',
vite:config     'vite:esbuild-transpile',
vite:config     'vite:terser',
vite:config     'vite:reporter',
vite:config     'vite:load-fallback'
vite:config   ],
vite:config   server: {
vite:config     preTransformRequests: true,
vite:config     host: true,
vite:config     port: 9778,
vite:config     open: true,
vite:config     proxy: { '/adminKml': [Object], '/prdAdminKml': [Object] },
vite:config     sourcemapIgnoreList: [Function: isInNodeModules],
vite:config     middlewareMode: false,
vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
vite:config   },
vite:config   optimizeDeps: {
vite:config     disabled: 'build',
vite:config     force: undefined,
vite:config     esbuildOptions: { preserveSymlinks: false }
vite:config   },
vite:config   define: { VUE_OPTIONS_API: true, VUE_PROD_DEVTOOLS: false },
vite:config   ssr: {
vite:config     format: 'esm',
vite:config     target: 'node',
vite:config     external: [],
vite:config     optimizeDeps: { disabled: true, esbuildOptions: [Object] }
vite:config   },
vite:config   esbuild: { jsxDev: false, include: /.ts$/ },
vite:config   configFile: '/Users/nailao/work/kml_admin/vite.config.ts',
vite:config   configFileDependencies: [ '/Users/nailao/work/kml_admin/vite.config.ts' ],
vite:config   inlineConfig: {
vite:config     root: undefined,
vite:config     base: undefined,
vite:config     mode: undefined,
vite:config     configFile: undefined,
vite:config     logLevel: undefined,
vite:config     clearScreen: undefined,
vite:config     optimizeDeps: { force: undefined },
vite:config     build: {}
vite:config   },
vite:config   root: '/Users/nailao/work/kml_admin',
vite:config   base: '/',
vite:config   rawBase: '/',
vite:config   publicDir: '/Users/nailao/work/kml_admin/public',
vite:config   cacheDir: '/Users/nailao/work/kml_admin/node_modules/.vite',
vite:config   command: 'build',
vite:config   mode: 'production',
vite:config   isWorker: false,
vite:config   mainConfig: null,
vite:config   isProduction: true,
vite:config   preview: {
vite:config     port: undefined,
vite:config     strictPort: undefined,
vite:config     host: true,
vite:config     https: undefined,
vite:config     open: true,
vite:config     proxy: { '/adminKml': [Object], '/prdAdminKml': [Object] },
vite:config     cors: undefined,
vite:config     headers: undefined
vite:config   },
vite:config   envDir: '/Users/nailao/work/kml_admin',
vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
vite:config   assetsInclude: [Function: assetsInclude],
vite:config   logger: {
vite:config     hasWarned: false,
vite:config     info: [Function: info],
vite:config     warn: [Function: warn],
vite:config     warnOnce: [Function: warnOnce],
vite:config     error: [Function: error],
vite:config     clearScreen: [Function: clearScreen],
vite:config     hasErrorLogged: [Function: hasErrorLogged]
vite:config   },
vite:config   packageCache: Map(1) {
vite:config     'fnpd_/Users/nailao/work/kml_admin' => {
vite:config       dir: '/Users/nailao/work/kml_admin',
vite:config       data: [Object],
vite:config       hasSideEffects: [Function: hasSideEffects],
vite:config       webResolvedImports: {},
vite:config       nodeResolvedImports: {},
vite:config       setResolvedCache: [Function: setResolvedCache],
vite:config       getResolvedCache: [Function: getResolvedCache]
vite:config     },
vite:config     set: [Function (anonymous)]
vite:config   },
vite:config   createResolver: [Function: createResolver],
vite:config   worker: {
vite:config     format: 'iife',
vite:config     plugins: [
vite:config       'vite:build-metadata',
vite:config       'vite:watch-package-data',
vite:config       'vite:pre-alias',
vite:config       'alias',
vite:config       'vite:modulepreload-polyfill',
vite:config       'vite:resolve',
vite:config       'vite:html-inline-proxy',
vite:config       'vite:css',
vite:config       'vite:esbuild',
vite:config       'vite:json',
vite:config       'vite:wasm-helper',
vite:config       'vite:worker',
vite:config       'vite:asset',
vite:config       'vite:wasm-fallback',
vite:config       'vite:define',
vite:config       'vite:css-post',
vite:config       'vite:build-html',
vite:config       'vite:worker-import-meta-url',
vite:config       'vite:asset-import-meta-url',
vite:config       'vite:force-systemjs-wrap-complete',
vite:config       'commonjs',
vite:config       'vite:data-uri',
vite:config       'vite:worker-post',
vite:config       'vite:dynamic-import-vars',
vite:config       'vite:import-glob',
vite:config       'vite:build-import-analysis',
vite:config       'vite:esbuild-transpile',
vite:config       'vite:terser',
vite:config       'vite:load-fallback'
vite:config     ],
vite:config     rollupOptions: {},
vite:config     getSortedPlugins: [Function: getSortedPlugins],
vite:config     getSortedPluginHooks: [Function: getSortedPluginHooks]
vite:config   },
vite:config   appType: 'spa',
vite:config   experimental: { importGlobRestoreExtension: false, hmrPartialAccept: false },
vite:config   getSortedPlugins: [Function: getSortedPlugins],
vite:config   getSortedPluginHooks: [Function: getSortedPluginHooks]
vite:config } +3s
vite v4.5.1 building for production...
transforming (1) index.html  vite:esbuild 2593.07ms tsconfck init /Users/nailao/work/kml_admin +0ms
transforming (11) node_modules/_nprogress@0.2.0@nprogress/nprogress.js  vite:resolve 0.62ms @/assets/scss/theme.scss -> /Users/nailao/work/kml_admin/src/assets/scss/theme.scss +0ms
vite:resolve 0.42ms @/assets/scss/theme.scss -> /Users/nailao/work/kml_admin/src/assets/scss/theme.scss +0ms
vite:resolve 5.96ms element-plus/theme-chalk/src/common/var.scss -> /Users/nailao/work/kml_admin/node_modules/_element-plus@2.4.2@element-plus/theme-chalk/src/common/var.scss +19ms
transforming (34) src/views/welcome/welcome.vuethread '' panicked at crates/core/src/parser.rs:52:40:
failed to parse module: Error { error: (Span { lo: BytePos(31), hi: BytePos(32), ctxt: #0 }, TS1109) }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
`

OK 我会尽快进行修复

@nailaojiang 0.15.4 已经发布。 0.15.3 已废弃。

authors: nailaojiang nonzzz

repo: nonzzz/vite-plugin-cdn


text:
Error messages need to be corrected for account creation-GIT must be a number

Environment info

NooBaa Version: noobaa-core-5.15.0-20231207-master.el8.x86_64.rpm
Platform: standalone

Actual behavior
node src/cmd/manage_nsfs account add --name noobaa1 --email noobaa@gmail.com --new_buckets_path /ibm/fs1/test --uid 1 --gid d1 --access_key 22w3 --secret_key 2w34 2>/dev/null
Error: GIT must be a number
Expected behavior
Error: Invalid gid. gid must be a number
Steps to reproduce

More information - Screenshots / Logs / Other output

@ramya-c3 adding request validation - should be fixed with https://github.com/noobaa/noobaa-core/pull/7568

repo: noobaa/noobaa-core


text:
Remove possibility to use go back button as it messes up state

Remove functionality of backPress since it is buggy

I would say quick fix. The backPress is not a critical function so it's better to just remove it in the worst case.
I think the solution would be to trigger handleFlowResultAsync if you are in the first screen of reset password flow (before email verification) to trigger a change in the uri reference which appears to be missing


text:
Use dotenv to set up environment variables

In preparation for adding some new features, I'd like to be able to run tests against my own credentials.  Pulling in https://github.com/bkeepers/dotenv will make it easier to swap out credentials in an .env file.
Should we perhaps rename to .env.default and require people running tests to either copy the file to .env or provide their own credentials?  This would of course go in the Readme.

This is a great addition, thanks for taking the time to do it.
I like your idea of setting up the .env.default
In addition, I think It would be nice to have an .env.test file so the tests would run 'out of the box'.
What are your thoughts?

Hi @szich -
I've added the .env.default as well as moved the credentials into .env.test.
Upon first run of rake test it will copy .env.test over to .env and Dotenv will load as usual.  Subsequent runs will respect the presence of .env.
I've then added .env to .gitignore so that developers can modify .env with their own credentials without fear of them getting accidentally committed to the repo.
I've also added a section to the README titled "Running Tests".
Let me know what you think.

Looks great, thanks!

Thanks for the quick merge!

authors: alexagranov szich


text:
Fix: False negative in prefer-message-ids rule

In some rules, context is passed to functions that eventually call context.report(), like no-duplicate-imports or padding-lines-between-statements, and that will prevent this existing rule from flagging such instances of context.report({ message: ... });.
So in addition to flagging that, we should also flag when rules are simply missing meta.messages, as all rules using message IDs should have at least one violation message defined in that object.
This will unblock this PR: https://github.com/eslint/eslint/pull/14841#issuecomment-888645170
CC: @mdjermanovic

released in v3.5.3. 🍺

authors: aladdin-add bmish


text:
이슈 체계화

배경
혼자서 여러 이슈를 관리하기 힘듦. 그렇다보니, 이슈의 처리 속도가 늦어짐.
또한, 작업 진척 현황을 명확하게 알기 힘들어, 커뮤니티의 오픈소스 기여 참여가 적극적으로 이루어지지 못함.
TODO

이슈를 체계화할 수 있는 방법을 검토해야 함
-> 이슈 템플릿, 깃허브 프로젝트 등 깃허브 이외에 의존성이 없는 방안이 가장 좋음.
but, 다른 방안이 더 문제를 효과적으로 해결할 수 있다면, 해결하기 위한 프로덕트를 새로 만들거나 외부 서비스에 의존할 수 있음.

사용해보기 위해, Github Project를 활성화하였음.
대부분의 작업이 가능할 것으로 보임.


text:
Greeting from the Po river

Open source moment

https://user-images.githubusercontent.com/12383260/203658485-1a532e4f-0414-42eb-89b3-f8c6eae034f7.mov

Open source moment

authors: AlexSartori notfilippo

repo: notfilippo/karmacount


text:
Update dependencies to remove vulnerable package json-schema@0.2.3

I updated node-pushnotifications and jest to remove vulnerable package json-schema@0.2.3
Could you merge it and release a new version please?

Thanks for the PR.
There is a problem with jest version: https://github.com/notifme/notifme-sdk/actions/runs/8192007358/job/22441743362?pr=132
And there is also a problem with push-notifications: see https://github.com/notifme/notifme-sdk/pull/116
I think fixing this is more complex: transpilation and all dev tools need to be upgraded.

Thank you for reply
I'll have a look

@BDav24 I've update babel, tests passed locally, let me know if there are any issues
notifme-sdk % yarn test
yarn run v1.22.21
$ yarn run lint && yarn run testonly
$ yarn run flow && standard
$ /Users/dnaumau/Documents/Dinerville/notifme-sdk/node_modules/.bin/flow
No errors!
$ jest
 PASS  __tests__/strategies/providers/index.js
(node:16434) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/webpush/gcm.js
(node:16433) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/voice/twilio.js
(node:16432) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:16431) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/voice/index.js
 PASS  __tests__/providers/webpush/index.js
(node:16436) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/voice/notificationCatcher.js
(node:16435) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/webpush/notificationCatcher.js
(node:16437) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  __tests__/providers/sms/twilio.js
 PASS  __tests__/providers/email/sendgrid.js
 PASS  __tests__/providers/email/mailgun.js
 PASS  __tests__/providers/email/ses.js
 PASS  __tests__/providers/sms/notificationCatcher.js
 PASS  __tests__/providers/email/notificationCatcher.js
 PASS  __tests__/providers/slack/notificationCatcher.js
 PASS  __tests__/providers/slack/slack.js
 PASS  __tests__/providers/email/smtp.js
 PASS  __tests__/providers/sms/46elks.js
 PASS  __tests__/providers/email/sendmail.js
 PASS  __tests__/providers/email/mandrill.js
 PASS  __tests__/providers/email/index.js
 PASS  __tests__/providers/sms/callr.js
 PASS  __tests__/providers/slack/index.js
 PASS  __tests__/providers/sms/plivo.js
 PASS  __tests__/providers/sms/index.js
 PASS  __tests__/providers/sms/ovh.js
 PASS  __tests__/providers/sms/clickatell.js
 PASS  __tests__/providers/sms/nexmo.js
 PASS  __tests__/providers/email/sparkpost.js
 PASS  __tests__/strategies/providers/no-fallback.js
 PASS  __tests__/providers/sms/infobip.js
 PASS  __tests__/strategies/providers/fallback.js
 PASS  __tests__/strategies/providers/roundrobin.js
 PASS  __tests__/sender.js
 PASS  __tests__/providers/mockHttp.js
 PASS  __tests__/custom-channel.js
 PASS  __tests__/notifme-sdk.js

=============================== Coverage summary ===============================
Statements   : 100% ( 398/398 )
Branches     : 100% ( 311/311 )
Functions    : 100% ( 100/100 )
Lines        : 100% ( 365/365 )
================================================================================

Test Suites: 36 passed, 36 total
Tests:       121 passed, 121 total
Snapshots:   0 total
Time:        12.13 s
Ran all test suites.
✨  Done in 16.45s.

Very nice, thanks!

repo: notifme/notifme-sdk


text:
Parsing a JWT without signature fails with JSON::JWS::InvalidFormat: Unknown Signature Algorithm

jwt.rb expects header[:alg] to be :none, but we get "none" from JSON.parse.

Thanks, I just released json-jwt v0.0.4 with your fix :)

authors: mad-p nov

repo: nov/json-jwt


text:
Governance. Delegate. Broken state when Delegate->Revoke

Description
Can't delegate again due to broken state after delegate->revoke (need to restart the app)
https://github.com/user-attachments/assets/9efe351c-3e32-4004-a283-79e4cd476d8d
Environment
https://github.com/novasamatech/nova-spektr/commit/79488c9a756ec07402056b351ea2aca2e43b47ac

Status verification: ✅

repo: novasamatech/nova-spektr


text:
ExoPlayer2/ Listeners and forwarders

Problem
The architecture behind no-player goes something like this.
The client requests a Player which can be either an ExoPlayer or an AndroidMediaPlayer, each of which has an underlying facade(forgive the naming)which talks directly to either the realexoplayerormediaplayer. NoPlayerexposes implementation agnostic listeners that the clients can use. Thefacades` have implementation specific listeners and forwarders (named listeners) that transform the implementation specific events into no-player events and forward to the relevant no-player listeners.
The problem is, that nearly everything is called a listener :laughing: which makes working on no-player confusing
Furthermore, because there are different events, some of the them have different interfaces and some of them even implement some interfaces and no-op them and then extend again only using the ones they need. Confusing!
Solution
Have one Listener that encapsulates all of the events that need to be mapped between exo-player and no-player. Implement a no-op version of Listener and then create additional forwarders from this that implement the methods they need to know about that map to no-player.
It's probably easier to see the diff :laughing:

Something is up with the MediaPlayer 😢

ExoPlayerForwarder now implements all event listeners that we are interested in ExoPlayer and we forward all events. There is an ExoPlayerEventForwarder which is an abstract class that swallows all events by default. We add specific ExoPlayerEventForwarders based on the Player listeners that we want to map to. The forwarders perform the mapping.

repo: novoda/no-player


text:
Demo audio track selection

Problem
The player supports audio track selecting but it's not present in the demo.
Solution
To add the ability to switch audio tracks to the demo.
Test(s) added
nil tests around the demo code
Screenshots

Before
After

Paired with
@Dorvaryn

Looks good to me ! 💯

authors: jackSzm ouchadam


text:
adding network policies to enforce minimal connectivity

Fixes # .
Change summary:
Remaining issues / concerns:

query
src_ns
src_pods
dst_ns
dst_pods
connection

, config: .

[default]
[app in (checkoutservice,frontend,recommendationservice)]
[default]
[productcatalogservice]
TCP 3550

[default]
[app in (checkoutservice,frontend)]
[default]
[shippingservice]
TCP 50051

[default]
[checkoutservice]
[default]
[paymentservice]
TCP 50051

[default]
[frontend]
[default]
[checkoutservice]
TCP 5050

[default]
[cartservice]
[default]
[redis-cart]
TCP 6379

[default]
[app in (checkoutservice,frontend)]
[default]
[currencyservice]
TCP 7000

[default]
[app in (checkoutservice,frontend)]
[default]
[cartservice]
TCP 7070

ip block: 0.0.0.0/0
[default]
[frontend]
TCP 8080

ip block: ::/0
[default]
[frontend]
TCP 8080

[default]
[checkoutservice]
[default]
[emailservice]
TCP 8080

[default]
[frontend]
[default]
[recommendationservice]
TCP 8080

[default]
[loadgenerator]
[default]
[frontend]
TCP 8080

[default]
[frontend]
[default]
[adservice]
TCP 9555

query
src_ns
src_pods
dst_ns
dst_pods
connection

Removed connections between persistent peers

[default]
[*]
[default]
[productcatalogservice]
All but TCP 3550

[default]
[recommendationservice]
[default]
[*]
All but TCP 3550

[default]
[*]
[default]
[app in (paymentservice,shippingservice)]
All but TCP 50051

[default]
[*]
[default]
[checkoutservice]
All but TCP 5050

[default]
[cartservice]
[default]
[*]
All but TCP 6379

[default]
[*]
[default]
[currencyservice]
All but TCP 7000

[default]
[*]
[default]
[cartservice]
All but TCP 7070

[default]
[*]
[default]
[app in (emailservice,recommendationservice)]
All but TCP 8080

[default]
[loadgenerator]
[default]
[*]
All but TCP 8080

[default]
[*]
[default]
[adservice]
All but TCP 9555

[default]
[*]
[default]
[loadgenerator]
All connections

[default]
[app not in (cartservice,checkoutservice,frontend,loadgenerator,recommendationservice)]
[default]
[*]
All connections

[default]
[cartservice]
[default]
[app not in (cartservice,loadgenerator,redis-cart)]
All connections

[default]
[checkoutservice]
[default]
[app in (adservice,frontend,recommendationservice,redis-cart)]
All connections

[default]
[frontend]
[default]
[app in (emailservice,paymentservice,redis-cart)]
All connections

[default]
[loadgenerator]
[default]
[app not in (frontend,loadgenerator)]
All connections

[default]
[recommendationservice]
[default]
[app not in (loadgenerator,productcatalogservice,recommendationservice)]
All connections

Removed connections between persistent peers and ipBlocks

ip block: 0.0.0.0/0
[default]
[*]
All but TCP 8080

ip block: ::/0
[default]
[*]
All but TCP 8080

ip block: 0.0.0.0/0
[default]
[app not in (frontend)]
All connections

ip block: ::/0
[default]
[app not in (frontend)]
All connections

[default]
[*]

ip block: 0.0.0.0/0
All connections

[default]
[*]

ip block: ::/0
All connections

query
src_ns
src_pods
dst_ns
dst_pods
connection

, config: .

[default]
[app in (checkoutservice,frontend,recommendationservice)]
[default]
[productcatalogservice]
TCP 3550

[default]
[app in (checkoutservice,frontend)]
[default]
[shippingservice]
TCP 50051

[default]
[checkoutservice]
[default]
[paymentservice]
TCP 50051

[default]
[frontend]
[default]
[checkoutservice]
TCP 5050

[default]
[cartservice]
[default]
[redis-cart]
TCP 6379

[default]
[app in (checkoutservice,frontend)]
[default]
[currencyservice]
TCP 7000

[default]
[app in (checkoutservice,frontend)]
[default]
[cartservice]
TCP 7070

ip block: 0.0.0.0/0
[default]
[frontend]
TCP 8080

ip block: ::/0
[default]
[frontend]
TCP 8080

[default]
[checkoutservice]
[default]
[emailservice]
TCP 8080

[default]
[frontend]
[default]
[recommendationservice]
TCP 8080

[default]
[loadgenerator]
[default]
[frontend]
TCP 8080

[default]
[frontend]
[default]
[adservice]
TCP 9555

repo: np-guard/online-boutique


text:
Update leaflet to 1.9.4

This is a starting point to update Leaflet to the most recent version (solves #792).
I managed to fix the most obvious issue with the no-go-area. They are usable.
However, there is still one exception on the browser console that I couldn't solve so far.

Maybe someone else is able to fix it.

I think I've figured it out and made a pull request in your repository.
It'd be nice if you can verify that it works now and update this PR.
https://github.com/gorgobacka/brouter-web/pull/1

@mjaschen found the missing piece. :+1:
This PR is ready now.

Unfortunately there's a problem which breaks the “No Go Area” feature on touch devices.
tap and hold to create a circle doesn't work.
I've spent some time on the weekend on the search for a fix and didn't found one. But at least I've a workaround which allows placing fixed size no go areas with a single tap on touch devices, so it's usable at least.
Also, the routing library issues a call to DomEvent.fakeStop() when tapping the route, but that method no longer exists. That's another thing which has to be fixed before merging this PR. My workaround for now is to simply remove that method call: https://github.com/mjaschen/leaflet-routing/commit/0690d5e29a8156121f4f6d102bf380459ef01b5a
With these two workarounds, BRouter-Web works fine with Leaflet 1.9.4 – as far as I've tested it.
If I don't find any further bugs, I'll deploy it in the next days to bikerouter.de and create pull requests here. Maybe someone has an idea how to create proper bugfixes instead of workarounds.

I don't have much time to test but I am more than happy to merge this PR when it's good enough to go live :) It'd be nice to fix the detected issues, but if it's really hard I think we can assess if that's really important (the nogo circle workaround seems good enough to me for instance).
If there are other testers available to give it a try and report issues, it would greatly help! Let us know @mjaschen when your instance is live with this branch so that it's easier to test it :)
And many thanks for the PR and follow-up!

A version with Leaflet 1.9.4 was deployed to https://bikerouter.de
It contains this pull request with the following additional changes:

“No Go Areas“ are placed with a single tap on touch devices; behavior on devices with mouse pointer is unchanged (click + drag). The tooltip adjusts accordingly. The initial size of the circle depends on the viewport width.

Todo: figure out how to use tap + drag on iOS touch devices

Leaflet-Routing library (diff):

replace fakeStop() call on DomEvent as this method no longer exists
force showing the trailing line in draw mode after the most recent waypoint was deleted
Todo: check if there's an easier/cleaner way to achieve this

authors: bagage gorgobacka mjaschen

repo: nrenner/brouter-web


text:
Conservative fences

Hey all,
This change introduces two major things:

Uses an AcqRel compiler fence before the end of each driver function that invokes DMA, to prevent misoptimization
Adds my write_read interface to TWIM, useful for I2C devices that implement a typical register interface (write address/subaddress, then read data)

The target for this merge is the re-release branch.
Closes https://github.com/nrf-rs/nrf52-hal/issues/33 - at least hopefully.

Merging


text:
new new-icon

Do you have an svg icon file?
Please upload this file as an attachment or name the upstream branch containing it.

Is the icon file ready to be added to the library?

It has been trimmed using a minifier like SVGOMG. (Lowest precision without visual degradation)
It has fill-rule of fill="currentColor"
It has no explicit width/height
It has viewbox of viewbox="0 0 24 24"

What is the name of the icon?
Make sure the icon fits the naming convention of nrk-category-name--state
Jeg er usikker på navngivningen da denne ikke har en annen state enn nrk-media-ny, men må bare implementeres på en annen måte (derav bare én bindestrek til slutt)
Additional context
Add any other context or screenshots about the feature request here.
Dette bildet forsøker å illustrere forskjellen på nrk-media-ny (alt 1) og nrk-media-ny-txt (alt. 2).

Hvis den skal erstatte ikonet med sirkel (nrk-media-ny) vil det brekke hos Radio. "ny" uten sirkel bør da legges inn som et eget ikon så vi slipper justere om pr nå.

After discussing with the developers we can do the change, fixing the circle behind when the new icon is pulled from the set, (I thought it would update automatically by default).
Ergo, it’s a thumbs up from me to override the current icon if needed.

To prevent bloating, we'll replace the existing nrk-media-ny icon using the same name.
The change will only take effect when team devs update their core-icons. We'll warn them of the breaking change.

authors: Isdoda marve-s stefanogden

repo: nrkno/core-icons


text:
Bundler could not find compatible versions for gem "rails"

Bundler could not find compatible versions for gem "rails":
  In snapshot (Gemfile.lock):
    rails (= 5.0.0.alpha)

  In Gemfile:
    knock (>= 0) ruby depends on
      rails (~> 4.2) ruby

    rails (>= 0) ruby

Any news about Rails 5 support?

I just submitted PR #30 as a first step for Rails 5 support

#30 should fix this indeed. Thanks @sespindola.

#30 should fix this indeed. Thanks @sespindola.

authors: nsarno sespindola stephanngamedev

repo: nsarno/knock


text:
Replace waf with Makefile

Using Python to build a C library seems a bit... odd.
Makefiles have been around for decades, and work perfectly for both small and large projects.
Makefiles have the advantage of being ubiquitous across UNIX-like systems. Anyone with a C compiler will have make, but a lot of people with C compilers won't have Python, and many of those won't want to install it just to build a single library.
Portability aside, Makefiles are a lot easier for contributors as well as for people who just want to use the library. Almost everyone who knows C can write, or at least understand, a Makefile, making it easier to contribute to projects that use them.

I removed the src and build directories because the root of the repo felt a bit empty with only src, README.rst and COPYING. It's easy enough to add them back in if necessary though, so let me know.
This also resolves issue #93, partly because I wanted to remove all Python code from the repo and partly because I couldn't be bothered to work out how the wrapper is generated and integrate that into the Makefile. Let me know if you'd prefer to keep it in and I'll see what I can do.

Another thing to bear in mind is the fact that my two Makefiles have a total SLOC of 32, whereas waf with the 3 wscript files totals 156 lines (the wscript files alone are 50).

i applaud you to your sane intentions, but this already happened in the past - followup: https://github.com/nsf/termbox/commit/36574f75b3c6567a72fe74a3306921025d76898d

No.

@rofl0r, I see. Why was the Makefile removed, out of interest?

Makefile was contributed by third party. There were multiple build systems. At the moment of removal the only build system I used for my own projects was waf. Now I would use cmake, but for termbox it doesn't matter what build system is used, it should only be used by a person who contributes to termbox (me or whoever). Termbox is a super small library that doesn't need a makefile. You can compile it with a single very small command invoking a compiler directly and I encourage people not to package termbox as a separate library, but embed the source into their own projects instead. The build system in-place I have is used as a convenient way to compile demos, probably I should replace it with a bash script.
Waf or cmake would be a better choice if termbox ever gets a windows port. Which was planned, but I ended up implementing it only in termbox-go. Makefiles on windows are useless.

@nsf, gotcha. I think I'll host my Makefile (modified slightly to fit the upstream termbox distribution) in a repo somewhere so I or others can use it in projects which use Makefiles.
What I'm currently doing is adding termbox as a git submodule in libs/termbox, and then copying in my Makefile as libs/termbox.mk. Then, in my project's Makefile, I can run make -C libs -f termbox.mk libtermbox.a to generate a static library which I can then link with my source files. By using git submodules, I ensure that I can still receive the latest updates to termbox and I reduce the amount of copying I have to do.
Once I get around to uploading the Makefile somewhere, would you consider adding it to the README so others can use it?

No.

authors: nsf rofl0r vktec

repo: nsf/termbox


text:
NEOFS_HTTP_GATE parameter not clear

Problem
This parameter confuses me as a regular user. Usually, I read the parameters of any function/action as a part of its code: if it needs it, it should use it and I can understand it better. How http gate is used in this action?
Context
Why do we need this parameter? It is a http gate that should be connected to a storage node used for object download. However, it is not used for object downloading, is not validated, and is not checked for an http-SN relation. It also does not simplify action usability: a user has to figure out the correct http gateway himself anyway, no matter if it happens after the objects download or before CI workflow creation. If he knows it, he can use it. If he does not need it, he doesn't want to find it (hehe, neofs does not live for browsers only), he should be able to omit it (once again, http is not a required thing for the action literally named "push to neofs").

Related to #18.

authors: carpawell roman-khimov

repo: nspcc-dev/gh-push-to-neofs


text:
can't initialize StateRoot service: open : no such file or directory

bad error description:
./neo-go-linux-amd64 node --config-file config.yml
...
can't initialize StateRoot service: open : no such file or directory

config.yml:
  StateRoot:
    Enabled: true

the same for oracle:
can't initialize Oracle module: open : no such file or directory

open what?

repo: nspcc-dev/neo-go


text:
Add support for reading from quorum queues

This PR adds the ability to specify queue type via the flags in the fluentd configuration file.

@mmasaki Thank you so much for this plugin for fluentd! I have no idea why fluentd doesn't have a supported rabbitmq plugin. I found that for the queue type that I needed to use this with I needed to support setting the "x-queue-type" queue argument, so I made the code changes and rebuilt the gem locally for my purposes.
I wanted to bring the gains back. Thanks again!

@karchf Thank you! This PR is greatly appreciated.

authors: karchf mmasaki

repo: nttcom/fluent-plugin-rabbitmq


text:
🛑 Secret Site BIS is down

In d503fc4, Secret Site BIS ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site BIS is back up in c2f470c after 14 minutes.


text:
🛑 Secret Site BIS is down

In 39b4ef5, Secret Site BIS ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site BIS is back up in 5ed9cb4.


text:
🛑 TCP ping is down

In 419a29b, TCP ping (1.1.1.1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TCP ping is back up in b2658c9.


text:
🛑 Università e ricerca is down

In e4ffa82, Università e ricerca (https://www.mur.gov.it/it) was down:

HTTP code: 403
Response time: 633 ms

Resolved: Università e ricerca is back up in cc17b47 after 149 days, 4 hours, 32 minutes.


text:
🛑 Agricoltura, Sovranità alimentare e Foreste is down

In b312d1c, Agricoltura, Sovranità alimentare e Foreste (http://www.politicheagricole.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Agricoltura, Sovranità alimentare e Foreste is back up in d6a3df7 after 28 minutes.


text:
🛑 Guardia di Finanza is down

In 8eac4c5, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in 755bda5 after 5 minutes.


text:
Komga Integration Does Not Seem to be Accurately Tracking Progress in App

Steps to reproduce

Follow manga in self-hosted Komga instance

Set Manga to Track in Yokai

Tracking lists 0/x chapters

Read Chapters in Yokai, these are correctly tracked locally

Tracking remains 0/x chapters in Yokai for the Komga Integration

Even removing and readding the Komga tracking integration does not correctly update it to the current state of Komga's read status.

Komga correctly updates the "recently read" list with the read chapters so it is receiving the api notice that they have been read.  However, the local Yokai Komga tracker (independent of the Yokai app's own tracker) does not update or change from 0/x.

I do see some mangas that do correctly list them as complete in Yokai, I cannot see any consistent reason why.
Expected behavior
Komga Tracker should match Komga and Yokai's own status tracker.  If they get out of sync, then removing and re-adding, or syncing the manga should fix it.
Actual behavior
Yokai's Komga Tracker remains at 0/x regardless of the chapters read.
Crash logs
`App version: 1.8.5.6 (standard, 2debbc0a1, 147, 2024-08-25T12:32:48Z)
Android version: 14 (SDK 34)
Android build ID: AP2A.240805.005
Device brand: google
Device manufacturer: Google
Device name: cheetah
Device model: Pixel 7 Pro
Device product name: cheetah
--------- beginning of main
08-29 08:06:50.552  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:50.553  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.
08-29 08:06:52.744  5429  5429 E tachiyomi.yokai: Invalid resource ID 0x00000000.`
Yōkai version
1.8.5.6
Android version
Android 14
Device
Pixel 7 Pro
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, or a request for an extension, I should be contacting the extensions repository's maintainer/support for help.
[X] I am reporting an issue exclusive to this fork. I have also checked that is not an issue on the main version of Mihon
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version 1.8.5.6.
[X] I have updated all installed extensions.
[X] I have filled out all of the requested information in this form.

I should add, I also tried migrating the komga source to the same komga source again after I saw that crash log had an invalid resource ID, thinking perhaps that some variable was a null value and screwing this up and that migration would repopulate them.  I did not see any change in behavior.


text:
README

README文件的启动方式需要修改下吧

最近很快会合并2.0分支，readme会同步修改

repo: nuls-io/nuls


text:
Using Exceptions to trigger continue in loops fails

using the latest version (v0.49.1), would expect this to work without an error - it's not particularly urgent though
from numba import njit
import numpy as np
a=np.arange(10)
@njit
def foo(a):
         for _ in a:
            try:
               raise Exception
            except Exception:
               continue
 foo(a)

Traceback (most recent call last):
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\IPython\core\interactiveshell.py", line 3331, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 11, in
foo(a)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 404, in _compile_for_args
error_rewrite(e, 'unsupported_error')
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 342, in error_rewrite
raise e
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 353, in _compile_for_args
return self.compile(tuple(argtypes))
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 794, in compile
cres = self._compiler.compile(args, return_type)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 77, in compile
status, retval = self._compile_cached(args, return_type)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 91, in _compile_cached
retval = self._compile_core(args, return_type)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\dispatcher.py", line 109, in _compile_core
pipeline_class=self.pipeline_class)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler.py", line 568, in compile_extra
return pipeline.compile_extra(func)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler.py", line 339, in compile_extra
return self._compile_bytecode()
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler.py", line 401, in _compile_bytecode
return self._compile_core()
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler.py", line 381, in _compile_core
raise e
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler.py", line 372, in _compile_core
pm.run(self.state)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_machinery.py", line 341, in run
raise patched_exception
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_machinery.py", line 332, in run
self._runPass(idx, pass_inst, state)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_machinery.py", line 291, in _runPass
mutated |= check(pss.run_pass, internal_state)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\compiler_machinery.py", line 264, in check
mangled = func(compiler_state)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\untyped_passes.py", line 86, in run_pass
func_ir = interp.interpret(bc)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\interpreter.py", line 116, in interpret
flow.run()
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\byteflow.py", line 107, in run
runner.dispatch(state)
File "C:\Workdir\Programs\Anaconda2\envs\LTM\lib\site-packages\numba\core\byteflow.py", line 269, in dispatch
raise UnsupportedError(msg, loc=self.get_debug_loc(inst.lineno))
numba.core.errors.UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
Use of unsupported opcode (CONTINUE_LOOP) found
File "", line 10:
def foo(a):

except Exception:
continue
^
Unsupported functionality was found in the code Numba was trying to compile.
If this functionality is important to you please file a feature request at:
https://github.com/numba/numba/issues/new
<!--

@p-ortmann thanks for reporting this. Unfortunately, I am unable to reproduce this using both master and 0.49.1. Perhaps you could share more details about your system, such as operating system  version and Python version and any other details that might be relevant? Thanks!
For reference, here is my terminal session to make sure I have run the code as intended.
💥 zsh» cat foo072.py
from numba import njit
import numpy as np

a = np.arange(10)

@njit
def foo(a):
    for _ in a:
        try:
            raise Exception
        except Exception:
            continue

foo(a)
💥 zsh» python foo072.py
💥 zsh» echo $?
0

@esc it's win 10 enterprise 17763 and python 3.7.7, if it's related to my setup maybe it's not worth while to pursue this.. it's easy to work around it. Thanks for checking anyhow!

@esc if you are using Python 3.8 you won't see it because CONTINUE_LOOP opcode was removed. Pretty sure that this is a bug.
$ python --version
Python 3.7.7

$ cat issue5749.py
from numba import njit, __version__
import numpy as np

print(__version__)

a=np.arange(10)

@njit
def foo(a):
    for _ in a:
        try:
            raise Exception
        except Exception:
            continue

foo(a)

$ python issue5749.py
0.49.1
Traceback (most recent call last):
  File "issue5749.py", line 16, in <module>
    foo(a)
  File "<path>/lib/python3.7/site-packages/numba/core/dispatcher.py", line 404, in _compile_for_args
    error_rewrite(e, 'unsupported_error')
  File "<path>/lib/python3.7/site-packages/numba/core/dispatcher.py", line 344, in error_rewrite
    reraise(type(e), e, None)
  File "<path>/lib/python3.7/site-packages/numba/core/utils.py", line 80, in reraise
    raise value.with_traceback(tb)
numba.core.errors.UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
Use of unsupported opcode (CONTINUE_LOOP) found

File "issue5749.py", line 14:
def foo(a):
    <source elided>
        except Exception:
            continue
            ^

@stuartarchibald indeed, with 3.7 I can reproduce it too!

authors: esc p-ortmann stuartarchibald

repo: numba/numba


text:
Bump deprecation notices.

Move these forward slightly to match reality.

LGMT.

authors: esc stuartarchibald


text:
Inconsistency in visualizer lifecycle; should it be changed?

Like the testing issues, the documentation issues are great for surfacing underlying problems. Responsive to #46, I am designing a "visualizer lifecycle diagram" (along the lines of the Vue component lifecycle diagram). That exercise has uncovered the following inconsistency:

We document the checkParameters() method of a (P5)Visualizer as being able to rely on, and use, the sequence .first and .last properties in validating the parameters of the visualizer, and indeed, some of our Visualizer classes (e.g. Turtle) do so. Yet when the sequence changes, the update pathway only goes back to presketch(); if no parameters specific to the visualizer have changed, the visualizer checkParameters() is not called again. So whatever validations were done on the sequence extents may now be in a failed state. This mismatch is even called out as a bug in the comments in Turtle.ts.

Should we modify the update pathway on sequence change for a Visualizer to include calling checkParameters()? Or if not, how should the above inconsistency be resolved? I do not think the inconsistency should be allowed to remain.

Is there any reason not to modify the update pathway as you suggest?

I can't think of any reason other than it's yet another change and will have various repercussions we need to track down and likely fix. But in the long run, it definitely seems like a better scheme. So we could just go for it now while everything is in turmoil anyway ;-)

Sounds like updating the pathway makes sense then?

OK, renamed the issue accordingly.

Implemented in ui2 by #486. Closing.

authors: gwhitney katestange

repo: numberscope/frontscope


text:
Add document

Purpose
We want to turn impress into a pad ie being able to create, edit, persist, print and share our content directly in the application.
Proposal
Add a Document model and the related API.
We propose to persist the document content (which is json content output by ProseMiror) to object storage. We thus benefit from object storage's versioning, robustness and scalability and will be able to store many versions of each document for a great  and safe collaboration experience.

I still have a prob with Minio, I cannot use the endpoints, although the env are set. I didn't want to loose too much time on it so I created another PR #34 to get the commits about documents endpoints.
NoCredentialsError at /api/v1.0/documents/
Unable to locate credentials
Request Method:	GET
Request URL:	http://localhost:8071/api/v1.0/documents/?page=1&ordering=-created_at
Django Version:	5.0.3
Exception Type:	NoCredentialsError
Exception Value:
Unable to locate credentials
Exception Location:	/usr/local/lib/python3.10/site-packages/botocore/auth.py, line 418, in add_auth
Raised during:	core.api.viewsets.DocumentViewSet
Python Executable:	/usr/local/bin/python
Python Version:	3.10.14
Python Path:	...
...

I still have a prob with Minio, I cannot use the endpoints, although the env are set. I didn't want to loose too much time on it so I created another PR #34 to get the commits about documents endpoints.

In fact you need to update your env.d/development/common file. I added a few parameters to the common.dist file that you need to port manually to your common file because it is not committed...
# Media
STORAGES_STATICFILES_BACKEND=django.contrib.staticfiles.storage.StaticFilesStorage
AWS_S3_ENDPOINT_URL=http://localhost:9000
AWS_S3_ACCESS_KEY_ID=impress
AWS_S3_SECRET_ACCESS_KEY=password

authors: AntoLC sampaccoud

repo: numerique-gouv/impress


text:
Better default for reg_param_vec in prob_calibration_function

right now it is 10**linspace(-6,6,241) but it is a little slow (241 might be overkill) and that may be too wide of a range.  Consider a default with fewer points to search.

Reduced to 43 values

repo: numeristical/introspective


text:
How can I run the test?

I am new to c#. Try to run the test. Where is the main function? Please advise.
Can you update the read me for some one new to c#?

After building the test, you run the assembly that is created. Running tests is completely language-agnostic since it only deals with the output assembly.
For info on how to run the assembly using NUnit, see the general nunit documentation at https://github.com/nunit/docs/wiki
For information about how to write or compile C# code, there are many standard references or you can ask in a forum that's dedicated to that kind of question.

authors: CharliePoole xueenda

repo: nunit/nunit-csharp-samples


text:
Long names prevent tests from being discovered

I get the following error while discovering tests which prevent me from getting tests from all projects.
I would expect to get the same shorted, perhaps receive a warning and then move forward.
Error:
Operation failed. The index entry of length 906 bytes for the index 'Idx_Stale_StateValue_DisplayName' exceeds the maximum length of 900 bytes.

I think this is related to https://github.com/nunit/nunit/issues/59

nunit/nunit#59 is the underlying cause but we should handle the error better.
Can you provide a test case to reproduce this problem?

I kept doing debug and found the test, in fact the problem was around the TestCase attribute which had chinese characters:
[TestCase("这个是中文内容, CSharp is the bast", "这是中国语内容，CSharp is the best language.", "这个是中文国语内容, CSharp，CSharp is the bastbest language.")]
The problem I think was around the third parameter which was too long.
I removed the attribute (it had few more TestCase attributes) and I manage to get the entire test suite loaded.

Maybe try pasting the code to a gist

didn't know about it, thanks :)
here's the link: https://gist.github.com/jaime-rq/410bc8ff2944ecd31098

Just a note in case anyone using the nunit3-vs-adapter sees this...
In NUnit 3.0, the parameters are currently truncated to 40 chars. So with
the nunit3 adapter, the problem changes from "too long" to "duplicate ids"
in some cases.
On Mon, Sep 28, 2015 at 12:02 PM, Victor Castillo Escoto <
notifications@github.com> wrote:

Maybe try pasting the code to a gist https://gist.github.com/
—
Reply to this email directly or view it on GitHub
https://github.com/nunit/nunit-vs-adapter/issues/83#issuecomment-143844961
.

I was trying to repro this, but to me this works.
What I get in the Test output window is:
Contents of string 'ThisHasALongName("\x8FD9\x4E2A\x662F\x4E2D\x6587\x5185\x5BB9, CSharp is the bast","\x8FD9\x662F\x4E2D\x56FD\x8BED\x5185\x5BB9\xFF0CCSharp is the best language.","\x8FD9<del class='diffdel'>\x4E2A\x662F\x4E2D<del class='diffmod'>\x6587<ins class='diffmod'>\x56FD\x8BED\x5185\x5BB9<del class='diffmod'>, CSharp<ins class='diffmod'>\xFF0CCSharp is the <del class='diffmod'>bast<ins class='diffmod'>best language.")' exceeds max of '449', string has been truncated.
And that message seems ok.

I'm closing this as the issue test I have doesn't reproduce the behaviour.

authors: CharliePoole OsirisTerje elbaloo jaime-rq

repo: nunit/nunit-vs-adapter


text:
Feature Request: Ability to reference UAP/WinRT C++ projects

I noticed that when I try to add a reference to a WinRT C++ project (it outputs an assembly dll), I get the following error (these are projects that have the vcxproj extension)
---------------------------
Microsoft Visual Studio
---------------------------
Confirm unsupported reference(s)

One or more of the selected items is not a valid reference for this type of project.  Do you want to continue and add all the references anyway?

Right now, NuProj is hard-coded to only accept c#, vb or f# https://github.com/nuproj/nuproj/blob/master/src/NuProj.ProjectSystem.12/NuProjValidProjectReferenceChecker.cs#L90
If you could provide me some sample of C++ project with expected NuGet package layout, I would love to have a look at this. Ideally you could prepre a unit test similar to References_PackageOutputGroups.

Yep, I had added the vcxproj to that as I was working through things.
Here is the projects I am trying to get to work with nuproj
https://github.com/XLabs/Xamarin-Forms-Labs/tree/master/src/Platform/XLabs.Platform.WinRT

Or even just desktop C++ projects using vcxproj. The AssignTargetFramework task fails:
Error	MSB4018	The "AssignTargetFramework" task failed unexpectedly.
System.ArgumentNullException: Value cannot be null.
Parameter name: path2
   at System.IO.Path.Combine(String path1, String path2, String path3, String path4)
   at NuProj.Tasks.Extensions.Combine(PackageDirectory packageDirectory, String targetFramework, String packageSubdirectory, String fileName)
   at NuProj.Tasks.AssignTargetFramework.ConvertToPackageFile(ITaskItem output)
   at System.Linq.Enumerable.<>c__DisplayClass7_0`3.<CombineSelectors>b__0(TSource x)
   at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at NuProj.Tasks.AssignTargetFramework.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()

authors: heaths kovalikp ravensorb

repo: nuproj/nuproj


text:
How to install the dropdown list plug-in on UNIX

Hi! I was watching the introductory videos and noticed that there was a plug-in installed on the terminal which had dropdown list suggestions where you can easily tab out longer command lines (for eg. just by typing "System" the entire "System.out.print()" can be auto-filled immediately). I know IDEs like intelliJ has this built-in function but how can i get this function for my mac terminal? Or is this not allowed for students in this course

You can search for the vim javacomplete plugin.  However, during the labs and assessment, this plugin will not be available... nor is it necessary.

authors: ReubenChay hwkchia


text:
Add feature: gnu_legacy mode for ansi styles

Hi,
gnu coreutils are still using double digit styles instead of single digit styles.
To make this available in uucoreutils (the rust drop in replacement for gnu core utils) I added a feature called gnu_legacy.
Related PR
By turning it on it will generate styles double digit. If not turned on it will behave as before. Tests have been added.
// without feature flag gnu_legacy
    test!(bunderline:            Style::new().bold().underline();   "hi" => ,"\x1B[1;4mhi\x1B[0m");
// with feature flag gnu_legacy
    test!(bunderline:            Style::new().bold().underline();   "hi" => "\x1B[01;04mhi\x1B[0m");

Please see the code and I hope this feature can make it.
The second missing feature would be to have the option to reset a style before applying. I would open another PR for this.

looks like some tests are failing

Thanks

repo: nushell/nu-ansi-term


text:
Reverted: force separator around binary operators

This PR reverts this trick introduced by #149 :
/**
 * group operator and its preceding/succeeding whitespace/newline
 * @param {string} opr
 * @param {boolean} parenthesized
 */
function operator_with_separator(opr, parenthesized) {
  const sep = parenthesized ? choice(/[ \t]/, /\r?\n/) : /[ \t]/;
  return alias(token(seq(repeat1(sep), opr, repeat1(sep))), opr);
}

It turns out that this will cause unwanted side effects of blurring boundaries of tokens around binary_expression:

compared to the ideal result after this PR:

Instead, cmd_identifier is tweaked to keep expressions like 1+1 away from being parsed as binary_expression.

good catch. thanks!

authors: blindFS fdncred

repo: nushell/tree-sitter-nu


text:
add PORTAL_AUTH Nuxeo authentication (portal-sso)

Hello,
Can you accept my pull-request for PORTAL_AUTH authentication ? please ?
I use a nuxeo server in version 7.10 and i have developed an php application symfony 2.7 with your bundle nuxeo/nuxeo-automation-php-client and on my nuxeo server i have installed the plugin authentication portal-sso (described in this page : https://doc.nuxeo.com/60/nxdoc/authentication/).
On my application i got a trust key. This key is shared on my nuxeo server. This is the PORTAL_AUTH plugin authentication.
My pull request is a code for use this functionnality.
Thanks!
Mathieu HETRU

From the blame information on this pull request, potential reviewers: @pgmillon

Hi,
I rebased your code on 1.5.0-rc2, switched authentication as interceptors in order to move your implementation in a Nuxeo\Client\Api\Auth\PortalSSOAuthentication (see branch feature-authent-sso).
I'll also share some thoughts as comments in your code.
Many thanks for your contribution !

Hello,
Thanks for your released code in 1.5.0-rc2.
But if i want use your 1.5.0-rc2 code using portal-sso, i need construct the $client object but the constructor of NuxeoClient require exactly a login/pass nuxeo calling himself the BasicMethod...
My code just avoid it, and in my application i don't need store a login/pass nuxeo for basic method.
I got only the secret key and the id of the user (id providing from my sso-server).
For your notice of random_int, i understand but random work fine. No?
You can use random_int if you want, if the result is the same result from random :)

here is my test code for my contributions :
`#!/usr/bin/php
automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return (array_key_exists(0, $result->getDocuments() )) ? $result->getDocuments()[0]->getUid() : null;

        }

        function getFilesOfDir($c, $path) {
                $folder_uid = getFolderUid($c, $path);
                $nxql = "SELECT * FROM Document WHERE ecm:parentId = '".$folder_uid."' AND ecm:currentLifeCycleState <> 'deleted' ORDER BY dc:title";
                $operation = $c->automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return $result;
        }

        $url = "https://ged-dev.univ.fr/nuxeo";
        $login = "1940";
        $password = "";
        $key = "mysecretkey";

        $client = new NuxeoClient($url, $login, $password, 'PORTAL', $key);

        $client->schemas('*');

        $documents = getFilesOfDir($client, "/default-domain/workspaces/Service DSI/Test");

        foreach($documents->getDocuments() as $document) {
                echo "---------------------------------------------------------\n";
                echo "UID = [" . $document->getUid() . "]\n";
                echo "Path = [" . $document->getPath() . "]\n";
                echo "Type = [" . $document->getType() . "]\n";
                echo "State = [" . $document->getState() . "]\n";
                echo "Title = [" . $document->getTitle() . "]\n";
                echo "Description = [". $document->getProperty("dc:description") . "]\n";
                echo "Creator = [" . $document->getProperty("dc:creator") . "]\n";
        }

?>
`

when i use your 1.5.0-rc2 i got an error :

PHP Parse error:  syntax error, unexpected '(' in /home/mhetru/public_html/reprise_nuxeo2/vendor/nuxeo/nuxeo-automation-php-client/src/Nuxeo/Client/Internals/Spi/SimpleInterceptor.php on line 42

My test code is :
#!/usr/bin/php
<?php
        include("vendor/autoload.php");

        use Nuxeo\Client\Api\NuxeoClient;
        use Nuxeo\Client\Api\Objects\Documents;
        use Nuxeo\Client\Api\Objects\Document;
        use Nuxeo\Client\Api\Auth\PortalSSOAuthentication;

        function getFolderUid($c, $path) {

                $nxql = " SELECT ecm:uuid FROM Document WHERE ecm:path = '" . utf8_decode($path) . "' ";
                $operation = $c->automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return (array_key_exists(0, $result->getDocuments() )) ? $result->getDocuments()[0]->getUid() : null;

        }

        function getFilesOfDir($c, $path) {
                $folder_uid = getFolderUid($c, $path);
                $nxql = "SELECT * FROM Document WHERE ecm:parentId = '".$folder_uid."' AND ecm:currentLifeCycleState <> 'deleted' ORDER BY dc:title";
                $operation = $c->automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return $result;
        }

        $url = "https://ged-dev.univ.fr/nuxeo";
        $login = "Administrator";
        $login_uid = "1940";
        $password = "mysecretpassword";
        $key = "mysecretpassword";

        $client = new NuxeoClient($url, $login, $password);

        $client->setAuthenticationMethod(new PortalSSOAuthentication($key, $login_uid));

        $client->schemas('*');

        $documents = getFilesOfDir($client, "/default-domain/workspaces/Service DSI/Test");

        foreach($documents->getDocuments() as $document) {
                echo "---------------------------------------------------------\n";
                echo "UID = [" . $document->getUid() . "]\n";
                echo "Path = [" . $document->getPath() . "]\n";
                echo "Type = [" . $document->getType() . "]\n";
                echo "State = [" . $document->getState() . "]\n";
                echo "Title = [" . $document->getTitle() . "]\n";
                echo "Description = [". $document->getProperty("dc:description") . "]\n";
                echo "Creator = [" . $document->getProperty("dc:creator") . "]\n";
        }

?>

Hi,
Thanks for the feedback.
About the NuxeoClient constructor, the $username and $password are optionals; you can instantiate the client with $client = new NuxeoClient($url) and then call $client->setAuthenticationMethod(new PortalSSOAuthentication($key, $login_uid)). See the testPortalSSOAuth method.
About random/random_int, the issue is that random can be predicted so the token we generate can be compromised. We must ensure maximum safety of our end-users, that's why we'd better use the safer random_int instead of random.
Finally about the Parse error, I messed up with the PHP version. I've made sure to run the tests with a PHP 5.3.3 so that cannot happen again.
I've updated the feature-authent-sso accordingly.

yes!!!! it works fine!!!! cool :)
thanks :)
my test code is :
#!/usr/bin/php
<?php
        include("vendor/autoload.php");

        use Nuxeo\Client\Api\NuxeoClient;
        use Nuxeo\Client\Api\Objects\Documents;
        use Nuxeo\Client\Api\Objects\Document;
        use Nuxeo\Client\Api\Auth\PortalSSOAuthentication;

        function getFolderUid($c, $path) {

                $nxql = " SELECT ecm:uuid FROM Document WHERE ecm:path = '" . utf8_decode($path) . "' ";
                $operation = $c->automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return (array_key_exists(0, $result->getDocuments() )) ? $result->getDocuments()[0]->getUid() : null;

        }

        function getFilesOfDir($c, $path) {
                $folder_uid = getFolderUid($c, $path);
                $nxql = "SELECT * FROM Document WHERE ecm:parentId = '".$folder_uid."' AND ecm:currentLifeCycleState <> 'deleted' ORDER BY dc:title";
                $operation = $c->automation('Document.Query')->param('query', $nxql);
                $result = $operation->execute(Documents::className);
                return $result;
        }

        $url = "https://ged-dev.univ-lille.fr/nuxeo";
        $login = "Administrator";
        $login_uid = "1940";
        $password = "mysecretpassword";
        $key = "mysecretkey";

        //$client = new NuxeoClient($url, $login, $password);
        $client = new NuxeoClient($url);

        $client->setAuthenticationMethod(new PortalSSOAuthentication($key, $login_uid));

        $client->schemas('*');

        $documents = getFilesOfDir($client, "/default-domain/workspaces/Service DSI/Test");

        foreach($documents->getDocuments() as $document) {
                echo "---------------------------------------------------------\n";
                echo "UID = [" . $document->getUid() . "]\n";
                echo "Path = [" . $document->getPath() . "]\n";
                echo "Type = [" . $document->getType() . "]\n";
                echo "State = [" . $document->getState() . "]\n";
                echo "Title = [" . $document->getTitle() . "]\n";
                echo "Description = [". $document->getProperty("dc:description") . "]\n";
                echo "Creator = [" . $document->getProperty("dc:creator") . "]\n";
        }

?>

in order to merge with master, finally for random_int your prefer use it in replace random?
you wish i test or you test? :)

Great,
About the random_int vs random, your code is already using it as I've already made the change in the PortalSSOAuthentication class.
I'll release that as a new Release Candidate but I think it will require the Documents being iterable first: you have to foreach($operation->execute(Documents::className)->getDocuments() as $document) while we should be able to foreach($operation->execute(Documents::className) as $document.

Hello my developer don't found the method setAuthenticationMethod in NuxeoClient class.
Can you make a new release with the code from master in order to update the packagist.org and in order to permit my developer to do "composer update" ? and get the setAuthenticationMethod ? please? Thanks!

Hello, you have forgotten to merge feature-authent-sso with the branch 1.5.0-rc2.
Can you merge? please?
Thanks!

Hi,
I have some work to finish in order to release a new Release Candidate, until then you can change the version in your composer.json with:
"require": {
  "nuxeo/nuxeo-automation-php-client": "1.5.x-dev",
}

thanks for your answer i test with my developer :)

it doesn't work :(
mhetru@php56-1-dev:~/public_html/reprise_nuxeo4$ composer require nuxeo/nuxeo-automation-php-client 1.5.x-dev
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install symfony/symfony v2.7.22
    - Conclusion: don't install nuxeo/nuxeo-automation-php-client 1.5.x-dev
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.0].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.0-BETA1].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.0-BETA2].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.1].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.2].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.3].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.4].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.5].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.6].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.10].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.11].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.12].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.7].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.8].
    - roave/security-advisories dev-master conflicts with symfony/symfony[v2.7.9].
    - nuxeo/nuxeo-automation-php-client 1.5.x-dev requires roave/security-advisories dev-master -> satisfiable by roave/security-advisories[dev-master].
    - Conclusion: don't install nuxeo/nuxeo-automation-php-client 1.5.x-dev|don't install paragonie/random_compat v1.4.1
    - Conclusion: don't install symfony/symfony v2.7.21
    - Conclusion: don't install symfony/symfony v2.7.20
    - Conclusion: don't install symfony/symfony v2.7.19
    - Conclusion: don't install symfony/symfony v2.7.18
    - Conclusion: don't install symfony/symfony v2.7.17
    - Conclusion: don't install symfony/symfony v2.7.16
    - Conclusion: don't install symfony/symfony v2.7.15
    - Conclusion: don't install symfony/symfony v2.7.14
    - Conclusion: don't install symfony/symfony v2.7.13
    - Conclusion: don't install paragonie/random_compat v2.0.4|don't install symfony/symfony 2.7.x-dev|install paragonie/random_compat v1.4.0|install paragonie/random_compat v1.4.1
    - Conclusion: don't install paragonie/random_compat v1.4.0
    - Conclusion: don't install paragonie/random_compat v2.0.3
    - Conclusion: don't install paragonie/random_compat v1.3.0|install paragonie/random_compat v2.0.3|install paragonie/random_compat v2.0.4
    - Conclusion: don't install paragonie/random_compat v2.0.2|don't install symfony/symfony 2.7.x-dev|install paragonie/random_compat v1.3.0|install paragonie/random_compat v1.3.1|install paragonie/random_compat v1.4.0|install paragonie/random_compat v1.4.1
    - Conclusion: don't install paragonie/random_compat v1.3.1|install paragonie/random_compat v2.0.3|install paragonie/random_compat v2.0.4
    - Installation request for symfony/symfony 2.7.* -> satisfiable by symfony/symfony[2.7.x-dev, v2.7.0, v2.7.0-BETA1, v2.7.0-BETA2, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9].
    - Installation request for nuxeo/nuxeo-automation-php-client 1.5.x-dev -> satisfiable by nuxeo/nuxeo-automation-php-client[1.5.x-dev].
    - symfony/symfony 2.7.x-dev requires paragonie/random_compat ~1.0 -> satisfiable by paragonie/random_compat[1.0.10, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.2.x-dev, v1.0.0, v1.0.1, v1.2.0, v1.2.1, v1.2.2, v1.2.3, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.x-dev].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.10].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.2].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.3].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.4].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.5].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.6].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.7].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.8].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.0.9].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.0].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.1].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.2].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.3].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.4].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.5].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.1.6].
    - Can only install one of: paragonie/random_compat[v2.0.0, 1.2.x-dev].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.0.0].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.0.1].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.2.0].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.2.1].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.2.2].
    - Can only install one of: paragonie/random_compat[v2.0.0, v1.x-dev].
    - nuxeo/nuxeo-automation-php-client 1.5.x-dev requires paragonie/random_compat 2.0.* -> satisfiable by paragonie/random_compat[v2.0.0, v2.0.1, v2.0.2, v2.0.3, v2.0.4].
    - Conclusion: don't install paragonie/random_compat v2.0.1|don't install symfony/symfony 2.7.x-dev|install paragonie/random_compat v1.2.3|install paragonie/random_compat v1.3.0|install paragonie/random_compat v1.3.1|install paragonie/random_compat v1.4.0|install paragonie/random_compat v1.4.1
    - Conclusion: don't install paragonie/random_compat v1.2.3|install paragonie/random_compat v2.0.2|install paragonie/random_compat v2.0.3|install paragonie/random_compat v2.0.4

i'm waiting the new release.
until i use a forked bundle :)

i am blocked, i got the same errors even with a bundle forked with the branche feature-authent-sso :( have you an idea?

Hi, I've released the 1.5.0-rc3, it should fix your issues.
If you have troubles, let's open a dedicated issue.

authors: mhetru nuxeojenkins pgmillon

repo: nuxeo/nuxeo-automation-php-client