Error when running tensorflow.python.ops.gen_array_ops.identity

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.10.0
Custom Code
Yes
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Probably due to very large input value.

Standalone code to reproduce the issue
import tensorflow as tf
import os
import numpy as np
from tensorflow.python.ops import gen_array_ops
try:
  arg_0_tensor = tf.saturate_cast(tf.constant(-23511698154024, shape=[130, 1000, 1000], dtype=tf.int64,),dtype=tf.uint64)
  arg_0 = tf.identity(arg_0_tensor)
  out = gen_array_ops.identity(arg_0,)
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
2023-01-21 10:40:07.326766: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-01-21 10:40:07.425381: E tensorflow/stream_executor/cuda/cuda_blas.cc:2981] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2023-01-21 10:40:07.893350: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 10:40:07.893521: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 10:40:07.893529: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2023-01-21 10:40:08.391504: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:980] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-01-21 10:40:08.415810: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudnn.so.8'; dlerror: libcudnn.so.8: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/lib/
2023-01-21 10:40:08.415826: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1934] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2023-01-21 10:40:08.416054: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-01-21 10:40:08.427915: W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory.
2023-01-21 10:40:08.521752: W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory.
2023-01-21 10:40:08.683694: W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of<PHONE_NUMBER> exceeds 10% of free system memory.

</details>

@nimashiri Could you refer this link to create a tensor with data type tf.String and, on the occurrence, cast the field to the desired data type , please find the gist in latest TF version where I faced different output.
Thank you!

@synandi vulnerabilities occur when invalid arguments are being sent to APIs. So your reply here is wrong.
@nimashiri this is not a vulnerability, it looks like the code is hanging based on your output. Please consult SECURITY.md before sending new reports as very few of them are really actionable (and they should have been submitted via private channels)


Add new installer failure reason when the install is failing due to new S3 defaults

This relates to OCPBUGS-11636

Skipping e2e as they wouldn't be affected and this change will help out with the bug.


Surya/core 10475/stop rpc rework

Tested by Danny on OSX.
Darwin: https://s3.amazonaws.com/prerelease.keybase.io/darwin-test/Keybase-3.3.0-20190411185237%2Bde7f09db09.dmg
Windows: https://prerelease.keybase.io/windows/Keybase_3.3.0-20190411145310%2Bde7f09db09.amd64.msi

Also, there are a lot of test-cases to consider, mainly around updating and auto-updating the app, and having it restart properly.

Some thoughts. First, this is a high-risk change. It might subtly break the update process that might get people stuck in the middle of their update cycle. We should let it bake for a long time on all platforms.
Sure, but can we get it in without the shell->rpc change on Linux first?

Second, I guess we're kinda hosed in the case where the service is crashed. There's no way to make the RPC and no way therefore to kill kbfs. This could be maybe why it was done the way it originally was (sorry not to think of it earlier). I'm not saying we should abandon this approach, it's just something to think about it.
I mentioned this in the original PR. I can make it support both "standalone" client and RPC, it already does this on Mac.

Third, if Electron is starting off this process off via RPC, and expects to be kill'ed as a result, maybe it should fallback to exiting if it hasn't exited after ~15 seconds?
Exiting just electron, or trying to kill keybase/kbfs itself?

Sure, but can we get it in without the shell->rpc change on Linux first?

Don't understand.

I mentioned this in the original PR. I can make it support both "standalone" client and RPC, it already does this on Mac.

OK!

Exiting just electron, or trying to kill keybase/kbfs itself?

I was thinking just killing itself (since that's pretty easy).

Don't understand

So the main "scary" change is changing what that rpc/cli does on Mac and WIndows right? I can revert that and leave the gui running shell commands if you think that's safer. I'd just change what the Linux command is doing to stop everything instead of just the service, no code change for mac/windows.

I was thinking just killing itself (since that's pretty easy).

It already does this


Should MAP really be "Mean Interpolated Average Precision"?

Hi
I should first say that this is a great project! I was just reading through a section of the source for evaluation and noticed the notion of "MAP", which typically means "Mean Average Precision", is implemented as mean of interpolated average precision:
                prmap_feed_dict[mAP_placeholder] = np.mean(AP[:,1], axis=0)

                #save model with biggest mean average precision
                if np.mean(AP[:,1], axis=0) > best_mAP:
                    best_mAP = np.mean(AP[:,1], axis=0)
                    best_mAP_ckpt = current_model

https://github.com/omni-us/squeezedet-keras/blob/master/scripts/eval.py#L378-L383
This implementation of MAP returns a larger value than the traditional, of course. Can I ask why the mean of inAP is used here?
Thanks

Hi
Thank you. The official Pascal VOC paper refers in section 4 to the interpolated version as Average Precision. The subject is a little confusing, as sometimes it is called differently and I have seen different versions. If your implementation produces others results, this might also be due to different interpolation points ( or a bug on my side).

@nischalhp  Sure.
BATCH_SIZE = 8
LEARNING_RATE  = 0.01
WEIGHT_DECAY = 0.00002
EPOCHS = 100

I've also tried the default LEARNING_RATE and WEIGHT_DECAY values. The loss clearly plateaus well before 100 epochs.


Bug: inline images don't account for concealed text or virtual text in the same line

We don't account for when text is concealed to the left of an inline image.
We don't account for virtual text in the same line as an inline image (nightly only, but soon to be stable).

Examples
unconcealed text:

concealed text:

images rendering inline without concealed text:

problem
There is no good way to get information about text concealed by TS/syntax.
This concealed text causes the desired image position to move, with no way for us to figure that out, we can't display the image in the right spot.
Potential workarounds
There's synconcealed(), but this method returns information about a single character at a time.
There's vim.inspect_pos(), but this also returns information about a single character at a time.
We could try to run a TS query for concealed items? This could work for TS conceals, but would not for only syntax conceals. This seems like the best option, and the one that I will probably attempt next.


Remove package cosmwasm-launchpad

Nobody seems to be using this.

[ ] Delete cosmwasm-launchpad from repo
[ ] Mark @cosmjs/cosmwasm-launchpad as deprecated on npm

I don't know if Terra or Secret are using this. Or they are maintaining their own forks?
@YunSuk-Yeo could you comment for Terra?
@reuvenpo could you comment for Secret?
We can also discuss this on Discord if you are using CosmJS and need this support still.
Everyone else should be on stargate already.

We use a forked version of CosmJS so I don't think any changes to CosmJS will directly affect us, but I'll let @assafmo comment on this

Yeah, we unfortunately have our own fork. A few months ago I suggested extending CosmJS' API a bit so that Secret Network would be able to use it directly and benefit from the progress you guys are making. Let me know what I can do to make this happen. :relaxed:

@assafmo thanks for the answer. My memory was you were going to try to wrap CosmWasmSigner rather than the message transformed idea.
Did you try that? Did it hit issues?
Also, are you planning to upgrade to stargate soon? In which case we can just close this and ensure there is a nice path for core reuse with cosmwasm-stargate

No, I didn't try yet to wrap CosmWasmSigner. I should though...
Yes, we will upgrade to Stargate somewhere this year, but I'm not sure if we'll upgrade our CosmWasm version as well, to not break existing contacts. We'll probably just backport bug fixes you guys made in the past 9 months. Is this a problem with CosmJS?

You will need to fork. Support is mainly with wasmd version.
If you will not be running exactly one of our wasmd versions, we will not guarantee support.

Okay, thanks for the info. We'll try to figure out what's the best approach for us.

Correction: x/wasm versions. Of course we expect you to embed it in your app (and I think you swap out with a custom wasmvm which is great for your use case). The main point is it is tested with a certain set of messages and queries and handlers and if those differ, the CosmJS code may not match.
With stargate we put more effort into making it generic. Thus, you could import all the standard components and build SigningSecretClient on those same basic points, not wrapping SigningCosmWasmClient but at the same level as it. That means, just one package for you to maintain and the rest is upstream.

Given that Secret uses a fork of CosmJS anyways and there is great potential to reuse latest upstream dependencies, we'll remove the package now. I think replacing some of the higher level functionality with a fork while building on top of lower level CosmJS packages is a solid long term solution.

Done 🐎


Ability to enter inside VS node function with double click

Operating system or device - Godot version:
72748d1363d090f33d5ca6b9c00142b5e8f7d78f
Issue description (what happened, and what was expected):
When we are working with multiple VS custom function nodes It would be super convenience if VS editor would allow us to double click on a node to enter 'inside'. If the function inside which we are entering is at the same time scene root, it would be the best if new scene tab would be opened.
It would allow us to move within the 'code' very quickly.

hint: it would be the best if it would work not only for vs scripts but for ordinary gdscripts as well
Steps to reproduce:
Link to minimal example project (optional but very welcome):

Tested on b276d92c8a63887df011032bc95d98bbb9c51c70, it's still valid

As mentioned in the gsoc status report we're working on group visual script node. This is the ability to save groups of visual script nodes as resources and then import as a node.
https://godotengine.org/article/gsoc-2019-progress-report-1-part-1

Closing this bug in favour of #8046


Merge Gmaps adjustments

Included in this PR:

updated sizes of the map in most popular resolutions (with/without sidebar). Missing case function for different resolutions
performance optimization
idrive whell direction for zooming (same as in original map)

To Do:

add case function based on the discobered resolution of the car screen
passing exact resolution to class VirtualDisplayScreenCapture

Please break these changes into discrete, smaller PRs, to reduce the chance of merge conflicts and to have cohesive commits that each describe a single feature or change. I did pull in the JPG quality fix, but haven't worked on the resolution fix yet, because I'm planning to focus on Maps in version 1.4. Thank you for your help!


Fixing javadoc error

Friendly greetings !
i wrote more javadoc and fixed some mistake from the previous PR.
I ran gradle precommit and check
There are some errors unrelated to my commits
meta ticket #221
PS : signoff should be ok this time
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

RESULT: FAILURE ❌

@ker2x there javadoc issues:
* What went wrong:
Execution failed for task ':libs:opensearch-core:javadoc'.
> Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting): '/var/jenkins/workspace/gradle-check/search/libs/core/build/tmp/javadoc/javadoc.options'

i found the problem. ImplNote isn't supported in this version of javadoc.

i can't find any more error related to my commits. i might be wrong, the test reports are difficult to read.

one of your fix that i approved (by mistake, i didn't see the extra line in the diff) generated an error. i pushed a fix

one of your fix that i approved (by mistake, i didn't see the extra line in the diff) generated an error. i pushed a fix

Thank you, apologies for messing it up

Gradle checks may keep failing until the PR is rebased to the latest main.
See https://github.com/opensearch-project/OpenSearch/issues/10032 for some details. Essentially, I think the checks will keep failing on the same test until the PR branch picks up https://github.com/opensearch-project/OpenSearch/commit/91821c79e3d1eb562a3829818cf397e328b84344.

Gradle checks may keep failing until the PR is rebased to the latest main.
See #10032 for some details. Essentially, I think the checks will keep failing on the same test until the PR branch picks up 91821c7.

Thanks @kotwanikunal , all kinds of issues, including
* What went wrong:
Execution failed for task ':test:fixtures:gcs-fixture:composeBuild'.
> Exit-code 1 when calling /usr/bin/docker-compose, stdout: Step 1/11 : FROM ubuntu:18.04


Question: collecting contextual information when crawling for binaries

Hi,
Sorry about posting a question in the issue tracker. I am not sure where to do that otherwise...
I am pretty new to crawler4j and I am trying to find and download some binary files available on a website.
Together with the downloaded binaries I'd like to store some contextual information like the title of the page the binaries were found, the surrounding link text, etc.
I know that HtmlParseData contains some information like title. However, within WebCrawler.visit  I do not have a back reference to the page including the binary, do I? As I understand it correctly, WebCrawler instances are created per thread and therefore could have a state like the last visited HTML page?
Could you please give me some clues what would be the best practice to achieve what I want?
Thanks

Are you using the ImageCrawler or BasicCrawler?

@shalipoto How does that matter? I thought those are just two example implementations of WebCrawler?

For those of you who want to achieve similar things, I've come up with this solution:
public class MyCrawler extends WebCrawler {
   private static Map<WebUrl, MetaInfo> metaInfo = new ConcurrentHashMap<>();

   @Override
   public boolean shouldVisit(Page referringPage, WebURL url) {
      boolean shouldVisit = false;
      // ...
      if (shouldVisit) {
         MetaInfo m= new MetaInfo();
         // ...
         m.title = ((HtmlParseData) referringPage.getParseData()).getTitle();
         metaInfo.put(metaInfo);
      }
      return shouldVisit;
   }

   @Override
   public void visit(Page page) {
      // ...
      MetaInfo m = metaInfo.get(page.getWebURL());
      // ...
      metaInfo.remove(page.getWebURL());
   }

   static class MetaInfo {
      String title;
      // ...
   }
}

Please note that the map has to be declared as static since each worker thread will have its own MyCrawler instance and the actual visit is not necessarily called by the same thread as shouldVisit. Therefore it's necessary to use a ConcurrentHashMap or similar synchronized data structures.
It's also absolutely essential to remove cached items from the map after the meta information had been consumed to not introduce a memory leak.


fix(appeals/web): cannot have more than 29 cases assigned to you

Describe your changes
BOAT-782
Issue ticket number and link
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

Duplicate work from James


Understand ApiNATOMY Code Data

Goal of this card is to understand how we are reading the connectivity model from the json file .
How do we create the scaffold TOO Map from the json with regions and wires? How do we create the Lyphs ?
How are we extracting the position of the lyphs? Position of the scaffold regions and wires?
How is the current application handling the rendering of these objects?
The main use case we are working on :
1 ) Load TOO Map with scaffold regions and wires
2) Load connectivity model
3) Remove scaffold wires and regions from TOO Map, if not referenced inside the connectivity model by 'hostedBy' and 'wiredTo'.
List of resources
https://docs.google.com/document/d/1XWk_XjTKnw7eKm3_sdDc2aGZ2lpeIhVaWInhVhmuxdg/edit

@enicolasgomez This is the json file we can use to test the physiology viewer.
https://scicrunch.slack.com/files/U085FF4TF/F02CZFZLUHY/dev-layout-conn-model.json

For own reference, diagram location:
https://lucid.app/lucidchart/54a2a39d-aba3-4afd-90d0-a4eefd58ccc4
will share to Jesus and Zoran when finished the initial phase


Add support for .sendCode()

Feature request for a .sendMessage() clone that will send contents as a code block.
channel.sendCode(content | Array, format)
E.g.  channel.sendCode('Hello World', 'xl');

I imagine this will also split the message greater than 2000 chars into multiples. All messages then should be wrapped around the same codeblock, so we don't get plain text and bad formatting.
Code could be split into multiple messages by line and not mid-sentence.

Code greater than 2k chars... first message

Second message, hopefully split by lines and not mid-sentence

@datitisev would that be necessary since sendMessage() doesn't do that?

I mean... sendMessage doesn't wrap your message in a code block either 😛
If we don't need the former, we don't need the latter either.
Would be useful, though.

Message splitting is now supported in indev. Is sendCode() useful/helpful enough to include? It would automatically add the split prepend and append properties, if splitting is enabled for it.

I do not believe it has a bit enough use. If people want this, they could make their own. Most bots using code blocks don't have blocks over 2k and they usually how more than just the block such as how my boy TypicalBot has server stats, stats, etc.

After a nice long discussion in Discord, added in 7ff9ac2bccaaadef9bee57daafffe9ef89bb982f.


Wrap-up graph tool public repo (Part 2)

Created by: @pepe-zamarripa Jun 21 2022 at 15:51 CET
Last updated: Jun 21 2022 at 15:51 CET
ClickUp ID: IK-3431
Given
A public repo for  the graph tool
When
A community user wants to access the source code for the graph tool
Then
It should be possible to access the graph tool source code

Commented by: @pepe-zamarripa Jun 08 2022 at 11:40 CET
Hi @andskaal ! I have marked this task as spillover. When you have time, please update the remaining SPs. Cheers!


Fix invalid assertion issues grouping

This PR adds a custom FOutputDeviceError implementation which should allow to hook into Unreal's error handling flow and override assert reporting logic.
By default, an exception is raised whenever assert is fired, which is then captured by crashpad/breakpad backend. The topmost callstack frames for such events are always the same preventing them from being grouped properly and they all appear under a single issue at Sentry.
To avoid this situation instead of crashing the app a corresponding event can be constructed manually and reported via CaptureEvent. Once it's done the app is forced to shut down which somewhat repeats the original flow.
The current problem with the approach suggested here is that the engine's error handling is mixed up with some platform-specific logic (i.e. logging, restoring UI, etc.) which leads to skipping some parts of it when using the new FSentryOutputDeviceError.
Closes #489
Closes #514
Closes #1

On Android assertions are intercepted by FSentryOutputDeviceError which also sets several global tags used for further analysis during the beforeSend on the next application launch.  This change also fixes the #1

@tustanivsky is there an update on this change?

One more thing that comes to mind: We can mark those engine frames as InAppExclude so those won't get considered by the grouping algorithm. And those should be able to be propagated to the respective SDKs.

Since there are quite a few questions regarding the assertions/ensures capturing on Android I'll try to address these with the following explanation:
The general idea of this PR is to hook into Unreal's error handling process using a custom FSentryOutputDeviceError so that whenever assertion is fired we capture a manually created exception event with a proper callstack and shut down the application.
The problem with this approach on Android is that Java event's callstack doesn't contain any C++ frames and thus it's not informative at all. There's no straightforward way to convert a native callstack which we can obtain on Unreal's side to a corresponding Java structure to override the default one either. However, instead of reporting assert in a described way within a single session we can set some flags identifying that it happened and force the app to crash. This allows to pass things over to sentry-native which captures a native crash with a "normal" C++ callstack. Now on the next application launch in beforeSend handler we verify if the crash was an Unreal assertion by checking aforementioned flags and cut off the redundant callstack part if there's any. Also, these flags (if any) should be removed and not get sent to Sentry since we need them only for client-side event pre-processing.
The assertion-specific flags are set to an event via tags and not context since sentry-java can't serialize the latter for native crashes and in this case the required values are lost upon the next application launch. I believe this is a known limitation of Java SDK which we've encountered a couple of times in the past.


Update beginner resources for webd

Added JS Hero and JavaScript30

@shubhamgupta2956 Pass this through some grammar checker like Grammarly please.


Feature Request: Set HELO

Within Docker, the HELO response seems locked into localhost, even thought I've set a hostname when launching the container.  Could you add an option for us to configure the HELO at runtime, or use the hostname automatically?
thanks!

Hi there. I'm confused because the HELO response isn't locked to "localhost", and it already uses the current hostname in the response, not that the response (beyond the 250) is mandatory.
telnet <IP_ADDRESS> 1025
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
220 abf5fb0499d6 Mailpit ESMTP Service ready
HELO <IP_ADDRESS>
250 abf5fb0499d6 greets <IP_ADDRESS>

... where abf5fb0499d6 is the hostname of my docker container running Mailpit, and <IP_ADDRESS> is the IP of my docker server. It sounds to me that you are connecting to localhost so your client is sending a HELO localhost, and is thus receiving a ...greets localhost in the response.
What is it that you are trying to achieve exactly?

It would actually be useful to be able to override HELO string @axllent
My specific use case is GMail's relay service which rejects any HELO string that isn't configured as one of the domains on the account.
I made a few simple changes to implement this via an extra variable in config file for relay and it is working in my environment.
Can I push a branch for you to check out the changes and hopefully approve?

@daqqad I'm not sure what impact your approach would have, so maybe best you sent a PR so I can see. Can't promise anything, but we can continue the discussion there. Please note that I'm currently very busy, so it may take a couple of days to review and get back to you, thanks.


Update to work better with UI

:tada: This PR is included in version 1.3.0 :tada:
Your semantic-release bot :package::rocket:


Remove empty bullet in log streaming documentation (for GHES versions)

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
<EMAIL_ADDRESS>What part(s) of the article would you like to see updated?
In the GHES versions of the docs, there is an empty bullet point in the about section:
<EMAIL_ADDRESS>Additional information
No response

👋 @adamrr724 Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

@adamrr724  Thanks for opening an issue! ⚡
You, or anyone else, are welcome to open a PR removing that empty bullet point from About audit log streaming. ✨


false positive release duplicate for multi context

releases:
  # {{ range $c := $clusters }}
  - name: {{ $name }}
    <<: *options
    chart: oci://registry-1.docker.io/bitnamicharts/bla-bla
    context: {{ .context}}
  # {{- end }} finish

extend uniqname like release@ns@context

That's backward incompatible changes, need to specifically note that in changelog

fixed in #914


Add file annotations to errors

We have errors surfaced in the issue navigator which is great, but they aren't linked to the .xcstrings file so clicking them takes you to the build log.
While we can't do line number navigation, it might be better if we take you to the file still?

This is done, but it doesn't work as well like it did with run scripts back in the day.. Maybe because the catalog format has a custom UI rather than just being source code?


Retrying pings and ignoring failed pings

At first I wrote my own simple client for healthchecks.io with just the minimal features that I need, but then I thought, someone must have done this already, so I searched and found your project. It's very clean and easy to understand, so well done.
Is your feature request related to a problem? Please describe.
My client does two things which I'm missing in yours, which is preventing me from throwing away mine and just using yours:

Retrying pings (by wrapping the requests.request function in a tenacity.retry decorator for all requests that are safe to retry (basically all of the ping API and some of the management API).
Ignore ping failures (because we would rather see a failing ping on the dashboard than crash the script). This is especially useful when monitoring scripts that don't need an internet connection to finish their job, but just use the internet connection to ping, and that connection is sometimes flaky. We would rather let the script finish and have a false positive on the dashboard, than let the script crash. An example of this is a backup script running on a VM somewhere.

Describe the solution you'd like
There are a few possible options:

Make the request back end pluggable – instead of this client prescribing the use of httpx. This can be done with proper typing by defining a Protocol with a __call__ method stub.
Keep using httpx, but wrap some calls in retries using tenacity AND add a flag to the client contructor and/or to specific methods to ignore all errors.

Describe alternatives you've considered

Monkey-patch the check_response and check_ping_response methods of your client. :/
Keep using my own client instead of contributing to yours :(
Let my backup scripts fail when the internet is flaky due to pings not going through :(((

Additional context
N/A

Hi @rudolfbyker, thank you for the issue.
At this point, this library is in maintenance mode. I am not actively using healthchecks.io anymore in my workflow, so I am no longer using their API daily. I will review PRs if you are interested in contributing.
I am not a big fan of adding retries to the library itself. I would leave that to the user. Could you wrap calls to success_ping or fail_ping in a retry wrapper in your code? They both raise unique exceptions you could use to control the retry behavior. You could also catch the exceptions in your script for when your internet is down and not fail there.
I think the pluggable backend is the best route to go if you want to contribute.


[Feature request] Allow user to swap onchain sats into LN sats.

Is your feature request related to a problem? Please describe.
There is no (easy) way for a user who has onchain sats in a different wallet to spend them on LN using LNbits.
The original implementation of LNDhub has a feature where the user of the custodial Lightning wallet can send funds to an onchain address (presented in Bluewallet als the refill option) belonging to the custodian's lightning node.
The user's custodial LN balance is then increased by the amount received onchain by the LN node, thus letting the user refill his wallet.
I think it would be nice for LNbits to also have this feature.
Describe the solution you'd like

Add a refill button to the LNbits wallet, when clicked it should request the next unused onchain address from the LN node and present the address in text and QR form for the user.
The user can send funds to the address.
LNbits monitors if funds have been received.
When funds have been sent and ~6 confirmations have passed the same amount of sats is added to the user's LNbits wallet.
If the user clicks refill but does not send funds, another user who also clicks refill should have a different address generated so LNbits can track which user actually used the refill option.
If a user clicks refill but does not send funds, the next time he clicks refill he should be presented with the same address.
If a user clicks refill and sends funds which receive 6 confirmations should have a new address generated the next time he uses the refill option.

Downsides:
LNbits needs to monitor the onchain wallet of the LN node.
Upsides:
A user who already knows how to make onchain transactions can easily (re)fill his LNbits wallet and spend sats on LN.
The LN node does not need to trust the user.
Describe alternatives you've considered
The user could contact the LNbits admin to swap onchain sats for LN sats by calling him from the nearest phonebooth.

have you seen, https://github.com/lnbits/boltz-extension/ ?

@Xiphid can the issue be closed? Boltz and Deezy extensions seem to do what you want.


lnwire.Error: failing link - unable to synchronize channel states

Background
Remote force close between LND and CLN node on reestablishing a channel:
failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required

Your environment

version of lnd: lnd-0.15.1-beta
which operating system (uname -a on *Nix): Linux node 5.15.0-46-generic 49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
version of btcd, bitcoind, or other backend: bitcoind 23
any other relevant environment details: hybrid setup

Steps to reproduce
Having a flaky Tor connection. Waiting for a force close to happen. Not really reproducable.
Expected behaviour
Connectivity resolved, Channel successfully resumed.
Actual behaviour
See logs (peer and channel point) below:
channel point w/ force close:
02:36:19.415 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=734054:976:20, HTLC ID=34782)->(Chan ID=750085:2303:0, HTLC ID=1237)
02:36:19.472 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=734054:976:20, HTLC ID=34782) from mailbox
02:36:34.810 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:39:08.021 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345104)->(Chan ID=750085:2303:0, HTLC ID=1238)
02:39:08.078 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345104) from mailbox
02:39:18.793 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:39:18.793 [DBG] HSWC: ChannelLink(x:0): Failed to send 365325536 mSAT
02:39:19.209 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345107)->(Chan ID=750085:2303:0, HTLC ID=1239)
02:39:19.265 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345107) from mailbox
02:39:30.001 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:39:30.001 [DBG] HSWC: ChannelLink(x:0): Failed to send 36857550 mSAT
02:39:30.217 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345110)->(Chan ID=750085:2303:0, HTLC ID=1240)
02:39:30.275 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345110) from mailbox
02:39:40.638 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:39:40.638 [DBG] HSWC: ChannelLink(x:0): Failed to send 454664958 mSAT
02:39:41.865 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345112)->(Chan ID=750085:2303:0, HTLC ID=1241)
02:39:41.921 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345112) from mailbox
02:39:52.339 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:39:52.339 [DBG] HSWC: ChannelLink(x:0): Failed to send 681995938 mSAT
02:39:53.634 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345113)->(Chan ID=750085:2303:0, HTLC ID=1242)
02:39:53.690 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345113) from mailbox
02:40:04.035 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:40:04.035 [DBG] HSWC: ChannelLink(x:0): Failed to send 795661429 mSAT
02:40:05.292 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345114)->(Chan ID=750085:2303:0, HTLC ID=1243)
02:40:05.347 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345114) from mailbox
02:40:16.432 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:40:16.432 [DBG] HSWC: ChannelLink(x:0): Failed to send 852494674 mSAT
02:40:17.662 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345115)->(Chan ID=750085:2303:0, HTLC ID=1244)
02:40:17.718 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345115) from mailbox
02:40:31.833 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
02:40:31.833 [DBG] HSWC: ChannelLink(x:0): Failed to send 880910798 mSAT
03:22:52.996 [DBG] HSWC: ChannelLink(x:0): forwarding 1 packets to switch: replay=false
03:22:52.999 [DBG] HSWC: ChannelLink(x:0): queueing removal of FAIL closed circuit: (Chan ID=750085:2303:0, HTLC ID=1842)->(Chan ID=734054:976:17, HTLC ID=0)
03:22:53.004 [DBG] HSWC: ChannelLink(x:0): removing Fail/Settle packet (Chan ID=750085:2303:0, HTLC ID=1842) from mailbox
03:28:25.626 [INF] HSWC: ChannelLink(x:0): stopping
03:28:25.627 [INF] HSWC: ChannelLink(x:0): exited
03:28:27.414 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
03:28:27.416 [INF] HSWC: ChannelLink(x:0): starting
03:28:27.417 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
03:28:27.417 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7185952280 mSAT
03:28:27.417 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
03:28:30.450 [INF] HSWC: ChannelLink(x:0): received re-establishment message from remote side
03:28:30.461 [DBG] HSWC: ChannelLink(x:0): loaded 3 fwd pks
03:28:30.461 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6728
03:28:30.463 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6729
03:28:30.465 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6730
03:32:57.923 [INF] HSWC: ChannelLink(x:0): stopping
03:32:57.923 [INF] HSWC: ChannelLink(x:0): exited
03:33:20.181 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
03:33:20.182 [INF] HSWC: ChannelLink(x:0): starting
03:33:20.183 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
03:33:20.183 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7185952280 mSAT
03:33:20.183 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
03:33:21.158 [INF] HSWC: ChannelLink(x:0): received re-establishment message from remote side
03:33:21.160 [DBG] HSWC: ChannelLink(x:0): loaded 0 fwd pks
03:37:33.321 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345205)->(Chan ID=750085:2303:0, HTLC ID=1245)
03:37:33.379 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345205) from mailbox
03:39:00.701 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:39:00.701 [DBG] HSWC: ChannelLink(x:0): Failed to send 342716531 mSAT
03:39:01.021 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345212)->(Chan ID=750085:2303:0, HTLC ID=1246)
03:39:01.077 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345212) from mailbox
03:40:00.001 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:40:00.001 [DBG] HSWC: ChannelLink(x:0): Failed to send 44036209 mSAT
03:40:00.318 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345213)->(Chan ID=750085:2303:0, HTLC ID=1247)
03:40:00.374 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345213) from mailbox
03:41:08.979 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:41:08.979 [DBG] HSWC: ChannelLink(x:0): Failed to send 246175019 mSAT
03:41:10.297 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345214)->(Chan ID=750085:2303:0, HTLC ID=1248)
03:41:10.353 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345214) from mailbox
03:42:10.242 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:42:10.242 [DBG] HSWC: ChannelLink(x:0): Failed to send 369260830 mSAT
03:42:11.499 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345215)->(Chan ID=750085:2303:0, HTLC ID=1249)
03:42:11.554 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345215) from mailbox
03:42:22.068 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:42:22.068 [DBG] HSWC: ChannelLink(x:0): Failed to send 430803734 mSAT
03:42:23.325 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345216)->(Chan ID=750085:2303:0, HTLC ID=1250)
03:42:23.381 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345216) from mailbox
03:43:05.706 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
03:43:05.706 [DBG] HSWC: ChannelLink(x:0): Failed to send 400031782 mSAT
04:10:14.159 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345243)->(Chan ID=750085:2303:0, HTLC ID=1251)
04:10:14.217 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345243) from mailbox
04:11:15.948 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:11:15.948 [DBG] HSWC: ChannelLink(x:0): Failed to send 211794535 mSAT
04:11:16.230 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345250)->(Chan ID=750085:2303:0, HTLC ID=1252)
04:11:16.286 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345250) from mailbox
04:12:26.607 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:12:26.607 [DBG] HSWC: ChannelLink(x:0): Failed to send 40647941 mSAT
04:12:26.933 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345251)->(Chan ID=750085:2303:0, HTLC ID=1253)
04:12:26.988 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345251) from mailbox
04:12:28.677 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:12:28.677 [DBG] HSWC: ChannelLink(x:0): Failed to send 439970324 mSAT
04:12:29.934 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345252)->(Chan ID=750085:2303:0, HTLC ID=1254)
04:12:29.989 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345252) from mailbox
04:13:15.541 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:13:15.541 [DBG] HSWC: ChannelLink(x:0): Failed to send 219984862 mSAT
04:13:16.867 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345253)->(Chan ID=750085:2303:0, HTLC ID=1255)
04:13:16.922 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345253) from mailbox
04:14:10.729 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:14:10.730 [DBG] HSWC: ChannelLink(x:0): Failed to send 329977092 mSAT
04:14:12.019 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345254)->(Chan ID=750085:2303:0, HTLC ID=1256)
04:14:12.075 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345254) from mailbox
04:14:13.452 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:14:13.452 [DBG] HSWC: ChannelLink(x:0): Failed to send 384973708 mSAT
04:14:14.675 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=345255)->(Chan ID=750085:2303:0, HTLC ID=1257)
04:14:14.730 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=0:0:0, HTLC ID=345255) from mailbox
04:14:16.252 [DBG] HSWC: ChannelLink(x:0): settle-fail-filter &{1 [0]}
04:14:16.252 [DBG] HSWC: ChannelLink(x:0): Failed to send 357474899 mSAT
04:16:43.404 [INF] HSWC: ChannelLink(x:0): stopping
04:16:43.404 [INF] HSWC: ChannelLink(x:0): exited
04:16:43.413 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
04:16:43.415 [INF] HSWC: ChannelLink(x:0): starting
04:16:43.416 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
04:16:43.416 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7185952280 mSAT
04:16:43.416 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
04:16:46.183 [INF] HSWC: ChannelLink(x:0): received re-establishment message from remote side
04:16:46.240 [DBG] HSWC: ChannelLink(x:0): loaded 26 fwd pks
04:16:46.240 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6731
04:16:46.242 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6732
04:16:46.244 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6733
04:16:46.246 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6734
04:16:46.248 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6735
04:16:46.249 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6736
04:16:46.251 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6737
04:16:46.252 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6738
04:16:46.254 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6739
04:16:46.255 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6740
04:16:46.256 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6741
04:16:46.257 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6742
04:16:46.259 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6743
04:16:46.260 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6744
04:16:46.261 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6745
04:16:46.262 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6746
04:16:46.263 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6747
04:16:46.264 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6748
04:16:46.265 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6749
04:16:46.267 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6750
04:16:46.268 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6751
04:16:46.269 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6752
04:16:46.270 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6753
04:16:46.271 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6754
04:16:46.272 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6755
04:16:46.273 [DBG] HSWC: ChannelLink(x:0): removing completed fwd pkg for height=6756
05:14:34.422 [INF] HSWC: ChannelLink(x:0): stopping
05:14:34.422 [INF] HSWC: ChannelLink(x:0): exited
05:14:34.430 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
05:14:34.432 [INF] HSWC: ChannelLink(x:0): starting
05:14:34.433 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
05:14:34.433 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7185952280 mSAT
05:14:34.433 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
05:14:35.964 [INF] HSWC: ChannelLink(x:0): received re-establishment message from remote side
05:14:35.966 [DBG] HSWC: ChannelLink(x:0): loaded 0 fwd pks
06:17:25.019 [DBG] HSWC: ChannelLink(x:0): forwarding 1 packets to switch: replay=false
06:17:25.772 [DBG] HSWC: ChannelLink(x:0): queueing removal of FAIL closed circuit: (Chan ID=750085:2303:0, HTLC ID=1843)->(Chan ID=746762:2141:1, HTLC ID=5873)
06:17:25.781 [DBG] HSWC: ChannelLink(x:0): removing Fail/Settle packet (Chan ID=750085:2303:0, HTLC ID=1843) from mailbox
06:54:49.909 [DBG] HSWC: ChannelLink(x:0): queueing keystone of ADD open circuit: (Chan ID=734054:976:20, HTLC ID=34811)->(Chan ID=750085:2303:0, HTLC ID=1258)
06:54:49.967 [DBG] HSWC: ChannelLink(x:0): removing Add packet (Chan ID=734054:976:20, HTLC ID=34811) from mailbox
06:54:57.593 [INF] HSWC: ChannelLink(x:0): stopping
06:54:57.593 [INF] HSWC: ChannelLink(x:0): exited
06:55:02.896 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:55:02.898 [INF] HSWC: ChannelLink(x:0): starting
06:55:02.899 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:55:02.899 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:55:02.899 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:55:03.796 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:55:03.796 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:55:03.796 [INF] HSWC: ChannelLink(x:0): exited
06:55:03.796 [INF] HSWC: ChannelLink(x:0): stopping
06:55:09.381 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:55:09.383 [INF] HSWC: ChannelLink(x:0): starting
06:55:09.384 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:55:09.384 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:55:09.384 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:55:12.167 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:55:12.167 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:55:12.168 [INF] HSWC: ChannelLink(x:0): exited
06:55:12.168 [INF] HSWC: ChannelLink(x:0): stopping
06:55:18.717 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:55:18.719 [INF] HSWC: ChannelLink(x:0): starting
06:55:18.720 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:55:18.720 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:55:18.720 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:55:20.125 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:55:20.125 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:55:20.125 [INF] HSWC: ChannelLink(x:0): exited
06:55:20.125 [INF] HSWC: ChannelLink(x:0): stopping
06:55:30.673 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:55:30.675 [INF] HSWC: ChannelLink(x:0): starting
06:55:30.676 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:55:30.676 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:55:30.676 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:55:31.676 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:55:31.676 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:55:31.676 [INF] HSWC: ChannelLink(x:0): exited
06:55:31.877 [INF] HSWC: ChannelLink(x:0): stopping
06:55:49.260 [DBG] NANN: Marking channel(x:0) pending-inactive
06:55:52.360 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:55:52.361 [INF] HSWC: ChannelLink(x:0): starting
06:55:52.362 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:55:52.362 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:55:52.362 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:55:53.372 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:55:53.372 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:55:53.372 [INF] HSWC: ChannelLink(x:0): exited
06:55:53.372 [INF] HSWC: ChannelLink(x:0): stopping
06:56:35.332 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:56:35.334 [INF] HSWC: ChannelLink(x:0): starting
06:56:35.335 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:56:35.335 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:56:35.335 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:56:36.210 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:56:36.211 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:56:36.211 [INF] HSWC: ChannelLink(x:0): exited
06:56:36.211 [INF] HSWC: ChannelLink(x:0): stopping
06:58:03.341 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
06:58:03.343 [INF] HSWC: ChannelLink(x:0): starting
06:58:03.344 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
06:58:03.344 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
06:58:03.344 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
06:58:04.596 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
06:58:04.596 [ERR] HSWC: ChannelLink(x:0): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
06:58:04.596 [INF] HSWC: ChannelLink(x:0): exited
06:58:04.796 [INF] HSWC: ChannelLink(x:0): stopping
07:00:01.996 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
07:00:01.997 [INF] HSWC: ChannelLink(x:0): starting
07:00:01.998 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
07:00:01.998 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
07:00:01.998 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
07:00:03.013 [INF] HSWC: ChannelLink(x:0): stopping
07:00:03.013 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: link shutting down
07:00:03.013 [DBG] HSWC: ChannelLink(x:0): unable to sync channel states, link is shutting down
07:00:03.013 [INF] HSWC: ChannelLink(x:0): exited
07:05:19.518 [INF] PEER: Peer(b): loading ChannelPoint(x:0)
07:05:19.519 [INF] HSWC: ChannelLink(x:0): starting
07:05:19.520 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(x:0)
07:05:19.520 [INF] HSWC: ChannelLink(x:0): HTLC manager started, bandwidth=7172234688 mSAT
07:05:19.520 [INF] HSWC: ChannelLink(x:0): attempting to re-synchronize
07:06:48.971 [DBG] NTFN: Found spend of outpoint=x:0, script=0 c: spend_tx=x, block_height=752360
07:06:49.162 [DBG] NTFN: Found spend of outpoint=x:0, script=0 c: spend_tx=x, block_height=752360
07:06:49.162 [DBG] NTFN: Spend request outpoint=x:0, script=0 c spent at tip=752360
07:06:58.373 [INF] NANN: Announcing channel(x:0) disabled [detected]
07:06:58.386 [INF] NTFN: Dispatching confirmed spend notification for outpoint=x:0, script=0 c at current height=752360: v[0] spending x:0 at height=752360
07:06:58.449 [ERR] NANN: Unable to sign update disabling channel(x:0): edge not found
07:06:58.449 [DBG] NANN: Removing channel(x:0) from consideration for passive disabling
07:06:58.654 [INF] CNCT: Unilateral close of ChannelPoint(x:0) detected
07:06:58.655 [INF] CNCT: ChannelArbitrator(x:0): remote party has closed channel out on-chain
07:06:59.683 [INF] CNCT: ChannelArbitrator(x:0): still awaiting contract resolution
07:06:59.897 [INF] CNCT: *contractcourt.commitSweepResolver(x:0): Sweeping with witness type: CommitmentNoDelayTweakless
07:06:59.897 [INF] CNCT: *contractcourt.commitSweepResolver(x:0): sweeping commit output
07:09:35.683 [INF] CNCT: *contractcourt.commitSweepResolver(x:0): local commitment output fully resolved by sweep tx: a
07:09:35.700 [INF] CNCT: ChannelArbitrator(x:0): a contract has been fully resolved!
07:09:35.700 [INF] CNCT: ChannelArbitrator(x:0): still awaiting contract resolution
07:09:35.708 [INF] CNCT: ChannelArbitrator(x:0): a contract has been fully resolved!
07:09:35.708 [INF] CNCT: ChannelArbitrator(x:0): still awaiting contract resolution
07:09:35.709 [INF] CNCT: ChannelPoint(x:0) has been fully resolved on-chain at height=752361
07:09:35.709 [INF] CNCT: Marking ChannelPoint(x:0) fully resolved
07:10:19.522 [ERR] PEER: Peer(b): Unable to enable channel x:0: edge not found
07:10:19.621 [INF] HSWC: ChannelLink(x:0): stopping
07:10:19.621 [WRN] HSWC: ChannelLink(x:0): error when syncing channel states: link shutting down
07:10:19.621 [DBG] HSWC: ChannelLink(x:0): unable to sync channel states, link is shutting down
07:10:19.621 [INF] HSWC: ChannelLink(x:0): exited

pubkey logs:
05:14:34.221 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:55374-><IP_ADDRESS>:17714: use of closed network connection
05:14:34.422 [INF] SRVR: Finalizing connection to X@<IP_ADDRESS>:31428, inbound=true
05:14:34.424 [WRN] RPCS: Gossip syncer for peer=X not found
05:14:34.430 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
05:14:34.433 [INF] PEER: Peer(X): Negotiated chan series queries
06:54:57.393 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:54:57.393 [INF] PEER: Peer(X): disconnecting X@<IP_ADDRESS>:31428, reason: read handler closed
06:55:02.567 [INF] SRVR: Established connection to: X@Y.onion:9736
06:55:02.567 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:55:02.569 [WRN] RPCS: Gossip syncer for peer=X not found
06:55:02.896 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:55:02.899 [INF] PEER: Peer(X): Negotiated chan series queries
06:55:03.796 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:55:03.796 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:55:03.796 [ERR] PEER: Peer(X): unable to send msg to remote peer: peer exiting
06:55:07.435 [INF] SRVR: Established connection to: X@Y.onion:9736
06:55:07.435 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:55:07.437 [WRN] RPCS: Gossip syncer for peer=X not found
06:55:09.381 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:55:09.384 [INF] PEER: Peer(X): Negotiated chan series queries
06:55:12.167 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:55:12.167 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:55:12.168 [ERR] PEER: Peer(X): unable to send msg to remote peer: peer exiting
06:55:18.382 [INF] SRVR: Established connection to: X@Y.onion:9736
06:55:18.382 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:55:18.383 [WRN] RPCS: Gossip syncer for peer=X not found
06:55:18.717 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:55:18.720 [INF] PEER: Peer(X): Negotiated chan series queries
06:55:20.124 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:55:20.125 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:55:20.125 [ERR] PEER: Peer(X): unable to send msg to remote peer: peer exiting
06:55:30.286 [INF] SRVR: Established connection to: X@Y.onion:9736
06:55:30.286 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:55:30.288 [WRN] RPCS: Gossip syncer for peer=X not found
06:55:30.673 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:55:30.676 [INF] PEER: Peer(X): Negotiated chan series queries
06:55:31.676 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:55:31.676 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:55:52.046 [INF] SRVR: Established connection to: X@Y.onion:9736
06:55:52.046 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:55:52.048 [WRN] RPCS: Gossip syncer for peer=X not found
06:55:52.360 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:55:52.362 [INF] PEER: Peer(X): Negotiated chan series queries
06:55:53.372 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:55:53.372 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:55:53.372 [ERR] PEER: Peer(X): unable to send msg to remote peer: peer exiting
06:56:35.000 [INF] SRVR: Established connection to: X@Y.onion:9736
06:56:35.000 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:56:35.004 [WRN] RPCS: Gossip syncer for peer=X not found
06:56:35.332 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:56:35.335 [INF] PEER: Peer(X): Negotiated chan series queries
06:56:36.210 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:56:36.210 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
06:56:36.211 [ERR] PEER: Peer(X): unable to send msg to remote peer: peer exiting
06:58:03.011 [INF] SRVR: Established connection to: X@Y.onion:9736
06:58:03.011 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
06:58:03.013 [WRN] RPCS: Gossip syncer for peer=X not found
06:58:03.341 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
06:58:03.344 [INF] PEER: Peer(X): Negotiated chan series queries
06:58:04.595 [INF] PEER: Peer(X): unable to read message from peer: EOF
06:58:04.596 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
07:00:00.895 [WRN] SRVR: Already have 1 persistent connection requests for X@Y.onion:9736, connecting anyway.
07:00:01.106 [WRN] SRVR: Already have 2 persistent connection requests for X@Y.onion:9736, connecting anyway.
07:00:01.512 [WRN] SRVR: Already have 3 persistent connection requests for X@Y.onion:9736, connecting anyway.
07:00:01.584 [INF] SRVR: Established connection to: X@Y.onion:9736
07:00:01.584 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:00:01.587 [WRN] RPCS: Gossip syncer for peer=X not found
07:00:01.996 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
07:00:01.998 [INF] PEER: Peer(X): Negotiated chan series queries
07:00:02.320 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: X@Y.onion:9736
07:00:02.320 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: already connected to peer: X@Y.onion:9736
07:00:02.913 [INF] PEER: Peer(X): unable to read message from peer: EOF
07:00:02.913 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: read handler closed
07:05:19.037 [INF] SRVR: Established connection to: X@Y.onion:9736
07:05:19.037 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:05:19.039 [WRN] RPCS: Gossip syncer for peer=X not found
07:05:19.518 [INF] PEER: Peer(X): loading ChannelPoint(x:0)
07:05:19.520 [INF] PEER: Peer(X): Negotiated chan series queries
07:09:35.711 [INF] CHDB: Pruning link node X with zero open channels from database
07:10:19.520 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
07:10:19.520 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:49802-><IP_ADDRESS>:9050: use of closed network connection
07:10:19.522 [ERR] PEER: Peer(X): Unable to enable channel x:0: edge not found
07:15:38.497 [INF] SRVR: Established connection to: X@Y.onion:9736
07:15:38.497 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:15:38.500 [WRN] RPCS: Gossip syncer for peer=X not found
07:15:39.078 [INF] PEER: Peer(X): Negotiated chan series queries
07:20:39.079 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
07:20:39.079 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:49994-><IP_ADDRESS>:9050: use of closed network connection
07:26:03.017 [INF] SRVR: Established connection to: X@Y.onion:9736
07:26:03.017 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:26:03.020 [WRN] RPCS: Gossip syncer for peer=X not found
07:26:03.594 [INF] PEER: Peer(X): Negotiated chan series queries
07:31:03.594 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
07:31:03.594 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:50294-><IP_ADDRESS>:9050: use of closed network connection
07:36:21.755 [INF] SRVR: Established connection to: X@Y.onion:9736
07:36:21.755 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:36:21.758 [WRN] RPCS: Gossip syncer for peer=X not found
07:36:22.577 [INF] PEER: Peer(X): Negotiated chan series queries
07:41:22.578 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
07:41:22.578 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:50524-><IP_ADDRESS>:9050: use of closed network connection
07:46:40.439 [INF] SRVR: Established connection to: X@Y.onion:9736
07:46:40.439 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:46:40.442 [WRN] RPCS: Gossip syncer for peer=X not found
07:46:41.208 [INF] PEER: Peer(X): Negotiated chan series queries
07:51:41.209 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
07:51:41.209 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:50930-><IP_ADDRESS>:9050: use of closed network connection
07:57:01.522 [INF] SRVR: Established connection to: X@Y.onion:9736
07:57:01.522 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
07:57:01.524 [WRN] RPCS: Gossip syncer for peer=X not found
07:57:03.071 [INF] PEER: Peer(X): Negotiated chan series queries
08:02:03.072 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:02:03.072 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:51238-><IP_ADDRESS>:9050: use of closed network connection
08:07:21.495 [INF] SRVR: Established connection to: X@Y.onion:9736
08:07:21.495 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:07:21.498 [WRN] RPCS: Gossip syncer for peer=X not found
08:07:22.275 [INF] PEER: Peer(X): Negotiated chan series queries
08:12:22.276 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:12:22.276 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:51434-><IP_ADDRESS>:9050: use of closed network connection
08:17:43.083 [INF] SRVR: Established connection to: X@Y.onion:9736
08:17:43.083 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:17:43.086 [WRN] RPCS: Gossip syncer for peer=X not found
08:17:43.918 [INF] PEER: Peer(X): Negotiated chan series queries
08:22:43.918 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:22:43.918 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:51754-><IP_ADDRESS>:9050: use of closed network connection
08:28:02.355 [INF] SRVR: Established connection to: X@Y.onion:9736
08:28:02.355 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:28:02.357 [WRN] RPCS: Gossip syncer for peer=X not found
08:28:02.560 [INF] PEER: Peer(X): Negotiated chan series queries
08:33:02.561 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:33:02.561 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:51952-><IP_ADDRESS>:9050: use of closed network connection
08:38:21.292 [INF] SRVR: Established connection to: X@Y.onion:9736
08:38:21.292 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:38:21.295 [WRN] RPCS: Gossip syncer for peer=X not found
08:38:22.322 [INF] PEER: Peer(X): Negotiated chan series queries
08:43:22.323 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:43:22.323 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:9050: use of closed network connection
08:48:52.309 [INF] SRVR: Established connection to: X@Y.onion:9736
08:48:52.309 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:48:52.311 [WRN] RPCS: Gossip syncer for peer=X not found
08:48:53.050 [INF] PEER: Peer(X): Negotiated chan series queries
08:53:53.050 [INF] PEER: Peer(X): disconnecting X@Y.onion:9736, reason: peer X@Y.onion:9736 no answer for 5m0s -- disconnecting
08:53:53.051 [INF] PEER: Peer(X): unable to read message from peer: read tcp <IP_ADDRESS>:52680-><IP_ADDRESS>:9050: use of closed network connection
08:59:10.136 [INF] SRVR: Established connection to: X@Y.onion:9736
08:59:10.136 [INF] SRVR: Finalizing connection to X@Y.onion:9736, inbound=false
08:59:10.139 [WRN] RPCS: Gossip syncer for peer=X not found

I'm looking into it.
Just as an FYI: as the channel was announced, providing the channel link allows to get the pubkey of both peers. So if you want to hide the peers, I would advise removing the channel link.

This doesn't seem like a bug, the peer is sending an Error, meaning they have probably failed the channel. The failing link bit is just that the connection has died while trying to send/receive channelreestablish

@Crypt-iQ The initial error / root cause is "unable to resume channel, recovery required", returned by lnd, though. The peer CLN doesn't send this kind of error message. It's rather weird to see who sent what, though...

the peer sent error instead of reestablish, triggering the log message "unable to resume..." which doesn't actually mean recovery is required. so the peer did not like something that was done earlier by us, and without logs from the other side, nothing can be done.

Unfortunately I don't have the possibility to contact that peer. So I guess this is where the story ends.

Hello. I just got a similar FC from my peer (*lnwire.Error). There were multiple dropped connections with EOF before and the ping is high (7000ms via Tor). Here is the log from my side. Is Tor dropping or corrupting the messages?
2023-11-02 17:18:18.014 [INF] SRVR: Established connection to: 02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70@gv65qc4k3mwxcjs3q3fzji4rrjoyx35ox77jq5i543na7c5em7ghmxid.onion:9735
2023-11-02 17:18:18.015 [INF] SRVR: Finalizing connection to 02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70@gv65qc4k3mwxcjs3q3fzji4rrjoyx35ox77jq5i543na7c5em7ghmxid.onion:9735, inbound=false
2023-11-02 17:18:18.179 [INF] CRTR: Processed channels=0 updates=88 nodes=5 in last 59.999887587s
2023-11-02 17:18:19.179 [INF] PEER: Peer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): Loading ChannelPoint(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1), isPending=false
2023-11-02 17:18:19.180 [INF] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): starting
2023-11-02 17:18:19.180 [INF] HSWC: Trimming open circuits for chan_id=806810:4321:1, start_htlc_id=34218
2023-11-02 17:18:19.180 [INF] HSWC: Adding live link chan_id=4386dd5c3de297a814b5a23882b215ebb02deb1132393f00756639f791ffd2e7, short_chan_id=806810:4321:1
2023-11-02 17:18:19.180 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1)
2023-11-02 17:18:19.180 [INF] NTFN: New block epoch subscription
2023-11-02 17:18:19.180 [INF] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): HTLC manager started, bandwidth=3873303059 mSAT
2023-11-02 17:18:19.180 [INF] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): attempting to re-synchronize
2023-11-02 17:18:19.180 [INF] PEER: Peer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): Negotiated chan series queries
2023-11-02 17:18:19.181 [INF] DISC: Creating new GossipSyncer for peer=02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70
2023-11-02 17:18:19.200 [INF] DISC: GossipSyncer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): applying new update horizon: start=2106-02-07 06:28:15 +0000 UTC, end=2242-03-16 12:56:30 +0000 UTC, backlog_size=0
2023-11-02 17:18:19.448 [WRN] DISC: ignoring remote ChannelAnnouncement for own channel
2023-11-02 17:18:20.701 [INF] PEER: Peer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): unable to read message from peer: EOF
2023-11-02 17:18:20.701 [WRN] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
2023-11-02 17:18:20.701 [ERR] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
2023-11-02 17:18:20.701 [INF] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): exited
2023-11-02 17:18:20.701 [INF] HSWC: ChannelLink(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): stopping
2023-11-02 17:18:20.701 [INF] PEER: Peer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): disconnecting 02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70@gv65qc4k3mwxcjs3q3fzji4rrjoyx35ox77jq5i543na7c5em7ghmxid.onion:9735, reason: read handler closed
2023-11-02 17:18:20.702 [INF] HSWC: Removing channel link with ChannelID(4386dd5c3de297a814b5a23882b215ebb02deb1132393f00756639f791ffd2e7)
2023-11-02 17:18:20.702 [ERR] PEER: Peer(02ea8c02945fa6e6ad45f7047be0403a4e05451b74cfc08846745e220720252f70): unable to send msg to remote peer: peer exiting
...
2023-11-02 17:19:13.246 [INF] NTFN: Dispatching confirmed spend notification for outpoint=e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1, script=0 ddd2e2da5e1999550f95974557c672d71ec985c01959dba6725816464d4b5d8b at current height=814993: d98665c9cdbf9c5317da77c3eeeebf43f2163741bacece296e3a87ba42e23e83[0] spending e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1 at height=814993
2023-11-02 17:19:13.255 [INF] UTXN: Attempting to graduate height=814993: num_kids=0, num_babies=0
2023-11-02 17:19:13.260 [INF] CNCT: Remote party broadcast base set, commit_num=77620
2023-11-02 17:19:13.260 [INF] CNCT: Unilateral close of ChannelPoint(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1) detected
2023-11-02 17:19:13.269 [INF] CNCT: ChannelArbitrator(e6d2ff91f7396675003f393211eb2db0eb15b28238a2b514a897e23d5cdd8643:1): remote party has closed channel out on-chain

This issue isn't tracked anymore, feel free to open a new issue


Box is not correct on multiple labels (x-axis ticks).

I am drawing a box on a line chart. I am having a problem when i dram the box and give it a xMax. It did not draw on the last point if the points are multiple, instead it draw on the first point. For example. i have labels [12-Mar-2017, 13-Mar-2017, 14-Mar-2017,15-Mar-2017,15-Mar-2017]. Notice here that 15-Mar-2017 is two times. If i want to draw a box from 13-Mar to 15-Mar It will only highlight the first 15-Mar-2017 Point not the next. Is there any solution for this ?
This is the jsFiddle
Any kind of help would be much appreciated.

In v1.0.0-beta.4 you pass the index as the value so this is resolved. See https://jsfiddle.net/prmnh1v3/2/


More test for entities reading

Closes: #53

PR-Codex overview
This PR adds new entity classes and updates the entities reader test. It also includes new tests for reading lambdas, data, and objects.
Detailed summary

Added Data, Empty, FlatObject, Lambda, and Locator classes to Entities
Updated Entities reader test to include nested entities tests
Added tests for reading lambdas, data, and objects
Disabled new tests for now

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@Graur, please have a look

@yegor256 please, have a look

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 2min)


Name of the module interfere with already installed modules

After module installation:
puppet module install profitbricks-puppet
there is problem with other modules from puppetforge (https://forge.puppet.com/theforeman/puppet). Both of them have the same name which cause conflict:

puppet

Maybe the name should be changed to

profitbricks-puppet

@rnosal We have released version 1.5.0 of the ProfitBricks module for Puppet. In addition to a number of changes, we renamed the module to "profitbricks-profitbricks" to match the module naming convention of [username]-[modulename]. This should avoid the naming conflict.


Design for Time Well Spent

Hello.
I'm not sure if it fits here but there is the Time Well Spent movement.

I think this would go under empathy for users. I'll definitely check it out, thanks!

And there is also How Technology Hijacks People’s Minds. The page above does not link to it directly.


Allow forcing colored output.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Use colored output on Travis.

Neat. What commands is this used by in particular? I reckon it might be a better fit for a change to brew test-bot instead which would cover all repos when run under Travis?

Particularly the new brew cask ci command: https://github.com/Homebrew/homebrew-cask/pull/50358


yii\db\ColumnSchemaBuilder boolean() doesn't support passing a value

I was just creating some new migrations, and looking at the docs. I see there is a boolean() function, but it doesn't look like we can specify whether it's true or false.
For example, in my migration, I would expect to do:
'receive_emails' => $this->boolean(1),

to set the value.

Nevermind, duh.. Its 3am :/
$this->boolean()->defaultValue(1)

Since boolean doesn't require a length, the way I "attempted" initially could be a shorthand special case :)


Add interrupted logic

It is embarrassed when i use this. Because it can't interrupted.

Hi! Big thanks for PR, it is a great idea, but I see some issues.

I tried to implement similar API as readLines from std https://deno.land/std/io/bufio.ts#L706 So if we can pass the Reader, we need to do it as the first argument. Also, the new function signature brokes backward compatibility. I think It would be better to add new arguments to the end.
CTRL+C has to cause a SIGINT, but in this code, CTRL+C causes the end of while cycle.
I think readKeypress must do one thing - read keypresses. Maybe it would be better to create a new function like readKeypressAndProcess(/*...*/, event => { /* do something */ }) (need a good naming), "do something" can be your defaultExit with immediate Deno.exit() (or maybe you need a warning?), or something else.

So I think this improvement has not to break existing code, need to be more flexible to change keypress handling.

Yeah, agree with you!
But I want write an example command line selector, like inquirer#list.
So I need a function to trigger once, maybe it would use addEventListener/dispatchEvent or use callback.


Extension causes high cpu load

Issue Type: Performance
Extension Name: solidity
Extension Version: 0.0.102
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.52.1

:warning: Make sure to attach this file from your home-directory:
:warning:c:\Users\ALEXAN~1\AppData\Local\Temp\JuanBlanco.solidity-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@SterlingKinder any more details?

@SterlingKinder any more details?

JuanBlanco.solidity-unresponsive.cpuprofile.txt

Having the same problem, vs code is saying the extension took a long time to complete its previous task and is preventing other extensions to run in background whenever I am starting vs code, thereby increasing cpu load

What are your settings?

I have all the default settings

What is your project structure, OS?

I am using Windows 10, writing smart contracts with Hardhat for dapps and for frontend I am using ReactJs having the hardhat simple basic project structure

can you make an screenshot of your project structure? Your current version of vscode solidity? Is autocomplete working?

My current version of vs code solidity  is v0.0.139 and yes it is giving me suggestions for autocompleting my code most of the times but sometimes it is not showing those.

Hmmmm if you right click or press F5 to compile is it ok?

yeah it is showing Compilation completed successfully!

Thank you, for all of this, I was just checking if there was something that might has caused this to be an issue, but nothing.
Maybe this is due to trying to download the latest version of solidity when starting? Do you have any connectivity issues?

Also is this just happening on the start of vscode?

No I am not having any connectivity issue,
yes the error is showing only when I am starting my vs code

Is your solidity version set to latest?

yes it is set to latest

Ok, I am assuming this is due when trying to load and download the latest version on startup, this will happen when is starting as it will be initialised using the current settings.
If you right click in a solidity smart contract and select this:

And change it to 0.8.15 let me know if it makes any difference.

Ok

I made the changes and the error is still showing

Thanks @nirban256, what is the spec of your PC? as this is not a normal issue.

Processor	Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz   3.10 GHz
Installed RAM	8.00 GB (7.70 GB usable)
System type	64-bit operating system, x64-based processor

Yes, that should not be an issue, if you don't have other processes hugging the cpu. Very strange, as you don't need to download the latest solidity and you are mainly loading the extension normally.

No I am not running any other processes, hope that future updates will resolve the problem.


data:emmyVon

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

We have tried to resolve the conflicts in your PR. If you wish to make any more changes then please raise a new PR.


(fix: solid-query): Revert breaking build

Apologies for going back and forth on this so often.
This is in reference to the breaking build in solid-query. Because client Context value is never passed into the provider
This is potentially an upstream issue https://github.com/TanStack/query/issues/4673
For now, this should be reverted as it's causing dependent packages to break unfortunately too
https://github.com/OrJDev/solid-trpc/issues/8

Codecov Report
Base: 96.36% // Head: 92.34% // Decreases project coverage by -4.01% :warning:

Coverage data is based on head (64acdef) compared to base (eab6e2c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4733      +/-   ##
==========================================
- Coverage   96.36%   92.34%   -4.02%
==========================================
  Files          45       89      +44
  Lines        2281     3751    +1470
  Branches      640      985     +345
==========================================
+ Hits         2198     3464    +1266
- Misses         80      271     +191
- Partials        3       16      +13

Impacted Files
Coverage Δ

src/core/queryObserver.ts

src/devtools/theme.tsx

src/react/useBaseQuery.ts

src/core/mutation.ts

src/core/query.ts

src/react/logger.native.ts

src/react/useQuery.ts

src/core/infiniteQueryObserver.ts

src/core/hydration.ts

src/react/useQueries.ts

... and 124 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.