text:
[bug]: Unable to retrieve initial bootstrap peers: no addresses found

Background
Unable to sync to graph
Your environment

0.15.2
Alpine 3.12 (Docker container)
Bitcoin 23.0.0
embassyOS

Steps to reproduce
Install LND and start the service.  LND syncs to chain and then us unable to sync to graph, complaining about bootstrap peers being unavailable.  It is possible to ping the bootstrap nodes directly from the LND container when this is happening.
[INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
[INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
[ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found

nslookup from the container:
# nslookup lseed.bitcoinstats.com

Server:    127.0.0.11
Address:  127.0.0.11:53

Non-authoritative answer:
Name:  lseed.bitcoinstats.com
Address: 2001:41d0:701:1100::1eb

Non-authoritative answer:
Name:  lseed.bitcoinstats.com
Address: 178.128.199.185
Name:  lseed.bitcoinstats.com
Address: 18.234.160.51
Name:  lseed.bitcoinstats.com
Address: 68.96.103.79
Name:  lseed.bitcoinstats.com
Address: 93.241.53.3
Name:  lseed.bitcoinstats.com
Address: 34.254.183.158
Name:  lseed.bitcoinstats.com
Address: 185.45.113.201
Name:  lseed.bitcoinstats.com
Address: 98.127.88.124
Name:  lseed.bitcoinstats.com
Address: 3.236.75.212
Name:  lseed.bitcoinstats.com
Address: 84.83.38.49
Name:  lseed.bitcoinstats.com
Address: 100.99.8.64
Name:  lseed.bitcoinstats.com
Address: 166.70.145.151
Name:  lseed.bitcoinstats.com
Address: 109.117.184.99
Name:  lseed.bitcoinstats.com
Address: 172.81.182.165
Name:  lseed.bitcoinstats.com
Address: 24.17.22.37
Name:  lseed.bitcoinstats.com
Address: 81.170.132.97
Name:  lseed.bitcoinstats.com
Address: 98.210.161.137
Name:  lseed.bitcoinstats.com
Address: 86.88.77.5
Name:  lseed.bitcoinstats.com
Address: 35.238.153.25
Name:  lseed.bitcoinstats.com
Address: 89.142.136.179
Name:  lseed.bitcoinstats.com
Address: 18.184.210.20
Name:  lseed.bitcoinstats.com
Address: 192.168.1.150
Name:  lseed.bitcoinstats.com
Address: 90.224.117.204
Name:  lseed.bitcoinstats.com
Address: 188.251.251.232
Name:  lseed.bitcoinstats.com
Address: 170.75.163.38
Name:  lseed.bitcoinstats.com
Address: 197.237.170.19

Adding a node manually does not solve
Expected behaviour
Sync to graph
Actual behaviour
Fails to bootstrap / sync to graph indefinitely (after days of testing)

Could you check your logs restarting the node with debuglevel=debug in your lnd.conf?

@kn0wmad and I are working together on this to solve it LND for EmbassyOS users.  Here is the debug log from one of them:
2022-10-24T20:51:11+01:00  config fetched. alias = "NodeNameWasHere"
2022-10-24T20:51:11+01:00  alias = "NodeNameWasHere"
2022-10-24T20:51:11+01:00  bitcoind_selected = true
2022-10-24T20:51:11+01:00  bitcoin_synced = true
2022-10-24T20:51:11+01:00  use_neutrino = false
2022-10-24T20:51:11+01:00  Certificate check complete. No changes required.
2022-10-24T20:51:11+01:00  creating public directory...
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.572 [INF] LTND: Version: 0.15.2-beta commit=v0.15.2-beta, build=production, logging=default, debuglevel=debug
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.572 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.576 [DBG] SGNR: Signer RPC server successfully register with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.576 [DBG] WLKT: WalletKit RPC server successfully registered with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.576 [DBG] RRPC: Router RPC server successfully register with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.577 [DBG] ARPC: Autopilot RPC server successfully register with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.577 [DBG] NTFR: ChainNotifier RPC server successfully register with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.577 [DBG] IRPC: Invoices RPC server successfully registered with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.577 [DBG] VRPC: Versioner RPC server successfully registered with root gRPC server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.577 [INF] RPCS: RPC server listening on 0.0.0.0:10009
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.579 [DBG] SGNR: Signer REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.584 [DBG] WLKT: WalletKit REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.585 [DBG] RRPC: Router REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.591 [DBG] ARPC: Autopilot REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.593 [DBG] NTFR: ChainNotifier REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.630 [DBG] IRPC: Invoices REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.631 [DBG] VRPC: Versioner REST server successfully registered with root REST server
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.631 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.632 [INF] LTND: Opening the main database, this might take a few minutes...
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.632 [INF] LTND: Opening bbolt database, sync_freelist=true, auto_compact=true
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.634 [INF] CHDB: Not compacting database file at /root/.lnd/data/graph/mainnet/channel.db, it was last compacted at 2022-10-24 19:48:58.92784646 +0000 UTC (2m12s ago), min age is set to 168h0m0s
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.635 [INF] CHDB: Not compacting database file at /root/.lnd/data/chain/bitcoin/mainnet/macaroons.db, it was last compacted at 2022-10-24 19:48:58.946153396 +0000 UTC (2m12s ago), min age is set to 168h0m0s
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.640 [INF] CHDB: Not compacting database file at /root/.lnd/data/graph/mainnet/sphinxreplay.db, it was last compacted at 2022-10-24 19:48:58.963879836 +0000 UTC (2m12s ago), min age is set to 168h0m0s
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.640 [INF] LTND: Creating local graph and channel state DB instances
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.659 [DBG] CHDB: Populating in-memory channel graph, this might take a while...
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.660 [DBG] CHDB: Finished populating in-memory channel graph (took 615.087µs, num_node_features=1, num_nodes=0, num_channels=0)
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.661 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.662 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.662 [INF] LTND: Database(s) now open (time_to_open=30.468145ms)!
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.663 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-10-24T20:51:11+01:00  2022-10-24 19:51:11.663 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
2022-10-24T20:51:19+01:00  2022-10-24 19:51:19.973 [INF] LNWL: Opened wallet
2022-10-24T20:51:20+01:00  2022-10-24 19:51:20.135 [INF] CHRE: Primary chain is set to: bitcoin
2022-10-24T20:51:20+01:00  2022-10-24 19:51:20.186 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 172.18.0.2:28332
2022-10-24T20:51:20+01:00  2022-10-24 19:51:20.186 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 172.18.0.2:28333
2022-10-24T20:51:20+01:00  2022-10-24 19:51:20.200 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2022-10-24T20:51:21+01:00  2022-10-24 19:51:21.850 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: the RPC server is in the process of starting up, but not yet ready to accept calls
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.846 [INF] LNWL: The wallet has been unlocked without a time limit
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.860 [INF] CHRE: LightningWallet opened
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.869 [DBG] LNWL: Birthday block has already been verified: height=758504, hash=00000000000000000003db8e9725525bf922831e1ffa60d6cd7fd7c331408392
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.869 [DBG] LNWL: Waiting for chain backend to sync to tip
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.906 [INF] SRVR: Onion services are accessible via Tor! NOTE: Traffic to clearnet services is not routed via Tor.
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.917 [INF] HSWC: Cleaning circuits from disk for closed channels
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.917 [DBG] HSWC: Found 0 closed channels
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.917 [INF] HSWC: Finished cleaning: no closed channels found, no actions taken.
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.917 [INF] HSWC: Restoring in-memory circuit state from disk
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.919 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.925 [DBG] CRTR: Instantiating mission control with config: Penalty Half Life: 1h0m0s, Apriori Hop Probablity: 0.6, Maximum History: 1000, Apriori Weight: 0.5, Minimum Failure Relax Interval: 1m0s
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.927 [DBG] CRTR: Mission control state reconstruction started
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.927 [DBG] CRTR: Mission control state reconstruction finished: n=0, time=54.851µs
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.927 [DBG] SRVR: Instantiating payment session source with config: AttemptCost=100 + 0.1%, MinRouteProbability=0.01
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [INF] LTND: Channel backup proxy channel notifier starting
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [INF] ATPL: Instantiating autopilot with active=false, max_channels=5, allocation=0.600000, min_chan_size=20000, max_chan_size=16777215, private=false, min_confs=1, conf_target=1
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [DBG] LTND: Populating dependencies for sub RPC server: SignRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [DBG] LTND: Populating dependencies for sub RPC server: WalletKitRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [DBG] LTND: Populating dependencies for sub RPC server: AutopilotRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [DBG] LTND: Populating dependencies for sub RPC server: ChainRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.932 [DBG] LTND: Populating dependencies for sub RPC server: InvoicesRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: PeersRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: NeutrinoKitRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: RouterRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: WatchtowerRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: WatchtowerClientRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] LTND: Populating dependencies for sub RPC server: DevRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: WatchtowerRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: WatchtowerClientRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: SignRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: WalletKitRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: RouterRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: AutopilotRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: ChainRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.933 [DBG] RPCS: Starting sub RPC server: InvoicesRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.934 [DBG] RPCS: Starting sub RPC server: VersionRPC
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.934 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-10-24T20:51:22+01:00  2022-10-24 19:51:22.939 [INF] LTND: Waiting for chain backend to finish sync, start_height=760138
2022-10-24T20:51:23+01:00  2022-10-24 19:51:23.887 [DBG] LNWL: Chain backend synced to tip!
2022-10-24T20:51:23+01:00  2022-10-24 19:51:23.920 [INF] LNWL: Started rescan from block 000000000000000000023332ae1f96085954c8a590078c07d9e5607593708b54 (height 760108) for 0 addresses
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.189 [INF] LNWL: Catching up block hashes to height 760138, this might take a while
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.193 [INF] LNWL: Done catching up block hashes
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.193 [INF] LNWL: Finished rescan for 0 addresses (synced to block 000000000000000000079e0a0cc1d4491c36ed86538faf2bef5f3d564ecc9832, height 760138)
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.434 [INF] LTND: Chain backend is fully synced (end_height=760138)!
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.434 [INF] NANN: HostAnnouncer starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.435 [WRN] HLCK: check: disk space configured with 0 attempts, skipping it
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.435 [WRN] HLCK: check: tls configured with 0 attempts, skipping it
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.435 [DBG] NANN: IP change detected! myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion: <nil> -> myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion:9735
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.435 [DBG] HLCK: Monitoring: chain backend
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.435 [INF] LNWL: SigPool starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.467 [INF] CHNF: ChannelNotifier starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.467 [INF] PRNF: PeerNotifier starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.468 [INF] HSWC: HtlcNotifier starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.469 [INF] SWPR: Sweeper starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.470 [INF] UTXN: UTXO nursery starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.471 [INF] NTFN: New block epoch subscription
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.477 [INF] BRAR: Breach arbiter starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.477 [DBG] BRAR: Found 0 closing channels, 0 retribution records
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.478 [INF] FNDG: Funding manager starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.478 [INF] HSWC: HTLC Switch starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.478 [INF] NTFN: New block epoch subscription
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.479 [INF] BRAR: Starting contract observer, watching for breaches.
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.490 [INF] NTFN: New block epoch subscription
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.491 [INF] CNCT: ChainArbitrator starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.492 [INF] DISC: Authenticated Gossiper starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.492 [INF] NTFN: New block epoch subscription
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.494 [INF] NTFN: New block epoch subscription
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.500 [INF] CRTR: Channel Router starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.501 [DBG] DISC: New block: height=760138, hash=000000000000000000079e0a0cc1d4491c36ed86538faf2bef5f3d564ecc9832
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.506 [INF] CRTR: FilteredChainView starting
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.533 [INF] CRTR: Filtering chain using 0 channels active
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.544 [INF] CRTR: Prune tip for Channel Graph: height=759843, hash=00000000000000000001a97505497277098746300af4809dded087d66697f8f1
2022-10-24T20:51:43+01:00  2022-10-24 19:51:43.550 [INF] CRTR: Syncing channel graph from height=759843 (hash=00000000000000000001a97505497277098746300af4809dded087d66697f8f1) to height=760138 (hash=000000000000000000079e0a0cc1d4491c36ed86538faf2bef5f3d564ecc9832)
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.172 [DBG] CHDB: Pruned graph, cache now has num_node_features=1, num_nodes=0, num_channels=0
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.172 [INF] CRTR: Graph pruning complete: 0 channels were closed since height 759843
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.175 [DBG] CRTR: Cleaning network result store.
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.177 [INF] INVC: InvoiceRegistry starting
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.177 [DBG] INVC: Adding 0 pending invoices to the expiry watcher
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.177 [INF] HSWC: Onion processor starting
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.178 [INF] NTFN: New block epoch subscription
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.187 [INF] NTFN: New block epoch subscription
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.187 [INF] NANN: Channel Status Manager starting
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.187 [INF] CHFT: ChannelEventStore starting
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.187 [INF] CHFT: Adding 0 channels to event store
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.187 [INF] CHBU: chanbackup.SubSwapper starting
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.214 [INF] CHBU: Updating backup file at /root/.lnd/data/chain/bitcoin/mainnet/channel.backup
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.221 [INF] CHBU: Swapping old multi backup file from /root/.lnd/data/chain/bitcoin/mainnet/temp-dont-use.backup to /root/.lnd/data/chain/bitcoin/mainnet/channel.backup
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.223 [DBG] CRTR: New graph topology client subscription, client 1
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.224 [DBG] SRVR: Establishing 0 persistent connections on start
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.224 [INF] SRVR: Initializing peer network bootstrappers!
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.224 [INF] SRVR: Creating DNS peer bootstrapper with seeds: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.224 [DBG] CHBU: SubSwapper's backupUpdater is active!
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.225 [INF] BTCN: Server listening on [::]:9735
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.225 [DBG] SRVR: Init bootstrap with targetPeers=3, bootstrappers=2, ignore=1
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.226 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:53:57+01:00  2022-10-24 19:53:57.228 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:54:09+01:00  2022-10-24 19:54:09.005 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:54:09+01:00  2022-10-24 19:54:09.006 [DBG] SRVR: Waiting 2s before trying to locate bootstrap peers (attempt #1)
2022-10-24T20:54:11+01:00  2022-10-24 19:54:11.008 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:54:21+01:00  2022-10-24 19:54:21.875 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:54:21+01:00  2022-10-24 19:54:21.876 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:54:21+01:00  2022-10-24 19:54:21.877 [DBG] SRVR: Waiting 4s before trying to locate bootstrap peers (attempt #2)
2022-10-24T20:54:25+01:00  2022-10-24 19:54:25.877 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:54:36+01:00  2022-10-24 19:54:36.836 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:54:36+01:00  2022-10-24 19:54:36.837 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:54:36+01:00  2022-10-24 19:54:36.837 [DBG] SRVR: Waiting 8s before trying to locate bootstrap peers (attempt #3)
2022-10-24T20:54:44+01:00  2022-10-24 19:54:44.837 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:55:06+01:00  2022-10-24 19:55:06.729 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:55:06+01:00  2022-10-24 19:55:06.732 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:55:06+01:00  2022-10-24 19:55:06.732 [DBG] SRVR: Waiting 16s before trying to locate bootstrap peers (attempt #4)
2022-10-24T20:55:22+01:00  2022-10-24 19:55:22.733 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:55:33+01:00  2022-10-24 19:55:33.660 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:55:33+01:00  2022-10-24 19:55:33.662 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:55:33+01:00  2022-10-24 19:55:33.662 [DBG] SRVR: Waiting 32s before trying to locate bootstrap peers (attempt #5)
2022-10-24T20:56:05+01:00  2022-10-24 19:56:05.662 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:56:16+01:00  2022-10-24 19:56:16.401 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:56:16+01:00  2022-10-24 19:56:16.402 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:56:16+01:00  2022-10-24 19:56:16.402 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #6)
2022-10-24T20:56:43+01:00  2022-10-24 19:56:43.437 [DBG] NANN: HostAnnouncer checking for any IP changes...
2022-10-24T20:56:43+01:00  2022-10-24 19:56:43.437 [DBG] NANN: No IP changes detected for hosts: [myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion]
2022-10-24T20:57:16+01:00  2022-10-24 19:57:16.403 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:57:16+01:00  2022-10-24 19:57:16.404 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:57:28+01:00  2022-10-24 19:57:28.001 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:57:28+01:00  2022-10-24 19:57:28.001 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #7)
2022-10-24T20:58:28+01:00  2022-10-24 19:58:28.002 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:58:40+01:00  2022-10-24 19:58:40.812 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:58:40+01:00  2022-10-24 19:58:40.813 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:58:40+01:00  2022-10-24 19:58:40.813 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #8)
2022-10-24T20:59:40+01:00  2022-10-24 19:59:40.814 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T20:59:51+01:00  2022-10-24 19:59:51.744 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T20:59:51+01:00  2022-10-24 19:59:51.746 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T20:59:51+01:00  2022-10-24 19:59:51.746 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #9)
2022-10-24T21:00:51+01:00  2022-10-24 20:00:51.746 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:01:03+01:00  2022-10-24 20:01:03.248 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:01:03+01:00  2022-10-24 20:01:03.249 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:01:03+01:00  2022-10-24 20:01:03.249 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #10)
2022-10-24T21:01:43+01:00  2022-10-24 20:01:43.436 [DBG] NANN: HostAnnouncer checking for any IP changes...
2022-10-24T21:01:43+01:00  2022-10-24 20:01:43.436 [DBG] NANN: No IP changes detected for hosts: [myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion]
2022-10-24T21:02:03+01:00  2022-10-24 20:02:03.250 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:02:03+01:00  2022-10-24 20:02:03.252 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:02:13+01:00  2022-10-24 20:02:13.621 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:02:13+01:00  2022-10-24 20:02:13.621 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #11)
2022-10-24T21:03:01+01:00  2022-10-24 20:03:01.700 [INF] CRTR: Pruning channel graph using block 000000000000000000037e7b4abd9f8f917fc050544ac2c2bc8723c21fa5e8ab (height=760139)
2022-10-24T21:03:01+01:00  2022-10-24 20:03:01.705 [DBG] CHDB: Pruned graph, cache now has num_node_features=1, num_nodes=0, num_channels=0
2022-10-24T21:03:01+01:00  2022-10-24 20:03:01.705 [INF] CRTR: Block 000000000000000000037e7b4abd9f8f917fc050544ac2c2bc8723c21fa5e8ab (height=760139) closed 0 channels
2022-10-24T21:03:02+01:00  2022-10-24 20:03:02.469 [DBG] NTFN: Filtering 2542 txns for 0 spend requests at height 760139
2022-10-24T21:03:02+01:00  2022-10-24 20:03:02.555 [INF] NTFN: New block: height=760139, sha=000000000000000000037e7b4abd9f8f917fc050544ac2c2bc8723c21fa5e8ab
2022-10-24T21:03:02+01:00  2022-10-24 20:03:02.555 [DBG] DISC: New block: height=760139, hash=000000000000000000037e7b4abd9f8f917fc050544ac2c2bc8723c21fa5e8ab
2022-10-24T21:03:02+01:00  2022-10-24 20:03:02.555 [DBG] SWPR: New block: height=760139, sha=000000000000000000037e7b4abd9f8f917fc050544ac2c2bc8723c21fa5e8ab
2022-10-24T21:03:02+01:00  2022-10-24 20:03:02.556 [INF] UTXN: Attempting to graduate height=760139: num_kids=0, num_babies=0
2022-10-24T21:03:13+01:00  2022-10-24 20:03:13.622 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:03:24+01:00  2022-10-24 20:03:24.148 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:03:24+01:00  2022-10-24 20:03:24.149 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:03:24+01:00  2022-10-24 20:03:24.149 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #12)
2022-10-24T21:04:24+01:00  2022-10-24 20:04:24.149 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:04:24+01:00  2022-10-24 20:04:24.151 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:04:37+01:00  2022-10-24 20:04:37.644 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:04:37+01:00  2022-10-24 20:04:37.645 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #13)
2022-10-24T21:05:37+01:00  2022-10-24 20:05:37.646 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:05:49+01:00  2022-10-24 20:05:49.765 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:05:49+01:00  2022-10-24 20:05:49.768 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:05:49+01:00  2022-10-24 20:05:49.768 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #14)
2022-10-24T21:06:43+01:00  2022-10-24 20:06:43.436 [DBG] NANN: HostAnnouncer checking for any IP changes...
2022-10-24T21:06:43+01:00  2022-10-24 20:06:43.436 [DBG] NANN: No IP changes detected for hosts: [myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion]
2022-10-24T21:06:49+01:00  2022-10-24 20:06:49.768 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:07:00+01:00  2022-10-24 20:07:00.551 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:07:00+01:00  2022-10-24 20:07:00.553 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:07:00+01:00  2022-10-24 20:07:00.554 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #15)
2022-10-24T21:08:00+01:00  2022-10-24 20:08:00.554 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:08:00+01:00  2022-10-24 20:08:00.555 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:08:11+01:00  2022-10-24 20:08:11.139 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:08:11+01:00  2022-10-24 20:08:11.139 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #16)
2022-10-24T21:09:11+01:00  2022-10-24 20:09:11.140 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:09:11+01:00  2022-10-24 20:09:11.141 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:09:21+01:00  2022-10-24 20:09:21.823 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:09:21+01:00  2022-10-24 20:09:21.823 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #17)
2022-10-24T21:10:21+01:00  2022-10-24 20:10:21.824 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:10:21+01:00  2022-10-24 20:10:21.826 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:10:32+01:00  2022-10-24 20:10:32.556 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:10:32+01:00  2022-10-24 20:10:32.556 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #18)
2022-10-24T21:11:32+01:00  2022-10-24 20:11:32.557 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:11:32+01:00  2022-10-24 20:11:32.558 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:11:43+01:00  2022-10-24 20:11:43.120 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:11:43+01:00  2022-10-24 20:11:43.120 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #19)
2022-10-24T21:11:43+01:00  2022-10-24 20:11:43.436 [DBG] NANN: HostAnnouncer checking for any IP changes...
2022-10-24T21:11:43+01:00  2022-10-24 20:11:43.436 [DBG] NANN: No IP changes detected for hosts: [myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion]
2022-10-24T21:11:43+01:00  2022-10-24 20:11:43.501 [DBG] DISC: No eligible active syncer to rotate
2022-10-24T21:12:43+01:00  2022-10-24 20:12:43.121 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:12:53+01:00  2022-10-24 20:12:53.529 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:12:53+01:00  2022-10-24 20:12:53.531 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:12:53+01:00  2022-10-24 20:12:53.531 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #20)
2022-10-24T21:13:53+01:00  2022-10-24 20:13:53.532 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:13:53+01:00  2022-10-24 20:13:53.534 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:14:03+01:00  2022-10-24 20:14:03.854 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:14:03+01:00  2022-10-24 20:14:03.854 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #21)
2022-10-24T21:15:03+01:00  2022-10-24 20:15:03.855 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:15:03+01:00  2022-10-24 20:15:03.857 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:15:14+01:00  2022-10-24 20:15:14.399 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:15:14+01:00  2022-10-24 20:15:14.399 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #22)
2022-10-24T21:16:14+01:00  2022-10-24 20:16:14.400 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:16:14+01:00  2022-10-24 20:16:14.402 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:16:27+01:00  2022-10-24 20:16:27.021 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T21:16:27+01:00  2022-10-24 20:16:27.021 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #23)
2022-10-24T21:16:43+01:00  2022-10-24 20:16:43.437 [DBG] NANN: HostAnnouncer checking for any IP changes...
2022-10-24T21:16:43+01:00  2022-10-24 20:16:43.438 [DBG] NANN: No IP changes detected for hosts: [myreallylongv3onionhostnameimeanitsreallylongevenlongerthand.onion]
2022-10-24T21:17:27+01:00  2022-10-24 20:17:27.022 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T21:17:27+01:00  2022-10-24 20:17:27.023 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T21:17:37+01:00  2022-10-24 20:17:37.853 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2022-10-24T18:51:27-04:00  2022-10-24 22:51:27.703 [INF] SRVR: Initializing peer network bootstrappers!
2022-10-24T18:51:27-04:00  2022-10-24 22:51:27.703 [INF] SRVR: Creating DNS peer bootstrapper with seeds: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T18:51:27-04:00  2022-10-24 22:51:27.704 [DBG] SRVR: Init bootstrap with targetPeers=3, bootstrappers=2, ignore=1
2022-10-24T18:51:27-04:00  2022-10-24 22:51:27.704 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T18:51:27-04:00  2022-10-24 22:51:27.704 [TRC] DISC: Querying for 3 addresses
2022-10-24T18:51:32-04:00  2022-10-24 22:51:32.710 [TRC] DISC: Unable to lookup SRV records via primary seed (nodes.lightning.directory): dial tcp: lookup soa.nodes.lightning.directory: Try again
2022-10-24T18:51:32-04:00  2022-10-24 22:51:32.710 [TRC] DISC: Falling back to secondary
2022-10-24T18:51:32-04:00  2022-10-24 22:51:32.712 [TRC] DISC: Attempting to query fallback DNS seed
2022-10-24T18:51:33-04:00  2022-10-24 22:51:33.287 [TRC] DISC: Unable to query fall back dns seed (soa.nodes.lightning.directory): tor host is unreachable
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [TRC] DISC: Unable to lookup SRV records via primary seed (lseed.bitcoinstats.com): dial tcp: lookup soa.nodes.lightning.directory: Try again
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [TRC] DISC: Falling back to secondary
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [TRC] DISC: DNS seed lseed.bitcoinstats.com has no secondary, skipping fallback
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [TRC] DISC: Querying for 3 addresses
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.291 [TRC] DISC: Ignored node 03f3d9a3796d498b59a13aba7bea6cc6dc7183c0f97aa74688083fa427c12b47ed for bootstrapping
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.293 [TRC] DISC: Ending hash accumulator state: 78e69e9ef6331e501c785ddfa722b5c5f28154b5d36ab159adea92a9ff20cdf3
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.293 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2022-10-24T18:51:38-04:00  2022-10-24 22:51:38.293 [DBG] SRVR: Waiting 2s before trying to locate bootstrap peers (attempt #1)
2022-10-24T18:51:40-04:00  2022-10-24 22:51:40.293 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2022-10-24T18:51:40-04:00  2022-10-24 22:51:40.293 [TRC] DISC: Querying for 3 addresses

It looks like container has access to internet but LND is using tor and it may not be well configured. I would try to hit an onion address from the container (not LND but manually) to check that the services is well configured, up and running.

@kn0wmad any updates on this?

We've been doing a lot of testing trying to understand the problem better.  Will hopefully have some kind of update today

@kn0wmad any updates on this?

Hitting onions is no problem, and the node is able to sync to graph when adding peers manually.  We don't see any reason that the bootstrap peers would be unable to connect - they are fully reachable by the network.  Can you provide any further insight?

So it appears that some of our people's nodes are failing to get the srv records from their own router or isp, for some reason.  I noticed this:
https://github.com/lightningnetwork/lnd/commit/5b226a9d37b3a9d0b2f874f40d50d4c575ff0e55
Is the logic here still valid?  Use a tcp srv dns request if it's detected your request will be large?
Is this a problem?  soa.nodes.lightning.directory and nodes.lightning.directory seem to return nothing:
user@desktop:~$ dig nodes.lightning.directory

; <<>> DiG 9.16.1-Ubuntu <<>> nodes.lightning.directory
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21764
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;nodes.lightning.directory.	IN	A

;; Query time: 528 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Oct 30 14:24:02 MST 2022
;; MSG SIZE  rcvd: 54

user@desktop:~$ dig soa.nodes.lightning.directory

; <<>> DiG 9.16.1-Ubuntu <<>> soa.nodes.lightning.directory
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 16548
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;soa.nodes.lightning.directory.	IN	A

;; Query time: 524 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Oct 30 14:24:05 MST 2022
;; MSG SIZE  rcvd: 58

Is this true?  https://github.com/lightning/bolts/blob/master/10-dns-bootstrap.md
It doesn't seem to be: I ask for 2 records and get 5+:
user@desktop:~$ dig r0.a2.n2.lseed.bitcoinstats.com SRV @1.1.1.1

; <<>> DiG 9.16.1-Ubuntu <<>> r0.a2.n2.lseed.bitcoinstats.com SRV @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8481
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;r0.a2.n2.lseed.bitcoinstats.com. IN	SRV

;; ANSWER SECTION:
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	SRV	10 10 9735 ln1q2tmn209te9d44nqn9sjklgzylhc0v5g4jtv20um89ysymfx7cg57jzugvt.lseed.bitcoinstats.com.
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	SRV	10 10 9735 ln1qfeu6huadu65kzaxg0vcxsjzg7989lgkkxumgwfzyqyewn5e5rrtwhg6clr.lseed.bitcoinstats.com.
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	SRV	10 10 9735 ln1qg9pmagtwqfnrg5hsgynyyzxpvgwac9vtmm2qxuu280lnw8ama0mq089s96.lseed.bitcoinstats.com.
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	SRV	10 10 9735 ln1qvnlwc7gfxlayxy3peq7aa60tfehnzf432e4vhcctcdxrwma73zmsmvwzk2.lseed.bitcoinstats.com.
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	SRV	10 10 9735 ln1qgpf5h4gjzh6r252yqdwvmat4249p0zhxkau3q3em8c96fq6x2xfj5g89lu.lseed.bitcoinstats.com.

;; Query time: 268 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Oct 30 14:31:00 MST 2022
;; MSG SIZE  rcvd: 585

user@desktop:~$ dig r0.a2.n2.lseed.bitcoinstats.com

; <<>> DiG 9.16.1-Ubuntu <<>> r0.a2.n2.lseed.bitcoinstats.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58573
;; flags: qr rd ra; QUERY: 1, ANSWER: 26, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;r0.a2.n2.lseed.bitcoinstats.com. IN	A

;; ANSWER SECTION:
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	172.81.181.12
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	3.227.242.191
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	153.126.136.98
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	23.29.35.242
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	98.207.97.156
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	116.203.143.6
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	84.26.119.35
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	89.161.26.78
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	97.81.213.61
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	80.1.182.141
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	34.65.85.39
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	5.70.59.39
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	94.10.178.130
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	144.76.234.246
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	172.81.177.39
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	69.251.113.136
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	178.189.229.27
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	176.9.63.240
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	178.85.255.85
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	170.75.170.45
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	18.234.160.51
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	116.203.4.18
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	34.199.21.59
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	167.179.139.79
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	92.29.101.57
r0.a2.n2.lseed.bitcoinstats.com. 60 IN	A	3.239.149.3

;; Query time: 140 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Oct 30 14:31:23 MST 2022
;; MSG SIZE  rcvd: 476

I can confirm I also don't get any real responses from nodes.lightning.directory. Might be an issue with that DNS service itself. I'm not sure who's running it, let me dig deeper.
I wasn't aware of the nXX part in the protocol but it sounds to me like that was just never implemented. For example the LSEED instance we're running seems to ignore it: https://github.com/lightninglabs/lseed/blob/master/seed/dns.go#L300

There seem to be multiple interacting problems here.

nodes.lightning.directory does not exist at all, on any dns server i can find. This seems like a centralization issue, given that it represents 2 out of 3 seed node directories. The lseed.bitcoinstats.com directory is the only domain out of the three that appears to exist.

The A records do not seem to be getting used... can anyone point me to how the A records are utilized in BOLT-10? A brief scan of the doc does not indicate how the pubkey would be found from the A record, so I'm uncertain how to test this primary functionality.

In the absence of working A records, SRV records (used to list nodes that are listening on non-standard ports) are used as a fallback. These also appear to be failing somehow. After some brief experiments with looking up nodes by bech32-decoding their subdomains into pubkeys, it appears that the nodes I tried have all been very low-quality, old nodes with maybe like 1 channel, and which refuse to connect when I invoke lncli connect. How do nodes end up in these SRV records?

When running the official docker image, I managed to recreate this behavior for a few minutes when spinning up a fresh neutrino node; ie docker run --rm --name lnd-mainnet lightninglabs/lnd:v0.15.2-beta --bitcoin.active --bitcoin.mainnet --bitcoin.node=neutrino --feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json --debuglevel=trace. For a while on first launch, DNS seeds could not be found:

2022-10-31 17:42:05.765 [TRC] DISC: Attempting to convert: ln1qwsgt5rj5vgtuearfawsl8ff8hztz9zrqng5qjvqrg6mvpsnwxru50g23jg.lseed.bitcoinstats.com.
2022-10-31 17:42:05.765 [TRC] DISC: Obtained 03a085d072a310be67a34f5d0f9d293dc4b1144304d14049801a35b606137187ca@194.187.224.132:4009 as valid reachable node
2022-10-31 17:42:05.929 [TRC] DISC: Attempting to convert: ln1qwgeaa7s2zrhx955779kumayw5rccq5kc2drf6t4fg05sajx9lf3vvu9eld.lseed.bitcoinstats.com.
2022-10-31 17:42:05.930 [TRC] DISC: Obtained 03919ef7d05087731694f78b6e6fa475078c0296c29a34e9754a1f4876462fd316@212.129.23.197:4022 as valid reachable node
2022-10-31 17:42:06.086 [TRC] DISC: Attempting to convert: ln1qtyxc66r7tmj6z5qs7fc4phat0mqzp6tgu3g4ldmrc4txhm2hlhwyjnmplh.lseed.bitcoinstats.com.
2022-10-31 17:42:06.086 [TRC] DISC: Obtained 02c86c6b43f2f72d0a8087938a86fd5bf601074b47228afdbb1e2ab35f6abfeee2@54.80.237.139:9735 as valid reachable node
2022-10-31 17:42:06.086 [INF] DISC: Obtained 3 addrs to bootstrap network with
2022-10-31 17:42:06.227 [ERR] SRVR: Unable to connect to 03a085d072a310be67a34f5d0f9d293dc4b1144304d14049801a35b606137187ca@194.187.224.132:4009: dial tcp 194.187.224.132:4009: connect: connection refused
2022-10-31 17:42:06.227 [ERR] SRVR: Unable to connect to 03a085d072a310be67a34f5d0f9d293dc4b1144304d14049801a35b606137187ca@194.187.224.132:4009: dial tcp 194.187.224.132:4009: connect: connection refused
2022-10-31 17:42:09.087 [TRC] SRVR: Skipping peer 03919ef7d05087731694f78b6e6fa475078c0296c29a34e9754a1f4876462fd316@212.129.23.197:4022 due to not establishing a connection within 3 seconds
2022-10-31 17:42:09.087 [TRC] SRVR: Skipping peer 02c86c6b43f2f72d0a8087938a86fd5bf601074b47228afdbb1e2ab35f6abfeee2@54.80.237.139:9735 due to not establishing a connection within 3 seconds
2022-10-31 17:42:09.087 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #7)
2022-10-31 17:42:10.043 [ERR] SRVR: Unable to connect to 027d7f94667974b10d3e8330de403111229669273dc9024745d195ba035d746e57@209.6.39.175:9735: dial tcp 209.6.39.175:9735: i/o timeout
2022-10-31 17:42:10.043 [ERR] SRVR: Unable to connect to 02da8d5a759ee9e4438da617cfdb61c87f723fb76c4b6371b877d0347abe953a4f@62.195.75.40:9735: dial tcp 62.195.75.40:9735: i/o timeout
2022-10-31 17:42:10.043 [ERR] SRVR: Unable to connect to 027cbd8e3bdaa6409e6422c8b839322f370e977247d8c2fc4f130ec886213fc3b2@34.136.104.148:9735: dial tcp 34.136.104.148:9735: i/o timeout

This again, is simply running the official LND docker image from my Ubuntu laptop. The problem seemed to resolve itself after a few minutes, but this is definitely related to what we're seeing on embassy-os.

nslookup lseed.bitcoinstats.com and nslookup -type=SRV lseed.bitcoinstats.com yields results on all affected machines. The way we do these lookups may be taking slightly longer on embassy-os than in a vanilla docker install, but there seems to be a difference between what nslookup and what LND itself are doing.

I think maybe the primary issue here is a lack of high-quality nodes in the seed data, and also potentially an issue utilizing the data from the A records, though it's possible I'm missing something there. In any case this definitely seems like an issue with LND, and not anything we're doing on our side, except for maybe sometimes taking a bit longer to deliver DNS responses and being somewhat more difficult to connect to given that our nodes listen exclusively via Tor.
Please let me know if you have any other ideas for how to get to the bottom of this, this is affecting all our fresh LND nodes.

nodes.lightning.directory does not exist at all, on any dns server i can find.

Yeah, that was a problem with the LSEED installation. It's fixed now and I get results for both A and SRV records.

it appears that the nodes I tried have all been very low-quality

Because of the first DNS (nodes.lightning.directory, run by LL) failing, lnd used the second DNS (lseed.bitcoinstats.com run by @cdecker IIRC). So I can't speak to the quality of the nodes returned there. Maybe that service needs to be restarted as well to refresh its list of nodes?

This seems like a centralization issue,

I agree. It would be good for more people to run their own instance of LSEED. You can configure custom LSEED servers by setting --bitcoin.dnsseed=. Maybe that's something you want to consider for embassy-os?
I can't really speak to the other points, but hope this helps to resolve your issue for now.

About the quality of the bitcoinstats.com results, I'll look into it. But ideally you'd use SRV requests to get addresses for specific nodes.

Seems like with the 15.4 update, we uncovered another, related issue... maybe?
2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.782 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.805 [INF] INVC: New invoice subscription client: id=1
2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.826 [INF] LTND: Waiting for chain backend to finish sync, start_height=761293
2022-11-01T13:24:40-04:00  2022-11-01 17:24:40.634 [INF] LNWL: Started rescan from block 0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f (height 761248) for 7 addresses
2022-11-01T13:24:41-04:00  2022-11-01 17:24:41.083 [ERR] LNWL: Unable to complete chain rescan: -1: allocation of oversized vector: requested 12000072, maximum 4000000
2022-11-01T13:24:44-04:00  2022-11-01 17:24:44.719 [INF] INVC: New invoice subscription client: id=2

Taking a look at that error, thanks.

Re the SOA thing: that's a hack we use to allow Tor clients (which can't do SOCKS DNS resolution over UDP) to hit the DNS server directly over TCP (still via Tor) to allow them to fetch the SRV records (which can't be fetched using normal SOCKS resolution either).

@islandbitcoin sounds like you're using Electrs somehow? https://github.com/romanz/electrs/issues/351

@islandbitcoin sounds like you're using Electrs somehow? romanz/electrs#351

no, using bitcoind mainnet. Electrs not installed

Re the SOA thing: that's a hack we use to allow Tor clients (which can't do SOCKS DNS resolution over UDP) to hit the DNS server directly over TCP (still via Tor) to allow them to fetch the SRV records (which can't be fetched using normal SOCKS resolution either).

Ahh, good to know! So if we're connecting via Tor and soa.nodes.lightning.directory goes down, then that should reliably produce this behavior?

@islandbitcoin what version of bitcoind?

bash-5.1# bitcoind --version
Bitcoin Core version v23.0.0

@islandbitcoin so something is very very weird here. Looking at the error message: -1: allocation of oversized vector: requested 12000072, maximum 4000000
The first part (-1) looks like an error code from the RPC. Meaning, the message is coming from the chain backend. Also, the error string allocation of oversized vector cannot be found in any of our repos that are involved (lnd, btcwallet, btcd). The only occurrence I found through Google was in Electrs. So is it possible that in your setup somehow there's an Electrs server (or some component that uses the same library) between your lnd and your bitcoind node?

it works fine when I use bitcoind directly, and works fine when I use Neutrino

@guggero thanks so much for fixing nodes.lightning.directory, will get back soon as to whether that fixed our issues.
Re: running our own LSEED implementation, not sure if that's something we want to take on right now but we'll consider it.

About the quality of the bitcoinstats.com results, I'll look into it. But ideally you'd use SRV requests to get addresses for specific nodes.

@cdecker What are the A records used for then? They don't seem to contain pubkeys?

@guggero thanks so much for fixing nodes.lightning.directory, will get back soon as to whether that fixed our issues.
Re: running our own LSEED implementation, not sure if that's something we want to take on right now but we'll consider it.

Oh, I didn't fix the LSEED, I only relayed the message :sweat_smile:  But I'm hopeful this will fix your issue.

@guggero haha well, whatever you did, nslookup nodes.lightning.directory returns results successfully now, and our nodes are no longer having problems syncing the graph :)

Closing ticket, lightning.directory lseeds being up has solved this issue.

Thanks for the assistance everyone

authors: Roasbeef cdecker chrisguida gStart9 guggero islandbitcoin kn0wmad positiveblue


text:
In ammonite released for Scala 2.13 macro annotations doesn't work

For cases that I tested I was unable to make macro annotations expand in Ammonite, despite enabling -YmacroAnnotations flag. These cases works if I compile them normally. Example:
@ interp.configureCompiler(_.settings.YmacroAnnotations.value = true)

@ import $ivy.`io.scalaland::catnip:1.0.0`, io.scalaland.catnip._, cats._, cats.implicits._, alleycats.std.all._
import $ivy.$                           , io.scalaland.catnip._, cats._, cats.implicits._, alleycats.std.all._

@ @Semi(Show) case class Test(a: String, b: Int, c: Double)
cmd2.sc:1: enable macro paradise to expand macro annotations
@Semi(Show) case class Test(a: String, b: Int, c: Double)
                       ^
Compilation Failed

In earlier version of Ammonite (which used 2.12) running this code with macro paradise plugin (interp.load.plugin.ivy("org.scalamacros" % "paradise_2.12.4" % "2.1.0")) worked.
I understand if this is low priority issue and will be a won't fix, though I would like to at least have it documented here as an issue, since I haven't found any information about it anywhere.

That could originate from the custom analyzer that Ammonite sets up. scalac uses a different analyzer when -Ymacro-annotation is passed. Ammonite should probably do the same.

I confirm that fixes it.

source: gharchive/issue

authors: MateuszKubuszok alexarchambault

repo: lihaoyi/Ammonite

license: MIT

license_type: permissive

license_source: github-api


text:
dotty 0.26.0-RC1, mill 0.8.0: cannot find main when using main functions

I found that with this dotty release, the main class was not automatically found whereas in 0.7.3 and previous version of dotty it was found. I had to add def mainClass = Option("mymain.run") to the build file under the above versions.

Can you provide a small example to reproduce?

Works for me.
$ mill all version example1.run
[1/37] version
0.8.0
[27/37] example1.compile
[info] Compiling 1 Scala source to /tmp/mill-957/out/example1/compile/dest/classes ...
[info] Done compiling.
[37/37] example1.run
example1

This is my dir layout:
$ tree .
.
├── build.sc
└── example1
    └── src
        └── example1.scala

Do you have more than one main defined?

Not in the example1 project. Having said that, I wonder if the out dir was not cleared as I had potentially did at one point have another main defined that was compiled.
If there was more than one main would it report that it could not find a main vs reporting there is more than one main?

It would say something like: "Multiple main classes found [...] please explicitly specify which one to use by overriding mainClass"

Closing this one. If you have any idea want went wrong and the issue re-appears, feel free to comment / re-open this ticket.

authors: aappddeevv lefou

repo: lihaoyi/mill


text:
Error: No file system is available - whilst using browser based github.dev

Hi,
As per title I see the following error (many times) when using github.dev on a custom repo.
language-server-worker.js:163 Uncaught (in promise) Error: No file system is available.
    at Lx.readFile (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:7305)
    at ap.update (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:154:6073)
    at https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:13886
    at _p.runCancelable (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:14823)
    at async _p.buildDocuments (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:13816)
    at async _p.update (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:13114)
    at async https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:18895
    at async Promise.all (index 0)
    at async Np.performNextOperation (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.17.1/extension/dist/browser/language-server-worker.js:163:18810)

followed by:
Attempted reference resolution before document reached ComputedScopes state (vscode-vfs://github%2B7b2276223a312c22726566223a7b2274797065223a342c226964223a2265636f6d227d7d/wp-access-for-ecomm-pilot/mdl/src/projects/simplification/identity/identity.c4).
createLinkingError @ language-server-worker.js:154
getCandidate @ language-server-worker.js:154
getLinkedNode @ language-server-worker.js:154
get ref @ language-server-worker.js:154
(anonymous) @ language-server-worker.js:193
(anonymous) @ language-server-worker.js:193
iterator @ language-server-worker.js:40
find @ language-server-worker.js:40
getElement @ language-server-worker.js:154
getCandidate @ language-server-worker.js:154
doLink @ language-server-worker.js:154
(anonymous) @ language-server-worker.js:154
forEach @ language-server-worker.js:40
link @ language-server-worker.js:154
await in link
(anonymous) @ language-server-worker.js:163
runCancelable @ language-server-worker.js:163
await in runCancelable
buildDocuments @ language-server-worker.js:163

I tried with vscode.dev and got similar behaviour but some extra error messages:
language-server-worker.js:175 lsp:debug [ModelBuilder] No documents to build model from
console.ts:137 [Extension Host] debug [LikeC4Model.fetchComputedModel] 424ms
log.ts:445   ERR [Extension Host] %cerror
      background: #c0392b;
      border-radius: 0.5em;
      color: white;
      font-weight: bold;
      padding: 2px 0.5em;
     SyntaxError: Failed to execute 'measure' on 'Performance': The mark 'fetchComputedModel:start' does not exist.
	at Vy.fetchModelAndUpdateCaches (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1635:3979)
	at async Vy.fetchComputedModel (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1635:3805)
	at async Object.eval [as handler] (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1652:1498)
	at async lN.processRequestMessage (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:65:26354)
	at async lN.processMessage (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:65:24310)
console.ts:137 [Extension Host] error SyntaxError: Failed to execute 'measure' on 'Performance': The mark 'fetchComputedModel:start' does not exist.
	at Vy.fetchModelAndUpdateCaches (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1635:3979)
	at async Vy.fetchComputedModel (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1635:3805)
	at async Object.eval [as handler] (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:1652:1498)
	at async lN.processRequestMessage (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:65:26354)
	at async lN.processMessage (https://likec4.vscode-unpkg.net/likec4/likec4-vscode/1.18.0/extension/dist/browser/extension.js#vscode-extension:65:24310)
YJi @ console.ts:137


text:
Automatically update Instagram access token and store in repo secrets

Update the Instagram access token every 53 days, a week before the token expires, and store the updated token and expiry date in the repo secrets.

Just realised that I need to update the same token on all repos at the same time as the refresh expires the old token.

source: gharchive/pull-request

repo: lildude/recent-instagram-to-jekyll


text:
テッセレーションの判定でスケールが考慮されていないため、モデルのスケールが大きいと細分化されない

関連 - https://twitter.com/wataameya_vr/status/1686287454121398273

e2881b704395b67140289c8be87b79d71e30426d で修正

repo: lilxyzw/lilToon


text:
Fix #226: Exception in Mobile API due to old version of Guava library

Libraries springfox-swagger2 and spring-ws-security depend on old version of Guava which was causing problems during validation of Mobile API requests. Guava is excluded for these two libraries.

I have proposed an alternative fix, with blackjack... and hookers... and no dependency exclusions... https://github.com/lime-company/powerauth-webflow/pull/230

It looks cleaner, let's use your fix.

authors: petrdvorak romanstrobl

repo: lime-company/powerauth-webflow

license_source: bigquery


text:
Feature request: Pipeline documentation

We need to have clear conceptual documentation of the pipeline. Multiple operations are conceptually confusing because they involve operations along multiple axes. To avoid errors and confusion, we need these to be documented.

Sounds good @scott-huberty, but in the interest of clarity, I think we are talking about two overlapping but different things. I think that what you have in mind is closer to code documentation (proper docstrings and such; and using these docstrings through Sphinx to generate API doc)? What I plan to address here is more of a "conceptual" documentation than a "code" documentation. In the end, Sphinx will certainly be able to digest and integrate this in some ways, but more specifically, the kind of doc I plan to prepare is:
1 - Overall diagram of the pipeline, with distinct naming and numbering of steps;
2 - Break down of each steps with, if useful, visual explanation.
I think that will help, among other thing, solving issues like #18

OK I see - and yes I think this is a good idea, happy to help once you've started a doc that can be shared.

First step would look something like that:

Second step would look something like this...

2 done, ~10 to go... ! ;)

Those look great!
What are you using to generate these graphs?

Inkscape! Two key open source imaging softwares: gimp (eq. to photoshops) for bitmaps, inkscape for vectorials (eq. to illustrator).

Developed in the "xarray" branch.

2.a Computing standard deviation across epochs.

2.b Z^_i is defined as Z^i(X) = \frac{X - Q{50,i}(X)}{Q_{70,i}(x) - Q_{30,i}(x)}

with Q_{j,i}(X) standing for the j-th percentile of X computed along the dimension i. At this step, this operation is broacasted, such that it does not results in a collapsing of the dimension channel even though the statistics are computed along this dimensions. These values are akin to a non-parametric z-score indicating how much a channel has a large variability (across epochs) compared to the other channels, at a given time point. Note that the use of both the time and epoch dimensions makes sense for event-related epochs, not so much for epochs of resting-state data.

2.c. Averaging the previously computed z-scores across time.
2.d Flagging bad channels as those with such z-scores  larger than the median plus 6 times the difference between the 70th and the 30th percentile.

I am somehow unclear that even such documentation helps make this operation more digestible.

I love thé graphic

When calculating variability across epochs, A channel's voltage value at a given sample (I.e sample 10) is compared across epochs?

Thanks.

If by "sample 10" you mean the tenth sample along the time dimension, then yes. Think of xarrays... with an xarray X with dimensions (channel, epoch, time), this is equivalent to X.std("epoch")

Yeah exactly. I should have said something like "the 10th index of the time dimension" across epochs.
Well, I think this documentation does help to convey the operation.

Yeah, I guess. This one is an intricate measure so I guess it would be hard to make it more transparent.

@christian-oreilly we could adapt thus code to plot a cube, label the axes (x=time,y=epoch, z=channel), and format one row of voxels (across epochs axis) to be a different color (red) than the rest of the cube (gray?), to help convey the concept of comparing the same channel and time index across epochs?
https://matplotlib.org/devdocs/gallery/mplot3d/voxels_numpy_logo.html

Yeah... I don't want to spend forever working on these diagrams though. It seems to me that coding these instead of just drawing them will not make this process faster (on the contrary). I think, personally, I prefer to work on these manually in Inkscape. I can revisit this one down the line to add the coloring you propose, but I'd first finish representing the other steps of the pipeline. Also, the coloring, for now, has been used to indicate flagged values, so it would need to made in a way that does not confuse these two things.

Numbers of channels as per the config.
Formula for outlier rejection as per the config.

Looks great.
It's been since my masters since I used Inkscape but I think I'll download it again. In the spirit of open source, would you be able  to share these Inkscape files with me 🙂

It is a good too to be comfortable using for figures in paper and stuff like that. I create SVG files, which is a very standard format.
Rank and bridge steps will be very easy to sketch (I have them on paper). A bit too lazy to do them tonight, but it should be done shortly. There would just be the gap removal and the large IC step remaining. I don't think ICA are worth depicting... it is as per the ICA algorithm... but I'll see. Anyway, short story, this is almost done. I'll glue them together with markdown text to have a nice complete explanation of the pipeline.

Finale set of schemas.

All schemas are now on the xarray branch. A pipeline.md display them all. The last steps is to add some text to pipeline.md to explain it all.

Great. Once you are ready to merge these schemas into the main branch, I can look into incorporating them to the sphinx documentation.

Any objection on closing this issue? Improving the documentation and filling all the TODOs will be an ongoing task, but I think this issue has been sufficiently addressed to close it instead of keeping it as an issue that we will go stale as the documentation will always be perfectible.

Close it!

authors: christian-oreilly scott-huberty

repo: lina-usc/pylossless


text:
Sphinx Server

Is it possible to provide a guide on how to install and configure the "Sphinx Server" with Carbon Forum?

install and copy sphinx.conf to you sphinx installation path.
@virteman

http://www.sphinx-doc.org/en/stable/install.html

I can help

	sql_user		= sphinx_u 	sql_pass		= search_perfect 	sql_db			= knowledge
Here I put db data from the forum?

right.

I followed this:
Install:
apt-get install sphinxsearch
Config: I upload the config with the db data from my carbon forum.
After, adding data to the Index
indexer --all
Start the daemon first I change the line:
nano /etc/default/sphinxsearch
START=yes
And after:
service sphinxsearch start
Test:
`# search test
Sphinx 2.0.4-id64-release (r3135)
Copyright (c) 2001-2012, Andrew Aksyonoff
Copyright (c) 2008-2012, Sphinx Technologies Inc (http://sphinxsearch.com)
using config file '/etc/sphinxsearch/sphinx.conf'...
index 'PostsIndexes': query 'test ': returned 10 matches of 10 total in 0.000 sec
displaying matches:

document=17, weight=2475, topicid=2, istopic=1, posttime=Wed May 11 03:34:33 2016
ID=17
TopicID=2
IsTopic=1
UserID=1
UserName=akira
Subject=Test
Content=test
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462952073
IsDel=0
document=2, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:15:16 2016
ID=2
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=@aiondesu test
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462950916
IsDel=0
document=3, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:15:51 2016
ID=3
TopicID=1
IsTopic=0
UserID=2
UserName=aiondesu
Subject=Desu Desu
Content=@akira test 2
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462950951
IsDel=0
document=4, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:16:43 2016
ID=4
TopicID=1
IsTopic=0
UserID=2
UserName=aiondesu
Subject=Desu Desu
Content=Reply to #1 @akira :D: test 3
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951003
IsDel=0
document=9, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:18:59 2016
ID=9
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=Test 5
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951139
IsDel=0
document=10, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:19:11 2016
ID=10
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=test 3123123
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951151
IsDel=0
document=13, weight=1482, topicid=1, istopic=0, posttime=Wed May 11 03:19:31 2016
ID=13
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=#1 test
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951171
IsDel=0
document=7, weight=1475, topicid=1, istopic=0, posttime=Wed May 11 03:18:48 2016
ID=7
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=Test test
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951128
IsDel=0
document=12, weight=1475, topicid=1, istopic=0, posttime=Wed May 11 03:19:25 2016
ID=12
TopicID=1
IsTopic=0
UserID=2
UserName=aiondesu
Subject=Desu Desu
Content=TEST TEST DESY TESTO DESU
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951165
IsDel=0
document=16, weight=1472, topicid=1, istopic=0, posttime=Wed May 11 03:21:55 2016
ID=16
TopicID=1
IsTopic=0
UserID=1
UserName=akira
Subject=Desu Desu
Content=Test#6 @akira :Test test
PostIP=xxxxxxxxxxxxxxxx
PostTime=1462951315
IsDel=0

words:

'test': 10 documents, 15 hits

`
Works fine, now I edit config.php:
 //Sphinx Server define('SearchServer', 'localhost'); define('SearchPort', '9312');
And don't work :(
http://i.imgur.com/bfCBqkN.png

Well, I edit the SearchClient.class.php and I add this:
require_once('sphinxapi.php');
And this works fine, http://i.imgur.com/OrR05vX.png
Now I have a problem, this dont show me the posts here: http://i.imgur.com/aH63PyF.png
It should be like thist: http://i.imgur.com/cQE6pmW.png

You need dictionary.
https://www.94cb.com/upload/file/20141109/1415523029263289.gz
↑↑↑SQL file of dictionary.

How works this?

Extract and execute it in MySQL.

So I need to fill the dictionary with keywords?

Yes, and the tag you created will be used as a dictionary.

@lincanbin Is there any way to automate this?

Currently not.

Oh well, thanks so much for the help, I cant wait for the 6.0 update.

It is too complex, I want it but too difficult to do it.

authors: alwaysontop617 hoogw lincanbin robotrono

repo: lincanbin/Carbon-Forum


text:
License?

Hello Author,
I would like to know what the license is.
Thanks in advance.

just added, thank you

Thank you 😄

repo: lincolnhard/openpose-darknet


text:
add prediction model to Solution to enable predict on it

This essentially stores the prediction model in the fit solution as well. This will make my life a lot easier in KSVM.jl to predict things. Otherwise I'd have to break the compatibility of KSVM and Regression.jl
It essentially allows the last line of this code
d = 3      # sample dimension
n = 1000   # number of samples

# prepare data
w = randn(d+1)    # generate the weight vector
X = randn(d, n)   # generate input features
y = sign(X'w[1:d] + w[d+1] + 0.2 * randn(n))  # generate (noisy) response

# perform estimation
ret = Regression.solve(
    logisticreg(X, y; bias=1.0),   # construct a logistic regression problem
    reg=SqrL2Reg(1.0e-2),          # apply squared L2 regularization
    options=Options(verbosity=:iter, grtol=1.0e-6 * n))  # set options

yhat = sign(predict(ret, X))

I will review over the weekend

I may have come up with a cleaner solution that doesn't affect Regression.jl at all. Let me get back to you on that

yes, I found a better solution by boxing the Solution into an SvmFit which allows for a nice clean user interface in the style of:
res = svm(X, y)
predict(res, X)

while still being 100% compatible with the Regression.jl API as it is now (for the primal linear SVM problem)
I'll close this. Sorry for PRs like this.

authors: Evizero lindahua

license: mit


text:
Add file exclusion rule for mirroring

Motivation
Related to https://github.com/line/centraldogma/issues/38
Modifications

Add remoteExclude property to SingleMirrorConfig.

It takes string of gitignore format

Known Limitations
~- Current rule can exclude only one directory or file. I think the property can be extended later to contain list of directory or file~
~- Doesn't support file matching like regex~

😆  Thank you for your help~~

Could you also update the documentation as the follow-up? 😆
https://github.com/line/centraldogma/blob/master/site/src/sphinx/mirroring.rst

retest this, please

Excellent work!
Congratulations, @yyuunn0044! 🎉 🎉 🎉
I'm really looking forward to your next PR. 😄

repo: line/centraldogma


text:
Xilem architecture prototype

I am writing a blog post on the Xilem architecture, and want that to refer to a PR, as that is the most stable identifier for a branch; the PR can be closed and the branch deleted, and still resolve.
I will also continue to explore and develop in this branch. We might rethink that if we start developing more collaboratively.
Also note, I do the same with the idiopath_py and idiopath_async branches. Those are shorter-term explorations, and basically I just want to capture what I did. It's likely the ideas for both will get merged into this branch.

Two months on, the peanut gallery wonders what impressions/experiences Druid developers and/or users have had with this prototype. Is the mood optimistic? Have unexpected challenges arisen?
I hope this doesn't come across as "are we there yet" — I'm actually just maddeningly curious about what people think about it! 😅

I didn't get the impression that this is in the state where it can be tried out easily, since there was no call for testing or similar.

The most innovative aspect of Xilem is event dispatching based on an id path, at each stage providing mutable access to app state.

Nice to see that this idea caught on. You can copy my code for compressed paths if you like, though they may be less useful for Xilem since you have separate Id and Path.
In general I like this idea quite a lot. Some comments:

Most elements have to implement both View and Widget
What's the relationship between View::event and Widget::event? Aha, the Widget impl leverages Druid's existing machinery for handling events, then triggers a "view event". Is this a temporary relationship or could all event handling code be pushed to the "view" side?
Is it desirable that an app always has one "app data"? What if, instead, an app consisted of any number of "modules", each with its own data and view, with each module's view optionally being a window root and optionally being embedded within another view?
EventResult::Nop — is that "no-op" or "nope"? :laughing:

Xilem has inspired me to consider something vaguely similar built on top of KAS, which could go some way to solving its biggest weaknesses (difficulty expressing dynamic layout, and not requiring manual updates of widgets dependant on app state). But if we're honest, the Rust UI space is a lot more crowded today than it was when these projects started.

authors: dhardy jeffparsons jplatte raphlinus

repo: linebender/druid


text:
"vid2vid_inference.yaml" is missing

Looks like "vid2vid_inference.yaml" is missing, where can I download it? Thanks.

Hi , I updated the code. You can find "vid2vid.yaml" in the main branch.


text:
强烈建议增加开始全部任务的接口

项目本身支持了暂停全部任务的接口，上层如果想要开始全部就需要再次根据url创建任务并且start，不太方便，尤其是跟列表绑定后，建议增加开始全部任务的接口;

+1

+1

+1

将会在okdownload的拓展库中支持该功能。

authors: Jacksgong appledong coolspan layasntx xiangyutian

repo: lingochamp/FileDownloader


text:
BUG: bulk download stuck

OkDownload Version
1.0.7
Problem Describe
Randomly (that happened 20% of the times so far) when trying to download files in bulk (900MB - 600 files) the queue gets stuck and it stops emitting events:
this is the code I'm using to set up the bulk download:
DownloadContext.Builder builder = new DownloadContext.QueueSet()
                        .setParentPathFile(new File(context.getCacheDir().toString() + File.separator + "tmpapp"))
                        .setMinIntervalMillisCallbackProcess(300)
                        .commit();
                for (int i = 0; i < downloadTasks.size(); i++) {
                    //downloadTasks list of MyDownloadTaskClass
                    MyDownloadTaskClass task = downloadTasks.get(i);
                    builder.bind(task.url).addTag(0, task.filename).addTag(1, task.savedDir).addTag(2, task.finalDir).addTag(3, i);
                }

                DownloadContext downloadContext = builder.setListener(new DownloadContextListener() {

                    @Override
                    public void taskEnd(@NonNull DownloadContext context, @NonNull com.liulishuo.okdownload.DownloadTask task, @NonNull EndCause cause, @Nullable Exception realCause, int remainCount) {
                        final int index = (int) task.getTag(3);
                        synchronized (updateFileNumberLock) {
                            switch (cause) {
                                case COMPLETED:
                                    break;
                                case PRE_ALLOCATE_FAILED:
                                case FILE_BUSY:
                                case ERROR:
                                case CANCELED:
                                    log("failed at index " + index);
                                    if (index < downloadTasks.size()) {
                                        failedTasks.add(downloadTasks.get(index));
                                        failedDownloads++;
                                    }
                                    break;
                            }
                            downloadedFiles++;
                        }
                    }

                    @Override
                    public void queueEnd(@NonNull DownloadContext context) {
                        //downloadFinished variable used to exit the service loop and hide the foreground notification
                        downloadFinished = true;
                        log("QUEUE END");
                    }
                }).build();

downloadContext.start(
                        new DownloadListener() {
                            @Override
                            public void taskStart(@NonNull com.liulishuo.okdownload.DownloadTask task) {
                                Log.e("DOWNLOADCONTEXT", "taskStart "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void connectTrialStart(@NonNull com.liulishuo.okdownload.DownloadTask task, @NonNull Map<String, List<String>> requestHeaderFields) {
                                Log.e("DOWNLOADCONTEXT", "connectTrialStart "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void connectTrialEnd(@NonNull com.liulishuo.okdownload.DownloadTask task, int responseCode, @NonNull Map<String, List<String>> responseHeaderFields) {
                                Log.e("DOWNLOADCONTEXT", "connectTrialEnd "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void downloadFromBeginning(@NonNull com.liulishuo.okdownload.DownloadTask task, @NonNull BreakpointInfo info, @NonNull ResumeFailedCause cause) {
                                Log.e("DOWNLOADCONTEXT", "downloadFromBeginning "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void downloadFromBreakpoint(@NonNull com.liulishuo.okdownload.DownloadTask task, @NonNull BreakpointInfo info) {
                                Log.e("DOWNLOADCONTEXT", "downloadFromBreakpoint "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void connectStart(@NonNull com.liulishuo.okdownload.DownloadTask task, int blockIndex, @NonNull Map<String, List<String>> requestHeaderFields) {
                                Log.e("DOWNLOADCONTEXT", "connectStart "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void connectEnd(@NonNull com.liulishuo.okdownload.DownloadTask task, int blockIndex, int responseCode, @NonNull Map<String, List<String>> responseHeaderFields) {
                                Log.e("DOWNLOADCONTEXT", "connectEnd "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void fetchStart(@NonNull com.liulishuo.okdownload.DownloadTask task, int blockIndex, long contentLength) {
                                Log.e("DOWNLOADCONTEXT", "fetchStart "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void fetchProgress(@NonNull com.liulishuo.okdownload.DownloadTask task, int blockIndex, long increaseBytes) {
                                Log.d("DOWNLOADCONTEXT", "fetchProgress "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void fetchEnd(@NonNull com.liulishuo.okdownload.DownloadTask task, int blockIndex, long contentLength) {
                                Log.d("DOWNLOADCONTEXT", "fetchEnd "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }

                            @Override
                            public void taskEnd(@NonNull final com.liulishuo.okdownload.DownloadTask task, @NonNull final EndCause cause, @Nullable final Exception realCause) {
                                Log.d("DOWNLOADCONTEXT", "taskEnd "+ task.getFilename());
                                cyclesWithouUpdate = 0; //update received reset the counter
                            }
                        }, false);

                while (!downloadFinished) {
                    log("CHECK LOOP cyclesWithouUpdate " + cyclesWithouUpdate + " downloadedFiles " + downloadedFiles + " failedDownloads " + failedDownloads + " progress " + (downloadedFiles - failedDownloads) * 100 / totalFiles);
                    //after not receiving updates for 60 seconds I kill the queue and retry stuck downloads
                    if(cyclesWithouUpdate > 60){
                        log("cyclesWithouUpdate > 60 stop and retry failedTasks "+failedTasks.size());
                        downloadContext.stop();
                    }
                    setForegroundAsync(updateNotification(context, notificationName, DownloadStatus.RUNNING, (downloadedFiles - failedDownloads) * 100 / totalFiles, null));
                    cyclesWithouUpdate++;
                    Thread.sleep(1000);
                }

Log
2022-05-25 10:06:33.267 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:33.651 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:34.021 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:34.324 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:34.628 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:34.953 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.266 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.566 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.897 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.944 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchProgress f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.955 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchEnd f9b760b0-263e-4316-bc4c-8cff7b64fe9f
2022-05-25 10:06:35.955 14078-14078/com.trizeta.pandora E/DownloadAllWorker: taskEnd f9b760b0-263e-4316-bc4c-8cff7b64fe9f

//from here I stop receiving updates from tasks and "queueEnd" is never called

2022-05-25 10:06:37.694 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 1 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:38.696 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 2 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:39.698 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 3 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:40.701 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 4 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:41.703 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 5 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:42.708 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 6 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:43.710 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 7 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:44.715 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 8 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:45.718 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 9 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:46.720 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 10 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:47.727 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 11 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:48.729 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 12 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:49.734 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 13 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:50.737 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 14 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:51.745 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 15 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:52.750 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 16 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:53.755 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 17 downloadedFiles 913 failedDownloads 3 progress 99
2022-05-25 10:06:54.759 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 18 downloadedFiles 913 failedDownloads 3 progress 99

[...]

2022-05-25 10:07:37.948 14078-14675/com.trizeta.pandora D/DownloadAllWorker: CHECK LOOP cyclesWithouUpdate 61 downloadedFiles 913 failedDownloads 3 progress 99

//3 failed downloads atm
2022-05-25 10:07:37.948 14078-14675/com.trizeta.pandora D/DownloadAllWorker: cyclesWithouUpdate > 60 stop and retry 3

//stop downloads
2022-05-25 10:07:37.950 14078-14078/com.trizeta.pandora E/DownloadAllWorker: fetchEnd 283b7f6a-c96e-4e2f-916e-6edd3b49b082
2022-05-25 10:07:37.952 14078-14078/com.trizeta.pandora E/DownloadAllWorker: taskEnd 283b7f6a-c96e-4e2f-916e-6edd3b49b082
2022-05-25 10:07:37.952 14078-14078/com.trizeta.pandora D/DownloadAllWorker:failed at index 405
2022-05-25 10:07:37.952 14078-14078/com.trizeta.pandora E/DownloadAllWorker: taskEnd cf4deb64-7a7f-4f13-a54e-2306eefeeffe
2022-05-25 10:07:37.952 14078-14078/com.trizeta.pandora D/DownloadAllWorker: failed at index 442
2022-05-25 10:07:37.952 14078-14078/com.trizeta.pandora D/DownloadAllWorker: QUEUE END
//2 downloads stuck so far

any solution here?!

same here...

repo: lingochamp/okdownload


text:
Reference Unsloth in header

Summary
Reference Unsloth in header section

Testing Done

Hardware Type:
[x] run make test to ensure correctness
[x] run make checkstyle to ensure code style
[x] run make test-convergence to ensure convergence

@ByronHsu @helloworld1 @yundai424 @qingquansong ptal

In apache license, it says If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.  Are those two files considered derived work? If so, we also need to change the NOTICE file.

In apache license, it says
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
Are those two files considered derived work? If so, we also need to change the NOTICE file.

Sure will followup with another ticket to change NOTICE file accordingly.

We are glad to announce that Unsloth and LinkedIn have fully resolved disagreements regarding references!

repo: linkedin/Liger-Kernel


text:
Fix NPE in NamedBlobPutHandler

Bug fix for routerStitchBlobCallback.

Codecov Report

Merging #1828 (6309976) into master (f994a2e) will decrease coverage by 58.70%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #1828       +/-   ##
=============================================
- Coverage     74.00%   15.30%   -58.71%
+ Complexity     9539     2214     -7325
=============================================
  Files           690      690
  Lines         52240    52243        +3
  Branches       6492     6492
=============================================
- Hits          38659     7994    -30665
- Misses        11556    43801    +32245
+ Partials       2025      448     -1577

Impacted Files
Coverage Δ
Complexity Δ

...github/ambry/frontend/AmbryIdConverterFactory.java
0.00% <0.00%> (-96.00%)
0.00 <0.00> (-2.00)

...com/github/ambry/frontend/NamedBlobPutHandler.java
0.00% <0.00%> (-92.15%)
0.00 <0.00> (-3.00)

.../src/main/java/com/github/ambry/router/Router.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-6.00%)

.../src/main/java/com/github/ambry/store/Message.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-3.00%)

...rc/main/java/com/github/ambry/named/PutResult.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-2.00%)

...rc/main/java/com/github/ambry/quota/QuotaMode.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...rc/main/java/com/github/ambry/quota/QuotaName.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...rc/main/java/com/github/ambry/rest/RestMethod.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...c/main/java/com/github/ambry/config/KMSConfig.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...c/main/java/com/github/ambry/config/SSLConfig.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

... and 545 more

Continue to review full report at Codecov.

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

repo: linkedin/ambry


text:
Does Datahub use H2 database?

I am using Skywalking App Performance monitor tool to play with Datahub,  Skywalking topology gives me a H2 database.
Wonder if it actually exits and get used.
Best,

We do use it for ImmutableLocalDAO, which is leveraged by /dataPlatforms endpoint: https://github.com/linkedin/datahub/blob/master/gms/impl/src/main/java/com/linkedin/metadata/resources/dataplatform/DataPlatforms.java#L28

Closing this assuming the question has been answered. Feel free to reopen otherwise.

authors: liangjun-jiang mars-lan

repo: linkedin/datahub