PW3 only showing first 4 strings (A-D) in the dashboard.

Problem
Being using Dashboard with PW3 since you updated it a few ago and it's been working great. At the time I only had 4 solar strings and could see all of them in the dashboard. But recently my solar installer actually redid the string layout for my setup and now I have 5 strings. But I'm not seeing the 5th string in the dashboard. I actually tried backing up, do a fresh setup of the dashboard to see if that cleared anything that was cached, but it came up the same showing only 4 strings.
I tried manually running PW3_Strings.py and it's definitely getting readings from all 5 strings. I don't know a way to verify if the data is in the influxDB though.
Also, random note - might want to update the dashboard to say "Powerwall+/PW3 String Data" or something along those lines.

#528
I was able to fix it by modifying influxdb.sql. I've added a pull request.

Merged!  Thanks for this.


Is the snake-slam code content uploaded correctly?

@darglein
Thank you very much for your work, I read the snake-slam paper and thought it was great, but when I compile the program, there are various errors, some internal errors, such as in SnakeGlobal.h:
using Vec4f  = Saiga::Vec4f;
using Vec3f  = Saiga::Vec3f;
using Vec2f  = Saiga::Vec2f;
error: no type named 'Vec4f' in namespace 'Saiga'
Next:
inline Intrinsics4& K = mono_intrinsics.model.K;
error: unknown type name 'Intrinsics4'
Intrinsics4 is a file name, but it is used as a definition variable in the program, which is obviously wrong. I changed it to the following:
inline IntrinsicsPinholed& K = mono_intrinsics.model.K;
The program runs normally
In addition to these bugs, there are some bugs in FeatureDetector.h and FeatureDetector.cpp. So I would like to ask, is your program uploading the full version or the correct version?
Had very high expectations for the snake-slam framework because of your paper and seeing your framework in a SenseTime competition, but the bugs did disappoint me a bit，so looking forward to your early reply！

@darglein
The latest progress, I have fixed all the above bugs, the reason is that your snake slam does not match the saiga master branch version, but when I compile, when the progress reaches 100%, libsnake.a will appear to Saiga::ORBExtractor: :Detect Undefined reference errors, I guess it should be that the snake module in the CMakeLists does not have a good link to the saiga module, so I hope you can take a look at these errors, after all, I have fixed a lot of bugs, and your slam framework is like this Excellent, makes people have to learn

Hello,
I finally had some time to update the Code base and fix some errors.
Could you please try it again and check if it works now?
Best
Darius


cmd/compile: float64 to int64 conversion gives different result between amd64 and arm64 on overflows

What version of Go are you using (go version)?

$ go version
go version go1.16.3 darwin/amd64

$ go version
go version go1.16.3 linux/arm64

Does this issue reproduce with the latest release?

Run the following small program on amd64 and arm64: https://play.golang.org/p/8nY1Dwgq-BU
What did you expect to see?
Same result on both platforms.
What did you see instead?
-9223372036854775808 on amd64 and<PHONE_NUMBER>854775807 on arm64.

For some reason I think this is actually implementation-define behavior, but I'll have a look at the spec real quick. Will CC people in if I can't figure it out.

Yes, this appears to be working-as-intended.
From https://golang.org/ref/spec#Conversions:

In all non-constant conversions involving floating-point or complex values, if the result type cannot represent the value the conversion succeeds but the result value is implementation-dependent.

That's what specified now. If you think it should work differently, please file a proposal issue for it. Closing this one for now.

FWIW #6923 seems somewhat related (I think for constants this sort of conversion may be well-defined), but I don't actually see any proposals. I believe for constants these non-representable conversions are caught at compile-time.

@mknyszek Can you clarify "implementation-dependent" and how to contact the corresponding owners?

I think it means specifically that Go implementations are free to choose the behavior, which includes allowing these differences across architectures. I suspect this particular rule is chosen as a performance optimization.
In general, the result of such a conversion is fairly non-sensical when you can't represent some value in the new type. By allowing a broad range of behaviors, the compiler is able to generate faster code by not having to deal with the case where the conversion fails. Note that there are lots of places where Go doesn't choose implementation-defined behavior for both platform compatibility and just general programmer sanity, but to me this particular case seems sensible because one frequently can't do anything much with such a conversion.
If you'd like to start a discussion about this, the golang-nuts group is a good place to do so. If you have a specific proposal in mind for how this should work, feel free to file a new issue about it with "proposal:" in the title.


Adding information about Pyramid Framework

Official documentation and a tutorial from Digital Ocean.

Done it :)

Thanks!


WIP / DNM: net_admin: remove this capability

What this PR does / why we need it:
see what breaks when we remove the capability and work from there ...
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
THIS IS NOT WORKING
NO ETA ON HAVING THIS WORKING
Release note:

NONE

Issue list:

mtu configuration on the tap creation (netlink bug - open one; address it)
dhcp disables eth tx offload - moving this into the first part of pod networking setup seems to appease the launcher
cap_net_admin required when the users (tap creator & tap consumer) mismatch. Is this the issue we're facing ? ....

I wonder if we need to tap into the user ns of virt-launcher; we're not doing that in the tap creation stage, and the kernel code seems to require it. The caller is here - it returns EPERM, which is the error above.

@maiqueb this is happening because libvirt currently runs as root but needs to create this tap device for qemu that runs as a user. afaik, net_admin won't be required the moment we will switch running libvirt as non-root and connect to qemu using  qemu:///session

I wonder if we need to tap into the user ns of virt-launcher; we're not doing that in the tap creation stage, and the kernel code seems to require it. The caller is here - it returns EPERM, which is the error above.

@maiqueb this is happening because libvirt currently runs as root but needs to create this tap device for qemu that runs as a user. afaik, net_admin won't be required the moment we will switch running libvirt as non-root and connect to qemu using qemu:///session
FYI, @ashleyschuett

Only one way to find out :)
Thanks for pitching in; is that tracked in any PR ?

I wonder if we need to tap into the user ns of virt-launcher; we're not doing that in the tap creation stage, and the kernel code seems to require it. The caller is here - it returns EPERM, which is the error above.

@maiqueb this is happening because libvirt currently runs as root but needs to create this tap device for qemu that runs as a user. afaik, net_admin won't be required the moment we will switch running libvirt as non-root and connect to qemu using qemu:///session
FYI, @ashleyschuett

Only one way to find out :)
Thanks for pitching in; is that tracked in any PR ?

I didn't see a PR yet, but I think Ashley is looking into this area.

I wonder if we need to tap into the user ns of virt-launcher; we're not doing that in the tap creation stage, and the kernel code seems to require it. The caller is here - it returns EPERM, which is the error above.

@maiqueb this is happening because libvirt currently runs as root but needs to create this tap device for qemu that runs as a user. afaik, net_admin won't be required the moment we will switch running libvirt as non-root and connect to qemu using qemu:///session

@vladikr
According to the tuntap documentation, it seems you're right.

Set permissions:
e.g. chmod 0666 /dev/net/tun
There's no harm in allowing the device to be accessible by non-root users,
since CAP_NET_ADMIN is required for creating network devices or for
connecting to network devices which aren't owned by the user in question.
If you want to create persistent devices and give ownership of them to
unprivileged users, then you need the /dev/net/tun device to be usable by
those users.

Is there an on-going effort to change the user of libvirt to be qemu (107)? @ashleyschuett

The real deal PR #4506 was merged.


update proxy of master to raftstore-proxy

What problem does this PR solve?
Issue Number: ref #4982 close #7849
Problem Summary:
update proxy to raftstore-proxy
Proxy PR:
Including:\nSubmodule contrib/tiflash-proxy d3c6a06291..dff672f735:

Replace the previous task if a new snapshot is coming (#344)

What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge

/run-all-tests

/run-integration-test


For #1637, #307, make webrtc audio work

FFMPEG和Opus库，是这个PR合并的：https://github.com/ossrs/srs/pull/1661

Codecov Report

Merging #1659 into feature/rtc will decrease coverage by 0.5%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           feature/rtc    #1659      +/-   ##
===============================================
- Coverage        66.14%   65.63%   -0.51%
===============================================
  Files              107      108       +1
  Lines            42262    42588     +326
===============================================
  Hits             27954    27954
- Misses           14308    14634     +326

Impacted Files
Coverage Δ

trunk/src/protocol/srs_rtmp_stack.hpp
85.18% <0%> (-3.28%)
:arrow_down:

trunk/src/app/srs_app_config.cpp
75.81% <0%> (-0.22%)
:arrow_down:

trunk/src/app/srs_app_source.cpp
0.64% <0%> (ø)
:arrow_up:

trunk/src/app/srs_app_rtc_conn.hpp
0% <0%> (ø)
:arrow_up:

trunk/src/app/srs_app_rtc.cpp
0% <0%> (ø)
:arrow_up:

trunk/src/app/srs_app_http_api.cpp
0% <0%> (ø)
:arrow_up:

trunk/src/app/srs_app_source.hpp
0% <0%> (ø)
:arrow_up:

trunk/src/kernel/srs_kernel_flv.cpp
98.76% <0%> (ø)
:arrow_up:

trunk/src/app/srs_app_audio_recode.cpp
0% <0%> (ø)

Continue to review full report at Codecov.

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


fix(Dropdown): aria-live region needs aria-atomic

Did an audit of our site with NVDA and ran into a problem where dropdowns act kind of funny depending on the order of the values in the dropdown. Apparently aria-live regions only read what changes in the region unless you specify aria-atomic to read the entire area aloud. This means that if you have a dropdown like this
Within 25 miles
Within 50 miles
Within 125 miles
Within 250 miles
Within 500 miles
More than 500 miles

The screen reader reads these options as 'Within 25 miles', '50', '125', '0'
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions#Advanced_live_regions

Codecov Report

Merging #3621 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #3621   +/-   ##
=======================================
  Coverage   99.81%   99.81%
=======================================
  Files         174      174
  Lines        2744     2744
=======================================
  Hits         2739     2739
  Misses          5        5

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


loco-cli: 0.2.6 -> 0.2.9

Update package to 0.2.9 (diff from 0.2.6)
https://github.com/loco-rs/loco/commits/master/loco-cli
Use fetchCrate instead of fetchFromGitHub
Skip broken tests
Format with nixfmt-rfc-style
Refactor meta: remove with lib;, move mainProgram to bottom

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/2017


⚠ PrivateHD has degraded performance

In ce0b02a, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1013 ms

Resolved: PrivateHD performance has improved in 9150c1d.


How to get rid of the "Upload x files to this site?" Chrome popup?

Describe the problem
I am trying to select a folder with HTML input tag but chrome gives me a popup that I don't like to see. I just need the folder path, nothing else... I tried Tkinter filedialog but it is not cool with my situation. I searched for a chrome flag to disable this popup but couldn't figure it out. I really need help.
Here is the screenshot of the popup. I want to disable this one and directly upload the folder name.

[x] I know that if I don't provide sample code that allows someone to quickly step into my shoes, I may not get the help I want or my issue may be closed.

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 103

Eel relies completely on the underlying browser to render the HTML and execute the JavaScript; it doesn't have hooks into any specific browser implementation nor can influence the rendering of HTML or the execution of JavaScript except through command-line start flags or environment variables (when the browser supports them).
If tkinter doesn't work for you and you can't find any Chrome flag or environment variable to change the behavior that you dislike, perhaps you can look for another lightweight Python GUI toolkit to use in lieu of tkinter for getting that file path?

Thanks for your answer, I'm planning to use Tkinter or plyer to do this and freeze the UI until filedialog to close.


Can't We Post SP directly ?!

hmm....i should say thanx @alexcroox :+1:  for rising the question   &  @dougwilson :+1:  for giving the proper solution !
And My Question is can we use SP name directly instead of query !
EX : var sql = 'usp_InsertLinkedInConnections_linkedin_Insert(?)';  [ im not able to use like this !]
i was able to execute my program with this syntax !
--> var sql = 'INSERT INTO linkedin(LinkedInID, FirstName, LastName, UserID) VALUES ? ';
Can any1 help me with this issue :) plzz......

You need to use proper MySQL syntax to call a stored procedure, namely you need to write CALL:
conn.query('CALL usp_InsertLinkedInConnections_linkedin_Insert(?)', ['value'])


How can set data to BootstrapDropDown programmatically?

How can set data to BootstrapDropDown programmatically?

if You have Array inside String.xml You can use this:
BTD.setDropdownData("@array/*****");
if you don't have, you want set data from Your Database, You must create a method with Object return.. why?
because you need too argument first count of data ,second value of data..
you can use this snippet code:
DBHandler handler = new DBHandler(this);
Object[] a = handler.QueryDropDown();
Count= (int) a[1];
Value= new String[Count];
Value= (String[]) a[0];
BTD.setDropdownData(Value);