Create Definition files to replace the Configuration classes and be fed to factories

This issue depends on the Configuration Array format defined in #1522; collaboration between these two items is recommended

The Version Definition AGGREGATE contains several Entities that work together to declare a definition for a new or existing Documentation object.
A Definition can be seen as a specification that informs a Factory how to construct a new object. In the current design we plan on having a Version Definition that is used as basis for creating a new Documentation object using the Documentation Factory; and to have a Definition for each type of DocumentGroup.
The above means that we need a common interface for Definitions for DocumentGroups but the actual Definition classes are part of their respective DocumentGroup component and as such not documented as part of this component.

With the DefinitionRepository for the Versions it is possible to retrieve a Definition for each Version that is defined in the configuration file. As can be seen in the Class Diagram it accepts the ConfigurationFactory, which will create an array containing configuration settings upon calling its ‘get’ method. The ConfigurationFactory allows the Configuration to be retrieved by the DefinitionRepository as a Data source but postpone loading the configuration until absolutely necessary so that a user can provide their own Configuration file location.
Since each DocumentGroup can have a separate set of properties (a Guide using RestructuredText as Format can have different properties from an ApiReference using PHP as Format) each can have their own specialised Factory (part of the Component for that specific DocumentGuide); since the Version Definition Factory needs to be able to know when to use which Factory these specialized Factories need to be registered using the registerDocumentGroupDefinitionFactory method.

@mvriel I think this one is solved. All classes in the diagram are there.


Forum GC not updating

so is this cuz of forums failure or just coincidence?

Coincidence. Will be fixed soon.

Fixed!


Vulkan: Unshaded CanvasItem is being affected by CanvasModulate (unlike in 3.x)

Godot version
v4.0.alpha6.official [e4f0fc50f]
System information
Ubuntu, Nvidia, Vulkan
Issue description
In Godot 3, an unshaded CanvasItem would not be affected by CanvasModulate.
This is no longer the case in the current version.

Steps to reproduce

Create a blank project
Create a scene
Add a Sprite2D node, use icon.png
Add a CanvasModulate node, set a dark modulation color
Notice the sprite is being affected
Add a CanvasItemMaterial to the Sprite2D and set it to unshaded
Notice the sprite is still being affected

Minimal reproduction project
godot_4_canvas_modulate_unshaded.zip

I still have the same issue in 4.2.1.stasble.mono.official
Unshaded has no effect on node visibility when CanvasModulate node is present..


"Canceled" element not fully inside the card

This is an issue that was also in a build from the 22nd of December, but it's still happening on the current build.

It seems that the canceled text is not fully inside the box, including the bubble. I feel like this issue might be happening due to my screen resolution, which it isn't very wide. (Samsung Galaxy Z Fold 4, outer screen).
Device:
Samsung Galaxy Z Fold 4
OS:
Android 14 (One UI 6.1)
Thank you!

See #35


core:  Fixed inspecting schema issue when working with InjectedToolArg annotations

[x] PR message:  This PR addresses the issue#27510 where InjectedToolArg annotations cannot be properly inspected or converted into JSON schema, causing errors when working with special type annotations.

Description:
(This PR has contributions from @Chloekyuu @JANERUBBISHTOEAT @chloepan33
1. Enhanced Argument Filtering with _check_injected_arg_type : It is used to correctly identify arguments annotated with InjectedToolArg within the create_schema_from_function, and ensures that arguments are properly added to the filter_args list when include_injected=False, allowing these arguments to be excluded from the schema as needed.
2. Custom JSON Schema for InjectedToolArg: Implemented InjectedToolArgSchema that wraps InjectedToolArg in Annotated with a custom schema defined via WithJsonSchema, which allows InjectedToolArg to be parsed into a JSON schema format without causing errors, enabling proper inspection and compatibility with Pydantic.

Issue:#27510

Hi @baskaryan, I’ve created a test case to address the problem scenario described in issue #27510. This test case verifies if user specific tools produce the correct Json schema for it's arguments(annotated with InjectedToolArg) using .args.
However, if the current explanation or test coverage is not clear enough, please let me know. I’d greatly appreciate it if you could provide:

A more detailed explanation of the issue or edge cases you’ve identified.
Specific use cases or test scripts where this problem occurs more prominently.

With this additional input, I can refine the solution further and ensure that the fix is comprehensive and robust across all relevant scenarios.


Where to put CORSANYWHERE_WHITELIST variable when setting up demo server on Heroku?

Hi! First off thanks for the great resource. I followed the instructions in the Demo Server section of the readme, but I'm not sure where to place this part to whitelist my specific site:
export CORSANYWHERE_WHITELIST=https://www.boardgamegeek.com/
node server.js

I've tried making an .env file with that text.
I've tried adding it to the Procfile.
I've tried adding it as a config var as described in the Heroku tutorial.
I also tried adding it to originWhitelist key of the corsAnywhere object on line 262 of cors-anywhere.js.
I'm sure the answer is super obvious, but I'm too much of a noob to know where this goes. :sweat_smile:

Nevermind I was able to figure it out by setting the config var using the following command:
heroku config:set CORSANYWHERE_WHITELIST=https://boardgamegeek.com/
I believe previously I had included the www, which seems to not work.

Ah shoot, I must've spoke too soon. I'm getting 403s for my whitelisted domain.

I tested adding PORT: 443 to the Heroku config vars and then did a heroku restart, but the 403s persist.
This is what my config vars look like now:

CORS Anywhere does currently not offer a way to restrict the destination URLs.
The CORSANYWHERE_WHITELIST configuration option allows you to restrict the origins, i.e. which pages can use the proxy to read data from other websites.

Ah okay! So in my case I should set up my local environment (e.g. http://localhost:3000) and my live domain (e.g. https://betterbggcollection.com), right? Is the PORT variable necessary if I already attached the port to the URL above?

The PORT variable should only be set if the proxy server should listen at a specific port.
From your comments so far, it is not clear what you're trying to do. To answer your question, you need to distinguish:

What is the location of your proxy server. For internal use: local host (e.g. <IP_ADDRESS>) + port, for external use (by the website, see next point): the host of the proxy (e.g. the herokuapp site).
What is the location (origin) of the website that wants to use the proxy. (can be multiple; pass this to CORSANYWHERE_WHITELIST )
What is the location of the website that you're trying to access over the proxy (can be multiple, CORS Anywhere does currently not offer the ability to filter this)

Sorry for not being clear. To address your three points:

Heroku
http://localhost:3000 and https://betterbggcollection.com
The BGG XML API

I was able to get it working by just setting the CORSANYWHERE_WHITELIST variable to http://localhost:3000,https://betterbggcollection.com.
Thanks for your help, I'll go ahead and close this issue out now!

For info, there is a web page  at https://dashboard.heroku.com/apps/HEROKUNAME-HEROKUID/settings
where you can set config vars:

I have not tested it yet, but I think that is one way to set the config vars mentioned in the README.

For info, there is a web page  at https://dashboard.heroku.com/apps/HEROKUNAME-HEROKUID/settings
where you can set config vars:

I have not tested it yet, but I think that is one way to set the config vars mentioned in the README.


[salsa] [jsdoc] Support for doted properties type assignment in destructive parameters.

TypeScript Version:  2.2.2 (VSCode integrated)
Code
/** Some description
 *
 * @param {PropsType} props The props of the component.
 * @param {string} props.one One property of the props.
 * @param {number} props.two Another property of the props.
 * @return {JSX.Element} A ReactElement.
 */
const SomeReactElement = ({ one, two }) => (
  <div>
    // `one` and `two` should be `string` and `number`, but they are `any`.
  </div>
);

Expected behavior:
Destructive parameters should retain type declaration in JSDoc tags
Actual behavior:
Destructive parameters lose the type definition, and are being declared as any

Duplicate of https://github.com/Microsoft/TypeScript/issues/11597

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


How?!

Honestly, why do you keep duplicating issues when on the first issue asking for this, you can ask there?

 Learn how to use grammar correctly.
2. I never sent you any piece of code about this.

 Grow up.
2. Does that even make any sense?
3. Are you trying to take that as a compliment?
Stop spamming duplicate issues on the repository.


Remove unused members from BPFtrace

A few functions didn't have implementations and one member variable was unused. The individual commits have details.
Related to #1080.

Thanks :)


Fix: tmp files exists when resyncing a repository

If a session is closed in the middle of a sync process the progress will be
interrupt. When this closed sessions restores the sync may fail since the tmp
clone folder will be occupied.
With this patch the api will try to remove the tmp folder first before
continuing the clone process.
Signed-off-by: Bruno Bottazzini<EMAIL_ADDRESS>

LGTM
Just apply the following "sed" to the commit msg: s/will be interrupt/will be interrupted/ ;)

right! Thanks


Sign in from Google Drive mobile

Hi, I'm trying to use this API and the Google Drive API to log in and display information contained in DICOM (*.dcm) files stored on Google Drive. The sign in works fine from a desktop browser but fails from the mobile app (v<IP_ADDRESS>.33 from 28 Jun 2017) complaining that sessionStorage is not available in the current the environment (error: idpiframe_initialization_failed).
How would you advise to sign in for that environment?
Just in case, the code is in the dwvgapi github repo and its associated chrome extension is dwvgapi.

HI @ivmartel, please provide more information on the device used, OS version, and browser used.

It's an Android 6.0 device. It has Google Chrome 59.0.3071.125 installed but I do not know if this is what the Google Drive app uses.
I forgot to mention that the error is triggered when calling the gapi.client.init in dwvgapi google.js#L71.

This error can be raised when web storage are disabled. We observed that to happen on iOS devices with Chrome in Incognito mode, or Chrome with third party data blocked (on any device). Would you have set any specific configuration such as incognito mode or third part data blocked in Chrome?

This is in the Android Google Drive App, correct? If so, it's probably using a WebView and that is not a supported environment for this client library

Yes, it is the Android Google Drive App. I did not set any specific configuration, just the basic install.
Ok for the not supported, would you know of another solution?

That's a question about the Google Drive app, and I don't know what auth mechanisms are supported/recommended/possible for it, if any. I recommend finding the appropriate forum and asking there — unfortunately, I don't know which forum that would be
Closing this as the usage is not supported

Ok, I asked on stackoverflow: sign-in-from-google-drive-android-app


No support for GLM4? It's the best model out there right now

Merging with https://github.com/ollama/ollama/issues/4826


Update branch name to release-0.15

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


[Chore] Merge develop into feature/v3

Description
This merges develop into feature/v3.
Context
This catches up feature/v3 so it can be merged into develop later.
Testing

./gradlew test

Documentation
N/A
Known limitations
N/A

Is it suppose to include these much commit? I made a merge 2 weeks ago https://github.com/stellar/java-stellar-anchor-sdk/pull/1553

@JiahuiWho Looks like it was squash merged by accident https://github.com/stellar/java-stellar-anchor-sdk/commit/0b327e91aaaf99c787212810db3b726a70859ba4

LGTM
Curious how to tell if it's a regular commit or a squash commit

@JiahuiWho The commit has a large diff. A merge commit would be empty.


NuGet package for version 1.1.3 but no release notes under releases.

I am wondering what changes are in 1.1.3? I cannot find anything about 1.1.3 at https://github.com/aspnet/EntityFrameworkCore/releases
Why I am asking...
I'm having issues with "Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified."
I've done an assembly binding redirect that seems to help. This is less than ideal and I was hoping 1.1.3 might help but I'm not going to blindly update without seeing what has changed.
I am targeting .NET 4.6.2.
EFCore 2.0.0 has an issue where the scaffold command creates a bool? field for a boolean not null column rather than a bool field. This seems to be a regression from 1.1.2 so I'm not keen to jump all the way to 2 just yet.

Looks like we fixed three issues. I don't think any of them will address assembly resolution issue you're seeing.
What version of Microsoft.EntityFrameworkCore.Tools.DotNet are you using?

If it's a class library project, you may also need to add the following to the *.csproj.
<PropertyGroup>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>

I don't appear to have Microsoft.EntityFrameworkCore.Tools.DotNet installed at all.
I have Microsoft.EntityFrameworkCore.Tools at version 1.1.1 (so I could bump that up a minor version).
The original install was done with the following commands.
Install-Package Microsoft.EntityFrameworkCore.SqlServer
Install-Package Microsoft.EntityFrameworkCore.Tools
Install-Package Microsoft.EntityFrameworkCore.SqlServer.Design
It is a class library project. I'll try adding your PropertyGroup suggestion and removing my binding redirect.

Without the binding redirect and with the above PropertyGroup added to the .csproj files I still get the error.
Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.

=== Pre-bind state information ===
LOG: DisplayName = System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51
 (Fully-specified)
LOG: Appbase = file:///C:/WF/LP/server/EBS_Deployment/
LOG: Initial PrivatePath = C:\WF\LP\server\EBS_Deployment\bin
Calling assembly : Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60.

LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\WF\LP\server\EBS_Deployment\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51
LOG: The same bind was seen before, and was failed with hr = 0x80070002.

   at Microsoft.EntityFrameworkCore.Infrastructure.RelationalServiceCollectionExtensions.AddRelational(IServiceCollection services)
   at Microsoft.Extensions.DependencyInjection.SqlServerServiceCollectionExtensions.AddEntityFrameworkSqlServer(IServiceCollection services)
   at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.<>c__DisplayClass4_1.<GetOrAdd>b__2(Int64 k)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.DbContext.GetServiceProvider(DbContextOptions options)
   at Microsoft.EntityFrameworkCore.DbContext.InitializeServices()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.Infrastructure.AccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.DbContext.get_QueryProvider()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.<.ctor>b__3_0()
   at Microsoft.EntityFrameworkCore.Internal.LazyRef`1.get_Value()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.System.Linq.IQueryable.get_Provider()
   at System.Linq.Queryable.Where[TSource](IQueryable`1 source, Expression`1 predicate)
   at nz.co.LanguagePerfect.Services.UserAccounts.Managers.UserAccountsClasses.<GetAcademicYears>d__57.MoveNext() in C:\WF\LP\server\Classes\Services\UserAccounts\Managers\UserAccountsClasses.cs:line 1774
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at nz.co.LanguagePerfect.Services.UserAccounts.Managers.UserAccountsClasses.<GetAcademicYears>d__55.MoveNext() in C:\WF\LP\server\Classes\Services\UserAccounts\Managers\UserAccountsClasses.cs:line 1754
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at nz.co.LanguagePerfect.Services.UserAccounts.Managers.UserAccountsManager.<GetAcademicYears>d__55.MoveNext() in C:\WF\LP\server\Classes\Services\UserAccounts\Managers\UserAccountsManager.cs:line 1808

@bricelam Thanks for showing me what has changed with the 1.1.3 release. The assembly binding redirect works for my purposes at the moment. I'll investigate moving to 2.0.0 so let's not worry about this issue too much. I appreciate the help.


The live update help link is not working

When clicking on 'Developer Center' link under the section "Live Update" , it gives 404.
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/using-the-mfpf-sdk/live-update/

The link needs to be corrected in operations console, the correct url would be https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/application-development/live-update/
Closing this git issue as this is not a Devcenter issue.


Utils: Use a temporary file for redirecting output

For the same reason as in ProcessCapture, see 839bcdb, use a temporary
file to redirect output to work around the 64k pipe buffer limit on Linux.

This change is

I've added a commit to revert to the previous implementation to call the sbt command line tool as the current solution was not stable.


Refresh stories spinner should be behind stories, not in front.

@nilnilnil Thanks, but this is a duplicate of #82. I've mentioned this issue a while ago but moved it to the 'iteration 1' milestone

@thm cool thanks. I didn't look through them all, sorry!


fix #155. Fix permissions for KibanaIndexMode

This PR fixes #155  and will most likely need additional changes in sg_action_groups for permissions
Also fixes #117

@ewolinetz @richm Please when looking at these changes consider looking at files like which is my expectation of what the perm file(s) should be according to how we define KibanaIndexMode.
[1] https://github.com/fabric8io/openshift-elasticsearch-plugin/blob/2abc1531a05dd5e067d4b57f8ced4dca164a5192/src/test/resources/io/fabric8/elasticsearch/plugin/project_strategy_roles_shared_non_ops_kibana_mode.yml

@richm @ewolinetz Updated per CR

@richm @ewolinetz I've updated the code to match the KibanaIndexMode as advertised as well as fix to pass https://github.com/openshift/origin-aggregated-logging/pull/1273.
NOTE:  Added several integration tests to match those we have in the logging repo.

openshift/origin-aggregated-logging#1273 passed so I'm assuming this PR is good to go
/lgtm

[merge]


Why CodeRefsTo() excludes all call type cross-references

I found that the implementation of CodeRefsTo() excludes all call type cross-references, which is inconsistent with the results of CodeRefsTo() I observed in IDA Pro 7.0.
# a code xref is like a fallthrough or jump, not like a call.
for xref in idb.analysis.get_crefs_to(self.idb, ea,
     types=[idaapi.fl_JN, idaapi.fl_JF, idaapi.fl_F]):
     yield xref.frm

can you provide a short snippet and/or test case that demonstrates this behavior in IDA?
maybe use https://github.com/williballenthin/python-idb/tree/master/tests/data/v7.0b/x32 as a base.

i dont recall off the top of my head, but since i left a comment there, i must have had a reason for it.

Idb file: https://github.com/williballenthin/python-idb/tree/master/tests/data/v7.0b/x64/kernel32.i64
Address: 0x689043FC
In IDA Pro:
Python>list(idautils.CodeRefsTo(0x689043FC, 1))
[1754272045L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L,<PHONE_NUMBER>L]

However, in python-idb:
In [3]: with idb.from_file('./kernel32.i64') as db:
   ...:     api = idb.IDAPython(db)

In [4]: list(api.idautils.CodeRefsTo(0x689043FC, 1))
Out[4]: []

Actually, all callees can't get their callers using CodeRefsTo in python-idb. I found the reason in implementation, types=[idaapi.fl_JN, idaapi.fl_JF, idaapi.fl_F]): excluded the call flows.

@bjchan9an could you please send a pull request?


routing: fix mc blinded path behaviour.

Because we hot swap the target public key when sending to a
blinded path we need to penalize all nodes after the introduction
point.
We could also just penalize the first node after the introduction node, however that would mean we would do a bit of more pathfinding work and only fail after considering the rest of the blinded path. I think it is not super critical to have this bit more data persistent in memory.

maybe we should add an itest ?

After a discussion with Elle we decided to only punish the first PubKey after the intropoint and create an issue which makes sure blinded route mc data is not persistent in the db but rather only held in memory and removed as soon as the payment is done.

come logs of the problem, so the problem is the wrong channel-pair is punished and we will always use the same path:
2024-11-29 18:06:59.843 [DBG] CRTR: Sending HTLC attempt(id=22159, total_amt=103302 mSAT, first_hop_amt={103302}) for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:06:59.848 [DBG] CRTR: Attempt 22159 for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323 successfully sent to switch, route:<PHONE_NUMBER>25120 (103302 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:06:59.848 [DBG] CRTR: Collecting result for attempt 22159 in payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:06:59.848 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=22159)->(Chan ID=859:1:0, HTLC ID=2832)
2024-11-29 18:06:59.848 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2832, amt=103302 mSAT, expiry=1234, hash=45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.849 [DBG] HSWC: Subscribing to result for attemptID=22159
2024-11-29 18:06:59.855 [DBG] CRTR: Payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=96698 mSAT
2024-11-29 18:06:59.909 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=22159) from mailbox
2024-11-29 18:06:59.909 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.919 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=2c97ddc578a4d2e3f07b9e70d7e697e9cec2d05219327567c21f1209cfc0a32b, next_point=03f2c7beb2228589d6572dd74d5179f29045d1dace74542e3b07fcbc0780a8bd7a) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.922 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.936 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=9e6001271edd5c1ef00a4cad685bd74a77bcbe990e3389a02d17cdff55730606, next_point=030d406edba90c6255a737210b2a9d0c15ca360722572dbff0aeebc90c394bdef2) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.971 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2832, reason=8a8c7e056ee2bcd7d30ac1e3a5d35e822cda06eb5b4dbaef74a25b4fce87f20f7a2b17ac7fa4f7634d74541acaa7e4da8ba59fd2937882b7c6adc1536afd92891829a1a0844836df0e91938463e6b8af9ab39d7b5be237cffe349f34d259565d4bec314c5c849c2a35b1bd4383c293331acce0ea97b570f84fc7b5b693b2aa0396125d1493f976da6d22ccd34c93a54ff5576f6d65cbe441b42a93b0478cf8c0d6ef0f9850ee2a7d30da3deee5538d9c75df3d87c09e2b9e369fb1ca109e623bb540e90807f6079f8879a021c304f08514a3c1d5ffda1001fe80d9594f20a7798355caf64795daa4b10ea0dd70caae3afdd57c1ff5120f2c08f1afa68a8c3413775ac3787390041fe5bba3cb048ebbe0056ff7ae89d52190dd69acfe1f6d6a45424f86d0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.980 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.986 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=54b4eab854449ef6904f9341ae08ccbdd8ab50bf1aef622dbc92e359c6fbb30a, next_point=0291f85235a104a71f4f6d28f5d3c84891fb7ecf73acf41272c39c41db221e4c91) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:06:59.991 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.020 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=acc9500344d5b22efd9b81364614872d3da7d9c913a31f747c5d62d33862b42a, next_point=02cb98e9c08c48977025b28f86c1adf59b984e26d7e6c903f69cc21238d87b34db) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.033 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:07:00.033 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2832
2024-11-29 18:07:00.033 [DBG] HSWC: Closed completed FAIL circuit for 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: (0:0:0, 22159) <-> (859:1:0, 2832)
2024-11-29 18:07:00.033 [DBG] HSWC: Storing result for attemptID=22159
2024-11-29 18:07:00.037 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=22159
2024-11-29 18:07:00.038 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=103302 mSAT
2024-11-29 18:07:00.041 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=22159) with keystone=(Chan ID=859:1:0, HTLC ID=2832)
2024-11-29 18:07:00.041 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [103302 mSAT-0 mSAT]
2024-11-29 18:07:00.041 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=025dcebc849966e84634e26e3b7d8ada5d5344c31ce22e00351abc53b62133926f -> 03b06f2a53e4c8a0b3aa47627ed94e6082cdbb256a8b1b22fe72ccdbddbaf41242, amt=0 mSAT
2024-11-29 18:07:00.041 [DBG] CRTR: Setting 025dcebc849966e84634e26e3b7d8ada5d5344c31ce22e00351abc53b62133926f->03b06f2a53e4c8a0b3aa47627ed94e6082cdbb256a8b1b22fe72ccdbddbaf41242 range to [0 mSAT-0 mSAT]
2024-11-29 18:07:00.041 [WRN] CRTR: Attempt 22159 for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323 failed: InvalidBlinding@1
2024-11-29 18:07:00.045 [DBG] HSWC: Closed FAIL circuit for 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: (0:0:0, 22159) <-> (859:1:0, 2832)
2024-11-29 18:07:00.070 [DBG] CRTR: Result collected for attempt 22159 in payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.077 [DBG] CRTR: Payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: status=In Flight, active_shards=0, rem_value=100000 mSAT, fee_limit=100000 mSAT
2024-11-29 18:07:00.077 [DBG] CRTR: PaymentSession(45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323): pathfinding for amt=100000 mSAT
2024-11-29 18:07:00.078 [DBG] CRTR: Pathfinding absolute attempt cost: 100.1 sats
2024-11-29 18:07:00.078 [DBG] CRTR: Amount 103302 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:07:00.078 [DBG] CRTR: Found route: probability=0.10260039450125205, hops=4, fee=3302 mSAT
2024-11-29 18:07:00.078 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=1.301458ms
2024-11-29 18:07:00.097 [DBG] CRTR: Sending HTLC attempt(id=22160, total_amt=103302 mSAT, first_hop_amt={103302}) for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.101 [DBG] CRTR: Attempt 22160 for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323 successfully sent to switch, route:<PHONE_NUMBER>25120 (103302 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:07:00.101 [DBG] CRTR: Collecting result for attempt 22160 in payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.101 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=22160)->(Chan ID=859:1:0, HTLC ID=2833)
2024-11-29 18:07:00.101 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2833, amt=103302 mSAT, expiry=1234, hash=45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.102 [DBG] HSWC: Subscribing to result for attemptID=22160
2024-11-29 18:07:00.108 [DBG] CRTR: Payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=96698 mSAT
2024-11-29 18:07:00.165 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=22160) from mailbox
2024-11-29 18:07:00.165 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.172 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=37cb1e59328780705a8b4e7a7870be79b17a526cb4ebeffbaf1b6f8f28e3021d, next_point=03fee998e5dea699f15229d814bd01394d0f56dd0842b1c39a5562d4b1b4509ec5) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.176 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.193 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=26cd749974fe3e8089e17430817c2cd14606fa737d7d320ade7ba05cdbb6d80f, next_point=037ea15d8aeb3deaf3cc2da0bd012b586fce0645c9dacd2428540afa06fdb5d9be) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.232 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2833, reason=26253d6b296e96c88db54ac9cad31690e3ad87c247a7f78035bed0b124ac6fbfee9670af265ffe918e48af0a0b45dd24844a03c9c8375a3927c78face47ec467314ec439d81a991d7c11c571d5d673837249945cf9f3fe01e3e8d73916f21b8b4a253bcaa455da0c75a1eab53f8312bd834519329e1c144358709cc83d924a463bae587d4dd4678360c3cabd3e2d1605cf8f68959c5bd5228a4821e0d5887addf6d66858ab00be56904ec7114317796de04dce3d699a4cd79a40b55f0adf510c8ed80f637ca227dd14f80ca42d41182d6aa4c60ef2891bd9378512d2d6b7852bc3e0fd8690be9dce51858ad5ebdbc53be366dfa2dab218f1bffb06b059d773f6c6865b9f4fd8d19e8d262969339eabe232b7080dd4054863b73da196c7ba47941fd80f40) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.239 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.245 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=60f29f300c087c0ecd6f93dea9d9c1ea30e748fe0ecaf81a8b7fa95da7f7d4b9, next_point=035e2f0cdd3dda825d21f891c6a500afb15c8e5af9a4834f7707e62df9af267c00) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.250 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.278 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=818596a2c2e3f352e266db6988465aea23051ce8538789987bb46228c2ec0692, next_point=021ea5ee870b77dd81c108dfd92bad11bdd24a6aaf62c5105c7f6973763ef97c7f) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:07:00.292 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:07:00.292 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2833
2024-11-29 18:07:00.292 [DBG] HSWC: Closed completed FAIL circuit for 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: (0:0:0, 22160) <-> (859:1:0, 2833)
2024-11-29 18:07:00.292 [DBG] HSWC: Storing result for attemptID=22160
2024-11-29 18:07:00.296 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=22160
2024-11-29 18:07:00.297 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=103302 mSAT
2024-11-29 18:07:00.300 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=22160) with keystone=(Chan ID=859:1:0, HTLC ID=2833)
2024-11-29 18:07:00.300 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [103302 mSAT-0 mSAT]
2024-11-29 18:07:00.300 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=025dcebc849966e84634e26e3b7d8ada5d5344c31ce22e00351abc53b62133926f -> 03b06f2a53e4c8a0b3aa47627ed94e6082cdbb256a8b1b22fe72ccdbddbaf41242, amt=0 mSAT
2024-11-29 18:07:00.300 [DBG] CRTR: Setting 025dcebc849966e84634e26e3b7d8ada5d5344c31ce22e00351abc53b62133926f->03b06f2a53e4c8a0b3aa47627ed94e6082cdbb256a8b1b22fe72ccdbddbaf41242 range to [0 mSAT-0 mSAT]
2024-11-29 18:07:00.300 [WRN] CRTR: Attempt 22160 for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323 failed: InvalidBlinding@1
2024-11-29 18:07:00.303 [DBG] HSWC: Closed FAIL circuit for 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: (0:0:0, 22160) <-> (859:1:0, 2833)
2024-11-29 18:07:00.324 [DBG] CRTR: Result collected for attempt 22160 in payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.331 [DBG] CRTR: Payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323: status=In Flight, active_shards=0, rem_value=100000 mSAT, fee_limit=100000 mSAT
2024-11-29 18:07:00.331 [DBG] CRTR: PaymentSession(45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323): pathfinding for amt=100000 mSAT
2024-11-29 18:07:00.331 [DBG] CRTR: Pathfinding absolute attempt cost: 100.1 sats
2024-11-29 18:07:00.331 [DBG] CRTR: Amount 103302 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:07:00.331 [DBG] CRTR: Found route: probability=0.10260033668913819, hops=4, fee=3302 mSAT
2024-11-29 18:07:00.331 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=166.584µs
2024-11-29 18:07:00.348 [DBG] CRTR: Sending HTLC attempt(id=22161, total_amt=103302 mSAT, first_hop_amt={103302}) for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.352 [DBG] CRTR: Attempt 22161 for payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323 successfully sent to switch, route:<PHONE_NUMBER>25120 (103302 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:07:00.352 [DBG] CRTR: Collecting result for attempt 22161 in payment 45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323
2024-11-29 18:07:00.352 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=22161)->(Chan ID=859:1:0, HTLC ID=2834)
2024-11-29 18:07:00.352 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2834, amt=103302 mSAT, expiry=1234, hash=45f1fdda6f8d45a7206fa7d7081fd115ea56964a010ac172e1815364ddd91323, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739

same for a bigger amount:
| INVALID_ONION_BLINDING @ 2nd hop |        0.031 |        0.446 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        0.455 |        0.823 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        0.838 |        1.191 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        1.200 |        1.550 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        1.555 |        1.906 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        1.922 |        2.295 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        2.312 |        2.651 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        2.666 |        3.033 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        3.050 |        3.404 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        3.420 |        3.766 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        3.782 |        4.119 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 2nd hop |        4.134 |        6.078 | 5000         | 4.332 |     1314 |<PHONE_NUMBER>25088 | My Lightning ☇->alice->03dd7d->02a8cf->033948 |
| INVALID_ONION_BLINDING @ 1st hop |        6.089 |        6.313 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        6.324 |        6.578 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        6.594 |        6.831 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        6.849 |        7.096 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        7.112 |        7.323 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        7.341 |        7.561 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        7.569 |        7.778 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        7.795 |        8.007 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        8.025 |        8.231 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        8.248 |        8.467 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        8.487 |        8.703 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        8.721 |        8.931 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        8.939 |        9.219 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948                 |
| INVALID_ONION_BLINDING @ 1st hop |        9.237 |        9.465 | 5000         | 3.327 |     1234 |<PHONE_NUMBER>25120 | alice->03dd7d->02a8cf->033948

2024-11-29 18:13:01.324 [DBG] CRTR: Attempt 23017 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:01.324 [DBG] CRTR: Collecting result for attempt 23017 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.324 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23017)->(Chan ID=859:1:0, HTLC ID=2841)
2024-11-29 18:13:01.324 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2841, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.325 [DBG] HSWC: Subscribing to result for attemptID=23017
2024-11-29 18:13:01.325 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=246673 mSAT
2024-11-29 18:13:01.387 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=23017) from mailbox
2024-11-29 18:13:01.387 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.394 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=84368afe2dfc73669997f266be120f04bc90f6c9938f4d250c17ae4cec3135de, next_point=031d628ab856c71d3c6881f9518643bef570b81b63589f06af18f475283e15f992) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.398 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.413 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=0d9fab2d2c6eb46cf7468f1ddc4d15ffe5a7394443d541dbc87467ae09fc1aff, next_point=0272657022a2e9a85d488dedf0603f3ace3de2a5142c2a9fdf10db7fa81f394d93) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.462 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2841, reason=1d5c3fdce1b1d3c237b898b93caacd55ca2be6a59b75aed3eb8f071ea795bf243111177fd5426f2e4ae411d247a3e3c9311aa5a67481190c40ddf2794abc4b24973c5e1def5a52b1fa5303ccfeace9ea1563e54b71fe80d7c3cc8cf625d34869d2e076fe7e7ea46142d6a93e15ba1b0f1ef3818fda0c6069afec7b13677d46e91e6f68bd0945090fb103b8a41c1e90979d277094e6f49cded62d48bebacce345efe60b384e498b715169faab6f2520ed4fc81963e12fd82037fa95bafc502ef197e21a42e9ddb4088ace9665cb9d271851ed0cf8c6d060683de845e7f7dc202012af489831cc2054271c674990e73d5df3ed82070b7f0540c780bf7d42a52b293be982e17454032a5ef2b89a2bec65435da3bedcdf66c26ca431bbcef2f746588134812f) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.469 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.474 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=60808f959b03d6ed0a45a1965ca5b6bdcea2b013d5fd98eec926aa5911d63f4a, next_point=0387f341f2da1ff1f2548e60a3133c17160806213315267bfcda6b16978c67a169) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.480 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.500 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=3b433beff07ddf04ff48ee8b3e9791b58ca4bf765ba7cf2b4026753b9e610f35, next_point=02f625966df33b65fc145983423c2e62cae7c8323b6a4a3c8c0bf0da7e9614ea0e) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.517 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:13:01.517 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2841
2024-11-29 18:13:01.518 [DBG] HSWC: Closed completed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23017) <-> (859:1:0, 2841)
2024-11-29 18:13:01.518 [DBG] HSWC: Storing result for attemptID=23017
2024-11-29 18:13:01.522 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=23017
2024-11-29 18:13:01.523 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=5003327 mSAT
2024-11-29 18:13:01.527 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [5003327 mSAT-0 mSAT]
2024-11-29 18:13:01.527 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=23017) with keystone=(Chan ID=859:1:0, HTLC ID=2841)
2024-11-29 18:13:01.527 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae -> 03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298, amt=0 mSAT
2024-11-29 18:13:01.527 [DBG] CRTR: Setting 02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae->03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298 range to [0 mSAT-0 mSAT]
2024-11-29 18:13:01.527 [WRN] CRTR: Attempt 23017 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 failed: InvalidBlinding@1
2024-11-29 18:13:01.533 [DBG] CRTR: Result collected for attempt 23017 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.534 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=0, rem_value=5000000 mSAT, fee_limit=250000 mSAT
2024-11-29 18:13:01.534 [DBG] CRTR: PaymentSession(8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7): pathfinding for amt=5000000 mSAT
2024-11-29 18:13:01.534 [DBG] CRTR: Pathfinding absolute attempt cost: 105 sats
2024-11-29 18:13:01.534 [DBG] CRTR: Amount 5003327 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:13:01.534 [DBG] CRTR: Found route: probability=0.05130812580074241, hops=4, fee=3327 mSAT
2024-11-29 18:13:01.534 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=185.917µs
2024-11-29 18:13:01.540 [DBG] CRTR: Sending HTLC attempt(id=23018, total_amt=5003327 mSAT, first_hop_amt={5003327}) for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.544 [DBG] CRTR: Attempt 23018 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:01.544 [DBG] CRTR: Collecting result for attempt 23018 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.545 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23018)->(Chan ID=859:1:0, HTLC ID=2842)
2024-11-29 18:13:01.545 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2842, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.547 [DBG] HSWC: Subscribing to result for attemptID=23018
2024-11-29 18:13:01.547 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=246673 mSAT
2024-11-29 18:13:01.550 [DBG] HSWC: Closed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23017) <-> (859:1:0, 2841)
2024-11-29 18:13:01.608 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=23018) from mailbox
2024-11-29 18:13:01.608 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.616 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=ba1cd17b76dfd8233520e1a6df32fb9a646336a9a5e244e109a96ed1f48b6df1, next_point=026a23761cf393611bd36d87e405b4230e2e867e5f5bf48886f6b70b9c23054c12) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.622 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.637 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=2f6b422d4946a26e57309a388c21aec202d4931bee068a2704db3d031b5c557c, next_point=02cf2d50d0df4b96efaa0c940552984061979fbb580dfe792b0ba956da70077bef) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.680 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2842, reason=90ef779f64e7efa7b62b3a7f060132d507d8831107032623b6cffa31eff71c22b30609476d938707e44c91d3f866c6f2b478a8661d297906b5beebcd819c5d3c63314d759e9c419ac89ba6fe883e2d3aaecdbfc8f2156420bea4548ad106288ef47635b1d7e5327c1533e872642919957d72203aa2c35c2e802d2438a7dae2e2dea227e7d340e560b3352cfce372aad40722f4c4de947ceb2a8c861c89865abb77cf6791a5076e7fdd0d341bb478c2f08241aafaf27a39a040eceb6fd90da8d5f9de5d0db6537ad7df07b548ee7002e0ac0f15d81f21b893f6891ca8c79a1800462eb2b725519404d9627bd1f0b961af569778c875d12d4f89498fe7209be5a70c5dea2c1eef4ea57dee29229f3c65353174b229195aa166fc1c085ce907412e1f2743f0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.686 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.692 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=a4d760919783a8993531070c17f66d111fcdd33205a6efc330359738ff1d13ed, next_point=03a44ba80a6fc36dbfee3d0abcbbd7f31f18b2cb2cf5994e28e464a98a4e84cdce) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.698 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.721 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=59ee5cda2c4cbf665d5a320c6f4626abea923c20b458a5271b34542ee4c18215, next_point=0384edf11f03aa7409deefa30574a2fb1eed264bc547c7a95fd4f2878592c7de98) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.735 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:13:01.735 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2842
2024-11-29 18:13:01.735 [DBG] HSWC: Closed completed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23018) <-> (859:1:0, 2842)
2024-11-29 18:13:01.735 [DBG] HSWC: Storing result for attemptID=23018
2024-11-29 18:13:01.740 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=23018
2024-11-29 18:13:01.741 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=5003327 mSAT
2024-11-29 18:13:01.744 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=23018) with keystone=(Chan ID=859:1:0, HTLC ID=2842)
2024-11-29 18:13:01.744 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [5003327 mSAT-0 mSAT]
2024-11-29 18:13:01.744 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae -> 03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298, amt=0 mSAT
2024-11-29 18:13:01.744 [DBG] CRTR: Setting 02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae->03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298 range to [0 mSAT-0 mSAT]
2024-11-29 18:13:01.744 [WRN] CRTR: Attempt 23018 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 failed: InvalidBlinding@1
2024-11-29 18:13:01.749 [DBG] HSWC: Closed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23018) <-> (859:1:0, 2842)
2024-11-29 18:13:01.759 [DBG] CRTR: Result collected for attempt 23018 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.760 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=0, rem_value=5000000 mSAT, fee_limit=250000 mSAT
2024-11-29 18:13:01.760 [DBG] CRTR: PaymentSession(8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7): pathfinding for amt=5000000 mSAT
2024-11-29 18:13:01.760 [DBG] CRTR: Pathfinding absolute attempt cost: 105 sats
2024-11-29 18:13:01.760 [DBG] CRTR: Amount 5003327 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:13:01.760 [DBG] CRTR: Found route: probability=0.05130928445199554, hops=4, fee=3327 mSAT
2024-11-29 18:13:01.760 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=218.583µs
2024-11-29 18:13:01.764 [DBG] CRTR: Sending HTLC attempt(id=23019, total_amt=5003327 mSAT, first_hop_amt={5003327}) for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.768 [DBG] CRTR: Attempt 23019 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:01.768 [DBG] CRTR: Collecting result for attempt 23019 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.768 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23019)->(Chan ID=859:1:0, HTLC ID=2843)
2024-11-29 18:13:01.768 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2843, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.769 [DBG] HSWC: Subscribing to result for attemptID=23019
2024-11-29 18:13:01.769 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=246673 mSAT
2024-11-29 18:13:01.830 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=23019) from mailbox
2024-11-29 18:13:01.830 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.838 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=6c64bdc41ecde0ab729102adf9802a1d91b6e067400450ca115e8933f62ca3f3, next_point=031d50bdae43898323d8b80345851e34eec1be701f6bfd115d43fd58971400acec) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.843 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.856 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=1ab1b9b7cc2f763c102ce75fa6f1452ed59a684460ae7e55cb5e4f3cb525b419, next_point=0313d1f85cdef6957eebd715d742321b1209ce6df8fce79804f6cdfa42eda98746) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.906 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2843, reason=32c9ec5c961feed37e8dec5478a7058199fd8b0bcce92fd88bce7cab99eba2e05ca9bef3d3eacb852230c43b85b7a9cd09ed588f57d1ccba28c67391c10b7b9176322851059fd0de27650e6aad85caebe145619bc5d06f59bebd94a147baed78800d1da34a97a99644be947488d09994f63e7fadde3789c5424910d754a7da7bc26d6e0e6a9d94319126168120b95a2be33a5b44a23a3584e52aa9a5c597e9aeed67a813fe0216c5da10208305b5676cece49ce3ab16b2f1db0e039ae192681fb87eff6af9146335b6174747b79a148ccd5f5abda2d633b1cac9a1659ac42c49235b30602b80cbed6f5faa746e71b912f1fdff55c26f86ffd64fc849cf5c40a21b726e77e9bca8e2c264f3e294523203f699d9cba2ffc14572aa4ef5f246d7b2e67af4f2) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.914 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.919 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=bcfcecd8ceec76a34112eae079cf5a81e644cf5614f1b919c58a3a2ffa8ce808, next_point=02a5e3301b5b478bac85a5467cf63d741ce18bae86127e4420246e35086deb2a7c) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.924 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.951 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=3cd27556690efe8f2e484cddb763ae0e469e5fb5611bd0eb8420e4fd9bfa2832, next_point=03096b29a9996ff630df5292d4d41141d3fcf4062d3a6fe86ab79c0567f120cacc) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:01.965 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:13:01.965 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2843
2024-11-29 18:13:01.965 [DBG] HSWC: Closed completed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23019) <-> (859:1:0, 2843)
2024-11-29 18:13:01.965 [DBG] HSWC: Storing result for attemptID=23019
2024-11-29 18:13:01.969 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=23019
2024-11-29 18:13:01.970 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae -> 03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298, amt=0 mSAT
2024-11-29 18:13:01.973 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=23019) with keystone=(Chan ID=859:1:0, HTLC ID=2843)
2024-11-29 18:13:01.973 [DBG] CRTR: Setting 02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae->03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298 range to [0 mSAT-0 mSAT]
2024-11-29 18:13:01.973 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=5003327 mSAT
2024-11-29 18:13:01.973 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [5003327 mSAT-0 mSAT]
2024-11-29 18:13:01.973 [WRN] CRTR: Attempt 23019 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 failed: InvalidBlinding@1
2024-11-29 18:13:01.977 [DBG] HSWC: Closed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23019) <-> (859:1:0, 2843)
2024-11-29 18:13:01.989 [DBG] CRTR: Result collected for attempt 23019 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:01.990 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=0, rem_value=5000000 mSAT, fee_limit=250000 mSAT
2024-11-29 18:13:01.990 [DBG] CRTR: PaymentSession(8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7): pathfinding for amt=5000000 mSAT
2024-11-29 18:13:01.990 [DBG] CRTR: Pathfinding absolute attempt cost: 105 sats
2024-11-29 18:13:01.991 [DBG] CRTR: Amount 5003327 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:13:01.991 [DBG] CRTR: Found route: probability=0.05131042760025676, hops=4, fee=3327 mSAT
2024-11-29 18:13:01.991 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=204.292µs
2024-11-29 18:13:01.997 [DBG] CRTR: Sending HTLC attempt(id=23020, total_amt=5003327 mSAT, first_hop_amt={5003327}) for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.001 [DBG] CRTR: Attempt 23020 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:02.001 [DBG] CRTR: Collecting result for attempt 23020 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.001 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23020)->(Chan ID=859:1:0, HTLC ID=2844)
2024-11-29 18:13:02.001 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2844, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.002 [DBG] HSWC: Subscribing to result for attemptID=23020
2024-11-29 18:13:02.003 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=246673 mSAT
2024-11-29 18:13:02.058 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=23020) from mailbox
2024-11-29 18:13:02.058 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.063 [DBG] CRTR: Stored mission control results: 5 added, 0 deleted
2024-11-29 18:13:02.067 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=0149918c0b1eaa79453c4e8928134b9b29fbb8961b95eab381d7a635af5b7727, next_point=036504da0224ff8d43e38cc3312ff71baa9846c3cfcb958cb3c2b8787476be6f43) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.072 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.085 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=7d7dc370684112852752fb766647a676a493619c4fc2ff02a6091955500725f0, next_point=02a2536b89b5b58a678ef85983ff3f4d29212caa49b548ab9a011bee4bcd151121) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.129 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2844, reason=ee3fa6ff25b893c2b35ef420fd471dcbc166b334decc53441605743d557e14234489cea7e069e24fd2b2dbe22897635587a85a156db5be0979dd04f38be7da21c5acb51809568b0ee512365f42751d4f9ce14a4bed38215c804d80ebf48c7c0da48fe760b1fde01bceb2801c016af5e9e696fe4e5b66a2d35fdff05ee96ac5a80196b7e00a9570f47557a21900da1e0c40118cb0a42d88657515062336a023242df2fc79b942ad4a8f9281e01909fe38ee5705e9837e808693607515cc8061c8c3445c5b89a936c99ec68f23d80093417910d0f8a85c54709cd799fccefdee9359f6f7ebdbc1c807917a616033e8287ea58789df6a82cf8b084aaf131d847620ae5592a4b357a138ebe2d0b0deb0806d14e5f5ddb666e63e37e34de3ba3e4edf7c1b5431) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.137 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.143 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=5e789cfa1da7199da0375d28f48f97a38553469044c4a4c99e45b3fea8282fd2, next_point=0326cefdecd315ffead5443cd306b3cbbf0c2b32681e12d7b9e80ae096f296d1f1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.148 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.176 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=c1f34281b7554b9506c22a3575ec1b6256f2f53357e00ffc317c5755b955b708, next_point=036c8ffa195907135c8a27ea6a747edc44ae1ea7158bf185e8a4cd1f5f186328e0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.188 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:13:02.188 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2844
2024-11-29 18:13:02.188 [DBG] HSWC: Closed completed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23020) <-> (859:1:0, 2844)
2024-11-29 18:13:02.188 [DBG] HSWC: Storing result for attemptID=23020
2024-11-29 18:13:02.193 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=23020
2024-11-29 18:13:02.194 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=5003327 mSAT
2024-11-29 18:13:02.194 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [5003327 mSAT-0 mSAT]
2024-11-29 18:13:02.197 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=23020) with keystone=(Chan ID=859:1:0, HTLC ID=2844)
2024-11-29 18:13:02.197 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae -> 03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298, amt=0 mSAT
2024-11-29 18:13:02.197 [DBG] CRTR: Setting 02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae->03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298 range to [0 mSAT-0 mSAT]
2024-11-29 18:13:02.197 [WRN] CRTR: Attempt 23020 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 failed: InvalidBlinding@1
2024-11-29 18:13:02.201 [DBG] HSWC: Closed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23020) <-> (859:1:0, 2844)
2024-11-29 18:13:02.212 [DBG] CRTR: Result collected for attempt 23020 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.213 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=0, rem_value=5000000 mSAT, fee_limit=250000 mSAT
2024-11-29 18:13:02.213 [DBG] CRTR: PaymentSession(8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7): pathfinding for amt=5000000 mSAT
2024-11-29 18:13:02.214 [DBG] CRTR: Pathfinding absolute attempt cost: 105 sats
2024-11-29 18:13:02.214 [DBG] CRTR: Amount 5003327 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:13:02.214 [DBG] CRTR: Found route: probability=0.051311526219394415, hops=4, fee=3327 mSAT
2024-11-29 18:13:02.214 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=375.75µs
2024-11-29 18:13:02.220 [DBG] CRTR: Sending HTLC attempt(id=23021, total_amt=5003327 mSAT, first_hop_amt={5003327}) for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.225 [DBG] CRTR: Attempt 23021 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:02.225 [DBG] CRTR: Collecting result for attempt 23021 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.225 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23021)->(Chan ID=859:1:0, HTLC ID=2845)
2024-11-29 18:13:02.225 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2845, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.226 [DBG] HSWC: Subscribing to result for attemptID=23021
2024-11-29 18:13:02.226 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=1, rem_value=0 mSAT, fee_limit=246673 mSAT
2024-11-29 18:13:02.286 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): removing Add packet (Chan ID=0:0:0, HTLC ID=23021) from mailbox
2024-11-29 18:13:02.286 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.296 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=87944b98fe28ae8ea3641394a79f7c05e2b96718a1bbbeb3c8e1f0b9a598850f, next_point=02ebb6f64a75b7ea527d830aaf3b1ce26a775eeca272e8c74aee59c0afe08d48db) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.301 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=1) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.313 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=addccc4878c423f1ee9dca15b20a5e313b40bdccbae6d149d5fd2d4f76f2e4e6, next_point=021b0872458f59041455beb80443fd3d975a3aebc26057f9562e7bc0e962975063) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.366 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2845, reason=ffa55dfa51a9a874ca6f29b9b0878431b0f730656340a1589ad59e35bc21b274d2b6caed905b604e88cb1ea632010458941a3be1f457cfee09170e5664c842898c18f7ba7ba861d0f209a67fd2cabf71086728935fd361d04692584d840e99e5554a8c795fe18b9a0006373f5335bdfc29cdd545b76bb819995918b188188e8b41d2d2fefe50897b9afa33a25c3904a4b62c2d78aa09f9be577847972569e4f5c209c182bdfa7880cd428614d4db1cdc95c25a61aa86c58d98c6804360e8c46f025961a69e2e73897361c116a2f9764c992a24f95f7ff7acf592213f7726ce8642dc64c6cd4f6094097c154332d9ae99853f2378770af0b09734f730293d6013578554a4550ff64c837f7522a1bd7f0c1f426dddef3f0bdb28aa033605ae83ce930cfde8) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.377 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.382 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=70e2280be3aa6ca8eae0201659a7f98bf35658b257156c74edda15563b35eecf, next_point=0289538931338c494fd26b9fc1a918ce93f639df8315ed928640ebd02677725648) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.388 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending CommitSig(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, num_htlcs=0) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.411 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received RevokeAndAck(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, rev=adf2a7cf052772c6d3548f0dd6b9841ae5b9c7ad8b02b1eb329388ee3fcdb491, next_point=0246417197bb1116205396d9ef9e20a1b16cbdeeba2beafe78e3b19187ab589f3b) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.425 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): settle-fail-filter: count=1, filter=[0]
2024-11-29 18:13:02.425 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): Failed to send HTLC with ID=2845
2024-11-29 18:13:02.425 [DBG] HSWC: Closed completed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23021) <-> (859:1:0, 2845)
2024-11-29 18:13:02.425 [DBG] HSWC: Storing result for attemptID=23021
2024-11-29 18:13:02.429 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=23021
2024-11-29 18:13:02.430 [DBG] CRTR: [default]: Reporting pair success to Mission Control: pair=02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73 -> 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c, amt=5003327 mSAT
2024-11-29 18:13:02.433 [DBG] HSWC: Tearing down circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=23021) with keystone=(Chan ID=859:1:0, HTLC ID=2845)
2024-11-29 18:13:02.433 [DBG] CRTR: Setting 02f945e7cca9aaa586ae01f775d3f9fbee4a31ea21e46198efc5812aa085c46d73->034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c range to [5003327 mSAT-0 mSAT]
2024-11-29 18:13:02.433 [DBG] CRTR: [default]: Reporting pair failure to Mission Control: pair=02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae -> 03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298, amt=0 mSAT
2024-11-29 18:13:02.433 [DBG] CRTR: Setting 02a8cffc7a9e20b88c8449e9c7af8c27bd4914823027a9072f9a225edbde19efae->03394891d80c82fdc080aa6215e68d0218f73cb5cc2c3423bd5312493a2197b298 range to [0 mSAT-0 mSAT]
2024-11-29 18:13:02.433 [WRN] CRTR: Attempt 23021 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 failed: InvalidBlinding@1
2024-11-29 18:13:02.438 [DBG] HSWC: Closed FAIL circuit for 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: (0:0:0, 23021) <-> (859:1:0, 2845)
2024-11-29 18:13:02.451 [DBG] CRTR: Result collected for attempt 23021 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.453 [DBG] CRTR: Payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7: status=In Flight, active_shards=0, rem_value=5000000 mSAT, fee_limit=250000 mSAT
2024-11-29 18:13:02.453 [DBG] CRTR: PaymentSession(8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7): pathfinding for amt=5000000 mSAT
2024-11-29 18:13:02.453 [DBG] CRTR: Pathfinding absolute attempt cost: 105 sats
2024-11-29 18:13:02.453 [DBG] CRTR: Amount 5003327 mSAT not in range for edge<PHONE_NUMBER>64032
2024-11-29 18:13:02.453 [DBG] CRTR: Found route: probability=0.051312721468216325, hops=4, fee=3327 mSAT
2024-11-29 18:13:02.453 [DBG] CRTR: Pathfinding perf metrics: nodes=8, edges=19, time=203.333µs
2024-11-29 18:13:02.459 [DBG] CRTR: Sending HTLC attempt(id=23022, total_amt=5003327 mSAT, first_hop_amt={5003327}) for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.463 [DBG] CRTR: Attempt 23022 for payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7 successfully sent to switch, route:<PHONE_NUMBER>25120 (5003327 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1234
2024-11-29 18:13:02.463 [DBG] HSWC: ChannelLink(4d371e0439980326339f0510e2701973235ecd878e2c37566219c5d059ce4a1b:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=23022)->(Chan ID=859:1:0, HTLC ID=2846)
2024-11-29 18:13:02.463 [DBG] CRTR: Collecting result for attempt 23022 in payment 8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7
2024-11-29 18:13:02.463 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=1b4ace59d0c5196256372c8e87cd5e23731970e210059f3326039839041e374d, id=2846, amt=5003327 mSAT, expiry=1234, hash=8215fba00d55634060aaced78b5a3f34a7cb6eeac2daaf981f4902e5570d17d7, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-11-29 18:13:02.464 [DBG] HSWC: Subscribing to result for attemptID=23022

After discussions with @bitromortac we decided to change the approach:
We are going to introduce a static target key (via a nums Point) so that no node can come up with the corresponding private key to create valid routes. When searching for paths or reporting an error in a blinded route we will use this key to persist the change. This will make it easy for us to clear the current MC-Store from blinded path data when we introduce the new blinded path logic where we won't persist blinded path MC data.

After trying to implement the option of a static target public key, I realised we cannot do this because the problem are rpc calls like SendToRoute. We do not want to swap out the public key for predefined routes, because there is no MPP payment happening. So we should keep it as is, and refactor the whole logic of Mission Control results in another PR.
Moreover because it came up in a discussion, I added a testcase where the blinded path has duplicated hops, to make sure the pathfinding logic can handle this case. Blinded routes can have duplicated hops we can either abort the payment when parsing the invoice, but because we currently don't do it a testcase was created to verify that this does not cause any trouble with the pathfinding logic.

Moreover because it came up in a discussion, I added a testcase where the blinded path has duplicated hops, to make sure the pathfinding logic can handle this case. Blinded routes can have duplicated hops we can either abort the payment when parsing the invoice, but because we currently don't do it a testcase was created to verify that this does not cause any trouble with the pathfinding logic.

Nice :pray:!
In the current state of the PR, where we penalize the hop starting at the introduction node, this will penalize the introduction node (as the "node probability" will start to decline if the starting node of the hop accrues a lot of failures). We originally tried to avoid that to not disincentivize nodes from routing blinded payments.
So the problem is that we can't penalize the first hop after the intro node, because we don't want the intro node to get penalized for its service and we can't penalize the last hop because the target node pubkey was replaced.
I think that the conclusive fix is to append a dummy hop (real target, dummy target) to the blinded paths and search a path to the dummy target. When penalizing we would then keep the penalization as is, using the real blinded route's last hop. This is then also compatible with somebody doing external pathfinding, using mission control data produced by SendToRoute?

I think that the conclusive fix is to append a dummy hop (real target, dummy target) to the blinded paths and search a path to the dummy target. When penalizing we would then keep the penalization as is, using the real blinded route's last hop. This is then also compatible with somebody doing external pathfinding, using mission control data produced by SendToRoute?

Ahh ok did not think about this, will come up with the dummy hop solution then.

The approach changed now, we are still penalizing the last hop but when sending a payment we add a NUMS Target key for blinded paths and as soon as the route is found before create the final route we drop it again. The CI passed lmk what you think, thank you @bitromortac for the ideas 🙏


QNCache.copy

It should be great if we can do something like:
new QNCacheBuilder().createFromQNCache(anotherQNCacheInstance);

Why? Please, share a history when you want to double the data and have it unrelated.
By the way, the cache is something you should wrap with another class. Something near to your domain. And that class is a good place to put that data duplication.

Inactive issue: closed


Application class implementation is redundant

It's not really convenient that you bring the default application impl with your android library. It's very rare for real-life project to don't have a chosen way of init already, usually via it's own Application class or via jetpack app-startup.
Not only it's unnecessary and mostly useless piece of code, it also forces usage of tricks then this library is used in your manifest - adding obscure tools:replace="android:name" in app AndroidManifest.xml

you can also look at other libraries which require init as an example, such as Stetho or AppCenter SDK

Released in 2.2.0.


Tarpaulin fails when default-run is present

When I leave the default-run key in my Cargo.toml, tarpaulin can't parse my manifest.
Here's my repo

This is now fixed, just had to bump the cargo version number :+1: it's pushed to the develop branch and I'm just doing a release now so that will be up in about 20 or so minutes


Enable 'all' for country filter to display the aggregated values for all countries

Allow --country=all
Aggegate then cases and deaths per day displaying the data for all countries
Change titles in graph in "... In All Countries"

done.


Add VRF device to support egress gateways

Issue #, if available:
Description of changes:
We require egress gateways for exposing services to the internet. VRF devices are a robust mechanism to do policy based routing. They also combine well with various BGP daemons and/or CNIs.
Testing performed:
Test cases added, clusters successfully rolled out.
Discussion:
The way networking is done in the machine template is rather wrong: We can not support multiple routes or IPs per network interface, or none of those if the devices is a slave of a virtual network devices. I've only added the pieces that are required to make this work, but I've designed it so that the existing code can be refactored easily.

The e2e tests failing has nothing to do with the PR itself. It fails on capmox-controller-manager not starting. The same e2e test works with this PR using my notebook.


update engines requirement in package.json to be greater or equal to node 0.12

This commit dropped Node 0.10.0 compatibility so let's update the engines prop in package.json to reflect this.
Possible it could be ">=0.11.0"? But testing is done on iojs and node 0.12 so that seemed like the safer bet.
thanks!

Sure, but doesn't really matter. It's not enforced anyways and nobody sees the warning.


Consider removing vite.config.js

Hydrogen is powered by Vite.
On the surface, it looks a lot like a standard Vite project, because we have a vite.config.js file with a simple hydrogen() plugin.
However, this is misleading:

Hydrogen's plugin does a BUNCH of stuff — introduces virtual modules, CSS processing for server components, SSR, etc. This likely interferes with behavior a developer might want to introduce if they are familiar with Vite — behavior which could be incompatible with Hydrogen.
We often are tempted to say "Hydrogen is a Vite project — go to Vite's docs to learn more about X." But this is not a good strategy, as Hydrogen customizes Vite so much that we should be supporting the breadth of documentation needed.
It's probably easy to screw up Hydrogen by introducing other Vite plugins.

To solve these problems, we should consider removing vite.config.js from the starter template, and adding a vite property to hydrogen.config.js, which was introduced in #1065.
This allows the developer to override certain Vite settings and apply plugins, but it's clear that the ability to customize Vite is merely an escape hatch allowed by Hydrogen and not a core expectation. This is similar to the behavior Next.js uses to customize Webpack.
To do this, we likely need to switch to a dedicated hydrogen dev and hydrogen build command rather than raw vite and vite build. There are additional benefits to this, too, like being able to provide better error messaging. I believe @cartogram is already working on this specific thing.

@frandiox — in the Plugin system you're exploring, we should follow through on this and remove the vite config file — though it would be nice to be able to eject this if necessary

@benjaminsehl Yes, I've had this in mind for a while and some of the recent changes will make this possible. This will be implemented after the plugins.
One of the reasons I'm trying to introduce plugin/vite.js and so on is basically to remove vite.config.js. Plugins will be able to pass optimizeDeps and similar without the user doing anything.
Eventually, we will be able to remove vite.config.js and allow users to create it to optionally add their own Vite config without doing anything Hydrogen-related in that file. In this case, it wouldn't even be considering "ejecting" since it's a completely optional file they add on their own.