Investigate why wrappers_test is flaky

Example log:
https://github.com/tensorflow/addons/runs/372915266
Caused by the test case of .remove() method.

Closed by https://github.com/tensorflow/addons/pull/1190


Latest version 1.2.0 re-introduces issue #18

The last update to v1.2.0 re-introduces the problem with the MMM-Netatmo module, reported in detail in issue #18.
I could reproduce it by changing the declaration from let back to var

Sorry that this happened again. In the fork you mentioned in #18, the variable UserPresence is used, that's the problem. I have changed it back to var, but actually there should be another solution here. But for that you would have to change all the modules that work with this variable.
Just for interest: why are you using a fork of MMM-Netatmo and not the upstream project, which is obviously still active: https://github.com/CFenner/MMM-Netatmo

Thanks a lot for fixing the issue so quickly!
The reason, why I use that specific fork is that I'm running two netatmo stations in two different houses and that module allows for selecting which station should be displayed on MM (deviceNumber). I searched quite intensively, but this fork was the only one that met my requirements. You can have multiple stations under one Netatmo account, but the @CFenner module (and most of other forks) pick the first installed station only.

Actually, I paused the development for quite some time. Just recently I added the ability to load all stations of an account. Stations from different accounts are not supported, but one may invite guest user to a station. Maybe that helps.


Go update

upgraded to go version 1.17 (1.18 did not pass the tests)
added a test.yml github workflow
fixed some styling issues that made tests fail

👍


Add tweaks for Android

This pull gets this repo to build and pass all the tests natively on my Android AArch64 phone.

@Azoy, would you review?

@swift-ci please test

Can someone merge? Would be nice to have this in the 5.8 branch tomorrow.


Issue between binary and libc

I've tried to use WhiteboxTools 1.2.0 for Linux 64 bits. I'm running the binary on Ubuntu 18.04 64 bits and it seems it does work only if you have the same GLIBC.
When I run command whitebox_tools, it returns the following error

whitebox_tools: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by whitebox_tools)

I've bypassed the issue by compiling the code using cargo and rust but I open this issue if others meet the same issue. I don't know if there is a better way to manage binaries to make them portable from one GLIBC to another.

I can confirm that I encounter the same issue. It works fine on my Manjaro Linux, but it is not working on the Ubuntu-based Google Colab. Here is an example.
Error
./whitebox_tools: /lib/x86_64-linux-gnu/libm.so.6: version 'GLIBC_2.29' not found (required by ./whitebox_tools)

This is odd, since I compile WhiteboxTools on an Ubuntu system to create the binaries for each release. Alex actually pointed out an issue with the last release and suggested that I only use LTS version of Ubuntu, since I was using the latest 19.10. However, as it turn out, back-porting Ubuntu to an earlier version seems next to impossible. I'm hoping that things will be okay when I compile the next version hopefully using the upgrade 20.04 LTS version. I'm open to suggestions as to how to make this more portable but I'm not really a linux user. I only use it for compiling release versions and only maintain one old laptop for this purpose.

@jblindsay I am not very familiar with GLIBC, but I did a quick check on the recent Ubuntu releases and corresponding GLIBC versions. See below. Based on the error (version 'GLIBC_2.29' not found ) from  Google Colab (Ubuntu 18.04 LTS: GLIBC 2.27), it seems  WBT was compiled using GLIBC 2.29. I guess programs complied using newer version of GLIBC might not be able to run with older version of GLIBC. Therefore, be cautious if you plan to compile WBT using Ubuntu 20.04 LTS because older versions of Ubuntu might not be able to run WBT. I am using Manjaro Linux , which uses a rolling release development model and is always equipped with the latest GLIBC. Therefore, I have never encountered this GLIBC issue until I recently tested WBT on Google Colab. I would be happy to help testing WBT linux binaries on different Ubuntu versions and other Linux distros when you are getting ready for the next release. I usually use VirtualBox and download pre-installed Linux distros from  osboxes.org without having to install a Linux system from scratch.
Check Ubuntu version: lsb_release -a
Check GLIBC version: ldd --version

Ubuntu 18.04 LTS: GLIBC 2.27
Ubuntu 19.04: GLIBC 2.29
Ubuntu 19.10: GLIBC 2.30

I just compiled WBT from source using Ubuntu 18.04 LTS with GLIBC 2.27 and it seems the problem is solved.

Download WhiteboxTools_linux_amd64.tar.xz compiled using Ubuntu 18.04 LTS with GLIBC 2.27
Test the recompiled WBT binary with Google Colab Notebook

I've also tried it and it works fine. Will close.
Thanks


Add bidirectional flag to existing generator functions

What is the expected enhancement?
The existing directed_* generator functions in https://github.com/Qiskit/retworkx/blob/master/src/generators.rs only have an option to add a single edge. But it could be useful to add edges in both directions. While this is essentially the same as a undirected version of the function there are use cases where you could want bidirectional edges added to a directed graph generatore. For example a bidirectional path graph: a <-> b <-> c instead of just a -> b -> c that exists now. This would be to add a new boolean kwarg to the existing (and potential future) directed generator functions to set adding bidirectional edges.
This is related to #150 but self contained enhancement for the existing generator functions rather than adding new functions.

Can I work on this?

@darknight009 sure go ahead. I've assigned the issue to you.

What is the default expected behavior of bidirectionality?  Should it be set to "false" for directed_* generators?

Yeah, it should be default false. By default things should not be bidirectional, it should be an opt-in option that a user can set

How should the case for directed_star_graph be handled where both bidirectionality and inward are passed. For eg. directed_star_graph(num_nodes = 5, bidirectional=True, inward= True). Does bidirectional override inward?

Hmm, I forgot about that. I'll defer to you on that as long as it's documented clearly. Either we have one flag take precedence over the other or raise an exception. It doesn't really matter as long as we make it clear what the behavior is in that edge case (and probably have a test asserting that behavior too).

Ok proceeding with precedence of bidirectional over inward.


Multiple connections

Due to connection hash construction it is not possible to use this library in one script which uses multiple database connections at the same time (for example with PCNTL).
Fix:
$hash = sha1($hostname . $username . $flags . rand(1111111, 9999999) . microtime());

@Jarogniew this would completely break the point of the hash - to reuse connections. Can you confirm that the original MySQL extension works as you expected?

I was using for a long time native MySQL extension with PCNTL to fork separate processes from one CLI script. Using your library, when the first process has finished, the rest of them got 'MySQL server has gone' response. The workaround is to give separate MySQL link to each process is to make hash more unique. But maybe this approach will make MySQL links less efficient for normal usage, like web pages.

shouldn't you use non-persistent connections when you dont expect the connections to be shared?

I got into this problem too. For me I needed to access two databases on the same server so I needed one connection per database to avoid switching database before every request.
I don't understand this part of the code:
            /* persistent connections start with p: */
            if ($hostname{1} !== ':' && isset(\Dshafik\MySQL::$connections[$hash])) {
                \Dshafik\MySQL::$last_connection = \Dshafik\MySQL::$connections[$hash]['conn'];
                \Dshafik\MySQL::$connections[$hash]['refcount'] += 1;
                return \Dshafik\MySQL::$connections[$hash]['conn'];
            }

Shouldn't this be $hostname{1} === ':' instead? An existing connection should only be used when 'p:' are the first two characters of the hostname according to the comment.

@dshafik  Look at @terrafrost commit: https://github.com/terrafrost/php7-mysql-shim/commit/d0ee3daef00106f3d9381b4cc4ef378d7dedce33
And some others: https://github.com/terrafrost/php7-mysql-shim/commits/master

Bump. I believe that @aalexgabi is correct. Any comment?

Bump. I believe that @aalexgabi is correct. Any comment?

Okay, actually not. I think that I understand the code now.
The default behavior for mysql_connect is to reuse the same link when called with the same arguments. This is emulated here. The code just chooses to skip the emulation when a persistent connection is used, as mysqli_connect will return a mysqli instance that represents the same underlying connection anyway. So this issue is not an issue. However, an improvement would be to actually use the ignored $new parameter here for better backwards compatibility with the original mysql_connect.
https://www.php.net/manual/en/function.mysql-connect.php
See documentation for new_link parameter.
/* persistent connections start with p: */
if (!$new && $hostname{1} !== ':' && isset(\Dshafik\MySQL::$connections[$hash])) {
		\Dshafik\MySQL::$last_connection = \Dshafik\MySQL::$connections[$hash]['conn'];
	\Dshafik\MySQL::$connections[$hash]['refcount'] += 1;
	return \Dshafik\MySQL::$connections[$hash]['conn'];
}

#45 Added pull request for suggested compatibility fix.

This is now fixed with the merge of #45, thanks @techhead !


Add distances to edges of visibility graph

both euclidean distance and great circle. Need to be able to choose which to use


[joy-ui] Release Cycle

Steps to reproduce
There have been 14 @mui/material releases since the last<EMAIL_ADDRESS>release. Obviously they are different release trains, so I'm not expecting 14 @mui/joy releases.
However, considering that it has been close to 4months since the last release and there have been major changes (i.e<EMAIL_ADDRESS>to joy's underlying dependencies, I'm left wondering what the status of joy is... ?
 (Is there an issue or tracker I can follow to monitor / contribute progress towards that?)
If it is abandoned, any guidance on replacement / migration steps?
Current behavior
No response
Expected behavior
No response
Context
No response
Your environment
No response
Search keywords: joy release cycle

Thanks for reporting the issue! Joy UI development is temporarily on hold as the maintainers focus on the next two major releases of Material UI

It would be a shame if this project didn't get ongoing support. Such a great project! ❤

When starting a new project from scratch, we recommend Material UI over Joy UI because we can guarantee ongoing support.

Thanks for reporting the issue! Joy UI development is temporarily on hold as the maintainers focus on the next two major releases of Material UI

This is the same thing that was said almost exactly a year ago now and since then MUI v6 has been released. In that same blog post we also were told we'd get an update in 2024 Q2 but that never happened as far as I'm aware. Will that be talked about in the upcoming announcement about MUI v7 and v8?

Yeah. I agree! Said it before! V6 was needed but Joy UI is an excellent product! It needs a major release with more than just React 19 Support!
That should be in minor! We need some fixes and above all else a clear roadmap for this package!
I was happy to give the benefit of the doubt to the team but you pushed back almost a Year now your own words!
It's not good! We need a roadmap, and a stable release with some bug fixes!
This is an excellent product and IMHO it should have taken prio over MUI but you know better.
Still it's not professional to say we will look at it in 6 Months 3 times in a row!
It's been over a Year now and the way y talk 2025 will pass and still nothing. Disappointed!

This project simply seems to be abandoned outside of React support which is sad because everywhere I see people talk about it they like Joy UI more than MUI from a design perspective.

This uncertainty is not good. I have designed new library based on Mui/Joy for all developers that there are over 45+ components. Moreover, the company will use this library for whole projects so I'm worried. Maybe, Joy UI could become a theme of Material UI but the theme isn't the only problem. For instance, how will you manage props of Dialog component? There are differences between Joy and Mui. I feel like I made a mistake because of choosing Joy.

I am gonna be honest. I understand how people feel. We just switched to Joy a few Months back.
I don't regret it. Time will tell. The theme is excellent. MUI would require me so much custom work to get what I need.
Joy theme is pure work of art! The component structure is better and the performance as well.
I think the team made a mistake tech wise. Brand value of MUI is immense but they could port JoyUI theming capabilities and branded it as MUI for MUI v6.
They bet on MUI which cost them 1.5 Years and still no MD3 (Don't are personally) and left such a capable lib behind!
Hope JoyUI gets some love soon. I would be happy to support of few fixes and improvements but I see even PR review don't get any support or review get rubbed off. That's just bad attitude.
I think they are betting big in MUI but just like NextJS it is going to take double the time they envisioned and now feel they can't back out.

Well, apparently, Joy UI is as good as dead. They expect users to migrate to MUI when v8 comes out.
I am frankly growing distrustful of MUIs roadmap. Between having been told for an entire year that development would be picked up again up, now both Joy UI and Base UI v5 having been turned into a dead end, and the strange indecisiveness and misaligned planning on whether the latest MUI X was going to support the latest MUI version, my faith in MUI as a whole is rapidly falling apart.
I love the library, have been a long time user of Material UI, Joy UI and Base UI (and recently began exploring the new Base UI). The API for these packages is just amazing to me... But every major release seems to be an attempt to pull the project in a different direction and before that vision is finished, the direction has changed again.
After splitting MUI v6 into v6 and v7, MUI v7 has now been split into MUI v7 and v8, with the Material Design 3 update seemingly planned for v8, but no clear announcement for this, just a brief passing mention that v7 won't include major visual changes. But while that blog post seems to imply MD3 is still the plan, this tweet from last week seems to imply that he plan is to drop Material Design altogether.
Meanwhile, the Base UI documentation still links to v5 and the MUI website completely ignores that Base UI v1 (why is this even v1 again?) exists. So I'd assume new users are still implied to start with v5, but since that's just a dead end and the migration to Base UI v1 seems extremely painful, this seems like a bad recommendation. The only indication to all of this is a warning on the Overview page of the Base UI documentation that links to a blog post, where you have to scroll all the way down then notice a link to the new repository which has a link to the new documentation.
IMO this all shows that MUI has some serious issues with communication, both towards the community (e.g. the state of Joy UI) as well as between different projects within MUI (e.g. MUI and MUI X being seemingly unaware of who's gonna support what, which Base UI is the right Base UI). It's like members of the team aren't even aware of the plans of their own teams.
Plans change, I get that, that is to be expected, but when they do, please communicate that properly and be honest with the users that have decided to put their trust (and money) in you and rely on your packages. That - I feel - is sorely missing here.
Because frankly, I don't know what to do here anymore. We're starting a brand new project from the ground up and are exploring some potential packages (including Base UI). Am I to put my faith in Base UI (v1)? Because this is starting to feel like I'm gambling that I won't end up at a dead end, and looking elsewhere - even if I like the API less - is a much more safe bet.


Missing CODE_OF_CONDUCT.md file

This file ( CODE_OF_CONDUCT.md ) will help future contributors.

#81 was merged. Closing


C++ Recursive Solution to "Swap Nodes in Pairs" on LeetCode under LGMSOC21

Description
C++ Recursive Solution to "Swap Nodes in Pairs" on LeetCode under LGMSOC21.
Fixes #1951
@Amit366 @ravikr126 @Ayush7614
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

Is there any problem with the code that I have to correct? This PR hasn't been merged for long... my more recent level2 PR was merged...
@ravikr126


Prepare Lighthouse client for the merge

Add the configuration required for the Bellatrix upgrade:
Before this update https://github.com/sigp/lighthouse/releases/tag/v2.4.0 (07/22/2022) some flags were another.

[x]  Indicate API engine endpoint

--execution-endpoints

[ ]  JWT authentication for the Engine API

--execution-jwt

[x]  Override TTD flag

--terminal-total-difficulty-override

[x] Update to version 2.4.0 of the client

This configuration has been tested on Ropsnet network successfully.
Repo: https://github.com/tropicar/DAppNodePackage-lighthouse-ropsten

TTD is set up in the Client by itself. So is not required to add the override flag.


Rename Fixers

Closes #889

done

thanks for updating,
:+1:

Then, mergy mergy ? :)

:ship:

Then, mergy mergy ? :)

yeah, like @GrahamCampbell said, ship it :)
:package:


The snapshot doesn't display when switching to 'Active blobs and blobs without current version' view context under 'Flat' mode

Storage Explorer Version: 1.21.0
Build Number: 20210908.7
Branch: rel/1.21.0
Platform/OS: Windows 10/Linux Ubuntu 18.04/MacOS Big Sur 11.4
Architecture: ia32\x64
How Found: From running test case
Regression From: 20210903.4
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Upload one blob -> Create a snapshot for the blob.
Open view options panel -> Select 'Flat' mode -> Hide the view options panel.
Right click the blob -> Click 'Manage History -> Manage Snapshots'.
The blob and its snapshot display in the editor.
Switch the view context to 'Active blobs and blobs without current version' or 'All blobs and blobs without current version'.
Check whether the snapshot still displays.

Expected Experience
The snapshot still displays.
Actual Experience
The snapshot doesn't display.

@JasonYeMsft it looks like a condition check for listing snapshots is probably missing here:

The scenario for this is pretty edge case, so we'll leave this for 1.22 or a possible 1.21.1.

Verified on the latest main build/20210923.3. Fixed.


Update scarlet tutorial

This PR is to resolve #1.
@herjy I just realized that the notebook I've already edited is lsst_stack_deblender.ipynb, not scarlet_tutorial.ipynb. The former is now in this PR.
Which one do you plan to use for your tutorial?

I was rather thinking of the tutorial, it is up to date with some of the convenience functions from scarlet.

But I'm actually fine with both. In any case there will be some editing from my part.

Thanks @herjy!


The asyncDate function gets the params incorrectly

This is my routing structure

The console prints the result when I refresh the page

And then every single page when the jump print the results and expectations do not meet

This seems to be resolved in 1.4.0. Closing. Reopen if still happens.


Client-side tutorial and server sandboxing

It is a no-brainer that a tutorial of some kind would make it much easier for people to get into SS14. Problem however is how do we implement it?
Because our server and client are separate by design, the client does not have the necessary stuff to "play locally". This leaves us with two options:

Load a second map on the game server that people in tutorial get put onto.

This has the problem of getting interrupted by server restarts and other shenanigans like server load.
It would be by far the easiest to implement however.

Have servers expose a downloadable server build as well that clients can download to play the tutorial, by hosting a local server.

Care must be taken if the server wants to have secrets to avoid them leaking, which could add enough development effort that server developers may not want to bother?
This requires the ability to fully sandbox the server.

Which would be best?

The most easy (and not that bad) way one could implement tutorials would be to integrate them into normal gameplay.
Examples:

Make a chemist go through a step by step list of making some chemical.
Make a security officer set an empty cell to 2 minutes.
Make a security officer go to the firing range to tase a dummy.

Special Components could be introduced to mark objects to be usable by a tutorial, eg give the firing range dummy a "TutorialDummy" component to register if someone doing the tutorial shoots it, then tick that box in their tutorial window.
Of course these kinds of Tutorials might get interrupted by surrounding events or even a roundend, but if we were to manage to make the tutorialstate persistent and the tutorial be opened/closed at any time, I don't see an issue:
If we were to take the chemist example again, lets say you were following your tutorial to mix your first Cryomix or whatever, but someone heavily injured comes into your medbay. You could simply pause what you are doing, help the person and continue on later.
Maybe it would make sense to have some kind of indication if someone is new in their department, altough that should be easily rp'd imo.

Those kinds of tutorials would definitely be great, but there are sadly things they can't teach easily. For example combat.
Other problems are people doing them for you. It's hard to learn how to set up the engine if two other engineers already did it for you. Every round.

As for #2, the very basics of gameplay are likely going to remain pretty consistent across servers, so maybe a catch-all tutorial using the "standard" server would work? This doesn't require sandboxing, but also can't teach server-specific mechanics and isn't a win-win.

Why not start with putting a in game item? A book . With a written guide. One for each department. It would at least act as temporary way to convey the basic department responsibilities and help maintain immersion.

Why not start with putting a in game item? A book . With a written guide.

You're about 8 hours late (#10979). Though having an interactive tutorial would still be better.

Why not start with putting a in game item? A book .

This is already supposed to be done in preference over the wiki.


x/mobile/cmd/gomobile: gomobile-build fails due to header-files not found error

What version of Go are you using (go version)?
go version go1.10 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/hajimehoshi/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/hajimehoshi/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7t/qw3np69559591s1v0mk5_p1m0000gn/T/go-build013947351=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
gomobile build -target ios golang.org/x/mobile/example/basic

What did you expect to see?
Build succeeds.
What did you see instead?
Build failed:
gomobile: go build -tags ios -o=/var/folders/7t/qw3np69559591s1v0mk5_p1m0000gn/T/gomobile-work-875171040/arm golang.org/x/mobile/example/basic failed: exit status 2
# golang.org/x/mobile/exp/gl/glutil
go/src/golang.org/x/mobile/exp/gl/glutil/context_darwin_desktop.go:15:9: fatal error: 'OpenGL/OpenGL.h' file not found
#import <OpenGL/OpenGL.h>
        ^~~~~~~~~~~~~~~~~
1 error generated.
# golang.org/x/mobile/app
go/src/golang.org/x/mobile/app/darwin_desktop.go:16:9: fatal error: 'Carbon/Carbon.h' file not found
#import <Carbon/Carbon.h> // for HIToolbox/Events.h
        ^~~~~~~~~~~~~~~~~
1 error generated.

Additional information
$ gomobile version
gomobile version unknown: binary is out of date, re-install it

I removed gomobile and redid go-get, but I couldn't remove this error.

Do you have xcode installed?

Yes.

(CC @eliasnaur)

The above error happened with 54bca6061991cbde3139dc01ec713e2bba9cdb51.
With the previous one 4e3d9b79444693d916d1ae1f1d358cb13ba479e1, the situation changed:
$ gomobile build -target=ios golang.org/x/mobile/example/basic
gomobile: xcrun xcodebuild -configuration Release -project /var/folders/7t/qw3np69559591s1v0mk5_p1m0000gn/T/gomobile-work-221160388/main.xcodeproj -allowProvisioningUpdates DEVELOPMENT_TEAM=JF56W8HGC5 failed: exit status 65
Build settings from command line:
    DEVELOPMENT_TEAM = JF56W8HGC5

=== BUILD TARGET main OF PROJECT main WITH CONFIGURATION Release ===

Check dependencies
2018-04-03 11:25:33.311 xcodebuild[6547:153334]  DVTPortal: Service '<DVTPortalAddAppIDService: 0x7fa2dbfd6100; action='addAppId'>' encountered an unexpected result code from the portal ('9401')
2018-04-03 11:25:33.311 xcodebuild[6547:153334]  DVTPortal: Error:
Error Domain=DVTPortalServiceErrorDomain Code=9401 "An App ID with Identifier 'org.golang.todo.basic' is not available. Please enter a different string." UserInfo={payload=<CFBasicHash 0x7fa2d96ccfb0 [0x7fff9fa5aaf0]>{type = mutable dict, count = 10,
entries =>
        0 : <CFString 0x7fa2dbf7d7d0 [0x7fff9fa5aaf0]>{contents = "requestId"} = <CFString 0x7fa2dc338a30 [0x7fff9fa5aaf0]>{contents = "FDC58D0A-2A94-4CFE-AB6D-86AF0D29B4BA"}
        1 : responseId = <CFString 0x7fa2dc32cf70 [0x7fff9fa5aaf0]>{contents = "af8a5adc-56fc-4053-94f1-ccd31e79d372"}
        2 : <CFString 0x7fff9f97db58 [0x7fff9fa5aaf0]>{contents = "protocolVersion"} = QH65B2
        3 : <CFString 0x7fa2dbf51a00 [0x7fff9fa5aaf0]>{contents = "requestUrl"} = <CFString 0x7fa2dbf6c200 [0x7fff9fa5aaf0]>{contents = "https://developerservices2.apple.com/services/QH65B2/ios/addAppId.action"}
        6 : <CFString 0x7fa2dc344310 [0x7fff9fa5aaf0]>{contents = "userLocale"} = en_US
        8 : resultCode = <CFNumber 0x24b937 [0x7fff9fa5aaf0]>{value = +9401, type = kCFNumberSInt64Type}
        9 : userString = <CFString 0x7fa2dc344b70 [0x7fff9fa5aaf0]>{contents = "An App ID with Identifier 'org.golang.todo.basic' is not available. Please enter a different string."}
        10 : <CFString 0x7fa2dbf57de0 [0x7fff9fa5aaf0]>{contents = "resultString"} = <CFString 0x7fa2dc344b70 [0x7fff9fa5aaf0]>{contents = "An App ID with Identifier 'org.golang.todo.basic' is not available. Please enter a different string."}
        11 : httpCode = <CFNumber 0xc837 [0x7fff9fa5aaf0]>{value = +200, type = kCFNumberSInt64Type}
        12 : <CFString 0x7fa2dc30b9f0 [0x7fff9fa5aaf0]>{contents = "creationTimestamp"} = <CFString 0x7fa2dc3493b0 [0x7fff9fa5aaf0]>{contents = "2018-04-03T02:25:33Z"}
}
, NSLocalizedDescription=An App ID with Identifier 'org.golang.todo.basic' is not available. Please enter a different string.}
Code Signing Error: Failed to create provisioning profile. The app ID "org.golang.todo.basic" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.
Code Signing Error: No profiles for 'org.golang.todo.basic' were found:  Xcode couldn't find any iOS App Development provisioning profiles matching 'org.golang.todo.basic'.
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.3'

** BUILD FAILED **

The following build commands failed:
        Check dependencies
(1 failure)

golang.org/cl/104355 should fix the compilation error.
The gomobile version issue is #24389 stalled on #24558.
The App ID problem is #20241.

I have another similar issue, and I am not sure this is related to #24389 or #24558.
go get -u github.com/hajimehoshi/go-inovation
cd $GOPATH/src/github.com/hajimehoshi/go-inovation
gomobile bind -v -target ios -o ./mobile/ios/Mobile.framework github.com/hajimehoshi/go-inovation/mobile

fails with this message:
# github.com/hajimehoshi/ebiten/internal/devicescale
../ebiten/internal/devicescale/impl_ios.go:22:10: fatal error: 'UIKit/UIKit.h' file not found
 #import <UIKit/UIKit.h>
         ^~~~~~~~~~~~~~~
1 error generated.
# golang.org/x/mobile/gl
In file included from ../../../golang.org/x/mobile/gl/work.go:28:
./work.h:18:10: fatal error: 'OpenGLES/ES2/glext.h' file not found
#include <OpenGLES/ES2/glext.h>
         ^~~~~~~~~~~~~~~~~~~~~~
1 error generated.
gomobile: gobind -lang=go,objc -outdir=/var/folders/7t/qw3np69559591s1v0mk5_p1m0000gn/T/gomobile-work-847470222 -tags=ios github.com/hajimehoshi/go-inovation/mobile failed: exit status 1

git-bisect says 4600df55ca9f03689ade154095e4daf53a00e223 is the cause.


curriculum: Change pre and code to blockquote in Advanced Node and Express challenges

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #35413

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Running out of memory on BeaconStateBellatrix GetTree

I am using this lib to get multiproofs for block_roots in the BeaconState. I download the BeaconState from Prysm, unmarshal the ssz bytes into a BeaconStateBellatrix object, then call GetTree on the object in preparation to get the proof. I keep running out of memory when calling GetTree.
I have made a demo repo to illustrate the issue: https://github.com/claravanstaden/beacon-state-scratchpad The beacon state as download from Prysm is included as a file.
Please let me know if I am doing something wrong?

It might be worthwhile that the unmarshalling is very quick and completes successfully, but converting the BeaconStateBellatrix object to a tree seems problematic.

Hi! I have seen this before.
The part of the trees is not part of the high-performance functions of the library. I think the issue is that with max lists it has to allocate nodes for the max number of entries. When max is big, the number of tree nodes gets too big to allocate the memory. Note that this happens even if the list itself has only one item.
I am not sure there is an immediate solution for that. I did not build that part myself (cc @s1na).
What is your use case?

I've noticed that (on my machine) it completes about hash tree root operations for about 140k validators about of the 400k. So it actually starts hashing the validator set correctly but doesn't complete. Here's the link to where it happens: https://github.com/ferranbt/fastssz/blob/main/spectests/structs_encoding.go#L6076
I am trying to get ancestry proofs for a light client. The light client gets a finalized beacon header update and verifies it. After that, it receives an ancestor of the finalized block and I need to prove that the ancestor block is in fact a grandparent of the finalized block. I want to do this by checking the block_roots field in the BeaconState. So to get the BeaconState proof, I think I need to call GetTree and then 'ProveMulti(with theblock_root generalized` indices that I need to prove)

I tried the demo. It did hash on my side with HashTreeRoot without problems.
For GetTree, it does run out of memory here. In this example, the validators field of the BeaconStateBellatrix has as max number of items<PHONE_NUMBER>776. Go cannot pre-allocate an array that big even when it is half empty (only 399333 validators in the example).

@ferranbt thanks for testing the repo out! 😄
Ok, that makes sense. Maybe I ran into memory issues in a different place because of my local config. I extended Go's max memory limit by changing the GOMEMLIMIT var.
But in any case, I wonder what the solution something like this should be. Maybe there's a different way to get the proof without creating the whole tree. Prysm must have around this issue in some way.

As far as I know, Prysm does not return the proofs.
I am unsure what the solution is, I do not have extensive experience in the proving part to think about an efficient architecture. Let me try to ping @s1na offline to see if he can bring some feedback.

@ferranbt appreciated the help! 😄
Maybe Prysm will support in the future, with beacon API requests like these: https://github.com/ethereum/beacon-APIs/pull/267

Go cannot pre-allocate an array that big even when it is half empty (only 399333 validators in the example).

Is the problem only pre-allocating a large enough block in one piece? we might be able to go around that with some modifications. However if the tree is so big it doesnt fit in memory then basically the tree needs to be re-written to use disk.
What I have in mind for constructing the tree is breaking it into smaller subtrees (we can set a limit for the size of a tree that can be constructed in one piece) and then link those subtries together.

@s1na maybe the subtree option is the more future-proof solution, either way.

Here is another idea. Use the HashTreeRootWith and the ssz.HashWalker interface to create an implementation that takes as input an ssz object and outputs a fieldsRoot object like the one generated by Prysm here.

@ferranbt that would also work! I've been working on a optimised version of the tree.go package and it seems to have resolved the out-of-memory problem. Will open a PR today. 😄

Fixed in #120


api\index.spec.js fails

When I ran npm run test, it tells me I need to run a couple other things. npm run build-main seemed to work fine, and npm run build-renderer took a long time, but ended up working. But after that, when I run the tests, all of them pass except api\index.spec.js:
C:\zap\zap-desktop>npm run test

><EMAIL_ADDRESS>test C:\zap\zap-desktop
> cross-env NODE_ENV=test BABEL_DISABLE_CACHE=1 node --trace-warnings ./test/runTests.js

 PASS  test\reducers\form.spec.js
 PASS  test\reducers\info.spec.js
 PASS  test\reducers\balance.spec.js
 PASS  test\reducers\payment.spec.js
 PASS  test\reducers\channels.spec.js
 PASS  test\reducers\invoice.spec.js
 PASS  test\reducers\ticker.spec.js
 PASS  test\reducers\peers.spec.js
 FAIL  test\api\index.spec.js (10.795s)
  ? API > getinfo > is synced to the chain

    TypeError: Cannot read property 'synced_to_chain' of undefined

      at Object.<anonymous> (test/api/index.spec.js:7:23)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > getinfo > only supports 1 chain at a time

    TypeError: Cannot read property 'chains' of undefined

      at Object.<anonymous> (test/api/index.spec.js:12:23)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > balance > returns wallet balance

    TypeError: Cannot read property 'balance' of undefined

      at Object.<anonymous> (test/api/index.spec.js:19:41)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > balance > returns channel balance

    TypeError: Cannot read property 'balance' of undefined

      at Object.<anonymous> (test/api/index.spec.js:24:42)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > peers > peers is an array

    TypeError: Cannot read property 'peers' of undefined

      at Object.<anonymous> (test/api/index.spec.js:31:38)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > channels > channels is an array

    TypeError: Cannot read property 'channels' of undefined

      at Object.<anonymous> (test/api/index.spec.js:38:41)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > invoices > invoices is an array

    TypeError: Cannot read property 'invoices' of undefined

      at Object.<anonymous> (test/api/index.spec.js:45:41)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ? API > payments > payments is an array

    TypeError: Cannot read property 'payments' of undefined

      at Object.<anonymous> (test/api/index.spec.js:52:41)
          at Generator.next (<anonymous>)
      at step (test/api/index.spec.js:1:323)
      at test/api/index.spec.js:1:483
      at process._tickCallback (internal/process/next_tick.js:109:7)

Test Suites: 1 failed, 8 passed, 9 total
Tests:       8 failed, 94 passed, 102 total
Snapshots:   51 passed, 51 total
Time:        12.811s
Ran all test suites matching "test\\(?!e2e\\)[^\\]+\\.+\.spec\.js$".

I'm on a windows 8.1 machine with node v7.10.0

Hm, interesting. The API tests failed, which means something is up with the nodejs repo or your BTCD/LND.
Do you have BTCD, LND and zap-nodejs up and running?

Oh I didn't have either the bitcoin daemon or the LN daemon up. My ad-blindness made me miss that greyed out note in the readme. The only requirements I payed attention to are the bolded bullet points. I'll edit the readme to be a bit more consistent in how requirements are listed.

https://github.com/LN-Zap/zap-desktop/pull/3

I suppose there should be something it does to detect which requirement isn't available and properly report this in the test


opensmtpd: 6.4.0p1 -> 6.4.0p2

Motivation for this change
Should fix the issues mentioned at https://github.com/NixOS/nixpkgs/pull/48901#issuecomment-435838142 and after, and on IRC.
See upstream https://github.com/OpenSMTPD/OpenSMTPD/issues/886
cc @obadz @rickynils @the-kenny @Izorkin
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test opensmtpd

Success on aarch64-linux (full log)
Attempted: opensmtpd
Partial log (click to expand)
shrinking /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/libexec/opensmtpd/mail.lmtp
shrinking /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/sbin/smtpctl
shrinking /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/sbin/smtpd
/nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2
gzipping man pages under /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/libexec  /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/bin  /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/sbin
patching script interpreter paths in /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2
checking for references to /build in /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2...
moving /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/sbin/* to /nix/store/xq5cnzxfw4ad6cmljkfffvs5s134qif0-opensmtpd-6.4.0p2/bin

Success on x86_64-linux (full log)
Attempted: opensmtpd
Partial log (click to expand)
shrinking /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/libexec/opensmtpd/mail.maildir
shrinking /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/sbin/smtpd
shrinking /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/sbin/smtpctl
gzipping man pages under /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/libexec  /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/bin  /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/sbin
patching script interpreter paths in /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2
checking for references to /build in /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2...
moving /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/sbin/* to /nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2/bin
/nix/store/vyv90gc4i8yf5p3bdjihpms3fi0sk9y9-opensmtpd-6.4.0p2

Thanks, worked.

Failure on x86_64-linux (full log)
Attempted: tests.opensmtpd
Partial log (click to expand)
error: timed out waiting for the VM to connect
timed out waiting for the VM to connect
cleaning up
killing client (pid 600)
killing smtp2 (pid 612)
killing smtp1 (pid 624)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
builder for '/nix/store/fqrgm6lgi4lhacsb83zw64h413wy243n-vm-test-run-opensmtpd.drv' failed with exit code 4
error: build of '/nix/store/fqrgm6lgi4lhacsb83zw64h413wy243n-vm-test-run-opensmtpd.drv' failed

Success on aarch64-linux (full log)
Attempted: tests.opensmtpd
Partial log (click to expand)
client: running command: sync
client: exit status 0
test script finished in 473.72s
cleaning up
killing smtp2 (pid 631)
killing smtp1 (pid 643)
killing client (pid 656)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/xbzgbxsm575gbgihs6m7i081dkri5jb8-vm-test-run-opensmtpd

Success on x86_64-linux (full log)
Attempted: tests.opensmtpd
Partial log (click to expand)
client: running command: sync
client: exit status 0
test script finished in 35.61s
cleaning up
killing smtp2 (pid 597)
killing smtp1 (pid 609)
killing client (pid 621)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/x6ph8d5l93va8rfbr8biyhj9dr7a0vpy-vm-test-run-opensmtpd


Prevent focus moving to preview window and bugfix

Bugfix:

pwin_prev_buf is not a valid bufnr if sending content to preview window when preview window is already opened

This PR is ready for review. I'm not in an environment that can use git CLI to push and manage branch so I have to use web editor. Sorry for the messy commits. Please use squash merge if possible.


Proper Exit codes

Make sure that the program exits with appropriate error codes and helpful error messages (stderr) in all cases. If there are no errors, exit with 0. Otherwise, exit with a non-zero exit code (e.g., 1).

closed by https://github.com/KrinsKumar/Scrappy/commit/947c74d89adf6b526924f7ba9a002641841a3d05


Extend Addition node rules

This PR includes new rules for computing the marginal and messages when all "interfaces" are of UnivariateNormalDistributionsFamily type.

@albertpod Please review my changes as well.


Not finding commands in jar

So, as I'm preparing my bot for JDA 5 and 2.3.0 of JDA-Commands, I have noticed that my current CI/CD breaks when packaging the bot in a jar file (runs normally when not running it as a jar file). It breaks in form of not finding any Commands anymore. In Version 2.2.0 this wasn't an issue and worked flawlessly.
Here's the code with which I start my Bot:
String[] packages = {"main.discord.commands", "main.api.jdaCommands"};
JDACommands commands = JDACommands.start(manager, Main.class, packages);

I've also included my debug level log file as well as my info level log file in case you need it. (Bot related stuff should start after "Starting JDA-Commands")
debug.log
info.log

Just tested with the newest commit of branch dev-jda5. Seems to still be the case. Reflections keeps responding with "producing 0 keys and 0 values"

we had this issue already in the past, see #18. Interesting to have it back. iirc I've updated reflections recently, so maybe downgrading again will do the trick

I've found this GitHub Issue on the reflections repository: https://github.com/ronmamo/reflections/issues/373
Maybe It'll help

Thanks. I'll try to reproduce the bug and then try to apply the workaround and otherwise I should consider to pick [this project] (https://github.com/Kaktushose/mirror) up again

Or maybe we should move away from using runtime reflections at all

Version 4.0.0-alpha.1 implements the fix found https://github.com/ronmamo/reflections/issues/373. If this error persists feel to open a new issue


UI Enhancements

Would it be possible to make the program look prettier?

Yes it is possible but why ?

@SowBiT The UI is really ugly.

@SnowBiT Something like this:
File > Open...
File > Open folder
File > Export > Selected
File > Export > All
File > Exit
Edit > Copy
Edit > Cut
Edit > Paste
Edit > Select All
Edit > Preferences
Debug > Show All
Debug > Export > Logs
Debug > Export > Raw

It would be possible, but I'm not good at designing the user interface

@Perfare If I were to design a user interface, could you apply it?

@Stellarspace how good are you at deigning/implementing UI?  Do you have any examples of UI's you did?


How to use js to release tconsole？

var c = new Console();
//How to release here？
delete c;//?
c = null;//?

c = null; works, as well as c = 42;. Just by assigning the variable a different value the previously stored instance's reference count is automatically decreased by ChakraCore, and later when the garbage collector sees 0 reference count it will call the registered finalizer callback which in turn frees the instance.

c=null;
But this does not release the object!

c=null;
But this does not release the object!

Not immediately - but that's by design. GC releases the object eventually. (It might be a good idea to extend the test suite with a proof.)
If you think you've found a bug please provide a MCVE.
Thanks!

I don't see where to call TNativeObject.AddRef and TNativeObject.Release！
In my opinion, is TNativeObject designed as an interface more appropriate?
Because now you don't have to call JsDisposeRuntime and all of your new objects won't be thrown!

Maybe my idea is not necessarily correct, maybe you have other better way!

procedure Main;
var
DataModule: TDataModuleMain;
begin
ShowInfo;
DataModule := TDataModuleMain.Create(nil);
try
DataModule.Execute(ParamStrings);
ReadLn; //At this point, new Console() is not released
finally
DataModule.Free;
//When you get here, new Console() is released
end;
end;

I'm closing this issue with "works as designed". Please see the new finalizer tests in 48bea58.


Type Script Definitions not working

Ran command "npx codeceptjs def" to get type script definitions
Instead of complete list of definitions found small bit of code mentioned below in steps.d.ts file. (Nothing in steps_file.js as well)
------>
**type steps_file = typeof import('./steps_file.js');
declare namespace CodeceptJS {
interface SupportObject { I: CodeceptJS.I }
interface CallbackOrder { [0]: CodeceptJS.I }
interface Methods extends CodeceptJS.WebDriver {}
interface I extends ReturnType<steps_file> {}
namespace Translation {
interface Actions {}
}
}**
<------------------
Console output --- "TypeScript Definitions provide autocompletion in Visual Studio Code and other IDEs
Definitions were generated in steps.d.ts"
# paste output here

Provide test source code if related

// paste test

Details

CodeceptJS version: Latest
NodeJS Version: Latest
Operating System: Windows
webdriverio

Below is Config file:
exports.config = {
tests: './*_test.js',
output: './output',
timeout: 1000,
helpers: {
WebDriver: {
url: 'https://xha-qa.hexagonxalt.net/',
browser: 'chrome'
}
},
include: {
I: './steps_file.js'
},
bootstrap: null,
mocha: {},
name: 'XALT_XHA_Codecept',
plugins: {
retryFailedStep: {
enabled: true
},
screenshotOnFail: {
enabled: true
}
}
}

Alrighty I have the same issue.
Workaround, set your codeceptjs version to 2.3.5. Everything >2.3.5 is broken.

Hello all,
Does this issue still exist ?
I have codeceptjs version 3.2.0. For me initially this was working but I made some changes in the config files and suddenly it stopped working.
Could anyone please help me with the same ?

@SDETDeven , what changes did you do?
which error are you getting?

The answer to this is to have this stanza your .tsconfig file
"ts-node":{
"files":true
},
--files is a flag to ts-node to make it pick up these types.


states and events with bogus unit recorded when sensor unavailable

Home Assistant release with the issue:
0.101.3
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Fedora 30, python 3.7, venv, pip
Integration:
ESPHome
Description of problem:
I have a ESPHome instance with a simple DHT22 sensor. It measures temperature in °C, but the sensor in HA uses °F, presumably because I have unit_system configured for imperial.
The problem occurs when the ESPHome device is temporarily unavailable. During those times, states and events are recorded in the database where the state is unavailable or unknown (maybe OK), but the unit_of_measurement is recorded as °C instead of °F. This causes the History Graph card in lovelave to get mightily confused, making it draw two graphs for the sensor (one with each unit of measurement). Perhaps it could be argued that the lovelace card should discard any states where the value is not a number, but it still seems very wrong for the bogus unit of measurement to be recorded.
sqlite> select last_updated, state, json_extract(attributes, '$.unit_of_measurement') from states where entity_id='sensor.garage_temperature' and last_updated between '2019-11-14 06:45' and '2019-11-14 07:00';
2019-11-14 06:48:06.976306|72.1|°F
2019-11-14 06:48:51.612151|unavailable|°C
2019-11-14 06:49:24.011967|unknown|°C
2019-11-14 06:49:53.405900|72.0|°F
2019-11-14 06:50:53.424571|72.1|°F
2019-11-14 06:53:53.412091|72.3|°F
2019-11-14 06:54:53.421104|72.1|°F
2019-11-14 06:56:56.692008|unavailable|°C
2019-11-14 06:57:29.065742|72.3|°F
2019-11-14 06:57:50.613364|72.1|°F
2019-11-14 06:58:50.614127|72.3|°F
2019-11-14 06:59:50.616945|72.1|°F
sqlite> select time_fired, json_extract(event_data, '$.new_state.state', '$.new_state.attributes.unit_of_measurement') from events where json_extract(event_data, '$.entity_id') = 'sensor.garage_temperature' and time_fired between '2019-11-14 06:45' and '2019-11-14 07:00';
2019-11-14 06:48:06.976367|["72.1","\u00b0F"]
2019-11-14 06:48:51.612231|["unavailable","\u00b0C"]
2019-11-14 06:49:24.012019|["unknown","\u00b0C"]
2019-11-14 06:49:53.405960|["72.0","\u00b0F"]
2019-11-14 06:50:53.424624|["72.1","\u00b0F"]
2019-11-14 06:53:53.412149|["72.3","\u00b0F"]
2019-11-14 06:54:53.421165|["72.1","\u00b0F"]
2019-11-14 06:56:56.692027|["unavailable","\u00b0C"]
2019-11-14 06:57:29.065783|["72.3","\u00b0F"]
2019-11-14 06:57:50.613426|["72.1","\u00b0F"]
2019-11-14 06:58:50.614202|["72.3","\u00b0F"]
2019-11-14 06:59:50.617008|["72.1","\u00b0F"]
sqlite>

In the above case, I had OTA-updated the ESPHome instance at 06:56, shortly after physically relocating it (causing a brief interruption) around 06:48.
hass log (timestamps in PST):
Nov 13 22:48:51 hass.mydomain.com hass[16324]: 2019-11-13 22:48:51 INFO (MainThread) [aioesphomeapi.connection] d1_mini_1: Ping Failed!
Nov 13 22:48:51 hass.mydomain.com hass[16324]: 2019-11-13 22:48:51 INFO (MainThread) [homeassistant.components.esphome] Disconnected from ESPHome API for d1_mini_1
Nov 13 22:48:51 hass.mydomain.com hass[16324]: 2019-11-13 22:48:51 INFO (MainThread) [aioesphomeapi.connection] d1_mini_1: Error while reading incoming messages: Error while receiving data: 0 bytes read on a total of 1 expected bytes
Nov 13 22:49:21 hass.mydomain.com hass[16324]: 2019-11-13 22:49:21 INFO (MainThread) [homeassistant.components.esphome] Can't connect to ESPHome API for d1_mini_1: Timeout while connecting to ('x.x.x.x', 6053)
Nov 13 22:49:21 hass.mydomain.com hass[16324]: 2019-11-13 22:49:21 INFO (MainThread) [homeassistant.components.esphome] Trying to reconnect in 2 seconds
Nov 13 22:49:23 hass.mydomain.com hass[16324]: 2019-11-13 22:49:23 INFO (MainThread) [homeassistant.components.esphome] Successfully connected to d1_mini_1
Nov 13 22:52:48 hass.mydomain.com hass[16324]: 2019-11-13 22:52:48 INFO (MainThread) [aioesphomeapi.connection] esp32s_1: Error while reading incoming messages: Error while receiving data: 0 bytes read on a total of 1 expected bytes
Nov 13 22:52:48 hass.mydomain.com hass[16324]: 2019-11-13 22:52:48 INFO (MainThread) [homeassistant.components.esphome] Successfully connected to esp32s_1
Nov 13 22:56:56 hass.mydomain.com hass[16324]: 2019-11-13 22:56:56 INFO (MainThread) [homeassistant.components.esphome] Disconnected from ESPHome API for d1_mini_1
Nov 13 22:56:59 hass.mydomain.com hass[16324]: 2019-11-13 22:56:59 INFO (MainThread) [aioesphomeapi.connection] d1_mini_1: Ping Failed!
Nov 13 22:57:26 hass.mydomain.com hass[16324]: 2019-11-13 22:57:26 INFO (MainThread) [homeassistant.components.esphome] Can't connect to ESPHome API for d1_mini_1: Timeout while connecting to ('x.x.x.x', 6053)
Nov 13 22:57:26 hass.mydomain.com hass[16324]: 2019-11-13 22:57:26 INFO (MainThread) [aioesphomeapi.connection] d1_mini_1: Unexpected error while reading incoming messages: 'NoneType' object has no attribute 'readexactly'
Nov 13 22:57:26 hass.mydomain.com hass[16324]: 2019-11-13 22:57:26 INFO (MainThread) [homeassistant.components.esphome] Trying to reconnect in 2 seconds
Nov 13 22:57:28 hass.mydomain.com hass[16324]: 2019-11-13 22:57:28 INFO (MainThread) [homeassistant.components.esphome] Successfully connected to d1_mini_1

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
ESPHome sensor definition:
sensor:
  - platform: dht
    model: DHT22
    pin: D1
    temperature:
      name: "Garage Temperature"
    humidity:
      name: "Garage Humidity"
    update_interval: 60s

Additional information:
I'm guessing that there's a unit translation that happens for each sensor event, but that translation is not reached in the case where the value is non-numeric, and the unit from the sensor gets passed through, instead of that from the unit_system

Correct, the line that causes this is here:
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/helpers/entity.py#L370-L384
IMO, this is a core problem and not specific to ESPHome. But you can also solve this on the ESPHome side by converting the unit to metric there (see sensor page).

Ahh, thanks for the pointer... I hadn't gotten around to digging in the code yet. Agree that it seems like a core problem, in that it could affect other entities.

Don't know if it's a good solution, but moving the unit setting outside the try/except (so it happens even if the number conversion fails) works around the issue for me.
diff --git a/homeassistant/helpers/entity.py b/homeassistant/helpers/entity.py
index 0d2182f88..632197189 100644
--- a/homeassistant/helpers/entity.py
+++ b/homeassistant/helpers/entity.py
@@ -378,10 +378,10 @@ class Entity:
                 prec = len(state) - state.index(".") - 1 if "." in state else 0
                 temp = units.temperature(float(state), unit_of_measure)
                 state = str(round(temp) if prec == 0 else round(temp, prec))
-                attr[ATTR_UNIT_OF_MEASUREMENT] = units.temperature_unit
         except ValueError:
             # Could not convert state to float
             pass
+        attr[ATTR_UNIT_OF_MEASUREMENT] = units.temperature_unit

         if (
             self._context is not None

Better ideas??

This is still an issue in 0.105.3

Grumble.  This is still an issue.


SIGSEGV: Illegal storage access. (Attempt to read from nil?)

Hello, I tried to use sgcocaller v0.3.7 to detect COs in gametes using scRNA sequences from pollens, and our reference genome was phased. Here is the command I ran:
dir_to_sgcocaller/bin/sgcocaller xo --threads 8 --cmPmb 1 --phased merged.bam informative_SNPs.recode.vcf cb.list myprefix

Then I got an error as follows:
{"<barcodeFile>": cb.list, "<BAM>": merged.bam, "--binSize": 2000, "<referenceVCF>": nil, "phase": false, "--lookBeyondSnps": 25, "--thetaREF": 0.1, "--outvcf": false, "--baseq": 13, "--minMAPQ": 20, "--threads": 8, "--stepSize": 200, "--cmPmb": 1, "--chrom": nil, "--minPositiveSwitchScores": 8, "--minSwitchScore": 50.0, "<VCF>": informative_SNPs.recode.vcf, "<gtMtxFile>": nil, "--barcodeTag": CB, "<phasedSnpAnnotFile>": nil, "sxo": false, "--maxExpand": 1000, "--maxTotalDP": 25, "xo": true, "--phased": true, "--templateCell": -1, "--help": false, "<SNPPhaseFile>": nil, "--maxDP": 5, "--minDP": 1, "--minTotalDP": 10, "--maxDissim": 0.0099, "swphase": false, "--posteriorProbMin": 0.99, "--minSNPdepth": 1, "--thetaALT": 0.9, "<out_prefix>": rbrevi_test, "<phaseOutputPrefix>": nil}
SIGSEGV: Illegal storage access. (Attempt to read from nil?)

The error message looks like from Nim, which I am not quite familiar with. Can you give me a clue about how to solve this?

Hi, I guess it is because it didn't find the input files at the given path? and I found if the output prefix contain dirs like a/b/prefix, when the sub directories don't exist it throws error like that. Perhaps if you could share your files with me and I can have a closer look? Best,RL-------- Original message --------From: Meng Zhang @.>Date: Thu, Jul 21, 2022, 02:01To: ruqianl/sgcocaller @.>Cc: Subscribed @.***>Subject: [ruqianl/sgcocaller] SIGSEGV: Illegal storage access. (Attempt to read from nil?) (Issue #2)
Hello, I tried to use sgcocaller v0.3.7 to detect COs in gametes using scRNA sequences from pollens, and our reference genome was phased. Here is the command I ran:
dir_to_sgcocaller/bin/sgcocaller xo --threads 8 --cmPmb 1 --phased merged.bam informative_SNPs.recode.vcf cb.list myprefix
Then I got an error as follows:
{"": cb.list, "": merged.bam, "--binSize": 2000, "": nil, "phase": false, "--lookBeyondSnps": 25, "--thetaREF": 0.1, "--outvcf": false, "--baseq": 13, "--minMAPQ": 20, "--threads": 8, "--stepSize": 200, "--cmPmb": 1, "--chrom": nil, "--minPositiveSwitchScores": 8, "--minSwitchScore": 50.0, "": informative_SNPs.recode.vcf, "": nil, "--barcodeTag": CB, "": nil, "sxo": false, "--maxExpand": 1000, "--maxTotalDP": 25, "xo": true, "--phased": true, "--templateCell": -1, "--help": false, "": nil, "--maxDP": 5, "--minDP": 1, "--minTotalDP": 10, "--maxDissim": 0.0099, "swphase": false, "--posteriorProbMin": 0.99, "--minSNPdepth": 1, "--thetaALT": 0.9, "<out_prefix>": rbrevi_test, "": nil}
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
The error message looks like from Nim, which I am not quite familiar with. Can you give me a clue about how to solve this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hello,
Thank you for the response, but I am sure that files and directories are accessible. I will send you some test data I currently use.

Hi, I'm very interested in using this tool. I also get an identical issue to this, using 0.3.9. I tried installing prior versions (0.3.6, 0.3.4 and 0.3.3) all using conda.
./sgcocaller xo \

--phased
--cmPmb 0.0001
possorted_genome_bam.bam
Cross.filt.recal.vcf
barcodes.tsv
BULK_1_sgco
2022-11-02T12:41:15-05:00{"": barcodes.tsv, "": possorted_genome_bam.bam, "--binSize": 2000, "--dissimThresh": 0.0099, "--notSortMtx": false, "": nil, "phase": false, "--lookBeyondSnps": 25, "--thetaREF": 0.1, "--outvcf": false, "--baseq": 13, "--minMAPQ": 20, "--threads": 4, "--stepSize": 200, "--cmPmb": 0.0001, "--chrom": nil, "--minPositiveSwitchScores": 8, "--minSwitchScore": 50.0, "": Cross.filt.recal.vcf, "": nil, "--barcodeTag": CB, "--maxUseNcells": nil, "": nil, "--maxExpand": 1000, "sxo": false, "autophase": false, "--maxTotalDP": 25, "xo": true, "--batchSize": nil, "--phased": true, "--templateCell": -1, "--help": false, "": nil, "--maxDP": 5, "--minDP": 1, "--minTotalDP": 10, "--maxDissim": 0.0099, "swphase": false, "--posteriorProbMin": 0.99, "--minSNPdepth": 1, "--thetaALT": 0.9, "<out_prefix>": BULK_1_sgco, "": nil}
2022-11-02T12:41:15-05:00 running sgcocaller 0.3.9
SIGSEGV: Illegal storage access. (Attempt to read from nil?)

I installed on both a linux cluster, and a WSL version of Ubuntu locally and get the same issue. File path does not appear to be the issue for me
I then tried installing from source though ran into an error here also:
nimble install https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git
Downloading https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git using git
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on docopt@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on regex@>= 0.11.1 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on unicodedb@>= 0.7.2 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on hts@>= 0.3.4 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on https://github.com/ruqianl/distributions.git@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Installing<EMAIL_ADDRESS>Building sgcocaller/sgcocaller using c backend
Prompt: Build failed for<EMAIL_ADDRESS>would you like to try installing 'https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git@#head' (latest unstable)? [y/N]
Answer:
Tip: 12 messages have been suppressed, use --verbose to show them.
Error: Aborting installation due to build failure
ianc@PC51:~$ nimble install https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git --verbose
Downloading https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git using git
Cloning latest tagged version: v0.3.9
Info /tmp/nimble_1192/gitlabsvieduau_biocellgenpublicsgcocallergit/sgcocaller_1192.nims(5, 22) Warning: imported and not used: 'strutils' [UnusedImport]
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for docopt@any version
Info: Dependency on docopt@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for regex@>= 0.11.1
Info: Dependency on regex@>= 0.11.1 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for unicodedb@>= 0.7.2
Info: Dependency on unicodedb@>= 0.7.2 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for hts@>= 0.3.4
Info: Dependency on hts@>= 0.3.4 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for https://github.com/ruqianl/distributions.git@any version
Info: Dependency on https://github.com/ruqianl/distributions.git@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Installing<EMAIL_ADDRESS>Building sgcocaller/sgcocaller using c backend
Prompt: Build failed for<EMAIL_ADDRESS>would you like to try installing 'https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git@#head' (latest unstable)? [y/N]
Answer: y
Downloading https://gitlab.svi.edu.au/biocellgen-public/sgcocaller.git using git
Info /tmp/nimble_1192/gitlabsvieduau_biocellgenpublicsgcocallergit_#head/sgcocaller_1192.nims(5, 22) Warning: imported and not used: 'strutils' [UnusedImport]
Verifying dependencies for sgcocaller@#head
Reading official package list
Checking for docopt@any version
Info: Dependency on docopt@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for regex@>= 0.11.1
Info: Dependency on regex@>= 0.11.1 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for unicodedb@>= 0.7.2
Info: Dependency on unicodedb@>= 0.7.2 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for hts@>= 0.3.4
Info: Dependency on hts@>= 0.3.4 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Reading official package list
Checking for https://github.com/ruqianl/distributions.git@any version
Info: Dependency on https://github.com/ruqianl/distributions.git@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Installing sgcocaller@#head
Building sgcocaller/sgcocaller using c backend
Error: Build failed for package: sgcocaller
... Details:
... Execution failed with exit code 1
... Command: "/usr/bin/nim" c --noNimblePath -d:NimblePkgVersion=0.3.5 -d:release --path:"/home/ianc/.nimble/pkgs/docopt-0.7.0"  --path:"/home/ianc/.nimble/pkgs/regex-0.20.0"  --path:"/home/ianc/.nimble/pkgs/unicodedb-0.10.0"  --path:"/home/ianc/.nimble/pkgs/hts-0.3.23"  --path:"/home/ianc/.nimble/pkgs/distributions-0.1.0"  -o:"/tmp/nimble_1192/gitlabsvieduau_biocellgenpublicsgcocallergit_#head/sgcocaller" "/tmp/nimble_1192/gitlabsvieduau_biocellgenpublicsgcocallergit_#head/src/sgcocaller.nim"
... Output: Hint: used config file '/etc/nim/nim.cfg' [Conf]
... Hint: system [Processing]
... Hint: widestrs [Processing]
... Hint: io [Processing]
... Hint: sgcocaller [Processing]
... Hint: os [Processing]
... Hint: strutils [Processing]
... Hint: parseutils [Processing]
... Hint: math [Processing]
... Hint: bitops [Processing]
... Hint: macros [Processing]
... Hint: algorithm [Processing]
... Hint: unicode [Processing]
... Hint: pathnorm [Processing]
... Hint: osseps [Processing]
... Hint: posix [Processing]
... Hint: times [Processing]
... Hint: options [Processing]
... Hint: typetraits [Processing]
... Hint: docopt [Processing]
... Hint: regex [Processing]
... Hint: tables [Processing]
... Hint: hashes [Processing]
... Hint: sequtils [Processing]
... Hint: types [Processing]
... Hint: sets [Processing]
... Hint: properties [Processing]
... Hint: properties_data [Processing]
... Hint: common [Processing]
... Hint: compiler [Processing]
... Hint: parser [Processing]
... Hint: exptype [Processing]
... Hint: scanner [Processing]
... Hint: exptransformation [Processing]
... Hint: nfatype [Processing]
... Hint: litopt [Processing]
... Hint: nodematch [Processing]
... Hint: types [Processing]
... Hint: types_data [Processing]
... Hint: nfa [Processing]
... Hint: deques [Processing]
... Hint: nfafindall [Processing]
... Hint: nfamatch [Processing]
... Hint: util [Processing]
... Hint: hts [Processing]
... Hint: utils [Processing]
... Hint: hts_concat [Processing]
... /home/ianc/.nimble/pkgs/hts-0.3.23/hts/private/hts_concat.nim(127, 9) Error: undeclared identifier: 'csize_t'


Update mrtk-porting-guide.md

Docs Build status updates of commit 055faca:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mrtk-porting-guide.md
:warning:Warning
View
Details

mixed-reality-docs/mrtk-porting-guide.md

[Warning] Author author:grbury cannot be recognized in GitHub.

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


Add export default types at package.json

First of all, Thanks cjk-slug.  I am using cjk-slug very well! 😄

I created native esm with typescript project. and I imported cjk-slug in typescript file. but d.ts cannot imported.
package.json
{
  ...
  "type": "module"
  ...
}

tsconfig.json
{
  "compilerOptions": {
    ...
    /* Language and Environment */
    "target": "ESNext" /* Set the JavaScript language version for emitted JavaScript and include compatible library declarations. */,

    /* Modules */
    "module": "NodeNext" /* Specify what module code is generated. */,
    "moduleResolution": "NodeNext" /* Specify how TypeScript looks up a file from a given module specifier. */,
    ...
  }
}

so, I searched a document.
as the document, I tried to update export map for d.ts.
"exports": {
    ".": {
      "require": {
        "types": "./lib/index.d.ts",
        "default": "./lib/index.cjs"
      },
      "import": {
        "types": "./lib/index.d.ts",
        "default": "./lib/index.mjs"
      },
      "types": "./lib/index.d.ts"
    },
    "./package.json": "./package.json"
  },

but I failed build for using export conditional object which have types.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received an instance of Object

so I added export default types.
"exports": {
    ".": {
      "require": "./lib/index.cjs",
      "import": "./lib/index.mjs",
      "types": "./lib/index.d.ts"
    },
    "./package.json": "./package.json"
  },

This may not good answer for the issue. but I hope it helps through this pr.

I don't know why there is no conflict. Closed as this has already been fixed.


Float Input to

The following is the example in the documentation for comparison of tweets. I wish to use similar set up for feature vector comparison. There are two feature vector has 100 attributes describing facial features of a person like Asian, Indian etc. The quantities are in float numbers.
The goal is to identify if two feature vectors are of same person or not.
However, in the example below, the input is discrete in 256 dimensions.
Please tell me how to remodel the same for my problem.
Many Thanks
from keras.layers import Input, LSTM, Dense, merge
from keras.models import Model
tweet_a = Input(shape=(140, 256))
tweet_b = Input(shape=(140, 256))
shared_lstm = LSTM(64)
encoded_a = shared_lstm(tweet_a)
encoded_b = shared_lstm(tweet_b)
merged_vector = merge([encoded_a, encoded_b], mode='concat', concat_axis=-1)
predictions = Dense(1, activation='sigmoid')(merged_vector)
model = Model(input=[tweet_a, tweet_b], output=predictions)
model.compile(optimizer='rmsprop',
loss='binary_crossentropy',
metrics=['accuracy'])
model.fit([data_a, data_b], labels, nb_epoch=10)

It's basically the same, except that you want to do regression, see #2399 for an example.

Thanks rpinsler for quick response.
I didn't understand the link you have sent. I will explain it again. I have set of instances <feature vector 1, feature vector 2>. Each feature vector has 100 attributes with floating values. The labels are <0,1> describing both feature vector belong to same person or not. In the example I quoted, it shows the tweet, feature attribute is one out of 256 values. In my case each attribute can have floating number. I need to know how should I be training my NN for this

Yeah, I realized it wasn't helpful, which is why I have deleted it in the meantime :) I think the above example is very similar to what you want to do. Since you don't have time-dependencies your input shape is simply Input(shape=(100,)). Furthermore, you have to replace the LSTM, e.g. by Dense layers.

Hi,
I tried that as suggested, but I am getting this error
when running
model.fit([data_a, data_b], labels, nb_epoch=10)
Input dimension mis-match. (input[0].shape[1] = 2, input[1].shape[1] = 1)


cmd/compile: missing write barrier on zeroing/assigning global

What version of Go are you using (go version)?
tip (go version devel +47d2a4dafa Mon Feb 6 07:21:14 2017 +0000 darwin/amd64)
For this code
type T struct {
        p *int
}

var t T

func f() {
        t = T{}
}

the compiler does not generate write barrier.
before f
.   AS l(10) tc(1)
.   .   NAME-main.t u(1) a(true) l(7) x(0) class(PEXTERN) tc(1) assigned main.T
.   .   STRUCTLIT l(10) tc(1) main.T
.   .   .   TYPE main.T u(1) a(true) l(3) x(0) class(PEXTERN) tc(1) type=main.T main.T main.T
after walk f
.   EMPTY-init
.   .   AS u(2) l(10) tc(1)
.   .   .   NAME-main.t u(1) a(true) l(7) x(0) class(PEXTERN) tc(1) assigned main.T
.   EMPTY u(100) l(10) tc(1)
.   .   NAME-main.t u(1) a(true) l(7) x(0) class(PEXTERN) tc(1) assigned main.T

   	00000 (x.go:9)	TEXT	"".f(SB)
   	00001 (x.go:9)	FUNCDATA	$0, "".gcargs·0(SB)
   	00002 (x.go:9)	FUNCDATA	$1, "".gclocals·1(SB)
v8	00003 (x.go:10)	MOVQ	$0, "".t(SB)
b1	00004 (x.go:11)	RET

But I believe it should have write barrier for the new hybrid barrier.
cc @aclements

CL 36530 pending for cherry-pick. Then this bug should be moved to Go 1.9 for the followup CL.

The new write barrier insertion in SSA shouldn't have this problem. Closing.


PXT7972TA13MAC:kafka-streams-examples user$ docker-compose up

PXT7972TA13MAC:kafka-streams-examples user$ docker-compose up
Pulling zookeeper (confluentinc/cp-zookeeper:5.4.0-SNAPSHOT)...
ERROR: manifest for confluentinc/cp-zookeeper:5.4.0-SNAPSHOT not found
PXT7972TA13MAC:kafka-streams-examples user$
Originally posted by @87abhii in https://github.com/confluentinc/kafka-streams-examples/issues/66#issuecomment-504799054

@87abhii Were you running this on master? Please try checking out the latest stable branch (5.3.0-post) and running it, you should not see this error. (The instructions used to say to checkout master but have been fixed to point to the correct branch, let me know if you see "checkout master" anywhere else -- this is a dev branch and in general is not intended for use)
Let me know if you continue to see an error on 5.3.0-post, otherwise I will close this issue.

Closing this due to inactivity.


ruff: 0.6.8 -> 0.6.9

Things done
Changelog: https://github.com/astral-sh/ruff/releases/tag/0.6.9

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] 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
[ ] 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.

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

2 packages marked as broken and skipped:

khoj
khoj.dist

109 packages built:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
marimo (python312Packages.marimo)
marimo.dist (python312Packages.marimo.dist)
nbqa
nbqa.dist
open-webui
open-webui.dist
openapi-python-client
openapi-python-client.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-ollama
python311Packages.langchain-ollama.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python311Packages.langgraph.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.marimo
python311Packages.marimo.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-ollama
python312Packages.langchain-ollama.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist
python312Packages.langgraph.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist
shell-gpt
shell-gpt.dist
vunnel
vunnel.dist

nixpkgs-review result
Generated using nixpkgs-review.