Provide tau constant, include unicode aliases in spec

Related pull requests:
https://github.com/perl6/roast/pull/81
https://github.com/rakudo/rakudo/pull/614

In my 5 years career as a physicist I never once encountered Tau in the real world, so I'd rather see this done in a module than in core Perl 6.

A module to provide 1 constant seems overkill.
The argument of not having seen it in the wild is a very weak one. Perl 6 includes a lot of new things that you probably haven't seen in the wild before Perl 6 started providing them.

Well, the stuff that Perl 6 provides and that I haven't seen in the wild isn't trivially composable from the usual components.

I'd rather see this done in a module than in core Perl 6.

It already exists too: http://modules.perl6.org/repo/Math::Tau

On Thu, Dec 3, 2015 at 10:28 AM, Juerd Waalboer<EMAIL_ADDRESS>wrote:

A module to provide 1 constant seems overkill.

That would seem to argue Perl 6 should include every possible constant
anyone might be interested in.  Which is a pretty daft notion, IMO.
If having a super short module is too much for you to contemplate, how
about creating Math::Constants and including a few other interesting
constants with it?
--
Solomon Foster<EMAIL_ADDRESS>HarmonyWare, Inc: http://www.harmonyware.com

Yes, including every possible constant would indeed be a pretty daft notion. Note that this patch is not about every possible constant, it is about a single one (and the unicode equivalents of tau and pi).

FYI, π is already available:
11:57 < [Coke]> m: say π
11:57 < camelia> rakudo-moar 09a3e3: OUTPUT«3.14159265358979␤»
On Thu, Dec 3, 2015 at 10:46 AM, Juerd Waalboer<EMAIL_ADDRESS>wrote:

Yes, including every possible constant would indeed be a pretty daft
notion. Note that this patch is not about every possible constant, it is
about a single one (and the unicode equivalents of tau and pi).
—
Reply to this email directly or view it on GitHub
https://github.com/perl6/specs/pull/103#issuecomment-161682219.

--
Will "Coke" Coleda

I studied physics, but never heard of tau being used for 2 pi.

Most people never heard about Perl 6 in their studies. :-)
Tau, like many things in Perl 6, is a concept that is new to many people. The tau name and τ symbol have only existed for a few years. It's not surprising that you may not have heard about it ever before. But why is your lack of prior experience with this thing a reason to exclude it, given the plethora of other fancy new stuff in Perl 6, that you probably also never got taught in school? Last time I checked, Perl 6 had very little to do with maintaining the status quo.
Google does support tau in their calculator: https://www.google.nl/search?q=tau/2

Check out the links that @Juerd added to the rakudo ticket.
Here's another one: http://www.scientificamerican.com/article/let-s-use-tau-it-s-easier-than-pi/

@MadcapJake IMHO as language designers, we should follow what math and physics actually do, not what somebody suggests they should do. Yes, we're supposed to innovate, but in our own domain.

Note, this isn't innovation, it's early adoption.  Earliest suggestion (that I know of) of tau as this constant is in 1988.  Younger than Perl 1, older than Perl 3.  :D  Initially it stalled, then began gaining cultural traction around 2011.
  These symbols do no harm to the people who prefer π, 'between', and 'if not'.  Some folks prefer one over the other, some feel each choice is more expressive in some cases.
  It's controversial, though--for some reason (reasons?), plenty of folks have strong immediate convictions about this label.  Perhaps because much of the primary advocacy centers, bathwater-ishly, around pi being 'wrong'.  Or I may have the causal arrow backwards.  Or there may be more than one arrow in the causal air, here.
On Thursday, December 3, 2015 1:03 PM, Moritz Lenz<EMAIL_ADDRESS>wrote:

@MadcapJake IMHO as language designers, we should follow what math and physics actually do, not what somebody suggests they should do. Yes, we're supposed to innovate, but in our own domain.—
Reply to this email directly or view it on GitHub.

I think that τ is very TIMTOWDTI-ish which fits the language. It is as basic as π is, so I don't think that it belongs to some other module.
That being said, I'm not sure if “tau” should be exported. But τ does not hurt for sure.

Another +1 for tau's inclusion. I do not find the arguments from authority
against it very convincing, but I'm not a big fan of the physics
establishment in general so that could be my own bias.
Either way this hurts nothing and potentially exposes people to an
interesting new mathematical question/debate. I think it is completely in
accord with Perl's philosophy. If the proof fits, tau works and can only
get more popular from here.
I don't  see any reason why Perl 6 can't be a part of that movement.
On Fri, Dec 4, 2015 at 5:03 AM, Aleks-Daniel Jakimenko <
<EMAIL_ADDRESS>wrote:

I think that τ is very TIMTOWDTI-ish which fits the language. It is as
basic as π is, so I don't think that it belongs to some other module.
That being said, I'm not sure if “tau” should be exported. But τ does not
hurt for sure.
—
Reply to this email directly or view it on GitHub
https://github.com/perl6/specs/pull/103#issuecomment-161868232.

Since we're bike-shedding -- On the one hand, I feel like this should go into a lib that people can pull in. On the other ... TAU IS AWESOME and we should put it in :)
Like... then I can brag to people about Yet Another Awesome Bizzaro Thing in Perl6!


Create documentation for partners on generating management SDKs using MPG

We plan to ship our MPG to customers, allowing them to generate the SDK independently.
Therefore, we need to create documentation that explains how to generate the Azure mgmt. SDK using MPG.
Please refer to the .NET generation documentation for guidance.

Made a simple guide https://github.com/Azure/azure-sdk-for-java/wiki/Generate-code-from-TypeSpec
Let's see whether we have anyone uses this doc first, before improving the doc.


Improve on Material Design

Only the date picker can be changed in material design, but this cannot be done cause of lacking espresso test support.


[i2c, rtl] Initial FSM implementation for target mode

Implemented target-mode finite state machine
Added tx_fifo_depth_i and tx_fifo_wvalid_i ports
Implemented clock stretching when TX FIFO is empty during Read
Implemented tx_empty, tx_nonempty, and ack_stop (host sending
Stop after Ack) interrupts

Signed-off-by: Igor Kouznetsov<EMAIL_ADDRESS>

Can someone please review? Thanks

Actually, it looks like this PR needs a rebase such that this can be merged...

Rebased this PR.

Thanks @igk8. CI seems to be failing due to the following issues with style lint:
../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:582:35: Binary literal 6'b1 is shorter than its declared width: 6. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:960:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:978:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:991:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:1009:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:1033:44: Binary literal 6'b1 is shorter than its declared width: 6. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:1064:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

../src/lowrisc_ip_i2c_0.1/rtl/i2c_fsm.sv:1082:29: Binary literal 20'b1 is shorter than its declared width: 20. [Style: number-literals] [undersized-binary-literal]

Making these literals hex or dec instead of binary should fix this.

Thanks @msfschaffner. I've fixed the style lint issues and all CI checks have passed.

Thanks @igk8, merging in!


About Paper

Hi! Thank you for your great work!  I want to know where the paper can be downloaded.

Thank you for your interest in our work! We will submit the paper to arXiv in a few days and update the link in the repository as soon as possible.

Hi! Thank you for your great work! I want to know where the paper can be downloaded.

Hi! The paper can be found here. Thank you for your interest!


Switch to initials-only avatars for messages

If I understand the README correctly, you're looking for a way to have all avatars be initial-based. I've looked at what would need to be done for that.
Avatar urls seem to be computed by vulcan-users/lib/avatar.js and then displayed by vulcan-base-components/lib/users/UsersAvatar.jsx
The fallbackType "initials" sets the option that gravatar returns 404 if there's no image. Probably this is supposed to make the React component switch to the initials if the image can't be found. That didn't work for me.
Unfortunately there's no option combination to force initials to be used always. (a function-valued customImageProperty comes close, but since the code doesn't distinguish between no-url and empty-url, that's not sufficient)
I'd suggest doing Users.avatar.getUrl = function (user) { return ''; } to just disable avatar urls entirely, thereby switching to initials.

This should be covered by #230


PUT HTTP API return status 500 without human-readable message

Hi there,
I have a PHP loop with 10, 20 or 30 CURL to Fleet API. I used it as STRESS TEST
CoreOS stable 723.3.0
fleetctl 0.10.2

This is my method class
  public function putUnit( $unitId, $options, $desiredState = 'launched' )
  {
    // Path
    $path = '/fleet/v1/units/' . $unitId;

    // Build the post fields - default only the desired state
    $postFields = [
      'desiredState' => $desiredState,
      'options'      => $options
    ];

    $postFields = json_encode( $postFields );

    $ch = curl_init( $this->endpoint . $path );
    curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
    curl_setopt( $ch, CURLOPT_FOLLOWLOCATION, true );
    curl_setopt( $ch, CURLOPT_CUSTOMREQUEST, 'PUT' );
    curl_setopt( $ch, CURLOPT_POSTFIELDS, $postFields );
    curl_setopt( $ch, CURLOPT_HTTPHEADER, array(
                      'Content-Type: application/json',
                      'Content-Length: ' . strlen( $postFields )
                    )
    );
    $res        = curl_exec( $ch );
    $httpStatus = curl_getinfo( $ch, CURLINFO_HTTP_CODE );
    curl_close( $ch );

    $result = [
      'result'       => $res,
      'status'       => $httpStatus,
      'unit'         => $unitId,
      'options'      => $options,
      'desiredState' => $desiredState
    ];

    return $result;

  }

But sometimes (randomly), the $res = curl_exec( $ch ); return 500 HTTP Status with a blank human-readable message. Consider that $unitId and $options are very simple and I keep them equals for each test.
Any suggestions?
Thanks in advance

The place to start is probably looking at the fleet engine's logs and
looking for errors there (in particular at the time you are receiving 500s
on the client)
On Mon, Sep 7, 2015 at 8:48 AM, Giovambattista Fazioli <
<EMAIL_ADDRESS>wrote:

Hi there,
I have a PHP loop with 10, 20 or 30 CURL to Fleet API. I used it as STRESS
TEST
CoreOS stable 723.3.0
fleetctl 0.10.2
This is my method class
public function putUnit( $unitId, $options, $desiredState = 'launched' )  {    // Path    $path = '/fleet/v1/units/' . $unitId;    // Build the post fields - default only the desired state    $postFields = [      'desiredState' => $desiredState,      'options'      => $options    ];    $postFields = json_encode( $postFields );    $ch = curl_init( $this->endpoint . $path );    curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );    curl_setopt( $ch, CURLOPT_FOLLOWLOCATION, true );    curl_setopt( $ch, CURLOPT_CUSTOMREQUEST, 'PUT' );    curl_setopt( $ch, CURLOPT_POSTFIELDS, $postFields );    curl_setopt( $ch, CURLOPT_HTTPHEADER, array(                      'Content-Type: application/json',                      'Content-Length: ' . strlen( $postFields )                    )    );    $res        = curl_exec( $ch );    $httpStatus = curl_getinfo( $ch, CURLINFO_HTTP_CODE );    curl_close( $ch );    $result = [      'result'       => $res,      'status'       => $httpStatus,      'unit'         => $unitId,      'options'      => $options,      'desiredState' => $desiredState    ];    return $result;  }
But sometimes (randomly), the $res = curl_exec( $ch ); return 500
HTTP Status with a blank human-readable message. Consider that $unitId
and $options are very simple and I keep them equals for each test.
Any suggestions?
Thanks in advance
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/fleet/issues/1345.

@gfazioli  @jonboulle , yes, Http 500 error is the "Internal server error", it always does not give the exact internal reason to the browser. Need check the fleetd's logs.

Ok, the error is
ERROR units.go:223: Failed creating Unit(web_test-app-40.johnf.service) in Registry: timeout reached

Any ideas?

That's indicative of etcd taking too long to respond, and fleet giving up
on the request - so now it seems most likely that performance of etcd is
your culprit. You could start exploring some of the metrics it exposes to
analyse its performance -
https://github.com/coreos/etcd/blob/master/Documentation/metrics.md
On Tue, Sep 8, 2015 at 10:23 AM, Giovambattista Fazioli <
<EMAIL_ADDRESS>wrote:

Ok, the error is
ERROR units.go:223: Failed creating Unit(web_test-app-40.johnf.service) in Registry: timeout reached
Any ideas?
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/fleet/issues/1345#issuecomment-138640231.

@jonboulle Ok, I will try, thx

Yes, seems like etcd is the culprit.
Maybe not the performance issue, maybe etcd is stopping or some error.
func (ur *unitsResource) create(rw http.ResponseWriter, name string, u *schema.Unit) {
	if err := ur.cAPI.CreateUnit(u); err != nil {
		log.Errorf("Failed creating Unit(%s) in Registry: %v", u.Name, err)
		sendError(rw, http.StatusInternalServerError, nil)
		return
	}

	rw.WriteHeader(http.StatusCreated)
}

Hey guys I join the conversation cause @gfazioli is my collegue (he deals with the code and I'm dealing with the CoreOS cluster). I suspected an etcd2 culprit. This is our testing infra:

3 machines acting as etcd2
2 machines acting as workers (configured as etcd2 proxy)

In the last days we were trying to launch 100 units (with its discovery) for testing, across all the 5 machines (and not only the two workers). For this reason I suspected that etcd2 cluster was suffering.
Today we started seeing  machines disappearing and reappearing again (never seen before). I restarted etcd2 service on all machines and this stopped. The only error I've seen on etcd2 logs is:
015/09/09 09:09:48 sender: error posting to 172991be8af6b7f8: unexpected http status Internal Server Error while posting to "http://<IP_ADDRESS>:2380/raft"

The next test we're going to do is to launch our units only on worker machines.
Btw any idea on how to reset etcd2 metrics? Atm I see a lot of getsFail, deleteFail, createFail and I can't understand if they are referred to the past or are new.

FYI these are etcd2 cluster stats

@gfazioli You have to update etcd to 2.1 to get all the metrics. See https://github.com/coreos/etcd/blob/release-2.1/Documentation/metrics.md

@gfazioli The easiest way to identify if it is an etcd issue is to monitoring the etcd log. You would see leader elections if etcd is not stable or under very heavy load.

I'm pretty sure this is the same as #1650 but there is not enough information here to tell how fleet and/or fleetctl was being used.


Steve's Feedback: Change the sign-off line "The LF Engineering Team" to "EasyCLA Support Team" for EasyCLA emails

Change the sign-off line "The LF Engineering Team" to "EasyCLA Support Team" in all the easycla emails.
Some of the emails have "EasyCLA Support Team" while some have "The LF Engineering Team" - it should be  "EasyCLA Support Team".

This is deployed to DEV, Staging & PROD.

Verified on Staging today and found changes are getting reflected. Please follows below emails for reference:

CLA Manager

CLA Signatory
![image.png](https://images.zenhubusercontent.com/5face8c0a2ad18653594316c/9f1689e8-33b
7-448a-b5fe-49fbbad4fff5)
CLA Manager Designee

Added as CLA Manager for Project

CLA Manager Added Notice

Approval List Update


disable building binary wheels for pypy

What does this pull request do?
The wrapt c-extension doesn't build with pypy, and our setup.py skips building the extension
when it detects pypy. However, we still mistakenly built pypy-specific binary wheels.
cibuildwheel introduced a check for this in 1.6, alerting us to the problem.

:green_heart: Build Succeeded

Expand to view the summary

Build stats

Build Cause: [Pull request #924 opened]

Start Time: 2020-09-15T14:15:15.090+0000

Duration: 26 min 10 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
10927

Skipped
8506

Total
19433

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 django-1.11

Duration: 2 min 55 sec

Start Time: 2020-09-15T14:21:03.988+0000

log


Add support for Python traceback lexer in markdown code cells

In the case of making a notebook for demonstrating how Python errors appear, it can be useful to create a markdown code cell showing the expected output of running some incorrect code. Consider this code example:
add_csv = lambda f: f if f.endswith('.csv') else f+'.csv

When you run this in a code cell you should get a traceback message something like this:
File "C:\Users\latanej\AppData\Local\Temp/ipykernel_22292/172927516.py", line 1
    add_csv = lambda f: f if f.endswith('.csv') else f+'.csv
                                                            ^
SyntaxError: EOL while scanning string literal

It would be helpful if you could put that traceback message int a markdown cell code block with the language specified for Python traceback output so that the colors and highlighting would match how it actually shows beneath the code cell. Something like:
```pytb
```
This way, readers of the notebook (who may be beginners to Python and traceback messages) should know what to expect when they run the incorrect code.

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.


Restructure code

Separate out the code for Infinite and InfExtended (and the future InfExtendedTime) into separate files, something like:
InfExtended.jl
utils.jl
infinite/
  base.jl
  io.jl
  ...
infextended/
  base.jl
  io.jl
  ...
infextendedtime/
  ...

Hey, just wondering if you were going to tackle this issue (I assume so since you assigned yourself). I possibly have some time to try and get this done myself, as it would be nice to have for #3.

Be my guest!


[DNM] remove useless rocksdb API

Some options are removed from RocksDB 5.2+, removing these is ok and has no problem with 5.1, only we need to remove set_disable_data_sync in TiKV later.
@BusyJay @hhkbp2 @zhangjinpeng1987

LGTM

LGTM

PTAL @zhangjinpeng1987


Live

Docs Build status updates of commit d107347:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Test PR


Use different class for memes in build desc.

When I enabled the "show in build desc" option the build history box overflowed with memes. It would be nice to put constraint sizes on images and a different class name would help with that.

Thanks! Merged


Tip: Make sure stuff works before you publish an article on it

Go through every single step in this article, and you'll not get anything that resembles a deployed application. Here's some output from my deployment
09:02:25 BKKTeamsHelloWorld: Command: bash deploy.sh
09:02:25 BKKTeamsHelloWorld: deploy.sh: line 2: $'\r': command not found
09:02:25 BKKTeamsHelloWorld: deploy.sh: line 7: $'\r': command not found
09:02:25 BKKTeamsHelloWorld: deploy.sh: line 10: $'\r': command not found
09:02:25 BKKTeamsHelloWorld: deploy.sh: line 11: syntax error near unexpected token $'{\r'' 09:02:25 BKKTeamsHelloWorld: deploy.sh: line 11: exitWithMessageOnError () {
09:02:25 BKKTeamsHelloWorld: '
09:02:25 BKKTeamsHelloWorld: deploy.sh: line 2: $'\r': command not found\ndeploy.sh: line 7: $'\r': command not found\ndeploy.sh: line 10: $'\r': command not found\ndeploy.sh: line 11: syntax error near unexpected token $'{\r''\ndeploy.sh: line 11: exitWithMessageOnError () {\n'\n/opt/Kudu/Scripts/starter.sh bash deploy.sh
On the other hand, the dialog box says the deployment was successful. So, I browse to the site created, but nothing. So apparently not.
Final step - gotta add app_bot_id and app_bot_password somewhere. Now, since the creation of my app happened through the Azure plugin for VS Code, I have not seen any, so I head over to the Azure portal to find the app_bot_id it presumably has created when creating my app, but there is no such thing anywhere.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c08b13b0-8c05-c6f1-c3fa-a58b67ae0123
Version Independent ID: 14116a6d-f66b-a81b-9808-cf6db771325f
Content: Host your Node based Teams app in Azure - Teams
Content Source: msteams-platform/get-started/get-started-nodejs-in-azure.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

Agreed very frustrating trying to follow this.
For others getting the above error In the Bottom Right hand corner of VSCode there is  CRLF button. Click this and you'll have the option to change to LF.
After that it should deploy successfully.
https://askubuntu.com/questions/1036322/running-script-made-in-visual-studio-code-on-windows-on-wsl-ubuntu-returns-li


v1.3.40

This repository contains GitHub workflows for managing releases automatically.
Please name this issue what you would like the new release to be called. E.x. "v1.0.0"
The following slash commands are available to use in comments on this issue:

Command
Description
Parameters

/release
Creates a new released based on the current state of the master branch
frontend=<version>backend=<version>engagement-status=<version>gitapi=<version>status=<version>config=<version>activity=<version>artifacts=<version>hosting=<version>participants=<version>engagements=<version>dispatcher=<version>agnosticv=<version>anarchy=<version>poolboy=<version>babylon-config=<version>

/promote
Promotes the created release to the next environment
N/A

/cancel
Cancels the current release (and closes this issue)
N/A

/finish
Completes the current release (and closes this issue)
N/A

/release frontend=v1.5.2 backend=v2.3.5 gitapi=v1.4.0 config=v1.3.1 status=v1.2.0 dispatcher=v1.0.16 activity=v1.0.1 artifacts=v1.0.0 participants=v1.0.0 engagements=v2.0.8 engagement-status=v1.0.0 hosting=v1.0.0

/promote

/cancel


OpenFileDialog undefined behavior on linux-distros

OpenFileDialog behavior differs from distro to distro. Tested on 4 different distros on different run configs.
Computer configuration:

Ryzen 7 1800x
RX 5600 XT
24 gb ram

.net core version: 3.1
App publishing options:

Win->Lin: Published from windows to linux
Lin->Lin: Published from linux to linux

Publish command for Win->Lin and Lin->Lin: dotnet publish -r linux-x64 -c Release /p:PublishSingleFile=true
App used for testing: link
Testing paths:

File selected
Expected behavior – OpenFileDialog.ShowAsync() returning array with one item – path to file.
File selected canceled
Expected behavior - OpenFileDialog.ShowAsync() returning array without items (but array is not nullable)
Expected program behavior: On button click, shows up a file select dialog. If file is selected the expected behavior is: Shows up a messagebox with file path If canceled: Shows up an empty messagebox.
 It used to work until distros have rolled a new libfreetype version, so everything began segfaulting.
Consider using managed file dialogs or switching to 0.10-preview

You can also try to switch to a newer build of SkiaSharp linux library by adding
<ItemGroup>
    <PackageReference Include="SkiaSharp.NativeAssets.Linux" Version="1.68.3" />
    <PackageReference Include="Avalonia.Skia.Linux.Natives" Version="<IP_ADDRESS>" ExcludeAssets="all" />
    <PackageReference Include="SkiaSharp" Version="1.68.3" />
</ItemGroup>

to your project (exactly those lines without changes)

Yes, changing SkiaSharp version helped, the application works as on ubuntu, tanks. But the problem with null aray is still there (Windows doesn't have that problem, instead of null array it is empty)
When 0.10-preview will be availble in nuget?

But the problem with null aray is still there

Yes, that inconsistency needs to be fixed.

When 0.10-preview will be availble in nuget?

https://www.nuget.org/packages/Avalonia/0.10.0-preview1


fix poc nbs and move poc unit test

This example cannot ask the user to remove cudf and tensorflow... that would mess up all other code... down the line

This example cannot ask the user to remove cudf and tensorflow... that would mess up all other code... down the line

This is intended to be done only if users want to run this on cpu. this was the only way to make it work, if we did not uninstall cudf it was still looking for GPUs and it gives errors.

rerun tests


Add: Verts Paturages TV [CD]

Channel Name
Verts Paturages TV
Alternative Names (optional)
Verts Paturages TV
Network (optional)
No response
Owners (optional)
No response
Country
CD
Subdivision (optional)
No response
City (optional)
Kinshasa
Broadcast Area
c/CD
Languages
fra
Categories (optional)
general
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
No response
Logo
https://i.imgur.com/65qrSXD.jpeg
Notes
No response

Please update your request:

alternative name should only be specified if it differs from the main name

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels


MicroWin don't remove bloatware from Windows 10 Pro

MicroWin don't remove bloatware from Windows 10 Pro ISO, only works on win11?

MicroWin don't remove bloatware from Windows 10 Pro ISO, only works on win11?

Yes it is designed for Windows 11. It will still work on Win10 but the start menu will have the normal bloat. I'm not sure it is worth modifying the script for Win10 since it goes End of Life next year.


Add PyArrow integration test for C Stream Interface

Which issue does this PR close?

Closes #1847.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

cc @sunchao

Codecov Report

Merging #1848 (469469c) into master (b5fbd11) will decrease coverage by 0.00%.
The diff coverage is 9.52%.

@@            Coverage Diff             @@
##           master    #1848      +/-   ##
==========================================
- Coverage   83.46%   83.46%   -0.01%
==========================================
  Files         199      201       +2
  Lines       56600    56852     +252
==========================================
+ Hits        47244    47449     +205
- Misses       9356     9403      +47

Impacted Files
Coverage Δ

arrow/src/pyarrow.rs
0.00% <0.00%> (ø)

arrow/src/ffi_stream.rs
79.67% <66.66%> (+1.17%)
:arrow_up:

parquet/src/util/memory.rs
87.17% <0.00%> (-2.30%)
:arrow_down:

parquet_derive/src/parquet_field.rs
65.75% <0.00%> (-0.23%)
:arrow_down:

parquet/src/errors.rs
29.62% <0.00%> (ø)

arrow/src/array/mod.rs
100.00% <0.00%> (ø)

arrow/src/buffer/mod.rs
73.33% <0.00%> (ø)

arrow/src/datatypes/native.rs
66.66% <0.00%> (ø)

parquet/src/arrow/async_reader.rs
0.00% <0.00%> (ø)

arrow/src/buffer/scalar.rs
93.47% <0.00%> (ø)

... and 7 more

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 b5fbd11...469469c. Read the comment docs.

Thanks @sunchao !


Timestamps.

Hi.
First, I want to thank you for the great work.
I use GigaSpeech pretrained model. I successfully create LM and TLG.fst decoding graph. I run ./tools/decode.sh with wfst_decode_opts and correct fst_path. I'm getting correct decoding/rescoring partial and final results in log file and in result file, but I don't get any timestamp info in log or result files. I even try to run decoder_main with unit_path key (taking words.txt from pretrained model as input), but nothing changes.
Could you please tell me, how can I get the timestamps for the words?
And is there any way to get lattice as in Kaldi instead of text when using TLG graph for decoding?
Thanks in advance.

The timestamp only works in websocket.
You could save the lattice or compact lattice after this statement: https://github.com/wenet-e2e/wenet/blob/d3f690a889e8b5aea3eabb5dcf39bb48d754d2ab/runtime/core/decoder/ctc_wfst_beam_search.cc#L135

Thank you.
Do I understand correctly that I can add the output of timestamps by adding something like this link to the decoder_main.cc?

Yes.

Thank you very much!


skip binary and empty files

https://linear.app/trunk/issue/TRUNK-4736/trunk-toolbox-failed-to-build-line-views

closes https://github.com/trunk-io/trunk/pull/5816


Add utxoBalanceShortfall field and remove balanceMissing function.

Issue Number
Split off from https://github.com/input-output-hk/cardano-wallet/pull/3723.
Summary
This PR cherry-picks a small number of commits from https://github.com/input-output-hk/cardano-wallet/pull/3723.
It adds a utxoBalanceShortfall field to the BalanceInsufficientError:
  data BalanceInsufficientError = BalanceInsufficientError
      { utxoBalanceAvailable
          :: !TokenBundle
      , utxoBalanceRequired
          :: !TokenBundle
+     , utxoBalanceShortfall
+         :: !TokenBundle
+         -- ^ The shortfall between 'utxoBalanceAvailable' and
+         -- 'utxoBalanceRequired'.
+         --
+         -- Equal to the /truncated subtraction/ of 'utxoBalanceAvailable' from
+         -- 'utxoBalanceRequired'.
+     }

Adding this field (and pre-computing its value) has the following benefits:

More informative error messages:
The shortfall field tells the caller which assets have a shortfall, and the minimum additional amount of each asset they would need to add to the UTxO balance in order to successfully balance a transaction. This means removes a burden from the caller to perform this calculation themselves.

Better abstraction boundary:
The HTTP server error layer no longer needs to call the internal coin selection function balanceMissing, which can now be removed.

Shortfall values are now captured in golden files for balanceTransaction:
Although this field is covered by property tests, it's also useful (from a sanity-checking perspective) to visually inspect these values and verify that they are reasonable.

bors r+


Pdf Form data not retrived and not showing any validation or error.

Hi,
I'm working with the PHP 7 and not able retrive data from pdf form fields.
I'm using follwoing php code index.php-

require('vendor\autoload.php');
use mikehaertl\pdftk\Pdf;

$pdf = new Pdf('template.pdf');
$data = $pdf->getData();
print_r($data);

This(index.php) file is located in the outside of vendor directory and template.pdf file is also located in same directory.
Please have a look on the issue and check what is the issue we are facing.

What is the output of your script? And which version of pdftk are you using?

Wait a minute - guess you're in the wrong project here. This is phpwkhtmltopdf - for creating PDF. Your issue is with pdftk, so you should open the issue there.
Before you do so, please also first try, if it works on the command line: pdftk dump_data_utf8 template.pdf. If it doesn't work there it's not a problem of php-pdftk.


implement istio.io/waypoint-for annotation

(This is used to request new product features, please visit https://github.com/istio/istio/discussions for questions on using Istio)
Describe the feature request
Need to implement the istio.io/waypoint-for annotation as described in the Ambient Waypoint Capture for Services and Workloads doc. The annotation gets applied to Gateway and GatewayClass resources and takes in a value to determine which type of traffic is being redirected through the waypoint.
These should be the allowed values:

none - Cannot handle any redirected traffic
service  - Can only handle to-service traffic
workload - Can only handle to-workload traffic
all - Can handle both to-service and to-workload traffic

Other important aspects of this annotation and the use of its values:

If a value is not declared on a Gateway or its associated GatewayClass then the network layer should default to service when redirecting traffic.
A Gateway can override the default value of its associated GatewayClass by explicitly declaring a value.
The istio.io/waypoint-for none value is useful/needed for scenarios where we want to disable or more finely control redirection while still allowing testing of the generated config.

Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[X] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

Gateway resource
GatewayClass resource
Ambient - Waypoint Capture for Services and Workloads, WIP design doc by John Howard and Louis Ryan

I need some clarification on the additional work to be done for implementing this annotation istio.io/waypoint-for.
I'm thinking that I may have to do a check for annotations[constants.WaypointForAddressType] and if set (by a user doing istioctl x waypoint apply --for), then I need to programmatically set the waypoint for that type (workload, service, or all (both?).. is that correct logic wise?
Also, can that be done in the ambient controllers for service and workload here: https://github.com/istio/istio/tree/ae117f8d6bc7ed1b684220749b929176945faaca/pilot/pkg/serviceregistry/kube/controller/ambient? Or is there another location that I'm not aware of?
I want to make sure I'm thinking of this correctly before I go down a rabbit hole.
cc/ @ilrudie @howardjohn

Are you at kubecon next week @MorrisLaw? If not maybe we should try to huddle in slack and discuss.

Unfortunately no @ilrudie. But, I’m down to do a huddle. Let’s try to find some time next week when you have down time between sessions.

I'm not hitting up kubecon either so I should have time to huddle


Use URLconnection for iOS

Advantages:

automatic proxy usage
HTTPS2 support

Requires HTTPS for all backends.

internal endpoints
review tilejson-s - indirect endpoints: https://github.com/CartoDB/lbs-services/issues/29

Review performance. Does it use HTTP/2 ?

Implemented, SDK 4.2 uses URLSession API on iOS.


Clean Up of unavailable and old projects/links

Updated several dead links
Updated several replaced projects
Removed some no longer available projects

Best

Updated the 2 repo links.

👍


Signals not working

posted in the wrong place

@bestofothers please also close the issue if it was posted wrongly


Are hardware cursors supported?

I am using your library through OpenTK, currently I can only see an arrow cursor.
Try to understand what's causing this, does ImGui.NET supports mouse cursors?
Thank you.

not really related to OpenTK but here is how I am showing different cursors in dx11 & Win32 & imgui. Hopes it helps...
https://github.com/zaafar/ClickableTransparentOverlay/blob/master/ClickableTransparentOverlay/ImGuiInputHandler.cs#L23
https://github.com/zaafar/ClickableTransparentOverlay/blob/master/ClickableTransparentOverlay/ImGuiInputHandler.cs#L86

@zaafar
This is at the same time great and not so great, I had to rewrite a substantial portion of what GLFW, OpenTK and Win32 already do, so I tried that, until things broke and aren't seen anymore by OpenTK and the thing started acting weird.
In your case it's okay since you're bare metal, there's no intermediate layer and you have full control of things.
Thanks anyway 😀

Problem solved, solution: https://github.com/ocornut/imgui/issues/5739#issuecomment-1268734162


HLS seeking

Hey @fougere-mike thanks for making this fork. Out of the box I do see that the stream is able to be played from some point in the past. What I'm a little confused by is how seeking is supposed to be used. When applying your patch and then playing the stream, it starts from the beginning of the window — how do I start it from "now" (i.e. "live")? I can calculate the offset and then use seekTo() but it seems like I'm missing something.
Thanks again for the patch!

Thanks for the patch and thanks for opening this. I am also interested to know how to achieve the seeking and reading from live point.

The duration and position info is all relative to the start of the video, not the start of the window.
If the window has slid forward and segments have been removed from the start of the playlist, the playlist's media sequence property should be updated to reflect that. That means, if there are truly only 2 segments in the playlist, but the media sequence is 2000, the duration reported by the player will be: (2000 + 2) * segmentDuration.
So, to seek to live you should be able to do something like: player.seekTo( player.getDuration() ); to seek to the very end of the playlist.
For my own streams, I defend against seeking to the real live edge because there might be a delay between seeking and the next segment actually being added to the playlist; that would result in a stall. I always stay at least 10 seconds behind the real live position:
private void seekToInternal(long position) {
        // If this is a live stream, we will guard against seeking
        // to the _real_ end of the stream.
        if( isLiveStream() ) {
            long virtualLiveEdge = getDuration() - INTERVAL_FROM_LIVE_EDGE_MS;
            position = Math.min(position, virtualLiveEdge);
        }

        seekTo(position);
    }

Let me know if that's not working for you. Cheers!

@fougere-mike Great advice! Using your notes I was able to get everything working well. Thank you so much! I'll close this.

@fougere-mike I can seek to the live position but the stream still starts by default at 0 (i.e. beginning of the window). Is there a way to tell it to start from live, besides starting the stream and then seeking?

Not presently, no. Although I can take a look at adding that if it's causing you problems.

I am going to do some work on it against your branch, I'll open a PR if there's anything worthwhile in there.

Sounds good.

There haven't been any updates here for a while -- closing for now.


Xception39 pretrained model

Hi!!!! Thanks for sharing your code. I wonder if you plan to release Xception39 pretrained model ??

Actually, this plan has a low priority because I have no machines to pre-train the Xception39 on ImageNet with PyTorch.

Can you share the training details and results on ImageNet val ? I am interested in that model. Maybe I can train and release the weight in this repo.

I’m sorry that the Xception pre-trained model is trained by someone else. Now I can not find its log. Maybe you can check the training details of the original paper of Xception. We just adapt its structure.


Suggest: sidebar shoule be auto collapsed at md resolution

Hi, I'm a user of AdminLTE from China. It's very very cool. I like it very much. I have used it in more than 500 web projects.
Devices such like iPad, have a width at 768px. It matches the MD width. In our AdminLTE, the sidebar (of course the left one) is not collapsed by default. I've had a look at some other admin templates, and discussed with my workmates and friends on github, we both think it's better to collapse the sidebar at MD width by default. It's too narrow for devices between 768 & 1000 with a full sidebar. Especially ipad mini, which is small.
Current:

Collapsed seems better:

Can you take a consideration about my suggestion?
Thank u.

This drives me crazy. Anybody knows how to change it?

@realpg do you know any workaround to collapse sidebar by default on MD resolution devices?
I'd try to edit JS screenSizes object and $screen-sm SCSS variable, without success.
Thanks

Check in JS file I think this is where it is set.

I've created a option for v3 with #2119, I'll create soon a documentation with detailed information about the option.
I close this issue for now


Can't upgrade many packages

Hi, I am trying to upgrade all of my packages using command choco upgrade all but afterwards I get following error messages:
Failures
 - 010editor.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - apktool - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - apktool.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - asreproast.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - autohotkey - Unable to resolve dependency 'autohotkey': Unable to resolve dependencies. 'autohotkey <IP_ADDRESS>' is not compatible with 'nmap.vm 7.93.0 constraint: autohotkey (= <IP_ADDRESS>)', 'npcap.vm 1.72.0 constraint: autohotkey (= <IP_ADDRESS>)'.
 - autohotkey.install - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - azurehound.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - bloodhound.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - capa.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - common.vm - Unable to resolve dependency 'vcredist2010': Unable to find a version of 'vcredist2010' that is compatible with 'Cmder 1.3.21 constraint: vcredist2010 (>= 10.0.40219.2)'.
 - cutter.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - cyberchef.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - dotnet-6.0-desktopruntime - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - exiftool - Unable to resolve dependency 'exiftool': Unable to find a version of 'exiftool' that is compatible with 'exiftool.vm 12.48.0 constraint: exiftool (= 12.48.0)'.
 - exiftool.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - gobuster.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - ilspy - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - ilspy.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - jre8 - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - libraries.python3.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - notepadplusplus - Unable to resolve dependency 'notepadplusplus': Unable to resolve dependencies. 'notepadplusplus 8.5.6' is not compatible with 'notepadplusplus.vm <IP_ADDRESS>21129 constraint: notepadplusplus (= 8.4.7)'.
 - notepadplusplus.install - Unable to resolve dependency: Unable to resolve dependencies. 'notepadplusplus.install 8.5.6' is not compatible with 'notepadplusplus 6.8.9 constraint: notepadplusplus.install (= 6.8.9)'.
 - notepadplusplus.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - notepadpp.plugin.compare.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - python3 - Unable to resolve dependency 'python3': Unable to find a version of 'python3' that is compatible with 'python3.vm <IP_ADDRESS>30314 constraint: python3 (= 3.10.0)'.
 - python3.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - sqlrecon.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - sysinternals - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - teamfiltration.vm - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - Temurin11 - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - wireshark - Unable to resolve dependency 'cygwin': Unable to resolve dependencies. 'cygwin 3.4.8' is not compatible with 'cygwin.vm 3.4.7 constraint: cygwin (= 3.4.7)'.
 - wireshark.vm - Unable to resolve dependency: Unable to find a version of 'autohotkey.install' that is compatible with 'autohotkey <IP_ADDRESS> constraint: autohotkey.install (>= <IP_ADDRESS>)'.

That's weird and I suspect a bug somewhere...
In the meantime we have updated a few packages, so it may work now.

I am not sure what the problem is with the information provided. Please when reporting bugs use the issue template and provide all the required information including the output of VM-Get-Host-Info .
Note that as documented in our Wiki updating packages is best effort and that we are not testing updates. We recommend to perform a fresh flare-vm installation instead of updating packages.


Add a macro symbol kind for languages that have macros

RustyCode advertises macros as simple functions because there is no specific symbol kind for macros.
https://github.com/saviorisdead/RustyCode/blob/dae6ac740e2b52466f8883da6a716faa8455d6de/src/rustSymbols.ts#L13

@nox Is that for completions or symbol search or both?

I filed this for symbol search, but I guess it could be used for context in completions too?

Any news on this?

Ping?

closing as dupe of https://github.com/Microsoft/vscode/issues/2628


PR: Support Rich and Colorama in the IPython console

Description of Changes
This makes the isatty attribute of the OutStream instance in our kernel to return True, which adds out of the box support for Rich and Colorama in our consoles.
Dependes on spyder-ide/spyder-kernels#305
Issue(s) Resolved

Fixes #1917.
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ccordoba12

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

In the file external-deps/spyder-kernels/spyder_kernels/console/outstream.py:

Line 19:80: E501 line too long (89 > 79 characters)


Pattern fills

Question
Description
When is the pattern fills feature planned and who's working on it?
Is there any workaround at this time, to add pattern and make it repeat itself?
Your environment

pdfkit version: latest
Node version: latest

AFAIK no one is working on it


Docker from Snap cannot find ingress_sbox.

I have installed docker from snap.
when i try to install DIRD, cannot find ingress_sbox.
2023-12-06.04:36:05.438065|Hedwig|1016512| Docker Ingress Routing Daemon 4.1.0 starting ...
nsenter: cannot open /var/run/docker/netns/ingress_sbox: No such file or directory
2023-12-06.04:36:05.544429|Hedwig|1016512| - Couldn't identify ingress network subnet or this node's ingress network IP; sleeping 1s, then exiting.

I think snap docker save network container in /run/snap.docker/netns/

Thanks for raising this issue. You're right that DIRD does not currently support non-standard paths to ingress_sbox.
Adding support shouldn't be hard though. Would you mind searching/replacing the standard path with the snap path in the code and trying that to see if it is sufficient?
If it works, we can look to add a command line option for configuring this and officially supporting it.

Okay. Thank you for comment.
I have changed the code like following.

  exit 0
fi

###############

I just change all nsenter --net option.
but encountered other nsenter issue.
2023-12-07.10:28:09.777109|jaeho-VirtualBox|05734| Docker Ingress Routing Daemon 4.1.1 starting ...
nsenter: reassociate to namespace 'ns/net' failed: Invalid argument
2023-12-07.10:28:09.922912|jaeho-VirtualBox|05734| - Couldn't identify ingress network subnet or this node's ingress network IP; sleeping 1s, then exiting.


Please apply to this job in Upwork and let us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Something weird happened here, going to unlock and relock

Trying again

Okay, that time it worked and 1.1.17-0 is deploying here

6433 is in production already.

@parasharrajat This is a known issue with pull requests that are CP'd. We should be close to a fix, but won't know for sure until the next checklist.

Regression is almost complete
Issues found

https://github.com/Expensify/App/issues/6518
https://github.com/Expensify/App/issues/6519
https://github.com/Expensify/App/issues/6520
https://github.com/Expensify/App/issues/6522
https://github.com/Expensify/App/issues/6529
https://github.com/Expensify/App/issues/6534

TCs Blocked
Log in / Messages / Notifications iOS/Android and mWeb TCs Blocked by #6519
iOS - Settings - blocked by #6520
iOS - Bank Account - Blocked by #6438

@roryabraham @marcaaron Got the notification to test these Cherry picks but both seem internal QA. I'll add them to the Internal list of PRs in the main comment.
https://github.com/Expensify/App/pull/6531
https://github.com/Expensify/App/pull/6411

Verified https://github.com/Expensify/App/pull/6531 on staging, checking it off.

https://github.com/Expensify/App/pull/6165 Will not be fully verified until the next checklist, but we've seen so far that it doesn't cause any regression. So I'm going to check it off on this checklist.

Checking off #6278 as Fix #6523 is Pass

#6548 & #6454 both retests Pass

@roryabraham Botify didn't like me adding stuff to the checklist 😆 I think what we can do is simply add comments with checklists to test the CPs until the CP checklist issue is resolved.

Only thing missing for this checklist is the fix for https://github.com/Expensify/App/issues/6518 (deploy blocker) being worked on here https://github.com/Expensify/App/pull/6535 - once that it fixed we will retest https://github.com/Expensify/App/pull/6442 and check both of them off if they are a pass.

Botify didn't like me adding stuff to the checklist

Oh, I can fix that 😄 Mind creating an issue?

The PRs not applicable to accessibility testing are: #6165, #6195, #6268, #6278, #6279, #6387, #6441, #6417, #6466, #6485. All others except #6442 have been tested, the failures are mentioned in comments for the corresponding PRs.

Testing this CP:

[ ]  https://github.com/Expensify/App/pull/6259

#6411 should be good to go - removing the blocker.

@roryabraham Friendly bump.
Still waiting for the fix for #6518 (deploy blocker) to retest #6442 & close this checklist

@mvtglobally We're working on getting https://github.com/Expensify/App/issues/6518 resolve ASAP.

The fix to https://github.com/Expensify/App/issues/6518 is being CP'd in 1.1.17-7 here

1.1.17-7 has finished deploying. @mvtglobally @isagoico please retest https://github.com/Expensify/App/pull/6442, https://github.com/Expensify/App/issues/6518, and https://github.com/Expensify/App/pull/6535

@roryabraham  #6518 and #6535 are pass. 1.1.17-7 is not available on Android yet, but PR #6442 seem pass on build 1.1.17-6 on Android. Let me know if we should wait for 1.1.17-7 or it is ok to check off this PR?

Sounds good, going to check everything off and deploy.

:shipit:


Use better sleep implementation

Apparently Julia's implementation of sleep will sleep for more than a millisecond even if you request 1 microsecond... And also has memory allocations. Argh...
This switches to Libc.systemsleep which not only has better resolution but also has 0 allocations: https://discourse.julialang.org/t/julia-seems-an-order-of-magnitude-slower-than-python-when-printing-to-the-terminal-because-of-issue-with-sleep/78151/44

Hm.. probably not worth the complexity..

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 94.624%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
2376

Relevant Lines:
2511

💛  - Coveralls

Okay I tested this on a machine with many CPUs, and it actually got a 30% performance improvement for the multi-threaded version. So I think it's worth it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 94.628%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
2378

Relevant Lines:
2513

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 7 (42.86%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 94.471%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Utils.jl
2
6
33.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
2375

Relevant Lines:
2514

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 94.63%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
2379

Relevant Lines:
2514

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 94.628%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
2378

Relevant Lines:
2513

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2373

Relevant Lines:
2508

💛  - Coveralls


Tasmota outlets show up as 2 switches

Describe The Bug:
Different versions on Tasmota flashed power plugs show up as 2 devices, the switch itself and the total energy plug.
To Reproduce:
Enable setoption19 1 for a tasmota flashed plug (version 9, 10)
Expected behavior:
Omit second plug
Logs:
[2/13/2022, 6:36:35 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge 72E9) is running on port 51655.
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY TotalStartTime sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla HDHomeRun ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Total
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Total sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Yesterday sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Today
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Today sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Power
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Power sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY ApparentPower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY ApparentPower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY ReactivePower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY ReactivePower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Factor sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type power_factor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Voltage sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun ENERGY Current sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota sensor type current
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: HDHomeRun status
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: HDHomeRun status sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Light status
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Light status sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY TotalStartTime sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla TV ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Total
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Total sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Yesterday sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Today
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Today sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Power
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Power sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY ApparentPower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY ApparentPower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY ReactivePower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY ReactivePower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Factor sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla TV ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Voltage sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla TV ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV ENERGY Current sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla TV ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: TV status
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: TV status sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY TotalStartTime sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Computer ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Total
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Total sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Yesterday sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Today
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Today sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Power
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Power sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY ApparentPower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY ApparentPower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY ReactivePower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY ReactivePower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Factor sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Computer ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Voltage sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Computer ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer ENERGY Current sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Computer ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Computer status
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Computer status sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Sensors AM2301 Temperature
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Sensors AM2301 Temperature sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Sensors AM2301 Humidity
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Sensors AM2301 Humidity sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Sensors AM2301 DewPoint
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Sensors AM2301 DewPoint sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Sensors BH1750 Illuminance
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Sensors BH1750 Illuminance sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Sensors status
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Sensors status sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY TotalStartTime sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Bed ENERGY TotalStartTime
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Total
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Total sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Yesterday sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Today
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Today sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Power
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Power sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY ApparentPower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY ApparentPower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY ReactivePower
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY ReactivePower sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Factor sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Bed ENERGY Factor
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Voltage sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Bed ENERGY Voltage
[2/13/2022, 6:36:35 PM] [Tasmota] Found existing accessory: Bed ENERGY Current
[2/13/2022, 6:36:35 PM] [Tasmota] Creating service: Bed ENERGY Current sensor
[2/13/2022, 6:36:35 PM] [Tasmota] Warning: missing dev_cla Bed ENERGY Current
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: Bed status
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: Bed status sensor
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: Light
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: Light light
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: HDHomeRun
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: HDHomeRun switch
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: TV
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: TV switch
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: Computer
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: Computer switch
[2/13/2022, 6:36:36 PM] [Tasmota] Found existing accessory: Bed
[2/13/2022, 6:36:36 PM] [Tasmota] Creating service: Bed switch
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'HDHomeRun ENERGY Power' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'HDHomeRun' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'TV ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'TV ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'TV' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Computer ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Computer ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Computer' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Sensors AM2301 Temperature' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Sensors AM2301 Humidity' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Sensors AM2301 DewPoint' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Sensors BH1750 Illuminance' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Bed ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Bed ENERGY Total' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Bed' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Light' to Online
[2/13/2022, 6:36:36 PM] [Tasmota] Marking accessory 'Light' to Online
Tasmota Device Config:
Please include the Tasmota Module Type / Configuration and Template ( if used )
{"NAME":"Neo Coolcam 16","GPIO":[32,0,0,0,2688,2656,0,0,2624,320,224,0,0,0],"FLAG":0,"BASE":49}

**Screenshots:**
<!-- If applicable, add screenshots to help explain your problem. -->

**Environment:**

* **Tasmota Version**: 9.3.1, 10.0.1
* **Plugin Version**: 0.1.1
* **Homebridge Version**: 1.4.0
* **Node.js Version**: <!-- node -v -->
* **NPM Version**: <!-- npm -v -->
* **Operating System**: ubuntu 18.04.5

<!-- Click the "Preview" tab before you submit to ensure the formatting is correct. -->

I’m currently away and don’t have access to my test environment for a few weeks, so this investigation will have to wait until I’m back

I have the same problem, I think the total-energy switch is the current power consumption, but shown as a switch and not as a status..


[on hold] Include omniscidb 5.6 on github CI

On hold until https://github.com/conda-forge/omniscidb-feedstock/pull/40 gets merged

omniscidb 5.6 is actually provided by https://github.com/conda-forge/omniscidb-feedstock/pull/39

Did omniscidb went from v5.5.2 straight to 5.7-dev on conda-forge (ref)?

Did omniscidb went from v5.5.2 straight to 5.7-dev on conda-forge (ref)?

yes. In fact, there is now 5.6.1 that we might want to conda packages at some point. Such a mess...

😅


Very slow tests

test catch_up_via_block_download has been running for over 60 seconds
test crash_recovery has been running for over 60 seconds

Locally they take forever for me, while the CI seems to be handling them somewhat faster.

    for _ in 0..4 {
        // we clear the message queues
        federation.reset_connections();

        let handles = vec![
            federation.start_broadcast(0, 0),
            federation.start_broadcast(1, 0),
            federation.start_broadcast(2, 0),
        ];

        sleep(Duration::from_secs(60)).await;

        for (broadcast_handle, decision_handle) in handles {
            decision_handle.abort();
            assert!(broadcast_handle.await.unwrap() == Shutdown::MidSession(0));
        }
    }

:rofl: . @joschisan . Is this supposed to be like that? We can't have tests that take 4 minutes...

Yes they are supposed to be that long but where not supposed to run in CI, I only used them for testing when I developed the broadcast locally. The long times comes from completing an entire session.

@joschisan Do you want to make them conditional on some env variable or something, so you can only when it makes sense?

right now lets just disable them, I approved you pr for this. I will work out something like that later.


Resolve permissions error when preview is initiated from fork

https://github.com/scpwiki/interwiki/runs/5834681840?check_suite_focus=true
This workflow run failed because it did not have permission to push to the upstream repository.
I believe this happened because the workflow was executed from the fork. The pull_request event is executed in the context of the merge commit, whereas the pull_request_target event is executed in the base repository. For internal PRs, these are identical; for forks, they are not. In particular this means that the action will not have permission to push to the repository when using the pull_request event type, as its GITHUB_TOKEN lacks that permission.
Switching to the pull_request_target event might resolve this, but there are security considerations to take into account: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
Changes shouldn't be needed to this action, but I will need to amend documentation to cover this use case. The README is getting pretty bloated - I should take this chance to move some of the code samples into the repository proper.

As recommended by the linked article, the flow I'm going to go with is a pull_request event that builds the deployment and saves it to an artifact, followed by a workflow_run that downloads the artifact and deploys it.
workflow_run is unique in that it executes with permissions inherited from the base repository, not the fork, so it will be able to deploy code. It's important to ensure that any code execution (i.e. the build script) is run in a non-privileged environment, in this case the pull_request event.
Downside to workflow_run is that it runs totally isolated from the calling context, and won't appear as e.g. a failing check in the PR. This is in contrast with e.g. workflow_call which is tightly integrated with the PR system and will appear as its own check; however, workflow_call does not execute with elevated permissions.
Also, the action currently strongly assumes that it's going to be run from a pull_request event, going so far as to assume github.event refers to a pull request. I need to make it also work for workflow_run, and in so doing I might as well remove its dependency on any specific kind of event.
That'll mean that I need to be able to pass it all the values that it would normally take directly from the pull request, via parameter instead. I can probably just set the defaults to the pull request values.

Would an option here be to have an example that uses pull_request_target for closed & labeled where it requires that a specific label has been applied indicating a review has taken place. The action can then remove the label at the end of the run to ensure that any updates require a fresh review. The closed event can always skip performing a build which prevents the risk of executing code under control of the fork.
I'm planning to set up a local action this way to support preview until workflow_run support is available at least, but I might still keep with the labeled approach to give things a once over before letting it publish either way.

Good idea, if perhaps a little complex to set up and then have your team remember. Depending on the scope of your project, at that point it may be a better idea to outsource that work to somewhere you know it's been done correctly e.g. Netlify, Vercel.

Not knowledgeable about this workflow, but I've been reading the docs and a few issues and I was wondering to get past this security problem is there no way to prompt the repository owners to allow deployment of a preview for the created PR. Ie: Require the owner to click a button or put a comment and only preview the PR after that?

@Fir121 Yes, the button you describe is possible - have a look at Deployment Reviews. I learned about this just the other day from @aspiers in https://github.com/rossjrw/pr-preview-action/pull/6#issuecomment-2054206391
There's any number of things you could put between a forked PR and that PR's preview running your repo with elevated permissions, and you could do any of those things right now, but I'm still wary at this time. That being said, if you happen to take the time to put together something functional that uses this or something like this, I'd be happy to have a look and see if I feel it's worth recommended in this documentation.


upgrade to numpy >2.0

Hi,
I just tried to implement the joulescope into my CI/CD environment.
Unfortunately, I have a dependency mismatch with numpy.
All the other libraries used are already on numpy=^2.0.0 only the joulscope is limiting it to <2.
Do you know if there is anything to do about this?
When will the change be done?
Can I offer support on that?
BR
Thomas

We do plan on migrating to Numpy 2.x, but we have no schedule yet.  Numpy just released 2.0.0 in June, and is already at 2.1.1.  My thought is to let things stabilize for another few months before migrating Joulescope software.
To complicate things, our projects use Cython and Nuitka to compile Python.  These tools also need to support Numpy 2.  When I tried back in June, they still had challenges, but I am sure they are making progress.
To migrate Joulescope software to Numpy 2.x, we need to update the following projects:

jls (pyjls)
joulescope_driver (pyjoulescope_driver)
[pymonocypher](https://github.com/jetperch/pymonocypher]
pyjoulescope
pyjoulescope_ui

We also need to upgrade some private packages.  Overall, this likely ends up being a significant amount of work that we need to schedule.
My recommendation for now is to continue to use Numpy 1.x and other older package versions that continue to support Numpy 1.x.
References

Numpy 2 migration guide
Cython
Nuitka

👍 I'll try to use an older version.
Please feel free to reach out if you need support for upgrading.

Completed in 1.2.0


Bot dashboard

It would be excellent to have either a self-hosted (within the container) or external server (with persistent storage) for displaying logs and metrics.
This expands on #32.

Closing issue - discussed in #122.


Add sanity check for registered entities' stake

Extract and generalize registry's staking sanity checks in go/consensus/tendermint/apps/supplementarysanity.checkStakeClaims() and move them to go/registry/api.SanityCheckStake() function.
Augment the checks to check if an entity has enough stake for all stake claims in the Genesis document to prevent panics at oasis-node start-up due to entities not having enough stake in the escrow to satisfy all their stake claims.
  What's the planned resolution for this when the sanity check fails?
And what's up with the (likely unrelated) CI failure?

ah yeah we are supposed to deregister them if they get slashed below the threshold

This is ready for another review.
Updating various tests made this PR a bit larger, but I tried to split things down into commits, so I suggest reviewing by commits.

ah now we're not sure after all, if we want to delete an entity if it gets slashed below the threshold. cc @peterjgilbert @ravenac95

Hmm... are you worried about a potentially invalid state dump (i.e. genesis file)?
Do we currently de-register entities that fall below the staking thresholds when they are slashed?
If not, this could be a problem.

code-wise though: this doesn't do a full accumulation. could this check miss cases where the amount escrowed is enough, but there isn't enough overall for the entity plus, for example, some nodes?

Good catch! Indeed, the current check, e.g. misses the case when an entity has enough stake to be registered itself, but not enough stake to also register its nodes.
We could augment the sanity checks to create a map of StakeAccumulators for each entity and then add StakeClaims as appropriate (i.e. one for the entity, one for each node's role, ... do we also want to add stake claims for compute and key manager runtimes?).
Finally, the sanity checks would check if an entity's escrow active balance is >= StakeAccumulator.TotalClaims().

Good catch! Indeed, the current check, e.g. misses the case when an entity has enough stake to be registered itself, but not enough stake to also register its nodes.
We could augment the sanity checks to create a map of StakeAccumulators for each entity and then add StakeClaims as appropriate (i.e. one for the entity, one for each node's role, ... do we also want to add stake claims for compute and key manager runtimes?).
Finally, the sanity checks would check if an entity's escrow active balance is >= StakeAccumulator.TotalClaims().

I've implemented that, please take a look.

Hmm... are you worried about a potentially invalid state dump (i.e. genesis file)?
Do we currently de-register entities that fall below the staking thresholds when they are slashed?
If not, this could be a problem.

I've filled a follow-up issue that will address this: #2886.

@pro-wh, could you take another look?


pos_debt_notebook unit-tour-test

Also ensure the pos_debt_notebook_sync does not repeat the whole steps of pos_debt. Some simple stuff as initial_scene tests is enough for it

Also ensure the pos_debt_notebook_sync does not repeat the whole steps of pos_debt. Some simple stuff as initial_scene tests is enough for it

At the moment, don't have a clue about how to do it. To be exactly, "how to pass arguments from python to js-tour-test"


PERF: stop copying frame for astype('category')

I'm going to add a copy to work around https://github.com/pandas-dev/pandas/issues/53658 to fix #6259

Fixed in #6692


Medhelm

Initial implementation of MedAlign functionality

The current implementation is a bit hacky regarding the custom Adapter and Input. I would be fine with merging this immediately if urgently needed, with the expectation that we might make breaking changes to undo the hacks. Otherwise, I'd like some time to think about how to implement this more cleanly.


DOC: Update READMEs

Adding information since the RFC has been merged. Also adding some instructions for adding examples.
Closes #168

Thx for the reviews! Let me know how the changes look

Thank you, Sean! @facaiy, feel free to merge this after you take a look :-)


Move away from dependency on deprecated applicationinsights-js package

This library currently depends on the deprecrated applicationinsights-js which as been moved to @microsoft/applicationinsights-web.
Any plans to move to the nondeprecated dependency to get the latest updates & features?

I have to look back into this one, I'm wondering how many breaking changes there might be 🤔

For us applicationinsights-js shows the expired certificate error since today. Unfortunately, have to switch to another package for this reason.


Raise when get_map gets a invalid space argument

Based on discussion on https://github.com/FZJ-INM1-BDA/siibra-python/pull/455
Fixes #453
TODO: update unit test for parcellations

Stale


New feature: support sending to multiple devices at once

Hi,
For personal use, I made a small update to be able to send to multiple devices at once, using the registration_ids parameter.
So, the first parameter [to] can either be a string for sending to one device or an array of strings to send to many devices.
Are you interested to merge this change to your codebase?
The possible merge request: https://github.com/fcannizzaro/firebase-messaging/compare/master...ktiniatros:dev?expand=1

#2 thanks :+1:


Use poutine.broadcast outside of inference

I love @poutine.broadcast and I wish I could use it to generate data, e.g.
@poutine.broadcast
def model(size, data=None):
    with pyro.iarange("data", size):
        return pyro.sample("x", dist.Bernoulli(0.5), obs=data)

This broadcasts correctly in the context of SVI, but I cannot run this model to generate data.
>>> model(3)
tensor(1.)

Is it possible to make @poutine.broadcast always take effect, even outside of inference?

Sorry, you're right.


Make sure that one-byte element optimised iteration still works

Maybe later we'll have some compression here and better have a regression test in place, just in case...

The SHA-256 folks will come after us if this ever breaks.


No access control?

I've gotten everything working, BUT it means I'm now running a daemon on port 5000 (or any other port number) that anybody can connect to (and create messages in my Mattermost channel). I could use firewall rules to limit connections, but then I would need to know all IPs Gitlab could use. Another alternative would be to add some magic cookie or similar to at least minimize unauthorized connections to the port. Is any of this supported already, and if so, how would I do it?

Hello,
There's no access control within this app.
I only use it on localhost, so no exposed service or open port..
To handle authentication, I guess I would set up a reverse proxy (nginx/apache) with basic auth in front of this daemon, and potentially HTTPS.
I assume that using a hook url of the form http://username:password@ip:port in gitlab will work, so that basic auth can be used easily ...
That's about it without modifications of the python code.

Ah, yes, if you self host there are no issues. If you use hosted Gitlab however.. Thanks for responding anyway.


The error message "Unexpected entry BlobContainerGroupTreeItem" is not very clear

OS: Win10
Build Version: 20191202.1
Regression: Not a Regression (for the previous release build )
Repro Steps:

Enable "Azure Storage: Enable View in File Explorer.
Create a storage account --> Create a blob container --> Click "Open in File Explorer...".
Save the workspace locally --> Modified the folders.uri like below:
azurestorageblob:/subscriptions/..../resourceGroups/.../providers/Microsoft.Storage/storageAccounts/.../Blob Containers
Re-open the edited workspace in VS Code again --> Pop up an error.

Expect:
Display a clear error.

Actual:
Display " Unexpected entry BlobContainerGroupTreeItem ".

I modified the workspace folders.uri with an old version of the URI like you provided but I couldn't repro that error. Do you have any more info on how to repro?


Is there an overall schema (for use with editor autocomplete)?

I had a search around, and I couldn't find an overall schema for ASL, in order to get editor autocomplete working in vscode.
I've put all the schemas from this repository together in a single schema here: https://gist.githubusercontent.com/studds/b9dbba056eaaaf42dfe70c191c12d848/raw/38a37cd9b3c1f48ad622df11261c314d2bf282da/aws-step-function.json
It seems to be working fine, am I reinventing the wheel?

Hi @studds,

Is there an overall schema

There isn't. If needed, we could probably add a compiling step that would aggregate all schema pieces in a single file, in a pre-push hook for instance.

Am I reinventing the wheel?

Maybe 😄 AWS Toolkit for VS now supports StepFunctions, and should already fit your needs.
Let me know if that's enough

Yep, more than enough. Thankfully I didn't spend too much time on this!!


Clarify the assumption of WireTransaction and see how strong the assumption holds for type agnostic

Why
In this PR: #227 , we are taking in WireTransaction format to parse the output by having the assumption of the input transactions for PaymentTx would follow certain data structure format.
As a result, since we are introducing the concept of WireTransaction, we need to clarify what it is and understand the assumption of it. Also, as I've got some concern on how strong the assumption (as in the implementation of the PR) would hold already, would need to evaluate how good is it and how long would it stay if we're coding in that style.
See the discussion here: https://github.com/omisego/plasma-contracts/pull/227#discussion_r317585477
What to do

Understand and doc the definition + assumption of WireTransaction
Evaluate is the assumption good enough in startIFE code.
If above is false, update the code to use a more flexible assumption such as using interface.

@paulperegud , I think it would need your help on the clarification of definition and the assumption part.

[NOTE]
After a call with @paulperegud
Following is my understanding of the assumption introduced from WireTransaction format
Wire transaction format
All transactions (types) would have the following fields and rlp encode with the order:
1 transaction type - uint16
2 [input()]
3 [output()]
4 metadata
Hash of fields 1..4 is a transactionId. Witness data is not included when computing transactionID.
output data structure
All output would be rlp encoding with the following order:

output_guard - bytes32, hash of RLP array containing output_type and specific information related to the output type (example is: [output_type, owner, nonce], nonce is chosen by user that sends transaction)
token_contract - address
amount - [token_standard, token_specific_info] (PS. I think the field need to rename)

FAQ

How to handle ERC721 in output?
token_standard would be the flag of what token_specific_info would be. So for payment, it would specify that the token_specific_info is just going to be amount, while for ERC721, it's going to be like token_uid (or lists of uid).

Personal concern to follow up on

[token_standard, token_specific_info] is a new concept, would need some more effort to code this.
Is the abstraction by token_standard really simpler than relying on existing output_type and decode accordingly?

I kinda recall with the call with @paulperegud  and @pdobacz that we might need to return fund directly back to trader. In that case, we need to differentiate output type directly when output is generated. As a result, I would image output type to be one of the field of output data structure too.
How do you handle that? @paulperegud

closing this. In this round of implementation we still stick with the output structure of: (outputType, guard, token, amont). We acknowledge that this data structure might not be enough for non-fungible token + fungible token swap tx. We can upgrade/extend new tx type with new data structure in the future.


Recent Visual Studio editions 15.6.2+ start spinning 90% CPU forever, on large projects with lots of errors

I left my Visual Studio open during the night and when I got back, the whole machine was sluggish. I saw this in the task manager, slowly going up further (and spiking from 60-90%):

With previous versions, memory used to be an issue, but this is the first time I saw the processor spinning.
Repro steps
Not sure how to repro consistently since I try to prevent this behavior, but it happened during a large refactoring session, where approx. 50 files showed perhaps thousands of errors and several hundreds other files and a dozen or so projects in the same solution compiled fine.
I also couldn't open the debugger to find out what was spinning, or hook up a profiler, the system was too sluggish for that.
Expected behavior
When in rest, the developer environment should be in rest.
Actual behavior
CPU spinning / overload.
Known workarounds
For a few years my modus operandi has been to work for a few hours on a large project and then restart Visual Studio. That used to be necessary because of memory congestion. This is the first time I see it happen with CPU congestion.
Related information
In the past I have seen many occasions where the CPU took 100% of a single processor and VS became sluggish or completely unresponsive. It is possible that recent changes allowed for better multi-threading behavior.
It seems reasonable that whatever kept a single thread running forever in the past, now runs in its own range of threads, leaving the system more responsive than before, but it doesn't finish its task.
The good news is that it was still somewhat responsive and I could close it, even though it took two minutes or so to quit, showing the unload-screen for a long time:

Windows 7, all recent updates and .NET versions available
Visual Studio 15.6.2 Professional, possible also other 15.6.x versions or previews
I'm not sure, but my guess is the large amount of errors has something to do with it: I had the same project open in a compilable state in a different instance, and that didn't start spinning with high CPU

PS: I would appreciate any suggestions on how to give more info on this, or to create a memory dump, or whatever, so that we can at least find out what method is looping. Also, if anybody else has seen this behavior, pointers / suggestions are welcome.

You can take a memory dump in Task Manager (right-click on the devenv.exe process and select "Create Dump File"), which will then save the file in AppData (the location is shown in the UI).
You'll probably need to upload it to a file share, though, since it will be quite large.
My suspicion is that you're in a "loop of death" where FCS data is getting flushed -> added -> flushed -> added forever and ever. A good course of action would be:

Turn off in-memory cross-project references
Turn off the unused opens analyzer (perf fix for it is only in nightlies)
Set the project cache size to be far lower (it used to be 3 in VS 2015)

If that doesn't help, then the answer is, "we need to do the hardcore perf work in the language service necessary to support this scenario".

@cartermp , thanks. I have these settings, which means cache-size was at your suggested setting, I'll try by removing that checkmark:

Not sure how to turn off the unused-opens analyzer (that used to be an option in FSharp Powertools, I believe), but it is certainly on (unused opens are grey).

@abelbraaksma unused opens setting is under Text Editor > F# > Code Fixes

@majocha, thanks, but that looks to me like automatic code fixes, I never thought that was the analyzer:

@abelbraaksm The 1st, 3rd, and 4th all analyze code; though it's only when a document is changed so turning these off is less likely to be a cause and more of a, "Let's see if more advanced features are related at all" kind of thing.

@cartermp, I have turned the 3rd (unused open statements) off. The others are essentially too valuable while coding, especially the one for unused values. That analyzer saved my world several times ;).
I've kept the new settings for a while and left VS open. While after some time it gets slower and slower in the editor, VS as a whole doesn't spin like crazy anymore. Maybe it was a fluke.
Though it keeps being necessary to open/close VS after a couple of hours work. But it has been like that since VS2017 came around anyway. It is generally much faster than VS2015, but in my experience, after some time, typing and syntax coloring starts to get sluggish.
It's essentially fastest (searching is instant, typing and coloring is fast, compiling is fast)  right after an upgrade, which suggests that temp files or an ever growing browse file (don't know where/what it is in F#, but in C++ that used to be a thing you needed to remove every now and then). Project > Clean doesn't erase these files I think (at least, it doesn't speed anything up). The performance drop is large: for instance, compiling a large project takes, say 30 seconds, but after a few weeks it takes 2 minutes. Same for searching: from almost instant, to dozens of seconds after a while. Restarting VS doesn't solve this.
I'd be grateful if someone can tell me what files the setup cleans, so I can do this maintenance by hand.

Unfortunately, I don't really know why it would slow down dramatically like that after a few weeks. I'm not aware of something like a large number of temp files affecting F# performance all-up. This would suggest that the way we read info off disk is getting affected for you, especially since build times are dropping by a lot. @dsyme @KevinRansom any thoughts?

@abelbraaksma I have no idea why VS should be fast after an update and then degrade over time.   Does updating the nightly, have the same affect, or is it just a full VS update where you see this effect?

@abelbraaksma I'm closing this since we don't have a specific repro, please reopen a new issue if you have repro steps, thanks

@dsyme I agree. It's difficult to repro something like this. While I continue to have performance troubles, there's another issue I raised,  with a repro, that has more detail to it. Let's keep this one closed.


Cannot execute as non-root user

Hi, I can run monitoror as a root user without problems, but I prefer to run as a non privileged user, but despite I copied and changed the owner of the files:
-rw-r--r-- 1 stefano stefano     1358 Jun 28 14:52 .env
-rw-r--r-- 1 stefano stefano     1520 Jun 28 15:02 config.json
-rwxr-xr-x 1 stefano stefano 20614027 Jun 27 15:32 monitoror
I have the following error in the UI and I can't understand which variant I should enable. If I add "configVariant": "default" in the config.json I have another error.
Variant "default" is disabled for PING type. Check errors on the server side for the reason
ERROR_DISABLED_VARIANT
{
"type": "PING",
"label": "Google DNS - <IP_ADDRESS>",
"params": {
"hostname": "<IP_ADDRESS>"
},
"configVariant": "default"
}

Hey!
First, you should create an issue, not a pull request.
Then, please read the note in the PING doc to run as non-root: https://monitoror.com/documentation/#ping

Hey so just to confirm there is no way currently to run PING as a non-root user?
From the note

Just read the doc as the suggestion by Alex-D and everything worked.

Just read the doc as the suggestion by Alex-D and everything worked.

Without having to launch as a super-user / non-root?