Cluster config with hostnames vs. IP addresses

Currently to set up clustered Rabbit nodes, the IP's of all the nodes need to be passed in via the manifest. I attempted to set up clustering by passing in hostnames which will always be the same, but the Rabbit jobs kept failing. Is there a property to set to allow hostnames instead of IP's or a way to tweak the scripts to accommodate this?
Thanks!

Hi,
Currently we require that you supply IP addresses, as we don't currently support resolving hostnames in our release for CF.  This is not planned for the near term and so I will close this issue.
Thanks,
Dave


fix: wrong translate

In English Version:

Aggregated total time. Aggregate total time for all invocations of the function, including functions called by this function.

In tradition Chinese Verison:

Aggregated total time。函数所有调用的总时间，不包含此函数调用的函数。

it's meaning that the former translator translate including to chinese meaning '不包含', but actually it's antonym, it really change the Aggregated total time conception meaning
same as this Pr,but I modify in github web page so make two pr.

:tada: This has been pushed live to https://developers.google.com/web/

Digital Marketing! | Work From Home!
Make money online without any expenses!
Our Journey Since 24.12.2012
Subscribe & help us to build a blog !
http://www.mizansurovi1.blogspot.com


terms&condition successfully changed

@MastanSayyad
Successfully changed terms & condition page.
Issue fixes: #138
before

After

Can add padding and margin similar to previous one? @Shrutibansal22

ya sure

@MastanSayyad
I have changed according to your requirement sir.
Kindly preview it.


Roll engine 2b94311a7764..2589d07ee93d (7 commits)

https://github.com/flutter/engine/compare/2b94311a7764...2589d07ee93d
git log 2b94311a7764..2589d07ee93d --first-parent --oneline
2020-04-24<EMAIL_ADDRESS>Fix accessibility focus loss when first focusing on text field (flutter/engine#17803)
2020-04-24<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from _dAFU... to G4HpJ... (flutter/engine#17938)
2020-04-24<EMAIL_ADDRESS>[web] Fix exception when getting boxes for rich text range (flutter/engine#17933)
2020-04-24<EMAIL_ADDRESS>[web] Batch systemFontChange messages (flutter/engine#17885)
2020-04-24<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from kpECk... to _dAFU... (flutter/engine#17929)
2020-04-24<EMAIL_ADDRESS>Roll src/third_party/skia b965ff597315..1e21d14f2b8b (25 commits) (flutter/engine#17928)
2020-04-24<EMAIL_ADDRESS>Roll src/third_party/dart 94178e920ee8..a69cb6d700f5 (22 commits) (flutter/engine#17926)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Commit queue failed; closing this roll.


Only use precondition for incorrect API usage, not for invalid hostname

Using precondition should not be used for user errors, only for incorrect API usage. So we should probably report this error using the delegate's didNotPublish(error:...).
https://github.com/Bouke/NetService/blob/d793820658e7048185c0094fb0f4e5673212e839/Sources/NetService/Responder.swift#L62

Shouldn't the error message read "local." rather than ".local", or do I have those scrambled in my code?


Bug with Secret Note #14

Steps to reproduce:

Start a new save file.
Sleep once to go to Spring 2.
Go to the Community Center and hoe the Stone Junimo.
Delete the Stone Junimo.
Sleep.
Use Stardew Checkup.

It displays that "Reward from Secret Note 14" is left to find, which is false.
Note that if you do not delete the Stone Junimo, and do everything else the same, Stardew Checkup seems to work just fine.
Also note that it does not seem to be possible to get another Stone Junimo (after you delete it). If you go back to the spot and hoe it, then nothing happens.

The only way I can detect if the note reward was found is to search containers and placed objects for the Stone Junimo. If somebody digs it up and then deletes it, there really isn't anything I can do. I can't imagine this is a common occurrence, but if you have some better idea for detecting the reward, I am open to hear it.

As I've said above, when I go back to hoe the same spot on the day after I have deleted the Stone Junimo, I am not able to re-hoe another one. Thus, this implies that this note condition is baked into the XML somewhere.
However, on my current save file, around 3 seasons have passed since I first destroyed the Stone Junimo. As a test, I went back to try and hoe it again, and it did actually give me a 2nd Stone Junimo. Thus, I hypothesize that it might function like a crop, where it takes a certain number of days to "grow back".
With respect to this issue, I think we should close it, but I think it would be helpful to change the description:
Reward from Secret Note 14
-->
Reward from Secret Note 14 (will show as incomplete if the Stone Junimo is destroyed)
This explicitly lets players know about the condition here, which is useful because I imagine that plenty of players destroy all furniture (as it cannot be sold and serves no min-max purpose). Are there any other Secret Note conditions like this?
As a completely separate issue, please fix all of the links for the Secret Notes, as they seem to be broken note.
And while I'm at it, can you please add links for the heart events? e.g. "7♥" under Shane's section links to https://stardewvalleywiki.com/Shane#Seven_Hearts_I
This would be tremendously helpful.

Based upon StardewValley.Locations.Town:DayUpdate, the game replaces the stone junimo every year on Spring 2 so long as you are not a Joja member and the location is clear. So even if you destroy it, it should be possible to get it again later. I can look at some extra phrasing for it though. I will also look at links for the heart events.

Thank you!

I guess I'll close this now since the site has text informing the player that it is inaccurate.

I guess I'll close this now since the site has text informing the player that it is inaccurate.


feat: use operator address as the permissioned address

currently, both x/denommetada and x/hub-genesis have allow list in their params.
we should get this data from the active sequencer (i.e the sequncer is the permissioned address)
to allow better usability, we can have for the sequencer list of "permissioned addresses" to grant permissions as well

I think it's not ideal for 2 reasons:

the usage of multi-sig may be wanted for this
the attack surface increases

Either way the x/hub-genesis "permissioend address" is a temporary solution until we will use IBC for validation the genesis event so don't think it's worth the effort.

closing this as for next stage we're gonna use ibc validation for that


The plugin supports 2021.3

@ptrdvrk Currently, the plugin is marked as compatible with 2021.1 and 2021.2.
2021.3 will be released in the next few weeks. We'd have to verify the plugin is working with this new major version. It's unclear yet if this requires any changes to the code.

@ptrdvrk I forgot that I already raised this a few weeks ago. I'll take a stab at the update.


Create cli.php

I created a comand line interface for dbdiff.

Half a year later... Sorry, completely missed this PR. Thanks!


test run_ack( '--match', 'Sue' ); fails on Windows, chokes on "stdout.log".

On Windows (XP SP2, Strawberry 5.16.2, should not matter), t/ack-match.t failed for me with Out of memory error. This is because ack searches the stdout.log file as it is written into the build dir, during the 5th test:
run_ack( '--match', 'Sue' );
This patch is a (silly) workaround, a better approach for a fix might be to tell the test instance of ack to ignore all/some .logfiles.
     --- Util.pm.original.ack-2.10  Tue Sep 24 23:35:58 2013
     +++ Util.pm    Thu Oct  3 11:33:44 2013
     @@ -178,8 +178,15 @@
          if ( is_windows() ) {
              require Win32::ShellQuote;
              # Capture stderr & stdout output into these files (only on Win32).
     -        my $catchout_file = 'stdout.log';
     -        my $catcherr_file = 'stderr.log';
     +
     +        # Put into parent of build dir, because build dir is searched by
     +        # ack tests.  Test 5 in ack-match.t:
     +        # run_ack( '--match', 'Sue' );
     +        # can fail with "Out of memory" or fill storage volume -
     +        # Test ack reads stdout.log, appending a message for every read line to
     +        # stdout.log, filling up both storage and memory.
     +        my $catchout_file = '../stdout.log';
     +        my $catcherr_file = '../stderr.log';

              open(SAVEOUT, ">&STDOUT") or die "Can't dup STDOUT: $!";
              open(SAVEERR, ">&STDERR") or die "Can't dup STDERR: $!";
     @@ -199,6 +206,8 @@
              close SAVEERR;
              @stdout = read_file($catchout_file);
              @stderr = read_file($catcherr_file);
     +        unlink $catchout_file;
     +        unlink $catcherr_file;
          }
          else {
              my ( $stdout_read, $stdout_write );

Or maybe stdout.log should not get written into the current directory?


fix(using bignumber): using BigNumber instead of number

A part of #468 fix

@cgilbe27 btw, the indexer unit test that is failing is also failing on the default branch


Memory issues

Hello,
I've been working with your docker build for Alfresco and was wondering if its normal to have memory issues when manually building from the Dockerfile instead of pulling from the docker hub.  I never seem to have issues pulling the image down from the hub and running the container, but when downloading the github repository and building from the Dockerfile, I get the following error during the build:
0.97 GB of RAM is not enough to run Alfresco for test or production purposes. Alfresco might not work correctly and if it does, will not perform well. Upgrade the server to have at least 2.0 GB of RAM, and optimally 4.0 GB of RAM. The command '/bin/sh -c /app/assets/install_alfresco.sh' returned a non-zero code: 1
I'm running docker toolbox in a Windows 10 environment.  I noticed that my virtual box VM only have 1024MB of RAM set for it which is likely causing the issue, but why does it work fine when I pull the image down from docker hub?

 In fact, we use the official install script that check the machine requirement before start installation. And the script check that you are the minimum memory for Alfresco before start installation. In not really good situation for docker context. Maybee there aare king of argument to not check the memory requirement during alfresco installation...

Ah I see.  So your staying when you download from the docker hub there may be an argument that prevents the memory check ?  How could I disable that check for the Dockerfile build?

I have the same problem on Mac OS X but in my case it detects 1.95Gb which is always lower than the minimum requirement of 2Gb.

Yep, Alfresco is not packaged to be include on Docker. So we need to use the Alfresco standard installer when build Docker image. The matter is that the Alfresco installer check the server requierement before process the installation. So if you haven't 2go of Ram on the machine that buid the docker image, you get your error. There are no error when the Docker image is build by docker hub or quay.io because of the server that run the build has more than 2go of ram.
I hope it's clear. I don't found any option on Alfresco installer to disable the memory check requirement.


Remove use of GetRuntimeInterfaceMap in IsTypeAwaitable

GetRuntimeInterfaceMap is a rather expensive API and it doesn't look like the use here is warranted.
The replacement should have equivalent behavior.

Cc @jkotas

So this should actually improve the performance of this API 😄 ?

So this should actually improve the performance of this API 😄 ?

We can call it a perf fix - it removes some useless array allocations and the extra work that GetInterfaceMap does and we don't need...


Update utf8CharsetTest.cpp

Sorry for late!!
I added test cases for UTF8 😄
Co-Authored-By: JK Park<EMAIL_ADDRESS>Co-Authored-By: SeongHo Park<EMAIL_ADDRESS>Co-Authored-By: Hyeseong Lee<EMAIL_ADDRESS>Co-Authored-By: SangYeon Min<EMAIL_ADDRESS>Co-Authored-By: suyeon<EMAIL_ADDRESS>Co-Authored-By: YoungSeokHong<EMAIL_ADDRESS>Co-Authored-By: Seohyun<EMAIL_ADDRESS>Co-Authored-By: eunzinn<EMAIL_ADDRESS>Co-Authored-By: kmsaidev<EMAIL_ADDRESS>

Good! 👍 👍


white-black

whiteBlack option passed to the Carousel component, it's an object with the following fields:

hover:

null - default - all the images are colorful
on: - the image on hover is white-black while the others are colorful
off - the image on hover is colorful while the others are white-black

central:

null - default - all the images are colorful
on: - the central image is white-black while the others are colorful
off - the central image is colorful while the others are white-black

visible

null - default - all the images are colorful
on: - all the fully visible images are white-black while the partially visible ones are colorful
off - all the fully visible images are colorful while the partially visible ones are white-black

thumbnails (Boolean, default false) - if set to true, the thumbnails are white-black
whiteBlackWins (Boolean, default false) - if any rules, telling whether the given image should be white-black or colorful, contradict each other, this rule specifies whether the image should be white-black

The issue with "central" prop, in this and other feature proposals, is that there is no central slide in some cases: with centered=false and slidesPerPage=1.
It would make more sense to call it "current" although, it's still problematic in case of centered=false and slidesPerPage > 1.

@Lukasz-pluszczewski
so maybe the central option would be available only for centered=false

@piotr-s-brainhub Sorry, we decided we won't have this feature in react-carousel


[Feature request] Bean lifecycle

We rely on bean lifecycle methods and need to have at least bean.destroy() and container.shutdown() methods.
Spring lifecycle is following:

Actually, I'm not sure that we need to implement all of these hooks but I believe bean.destroy() and container.shutdown() are really necessary.

Can you describe any particular use-case of bean destruction? I've been using Spring for quite some time and I have never had a need to destroy a bean (neither did I ever need to completely shut down the container) 🤔

It needed for implementing graceful shutdowns when your service destroys beans depending on the dependency graph.


[Question] How to create SAS URLs when using System Managed Identity?

I am using adal.NewServicePrincipalTokenFromMSI to create a azblob.TokenCredential.  NewSASQueryParameters seems to only accept azblob.StorageAccountCredential.
How can I generate a SAS URL without using a storage account key on Azure VM with a System Managed Identity?

I would also like to know how to do this. I'm having trouble finding any relevant documentation.

Please refer to the tests: https://github.com/Azure/azure-storage-blob-go/blob/master/azblob/zt_user_delegation_sas_test.go#L87

Please refer to the tests: https://github.com/Azure/azure-storage-blob-go/blob/master/azblob/zt_user_delegation_sas_test.go#L87


Use abspath for template basedir

This fixes issue #130
Signed-off-by: Paul Belanger<EMAIL_ADDRESS>

Merged, thanks.
I've pushed 2.4.2 to pypi with this change.


Runtime plugins (FOR NEW PLUGIN)

Hi @smelukov thanks for your help, can you describe your changes in the PR pls?

This is an enhancement that supports runtime plugins of module-federation2.0


Fix race condition on cilium_ratelimit map

First two commits are preparatory work and third one actually contains the fix. See their descriptions for details.

/test

/test

@pchaigno While backporting this PR I've hit some conflicts because of the ratelimit map not existing in v1.16, i.e. https://github.com/cilium/cilium/pull/29711 which added the map wasn't backported to v1.16 it seems. Should we backport #29711 as well, just resolve conflicts or skip this PR from being backported?

@tklauser My bad, we should skip it. For some reason, I thought we had had that map for a while.


[ButtonGroup] Split Button with href does not style correctly

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯

Expected behavior 🤔

Steps to reproduce 🕹
Steps:

Try the following code. With an href, you get the incorrect styling, without the href, you get the correct styling

<ButtonGroup aria-label="split button">
  <Button href='test.com' style={{ flex: 1 }}>
    Test
  </Button>
  <Button>
    <ArrowDropDown />
  </Button>
</ButtonGroup>

Context 🔦
This functionality used to work in v4 but seems to maybe be broken in v5. I'm open to workarounds in the meantime if anyone has any ideas.
Your environment 🌎
I can't get this to run. It returns with the output: '"C:\Users\Jas\AppData\Local\Yarn\bin\\..\Data\global\node_modules\.bin\envinfo.cmd"' is not recognized as an internal or external command, operable program or batch file.
Any advice?

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
Codesandbox I tried: https://codesandbox.io/s/flamboyant-sun-qml7h0?file=/src/App.tsx

@JLaferri
The result you want to achieve is pretty much simple.
Check below sandbox code and let me know if you have any confusion.
And also I have fixed your link redirection as well on click of the button
Codesandbox


Custom Component losing connection to the P1 Meter

The Home Assistant log has errors in the log of the form:
Error requesting p1 meter data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
These errors started being reported on the 29th January, but they may have been there earlier. We had a powercut that day, and so the logging could have started from scratch again.
The log summary states:
Logger: custom_components.homewizard_energy.sensor
Source: helpers/update_coordinator.py:153
Integration: HomeWizard Energy ([documentation](https://github.com/Unsigus/hass-homewizard-energy), [issues](https://github.com/Unsigus/hass-homewizard-energy/issues))
First occurred: 29 January 2021, 9:50:18 (89 occurrences)
Last logged: 11:30:25
Error requesting p1 meter data: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]

They seem to be fairly random failures, perhaps 2 or 3 times per hour. Is this something to be looked at, or just ignore? Thanks.
The HomeWizard Energy app itself seems to be functioning as normal.
System Health

version
2021.1.5

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

virtualenv
false

python_version
3.8.7

os_name
Linux

os_version
5.4.79-v8

arch
aarch64

timezone
Europe/Amsterdam

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
4950

Installed Version
1.10.1

Stage
running

Available Repositories
773

Installed Repositories
12

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 5.10

update_channel
stable

supervisor_version
2021.01.7

docker_version
19.03.13

disk_total
109.3 GB

disk_used
10.3 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.2.0), Samba share (9.3.0), Mosquitto broker (5.1), OpenZWave (0.9.0), Node-RED (8.0.1), InfluxDB (4.0.1), Terminal & SSH (8.10.0), Grafana (6.0.0)

Lovelace

dashboards
2

mode
auto-gen

resources
8

Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

Hallo,
I can't seem to select the Beta version. I see it in the drop down menu, but when I try and select it in HACS, it seems to revert to version 0.4.3...
<EMAIL_ADDRESS>Is there a workaround? Thanks
Met vriendelijke groeten,
Geoff Coupe
http://gcoupe.wordpress.com/ - the Blog
http://flickr.com/photos/gcoupe - the Photos
https://cloud.collectorz.com/gcoupe/books  - the Library
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:22
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770426396&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bi%2Bkp%2F2NDib4HWqp%2B4GC7WdC5ads6folbXlkvix7GHI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXS7AOC6BKNWJ2KDSDLS4WNV7ANCNFSM4W3NMYZA&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0iejqnvM8%2Bl5j%2B7Tzs1Prs5tG88mNiwLWDsPxfqfaAo%3D&reserved=0.

Hallo,
I can't seem to select the Beta version. I see it in the drop down menu, but when I try and select it in HACS, it seems to revert to version 0.4.3...
<EMAIL_ADDRESS>Is there a workaround? Thanks
Met vriendelijke groeten,
Geoff Coupe
http://gcoupe.wordpress.com/ - the Blog
http://flickr.com/photos/gcoupe - the Photos
https://cloud.collectorz.com/gcoupe/books  - the Library
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:22
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770426396&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bi%2Bkp%2F2NDib4HWqp%2B4GC7WdC5ads6folbXlkvix7GHI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXS7AOC6BKNWJ2KDSDLS4WNV7ANCNFSM4W3NMYZA&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0iejqnvM8%2Bl5j%2B7Tzs1Prs5tG88mNiwLWDsPxfqfaAo%3D&reserved=0.

OK, ignore the last message - I needed to first select an old version before the Beta version became available. Sorry for the trouble.
Met vriendelijke groeten,
Geoff Coupe
http://gcoupe.wordpress.com/ - the Blog
http://flickr.com/photos/gcoupe - the Photos
https://cloud.collectorz.com/gcoupe/books  - the Library
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:22
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770426396&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bi%2Bkp%2F2NDib4HWqp%2B4GC7WdC5ads6folbXlkvix7GHI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXS7AOC6BKNWJ2KDSDLS4WNV7ANCNFSM4W3NMYZA&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0iejqnvM8%2Bl5j%2B7Tzs1Prs5tG88mNiwLWDsPxfqfaAo%3D&reserved=0.

OK, ignore the last message - I needed to first select an old version before the Beta version became available. Sorry for the trouble.
Met vriendelijke groeten,
Geoff Coupe
http://gcoupe.wordpress.com/ - the Blog
http://flickr.com/photos/gcoupe - the Photos
https://cloud.collectorz.com/gcoupe/books  - the Library
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:22
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
Thank you for reporting!
I think you are using version v0.4? This version uses an 'old' method for fetching data. I think this should be solved with the release of v0.5.
If you are using HACS, you could try to install the beta version of 0.5. (You can select 'Reinstall' and then 'Show beta versions'.) You won't loose any data. If you do not use HACS or you don't trust updating, you can ignore the error for now.
Please let me know any results!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770426396&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bi%2Bkp%2F2NDib4HWqp%2B4GC7WdC5ads6folbXlkvix7GHI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXS7AOC6BKNWJ2KDSDLS4WNV7ANCNFSM4W3NMYZA&data=04|01||90470a6eb5bc4525b21208d8c6152831|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477141454468900|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0iejqnvM8%2Bl5j%2B7Tzs1Prs5tG88mNiwLWDsPxfqfaAo%3D&reserved=0.

No worries! Great to see that you want to try!

No worries! Great to see that you want to try!

Hmm,
I've restarted HA, but none of the P1 sensors are available anymore. Any thoughts? Thanks.
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:36
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
No worries! Great to see that you want to try!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770428176&data=04|01||55ea7c80af474b0bae2408d8c61702b0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477149410962711|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=45qhLVYW91hhZ0NX5Dc%2FhezYPSagBClG89EkHPD8xIo%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXV4TK7TX7NPXGGUFT3S4WPHXANCNFSM4W3NMYZA&data=04|01||55ea7c80af474b0bae2408d8c61702b0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477149410972705|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ffRFctytjaV47G0NlWm4zWV6qw61%2FdfCd0fe4mgzx1w%3D&reserved=0.

Hmm,
I've restarted HA, but none of the P1 sensors are available anymore. Any thoughts? Thanks.
From: Duco Sebel<EMAIL_ADDRESS>Sent: 31 January 2021 19:36
To: DCSBL/ha-homewizard-energy<EMAIL_ADDRESS>Cc: gcoupe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DCSBL/ha-homewizard-energy] Custom Component losing connection to the P1 Meter (#11)
No worries! Great to see that you want to try!

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDCSBL%2Fha-homewizard-energy%2Fissues%2F11%23issuecomment-770428176&data=04|01||55ea7c80af474b0bae2408d8c61702b0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477149410962711|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=45qhLVYW91hhZ0NX5Dc%2FhezYPSagBClG89EkHPD8xIo%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABO6EXV4TK7TX7NPXGGUFT3S4WPHXANCNFSM4W3NMYZA&data=04|01||55ea7c80af474b0bae2408d8c61702b0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637477149410972705|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ffRFctytjaV47G0NlWm4zWV6qw61%2FdfCd0fe4mgzx1w%3D&reserved=0.

Is there anything to see in the log? Also, another restart has worked for me sometimes.

Is there anything to see in the log? Also, another restart has worked for me sometimes.

Yup - a second restart has brought everything back. Phew!

Yup - a second restart has brought everything back. Phew!

All right! I will close this issue for now, please let me know if you get this, or another 'no connection' error back! Thanks for the quick replies!

All right! I will close this issue for now, please let me know if you get this, or another 'no connection' error back! Thanks for the quick replies!


[TACHYON-1344] Remove main function of tachyon.master.LocalTachyonCluster

tachyon.master.LocalTachyonCluster has a main function which is not used anywhere. Remove this main function.
https://tachyon.atlassian.net/browse/TACHYON-1344

Can one of the admins verify this patch?

Jenkins, add to whitelist

Jenkins, test this please.

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7132/
Test PASSed.

Thanks for the improvement!

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7140/
Test PASSed.

LGTM. Thanks!


ci: Test on Node 22

there is something regarding node 22 on windows. we excluded it for fastify. we should exclude node22 on windows

This seems to have been reported https://github.com/nodejs/node/issues/52682


reflect relase 1.2.0

@chaudum should this not also add the 1.2 release notes?

superseded by https://github.com/crate/crate/commit/7bf917b227fc56a126279b0744efc2045207f0d4


[NOISSUE] fix: Refactor Modal component

Refactored Acceptor and Broker delete Modal component.

The confirmation modal to delete the acceptor must also work for connectors:  The issue in the current proposal is that that text doesn't adapt to what is supposed to get deleted. This is a regression in behavior, can you fix it please?

@lavocatt , means we need to display the selected acceptor/connectors name in the description message right as we were displaying in the brokers?

@lavocatt , means we need to display the selected acceptor/connectors name in the description message right as we were displaying in the brokers?

It means that the title should be: Permanently delete the acceptor when the user deletes an acceptor. And Permanently delete the connector when the user deletes a connector.
Look at the what the code was doing before your changes:
The subject of the deletion was passed as a parameter. And was used in the title. Is it clearer?

yes Got it. i will update the PR. thanks!


Refactor code for parsing and creating postgresql.conf.

There's surely more that could be done, but this makes it a bit more
readable at least.

I added append functions for constructing the config file from scratch, and replaced the append_conf stuff with that. Please take another look.


mini.pairs: TextChanged event is triggered after <CR>

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.pairs
Description
So I co-maintain a plugin for autosaving (see https://github.com/okuuva/auto-save.nvim). One functionality we offer is to provide a defer_save and a cancel_deferred_save action. Each of these gets a list of events. When one of these events trigger the action is triggered.
As you might guess, defer_save defers a save to be run in the future, where as cancel_deferred_save cancels a pending save. By default the events are:
    defer_save = { "InsertLeave", "TextChanged" },
    cancel_deferred_save = { "InsertEnter" },

Now we had users report a weird thing. When pressing <CR> betwen e.g. {} in insert mode, a save would be deferred. We realized it is because of this plugin, since it remaps <CR> in these situations. I'm not sure what happens but it looks it triggers "InsertLeave" but won't trigger "InsertEnter", because of this code: https://github.com/echasnovski/mini.pairs/blob/694d9beb488ff1afaf3d1977b067e53c827d9af5/lua/mini/pairs.lua#L398
In the end it leads to an unexpected save confuses the user.
How could we go on with this? User @akikanellis showed some solutions here: https://github.com/okuuva/auto-save.nvim/issues/57#issuecomment-2322882389 . Maybe you could give some feedback.
Neovim version
0.10.2
Steps to reproduce
I will provide one if needed, but I think it's more of a technical problem.
Expected behavior
No response
Actual behavior
?

Thanks for the issue!

I'm not sure what happens but it looks it triggers "InsertLeave" but won't trigger "InsertEnter", because of this code: https://github.com/echasnovski/mini.pairs/blob/694d9beb488ff1afaf3d1977b067e53c827d9af5/lua/mini/pairs.lua#L398

This code prevents listed events from being triggered during execution of <C-o> which accompanies <CR> . See 2049bca9c51214ef61a9c29e05cc7ef82556840b for more details.
Both in tests and right interactively I can not reproduce the "... it triggers "InsertLeave" but won't trigger "InsertEnter" ..." part. Typing in Insert mode <CR> with cursor inside {} and 'mini.pairs' set up does not trigger any of the listed there events. Entering and exiting Insert mode with a regular i and <Esc> still work as expected. So I would need a reproduction example here, please (with latest main branch, of course).

What 'mini.pairs' does do, though, is triggering TextChanged event in <CR> (which you outline here). And this indeed seems like an issue.
Would you mind checking if applying the following patch to 'mini.pairs' solves the issue on your end?
diff --git a/lua/mini/pairs.lua b/lua/mini/pairs.lua
index c32efb3..4e2b20f 100644
--- a/lua/mini/pairs.lua
+++ b/lua/mini/pairs.lua
@@ -395,7 +395,7 @@ MiniPairs.cr = function(key)
     -- Temporarily ignore mode change to not trigger some common expensive
     -- autocommands (like diagnostic check, etc.)
     local cache_eventignore = vim.o.eventignore
-    vim.o.eventignore = 'InsertLeave,InsertLeavePre,InsertEnter,ModeChanged'
+    vim.o.eventignore = 'InsertLeave,InsertLeavePre,InsertEnter,TextChanged,ModeChanged'
     H.restore_eventignore(cache_eventignore)

     -- Temporarily redraw lazily for no cursor flicker due to `<C-o>O`.

I am pretty sure that triggered TextChanged was the culprit here and it now should be fixed on latest main.
It would be still useful to see a possible confirmation that 'okuuva/auto-save.nvim' now works with 'mini.pairs'.

@echasnovski I tested this out with latest mini.pairs and auto-save.nvim and it is working as expected, making the vim.api.nvim_get_mode()["mode"] ~= "niI" fix from my comment redundant. Thank you for the fix!

I also tested it and everything works now. Thanks a lot @echasnovski , there is a reason I switched most of my plugins to their mini equivalent :)


BUG/ENH: Added default _transpose into LinearOperator. Fixes 8486

I have submitted possible default implementation of _transpose. As discussed by @Tokixix and @pv  it is based on conjugating and swapping rmatvec and matvec. In similar manner to default implementation of _adjoint.
I had doubts about necessity of new _TransposedLinearOperator subclass, as all essential functionality may be carried out via _CustomLinearOperator.

Needs tests.
A motivation for a separate class could be that it's not really
possible to know what a given _CustomLinearOperator does, whereas it's
possible to reason about the classes.

Is it worthwhile to make the outer conj operate in place?  The inner can’t,
since we don’t want to mutate the input, but we could save that allocation
for the outer. Is there a drawback that I’m missing?
On Sat, Jul 21, 2018 at 9:57 AM Pauli Virtanen<EMAIL_ADDRESS>wrote:

Needs tests.
A motivation for a separate class could be that it's not really
possible to know what a given _CustomLinearOperator does, whereas it's
possible to reason about the classes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/pull/9064#issuecomment-406798430, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACNRkVJEQTZ6YlDLSo4EQGWVxy8r3hTKks5uIzM9gaJpZM4VZoVI
.

np.conj(x) happens to work even if x is sparse, but in-place might not.

I created _TransposedLinearOperator and added unit tests. It doesn't pass on continuous integration though. It probably means that new functionality is not fully covered, but I'm not really sure.

One of the failures is about code style (need to be fixed): https://travis-ci.org/scipy/scipy/jobs/409902898#L741
The other failure is probably some CI hiccup, restarted that.

It seems to be intact now

Fixed a bug (there need to be two conjugations) + added some additional tests.


nudge module.source.value report forward by 1 column

In the interest of highlighting the source string instead of its leading quote, as shown here:

...add 1 to the column location of node.source when reporting.
Probably want to pull this out to some util since it will be needed by a number of rules (no-duplicates shown here).
Also worth opening up PyCharm to see what the impact is there. This may be a Sublime quirk.

seems like this won't help. closing.


Differentiate between maximised and fullscreen borderless state in macOS

Considering them the same looks to be wrong and have been causing state management problems (e.g. switching to borderless in a maximised window applies no effect).
For confirmation, I've added a "current window state" to TestSceneFullscreen, and started playing with the window states while checking what the WindowState value is, after applying this change. Looks to be correct in all scenarios.
https://user-images.githubusercontent.com/22781491/123504990-3427da00-d665-11eb-84b6-93dcd1807508.mp4

Seems to work more correctly with this change.
Bonus points if you can find why that comment was there, and when the underlying behaviour changed.


Detect Country Code from provided Phone Number (if any)

Problem:
With build 3.0.5, the countries is now internal and this breaks an extension function I wrote for my project that needs to initialize an array of countries for manipulation.
Possible Solutions:

If there's a function in CountryPickerView that does what I need (i.e. detect the Country given a Phone Number that may or may not contain a country code), then I can use it. My current ext func returns me the Phone Code as a String if found, otherwise returns an empty String. If CPV has a func that does this, I don't mind if it returns an Optional Country, String, or Array.
If there's another way to get a read-only list of countries, I can make a copy for manipulation.
If the above 2 solutions don't work, maybe include the function I wrote (see below) in a new release?
I can just use v3.0.4, but I'm the kind of person that likes to keep everything up to date. (This is what I'm doing for now)
I could make a fork of 3.0.5 and add my function, but then my project would need to point to my fork, and I would have to constantly rebase, and I don't really wanna have to maintain yet another lib if I don't have to.

More details:
In my project, I wrote an extension function to extract the Country Code (if any) from a provided phone number.
The intention was so that if a User pastes in a phone number into a text field, the CountryPicker can use this function to detect the country code. If a country code is found, my VC can change the flag and remove the country code from the pasted text.
E.g.
If a User pastes "+6512345678" into the TextBox, then the CountryPickerView will update the flag to 🇸🇬 and the TextBox would display "12345678".
But if a User pastes "12345678" into the TextBox, then the CountryPickerView will not update the flag and the TextBox would display "12345678".
This is the function itself with comments. I chose to return a String because I'd rather deal with empty Strings than have to unwrap Optionals and I didn't need the Country (just the CountryCode) in order to manipulate the pasted PhoneNumber String.
func extractCountryCodeFromPhoneNumber(_ phoneNumber: String) -> String {
    guard phoneNumber.count > 1 else { return "" }
    var possibleCodes = countries.map { $0.phoneCode }
    for i in 2...phoneNumber.count {
        let code = phoneNumber.prefix(i).string

        // Need to make sure both the current code and the possibleCodes start with each other to prevent false negatives.
        // E.g. if current code is "+12", this ensures that "+1" (US/Canada) is still included as a possible code
        // while also including "+1242" (Bahamas), "+1264" (Anguila) and "+1246" (Barbados).
        possibleCodes = possibleCodes.filter { $0.starts(with: code) || code.starts(with: $0) }

        // If there no more possible codes, return empty String since there's no point continuing the search.
        if possibleCodes.isEmpty { return "" }

        // If there's only 1 possibleCode and the phoneNumber starts with it, return it.
        // This prevents false positives where checking the code partially returns a single possibleCode but the rest of the phoneNumber doesn't match.
        // E.g. The phoneNumber is like "+878783..." and the current code is "+87", so the only possibleCode is "+872" (Pitcairn).
        // This check will ensure that the phoneNumber actually does starts with "+872".
        // Since this example does not start with the only possibleCode, it will not return it.
        if possibleCodes.count == 1 && phoneNumber.starts(with: possibleCodes[0]) { return possibleCodes[0] }
    }

    // If there are still many possibleCodes even after going through the whole phoneNumber, find the longest possibleCode and return it.
    // E.g. if the phoneNumber is like "+12429832...", this ensures that it returns "+1242" (Bahamas) rather than "+1" (US/Canada).
    return possibleCodes.reduce("") { $0.count > $1.count ? $0 : $1 }
}

The countries property is now public again in 3.0.6.

Thanks!


Yarn install fails

On a fresh build and using yarn instead of npm -1 receiving the following error:
[1/5] 🔍  Validating package.json...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^6.2.2".
error Found incompatible module

Likely related to:  https://github.com/yarnpkg/yarn/issues/1160
adding the --ignore-engines flag fixes this.  yarn --ignore-engines

It has been documented in the installation, thank you!


cargo: update to fail 0.3

This updates to latest fail 0.3. It aligns feature naming to use failpoints everywhere, like the
underlying library.

Rebased on latest master, CI is green. This is ready for review now, PTAL.

LGTM!


Allow serve multiple directories as baseDir

Expected behavior
Allow specify a configuration option to be able to serve some directories like node_modules and bower_components as base directories.
This should be similar to what (browserSync baseDir)[https://www.browsersync.io/docs/options#option-server] option does. This will allow developers to use npm packages for browser unit-testing.
Actual behavior
Right now we should specify all the files coming from node_modules one by one. This is cumbersome. For example if we want to use requirejs, angular and lodash we should do:
files: [
  {pattern: 'node_modules/angular/angular.js', included: false},
  {pattern: 'node_modules/requirejs/require.js', included: false},
  {pattern: 'node_modules/lodash/lodash.js', included: false},
  'test-main.js'
}

since trying to use a glob value for node modules doesn't work, for example doing this:
files: [
  {pattern: 'node_modules/**/*.js', included: false},
  'test-main.js'
}

throws next error:
You need to include some adapter that implements __karma__.start method!

Enviroment Details

Karma version: 1.1.1
Relevant part of your karma.config.js file

    files: [
      {pattern: 'node_modules/angular/**/*.js', included: false},
      {pattern: 'node_modules/angular-mocks/**/*.js', included: false},
      {pattern: 'node_modules/angular-resource/**/*.js', included: false},
      {pattern: 'node_modules/ts-helpers/index.js', included: false},
      {pattern: 'src/**/*', included: false},
      {pattern: 'test/**/*', included: false},
      'test/test-main.js'
    ],
    // list of files to exclude
    exclude: [
      'node_modules/**/test/**/*.js',
      'node_modules/**/*.spec.js',
      'node_modules/**/*.test.js'
    ],

The error about the __karma__.start method is tracked in #2237 and has nothing to do with the behaviour you are looking for. Your second configuration should work fine. Also in general you can easily write a method for the behaviour that you want
function toModule (name) {
  return {
  }
}

with karma 1.2.0 having next code in karma.config.js:
files: [
  {pattern: 'node_modules/**/*.js', included: false},
  'test-main.js'
}

it produces next error message:
25 08 2016 18:41:32.578:ERROR [karma]: { Error: listen ENFILE <IP_ADDRESS>:9876
    at Object.exports._errnoException (util.js:1008:11)
    at exports._exceptionWithHostPort (util.js:1031:20)
    at Server._listen2 (net.js:1240:19)
    at listen (net.js:1289:10)
    at Server.listen (net.js:1385:5)
    at afterPreprocess (/Users/lvargas/projects/js/angular-typescript/node_modules/karma/lib/server.js:174:15)
    at tryCatcher (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/promise.js:509:31)
    at Promise._settlePromise (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/promise.js:566:18)
    at Promise._settlePromise0 (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/promise.js:611:10)
    at Promise._settlePromises (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/promise.js:686:18)
    at Async._drainQueue (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/async.js:138:16)
    at Async._drainQueues (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/async.js:148:10)
    at Immediate.Async.drainQueues (/Users/lvargas/projects/js/angular-typescript/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:566:20)
    at tryOnImmediate (timers.js:546:5)
  code: 'ENFILE',
  errno: 'ENFILE',
  syscall: 'listen',
  address: '<IP_ADDRESS>',
  port: 9876 }

From what I understand it means that Karma Server is trying to open and listen into too many files.

This is because that glob pattern is overly broad.
IMO, that is fine, because a broad glob pattern has huge negative performance implications as well. This is one area where I think supporting has large negative ramifications for the user on the performance side, and that nothing more should be done in karma itself in regards to this area.


Clean up Touchable and Wheelable

Touchable has public properties that should be private.
The variable names in Touchable should be consistent with Wheelable.
Event object property item can also be a function. Misleading name. Consider target

Related issues

https://github.com/taataa/tapspace/issues/101

See issue #110


Link not working

Thank you very much for your work, the link you provided for the pretrained scgpt checkpoint is not working, is it convenient to provide it again?

I upload the checkpoint here: https://drive.google.com/file/d/16bIBimhsNHXiLt1ylx5oC6h2yTHyQYLq/view?usp=sharing
Please let me know if you can download it, thanks!


Add your Matrikelnumber to the deckblatt

Please add your matrikelnumber to the deckblatt.
You can do this under einstellungen.tex
The last one should close the issue.

@Osslack @dominicstein @jrjg

seems to me that everybody has added his matrikelnumber


This PR fixes that, allowing both array and non-array except values.

Thanks!


Issues running train.sh

Dear contributors,
I met some problems reproducing your results.
When I was running ./train.sh under this folder, it reported this error
./train.sh: line 4: ../../../caffe_nd_sense_segmetation/.build_release/tools/caffe.bin: No such file or directory
I have already cloned caffe_nd_sense_segmetation repo but this error persists.
Do you have any ideas of what caused this issue?
Thanks in advance!

You need to compile it to create caffe.bin

Great. Thanks a lot!


Help please 🙏

Hello all, I made a mistake by pasting the address (sending from Nami to Nami receiving address) I thought I was sending to Yoroi. Can I recover my cryptos??? 🙏
https://cardanoscan.io/transaction/837a6aeebc144d1c22bd30b4c5923923a204d86473e2bc6c1f0b51831e667793

@Sunpex Talk to Cardano Support on the Live support page so that your issue can be looked into.

Thank you, My English sucks, to whom exactly should I ask?

Kindly talk with the live support about your issues.

If you sent it from your nami wallet to your nami wallet receiving address the funds should be there, hazelbot uses that method to verify nami accounts


Use in Neovim

Yo @vigoux should we try and pursue something like this for internal use of treesitter? :) I don't know how any of that works, figured I'd just mention it here.

iirc, neovim's internal tree-sitter bindings look kinda similar to these already*, additionally it uses libUV to open grammars' .so and .dll files whereas I have some ifdefs around LoadLibrary and dlopen, but as it's open source, neovim is free to steal/use any of this if any of those super cool core-dev people find it neat ;)
* the only real difference from the glances I've taken are that neovim uses some 5.1-isms (setfenv mostly) to keep references alive, whereas I try to keep this 5.1-5.4 compatible by using the registry and some weak tables

Interesting work!
I'll look into using this for the tree-sitter integration!
Externalising things is always a good thing.


Add explicit Content-Type header for Query requests

Query requests should have a header of
application/x-www-form-urlencoded; charset=utf-8. The vendored version
of requests adds the header
application/x-www-form-urlencoded after our serialization step
but does not add the charset which causes some requests with unicode
content to fail with a signature error.
closes #1244
cc @jamesls @kyleknap @JordonPhillips @dstufft @joguSD

Codecov Report

Merging #1285 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop    #1285      +/-   ##
===========================================
+ Coverage    98.05%   98.05%   +<.01%
===========================================
  Files           45       45
  Lines         7396     7397       +1
===========================================
+ Hits          7252     7253       +1
  Misses         144      144

Impacted Files
Coverage Δ

botocore/serialize.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

This change affects pre-signed URLs generated for STS. Not sure what the best way to address is, but let me offer an example:
Before this change:
curl -X POST 'https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=REDACTED%2F20171114%2Fus-east-1%2Fsts%2Faws4_request&X-Amz-Date=20171114T225312Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Security-Token=REDACTED&X-Amz-Signature=f7f356acde4a03fa1a3e6f4e9ab2814bb95a5624c52d64e30bae253b179444a3'

yields a successful response.
After this change, signature validation obviously fails if I don't include that header
curl -X POST 'https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=REDACTED%2F20171114%2Fus-east-1%2Fsts%2Faws4_request&X-Amz-Date=20171114T225939Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Security-Token=REDACTED&X-Amz-Signature=339c2f6aa431da06382abe3b50c02fbd008cae98c43eba2bf4db791c32a7dbec'
<ErrorResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/">
  <Error>
    <Type>Sender</Type>
    SignatureDoesNotMatch
    <Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message>
  </Error>
  <RequestId>84042574-c98f-11e7-9a11-ff73b2efe87e</RequestId>
</ErrorResponse>

but if I do include the header, AWS API validation stops me instead, stating that When Content-Type:application/x-www-form-urlencoded, URL cannot include query-string parameters:
curl -X POST -H 'Content-Type: application/x-www-form-urlencoded; charset=utf-8' 'https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=REDACTED%2F20171114%2Fus-east-1%2Fsts%2Faws4_request&X-Amz-Date=20171114T225939Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Security-Token=REDACTED&X-Amz-Signature=339c2f6aa431da06382abe3b50c02fbd008cae98c43eba2bf4db791c32a7dbec'
<ErrorResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/">
  <Error>
    <Type>Sender</Type>
    IncompleteSignature
    <Message>When Content-Type:application/x-www-form-urlencoded, URL cannot include query-string parameters (after '?'): '/?Action=GetCallerIdentity&Version=2011-06-15&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=REDACTED%2F20171114%2Fus-east-1%2Fsts%2Faws4_request&X-Amz-Date=20171114T225939Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Security-Token=REDACTED&X-Amz-Signature=339c2f6aa431da06382abe3b50c02fbd008cae98c43eba2bf4db791c32a7dbec'</Message>
  </Error>
  <RequestId>a2d5db9c-c98f-11e7-9b71-dfccdc223045</RequestId>
</ErrorResponse>

Does this work fine on other AWS APIs but not STS?

(I should note that I generated all of the above tokens using import boto3; boto3.client('sts').generate_presigned_url('get_caller_identity', {}))


simpler build for local

Is this version easier for local build?

where do you find the --build option for docker-compose up?
will it force rebuild the image every time?

Yes, it forces rebuild

Usage: up [options] [SERVICE...]

Options:
    -d                         Detached mode: Run containers in the background,
                               print new container names.
                               Incompatible with --abort-on-container-exit.
    --no-color                 Produce monochrome output.
    --no-deps                  Don't start linked services.
    --force-recreate           Recreate containers even if their configuration
                               and image haven't changed.
                               Incompatible with --no-recreate.
    --no-recreate              If containers already exist, don't recreate them.
                               Incompatible with --force-recreate.
    --no-build                 Don't build an image, even if it's missing.
    --build                    Build images before starting containers.
    --abort-on-container-exit  Stops all containers if any container was stopped.
                               Incompatible with -d.
    -t, --timeout TIMEOUT      Use this timeout in seconds for container shutdown
                               when attached or when containers are already
                               running. (default: 10)
    --remove-orphans           Remove containers for services not
                               defined in the Compose file

Do we want this to rebuild everytime ?

If we mount the src directly then I would say no...

There are some frontend recompilation need to happen ,don't think that would work either

ok, this need docker-compose v1.7+

ok done


Massive drift, can you review my config?

I see you've gotten the GPH9 to work with VINS. I have ROS, gopro_ros, VINS-Fusion, Kalibr, etc. set up and running, including extraction using gopro_ros. However, I'm getting massive amounts of positional drift/acceleration, even when the device is sitting still. Simple movements like tracing the edge of a coffee table or driving a small city block, end up with 10s to 100s of meters off, with the path shooting off in one direction.
I've fully calibrated my GoPro per Patrick Geneva's tutorial, and all the bounds in the final report are well within 3 sigma limits. Static, Static IMU, and Dynamic calibration all look very good.
Since you've gotten this working, could you have a look at my config, and let me know if you see anything wrong? And/or do you have your original config posted anywhere?
GoPro Settings

1080p/24
Hypersmoothing is OFF

cam_gph9_stdw.yaml.txt
gph9_stdw_config.yaml.txt

the parameters look good. I am not sure what's happening with your data.

Okay, thanks for having a look.


[Issue#1785]-Create Data Index(DI)/ Jobs Service(JS) Database(DB) migration image

This task is to create a Data Index(DI)/ Jobs Service(JS) Database(DB) migration image, which can be used by Kubernetes/OpenShift job to perform necessary database changes for DI/JS application, before they are started with SonataFlowPlatform. A detailed description can be found here.

[Yes] Your feature/bug fix has a testcase that verifies it
[Yes] You've tested the new feature/bug fix in an actual OpenShift cluster
[Yes] You've added a RELEASE_NOTES.md entry regarding this change

PR job #32 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/32/display/redirect
See console log:

Console Logs
Starting building: KIE » kogito » main » pullrequest » kogito-images.build-image #110Starting building: KIE » kogito » main » pullrequest » kogito-images.build-image #116Starting building: KIE » kogito » main » pullrequest » kogito-images.build-image #115Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-base-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-ephemeralBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-postgres-db-migration: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/32/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@rhkp
One more nitpick regarding the name of the image, considering that the name of the images we have now are like this:
apache/incubator-kie-kogito-jobs-service-postgresql
apache/incubator-kie-kogito-data-index-postgresql
I think this image must have a name like this:
apache/incubator-kie-kogito-service-db-migration-postgresql

PR job #33 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/33/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-postgresqlBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1791 - kogito-postgres-db-migration: https://github.com/apache/incubator-kie-kogito-images/pull/1791 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-postgres-db-migration seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/33/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

This PR is being closed as we are pursuing custom sonataflow-db-migrator, which is a different approach from this one.


add tutorial link

Signed-off-by: Ryo Sato<EMAIL_ADDRESS>

Great! Could you add the corresponding issue to the description? @3100

@bluele Updated the description.


chore: refactored InkAPIPrivateIOCore.h

This commit refactors the header to remove API's mentioned in #6245
Signed-off-by: Shikhar Vashistha<EMAIL_ADDRESS>

Hello, Thanks for working on this.
few things to mention:

Check here as this needs to be removed too if we are going ahead with this cleanup.
Haven't check but on the issue it was mentioned that it would be good to run this by sending an email to the dev@ list. You can include the link to this PR .

Thanks again for working on this.

[approve ci]


Workaround for Dart VM timeout

Workaround solution for: https://github.com/flutter/flutter/issues/121231
See https://github.com/flutter/flutter/issues/120808#issuecomment-1551826299 Error Case 2 for more information.
Sometimes the ios-deploy process does not return the logs from the application. We've been unable to figure out why. This is a solution to workaround that by using idevicesyslog alongside ios-deploy as a backup in getting the log for the Dart VM url. As explained in https://github.com/flutter/flutter/issues/120808#issuecomment-1551826299, when error case 2 happens, the idevicesyslog does successfully find the Dart VM.
Also, in the comments of the code it mentions syslog is not written on iOS 13+, this was added in response to this issue: https://github.com/flutter/flutter/issues/41133.
However, idevicesyslog does in fact work (at least for iOS 16), we use it to collect device logs for our CI tests already: https://github.com/flutter/flutter/blob/1dc26f80f04c1c1091a83c5fead9b3aa83483292/dev/devicelab/lib/framework/devices.dart#L998-L1006
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

However, idevicesyslog does in fact work (at least for iOS 16), we use it to collect device logs for our CI tests already

Oh, this is really interesting. I wonder if a) idevicesyslog was updated to support the new log system; b) ios was updated to support the method idevicesyslog was using; or c) something else?

Sometimes the ios-deploy process does not return the logs from the application. We've been unable to figure out why. This is a solution to workaround that by using idevicesyslog alongside ios-deploy as a backup in getting the log for the Dart VM url. As explained in https://github.com/flutter/flutter/issues/120808#issuecomment-1551826299, when error case 2 happens, the idevicesyslog does successfully find the Dart VM.

Is the solution here actually to default back to using idevicesyslog?

Oh, this is really interesting. I wonder if a) idevicesyslog was updated to support the new log system; b) ios was updated to support the method idevicesyslog was using; or c) something else?

I'm unsure. I looked through idevicesyslog git history and didn't see anything stand out.

Is the solution here actually to default back to using idevicesyslog?

Oh that's a possibility. I'm not sure we should default to idevicesyslog for everyone since it has been an issue in the past, but we could default to it for CI

Is the solution here actually to default back to using idevicesyslog?

Oh that's a possibility. I'm not sure we should default to idevicesyslog for everyone since it has been an issue in the past, but we could default to it for CI

Yeah, let's land this change as is for now. I would be worried about flipping the default without understanding why idevicesyslog started working again :)

If I may chip in, I'd suggest you take a look at replacing ios-deploy with go-ios.
A few copy-pasted arguments:
ios-deploy a fragile dependency:

basically a single Objective-C file containing 3000+ lines of code with no tests.
looks like it's pretty much in maintenance mode (this probably stems from the fact that no one knows what's happening inside of it)
it's somewhat flaky

Meanwhile go-ios:

actively maintained
written in quite clean Go
outputs all logs in JSON
has its own Discord server.

I tried out go-ios and it already does most (if not all - didn't dig in that far) of what is already possible ios-deploy.

If I may chip in, I'd suggest you consider replacing ios-deploy with go-ios in the future.

Thanks for the recommendation. I'll look into it

I'm scheduling retries of the firebase test failures, as those were upstream infra issues

@christopherfujino friendly ping to let you know it's ready for review again


Use viewmodel cache instead of polling the shared preferences on every recomposition

The decision of whether to show the dialog offering to send testnet coins currently requires we ask the shared preferences every time if that dialog has been shown before. We should poll shared preferences once upon creating the viewmodel and cache its response.

Fixed by 95239be.


SeismicPlotter scale options does not work

I noticed some time ago that the scale argument for the constructor of the SeismicPlotter does nothing.   We have workarounds in the tutorials that use the scale algorithm before calling the plot method.   I just looked and the cause of this bug is clear:   it is a feature that the comments say was not completed.  Here, in fact, is the current section that needs to be fixed:
    def _normalize(self, d):
        """
        Normalizes data (d) using scale function.  for ensembles that
        is peak normalization to level self.scale by section. For
        Seismograms each component will be normalized independently.
        For TimeSeries the peak is adjusted to self.scale.

        :param d:  input data to be scanned (must be one of mspass supported
        data objects or will throw an exception)
        :param perf:  clip level as used in seismic unix displays.
        """
        # These are place holders for now.  Requires some new code in ccore
        # to sort absolute values and return perf level - should use faster
        # max value when perf is 100%
        if isinstance(d, SeismogramEnsemble):
            alg_scale(d, scale_by_section=True, level=self.scale)
        elif isinstance(d, TimeSeriesEnsemble):
            alg_scale(d, scale_by_section=True, level=self.scale)
        elif isinstance(d, TimeSeries):
            alg_scale(d, level=self.scale)
        elif isinstance(d, Seismogram):
            alg_scale(d, level=self.scale)
        else:
            raise RuntimeError(
                "SeismicPlotter._normalize:  Received unsupported data type=", type(d)
            )

A simple fix is to replace that whole chain of if-elif-else conditions to this:
d=scale(d,level=self.scale,method='peak')

which would make the _normalize method pretty trivial.   I didn't do this for two reasons:

I think this shows a need to add a self.scaling_method to the SeismicPlotter class constructor that would allow the scaling to be run like this:  d=scale(d,level=self.scale,method=self.scaling_method) .   There are other options for scale, but the method is one that should be selectable as you can get very different results with different scaling methods.  The "perc" algorithm as used in seismic unix, for example, is known to be useful.   What we need really is a default set of arguments for scaling that would  make most plots useful without options.  Right now that is not true as it is too easy to get a black screen from the wrong scaling.   So, I think the group needs to discuss what options we need before I jump in and just fix this crudely.
We need a pytest function for this kind of thing in SeismicPlotter.  There is currently no pytest for the graphics module, which is not good.   I know no way to test if the graphics functionality in pytest, but we should at least test the exception handlers and functions like _normalize that don't produce graphical output.

An additional change we should make with this bug fix:  I strongly recommend we change the default "style" from "wtvaimg" to "wt".   It is faster and more conventional to most seismologists.

I may have fixed this bug in pull request #558 but that needs to be verified before we close this.   I know I fixed the issue with dead data but am less confident I fixed this one.


Feature/issue 1739 writer

Summary:
Updating the code base. This should get us really close to finishing the writer-refactor. This propagates the writer to almost the rest of the code base.
How to Verify:
Run tests. Verify output.
Side Effects:
Will affect CmdStan (already taken care of), PyStan, and RStan.
Documentation:
C++ level documentation to changes taken care of in the PR. No other doc needed.
Reviewer Suggestions:
@betanalpha

Looks fine.

Jenkins, retest this please.

Jenkins, retest this please.


Ring blocks don't get detected on the demo site

They appear as obsolete and don't have the ring slot. They also fail to be rendered if there isn't new lines between {, }, and the blocks inside them.
demo site (without newlines)
demo site (with newlines)
scratch (agnostic to new lines in the ring slot)
Obviously this is not too urgent. I'm guessing it's just some sync problem between the version on Github and Scratch.

Interesting. Presumably this is a regression; the version on the forums should in theory be older.

Ignore the above. I remember now:

You need :: grey ring for something to look like a ring.
{} gets rendered as an embedded command, unless it's inside a ring.
{\n} is always rendered as an embedded script (e.g. the inside of an "if" block).
The forums probably mangle newlines/whitespace in irritating ways. The conversion from BBCode to HTML isn't always convenient.

If anyone wants to fix the inconsistency by sending a PR to scratch-forums, be my guest!

Closing due to the above -- rings should be written ({stamp} :: grey ring)).
Note that the Scratch 3.0 renderer deliberately doesn't support rings.

Closing due to the above -- rings should be written ({stamp} :: grey ring)).

But it should be ({stamp} @addInput): https://github.com/scratchblocks/scratchblocks/releases/tag/v3.1 That works on the forums, and used to work on the wiki.


Preview never shows

Describe the bug
The preview screen never showed anything other than a white blank screen. The tool could not resolve it after multiple attempts. A red X showed next to "Start Application"
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-twyxbq
Steps to reproduce
This was the prompt I gave it: I want to create an interactive webpage that shows covers of books on a shelf as if it is a virtual bookshelf. I want the books to be clickable with a cool animation of the book being taken from the shelf and opening up in a pop-up page with book title, summary, author, publish date, and links to buy the book on Amazon
Expected behavior
I was hoping to preview the code but I could never get the preview to appear
Screen Recording / Screenshot
No response
Platform
Browser name = Safari
Full version = 18.0.1
Major version = 18
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0.1 Safari/605.1.15
performance.memory = undefined
Username = hwilsonia
Chat ID = 71806fdeffac

Additional context

i have the same problem, consistently. I don't think this app actually works yet.

I also see blank screens because I also use the Dark theme. You'll probably find the "No preview available" message using your browser's DevTools. It's in white text over a white background (!!!). It happens with Dark theme only. If you switch themes or disable .bg-white's background-color, it will appear.

Hi all,
Appreciate the feedback here. We are tracking this issue: #1791. You can follow there for updates. If you continue to have this problem, posting the requested details on that issue page would be helpful. Thanks!


chore: Update cmdliner

Problem

The community is moving to cmdliner 1.1+ and we don't want to be left beind
Solution

Update cmdliner, make sure it works with our dependencies and update our usage.

Why this PR is draft?

Why this PR is draft?

Because it doesn't build - we have to change a bunch of things in ./src/bin and ./test/e2e to get this build correctly. But Ulrik was kind enough to do the nix parts for us.

I was planning on doing this with @AngryStitch but we have yet to find time to actually do it :see_no_evil:

There is some additional cleanup we can do here but this at least lets us use the latest Cmdliner

The cleanup I wanted to do is now done so this is ready.


Cant install on termux nodejs 20+

Build error

nvm, the curl method worked.

I also got the curl method working, for anyone wondering it can be found here: https://github.com/bajrangCoder/acode-plugin-acodex#installation

Or you can run a command to get it to work with the regular PKG build system: cd $HOME && mkdir -p .gyp && echo "{'variables': {'android_ndk_path': ''}}" > .gyp/include.gypi


determine alpn-boot version

determining alpn-boot version based on jdk version

Coverage remained the same at 43.491% when pulling 44a14c42623e9fb1c931ec861692f167ae078caf on wk/alpn-boot into 341b967cd47dd9359c7901a9c4edc93110bacbd6 on master.


Upgrade to Malachite 0.4.13

Hi,
I recently received a pull request from a contributor that improved Malachite's multiplication performance. Could you rerun your benchmarks with Malachite 0.4.13?
Malachite also builds with no-std now.
Thanks,
Mikhail Hogrefe

Done, updated to 0.4.14.


Default ImageRegistry is "quay.io or k8s.gcr.io"  but trident image is on docker hub.

so then we get...
quay.io/netapp/trident: unauthorized: access to the requested resource is not authorized

ErrImagePull, Message: rpc error: code = Unknown desc = Error reading manifest 21.01 in quay.io/netapp/trident-autosupport: unauthorized: access to the requested resource is not authorized trident-main: Reason: ErrImagePull, Message: rpc error: code = Unknown desc = Error reading manifest 21.07.1 in quay.io/netapp/trident: unauthorized: access to the requested resource is not authorized]

Trident version: [21.07.1]
RuntimeName:  cri-o
RuntimeVersion:  1.21.2

worked arround by manually (using clush) pulled image from docker and because pull policy is if its not present then it worked out.
did i make a mistake or the setup is broken?

Hi,
were is that default coming from in your environment? Trident uses standard CSI sidecar containers in addition to Trident itself. Those sidecars live on quay.io or k8s.gcr.io (depending on the K8s version), but Trident images themselves have always been on Docker hub. You can override the registry for Trident as well as the sidecars, if you prefer to use an internal registry.
What deployment method did you choose? (Helm, Operator, tridentctl)

we used tridentctl for the install. I reached the docker hub limit thats why ended up trying to fetch from quay. worked arround by login into docker hub.


nuget

can use nuget  ,local not found

@WJdenghuo ,
Yes, you can download and install Aspose.PDF for .NET from Nuget here: https://www.nuget.org/packages/Aspose.PDF/ . Please let us know if you come acrorss any issue.


Distribute workload

Is your feature request related to a problem? Please describe.
Currently, the program is targeted to run on a single instance.  We need high availability, and a way to scale it horizontally.
Describe the solution you'd like
Every new worker should process number of mosaics / number of nodes mosaics. It grants an even distribution of the workload.
We also need to handle topics like:

Uniqueness - a mosaic should not run in two differentes nodes at the same time.
Healthcheck - a way to check if the process is still running. In negative case, we should release the lock so other servers can start process the mosaic.

Suggested approach 1:
Whenever a worker initiates, it should insert or update a key in Redis under the workers namespace. We could use the hostname or a predefined ID for each worker. This is crucial for workload distribution. For instance, if two workers are registered and there are 10 mosaics to be processed, each worker would handle number of mosaics / number of nodes, as initially outlined

Maybe we can expose some metrics of which mosaics are being processed by each worker.
When a worker dies (or is intentionally terminated), the node must be unregistered, either through TTL or graceful shutdown. Subsequently, other workers should take over the tasks that were being processed by the now unavailable worker.
When a new worker joins the cluster, it is necessary to redistribute the workload. For instance, if there are 2 workers processing a total of 12 tasks, each worker handles 6 tasks. If a new worker joins, we need to terminate 2 tasks (possibly selected at random) from each of the currently running workers. The new worker will then take on 4 of these tasks, ensuring that each worker is now processing 4 tasks.
Suggested approach 2:
We can use a framework like asynq and use a Redis as a queue.
Some things like healthchecks and workload distribution will still happen but in a lower degree.
Describe alternatives you've considered
No changes needed.
Additional context
We already use a strategy to lock the mosaic, but it needs to have the node ID in it.

Closed via #35


Not compatible with semver 3.0.2

After running a dependency update on my project I was getting this error:
    import pydantic_numpy.typing as pnd
../../../.cache/pypoetry/virtualenvs/metal-core-aCGQNnAQ-py3.11/lib/python3.11/site-packages/pydantic_numpy/__init__.py:1: in <module>
    from pydantic_numpy.helper.annotation import np_array_pydantic_annotated_typing
../../../.cache/pypoetry/virtualenvs/metal-core-aCGQNnAQ-py3.11/lib/python3.11/site-packages/pydantic_numpy/helper/annotation.py:12: in <module>
    from pydantic_numpy.helper.validation import (
../../../.cache/pypoetry/virtualenvs/metal-core-aCGQNnAQ-py3.11/lib/python3.11/site-packages/pydantic_numpy/helper/validation.py:10: in <module>
    from pydantic_numpy.model import MultiArrayNumpyFile
../../../.cache/pypoetry/virtualenvs/metal-core-aCGQNnAQ-py3.11/lib/python3.11/site-packages/pydantic_numpy/model.py:13: in <module>
    from pydantic_numpy.util import np_general_all_close
../../../.cache/pypoetry/virtualenvs/metal-core-aCGQNnAQ-py3.11/lib/python3.11/site-packages/pydantic_numpy/util.py:4: in <module>
    from semver import Version
E   ImportError: cannot import name 'Version' from 'semver' (unknown location)

with semver on 3.0.2. Downgrading semver to 3.0.1 resolves the issue.
Tbh I'm not sure why this issue just came up, both pydantic-numpy and semver latest release are not super recent. So this might be something else on my side?

Can you provide a method for reproducing from a virtualenv, and your Python version?

It worked for me:
 ╰─λ virtualenv venv
created virtual environment CPython3.11.7.final.0-64 in 187ms
  creator CPython3Posix(dest=/data/can/sand/venv, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/can/.local/share/virtualenv)
    added seed packages: pip==23.3.1, setuptools==69.0.2, wheel==0.42.0
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

 ╭─can@normandy in /data/can/sand as 🧙 took 345ms
 ╰─λ source venv/bin/activate
venv/bin/activate (line 48): Unsupported use of '='. In fish, please use 'set VIRTUAL_ENV '/data/can/sand/venv''.
VIRTUAL_ENV='/data/can/sand/venv'
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
from sourcing file venv/bin/activate
source: Error while reading file 'venv/bin/activate'

 ╭─can@normandy in /data/can/sand as 🧙
[🔴] × source venv/bin/activate.fish

 ╭─can@normandy in /data/can/sand via  v3.11.7 (venv) as 🧙 took 10ms
 ╰─λ pip install semver pydantic-numpy
Collecting semver
  Downloading semver-3.0.2-py3-none-any.whl.metadata (5.0 kB)
Collecting pydantic-numpy
  Downloading pydantic_numpy-4.1.3-py3-none-any.whl.metadata (4.3 kB)
Collecting compress-pickle[lz4] (from pydantic-numpy)
  Downloading compress_pickle-2.1.0-py3-none-any.whl (24 kB)
Collecting numpy>=1.23.0 (from pydantic-numpy)
  Downloading numpy-1.26.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.0/61.0 kB 4.3 MB/s eta 0:00:00
Collecting pydantic<3.0,>=2.0 (from pydantic-numpy)
  Downloading pydantic-2.6.1-py3-none-any.whl.metadata (83 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 83.5/83.5 kB 5.3 MB/s eta 0:00:00
Collecting ruamel-yaml<0.19.0,>=0.18.5 (from pydantic-numpy)
  Downloading ruamel.yaml-0.18.6-py3-none-any.whl.metadata (23 kB)
Collecting annotated-types>=0.4.0 (from pydantic<3.0,>=2.0->pydantic-numpy)
  Downloading annotated_types-0.6.0-py3-none-any.whl.metadata (12 kB)
Collecting pydantic-core==2.16.2 (from pydantic<3.0,>=2.0->pydantic-numpy)
  Downloading pydantic_core-2.16.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.5 kB)
Collecting typing-extensions>=4.6.1 (from pydantic<3.0,>=2.0->pydantic-numpy)
  Downloading typing_extensions-4.9.0-py3-none-any.whl.metadata (3.0 kB)
Collecting ruamel.yaml.clib>=0.2.7 (from ruamel-yaml<0.19.0,>=0.18.5->pydantic-numpy)
  Downloading ruamel.yaml.clib-0.2.8-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl.metadata (2.2 kB)
Collecting lz4 (from compress-pickle[lz4]->pydantic-numpy)
  Downloading lz4-4.3.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.7 kB)
Downloading semver-3.0.2-py3-none-any.whl (17 kB)
Downloading pydantic_numpy-4.1.3-py3-none-any.whl (17 kB)
Downloading numpy-1.26.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (18.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.3/18.3 MB 13.2 MB/s eta 0:00:00
Downloading pydantic-2.6.1-py3-none-any.whl (394 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 394.8/394.8 kB 12.9 MB/s eta 0:00:00
Downloading pydantic_core-2.16.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.2 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.2/2.2 MB 12.5 MB/s eta 0:00:00
Downloading ruamel.yaml-0.18.6-py3-none-any.whl (117 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 117.8/117.8 kB 16.2 MB/s eta 0:00:00
Downloading annotated_types-0.6.0-py3-none-any.whl (12 kB)
Downloading ruamel.yaml.clib-0.2.8-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (544 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 544.0/544.0 kB 13.5 MB/s eta 0:00:00
Downloading typing_extensions-4.9.0-py3-none-any.whl (32 kB)
Downloading lz4-4.3.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 12.3 MB/s eta 0:00:00
Installing collected packages: typing-extensions, semver, ruamel.yaml.clib, numpy, lz4, compress-pickle, annotated-types, ruamel-yaml, pydantic-core, pydantic, pydantic-numpy
Successfully installed annotated-types-0.6.0 compress-pickle-2.1.0 lz4-4.3.3 numpy-1.26.4 pydantic-2.6.1 pydantic-core-2.16.2 pydantic-numpy-4.1.3 ruamel-yaml-0.18.6 ruamel.yaml.clib-0.2.8 semver-3.0.2 typing-extensions-4.9.0

[notice] A new release of pip is available: 23.3.1 -> 24.0
[notice] To update, run: pip install --upgrade pip

 ╭─can@normandy in /data/can/sand via  v3.11.7 (venv) as 🧙 took 8s
 ╰─λ python
Python 3.11.7 (main, Jan 29 2024, 16:03:57) [GCC 13.2.1 20230801] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import semver
>>> semver.
semver.SEMVER_SPEC_VERSION  semver.cmd_bump(            semver.match(
semver.Version(             semver.cmd_check(           semver.max_ver(
semver.VersionInfo(         semver.cmd_compare(         semver.min_ver(
semver.bump_build(          semver.cmd_nextver(         semver.parse(
semver.bump_major(          semver.compare(             semver.parse_version_info(
semver.bump_minor(          semver.createparser()       semver.process(
semver.bump_patch(          semver.finalize_version(    semver.replace(
semver.bump_prerelease(     semver.format_version(      semver.version
semver.cli                  semver.main(
>>> semver.Version()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: Version.__init__() missing 1 required positional argument: 'major'
>>> semver.Version("1.0.0")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/data/can/sand/venv/lib/python3.11/site-packages/semver/version.py", line 125, in __init__
    version_parts = {"major": int(major), "minor": int(minor), "patch": int(patch)}
                              ^^^^^^^^^^
ValueError: invalid literal for int() with base 10: '1.0.0'
>>> semver.Version()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: Version.__init__() missing 1 required positional argument: 'major'
>>> semver.Version(major=1)
Version(major=1, minor=0, patch=0, prerelease=None, build=None)
>>>

I just reinstalled the project from scratch and don't have the issue. No clue what was going before...
Sorry for wasting your time!

No worries, just happy to help! :+1:


[Linked Account] Cadence script for moving FT/NFT from child to parent and vice versa

[ ] ft
[ ] nft

This feature already add in Script.


Expose WrappedComponent property on withSend

cc @solomonhawk
const Button = function ({ send }) {
  return (
    <button type="button" onClick={() => send('action')}>Click me</button>
  )
})

const WrappedButton = withSend(Button)

WrappedButton.WrappedComponent // Button

Codecov Report

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

@@          Coverage Diff          @@
##           master   #287   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          22     22
  Lines         771    772    +1
=====================================
+ Hits          771    772    +1

Impacted Files
Coverage Δ

src/addons/with-send.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


install.ps1 isn't run in PackageReference projects

When migrating from packages.config to PackageReference using this official tool in Visual Studio 2019, the tool warns that Entity Framework's install.ps1 won't be run as such files are not supported in the new PackageReference format. Is this okay?
Further technical details
EF version: 6.3.0
Database Provider: EntityFramework.SqlServer
Operating system: Windows 10)
IDE: Visual Studio 2019 16.3.5

@NetherGranite Depends what you mean by "okay". It's okay in the sense that the package is still usable. However, not being able to run a script on installation means that some things that may have been configured automatically, such as the default connection factory, may now need to be configured manually.

@ajcvickers Is there any documentation stating that some things have to be configured manually in a project that uses PackageReference and how to do so, or does EF6 not officially support PackageReference projects?

@NetherGranite It is supported, but we haven't yet completed the documentation.
This is the way to think about EF6 on .NET Core: it works and is supported, but the experience was designed for .NET Framework in ways that are not a good match for .NET Core. For example, EF6 configuration is based heavily on app.config, which has only minimal functionality in .NET Core. Likewise, .NET Core/modern NuGet requires package references to work correctly, but the NuGet experience for package references doesn't support an install script, which EF6 uses to setup the app.config, and so this can't be done.


Using Win32-OpenSSH for Docker on Windows

Opening issue here for docker/machine as requested by @thaJeztah https://github.com/docker/docker/issues/20583.
Steps to reproduce:

Install Win32-OpenSSH (ex. choco install win32-openssh)
Reboot Windows.
Follow Docker Install instructions for Windows from official documentation using the CMD or PowerShell option (https://docs.docker.com/engine/installation/windows/#using-the-docker-quickstart-terminal)

Expected result: Same result as the documentation specifies.
Actual result: Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
Following the instructions for installing Docker on Windows I ran into an issue which resulted in an error when creating a machine using the docker-machine create command. I narrowed it down to it likely being due to the use of ssh distributed as part of Win32-OpenSSH as opposed to the copy that is installed along with Git. Since the documentation suggests appending as opposed to prepending c:\Program Files (x86)\Git\bin to the PATH environment variable the Win32-OpenSSH copy of ssh.exe is always resolved regardless and ends up failing presumably due to either are hard coded dependency on something related to the bundled Git implementation or a deficit in the Win32-OpenSSH implementation. Since I'm unaware of whether the issue is on the Docker or Win32-OpenSSH side of things I'm posting an issue here to investigate and perhaps answer that question.
Ultimately with the prospect that we may have a well supported ssh capability bundled for windows means that we may be able to simplify the story of tools like this on Windows which may have been born out of the Linux/Unix ecosystem so the sooner issues like this are resolved the better experience we will have for all devs that use these tools. Thanks for all the great work!
OS: Windows 10
docker version:

Client:
Version:      1.10.1
API version:  1.22
Go version:   go1.5.3
Git commit:   9e83765
Built:        Thu Feb 11 19:14:21 2016
OS/Arch:      windows/amd64
An error occurred trying to connect: Get http://<IP_ADDRESS>:2375/v1.22/version: dial tcp <IP_ADDRESS>:2375: connectex: No connection could be made because the target machine actively refused it.

docker info:

An error occurred trying to connect: Get http://<IP_ADDRESS>:2375/v1.22/info: dial tcp <IP_ADDRESS>:2375: connectex: No connection could be made because the target machine actively refused it.

@jpierson please not that the Win32-OpenSSH from the PowerShell team is still a pre-release as marked in the GitHub release page. Sure this should work in the future.
For now I suggest have a look at http://www.hurryupandwait.io/blog/need-an-ssh-client-on-windows-dont-use-putty-or-cygwinuse-git and use Git for Windows which has a working SSH client.
My favorite:
choco install git -params "/GitAndUnixToolsOnPath"

#3509


Move PR guidelines to comment, allow freeform description

The current pull request template isn't really working, imho. Either we just tick all the boxes, or we don't even bother at all. How can we improve this? Make sure PRs all complete including descriptions that make sense?
This PR introduces an even simpler message, since I think "freeform" results in a lower threshold to fill out the description with relevant things, but happy to hear your thoughts.

Perhaps instead of deleting the boxes entirely, we can keep the list of them as reminders. E.g. "Please check that you've done the following (as relevant/appropriate to your changes): ...."