codeunit "Reminder-Make" add new event OnAfterReminderLevelProcessed

Hello,
Could you please add new event to codeunit "Reminder-Make" , procedure MakeReminder:

Event Call:
OnAfterReminderLevelProcessed(ReminderLevel, NextLineNo, StartLineInserted);
Event Declaration:
    [IntegrationEvent(false, false)]     local procedure OnAfterReminderLevelProcessed(var ReminderLevel: Record "Reminder Level"; var NextLineNo: Integer; StartLineInserted: Boolean)     begin     end;
Thank you in advance!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Running tests locally fail

Question
When I git clone to my Mac, and run tests, I get a lot of errors:
  ● Models › Loading different architecture types › gpt2 (GPT2Model)

    Could not locate file: "https://huggingface.co/gpt2/resolve/main/tokenizer_config.json".

      239 |
      240 |     const message = ERROR_MAPPING[status] ?? `Error (${status}) occurred while trying to load file`;
    > 241 |     throw Error(`${message}: "${remoteURL}".`);
          |           ^
      242 | }
      243 |
      244 | class FileCache {

      at handleError (src/utils/hub.js:241:11)
      at getModelFile (src/utils/hub.js:474:24)
      at getModelJSON (src/utils/hub.js:575:18)
          at async Promise.all (index 1)
      at loadTokenizer (src/tokenizers.js:61:16)
      at Function.from_pretrained (src/tokenizers.js:2465:20)
      at Object.<anonymous> (tests/models.test.js:61:37)

And indeed, a lot of files don't actually exist, like in this case:
https://huggingface.co/gpt2/resolve/main/tokenizer_config.json
But I don't see this in the logs for your github actions, so i am confused.

Oh, I see what you did. Local tests are.... optimistic.
Perhaps a better way would be to try optimistic, and if it fails, then use your copies?

BTW: you can have github actions cache your .cache folder, but you would need a decent cache key.

Hi there :wave: This behaviour was taken over from a very early version of the project, where I would just name the models the same as they are on the HF Hub, and store the model weights under my HF account. A change was needed to run with github actions, so I introduced the TESTING_REMOTELY environment variable to link to models under the Xenova account on HF. So, if you want to test locally, you can set TESTING_REMOTELY=1 (a bit confusing I guess), which will use the web-ready versions.
A follow-up PR will be ideal to improve this.


Add a flatten operator

The flatten operator (and the corresponding flatten function) takes events and flattens them such that the outermost record is the only record and nested lists get flattened into a single list.
Consequently, the operator removes nulls from list, because they cannot be distinguished from absent values in Arrow's data model.
- [x] Implement flatten
- [x] Detect and warn for duplicate flattened keys
- [x] Document flatten behavior in detail
- [x] Write changelog entry
- [x] Add integration tests
- [x] ~Fix behavior for `list<record<list<T>>>`; probably need to combine validity bitmaps~ Document broken behavior

Playing around some more, I noticed that flatten transforms null values into empty lists if the type is a list.
Consider the following example where answers and TTLs are defined as lists:

Is this intended under the "removes nulls from list" edge case, even though there is no null to remove, because the list is missing in the first place?

Note to (maybe) myself: This PR could also implement a flatten call for the zeek-tsv format, as in this commit

@dakostu I cannot approve this PR myself as I created it originally, but I did enable auto-merge. If you approve it, it should get merged straight away.


Return different exit code if repo is locked or does not exist

What does this PR change? What problem does it solve?
Return exit code 11 if a repository cannot be locked and exit code 10 if the repository does not exist. The existence check relies on the presence of the config files. Other errors like an invalid password still result in exit code 1.
The new exit codes effectively form a category of exit codes (10+) that are related to the repository itself. The 1+ group contains the main exit codes.

Was the change previously discussed in an issue or on the forum?
Address two use cases from https://github.com/restic/restic/issues/956 .

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

I've changed the exit codes to 10 and 11. With a bit of luck this might allow establishing at least a minimal kind of ordering in the exit codes.


Webview Api Prototype

Moving #41853 to branch on main repo

Proposes a new Api for webviews. This API aims to make the current html preview api more usable, safer, and more extensible for the future.
Besides the new API, the new webviews also differ in several important ways:

They are no longer loaded in the file:// origin so they can't read files on disk (you have to use the new protocols for this)
Scripts are disabled by default
Command uris are disabled by default
postMessage inside of webviews now posts back to vscode directly (no more weird click faking required)

TODO

[x] Discuss and finalize API
[x] Add onFocus and onBlur to the webview object
[ ] See if implementation can be cleaned up
[X] Add dispose method on webview
[ ] ~Add editorColumn property on webview~
[X] Make enableCommandUris option actually enable command uris
[X] Add a new protocol for accessing a resource inside of a workspace folder (markdown loading a local image for example)
[x] Finish moving markdown extension to use the new API

A suggestion: allow reading the current content of the view as text. This way it's possible to see the actual HTML text, including what vscode added/changed. And I would love to see a way to access variables in the DOM. That doesn't require to make the entire DOM public, just a way to read and set variables. This would make updating a webview a lot simpler, without fully reloading it. It would also allow to save and restore state, in case such a view must be generated the same way as it was when the user left it.

@mike-lischke This new API makes it easier to implement that functionality if you would find it useful. They are a bit too high level in my view for the vscode core api

Thanks @mjbvz, I'll certainly give it a try. The simplified messaging looks good, I can probably come up with a function that allows to update variables via that. Does keepAlive keep the content also if the webview's tab is closed or only when it becomes inactive (switching to another tab). For me it is enough keep the content as long as the tab exists, not longer.

@mjbvz Will you add a WebView example to https://github.com/Microsoft/vscode-extension-samples?

@mjbvz when the WebView can be used in the extension development?
I can't wait to use it.


Bot crashes on new coin listing

TRIBE got listed this morning, and the bot did this:
Traceback (most recent call last):
File "Binance Detect Moonings.py", line 597, in
orders, last_price, volume = buy()
File "Binance Detect Moonings.py", line 294, in buy
volume, last_price = convert_volume()
File "Binance Detect Moonings.py", line 255, in convert_volume
volatile_coins, number_of_coins, last_price = wait_for_price()
File "Binance Detect Moonings.py", line 153, in wait_for_price
min_price = min(historical_prices, key = lambda x: float("inf") if x is None else float(x[coin]['price']))
File "Binance Detect Moonings.py", line 153, in
min_price = min(historical_prices, key = lambda x: float("inf") if x is None else float(x[coin]['price']))
KeyError: 'TRIBEUSDT'

I was able to fix the problem.
The file tickers.txt is the reference file.
If you want that the bot consider your new listing, you coin ticket (TRIBE), shall be inserted on that list.
THEN,
you add TRIBE on your signalsample.txt.
In summary, the tool gets the price of all tickers inside tickers.txt. while the file signalsample.txt is where you can filter the tickers to work with.
Regards,

Didnt work for me.  I made sure both files EXACTLY the same. I even went into the signalsample and changed it to only look at the tickers.txt file and still get the error.  I still get the same error.  Anyone else figure this out?

I was able to fix the problem.
The file tickers.txt is the reference file. If you want that the bot consider your new listing, you coin ticket (TRIBE), shall be inserted on that list.
THEN,
you add TRIBE on your signalsample.txt.
In summary, the tool gets the price of all tickers inside tickers.txt. while the file signalsample.txt is where you can filter the tickers to work with.
Regards,

This might work but if it does not I think I figured out why mine was also crashing.  This was not the reason but also would probably make it crash so good answer.  BUT.    You can clear them out so the bot no longer sees you own them, but you must leave in the {} in the file. I think this was doing it.  I just took everything out when testing and  left the file blank.  Then I think when the bought was trying to buy it would look to this blank file and error out.  I think it needed the {} in the file to see it was truly blank.  Anyway, testing again but thought it was good to share.   So, just to into the test couins bought file, be sure you have at least {} in the file and you did not clear it out.  THEN I would also be sure your tickers list matches your sample list like he said above.


foo(()) should print to foo()

Where are you seeing this?
Can't reproduce on master:
echo "foo(());" | ./refmt_impl.native
foo();

Polymorphic variant

Apparently the parser doesn't support this yet, so you might as well change the label into GOOD FIRST SHIFT/REDUCE TASK 😛


Little Snitch Package recipe fails

Hi
The current Little Snitch recipe fails as both the location of the support files has changed with the v5.x release and where the system installs these on disk has changed.
I'm looking into this now but I suspect its more self contained and it should just be a case of deploying the App to /Applications and letting users go through the initial setup.
I'll see what I can find

@Daz-wallace I haven't used Little Snitch for a couple of years now but let me know what you find. IIRC it was a pain to make this recipe in the first place because of the Installer Application rather than a traditional PKG. I ended up capturing where everything was deployed via Composer 😅

@smithjw Haha that's what I'm doing now to see what moves.
If it's radically different, I might create a new set for "Little Snitch 5", as we're only looking for the v5 version 😊

Sounds good! I might update this recipe to state it may no longer work and point to yours when you're done

My VM is struggling to capture what I need so I'll need to come back to this. I'll keep you posted

Hi @smithjw
So It does look like Little Snitch 5 is more self contained. With the right SEXT profile in place there's still a 'setup' wizard you'll need to follow but it shouldn't need any admins rights.
It's your call but we can either spawn off a Little Snitch v5 recipes, or I can put in a PR to simplify the .pkg recipe you have, and set the minimum OS to macOS 11+
Lemmie know if you have a preference 😊

Hmmm, thought I replied to this. If you create the pull request, I'm happy to test and merge it in :)


map data

hello, do you have saved map data?

map.pcd is stored in the workspace when the loop ends or with the following service calls.
ros2 service call /map_save std_srvs/Empty


Convert unnecessary double quotes to single quotes

Unify code style

Good catch! Fixed both.^^

I close this, since resolving merge conflicts will be a much larger task than the actual changes provided.


Add Feathers JS example

This example demonstrates how Next can be used in combination with Feathers JS.

In the spirit of not trying to confuse people (per @arunoda's comments), and due to the larger nature of this example, I'd like to link to this from the Wiki, as a question in the FAQ. Thanks for your contribution though!


Forced close and now balance stuck on chain x1 week

Hi Tony, I mentioned this issue to you at Nostrville. I had my lightning channels close, and the sats went on-chain. The total is about 150k but only 29k is available for me to convert back to Lightning. Let me know what I can do to get them back. Thanks!

If you could provide your logs that would help

@DocNR you can you link the file on github when you attach it in an email like that we don't get the full file.

Sorry Ben, I'm kind of a retard with GitHub. Is there a way to upload the file? I'm using the iOS app and don't see one

You might be able to use this button, otherwise it's easier to just use it on desktop and you can drag and drop the file.

 I just took a look. The wallet says I have
153,424 sats on-chain, but when I click to convert to lightning I only have
access to 26,396 sats.
On Mon, Nov 13, 2023 at 12:18 PM benthecarman @.***>
wrote:

[image: image]
https://user-images.githubusercontent.com/15256660/282537325-5a188033-3ea9-416d-871f-1bd73c3a9449.png
You might be able to use this button, otherwise it's easier to just use it
on desktop and you can drag and drop the file.
—
Reply to this email directly, view it on GitHub
https://github.com/MutinyWallet/mutiny-web/issues/697#issuecomment-1808623910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAHBX7FNX6SOW7HKOJ4NKV3YEJI5BAVCNFSM6AAAAAA7HLCPXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYGYZDGOJRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

cf18 2023-11-26 20:36:12.677 INFO  [mutiny_core::nodemanager:550] Current device lock: DeviceLock { time:<PHONE_NUMBER>, device: "b11b0e1a-c952-44d1-8d3d-bad2f1546884" }
cf18 2023-11-26 20:36:13.614 DEBUG [mutiny_core::gossip:155] Previous gossip sync timestamp: 0
cf18 2023-11-26 20:36:14.735 DEBUG [mutiny_core::gossip:176] retrieved remote scorer
cf18 2023-11-26 20:36:15.362 INFO  [mutiny_core::node:199] initializing a new node: a2ba3afb-88ba-4ced-822c-e1d0ecd12755
cf18 2023-11-26 20:36:15.517 DEBUG [mutiny_core::ldkstorage:209] Reading channel manager from storage
cf18 2023-11-26 20:36:15.518 INFO  [lightning::ln::channelmanager:10051] Queueing monitor update to ensure missing channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 is force closed
cf18 2023-11-26 20:36:15.527 INFO  [lightning::ln::channelmanager:10358] Had a pending payment path for 1000 msat for session priv ef931d56406fd41cf12df54fbcdc13f6144b6b0bf35fdbc0a94d358c79f0aff4 on an existing pending payment with payment hash 3323ade9520192ac2cef719bfd98680d43bf6db295fd9b09c527526483b95429
cf18 2023-11-26 20:36:15.529 INFO  [mutiny_core::node:321] creating lsp client
cf18 2023-11-26 20:36:15.532 TRACE [lightning::chain::chainmonitor:722] Got new ChannelMonitor for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3
cf18 2023-11-26 20:36:15.545 INFO  [lightning::chain::chainmonitor:728] Persistence of new ChannelMonitor for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 in progress
cf18 2023-11-26 20:36:15.546 INFO  [mutiny_core::node:562] Node started: 028eba16bdfa0b6cbe0576e0750e678b6638a85baedf4fbeef38b2b92453556524
cf18 2023-11-26 20:36:15.546 INFO  [mutiny_core::nodemanager:699] inserting updated nodes
cf18 2023-11-26 20:36:15.546 INFO  [mutiny_core::nodemanager:706] inserted updated nodes
cf18 2023-11-26 20:36:15.554 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred on startup
cf18 2023-11-26 20:36:15.555 TRACE [lightning::chain::chainmonitor:768] Updating ChannelMonitor for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3
cf18 2023-11-26 20:36:15.555 INFO  [lightning::chain::channelmonitor:2625] Applying post-force-closed update to monitor 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 with 1 change(s).
cf18 2023-11-26 20:36:15.555 TRACE [lightning::chain::channelmonitor:2689] Updating ChannelMonitor: channel force closed, should broadcast: true
cf18 2023-11-26 20:36:15.555 DEBUG [lightning::chain::channelmonitor:3303] Getting signed latest holder commitment transaction!
cf18 2023-11-26 20:36:15.558 INFO  [lightning::chain::channelmonitor:2612] Broadcasting local commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:15.559 DEBUG [lightning::chain::chainmonitor:787] Persistence of ChannelMonitorUpdate for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 in progress
cf18 2023-11-26 20:36:15.560 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims on startup
cf18 2023-11-26 20:36:15.561 INFO  [lightning::chain::onchaintx:488] Triggering rebroadcast/fee-bump for request with inputs [OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, vout: 0 }]
cf18 2023-11-26 20:36:15.562 DEBUG [lightning::chain::package:940] Adding claiming input for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0
cf18 2023-11-26 20:36:15.562 DEBUG [lightning::chain::package:941] Finalized transaction eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82 ready to broadcast
cf18 2023-11-26 20:36:15.563 INFO  [lightning::chain::onchaintx:502] Rebroadcasting onchain commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:15.563 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:15.564 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:15.567 INFO  [mutiny_core::nodemanager:1437] RGS URL: https://scorer.mutinywallet.com/v1/rgs/snapshot/0
cf18 2023-11-26 20:36:15.568 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:15.569 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c6371575040047304402201ceef1960a80f2896563f95ceaa9f535bf15d8ae1b5f1beb068bec4078b4d1b802201fac4e0f4d5664d6460f839bd686c22787833e75acd592031d4eff8653f79d2e014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:36:15.571 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:15.571 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c6371575040047304402200f30673ad5f3d7e4838ef275475287bfb99d06abd44903ac823940750b2feb8b02202b6c33a957e6f9b245f41a62120f26cbf6bb1b9ef69a578e87aafa1ef0ad647c014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:36:16.544 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:16.547 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:16.550 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:16.550 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:16.625 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(18446744073709551615) } }
cf18 2023-11-26 20:36:16.627 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:16.628 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:17.139 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, index: 0 }, monitor_update_id: MonitorUpdateId { contents: OffChain(18446744073709551615) } }
cf18 2023-11-26 20:36:17.140 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:17.141 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:18.320 TRACE [lightning_rapid_gossip_sync::processing:62] Processing RGS data...
cf18 2023-11-26 20:36:18.986 DEBUG [lightning_rapid_gossip_sync::processing:148] Processing RGS update from<PHONE_NUMBER> with 8214 nodes, 50000 channel announcements and 99886 channel updates.
cf18 2023-11-26 20:36:19.490 TRACE [lightning_rapid_gossip_sync::processing:257] Done processing RGS data from<PHONE_NUMBER>
cf18 2023-11-26 20:36:19.490 INFO  [mutiny_core::gossip:234] RGS sync result:<PHONE_NUMBER>
cf18 2023-11-26 20:36:19.491 INFO  [mutiny_core::nodemanager:900] RGS Synced!
cf18 2023-11-26 20:36:19.498 TRACE [mutiny_core::background:557] Persisting network graph.
cf18 2023-11-26 20:36:19.915 TRACE [mutiny_core::fees:125] Retrieved fees from mempool
cf18 2023-11-26 20:36:19.915 INFO  [mutiny_core::nodemanager:909] Updated fee estimates!
cf18 2023-11-26 20:36:19.915 INFO  [mutiny_core::esplora:221] Starting transaction sync.
cf18 2023-11-26 20:36:19.967 TRACE [lightning::ln::channelmanager:8074] New best block:<PHONE_NUMBER>0000000001d6738a954f8f70a2fb0cc67110a90197225c7c157148 at height 818619
cf18 2023-11-26 20:36:19.967 DEBUG [lightning::chain::chainmonitor:682] New best block<PHONE_NUMBER>0000000001d6738a954f8f70a2fb0cc67110a90197225c7c157148 at height 818619 provided via best_block_updated
cf18 2023-11-26 20:36:19.969 TRACE [lightning::chain::chainmonitor:378] Syncing Channel Monitor for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3
cf18 2023-11-26 20:36:19.969 DEBUG [lightning::chain::chainmonitor:383] Channel Monitor sync for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 in progress, holding events until completion!
cf18 2023-11-26 20:36:19.976 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:19.977 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:19.977 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:19.977 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.079 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.079 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.181 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.182 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.283 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.284 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.385 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.385 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.486 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.487 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.589 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.590 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.692 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.692 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.794 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.796 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.898 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:20.898 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.001 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.002 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.104 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.105 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.207 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.208 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.310 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.310 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.413 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.414 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:21.534 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, index: 0 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(0) } }
cf18 2023-11-26 20:36:22.634 DEBUG [mutiny_core::networking::proxy:69] connected to ws: wss://p.mutinywallet.com
cf18 2023-11-26 20:36:22.639 DEBUG [mutiny_core::peermanager:432] connected to peer: PubkeyConnectionInfo { pubkey: PublicKey(f0e18eca0f86800041211951fbbbabdbb7743995059d12a4219b00b4fb43faaec9a0af987303533cdaa9a57b32494716c973a7a53696dd46367cb483a5fa46e6), connection_type: Tcp("<IP_ADDRESS>:9735"), original_connection_string: @.***:9735" }
cf18 2023-11-26 20:36:22.640 TRACE [mutiny_core::peermanager:435] sent 50 to node: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:22.640 TRACE [mutiny_core::networking::socket:65] scheduling descriptor reader
cf18 2023-11-26 20:36:22.640 TRACE [mutiny_core::node:1734] auto connected lsp: 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:22.641 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:23.046 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:23.057 DEBUG [lightning::ln::peer_handler:1374] Finished noise handshake for connection with 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:23.058 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Init { features: [33, 81, 10, 8, 128, 160, 8], networks: Some([6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000]), remote_network_address: Some(TcpIpV4 { addr: [52, 88, 33, 119], port: 9735 }) } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:23.059 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:23.060 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:23.462 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:23.463 INFO  [lightning::ln::peer_handler:1539] Received peer Init message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: supported, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsNonzeroFeeHtlcTx: not supported, AnchorsZeroFeeHtlcTx: not supported, ShutdownAnySegwit: supported, Taproot: not supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: supported
cf18 2023-11-26 20:36:23.463 DEBUG [lightning::ln::channelmanager:8721] Generating channel_reestablish events for 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:23.513 TRACE [lightning::ln::channelmanager:8053] 1 transactions included in block<PHONE_NUMBER>000000000004ca50c766c910323e7af83c1f1caf494a53376dc4a0 at height 814133 provided
cf18 2023-11-26 20:36:23.514 DEBUG [lightning::chain::chainmonitor:666] 1 provided transactions confirmed at height 814133 in block<PHONE_NUMBER>000000000004ca50c766c910323e7af83c1f1caf494a53376dc4a0
cf18 2023-11-26 20:36:23.528 TRACE [lightning::chain::channelmonitor:3567] Processing 0 matched transactions for block at height 814133.
cf18 2023-11-26 20:36:23.528 INFO  [lightning::chain::channelmonitor:3865] Force-closing channel due to outbound HTLC timeout, HTLC expiry is 815149
cf18 2023-11-26 20:36:23.530 DEBUG [lightning::chain::onchaintx:699] Updating claims view at height 818619 with 1 claim requests
cf18 2023-11-26 20:36:23.530 INFO  [lightning::chain::onchaintx:708] Ignoring second claim for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0, already registered its claiming request
cf18 2023-11-26 20:36:23.531 DEBUG [lightning::chain::onchaintx:820] Updating claims view at height 818619 with 0 matched transactions in block 814133
cf18 2023-11-26 20:36:23.531 TRACE [lightning::chain::onchaintx:951] Bumping 0 candidates
cf18 2023-11-26 20:36:23.531 TRACE [lightning::chain::chainmonitor:378] Syncing Channel Monitor for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3
cf18 2023-11-26 20:36:23.531 DEBUG [lightning::chain::chainmonitor:383] Channel Monitor sync for channel 0cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd3 in progress, holding events until completion!
cf18 2023-11-26 20:36:23.532 INFO  [mutiny_core::esplora:317] Finished transaction sync.
cf18 2023-11-26 20:36:23.533 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:23.534 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:23.534 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.534 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.534 DEBUG [mutiny_core::node:596] Retrying to persist monitor for outpoint: OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, index: 0 }
cf18 2023-11-26 20:36:23.550 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:23.551 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:36:23.551 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:36:23.551 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:36:23.559 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.560 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:23.562 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.635 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.635 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.710 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:23.710 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.736 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.736 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.837 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.838 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.941 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:23.942 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.044 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.046 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.149 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.150 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.253 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.254 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.351 INFO  [mutiny_core::nodemanager:1479] We are synced!
cf18 2023-11-26 20:36:24.363 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.364 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.466 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.467 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.569 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.570 DEBUG [lightning::chain::chainmonitor:821] A Channel Monitor sync is still in progress, refusing to provide monitor events!
cf18 2023-11-26 20:36:24.597 TRACE [mutiny_core::background:557] Persisting ChannelManager...
cf18 2023-11-26 20:36:24.599 TRACE [mutiny_core::background:557] Done persisting ChannelManager.
cf18 2023-11-26 20:36:25.138 DEBUG [mutiny_core::ldkstorage:121] Persisted channel monitor: MonitorUpdateIdentifier { funding_txo: OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, index: 0 }, monitor_update_id: MonitorUpdateId { contents: ChainSync(4294967297) } }
cf18 2023-11-26 20:36:25.647 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:36:25.648 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:25.651 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:26.519 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:26.521 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:35.795 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:36:35.797 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:35.799 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:36.655 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:36.657 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:45.616 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
cf18 2023-11-26 20:36:45.617 INFO  [lightning::chain::onchaintx:488] Triggering rebroadcast/fee-bump for request with inputs [OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, vout: 0 }]
cf18 2023-11-26 20:36:45.638 DEBUG [lightning::chain::package:940] Adding claiming input for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0
cf18 2023-11-26 20:36:45.639 DEBUG [lightning::chain::package:941] Finalized transaction eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82 ready to broadcast
cf18 2023-11-26 20:36:45.639 INFO  [lightning::chain::onchaintx:502] Rebroadcasting onchain commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:45.641 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:36:45.642 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c6371575040047304402205b698371d313ae8f152e4dd7fbb3758fdda7ffe66bfac7fb695492227cf6c7c00220496d3b01fa18fe55f1ebfee1872b0953851b3864db3c71dfeaa36f52c0fe7728014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:36:45.949 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:36:45.949 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:45.950 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:45.996 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:45.998 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:36:46.791 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:46.792 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:56.100 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:36:56.101 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:36:56.104 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:36:57.031 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:36:57.032 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:37:06.220 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:37:06.221 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:37:06.222 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:37:07.070 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:07.072 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:37:23.921 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.937 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.938 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:37:23.967 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.969 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.971 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.973 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.976 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:23.977 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: No existing channels for node_announcement
cf18 2023-11-26 20:37:57.524 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred
cf18 2023-11-26 20:37:57.525 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
cf18 2023-11-26 20:37:57.525 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
cf18 2023-11-26 20:37:58.528 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:37:58.529 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:37:58.530 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
cf18 2023-11-26 20:37:58.530 INFO  [lightning::chain::onchaintx:488] Triggering rebroadcast/fee-bump for request with inputs [OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, vout: 0 }]
cf18 2023-11-26 20:37:58.565 DEBUG [lightning::chain::package:940] Adding claiming input for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0
cf18 2023-11-26 20:37:58.566 DEBUG [lightning::chain::package:941] Finalized transaction eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82 ready to broadcast
cf18 2023-11-26 20:37:58.568 INFO  [lightning::chain::onchaintx:502] Rebroadcasting onchain commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:37:58.571 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:37:58.571 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:37:58.572 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c6371575040047304402202703cd0083f8f45843f2d212e4f3d2e20b8af1cff640ef381b30981f43567cc102204b9afa1e2930fc7a6463074479a6a516c8e63f8266ecb48fe9ff0c726274c22d014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:37:59.343 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:37:59.344 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:37:59.680 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:37:59.683 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:38:23.922 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:38:23.926 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:38:23.927 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:38:23.947 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:38:23.950 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:38:23.952 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:06.115 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:39:06.116 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:39:06.117 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:39:07.141 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:07.142 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:39:23.731 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.739 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.786 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:39:23.861 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.865 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.868 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.870 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.873 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:23.938 INFO  [mutiny_core::nodemanager:909] Updated fee estimates!
cf18 2023-11-26 20:39:23.940 INFO  [mutiny_core::esplora:221] Starting transaction sync.
cf18 2023-11-26 20:39:24.939 INFO  [mutiny_core::esplora:317] Finished transaction sync.
cf18 2023-11-26 20:39:26.830 INFO  [mutiny_core::nodemanager:1479] We are synced!
cf18 2023-11-26 20:39:42.359 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:39:42.359 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:39:42.360 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:39:43.224 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:39:43.224 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:40:13.896 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
cf18 2023-11-26 20:40:13.896 INFO  [lightning::chain::onchaintx:488] Triggering rebroadcast/fee-bump for request with inputs [OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, vout: 0 }]
cf18 2023-11-26 20:40:13.922 DEBUG [lightning::chain::package:940] Adding claiming input for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0
cf18 2023-11-26 20:40:13.923 DEBUG [lightning::chain::package:941] Finalized transaction eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82 ready to broadcast
cf18 2023-11-26 20:40:13.924 INFO  [lightning::chain::onchaintx:502] Rebroadcasting onchain commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:40:13.925 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:40:13.926 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c6371575040047304402201a9411f298238a88494755df12ba1cf93fe1b0babcd73d078278397f81b2abd902203a3cfc96d2847e1d4f7a9337aa5b250e41495a8a0ee9f055452289f8d49c0f8c014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:40:14.530 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:40:14.531 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:40:23.733 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:23.735 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:23.737 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:23.741 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:23.741 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:40:24.187 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:24.194 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:24.200 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:24.205 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:24.206 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:40:24.212 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:24.213 DEBUG [lightning::ln::peer_handler:1472] Error handling message from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0; ignoring: Couldn't find channel for update
cf18 2023-11-26 20:40:39.511 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:40:39.511 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:40:39.512 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:40:40.540 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:40:40.541 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:04.182 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:41:04.183 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:04.186 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:41:04.975 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:04.976 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:14.368 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:41:14.369 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:14.372 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:41:15.290 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:15.291 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:16.945 TRACE [mutiny_core::background:557] Calling ChannelManager's timer_tick_occurred
cf18 2023-11-26 20:41:16.946 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
cf18 2023-11-26 20:41:16.946 TRACE [mutiny_core::fees:174] Got fee rate from saved cache!
cf18 2023-11-26 20:41:19.966 TRACE [mutiny_core::background:557] Rebroadcasting monitor's pending claims
cf18 2023-11-26 20:41:19.966 INFO  [lightning::chain::onchaintx:488] Triggering rebroadcast/fee-bump for request with inputs [OutPoint { txid: d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c, vout: 0 }]
cf18 2023-11-26 20:41:19.970 DEBUG [lightning::chain::package:940] Adding claiming input for outpoint d32b1fe49ab8749a00cd7ed2c50271fe3dd5ec16cdb0cad08f184d2011bab50c:0
cf18 2023-11-26 20:41:19.970 DEBUG [lightning::chain::package:941] Finalized transaction eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82 ready to broadcast
cf18 2023-11-26 20:41:19.971 INFO  [lightning::chain::onchaintx:502] Rebroadcasting onchain commitment tx with txid eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:41:19.971 INFO  [mutiny_core::onchain:75] Broadcasting transaction: eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82
cf18 2023-11-26 20:41:19.972 DEBUG [mutiny_core::onchain:76] Transaction:<PHONE_NUMBER>01010cb5ba11204d188fd0cab0cd16ecd53dfe7102c5d27ecd009a74b89ae41f2bd300000000007d8060800134f00100000000002200204d3d08a7ee4df7f927f93f92c0aec1c77031b7e238c61a87bb0baa89c63715750400473044022071c6e560ddfec965cab10c09127c165dfebd9e0c3a103fa43c21524ec9b9693902201d50dfe75fa0d9b8396518a38622aba640459340f25358c8b6fb59ca589cdb94014730440220437fbee1647409f6247a58d0029b08f1cb1a708b6c956191aa3a0812af872b3d02204a7a64f95f77da7ea57dea3eaeb844d133d08bf556160c42fe243934896f643901475221026d371745b04b12c79ac3b7e36cdf65144a1f6ce9367bf6a92bc6970b4ab4998321033b9ab37b11ca6a56e88b50941b144249030c95e384e778d99dd49ffeab48923852aec9f92420
cf18 2023-11-26 20:41:20.431 ERROR [mutiny_core::onchain:79] Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:41:20.433 WARN  [mutiny_core::chain:56] Error broadcasting transaction: Failed to broadcast transaction (eac3559e83898194474a28393ff73e8713b37ea116f88c904f484436234d0f82): Reqwest(reqwest::Error { kind: Status(400), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("mutiny.mempool.space")), port: None, path: "/api/tx", query: None, fragment: None } })
cf18 2023-11-26 20:41:23.647 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:23.654 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.005 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.008 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.010 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.012 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.013 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:24.538 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:41:24.539 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:24.540 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:41:25.320 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:25.321 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:34.691 TRACE [mutiny_core::background:557] Calling PeerManager's timer_tick_occurred
cf18 2023-11-26 20:41:34.691 TRACE [lightning::ln::peer_handler:1240] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
cf18 2023-11-26 20:41:34.694 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
cf18 2023-11-26 20:41:35.468 TRACE [mutiny_core::networking::socket:77] received binary data from websocket
cf18 2023-11-26 20:41:35.470 TRACE [lightning::ln::peer_handler:1586] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0

@DocNR you need to link the whole log file, you either need to go through the github UI or you can email it as an attachment to<EMAIL_ADDRESS>

So this is a closing transaction that happened awhile back and never confirmed. This is the transaction: https://mempool.space/tx/2ba6191b366bfd5b0a0d482dd2d6d0144bd7e9c8a0db77192f45a9f218a37c4c
Unfortunately there's not much else that can be done, can't bump these transactions, though you could use a transaction accelerator to confirm these if you wanted. Mempool just launched theirs.

Shit… I’ll take a look into the transaction accelerator. Looks like the tx
fee was only 6 sats/vb. Is it possible it gets purged? What happens then?

your wallet will continually rebroadcast it so it should be fine, just need to wait for the mempool to clear

If I wanted to open another channel, are there any concerns with the funds
that are stuck in the mempool?
On Mon, Nov 27, 2023 at 12:04 benthecarman @.***> wrote:

Shit… I’ll take a look into the transaction accelerator. Looks like the tx
fee was only 6 sats/vb. Is it possible it gets purged? What happens then?
your wallet will continually rebroadcast it so it should be fine, just
need to wait for the mempool to clear
—
Reply to this email directly, view it on GitHub
https://github.com/MutinyWallet/mutiny-web/issues/697#issuecomment-1828261566,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAHBX7CWHJG6YZEAXVRY25TYGTB2VAVCNFSM6AAAAAA7HLCPXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGI3DCNJWGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

You won't be able to open a channel with those funds, but opening another channel with other funds you have on chain should work.
Once the force close transaction confirms, a few days after that another transaction will happen that sweeps the funds back into your available on chain balance. Until then, there might be a difference in balance for your on chain wallet.

Hey @DocNR - check your wallet. We were running some tests with mempool's accelerator and used yours as an example. It should be confirmed now and the sweep can occur a few days from now if you check your wallet over the next few days.

Cool thanks. Looks like the on-chain available balance is still at 26k
while the total is 153k. I’ll keep checking to see if it updates.
On Thu, Dec 14, 2023 at 14:21 Tony Giorgio @.***> wrote:

Hey @DocNR https://github.com/DocNR - check your wallet. We were
running some tests with mempool's accelerator and used yours as an example.
It should be confirmed now and the sweep can occur a few days from now if
you check your wallet over the next few days.
—
Reply to this email directly, view it on GitHub
https://github.com/MutinyWallet/mutiny-web/issues/697#issuecomment-1856445348,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAHBX7E7SNXZKWU4MSPUX6TYJNGUZAVCNFSM6AAAAAA7HLCPXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGQ2DKMZUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Correct, still requires a sweep transaction to pop up after the timelock ends starting with the confirmation today. Check back tomorrow or Saturday.

It swept and I see it on my on-chain balance. Thank you!
On Thu, Dec 14, 2023, 23:47 Tony Giorgio @.***> wrote:

Correct, still requires a sweep transaction to pop up after the timelock
ends starting with the confirmation today. Check back tomorrow or Saturday.
—
Reply to this email directly, view it on GitHub
https://github.com/MutinyWallet/mutiny-web/issues/697#issuecomment-1857271418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAHBX7G5LMRTSCQBSWQ3UF3YJPI4XAVCNFSM6AAAAAA7HLCPXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGI3TCNBRHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


rename submission to content tools

https://github.com/mozilla-services/svcops-puppet/pull/125

r+


CS525

You need to make a pull request and add the link to the pull request to this issue when you submit

https://github.com/Carlomos7/project-management-github-activity/pull/33


Failed to establish a connection Error continuously showing in console

I am using chrome browser and Next JS 13.4.7 version with typescript.
And these our helia packages i am using:
"helia": "^1.3.4",  "@helia/json": "^1.0.0",

see https://github.com/ipfs/helia/issues/151#issuecomment-1591437544 for an explanation about these errors. Please follow #151 for updates


Watch task for tests

Is it possible to watch filechange in test files and trigger test command?

try npm test -- --watch

Let me know if you need any further information

Thank you!


Apple Pay does not work with xcomponent due to insecure parent frame

Hi,
I'm using Stripe API to open Apple Pay within an xcomponent lightbox. However, it throws an error "Trying to call an ApplePaySession API from a document with an insecure parent frame" when it detects the outermost iframe is not secure (not starting with https) as below:
<iframe name="__lightbox_container__ec6827b044__" scrolling="no" frameborder="0" style="display: block; position: fixed; top: 0px; left: 0px; width: 100%; height: 100%; z-index:<PHONE_NUMBER>;"></iframe>
Can you please look into?
Here is how I implement the Apply Pay:
<style>
  #apple-pay-button {
    display: none;
    background-color: black;
    background-image: -webkit-named-image(apple-pay-logo-white);
    background-size: 100% 100%;
    background-origin: content-box;
    background-repeat: no-repeat;
    width: 100%;
    height: 44px;
    padding: 10px 0;
    border-radius: 10px;
  }
</style>

<button id="apple-pay-button"></button>

<script type="text/javascript" src="https://js.stripe.com/v2/"></script>
<script>
    Stripe.setPublishableKey('pk_test_6pRNASCoBOKtIshFeQd4XMUh');

    Stripe.applePay.checkAvailability(function(available) {
        if (available) {
            document.getElementById('apple-pay-button').style.display = 'block';
        }
    });

    document.getElementById('apple-pay-button').addEventListener('click', beginApplePay);

    function beginApplePay() {
        var paymentRequest = {
            countryCode: 'US',
            currencyCode: 'USD',
            total: {
                label: 'Stripe.com',
                amount: '19.99'
            }
        };
        var session = Stripe.applePay.buildSession(paymentRequest,
            function(result, completion) {

            $.post('/charges', { token: result.token.id }).done(function() {
                completion(ApplePaySession.STATUS_SUCCESS);
                //window.xchild.props.onComplete('Apple Pay succeeded!');

            }).fail(function() {
                completion(ApplePaySession.STATUS_FAILURE);
                //window.xchild.props.onComplete('Apple Pay error!');

            });

        }, function(error) {
            console.log(error.message);
        });

        session.oncancel = function() {
            console.log("User hit the cancel button in the payment window");
            //window.xchild.props.onComplete('Apple Pay canceled!');
        };

        session.begin();
    }
</script>

Thanks,
Ky

Are both your parent page and your frame served up over https?
This sounds like a restriction with apple-pay, rather than xcomponent. xcomponent will allow non-https pages, but seems like apple-pay is blocking them.

Hi,
The page and its frames are served up over https, except the outermost iframe I mentioned in the issue. That iframe is generated when the context is 'lightbox' to create the overlay - I guess.
Could you tell me the purposes of that iframe?
If it is there just to handle the overlay, I can make some changes by myself.
Many thanks,
Ky

Hi,
That iframe is just used to ensure that the parent page's css doesn't conflict with the css for the overlay. It doesn't have a src - and as such it should inherit the domain from the parent window.
I tried your example code, but didn't see any errors when both the parent and the child were rendered using https.
Can you possibly link me to your test site so I can see the error and debug? Also, can you let me know which browser you're testing in?
Thanks!

Any updates on this issue? Otherwise planning to close it as I can't repro.

Hi @bluepnume,
Sorry for the delay.
I'll fork the kraken-js today and put my implementation there so that you can see the error and debugs.
Thanks,
Ky

Hi @bluepnume,
Please pull the demo from https://github.com/kms-ky-truong/xcomponentapplepay.
It was generated from kraken-js.
For the demo to work with Apple Pay, you might need to meet its Minimum Requirements.
Thanks,
Ky

Yeah, managed to repro, thanks for sharing the code.
Seems like this check is being done somewhere in ApplePaySession.canMakePaymentsWithActiveCard which is a native browser function.
I can probably add a setting to disable rendering the overlay into a new iframe. That was mainly to make sure the stylesheet of the overlay didn't conflict with any existing styles on the parent page.

That would be awesome. Many thanks for your effort.

OK, I've added an option for this: sandboxContainer: false
xcomponent.create({
    sandboxContainer: false
});

I tried this with your code and I now see the apple pay button. Can you give it a try on your side? Thanks!

It works now.
Much thanks for your effort.
-- Ky


[AIRFLOW-850] Add a PythonSensor

A general purpose PythonSensor which allows an arbitrary Python
callable to delay Task execution until the callable returns True
Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:
https://issues.apache.org/jira/browse/AIRFLOW-850
Testing Done:
Added tests for python callables which return True, False, or raise an exception

Codecov Report

Merging #2058 into master will not impact coverage by -0.11%.

@@            Coverage Diff             @@
##           master    #2058      +/-   ##
==========================================
- Coverage   67.69%   67.59%   -0.11%
==========================================
  Files         139      139
  Lines       10578    10596      +18
==========================================
+ Hits         7161     7162       +1
- Misses       3417     3434      +17

Impacted Files
Coverage Δ

airflow/operators/sensors.py
68.43% <83.33%> (+0.94%)
:white_check_mark:

airflow/task_runner/bash_task_runner.py
93.33% <ø> (-6.67%)
:x:

airflow/utils/helpers.py
41.08% <ø> (-2.48%)
:x:

airflow/jobs.py
72.16% <ø> (-0.85%)
:x:

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 d428a90...221f3a9. Read the comment docs.

@dgies it looks like your tests mostly passed but one was caught up in an issue we had recently with the travis box being overloaded by logging. Could you please rebase (without changes) and force-push to your branch, which will kick off a new round of testing?

@jlowin OK, rebased/repushed, crossed fingers.

@dgies can you put the tests in their own file please? Core needs to be refactored

I moved the tests to the file sensors.py as that seems to be where every other sensor test lives.

@dgies the github integration didn't update, but it seems like the new tests failed.
======================================================================
ERROR: test_python_sensor_false (tests.PythonSensorTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/apache/incubator-airflow/tests/operators/sensors.py", line 199, in test_python_sensor_false
    dag=self.dag)
AttributeError: 'PythonSensorTests' object has no attribute 'dag'

This sounds like a nice addition - If anyone (original author or some else finding this issue) wants to fix this and pick up this PR (sorry it got abandonded for so long!): if you get a version that applies to current master @ me and I'll take a look.

@dgies Still working on this? I was amazed that this wasn't in (yet).

I still think it's a good idea, but don't have any time to contribute.
On Mon, Nov 5, 2018 at 10:44 AM Fokko Driesprong<EMAIL_ADDRESS>wrote:

@dgies https://github.com/dgies Still working on this? I was amazed
that this wasn't in (yet).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-airflow/pull/2058#issuecomment-435987793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AESJURj7uT0PrCWWYQrc-yXhXLuOQLfuks5usIcVgaJpZM4L6McC
.

I think this is a good addition. I will submit a new pr based on this one. cc @ashb @Fokko


Implement bind / unbind handling in broker client + fake broker + tests

Address #263

Thanks, PTAL @arschles

@vaikas-google LGTM

LGTM

just waiting on CI

The light is green; the trap is clean! 👻


[W4.4b] Song Weiyang

This PR/issue should be against a repo in the org nus-cs2103-AY1718S2 not against the repo in se-edu org :-)
Closing...


Unable to instantiate abstract class

When using polymorphism and your base class is abstract you get the error? in serializer.h line 482.
It seems serializer is unable to handle unique_pointer to abstract classes.

@arneves can you provide a small sample?


Ubuntu 16.04 dependency scripts fail due to the openjdk-6-jre package

on Ubuntu 16.04 fresh install,
both installUbuntuDepsUnattended.sh and installUbuntuDeps.sh
fails to install the openjdk-6-jre package,
in 16.04 there's no openjdk-6-jre package, use the openjdk-8-jre or openjdk-9-jre instead.

Ubuntu 16.04 is not officially supported yet. Please share with us any advance! Thanks a lot!


Adds Task.on_external_failure method to provide custom error messages for failed External Tasks

Description
This PR adds an on_external_failure method to the Task class.  This method is called in the TaskProcess.run method when an external task fails, and enables the user to provide a custom failure message for external tasks.  I also add 2 relevant tests to cover the additional codepaths.
Motivation and Context
My pipeline consists of a fair amount of external tasks, many of which have overridden Task.complete methods.  One thing that I'd like to be able to do is provide a more informative explanation for why an external task failed in the luigi dashboard.   Currently, there is no way to do this, and I can't repurpose the existing on_failure method because no Exception was raised.
I added the method directly to the Task class in case users use the externalize method instead of inheriting from the ExternalTask class.
Have you tested this? If so, how?
Included 2 additional unit tests that pass.

@Tarrasch, I like the suggestion of moving the "Task is an external data dep..." text to the on_external_failure method body, which I implemented in the latest diff.
Even though dynamic nature of python gives you the flexibility to return strings from the complete() method, I think it could confuse users (and perhaps introduce unintentional bugs) if I implemented that functionality.  Since it is such a core component of the luigi workflow, I personally prefer that complete() only return boolean values.

Can you paste some example of how you would implement the on_external_failure method?

Also, I think on_external_failure() isn't the best name and it doesn't need to be specific to external tasks. Why not call it reason_not_complete()? It could be implemented for both external and normal tasks. It could even have an intelligent default returning which files are missing (if you depend on tasks with only FileSystemTargets).

Sorry about the delay on this, I'm just working through whether or not it would be a good idea to take care of @erikbern's TODO in luigi/worker.py:182 which should resolve #814.  Unfortunately, changing the logic in worker.py to:
if self.task.complete():
    status = DONE
 elif _is_external(self.task):
    status = FAILED
    expl = self.task.on_external_failure()
else:
    new_deps = self._run_get_new_deps()
``` yields additional test failures in `test/worker_multiprocess_test.py`

Just want to provide a status update

I agree with Tarrasch that on_external_failure() is a bad name and reason_not_complete() is a better name.


Share to twitter functionality

Secretive:
When a character dies can we have a share memorial to twitter?
Would love to see ‘share to twitter’ for pretty much every page (fights, load out, leaderboard)

Handling in #52


Fix/refetch mood query

Fixes issue where the cached query wasn't being updated when a new mood was added
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Change Status

[x] Complete, but not tested (may need new tests)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] There are no merge conflicts

looks good! thanks for this.  Learned something new 👍


Validate parameter types in method signature

Codecov Report

Merging #6 (6627fbd) into main (45eab1e) will increase coverage by 4.30%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   69.63%   73.93%   +4.30%
==========================================
  Files           7        8       +1
  Lines         303      330      +27
==========================================
+ Hits          211      244      +33
- Misses         57       61       +4
+ Partials       35       25      -10

Flag
Coverage Δ

unittests
73.93% <66.66%> (+4.30%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/spec/errors.go
0.00% <0.00%> (ø)

internal/spec/models.go
100.00% <ø> (ø)

internal/mongo/generator.go
60.24% <81.81%> (+1.49%)
:arrow_up:

internal/spec/parser.go
95.60% <91.66%> (+26.92%)
: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 45eab1e...6627fbd. Read the comment docs.

Codecov Report

Merging #6 (6627fbd) into main (45eab1e) will increase coverage by 4.30%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   69.63%   73.93%   +4.30%
==========================================
  Files           7        8       +1
  Lines         303      330      +27
==========================================
+ Hits          211      244      +33
- Misses         57       61       +4
+ Partials       35       25      -10

Flag
Coverage Δ

unittests
73.93% <66.66%> (+4.30%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/spec/errors.go
0.00% <0.00%> (ø)

internal/spec/models.go
100.00% <ø> (ø)

internal/mongo/generator.go
60.24% <81.81%> (+1.49%)
:arrow_up:

internal/spec/parser.go
95.60% <91.66%> (+26.92%)
: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 45eab1e...6627fbd. Read the comment docs.


Add ZenML as official Docker template

Making this PR ahead of becoming an official template. (CC: @davanstrien)
I wasn't sure if the {% hint } markdown syntax was supported. Happy to amend if there's a better way to do those. I see that <Tip></Tip> is used in some places, but I couldn't figure out the equivalent for some kind of a warning.
The photo used to illustrate using the official template will need updating as / when the template gets set up.

Preview of the select spaces template view

I will update this on https://huggingface.co/datasets/huggingface/documentation-images

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@osanseviero think this should be good to go now, but we might want to hold off merging until we're ready to launch.

@osanseviero you okay with me merging this now?


Cmdlinetests

Command-line tests based on cram.

Let's see what Travis says!

the python 3 builds are failing!

I'd like to get this merged up and fix the python 3 tests in a second iteration.

Oh, wait, the cram tests are failing on Python3

some unicode errros and other stuff, also bottledaemon seems to have python 3 issues

So I ended up vendoring bottledaemon, to be removed when a new version is released.

ZOMG all checks successfull

Please stand back, rebase in progress!

Fixes #12 and #13

ty


linear view stalls

When scrolling through linear view while analyzing it's possible that the view stalls.

Fixed in dev


added PHP_EOL between XML tags

Was not able to upload to BulkDataExchange because XML file cannot be longer than certain length for each line.

Thanks for spotting this issue. Sorry it took so long for me to merge the pull request. I've made some small changes to your original changes. I don't use the PHP_EOL constant as it meant the tests would not work on Windows system.

Thank you for the update. I tried making more changed to pass the automated
test but wasn't successful.
On Oct 11, 2015 8:45 AM, "David Terence Sadler"<EMAIL_ADDRESS>wrote:

Thanks for spotting this issue. Sorry it took so long for me to merge the
pull request. I've made some small changes to your original changes. I
don't use the PHP_EOL constant as it meant the tests would not work on
Windows system.
—
Reply to this email directly or view it on GitHub
https://github.com/davidtsadler/ebay-sdk-php/pull/2#issuecomment-147212288
.


Handling ASP.NET MVC Input Arrays Exception (function: idOrName)

Hi,
I'm getting errors using jquery validation in an asp.net mvc 5 project. I also use jquery validation obtrusive but I believe the error sits inside jquery validation.
MVC 5 generates input elements for arrays like that:
<input name="[0].somefieldname" type="text" value="10" data-val="true" data-val-number="the error message" data-field="somefieldname">
<input name="[1].somefieldname" type="text" value="21" data-val="true" data-val-number="the error message" data-field="somefieldname">
<input name="[2].somefieldname" type="text" value="4" data-val="true" data-val-number="the error message" data-field="somefieldname">

The problem is that jquery validation looks for the name in a jquery selector which causes following exception:
JavaScript runtime error: Syntax error, unrecognized expression: label[for='[0].somefieldname'], label[for='[0].somefieldname'] *, #[0].somefieldname-error
Proposal:
change function idOrName from
idOrName: function( element ) {
return this.groups[element.name] || (this.checkable(element) ? element.name : element.id || element.name);
},
to
idOrName: function( element ) {
return this.groups[element.name] || (this.checkable(element) ? element.name : element.id || element.name).replace("[", "\[").replace("]", "\]");
},

There is a small problem with your proposed fix - you have to use double slashes when replacing, like this:
return this.groups[element.name]
|| (this.checkable(element)
? element.name
: element.id || element.name)
.replace("[", "\[")
.replace("]", "\]");

I can't reproduce this problem. I've opend demo/index.html', removed the idattribute on the first input and set itsnameattribute toname="[0].somefieldname". I also tried setting errorElement: "span"` for the form, but that doesn't make a difference either, it still works fine.
Please make sure you're testing with the latest release, currently 1.13.1. If you're still having issues, please provide a testpage that shows the issue.

Checked. Reproducable with 1.13.0, works fine with 1.13.1.

Well, if it works with 1.13.1, there's nothing to do here :-)

Yes, I can confirm. Works with 1.13.1. Well done!
On Tue, Jan 20, 2015 at 4:36 PM, Jörn Zaefferer<EMAIL_ADDRESS>wrote:

Well, if it works with 1.13.1, there's nothing to do here :-)
—
Reply to this email directly or view it on GitHub
https://github.com/jzaefferer/jquery-validation/issues/1337#issuecomment-70672785
.

--
www.svenjohannsen.net

Yup, just leaving mark for history – wasn’t working with 1.13.0, works with 1.13.1 :)
From: Jörn Zaefferer<EMAIL_ADDRESS>Sent: Tuesday, January 20, 2015 5:36 PM
To: jzaefferer/jquery-validation
Cc: PiRXlv
Subject: Re: [jquery-validation] Handling ASP.NET MVC Input Arrays Exception (function: idOrName) (#1337)
Well, if it works with 1.13.1, there's nothing to do here :-)
—
Reply to this email directly or view it on GitHub https://github.com/jzaefferer/jquery-validation/issues/1337#issuecomment-70672785 .  https://github.com/notifications/beacon/AFp0hr8h9OcfDA51wEhj1bMcn4BYqC7Kks5njm1zgaJpZM4DBurz.gif


Cannot connect to MQTT via TLS

What type of installation are you running?
Desktop
Which Linux OS are you using?
Linux Mint 21.1
Which version of LNXLink has the issue?
2023.8.0
Describe the problem
My MQTT broker (mosquitto) is configured to accept mqtts connections via port 8883 with TLS encryption.
When server port in my Lnxlink Desktop installation is configured to 8883, no connection to mqtt broker is possible.
For testing purposes I also opened regular port 1883 (without TLS). When changing port in Lnxlink to 1883 everythin works as expected.
How can I configure TLS within Lnxlink?
Additional context
No response
Configuration
mqtt:
  prefix: homeassistant
  clientId: client1
  statsPrefix: monitor/stats
  server: 'server.name'
  port: 8883
  auth:
    user: 'usr'
    pass: 'pwd'
  discovery:
    enabled: true
  lwt:
    enabled: true
    qos: 1
    retain: true
    connectMsg: 'ON'
    disconnectMsg: 'OFF'
update_interval: 5
modules:

Logs
Aug 14 00:01:48 nuc3 systemd[374585]: Started LNXlink.
Aug 14 00:01:49 nuc3 lnxlink[2019599]: INFO:lnxlink:LNXlink 2023.8.0 started: 3.10.6
Aug 14 00:01:49 nuc3 lnxlink[2019599]: INFO:lnxlink:Loaded addons: screenshot, required_restart, update, notify, disk_usage, sys_updates, battery, camera_used, network, webcam, media, suspend, microphone_used, gpu, memory, xdg_open, keep_alive, cpu, fullscreen, bash, boot_select, screen_onoff, shutdown, brightness, idle, restart, send_keys

Looking at the MQTT client docs, there's a tls_set() method which must be called to enable TLS connections: https://pypi.org/project/paho-mqtt/#client
It currently doesn't seem to be called, so right now it doesn't seem to be possible without changing the code.

I haven't used TLS on mqtt broker so I didn't notice that issue.
Thanks for letting me know.

With the latest commit I've added an option on the configuration to enable TLS.
You should follow the instructions that installs LNXlink as a developer and add the tls option under mqtt/auth like this:
  auth:
    user: user
    pass: pass
    tls: true

I haven't tested it, so I would love your feedback.

@bkbilly I just tested the latest dev version with TLS and it works for me now!
Thank you for quick reply and fix!

I'm happy that it worked for you!
I'll leave this issue open until I publish the next release on September.

Added this feature on LNXlink version 2023.9.0.
If you have a configuration from previous versions, you will have to add the tls option manually.


Log files should include a version number

Log files for all commands should include a laue-dials version number, like DIALS does. A laue.version command may also be helpful.

Fixed by this commit


feat: Add dart image upload sample

Description
Added Dart server-side examples to upload images
Related Issue
Fixes #69

@colbyfayock the PR is ready to review

hey @adityaoberai the script worked perfectly!!
what do you think about adding the ability (at least in the form of docs) to install dependencies with dart pub get? in my mind its kinda like an npm install
also any thoughts on adding .env support instead of the exports?
this other dart example someone provided has those things, curious about if you think its worth adding: https://github.com/cloudinary-community/cloudinary-examples/tree/main/examples/dart-transformation-effects

That's a great idea @colbyfayock! I'll make these changes :)

@colbyfayock made the update

worked perfectly @adityaoberai!!
thanks for your help 🚀