Blockchain request timed out, then UXTO/network rules issues

Bill posted this spee.ch issue a couple days ago on the team Slack.  The end result was the daemon not being able to publish/create channels due to network rules.  Looks like there was a blockchain timeout during a publish which started the problem.
2017-10-25 12:12:51,022 INFO     lbrynet.daemon.Daemon:1908: Publish: {'claim_address': u'banpwixPosfVDWnGvXqU2af36Qpsd7buGd', 'name': u'29052016-PORTOGR4', 'bid': 0.01, 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'', u'license': u'Public Domain', u'author': u'spee.ch', u'title': u'29052016-PORTOGR4', u'language': u'en', 'version': '_0_1_0', u'nsfw': False}}}, 'file_path': u'/home/lbry/Downloads/29052016-PORTOGR4.jpg', 'change_address': None}
2017-10-25 12:13:05,503 INFO     lbrynet.daemon.Publisher:27: Starting publish for 29052016-PORTOGR4
2017-10-25 12:13:06,567 INFO     lbrynet.lbry_file.EncryptedFileMetadataManager:246: Saved sd blob hash be4a8a928b2dbb4a0ddaa91b691ce9b75af2217567c1db43ccdf5c43c45063867b3b88b9fafded60c577964ef88fc7b3 to stream hash 2cad6eb8b085ea2716c99789a5e4b11d519d166d2a8ed9b4293edd08e80a8ac532aaa64198b4f7488887100a9c306444
2017-10-25 12:13:06,570 INFO     lbrynet.core.Wallet:1368: Send claim: 29052016-PORTOGR4 for 0.01: 080110011a810108011239080410011a1132393035323031362d504f52544f47523422002a07737065652e6368320d5075626c696320446f6d61696e38004a0052005a001a42080110011a30be4a8a928b2dbb4a0ddaa91b691ce9b75af2217567c1db43ccdf5c43c45063867b3b88b9fafded60c577964ef88fc7b3220a696d6167652f6a706567
2017-10-25 12:13:13,512 ERROR    lbryum.network:698: blockchain request timed out
2017-10-25 12:13:14,310 ERROR    lbryum:116: [CoinChooserOldestFirst] change: [(1, 'bDXadMe4zadBCCPkCc3TgjcdeqNNQF8CPM', 59516800)]

2017-10-25 12:13:14,310 ERROR    lbryum:116: [CoinChooserOldestFirst] using 1 inputs

2017-10-25 12:13:14,310 ERROR    lbryum:116: [CoinChooserOldestFirst] using buckets: [u'0c867d7997aa4936d9f23d23945b50bb738c5cc7b048c1144972a09b3f40e16e:1']

2017-10-25 12:13:14,526 ERROR    lbryum:116: adding signature for ff0488b21e000000000000000000bd65a3a5d0de7088b844ce8e0c8d766fdb05becbe2c7ae4f2688b2d61265f5da02da986b32ad2352e30a0039ad438c9e06c572ba149d5fa364dcaece6c7ab515d90100562c

2017-10-25 12:13:14,929 ERROR    lbryum:116: is_complete True

2017-10-25 12:13:14,930 ERROR    lbrynet.daemon.auth.server:353: Failed to process publish: Not connected.
Traceback (most recent call last):
  File "site-packages/twisted/internet/defer.py", line 1299, in _inlineCallbacks
  File "site-packages/lbrynet/core/Wallet.py", line 1372, in _send_name_claim
  File "site-packages/lbrynet/core/Wallet.py", line 1288, in _run_cmd_as_defer_succeed
  File "site-packages/lbryum/commands.py", line 91, in func_wrapper
  File "site-packages/lbryum/commands.py", line 1689, in claim
  File "site-packages/lbryum/wallet.py", line 1214, in sendtx
  File "site-packages/lbryum/wallet.py", line 1222, in send_tx
AssertionError: Not connected.
2017-10-25 12:13:51,253 ERROR    lbryum.network:698: blockchain request timed out
2017-10-25 12:14:33,187 INFO     lbrynet.core.Wallet:823: Resolving 29052016-PORTOGR2#28d8d44f7fad0ec84724a181c9e47a89a4412079
2017-10-25 12:14:34,187 INFO     lbrynet.core.Wallet:823: Resolving 29052016-PORTOGR3#bd389aceebbfc58b5302cba3242ed7be5d155606
2017-10-25 12:14:35,189 INFO     lbrynet.core.Wallet:823: Resolving 29052016-PORTOGR1#1e605994cbbce948289a41ae3ba1c2729dbc16be
2017-10-25 12:14:36,187 INFO     lbrynet.core.Wallet:823: Resolving a-false-mirror-charles-todd-mobi#850baec0af66d766fcaaedf1531ac4f3519c6376
2017-10-25 12:14:51,205 ERROR    lbryum.network:698: blockchain request timed out

Transactions afterwards would result in this:
2017-10-25 18:26:32,912 INFO     lbrynet.daemon.Publisher:27: Starting publish for get-out-of-here
2017-10-25 18:26:33,065 INFO     lbrynet.lbry_file.EncryptedFileMetadataManager:246: Saved sd blob hash efc0e11fb9c9207c2f5ef8826f7b55b1a141fc7c944142e7d5b946a6a9a57dac1e45c9ae5b1ab983d50ec1163db203c4 to stream hash<PHONE_NUMBER>4ee21026c4992b1019b8eecd394ea472a1a28751ce9fdc3b4df41b705d13d1775004558cabc2a1491364d7
2017-10-25 18:26:33,068 INFO     lbrynet.core.Wallet:1368: Send claim: get-out-of-here for 0.01: 080110011a7e08011237080410011a0f6765742d6f75742d6f662d6865726522002a07737065652e6368320d5075626c696320446f6d61696e38004a0052005a001a41080110011a30efc0e11fb9c9207c2f5ef8826f7b55b1a141fc7c944142e7d5b946a6a9a57dac1e45c9ae5b1ab983d50ec1163db203c42209696d6167652f676966
2017-10-25 18:26:38,440 ERROR    lbryum:116: [CoinChooserOldestFirst] change: [(1, 'bKoHKmpz18K2fXsMuaNeoCRASJd5XpxHyu', 59521900)]

2017-10-25 18:26:38,442 ERROR    lbryum:116: [CoinChooserOldestFirst] using 1 inputs

2017-10-25 18:26:38,442 ERROR    lbryum:116: [CoinChooserOldestFirst] using buckets: [u'0c867d7997aa4936d9f23d23945b50bb738c5cc7b048c1144972a09b3f40e16e:1']

2017-10-25 18:26:39,133 ERROR    lbryum:116: adding signature for ff0488b21e000000000000000000bd65a3a5d0de7088b844ce8e0c8d766fdb05becbe2c7ae4f2688b2d61265f5da02da986b32ad2352e30a0039ad438c9e06c572ba149d5fa364dcaece6c7ab515d90100562c

2017-10-25 18:26:40,349 ERROR    lbryum:116: is_complete True

2017-10-25 18:26:40,475 ERROR    lbrynet.daemon.auth.server:353: Failed to process publish: Claim to name get-out-of-here failed: error: The transaction was rejected by network rules.(18: bad-txns-inputs-spent)
[01000000016ee1403f9ba0724914c148b0c75c8c73bb505b94233df2d93649aa97797d860c010000006b483045022100e859b3077b2960de38903df19b1458ee04bf9eb3619f7bc5be79f775e024211b02207cd89ede20a4370905eae2a5059bc985874c618b4fe66dbc32809eab1639e97d012102f6307f114727bec182d67d17e1d33e878066af1eb195dfc2b75f2e711d39c067ffffffff0240420f0000000000b2b50f6765742d6f75742d6f662d686572654c84080110011a7e08011237080410011a0f6765742d6f75742d6f662d6865726522002a07737065652e6368320d5075626c696320446f6d61696e38004a0052005a001a41080110011a30efc0e11fb9c9207c2f5ef8826f7b55b1a141fc7c944142e7d5b946a6a9a57dac1e45c9ae5b1ab983d50ec1163db203c42209696d6167652f6769666d7576a914f1feef9c44a91ed89ac8d8cc746523e3d18af3ec88ac6c3b8c03000000001976a9144d8b11fd73a90760a38354a8bc2466e0ee8020ff88ac00000000]
Traceback (most recent call last):
  File "site-packages/twisted/internet/defer.py", line 1299, in _inlineCallbacks
  File "site-packages/lbrynet/core/Wallet.py", line 945, in claim_name
Exception: Claim to name get-out-of-here failed: error: The transaction was rejected by network rules.(18: bad-txns-inputs-spent)
[01000000016ee1403f9ba0724914c148b0c75c8c73bb505b94233df2d93649aa97797d860c010000006b483045022100e859b3077b2960de38903df19b1458ee04bf9eb3619f7bc5be79f775e024211b02207cd89ede20a4370905eae2a5059bc985874c618b4fe66dbc32809eab1639e97d012102f6307f114727bec182d67d17e1d33e878066af1eb195dfc2b75f2e711d39c067ffffffff0240420f0000000000b2b50f6765742d6f75742d6f662d686572654c84080110011a7e08011237080410011a0f6765742d6f75742d6f662d6865726522002a07737065652e6368320d5075626c696320446f6d61696e38004a0052005a001a41080110011a30efc0e11fb9c9207c2f5ef8826f7b55b1a141fc7c944142e7d5b946a6a9a57dac1e45c9ae5b1ab983d50ec1163db203c42209696d6167652f6769666d7576a914f1feef9c44a91ed89ac8d8

Longer log file here: fulllog.txt
cc746523e3d18af3ec88ac6c3b8c03000000001976a9144d8b11fd73a90760a38354a8bc2466e0ee8020ff88ac00000000]

Something similar happened to be on my main machine - I can't run claim_list_mine or resolves (probably other blockchain related commands too) - they time out.  Still need to find out is this is related to lbry wallet bloat, but I still think the daemon should be able to recover from this somehow.
c:\Program Files (x86)\LBRY\resources\app\dist>lbrynet-cli resolve ten
ERROR: Failed to get response from server within timeout of 30

2017-10-30 16:21:31,638 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:21:31,638 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:24:31,996 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:24:31,996 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:25:31,894 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:25:31,894 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:26:31,911 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:26:31,911 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:27:31,956 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:27:31,956 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:28:32,204 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:28:32,204 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:31:32,142 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:31:32,142 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:31:58,089 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 050f1c8ef767d359 to <IP_ADDRESS>:56149
2017-10-30 16:33:32,611 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:33:32,611 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:34:32,427 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:34:32,427 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:36:32,523 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:36:32,523 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:39:32,592 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:39:32,592 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:41:32,739 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:41:32,739 ERROR    lbryum.network:698: blockchain request timed out
2017-10-30 16:42:55,492 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 5b61d8005d3799b4 to <IP_ADDRESS>:62028
2017-10-30 16:43:02,710 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending f6100f902e0b41b9 to <IP_ADDRESS>:62041
2017-10-30 16:43:04,615 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 63d17a725a474e5f to <IP_ADDRESS>:62041

Even Franklin ran into the issue this morning:
2017-11-03 08:00:04,365 INFO     lbrynet.daemon.DaemonControl:70: Starting lbrynet-daemon from command line
2017-11-03 08:00:04,862 INFO     lbrynet.daemon.DaemonServer:66: Using non-authenticated API
2017-11-03 08:00:04,865 INFO     lbrynet.daemon.Daemon:243: Starting lbrynet-daemon
2017-11-03 08:00:04,878 INFO     lbrynet.daemon.ExchangeRateManager:210: Starting exchange rate manager
2017-11-03 08:00:05,282 INFO     lbrynet.daemon.Daemon:269: Platform: {"lbrynet_version": "0.17.2rc7", "platform": "Linux-4.4.0-93-generic-x86_64-with-Ubuntu-16.04-xenial", "os_system": "Linux", "python_version": "2.7.12", "os_release": "4.4.0-93-generic", "lbryum_version": "3.1.11rc6", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.14rc2", "processor": "x86_64", "build": "rc"}
2017-11-03 08:00:05,289 INFO     lbrynet.daemon.Daemon:479: Loading databases
2017-11-03 08:00:05,298 WARNING  lbrynet.daemon.Daemon:490: db_revision file not found. Creating it
2017-11-03 08:00:05,333 INFO     lbrynet.daemon.Daemon:509: Upgrading your databases
2017-11-03 08:00:05,350 INFO     lbrynet.db_migrator.migrate1to2:9: Doing the migration
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate1to2:11: Migration succeeded
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate2to3:9: Doing the migration
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate2to3:11: Migration succeeded
2017-11-03 08:00:05,352 INFO     lbrynet.db_migrator.migrate3to4:9: Doing the migration
2017-11-03 08:00:05,352 INFO     lbrynet.db_migrator.migrate3to4:11: Migration succeeded
2017-11-03 08:00:05,353 INFO     lbrynet.daemon.Daemon:505: Finished upgrading the databases.
2017-11-03 08:00:05,353 INFO     lbrynet.daemon.Daemon:545: Using lbryum wallet
2017-11-03 08:00:07,918 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:09,372 INFO     lbrynet.core.Session:254: Starting DHT
2017-11-03 08:00:09,420 INFO     lbrynet.dht.protocol:178: DHT listening on UDP 4444
2017-11-03 08:00:11,656 INFO     lbrynet.core.RateLimiter:72: Starting rate limiter.
2017-11-03 08:00:11,657 INFO     lbrynet.core.BlobManager:42: Starting disk blob manager. blob_dir: /home/lbry/.lbrynet/blobfiles, db_file: /home/lbry/.lbrynet/blobs.db
2017-11-03 08:00:11,658 INFO     lbrynet.core.Wallet:451: Starting wallet.
2017-11-03 08:00:11,704 INFO     lbrynet.core.Wallet:1170: Loading the wallet
2017-11-03 08:00:13,844 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:18,848 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:23,851 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:24,001 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 266389, behind: 488
2017-11-03 08:00:28,856 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:33,861 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:38,866 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:43,871 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:48,876 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:53,881 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:58,886 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:03,892 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:08,897 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:12,244 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 0, behind: None
2017-11-03 08:01:13,902 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:18,908 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:19,238 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 266389, behind: 488
2017-11-03 08:01:23,913 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:28,918 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:33,923 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:38,927 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:43,931 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:02:12,243 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 0, behind: None
2017-11-03 08:02:12,770 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:02:42,901 ERROR    lbryum.network:698: blockchain request timed out
2017-11-03 08:03:12,103 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 0, behind: None
2017-11-03 08:03:12,263 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:03:17,497 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:03:32,661 INFO     lbrynet.core.Wallet:1261: Local Height: 266389, remote height: 266389, behind: 0
2017-11-03 08:03:32,661 INFO     lbrynet.core.Wallet:1269: Wallet Loaded
2017-11-03 08:03:32,662 INFO     lbrynet.core.Wallet:1194: Subscribing to addresses
2017-11-03 08:03:32,762 INFO     lbrynet.core.Wallet:1196: Synchronized wallet
2017-11-03 08:03:32,783 INFO     lbrynet.core.BlobAvailability:30: Starting blob availability tracker.
2017-11-03 08:03:32,787 INFO     lbrynet.daemon.Daemon:518: Starting to setup up file manager
2017-11-03 08:03:32,820 INFO     lbrynet.file_manager.EncryptedFileManager:58: Started file manager
2017-11-03 08:03:32,821 INFO     lbrynet.daemon.Daemon:529: Done setting up file manager
2017-11-03 08:03:32,821 INFO     lbrynet.daemon.Daemon:303: Daemon bound to port: 3333
2017-11-03 08:03:32,822 INFO     lbrynet.daemon.Daemon:259: Starting balance: 8547.050317
2017-11-03 08:03:32,823 INFO     lbrynet.daemon.Daemon:237: Started lbrynet-daemon
2017-11-03 08:03:32,823 INFO     lbrynet.daemon.Daemon:238: 0 blobs in manager
2017-11-03 08:03:32,824 INFO     lbrynet.file_manager.EncryptedFileManager:125: Started 0 lbry files
2017-11-03 08:31:04,459 ERROR    lbryum.network:698: blockchain request timed out
2017-11-03 08:33:47,423 ERROR    lbryum.network:698: blockchain request timed out

I've also been having issues with lbryum servers during publishing. Jack
said he restarted one last night. That seems to have  helped with my stuff.
On Fri, Nov 3, 2017 at 9:29 AM, Thomas Zarebczan<EMAIL_ADDRESS>wrote:

Even Franklin ran into the issue this morning:
2017-11-03 08:00:04,365 INFO     lbrynet.daemon.DaemonControl:70: Starting lbrynet-daemon from command line
2017-11-03 08:00:04,862 INFO     lbrynet.daemon.DaemonServer:66: Using non-authenticated API
2017-11-03 08:00:04,865 INFO     lbrynet.daemon.Daemon:243: Starting lbrynet-daemon
2017-11-03 08:00:04,878 INFO     lbrynet.daemon.ExchangeRateManager:210: Starting exchange rate manager
2017-11-03 08:00:05,282 INFO     lbrynet.daemon.Daemon:269: Platform: {"lbrynet_version": "0.17.2rc7", "platform": "Linux-4.4.0-93-generic-x86_64-with-Ubuntu-16.04-xenial", "os_system": "Linux", "python_version": "2.7.12", "os_release": "4.4.0-93-generic", "lbryum_version": "3.1.11rc6", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.14rc2", "processor": "x86_64", "build": "rc"}
2017-11-03 08:00:05,289 INFO     lbrynet.daemon.Daemon:479: Loading databases
2017-11-03 08:00:05,298 WARNING  lbrynet.daemon.Daemon:490: db_revision file not found. Creating it
2017-11-03 08:00:05,333 INFO     lbrynet.daemon.Daemon:509: Upgrading your databases
2017-11-03 08:00:05,350 INFO     lbrynet.db_migrator.migrate1to2:9: Doing the migration
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate1to2:11: Migration succeeded
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate2to3:9: Doing the migration
2017-11-03 08:00:05,351 INFO     lbrynet.db_migrator.migrate2to3:11: Migration succeeded
2017-11-03 08:00:05,352 INFO     lbrynet.db_migrator.migrate3to4:9: Doing the migration
2017-11-03 08:00:05,352 INFO     lbrynet.db_migrator.migrate3to4:11: Migration succeeded
2017-11-03 08:00:05,353 INFO     lbrynet.daemon.Daemon:505: Finished upgrading the databases.
2017-11-03 08:00:05,353 INFO     lbrynet.daemon.Daemon:545: Using lbryum wallet
2017-11-03 08:00:07,918 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:09,372 INFO     lbrynet.core.Session:254: Starting DHT
2017-11-03 08:00:09,420 INFO     lbrynet.dht.protocol:178: DHT listening on UDP 4444
2017-11-03 08:00:11,656 INFO     lbrynet.core.RateLimiter:72: Starting rate limiter.
2017-11-03 08:00:11,657 INFO     lbrynet.core.BlobManager:42: Starting disk blob manager. blob_dir: /home/lbry/.lbrynet/blobfiles, db_file: /home/lbry/.lbrynet/blobs.db
2017-11-03 08:00:11,658 INFO     lbrynet.core.Wallet:451: Starting wallet.
2017-11-03 08:00:11,704 INFO     lbrynet.core.Wallet:1170: Loading the wallet
2017-11-03 08:00:13,844 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:18,848 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:23,851 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:24,001 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 266389, behind: 488
2017-11-03 08:00:28,856 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:33,861 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:38,866 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:43,871 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:48,876 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:53,881 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:00:58,886 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:03,892 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:08,897 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:12,244 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 0, behind: None
2017-11-03 08:01:13,902 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:18,908 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:19,238 INFO     lbrynet.core.Wallet:1261: Local Height: 265901, remote height: 266389, behind: 488
2017-11-03 08:01:23,913 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:28,918 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:33,923 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:38,927 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:01:43,931 WARNING  lbrynet.daemon.auth.server:331: Function not allowed during startup: wallet_balance
2017-11-03 08:02:12,243 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 0, behind: None
2017-11-03 08:02:12,770 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:02:42,901 ERROR    lbryum.network:698: blockchain request timed out
2017-11-03 08:03:12,103 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 0, behind: None
2017-11-03 08:03:12,263 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:03:17,497 INFO     lbrynet.core.Wallet:1261: Local Height: 266015, remote height: 266389, behind: 374
2017-11-03 08:03:32,661 INFO     lbrynet.core.Wallet:1261: Local Height: 266389, remote height: 266389, behind: 0
2017-11-03 08:03:32,661 INFO     lbrynet.core.Wallet:1269: Wallet Loaded
2017-11-03 08:03:32,662 INFO     lbrynet.core.Wallet:1194: Subscribing to addresses
2017-11-03 08:03:32,762 INFO     lbrynet.core.Wallet:1196: Synchronized wallet
2017-11-03 08:03:32,783 INFO     lbrynet.core.BlobAvailability:30: Starting blob availability tracker.
2017-11-03 08:03:32,787 INFO     lbrynet.daemon.Daemon:518: Starting to setup up file manager
2017-11-03 08:03:32,820 INFO     lbrynet.file_manager.EncryptedFileManager:58: Started file manager
2017-11-03 08:03:32,821 INFO     lbrynet.daemon.Daemon:529: Done setting up file manager
2017-11-03 08:03:32,821 INFO     lbrynet.daemon.Daemon:303: Daemon bound to port: 3333
2017-11-03 08:03:32,822 INFO     lbrynet.daemon.Daemon:259: Starting balance: 8547.050317
2017-11-03 08:03:32,823 INFO     lbrynet.daemon.Daemon:237: Started lbrynet-daemon
2017-11-03 08:03:32,823 INFO     lbrynet.daemon.Daemon:238: 0 blobs in manager
2017-11-03 08:03:32,824 INFO     lbrynet.file_manager.EncryptedFileManager:125: Started 0 lbry files
2017-11-03 08:31:04,459 ERROR    lbryum.network:698: blockchain request timed out
2017-11-03 08:33:47,423 ERROR    lbryum.network:698: blockchain request timed out
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbryum/issues/165#issuecomment-341703236, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWJIMxiS-eo9oGBMiTu2glvOkeM3e1Oks5syxU4gaJpZM4QLk9K
.

Still getting blockchain timeouts upon startup sometimes. Restarting fixes it.

Theoretically, the daemon/wallet should be able to recover from a timeout and sync back up when the server is available.

new wallet re-connects when connection is lost to lbryumx


Fix startup

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   95.78%   95.78%
=======================================
  Files          63       63
  Lines         996      996
  Branches       43       43
=======================================
  Hits          954      954
  Misses         41       41
  Partials        1        1

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 48196b9...f6abd0c. Read the comment docs.


SPARK-34800 use fine-grained lock in SessionCatalog.tableExists

What changes were proposed in this pull request?
Use fine-grained lock in SessionCatalog.tableExists, in order to lock currentDB variable rather than lock tableExists method which will block inner external catalog's behaviour.
Why are the changes needed?
We have modified the underlying hive meta store which a different hive  database is placed in its own shard for performance. However, we found that the synchronized lock  limits the concurrency.
How was this patch tested?
Existing tests.

Can one of the admins verify this patch?

ok to test

please fix the format of the PR title, like [SPARK-34800][SQL] U...

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40819/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136237/

please fix the format of the PR title, like [SPARK-34800][SQL] U...

done

@cloud-fan would you please review this PR

thanks, merging to master!


Cannot use encodeData with a tuple of CompactBytesArray

I'm submitting a...

[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
The Typescript types fail in the following case below.

Error: Type '[string, string, string, string]' is not assignable to type 'string | number'

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
The following test should pass and be able to be run without any Typescript errors:
describe('for CompactBytesArray of tuples `(...,...)[CompactBytesArray]`', () => {
      it(`encodes/decodes: [ ["0x00000002", "0xcafecafecafecafecafecafecafecafecafecafe", "0x11223344", "0xbb11bb11"] ] as (bytes4,address,bytes4,bytes4)[CompactBytesArray]`, () => {
        const schema = {
          name: 'AddressPermissions:AllowedCalls:<address>',
          key: '0x4b80742de2bf393a64c70000<address>',
          keyType: 'MappingWithGrouping',
          valueType: '(bytes4,address,bytes4,bytes4)[CompactBytesArray]',
          valueContent: '(BitArray,Address,Bytes4,Bytes4)',
        };

        const expectedEncodedValue =
          '0x002000000002cafecafecafecafecafecafecafecafecafecafe11223344bb11bb11';

        const result = ERC725.encodeData(
          [
            {
              keyName: 'AddressPermissions:AllowedCalls:<address>',
              dynamicKeyParts: address,
              value: [
                [
                  '0x00000002',
                  '0xcafecafecafecafecafecafecafecafecafecafe',
                  '0x11223344',
                  '0xbb11bb11',
                ],
              ],
            },
          ],
          [schema],
        );

        assert.equal(result.values[0], expectedEncodedValue);
      });
    });
  });

An example of the test above is provided in the branch fix/encodeData-CompactBytesArray
https://github.com/ERC725Alliance/erc725.js/tree/fix/encodeData-CompactBytesArray


x86_64: Fix /dev/random rdrand implementation

Summary
This restores the functionally of /dev/random for x86_64 which was using the rdrand intrinsics incorrectly. They are defined by Intel here:
https://software.intel.com/en-us/cpp-compiler-developer-guide-and-reference-rdrand16-step-rdrand32-step-rdrand64-step
Impact
rdrand was checking the wrong return value for the intrinsics
so it would block forever.  The read function was also not returning
the actual number of bytes read, if you read 8 you would get 2 back.
Testing
This was tested by running the rand example application
NuttShell (NSH) NuttX-9.0.0
nsh>rand
Reading 8 random numbers
Random values (0x101584f70):
0000: 019a172df7d539f2df8550362e2d3f74 9b467c51ebe30b9f6510e540e34fabcc ...-..9...P6.-?t<EMAIL_ADDRESS>

@btashton compare with other sucessful check, version.sh always fail from yesterday because "git -C sources/nuttx fetch --tags" can't receive any tag from server.
The good log:
020-05-04T09:14:12.0307391Z ##[command]/usr/bin/docker run --name dockerpkggithubcomapacheincubatornuttxtestingnuttxcilinux_b04a6b --label c27d31 --workdir /github/workspace --rm -e DOCKER_BUILDKIT -e DOCKER_CONFIG -e BLOBDIR -e INPUT_RUN -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/incubator-nuttx/incubator-nuttx":"/github/workspace" docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux  "-c" "git -C sources/nuttx fetch --tags
cd sources/testing
./cibuild.sh -x testlist/arm-01.dat
"
2020-05-04T09:14:49.8181960Z From https://github.com/apache/incubator-nuttx
2020-05-04T09:14:49.8182567Z  * [new branch]      SocketCAN       -> origin/SocketCAN
2020-05-04T09:14:49.8182877Z  * [new branch]      master          -> origin/master
2020-05-04T09:14:49.8183187Z  * [new branch]      releases/9.0    -> origin/releases/9.0
2020-05-04T09:14:49.8183500Z  * [new tag]         nuttx-1.0       -> nuttx-1.0
2020-05-04T09:14:49.8183785Z  * [new tag]         nuttx-1.1       -> nuttx-1.1
2020-05-04T09:14:49.8184060Z  * [new tag]         nuttx-1.2       -> nuttx-1.2
2020-05-04T09:14:49.8184319Z  * [new tag]         nuttx-2.1       -> nuttx-2.1
2020-05-04T09:14:49.8184596Z  * [new tag]         nuttx-2.2       -> nuttx-2.2

The bad log:
2020-05-05T04:05:49.0182079Z ##[command]/usr/bin/docker run --name dockerpkggithubcomapacheincubatornuttxtestingnuttxcilinux_2d83e4 --label c27d31 --workdir /github/workspace --rm -e DOCKER_BUILDKIT -e DOCKER_CONFIG -e BLOBDIR -e INPUT_RUN -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/incubator-nuttx/incubator-nuttx":"/github/workspace" docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux  "-c" "git -C sources/nuttx fetch --tags
cd sources/testing
./cibuild.sh -x testlist/mips-riscv-x86-xtensa.dat
"
2020-05-05T04:05:55.2256950Z fatal: could not read Username for 'https://github.com': No such device or address
2020-05-05T04:05:55.2488909Z ====================================================================================
2020-05-05T04:05:55.2504708Z Configuration/Tool: hifive1-revb/nsh,CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL
2020-05-05T04:05:55.2644549Z ------------------------------------------------------------------------------------
2020-05-05T04:05:55.2645282Z   Cleaning...
2020-05-05T04:05:55.2647995Z   Configuring...
2020-05-05T04:05:55.2806083Z   Copy files
2020-05-05T04:05:55.3033737Z   Select CONFIG_HOST_LINUX=y
2020-05-05T04:05:55.3190231Z   Refreshing...
2020-05-05T04:05:59.7179859Z   Disabling CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL
2020-05-05T04:05:59.7198713Z   Enabling CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL
2020-05-05T04:06:00.0047408Z   Building NuttX...
2020-05-05T04:06:00.0188601Z make: *** [tools/Makefile.unix:270: /github/workspace/sources/nuttx/.version] Error 1
2020-05-05T04:06:00.0189736Z make: *** Waiting for unfinished jobs....
2020-05-05T04:06:00.1861137Z   Normalize hifive1-revb/nsh

Do you know why this happen?

I'm looking into it now.  It seems the github credentials are not getting persisted.

Good someone is checking this.
I was not confident about this last minute implementation.

@sonicyang Thanks for getting the port where it is.  I have really been wanting something stable I can run in the kvm.  Starting to look at what it would take to get PCIe in to enable virtio to test a lot more of the systems without being so tied to embedded hardware.

@btashton Glad to hear this. and have someone shared some point of view as mine. I am getting a PCI-e patch ready at the moment. We can start porting virt-io driver after this.

@sonicyang Thanks for getting the port where it is. I have really been wanting something stable I can run in the kvm. Starting to look at what it would take to get PCIe in to enable virtio to test a lot more of the systems without being so tied to embedded hardware.

For virtio support, maybe we can consider OpenAMP(actually, rpmsg is just an other virtio device like virito-block):
https://github.com/OpenAMP/open-amp/tree/master/lib/virtio
and here is the OpenAMP NuttX integration:
https://github.com/apache/incubator-nuttx/tree/master/openamp


Framework로 만들어보자

https://www.raywenderlich.com/17753301-creating-a-framework-for-ios
참고

iOS
xcodebuild archive -scheme BottomSheet -configuration Release -destination 'generic/platform=iOS' -archivePath ‘./build/BottomSheet.framework-iphoneos.xcarchive' SKIP_INSTALL=NO BUILD_LIBRARIES_FOR_DISTRIBUTION=YES
Simulator
xcodebuild archive -scheme BottomSheet -configuration Release -destination 'generic/platform=iOS Simulator' -archivePath ‘./build/BottomSheet.framework-iphonesimulator.xcarchive' SKIP_INSTALL=NO BUILD_LIBRARIES_FOR_DISTRIBUTION=YES

xcodebuild -create-xcframework -framework './build/CalendarControl.framework-iphonesimulator.xcarchive/Products/Library/Frameworks/CalendarControl.framework' -framework './build/CalendarControl.framework-iphoneos.xcarchive/Products/Library/Frameworks/CalendarControl.framework' -output './build/CalendarControl.xcframework'

Reference xcproject를 제거하고 XCFramework를 추가해서 사용


Android - Polygon only fills after zooming in

Bug
Rendering a Geojson component, with Multpolygons and a fill color of red, it renders only some of the polygons with the fill, and the more complex one with no fill, it only fills after I zoom in
I have installed the lib with expo install
testing on expo snack I saw that this bug only happens on android devices

Environment info
react-native info output:
System:
    OS: Windows 10 10.0.18362
    CPU: (4) x64 Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
    Memory: 2.33 GB / 7.95 GB
  Binaries:
    Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.15.2 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.2 - ~\AppData\Roaming\npm\npm.CMD
  SDKs:
    Android SDK:
      API Levels: 26, 27, 9
      Build Tools: 27.0.3, 28.0.3
      System Images: android-23 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-181.55<IP_ADDRESS>56338
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4

Library version: 0.27.1
Steps To Reproduce
Example on snack
https://snack.expo.io/Xneuy_yId

Run in Android device
Double touch to zoom in and see the polygon fills after that
...

Describe what you expected to happen:

Opening the app, waiting to the polyogon render with the properly fill

Reproducible sample code
import * as React from 'react';
import { Text, View, StyleSheet, Dimensions } from 'react-native';
import MapView, {Geojson} from 'react-native-maps';

// All the coordinates are available in the snack examaple https://snack.expo.io/Xneuy_yId
const BrazilGeojson = {
  "type": "FeatureCollection",
  "features": [
    { "type": "Feature", "properties": { "ADMIN": "Brazil", "ISO_A3": "BRA" }, "geometry": { "type": "MultiPolygon", "coordinates": [ [ [ [ -48.542591925999972, -27.816664320999834 ], [ -48.551869269999912, -27.819431247999887 ], [ -48.559803839999887, -27.818454684999907 ], [ -48.563791469999956, -27.817315362999878 ], [ -48.565093553999958, -27.813653253 ] ... ] } },
  ]
}

export default function App() {
  return (
    <View style={styles.container}>
      <MapView style={styles.map}>
        <Geojson geojson={BrazilGeojson} fillColor="red" />
      </MapView>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
  },
  map: {
    width: Dimensions.get('window').width,
    height: Dimensions.get('window').height
  }
});

in my case, Polygon doesn't show up at all
I got implementation from this example
android 29
react-native-maps: 0.27.1
System:
    OS: Windows 10 10.0.18362
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 9.41 GB / 15.95 GB
  Binaries:
    Node: 12.11.0 - ~\AppData\Local\Temp\yarn--1587373073393-0.4193863501487958\node.CMD
    Yarn: 1.22.4 - ~\AppData\Local\Temp\yarn--1587373073393-0.4193863501487958\yarn.CMD
    npm: 6.13.7 - C:\Program Files\nodejs\npm.CMD
    Watchman: 4.9.4 - C:\Development\tools\watchman\watchman\windows\bin\watchman.EXE
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-192.7<IP_ADDRESS>08749
  Languages:
    Python: 2.7.17 - C:\Python27\python.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ^0.62.1 => 0.62.1
  npmGlobalPackages:
    *react-native*: Not Found

@spacedog4 Did you find a solution ?

@JUNNNI no, I gave up on the app after that problem

same problem


Production build error in codebases using jsondiffpatch package with Vite version above @4.0.2

Describe the bug
I was trying to update Vite to the version of 4.1.1 in our company and I was facing an error saying:
Uncaught TypeError: Cannot read properties of undefined (reading 'close') from vendor.js file.
I knew it is coming from a node_modules deps, but I had no clue which package exactly and we got stuck. Finally I figured it out so I created a dummy project including that package: jsondiffpatch.
I downgraded vite to 4.1.1, 4.0.4, 4.0.3 - Failing
I downgraded vite to 4.0.2 and lower - Working
I feel there was a breaking change in releasing<EMAIL_ADDRESS>and if I had to guess I would say it's the commonjs update.
Reproduction
https://github.com/bpetii/Vite-issue-reproduction
Steps to reproduce

Run yarn or npm install
Run server by yarn run server command
Type localhost:3000 in a browser
Open devtools and see the error in the console tab

System Info
System:
    OS: macOS 12.5.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 6.08 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.7.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.15.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Safari: 15.6.1
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    vite: ^4.1.0 => 4.1.1

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

in 4.0.3 https://github.com/vitejs/vite/blob/v4.0.3/packages/vite/CHANGELOG.md, @rollup/plugin-commonjs is bumped to 24 from 23, the breaking change is https://github.com/rollup/plugins/pull/1358. You may can fix this by turning build.commonjsOptions. defaultIsModuleExports to true

@fi3ework I just tried out this option and no success unfortunately:/

I tested this with rollup.
It seems this doesn't work from 23.0.5.
https://stackblitz.com/edit/rollup-template-t6mulq?file=src%2Fmain.js
The change is https://github.com/rollup/plugins/pull/1363.

@sapphi-red Nice one! Thank you:)

I've added a new plugin to vite.config.js to solve this problem:
      {
        // https://github.com/vitejs/vite/issues/11986
        // https://github.com/rollup/rollup/issues/4861
        name: 'my:jsondiffpatch',
        configResolved() {
          const cjsFile = require.resolve('jsondiffpatch');
          const cjsCode = fs.readFileSync(cjsFile, 'utf-8');
          const cjsModifiedCode = cjsCode.replace(
            `var chalk = _interopDefault(require('chalk'));`,
            'var chalk = null;',
          );
          fs.writeFileSync(cjsFile, cjsModifiedCode);

          const esmFile = file.replace(
            path.join('jsondiffpatch.cjs.js'),
            path.join('jsondiffpatch.esm.js'),
          );
          const esmCode = fs.readFileSync(esmFile, 'utf-8');
          const esmModifiedCode = esmCode.replace(
            `import chalk from 'chalk';`,
            'const chalk = null;',
          );
          fs.writeFileSync(esmFile, esmModifiedCode);
        },
      },

I tested https://github.com/rollup/plugins/pull/1455 and it worked.

Beautiful! I hope Vite will release a new version including this new version of the rollup

https://www.npmjs.com/package/jsondiffpatch-rc
this seems to have this issue fixed


Query functions

This change is

tests/test_function.py line 246 at r1 (raw file):

    @pxt.query
    def lt_x(t, x: int) -> int:

I find this pattern of defining this test query function as a method within a test class confusing, what's the type of its first argument? (and what is the effect of the decorator in this context).
Can we just move it outside the class to make it clear what this is (I'm kind of using it as documentation)

tests/test_function.py line 246 at r1 (raw file):
Previously, mkornacker (Marcel Kornacker) wrote…
We can do that, but I'm not quite following: how will that make anything clearer? It's going to be the same symbol, but you'll use it without the 'self.'
The type of the first argument is Table. Happy to add that.
The effect of the decorator is to turn it into an object that can then be used with Table.query(), analogously to @udf.

What I mean is: if you didn't have that decorator, self.lt_x(1) would bind an instance of  TestFunction to t and thats what t would be. The decorator somehow makes this work with t being a table, but its really not obvious to me what's going on here.

Hi, I was accidentally mentioned here. Not sure how to opt out of the review on reviewable, or if i even have to.

Don't worry, I'm used to it. Putting it in monospace makes it not mention me, but if I'm tagged once then reviewable will see me as a mentionee and keep tagging me.


Extension request

Please add extensions for:
9anime,
Kissanime,
Kiss cartoon,
Watch cartoon online etc.

wco has been added the other ones have already been requested.


[swagger-parser-v3] Unable to load the attributes of the property which is of type “ref”

The Property "Parent" of model Category is of type "ref", it has additional attributes "Description" and "readonly" which not getting loaded by open api parser.
Description is showing null and readonly as false (ideally it should be true)
Category.Parent:
      description: A relationship to the 'mo.BaseMo' resource, or the expanded 'mo.BaseMo'
        resource, or the 'null' value.
      x-one-of-name: Category.Parent
      title: Parent category
      type: object
      properties:
        Parentid:
          type: integer
          format: int64
    Category:
      title: Pet category
      description: A category for a pet
      type: object
      properties:
        id:
          type: integer
          format: int64
          readOnly: true
          x-omitempty: true
        Parent:
          # A Relationship to Parent
          $ref: '#/components/schemas/Category.Parent'
          # The attributes below are for documentation purpose only. They are not used by OpenAPI tooling.
          description: |-
            A reference to a moBaseMo resource.
            When the $expand query parameter is specified, the referenced resource is returned inline.
          readOnly: true
        name:
          type: string
          pattern: '^[a-zA-Z0-9]+[a-zA-Z0-9\.\-_]*[a-zA-Z0-9]+$'
      xml:
        name: Category

Hi @Ghufz, reference objects cannot be extended with additional properties and any properties added is going to be ignored. Please take a look at Open API Specification:
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#reference-object
I hope this helps.


Fixed-position navbar obscures start of content of in-page fragment links

The fixed navbar is not compatible with in page bookmark links as clicking on a link that's supposed to take you to another point on a page causes that point on the page to be at the top of the viewport and as a result, the fixed navbar covers it. I'm able to duplicate this issue using BS3's fixed navbar example page.
Example: https://jsfiddle.net/sd5nhnhg/

Duplicate of #1768, although personally I agree we should try to address this somehow.
Retargeting at Bootstrap v4.

I have a fiddle that shows a possible fix by attaching a callback to the body. I'm open to criticism.
https://jsfiddle.net/a_matt_appeared/92ce7ne6/

Closing this as we currently have no plans to write generic JS to address this for in v4.


Frontend Assessment 1

Screenshots:

Metric
Value

alert_status
:white_check_mark: OK

bugs
3

code_smells
2

reliability_rating
D (at least 1 Critical Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


Performance

Seems to die on a single threaded hill with https://github.com/gocd/gocd

Track benchmarks here https://kaihendry.github.io/lesshero/dev/bench/

it's ok now, but i have messed up the chart generation


Import wizard not opening

Type: Bug
Selecting "Import wizard" on a database shows "Activating Extensions..." on the bottom left of the app but does not do anything else. It was working previously.
Azure Data Studio version: azuredatastudio 1.47.0 (Universal) (c7c2b2f21505562d21972d4c135119d00806db4f, 2023-11-07T17:18:22.205Z)
OS version: Darwin arm64 22.6.0
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
Apple M1 Max (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (0.23GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

admin-pack
Mic
0.0.2

admin-tool-ext-win
Mic
0.1.3

agent
Mic
0.49.0

dacpac
Mic
1.14.0

import
Mic
1.5.5

profiler
Mic
0.14.0

sql-search
Red
0.4.1

vscodeintellicode
Vis
1.2.1

poor-sql-formatter
WSR
0.1.0

@mrlife do you see the import extension getting activated if you go to the Output view and select "Extension Host" in the dropdown?

Also check if there are any errors when "Flat File Import Service" is selected in the Output view

@kisantia Thanks for the suggestions. I had already closed Azure Data Studio and don't see anything in those sections now. Is there a log history somewhere?
After 10 minutes or so, all of the Import wizard panes opened up at the same time. There was some kind of significant delay there.

might be similar to the slow download speed mentioned in https://github.com/microsoft/azuredatastudio/issues/24612#issuecomment-1806824359

might be similar to the slow download speed mentioned in #24612 (comment)

Yes, that could definitely be it. I have previously used the Import wizard, but maybe it was downloading an update to it?

Closing as issue is resolved and was related with network delay.


Don't define label encoder for binary logistic.

During testing #5277 , I found the generated model is extremely huge and slow.  The result is binary logistic doesn't require label to be strictly in {0, 1}.  Anything fits into sigmoid is accepted.  So running label encoding will simply return the labels in worse case.

@hcho3 It's a little bit tricky.  If we don't run np.unique, we don't know how many classes are there, hence we can't decide the objective.  But if we run it on a binary classification model, np.unique is not accurate.

But if we run it on a binary classification model, np.unique is not accurate

Why? You’d still get two classes in this case?

@hcho3 The issue is, y is not necessarily integers or categorical.  It can be floating point numbers.

@hcho3 We can throw a warning for non-discrete types.  But since the input varies as there are numpy, pandas, and possibly others may also works with Python duck typing.  Checking types is not easy either.  Do you have any suggestion?


[Feature]: new page under devops for terraform

Is your feature request related to a problem? Please describe.
https://www.nsccbpit.tech/devops
create the page for the subject, connect it to the card.
On the page provide all information and resources related to the concerned topic such as tutorials, documentation, youtube channels, articles, courses etc.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

assigned to @Shruti700

resolved


refactor: complete seed column definitions and move location

Sumamry
This pull request includes significant updates to the seeds configuration in the dbt_project.yml file and the addition of detailed seed configurations in the seeds/synthea/_sources.yml file. The main changes involve enabling the synthea schema and adding comprehensive column type definitions for various tables.
Updates to dbt_project.yml:

Removed table schema definitions.

Additions to seeds/synthea/_sources.yml:

Added detailed seed configurations with column type definitions for synthea output.

Why Bother?

Removes ambiguity
If using other seed files/larger seed files columns may not be sniffed in their entirety and this will result in errors downstream when an incorrect type (e.g. ZIP looks like a numeric type by default - causing issues when doing string parsing)

Thank you @katy-sadowski !! Some silly mistake from myself...


Bittrex API optionally supports asyncio and twisted (Python v2 and v3)

Example of asyncio (Python 3 only):
#!/usr/bin/env python3

import asyncio
from aiohttp import ClientSession
from bittrex.bittrex import Bittrex

key = "<>"
secret = "<>"

async def using_asyncio(request_url, apisign):
    async with ClientSession() as session:
        headers = {'apisign': apisign}
        async with session.get(request_url, headers=headers) as response:
            return await response.json()

async def main():
    bittrex = Bittrex(key, secret, using_asyncio)
    actual = await bittrex.get_balance('BTC')
    print(actual)

loop = asyncio.get_event_loop()
loop.run_until_complete(main())

Example of Twisted (Python 2 and 3). Requires treq (pip install treq):
#!/usr/bin/env python

from twisted.internet.task import react
from twisted.internet.defer import inlineCallbacks, returnValue
import treq
from bittrex.bittrex import Bittrex

key = "<>"
secret = "<>"

@inlineCallbacks
def using_twisted(request_url, apisign):
    headers = {'apisign': apisign}
    response = yield treq.get(request_url, headers=headers)
    result = yield response.json()
    returnValue(result)

@inlineCallbacks
def main(reactor):
    bittrex = Bittrex(key, secret, using_twisted)
    actual = yield bittrex.get_balance('BTC')
    print(actual)

react(main)

The original requests-based version works as usually:
#!/usr/bin/env python

from bittrex.bittrex import Bittrex

key = "<>"
secret = "<>"

bittrex = Bittrex(key, secret)
actual = bittrex.get_balance('BTC')
print(actual)

Using the code example above for asyncio in Python 3.6 I get this error message:
TypeError: object dict can't be used in 'await' expression
This error is raised by the line:
actual = await bittrex.get_balance('BTC')
Any ideas how to fix this?

@qlandman interesting - I see something - maybe relevant here. Does removing await solve the problem?


gltf model rendering error

Describe the bug
When rendering the gltf model, there is a rectangular area that is not rendered.
To Reproduce
Steps to reproduce the behavior:
Can be reproduced here：https://oasisengine.cn/0.4/docs/material-cn#unlitmaterial
Screenshots

Desktop (please complete the following information):

OS: [MacBook Pro (16-inch, 2019)]
Browser [版本 81.0.4044.138（正式版本） （64 位）]
Version [0.4.0 alpha.2]

The problem has disappeared


CODEOWNERS: Split test/ code owners

The @cilium/ci team (renamed in this pull request to @cilium/ci-structure) is in charge of the CI infra. (e.g., Jenkinsfile, scripts, etc.), including the Go helper functions and the overall structure of our tests, but it doesn't have the charge of the actual testing logic.
This pull request splits the test/ code owners across team to better represents the actual owners of the testing logic.
I have been unable to assign the following files to specific teams and they are therefore matched by the @cilium/ci catch-all at the moment:
/test/k8sT/Conformance.go
/test/k8sT/istio.go

:warning:  @aanm If we agree on the renaming, we will have to change the team's name when we merge this pull request.

test-me-please

After discussion with André and Maciej, I've reworked several files in test/ to enable further codeowner splitting. Please review commit by commit.
I've re-requested all your reviews because you should know better than to review a draft pull request :stuck_out_tongue_closed_eyes:

test-nightly

test-nightly

After discussion with Maciej, we decided to remove the Nightly test files (except for PoliciesNightly.go) because the associated pipelines have been deprecated a while ago. Maciej also suggested removing a couple stale Jenkinsfile; done in the commit before last.

test-me-please

retest-4.9


feat: Add disableIpv6 ServiceConfig option

Are you interested in adding the option to disable ipv6 for service advertisement? Our use-case is advertising a service that is bound to <IP_ADDRESS> e.g. it is not listening on a ipv6 address. I can look into adding tests if this is of interest. I'm not sure if any other places require modifications to support this option.

@gmaclennan Yes, makes sense. I'm going to update the property to disableIPv6 over disableIpv6 for standardisation and update the readme. Additional tests would be great.
Including in PR #44.


docs: generate c api list using doxygen

Import doxygen to generate C API documents.
The imported binary file is precompiled for linux, so it is only available on linux for now.

Could you add some instruction guides to run doxygen ?

Could you add some instruction guides to run doxygen ?

When //docs/doxygen:generate_docs is built, it generates html files in binary directory(bazel-bin/docs/doxygen/html).
So there are no other instructions to run doxygen. It runs every time when building on linux.
I just added the comment about this to the BUILD file.

How about changing the commit order of 4eb6d73 and 6f0bf97 since generation rule is dependent on main_page.md?

https://github.com/kroma-network/tachyon/pull/358/commits/748ec3c4ab00c0bd408ec2bb64e4a9d7e6611590
add example codes for document -> add example code for documentation


Create Invoke-ScratchDialog.ps1

function file

@LeeDowA do you work for facebook or something? :) We do pull requests per logic unit/topic all your prs will work only togeather why split them into multiple prs?

I know. But i did not know how to post all the changes together :). _/

I know. But i did not know how to post all the changes together :). _/

Thank you for your contributions :)

Thanks for the contributions but I can't accept them in their current form. These should have been in 1 PR that I could test before merging into our test branch.
Also, these were commited to main which I don't accept PR directly to. TEST Branch must be used.
Closing all PRs.


Throws exception on invalid input

When I request this url http://localhost:8440/some/table?search=da I get
ErrorException in Request.php line 34:
Illegal string offset 'value'

I would have expected it to show a 400, invalid input.

This is correct since invalid inputs were sent on the request.

There is no way to tell that this was invalid input from that exception though, as it is an ErrorException (or just a literal error in < php 7).

I think I will label this for enhancement and will add custom error handler for invalid inputs. Thanks!


Change acknowledger to be a triplet

{ack_module, ack_id, message_data}
ack_module.ack_message(ack_id, successful, failure)

Closed by #43.


Why does preserve default to true?

The only reason I can think of why preserve would default to true is developer convenience in modifying the selector in-browser, which seems a very flimsy reason. Is there something I haven’t thought of? Otherwise, it seems purely wasteful, duplicating rules to no advantage.

That’s a good question.
I want polyfill plugins to “fall forward” so that browsers supporting :any-link use the original code. With how gzipping works, the duplication this shouldn’t significantly impact output size. I do want the developer to be accustomed to the standards-driven markup in devtools, and the tradeoff here is duplication of the rule in devtools, right?
Now, when this polyfill is used with something like postcss-preset-env, then as Edge adopts :any-link and a project’s browserslist no longer needs support for IE or older Edge, then the fallbacks should disappear. That’s what I mean by “fall forward”.


[BUG] Neorg plugin lacks norg-meta treesitter parser

Field
Description

Plugin
neorg

Nixpkgs
unstable

Home Manager
unstable

[x] I have read the FAQ and my bug is not listed there.

Description
There are several issues that might be related to not having norg-meta  treesitter parser packaged or included with neorg on Nixvim.
Syntax highlighting for metadata field in norg files doesn't work. Here are screenshots, the one without highlights is norg file opened in nixvim with option configured Neorg, and the other is nixvim with Neorg-overlay

no norg-meta
norg-meta from overlay

The auto command for norg buffers that executes after writing a buffer trows an error:
Error detected while processing BufWritePost Autocommands for "*.norg":
Error executing Lua callback: ....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser f
or 'norg_meta' language, see :help treesitter-parsers
stack traceback:
        [C]: in function 'error'
        ....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: in function 'add'
        ...d-0.10.1/share/nvim/runtime/lua/vim/treesitter/query.lua:250: in function 'fn'
        ...pped-0.10.1/share/nvim/runtime/lua/vim/func/_memoize.lua:58: in function 'ts_parse_query'
        ...ua/neorg/modules/core/integrations/treesitter/module.lua:808: in function 'get_document_metadat
a'
        ...ges/start/neorg/lua/neorg/modules/core/tangle/module.lua:226: in function 'tangle'
        ...ges/start/neorg/lua/neorg/modules/core/tangle/module.lua:466: in function 'on_event'
        .../myNeovimPackages/start/neorg/lua/neorg/core/modules.lua:781: in function 'broadcast_event'
        ...s/start/neorg/lua/neorg/modules/core/neorgcmd/module.lua:298: in function <...s/start/neorg/lua
/neorg/modules/core/neorgcmd/module.lua:205>

And it seems that it also breaks the core.tangle module. Because when  core.tangle is enabled as a module in neorg the :Neorg journal today trows an error:

Minimal, Reproducible Example (MRE)

programs.nixvim = {
      enable = true;
      defaultEditor = true;
      plugins = {
        treesitter = {
          enable = true;
        };
        neorg = {
          enable = true;
          modules = {
            "core.defaults" = {
              __empty = null;
            };
            "core.dirman" = {
              config = {
                workspaces = {
                  general = "~/Norg";
                };
              };
            };
            "core.esupports.metagen" = {
              config = {
                timezone = "implicit-local";
                type = "empty";
                undojoin_updates = "false";
              };
            };
            "core.concealer" = {
              config = {
                __empty = null;
              };
            };
              "core.journal" = {
                config = {
                  workspace = "general";
                  journal_folder = "/./";
                };
              };
              "core.tangle" = {
                config = {
                  report_on_empty = false;
                  tangle_on_write = true;
                };
              };
            };
          };
        };
}

We don't do packaging itself in nixvim, that is handled upstream in nixpkgs. The neorg plugin doesn't include treesitter grammars and the packages treesitter doesn't contain https://github.com/nvim-neorg/tree-sitter-norg-meta. If you'd like to include that grammar you would have to follow the treesitter instructions for installing a custom grammar. https://nix-community.github.io/nixvim/plugins/treesitter/index.html?highlight=tree#installing-your-own-grammars-with-nixvim.
I implemented it myself if you want to see an example:
Grammar implementation: https://github.com/khaneliman/khanelivim/commit/ae3d016e4e8bafff38441b7dd400d70831407769
Installing Grammar: https://github.com/khaneliman/khanelivim/commit/8aeb4a4ecdc7cce804ea5e6cd2eab8d86ff504a8

eventually thanks to https://github.com/nvim-neorocks/rocks-treesitter.nvim/ we should be able to have the grammar as dependencies of the plugin when installed via luarocks (with Rocks.nvim), which is then picked up automatically by nixpkgs. Can't say when it will happen though but neorg author is a rocks.nvim maintainer

Tried the khaneliman's method. Works well. Hope that one day it could be bundled by default to make the experience more seamless. Thanks for support.


fix variable to use configure option

Realated with issue #715 ,

changed above part to use configuration option rather fixed value.

Codecov Report

Merging #736 into master will decrease coverage by 2.29%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #736     +/-   ##
=========================================
- Coverage   94.24%   91.95%   -2.3%
=========================================
  Files          32       32
  Lines        5579     5580      +1
=========================================
- Hits         5258     5131    -127
- Misses        321      449    +128

Impacted Files
Coverage Δ

databricks/koalas/frame.py
93.26% <100%> (-1.58%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
23.14% <0%> (-74.08%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
77.5% <0%> (-7.5%)
:arrow_down:

databricks/conftest.py
90.69% <0%> (-6.98%)
:arrow_down:

databricks/koalas/namespace.py
92.15% <0%> (-1.57%)
:arrow_down:

databricks/koalas/utils.py
97.24% <0%> (-0.69%)
:arrow_down:

databricks/koalas/testing/utils.py
77.35% <0%> (-0.63%)
:arrow_down:

databricks/koalas/internal.py
95.83% <0%> (-0.47%)
:arrow_down:

... and 1 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 d8a7fa4...2d25103. Read the comment docs.


Map CIM class 'BusbarSection' to IEC 61850 SCL equivalent

As an engineer
I want to map the IEC CIM 'Busbar' class to the IEC 61850 equivalent
So I can generate 61850 single line diagrams without manual editing
Background:
Mapping can be based on IEC/TS 62361-102

According to IEC 62361-102, a busbar is not recognized in IEC61850, it is just a logical node. This issue can be closed.


typo: Adapater -> Adapter

The second example uses adapter throughout, but the first one uses 3 different undeclared variables :confused:

Please file an issue for the other issue you're reporting @nschonni so @stevestein can take a look.


added CI workflow

This pr is related to #2

@SAtacker

@pingu-73 please could you do the same for ubuntu and windows?


Use username instead of displayname in GetListLockHandler

Feature Description
When listing lfs locks from command line, response contains display name in owner field
It could happen that the same display name may be used by several users and it becomes hard to distinguish owner of the lock without finding branch and file in web ui
This plugin relies on this field to determine if user can edit file and prevent conflicts later
https://github.com/ProjectBorealis/UEGitPlugin
Screenshots
No response

The current implementation is following the example from the Git LFS docs.
https://github.com/git-lfs/git-lfs/blob/main/docs/api/locking.md#successful-response
Would Fullname (Username) help?

Hello @KN4CK3R it would definitely help to distinguish users with same fullname, but in case of mentioned plugin it will require to place this combination in settings instead of just fullname, which, at least for me, seems more counter-intuitive.

Sure, but that's how the plugin works. What solution do you propose?

Why don't just use username?


5DcCqFpFkvDQLsMRabGbki26ducMP6zT2QBaxTmM5aGhhngf

5DcCqFpFkvDQLsMRabGbki26ducMP6zT2QBaxTmM5aGhhngf

Do you have specific details around this account?

Sorry. Sent not there
вт, 2 мар. 2021 г. в 21:20, Jaco Greeff<EMAIL_ADDRESS>
Do you have specific details around this account?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/polkadot-js/phishing/issues/145#issuecomment-789151129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO35BSPLNGFVBA2454OM3YDTBU273ANCNFSM4YPSET3A
.


DNS-01 solver for cert-manager

Implement the basic functionality for Phonebook to integrate with
Cert-Manager. This allows any users that have a domain configured with
Phonebook to leverages cert-manager and Let's Encrypt to create
wildcard SSL Certificates dynamically.
The DNS-01 solver should work out of the box for any supported Provider.
This means that any provider that gets added to Phonebook will
automatically support dynamic SSL certificate, including wildcard
certificates.
Here's a screenshot of the solver in action on my local machine using Cloudflare's DNS  Provider:

@ainsey11 It's a big PR with many changes, and don't feel like you have to review it, but I wanted to give you a chance to give it a look if you wanted to.

Wow! This is awesome
I'll give it a read through when I've finished work this afternoon :)


Get virtual funding working in web3torrent

Assuming that a ledger channel already exists (e.g. by creating manually), fund channels virtually in web3torrent.

Closing as this is too broad


Desync with test case (moved from LRU fixes)

This was originally reported in #1633, but occurs on master without the LRU tiling fixes patch.  It also appears to have popped up well after the last LRU patch on master, but YaLTeR has presented some evidence it's not entirely deterministic which commit hash causes it.  I only get it at/after cc170c2a17675aae6fdcfd12ecc97eaeba90b974, YaLTeR is pretty sure he saw it happen on the commit before.
#[cfg_attr(feature = "decode_test", interpolate_test(aom, "aom"))]
#[cfg_attr(feature = "decode_test_dav1d", interpolate_test(dav1d, "dav1d"))]
fn fuzz_desync_1(decoder: &str) {
  let w = 11;
  let h = 256;
  let speed = 10;
  let q = 200;
  let limit = 2;
  let min_keyint = 2;
  let max_keyint = 4;
  let low_latency = true;
  let bitrate = 16384;

  let mut dec = get_decoder::<u8>(decoder, w, h);
  dec.encode_decode(
    w,
    h,
    speed,
    q,
    limit,
    8,
    Default::default(),
    min_keyint,
    max_keyint,
    low_latency,
    bitrate,
    1,
    1,
  );
}

---- test_encode_decode::fuzz_desync_1_dav1d stdout ----
Encoding 11x256 speed 10 quantizer 200 bit-depth 8 bitrate 16384
Encoded packet 0
Decoding frame 0
Decoded. -> 0
Retrieving frame
Retrieved.
thread 'test_encode_decode::fuzz_desync_1_dav1d' panicked at 'assertion failed: `(left == right)`

Diff < left / right > :
 [
<    129,
>    121,
     255,
     101,
     0,
     6,
 ]

', src/test_encode_decode/mod.rs:145:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- test_encode_decode::fuzz_desync_1_aom stdout ----
Encoding 11x256 speed 10 quantizer 200 bit-depth 8 bitrate 16384
Encoded packet 0
Decoding frame 0
Decoded. -> 0
Retrieving frame
Retrieved.
thread 'test_encode_decode::fuzz_desync_1_aom' panicked at 'assertion failed: `(left == right)`

Diff < left / right > :
 [
<    129,
>    121,
     255,
     101,
     0,
     6,
 ]

', src/test_encode_decode/mod.rs:145:5

On master this causes the debug assert from #1611.
Originally posted by @YaLTeR in https://github.com/xiph/rav1e/pull/1633#issuecomment-528505316

Can anyone tell me how to run this test? "test_encode_decode::fuzz_desync_1_dav1d"
Should I add fn fuzz_desync_1() above to the rav1e?

In particular this affects all odd luma widths below 16, for 4:2:0 and 4:2:2.

As of #1583 this test case no longer causes a desync.


docs: extras formatting is hard to read

On https://docs.meltano.com/concepts/plugins#metadata-extra the formatting is hard to read because the code snippet from the previous sections blends with the section header. I think we should either add some space between the two or make the header background color different than the code background color.

@DouweM you did the CSS changes on the docs - what's a quick fix for this?

Looks much better now with Docusaurus: https://docs.meltano.com/concepts/plugins/#metadata-extra


Update README.md: Installation on Windows 10 and Other Unix-like Systems

For Windows 10, Microsoft Visual C++ 14.0 or greater is needed for multidict.
For Other Unix-like Systems, made formatting consistent with other sections.

Will submit another that includes updates to README.dev.md


Weight Percentage hd no effect.

I don't know why but Weight Percentage not had any different in image out put for me.
But my lora merge together nicely .But i want to adjust more with  Weight Percentage.

The adaptive merge focuses on dynamically combining models, adjusting weights automatically based on the characteristics of the LoRAs being merged. While the manual weight you specify is still considered, its impact might not always be as noticeable as you’d expect.
This is particularly true when there’s little conflict between the models or when the tensor properties naturally guide the merging process. So, you might see that changing the weight percentage doesn’t significantly alter the output image. The goal of adaptive merging is to find the best blend on the fly, which can sometimes make manual weight adjustments less obvious.
If you prefer having direct control over weight percentages without the adaptive adjustments, I’ve added a standard merge option.  If adaptive merging doesn’t quite meet your needs, switching to the standard merge will give you more control over how weights are applied.

Thank you for your update.
But i test new   standard merge option it still same output like adjusting weights.

The merging process is not just about creating a blend like mixing colors. Breaking it down into key elements can help better understand what I try to do with this AI Toolkit. Here’s what happens during merging and why it can offer more than simply using the models independently with live weights during generation.
1. Elements Involved in Merging LoRA Models
When you merge two LoRA models, you are essentially combining their internal components, mainly the tensors that hold the learned patterns of each model.

Tensors (Layers): Each tensor is a multidimensional array of numbers that stores the learned weights of the LoRA model. They represent the "knowledge" the model has learned from its training data, such as textures, colors, styles, and structural features.

Weights of Layers: In each LoRA model, layers have weights that determine how much influence that layer has on the overall output. These weights are what make each model unique in how it applies its patterns during generation.

When merging, these weights are combined, adjusted, or balanced between the two models. That’s where the merging strategy comes in:

Adaptive Merge: Combines weights based on the data inside each tensor, allowing for a dynamic and context-aware blend.

Fixed Weights Merge: Uses manually set percentages to control how much of Model A and Model B influences the final merged model.

2. What I Aim to Achieve with Merging

Unified Model: Merging combines the models into a single LoRA file, meaning all the learned patterns, weights, and features are baked into one set of tensors. This is more than just a mix; it’s about creating a unified entity where the features of each model are blended at a foundational level.

Integrated Features: I want the features of each model to interact and enhance each other in ways that don’t happen when using them separately. It’s like merging the DNA of both models to create a new organism that can express traits from both parents in a deeply integrated way.

3. Why Merging Is Different from Using Live Weights
When I use two LoRAs independently during image generation, I’m essentially telling the generation engine to apply each model’s influence at specific strengths (e.g., 60% from Model A, 40% from Model B). This works like applying filters on top of each other, with each adding its touch independently.
Merging fuses the models at the parameter level, meaning the patterns, textures, and styles are combined deeply. It’s like taking the DNA of both models and creating a new, integrated layer that expresses the traits of both models in a way that live weighting can’t replicate.
Example of Interaction:

Live Interaction: If Model A adds texture and Model B adds color, using them live means they affect the image independently.

Merged Integration: Merging these models allows the texture and color to blend more cohesively, creating effects where the texture influences how the color is applied, resulting in a unique look that feels more cohesive.

4. When Merging and Live Weighting Yield Similar Results

Similar or Redundant Features: If both LoRA models have similar learned features or overlapping patterns, merging them doesn’t create much new synergy. In some cases, merging behaves like a weighted average, which is what happens when using live weights to combine models during generation.

Linear Combinations: Basic merging strategies can sometimes act like straightforward blends. If the merged model doesn’t deeply integrate features, the output might be nearly identical to what I get by using the LoRAs independently with similar weights.

Minimal Feature Interaction: If the models’ effects are independent (e.g., one adjusts texture, the other adjusts lighting), merging and live weighting often produce similar outcomes because the features don’t deeply influence each other at the core level.

5. Unique Benefits of Merging

Deep Feature Fusion: Merging allows layers to interact at a fundamental level, creating new, cohesive effects. For example, merging can produce a detailed, realistic portrait overlaid with soft watercolor brush strokes—a hybrid effect that can’t be achieved by simply adjusting live weights.

More than Stacking: While live weighting is like stacking ingredients on a burger, merging transforms those ingredients into a new, unified layer—like blending them into a sauce, creating something more cohesive and uniquely expressive.

I hope that's help! :)
I am about to publish some very very experimental an even more advanced merge strategy this weekend along wiht example of data output grid.

@Anashel-RPG . Thanks for the explanations.


Interesting but unavailable

This feature seems really interesting and a time saver to manage VSTS.
But, even the documentation is from one month ago, I can't see the feature in my VSTS environment.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c9fa6b17-595a-05e9-e95d-b5c290127abb
Version Independent ID: 62524794-e27b-f9a2-7e80-cc1c3585706c
Content: Assign access levels and extensions to users by group membership
Content Source: docs/accounts/assign-access-levels-and-extensions-by-group-membership.md
Service: unspecified
GitHub Login: @douge
Microsoft Alias: chcomley

@GeoffreyDelmee Thank you for your comment! I've updated the doc accordingly, by adding a note about how the feature is still rolling out and you can expect to see it available within the next 3 weeks (as of today, 3/20).


Can i update the size?

Hello rendo,
I am trying to make this plugin responsive.
Is there a way that i can update the size ?
$('.pieanimation').on('click', function(e) {
    $('.chart').size('easyPieChart').update($xsize);
});

now we have 2017... is this feature now implemented?

@dilotec-2015 its 2017 and you still have not sent me a pull request. Open source means participation not demanding features. Comments like yours are the reason why people like me who dedicated some of their time to build free and open software are sick of supporting it.

hey everyone - you just need to target the Canvas element via CSS in a media-query:
@media screen and (max-width: 767px) {
.cs-wrap canvas[width="150"] {
width: 120px;
}
.cs-wrap canvas[height="150"] {
height: 120px;
}
}
you will need to restyle the font-sizes etc. - but its actually pretty easy - just a little extra typing (thanks for providing :-))

The fix that I used was that I added the easy-pie-canvas class to the canvas element, see THIS pull request I just submitted.
If you have this class name, you can simply do the following in your stylesheet:
.easy-pie-canvas {
  height: 50px;
  width: 50px;
}

But make sure you first remove the default widths/heights from the canvases:
$(".easy-pie-canvas").css("width", "");
$(".easy-pie-canvas").css("height", "");

Ran into this too. You can remove the canvases of your easy pie charts. Then destroy the data context. Then simply rebuild them. Works good for me.
Here's an example:
//  Note: This pattern is used to throttle window resize callbacks
let performResizeCallback;

$(window).resize(function() {

    clearTimeout(performResizeCallback);

    performResizeCallback = setTimeout(function() {

      //  Remove the pie charts canvases
      $('.pie-chart canvas').remove();

      let $pieCharts = $('.pie-chart');

      //  Remove the pie chart data contexts so it knows to rebuild them.
      //  It won't work without this
      $pieCharts.removeData('easyPieChart');

      //  Add logic here based on window size

      //  Adjust pie chart size dynamically
      $pieCharts.data("size", 75);

      //  Rebuild the pie charts
      $pieCharts.easyPieChart()
   }, 250);
});


Add missing base classes for some stubbed interfaces. Fix #901.

During our stubbing exercise, some interfaces didn't get any parent, so you can't really compile using them..

@DHowett-MSFT is added to the review. #Closed

@bbowman is added to the review. #Closed

:shipit:

Do you need to import Foundation or NSObject here?

Refers to: include/MapKit/MKMapSnapshotter.h:21 in 58c28c5. [](commit_id = 58c28c517a6ab57bc98b583dd738817b92b5ad3e, deletion_comment = False)

:clock1:

Likely yes, strangely it didnt break during build.

In reply to: 242160644 [](ancestors = 242160644)

Refers to: include/MapKit/MKMapSnapshotter.h:21 in 58c28c5. [](commit_id = 58c28c517a6ab57bc98b583dd738817b92b5ad3e, deletion_comment = False)

:shipit:


Consider aliases

Seeing that some artifact definitions cover a group of applications, might be useful to have aliases e.g. ChromeHistory as an alias for ChromiumBasedBrowsersHistory

Changes add aliases in https://github.com/ForensicArtifacts/artifacts/pull/464


[Bug] Sensor property renamed from device_state_attributes to extra_state_attributes in HA core

Describe the issue

device_state_attributes is deprecated and needs to be changed to extra_state_attributes
How to reproduce the issue

Run HA 2021.12.0+
Expected behavior

n/a
Screenshots

n/a
Software versions

Home Assistant version: 2021.12.0b1
openmediavault integration version: n/a
openmediavault software version: n/a

Traceback/Error logs

(<class 'custom_components.openmediavault.binary_sensor.OMVBinarySensor'>) implements device_state_attributes. Please report it to the custom component author.

(<class 'custom_components.openmediavault.sensor.OMVSensor'>) implements device_state_attributes. Please report it to the custom component author.

(<class 'custom_components.openmediavault.sensor.OMVFileSystemSensor'>) implements device_state_attributes. Please report it to the custom component author.

(<class 'custom_components.openmediavault.sensor.OMVDiskSensor'>) implements device_state_attributes. Please report it to the custom component author.

Additional context

n/a

thanks :)
btw, no need to spend extra time to open issue. PR is more then enough :)

I opened it as I didn't have time at the time to get to a PR hehe but 👍

I dont mind, its just to save your time :-)


Template change issue

Bug description
There is issue when I want to change template.
Steps to reproduce

On first setup choose 2-click template
add room, character, walkable area, assign character to the room
click setup

Expected vs observed behavior
There should be 4 templates but every second click there are only 2
Environment information (please complete):

MacOS Sonoma 14.2.1 (M1)
Godot 4.2.1
Popochiu 2 Beta 2

https://github.com/carenalgas/popochiu/assets/22888465/9a24eb88-4788-4b79-bfa4-f1deaa280503

Thanks for reporting the bug. I'll work on it tomorrow.


Tokenizer trimming causes offset matches if document content begins with whitespace

If a document starts with a whitespace character, trim() in tokenizer.js will remove those characters, causing the returned match data to be offset.
See this fiddle for a simple example

Thanks for the report @rgaiken ! I wrote up a fix in #418

I've just pushed 2.3.7 which includes the fix provided by @hoelzro .