lzma: 5.2.4 -> 5.2.5

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xz/versions.
meta.description for lzma is: "XZ, general-purpose data compression software, successor of LZMA"
meta.homepage for lzma is: "https://tukaani.org/xz/"
Updates performed:

Version update
Quoted meta.homepage for RFC 45

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.2.5 with grep in /nix/store/b24kv0yi3sjs4nygkba0k6np0rh2bcnz-xz-5.2.5-bin

directory tree listing: https://gist.github.com/199c0d31d5ab3b13c655e61fde6781a6

du listing: https://gist.github.com/bd5373fe9533ea4d2195fd3e409980c6

Rebuild report (if merged into master) (click to expand)

110635 total rebuild path(s)
33859 package rebuild(s)
33720 x86_64-linux rebuild(s)
29924 i686-linux rebuild(s)
23633 x86_64-darwin rebuild(s)
23358 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
AMB-plugins
AgdaSheaves
AgdaStdlib
CoinMP
DisnixWebService
EBTKS
EmptyEpsilon
FIL-plugins
Fabric
LASzip
Literate
MMA
NSPlist
OVMF
OVMF-CSM
OVMF-secureBoot
PlistCpp
QuadProgpp
R
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL_Pango
SDL_gfx
SDL_gpu
SDL_image
SDL_mixer
SDL_net
SDL_sixel
SDL_sound
SDL_stretch
SDL_ttf
SPAdes
SkypeExport
Sylk
TotalParserCombinators
Xaw3d
_0x0
_1password
_2048-in-terminal
_20kly
_2bwm
_389-ds-base
_3llo
_3proxy
_6tunnel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b24kv0yi3sjs4nygkba0k6np0rh2bcnz-xz-5.2.5-bin \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lzma https://github.com/r-ryantm/nixpkgs/archive/18482042bbda00419507c6f770786814cdb64f0e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b24kv0yi3sjs4nygkba0k6np0rh2bcnz-xz-5.2.5-bin
ls -la /nix/store/b24kv0yi3sjs4nygkba0k6np0rh2bcnz-xz-5.2.5-bin/bin

cc @svanderburg for testing.

@worldofpeace Can you merge this? it's a minor/inconsequential update as far as I can see.


chore(main): release 0.2.3

:robot: I have created a release beep boop
0.2.3 (2024-06-11)
Bug Fixes

refactored autoform (3916174)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.2.3
:sunflower:


Can't se any Docs in faction screen

Hello If have an issue with the Plugin.
I have add everything what the readmefile Said i have to add.
It Takes a while for me untill i understand that i need a new Ressource called Like that i set in the configs but i also have a Ressource called rolelife-docs now.
Anyway there are no documents in factionscreen.
If i use /fadddocs they shown in mongoDB but Not ingame
If i try to a new File over the factionscreen i dont see it anywhere
Excuse my bad english

okay now it works. i failed with the dependencies.
but if i click to creat new the editor shown but it doesn't creat a new file and it doesn't save the files if i click to save while i edit it


Radar not showing up in any instance

Hello,
Im having some trouble with the add on, up until a few days ago it seems like it was working fine but now when I enter an instance the radar remains hidden and if I force it to appear with the "show boss module demo out of instance" option it does appear inside the instance but its just that, the demo and it wont really show anything but my character arrow moving inside of it. Here are the logs, I hope someone can help me with this, I went to a abyssos 8 normal before uploading the log so that the situation where the radar doesnt show up would happen again.
dalamud.log
Thank you.

When I force it to show the demo out of instances it looks like this...

and whenever im inside of an instance and I force show it it looks like this:

if shows me moving around but the demo "me" and demo aoe still shows there, none of the actual mechanics show there tho

and these are my settings if it helps anything...

Ok so I read the stuff about the logs that I should post lol, sorry about not doing it sooner, I entered an abyssos 8th floor normal so I could recreate the situation and here are the logs:
dalamud.log

There is no support for EW normal raids.


Engineering Firms

Full name: Site Development and Planning, PC
Short name: SECI
Project ID: 104355

Name: Gray Engineering Consultants, Inc
Project ID: 10801

SECI and Gray Engineering added

Name: Piedmont Land Design, LLP
Project ID: 102858

Name: Blackburn and Consulting Engineering
Project ID: 105726
Thanks!

All additions complete to this point.

Please add: Huge J Gilleece & Associates
Project ID: 105047

Hugh***

Engineering Firm: Garrett and Moore, PLLC
Project ID: 108162

Steve,
Will you please add the following
Firm: Eric L. Thompson & Associates, P.C.
Project: Foxborough Crossing - 102385.
Thanks

Added.
Steven Kaufman PLS, GISP
GIS Technician
Capital Improvements Management Division
City of Raleigh – Public Utilities Department
919.996.5903 voice
From: egreen3385<EMAIL_ADDRESS>Sent: Tuesday, June 30, 2015 10:01 AM
To: City-of-Raleigh-Public-Utilities/PUMPR
Cc: Kaufman, Steven
Subject: Re: [PUMPR] Engineering Firms (#39)
Steve,
Will you please add the following
Firm: Eric L. Thompson & Associates, P.C.
Project: Foxborough Crossing - 102385.
Thanks
—
Reply to this email directly or view it on GitHubhttps://github.com/City-of-Raleigh-Public-Utilities/PUMPR/issues/39#issuecomment-117195474.
“E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized City or Law Enforcement official.”


home-manager: race condition with certain services

I use syncthing via home-manager, so I have to bind-mount its mutable directories. The problem is that both the bind-mount and syncthing itself are started via systemd, so syncthing may start and recreate its configuration from scratch before bindfs gets a chance to do its thing.
My current solution is to turn the bindfs unit into a forking-type systemd unit and make the syncthing unit depend on it. Is there a known better solution? If not I will PR my patch.

I've created a follow-up PR (#62) to address the second part of your issue. Can you try it out without adding dependencies to the syncthing unit and see if it still works?


net/virtual: test case need have random generator driver

add below to fitler out correct platforms
filter: CONFIG_ENTROPY_HAS_DRIVER
Signed-off-by: Hake Huang<EMAIL_ADDRESS>

The prj.conf file has CONFIG_TEST_RANDOM_GENERATOR=y, why that is not enough, why do we need to add the filter?

it is for testing filter, the west scripts will use testcases.yml to find dependency.


Just enchantment, can you add a JAR download link?

Yep, can u add a JAR file download link for easy add to project. Thx

cmon i didn't see )


Add .DS_Store to .gitignore for cursorless-talon

When this is synced to cursorless-talon the .gitignore in the monorepo doesn't apply so copy the .DS_Store ignore for those on macOS to prevent spurious untracked content messages in git.
I don't think the checklist below applies in this case.
Checklist

[ ] I have added tests
[ ] I have updated the docs and cheatsheet
[x] I have not broken the cheatsheet

Thanks!


Clean up the error message decoder

Now that we're on API v3 endpoints exclusively, we can expect more consistent error messages.
Fixes #183

Ready for review @heroku/api

LGTM!

LGTM

Thanks!


Have difficulties to run

Hello,
This is a very good example for using bluetooth with intel Edison and Curie.  I followed the steps and have some difficulties to run "node sensor.js".  I got the following errors:
root@edison:~/edison-arduino101/edison# node sensors.js
**module.js:338
throw err;
^
Error: Cannot find module '../build/Release/binding.node'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/home/root/edison-arduino101/edison/node_modules/noble/node_modules/bluetooth-hci-socket/lib/native.js:3:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
**
I though it was due to node.js version issue (image from intel was  version 0.10.38-r0).  So I upgraded the node.js to latest version:
root@edison:~/edison-arduino101/edison# opkg list nodejs
nodejs - 0.12.7-r1 - nodejs version 0.12.7-r1  nodeJS Evented I/O for V8 JavaScript
But still got the same error.  It turns this error happens at the first line of sensor.js:
var noble = require('noble');
I tried to remove all the node_modules under /edison, and reinstall all modules by "npm install".  It doesn't help.
Here are the modules versions installed:
root@edison:~/edison-arduino101/edison# npm -v noble
1.4.28
root@edison:~/edison-arduino101/edison# npm -v socket.io-client
1.4.28
root@edison:~/edison-arduino101/edison# npm -v bluetooth-hci-socket
1.4.28
I have stuck on this for one week, any help will be greatly appreciated.
Many thanks....
-Tom

Hi Tom, sorry to hear you've been having issues. Can you double-check that you have systemd-dev installed via opkg and async installed globally using npm -g install async? Then, try removing your node_modules folder and re-installing.

Hi Kim,
Thank you very much for the quick response.  I redo the whole procedure and this time everything works.  I don't need to upgrade the node.js to the latest version.  I might made a mistakes somewhere. After I strictly follow your writeup, everything works !
Many thanks again !!

Awesome! Glad it's working now!

Hello Esther,
Your instructions are very helpful.  I have followed it and finished most of the exercises !
My goal is to use one Edison module for receiving data from Curie module, and to server as a web server.  Do you think if this is possible ?  I am trying to figure out how to modify the codes...  Any suggestions ?
Thanks a lot,
-Tom

From: Esther Jun Kim<EMAIL_ADDRESS>Sent: Saturday, April 30, 2016 3:15 PM
To: drejkim/edison-arduino101-iot
Cc: tom6870; Author
Subject: Re: [drejkim/edison-arduino101-iot] Have difficulties to run (#1)
Closed #1https://github.com/drejkim/edison-arduino101-iot/issues/1.

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/drejkim/edison-arduino101-iot/issues/1#event-646598437


[RELENG-7422] 📝 Add tags documentation

We won't be merging this PR and going forward with this work.


Keep verify setting when no CA_BUNDLE variable exists

If the trust_env flag is set on a session and verify is True
or None, the environment is checked for CURL_CA_BUNDLE and
REQUESTS_CA_BUNDLE. Before this patch, if neither existed,
verify would always be set to None rather than True when it
was originally True.
I found this while working on a patch for https://github.com/kennethreitz/requests/issues/3633.

@Lukasa I've adjusted the test.

@Lukasa no worries. I haven't really worked with pytest and didn't see examples of patching in the existing tests so I got lazy :frowning_face:.

Hurrah! No need to worry @jeremycline, this is what code review is for! I'm delighted to say that I'm now happy with this patch, and ready to merge. Thanks so much! :sparkles: :cake: :sparkles:


Adding some details about the configuration file

This option was added in 0.3.0 but not well documented.  This should be enough to get people started.  Thanks for such an awesome gem!

.scss has become the default file extension in the meantime.  but I put the rest of your documentation into the README 38e64ce   thanks a lot


RIP gorpc tabletmanager. We have a fully functional gRPC version.

@enisoc @michael-berlin

LGTM

Very cool!


Major UX: Phase progress bar broken, gives impression that players/rounds get skipped

I started the game with three players on chrome desktop, Decider, Desktop 1, and Desktop 2. I made it to the start of the pitch phase without any issues. Desktop 1 got to pitch, and then chose not to buy any additional time. Then, the game's dialogue suggested that it was Desktop 2's turn to pitch, but the phase bar showed that the game had advanced to the next round, Deliberate, for all players.

After Desktop 2 finishes its pitch (with the phase bar still in "Deliberate"), the game's dialogue implies that the game is moving into the "Deliberate" stage, but the phase bar shows the game has advanced:

After the "deliberation" time has finished (with the phase bar still at "Decide"), the game appears to entirely skip the "decide" round (at least from a UX perspective), jumping straight to "score" while the decider chooses the winner.

Should be resolved via 87d185cee2df306ce78dc0bcd23e477d043721eb.


Update python build to work with rust compiler from stable release channel

I'm getting build failures when running pip install celery-exporter on a system with rustc 1.39.0 compiler installed on it:
    error[E0554]: #![feature] may not be used on the stable release channel
     --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pyo3-0.7.0/src/lib.rs:1:1
      |
    1 | #![feature(specialization)]
      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^

    error: aborting due to previous error

    For more information about this error, try `rustc --explain E0554`.
    The following warnings were emitted during compilation:

    warning: pyo3 was unable to check rustc compatibility.
    warning: Build may fail due to incompatible rustc version.

    error: Could not compile `pyo3`.

I'd like to use this library but don't think I can if it is not based on a rust environment from the stable release channel.
Is there a reason why this package relies on a rust environment based on nightly-2019-06-20?

it'a pyo3 issue that is tracked here

This still doesn't work. Can't build with nightly rust also. PyO3 error is constant.


Support inlining of simple functions.

This change is

crates/cairo-lang-lowering/src/lower/inline.rs line 95 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
This should not be possible at the root block. You can panic.

It happes when you are doing
#[inline]
fn bar() -> felt {
1
}

crates/cairo-lang-lowering/src/lower/inline.rs line 21 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
Use ctx.new_var()

isnt it wasteful to do the type_info lookup again?

crates/cairo-lang-lowering/src/lower/inline.rs line 21 at r2 (raw file):
Previously, ilyalesokhin-starkware wrote…
isnt it wasteful to do the type_info lookup again?

new_var borrows ctx.

crates/cairo-lang-lowering/src/lower/mod.rs line 516 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
This could potentially cause cycles. See above.

only if you put #[inline] in the wrong place.

crates/cairo-lang-lowering/src/lower/mod.rs line 516 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
And you would crash the compiler, yes.

I think we are ok with that.

crates/cairo-lang-lowering/src/lower/mod.rs line 516 at r2 (raw file):
Previously, ilyalesokhin-starkware wrote…
I think we are ok with that.

you can also crash it with a wrong extern decleration

crates/cairo-lang-lowering/src/lower/mod.rs line 504 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
The lowering should be done in a separate phase, no in the main lowering phase.

To reduce complexity from this phase.
To not crash on cycles, and even allow them when inlining (kind of loop unrolling),

Are you suggesting a phase that only goes over things looking for
StatementCall
?

crates/cairo-lang-lowering/src/lower/inline.rs line 21 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
MAke rename_var accept ctx as a parameter. Right now, your rename_var borrows ctx.variables. You don't use it in anymore in the body, but it's not the best pattern, since it prevents you from passing ctx to subfunction, if you wanted to split your code to functions, for example.

it would make it a lot more cumbersome to use in maps :(

crates/cairo-lang-lowering/src/lower/mod.rs line 516 at r2 (raw file):
Previously, orizi wrote…
we are not really ok with it - we want to fix both.
if you have a plan on how to fix it here - add a todo.
note that we already have an option to read

what is "an option to read"?

crates/cairo-lang-lowering/src/lower/inline.rs line 95 at r2 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
I don't understand how this can work. It doesn't make sense.

can you elaborate?

crates/cairo-lang-lowering/src/lower/inline.rs line 70 at r12 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…

Why don't we support this?
This check isn't equivalent to "no ref arguments"
arguments -> params
initial_regs includes implicits. We don't support that too?

it would make the PR larger.
why not?
ok
in this PR we don't support that.

crates/cairo-lang-lowering/src/lower/inline.rs line 108 at r12 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
Again, note that this includes implicits. Are we sure that's what we want?

yes

crates/cairo-lang-lowering/src/lower/inline.rs line 190 at r12 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
Is this just temporary?

yes

crates/cairo-lang-lowering/src/test.rs line 78 at r12 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
Shouldn't this test sit in another rust file, maybe under the inline module? inline_test.rs?

I'm hoping this could be merged with the other lowering test.

crates/cairo-lang-lowering/src/inline/mod.rs line 203 at r14 (raw file):

            lowered.blocks[root_block_id].inputs.iter().cloned(),
            inputs.iter().cloned()
        ));

@spapinistarkware
is it ok to make different variable
in    lowered.blocks[root_block_id].inputs to the same variable?
e.g.
lowered.blocks[root_block_id].inputs = [1, 2]
inputs = [1,1]
Code quote:
        // The input variables need to be renamed to match the inputs to the function call.
        let mut renamed_vars = HashMap::<VariableId, VariableId>::from_iter(izip!(
            lowered.blocks[root_block_id].inputs.iter().cloned(),
            inputs.iter().cloned()
        ));


[Feature Request] Ability to reorder and default parameters in customization

Describe the issue or request
Today, there isn't great support for reordering and setting defaults without wrapping the generated API yourself.
Describe your ideas for solutions
Run generator as-is. I get:
public virtual Task<Response> SendToUserAsync(string userId, string contentType, RequestContent requestBody, RequestOptions requestOptions = null);

Add an override file with:
    public class WebPubSubService
    {
        [Operation("WebPubSubService_SendToUser")]
        public extern virtual Task<Response> SendToUserAsync(string userId, RequestContent requestBody, string contentType = "application/json", RequestOptions requestOptions = null);
    }

Which tells the generator to rearrange parameters and default one of them

If done, this is a superset of https://github.com/Azure/autorest.csharp/issues/1228

Possible Implementation Notes:
In general this is "customizations of methods":

Visibility
Param type
Ordering
Default

Ideas

#1 - One idea is to have a list of extern methods not included in project. But not how we parse other customizations.
#2 - Another idea is to use partial methods (like we do other customization).
#3 - Another (hacky) solution is to just write out what we're given, but it falls apart if we rename parameter or change types

If we don't just hack solution #3, then we need to parse the partial and understand what params are given.

Might need to do it bite by bite, say visibility. Match visibility. If I have method you like, and codegen attribute for renaming.
Biggest concern - The building parameter list is already scary code, and we have to reconcile two collections (original def and partial definition).
Where would we do this for DataPlane? Developer wants to customize external client but we reflect this from REST client. Do we pipe both to rest and public client? Forcing rest client customization is :( If we don't customize rest then big difference from LLC. If we don't allow DataPlane customization then it hurts grow up.
Need to test this for DataPlane and LLC for sure.

Estimate:
3-4 for Names/Accessibility (LLC only)
3-4 for Param Ordering/Renaming (LLC only)
DataPlane - ?


Feature/ha discovery

This is a work in progress, but wanted to get some early feedback. The main contributions of this PR are:

Implemented support for home assistant discovery (https://github.com/DennisOSRM/hms-mqtt-publisher/issues/17)
Add extra sensors (https://github.com/DennisOSRM/hms-mqtt-publisher/issues/14)

Other notable changes / additions:

added vscode devcontainer support and debug launch configuration to simplify development for future contributors
add serde dependency for json serialization
version bump to 0.2.0 because of breaking changes (mqtt paths change)
refactor log init into its own module
add mock_state function to inverter for testing purposes

Note that this is my first time developing in rust and there's probably a lot of things to improve / things that an experienced rust developer would've probably done differently. I'm happy to receive some constructive feedback and improve where necessary :-)
TODO:

update home assistant addon once PR is merged / docker build is ready
make home assistant prefix configurable (https://github.com/DennisOSRM/hms-mqtt-publisher/issues/25)

Thanks for the PR. It will take a couple of days before I can get around to reviewing this.
From a quick glance, it seems this PR contains a couple of things that likely should be seperate PRs, and the testing code perhaps should not bleed into the implementation. That being said, this isn't a comprehensive review and just an initial impression.
Thanks for the contribution, please keep up the great work.

Thanks for your comprehensive review!

remove the development related files and directories

I will create a separate PR for this

the testing code should be done in a distinct PR without having to branch between test and non-test code.

Good point. Didn't have time to address this properly so just hacked in something quickly that allowed me to do some minimal testing during the addon development. I will remove the testing related code for now

move structs into their own source file

Will do. Wasn't sure how to structure it or whether it's necessary to split the mqtt implementation up in two parts, one for home assistant, one without home assistant support.

consider using protobuf_json crate instead of the rolling your own conversion to json

Thought about this as well, but since the values are scaled during the serialization, I decided to just do it the manual way. I assume the protobuf schemas won't often if at all, so I hope that's okay.

implement the auto discovery in a non-breaking way

The breaking change is unfortunate. But apart from home assistant support, another upside is that it would allow utilizing multiple inverters in the future (part of the serial number is added to the topic). Another part of the breaking change is that the whole update is sent json-encoded to a single topic instead of splitting it to multiple topics. This should make it more efficient in combination with home assistant (and possibly other endpoints)

The breaking change is unfortunate. But apart from home assistant support, another upside is that it would allow utilizing multiple inverters in the future (part of the serial number is added to the topic). Another part of the breaking change is that the whole update is sent json-encoded to a single topic instead of splitting it to multiple topics. This should make it more efficient in combination with home assistant (and possibly other endpoints)

That's a good point. Thanks for the clarification. I think the json-encoded single topic could be done independently, is that right? If so, we could first add things, and consider the breaking change at a later point. Would this make sense?

Yes, we could change the home assistant device configurations and publish on separate topics to delay the breaking change. But if we're certain it's going to happen sooner or later (and I think supporting multiple inverters is a enough good reason), delaying the breaking change will only cause more users to be affected.
While we're at it we should also remove the "800W-2T" references, e.g. from the topic, to prevent a future breaking change.

Ok, that's a convincing argument. Let's do the breaking change now, and aim at the same time to minimize the size of this PR.

I think I addressed all of the review comments and fixed some additional bugs. Here's an example of the provided data in home assistant:

In order to enable these changes in the addon, we first need an image on docker hub that I can reference in the Dockerfile of the home assistant addon. I have a build running right now, but it's taking a while. I will hopefully push another update tomorrow when it's done

Very cool. Please have a bit of patience, since it will again take a couple of days before I can get to it.

I did a very hasty implementation of output channels (cf. https://github.com/DennisOSRM/hms-mqtt-publisher/pull/27#pullrequestreview-1746689155) on top of your PR: https://github.com/DennisOSRM/hms-mqtt-publisher/pull/34/commits/7460c0e6194d36540d5682457d884d2e632e5074

Sorry I was preoccupied with my day job and family. I'll have a look at the output channels PR

No worries. Life comes first, hacking on code second. 😉


Publish lakeFS to Maven Central

Part of #2079.

Published 2 SNAPSHOT JARs to Maven Central, with and without assembly.  Have a look at https://s01.oss.sonatype.org/#nexus-search;quick~hadoop-lakefs.

Thanks, pulling!
Doesn't entirely do #2079 because it's not yet on S3.

@talSofer actually it prints a scary warning when changing the artifact ID based on profile:
[WARNING]
[WARNING] Some problems were encountered while building the effective model for io.lakefs:hadoop-lakefs-assembly:jar:0.1.0-RC.0-SNAPSHOT
[WARNING] 'artifactId' contains an expression but should be a constant. @ io.lakefs:hadoop-lakefs${name-suffix}:0.1.0-RC.0-SNAPSHOT, /home/ariels/dev/lakeFS/clients/hadoopfs/pom.xml, line 7, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

So it will work for now, but may get interesting in future.


[Bug] [API] Add language to user api

close #8961

Codecov Report

Merging #9215 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #9215      +/-   ##
==========================================
+ Coverage   41.02%   41.02%   +<.01%
==========================================
  Files         553      553
  Lines       72141    72142       +1
==========================================
+ Hits        29593    29599       +6
+ Misses      38816    38810       -6
- Partials     3732     3733       +1

Impacted Files
Coverage Δ

modules/convert/convert.go
79.11% <100%> (+0.08%)
:arrow_up:

models/repo_list.go
73.14% <0%> (-0.93%)
:arrow_down:

modules/log/file.go
77.62% <0%> (+2.09%)
:arrow_up:

modules/indexer/indexer.go
55.26% <0%> (+10.52%)
:arrow_up:

Continue to review full report at Codecov.

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

@lunny smal bugfix :D

@lunny ready for merge :rocket:


New Input System Package Warning popup

Hello,
It looks like since the last upgrade of cesium 1.1.0, i've this popup when opening our Unity project.
Do you've changed something on your side about this ?

Please post questions like these on the community forum. We reserve Github for confirmed bugs and feature requests.
We added the InputSystem package as a dependency so people would stop seeing compiler errors about not having it in their project. You can always revert to the legacy input system for your own needs. In the future, you can see the full change log for the newest release here.

Ohh ok

Please post questions like these on the community forum. We reserve Github for confirmed bugs and feature requests.

It is not about not knowing how to change from New to Old input system. It is annoying to have this popup when the project is still using the old input system.

We added the InputSystem package as a dependency so people would stop seeing compiler errors about not having it in their project. You can always revert to the legacy input system for your own needs. In the future, you can see the full change log for the newest release here.

But thanks for answering


psiphon3@180: hash check failed

ERROR Hash check failed!
App:         extras/psiphon3
URL:         https://psiphon.ca/psiphon3.exe
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    10b0c790884207a46e4052786fdeb2e04b415c150339001d3537cf7e56f6c21f
Actual:      520cf7b69736565ba355081e3c4184800b9931b6c7253cc6c47c2c1646c88700
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=psiphon3%40180%3A+hash+check+failed

seem to have it now , my apologies


create istio-announce@ or remove reference to it; ditto for twitter account

at the bottom of https://istio.io/blog/0.1-announcement.html
it says
"And follow @istio on Twitter or join istio-announce@ for key announcements regarding the project."
that group/list doesn't exist yet. once it exist it should be a hyperlink (probably so does the twitter link (happy to do the linking once it exist))
source is https://github.com/istio/istio.github.io/blob/master/_posts/2017-05-01-0.1-announcement.md

https://twitter.com/istio is someone else so we need to change that too

The group has been created and I linked to it from the docs.
I opened a separate issue to track the creation of a Twitter account, and adding it to a few spots in the docs. I also created an issue to track the completion of the release announcement blog post (what we have in the repo right now is just a snapshot of WIP)


Don't make things null in Dispose

src/Microsoft.AspNet.WebUtilities/HttpRequestStreamReader.Dispose nulls out properties. According to @Tratcher https://github.com/aspnet/HttpAbstractions/pull/539#discussion_r49917289 we should instead set up a disposed bool so we don't accidentally get nullrefs.

Not against following a more traditional pattern if it makes people happy, but look closer at the code. The stream null-check is used where you'd normally see if (_disposed) it's functionally the same.

Until there are race conditions, then null refs. It's a defensive practice. Nulling things out doesn't help the gc in any meaningful way.

Moving this to Backlog as we will be in RC2 ask mode very soon.  If you feel strongly about this issue, please ping me.


I'm looking for version 1.50.0

1.50.0 is a pretty significant update and, crucially, will enable Rocket to be built with stable.
I tried this locally and it seems to work ok.

master is now at 1.51, @softprops just needs to push a new tag to publish the new image I believe!

I know it's been a while since you opened this issue but you can get around this for local development by cloning the repo and doing:
> docker build
# lots of output, assume went OK

> docker image list
REPOSITORY               TAG                  IMAGE ID       CREATED         SIZE
<none>                   <none>               <IMAGE ID>     3 minutes ago   2.28GB
lambci/lambda            provided             c33a39474d91   2 months ago    701MB
sls-docker-provided      latest               c33a39474d91   2 months ago    701MB
lambci/lambda            build-provided.al2   79af384846a7   2 months ago    1.57GB
softprops/lambda-rust    0.2.7-rust-1.43.1    4fa341bf5218   10 months ago   2.49GB

# copy <IMAGE ID> for the image you just built, in my case `9e8c78b4e171`, then:

> docker tag <IMAGE ID> james-tru/lambda-rust:1.3.0-rust-1.51.0
# no output if OK

finally, if you're using softprops/serverless-rust, update serverless.yaml with:
custom:
  rust:
    dockerImage: 'james-tru/lambda-rust'
    dockerTag: '0.3.0-rust-1.51.0'


Views array fatal error

        var views:[UIView] = []
        let view1 = UIView()
        view1.backgroundColor = UIColor.redColor()
        let view2 = UIView()
        view2.backgroundColor = UIColor.greenColor()

        view.addSubview(view1)
        view.addSubview(view2)

        views.append(view1)
        views.append(view2)

        view.groupAndFill(group: .Horizontal, views: views, padding: 10)

fatal error: array cannot be bridged from Objective-C

I'm not sure why, but a workaround is:
view.groupAndFill(group: .Horizontal, views: views.map { $0 }, padding: 10)

I think it's a Swift bug. Haven't looked into it yet though.

What version of Swift/Xcode are you on?


upgrade to org.apache.httpcomponents:httpclient:4.5.1 for CookieSpecProvider

Upgrade because I've confirmed that httpclient-4.1 will cause https://github.com/groupon/DotCi-Plugins-Starter-Pack/issues/9
Caused by: java.lang.ClassNotFoundException: org.apache.http.cookie.CookieSpecProvider

Therefore you want httpclient-4.5.1 for https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/cookie/CookieSpecProvider.html
now available as-of https://github.com/apache/httpclient/commit/8901aed4949de2d597e09f645dfb2a0507839483 in 4.3+

now available in DotCi-2.27.0

now available in DotCi-2.27.0


ovh-ttyrec: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ovh/ovh-ttyrec/releases.
meta.description for ovh-ttyrec is: "Terminal interaction recorder and player"
meta.homepage for ovh-ttyrec is: "https://github.com/ovh/ovh-ttyrec/"
meta.changelog for ovh-ttyrec is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>/bin/ttytime passed the binary check.

/nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>/bin/ttyplay passed the binary check.

/nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>/bin/ttyrec passed the binary check.

3 of 3 passed binary check by having a zero exit code.

2 of 3 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>

found <IP_ADDRESS> in filename of file in /nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>

directory tree listing: https://gist.github.com/c2ac09e48b878a04dd9f866452caa76e

du listing: https://gist.github.com/0c5b2ee2e55b164e9ad364e4b714c5aa

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
ovh-ttyrec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ovh-ttyrec https://github.com/r-ryantm/nixpkgs/archive/1de986d80a25b002313b149ff10f0869945580d1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>
ls -la /nix/store/322s828yvi7cx0np5nc444clphx07ppn-ovh-ttyrec-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ttyrec (ovh-ttyrec)

Maintainer pings
cc @charles-dyfis-net @zimbatm for testing.

Result of nixpkgs-review pr 118529 at 1de986d8 run on x86_64-linux 1

1 package built successfully:

ovh-ttyrec

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/misc/ovh-ttyrec/default.nix:16:3:
   |
16 |   installPhase = ''
   |   ^


Fix AFNetworking UIWebView extensions migrated to WKWebView

I've tried to remove the UIWebView references + extensions in favor of the WKWebview. Since Apple now throws warnings when submitting apps with UIWebView references (and soon will start rejecting apps using UIWebViews). I have NOT tested this myself since time constraints, also I don't really know if the Unit tests are correct with the WKNavigation object.

Duplicated of #4417.

Hey everybody, #4439 is available and passing all CI tests. We have one dependency on one of our projects that uses this lib so we would like to see this addressed and a new version of AFNetworking pushed out.
Does anybody here have a direct comm channel with one of the maintainers?
Thanks!

Closing in favor of #4439. We'll get this released, but since it's such a breaking change we'll have to do it as a version 4. In the meantime we'll work on a 3.4 release to fix as many bugs as possible and then move to the more breaking changes.

Hi @jshier, I've encountered this problem and my app can't be published until the release of the version 4, the one without UIWebView.
Do you have an estimated date for the release of this breaking change version? Or can I use some workaround to get my app publishable again?
My problem is that I need to use the methods contained in the UIKit subspec, in particular the ones contained here #import <AFNetworking/UIImageView+AFNetworking.h> and here #import <AFNetworking/AFImageDownloader.h>.
Thank you in advance for your time and your patience.
Have a nice day,
Davide

I confirm UIWebView is still part of AFNetworking 3.2.1
@davide1945 a quick and temporary workaround is to edit the AFNetworking pod :

remove UIWebView+AFNetworking.h/.m from the lib (you can uncheck them from the target membership panel
go to UIKit+AFNetworking.h and comment #import "UIWebView+AFNetworking.h"
go to AFNetworking-umbrella.h and comment #import "UIWebView+AFNetworking.h"

Note that this is a temporary workaround, and you will do it again each time you pod update.

@jshier Any updates on this? April is coming quick, and we need to get this fix in our apps ASAP. Can you at least give us an estimate on when you think it will be available? Thanks.


Fix operator reconcile loop - pass existing PostgreSQL credentals

Backstory
Backstage chart uses bitnami/postgresql chart as a DB provider. When this chart is initially installed it generates credentials for the new database. New credentials are generated, passed to the database pod, and also stored in a Kubernetes Secret. This Secret is in turn mounted to the Backstage pod. Backstage then uses these credentials to access the DB.
When a helm upgrade is triggered (the operator does reconcile through helm upgrade), given credentials are regenerated, new password is created for the secret. However, the DB is already seeded with the original credentials so the new password is ignored by the DB. Unfortunately, that's not the case for the Backstage pod, which receives the new credentials which are invalid for the DB.
Solution
Implement a logic that would check for DB credentials Secret in the target namespace and if found, make it enforce this Secret as .upstream.postgresql.auth.existingSecret value. This would ensure new credentials are not generated and "old" password remains in use by the Backstage pod.

If so, will the secret config name always have a suffix of -postgresql?

It doesn't always have to be with this suffix.
The secret name is generated using this macro https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_names.tpl#L34. Someone can override Chart name name using nameOverride in values.yaml and than it will have suffix based on that new name.


Route constraints which contain a period do not work without trailing '/'

If you try to define a custom route products/{category:alpha}/{id:regex(\d+.\d+.\d+)} it will match requests like https://function-fun.azurewebsites.net/api/products/electronics/1.2.3/ but not https://function-fun.azurewebsites.net/api/products/electronics/1.2.3 (no trailing slash).

We've tried two things that seem to fix it:
<system.webServer>
  <modules>
    <remove name="UrlRoutingModule-4.0" />
    <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" />
  </modules>
</system.webServer>

or
<system.webServer>
  <modules runAllManagedModulesForAllRequests="true" />
</system.webServer>

But we'll need to make sure this doesn't regress cold start perf and functionality.

A little more update, checked freb logs on the requests, I'm pretty sure this handler change is causing managed modules (urlrouting in particular) to be skipped.  Explains why rammfar and the url routing module change (removing manage precondition) fix this.

Notes from triage: we suspect no perf impact on routes that we already handle, but we should do perf tests to confirm.

This is a problem with wildcards as well (I'm using node.js):
      "route": "testpath/{*pathName}"

This works fine for any route unless the route has a filename with extension at the end (with or without query string).
Adding a trailing / does fix it.
Since I am using node.js, I'm not sure how to control the IIS settings mentioned above that are normally controlled by web.config.
Note: I also found another web.config setting mentioned that could be relevant:
<httpRuntime relaxedUrlToFileSystemMapping="true" />

From: http://stackoverflow.com/questions/294495/semantic-urls-with-dots-in-net#328873
Anyway, any ideas how to work around this for node.js?

@safihamid mentioned on stackoverflow that the dot issue - at least for functions proxies - is fixed now.
unfortunately it still does not work for me (i restarted the function app).
proxy.json
{
    "proxies": {
        "Proxy2": {
            "matchCondition": {
                "route": "/test.html"
            },
            "backendUri": "https://<funcapp>.azurewebsites.net/func1"
        }
    }
}

@mikezks please make sure you have updated the proxy version to ~0.1

Yes! The final piece to the puzzle!
Thanks Azure Functions team!
I can confirm this is working:
https://test-azure-functions-proxies.azurewebsites.net/file/file.json

@safihamid:
yes, i updated the proxy version before, but it did not work yesterday.
now everything is fine and i can confirm as well that this issue is resolved. thanks a lot! 😃

I just noticed that the dot issue still occurs for Azure Functions routing.
...but it is correct that it works for Functions Proxies.
Though this is not a big issue for me because we now have the workaround with Functions Proxies, this needs to be fixed one day. Thanks!

Indeed, I'm facing this in functions routing.
I've got:
      "route": "test/{owner:alpha}/{repo:alpha}/{sha:alpha}"

As soon as the client url contains a dot in any of the url patterns (i.e. test/kzu/foo.bar/baz), it stops matching. Adding a trailing / doesn't fix it for functions, neither any of the web.config workarounds mentioned here. :(

@kzu Note that you can't customize web.config when running on Azure Functions.
CC @mathewc and @fabiocav

@lindydonna fair. Still, the dot is broken if it shows up in any of the url patterns :(. Any suggested workarounds?

btw, I was hoping uploading a web.config via https://*.scm.azurewebsites.net/dev/wwwroot/ would work :(

Given the following proxy definition:
{
    "$schema": "http://json.schemastore.org/proxies",
    "proxies": {
        "root": {
            "matchCondition": {
                "route": "{owner}",
                "methods": [
                    "GET"
                ]
            },
            "backendUri": "https://APP.azurewebsites.net/test/{owner}"
        }
    }
}```

I see the following:

OK: http://APP.azurewebsites.net/test/foo
FAIL: http://APP.azurewebsites.net/test/fo_o
FAIL: http://APP.azurewebsites.net/test/fo.o
FAIL: http://APP.azurewebsites.net/test/fo`o
FAIL: http://APP.azurewebsites.net/test/fo o
FAIL: http://APP.azurewebsites.net/test/fo|o

(with appropriate URL escaping performed by the browser itself, they all fail with or without a trailing `/`).

Makes the routing very very brittle.

Note: I was looking for a way to turn the problematic dots into some fairly uncommon char just for routing and inside the function convert it back, and that's how I found that it's broken for at least a whole bunch of other chars.

Please try adding a slash in your proxy's config:
"backendUri": "https://APP.azurewebsites.net/test/{owner}/"
...I hope I remember this workaround correctly.

Below is how I do it with proxies, and it seems to handle dots fine.
(I use this for static file serving to a CDN and also something like this for my SPA apps where the app does internal routing.)
I use a wildcard and it seems to handle all sub routes which can be passed to a function.
Also, if you leave the route "" (blank), you can override the root index page. (But you have to edit the file manually because the Functions editor doesn't accept a blank route.)
{
    "$schema": "http://json.schemastore.org/proxies",
    "proxies": {
        "Static": {
            "matchCondition": {
                "route": "static/{*file}"
            },
            "backendUri": "https://told-stack-demo.azurewebsites.net/api/static?file={file}"
        },
        "Root": {
            "matchCondition": {
                "route": "",
                "methods": [
                    "GET"
                ]
            },
            "backendUri": "https://told-stack-demo.azurewebsites.net/api/static?file=demo/"
        }
    }
}

That's cheating ;). I also got it to "work" by having one route that consumes everything with {*everything} and making that a query string arg for the function. But the fact is that if the function has a route, any dots (or any other chars as I showed) don't work. Adding trailing slashes doesn't work either.
So, a "catch-all" route on the proxy, and no route at all possible in functions, is not a great experience, quite the contrary.

True, it would be nice if the function routing could accept any valid URL value.
(For example when doing Function Binding with BlobNames, it would likely have a dot in the parameter.)
At least the proxy can function as a work around, which we didn't have a few months ago.

Ran into this while building an HTTP API with dots in the route.
https://api.site.com/users.info
https://api.site.com/users.create
https://api.site.com/users.update
https://api.site.com/users.delete
Its not as common but is definitely legal routing. I agree the route should allow any valid URL.

Indeed @codeitcody

@mathewc any ideas when this is hitting production?

@kzu it's partially deployed. If you have the cycles, you can verify it in North Central US. It should reach everywhere on Tuesday.


App Deployment failed while deploying Asp.net core app n App Engine flexible enviornment

Encountered following error while trying to deploy Asp.net core application in GCP app engine flexible environment. Targeting netcore 2.2 version now. I've tried deploying netcore with 3.0 version. Both failed. Receiving same error in both scenarios. Please help. Attaching the error log.
Beginning deployment of service [default]...
Building and pushing image for service [default]
Started cloud build [b9478e4c-1e01-447b-81d7-090c5194a900].
To see logs in the Cloud Console: https://console.cloud.google.com/gcr/builds/b9478e4c-1e01-447b-81d7-090c5194a900?project=849277635841
----------------------------- REMOTE BUILD OUTPUT ------------------------------
starting build "b9478e4c-1e01-447b-81d7-090c5194a900"

FETCHSOURCE
Fetching storage object: gs://staging.cosmoapis.appspot.com/asia.gcr.io/cosmoapis/appengine/default.20191222t131443:latest#1577000842536701
Copying gs://staging.cosmoapis.appspot.com/asia.gcr.io/cosmoapis/appengine/default.20191222t131443:latest#1577000842536701...
/ [0 files][    0.0 B/  5.8 MiB]
/ [0 files][264.0 KiB/  5.8 MiB]
-
- [0 files][  4.1 MiB/  5.8 MiB]
\
\ [1 files][  5.8 MiB/  5.8 MiB]

Operation completed over 1 objects/5.8 MiB.
 Check logs at https://console.cloud.google.com/gcr/builds/b9478e4c-1e01-447b-81d7-090c5194a900?project=849277635841 Failure status: UNKNOWN: Error Response: [2] Build failed; check build logs for details
Project CosmoApiSystem deployed to App Engine Flex.

"Unable to connect to any of the specified MySQL hosts


feat(mission_planner): add modified goal reroute planner

Description
Add new rerouting function to enable the planner to plan a new route based on a modified goal.

Related links

Tests performed
PSim
Screencast from 2023年06月06日 12時44分56秒.webm
Notes for reviewers

Interface changes
No Interface changes

Effects on system behavior
No effects

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@purewater0901 Please do not throw component_interface_utils::ServiceException in a process that doesn't start at the callback of component_interface_utils::Service.


Support xliff2 & set as default.

Added support for xliff2
Set xliff2 as default

CORE already supports xliff2. The CLI should too, and it should default to using it. https://github.com/angular/angular/issues/11735

Think it's nice to move forward with xliff2 by default, but it's not the same default as provided by Angular: https://angular.io/guide/i18n#create-a-translation-source-file-with-the-ng-xi18n-tool

By default, the tool generates a translation file named messages.xlf in the XML Localization Interchange File Format (XLIFF, version 1.2).

@intellix would it get committed if I made the appropriate changes  in @angular/angular first?

@EvanCarroll thanks a lot for the PR. Unfortunately, as we follow semver, we won't be able to change the default value until we do a major release (2.0 is the next one).
Supporting the xliff2 format is definitely something we want, so if you remove changing the default from this PR I'll approve it.
Of course, if you change the default in Angular it would be more of a motivation for us. Let us know. You can also file an issue so we can remember to do it when we start a 2.0 branch.
Thanks!

@hansl done, I can patch @Angular/angular and docs to use xliff2, but they have translations in there written in xliff1 and I can't find a tool that works with the ng output in xliff2.


global: simplify development

Following is a quick brainstorming on commands that potentially could be useful for making it easier to develop with RDM:
Boostrap and install RDM locally:
invenio-cli init rdm
cd ~/src/my-site
invenio-cli install --pre

Install a Python and JS module for development:
invenio-cli module-install -e ~/src/invenio-records-resources
invenio-cli js-install -e ~/src/react-invenio-forms

Run:
invenio-cli services
invenio-cli run

Watch JS changes if needed:
invenio-cli watch ~/src/react-invenio-forms

Alternative assets commands:
invenio-cli assets clean
invenio-cli assets buildall

I was thinking about the extensions (https://inveniordm.docs.cern.ch/extensions/) and how the install commands actually fall in that category of functionality.
So having
invenio-cli ext init  To create your own.
invenio-cli ext js-install ...  To install
invenio-cli ext module-install ...
could be an idea..

What should invenio-cli ext module-install <PATH> do?
pipenv run pip install -e <PATH>

Should it also run update?
Do we need to write something to the .invenio file?

In #173 I've added the commands:
invenio assets update --force --development
invenio assets watch

The --development or --production will respectively set FLASK_ENV=development/production to ensure we either copy or symlinkfiles.
The --force replaces --instal-js/--no-install-js. Force will clean the folder and install node modules. If not, only a invenio webpack create/build is run (this is needed to wipe assets if e.g. it was created with production and you now want development mode).
For the React module development I'm thinking instead of invenio-cli ext js-install ~/src/react-invenio-deposit, we could have something like:
invenio-cli assets watch-module ~/src/react-invenio-deposit

This would:

Install and build module: cd ~/src/react-invenio-deposit; npm install; npm run build
Link module cd ~/src/react-invenio-deposit; npm run link-dist
Link project cd <path-to-your-virtualenv>/var/instance/assets/node_modules; npm link react-invenio-deposit
Start watching changes: cd ~/src/react-invenio-deposit; npm run watch

You will still need afterwards to run:
invenio-cli assets watch

A full dev flow would then look like:
invenio-cli init rdm -c master
invenio-cli install --pre
invenio-cli ext module-install ~/src/invenio-rdm-records ~/src/invenio-app-rdm
invenio-cli services
invenio-cli demo --local
invenio-cli asset update -f -d
invenio-cli assets watch-module ~/src/react-invenio-deposit
invenio-cli assets watch
invenio-cli run

Now implemented in #173

@lnielsen for this command invenio-cli assets watch-module ~/src/react-invenio-deposit I would add an option to skip the relinking part in case you just want to watch the module i.e npm run watch equivalent, assuming you had linked it and now you just want to watch it again :)


Social Icon Buttons - double  on 3rd line in HTML CODE

BUILDING BLOCKS SOCIAL ICONS
Social Icon Buttons - double  in 3rd example in HTML CODE just before the
http://foundation.zurb.com/building-blocks/blocks/social-icon-button.html
`

`

I referenced your issue in the corresponding PR: zurb/building-blocks/pull/179/files#r118654000
Thanks for reporting!

Good catch! Are you able to submit a fix through PR?


Update readme.md

added licence and contribution info
Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
Description
[I have updated the readme.md file .I have added few information about licence and contribution]
Type of PR

[ ] Bug fix
[ ] Feature enhancement
[x] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have followed the code style guidelines of this project.
[x] I have checked for any existing open issues that my pull request may address.
[x] I have ensured that my changes do not break any existing functionality.
[x] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[x] I have read the resources for guidance listed below.
[x] I have followed security best practices in my code changes.

Additional Context
[Updating the readme.md file will be helpful for contributors .]
Resources for Guidance
Please read the following resources before submitting your contribution:

[x] Code Harbor Hub Community Features
[x] Docusaurus Documentation
[x] React.js Documentation
[x] Markdown Guide
[x] MDX Documentation
[x] Mermaid Documentation

Resources for DSA Features on Our Site:

[x] Tabs: Switch Languages
[x] Line Numbering
[x] Math Equations

Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the level1 label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to level2. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Level1:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Level2:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Level3:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

#4029


add SSM resize EBS volume document

Issue #, if available:
Description of changes:
Add SSM document module to resize EBS volume attached to an EC2 instance.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kddejong please review updated cicd updated to resolve merging issue.

@ericzbeard @kddejong Please review the most recent revisions since I need to submit other modules relevant to IOT and waiting for this one to go first.


Hour Recording Cron doesn’t record if on visitor roster

Update the code for the cron job to include the controllers on the visiting roster.

Rosters combined. Closed.


Make sr25519-crust external project

Make sr25519-crust external project instead of submodule.
This prevents tests building of sr25519 and speeds up compilation

bad idea


java.lang.IllegalStateException: containerSize or previewSize is not set yet

'com.journeyapps:zxing-android-embedded:3.6.0'
I have such kind of error in my crashlytics report and It is only in this phone: Xiaomi Mi A2, Android 9
Fatal Exception: java.lang.IllegalStateException: containerSize or previewSize is not set yet
at com.journeyapps.barcodescanner.CameraPreview.calculateFrames(CameraPreview.java:369)
at com.journeyapps.barcodescanner.CameraPreview.previewSized(CameraPreview.java:469)
at com.journeyapps.barcodescanner.CameraPreview.access$300(CameraPreview.java:60)
at com.journeyapps.barcodescanner.CameraPreview$3.handleMessage(CameraPreview.java:200)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6692)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
How to solve this???

Try upgrading to the latest version (currently 4.1.0) - some crashes have been fixed.

Rare crashes are generally not worth fixing, unless the cause is obvious. If you see a lot of reports, or have a way to reproduce the issue, we can investigate further.

I found following scenario to reproduce this issue.
Set a breakpoint in com.journeyapps.barcodescanner.camera.CameraInstance on line 215 readyHandler.obtainMessage(R.id.zxing_prewiew_size_ready, getPreviewSize()).sendToTarget(); When the breakpoint is reached, then close/recreate the fragment/activity which calls pause and clears necessary fields. Then proceed from breakpoint, issue will show up.
I got no live reports yet, only my tests where running into this issue, because of fast open and close actions. Looks like this is no real issue, because the camera instance is not relevant anymore. But at this moment it would crash the app and I didn't found a way to catch this exception.
I think an option could be to have a paused flag somewhere to avoid this crash situation.

@rkistner any updates on this issue?
I have the same crashes but for the new version 4.3.0

Fatal Exception: java.lang.IllegalStateException: containerSize or previewSize is not set yet
at com.journeyapps.barcodescanner.CameraPreview.calculateFrames(CameraPreview.java:366)
at com.journeyapps.barcodescanner.CameraPreview.previewSized(CameraPreview.java:472)
at com.journeyapps.barcodescanner.CameraPreview.access$300(CameraPreview.java:60)
at com.journeyapps.barcodescanner.CameraPreview$3.handleMessage(CameraPreview.java:202)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6119)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)


Add sorting for TailwindCSS classes

See https://tailwindcss.com/blog/automatic-class-sorting-with-prettier#how-classes-are-sorted and https://github.com/tailwindlabs/prettier-plugin-tailwindcss/blob/main/src/sorting.js.

would be wonderful

Fixed by https://github.com/nebulab/erb-formatter/pull/39


CentOs build error

Bug Template
Title: CenOS build image fails
Description:

"Your toolchain has set _GLIBCXX_USE_CXX11_ABI to a value that uses a std::string " "implementation that is not thread-safe. This may cause rare and difficult-to-debug errors " "if std::string is passed between threads in any way. If you accept this risk, you may define " "ENVOY_IGNORE_GLIBCXX_USE_CXX11_ABI_ERROR=1 in your build."
#error "Your toolchain has set _GLIBCXX_USE_CXX11_ABI to a value that uses a std::string "

[optional Relevant Links:]

This is the command I have run

IMAGE_NAME=envoyproxy/envoy-build-centos ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.release.server_only'
Question: Can you please let us know how do we include this ENVOY_IGNORE_GLIBCXX_USE_CXX11_ABI_ERROR=1 in the Basel build options
I have modified BAZEL_OPTIONS but there is no effect. Thanks for your help !

@vpiduri you might want to set this in SOURCE_DIR/.bazelrc as a --copt="-DENVOY_IGNORE_GLIBCXX_USE_CXX11_ABI_ERROR=1 " build option, see https://docs.bazel.build/versions/master/user-manual.html#bazelrc.


enable doctests

We should run doctests within pytest to ensure the examples given in the documentation are always functional. This should be very easy to enable, since it is only a flag passed to pytest. Eventually some doctests are already out of sync.

we currently do not have many code examples in the docstrings but would be nice to couple with doctest if we add more


Newer CMake is going to drop <2.8.12

So update to <IP_ADDRESS> (in Ubuntu 14.04)
CentOS 7 has a way to install CMake3.
This avoids the warning in newer CMakes:
flatcc/CMakeLists.txt:5 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.

Relying on ancient versions of CMake such as 2.8 has more serious implications. For example, CMake policy CMP0077 was introduced in 3.13 so that higher-level CMakeLists.txt can adjust option()s programmatically using set(). Otherwise, the settings from the following example would be ignored by flatcc:
cmake_minimum_required(VERSION 3.13.5)
project(test_project)
set(FLATCC_TEST OFF) # This will be ignored since flatcc currently uses cmake_minimum_required(VERSION 2.8)
add_subdirectory(flatcc)

Typically, CMake would then return the following warning message:
Policy CMP0077 is not set: option() honors normal variables.  Run "cmake
  --help-policy CMP0077" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

If flatcc does not bump cmake_minimum_required to 3.13, the only solution is to move all configurations as command line options e.g.:
$ cmake .. -D FLATCC_TEST=OFF

Which shifts responsibility to end users (who might be or not maintainers of the higher-level CMakeLists.txt), potentially causing confusion and issues.

Historically, certain important Ubuntu versions did not trivially work with more recent CMake.
I'm all for moving forward now. Especially since flatcc has just had a new release.
As I mentioned, there is a rather large pending PR on upgrading CMake already.
However, I cannot invest a lot of time in this for the time being.
At the same time, the build system for flatcc needs to be migrated to GH Actions. Especially for *nix builds, but for consistency also Windows builds.
Anyone willing to take on this, speak up.

As I mentioned, there is a rather large pending PR on upgrading CMake already.

I had a look at https://github.com/dvidelabs/flatcc/pull/171, but IMHO this PR introduces too many several architectural changes that affect many aspects of this project i.e., not only build-related stuff, but also integration with Github Actions, cross-compilation and introduction of new APIs such as flatcc_generate_sources, among others.
I would rather suggest to split the effort in #171 into smaller, independent PRs that make it easier for others to review. Therefore, as a first step, I plan to create a PR that identifies obsolete and deprecated CMake constructs within the project and fixes them with modern alternatives.

I tend to agree, but I'd rather have GH Actions working first because the Travis build stopped working after they made a change. So there is no way to verify complex changes across several operating systems and compiler versions as it is.
Thanks for having a look.

@midokura-xavi92 don't let this stop you if you have something of interest. This is just the order of events I think makes the most sense.

@mikkelfj thank you very much for your support. I will then provide a few suggestions whenever possible.

This was merged into PR #250 so closing this one.
@midokura-xavi92 if you still have some input on CMake changes, the new GH Actions makes it easier to test changes.

Sorry for not bringing attention to this topic earlier - priorities were shifted to other projects, so no time could be dedicated to this suggestion, unfortunately, and I do not know when I could take back on it.


Link mouse cursor property

As nodes, links could have a configurable mouseCursor property that defines on the fly what is the cursor like when the mouse is hovering on some link.
The new config API should have a new mouseCursor property as specified below:
node: {
    color: '#d3d3d3',
    // ...
    mouseCursor: 'pointer',
},
link: {
    color: '#d3d3d3',
    // ...
    mouseCursor: 'pointer' --> new configurable property!
}

Please remember that:

configs are documented on top of the graph.config.js file
Adding a new config to a link means that you need then to provide it in the Link component Link.jsx
Adding a new config means that links builder in graph.helper.js needs to pass along that new property

Happy Hacktoberfest!

I'll work on this.


Clean up prompt helper

I introduced breaking API changes (mostly param naming), as it was pretty difficult/confusing to do so without proper renaming etc.
Notable changes

Change PromptHelper to be configured via chunk_overlap_ratio and chunk_size_limit
Change ServiceContext to only pass chunk_size to node parser, and NOT configure chunk_size_limit for the PromptHelper

It's not clear to me why users may want to set a chunk_size_limit on PromptHelper. AFAIK the whole point of PromptHelper is to automatically set chunk size to maximally pack context window given desired number of chunks.

Set DEFAULT_CHUNK_OVERLAP to be much smaller at 20

This makes it less likely that users encounter the issue of setting too small of a chunk size for node parser. And it's no clear to me that we need high chunk overlap, especially if we have good text splitters.

Other changes

Broad refactor in PromptHelper to improve code quality

Todos

[ ] Fix tests and unit-tests

wow this is an involved change, thanks for taking this on!
I think I need to pull this branch and run a few tests, there's a few key things I wanted to test for (negative chunk size errors, UX for setting up things, etc.)

Absolutely, would appreciate help in testing this in various configurations.

Did some testing, seems to work super well. I know the term max_input_size confused a lot of people, hopefully context_window makes more sense.
Using a chunk overlap ratio also seemed to help with the old negative chunk size errors. Even when using problematic languages like mandarin, as well as setting absurd settings (num_output=3500, context_size=4096), it seemed to run smoothly.
One nit:

I didn't get any deprecation warnings when doing this: prompt_helper = PromptHelper(max_input_size=4096, num_output=2000, max_chunk_overlap=200, chunk_size_limit=1024)
Do I need to set the logging level or something for this?

Did some testing, seems to work super well. I know the term max_input_size confused a lot of people, hopefully context_window makes more sense.
Using a chunk overlap ratio also seemed to help with the old negative chunk size errors. Even when using problematic languages like mandarin, as well as setting absurd settings (num_output=3500, context_size=4096), it seemed to run smoothly.
One nit:

I didn't get any deprecation warnings when doing this: prompt_helper = PromptHelper(max_input_size=4096, num_output=2000, max_chunk_overlap=200, chunk_size_limit=1024)
Do I need to set the logging level or something for this?

RE deprecation warning, did you do it in a notebook? I noticed that as well, and it seems like you need to explicitly configure something for it to show up. Maybe we should just print instead?

@Disiok

RE deprecation warning, did you do it in a notebook? I noticed that as well, and it seems like you need to explicitly configure something for it to show up. Maybe we should just print instead?

I was running from a script in the terminal (and also in repl), also nothing 🤔 A print (or even a logger.warning) works for me though too

@Disiok

RE deprecation warning, did you do it in a notebook? I noticed that as well, and it seems like you need to explicitly configure something for it to show up. Maybe we should just print instead?

I was running from a script in the terminal (and also in repl), also nothing 🤔 A print (or even a logger.warning) works for me though too

Reverted to using logger.warning 😛

heads up @Disiok docs need to be changed:

at least one example here: https://gpt-index.readthedocs.io/en/latest/guides/primer/usage_pattern.html#customizing-llm-s

Yep, there's way more than that to be changed. But should be updated now.


Make cargo test depend only on deps build

Codecov Report

Merging #478 (dd05937) into master (4ad1a46) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #478   +/-   ##
=======================================
  Coverage   73.79%   73.79%
=======================================
  Files          83       83
  Lines       10637    10637
=======================================
  Hits         7850     7850
  Misses       2787     2787

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


Handle shifting inside a join condition in qscript

Example query:
select zips.city, smallZips.loc from zips join smallZips on zips.loc[*]{*} = smallZips[*]

Currently qscript detects the shift in the join condition as a "non-mapping join condition" and fails to create a join.
Fixing this should enable joins/nonJsJoinCondition.test and joins/symmetricNonJsJoinCondition.test. Additionally a test with multiple flattens on a single side (as in the example above) should be added.

Additionally, to enable those integration tests, we need to match on Constant(Arr(List(NA))) and Constant(Obj(Map( -> NA))) in the LP optimizer where we move Typecheck outside of join conditions. With new mongo, it should be sufficient to just match on NA.

The solution will be to extract the LeftShift out of the join condition into the join branch FreeQS. There the LeftShift can provide access to both the shifted and unshifted values.

A duplicate (or at least an extension of) #2133. Fixing #2133 will enable this to be fixed.

Also should note that this query will not execute on any qscript-based backend until this issue is fixed.


Remove redundant logging

Signed-off-by: Nishant Shreshth<EMAIL_ADDRESS>

Already fixed in #99.


Revert "Merge pull request #6440 from kmaehashi/fix-scipy-intersphinx"

SciPy's reverence looks back. https://docs.scipy.org/doc/scipy/reference

Still fails as we can see https://docs.scipy.org/doc/scipy-1.8.0/html-scipyorg/objects.inv, but https://docs.scipy.org/doc/scipy/objects.inv just redirects to https://docs.scipy.org/doc/scipy-1.8.0/html-scipyorg/reference/ .

See https://github.com/scipy/scipy/issues/15545.

Let me withdraw this.


DEBUG message Invalid TraceId and Invalid span context

I see this debug message in the log. I get it running locally but also in AWS
{"timestamp":"2021-12-16T04:36:33,978","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}

{"timestamp":"2021-12-16T04:36:33,919","level":"DEBUG","thread":"nioEventLoopGroup-3-1","class":"ApiHandler","message":"Received Wire PING","throwable":""}
{"timestamp":"2021-12-16T04:36:33,978","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"JsonRpcHttpService","message":"Opened connection from <IP_ADDRESS>:48576. Total of active connections
: 1/80","throwable":""}
{"timestamp":"2021-12-16T04:36:33,978","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning IN
VALID span context.","throwable":""}
{"timestamp":"2021-12-16T04:36:33,978","level":"DEBUG","thread":"vert.x-worker-thread-17","class":"JsonRpcHttpService","message":"JSON-RPC request -> eth_syncing","throwable":""}
{"timestamp":"2021-12-16T04:36:33,979","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"JsonRpcHttpService","message":"Connection closed from <IP_ADDRESS>:48576. Total of active connections
: 0/80","throwable":""}
{"timestamp":"2021-12-16T04:36:34,061","level":"DEBUG","thread":"nioEventLoopGroup-3-2","class":"AbstractHandshakeHandler","message":"Handshake error:","throwable":" java.io.IOException: Connection r
eset by peer\n\tat java.base/sun.nio.ch.FileDispatcherImpl.read0(Native Method)\n\tat java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)\n\tat java.base/sun.nio.ch.IOUtil.readIntoNa
tiveBuffer(IOUtil.java:276)\n\tat java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233)\n\tat java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223)\n\tat java.base/sun.nio.ch.SocketChannelImpl.read(SocketCha
nnelImpl.java:356)\n\tat io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)\n\tat io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)\n\tat io.netty.channel.socket.nio.N
ioSocketChannel.doReadBytes(NioSocketChannel.java:350)\n\tat io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)\n\tat io.netty.channel.nio.NioEventLoop.pr
ocessSelectedKey(NioEventLoop.java:719)\n\tat io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)\n\tat io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEven
tLoop.java:581)\n\tat io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)\n\tat io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)\n\tat io.netty.ut
il.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base/java.lang.Thread.run(Thread.
java:829)\n"}
{"timestamp":"2021-12-16T04:36:34,270","level":"DEBUG","thread":"nioEventLoopGroup-3-8","class":"ApiHandler","message":"Received Wire PING","throwable":""}
{"timestamp":"2021-12-16T04:36:34,334","level":"DEBUG","thread":"vert.x-worker-thread-10","class":"PingPacketData","message":"read PING enr as long scalar","throwable":""}
{"timestamp":"2021-12-16T04:36:34,347","level":"DEBUG","thread":"nioEventLoopGroup-3-2","class":"RlpxAgent","message":"Too many peers. Disconnect incoming connection: NettyPeerConnection{nodeId=0xf61
85b64224d9d971200b234dd9ccc15089dd688c01dbd02ed977d5c492f44ca11c3d793c18b9251b83508efd19f5e0b0267d8b3c98afa17713adbd8f0b74ae5, clientId=Geth/v4.3.0-stable-86215cd4/linux-amd64/go1.17.2, caps=eth/66}"
,"throwable":""}
{"timestamp":"2021-12-16T04:36:34,347","level":"DEBUG","thread":"nioEventLoopGroup-3-2","class":"EthProtocolManager","message":"Disconnect - Outbound - 0x04 TOO_MANY_PEERS - PeerInfo{version=5, clien
tId='Geth/v4.3.0-stable-86215cd4/linux-amd64/go1.17.2', capabilities=[eth/66, snap/1], port=0, nodeId=0xf6185b64224d9d971200b234dd9ccc15089dd688c01dbd02ed977d5c492f44ca11c3d793c18b9251b83508efd19f5e0
b0267d8b3c98afa17713adbd8f0b74ae5} - 32 peers left","throwable":""}
{"timestamp":"2021-12-16T04:36:34,476","level":"DEBUG","thread":"vert.x-worker-thread-3","class":"PingPacketData","message":"read PING enr as long scalar","throwable":""}
{"timestamp":"2021-12-16T04:36:34,477","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"JsonRpcHttpService","message":"Opened connection from <IP_ADDRESS>:48578. Total of active connections
: 1/80","throwable":""}
{"timestamp":"2021-12-16T04:36:34,477","level":"DEBUG","thread":"vert.x-eventloop-thread-0","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning IN
VALID span context.","throwable":""}
{"timestamp":"2021-12-16T04:36:34,478","level":"DEBUG","thread":"vert.x-worker-thread-19","class":"JsonRpcHttpService","message":"JSON-RPC request -> eth_syncing","throwable":""}

Versions (Add all that apply)

Software version: [besu --version] 21.10.3 but I have seen it before
Java version: [java -version]
openjdk 11.0.11 2021-04-20 LTS
OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 11.0.11+9-LTS)
OpenJDK 64-Bit Server VM Corretto-<IP_ADDRESS>.1 (build 11.0.11+9-LTS, mixed mode)
OS Name & Version: [cat /etc/*release]
[ec2-user@ip-10-0-2-150 besu]$ cat /etc/*release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"
Amazon Linux release 2 (Karoo)
Kernel Version: [uname -a]
Linux ip-10-0-2-150.us-east-2.compute.internal 4.14.173-137.229.amzn2.x86_64 #1 SMP Wed Apr 1 18:06:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Additional Information

This does not affect operation of Besu, it's only noticeable in the DEBUG logs

it's to do with open telemetry. We're upgrading so maybe it will even be fixed. https://programtalk.com/vs3/?source=java/open-telemetry/opentelemetry-java/extensions/trace-propagators/src/main/java/io/opentelemetry/extension/trace/propagation/B3PropagatorExtractorMultipleHeaders.java

I no longer see these DEBUG messages.
besu/v22.1.3-dev-7e0d06ac/osx-x86_64/openjdk-java-11

I see:
Sep 14 15:44:35 SRV-02 run_node.sh[70540]: 2022-09-14 15:44:35.058+02:00 | vert.x-eventloop-thread-1 | DEBUG | JsonRpcHttpService | Opened connection from 0:0:0:0:0:0:0:1%0
:49934. Total of active connections: 1/80
Sep 14 15:44:35 SRV-02 run_node.sh[70540]: 2022-09-14 15:44:35.058+02:00 | vert.x-eventloop-thread-1 | DEBUG | B3PropagatorExtractorMultipleHeaders | Invalid TraceId in B3
header: null'. Returning INVALID span context.

My system:
# uname -a
Linux  5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
# besu --version
besu/v22.4.4/linux-x86_64/openjdk-java-11
# java -version
openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8-post-Debian-1deb11u1)
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Debian-1deb11u1, mixed mode, sharing)

Seeing this log too when I try to call
curl -X 'GET' \
  'http://<IP_ADDRESS>:8545/eth/v1/config/spec' \
  -H 'accept: application/json'

2023-12-29 16:05:20.602+08:00 | vert.x-eventloop-thread-1 | DEBUG | JsonRpcHttpService | Opened connection from <IP_ADDRESS>:51734. Total of active connections: 1/80
2023-12-29 16:05:20.602+08:00 | vert.x-eventloop-thread-1 | DEBUG | B3PropagatorExtractorMultipleHeaders | Invalid TraceId in B3 header: null'. Returning INVALID span context.
2023-12-29 16:05:20.604+08:00 | vert.x-eventloop-thread-1 | DEBUG | JsonRpcHttpService | Connection closed from <IP_ADDRESS>:51734. Total of active connections: 0/80


Add ability for interface binding

Can now use --sourceip IP-ADDRESS arg with the bin file
Or use the options object with the key sourceIp
It works with IP addresses only.
Closes #61.

Superseded by #95 (rebase)

hey @DjLegolas I just tested this and the flag seems to be ignored. Any ideas?

Hi @rodcul, this option will let you choose a specific network interface based on it's IP address.
If there is no interface with the given IP, it will not work.
This option will not spoof the source IP.


After successful de-encryption, the encrypted file is not deleted in Windows 11

After successful de-encryption of the encrypted zip it is not deleted when the zip file has been successfully created. (v0.5.2 on Windows 11).

That's intended behavior to provide consistency among platforms. Because of a bug in Java, you'll need to close the app to delete the file.

Ok. Good to know
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Zachary Wander @.>
Sent: Saturday, September 4, 2021 6:59:02 AM
To: zacharee/SamloaderKotlin @.>
Cc: Joseph Tash @.>; Author @.>
Subject: Re: [zacharee/SamloaderKotlin] After successful de-encryption, the encrypted file is not deleted in Windows 11 (#36)
That's intended behavior to provide consistency among platforms. Because of a bug in Java, you'll need to close the app to delete the file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/zacharee/SamloaderKotlin/issues/36#issuecomment-912979000, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABWQBEQTX4ZXTDGRAPJJXHTUAIQ2NANCNFSM5DNKEHGQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Damage but noted


Installation Error

I tried installing this bot into our UK South subscription last week and it failed with a series of 4 related errors:
"Update Web App Source Control Configuration","Failed","Administrative","Error"... ,"Microsoft.Web/sites/sourcecontrols",..."Update Web App Source Control
Before the script reports a failed deployment. This looks to be something to do with configuring the bot to talk to github?
I'm suspecting this may be a permissions issue - We have various resources in our tenancy spread across several subscriptions, and I was elevated with PIM in the subscription the destinations resource group was in, but I wouldn't have had any write permisison into, say, azure AD or any of our keyvaults at that time.
Any suggestions as to what I can do to investigate this error more thoroughly would be welcome.

This appears to have been a transitory problem - a second attempt to deploy the bot took 1 hr to complete. A  third attempt worked after 14 mins. I'll close this issue


Add Discord link

I have created a Discord server for our community: http://discord.devsdope.com/
Add it to README.md at the bottom.

@khattakdev can this issue be assigned to me pls


requirements: Adding pycairo

The default rendering engine in hwgraph is cairo, so let's ensure the dependency is explicit to avoid any issue at rendering time.

I just realized we forgot to update the genarated requirements file (make regen_hashes)


Wait for detach and reattach to complete with certain flags

When detach --wait is used, wait 11 seconds for the detach to take place.
When attach --inspect is used, wait 10 seconds (plus 2) if we are doing a reattach.

approved by @iapaddler


Update Lauhdutin.lua

Many Have problems With the the skins saying that it cant find games  the bug found Cyb3rzombie is an error in the lua script

I appreciate the pull request, but I disagree with the implementation of the fix to the issue at hand:

The global variables (S_VDF_KEY_*) are used so that just the declarations need to be changed when the same values are used in multiple places.
The change is not backwards compatible with older VDF files where "apps" is used instead of "Apps".

A new branch has been created as an effort to fix the issue brought up. I would appreciate help with testing the solution(s) implemented in that branch. The current solution on that branch converts all keys to lower case and should be able to handle any variations (apps, Apps, ApPS, etc.).


Fix a leak in the duplicator

Motivation:
We have the customized circular queue in the DefaultStreamMessageDuplicator to store data.
Because it's a circular queue the head index can be higher than the tail index.
But we didn't consider that when removing all data in the queue.
Special thanks to @haithamgabr who reported the leak.
Modifications:

Fix remove method working when the head index is higher than the tail index.
Change to use ByteBuf in the test so that we can know when a leak happens.

Result:

Less leak.

Thanks A LOT @minwoox for working on this.
Here is the issue if you'd like to link it
https://github.com/line/armeria/issues/3476


Fix unsafe wallet function implementation

Came across something that might cause problems soon.

Looks fine to me. Nami "should" always return an array containing a single collateral UTxO when getCollateral is called, but it's probably a better idea to check this

It doesn't. Yesterday I tried to run pk2pk example and it was returning empty array.

@adamczykm Did you set collateral in Nami?


Always fail the test task if unrecoverable errors occur during test result processing

We fixed an issue with serialization/deserialization of test failures in #24056, but there could be other unrecoverable failures that occur during test result processing that are not captured.  This makes it so that we always fail the test task when such errors occur.

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge


Change the properety "status" of a time registration to an enum in the API (instead of a string)

See https://swagger.io/docs/specification/data-models/enums/

Note: Can easily be done - doesn't affect the Kotlin plugin, backend still has to validate a String.
Valid values:
pending, valid, and invalid


Update README.md

The skip button dataSource delegate was changed from 'inParentView' to 'inParent' now.

Thanks!


curl: option --proto: is unknown on CentOS 6

Problem
curl error when using: curl https://sh.rustup.rs -sSf | sh -s -- -y
docker run -it centos:6 /bin/bash
[root@081cc8b7180c /]# curl
curl: try 'curl --help' or 'curl --manual' for more information
[root@081cc8b7180c /]# curl https://sh.rustup.rs -sSf | sh -s -- -y
info: downloading installer
curl: option --proto: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
rustup: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init /tmp/tmp.fBaoqs014w/rustup-init

Expected (this worked until 4 days ago):
curl https://sh.rustup.rs -sSf | sh -s -- -y
info: downloading installer
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2019-04-11, rust version 1.34.0 (91856ed52 2019-04-10)
info: downloading component 'rustc'
info: downloading component 'rust-std'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: installing component 'rustc'
info: installing component 'rust-std'
info: installing component 'cargo'
info: installing component 'rust-docs'
info: default toolchain set to 'stable'

  stable installed - rustc 1.34.0 (91856ed52 2019-04-10)

Rust is installed now. Great!

To get started you need Cargo's bin directory ($HOME/.cargo/bin) in your PATH
environment variable. Next time you log in this will be done automatically.

To configure your current shell run source $HOME/.cargo/env

Steps

docker run -it centos:6 /bin/bash
curl https://sh.rustup.rs -sSf | sh -s -- -y

Possible Solution(s)
N/A
Notes
Output of rustup --version: N/A
Output of rustup show: N/A

This is a side-effect of our change to rustup-init.sh to force newer TLS versions always.
The --proto option is nine years old and was part of 7.21.0 released June 16th 2010.
I suggest that you come up with a way to update the version of curl available in your docker because to undo the change we made would be to weaken a commitment to stronger security around the installation of rustup.
If you really can't update curl, then perhaps we can come up with a way to force the use of wget on centos (assuming centos's wget supports --https-only and --secure-protocol=TLSv1_2)

Simpler solution is to download and run this file if you're on x86-64-linux machine:
https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init

Ok that is unfortunate. Does this mean CentOS 6 is not a supported target for rustup? At https://github.com/OISF/suricata we just made our Rust support mandatory and one of the reasons was that for CentOS 6 it could be installed (& then kept up to date) using very simple instructions.

No, Rustup should run well on CentOS 5+. The problem is in the rustup-init.sh.
Can you point out which part in your project use rustup.sh so we can help?

I don't use it other than as part of my QA/CI infra, but we want to give users a simple instruction of how to upgrade our program from 4 (optional rust) to 5 (mandatory rust). Since quite a few of our users are still on CentOS 6, having a simple instruction like rustup normally provides would work best.
We could tell them to pull down the rustup-init for their arch manually (I confirmed it works), or have them install a more recent curl. But I was under the impression rustup was actually trying to solve these issues for us :)

We are trying to make it easy and safe to get Rust.  In order to reduce the chance of TLS downgrade attacks, we introduced this flag to our use of curl (and similarly for wget) and we ensured our configuration of TLS inside rustup was similarly secured.  I certainly don't want to make it impossible for your users, so we need to come up with a halfway house.
@lzutao suggested on our discord channel that we have some kind of flag to allow you to say to rustup-init.sh that you accept the risks of not requiring TLS 1.2.  Would you prefer that to be a commandline argument, or an environment variable?
As a work-around, if you're able to install a curl proxy into the user's path, you could swallow the unrecognised arguments before passing it on to curl-proper.

I could see 2 paths (w/o reverting the new behaviour):

some kind of version and/or functionality check on curl/wget. What to do in case of too old versions is the next problem then of course. You could warn and continue, or you could fail and explain.
add some kind of 'legacy' commandline option that allows for these kinds of older versions. I guess this could even be combined with (1) to only leave out the strict options if the tools really don't support them.

I'm wondering though, how much protection does this option really give? I mean it seems everything that is done is under the Rust projects control, so I guess I'm not really seeing the attack vector. But maybe I've missed an analysis on the issue somewhere.

I think that a check/downgrade-if-option-set is the only approach which is going to maintain the benefit while not causing users of older operating systems too much pain.  Regarding the protections - downgrade attacks (which I'd tend to assume would be in the infra between the users's computer and rust-lang's servers) open the way to potentially introducing bad code into the compiler which is installed.  Right now this is (to my mind) fairly unlikely, but it is a vector we'd prefer to protect ourselves against, no matter how unlikely we imagine it might be.

This is hitting us with our CI in https://github.com/pantsbuild/pants too, as we use Centos6 to build our native wheels for max compatibility.

I think that a check/downgrade-if-option-set is the only approach which is going to maintain the benefit while not causing users of older operating systems too much pain.

I think this is a good solution. Perhaps log a warning that you have to make this downgrade.
Thanks for your help here!

Looks like macOS 10.12 is broken with image xcode9.2. :sob:

Is this travis-ci error related as well?
info: downloading installer
curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect
rustup: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/bb/n7t3rs157850byt_jfdcq9k80000gn/T/tmp.yZX1SGRn/rustup-init
/Users/travis/.travis/functions: line 108: rustc: command not found

https://travis-ci.org/OISF/suricata/jobs/523642627
I believe its using xcode 8.3


Add standard deviation group data in group mean table

We add standard deviation in price and price per sqft to the group_mean table so that we can back out the how a sale was flagged in terms of price.
If this looks good - I can wipe all of the tables, re-run the initial flagging script, and update the athena schema, if that seems like the best move.
Closes #78


Would it be worth taking a crack at this again now that the Banjo N64 Decomp is getting back on track?

Technically, I never stopped. I've been working on other banjo-related things and been annotating functions and data in Ghidra all that time. The fact that the N64 decomp gained a few tenth of % isn't really relevant since there are already so much code to try to match.