Atom not opening files

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

[ ] Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
[x] Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
[x] Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
[x] Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
[x] Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
If I open Atom via the GUI I can't open any files or preferences .etc.
Although if I open a file via terminal, atom works as intended even in safe mode.
I have tried running the command atom --clear-window-state
Expected behavior: Open a file
Actual behavior: Atom stays in the same state that it opened in.
Reproduces how often: 100%
Versions
Atom: 1.22.1
Electron: 1.6.15
Chrome: 56.0.2924.87
Node: 7.4.0
OSX: 10.13.1

Thanks for the report - so just to confirm, if you start Atom from terminal not in safe mode like this:
atom

Atom works ok?

If I open Atom via the GUI

How exactly are you opening Atom?  With Spotlight?

Sorry, also:

I can't open any files or preferences .etc.

Does nothing happen when you try to open a file or Settings view or do you get an error?

If I open the app by clicking on it I can't open anything no matter if it is a file or setting .etc.
if I use atom filename.ext it works perfectly and I can open other files too after the app has started via the terminal through file > open or even the tree view.

If I open the app by clicking on it

Where are you clicking on Atom?  From the Applications folder?

Yes the applications folder.

Hmmm, can you share the output of this command?
ls -l `which atom`

Also, did this behavior start after updating to 1.22.1?  Or was it a fresh install of Atom?

The output is: lrwxr-xr-x  1 Jbonnett  admin  53 18 May  2017 /usr/local/bin/atom -> /Applications/Atom.app/Contents/Resources/app/atom.sh.
As to when it started I couldn't tell you as it was a while back.

Not sure what's going on - can you go ahead and download the .zip install from https://atom.io and re-install?   Just choose "Replace" when dragging the unzipped Atom application to your Applications folder.

I am having the same exact issue.
lrwxr-xr-x  1 peterugh  admin  53 Dec  2  2016 /usr/local/bin/atom -> /Applications/Atom.app/Contents/Resources/app/atom.sh
Downloaded the zip and re-installed.

I've already tried that. I didn't work after a while.

I have had same problem, coudn't open any file. In console were no errors. But after 5-10 minutes in console showed up 'All dependencies installed, good to go' and problem was fixed.
Atom: 1.34.0/ Ubuntu

I would like to add that i am dealing with the same problem on 1.36/ 18.04. No solution found yet. Good luck to all that attempt to find problems.

Got the same issue. "Fixed" the same way as previous person. Find the root of evil in my case.
First time issue:
At startup I had ~15 opened files and I could open one more file from tree-view. And not any more. I could also switch between tabs by clicking on proper files at tree-view.
After some atom and PC restarts I lost the ability to open new files at all. I tried to open file from tree-view's right-click menu "Split up [Ctrl+K Up]". And I got new blank area without the actual file or even empty new file. After restarting atom this area disappeared and my previously opened files' editor view took all availiable space.
After I have launched atom from command line with shallow atom I could open any file I want. It also returned control of command line immediately after launching. So I can not say if there was any "All dependencies installed, good to go" message. I have not tried other commands like atom --safe, etc. as shallow command worked for me. I could open atom from application menu without this issue.
--- Temporary fix: open atom from termimal.
Second time issue:
I restarted PC and lauched atom through application menu. I got presented with popup window above atom "Unlock Login Keyring" from "gnome-keyring" package. After I closed it I quickly opened another file. And got stuck again with no possibility to open other files. So I removed this package and packages that require it:
gnome-keyring
|---xdg-desktop-portal-gtk
....|---xdg-desktop-portal
........|---flatpak
............|---flatpak-builder
............|...|---gnome-builder
............|---malcontent
................|---gnome-software
I used gnome with gdm at past but now I use xfce4 with lightdm.
After doing so I restarted PC and so far so good. There have been no problems with atom.
--- Final fix in my case: remove "gnome-keyring" package and packages that require it.
Atom: 1.45.0
Electron: 4.2.12
Chrome: 69.0.3497.128
Node: 10.11.0
OS: Linux 5.5.13-arch2-1

My workaround was to disable all "Github" related package (github, open-on-github) in Atom preferences.
This might be related to Atom trying to "unlock the keyring" but failing to show the appropriate dialog. Unlocking the keyring to do some Github (not Git) -related stuff is a rather braindead feature anyway IMO.


docs(two-column-layout-example): add products plugin

This PR adds the products plugin to the Autocomplete two columns layout example.
Main PR: #908

Another UI comment: I'm not a big fan of the color and styles for the star rating system, I find the blue a bit too "system" and it overpowers the rest.
Here's a suggestion, wdyt? These are the colors we use for the star rating system on the docs' solutions.

Thanks for your comments! 🙏

I've noticed a few things in the UI:

The title "Products" is very discreet. Why not use the header template from the theme?

It should be better like this. I removed the line at the end because the title is using a white background, conflicting with the background color on all products added by the smart preview feature.
I'll see how to handle this specific case in the relevant PR.

When there are less than 3 products, they fill the space, meaning they grow in height too. Couldn't we instead keep them at the same size?

Indeed, thanks!

When images are loading, the space isn't "reserved" so there's layout shift. Also, with the blurhash we likely have three possible states: empty image, blurred image and crisp image instead of going from not loaded to loaded. Do we think it's good UX?

When the image wasn't loaded, the body part was taking all the available height, hiding the Blurhash canvas. Now it should work properly. The blur placeholder is not an image, so it should be visible as the same time as the results.
I added a timeout + network throttling to see the states in the below video.
https://user-images.githubusercontent.com/662153/157309965-46c01d13-f23d-408a-8c03-7603429c891c.mov

When resizing the browser (large to narrow) there's a moment when the panel has a weird width (while resizing). It's particularly visible on Firefox. Is this caused by the custom CSS, or was it already there?

I think it is due to media queries that update the max-width of the container, I removed them, can you try again?

Another UI comment: I'm not a big fan of the color and styles for the star rating system, I find the blue a bit too "system" and it overpowers the rest.
Here's a suggestion, wdyt? These are the colors we use for the star rating system on the docs' solutions. I also reduced the descriptive text and used a more muted color.

It's looking much better, thank you (and using one less SVG)!

Can we add a "See all products (x)" as done in the "[Desktop] Multi category results" view in the Ecom UI Design Kit?

Same for the "See all" displayed next to the articles

Could we add some debouncing so it reduces this flickering effect, while keeping it on the left items composed of the QuerySuggestions. So this way the end users can better focus on the left part, before focusing on the right part later on.

Could we work on adding the highlighting on the product hits?


Results table doesn't show cumulative error #

The results table shows the total n° of pages containing a Success criterion failure, but the n° of errors next to it is always the n° of errors ont he first page that fails the criterion, no the cumulative total.

Should be fixed now

Indeed it is


Fix yaws_api:url_encode/1 to handle unicode chars

This PR makes it possible for Yaws to serve a directory tree that may contain non-latin1 chars in dir/file names. Please review. Thanks.

Looks like all the Travis tests failed, so please investigate the failures and amend your commit with a fix.
Also, are there any existing tests that cover these changes? If not, please add test(s). You can try adding unit tests under test/eunit if the functionality can be exercised from there, otherwise we'll need to figure out one of the test/t* directories to put new tests in.

I can't seem to get enough info from the log to see where the issue is. Trying to run the tests locally without this PR also fails here. This is what make check in test/ gives me on OSX with Erlang 18.3.1:
Making check in src
make[1]: Nothing to be done for `check'.
Making check in eunit
/Applications/Xcode.app/Contents/Developer/usr/bin/make  check-local

 ==== EUNIT TESTS ====

  ERLC     multipart_post_parsing.beam
  ERLC     yaws_session_server_test.beam
  ERLC     ehtml_test.beam
  ERLC     cookies.beam
  ERLC     headers.beam
  ERLC     ipmask.beam
  ERLC     gconf.beam
  ERLC     sconf.beam
  ERLC     yaws_rpc_test.beam
  ERLC     proc_cleanup.beam
  ERLC     subconfig.beam
  ERLC     copy_error_log.beam
  ERLC     dynopts.beam
  GEN      ../../test/bin/yaws
Running multipart_post_parsing
  All 13 tests passed.
Running yaws_session_server_test
yaws_session_server_test: new_session_and_list_test...*failed*
in function yaws_session_server_test:new_session_and_list_test/0 (yaws_session_server_test.erl, line 39)
<EMAIL_ADDRESS>  output:<<"">>

yaws_session_server_test: replace_session_test...*failed*
in function yaws_session_server_test:replace_session_test/0 (yaws_session_server_test.erl, line 46)
**error:{badmatch,{error,{already_started,<0.47.0>}}}
  output:<<"">>

yaws_session_server_test: replace_session_cleanup_test...*failed*
in function yaws_session_server_test:replace_session_cleanup_test/0 (yaws_session_server_test.erl, line 64)
**error:{badmatch,{error,{already_started,<0.47.0>}}}
  output:<<"">>

yaws_session_server_test: cookieval_to_opaque_test...*failed*
in function yaws_session_server_test:cookieval_to_opaque_test/0 (yaws_session_server_test.erl, line 86)
**error:{badmatch,{error,{already_started,<0.47.0>}}}
  output:<<"">>

yaws_session_server_test: delete_session_test...*failed*
in function yaws_session_server_test:delete_session_test/0 (yaws_session_server_test.erl, line 98)
**error:{badmatch,{error,{already_started,<0.47.0>}}}
  output:<<"">>

yaws_session_server_test: timeout_test...*failed*
in function yaws_session_server_test:timeout_test/0 (yaws_session_server_test.erl, line 114)
**error:{badmatch,{error,{already_started,<0.47.0>}}}
  output:<<"">>

=======================================================
  Failed: 6.  Skipped: 0.  Passed: 1.
make[2]: *** [yaws_session_server_test] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

I restarted the build that fails on Travis, and it works. There is definitely an issue with Travis.
Beside that, the error you observe locally is different. For an unknown reason, in the test t12, instead of having 'nonode@nohost' as node name, you have<EMAIL_ADDRESS>This is unexpected.

@capflam,
Many thanks. I set the node to<EMAIL_ADDRESS>in ~/.erlang. I guess that is what was wrong.
BTW, is the design of yaws_api:url_encode/1 flawed i.e. it encodes : to : and / to /? In the PR I keep the same behaviour.
Thanks.

@leoliu: if : and / are not encoded, that's a bug. I'm taking your PR to a local branch and will amend your commit with a fix and test for this.

OK, trying to fix the : and / encoding problem is way more involved than I thought, so I'm going to keep your behavior for them for now.

Conflicts resolved and fixes pushed. Thanks @leoliu !

@vinoski thanks for working on it.


docs: show extended values through the component reference

Clear and concise description of the problem
In situations where components extend the values of other components, there needs to be an extension to the component reference.
I believe something like (BAvatar example)

BAvatar props

badge
default: false
badge desc

Omit<BLinkProps, 'event' | 'routerTag'>

variant
'secondary' (Not a BLink default)
(desc taken automatically from BLink)

active
undefined -- (default taken from BLink)
(desc taken automatically from BLink)

Suggested solution
n
Alternative
n
Additional context
n
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

related: https://github.com/bootstrap-vue-next/bootstrap-vue-next/pull/1580#discussion_r1389474061


[Bug]: toNextClosingBracket is broken

Bug Description
Looks like toNextClosingBracket is broken after this commit:
https://github.com/chrisgrieser/nvim-various-textobjs/commit/7cef84c275d191406e99e0aade866e77702df4c8
Tested in lazy using the previous commit SHA and it works as expected:
{
	'chrisgrieser/nvim-various-textobjs',
	commit = 'b0ec67f8d06f03b5e84aa90eac96f6153100c963',
}

Relevant Screenshot
No response
To Reproduce

Go to starting bracket
Go to next using %

Actual Result: Doesn't jump to next closing bracket
neovim version
NVIM v0.10.0-dev-2647+g62b7b1daf-Homebrew
Build type: Release
LuaJIT 2.1.0-beta3

Make sure you have done the following

[X] I have updated to the latest version of the plugin.

Hmm, I cannot reproduce the issue, d% and other variants all work fine for me. Also, the commit you linked only changes a linting rule, so it cannot have broken anything.
Could you double check that the issue is not due to some conflicting keybinding or something on your end?

Ahh, I see what I missed. It seems to break with lazy when passing in keymaps (to inform lazy when to lazy-load the plugin) in the plugin spec.
It breaks consistently for me in visual mode.
(what I meant in my original message was that the issue is non-existent on https://github.com/chrisgrieser/nvim-various-textobjs/commit/b0ec67f8d06f03b5e84aa90eac96f6153100c963 and is reproducible on https://github.com/chrisgrieser/nvim-various-textobjs/commit/7cef84c275d191406e99e0aade866e77702df4c8.)
Very weird, but managed to fix this by removing the keys and simply passed lazy: true.

Very weird, but managed to fix this by removing the keys and simply passed lazy: true.

yep, when you add lazy: true, lazy will automatically load the plugin as soon as it is required by one of the keymaps. 🙂


sic-image-cli: 0.22.3 -> 0.22.4

Diff: https://github.com/foresterre/sic/compare/v0.22.3...v0.22.4
Changelog: https://github.com/foresterre/sic/blob/v0.22.4/CHANGELOG.md
Description of changes

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.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 255559 run on x86_64-linux 1

1 package built:

sic-image-cli


Call to an undefined method Illuminate\Database\Query\Builder::orWhereHas().

Larastan Version: v0.3.15
--level used: 2

Description
51     Call to an undefined method Illuminate\Database\Query\Builder::orWhereHas().
on the line with the -->
In the api description the method does exist.
I think this is a false positive.
Strange thing this actually is line 56
this also creates an issue on the same line
51     Method Illuminate\Database\Query\Builder::dynamicWhere() invoked with 2 parameters, 1 required.
Laravel code where the issue was found

        $duties = new Duty();
        $duties = $duties->sortable();

        // Apply search
        if ($request->filled('search')) {
            $search = '%' . $request->get('search') . '%';
51          $duties->whereHas(
                'customer',
                function ($query) use ($search) {
                    $query->where('company_name', 'LIKE', $search);
                }
56 -->      )->orWhereHas(
                'type',
                function ($query) use ($search) {
                    $query->where('title', 'LIKE', $search);
                }

Thank you.
We have other Eloquent false positives.

I get this error when wrapping orWhereHas() inside of whereNested(), but it works fine wrapped inside of where()

Can you test this with the latest changes in master branch?

works


Revert "Fix flaky test StreamingDataflowWorkerTest"

Reverts apache/beam#28173
The enabled test has been flaky on both Jenkins and actions. e,g, https://ci-beam.apache.org/job/beam_PreCommit_Java_Cron/7319/testReport/junit/org.apache.beam.runners.dataflow.worker/StreamingDataflowWorkerTest/testMaxThreadMetric_0___streamingEngine_false__/
Stacktrace
java.lang.AssertionError: expected:<1000> but was:<0>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:633)
	at org.apache.beam.runners.dataflow.worker.StreamingDataflowWorkerTest.testMaxThreadMetric(StreamingDataflowWorkerTest.java:2935)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

R: @tvalentyn
CC: @olalamichelle thanks willing to dig into this in the original PR. The branch hash is stay so we can always come back and investigate. For now I would propose this change to de-noise purpose

LGTM, thanks. Sorry about the noise it caused.

Ironically the PreCommit GitHub Action still fails this test even it's reverted in this PR: https://github.com/apache/beam/actions/runs/6174695355/job/16759856184?pr=28434


Can you tag a release?

The current tagged version is rather old.

Sure thing!
v0.3.0: https://github.com/muesli/smartcrop/releases/tag/v0.3.0


error: unknown option '--template'

🐛 Bug Report
When running react-native init App --template typescript I get "error: unknown option --template"
To Reproduce
react-native init App --template typescript
Expected Behavior
All the documentation I've seen implies this should work out of the box. Every example I've seen only mentions installing react-native-cli, which I have.
Code Example
react-native init App --template typescript
OUTPUT:
Scanning folders for symlinks in C:\Users\ajohn\Desktop\node_dev\hippo\client\node_modules (75ms)
error: unknown option `--template'
Environment
Environment:
OS: Windows 10
Node: 10.12.0
Yarn: 1.15.2
npm: 6.9.0
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found
Packages: (wanted => installed)
react: ^16.8.6 => 16.8.6
react-native: ^0.55.4 => 0.55.4

This may be better raised in https://github.com/react-native-community/react-native-cli
I would recommend checking you have the latest version of the cli installed as well: https://blog.callstack.io/the-react-native-cli-has-a-new-home-79b63838f0e6


Fixes more #1241

I haven't ready function when i use polymer-micro.html
I think, it's better to use attached function, because it is basic lifecycle callbacks.

My CLA has been submitted.

@sorvell or @kevinpschaaf should probably review this one.

In PRIMER.md:274 also wrong example. Need change to attached:

I don't want include https://github.com/Pofigizm/polymer/commit/7d2398888f4d6049d59d82931cf678f8636d7317 to this PR. I don't understand why it came here.


Allow Data Receiver to handle headers of length 0 and continue

ref #

@aturley updated, let me know if that's sufficient

@JONBRWN yup, that looks good, thank you.


Feature: Additional example - the internet

This is to track an example we're thinking to add as part of becoming familiar with Goose.
In general we think you can never have too many examples, and if they become difficult to update that is a sign "Something is rotten in the state of Denmark", but not everyone shares that view....

PRs adding useful examples are definitely welcome. I also intend to set up a secondary repository which is more a cookbook of common patterns and helpers when writing Goose load tests.

Closing per remark in PR


Add doctests to CI

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] Package installs: julia> ]dev .
[ ] All tests pass: julia> ]test ChaoticEncryption
[ ] The documentation builds: $ cd docs and then $ julia make.jl

Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Acknowledgements
This Pull Request template was taken from the excellent PyBaMM repository.

Hmmmm, now that I think of it, this PR is not required. The current Documentation CI does the exact same thing.


[OSPRH-9252] Support for ephemeral metric storage

I had to switch the "Persistent" field in storage to pointer, so I can set it to nil in the webhook. Otherwise it would always appear in the applied CR when running the operator with webhooks, so it would be there even when strategy=ephemeral, which we don't want. I also uncommented the ScrapeInterval line in pkg/monitoring stack. The OBO version we're using now allows us to use it.

/lgtm

/cherry-pick 18.0.0-proposed


[py2py3] Migration at level scr/python/A/B/C - slice 25

Fixes #10149
Status
Ready
Related PRs

Previous migration PR: #10371  (slice5, issue #10148 )
Next migration PR: not open yet (slice7, issue #10150  )

Description
Run futurize and some manual changes on the first batch of src/python/A/B/C.
Strings:

src/python/WMCore/ReqMgr/Web/*: a ton of changes. need to be validated!

such as kwds[str(key)] = str(val)
or also:from builtins import str as newstr, bytes,
...
def toString(data):
if isinstance(data, (newstr, bytes)):
    return str(data)  # native-string approach

tracked in #10382

Is it backward compatible (if not, which system it affects?)
It should be. (Any possible cause for errors will we reported here)
External dependencies / deployment changes
Requires python-future in both py2 and py3 environments.

Perfect, thank you very much, Alan!

Very basic checks of the ReqMgr2 GUI do not show anything abnormal. Thanks Dario.


Make pkg.json#main a .js file

JavaScript ecosystem strikes again 🤦 Explained here: https://github.com/emotion-js/emotion/issues/2103#issuecomment-727207340
I will understand if you don't want to merge this but it would make my life easier if this could be released as people wouldn't be hurt by the ecosystem tooling quirks and I wouldn't have to explain this 😢

Would the reason that we changed this in the first place surface as an issue again?
https://github.com/thysultan/stylis.js/pull/207#discussion_r409460723

Would the reason that we changed this in the first place surface as an issue again?

Not as far as I can tell - .cjs has to be used because this is type: "module" package but it only has to be used within pkg.json#exports and this has been left untouched. This only affects pkg.json#main which should be ignored by any pkg.json#exports/pkg.json#type-aware tool.

In that case this looks good to merge.

Thanks! The only thing left to do is a new release then :)


SetAnimationByName does not work

I have put one NPC inside interior. When I enter the interior, the animation is not synced!
public FCNPC_OnSpawn( npcid )
{
    FCNPC_ApplyAnimation( npcid, "GANGS", "null", 0.0, 0, 0, 0, 0, 0 ); // preload
    FCNPC_ApplyAnimation( npcid, "GANGS", "leanIDLE", 3.0, 0, 1, 1, 1, 0 );
    FCNPC_SetAnimationByName( npcid, "GANGS:leanIDLE", 3.0, 0, 1, 1, 1, 0 );
    return 1;
}

Here's my code. Cheers.

Preloading animations is for the person viewing the animation, not the person doing the animation.
No matter what, if an animation is applied to a player/NPC, that player/NPC tells the server it's doing an animation. If any players are around, the server tells them too. When players are told about other players/NPCs doing animation it's played for them on their end. If they don't have it preloaded on THEIR end then it might not play.
Basically... preloading animations for NPC's is 100% pointless because they are not going to see the animation.

Pointless or not, the issue is not addressed.
On Dec 24, 2016 5:32 AM, "Corey Iles"<EMAIL_ADDRESS>wrote:

Preloading animations is for the person viewing the animation, not the
person doing the animation.
No matter what, if an animation is applied to a player/NPC, that
player/NPC tells the server it's doing an animation. If any players are
around, the server tells them too. When players are told about other
players/NPCs doing animation it's played for them on their end. If they
don't have it preloaded on THEIR end then it might not play.
Basically... preloading animations for NPC's is 100% pointless because
they are not going to see the animation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ziggi/FCNPC/issues/32#issuecomment-269029026, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD5UmxB5vdjwJB-sGfMEfRhQiv9LYPSIks5rLBO2gaJpZM4LUvnm
.

The issue is not addressed?

Not the NPC.

Fixed.


Replace the motherboard and PSU

Finding out my power supply was not good. It was 💩 actually. Got a new motherboard for better performance and PSU to upgrade.

Completed upgrade on 10/2/2022.


[feature]: further test coverage for manual fee rates and fee rate estimation

Continuation of work from https://github.com/lightninglabs/taproot-assets/pull/595 , being implemented in https://github.com/lightninglabs/taproot-assets/pull/605 .

[ ] change units for manual fees to sat/vB to better match LND etc.
[ ] test negative cases for manual fees below the minimum fee, exceeding wallet funds
[ ] negative cases for fee estimation exceeding wallet funds or excessively low estimate
[ ] increase logging of fees used and TX weights
[ ] investigate mis-adjustment of final absolute fees for anchor TXs for minting and transfers

Closed with #605.


Add page decoding test for large message …

…with no persistence
(cherry picked from commit aba9384139956aaf37bde4fc881c7a0e27bbcf32)
Test change port from downstream https://github.com/rh-messaging/jboss-activemq-artemis/pull/276
This just make sure problem described in https://issues.jboss.org/browse/JBEAP-15599 and https://issues.jboss.org/browse/ENTMQBR-2035 does not present in upstream. (Fixed in upstream by https://github.com/rh-messaging/jboss-activemq-artemis/commit/fe0ca4d84fc587b701e4b83ae8e5f2240c222842)

You shouldn’t reference an external JiRA on a commit.

I updated commit message and PR title.


V1.5 DIO API change

This pull request includes the following change:

Python API has changed for all the builders. Builders now have to follow a flow similar to: init() --> setup() --> run() --> stop().

Dummy state has been added to FSM machine so users will see consistent initial state in the 1st sample of trace analyzer. Dummy sample is also added to pattern builder to make sure FSM and pattern builders work in sync.

Boolean builder bugs have been fixed so in the RUNNING state, logic outputs are held on output pins.

For now this branch should work but remaining changes are expected for this pull request soon:

Will update names in SDK project and tcl file so names like SMG, PG, CFG will disappear.

Will update Python constants based on the above name change.

@drichmond  Your changes on these files make my pull request conflicting... This produces more work for me, so next time please leave these files untouched. I can do the formatted string by myself.

I was told to fix all of the format strings by yesterday afternoon - sorry if it caused any conflicts, but those were my instructions.


[KeyVault] update*Properties should receive the optional version in the options bag.

This is relevant for keys, secrets and certificates.
See this conversation for context: https://github.com/Azure/azure-sdk-for-js/pull/6527#discussion_r357365579

Moving the version to the options bag for keys & secrets will be a breaking change.
cc @bterlson

One non-breaking solution is to add overloads.

Discussed with Brian and he agreed on adding overloads.

Update certificate actually requires the version to be passed, so I will make it required again: https://docs.microsoft.com/en-us/rest/api/keyvault/updatecertificate/updatecertificate

Also, this issue number is 6543! Neat.


Revert "Release 8.7.1 (hotfix)"

Reverts microsoft/onefuzz#3459

Codecov Report

Merging #3468 (9602ae1) into main (c69deed) will decrease coverage by 0.81%.
The diff coverage is 4.61%.

@@            Coverage Diff             @@
##             main    #3468      +/-   ##
==========================================
- Coverage   33.86%   33.06%   -0.81%
==========================================
  Files         297      271      -26
  Lines       36821    31267    -5554
==========================================
- Hits        12470    10338    -2132
+ Misses      24351    20929    -3422

Files Changed
Coverage Δ

.../ApiService/ApiService/Functions/QueueJobResult.cs
0.00% <0.00%> (ø)

src/ApiService/ApiService/OneFuzzTypes/Model.cs
70.37% <0.00%> (-2.26%)
:arrow_down:

src/ApiService/ApiService/Program.cs
11.76% <0.00%> (-0.08%)
:arrow_down:

src/ApiService/ApiService/onefuzzlib/Config.cs
0.00% <0.00%> (ø)

src/ApiService/ApiService/onefuzzlib/Extension.cs
0.00% <0.00%> (ø)

...ApiService/ApiService/onefuzzlib/OnefuzzContext.cs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/config.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/log_uploader.rs
0.00% <ø> (ø)

src/agent/onefuzz-result/src/job_result.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-task/src/local/cmd.rs
0.00% <ø> (ø)

... and 31 more

... and 59 files with indirect coverage changes


pyPowerwall [0.8.2] Proxy Server [t53] testing

These aren't unique to 0.8.2, but thought you'd like to see them regardless with all the new error handling.
2024-04-12 22:01:05 04/12/2024 10:01:05 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:01:05 04/12/2024 10:01:05 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:01:06 04/12/2024 10:01:06 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:01:08 04/12/2024 10:01:08 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:01:08 04/12/2024 10:01:08 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:31:10 04/12/2024 10:31:10 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:31:10 04/12/2024 10:31:10 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe
2024-04-12 22:31:11 ----------------------------------------
2024-04-12 22:31:11 Exception occurred during processing of request from ('<IP_ADDRESS>', 42768)
2024-04-12 22:31:11 Traceback (most recent call last):
2024-04-12 22:31:11   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-12 22:31:11     self.finish_request(request, client_address)
2024-04-12 22:31:11   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-12 22:31:11     self.RequestHandlerClass(request, client_address, self)
2024-04-12 22:31:11   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-12 22:31:11     self.handle()
2024-04-12 22:31:11   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-12 22:31:11     self.handle_one_request()
2024-04-12 22:31:11   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-12 22:31:11     method()
2024-04-12 22:31:11   File "/app/server.py", line 321, in do_GET
2024-04-12 22:31:11     fcv["grid_status"] = pw.grid_status(type="numeric")
2024-04-12 22:31:11   File "/app/pypowerwall/__init__.py", line 616, in grid_status
2024-04-12 22:31:11     grid_status = payload['grid_status']
2024-04-12 22:31:11 TypeError: 'NoneType' object is not subscriptable
2024-04-12 22:31:11 ----------------------------------------

Thanks @jgleigh  - I do appreciate these. For some reason, I don't get these but suspect it is due to having my Powerwall hardwired into my network. This is likely caused by something like a network communication error that results in a malformed payload that is missing that key. I'm going to start adding dictionary getters to these elements to help reduce the noise in the logs. However, I will have it continue to log a notice otherwise you won't know that these calls are failing, a possible indication of a weak network link.

Mine is hardwired too. These errors don't seem to cause any issues though which is good.

Are these coming from an external source? I noticed the IP address isn't inside my network.
Exception occurred during processing of request from ('<IP_ADDRESS>', 42768)
Exception occurred during processing of request from ('<IP_ADDRESS>', 59624)
Exception occurred during processing of request from ('<IP_ADDRESS>', 36076)
Exception occurred during processing of request from ('<IP_ADDRESS>', 40034)

Might be something inside the Docker instance, since 172.18.x.x is a private IP address. Very strange.

Since you are using the Powerwall-Dashbaord setup, that is telegraf.  The Dashboard setup uses docker-compose which create a private network inside docker to manage the communication between the containers. The setup is defined in the compose (powerwall.yml) setup.
Telegraf's job is to poll for data and store it in InfluxDB for use by Grafana.  What happens is this:
telegraf --(polls)--> pypowerwall --(polls)--> Powerwall Gateway
Pypowerwall doesn't proactively poll the Powerwall, it waits for a request. That is why you see "processing a request from" in the log. You will likely see other traffic too. You can directly hit pypowerwall via your browser or other means, and that is exactly what we do for the Power Flow Animation  built in to the proxy (e.g. http://localhost:8675/example.html).
If you want to test the patch to improve the exception errors you are seeing you can update powerwall.yml to use this:
jasonacox/pypowerwall:0.8.3t53-beta

and restart
./compose-dash.sh up -d

No change with 0.8.3 :(
2024-04-13 11:16:11 Exception occurred during processing of request from ('<IP_ADDRESS>', 41366)
2024-04-13 11:16:11 Traceback (most recent call last):
2024-04-13 11:16:11   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-13 11:16:11     self.finish_request(request, client_address)
2024-04-13 11:16:11   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-13 11:16:11     self.RequestHandlerClass(request, client_address, self)
2024-04-13 11:16:11   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-13 11:16:11     self.handle()
2024-04-13 11:16:11   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-13 11:16:11     self.handle_one_request()
2024-04-13 11:16:11   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-13 11:16:11     method()
2024-04-13 11:16:11   File "/app/server.py", line 321, in do_GET
2024-04-13 11:16:11     fcv["grid_status"] = pw.grid_status(type="numeric")
2024-04-13 11:16:11   File "/app/pypowerwall/__init__.py", line 616, in grid_status
2024-04-13 11:16:11     grid_status = payload.get('grid_status')
2024-04-13 11:16:11 AttributeError: 'NoneType' object has no attribute 'get'
2024-04-13 11:16:11 ----------------------------------------```

A quick Google search found similar issues with other Python scripts and people aren't always sure why they happen intermittently.

Hi @jgleigh - can you check http://localhost:8675/stats to make sure it show 0.8.3 as the version? If not, use this container:
jasonacox/pypowerwall:0.8.3t53-beta2

{"pypowerwall": "0.8.3 Proxy t53", "gets": 13664, "errors": 0

Ok, another try... I saw where I was missing the empty payload. It will still log an error because this could be indicative of a bigger problem (unable to communicate with the Powerwall), but should not be a exception trace.
jasonacox/pypowerwall:0.8.3t54-beta

2024-04-13 22:46:25 04/13/2024 10:46:25 PM [pypowerwall.local.pypowerwall_local] [ERROR] 503 Service Unavailable at https://<IP_ADDRESS>/api/solar_powerwall - Activating 5 minute API cooldown
I like it!

04/15/2024 06:33:42 AM [proxy] [INFO] Control Command: Set Reserve to 15
04/15/2024 08:00:04 AM [proxy] [INFO] Control Command: Set Reserve to 5
 CANCEL

Mine shows 'CANCEL' after setting the reserve this morning.
Seems to be working fine regardless.

Seeing this a lot more now. Not sure what's going on. Also seeing periodic data dropouts of 2min each.
2024-04-18 15:16:07 04/18/2024 03:16:07 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe

2024-04-18 15:16:07 04/18/2024 03:16:07 PM [proxy] [ERROR] Socket broken sending API response to client [doGET]: [Errno 32] Broken pipe

This is an indication of a network connection breaking. It is actually on the "client" side (e.g. web browser, telegraf, etc) and is could be due to a timeout of that client waiting for a response from the Powerwall (via the Proxy).

Seeing a lot more errors lately. Anything else I can look at to see what is going on here?
Running for period: [2024-04-01 00:00:00-07:00] - [2024-04-23 23:59:59-07:00] (22 days, 23:59:59s)

Searching InfluxDB for data gaps (power usage)
* Found data gap: [2024-04-19 20:31:00-07:00] - [2024-04-19 20:38:00-07:00] (0:07:00s)
* Found data gap: [2024-04-20 04:16:00-07:00] - [2024-04-20 04:34:00-07:00] (0:18:00s)
* Found data gap: [2024-04-20 17:02:00-07:00] - [2024-04-20 17:10:00-07:00] (0:08:00s)
* Found data gap: [2024-04-21 17:17:00-07:00] - [2024-04-21 17:24:00-07:00] (0:07:00s)

Searching InfluxDB for data gaps (grid status)
* Found data gap: [2024-04-19 01:30:00-07:00] - [2024-04-19 01:33:00-07:00] (0:03:00s)
* Found data gap: [2024-04-19 18:15:00-07:00] - [2024-04-19 18:17:00-07:00] (0:02:00s)
* Found data gap: [2024-04-19 20:31:00-07:00] - [2024-04-19 20:38:00-07:00] (0:07:00s)
* Found data gap: [2024-04-20 04:16:00-07:00] - [2024-04-20 04:34:00-07:00] (0:18:00s)
* Found data gap: [2024-04-20 11:32:00-07:00] - [2024-04-20 11:37:00-07:00] (0:05:00s)
* Found data gap: [2024-04-20 17:02:00-07:00] - [2024-04-20 17:10:00-07:00] (0:08:00s)
* Found data gap: [2024-04-21 17:17:00-07:00] - [2024-04-21 17:24:00-07:00] (0:07:00s)

Retrieving data for gap: [2024-04-19 20:32:00-07:00] - [2024-04-19 20:37:59-07:00] (0:05:59s)
* Loading daily history: [2024-04-19] (America/Phoenix)
Retrieving data for gap: [2024-04-20 04:17:00-07:00] - [2024-04-20 04:33:59-07:00] (0:16:59s)
* Loading daily history: [2024-04-20] (America/Phoenix)
Retrieving data for gap: [2024-04-20 17:03:00-07:00] - [2024-04-20 17:09:59-07:00] (0:06:59s)
Retrieving data for gap: [2024-04-21 17:18:00-07:00] - [2024-04-21 17:23:59-07:00] (0:05:59s)
* Loading daily history: [2024-04-21] (America/Phoenix)

Retrieving backup event history
* Creating grid status data: [2024-04-19 01:31:00-07:00] - [2024-04-19 01:32:59-07:00] (0:01:59s)
* Creating grid status data: [2024-04-19 18:16:00-07:00] - [2024-04-19 18:16:59-07:00] (0:00:59s)
* Creating grid status data: [2024-04-19 20:32:00-07:00] - [2024-04-19 20:37:59-07:00] (0:05:59s)
* Creating grid status data: [2024-04-20 04:17:00-07:00] - [2024-04-20 04:33:59-07:00] (0:16:59s)
* Creating grid status data: [2024-04-20 11:33:00-07:00] - [2024-04-20 11:36:59-07:00] (0:03:59s)
* Creating grid status data: [2024-04-20 17:03:00-07:00] - [2024-04-20 17:09:59-07:00] (0:06:59s)
* Creating grid status data: [2024-04-21 17:18:00-07:00] - [2024-04-21 17:23:59-07:00] (0:05:59s)

Writing to InfluxDB
Updating InfluxDB
Done.

2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 Exception occurred during processing of request from ('<IP_ADDRESS>', 50070)
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:45     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:45     return self._find_no_duplicates(name)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:45     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:45 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:45
2024-04-21 17:24:45 During handling of the above exception, another exception occurred:
2024-04-21 17:24:45
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:45     self.finish_request(request, client_address)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:45     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:45     self.handle()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:45     self.handle_one_request()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:45     method()
2024-04-21 17:24:45   File "/app/server.py", line 293, in do_GET
2024-04-21 17:24:45     alerts = pw.alerts()
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 484, in alerts
2024-04-21 17:24:45     data: dict = self.poll('/api/solar_powerwall') or {}
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:45     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:45     self._get_session()
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:45     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:45 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 Exception occurred during processing of request from ('<IP_ADDRESS>', 50084)
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:45     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:45     return self._find_no_duplicates(name)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:45     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:45 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:45
2024-04-21 17:24:45 During handling of the above exception, another exception occurred:
2024-04-21 17:24:45
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:45     self.finish_request(request, client_address)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:45     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:45     self.handle()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:45     self.handle_one_request()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:45     method()
2024-04-21 17:24:45   File "/app/server.py", line 343, in do_GET
2024-04-21 17:24:45     d = pw.system_status() or {}
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 650, in system_status
2024-04-21 17:24:45     payload: dict = self.poll('/api/system_status')
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:45     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:45     self._get_session()
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:45     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:45 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 Exception occurred during processing of request from ('<IP_ADDRESS>', 50086)
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:45     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:45     return self._find_no_duplicates(name)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:45     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:45 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:45
2024-04-21 17:24:45 During handling of the above exception, another exception occurred:
2024-04-21 17:24:45
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:45     self.finish_request(request, client_address)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:45     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:45     self.handle()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:45     self.handle_one_request()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:45     method()
2024-04-21 17:24:45   File "/app/server.py", line 252, in do_GET
2024-04-21 17:24:45     message: str = pw.strings(jsonformat=True) or json.dumps({})
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 333, in strings
2024-04-21 17:24:45     payload: dict = self.poll('/api/solar_powerwall') or {}
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:45     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:45     self._get_session()
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:45     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:45 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:45 Exception occurred during processing of request from ('<IP_ADDRESS>', 50050)
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:45     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:45     return self._find_no_duplicates(name)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:45     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:45 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:45
2024-04-21 17:24:45 During handling of the above exception, another exception occurred:
2024-04-21 17:24:45
2024-04-21 17:24:45 Traceback (most recent call last):
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:45     self.finish_request(request, client_address)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:45     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:45     self.handle()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:45     self.handle_one_request()
2024-04-21 17:24:45   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:45     method()
2024-04-21 17:24:45   File "/app/server.py", line 226, in do_GET
2024-04-21 17:24:45     message: str = pw.poll('/api/meters/aggregates', jsonformat=True)
2024-04-21 17:24:45   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:45     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:45     self._get_session()
2024-04-21 17:24:45   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:45     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:45 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:45 ----------------------------------------
2024-04-21 17:24:46 ----------------------------------------
2024-04-21 17:24:46 Exception occurred during processing of request from ('<IP_ADDRESS>', 50092)
2024-04-21 17:24:46 Traceback (most recent call last):
2024-04-21 17:24:46   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:46     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:46     return self._find_no_duplicates(name)
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:46     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:46 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:46
2024-04-21 17:24:46 During handling of the above exception, another exception occurred:
2024-04-21 17:24:46
2024-04-21 17:24:46 Traceback (most recent call last):
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:46     self.finish_request(request, client_address)
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:46     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:46     self.handle()
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:46     self.handle_one_request()
2024-04-21 17:24:46   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:46     method()
2024-04-21 17:24:46   File "/app/server.py", line 305, in do_GET
2024-04-21 17:24:46     d = pw.system_status() or {}
2024-04-21 17:24:46   File "/app/pypowerwall/__init__.py", line 650, in system_status
2024-04-21 17:24:46     payload: dict = self.poll('/api/system_status')
2024-04-21 17:24:46   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:46     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:46   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:46     self._get_session()
2024-04-21 17:24:46   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:46     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:46 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:46 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 37662)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:50     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:50     return self._find_no_duplicates(name)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:50     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:50 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 252, in do_GET
2024-04-21 17:24:50     message: str = pw.strings(jsonformat=True) or json.dumps({})
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 333, in strings
2024-04-21 17:24:50     payload: dict = self.poll('/api/solar_powerwall') or {}
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:50     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:50 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 37692)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:50     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:50     return self._find_no_duplicates(name)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:50     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:50 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 305, in do_GET
2024-04-21 17:24:50     d = pw.system_status() or {}
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 650, in system_status
2024-04-21 17:24:50     payload: dict = self.poll('/api/system_status')
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:50     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:50 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 37676)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:50     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:50     return self._find_no_duplicates(name)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:50     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:50 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 229, in do_GET
2024-04-21 17:24:50     message: str = pw.poll('/api/system_status/soe', jsonformat=True)
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:50     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:50 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 37686)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:50     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:50     return self._find_no_duplicates(name)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:50     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:50 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 343, in do_GET
2024-04-21 17:24:50     d = pw.system_status() or {}
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 650, in system_status
2024-04-21 17:24:50     payload: dict = self.poll('/api/system_status')
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:50     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:50 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 37664)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 91, in _get_session
2024-04-21 17:24:50     self.auth = {'AuthCookie': r.cookies['AuthCookie'], 'UserRecord': r.cookies['UserRecord']}
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 334, in __getitem__
2024-04-21 17:24:50     return self._find_no_duplicates(name)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/cookies.py", line 413, in _find_no_duplicates
2024-04-21 17:24:50     raise KeyError(f"name={name!r}, domain={domain!r}, path={path!r}")
2024-04-21 17:24:50 KeyError: "name='AuthCookie', domain=None, path=None"
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 226, in do_GET
2024-04-21 17:24:50     message: str = pw.poll('/api/meters/aggregates', jsonformat=True)
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 100, in _get_session
2024-04-21 17:24:50     raise LoginError("Invalid Powerwall Login")
2024-04-21 17:24:50 pypowerwall.local.exceptions.LoginError: Invalid Powerwall Login
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 ----------------------------------------
2024-04-21 17:24:50 Exception occurred during processing of request from ('<IP_ADDRESS>', 50038)
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
2024-04-21 17:24:50     response = conn.getresponse()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 466, in getresponse
2024-04-21 17:24:50     httplib_response = super().getresponse()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/client.py", line 1375, in getresponse
2024-04-21 17:24:50     response.begin()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/client.py", line 318, in begin
2024-04-21 17:24:50     version, status, reason = self._read_status()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/client.py", line 279, in _read_status
2024-04-21 17:24:50     line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socket.py", line 705, in readinto
2024-04-21 17:24:50     return self._sock.recv_into(b)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/ssl.py", line 1307, in recv_into
2024-04-21 17:24:50     return self.read(nbytes, buffer)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/ssl.py", line 1163, in read
2024-04-21 17:24:50     return self._sslobj.read(len, buffer)
2024-04-21 17:24:50 TimeoutError: The read operation timed out
2024-04-21 17:24:50
2024-04-21 17:24:50 The above exception was the direct cause of the following exception:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
2024-04-21 17:24:50     resp = conn.urlopen(
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
2024-04-21 17:24:50     retries = retries.increment(
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 470, in increment
2024-04-21 17:24:50     raise reraise(type(error), error, _stacktrace)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/util/util.py", line 39, in reraise
2024-04-21 17:24:50     raise value
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
2024-04-21 17:24:50     response = self._make_request(
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 539, in _make_request
2024-04-21 17:24:50     self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 370, in _raise_timeout
2024-04-21 17:24:50     raise ReadTimeoutError(
2024-04-21 17:24:50 urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=5)
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 78, in _get_session
2024-04-21 17:24:50     r = self.session.post(url, data=pload, verify=False, timeout=self.timeout)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 637, in post
2024-04-21 17:24:50     return self.request("POST", url, data=data, json=json, **kwargs)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
2024-04-21 17:24:50     resp = self.send(prep, **send_kwargs)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
2024-04-21 17:24:50     r = adapter.send(request, **kwargs)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 532, in send
2024-04-21 17:24:50     raise ReadTimeout(e, request=request)
2024-04-21 17:24:50 requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=5)
2024-04-21 17:24:50
2024-04-21 17:24:50 During handling of the above exception, another exception occurred:
2024-04-21 17:24:50
2024-04-21 17:24:50 Traceback (most recent call last):
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 683, in process_request_thread
2024-04-21 17:24:50     self.finish_request(request, client_address)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 360, in finish_request
2024-04-21 17:24:50     self.RequestHandlerClass(request, client_address, self)
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/socketserver.py", line 747, in __init__
2024-04-21 17:24:50     self.handle()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 433, in handle
2024-04-21 17:24:50     self.handle_one_request()
2024-04-21 17:24:50   File "/usr/local/lib/python3.10/http/server.py", line 421, in handle_one_request
2024-04-21 17:24:50     method()
2024-04-21 17:24:50   File "/app/server.py", line 229, in do_GET
2024-04-21 17:24:50     message: str = pw.poll('/api/system_status/soe', jsonformat=True)
2024-04-21 17:24:50   File "/app/pypowerwall/__init__.py", line 202, in poll
2024-04-21 17:24:50     payload = self.client.poll(api, force, recursive, raw)
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 182, in poll
2024-04-21 17:24:50     self._get_session()
2024-04-21 17:24:50   File "/app/pypowerwall/local/pypowerwall_local.py", line 83, in _get_session
2024-04-21 17:24:50     raise ConnectionError(err)
2024-04-21 17:24:50 ConnectionError: Unable to connect to Powerwall at https://<IP_ADDRESS>: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=5)
2024-04-21 17:24:50 ----------------------------------------

Just noticed something...looks like my Gateway rebooted around 17:24 on 4/21. Not sure why. I'm going to keep an eye on that to see if my Gateway is starting to act up.
System Uptime: 38h30m36.182464703s

I was gonna say, my console looked the same when I was doing some core maintenance at the weekend that affected connectivity. Read timed out. (read timeout=5) is the clue.

Another Gateway reboot about 10 hours ago. Starting to wonder if 24.4.0 has some issues.

@jgleigh Yikes... Did it require you to reset your password?

@jasonacox Nope, I only notice from the proxy logs. The system reboots fast enough that nothing goes offline.

And again today...really don't know why it's so unstable these days. Either the Gateway computer is having issues or 24.4.0 has some seriously bad bugs.
"start_time": "2024-05-02 13:50:57 +0800",
"up_time_seconds": "5h56m3.175433462s",
"is_new": false,
"version": "24.4.0 0fe780c9",

Good idea, @jgleigh - I am on the same Firmware but haven't seen the same thing. However, I do notice that start_time and up_time don't match but that could just be a integer wraparound.
"start_time": "2024-03-21 21:04:21 +0800",
"up_time_seconds": "1007h8m57.41338074s",
"is_new": false,
"version": "24.4.0 0fe780c9",

Just noticed there might a bug in the API...it's reporting the start time as +0800, but my time zone is actually -07:00 and the time reported is correct for -07:00. Unless that +0800 means something else. It looks like all the API documentation shows it always as +0800.

However, I do notice that start_time and up_time don't match but that could just be a integer wraparound.

Looks correct. Your start time is 9:04 PM on 3/21 which works out to 1007 hours ago.

I noticed that PowerDashboard is still using proxy 0.8.2. What's the plan to sync up the two projects?
I got two longer dropouts today...very odd.

Hi @jgleigh - Here is the plan to sync them up: https://github.com/jasonacox/Powerwall-Dashboard/pull/474
The tests have gone well and today I heard back from someone in the community that confirmed the new controls.  I'm ready to merge.
However, I don't believe this update will help your issue. The behavior you are seeing seems very suspicious. It could be the hardware itself, or it could be some unusual load/traffic coming from somewhere on the network. My only suggestion would be based on what I would do. I would change the IP address (change the DHCP pinning to a new address) and power cycle the Powerwall Gateway. I don't know if that would help, but I would have to try.
I'll merge the PR so you can pull the latest if you want.

Agreed, there's something else going on with my system. I was more just curious since we've been testing out new proxy features. Thanks again.

Let me know what you think...  Hopefully it works. :)


Atlas Docker Build compilation error

when I ran mvn clean install -Ddocker -Ddocker.repo=XXX  for docker atlas. Giving me the below error.
[INFO] [INFO] Apache Atlas Notification 2.0.0-SNAPSHOT ........... SUCCESS [ 31.282 s]
[INFO] [INFO] Open Metadata support for Atlas 2.0.0-SNAPSHOT ..... FAILURE [02:48 min]
[INFO] [INFO] atlas-client-v2 2.0.0-SNAPSHOT ..................... SKIPPED
[INFO] [INFO] Apache Atlas UI 2.0.0-SNAPSHOT ..................... SKIPPED
[INFO] [INFO] Apache Atlas Web Application 2.0.0-SNAPSHOT ........ SKIPPED
[INFO] [INFO] Apache Atlas Documentation 2.0.0-SNAPSHOT .......... SKIPPED
[INFO] [INFO] Apache Atlas FileSystem Model 2.0.0-SNAPSHOT ....... SKIPPED
[INFO] [INFO] Apache Atlas Plugin Classloader 2.0.0-SNAPSHOT ..... SKIPPED
[INFO] [INFO] Apache Atlas Hive Bridge Shim 2.0.0-SNAPSHOT ....... SKIPPED
[INFO] [INFO] Apache Atlas Hive Bridge 2.0.0-SNAPSHOT ............ SKIPPED
[INFO] [INFO] Apache Atlas Falcon Bridge Shim 2.0.0-SNAPSHOT ..... SKIPPED
[INFO] [INFO] Apache Atlas Falcon Bridge 2.0.0-SNAPSHOT .......... SKIPPED
[INFO] [INFO] Apache Atlas Sqoop Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED
[INFO] [INFO] Apache Atlas Sqoop Bridge 2.0.0-SNAPSHOT ........... SKIPPED
[INFO] [INFO] Apache Atlas Storm Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED
[INFO] [INFO] Apache Atlas Storm Bridge 2.0.0-SNAPSHOT ........... SKIPPED
[INFO] [INFO] Apache Atlas Hbase Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED
[INFO] [INFO] Apache Atlas Hbase Bridge 2.0.0-SNAPSHOT ........... SKIPPED
[INFO] [INFO] Apache Atlas Kafka Bridge 2.0.0-SNAPSHOT ........... SKIPPED
[INFO] [INFO] Apache Atlas Distribution 2.0.0-SNAPSHOT ........... SKIPPED
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time:  16:05 min
[INFO] [INFO] Finished at: 2019-07-02T04:20:48Z
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project open-metadata: Compilation failure: Compilation failure:
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSMetadataCollection.java:[407,36] cannot find symbol
[INFO] [ERROR]   symbol:   method getActiveTypesByWildCardName(java.lang.String,java.lang.String)
[INFO] [ERROR]   location: variable repositoryHelper of type org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.repositoryconnector.OMRSRepositoryHelper
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipMapper.java:[551,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable DATA_PLATFORM
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipMapper.java:[554,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable EXTERNAL_ENGINE
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipMapper.java:[557,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable EXTERNAL_TOOL
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityMapper.java:[682,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable DATA_PLATFORM
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityMapper.java:[685,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable EXTERNAL_ENGINE
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] /root/atlas/open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityMapper.java:[688,64] cannot find symbol
[INFO] [ERROR]   symbol:   variable EXTERNAL_TOOL
[INFO] [ERROR]   location: class org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore.properties.instances.InstanceProvenanceType
[INFO] [ERROR] -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[INFO] [ERROR]
[INFO] [ERROR] After correcting the problems, you can resume the build with the command
[INFO] [ERROR]   mvn <goals> -rf :open-metadata
[ERROR] The command '/bin/sh -c mvn clean install -DskipTests -Pdist,embedded-hbase-solr -DskipEnunciate -f ./atlas/pom.xml' returned a non-zero code: 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  35:50 min
[INFO] Finished at: 2019-07-02T04:20:49Z

will let @cmgrote handle this. He has a tougher challenge with combining egeria code and atlas code together. May be worth considering whether any combined build (docker or other) should be an additional required check --

From the build steps, this looks like this is the Atlas fork (eg. ..../docker/atlas rather than ..../docker/apache-atlas)?  This is a fork that we don't plan to maintain going forward -- I understood that it was still working, but now be broken (?)

Oops - I misread the name. I'll check

From the build steps, this looks like this is the Atlas fork (eg. ..../docker/atlas rather than ..../docker/apache-atlas)? This is a fork that we don't plan to maintain going forward -- I understood that it was still working, but now may be broken (?)

@cmgrote  i am assuming ../docker/atlas is not required instead apache-atlas will consider.

The failing constants are defined in org.odpi.openmetadata.accessservices.dataplatform.utils - refactoring likely means atlas isn't pulling in all the needed dependencies
However as @cmgrote mentioned this atlas fork will be removed just as soon as we get some replacement UIs in place so we won't put too much effort into fixing.
I'll take a short look at the egeria dependencies used by the fork

Actually the first failure relates to getActiveTypesByWildCardName. This was removed in e1d1eb94c3974d75fe312f58c1f4dc667c043634 which was committed on June 30
It would be possible to refactor the connector, but I think we're fighting a losing battle as we want to move the egeria code on
@cmgrote @mandy-chessell @grahamwallis I think it's time to retire the old atlas connector

remove from the source
remove from the build infrastructure requirements

We could see if old atlas image  will still work with the help charts but given @cmgrote 's work to build the new connector is progressing, and a merge on our container stuff is blocked whilst we supported old atlas, I'm inclined to say let's take it and move on.
It will impact consumers wanting to view what is in Egeria, we can individually talk to them and suggest using postman in the interim, with initial versions of new UIs expected in weeks
Ok?
If so I'll do the removal and merge

I've now removed the atlas fork in #1236 and merged
We now need to remove the build for the atlas fork
I shall raise a helpdesk item for this (as a request to your team?)

issue was raised. closing here


rename example change_detection to have unique name

Objective
Noticed a warning when running tests:
> cargo test --workspace
warning: output filename collision.
The example target `change_detection` in package `bevy_ecs v0.5.0 (/bevy/crates/bevy_ecs)` has the same output filename as the example target `change_detection` in package `bevy v0.5.0 (/bevy)`.
Colliding filename is: /bevy/target/debug/examples/change_detection
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The example target `change_detection` in package `bevy_ecs v0.5.0 (/bevy/crates/bevy_ecs)` has the same output filename as the example target `change_detection` in package `bevy v0.5.0 (/bevy)`.
Colliding filename is: /bevy/target/debug/examples/change_detection.dSYM
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.

Solution
I renamed example change_detection to component_change_detection

bors r+


Record tree pipes API

Create an API that accepts a sequence of token strings and returns static responses, function handlers or undefined if input is verifiable and otherwise throws an error.
Store the record tree in memory based on the JS object model.
Stick to the Record JS API specification regarding the handler model.
Satisfy API required by #1

Depends on #6


Adding some text-boxes enhancements

Hi,
@DhairyaBahl I want to make some changes to the textboxes while hovering onto them to make them look trendy.
It will become somewhat different from all the other messaging apps.
I think u got my point .
Kindly assign me this issue so that I can work on it ASAP.
thanks,
Himika Mishra

@Himika-Mishra I am assigning this issue to you but first try to merge the PR for your first issue. That way you will also not get confused between multiple issues. Hope you got my point.
All the best 🔥

Okay thanx. I have done that and it got merged too.
Now will be working on this issue.

Resolved


perf(client): adjust threshold of done jobs for callback to 50

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.907%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5282

Relevant Lines:
6371

💛  - Coveralls


pulling Granite 3 models

Currently, granite is shown shortcode corresponding to a gguf serialization:
https://github.com/containers/ramalama/blob/cd1e7d53b570beb00cb767b97fe14749b3932ac0/README.md?plain=1#L56-L57
What would be the equivalent for Granite 3 series recently released, please?
https://huggingface.co/collections/ibm-granite/granite-30-models-66fdb59bbb54785c3512114f
Can ramalama pull also the HF ModelCard, so to make use of it during push?

I can't seem to find gguf's for those on huggingface, but since they are on ollama, we can just pull via shortnames:
granite3-dense and granite3-moe
already.

Can ramalama pull also the HF ModelCard, so to make use of it during push?

I don't see why not 😄 would merge functionality like this

Thanks for the feedback in https://github.com/containers/ramalama/issues/367#issuecomment-2435172868 and https://github.com/containers/ramalama/issues/367#issuecomment-2435173992 !

I can't seem to find gguf's for those on huggingface

So for my understanding: is gguf the supported format, or are there other supported formats? 🤔  (sorry if maybe a banal question 😅  )

Thanks for the feedback in #367 (comment) and #367 (comment) !

I can't seem to find gguf's for those on huggingface

So for my understanding: is gguf the supported format, or are there other supported formats? 🤔 (sorry if maybe a banal question 😅 )

Right now only .gguf works well. We are open to supporting other formats and other runtimes (like llama.cpp and vllm are two ones planned).
As with most feature, it's often comes down to if someone with the time can open a PR!

I'm gonna close this because Ollama versions already have shortnames and these aren't available on HF in the correct format which is kinda out of our control


Cannot use profiles on windows

When using the default profile, the shell works, but trying to specify a profile like aws-shell --profile dev results in:
Creating doc index in the background. It will be a few minutes before all documentation is available.
aws> ec2 describe-instances
Traceback (most recent call last):
  File "c:\python27\lib\runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "c:\python27\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\Python27\Scripts\aws-shell.exe\__main__.py", line 9, in <module>
  File "c:\python27\lib\site-packages\awsshell\__init__.py", line 70, in main
    shell.run()
  File "c:\python27\lib\site-packages\awsshell\app.py", line 319, in run
    p = self._popen_cls(full_cmd, shell=True, env=self._env)
  File "c:\python27\lib\subprocess.py", line 710, in __init__
    errread, errwrite)
  File "c:\python27\lib\subprocess.py", line 958, in _execute_child
    startupinfo)
TypeError: environment can only contain strings

How did you install the shell?

Using PIP.


Load webview once in my app

Hello there,
Thanks for this library, I have a question, does somebody went threw this issue : Having Webviews on multiple page on a tab navigator, and the webview gets unmounted and mounted all the time.
So my question is : Is there a way to keep a webview mounted in the entire application and make use of it when it's necessary ?
Thanks,
Regards,

global modal ?


[Windows] please provide pre built binaries in release section from latest code

Is your feature request related to a problem? Please describe.
Well, it is really a very bad experiencing for newbies or noobs to first install ungoogled chromium and update, often the prebuilt binaries from volunteers are a month old and can't match up to the latest code, also they can be harmful or tampered( a small possibility)
Describe the solution you'd like
provide pre built binaries/packages in release section matching up to the latest code

There are binaries available for certain platforms in their corresponding platform repo (Debian/Ubuntu, Fedora, Android), and Guix has a general build for any Linux-based system. What platform are you on?
I believe this has been discussed before and splitting platforms into their separate repos was the conclusion. The reason why there is not a centralized binary release is because each platform has different additional steps/patches/dependencies so they need different updates after the main repo gets updated. For example, if you go to the Debian and Arch repo you will see that they have different patches and different way of building. If you go to the Android repo you can see it is even more different from Linux ones. Also different platforms are maintained by different people in addition to the main repo, so this results in a complicated situation and that is why we do not compile all versions together and put them here.

There are binaries available for certain platforms in their corresponding platform repo (Debian/Ubuntu, Fedora, Android), and Guix has a general build for any Linux-based system. What platform are you on?
I believe this has been discussed before and splitting platforms into their separate repos was the conclusion. The reason why there is not a centralized binary release is because each platform has different additional steps/patches/dependencies so they need different updates after the main repo gets updated. For example, if you go to the Debian and Arch repo you will see that they have different patches and different way of building. If you go to the Android repo you can see it is even more different from Linux ones. Also different platforms are maintained by different people in addition to the main repo, so this results in a complicated situation and that is why we do not compile all versions together and put them here.

i agree, but the only os left behind in this case is windows 10,all other os'es have builds from latest code, so there is a need for windows automated builds

i agree, but the only os left behind in this case is windows 10,all other os'es have builds from latest code, so there is a need for windows automated builds

Here you can download the Ungoogled assembly for Win64 from Marmaduke https://chromium.woolyss.com/#windows-64-bit

Here you can download the Ungoogled assembly for Win64 from Marmaduke https://chromium.woolyss.com/#windows-64-bit

Here you can download the Ungoogled assembly for Win64 from Marmaduke https://chromium.woolyss.com/#windows-64-bit

It is based on ungoogled chromium, but it still has widevine module installed, which is not a part of vanilla ungoogled chromium

Here you can download the Ungoogled assembly for Win64 from Marmaduke https://chromium.woolyss.com/#windows-64-bit

It is based on ungoogled chromium, but it still has widevine module installed, which is not a part of vanilla ungoogled chromium

somenody please build  32 bit version

somenody please build  32 bit version

Windows code has been updated along with binaries. Closing.

Windows code has been updated along with binaries. Closing.

Windows code has been updated along with binaries. Closing.

how do we update?

Windows code has been updated along with binaries. Closing.

how do we update?


Problem with mocking N requests of one type [GET].

I have a problem with mock requests of the same type. Namely, the data is mocked only for the last request from the mockData array.

In the #64 issue reportedly solved the problem. Am I doing something wrong?
Versions
storybook-addon-mock -4.3.0
Storybook 7.6.5
@nutboltu

It seems that the issue lies specifically with handling GET parameters. Different links with GET requests are processed successfully, but multiple instances with the same link but different GET parameters are not. However, your problem with the appearance of a fix can be solved by either moving the GET parameters into the URL - /api/currencies/<page>, or by creating a single object with a function in response, and forming the necessary response based on the GET parameters there:
export constStandart = {
    mockAddonConfigs: {
        globalMockData: [
        {
                url: '/api/currencies',
                method: 'GET',
                status: 200,
                response: ({ searchParams: { page, size }}) => {
                    ...
                },
            },
        ],
        ignoreQueryParams: true,
        disableUsingOriginal: true,
    },
};


Raspberry Pi Zero W Console No Output with ENABLE_UART = "1"

Description
I can successfully produce an image that boots the Raspberry Pi Zero with the following command:
source ./oe-init-build-env build-rpi ; bitbake -c cleansstate core-image-minimal ; bitbake core-image-minimal ; bitbake -c populate_sdk core-image-minimal'
However, I get no console output at all.
My machine is set:
MACHINE ??= "raspberrypi0-wifi"
My local.conf has the following related contents ( Raspberry ):
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
ENABLE_UART = "1"
RPI_USE_U_BOOT = "1"
BOOT_DELAY = "1"
#BOOT_DELAY_MS = "1"
#DISABLE_RPI_BOOT_LOGO = "1"
ENABLE_SPI_BUS = "1"
ENABLE_I2C = "1"
ENABLE_DWC2_PERIPHERAL = "1"
GPU_MEM = "16"
IMAGE_FSTYPES_append = " wic"
WKS_FILE = "sdimage-raspberrypi.wks"

My HDMI Monitor shows the Raspberry and eventually shows a prompt to log in.
I have this standard cable:

https://www.adafruit.com/product/954

I have triple checked my connection between the USB Serial Cable and my PC using the following instructions:

https://learn.adafruit.com/assets/41603
https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable
https://learn.adafruit.com/raspberry-pi-zero-creation/enable-uart

After flashing the card, in the boot partition, the config.txt shows this at the end:
# Enable UART
enable_uart=1
# Enable VC4 Graphics
dtoverlay=vc4-kms-v3d

I am launching the terminal console command like this:
sudo screen /dev/cu.usbserial-14220 115200
I get no console output, even though the Raspberry Pi Boots Successfully and local.conf has ENABLE_UART = "1"
Steps to reproduce the issue:

Set MACHINE ??= "raspberrypi0-wifi"
Add ENABLE_UART = "1" to local.conf
Build core-image-minimal
Flash chard and boot

Describe the results you received:
No Console Output to Mac Terminal screen command
Describe the results you expected:
Console Output to Mac Terminal screen command
Additional information you deem important (e.g. issue happens only occasionally):
This has never worked for me.
Additional details (revisions used, host distro, etc.):
Host is a Macbook Pro

I don't have a 0w to test but it would help if you could run, as a sanity check, a raspbian image.

Thanks for the comment. It turns out that I get console output on my native Ubuntu machine - but not my MacBook, maybe something with the Prolific USB/Serial drivers there.. Anyway this is not a bug with meta-raspberry and so I'll close it.


Feature: Symmetry breaking tuples

Rules like
foo(X) :- room(X, P1), room(X, P2), P1 != P2.

to
foo(X) :- room(X, P1), room(X, P2), P1 < P2.

Are there other cases ?

Done

Feature request: Add support for tuples:
foo(X) :- room(X, P1, V1), room(X, P2, V2), (P1,V1) != (P2,V2).

#false :- at(X,Y,T); at(X,Y,U); minot(Z,W,T); minot(Z,W,U); not U = T.
could be translated

add debug logging


⚠ Bofrost.at has degraded performance

In ad4314a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1598 ms

Resolved: Bofrost.at performance has improved in b5e2cf1.