Whimsy rework

Like I said... Huge changes... Sorry about that.
Luckily, gem5_verify_config doesn't change at all to test writers. (Other than the fact that it works.) Feel free to tell me if the changes are cruft (Or if any portion of them are.) Besides everything actually working, in my experience this implementation has been a lot easier to debug.
I've really only done preliminary integration testing. All the tests are passing so that's pretty neat...
A good quick command I've used to test execution is ./main.py run gem5/ -vvv --include-tags opt
If you'd like me to go through any of my thought process with these changes or a provide an overview via videochat let me know. My schedule this coming weekend will be full, but the middle of the week I should be available.
Whimsy 1.0 known issues this rework fixes:

JUnit XML output is working now
SCons Build correctly creates minimal set of targets
Verifiers are correctly instantiated for gem5_verify_config suites
Fixture setup failures result in library/suite/test error, and display message.

TODOs
So there are a couple things I already know I still have to get working:

Rerun command
Your newbie friendly isa, variant, and length tags.
Multi-threaded test suite execution
JUnit XML error, skip results don't supply the fixture setup exception that caused the result.
I'll need to look at merging in my unit test patch, I don't think that will be a big change, just a refactor.
Adding license headers to the source.

If I have time Tuesday night I'll also be sure to start re-writing documentation.
Finally, if I get all the above sorted out I'd like to take a stab at refactoring that config. I'd like to get all gem5 specific configuration out of the test library if possible. It would make it much easier for me to continue to work on library improvements and import/export patches in the future.

Restored:

rerun
isa, variant, and length tags
multithreaded/parallel suite execution
license
some documentation (still needs more)

Only bug I've found so far is that single fixture instances attached to multiple tests/suites will be built multiple times. This could cause issues in parallel test execution, as a solution I intend to require fixtures implement a copy method which will be executed when they receive the test schedule. This way setup/teardown will be performed on a separate instance each time.
I should have a fix for this in tonight.

I haven't had a chance to go through this yet, but I have a quick question...
Should I hold off on pushing what we have now on gerrit for these changes?

I hope to be able to go through this this afternoon.

Yeah I would hold off. I think these changes are about ready to merge into
our Gerrit patchset.
As it is now, the fixture logic and verifier fixes make the library much
more reliable to use and program against.
On Thu, Jul 12, 2018, 13:22 Jason Lowe-Power<EMAIL_ADDRESS>wrote:

I hope to be able to go through this this afternoon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jlpresearch/gem5/pull/5#issuecomment-404605025, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9rOMB7jUS7B6oXSDqQg9MflGJv7-xAks5uF5PXgaJpZM4VG932
.

Sounds good. I'll try to take a deeper look this afternoon.
FYI, a quick glance shows some style issues (e.g., lines with more than 79
chars and newlines missing at the end of files).
Cheers,
Jason
On Thu, Jul 12, 2018 at 11:29 AM Sean Wilson<EMAIL_ADDRESS>wrote:

Yeah I would hold off. I think these changes are about ready to merge into
our Gerrit patchset.
As it is now, the fixture logic and verifier fixes make the library much
more reliable to use and program against.
On Thu, Jul 12, 2018, 13:22 Jason Lowe-Power<EMAIL_ADDRESS>wrote:

I hope to be able to go through this this afternoon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jlpresearch/gem5/pull/5#issuecomment-404605025, or
mute
the thread
<
https://github.com/notifications/unsubscribe-auth/AK9rOMB7jUS7B6oXSDqQg9MflGJv7-xAks5uF5PXgaJpZM4VG932
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jlpresearch/gem5/pull/5#issuecomment-404607207, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGsHCfQ077yrEsgoKeqbDW1M39csqPuks5uF5WUgaJpZM4VG932
.

--
Jason Lowe-Power
Assistant Professor, Computer Science Department
University of California, Davis
3049 Kemper Hall
https://faculty.engineering.ucdavis.edu/lowepower/

Oops, yeah forgot to re-enable style-check. I'' be sure to give it a run through.
Also, the last thing I'd really like to get back in is the --uid flag for the run command. After that's back I don't have any blocking issues with this being merged.

Hey Sean,
Sorry this took so long. I've finally had some time to test it out.
A few things:

Could you rebase this branch so it can be pushed to mainline? If we want to push with the new whimsy that commit should be amended.
There's a bug in python threading that requires a change in tests/gem5/fixtures.py (sorry for the bad formatting, but it'll be easier for you to fix since you're rebasing anyway).
diff --git a/tests/gem5/fixture.py b/tests/gem5/fixture.py                                                                                index 084ecc2..4d9b455 100644                                                                                --- a/tests/gem5/fixture.py                                                                                +++ b/tests/gem5/fixture.py                                                                                @@ -219,6 +219,7 @@ class DownloadedProgram(Fixture):                                                                                def _getremotetime(self):                                                                                import urllib2, datetime, time                                                                                +        import _strptime # Needed for python threading bug                                                                                u = urllib2.urlopen(self.url)                                                                                return time.mktime(datetime.datetime.strptime( \                                                                                u.info().getheaders("Last-Modified")[0],
I can't run any tests for ISAs other than NULL, X86, and ARM. There should be one RISC-V test to make sure it compiles (see tests/gem5/test_build.py), but it's not showing up no matter what I do.
I tried ./main.py run --isa RISCV, but it tires to build all ISAs, but it doesn't list any valid targets under "Building the following targets...". It's definitely a bug, but I'm not sure what's going on.
Another small thing while you're rebasing... Could you change the print message "Building the following targets. This may take a while." to "Building the following targets. This may take a while. You may want to run with only a single ISA (--isa=), use --skip-build, or use 'retest'."
4a) BTW, is retest documented anywhere?
Have you gone back through TESTING.md to make sure the documentation is still correct?
Try running ./main.py run --uid SuiteUID:tests/gem5/m5_util/test_exit.py:m5_exit_test-X86-fast This definitely doesn't work correctly.
I'm not sure if --include-tags works correctly.
When I run ./main.py run --include-tags fast -vvv It doesn't run any of the fast tests. I see this:
Filtering suites with tags as follows:   Include: fast                                                                                Include: ^X86$                                                                                Include: ^SPARC$                                                                                Include: ^ALPHA$                                                                                Include: ^RISCV$                                                                                Include: ^ARM$                                                                                Include: ^MIPS$                                                                                Include: ^POWER$                                                                                Include: ^NULL$                                                                                Include: ^quick$                                                                                Include: ^opt$                                                                                Remove: ^long$                                                                                Remove: ^debug$                                                                                Remove: ^fast$

Hey Jason,
No worries thanks for reviewing!
I'm out for the weekend at a music festival and don't get back till late
monday night so I won't be able to address this until probably
Wednesday/Thursday.
On Thu, Jul 19, 2018, 19:58 Jason Lowe-Power<EMAIL_ADDRESS>wrote:

Hey Sean,
Sorry this took so long. I've finally had some time to test it out.
A few things:

Could you rebase this branch so it can be pushed to mainline? If we
want to push with the new whimsy that commit should be amended.
There's a bug in python threading that requires a change in
tests/gem5/fixtures.py (sorry for the bad formatting, but it'll be easier
for you to fix since you're rebasing anyway).
diff --git a/tests/gem5/fixture.py b/tests/gem5/fixture.py index
084ecc2..4d9b455 100644 --- a/tests/gem5/fixture.py +++
b/tests/gem5/fixture.py @@ -219,6 +219,7 @@ class
DownloadedProgram(Fixture): def _getremotetime(self): import urllib2,
datetime, time + import _strptime # Needed for python threading bug u =
urllib2.urlopen(self.url) return time.mktime(datetime.datetime.strptime(
u.info().getheaders("Last-Modified")[0],
I can't run any tests for ISAs other than NULL, X86, and ARM. There
should be one RISC-V test to make sure it compiles (see
tests/gem5/test_build.py), but it's not showing up no matter what I do.
I tried ./main.py run --isa RISCV, but it tires to build all ISAs, but
it doesn't list any valid targets under "Building the following
targets...". It's definitely a bug, but I'm not sure what's going on.
Another small thing while you're rebasing... Could you change the
print message "Building the following targets. This may take a while." to
"Building the following targets. This may take a while. You may want to run
with only a single ISA (--isa=), use --skip-build, or use 'retest'."
4a) BTW, is retest documented anywhere?
Have you gone back through TESTING.md to make sure the
documentation is still correct?
Try running ./main.py run --uid
SuiteUID:tests/gem5/m5_util/test_exit.py:m5_exit_test-X86-fast This
definitely doesn't work correctly.
I'm not sure if --include-tags works correctly.
When I run ./main.py run --include-tags fast -vvv It doesn't run any
of the fast tests. I see this:
Filtering suites with tags as follows: Include: fast Include: ^X86$
Include: ^SPARC$ Include: ^ALPHA$ Include: ^RISCV$ Include: ^ARM$ Include:
^MIPS$ Include: ^POWER$ Include: ^NULL$ Include: ^quick$ Include: ^opt$
Remove: ^long$ Remove: ^debug$ Remove: ^fast$

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/darchr/gem5/pull/5#issuecomment-406457461, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9rOGlw1pmltSS5jH5f63H09GRDPxrsks5uISs8gaJpZM4VG932
.

No worries. Have fun!
Jason
On Thu, Jul 19, 2018 at 10:14 PM Sean Wilson<EMAIL_ADDRESS>wrote:

Hey Jason,
No worries thanks for reviewing!
I'm out for the weekend at a music festival and don't get back till late
monday night so I won't be able to address this until probably
Wednesday/Thursday.
On Thu, Jul 19, 2018, 19:58 Jason Lowe-Power<EMAIL_ADDRESS>wrote:

Hey Sean,
Sorry this took so long. I've finally had some time to test it out.
A few things:

Could you rebase this branch so it can be pushed to mainline? If we
want to push with the new whimsy that commit should be amended.
There's a bug in python threading that requires a change in
tests/gem5/fixtures.py (sorry for the bad formatting, but it'll be easier
for you to fix since you're rebasing anyway).
diff --git a/tests/gem5/fixture.py b/tests/gem5/fixture.py index
084ecc2..4d9b455 100644 --- a/tests/gem5/fixture.py +++
b/tests/gem5/fixture.py @@ -219,6 +219,7 @@ class
DownloadedProgram(Fixture): def _getremotetime(self): import urllib2,
datetime, time + import _strptime # Needed for python threading bug u =
urllib2.urlopen(self.url) return time.mktime(datetime.datetime.strptime(

u.info().getheaders("Last-Modified")[0],
I can't run any tests for ISAs other than NULL, X86, and ARM. There
should be one RISC-V test to make sure it compiles (see
tests/gem5/test_build.py), but it's not showing up no matter what I do.
I tried ./main.py run --isa RISCV, but it tires to build all ISAs, but
it doesn't list any valid targets under "Building the following
targets...". It's definitely a bug, but I'm not sure what's going on.
Another small thing while you're rebasing... Could you change the
print message "Building the following targets. This may take a while." to
"Building the following targets. This may take a while. You may want to
run
with only a single ISA (--isa=), use --skip-build, or use 'retest'."
4a) BTW, is retest documented anywhere?
Have you gone back through TESTING.md to make sure the
documentation is still correct?
Try running ./main.py run --uid
SuiteUID:tests/gem5/m5_util/test_exit.py:m5_exit_test-X86-fast This
definitely doesn't work correctly.
I'm not sure if --include-tags works correctly.
When I run ./main.py run --include-tags fast -vvv It doesn't run any
of the fast tests. I see this:
Filtering suites with tags as follows: Include: fast Include: ^X86$
Include: ^SPARC$ Include: ^ALPHA$ Include: ^RISCV$ Include: ^ARM$
Include:
^MIPS$ Include: ^POWER$ Include: ^NULL$ Include: ^quick$ Include: ^opt$
Remove: ^long$ Remove: ^debug$ Remove: ^fast$

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/darchr/gem5/pull/5#issuecomment-406457461, or mute
the thread
<
https://github.com/notifications/unsubscribe-auth/AK9rOGlw1pmltSS5jH5f63H09GRDPxrsks5uISs8gaJpZM4VG932
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/darchr/gem5/pull/5#issuecomment-406491260, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGsHDbC-9WB70ZLxaXp44ClPQDz85T4ks5uIWdPgaJpZM4VG932
.

--
Jason Lowe-Power
Assistant Professor, Computer Science Department
University of California, Davis
3049 Kemper Hall
https://faculty.engineering.ucdavis.edu/lowepower/

Alright finally getting to this...

In Progress.
Done.
Fixed. I changed the tag logic back to just a simple iterable of tags. The definition in tests/gem5/test_build/test_build.py was using a dictionary, this has been fixed and now adds a RISCV test+suite.
Done. I also added a warning message in the event that no SCons target was specified so users don't unknowingly build every gem5 target.
I also added a section on rerun to TESTING.md
I made a pass through and it looks all good to me. I think I only had to adjust the parallel execution section and the list command.
Good catch. This is a bug, the tags are currently filtering out suites when the --uid flag is provided. Flag filter no longer occurs when the --uid flag is provided, and your usage now works as expected.
So this usage is an edge case and I'm not sure how we should deal with it.
The library implementation expects users to use the --variant flag for something like this.
What happens is that all the gem5 "special" flag filters (opt, fast; quick, long; RISCV, ARM; etc.) are applied after the user specific filters. This makes the gem5 options supplied by the command line take priority.

So you don't have to dig through a markdown ordered list for actions to take:
If my comment on number 7 doesn't make sense or your usage should be enabled let me know. Otherwise, I'll work on the rebase which should be good to go.


Improve the precision of the binary_sensor.fan_running depend of the temperature

Good morning,
This is less of an issue for me and more of a question regarding the starting temperature of the fan.
Your code shows an active fan from 45°C. In my case, however, the fan switches to active above 43°C and switches off again below 40.5°C. This means that the ICON of the fan is not active, even though it is already running, as I have only reached 45°C a few times so far.
Is it somehow possible to change this in the code so that the value is set as "Fan on" from 43°C?
logs_wt32-eth01_logs.txt

I will compare the threshold on my side another time and make the value configurable if it's different. At the moment it's hardcoded and cannot be changed easily.

Thanks for your reply.
Addtionally I found out, that your current code works corrcetly, if the inverter temp reaches 45°C. Then it shows, "FAN on" even it is running since 43°C.

The fan of my Soyosource 1200W (Display version + chatty via RS485) turns on at 44.5°C (the display shows ceil(44.5) = 45°C) and off around 40°C (40.4°C).

@Chickenbreast0 Which model do you own?

@Chickenbreast0 Which model do you own?

Mine is a 1000W model with display and talkative RS485 Port. Those values above I got from the RS485 Port.
Offtopic reg. the talkative part: I replaced the CPU PCB with a "new" one from Aliexpress for testing purposes. Suddenly it stopped showing me all values. After changing it back, it "spoke" to me again. Therefore I guess the communication thing depends on the CPU Board.


Add parameter for connection demodulator with selected oscillator

Changes proposed in this pull request:

Add parameter to UHFLI driver to select oscillator per demodulator

@WilliamHPNielsen

@WilliamHPNielsen Great thanks. I have only tested this on a device with MF enabled.

@qSaevar, that's what I thought. And I have one without MF, so that could be good to test, but I'll risk it, just this once.


[TACHYON-935] Added the usage of links in the documentation in the tachyon.worker.block package

https://tachyon.atlassian.net/browse/TACHYON-935

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7192/
Test PASSed.

LGTM. Thanks.


Add blobToDataURL (for testing)

This PR is just to test in Sauce Labs: https://github.com/nolanlawson/blob-util/pull/29

I've spent like an hour just trying to get the damned tests running again. Sauce Labs and LocalTunnel are not being kind to me.

Once the build is fixed, the next challenge is migrating over the documentation which unfortunately must be done manually. :/

passed


Add support PSP enabled clusters in chart

Subj

Hi!
For your information PSP are going to be deprecated in the next Kubernetes release:
kubernetes/kubernetes#97171
Any way PRs are welcome, here is example commits to add similar functionality in another my project, it can be used as template:
https://github.com/kvaps/kube-linstor/commit/d9f3dd74771250303b063577087c8117176a00f0 https://github.com/kvaps/kube-linstor/commit/591694ebdccccfb2d00ddd4e43983071b688bfc1


Update to SenzingAPI 3.8.0

Phase 1

[x] g2-sdk-go

Phase 2

[x] g2-sdk-go-base
[x] g2-sdk-go-grpc
[x] g2-sdk-go-mock

Phase 3

[x] serve-grpc
[x] go-sdk-abstract-factory

Phase 4

[x] go-rest-api-service
[x] init-database
[x] serve-chat
[x] serve-http

Phase 5

[x] senzing-tools

Pull requests:

https://github.com/Senzing/g2-sdk-go/pull/96
https://github.com/Senzing/g2-sdk-go/pull/97


(FACT-3205) Ignore ENOENT when cleaning up temporary test files

Facter tests sometimes fail on JRuby with the following, even when using
the same seed:
$ bundle exec rspec --order random:22464 spec_integration
...
Errno::ENOENT:
  No such file or directory - /tmp/external_facts20240617-2780089-h18bte/XFZQDAMC_data.yaml
# ./spec_integration/facter_spec.rb:13:in `write_to_file'
# ./spec_integration/facter_spec.rb:752:in `block in <main>'

Since ENOENT means the entry doesn't exist, ignore it like puppet does[1].
However, we don't want to use rm_rf because that will ignore all
StandardErrors, not just ENOENT[2].
[1] https://github.com/puppetlabs/puppet/blob/8.6.0/spec/lib/puppet_spec/files.rb#L11-L15
[2] https://bugs.ruby-lang.org/issues/18784

For the commit, 69030d149a3d94f53153925f2bd77ca602c6f4db, could we just include the removal of RSpec/MultipleMemoizedHelpers?


Fix escaping in LDAP search strings [CVE-2020-14013]

When username contains any special character (parentheses, asterisk, ...)
user search will fail.
When returned DN of user contains any escaped character (for example ",")
group filter will fail.
Example:
(&(CN=group)(member=CN=dummy\, dummy2,OU=ou,DC=dc))"

Which is wrong and doesn't work with Active directory.
Correct is:
(&(CN=group)(member=CN=dummy\5C, dummy2,OU=ou,DC=dc))"

This patch fixies both of these bugs by using ldap_bv2escaped_filter_value
from LDAP client to escape all of filter values.
See: https://tools.ietf.org/search/rfc2254#page-5
Fixes #224 fixes #180
CVE-2020-14013

I encountered the error during make install with this module.
/root/nginx-auth-ldap/ngx_http_auth_ldap_module.c: In function ‘ngx_http_auth_ldap_escape_filter’:
/root/nginx-auth-ldap/ngx_http_auth_ldap_module.c:766:19: error: pointer targets in assignment differ in signedness [-Werror=pointer-sign]
     userbv.bv_val = in->data;
                   ^
cc1: all warnings being treated as errors
make[1]: *** [objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o] Error 1
make[1]: Leaving directory `/root/nginx-1.20.1'
make: *** [build] Error 2


Lightbox animated gif App IOS

Full page animated gifs do now show animated (in lightbox). In a thread they are animated.
Happens in IOS app (tested on miniIpad IOS 12)
In Android App, animations show in threads and in full screen. The same in webapp in Chrome.
Note; I am not a coder, this is my first issue on github / Zulip ever. If I did something wrong or can do better please let me know.

Hmm! Thanks for the report. I reproduce the issue, with the current beta version v26.28.151.
We previously had #3497 and fixed that with #3825 -- but that was specific to Android and it seems we didn't notice there was also a problem on iOS.

The earlier fix #3825 added something that the React Native docs specifically say is needed on Android:
https://reactnative.dev/docs/0.59/image#gif-and-webp-support-on-android
The docs don't say anything about animated-GIF support being missing on iOS. So the first thing we'll need to do to resolve this is some debugging -- why are animated GIFs not working?
A quick reproduction is to go to #test here > gif test on chat.zulip.org. (Same topic @agrawal-d used in the demonstration in #3825.)


DbfFieldType What type is Chinese

Hi  I'm using Dbase.net but there doesn't seem to be any Chinese for field types

So sorry   It's because I use Encoding myself in wrong formats


Add support for e10s

In the latest versions of firefox, mozilla is adding support for multithreading. Pentadactyl should work to being compatable with this eventually, right now it is completely unusable. So far ex commands seem to work fine, but any movement (among other things) is broken. I've attached a paste of me using it for a few seconds. Pentadactyl works fine w/o e10s enabled!
This page seems relevant. This seems like a long term goal, but I'm just putting it out there, because this will eventually be default in firefox, and it would be great if pentadactyl could support it before then!
paste data
my pentadactylrc, it seems to be breaking up on map commands...

Hm, back when this was hosted on google code, there was a feature request thread about this, but I guess it wasn't transfered here.
This is known problem, firefox had some experimental code for this for long time, but it looks like it's gonna go enabled by default really soon (3-6 months).
It doesn't break just pentadactyl tho, it breaks many common extensions.

At this point, all ~20 of the extensions I use work with e10s, except pentadactyl.

http://arewee10syet.com/

Seeing as e10s is default very soon, a fix for this would be appreciated. If no-one has time, where should I get started looking to try and fix myself?

@triclops200
<3

Any chance devs can make this milestone for next stable version?

Pentadactyl works 41 Developer Edition if multi-process is turned off. It if is turned on pentadactyl url line is often red and searching through the page doesn't work.


Feedback: Move + Rotation Gizmos are too big

Please resize the gizmos to half size... or allow settings to control the size of the gizmos as they are too big. (Possible Hotkey - or +)

Thanks for your feedback. I will improve it.


propagate specific target tags to run and run_shell actions as execution_requirements

Resolves #187

The underlying issue is that tags are not propagated to actions automatically and thus are only applied when the ruleset they're used with propagates them explicitly. This PR handles said propagation for higherkindness/rules_scala.
There is an open PR to bazelbuild/bazel that will handle this propagation on Bazel's side (https://github.com/bazelbuild/bazel/pull/8612), but I wanted the issue to be resolved for highkindness/rules_scala sooner than later. For future consistency, I'm propagating the same tags that PR will propagate.

@borkaehw @jjudd would you mind reviewing when you get a min?


Added The Currency Converter Tool

#3
Added Currency Converter

Added One Folder currency with 3 files

Made changes to the Index.html file

Made changes to the Readme.md file

[x] Read Contributing.md

[x] Followed all Guidelines

[x] Linked my tool to index.html file

[x] Updated Readme.md

Add the navbar and the footer as added in the index.html.
follow the design theme
add your name to the contributors.html
@Asies23 Awesome job on the PR 💯 . Just make the requested changes and it will be ready to merge.

Calculator is also not working fix it

I cannot find the styles of the navbar and footer can you help me with that

@Asies23 you can find navbar in index.html file.
Also, our contributing guidelines have been changed, so please follow them before creating PR.

Add navbar in your tool's html file. You can copy the navbar from index.html.
Add screenshot of your tool in, PR message and also in the folder of your tool
Before Making the PR Pull the latest changes that have been made to the repository
PR with any conflicts will not be merged
**Note: Please Don't Make Any Changes In index.html AND contributors.html **


Add to tsv-utils-dlang csv-parsers-comparison

It would be nice to get comparison with https://github.com/uniVocity/csv-parsers-comparison
And other native parsers (written on C/C++)

Thanks for pointing this page out, I wasn't aware of it. It doesn't look like the specifics of the test fit, as none of my tools actually does a csv parse and count the lines. And, the test suite is specific to java.
Still, it would be useful to have a comparison basis against java tools, and there is a good list on the page. I didn't investigate java tools primarily because I didn't want to deal with the fairly accounting for jvm startup time, but a comparison would be useful.


Language chooser unreviewed

This change is

First, set up Nx if you haven't done so already (see [README.md](../../README.md)).

We recommend installing nx globally, but if you haven't, you can just prefix all the commands with `npx`

Let's be consistent with capitalization of "Nx". I suggest lowercase everywhere.

FWIW, they refer to their own product with capitalized Nx.

Let's be consistent with capitalization of "Nx". I suggest lowercase everywhere.

FWIW, they refer to their own product with capitalized Nx.

Thanks. At first, I was leaning toward using Nx for the thing and nx for the commands, but after seeing it would sometimes be ambiguous, I thought it was easier to just use nx everywhere.
Example: "... you can alternatively run the nx commands ..."


Check library version

Make it possible to check library version via access to some built-in variable, like:
$.fn.jquery // "2.1.4"

done in #101


download using actions="only" does not work for me since version 0.0.22

I use fix_yahoo_finance to download pure dividend information. Since the removal of the
deprecated Panel in version 0.0.22 this no longer seems to work. It works fine for downloading the regular price data. I think its related to specifically looking for certain columns in the scraped data. The error message is "KeyError: "['Open' 'High' 'Low' 'Close' 'Adj Close' 'Volume'] not in index". You can replicate the problem in version 0.0.21 by calling the download function with actions="only", and as_panel=False.

Having the same issue...


FCREPO-2853. Add acl:accessTo for current resource if none specified

JIRA Ticket: https://jira.duraspace.org/browse/FCREPO-2853

Other Relevant Links (Mailing list discussion, related pull requests, etc.)

What does this Pull Request do?
If an ACL Authorization does not include an accessTo or accessToClass, set the accessTo to the current resource.
What's new?
Updated the replaceResourceWithStream method in ContentExposingResouce class to add the default accessTo when not specified.
How should this be tested?
Verify default accessTo is set when not specified.

Create an ACL at http://localhost:8080/rest/test_resource/fcr:acl with content

PREFIX acl: <http://www.w3.org/ns/auth/acl#>
PREFIX webac: <http://fedora.info/definitions/v4/webac#>

<> a webac:Acl .

<#authorization1> a acl:Authorization ;
   acl:mode acl:Read ;
   acl:agent "testuser" .

Verify that the http://localhost:8080/rest/test_resource/fcr:acl#authorization1 resource contains an acl:accessTo predicate with http://localhost:8080/rest/test_resource as object.

Verify default accessTo is not set when already specified in the turtle.

Create an ACL at http://localhost:8080/rest/test_resource1/fcr:acl with content

PREFIX acl: <http://www.w3.org/ns/auth/acl#>
PREFIX webac: <http://fedora.info/definitions/v4/webac#>

<> a webac:Acl .

<#authorization1> a acl:Authorization ;
   acl:mode acl:Read ;
   acl:accessToClass webac:Acl ;
   acl:agent "testuser" .

Verify that the http://localhost:8080/rest/test_resource1/fcr:acl#authorization1 resource does NOT contain an acl:accessTo predicate with http://localhost:8080/rest/test_resource1 as object.

Interested parties
@fcrepo4/committers

Commit already merged algongside changes for #1401


Yubikey Support

OS: Windows
GPMDP Version: 4.6.1
Issue Descriptions:
Yubikey does not work when authenticating. This is an old issue (#268 #925), but it looks like it is now supported with Electron 4.
https://github.com/electron/electron/issues/3226#issuecomment-433541540

If it works in Electron 4 it will work when we update to that version


Use default config on missing configuration section

Use default config on missing configuration section
On serving initialize request, the deserialization of HIE configuration
embedded in InitializeParam passed by client will result in an error if
during the deserialization process the server cannot find HIE specific
configuration key under initializationOptions.
This commit changes the initializationOptions deserialization to return
the default configuration if configuration key cannot be found under
initializationOptions. Here, setting the key with a value of null will
also be considered as part of not found condition to accommodate clients
that fills missing user options as null.

@aufarg This project is not actually active any more, so PRs will not be merged.  I see you did do something on haskell-language-server too, which is the project superseding this one

@alanz Okay, I'll close the PR then. Thanks for telling me this.


ability to invoke another API from document within JavaScript code editor

in Unit testing  https://docs.insomnia.rest/insomnia/unit-testing.  Would you please add the ability to invoke another API from the Javascript code editor?
const response = await insomnia.send();
const body = JSON.parse(response.data);
expect(body).to.be.an('array');

I realized I can invoke another API like below, however, is there a way to send in query variables data dynamically?
const response2 = await insomnia.send('req_b733c874b56c477982ac7da149d21ab6');

What is req_b733c874b56c477982ac7da149d21ab6 ? where can I find it? Also is there a way to find detailed test results, like why it diff between expected and received response?

@me-nkr that is an Insomnia id for a request that is defined in the document.

You can call other requests within Unit test code using this id, for example:

Hi @tina-barrett-mahana thank you for reporting this issue! There is no way at the moment to edit query variables or other parts of request before sending it within an Insomnia Unit test.
We are at the moment gathering all this kind of feedback to try and come up with a feasible plan to improve the test feature.
Feel free to report any other issues or improvements you notice 👍


chore: release 2.2.0

:robot: I have created a release *beep* *boop*
2.2.0 (2021-01-09)
Features

components such as responses, request bodies and deeply nested schemas are now supported (65c1f42)

This PR was generated with Release Please. See documentation.

Codecov Report

Merging #18 (66846ac) into main (65c1f42) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   99.21%   99.21%
=======================================
  Files          17       17
  Lines         254      254
  Branches       61       61
=======================================
  Hits          252      252
  Partials        2        2

Continue to review full report at Codecov.

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

Codecov Report

Merging #18 (66846ac) into main (65c1f42) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   99.21%   99.21%
=======================================
  Files          17       17
  Lines         254      254
  Branches       61       61
=======================================
  Hits          252      252
  Partials        2        2

Continue to review full report at Codecov.

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


Added operator-sdk target to Makefile

This will be helpful for the downstream build and will help to run the make bundle command if operator-sdk is not present on the system.
Signed-off-by: bindrad<EMAIL_ADDRESS>

@renan-campos @kesavanvt Can you please review this PR?

@bindrad Can we try to revive this PR?

@bindrad Can we try to revive this PR?

Yes, we can @nb-ohad

@bindrad Does the change in this PR still valid? are we sure it still works?

@bindrad Can we close this one?

Closing PR as work was done in another PR


Upgrade version 2.6.0

Upgrade version to 2.6.0
#192

Pull Request Test Coverage Report for Build 447

0 of 0   changed or added relevant lines in 0 files are covered.
58 unchanged lines in 14 files lost coverage.
Overall coverage decreased (-0.5%) to 65.369%

Files with Coverage Reduction
New Missed Lines
%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/endpoint/SofaBootVersionEndpoint.java
1
81.94%

isle-sofa-boot-starter/src/main/java/com/alipay/sofa/isle/spring/listener/SofaModuleContextRefreshedListener.java
1
72.41%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/startup/ReadinessCheckProcessor.java
1
75.86%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/factory/ServiceFactoryBean.java
2
69.44%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/service/helper/ReferenceRegisterHelper.java
2
76.19%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/config/spring/namespace/handler/SofaBootNamespaceHandler.java
3
0.0%

test-sofa-boot-starter/src/main/java/com/alipay/sofa/test/runner/SofaJUnit4Runner.java
3
56.67%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/factory/AbstractContractFactoryBean.java
4
52.38%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/core/AfterHealthCheckCallbackProcessor.java
4
60.87%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/configuration/HealthCheckConfiguration.java
4
40.0%

Totals

Change from base Build 443:
-0.5%

Covered Lines:
1461

Relevant Lines:
2235

💛  - Coveralls


Simpler IPC implementation using std::os::unix::net instead of using interprocess crate.

I'm going to go ahead and merge this, let me know if any improvements can be made with by opening a GitHub issue or by leaving a message here.


Do terrible things to use a provided Pool

This will slice off the ?pool= param

@franknoirot thank you! Some changes in now; happy to keep iterating to prevent this from being a mess to maintain. Works locally!


SNS with KMS

Took inspiration from the SQS module for the KMS and added some support here

Adding KMS support to SNS module

Added SNS Topic Policy and Delivery Policy Variables + Updated Docs

Thanks for opening this pull-request. I've just released v2.0.0 where this functionality is implemented and it requires Terraform 0.12.
Closing this PR.


Web Edition

Is your feature request related to a problem? Please describe.
I would like to work at my Android tablet.
Describe the solution you'd like
A browser version powered by wasm.
Describe alternatives you've considered
An Android app.
Additional context

Duplicate of #1642


surface form for SPMe

At the moment if you pass the option {"surface form":"differential"} or {"surface form": "algebraic"} to SPMe nothing happens. SPMe always uses pybamm.electrolyte_conductivity.Composite.
We should either raise an OptionError or add the relevant surface models for SPMe

I tried implementing this in #884 in case it was a quick fix but I am getting errors for both models (full and leading-order). For the moment I set it to throw a NotImplementedError so if that is enough we may close this issue once #884 is merged.
Otherwise, if we want to implement the model, we need to derive the appropriate surface form for Composite. Is there any reference on this kind of formulation?

There is my thesis, if you are feeling brave, but I wouldn't go down that route. In theory the leading order form should work though. What was the error?

The differential works but the algebraic doesn't. Here is the error:
======================================================================
ERROR: test_surface_form_algebraic (__main__.TestSPMe)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ferranbrosa/PyBaMM/tests/unit/test_models/test_full_battery_models/test_lithium_ion/test_spme.py", line 119, in test_surface_form_algebraic
    model.check_well_posedness()
  File "/home/ferranbrosa/PyBaMM/pybamm/models/base_model.py", line 377, in check_well_posedness
    self.check_well_determined(post_discretisation)
  File "/home/ferranbrosa/PyBaMM/pybamm/models/base_model.py", line 469, in check_well_determined
    raise pybamm.ModelError("model is overdetermined (repeated keys)")
pybamm.expression_tree.exceptions.ModelError: model is overdetermined (repeated keys)

----------------------------------------------------------------------


Activate sponsor button in GitHub

Displays the "❤ Sponsor" in the repository, more info:
https://help.github.com/en/github/building-a-strong-community/displaying-a-sponsor-button-in-your-repository
The link is the same as the one in the README

Sounds like a good idea to me, merging!

Nice it worked, thanks @fredj now if we only had some donations :)

If you want to get involved more in the project feel free to suggest ideas, grab tickets etc... Just comment on anything you feel like working on. If you have time and are unsure what you would interest in, also feel free to list your skills, a can help find something. There are tons of things I can think of that would make Maputnik better other that editor contributions also

Documentation
Building a truly open source map style from https://github.com/lukasmartinelli/naturalearthtiles (rather than pay to use providers)
Better release notes, gifs/videos etc... so we can let people know whats going on a little more
UX reviews with users

Obviously it's totally up to you, just good to have people about either way. Thanks for all the effort
CC'ing @pathmapper because we should probably put that sort of statement in a contributing file or something and get better at welcoming new contributors (I'll raise a ticket separately for that)

Thanks for the welcome message @orangemug !

we should probably put that sort of statement in a contributing file or something and get better at welcoming new contributors (I'll raise a ticket separately for that)

Yeah, let's do it.

Building a truly open source map style

That's something I'm having also on my list. If someone wants to start working on this together, just let me know.


Vault Banning

Vaults are slashed on redeem failure, do we also need to ban them for 24h?

The question was, what is the reason for the punishment delay? The delay stopped them to perform redeems for 24 hours.
As the fees are spread over all participants, the consequence of not being able to act seem unclear.
Perhaps not paying out fees (or reducing their SLA) for 24 hours would make more sense? But I haven't studied the new fee / sla specs and code in detail yet.

For reference, the following actions are currently prohibited when a Vault is banned:

request_issue
request_redeem
request_replace
accept_replace

We have recently removed the SLA module, but the Vault may still earn rewards on locked interBTC unless `reimburse == true``.

I agree that disallowing redeem does not really punish vaults - rather the opposite, since it's in the vault's interest to have as many issued tokens as possible for maximum reward generation.

Perhaps not paying out fees (or reducing their SLA) for 24 hours would make more sense

I like this idea, we could certainly temporarily reduce the vault's stake for the rewards. Although implementing it requires a bit of a change since stake will no longer be equal to the collateral - we would need to separate the accounting for both of these.

Good points. Agree that banning the vaults for 24 hours is not a punishment per se.
Punishment aspect Banning vaults only prevents them from not being able to accept additional issue requests and thus not being able to increase their reward stake in the system. For that reason alone, we might not want to include it.
Vault protection aspect A vault client might experience a temporary outage (e.g., servers are down). In that case, the 24 hour delay might help vault operators that their system is not drained of collateral if they go offline for 24 hours. The punishment delay might actually help them to recover their services. This might be a good enough reason to keep this.


fix: add entrypoint and cmd to Dockerfiles

Fixes #1296.

Closing this since

We'll land this on the v2 branch.


.NetworkSettings.IPAddress does not work for non-default Docker networks

[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "docker.localhost"
watch = true

[web]
address = ":8080"

docker run -d -p 8080:8080 -p 80:80 -v /var/run/docker.sock:/var/run/docker.sock -v $PWD/traefik.toml:/traefik.toml containous/traefik
docker run swarm:1.0.0 manage token://blablabla

docker network create bla
docker run -d --net=bla -p 8080:8080 -p 80:80 -v /var/run/docker.sock:/var/run/docker.sock -v $PWD/traefik.toml:/traefik.toml containous/traefik
docker run --net=bla swarm:1.0.0 manage token://blablabla

This especially hurts docker-compose setups, as it creates a custom network by default.

Turns out this is due to {{.NetworkSettings.IPAddress}} being empty, and is deprecated.
There probably needs to be a setting to configure which network you want to use per container, but a quick workaround is to override the default template with:
{{range $i := .NetworkSettings.Networks}}{{if $i}}{{.IPAddress}}{{end}}{{end}}

However, it seems the currently stable containous/traefik Docker image probably contains an older version of the github.com/fsouza/go-dockerclient library, as it doesn't recognise Networks as a valid field:
docker.tmpl:3:61: executing \"docker.tmpl\" at <.NetworkSettings.Net...>: Networks is not a field of struct type *docker.NetworkSettings"

From the looks of it, this feature was merged in november last year.

Thanks a lot @JeanMertz for reporting and analyzing this :)
I just created a PR that fixes this #227. Can you test using this branch?


Create Conda environment file

This environment file is very convenient for Conda users to create an Pommerman environment by conda env create -f env.yml.
And Conda is much better because it can manage versions of Python and installation of CUDA toolkits.

The version of numpy is 1.14.6 which is different from that in setup.py.

If this can be merged, I can edit README.md before merged.

Temporarily closed due to cross-platform problems I have just found.


I have ARFIMA, you can use it

Just letting you know of this: https://github.com/Datseris/ARFIMA.jl  that you may want to use.

Thank you again. I will take a serious look as soon as I will start implementing simulations. I detailed a plan for the next releases at this link. I will look back at your package and try to implement simulations for most models when I will work on v0.1.6.
At the moment, I am working on implementing VARIMA models (estimation and forecast) - in a similar fashion to what is currently implemented for the ARIMA models.

I will keep this issue opened and look back at it as soon as I get to v0.1.5.

I have decided to close this issue. In the near future, I do not plan to add fractional models.


Actions: add a Signed-off-by check for incoming PRs

Add a new Github action to check that all commits in an incoming PR contain a Signed-off-by tag.

LGTM, thanks for implementing this!


Also I don't pull any YKWhat


Fix delete network error.

Fix a bug when deleting a network which can't be found.
@guangxuli

Pull Request Test Coverage Report for Build 52

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 35.538%

Totals

Change from base Build 48:
0.0%

Covered Lines:
5630

Relevant Lines:
15842

💛  - Coveralls


trigger prod cli 0.16

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


Propagate lack of stored proc support to 21.2.

Fixes https://github.com/cockroachdb/docs/issues/10689 in 21.2.

This change is

The last (Misc) table on the web site is broken.

I played around with the included warning, but the only way to fix the table was to explictly specify the warning instead of including it. Not sure why.

Approved. But I think the reason the include didn't work is because there's a trailing line break in interleave-deprecation-notice.md. Can you try removing the line break and see if the table still breaks?

There is no trailing line break that I can see either in Atom, vi, or GH.

@ianjevans I could not get the include file to work with the latest version of the referring file. I realized that the include exists because multiple files were including it. I'm worried that the include file still referenced in alter-primary-key and the explicit warning in sql-feature-support will get out of sync. Should I still merge this?

@ianjevans I could not get the include file to work with the latest version of the referring file. I realized that the include exists because multiple files were including it. I'm worried that the include file still referenced in alter-primary-key and the explicit warning in sql-feature-support will get out of sync. Should I still merge this?

I tried this locally, and it worked.
Interleaved tables | ✓ | CockroachDB Extension | [Interleaved Tables documentation](interleave-in-parent.html)<br>{% include {{ page.version.version }}/misc/interleave-deprecation-note.md -%}

See the Liquid docs on whitespace control.
But I also see that my local build doesn't break the table even without the -%}. So there's a discrepancy between local Jekyll builds and the Netlify builds, perhaps. Regardless, try pushing a commit with the -%} at the end of the include and see if it breaks the table.


Kmesh does not handle request unless return value of check_sock_enable_kmesh is hardcoded to True

If we deploy Kmesh using a locally built image, Kmesh does not handle any requests. In order for Kmesh to handle requests we need to hardcode the return value of check_sock_enable to True
What you expected to happen:
We should not need to make this code change for Kmesh to handle the request.
How to reproduce it (as minimally and precisely as possible):

Build Kmesh locally.
Deploy the below backend service

apiVersion: v1
kind: Service
metadata:
  name: app-b
  labels:
    app: app-b
    service: app-b
spec:
  ports:
  - port: 8000
    name: httpb
  selector:
    app: app-b
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: app-b
  labels:
    app: app-b
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app-b
  template:
    metadata:
      labels:
        app: app-b
    spec:
      containers:
      - name: app-b
        image: swr.cn-north-4.myhuaweicloud.com/hwstaff_pub_torontodsdelab/fastapi-sample:v1.2
        env:
        - name: SERVICE_NAME
          value: "app-b"
        resources:
          requests:
            cpu: "100m"
        imagePullPolicy: IfNotPresent #Always
        ports:
        - containerPort: 8000

Deploy Kmesh
Send Http Request And View BPF Logs

kubectl exec -it netutils -- curl app-b:8000/hello

The BPF logs show no response, meaning Kmesh does not handel the request.

Perform all the above steps and set the return type of check_sock_enable_kmesh to True instead of False and send the HTTP request. The bpf logs show that kmesh handles the request.

..
21<PHONE_NUMBER>86: bpf_trace_printk: [KMESH] DEBUG: bpf find listener addr=[2681824522:16415]

<...>-341703  [002] d..21<PHONE_NUMBER>55: bpf_trace_printk: [CLUSTER] INFO: 1 lb_policy is unsupport, defaut:ROUND_ROBIN

<...>-341703  [002] d..21<PHONE_NUMBER>60: bpf_trace_printk: [CLUSTER] INFO: cluster="outbound|8000||app-b.default.svc.cluster.local", loadbalance to addr=[3339430080:16415]

Anything else we need to know?:

OS: OpenEuler 23.03 and Ubuntu 22.04
Istio: 1.19
Kubernetes: 1.27.
Kmesh version: Latest code from main branch

cc @lec-bit

I had met the same problem, i solved this problem by : 1. add label istio.io/dataplane-mode=Kmesh to namespace;
2. or the net_cls cgroup file of the netutils pod is not correct.

We are changing the way to be aware of whether a pod is controlled by kmesh, simply saying we are removing the dependency on net_cls,  because it is only supported by group v1
FYI https://github.com/kmesh-net/kmesh/pull/242

我们正在改变判断 pod 是否由 kmesh 控制的方式，简单地说，我们正在删除对 net_cls 的依赖，因为它仅受 v1 组支持
仅供参考#242

This feature is supported in v0.3.


etcdctl: update the ls subcommand help to match behavior

Currently the etcdctl ls subcommand help output is a bit misleading.
It mentions that using the --recursive flag will output all keys and
values for a given path:
--recursive  returns all values for key and child keys

This is inaccurate. The --recursive will only output the key names
under the given path. Fix the issue by updating the help string for
the --recursive flag.
--recursive  returns all key names recursively for the given path

Fixes #2379.

lgtm


Gitea ZIP Download of LFS Files downloads the pointer

Description
Using LFS in my repo and downloading the zip file of the repo downloads the pointers of the LFS Files instead of the correctly stored LFS File. If i go to the file in the Browser and klick the single file download it downloads the correct file.
I wanted to test it on try.gitea.io but currently the register / sign in pages timed out and i am not sure if LFS is active on the Server.
important app.ini config
[server]
SSH_DOMAIN =
DOMAIN =
HTTP_PORT =
ROOT_URL =
APP_DATA_PATH =
SSH_AUTHORIZED_KEYS_BACKUP = true
DISABLE_SSH = false
SSH_PORT =
LFS_START_SERVER = true
OFFLINE_MODE = false
LFS_JWT_SECRET =

Gitea Version
1.21.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.42.0, Wire Protocol Version 2 Enabled
Operating System
Windows
How are you running Gitea?
1.21.5 built with GNU Make 4.3, go1.21.6 : bindata, sqlite, sqlite_unlock_notify
downloaded from your server
Database
SQLite

Tested in GitHub. Not sure which is better, but GitHub has the same behavior.
https://github.com/yp05327/testlfs

Gitea just provides the archive that git exports which means it only provides pointers. There is an enhancement request open already to include the files in the archive.


Crashing

Hey, I got a similar issue like @josho2011:
My game Crashes with this error in game: "Create Utilities (createutilities) encountered an error during the sided_setup_event phase
java.lang.ExceptionInInitializerError: null
---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.

Time: 2023-09-19 17:25:31
Description: Mod loading error has occurred

java.lang.Exception: Mod Loading has failed
	at net.minecraftforge.logging.CrashReportExtender.dumpModLoadingCrashReport(CrashReportExtender.java:55) ~[forge-1.19.2-43.2.19-universal.jar%23796!/:?] {re:classloading}
	at net.minecraftforge.client.loading.ClientModLoader.completeModLoading(ClientModLoader.java:167) ~[forge-1.19.2-43.2.19-universal.jar%23796!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:memorysettings.mixins.json:ClienModLoaderMixin,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.Minecraft.lambda$new$2(Minecraft.java:585) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.Util.m_137521_(Util.java:438) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:perf.thread_priorities.UtilMixin,pl:mixin:APP:yungsbridges.mixins.json:SuppressLogMixin,pl:mixin:APP:bettermineshafts.mixins.json:SuppressLogMixin,pl:mixin:APP:blue_skies.mixins.json:UtilMixin,pl:mixin:APP:mixins.mega.json:UtilMixin,pl:mixin:A}
	at net.minecraft.client.Minecraft.lambda$new$3(Minecraft.java:579) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.gui.screens.LoadingOverlay.m_6305_(LoadingOverlay.java:135) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:drippyloadingscreen.mixin.json:client.IMixinLoadingOverlay,pl:mixin:APP:drippyloadingscreen.mixin.json:client.MixinLoadingOverlay,pl:mixin:APP:fancymenu.general.mixin.json:MixinLoadingOverlay,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.renderer.GameRenderer.m_109093_(GameRenderer.java:885) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:vinery-common.mixins.json:GameRendererMixin,pl:mixin:APP:supplementaries-common.mixins.json:GameRendererMixin,pl:mixin:APP:mixins.oculus.json:GameRendererAccessor,pl:mixin:APP:mixins.oculus.json:MixinGameRenderer,pl:mixin:APP:mixins.oculus.json:MixinModelViewBobbing,pl:mixin:APP:mixins.oculus.json:MixinTweakFarPlane,pl:mixin:APP:rubidium_extras.mixins.json:TotalDarkness.MixinGameRenderer,pl:mixin:APP:rubidium_extras.mixins.json:Zoom.GameRendererMixin,pl:mixin:APP:railways-common.mixins.json:conductor_possession.MixinGameRenderer,pl:mixin:APP:create.mixins.json:client.GameRendererMixin,pl:mixin:APP:create.mixins.json:accessor.GameRendererAccessor,pl:mixin:APP:mixins.oculus.json:MixinGameRenderer_NightVisionCompat,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.Minecraft.m_91383_(Minecraft.java:1115) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.Minecraft.m_91374_(Minecraft.java:700) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:mixin,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,xf:fml:xaeroworldmap:xaero_wm_minecraft_runtick,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.main.Main.m_239872_(Main.java:212) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:classloading,re:mixin,pl:runtimedistcleaner:A,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.client.main.Main.main(Main.java:51) ~[client-1.19.2-20220805.130853-srg.jar%23791!/:?] {re:classloading,re:mixin,pl:runtimedistcleaner:A,pl:mixin:A,pl:runtimedistcleaner:A}
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] {}
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:?] {}
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?] {}
	at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?] {}
	at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:27) ~[fmlloader-1.19.2-43.2.19.jar%23101!/:?] {}
	at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:30) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-10.0.8.jar%2388!/:?] {}
	at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141) [bootstraplauncher-1.1.2.jar:?] {}

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Render thread
Stacktrace:
	at com.jozufozu.flywheel.core.PartialModel.<init>(PartialModel.java:31) ~[flywheel-forge-1.19.2-0.6.9-18.jar%23849!/:0.6.9-18] {re:mixin,re:classloading,pl:mixin:APP:railways-common.mixins.json:client.AccessorPartialModel,pl:mixin:A}
-- MOD createutilities --
Details:
	Caused by 0: java.lang.ExceptionInInitializerError
		at me.duquee.createutilities.CreateUtilitiesClient.clientInit(CreateUtilitiesClient.java:17) ~[createutilities-0.1.3+1.19.2.jar%23538!/:1.19.2-0.5.1.c-37-0.1.3] {re:classloading}
		at net.minecraftforge.eventbus.EventBus.doCastFilter(EventBus.java:260) ~[eventbus-6.0.3.jar%2385!/:?] {}
		at net.minecraftforge.eventbus.EventBus.lambda$addListener$11(EventBus.java:252) ~[eventbus-6.0.3.jar%2385!/:?] {}
		at net.minecraftforge.eventbus.EventBus.post(EventBus.java:315) ~[eventbus-6.0.3.jar%2385!/:?] {}
		at net.minecraftforge.eventbus.EventBus.post(EventBus.java:296) ~[eventbus-6.0.3.jar%2385!/:?] {}
		at net.minecraftforge.fml.javafmlmod.FMLModContainer.acceptEvent(FMLModContainer.java:107) ~[javafmllanguage-1.19.2-43.2.19.jar%23793!/:?] {}
		at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$10(ModContainer.java:122) ~[fmlcore-1.19.2-43.2.19.jar%23792!/:?] {re:mixin}
		at java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) ~[?:?] {}
		at java.util.concurrent.CompletableFuture$AsyncRun.exec(Unknown Source) ~[?:?] {}
		at java.util.concurrent.ForkJoinTask.doExec(Unknown Source) ~[?:?] {}
		at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) ~[?:?] {}
		at java.util.concurrent.ForkJoinPool.scan(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
		at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
		at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source) ~[?:?] {re:mixin}

	Mod File: /C:/Users/ksarr/AppData/Roaming/com.modrinth.theseus/profiles/Better_MC_Enhanced_1.0.0/mods/createutilities-0.1.3+1.19.2.jar
	Failure message: Create Utilities (createutilities) encountered an error during the sided_setup event phase
		java.lang.ExceptionInInitializerError: null
	Mod Version: 1.19.2-0.5.1.c-37-0.1.3
	Mod Issue URL: NOT PROVIDED
	Exception message: java.lang.RuntimeException: PartialModel 'createutilities:block/void_chest/lid' loaded after ModelEvent.RegisterAdditional
Stacktrace:
	at com.jozufozu.flywheel.core.PartialModel.<init>(PartialModel.java:31) ~[flywheel-forge-1.19.2-0.6.9-18.jar%23849!/:0.6.9-18] {re:mixin,re:classloading,pl:mixin:APP:railways-common.mixins.json:client.AccessorPartialModel,pl:mixin:A}
	at me.duquee.createutilities.blocks.CUPartialsModels.block(CUPartialsModels.java:12) ~[createutilities-0.1.3+1.19.2.jar%23538!/:1.19.2-0.5.1.c-37-0.1.3] {re:classloading}
	at me.duquee.createutilities.blocks.CUPartialsModels.<clinit>(CUPartialsModels.java:9) ~[createutilities-0.1.3+1.19.2.jar%23538!/:1.19.2-0.5.1.c-37-0.1.3] {re:classloading}
	at me.duquee.createutilities.CreateUtilitiesClient.clientInit(CreateUtilitiesClient.java:17) ~[createutilities-0.1.3+1.19.2.jar%23538!/:1.19.2-0.5.1.c-37-0.1.3] {re:classloading}
	at net.minecraftforge.eventbus.EventBus.doCastFilter(EventBus.java:260) ~[eventbus-6.0.3.jar%2385!/:?] {}
	at net.minecraftforge.eventbus.EventBus.lambda$addListener$11(EventBus.java:252) ~[eventbus-6.0.3.jar%2385!/:?] {}
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:315) ~[eventbus-6.0.3.jar%2385!/:?] {}
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:296) ~[eventbus-6.0.3.jar%2385!/:?] {}
	at net.minecraftforge.fml.javafmlmod.FMLModContainer.acceptEvent(FMLModContainer.java:107) ~[javafmllanguage-1.19.2-43.2.19.jar%23793!/:?] {}
	at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$10(ModContainer.java:122) ~[fmlcore-1.19.2-43.2.19.jar%23792!/:?] {re:mixin}
	at java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) ~[?:?] {}
	at java.util.concurrent.CompletableFuture$AsyncRun.exec(Unknown Source) ~[?:?] {}
	at java.util.concurrent.ForkJoinTask.doExec(Unknown Source) ~[?:?] {}
	at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) ~[?:?] {}
	at java.util.concurrent.ForkJoinPool.scan(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
	at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
	at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source) ~[?:?] {re:mixin}

-- System Details --
Details:
	Minecraft Version: 1.19.2
	Minecraft Version ID: 1.19.2
	Operating System: Windows 10 (amd64) version 10.0
	Java Version: <IP_ADDRESS>, Azul Systems, Inc.
	Java VM Version: OpenJDK 64-Bit Server VM (mixed mode, sharing), Azul Systems, Inc.
	Memory:<PHONE_NUMBER> bytes (5203 MiB) /<PHONE_NUMBER>6 bytes (10016 MiB) up to<PHONE_NUMBER>8 bytes (12648 MiB)
	CPUs: 4
	Processor Vendor: AuthenticAMD
	Processor Name: AMD Ryzen 3 1200 Quad-Core Processor
	Identifier: AuthenticAMD Family 23 Model 1 Stepping 1
	Microarchitecture: Zen
	Frequency (GHz): 3.09
	Number of physical packages: 1
	Number of physical CPUs: 4
	Number of logical CPUs: 4
	Graphics card #0 name: NVIDIA GeForce GTX 1650 SUPER
	Graphics card #0 vendor: NVIDIA (0x10de)
	Graphics card #0 VRAM (MB): 4095.00
	Graphics card #0 deviceId: 0x2187
	Graphics card #0 versionInfo: DriverVersion=<IP_ADDRESS>79
	Memory slot #0 capacity (MB): 4096.00
	Memory slot #0 clockSpeed (GHz): 2.67
	Memory slot #0 type: DDR4
	Memory slot #1 capacity (MB): 4096.00
	Memory slot #1 clockSpeed (GHz): 2.67
	Memory slot #1 type: DDR4
	Memory slot #2 capacity (MB): 4096.00
	Memory slot #2 clockSpeed (GHz): 2.67
	Memory slot #2 type: DDR4
	Memory slot #3 capacity (MB): 4096.00
	Memory slot #3 clockSpeed (GHz): 2.67
	Memory slot #3 type: DDR4
	Virtual memory max (MB): 24037.84
	Virtual memory used (MB): 21138.00
	Swap memory total (MB): 7718.52
	Swap memory used (MB): 814.99
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx12648M
	Loaded Shaderpack: ComplementaryShaders_v4.7.1.zip
		Profile: LOW (+5 options changed by user)
	NEC status: Has NEC: INVALID
	ModLauncher: 10.0.8+10.0.8+main.0ef7e830
	ModLauncher launch target: forgeclient
	ModLauncher naming: srg
	ModLauncher services:
		mixin-0.8.5.jar mixin PLUGINSERVICE
		eventbus-6.0.3.jar eventbus PLUGINSERVICE
		fmlloader-1.19.2-43.2.19.jar slf4jfixer PLUGINSERVICE
		fmlloader-1.19.2-43.2.19.jar object_holder_definalize PLUGINSERVICE
		fmlloader-1.19.2-43.2.19.jar runtime_enum_extender PLUGINSERVICE
		fmlloader-1.19.2-43.2.19.jar capability_token_subclass PLUGINSERVICE
		accesstransformers-8.0.4.jar accesstransformer PLUGINSERVICE
		fmlloader-1.19.2-43.2.19.jar runtimedistcleaner PLUGINSERVICE
		modlauncher-10.0.8.jar mixin TRANSFORMATIONSERVICE
		modlauncher-10.0.8.jar fml TRANSFORMATIONSERVICE
	FML Language Providers:
<EMAIL_ADDRESS>		javafml@null
<EMAIL_ADDRESS>		lowcodefml@null

Thanks in advance

Mod List:  		dynamiclightsreforged-1.19.2_v1.4.0.jar           |Rubidium Dynamic Lights       |dynamiclightsreforged         |1.19.2_v1.4.0       |ENQUEUE_IM|Manifest: NOSIGNATURE 		YungsBetterDungeons-1.19.2-Forge-3.2.2.jar        |YUNG's Better Dungeons        |betterdungeons                |1.19.2-Forge-3.2.2  |ENQUEUE_IM|Manifest: NOSIGNATURE 		EasyAnvils-v4.0.11-1.19.2-Forge.jar               |Easy Anvils                   |easyanvils                    |4.0.11              |ENQUEUE_IM|Manifest: 9a:09:85:98:65:c4:8c:11:c5:49:f6:d6:33:23:39:df:8d:b4:ff:92:84:b8:bd:a5:83:9f:ac:7f:2a:d1:4b:6a 		open-parties-and-claims-forge-1.19.2-0.19.1.jar   |Open Parties and Claims       |openpartiesandclaims          |0.19.1              |ENQUEUE_IM|Manifest: NOSIGNATURE 		reeves-furniture-1.19.2-1.4.jar                   |Reeves Furniture              |reevesfurniture               |1.4                 |ENQUEUE_IM|Manifest: NOSIGNATURE 		Public GUI Announcement-forge-1.19.2-4.3.3.jar    |Public GUI Announcement       |publicguiannouncement         |4.3.3               |ENQUEUE_IM|Manifest: NOSIGNATURE 		paragon-forge-3.0.2-1.19x.jar                     |Paragon                       |paragon                       |3.0.2               |ENQUEUE_IM|Manifest: NOSIGNATURE 		Entity_Collision_FPS_Fix-forge-1.19-<IP_ADDRESS>.jar   |Entity Collision FPS Fix      |entitycollisionfpsfix         |<IP_ADDRESS>             |ENQUEUE_IM|Manifest: NOSIGNATURE 		mcw-windows-2.2.0-mc1.19.2forge.jar               |Macaw's Windows               |mcwwindows                    |2.2.0               |ENQUEUE_IM|Manifest: NOSIGNATURE 		stalwart-dungeons-1.19.2-1.2.8.jar                |Stalwart Dungeons             |stalwart_dungeons             |1.2.8               |ENQUEUE_IM|Manifest: NOSIGNATURE 		PureCopperTools-v1.0.0-1.19.2-Forge.jar           |Pure Copper Tools             |purecoppertools               |1.0.0               |ENQUEUE_IM|Manifest: NOSIGNATURE 		rubidium-0.6.2b.jar                               |Rubidium                      |rubidium                      |0.6.2b              |ENQUEUE_IM|Manifest: NOSIGNATURE 		modernfix-forge-5.4.1+mc1.19.2.jar                |ModernFix                     |modernfix                     |5.4.1+mc1.19.2      |ENQUEUE_IM|Manifest: NOSIGNATURE 		VillagersPlus_1.2_(FORGE)_for_1.19.2.jar          |Villagers Plus                |villagersplus                 |1.2                 |ENQUEUE_IM|Manifest: NOSIGNATURE 		YungsApi-1.19.2-Forge-3.8.9.jar                   |YUNG's API                    |yungsapi                      |1.19.2-Forge-3.8.9  |ENQUEUE_IM|Manifest: NOSIGNATURE 		ppastries-croissant.0.jar                         |Create: Precocious Pastries   |ppastries                     |1.0.0               |ENQUEUE_IM|Manifest: NOSIGNATURE 		does_potato_tick-1.19.2-3.6.1.jar                 |Does Potato Tick              |does_potato_tick              |1.19.2-3.6.1        |ENQUEUE_IM|Manifest: NOSIGNATURE 		upgradednetherite_items-1.19.2-<IP_ADDRESS>-release.jar|Upgraded Netherite : Items    |upgradednetherite_items       |1.19.2-<IP_ADDRESS>-relea|ENQUEUE_IM|Manifest: NOSIGNATURE 		clientcrafting-1.19.2-1.6.jar                     |clientcrafting mod            |clientcrafting                |1.19.2-1.6          |ENQUEUE_IM|Manifest: NOSIGNATURE 		ResourcePackOverrides-v4.0.4-1.19.2-Forge.jar     |Resource Pack Overrides       |resourcepackoverrides         |4.0.4               |ENQUEUE_IM|Manifest: 9a:09:85:98:65:c4:8c:11:c5:49:f6:d6:33:23:39:df:8d:b4:ff:92:84:b8:bd:a5:83:9f:ac:7f:2a:d1:4b:6a 		guardvillagers-1.19.2-1.5.6.jar                   |Guard Villagers               |guardvillagers                |1.19.2-1.5.6        |ENQUEUE_IM|Manifest: NOSIGNATURE 		PickUpNotifier-v4.2.4-1.19.2-Forge.jar            |Pick Up Notifier              |pickupnotifier                |4.2.4               |ENQUEUE_IM|Manifest: 9a:09:85:98:65:c4:8c:11:c5:49:f6:d6:33:23:39:df:8d:b4:ff:92:84:b8:bd:a5:83:9f:ac:7f:2a:d1:4b:6a 		balm-forge-1.19.2-4.5.7.jar                       |Balm                          |balm                          |4.5.7               |ENQUEUE_IM|Manifest: NOSIGNATURE 		SnowRealMagic-1.19.2-forge-6.5.3.jar              |Snow!  The problem has been resolved in the latest patch!


dubboctl requirements

Implement dubbo operator to automate installation and updates
Now the types are defined, we need to implement the controller using KubeBuilder. ref: https://istio.io/latest/docs/reference/commands/istioctl/#istioctl-operator
Expose functionalities of dubbo-admin to dubboctl
For scenarios where the browser can not be used, dubboctl can provide a command-line query method.
Dashboard shortcut
Dubboctl should provide shortcuts to open dashboards directly. eg: dubboctl dashboard grafana.
Component validation
Integrate component types and validation logic into each component.
More detailed help information
More user-oriented test cases

/assign


fix: missing & on hourly params

When building the url to call the open-meteo endpoint, if variables other than hourly are provided, the request cannot be performed as the & is missing in the generated URL.
The logic from the other variables is added to the hourly.

Thank you so much for catching that!


Exception in init event doesn't terminate process

Describe the bug

Exceptions raised in init event listeners don't lead locust to exit. This seems odd given that failing initialization code likely leads to subsequent failures that would then mask the initial issue.
Expected behavior

Exceptions in event listeners should, especially init should exit locust. If that is undesirable for some reason, then there should be an "official" way to trigger shutdown by manually try-except wrapping and calling some locust function.
Actual behavior

Exceptions get dumped to console but otherwise don't influence the rest of the execution.
Steps to reproduce

@events.init.add_listener
def on_locust_init(environment, **kwargs):
  # ...some code that raises an exception

Environment

OS: Ubuntu 20.04
Python version: 3.8
Locust version: 2.8.4
Locust command line that you ran: locust
Locust file contents (anonymized if necessary):

I think I agree, an unhandled exception in init should probably exit locust (not the other handlers though). PRs welcome.

I haven't actually found a way to deal with the situation. I've tried having a generic exception in my initialization:
@events.init.add_listener
def on_locust_init(environment, **_kwargs):
    logger.info("locust_on_locust_init")
    try:
        environment.context = Context()
    except Exception as e:
        logger.error("locust_on_locust_init_error", exception=str(e))
        exit(1)

Unfortunately, it continues execution when there are unhandled exceptions.
Does anyone know how it would be possible to handle it?
I don't quite understand why it's behaving like this or how contribute with a solution.

I'm guessing locust catches any exceptions thrown in init? Did you look at the source code?

It seems that this do not happen anymore after update to Python3.10 and use locus v2.32.0


when using 'children' but not 'parent' property in json model for jstree pushing to tree model doesn't update the jstree view

Hi!
When I use json data for jsTree with children but without parent, like this:
{
  id          : "string" // will be autogenerated if omitted
  text        : "string" // node text
  icon        : "string" // string for custom
  state       : {
    opened    : boolean  // is the node open
    disabled  : boolean  // is the node disabled
    selected  : boolean  // is the node selected
  },
  children    : []  // array of strings or objects
  li_attr     : {}  // attributes for the generated LI node
  a_attr      : {}  // attributes for the generated A node
} // note there is no parent property in this json

-- then pushing to ngJsTree's model doesn't rerender jsTree view/ incrementing version will do the trick, but I don't want to rerender whole tree if only one node is added.
I noticed that you use following code to add newly pushed node to the ngjsTree's model:
...
var parent = scope.tree.jstree(true).get_node(node.parent);
var res = scope.tree.jstree(true).create_node(parent, node, 'inside',function() {
...

-- so if node doesn't have parent property(as in my case) node wont' be added/
Using both children and parent at the same time is impossible as jstree prefers parent and ignores children as far as I understand.

will check this week

Thanks!
And one more thing. Your method:
            var getTokens = function () {
                var result = [], token, el;
                if (arraySource) {
                    var array = angular.isFunction(arraySource) ? arraySource() : arraySource;
                    for (var i = 0, n = array.length; i < n; i++) {
                        el = array[i];
                        token = tokenFn(el);
                        map[token] = el;
                        result.push(token);
                    }
                }
                return result;
            };

which is used to watch model changes watches only first-level elements (doesn't take 'children' property into account).

Yes, because in the other syntax (the parent one), all are first level.
From what i saw, there is not create_node function in the jsTree that doesn't require parent node. Looks like to support this data format i will need to change many things, not sure i will have time soon. Sorry, you are welcome to fork and pr :)

ok, got it, thanks for your quick reply :)

+1. would need this.


Error building against musl

I couldn't find a great example on how to compile against musl. Using archlinux (after installing musl and the build deps) I am seeing:
...
  TARGET = Some("x86_64-unknown-linux-musl")
  OPT_LEVEL = Some("z")
  HOST = Some("x86_64-unknown-linux-gnu")
  CC_x86_64-unknown-linux-musl = None
  CC_x86_64_unknown_linux_musl = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_x86_64-unknown-linux-musl = None
  CFLAGS_x86_64_unknown_linux_musl = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
...
  running: "musl-gcc" "-Os" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/generated/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include/generated/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/usr/local/target/x86_64-unknown-linux-musl/release/build/bpf-sys-08ba1431d87e1df6/out/libbpf/src/libbpf.o" "-c" "libbpf/src/libbpf.c"
  cargo:warning=In file included from libbpf/src/libbpf.c:44:
  cargo:warning=libbpf/include/tools/libc_compat.h:11:21: error: static declaration of ‘reallocarray’ follows non-static declaration
  cargo:warning=   11 | static inline void *reallocarray(void *ptr, size_t nmemb, size_t size)
  cargo:warning=      |                     ^~~~~~~~~~~~
  cargo:warning=In file included from libbpf/src/libbpf.c:16:
  cargo:warning=/usr/lib/musl/include/stdlib.h:148:7: note: previous declaration of ‘reallocarray’ was here
  cargo:warning=  148 | void *reallocarray (void *, size_t, size_t);
  cargo:warning=      |       ^~~~~~~~~~~~
  exit code: 1

  --- stderr

  error occurred: Command "musl-gcc" "-Os" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/generated/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/arch/x86/include/" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include/generated/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include/uapi" "-I" "/usr/lib/modules/5.11.8-arch1-1/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/usr/local/target/x86_64-unknown-linux-musl/release/build/bpf-sys-08ba1431d87e1df6/out/libbpf/src/libbpf.o" "-c" "libbpf/src/libbpf.c" with args "musl-gcc" did not execute successfully (status code exit code: 1).

I managed to get this working with Ubuntu. Took a peak at the Ingraind project: https://github.com/andrewrynhard/cosi-demo/blob/initial-implementation/Dockerfile#L8-L20. I would prefer to avoid Ubuntu if I can. In fact, I plan to use redbpf in Talos where we maintain our own C toolchain based on musl. I'd like to understand this a bit before I go and and LLVM and Clang to our toolchain.

It seems that the error is related to libbpf (https://github.com/libbpf/libbpf).
There might exist problems about building libbpf under less common environment.
Or the problem might be fixed in the recent version of libbpf..
But I am not sure because I had no experience of building redbpf using musl yet.
cc. @rsdy

@andrewrynhard Can you send me the full command you're using to build with musl-gcc in Arch? I want to reproduce this before getting to any conclusions. I vaguely remember that the Ubuntu musl-gcc package is specifically not intended to be relied on to compile complex pieces of software, and I don't know if the same is true for Arch.

Ok, just did a quick test, and cargo +stable build --release --target=x86_64-unknown-linux-musl produces the same result. I tried pulling in a new libbpf version, but now I get
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
  running: "musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/" "-I" "/lib/modules/5.10.23-1-lts/build/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/home/p2501/rust/redbpf/target/x86_64-unknown-linux-musl/release/build/bpf-sys-4afc5465d18a986f/out/libbpf/src/bpf.o" "-c" "libbpf/src/bpf.c"
  exit code: 0
  running: "musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/" "-I" "/lib/modules/5.10.23-1-lts/build/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/home/p2501/rust/redbpf/target/x86_64-unknown-linux-musl/release/build/bpf-sys-4afc5465d18a986f/out/libbpf/src/bpf_prog_linfo.o" "-c" "libbpf/src/bpf_prog_linfo.c"
  exit code: 0
  running: "musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/" "-I" "/lib/modules/5.10.23-1-lts/build/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/home/p2501/rust/redbpf/target/x86_64-unknown-linux-musl/release/build/bpf-sys-4afc5465d18a986f/out/libbpf/src/btf.o" "-c" "libbpf/src/btf.c"
  exit code: 0
  running: "musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "libbpf/include/uapi" "-I" "libbpf/include" "-I" "bcc" "-I" "libelf" "-I" "." "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/arch/x86/include/" "-I" "/lib/modules/5.10.23-1-lts/build/include/generated/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include/uapi" "-I" "/lib/modules/5.10.23-1-lts/build/include" "-Wall" "-Wextra" "-Wno-sign-compare" "-Wno-int-conversion" "-Wno-unused-parameter" "-Wno-unused-result" "-Wno-format-truncation" "-Wno-missing-field-initializers" "-include" "bpfsys-musl.h" "-include" "linux/stddef.h" "-DCOMPAT_NEED_REALLOCARRAY=1" "-o" "/home/p2501/rust/redbpf/target/x86_64-unknown-linux-musl/release/build/bpf-sys-4afc5465d18a986f/out/libbpf/src/libbpf.o" "-c" "libbpf/src/libbpf.c"
  cargo:warning=In file included from libbpf/src/libbpf.c:35:
  cargo:warning=/lib/modules/5.10.23-1-lts/build/include/uapi/linux/limits.h:7: warning: "NGROUPS_MAX" redefined
  cargo:warning=    7 | #define NGROUPS_MAX    65536 /* supplemental group IDs are available */
  cargo:warning=      |
  cargo:warning=In file included from libbpf/src/libbpf.c:21:
  cargo:warning=/usr/lib/musl/include/limits.h:48: note: this is the location of the previous definition
  cargo:warning=   48 | #define NGROUPS_MAX 32
  cargo:warning=      |
  cargo:warning=libbpf/src/libbpf.c:49:10: fatal error: zlib.h: No such file or directory
  cargo:warning=   49 | #include <zlib.h>
  cargo:warning=      |          ^~~~~~~~
  cargo:warning=compilation terminated.

So I will need to fix the build env before continuing on this road.

@rsdy I have since moved on to Ubuntu, but let me put together a Dockerfile. I will send once I have it.

I recently ran through a series of issues when trying to build with Ubuntu 18.04. - More info at: https://github.com/redsift/ingraind-build/issues/2
After fixing this as documented on the issue, I've struggled to build as I was receiving a few different type of errors:

Unable to build if no target is defined, producing errors:

Compiling ingraind v1.0.0 (/local)
error: linking with `cc` failed: exit code: 1
...
  = note: /usr/bin/ld: /tmp/rustchLm9DQ/libopenssl_sys-4c5a9937b56b542c.rlib(s23_meth.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE
object; recompile with -fPIC
          /usr/bin/ld: /tmp/rustchLm9DQ/libopenssl_sys-4c5a9937b56b542c.rlib(s23_srvr.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE
object; recompile with -fPIC
          /usr/bin/ld: /tmp/rustchLm9DQ/libopenssl_sys-4c5a9937b56b542c.rlib(s23_clnt.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making
 a PIE object; recompile with -fPIC
          /usr/bin/ld: /tmp/rustchLm9DQ/libopenssl_sys-4c5a9937b56b542c.rlib(s23_lib.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making
a PIE object; recompile with -fPIC
...
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: could not compile `ingraind`
To learn more, run the command again with --verbose.

The only solution was to use --target=x86_64-unknown-linux-musl which got me to the next error:

--target=x86_64-unknown-linux-musl fails due to

error: failed to run custom build command for `redbpf-probes v1.3.0`

Caused by:
  process didn't exit successfully: `/local/target/release/build/redbpf-probes-95c2ccc3902c6de8/build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-changed=include/
  cargo:rerun-if-changed=include/bpf_helper_defs.h
  cargo:rerun-if-changed=include/bpf_helpers.h
  cargo:rerun-if-changed=include/redbpf_helpers.h
  cargo:rerun-if-changed=include/xdp.h

  --- stderr
  /usr/src/linux-headers-4.15.0-142-generic/include/linux/kernel.h:6:10: fatal error: 'stdarg.h' file not found
  /usr/src/linux-headers-4.15.0-142-generic/include/linux/kernel.h:6:10: fatal error: 'stdarg.h' file not found, err: true
  thread 'main' panicked at 'failed to generate bindings: ()', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/redbpf-probes-1.3.0/build.rs:84:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

The solution for this is to set the INCLUDE_PATH before running cargo buld like this:
export C_INCLUDE_PATH=/usr/include/x86_64-linux-musl/
export CPLUS_INCLUDE_PATH=/usr/include/x86_64-linux-musl/

With this, ingraind compiles and works fine, in a few targets, including Amazon Linux 2

@pcolazurdo Thanks for this. I won't have much time to focus on clearing up the build system, but will definitely keep this in mind in a few weeks when I get around to it.


Update source control cheatsheet with one-liner tool installs

Also:

update README with add links to Terra workspaces
use underscores in directory names, fixes https://github.com/DataBiosphere/terra-example-notebooks/issues/38
strip outputs from a few more notebooks

There were no changes to the analysis-of-felis-catus-behavior notebooks other than removing outputs.


Fix three issues when building RPM packages

There are three issues with the current RPM packages generated by make -C tmp package:

The build fails at this step due to an invalid rpath setting:

+ /usr/lib/rpm/check-rpaths
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
*          to fail.
[...]
*******************************************************************************
ERROR   0002: file '/usr/local/lib64/libcedar.so' contains an invalid rpath '/usr/local/lib64' in [/usr/local/lib64]
ERROR   0002: file '/usr/local/lib64/libmayaqua.so' contains an invalid rpath '/usr/local/lib64' in [/usr/local/lib64]

Installation of the generated RPM fails on Fedora because /lib is a symlink to /usr/lib, but it's in the RPM as a directory:

file /lib from install of softether-vpnserver-5.1.9674-1.x86_64 conflicts with file from package filesystem-3.12-2.fc31.x86_64

CMake defaults to installing in /usr/local. This should be /usr. See https://www.tldp.org/HOWTO/HighQuality-Apps-HOWTO/fhs.html and the underlying FHS for further discussion.

A PR for all three of these is coming momentarily.

Upon further research: #1 is a known issue in CPack (see here among many other reports). I'm using a much newer version of CMake, but it appears their "solution" was just to allow you to specify more directories in CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST. I'll make this more comprehensive.
And for #3, /usr/local is correct when doing make install. It's only the RPM that should use /usr.
I'll update and resubmit.

I played a bit with CPack. I found it pretty flexible on one hand. However, we cannot easily use it together with Fedora COPR

Have you tried using CPACK_RPM_PACKAGE_SOURCES to generate a src.rpm? In theory, you should then be able to upload that to COPR. This is a little outside of the scope but I can take a look at that as well.

well, I think at least major RPM distributions (which are served by COPR) would be good to have on yum/dnf level.
it is not that useful to be able to build RPM by people themselves, just because if they build, they can build from source code.

This is how I always do it, incidentally, when installing either the server or client on a new machine. Clone from github, follow the build instructions, but as the last step, do make -C tmp package instead of make -C tmp install. Then install the generated package.
This has SO many advantages. The idea of using make install to put stuff in /usr/local really should have gone out with the '90s.

I understand advantages of using packages :)


Remove unsupported tests and use more complete rised error

[ ] closes #xxxx (Replace xxxx with the Github issue number)
[ ] Tests added and passed if fixing a bug or adding a new feature
[ ] All code checks passed.
[ ] Added type annotations to new arguments/methods/functions.
[ ] Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

@brisvag hey Lorenzo, I think we should merge this in your branch, it will resolve the failing tests


Transfer, instead of mint, tokens

To make the system useable without paying too much gas, the vaults contracxt will be deployed to Arbitrum.
Currently, the HatVaults contract will mint new tokens for rewarding vault share holders.
We cannot, of course, mint new tokens on arbitrum. Instead, we will need to bridge Hats tokens over to abitrum and use those.
The approach here, I guess, is to send hats tokens to the HatVaults contract, and change the the line at https://github.com/hats-finance/hats-contracts/blob/develop/contracts/HATMaster.sol#L143 and instead of minting there, transfer the tokens. We can consider implement on mainnet as well.
(another approach is to change the Arbitrum Hats contract, and implement the mint function as a transfer function. This is a bit riskier, and probably not acceptable as the token will have a different address as well)
The migration path would then be:

Deploy Hats erc20 contract to arbitrum
Change the HatVaults.sol contract, to call transfer instead of mint on https://github.com/hats-finance/hats-contracts/blob/develop/contracts/HATMaster.sol#L143.  (decide if we want to change that on mainnet as well or have two versions, or make it depend on the chainid)
Deploy hatvaults do arbitrum
Send HATs tokens over to the new vault

We decided to do transfer also on main net


Mocking doesn't work properly with ESM modules

Describe the bug
Given the following code:
// index.ts
import child_process from 'child_process';
import util from 'util';

export default function main () {
    child_process.exec('test');
}

// index.test.ts
describe('test', () => {
    it('check', () => {
        vi.mock('child_process');

const mockedExec = vi
      .spyOn(child_process, 'exec')
      .mockImplementation((command, callback) => {
        callback();
      });

exec('test');

expect(mockedExec).toHaveBeenCalledWith('test');
    });
});

Everything in the mocking works fine, and the spy is able to get attached.
However, if we:

Change the first line to import {exec} from 'child_process';
And change the main function to exec('test')

Then mocking fails to get installed. Jest handles this behaviour, but Vitest doesn't.
Reproduction
https://stackblitz.com/edit/node-hgmz55?file=index.test.ts
Note how index.test.ts has two identical tests but for 2 different files.
File works.test.ts works fine, but fails.test.ts doesn't. The only difference is the way the import statement is defined.
System Info
System:
    OS: macOS 12.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Memory: 139.89 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 96.0.4664.110
    Chrome Canary: 99.0.4807.0
    Firefox: 95.0
    Safari: 15.2

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

vi.mock doesn't work with node internals at the moment. Your first test passes because you use vi.spyOn. If you remove vi.mock it will still pass.
Will look into it today.

Turns out it was pretty easy to fix. Will be in the next version by https://github.com/vitest-dev/vitest/commit/9c119ad1e06c0bd635b76b7de18e18ae723d8667

Actually I was wrong! It is already working, but you mock it incorrectly, see https://stackblitz.com/edit/node-ebcpim?file=index.test.ts
You don't need spyOn at all. exec should already be a spy. Does jest works with the same setup? Maybe we have another bug when we put spy on top of another

You're right, it's not required in this simplified example, but in my real world app I want the explicit spyOn in each it() test because I want to have different mocked implementations for that function.

You're right, it's not required in this simplified example, but in my real world app I want the explicit spyOn in each it() test because I want to have different mocked implementations for that function.

It is already a spy, so you can just use vi.mocked(exec).mockImplementation(() => ...)

Hmm. It's not working consistently for me. Even in your attached stackblitz, the first case is failing with:
TypeError: [Function: exec] is not a spy or a call to a spy!
And if I try to do vi.mocked(exec).mockImplementation(() => ...) I get:
__vite_ssr_import_0__.exec.mockImplementation is not a function

I've managed to fix auto mocking for Node builtins, but I'm not sure if behaviour described in issue can be supported.
You see, exec is located on a different object:
import cp from 'child_process'
// exec is on `cp.default.exec`
import { exec } from 'child_process'
// exec is on `cp.exec`

This concept doesn't exist in CJS, so maybe that's why it's supported in Jest.

And if I try to do vi.mocked(exec).mockImplementation(() => ...) I get:
__vite_ssr_import_0__.exec.mockImplementation is not a function

This was a bug, bc automocking didn't work for Node builtins. You can use mock factory for now.

Should be fixed in the latest version. Can you confirm?

Works great now, thank you!

Stumbled upon this issue after a few hours of digging around why my mocking of node:child_process wasn't working, it was the same deal of the import style.
Would be great to have this as a note in the docs somewhere even if it is a bit specific, just as a "have you tried blah"
Working great for me now too :)