Fails to Start

Activity fails to start and this is seen in the logs.
GLib-GIO-ERROR **: 06:16:20.565: Settings schema 'org.laptop.TurtleArtActivity' does not contain a key named 'plugins-list'.

I'm having the same issue, is there any change we could address it?

Yes, please.  org.laptop.TurtleArtActivity.gschema.xml has a key plugins, but not a key plugins-list, so this may be a very simple mistake.

What should be right, changing the schema to plugins-list or changing the TurtleArtActivity.py to plugins ?

I don't know.  I'm just guessing.  Perhaps look at the history of change in those areas, using git blame.

Making the change on TurtleArtActivity.py (plugin-list > plugins) on a running env  allows to start the activity, building to see if anything breaks on a clean install.

So just to check, you were trying to use master rather than the latest release tag v220?  I've just looked through the commits since that release, and there's a good chance there may be other discoveries to make.  What you have found already looks like nobody has been testing.

I don't know. I'm just guessing. Perhaps look at the history of change in those areas, using git blame.

That seems to fix the issue, I'll make a PR and we can review it maybe (not in a sunday) later, thanks for the heads up.

So just to check, you were trying to use master rather than the latest release tag v220?

Checking.... but there is a good chance we are using master.

http://download.sugarlabs.org/sources/sucrose/fructose/ is where releases are made for this source repository.
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer is the release process checklist.

Checking.... but there is a good chance we are using master.

Yep, master :cold_sweat:

@Ark74 said;

Making the change on TurtleArtActivity.py (plugin-list > plugins) on a running env allows to start the activity, building to see if anything breaks on a clean install.

Yes, that is expected and I haven't taken a look to see if that should be the fix and one way to determine that is to see what the expected type of plugins is and if plugins-list is of the same type.

Edit: Well, both master and v220 has the same issue, so should I hold any PR then?

Please make a PR if you have a fix.

I think it will be wise to package releases instead of code from master, that will change our workflow, so we'll need to adjust on that path in the coming release.

Our releases are packaged as @quozl has shared above, and they're packaged from master because that's the branch that's released.

Fixed by #86

Yes, thanks for pointing that out @Ark74. Closing as issue has been fixed.


bpf: on prog dump, allow for replacing map pointers in xlated prog with map ids

Remaining todo for introspection here is that dump can correlate maps which are in the prog, so that maps can be dumped based on their id.

in bpf-next
http://patchwork.ozlabs.org/cover/851446/


Allow at most one file to be specified

It might be reasonable to expect
$ rustfmt src/bin/rustfmt.rs src/lib.rs

to work, but it silently formats only the first argument.

Sorry for peppering with small PRs. I'm now thinking I should file an issue to discuss the UI.

Introducing this could break people's build scripts.
If it's reasonable to expect it to work, why not fix it instead of throwing an error saying this program has a bug. We could change the code in lib.rs to support formatting multiple Cratess.
If it's not expected to work, then we could throw this error although I'm not sure this is a common pattern for CLI interfaces.
@nrc would you like to support multiple files as input?
In any case it should be a rare scenario of someone actually using this on purpose, since rustfmt walks the whole mod tree and formats all files in the project.

Hmm, so I had formerly wanted to match rustc's command line as closely as possible, which means just one file. However, we've been moving away from that over time and I think I'm ready to give up on the idea completely. Which means I think we should be able to accept multiple files as input (unless there is a good reason not to). We should probably open a proper issue, but nevermind.
@marcusklaas, @cassiersg - do either of you have an opinion on taking multiple files?

Sounds like a good idea to me.

I haven't strong opinion in favor/against this. Usually you don't have to invoque rustfmt on a lot of files at a time since it automatically reformats recursively. The only usecase I see might be a situation where recrusive reformating is disabled for whatever reason, and thus be able to format more than one file at a time would be useful (allowing shell wildcards, etc.).

Sounds like processing multiple files is a better way forward here. I filed https://github.com/rust-lang-nursery/rustfmt/issues/580 for that. I'll close this PR.


Only show node projects in web app

Instead of simply showing all repos, we should hide the ones that don't even have a package.json.

Hey @leo,
this indeed sounds like a good idea.
We're hard at work to migrate to GitHub integrations and with it the whole enabling mechanism will slightly change, so that this isn't even necessary anymore. So we'll rather hurry with that and hope to get rid of it, rather than implementing your suggestion now.
Thanks for understanding :)
Best,
Stephan

@boennemann Nice! Thanks for that. 😄


Cargo install fails on the latest version

Current published version is 0.7.0. I tried following:
cargo install cargo-dist

It failed with:
Compiling cargo-dist v0.7.0
error[E0277]: the trait bound `Stdio: From<std::io::Stderr>` is not satisfied
   --> /Users/avi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-dist-0.7.0/src/generic_build.rs:101:20
    |
101 |     command.stdout(std::io::stderr());
    |             ------ ^^^^^^^^^^^^^^^^^ the trait `From<std::io::Stderr>` is not implemented for `Stdio`
    |             |
    |             required by a bound introduced by this call
    |
    = help: the following other types implement trait `From<T>`:
              <Stdio as From<std::fs::File>>
              <Stdio as From<OwnedFd>>
              <Stdio as From<std::process::ChildStdin>>
              <Stdio as From<std::process::ChildStdout>>
              <Stdio as From<std::process::ChildStderr>>
    = note: required for `std::io::Stderr` to implement `Into<Stdio>`
note: required by a bound in `std::process::Command::stdout`
   --> /Users/avi/.rustup/toolchains/1.73.0-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/src/process.rs:898:22
    |
898 |     pub fn stdout<T: Into<Stdio>>(&mut self, cfg: T) -> &mut Command {
    |                      ^^^^^^^^^^^ required by this bound in `Command::stdout`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `cargo-dist` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo-dist v0.7.0`, intermediate artifacts can be found at `/var/folders/8_/j9jcz5793r9ft9fy85ft3jn00000gn/T/cargo-installAtSHae`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

OS: macOS 12.6.7
rustc 1.73.0 (cc66ad468 2023-10-03)

Should ideally be fixed by https://github.com/axodotdev/cargo-dist/pull/693 which introduces a default of fear_no_msrv feature that our prebuilt binaries flip on.

0.7.1 should be easier to install!

works, thank you!


Inquiry about generation and feasibility of tossing motion

Hi Jimmy, very nice work and very "tidy" code! Thanks a lot for sharing it!
I'd like to know the generation and feasibility of the tossing motion. If I understand correctly, the tossing primitive is a trapezoidal motion with hard-coded gripper opening time. How is the motion obtained?
Furthermore, I am curious about the feasibility of the tossing motion. According to the datasheet of Kinova Gen 3, the joint velocity limits are 79.64 °/s for large joints (1-4) and 69.91 °/s for small joints (5-7). However, the maximum velocity of the tossing motion is 140 °/s (as indicated here). Is the joint limit info on Kinova datasheet inaccurate or is there some way to bypass the limit? From the videos, the tossing motion looks much more dynamic than the official limit.

How is the motion obtained?

The trajectory is computed in the trapezoidal_motion_profile function.

According to the datasheet of Kinova Gen 3, the joint velocity limits are 79.64 °/s for large joints (1-4) and 69.91 °/s for small joints (5-7).

Those limits are for the high-level Kortex API (BaseClient).

However, the maximum velocity of the tossing motion is 140 °/s (as indicated here). Is the joint limit info on Kinova datasheet inaccurate or is there some way to bypass the limit?

For tossing, we use the low-level Kortex API (BaseCyclicClient). In low-level, the maximum velocities are roughly 100 °/s for large joints and 150 °/s for small joints (empirically determined). During our toss primitive, joint 1 moves at 35 °/s, joint 3 moves at 85 °/s, and joint 5 moves at 140 °/s.

Sorry for my confusing question, I meant to ask the way to determine the parameters of the trapezoidal_motion_profile, i.e. pos_diff, max_vel, max_accel, max_decel and  joint_position and how the motion is coordinated with gripper_release_ms?
Thanks for pointing out the low-level Kortex API and providing the throwing state info, the tossing motion is much clearer to me.

pos_diff is the difference between the current and desired joint positions. The other values you listed are set such that the arm will toss objects as far as it can.

pos_diff is the difference between the current and desired joint positions. The other values you listed are set such that the arm will toss objects as far as it can.

I see, thanks a lot!


Manage dependencies using Poetry

Description of the change
This pull request moves dependency management to a new pyproject.toml file to be used with Poetry.
Dependencies were cleaned up where possible. Dockerfiles have been edited to use poetry to install dependencies for unit testing. In addition, the production Dockerfiles will now install Turbinia and its dependencies via PyPi instead of setup.py install.
A new GitHub action was added to automatically push new release packages to PyPi containing a wheel and source. This will allow the Cloud Build triggers to use pip install turbinia==$RELEASE_TAG to install the packages. The publish-pypi action will trigger once a new release and tag are published in GitHub.
Applicable issues

fixes #1311

Additional information

Checklist

[ ] All tests were successful.
[ ] Unit tests added.
[ ] Documentation updated.

E2E tests will currently fail because the RELEASE_TAG does not exist yet.

@rbdebeer-zz Please take a look at the approach and let me know your thoughts.

@hacktobeer PTAL at latest changes. I adjusted a few things. Included dockerignore files, using poetry to install dependencies in the containers, updated start.sh scripts, etc.

@jleaniz would love to see this PR reviewed and merged, a lot of the (docker/dev) work moving forward will depend on the new poetry changes and I do not want to merge bigger changes with this big PR.

@jleaniz would love to see this PR reviewed and merged, a lot of the (docker/dev) work moving forward will depend on the new poetry changes and I do not want to merge bigger changes with this big PR.

It's ready for review, please take a look


Multiple calls of wiki command lead to FetchError

Describe the problem you experienced in as much detail as possible:
The bug occurs when the wiki command get called multiple times at the same time.
This leads to an FetchError and will lead to the Discord reply, that there was a problem executing the command.
Include here, how to reproduce the problem / bug:
Calling the wiki command multiple times at the same time.
FetchError: invalid json response body at https://en.wikipedia.org/w/api.php?format=json&action=query&redirects=&prop=extracts&explaintext=&exintro=&titles=Rocket%20League&origin=* reason: Unexpected token < in JSON at position 0
    at D:\Dev\Web-JS\wikipedia-bot\node_modules\node-fetch\lib\index.js:272:32
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  message: 'invalid json response body at https://en.wikipedia.org/w/api.php?format=json&action=query&redirects=&prop=extracts&explaintext=&exintro=&titles=Rocket%20League&origin=* reason: Unexpected token < in JSON at position 0',
  type: 'invalid-json'
}

Possible problem solution:
Inserting a cooldown where the user can execute a command 3-5 seconds after the previous one.
This could also prevent spamming and timeouts because of too many API calls more effeciently.
Details:

OS: All OS affected
Node.js version: 12.14.0
Version: 1.6.1 - developing 1.7

[x] I installed the used the bot according to the contributing guidelines.
[x] I updated every dependecy to its latest release with npm update --save
Branch: dev-1.7
Last commit hash: aaccb3b60d8dc1353414a0ee28396e38a47520aa

It looks like that this error is common when trying to fetch Wikipedia articles as described on this issue https://github.com/dijs/wiki/issues/136

The issue will be marked as closed when the 1.7 update will be released!


Support UI Based Configuration & Devices

I started some work on supporting UI based configuration of this component, and grouping the entities into devices.
Link:  https://github.com/HyperActiveJ/lennoxs30
Feedback appreciated.
Running into merge conflicts due to the pace of development this week.
Tasks:

Support migration from YAML
Support all configuration options including optional
Cleanup

Proposed design for config flow:
Step 1:  Have the user select cloud or local
Step 2:  Direct the user to a cloud or local config specific page.  (e.g. user/pass - cloud page, ip_address - local page, app_id)
Step 3: During validation of the page, attempt to connect using the info provided
Step 4: Allow settings to be configured (scan rates, create sensors, etc.)
After configuration is complete, allow setting in step 4 to be changed.

Going make a release next week.  Looks like we need more time on this and will get it in the next drop?

https://github.com/PeteRager/lennoxs30/releases/tag/v0.2.0


Generate integrity sha384 for script

For the CSP it would be nice if we could generate the sha calculation to create better security of the files that needs to be loaded in javascript. https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity#subresource_integrity_with_the_script_element

Activity

I wanna try working on this and submitting a PR as soon as i'm done with my other PR.
does this rust playground snippet work?
also, it supports sha256, sha384 and sha512 hashes, i think we should implement them all.

ok so i feel like there should be both an opt-in per file and a global option (with per-file opt-out).
<link data-trunk rel="tailwind-css" href="src/tailwind.css" integrity="none"/>
<link data-trunk rel="tailwind-css" href="src/tailwind.css" integrity="sha256"/>
<link data-trunk rel="tailwind-css" href="src/tailwind.css" integrity="sha384"/>
<link data-trunk rel="tailwind-css" href="src/tailwind.css" integrity="sha512"/>

and then a --integrity option to set it globally?
i'll start working on this now as i feel like it's a nice addition, we'll see about naming changes when i'm actually done implementing it.

@adryzz this looks good. Will this also apply for all the js and wasm glue to?

it will, but while i have basic functionality working, i need to make it all clean and working properly without any hacks before i submit the PR

Not stale :)

I will try get this implemented into trunk-ng, as we seem to have a need for this too.

For the WASM and loader script, this is part of the trung-ng branch now: https://github.com/ctron/trunk … I might release this in the next few days with trunk-ng.

@ctron when can we expect a release of trunk-ng?

I just released 0.17.12 which contains this: https://github.com/ctron/trunk/releases/tag/v0.17.12

This got merged with #623 and it should be part of the next trunk release too.

Released with trunk 0.18.0


Add Components analyzer flag to ensure no analyzer duplicates.

Chose the name DisableImplicitComponentAnalyzers (DICA) to not conflict with DisableImplicitAspNetCoreAnalyzers (DIAA). The goal with this flag is that in the SDK we can read its value and do one of the following:

DICA
DIAA
Action

true
true
No component analyzers added from SDK, remove the component analyzers that were added from the package ref

true
false
No component analyzers added from SDK

false
true
No component analyzers added from SDK

false
false
Component analyzers added in SDK

Addresses part of #8825

This looks like what I was expecting to see.


Only release a new official version when merging to "master"

Check on the behavior in the Pulser repo: whether the release happens when merging to master or when adding a tag
Implement same behavior in our repo

I would like to work on it. Please assign it to me.


Update tool description on uploaded and removed file

For the llm to work properly with the tool, it needs context of the current files. This seems little bit hackish, so if you have better approach, let me know!

not sure i fully understand the problem. isn't description already updated every time a file is uploaded?

When the agent is created, it creates the tools (Tool model) by calling Tool.from_function and sets the description, this is then passed to LLM. If I change the description on E2BDataAnalysisTool it won't propagate to Tool, because you have to pass when calling Tool.from_function.
TBH not sure everything we do is the best way, maybe there's better way? Would it be possible to have E2BDataAnalysisTool as superclass of Tool?

@baskaryan Did you have time to look at it?


isGuest() check in controller's action with HttpBearerAuth

Hello!
I'm trying to make one of my actions allowed to both guests and registered users with checking isGuest() inside this action to provide user specific info if user authorised.
But if I use HttpBearerAuth inside behaviours I always get error "You are requesting with an invalid credential." and as you can see I'm unable to use 'except' inside authenticator.
The code looks like this:
public function behaviors()
	{
	    $behaviors = parent::behaviors();
	    $behaviors['authenticator'] = [
	        'class' => HttpBearerAuth::className()
	    ];
	    //Access is not used at all by Yii in this situation...
	    $behaviors['access'] = [
		    'class' => AccessControl::className(),
		    'rules' => [
		        [
		            'allow' => true,
		            'roles' => ['?', '@']
		        ],
		    ],
		];

	    return $behaviors;
	}

The same topic from another user at yiiframework forum:
http://www.yiiframework.com/forum/index.php/topic/67962-api-authenticator-blocking-guest-users/

You should only add the HttpBearerAuth behavior if the user is a guest. If he is already authenticated you do not require additional auth via HttpBearer so you must skip adding the behavior.
You must remove the '?' from AccessControl then.

I want both guests and authenticated users to have access to the same action.
If I do not authorize user with bearer access token on every page I can't use isGuest(), because it returns true even with authenticated users.

Check out #7405


Add config for stale bot

Zuul merged the master, which means your branch is not up to date with upstream/master.
Please, rebase!

Oh, somebody forgot to rebase..;-(

metoo (could have clicked on rebase&merge), sorry


Docker development flow for frontend

My recent changes to our docker images (https://github.com/linkedin/datahub/issues/1760) didn't include changes for frontend. We should add a similar lightweight, easy dev/refresh image for frontend.
@cptran777 Is this something you'd be willing to help me out with? :)

Has this been addressed?

Also, what is the scope of work here?

This has not been addressed. The scope would be making it easier to use the frontend during development with docker; e.g. edit-refresh while using docker. This makes it easy to spin up the entire stack while developing.

We are now managing feature requests through our new portal to improve visibility & prioritize work into our public roadmap. If this request is still relevant, please create a new issue so we can gauge current interest from the Community & prioritize work accordingly.
We'll close out this issue in the meantime. Feel free to reach out to me on DataHub Slack with any questions!


Add Tailwind purge

Purges all unused Tailwind styles
Make sure not to use dynamic styles, like I fixed for the badge component I made. It will not recognize this and purge the styles.
Mentioned in #40

LGTM. Approved and merging.


Find which region the agent is in

Hi,
I have a question about how to get the current room label that the agent is in. I am working on the mp3d datatset. I noticed these two previous issues: #331 and issue in habitat-sim addressing this problem. But I still couldn't make it work.
I wonder if I am doing the right thing.
regions = sim.semantic_annotations().regions
agent_loc = sim.get_agent_state(0).position

''' Check if agent is in region 0 '''
center = region[0].aabb.center
sizes = region[0].aabb.sizes
if center - 1/2 sizes < agent_loc < center + 1/2 sizes, then True

Also, I find the z-axis of regions sizes are all negative in the scene "EU6Fwq7SyZv". This doesn't make sense to me.

I was using a very old version. Now I can get the correct room bounding box. Thank you!


issue5 - removed oauth and use api key

Codecov Report

Merging #6 into develop will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           develop     #6   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files            1      1
  Lines           14     12    -2
======================================
- Hits            14     12    -2

Impacted Files
Coverage Δ

lib/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


@Service我把timeout时间从原来的3秒改到30秒，我发现重启启动服务后没有生效，跟踪源码调试发现服务消费者调用的url里面还是3秒

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.1
Operating System version: linux
Java version: 1.8

Steps to reproduce this issue
@Service我把timeout时间从原来的3秒改到30秒，我发现重启启动服务后没有生效，跟踪源码调试发现服务消费者调用的url里面还是3秒
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
Just put your stack trace here!

请先检查确认注册中心中的数值是否是timeout=30s


Fix resin supervisor disk PV variable

@agherzan @telphan

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Hooks API Reference to spanish

Related to
https://github.com/reactjs/es.reactjs.org/issues/32
Is there is any typos please let me know 👍

Hey @jvelezpo, thanks for your hard work! Welcome to the project! 🎉

Awesome @alejandronanez i am looking forward to keep contributing


Update owners

Updates owners with those that are active in this project 👍
/cc @castrojo

/lgtm

/lgtm


API network error

I am unable to run most keybase commands on MacOS:
$ keybase login
▶ ERROR API network error: Get https://api-0.core.keybaseapi.com/_/api/1.0/merkle/path.json?last=3772402&load_deleted=1&load_reset_chain=1&poll=10&sig_hints_low=0&uid=cdb3958232d90f8e09238099fc65f319: x509: certificate signed by unknown authority (code 1601)

my log id: b26cf6567c21293bb044571c

You behind an evil MITM proxy?

@maxtaco Yes, however we added exceptions for the keybase hosts.

Seems like it didn’t work

@dnoll Do you have the SSL certificates used by the proxies in the System.keychain as "Always Trusted"?
There was a bug a for a while in Go (not sure if it is fixed, https://github.com/golang/go/issues/24652) where it has issues accessing the certificates from System or SystemRoot, one workaround is to toggle the trust to Never Trusted and then back to Always Trusted, this triggers an update of the cert in the keychain which sometimes allows Go to correctly find/use them. Another workaround is to copy the certificate to the login keychain associated with your user and give it full trust there.
Open Keychain Access and navigate to the certificate in question under System and then drag and drop it onto login to initiate the copy, at which point you need to provide sudo capable credentials. Once that is done, double click the certificate to view it, then expand the Trust arrow and give it System-wide Always Trust and you should be able to talk using golang tools like hub without getting this error.
Let me know if this works for you. I'm still looking into who I need to contact about getting Keybase.io and keybaseapi.com on the "nice list", as currently our proxy blackholes it with a bunker buster certificate that pretty much can't be trusted.

I wonder if it would be possible to add some testing around this by using the Python mitmproxy package on Linux/OSX/Windows to simulate having an untrusted certificate on a proxy intercepting traffic. It may even support whitelists/blacklists of domains to access to make the testing more like real life, otherwise some firewall rules could possibly be added for dropping DNS requests/etc to simulate the behaviors people are seeing.


Cannot create connector

As the Microsoft support<EMAIL_ADDRESS>email alias cannot support a site in the DEU German domain then I will reopen this here.
I am trying to follow the tutorial linked here
https://docs.microsoft.com/en-us/microsoftsearch/configure-connector#step-1-add-a-graph-connector-in-the-microsoft-365-admin-center
And when I try to create a new connection I get an error when trying to create the name ‘The request is malformed or incorrect’
example in the attached screenshot.

I am using a dev account which allows up to 12500 items to be indexed.

Adding @anonymous085 to help create this File Share connector

This issue is being followed on the Graph connectors feedback alias. Meet Gupta is tracking it


Levels' repr shows _weight instead of weight

Because of the funny implementation of weighting factors in Levels, the automatically generated __repr__ method produced by dataclasses.dataclass renders levels poorly:
>>> SimpleLevel("hello")
SimpleLevel(name='hello', internal_name='hello75643', _weight=1)

I would prefer for this to be:
>>> SimpleLevel("hello")
SimpleLevel(name='hello', internal_name='hello75643', weight=1)

May need to manually generate a __repr__ method instead of using the default one provided by dataclass.

Actually, internal_name probably shouldn't be shown either, since it's not part of the __init__ signature. Additionally... what is internal_name even for? Probably should remove that entirely and just use object identity in its place.


Build with duneanaobj  v03_05_00

Updated setup script to build with newest version of duneanaobj

I'm able to make , run and the output files seems normal (can be opened, it doesn't complain and it's filled)


ProcessException with message 'Could not determine PID'

The following code:
\Amp\Loop::run(function() {
    $process = new \Amp\Process\Process('diff <(echo 1) <(echo 2)');
    yield $process->start();
    yield $process->join();
});

Raises exception:
Amp\Process\ProcessException: Could not determine PID

vendor/amphp/process/lib/Internal/Posix/Runner.php:54
vendor/amphp/amp/lib/Loop/NativeDriver.php:201
vendor/amphp/amp/lib/Loop/NativeDriver.php:104
vendor/amphp/amp/lib/Loop/Driver.php:138
vendor/amphp/amp/lib/Loop/Driver.php:72
vendor/amphp/amp/lib/Loop.php:95
tests/CsvDiffIteratorTest.php:69

Actual command executed is:
{ (diff <(echo 1) <(echo 2)) <&3 3<&- 3>/dev/null & } 3<&0; trap "" INT TERM QUIT HUP;pid=$!; echo $pid >&3; wait $pid; RC=$?; echo $RC >&3; exit $RC
Executing it in terminal gives:
$ { (diff <(echo 1) <(echo 2)) <&3 3<&- 3>/dev/null & } 3<&0; trap "" INT TERM QUIT HUP;pid=$!; echo $pid >&3; wait $pid; RC=$?; echo $RC >&3
[1] 172
bash: 3: Bad file descriptor
1c1
< 1
---
> 2
[1]+  Exit 1                  ( diff <(echo 1) <(echo 2) ) 0<&3 3>&- 3> /dev/null
bash: 3: Bad file descriptor

diff <(echo 1) <(echo 2) is a shell syntax not supported within the Posix standard, it works in Bash (and ZSH and some other)
/bin/bash -c 'diff <(echo 1) <(echo 2);'
1c1
< 1
---
> 2

but not in posix:
/bin/bash --posix -c 'diff <(echo 1) <(echo 2);'
/bin/bash: -c: line 0: syntax error near unexpected token `('
/bin/bash: -c: line 0: `diff <(echo 1) <(echo 2);'

the bash example only to show how it could be simulated, the actual shell in use is /bin/sh:
/bin/sh -c 'diff <(echo 1) <(echo 2);'
/bin/sh: 1: Syntax error: "(" unexpected

This is equivalent with the long variant:
/bin/sh -c '{ (diff <(echo 1) <(echo 2)) <&3 3<&- 3>/dev/null & } 3<&0; trap "" INT TERM QUIT HUP;pid=$!; echo $pid >&3; wait $pid; RC=$?; echo $RC >&3; exit $RC' 3>&2
/bin/sh: 1: Syntax error: "(" unexpected

As no PID is being output on stream 3, it could not be determined, hence the

Could not determine PID

exception message.
Long description now, but it contains already the solution. Change the command to bash:
\Amp\Loop::run(function() {
    $process = new \Amp\Process\Process('/bin/bash -c "diff <(echo 1) <(echo 2);"');
    yield $process->start();
    yield $process->join();
});


[forest] Update to version 7.0.1

Thanks for the update!
While merging, I tweaked the port to use "vcpkg_from_github()", which enables users to do
vcpkg install forest --head

and get the latest master branch.

Thanks a lot !!!!!!!!!!


go-E & Renault Zoe: Not correctly phase switching phases and using grid power - charge power must not be negative: -374

Describe the bug
With v0.123.2 I was seeing a bunch of charge power must not be negative: -374 errors in the logs so I upgraded to v0.125.0 to see if the issue was resolved there (didn't want to start debugging something that might be resolved already).
After the upgrade I noticed this very weird behaviour that made my Charge power jump all over the place that seems to be related to evcc not switching between phases correctly and instead oscillating the Charge Current between min/max.
It seems that when I have just enough power to do 3p charging (so something around ~4.5kW) the following happens:

As you can see (this is from the associated Influx DB) the Charger starts jumping between -374 charge power and then full 11 kW. Which then immediately causes EVCC to throttle it down again and we're back to -374.
(Don't ask me about the -374 - it's always exactly -374 - also before the v0.125.0 upgrade)
I resolved the oscillation by manually setting the phases to 1p in the EVCC UI at 13:09
This makes the Automatic Phase switching really unusable right now and I am not sure if the car was even charging during the time of the oscillation.
Also notice that it was correctly charging at 3p before and then just randomly started the jump. No idea why - as the PV power was mostly stable before that)

Also the only variation I see in Battery power and Grid Power is then related to evcc starting to go crazy and oscillating between 11kW charging and no-charging.
I did spend some time investigating the logs and the pattern looks like this:
WARN 2024/04/22 13:01:27 charge power must not be negative: -374 start occuring in the logs.
I also see that the PV current starts being all over the place:
DEBUG 2024/04/22 13:01:08 pv charge current: 14.1A = 7A + 7.14A (-4929W @ 3p)
DEBUG 2024/04/22 13:01:17 pv charge current: 7.72A = 14A + -6.28A (4331W @ 3p)
DEBUG 2024/04/22 13:01:28 pv charge current: 14.8A = 7A + 7.84A (-5412W @ 3p)
DEBUG 2024/04/22 13:01:38 pv charge current: 6.44A = 14A + -7.56A (5217W @ 3p)

What happened here was that EVCC started oscillating the max charge current between 6A and 13A on each refresh - all while the phase scale1p in 5m0s keeps getting reset:
Apr 22 13:08:18 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:18 start phase scale1p timer
Apr 22 13:08:18 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:18 phase scale1p in 5m0s
Apr 22 13:08:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:28 phase timer inactive
Apr 22 13:08:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:38 start phase scale1p timer
Apr 22 13:08:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:38 phase scale1p in 5m0s
Apr 22 13:08:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:48 phase timer inactive
Apr 22 13:08:58 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:58 start phase scale1p timer
Apr 22 13:08:58 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:08:58 phase scale1p in 5m0s

(before any confusion as of the config happens - I had the disable: timer set to 5m at the time but removed it since as it didn't change anything. Also the phases were set to "automatic" via the UI - the config has it at 1)
Hope this helps in maybe uncovering an issue - let me know if I can help debug this further.
Switching to 1p manually fixed the issue.
But this should not really be happening.
I'll try downgrading to 0.123.2 now and see if the issue persists.
PS: I know a interval < 30 can lead to issues. But i've been running this setup now for months and never had an issue on 0.123.2 that's why I left the refresh interval at the 10s
Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: raspberrypi.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: XXXX

interval: 10s # control cycle interval

sponsortoken: XXXX

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: false

influx:
  url: http://localhost:8086
  database: evcc_log
  token: XXXX
  org: tigraine

meters:
- type: template
  template: fronius-gen24
  usage: grid
  host: <IP_ADDRESS>
  port: 502
  name: grid1
- type: template
  template: fronius-gen24
  usage: pv
  host: <IP_ADDRESS>
  port: 502
  name: pv2
- type: template
  template: fronius-gen24
  usage: battery
  host: <IP_ADDRESS>
  port: 502
  name: battery3

chargers:
- type: template
  template: go-e-v3
  host: <IP_ADDRESS>
  name: wallbox4

loadpoints:
- title: Garage
  charger: wallbox4
  vehicle: zoe
  mode: pv
  phases: 1
  mincurrent: 6
  maxcurrent: 16

vehicles:
- name: zoe
  title: Renault Zoe
  icon: car
  type: template
  template: offline
  capacity: 50

tariffs:
  grid:
    type: awattar
    region: at # optional, choose at for Austria
    charges: 0 # optional, additional charges per kWh
    tax: 0 # optional, additional tax (0.1 for 10%)
  feedin:
    type: fixed
    price: 0.12
site:
  title: Carport
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3

Log details
Apr 22 13:00:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:07 ----
Apr 22 13:00:07 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:07 charge power: 4616W
Apr 22 13:00:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:07 pv power: 5484W
Apr 22 13:00:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:07 battery soc: 100%
Apr 22 13:00:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:07 battery power: 42W
Apr 22 13:00:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:07 grid meter: -152W
Apr 22 13:00:08 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:08 grid currents: [5.3 -4.84 -4.37]A
Apr 22 13:00:08 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:08 site power: -110W
Apr 22 13:00:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:08 charge currents: [8.06 8.13 8.17]A
Apr 22 13:00:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:08 detected active phases: 3p
Apr 22 13:00:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:08 charge total import: 1717.213kWh
Apr 22 13:00:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:08 charger status: C
Apr 22 13:00:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:08 pv charge current: 9.16A = 9A + 0.159A (-110W @ 3p)
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 ----
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 charge power: 4606W
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 pv power: 5493W
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 battery soc: 100%
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 battery power: -8W
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 grid meter: -193W
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 grid currents: [5.25 -4.79 -4.33]A
Apr 22 13:00:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:17 site power: -200W
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 charge currents: [8.02 8.09 8.17]A
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 detected active phases: 3p
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 charge total import: 1717.226kWh
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 charger status: C
Apr 22 13:00:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:17 pv charge current: 9.29A = 9A + 0.291A (-200W @ 3p)
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 ----
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 charge power: 4615W
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 pv power: 5472W
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 battery soc: 100%
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 battery power: 9W
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 grid meter: -158W
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 grid currents: [5.25 -4.8 -4.33]A
Apr 22 13:00:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:27 site power: -148W
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 charge currents: [8.06 8.09 8.17]A
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 detected active phases: 3p
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 charge total import: 1717.239kWh
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 charger status: C
Apr 22 13:00:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:27 pv charge current: 9.22A = 9A + 0.215A (-148W @ 3p)
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 ----
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 charge power: 4613W
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 pv power: 5334W
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 battery soc: 100%
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 battery power: 72W
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 grid meter: -66W
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 grid currents: [5.26 -4.78 -4.31]A
Apr 22 13:00:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:37 site power: 7W
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 charge currents: [8.02 8.13 8.17]A
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 detected active phases: 3p
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 charge total import: 1717.250kWh
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 charger status: C
Apr 22 13:00:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:37 pv charge current: 8.99A = 9A + -0.00986A (7W @ 3p)
Apr 22 13:00:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:38 max charge current: 8A
Apr 22 13:00:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:47 ----
Apr 22 13:00:47 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:47 charge power: 1533W
Apr 22 13:00:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:47 pv power: 5306W
Apr 22 13:00:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:48 battery soc: 100%
Apr 22 13:00:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:48 battery power: -5W
Apr 22 13:00:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:48 grid meter: -2946W
Apr 22 13:00:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:48 grid currents: [-8.39 -8.42 -8]A
Apr 22 13:00:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:48 site power: -2951W
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 charge currents: [6.92 6.99 7.07]A
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 detected active phases: 3p
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 charge total import: 1717.256kWh
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 charger status: C
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 pv charge current: 12.3A = 8A + 4.28A (-2951W @ 3p)
Apr 22 13:00:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:48 max charge current: 12A
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 ----
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 charge power: 6574W
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 pv power: 5336W
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 battery soc: 100%
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 battery power: 1319W
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 grid meter: 1886W
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 grid currents: [6.06 5.36 4.93]A
Apr 22 13:00:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:00:57 site power: 3205W
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 charge currents: [10.9 10.9 10.9]A
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 detected active phases: 3p
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 charge total import: 1717.270kWh
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 charger status: C
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 available power 3369W < 4140W min 3p threshold
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 start phase scale1p timer
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 phase scale1p in 5m0s
Apr 22 13:00:57 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:57 pv charge current: 7.35A = 12A + -4.65A (3205W @ 3p)
Apr 22 13:00:58 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:00:58 max charge current: 7A
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 ----
Apr 22 13:01:07 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:07 charge power: -373W
Apr 22 13:01:07 raspberrypi evcc[768059]: [lp-1  ] WARN 2024/04/22 13:01:07 charge power must not be negative: -373
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 pv power: 5348W
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 battery soc: 100%
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 battery power: 527W
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 grid meter: -5456W
Apr 22 13:01:07 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:07 grid currents: [-10.6 -10.9 -10.5]A
Apr 22 13:01:08 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:08 site power: -4929W
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 charge currents: [6.54 6.61 6.65]A
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 detected active phases: 3p
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 charge total import: 1717.273kWh
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 charger status: C
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 phase timer inactive
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 pv charge current: 14.1A = 7A + 7.14A (-4929W @ 3p)
Apr 22 13:01:08 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:08 max charge current: 14A
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 ----
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 charge power: 8049W
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 pv power: 5232W
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 battery soc: 100%
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 battery power: 4398W
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 grid meter: -67W
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 grid currents: [6.35 -5.87 -5.44]A
Apr 22 13:01:17 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:17 site power: 4331W
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 charge currents: [13.1 13.2 13.2]A
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 detected active phases: 3p
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 charge total import: 1717.290kWh
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 charger status: C
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 available power 3719W < 4140W min 3p threshold
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 start phase scale1p timer
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 phase scale1p in 5m0s
Apr 22 13:01:17 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:17 pv charge current: 7.72A = 14A + -6.28A (4331W @ 3p)
Apr 22 13:01:18 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:18 max charge current: 7A
Apr 22 13:01:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:27 ----
Apr 22 13:01:27 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:27 charge power: -374W
Apr 22 13:01:27 raspberrypi evcc[768059]: [lp-1  ] WARN 2024/04/22 13:01:27 charge power must not be negative: -374
Apr 22 13:01:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:27 pv power: 5222W
Apr 22 13:01:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:27 battery soc: 100%
Apr 22 13:01:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:27 battery power: -6W
Apr 22 13:01:27 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:27 grid meter: -5406W
Apr 22 13:01:28 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:28 grid currents: [-10.6 -10.8 -10.4]A
Apr 22 13:01:28 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:28 site power: -5412W
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 charge currents: [6.54 6.61 6.61]A
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 detected active phases: 3p
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 charge total import: 1717.293kWh
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 charger status: C
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 phase timer inactive
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 pv charge current: 14.8A = 7A + 7.84A (-5412W @ 3p)
Apr 22 13:01:28 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:28 max charge current: 14A
Apr 22 13:01:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:37 ----
Apr 22 13:01:37 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:37 charge power: 8047W
Apr 22 13:01:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:37 pv power: 5314W
Apr 22 13:01:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:37 battery soc: 100%
Apr 22 13:01:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:37 battery power: 3819W
Apr 22 13:01:37 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:37 grid meter: 1399W
Apr 22 13:01:38 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:38 grid currents: [6.84 6.14 5.72]A
Apr 22 13:01:38 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:38 site power: 5217W
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 charge currents: [13.1 13.2 13.2]A
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 detected active phases: 3p
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 charge total import: 1717.311kWh
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 charger status: C
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 available power 2830W < 4140W min 3p threshold
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 start phase scale1p timer
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 phase scale1p in 5m0s
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 pv charge current: 6.44A = 14A + -7.56A (5217W @ 3p)
Apr 22 13:01:38 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:38 max charge current: 6A
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 ----
Apr 22 13:01:47 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:47 charge power: -372W
Apr 22 13:01:47 raspberrypi evcc[768059]: [lp-1  ] WARN 2024/04/22 13:01:47 charge power must not be negative: -372
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 pv power: 5272W
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 battery soc: 100%
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 battery power: 165W
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 grid meter: -5426W
Apr 22 13:01:47 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:47 grid currents: [-10.6 -10.8 -10.5]A
Apr 22 13:01:48 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:48 site power: -5261W
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 charge currents: [6.54 6.61 6.61]A
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 detected active phases: 3p
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 charge total import: 1717.314kWh
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 charger status: C
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 phase timer inactive
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 pv charge current: 13.6A = 6A + 7.62A (-5261W @ 3p)
Apr 22 13:01:48 raspberrypi evcc[768059]: [lp-1  ] DEBUG 2024/04/22 13:01:48 max charge current: 13A
Apr 22 13:01:57 raspberrypi evcc[768059]: [site  ] DEBUG 2024/04/22 13:01:57 ----

What type of operating system are you running?
Linux
Version
v0.125.0

Negative charge power is a bug in go-E.  https://github.com/evcc-io/evcc/issues/13378
it is fixed in the actual nightly version.
The other problem is ZOE. In 3p it doesn´t like charge current below 8A (older model below 10A).

After the upgrade I noticed this very weird behaviour that made my Charge power jump all over the place

Is there a log from 0.123 that does not have these jumps? Otherwise I'd follow with @VolkerK62 that >8A min current should fix it.

Also the phases were set to "automatic" via the UI - the config has it at 1

I would comment out any settings in yaml, that you are planning to change in UI

Thank you very much for the replies. Good to hear this is fixed already.
Also I didn't know that about the Zoe - thank you for that.
I've now changed the phases to fixed 1p.
Gotta say - been driving the Zoe for 2 years now and the longer you get to live with that car the more it annoys you to no end. (No passenger heating while fast-charging takes the cake though)
Thanks everyone - I'll close the bug.

With the current Renault Kangoo E-Tech I have the same trouble. It will not charge on 3p if the wallbox limits the current below 8A. If the wallbox sets the limit to 8A, the car will start charging with 4kW.

With the current Renault Kangoo E-Tech I have the same trouble. It will not charge on 3p if the wallbox limits the current below 8A. If the wallbox sets the limit to 8A, the car will start charging with 4kW.

This issue has been closed as Go-E bug. Open new issue if problem persists.


chore: default to 0s when unable to detect git hash version during build

During 0.4 release process we've hit a case where we are unable to have auto-detection working, potentially forcing all downstream users to set env vars when building their projects.
Seems like having that git hash version always is not worth the troubles like this for the end users, so let's just default to 0s when all else failed.

Another issue with the self-hosted runner
The self-hosted runner: runner-02-cc lost communication with the server

https://github.com/fedimint/fedimint/actions/runs/9997756499?pr=5692
Restarted the failing jobs

Successfully created backport PR for releases/v0.4:

#5696


Switching Themes breaks view with Slick sliders

Since slick.css is added via Theme facility, switching to a different Theme (e.g. some black one) breaks any view which uses Slick JS library.
Multi-image should be usable regardless of the Theme selected.
Hence, css must be added to website.assets_frontend template directly.

@a0c ,
Thanks for the issue report.


2.3.3 does not build on Arch

Libxml2 version 2.9.1-5. Here is the output from gem install libxml-ruby -v '2.3.3':
http://pastie.org/8512073

Seeing similar errors on CentOS 7. Was there any resolution to this?

I should mention — that's CentOS7, Ruby 1.8.7, libxml-ruby 2.3.3 from "gem install" or "bundle install"

Hopefully this latch patch solves.


Move CI tests to GitHub Actions

Right now Travis CI is not working anymore as we consumed the total quantity of credits we have.
Therefore, we need to move PySD to another CI tool.
I have moved the testing to GitHub Actions. Everything works well, however, coveralls shows a 0% of coverage, nevertheless during testing the coverage achieves the 99%.
I have tried several ways to fix this bug (using coveralls action, a modified version of it, removing my repo from the coveralls.io...)  but anyone worked.
Help is needed to make coveralls work properly soon, otherwise, we will not be able to check the coverage change in new PRs.
@JamesPHoughton

Coverage decreased (-98.5%) to 0.0% when pulling daf2d8f69fa11e7d48e932ac60d1a558fadf6b16 on enekomartinmartinez:GHActions into 36efa5063a679e3c19b78a1172dfa2766532df39 on JamesPHoughton:master.

Hello @enekomartinmartinez! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/integration_test_vensim_pathway.py:

Line 24:80: E501 line too long (87 > 79 characters)
Line 30:80: E501 line too long (81 > 79 characters)
Line 42:80: E501 line too long (103 > 79 characters)
Line 46:80: E501 line too long (99 > 79 characters)
Line 53:80: E501 line too long (85 > 79 characters)
Line 58:80: E501 line too long (97 > 79 characters)
Line 62:80: E501 line too long (93 > 79 characters)
Line 69:80: E501 line too long (92 > 79 characters)
Line 79:80: E501 line too long (95 > 79 characters)
Line 83:80: E501 line too long (101 > 79 characters)
Line 91:80: E501 line too long (82 > 79 characters)
Line 95:80: E501 line too long (105 > 79 characters)
Line 186:80: E501 line too long (82 > 79 characters)
Line 190:80: E501 line too long (80 > 79 characters)
Line 198:80: E501 line too long (81 > 79 characters)
Line 202:80: E501 line too long (93 > 79 characters)
Line 222:80: E501 line too long (101 > 79 characters)
Line 226:80: E501 line too long (93 > 79 characters)
Line 230:80: E501 line too long (87 > 79 characters)
Line 234:80: E501 line too long (103 > 79 characters)
Line 238:80: E501 line too long (93 > 79 characters)
Line 242:80: E501 line too long (101 > 79 characters)
Line 246:80: E501 line too long (91 > 79 characters)
Line 250:80: E501 line too long (103 > 79 characters)
Line 254:80: E501 line too long (95 > 79 characters)
Line 259:80: E501 line too long (83 > 79 characters)
Line 263:80: E501 line too long (81 > 79 characters)
Line 268:80: E501 line too long (109 > 79 characters)
Line 276:80: E501 line too long (91 > 79 characters)
Line 280:80: E501 line too long (89 > 79 characters)
Line 290:80: E501 line too long (107 > 79 characters)
Line 296:80: E501 line too long (99 > 79 characters)
Line 305:80: E501 line too long (87 > 79 characters)
Line 313:80: E501 line too long (91 > 79 characters)
Line 317:80: E501 line too long (99 > 79 characters)
Line 325:80: E501 line too long (87 > 79 characters)
Line 329:80: E501 line too long (97 > 79 characters)
Line 333:80: E501 line too long (97 > 79 characters)
Line 337:80: E501 line too long (97 > 79 characters)
Line 341:80: E501 line too long (97 > 79 characters)
Line 345:80: E501 line too long (119 > 79 characters)
Line 349:80: E501 line too long (117 > 79 characters)
Line 353:80: E501 line too long (101 > 79 characters)
Line 357:80: E501 line too long (105 > 79 characters)
Line 361:80: E501 line too long (87 > 79 characters)
Line 365:80: E501 line too long (82 > 79 characters)
Line 370:80: E501 line too long (103 > 79 characters)
Line 374:80: E501 line too long (144 > 79 characters)
Line 378:80: E501 line too long (168 > 79 characters)
Line 382:80: E501 line too long (134 > 79 characters)
Line 386:80: E501 line too long (133 > 79 characters)
Line 392:80: E501 line too long (111 > 79 characters)
Line 398:80: E501 line too long (111 > 79 characters)
Line 402:80: E501 line too long (107 > 79 characters)
Line 406:80: E501 line too long (92 > 79 characters)
Line 410:80: E501 line too long (105 > 79 characters)
Line 414:80: E501 line too long (96 > 79 characters)
Line 418:80: E501 line too long (108 > 79 characters)
Line 422:80: E501 line too long (92 > 79 characters)
Line 426:80: E501 line too long (105 > 79 characters)
Line 430:80: E501 line too long (107 > 79 characters)
Line 434:80: E501 line too long (95 > 79 characters)
Line 438:80: E501 line too long (93 > 79 characters)
Line 442:80: E501 line too long (107 > 79 characters)
Line 446:80: E501 line too long (99 > 79 characters)
Line 451:80: E501 line too long (95 > 79 characters)
Line 456:80: E501 line too long (93 > 79 characters)
Line 460:80: E501 line too long (91 > 79 characters)
Line 481:80: E501 line too long (89 > 79 characters)
Line 485:80: E501 line too long (90 > 79 characters)
Line 493:80: E501 line too long (90 > 79 characters)
Line 497:80: E501 line too long (85 > 79 characters)

In the file tests/integration_test_xmile_pathway.py:

Line 20:80: E501 line too long (89 > 79 characters)
Line 38:80: E501 line too long (86 > 79 characters)
Line 48:80: E501 line too long (82 > 79 characters)
Line 65:80: E501 line too long (84 > 79 characters)
Line 78:80: E501 line too long (84 > 79 characters)
Line 83:80: E501 line too long (88 > 79 characters)
Line 96:80: E501 line too long (84 > 79 characters)
Line 101:80: E501 line too long (80 > 79 characters)
Line 109:80: E501 line too long (83 > 79 characters)
Line 113:80: E501 line too long (95 > 79 characters)
Line 133:80: E501 line too long (82 > 79 characters)
Line 137:80: E501 line too long (84 > 79 characters)
Line 141:80: E501 line too long (84 > 79 characters)
Line 146:80: E501 line too long (93 > 79 characters)
Line 150:80: E501 line too long (89 > 79 characters)
Line 156:80: E501 line too long (84 > 79 characters)
Line 161:80: E501 line too long (101 > 79 characters)
Line 166:80: E501 line too long (93 > 79 characters)
Line 172:80: E501 line too long (86 > 79 characters)
Line 183:80: E501 line too long (83 > 79 characters)
Line 188:80: E501 line too long (83 > 79 characters)
Line 193:80: E501 line too long (109 > 79 characters)
Line 201:80: E501 line too long (91 > 79 characters)
Line 211:80: E501 line too long (90 > 79 characters)
Line 226:80: E501 line too long (93 > 79 characters)
Line 232:80: E501 line too long (82 > 79 characters)
Line 242:80: E501 line too long (80 > 79 characters)
Line 248:80: E501 line too long (80 > 79 characters)
Line 254:80: E501 line too long (80 > 79 characters)
Line 259:80: E501 line too long (97 > 79 characters)
Line 264:80: E501 line too long (119 > 79 characters)
Line 269:80: E501 line too long (117 > 79 characters)
Line 274:80: E501 line too long (101 > 79 characters)
Line 280:80: E501 line too long (88 > 79 characters)
Line 285:80: E501 line too long (82 > 79 characters)
Line 290:80: E501 line too long (144 > 79 characters)
Line 295:80: E501 line too long (168 > 79 characters)
Line 300:80: E501 line too long (134 > 79 characters)
Line 305:80: E501 line too long (133 > 79 characters)
Line 310:80: E501 line too long (107 > 79 characters)
Line 315:80: E501 line too long (92 > 79 characters)
Line 327:80: E501 line too long (91 > 79 characters)
Line 332:80: E501 line too long (92 > 79 characters)
Line 338:80: E501 line too long (90 > 79 characters)
Line 343:80: E501 line too long (95 > 79 characters)
Line 348:80: E501 line too long (93 > 79 characters)

@JamesPHoughton the issue with coveralls was solved, you can merge this branch if you think is okay. Maybe we can squash the commits when merging to keep the repo cleaner.
Moreover, I update the tests files so we can run the tests from any directory.

Thanks @enekomartinmartinez! Github actions also has a monthly limit on the usage (3000 mins/month), which I believe accrues to me (not to the PR contributor?) so hopefully we'll be below that limit too. If not we'll find another way to make it work.

@enekomartinmartinez, Just saw this: https://github.com/JamesPHoughton/pysd/actions/runs/1113106209

Thanks @enekomartinmartinez! Github actions also has a monthly limit on the usage (3000 mins/month), which I believe accrues to me (not to the PR contributor?) so hopefully we'll be below that limit too. If not we'll find another way to make it work.

HI @JamesPHoughton
I see, during August @rogersamso and I are on vacation, so I suppose we won't consume the time. After that, if we think the time is not enough we can run the tests only with Python 3.7.

Well, currently the tests seem to be running about 7 minutes, so as long as we do fewer than 14 commits/day on avg, we should be good. =)


Error fetching subscriptions - Cannot read property 'getItems' of undefined

Version of react-native-iap
0.3.23
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
RNIap.getSubscriptions should return subscription products
Actual behavior
Error
TypeError: Cannot read property 'getItems' of undefined
    at ios (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:116941:23)
    at Object.getSubscriptions (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:116950:5)
    at InAppPurchaseScreen.componentDidMount$ (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:116821:53)
    at tryCatch (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16271:40)
    at Generator.invoke [as _invoke] (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16459:22)
    at Generator.prototype.(anonymous function) [as next] (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16296:21)
    at tryCatch (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16271:40)
    at invoke (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16329:20)
    at http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:16337:13
    at tryCallOne (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:15627:12)

Tested environment (Emulator? Real Device?)
Emulator
Steps to reproduce the behavior
I merely followed the example from the readme.
  async componentDidMount() {
    try {
      await RNIap.prepare();
      const products = await RNIap.getSubscriptions(itemSkus);
      this.setState({ products });
    } catch(err) {
      console.warn(err); // standardized err.code and err.message available
    }
  }

@phlco  getItems?
Exists these method?
I can see this example in the repo
And you must use a REAL Device to use this npm

Fetching products works in IOS simulator but purchase should be in real device. @phlco it seems react-native-iap module is not linked to your project because you get undefined result in calling the native modules. Please try to link library properly. react-native link or follow the manual guideline.

@dooboolab Yes! Thank you! I skipped the manual installation.


added VS code coverage files

Reasons for making this change:
Automatically ignore VS Enterprise code coverage files.
Links to documentation supporting these rule changes:
https://msdn.microsoft.com/en-us/library/dd537628.aspx#Anchor_1
Mentions of the extensions:

The coverage coloring might be incorrect if the source code has changed since the .coverage file was generated.

(...)

To make results readable as text, choose Export Code Coverage Results. This generates a readable .coveragexml file which you could process with other tools or send easily in mail.

@filipw thanks!


Proposal: Increase headline margin for better readability

Hey there :wave:.
First of all thank you for silverbullet. I am using it for a couple of weeks now and it is a blast!
One thing I noticed is the narrow spacing between headlines and paragraphs, which can make it hard to skim through long pages with lots of text including multiple headlines and paragraphs.

I would like to suggest adding a bit of margin to the top of headings. This gives them "a bit more room to breath" and results in a clearer distinction between sections on a page, e.g.:

I know about the possibility of custom styles, but this might be a general improvement for increasing readability. What do you think? I can also open a PR for this if there is interest in this change.

Sounds good to me, looking forward to a PR!

PR is open and ready to review: https://github.com/silverbulletmd/silverbullet/pull/1039


[BUG] Alert Expression Metrics Not Populating

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Install Rancher v2.4.2
Enable Monitoring
Create New Alert
Select Expression radio button.
Attempt to drop-down the list of metrics.

Result:
Metrics fields are not populating in the drop-down.
Other details that may be helpful:
See attached image
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.2
Installation option (single install/HA): HA/RKE

@maggieliu from discussion with @westlywright this appears to be a UI bug

@codyrancher Can you add the PR for 2.4 release branch to this issue?

https://github.com/rancher/ui/pull/3943

Rancher version master-head (04/28/2020) master-2821-head commit id: 14013a8d0
I was able to select expression, the dropdown gets populated in a second and no errors in the browser devtools console and network.
Rule was successfully added and I was able to also remove it.


Template script error in IE11

Console message:
SCRIPT5009: 'Promise' is undefined
script.min.js (8,826)
(this is at
t=new Promise(function(e,t){try{var n=new Audio,i=n.canPlayType("audio/ogg") ...)
The script error results in navigation menus not working on IE11, so visitors aren't able to get to Provost subpages at www.ndsu.edu/provost/ .

I tested the page on IE11 running on Windows 10, it works fine. When I switch it to  IE10 compatibility mode, I see the error.

Scratch my previous comment, now I do see it.

Fixed with polyfill addition in dc0e496664aac1b79cdb55c4ea45c3432292f346


React invalid hook call

Inputting a  into a grid component of material UI results in an invalid hook call.
Expected Behavior
Expected there to be a simple line graph in the grid with the example data taken from the chartjs github.
Actual Behavior
Error: Invalid hook call
URL, screen shot, or Codepen exhibiting the issue
// material
import { Container, Box, Typography, Grid } from '@mui/material';
import { useState, React } from 'react';
import { makeStyles } from '@mui/styles';
import { Line } from 'react-chartjs-2';
// components
import Page from '../components/Page';
import DropDown from '../components/DropDown';
import DashBox from '../components/DashBox';

// ----------------------------------------------------------------------

const data = {
  labels: ['1', '2', '3', '4', '5', '6'],
  datasets: [
    {
      label: '# of Votes',
      data: [12, 19, 3, 5, 2, 3],
      fill: false,
      backgroundColor: 'rgb(255, 99, 132)',
      borderColor: 'rgba(255, 99, 132, 0.2)'
    }
  ]
};

const options = {
  scales: {
    y: {
      beginAtZero: true
    }
  }
};

// I think after I build it, we can reuse the filters, like in the dashboard, add a new filter depending on what we want to add
// filling in the filters should be a query that returns the options, ie the cohorts can be done via getting the distinct cohorts
export default function Finances() {
  const optionsCohort = ['Cohort One', 'Cohort Two', 'Cohort Three'];
  const optionsDate = ['One', 'Two'];
  const [componentsFinancial, setComponentsMember = useState([
    {
      title: 'Members',
      urlOne: 'http://api/memberone',
      reportOneTitle: 'Count One',
      urlTwo: 'http://api/membertwo',
      reportTwoTitle: 'Count Two'
    }
  ]);

  return (
    <Page title="Finances">
      <Line data={data} options={options} />
      <Container>
        <Typography variant="h4" sx={{ mb: 5 }}>
          Financial Page
        </Typography>
        <Container marginBottom="10px">
          <Typography marginLeft="5px" variant="h5">
            Filters
          </Typography>
          <Grid
            columns={5}
            sx={{
              display: 'flex',
              flexDirection: 'row',
              alignItems: 'stretch',
              marginTop: '10px',
              marginLeft: '5px',
              justifyContent: 'space-evenly'
            }}
          >
            <Grid item sx={{ pr: 5 }}>
              <DropDown options={optionsDate} title="Date" />
            </Grid>
          </Grid>
        </Container>
        <br />
        <Box
          container
          sx={{ border: 2 }}
          marginLeft="20px"
          pr="20px"
          pb="20px"
          pl="20px"
          width="100%"
        >
          <Typography variant="h3">Financial Dashboard</Typography>
          <DashBox components={componentsFinancial} />
        </Box>
        <Grid>
          <Grid item>
            <Typography>Member Count</Typography>
          </Grid>
        </Grid>
      </Container>
    </Page>
  );
}

Steps to Reproduce
See above.
Your Environment

Browser Name and version: Firefox
Operating System and version (desktop or mobile): Windows desktop
React dom and React have the same version number of 17.0.2
Code works before the chart is added
There are some custom items here (ie DashBox)

This should be filed directly on the react-chartjs-2 repo https://github.com/reactchartjs/react-chartjs-2

Thanks! I just left it there, but I'm on mobile and couldn't mark it as a bug.

https://github.com/reactchartjs/react-chartjs-2/issues/875


Show node's role in 'skuba cluster status'

Why is this PR needed?
Does it fix an issue? addresses a business case?skuba cluster status should show if a node is a master or worker (Daimler and T-Systems requested this).
What does this PR do?
Sample output:
 skuba cluster status
** This is an UNTAGGED version and NOT intended for production usage. **
NAME       ROLE     OS-IMAGE                              KERNEL-VERSION           KUBELET-VERSION   CONTAINER-RUNTIME   HAS-UPDATES   HAS-DISRUPTIVE-UPDATES   CAASP-RELEASE-VERSION
master-0   master   SUSE Linux Enterprise Server 15 SP1   4.12.14-197.29-default   v1.16.2           cri-o://1.16.1      yes           no                       <none>
master-1   master   SUSE Linux Enterprise Server 15 SP1   4.12.14-197.29-default   v1.16.2           cri-o://1.16.1      <none>        <none>                   <none>
worker-0   worker   SUSE Linux Enterprise Server 15 SP1   4.12.14-197.29-default   v1.16.2           cri-o://1.16.1      yes           no                       <none>
worker-1   worker   SUSE Linux Enterprise Server 15 SP1   4.12.14-197.29-default   v1.16.2           cri-o://1.16.1      yes           no                       <none>

Anything else a reviewer needs to know?
This is the indication of master node from kubectl get node -o json.
"labels": {
"beta.kubernetes.io/arch": "amd64",
"beta.kubernetes.io/os": "linux",
"kubernetes.io/arch": "amd64",
"kubernetes.io/hostname": "master-0",
"kubernetes.io/os": "linux",
"node-role.kubernetes.io/master": ""
},
In the case of worker nodes, there is no label.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

Do we have a bsc number for this?

Do we have a bsc number for this?

Sorry for being late. We had a holiday on Monday. The number is #1140530: https://bugzilla.suse.com/show_bug.cgi?id=1140530

Thanks. I see this is refered in https://github.com/SUSE/avant-garde/issues/545 which is already closed and in staging. All matches now. :+1:


Hackernews Firebase Client Blocks Forever on StackBlitz

Describe the bug
Summary
It appears that using the Firebase Client to query the HackerNews API on StackBlitz blocks forever.  To demonstrate, I've created the StackBlitz project: https://stackblitz.com/edit/hackernews-firebase-blocked?file=README.md
In the project we attempt to query the Firebase DB in two ways: 1) use the Firebase client and 2) use node-fetch.
There is only a single file: src/firebase.ts.
Fails/Blocks in StackBlitz
Running this project in StackBlitz fails as the Firebase client query does not complete while the direct query does.
Runs Locally
If you run this project on your local computer it will complete as expected with both the Firebase Client query AND the node-fetch query completing with 500 results.
Link to the blitz that caused the error
https://stackblitz.com/edit/hackernews-firebase-blocked?file=README.md
Steps to reproduce

Just load the StackBlitz Project: https://stackblitz.com/edit/hackernews-firebase-blocked?file=README.md
Notice the direct query returns and the firebase query blocks forever

Expected behavior
It is expected that the Firebase Client should return just like it does locally.
StackBlitz Output:
$ ts-node ./src/firebase.ts
started firebase query
started direct query
waiting...
finished direct query 500
waiting...
waiting...
waiting...
waiting...
waiting...
waiting...
waiting...

Local Output:
> ts-node ./src/firebase.ts

started firebase query
started direct query
waiting...
finished direct query 500
finished firebase query 500
waiting...
done!

Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 106
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 222312099,
  "usedJSHeapSize": 214592591,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = dfae8564d35fe429a0bab219bd7d77341f3ec782

Additional context
It appears this stopped working over the last 10 days sometime.  The original project that stopped working was working correctly approximately ten days ago.  Original project: https://stackblitz.com/edit/liveviewjs-hackernews?file=README.md

You mean does Firebase client connect over a websocket?  I don't know for sure but it seems like a reasonable guess considering it can push data changes to connected clients.  Did something change on the StackBlitz side to disallow websocket connections?  You should be able to run this same code "locally" and see it working if that is helpful to answer your question.

Yes, I tried it earlier on local and it does seem to work. Maybe Firebase pushed some changes which broke it on WebContainer. I have to dig deeper on this.

Thanks!  LMK if I can be helpful.


Fixed security bug

Letting the user set the filename is a recipe for disaster.

This was just an emergency fix, i'm not sure if it doesn't break any functionality. Sadly, all other forks of this project still have this bug. Without the fix it is very easy to send "badfile.php" instead of mp3 and put something bad inside.


Enable extending user tsconfig

This resolves issue 6868 by allowing the user to specify a root tsconfig to extend. This is useful for monorepos where the is a base tsconfig file at the root that needs to be extended.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Thank you. extends probably isn't the right name — it should be something tsconfig-specific.
I wonder if a more future-proof approach might be to allow the generated config to be augmented in arbitrary ways? Something like this:
// svelte.config.js
import path from 'path';

export const config = {
  kit: {
    tsconfig: (tsconfig) => {
      tsconfig.extends = path.resolve('../tsconfig.json');
    }
  }
};

Or this:
// svelte.config.js
import path from 'path';

export const config = {
  kit: {
    tsconfig: (tsconfig) => {
      return {
        ...tsconfig,
        extends: path.resolve('../tsconfig.json')
      };
    }
  }
};

I don't know if tsconfig is the best name for the option.

I like the second version of Rich's proposal. I think tsconfig is the right name.

going to close this in favour of #8606 which implements the idea above — thanks!


added ability to configure the size of the macro square

This builds on #399, changing the parameters to short and long axis rather than width and height.  It also adds some basic docs.

Looks great!


GUI crash

Hi, still getting an error when executing the GUI :

Thank you, I can't wait to see it work :)

By chance, do any of the user names contain special characters, or non A-Z letters?
I updated the GUI to attempt to find what type of encoding the user list is using, before cleaning the user list results. I left the option to show a command windows Please try running the GUI again and posting a screenshot of the command prompt, if the error still shows,

No special character to my knowledge :/

It seems to have worked this time, but there are some errors in the command prompt (in french) that might interest you.
Thanks again


blas/gonum/internal/math32: hypot has a flaky test

math32.Hypot uses testing/quick, but the current test as written fails for certain float32 values. For instance
func TestHypot2(t *testing.T) {
	var p float32 = -3.6557444e+37
	var q float32 = 7.9378095e+37
	y := Hypot(p, q)
	if !floats.EqualWithinRel(float64(y), math.Hypot(float64(p), float64(q)), tol) {
		t.Errorf("hypot mismatch")
	}
}

fails.
I'm not sure why this hasn't come up before, but it fails under go1.9beta2.  See https://github.com/golang/go/issues/20809

Yeah, I noticed this the other day.


schedules.delete tries to parse non json response

Current Behavior
When invoking client.schedules.delete({ id: scheduleId }) with an active/valid scheduleId the client throws an exception but also deletes the schedule entry from the system:
invalid json response body at https://qstash.upstash.io/v1/schedules/{scheduleId}
...

Expected Behavior
When invoking client.schedules.delete({ id: scheduleId }) with an active/valid scheduleId the client should not throw an exception.
Example Code
const client = new Client({
  token: "{QSTASH_TOKEN}",
});

await client.schedules.delete({ id: '{scheduleId}' })
// => throws new Error("invalid json response body at https://qstash.upstash.io/v1/schedules/{scheduleId}")

👍 thank you
I'll fix the response on the server and deploy it today

Hey just a heads up:
we discovered a different issue which blocks the deployment right now.
The changes here should be deployed early next week though.


Minor Typos in dataset

In mediasum_factual_eval_dev.csv row 446 and 447, the sent_idx for row 447 is incorrectly written as 1 (there are indeed two sentences in the summary, so the sent_idx should be 1 and 2).

Similarly, typos in mediasum_factual_eval_test.csv, rows 169 and 170.

There is another one in meetingbank_factual_eval_test.csv,  148-151.

Thanks for letting me know, I'll address these typos over the weekend and upload the updated version of the file.

These typos are fixed now and I'll update the repo shortly. Thanks again for pointing out the typos!

 Thanks for the quick response and efforts in fixing the typos!


Progress End / Closing Event

Hi, is there a way to check if progress time ended? I'm trying to use Closing Event but i can't find out the type of closing.
What I want to do is: Every time the progress timer reaches the end, the modal will not close. It will fired Next Event to the next Modal instead (They are from the same gorup).
Thanks

This is what I want perhaps! I will wait for your review and feedback


Fix AMD Dependency

Fix AMD Dependency, add handlebars and medium editor to the factory arguments

Thanks !
Could you please remove dist/* files and template.js too?

Great! We've only recently added AMD support and I've completely forgotten about dependencies there. My bad. Can you also add jquery.fileupload.js and jquery-sortable-min.js?

Could you check it ?


Error when accessing global admin panel as anonymous user

An error is thrown when accessing the global administrator panel when the user is not logged in: Uncaught TypeError: Cannot read property 'length' of undefined

Assigning to myself

Assigning to @bp323 for review

Verified and merged.


Add form HOC.

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          155       155
=========================================
  Hits           155       155

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 55454b3...ab0035d. Read the comment docs.


Crash on gradle task :react-native-sodium:externalNativeBuildRelease

Building on Android is crashing for me in a place I've never had any problems before and I'm stumped about why.
...
:react-native-sodium:externalNativeBuildRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-sodium:externalNativeBuildRelease'.
> java.io.FileNotFoundException: /path/to/app/node_modules/react-native-sodium/android/.externalNativeBuild/cmake/release/mips64/android_gradle_build.json (No such file or directory)

Does anybody have any idea why?

React-Native-Sodium was working correctly in my project before.
But it crash on gradle task: react-native-sodium:externalNativeBuildRelease when I did npm install recently.


How to install by pod for swift3 ??

I cannot install SwiftGif for swift3.
My Podfile is ..
pod 'SwiftGifOrigin', '~> 1.6'

But I get the following error.
Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `SwiftGifOrigin (~> 1.6)` required by `Podfile`
- `SwiftGifOrigin (~> 1.6)` required by `Podfile`

None of your spec sources contain a spec satisfying the dependency: `SwiftGifOrigin (~> 1.6)`.

You have either:
 * out-of-date source repos which you can update with `pod repo update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

I run pod repo update, but I get the same error again.
How can I use SwiftGif??

I have also run into this issue, the way i fixed it was to remove ~.1.6. Then do a pod install then a pod update

Swithcing to 1.5.3 is not a real solution as it is not Swift3. 1.5.3 cannot be build in Xcode8.
Only real solution is wait so that pod autoupdate picks in or the author issues force update.
1.6 is not visible in  cocopods

Hey guys, sorry for the trouble. Will look into it asap 👍

@bahlo looks like this can be fixed by changing the folder "SwiftGifCommon" to "SwiftGifOrigin".

Hi, a Swift3 -compatible pod release coming out soonish?

I'm so sorry guys, I'm drowning in work, will try and fix it this week. 💪

Hey, @bahlo should we wait for a fix in the near future?

Closed via v1.6.1, thank you all for waiting.
BTW: If anyone is interested in becoming a maintainer of SwiftGif, please let me know - I barely find time as you may have noticed

@bahlo Thank You ! now it works.


Azure AD Pod Identity support for Azure Storage Queue

Modified scalers for Azure Storage Queue to support AAD Pod Identity. Added tests for Metadata checks for Azure Storage Queues.
Existing ScaledObjects would work. New metadata added looks like the following:
apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: azure-queue-po-id-scaledobject
  namespace: keda-aad-pod-id
  labels:
    deploymentName: keda-aad-pod-id
spec:
  scaleTargetRef:
    deploymentName: keda-aad-pod-id
  triggers:
  - type: azure-queue
    metadata:
      queueName: keda-test
      accountName: kedastoragequeuetest
      useAAdPodIdentity: "true"
      queueLength: "5"

This is for issue. Might need to make a change to the helm chart so that the identity name (label) can be added to the pods in the keda deployment.

@ahmelsayed removed that file from the latest commit.

I agree with you on the semantics @ahmelsayed 	, I did a suggestion for the spec on the issue - https://github.com/kedacore/keda/issues/161#issuecomment-507229799


Update snapshots for d2d specialization.

For https://github.com/linebender/piet/pull/307.

Double check that the bottom left circle change in 6 is acceptable, the size of all the wedges changes.


Add timeout and clean

This PR does two things:

Adds a timeout helper and adds it to the application layer (probably more places where it can be used...)
Clean up print statements in the stack, now only printing from main

I could probably find some more suitable timeout values... but I guess these will do just fine unless proven otherwise.

Added fixups after HW test. Guess nothing will break now :)


09/09/2018 22:56 : Create Pull Request for branch master -> prTesting1_2018090922

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Question] Is it possible to use it with Beautify

Hi,
I have a question because i'm not sure how your add-on work.
Is your add-on only used to transfer the formatter functionality to php files?
Is it possible to choose formatter that will format my html in php?
I use Beautify by HookyQR to format html files and i would like to use it for mixed html/php files too

Yeah so that would be fine, this plugin only does PHP files and only if you tell it too or you have format on save enabled.


Wine Quality Prediction

💥 Proposal
Wine Quality Prediction using machine learning algorithms

Hey @khusheekapoor  i would love to work on this issue , please assign this to me.

@asthabarwal since we are following the first-come-first-serve policy, we will not be able to assign you this issue. However, you can create another issue and use the same algorithm on a different dataset.

@Soumya-Kushwaha Please give a link for the dataset.

@Soumya-Kushwaha - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


remove an old Go 1.8 test case

Codecov Report

Merging #1694 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1694      +/-   ##
==========================================
- Coverage   87.39%   87.35%   -0.03%
==========================================
  Files          96       96
  Lines        6263     6263
==========================================
- Hits         5473     5471       -2
- Misses        558      560       +2
  Partials      232      232

Impacted Files
Coverage Δ

session.go
73.43% <0%> (-0.32%)
:arrow_down:

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 3d2d45d...ae385e7. Read the comment docs.


No instructions on how to return to menu

If you end up in the situation pictured in the screenshot with the user having exited to the command line there is no obvious command instructions to get back to the menu.

although $raspiblitz command obviously returns perhaps we should create a wiki page with a list of commands for the user to know

you can run ./00mainMenu.sh
that plus the debug command ./XXdebugLogs.sh
are probably the only two you need to know.


How to read json strings in array

I have an problem: i need to extract only json strings from response than contains array of simple objects:
new Response('[{}, {}, {}, ...]')...
// should return generator/stream of '{}', '{}', '{}'

One way to do it would be to parse the JSON values and then stringify them again:
import { parseJsonStream } from "json-stream-es";

const stream = response
	.pipeThrough(new TextDecoderStream())
	.pipeThrough(parseJsonStream([]))
	.pipeThrough(new TransformStream({
		transform: (chunk, controller) => {
			controller.enqueue(JSON.stringify(chunk));
		}
	}));

Another way (I’m not sure if it is more or less performant than the above approach) that would also preserve the formatting of the JSON would be to manually combine the different transformers to split up the stream into single JSON value streams and stringify those again:
import { JsonParser, JsonPathDetector, JsonPathSelector, JsonPathStreamSplitter, streamToString } from "json-stream-es";

const stream = response
	.pipeThrough(new JsonParser())
	.pipeThrough(new JsonPathDetector())
	.pipeThrough(new JsonPathSelector((path) => path.length === 1))
	.pipeThrough(new JsonPathStreamSplitter())
	.pipeThrough(new TransformStream({
		transform: async (chunk, controller) => {
			controller.enqueue(await streamToString(chunk.pipeThrough(new JsonStringifier())));
		}
	});

I haven't tested this code, let me know if something doesn't work.

This solution is very unproductive, 1000 times slower than a regular stream

Which of the two, and compared to what?

Yes, if your data has a unique delimiter (which seems to be a newline in your case), it does not make any sense to use this library. This library parses the whole JSON, which is not necessary for your use case. It would be necessary only if there is no delimiter, so you don’t know where each JSON object ends. The example that you originally posted didn’t have a unique delimiter.

so you don’t know where each JSON object ends

This problem is solved through the stack (For example, the reverse notation of writing an expression https://en.wikipedia.org/wiki/Polish_notation, https://en.wikipedia.org/wiki/Reverse_Polish_notation).
And what does JsonPathDetector do?

so you don’t know where each JSON object ends

This problem is solved through the stack (For example, the reverse notation of writing an expression https://en.wikipedia.org/wiki/Polish_notation, https://en.wikipedia.org/wiki/Reverse_Polish_notation).

I don’t understand what you mean by that.

And what does JsonPathDetector do?

It detects the path of each JSON chunk within the hierarchy of JSON values and is a prerequisite for JsonPathSelector. This is also documented in the README.


Cow: Watch homefix.bh

Cow requests the watch of the watch_keyword homefix\.bh. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

homefix\.bh has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Change world_string to model_string in gz_spawn_model files

🦟 Bug fix
Updates world_string to model_string in some files which were not updated in #605.
cc @caguero
Summary
Updates world_string to model_string in some files which were not updated in #605.
Also changed the description from XML string to XML(SDF) string
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Thanks!


morewaita-icon-theme: init at 42.3

Description of changes
Add MoreWaita, an Adwaita style extra icons theme for Gnome Shell.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Can this PR be merged?

This PR has merge conflicts. I'll try to rebase and force push, but pushing a full year's commits is going to take a long time.

Thanks guys! Really appreciate this!