text:
Blockchain progress stuck at zero percent

it seems like the blockchain sync process stucks. I have reboot many times already. can someone please help me solve the issues.
=======

cat raspiblitz.log

Running RaspiBlitz Bootstrap 1.7.1
Sun 21 Nov 03:25:57 GMT 2021

*** blitz.ssh.sh checkrepair
countKeyFiles(8)
OK: SSHD RUNNING
No HDMI switch found.
No FS EXPAND needed. needsExpansion(0) fsexpanded(1)
No SSHRESET switch found.
No UASP FIX needed (1st-try).
Waiting for HDD/SSD ...
total 604
drwxr-xr-x   2 root root   4096 Oct 28 11:00 .
drwxr-xr-x 118 root root   4096 Nov 20 01:12 ..
-rw-r--r--   1 root root 565189 Jan 31  2020 moduli
-rw-r--r--   1 root root   1580 Jan 31  2020 ssh_config
-rw-r--r--   1 root root   3250 Jan 31  2020 sshd_config
-rw-------   1 root root   1385 Oct 28 11:00 ssh_host_dsa_key
-rw-r--r--   1 root root    606 Oct 28 11:00 ssh_host_dsa_key.pub
-rw-------   1 root root    513 Oct 28 11:00 ssh_host_ecdsa_key
-rw-r--r--   1 root root    178 Oct 28 11:00 ssh_host_ecdsa_key.pub
-rw-------   1 root root    411 Oct 28 11:00 ssh_host_ed25519_key
-rw-r--r--   1 root root     98 Oct 28 11:00 ssh_host_ed25519_key.pub
-rw-------   1 root root   1823 Oct 28 11:00 ssh_host_rsa_key
-rw-r--r--   1 root root    398 Oct 28 11:00 ssh_host_rsa_key.pub
-rw-r--r--   1 root root    338 Mar  5  2021 ssh_import_id
wifiIsSet=0
hddBackupLocationAvailable=1
hddRestoreConfigAvailable=0
memRestoreConfigAvailable=0
wifiRestore=0
wifiBackup=0
No UASP FIX needed (2nd-try).
isMounted: 1
Skipping UASP deactivation ... cmdlineExists(1) hddAdapterUSB() hddAdapterUSAP(0)
HDD already part of system: 1
load configfile data
running LND users credentials update
SYNCING MACAROONS, RPC Password AND TLS Certificate
make sure LND app-data directories exist
copy macaroons to central app-data directory and ensure unix ownerships and permissions
make sure admin has a symlink at ~/.lnd to /mnt/hdd/app-data/lnd/
make sure LND conf is readable and symlinked
make sure TLS certificate is readable and symlinked
Checking if additional backup device is configured .. ()
No additional backup device was configured.
CLEANING TEMP DRIVE/FOLDER
OK: Temp cleaned
DONE BOOTSTRAP
================================================
cat raspiblitz.provision-setup.log
###################################
_provision.setup.sh
###################################
*** Prepare bitcoin ***
mkdir: cannot create directory ‘/mnt/hdd/bitcoin’: File exists
File Exists: /mnt/hdd/bitcoin/bitcoin.conf --> 1
setting PASSWORD B
OK -> RPC Password B changed
Reboot is needed
...
*** Start bitcoin (SETUP) ***

This can take a while ..

(0/50) checking if bitcoind is running ...
(1/50) checking if bitcoind is running ...
OK bitcoin startup successful
Prepare Lightning (lnd)
############## Setup LND
Creating new LND config ...
*** Init LND Service & Start ***
Starting LND Service ...
WALLET --> NEW
*** Copy LND Macaroons to user admin ***
SYNCING MACAROONS, RPC Password AND TLS Certificate
make sure LND app-data directories exist
copy macaroons to central app-data directory and ensure unix ownerships and permissions
make sure admin has a symlink at ~/.lnd to /mnt/hdd/app-data/lnd/
make sure LND conf is readable and symlinked
make sure TLS certificate is readable and symlinked
END Setup
=======================================
cat systemd.lightning.log | grep -i ERROR
1637467738 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637470100 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637473067 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637473794 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637473976 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637474703 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637480394 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637480576 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637482030 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637484391 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637484755 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637485118 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637485300 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486027 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486208 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486390 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486935 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637487117 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637490205 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637490568 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637491294 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637492021 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637492203 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637495290 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637495654 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496017 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496381 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496562 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637511211 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637513692 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
=====================================
cat systemd.lightning.log
SYSTEMD RESTART LOG: lightning (LND)
1637467010 STARTED
1637467071 STARTED
1637467131 STARTED
1637467192 STARTED
1637467253 STARTED
1637467313 STARTED
1637467374 STARTED
1637467434 STARTED
1637467495 STARTED
1637467555 STARTED
1637467616 STARTED
1637467676 STARTED
1637467737 STARTED
1637467738 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637467798 STARTED
1637467858 STARTED
1637467919 STARTED
1637467979 STARTED
1637468040 STARTED
1637468100 STARTED
1637468161 STARTED
1637468221 STARTED
1637468282 STARTED
1637468342 STARTED
1637468403 STARTED
1637468463 STARTED
1637468524 STARTED
1637468584 STARTED
1637468645 STARTED
1637468705 STARTED
1637468766 STARTED
1637468827 STARTED
1637468887 STARTED
1637468948 STARTED
1637469008 STARTED
1637469069 STARTED
1637469129 STARTED
1637469190 STARTED
1637469250 STARTED
1637469311 STARTED
1637469372 STARTED
1637469432 STARTED
1637469493 STARTED
1637469554 STARTED
1637469614 STARTED
1637469675 STARTED
1637469736 STARTED
1637469796 STARTED
1637469857 STARTED
1637469917 STARTED
1637469978 STARTED
1637470038 STARTED
1637470099 STARTED
1637470100 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637470160 STARTED
1637470220 STARTED
1637470281 STARTED
1637470342 STARTED
1637470402 STARTED
1637470463 STARTED
1637470523 STARTED
1637470584 STARTED
1637470644 STARTED
1637470705 STARTED
1637470765 STARTED
1637470826 STARTED
1637470886 STARTED
1637470947 STARTED
1637471008 STARTED
1637471068 STARTED
1637471129 STARTED
1637471189 STARTED
1637471250 STARTED
1637471310 STARTED
1637471371 STARTED
1637471431 STARTED
1637471492 STARTED
1637471552 STARTED
1637471613 STARTED
1637471673 STARTED
1637471734 STARTED
1637471795 STARTED
1637471855 STARTED
1637471916 STARTED
1637471976 STARTED
1637472037 STARTED
1637472098 STARTED
1637472158 STARTED
1637472219 STARTED
1637472280 STARTED
1637472340 STARTED
1637472401 STARTED
1637472461 STARTED
1637472522 STARTED
1637472582 STARTED
1637472643 STARTED
1637472703 STARTED
1637472764 STARTED
1637472824 STARTED
1637472885 STARTED
1637472945 STARTED
1637473006 STARTED
1637473067 STARTED
1637473067 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637473127 STARTED
1637473188 STARTED
1637473249 STARTED
1637473309 STARTED
1637473370 STARTED
1637473430 STARTED
1637473491 STARTED
1637473551 STARTED
1637473612 STARTED
1637473672 STARTED
1637473733 STARTED
1637473793 STARTED
1637473794 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637473854 STARTED
1637473915 STARTED
1637473975 STARTED
1637473976 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637474036 STARTED
1637474096 STARTED
1637474157 STARTED
1637474218 STARTED
1637474278 STARTED
1637474339 STARTED
1637474399 STARTED
1637474460 STARTED
1637474520 STARTED
1637474581 STARTED
1637474641 STARTED
1637474702 STARTED
1637474703 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637474763 STARTED
1637474823 STARTED
1637474884 STARTED
1637474945 STARTED
1637475005 STARTED
1637475066 STARTED
1637475126 STARTED
1637475187 STARTED
1637475248 STARTED
1637475308 STARTED
1637475369 STARTED
1637475429 STARTED
1637475490 STARTED
1637475551 STARTED
1637475611 STARTED
1637475672 STARTED
1637475732 STARTED
1637475793 STARTED
1637475853 STARTED
1637475914 STARTED
1637475974 STARTED
1637476035 STARTED
1637476095 STARTED
1637476156 STARTED
1637476216 STARTED
1637476277 STARTED
1637476337 STARTED
1637476398 STARTED
1637476458 STARTED
1637476519 STARTED
1637476579 STARTED
1637476640 STARTED
1637476700 STARTED
1637476761 STARTED
1637476821 STARTED
1637476882 STARTED
1637476943 STARTED
1637477003 STARTED
1637477064 STARTED
1637477125 STARTED
1637477185 STARTED
1637477246 STARTED
1637477306 STARTED
1637477367 STARTED
1637477427 STARTED
1637477488 STARTED
1637477548 STARTED
1637477609 STARTED
1637477669 STARTED
1637477730 STARTED
1637477790 STARTED
1637477851 STARTED
1637477911 STARTED
1637477972 STARTED
1637478032 STARTED
1637478093 STARTED
1637478154 STARTED
1637478214 STARTED
1637478275 STARTED
1637478335 STARTED
1637478396 STARTED
1637478456 STARTED
1637478517 STARTED
1637478577 STARTED
1637478638 STARTED
1637478698 STARTED
1637478759 STARTED
1637478819 STARTED
1637478880 STARTED
1637478940 STARTED
1637479001 STARTED
1637479061 STARTED
1637479122 STARTED
1637479182 STARTED
1637479243 STARTED
1637479303 STARTED
1637479364 STARTED
1637479424 STARTED
1637479485 STARTED
1637479546 STARTED
1637479606 STARTED
1637479667 STARTED
1637479727 STARTED
1637479788 STARTED
1637479848 STARTED
1637479909 STARTED
1637479969 STARTED
1637480030 STARTED
1637480091 STARTED
1637480151 STARTED
1637480212 STARTED
1637480272 STARTED
1637480333 STARTED
1637480393 STARTED
1637480394 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637480454 STARTED
1637480515 STARTED
1637480575 STARTED
1637480576 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637480636 STARTED
1637480696 STARTED
1637480757 STARTED
1637480818 STARTED
1637480878 STARTED
1637480939 STARTED
1637480999 STARTED
1637481060 STARTED
1637481120 STARTED
1637481181 STARTED
1637481241 STARTED
1637481302 STARTED
1637481363 STARTED
1637481423 STARTED
1637481484 STARTED
1637481544 STARTED
1637481605 STARTED
1637481665 STARTED
1637481726 STARTED
1637481786 STARTED
1637481847 STARTED
1637481908 STARTED
1637481968 STARTED
1637482029 STARTED
1637482030 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637482089 STARTED
1637482150 STARTED
1637482210 STARTED
1637482271 STARTED
1637482332 STARTED
1637482392 STARTED
1637482453 STARTED
1637482513 STARTED
1637482574 STARTED
1637482634 STARTED
1637482695 STARTED
1637482755 STARTED
1637482816 STARTED
1637482876 STARTED
1637482937 STARTED
1637482997 STARTED
1637483058 STARTED
1637483118 STARTED
1637483179 STARTED
1637483239 STARTED
1637483300 STARTED
1637483360 STARTED
1637483421 STARTED
1637483481 STARTED
1637483542 STARTED
1637483603 STARTED
1637483663 STARTED
1637483724 STARTED
1637483784 STARTED
1637483845 STARTED
1637483905 STARTED
1637483966 STARTED
1637484027 STARTED
1637484087 STARTED
1637484148 STARTED
1637484209 STARTED
1637484269 STARTED
1637484330 STARTED
1637484390 STARTED
1637484391 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637484451 STARTED
1637484512 STARTED
1637484572 STARTED
1637484633 STARTED
1637484693 STARTED
1637484754 STARTED
1637484755 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637484815 STARTED
1637484875 STARTED
1637484936 STARTED
1637484996 STARTED
1637485057 STARTED
1637485117 STARTED
1637485118 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637485178 STARTED
1637485239 STARTED
1637485299 STARTED
1637485300 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637485360 STARTED
1637485420 STARTED
1637485481 STARTED
1637485542 STARTED
1637485602 STARTED
1637485663 STARTED
1637485723 STARTED
1637485784 STARTED
1637485844 STARTED
1637485905 STARTED
1637485965 STARTED
1637486026 STARTED
1637486027 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486087 STARTED
1637486147 STARTED
1637486208 STARTED
1637486208 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486268 STARTED
1637486329 STARTED
1637486389 STARTED
1637486390 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486450 STARTED
1637486510 STARTED
1637486571 STARTED
1637486632 STARTED
1637486692 STARTED
1637486753 STARTED
1637486813 STARTED
1637486874 STARTED
1637486935 STARTED
1637486935 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637486995 STARTED
1637487056 STARTED
1637487117 STARTED
1637487117 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637487177 STARTED
1637487238 STARTED
1637487298 STARTED
1637487359 STARTED
1637487419 STARTED
1637487480 STARTED
1637487540 STARTED
1637487601 STARTED
1637487662 STARTED
1637487722 STARTED
1637487783 STARTED
1637487843 STARTED
1637487904 STARTED
1637487965 STARTED
1637488025 STARTED
1637488086 STARTED
1637488146 STARTED
1637488207 STARTED
1637488267 STARTED
1637488328 STARTED
1637488388 STARTED
1637488449 STARTED
1637488509 STARTED
1637488570 STARTED
1637488630 STARTED
1637488691 STARTED
1637488751 STARTED
1637488812 STARTED
1637488872 STARTED
1637488933 STARTED
1637488993 STARTED
1637489054 STARTED
1637489114 STARTED
1637489175 STARTED
1637489235 STARTED
1637489296 STARTED
1637489357 STARTED
1637489417 STARTED
1637489478 STARTED
1637489538 STARTED
1637489599 STARTED
1637489659 STARTED
1637489720 STARTED
1637489780 STARTED
1637489841 STARTED
1637489902 STARTED
1637489962 STARTED
1637490023 STARTED
1637490083 STARTED
1637490144 STARTED
1637490204 STARTED
1637490205 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637490265 STARTED
1637490325 STARTED
1637490386 STARTED
1637490446 STARTED
1637490507 STARTED
1637490567 STARTED
1637490568 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637490628 STARTED
1637490688 STARTED
1637490749 STARTED
1637490809 STARTED
1637490870 STARTED
1637490930 STARTED
1637490991 STARTED
1637491051 STARTED
1637491112 STARTED
1637491172 STARTED
1637491233 STARTED
1637491293 STARTED
1637491294 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637491354 STARTED
1637491415 STARTED
1637491475 STARTED
1637491536 STARTED
1637491596 STARTED
1637491657 STARTED
1637491717 STARTED
1637491778 STARTED
1637491838 STARTED
1637491899 STARTED
1637491960 STARTED
1637492020 STARTED
1637492021 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637492081 STARTED
1637492141 STARTED
1637492202 STARTED
1637492203 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637492263 STARTED
1637492323 STARTED
1637492384 STARTED
1637492444 STARTED
1637492505 STARTED
1637492565 STARTED
1637492626 STARTED
1637492686 STARTED
1637492747 STARTED
1637492807 STARTED
1637492868 STARTED
1637492928 STARTED
1637492989 STARTED
1637493049 STARTED
1637493110 STARTED
1637493170 STARTED
1637493231 STARTED
1637493292 STARTED
1637493352 STARTED
1637493413 STARTED
1637493473 STARTED
1637493534 STARTED
1637493594 STARTED
1637493655 STARTED
1637493715 STARTED
1637493776 STARTED
1637493836 STARTED
1637493897 STARTED
1637493957 STARTED
1637494018 STARTED
1637494078 STARTED
1637494139 STARTED
1637494200 STARTED
1637494260 STARTED
1637494321 STARTED
1637494381 STARTED
1637494442 STARTED
1637494502 STARTED
1637494563 STARTED
1637494624 STARTED
1637494684 STARTED
1637494745 STARTED
1637494805 STARTED
1637494866 STARTED
1637494926 STARTED
1637494987 STARTED
1637495047 STARTED
1637495108 STARTED
1637495168 STARTED
1637495229 STARTED
1637495290 STARTED
1637495290 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637495350 STARTED
1637495411 STARTED
1637495471 STARTED
1637495532 STARTED
1637495592 STARTED
1637495653 STARTED
1637495654 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637495714 STARTED
1637495774 STARTED
1637495835 STARTED
1637495896 STARTED
1637495956 STARTED
1637496017 STARTED
1637496017 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496077 STARTED
1637496138 STARTED
1637496198 STARTED
1637496259 STARTED
1637496319 STARTED
1637496380 STARTED
1637496381 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496441 STARTED
1637496501 STARTED
1637496562 STARTED
1637496562 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637496622 STARTED
1637496683 STARTED
1637496743 STARTED
1637496804 STARTED
1637496864 STARTED
1637496925 STARTED
1637496985 STARTED
1637497046 STARTED
1637497106 STARTED
1637497167 STARTED
1637497227 STARTED
1637497288 STARTED
1637497348 STARTED
1637497409 STARTED
1637497469 STARTED
1637497530 STARTED
1637497590 STARTED
1637497651 STARTED
1637497711 STARTED
1637497772 STARTED
1637497832 STARTED
1637497893 STARTED
1637497953 STARTED
1637498014 STARTED
1637498074 STARTED
1637498135 STARTED
1637498195 STARTED
1637498256 STARTED
1637498316 STARTED
1637498377 STARTED
1637498437 STARTED
1637498498 STARTED
1637498559 STARTED
1637498619 STARTED
1637498680 STARTED
1637498740 STARTED
1637498801 STARTED
1637498862 STARTED
1637498922 STARTED
1637498983 STARTED
1637499043 STARTED
1637499104 STARTED
1637499164 STARTED
1637499225 STARTED
1637499285 STARTED
1637499346 STARTED
1637499406 STARTED
1637499467 STARTED
1637499527 STARTED
1637499588 STARTED
1637499648 STARTED
1637499709 STARTED
1637499769 STARTED
1637499830 STARTED
1637499890 STARTED
1637499951 STARTED
1637500011 STARTED
1637500072 STARTED
1637500133 STARTED
1637500193 STARTED
1637500254 STARTED
1637500314 STARTED
1637500375 STARTED
1637500435 STARTED
1637500496 STARTED
1637500557 STARTED
1637500617 STARTED
1637500678 STARTED
1637500738 STARTED
1637500799 STARTED
1637500859 STARTED
1637500920 STARTED
1637500980 STARTED
1637501041 STARTED
1637501101 STARTED
1637501162 STARTED
1637501222 STARTED
1637501283 STARTED
1637501343 STARTED
1637501404 STARTED
1637501464 STARTED
1637501525 STARTED
1637501586 STARTED
1637501646 STARTED
1637501707 STARTED
1637501767 STARTED
1637501828 STARTED
1637501888 STARTED
1637501949 STARTED
1637502009 STARTED
1637502070 STARTED
1637502130 STARTED
1637502191 STARTED
1637502251 STARTED
1637502312 STARTED
1637502372 STARTED
1637502433 STARTED
1637502494 STARTED
1637502554 STARTED
1637502615 STARTED
1637502675 STARTED
1637502736 STARTED
1637502796 STARTED
1637502857 STARTED
1637502917 STARTED
1637502978 STARTED
1637503038 STARTED
1637503099 STARTED
1637503159 STARTED
1637503220 STARTED
1637503281 STARTED
1637503341 STARTED
1637503402 STARTED
1637503462 STARTED
1637503523 STARTED
1637503583 STARTED
1637503644 STARTED
1637503704 STARTED
1637503765 STARTED
1637503825 STARTED
1637503886 STARTED
1637503946 STARTED
1637504007 STARTED
1637504067 STARTED
1637504128 STARTED
1637504188 STARTED
1637504249 STARTED
1637504309 STARTED
1637504370 STARTED
1637504430 STARTED
1637504491 STARTED
1637504551 STARTED
1637504612 STARTED
1637504672 STARTED
1637504733 STARTED
1637504794 STARTED
1637504854 STARTED
1637504915 STARTED
1637504975 STARTED
1637505036 STARTED
1637505096 STARTED
1637505157 STARTED
1637505217 STARTED
1637505278 STARTED
1637505338 STARTED
1637505399 STARTED
1637505459 STARTED
1637505520 STARTED
1637505580 STARTED
1637505641 STARTED
1637505701 STARTED
1637505762 STARTED
1637505823 STARTED
1637505883 STARTED
1637505944 STARTED
1637506004 STARTED
1637506065 STARTED
1637506125 STARTED
1637506186 STARTED
1637506246 STARTED
1637506307 STARTED
1637506368 STARTED
1637506428 STARTED
1637506489 STARTED
1637506549 STARTED
1637506610 STARTED
1637506670 STARTED
1637506731 STARTED
1637506791 STARTED
1637506852 STARTED
1637506912 STARTED
1637506973 STARTED
1637507033 STARTED
1637507094 STARTED
1637507155 STARTED
1637507215 STARTED
1637507276 STARTED
1637507336 STARTED
1637507397 STARTED
1637507457 STARTED
1637507518 STARTED
1637507579 STARTED
1637507639 STARTED
1637507700 STARTED
1637507760 STARTED
1637507821 STARTED
1637507881 STARTED
1637507942 STARTED
1637508002 STARTED
1637508063 STARTED
1637508123 STARTED
1637508184 STARTED
1637508244 STARTED
1637508305 STARTED
1637508365 STARTED
1637508426 STARTED
1637508486 STARTED
1637508547 STARTED
1637508608 STARTED
1637508668 STARTED
1637508729 STARTED
1637508789 STARTED
1637508850 STARTED
1637508910 STARTED
1637508971 STARTED
1637509031 STARTED
1637509092 STARTED
1637509152 STARTED
1637509213 STARTED
1637509273 STARTED
1637509334 STARTED
1637509394 STARTED
1637509455 STARTED
1637509515 STARTED
1637509576 STARTED
1637509637 STARTED
1637509697 STARTED
1637509758 STARTED
1637509818 STARTED
1637509879 STARTED
1637509939 STARTED
1637510000 STARTED
1637510061 STARTED
1637510121 STARTED
1637510182 STARTED
1637510242 STARTED
1637510303 STARTED
1637510363 STARTED
1637510424 STARTED
1637510484 STARTED
1637510545 STARTED
1637510605 STARTED
1637510666 STARTED
1637510726 STARTED
1637510787 STARTED
1637510847 STARTED
1637510908 STARTED
1637510968 STARTED
1637511029 STARTED
1637511089 STARTED
1637511150 STARTED
1637511210 STARTED
1637511211 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637511271 STARTED
1637511332 STARTED
1637511392 STARTED
1637511453 STARTED
1637511513 STARTED
1637511574 STARTED
1637511634 STARTED
1637511695 STARTED
1637511755 STARTED
1637511816 STARTED
1637511876 STARTED
1637511937 STARTED
1637511997 STARTED
1637512058 STARTED
1637512118 STARTED
1637512179 STARTED
1637512239 STARTED
1637512300 STARTED
1637512360 STARTED
1637512421 STARTED
1637512481 STARTED
1637512542 STARTED
1637512602 STARTED
1637512663 STARTED
1637512723 STARTED
1637512784 STARTED
1637512845 STARTED
1637512905 STARTED
1637512966 STARTED
1637513026 STARTED
1637513087 STARTED
1637513147 STARTED
1637513208 STARTED
1637513268 STARTED
1637513329 STARTED
1637513389 STARTED
1637513450 STARTED
1637513510 STARTED
1637513571 STARTED
1637513631 STARTED
1637513692 STARTED
1637513692 ERROR: [lncli] could not load global options: unable to decode macaroon: empty macaroon data
1637513752 STARTED
1637513813 STARTED
1637513873 STARTED
1637513934 STARTED

I dont think in your case the problem is with the lightning part ... something seems to be off with bitcoind that makes lnd restart a lot of times. If this is a fresh setup I would recommend starting fresh again. Turn everything off, flash a new sd card and during then dont choose recover do with fresh setup and dont delete the HDD/SSD when asked (dont reuse blockchain).
If you run into the same problem, please write again.

Closing this issue .. please reopen if problem still exists.


text:
Refused to set unsafe header "User-Agent"

When map is loading or i zoom in/out i have this error in the console
Refused to set unsafe header "User-Agent" linked_hash_map.dart:21

Best Regards

Hi,
it seems that this problem has been fixed with flutter_map 6.0.1
When is the new version of the package compatible with the latest version of flutter_map coming out?
Regards

I'm facing the same issue, quite annoying to see hundreds of errors in the browser console.
@rorystephenson I see there was some work done to support flutter_map 6 in https://github.com/rorystephenson/flutter_map_supercluster/tree/v5
Is it possible to release it in the nearest future? Do you need help with testing?

Hey sorry for the slow response, agreed it's very annoying to be spammed with these messages.
I started work on a big overhaul when v6 was still WIP. Unfortunately it took a while for v6 to actually drop and when it did there were a lot more breaking changes added. For that reason I have a pretty set of changes in limbo (the v5 branch) which, last time I checked, had some bugs to iron out. I'm not actively working on projects that use this package right now but I'm still committed to maintaining it. I will try to get to finishing the v5 changes asap.

In the interest of moving forward I have just pushed 5.0.0-dev.1 which contains the latest changes I had locally.
If you find any issues let me know. I have a nagging feeling that there was something left to resolve but a quick test didn't uncover any problems.

Hi, I have installed version 5.0.0-dev.11 and at the moment I am not experiencing any problems
I had to make some code changes (MapOptions) but they depend on the fact that I updated flutter_map to version 6.0.0
If I encounter any problems I will let you know

At the moment I have not found any bugs on using the new released version 5.0.0-dev.1
With version 6 of flutter_map from the logs when debugging the app it is recommended to use "flutter_map_deletable_tile_provider"
To implement it among the parameters of the TileLayer should be added this
tileProvider: deleteableNetworkTileProvider()

source: gharchive/issue

authors: DeltaFox0018 lagivan rorystephenson

license_type: permissive

license_source: github-api


text:
ign_ros2_control fail to build [humble]

I encountered this issue when building this package on the humble branch.
.../gz_ros2_control/ign_ros2_control/src/ign_ros2_control_plugin.cpp:382:33: error: no matching function for call to ‘hardware_interface::ResourceManager::load_urdf(std::string&, bool, bool)’   382 |     resource_manager_->load_urdf(urdf_string, false, false);       |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
The error seems to be with one extra boolean argument on that load_urdf method. The log also show this:
/opt/ros/humble/include/hardware_interface/resource_manager.hpp:84:8: note: candidate: ‘void hardware_interface::ResourceManager::load_urdf(const string&, bool)’    84 |   void load_urdf(const std::string & urdf, bool validate_interfaces = true);       |        ^~~~~~~~~
check here
I deleted one of the "false" arguments and the package builds just fine

related with this other issue https://github.com/ros-controls/gz_ros2_control/issues/228


text:
Collect more rapid task info

As per title

@gavanderhoorn, can you reapprove the PR? I have just synced it with the base branch.

Thanks for the review @gavanderhoorn 👍

source: gharchive/pull-request


text:
Update tutorials to pipeline refactoring changes

Depends on

https://github.com/ros-planning/moveit2/pull/2457
https://github.com/ros-planning/moveit_resources/pull/191

Description

Update tutorials to latest changes introduced by https://github.com/ros-planning/moveit2/pull/2429 and https://github.com/ros-planning/moveit2/pull/2457

CI failure does not seem to be related to this PR  https://github.com/ros-planning/moveit2_tutorials/actions/runs/7121969390

CI failure does not seem to be related to this PR https://github.com/ros-planning/moveit2_tutorials/actions/runs/7121969390

Fix in moveit2 is here: https://github.com/ros-planning/moveit2/pull/2584

authors: sea-bass sjahr


text:
Migrate PID controllers

PID controllers are not migrated yet

https://github.com/ros-controls/ros2_controllers/issues/50
https://github.com/ros-controls/ros2_controllers/issues/51
https://github.com/ros-controls/ros2_controllers/issues/52

https://github.com/ros-simulation/gazebo_ros2_control/pull/25

authors: ahcorde bmagyar


text:
Use rosidl_get_typesupport_target()

Part of ros2/rosidl#606 which deprecates rosidl_target_interfaces() in favor of rosidl_get_typesupport_target()

Is someone with write access on this repo available to merge this in a few minutes?
The upstream pr ros2/rosidl#606 is ready to merge, but I'd like to merge all downstream PRs quickly to minimize the number of CI jobs with a CMake warning.

Done - saw the passing CI on ros2/rosidl#606

This is breaking Galactic builds because the master branch here is used for both Rolling and Galactic: https://github.com/ros/rosdistro/blob/d32b707cd78ba1c63972b870826a5b434abdc7ff/galactic/distribution.yaml#L1357. We should probably create a galactic/galactic-devel branch and point it to the commit before this one.

I created a galactic-devel branch pointing to the last commit before this one and opened https://github.com/ros2/ros2/pull/1166 as a proposed fix. We'll need to update the branch in the Galactic distribution file too.

Thanks for creating the branch! I'll do a bloom-edit now into galactic to update the tracks

As a note, I'm going to go with galactic branch to match other projects going forward - i've never been a fan of the -devel branch naming.

tracks is updated https://github.com/ros2-gbp/libstatistics_collector-release/blob/master/tracks.yaml#L41

This looks like this has broken some of the galactic nightlies.
For example: https://build.ros2.org/view/Gci/job/Gci__nightly-release_ubuntu_focal_amd64/30/console#console-section-13
And the error is:
10:39:27 --- stderr: libstatistics_collector
10:39:27 CMake Error at CMakeLists.txt:100 (rosidl_get_typesupport_target):
10:39:27   Unknown CMake command "rosidl_get_typesupport_target".
10:39:27
10:39:27
10:39:27 ---

Is this using a feature that should have only been targeted at rolling?

Is this using a feature that should have only been targeted at rolling?

Definitely. I think galactic CI should be fixed by ros/rosdistro#30426

Those have just been updated in rosdistro to use galactic branch instead of master - I don't know how long that would take to go through?
https://github.com/ros/rosdistro/pull/30411
https://github.com/ros/rosdistro/pull/30426

Thanks @emersonknapp and @sloretz. Looks like rosdep has been merged and everything should be happy by next go-around.

authors: christophebedard emersonknapp mjcarroll sloretz


text:
Update maintainers

Signed-off-by: Michael Jeronimo michael.jeronimo@openrobotics.org

Will do, thanks.


text:
e100_base-relase: 0.0.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository e100_base-relase to 0.0.0-0:

upstream repository: https://github.com/gaitech-robotics/e100_base.git
release repository: https://github.com/gaitech-robotics/e100_base-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.7.2
previous version for package: null

Holding for sync .

authors: BrightenLee clalancette

repo: ros/rosdistro


text:
distance_map: 0.1.0-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository distance_map to 0.1.0-1:

upstream repository: https://github.com/artivis/distance_map.git
release repository: https://github.com/artivis/distance_map-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: null

distance_map
* Initial release

distance_map_core
* Initial release

distance_map_deadreck
* Initial release

distance_map_msgs
* Initial release

distance_map_node
* Initial release

distance_map_opencv
* Initial release

distance_map_rviz
* Initial release

distance_map_tools
* Initial release

It is a little generic but it's solidly descriptive and not overly broad so I'm ok with it.

authors: artivis tfoote


text:
pangolin: 0.9.0-2 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository pangolin to 0.9.0-2:

upstream repository: https://github.com/stevenlovegrove/Pangolin.git
release repository: https://github.com/ros2-gbp/Pangolin-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.9.0-1

This is a re-release of https://github.com/ros/rosdistro/pull/39541 with the rpm package, now that its remaining dependency, libxkbcommon-dev, is available in rosdep (https://github.com/ros/rosdistro/pull/39540).

@christian-rauch we are holding all ROS 2 releases for a little bit so that we can deploy initial noble and trixie repositories, look for updates here: https://discourse.ros.org/chat/c/packaging-and-release-management/11

authors: christian-rauch mjcarroll


text:
pr2_map_navigation_app: 1.0.2-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository pr2_map_navigation_app to 1.0.2-0:

upstream repository: https://github.com/PR2/pr2_map_navigation_app.git
release repository: https://github.com/pr2-gbp/pr2_map_navigation_app-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.18
previous version for package: null

pr2_map_navigation_app
* Fixes
* Contributors: TheDash

This needs a rebase to be mergable.

authors: TheDash dirk-thomas


text:
carl_bot: 0.0.17-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository carl_bot to 0.0.17-0:

upstream repository: https://github.com/WPI-RAIL/carl_bot.git
release repository: https://github.com/wpi-rail-release/carl_bot-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.19
previous version for package: 0.0.16-0

carl_bot

No changes

carl_bringup
* limited output on phidgets initialization, added moveit stuff to carl_bringup launch
* Contributors: David Kent

carl_description
* Added an end effector frame for the JACO
* Contributors: David Kent

carl_dynamixel

No changes

carl_interactive_manipulation
* Added new recognition calls to carl_interactive_manipulation (note that pickup is still in progress and will not currently work)
* updted message
* Updated to reflect moving some messages from rail_segmentation to rail_manipulation_messages
* Switched im to use new rail_manipulation_msgs
* Contributors: David Kent, Russell Toris

carl_phidgets
* limited output on phidgets initialization, added moveit stuff to carl_bringup launch
* Contributors: David Kent

carl_teleop

No changes

carl_tools

No changes

This PR reverts a number of changes to other repos (ros-infrastructure/bloom#252). Please either update this PR or create a new one with bloom-release -p.

Replaced with https://github.com/ros/rosdistro/pull/7623

authors: dirk-thomas rctoris


text:
a period missed

Just a tiny fix.
NOTE: https://github.com/osrf/ros2_test_cases/issues/966#issuecomment-1547096162

@Yadunund can you help us to merge this?

authors: fujitatomoya iuhilnehc-ynos


text:
Transparency not applying

Hi team,
I'm attempting to enable a transparent status line with the plugin turned on, but I can't seem to get it working.
I am using alacritty with transparency on:

With set -g @rose_pine_bar_bg_disable "on", the bar just turns to black.
Here's my tmux config: https://gist.github.com/haydenrou/071ed660c7648fc80a8dabb8c9dfda25 (I noticed I spelt pine wrong somewhere in there and fixed that)
I've tried playing around with the options quite a bit, and without the plugin activated, it is transparent.

I'd recommend, as tmux reads the file sequentially, that you put the plugin optons after the plugin definition, like this (just a snippet of how the end of the config file you linked should be):
# List of plugins
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-sensible'

set -g @plugin 'rose-pine/tmux'

set -g @rose_pine_variant 'moon'

# ### Theming Settings ###
# # set -g @rose_pine_date_time '' # It accepts the date UNIX command format (man date for info)
set -g @rose_pine_user 'on' # Turn on the username component in the statusbar
# set -g @rose_pine_bar_bg_disable 'on'
# # If set to 'on', disables background color, for transparent terminal emulators
set -g @rose_pine_bar_bg_disabled_color_option '0'
# # If @rose_pine_bar_bg_disable is set to 'on', uses the provided value to set the background color
set -g @rose_pine_bar_bg_disable "on"
# # It can be any of the on tmux (named colors, 256-color set, `default` or hex colors)
# # See more on http://man.openbsd.org/OpenBSD-current/man1/tmux.1#STYLES

set -g @rose_pine_disable_active_window_menu 'on' # Disables the menu that shows the active window on the left
set -g @rose_pine_show_current_program 'on' # Forces tmux to show the current running program as window name
set -g @rose_pine_show_pane_directory 'on' # Forces tmux to show the current directory as window name
set -g @rose_pine_session_icon '' # Changes the default icon to the left of the session name
set -g @rose_pine_current_window_icon '' # Changes the default icon to the left of the active window name
set -g @rose_pine_folder_icon '' # Changes the default icon to the left of the current directory folder
set -g @rose_pine_username_icon ' ' # Changes the default icon to the right of the hostname
set -g @rose_pine_date_time_icon '󰃰' # Changes the default icon to the right of the date module
set -g @rose_pine_window_status_separator "  " # Changes the default icon that appears between window names

set-option -g status-style bg=default

# turn on vi mode by pressing prefix-[
set-window-option -g mode-keys vi
bind-key -T copy-mode-vi v send-keys -X begin-selection
bind -T copy-mode-vi y send-keys -X copy-pipe-and-cancel 'xclip -in -selection clipboard'

# Initialize TMUX plugin manager (keep this line at the very bottom of tmux.conf)
run -b '~/.tmux/plugins/tpm/tpm'

It's a matter of load order :)

I tried that with the same result unfortunately (updated the gist for clarification)

Welp, then we are at a crossroad. I have tested with your config file (excluding the zsh line because I use bash), entering and exiting multiple times from tmux, and the background of the bar is not there :)
Can you tell me the version of tmux you're using?

Hmm, that's so strange!
I'm running tmux 3.3a .
I'll keep debugging and see

I finally figured this out and it really reminded me I should just delve into the source-code more often.
As stated here the @rose_pine_bar_bg_disabled_color_option is used to set the bg color. The default in the README docs is 0 seemingly for transparency, and I when I tried changing this to another random number (i.e. 123) I got an initialization method - so I didn't think to look any further.
After trying a plethora of different things, I figured that I could just set this to default. This provides the same functionality as setting set-option -g status-style bg=default, but within the plugin.
I'm still not sure why adding set-option -g status-style bg=default below didn't work, but setting it manually through Ctrl-b+:set-option -g status-style bg=default did. Perhaps it's how TPM loads plugins.
@mrs4ndman Is there a reason the docs specifies using 0 as the default value for @rose_pine_bar_bg_disabled_color_option? I'm assuming so - but regardless, think a PR to add details to the docs and clarify transparency could be useful, if you don't mind me submitting that (mainly just to state that default is a valid option for transparency here). I can change the 0 too, if necessary (but I assume 0 is for a reason).

repo: rose-pine/tmux

license: MIT


text:
Fix Table::grow; more tests

API CHANGE: Add init parameter to Table::grow/wasm_table_grow.
API CHANGE: Make init parameter default to nullptr for Table::make and Table::grow.
Correctly handle nullptr as init value in Table::make/wasm_table_make.
Check against max size for Table::grow/wasm_table_grow, since V8 does it in a different place.
Add tests for Table::make/wasm_table_make and Memory::make/wasm_memory_make.
Add tests for growing at and beyond max limit.

This probably subsumes PR #39.

@lostman, FYI.

repo: rossberg/wasm-c-api


text:
🛑 Wiki is down

In e175fa8, Wiki (https://wiki.roundup-tracker.org) was down:

HTTP code: 503
Response time: 1138 ms

Resolved: Wiki is back up in cdbbbee.

repo: rouilj/RoundupAssets


text:
[refactor] Optimize LLM execution by moving source retrieval to server-side

Changes

Modified LLM execution flow to handle source code retrieval on server-side
Implemented source index-based retrieval system
Removed direct source code transmission from client
Added server-side source code embedding in prompts

Why
This change improves the system architecture by:

Reducing network traffic between client and server
Improving security by keeping source code handling server-side
Centralizing source code management
Creating a more efficient source retrieval process using indices

Verification Steps
The following operations should work without regression:

[ ] 1. Text Generator Node

[ ] Place a Text Generator node
[ ] Enter text and press Push Value
[ ] Verify text generation works

[ ] 2. Web Search Node

[ ] Place a Web Search node
[ ] Enter text and press Push Value
[ ] Verify search results are generated

[ ] 3. Prompt Node Source Operations

[ ] Add text content and verify text generation
[ ] Add file and verify text generation
[ ] Add Text Generator artifacts and verify text generation
[ ] Add Web Search artifacts and verify text generation

@toyamarinyon https://github.com/route06inc/giselle/pull/57#issuecomment-2445866716 was merged into the main branch an hour ago.
Could you please merge or rebase it with the latest main branch to resolve the Queued status in GitHub Actions?

I'm not sure, It might be better to cancel the job that is currently running.Something is wrong. It is very strange. Something is wrong.
https://github.com/route06inc/giselle/actions
e.g. https://github.com/route06inc/giselle/actions/runs/11588098366/job/32261395602

There may be a problem with GitHub Actions.
https://x.com/search?q=github&src=typed_query&f=live
But I can't see the fault at https://www.githubstatus.com/ .

There may be a problem with GitHub Actions. https://x.com/search?q=github&src=typed_query&f=live

Got it! Let's wait for the recovery. 🙏

I cancelled all jobs because they could be charged. But jobs are still queued. 😅
https://github.com/route06inc/giselle/actions

@shige All checks have passed successfully!

Thanks, I'll review it right now!

authors: masutaka shige toyamarinyon


text:
Update to Hyper 0.14 and Tokio 1

Keeping in line with dep updates, removed broken example since I can't fix stream_body

Send PR to develop branch.

Send PR to develop branch.

Need to update the PR as we released the new version of Routerify.

I was gonna do this by myself lucky i saw your pr first. @rousan  approximately when do you think we will have a 2.0 release so this can be merged ?

@NikosEfthias An updated version of these drop-in middlewares are to be released when a new major version release of Routerify is made.
Please continue the discussion here.

@seanpianka have you tested this against v2 ?

The Cargo.toml needs to be updated to use v2, @NikosEfthias. Once that change is merged to master, we should then create a new release on crates.io.

authors: NikosEfthias rousan seanpianka

repo: routerify/routerify-cors


text:
Inference infos

Hi! I found this repository reading the official paper, it was a very interesting paper!
I want to know how perform your architecture for a specific ball object into a moving scenario. To be more precise I want to track a small ball into a foosball table.
Do you have any advise?
Thanks :)

Hi, thanks! Have you just tried running this codebase on your data? It could work as it is. Some problems can arise if your ball is too small (a few pixels) or the camera is shaking a lot. On the other hand, you can also finetune this architecture to a single specific ball, e.g. by setting the thresholds or even retraining. You can also share your data with me, and I can take a look.
Best,
Denys

authors: lorenzoloretucci rozumden

repo: rozumden/FMODetect


text:
🛑 Raj Haraniya - Portfolio is down

In e895315, Raj Haraniya - Portfolio (https://rajharaniya.me) was down:

HTTP code: 403
Response time: 848 ms

Resolved: Raj Haraniya - Portfolio is back up in af3c155 after 8 minutes.

repo: rpharaniya/websites-uptime-monitor


text:
Version 0.4.3 that comes with git bash 2.14.1 cannot execute cmd.exe

This was tested on windows 7 pro with latest updates.
Every time I type winpty cmd.exe in git bash prompt, it will exit immediately with no error message. I also notice that it creates an .exe subdirectory in the current directory, because after the second winpty cmd.exe it reports an error: "A subdirectory or  file .exe already exists"
Other commands such as python.exe/node.exe/powershell.exe seem to work fine.

The problem reproduces in MSYS2 without the Git-for-Windows packaging.  The root cause is this MSYS2 patch which uses backslashes instead of forward slashes.
https://github.com/Alexpux/MSYS2-packages/blob/ec549593cd9874c801b3a95106d032d23b3ac0b8/winpty/0002-fix-path-conversion.patch#L38
Maybe the fix for https://github.com/rprichard/winpty/issues/81 / https://github.com/rprichard/winpty/issues/98 probably contributes to the issue by making winpty use absolute paths more often.
With the MSYS2 patch, winpty-agent.exe runs C:/Windows/System32/cmd.exe.  With upstream winpty, it would instead run C:\Windows\System32\cmd.exe.  cmd.exe does not like being started with forward slashes.  It seems to interpret the absolute path as the command /c md .exe.  e.g.:
C:\Users\rprichard>C:/Windows/System32/cmd.exe
A subdirectory or file .exe already exists.

C:\Users\rprichard>cmd /cmd.exe
A subdirectory or file .exe already exists.

C:\Users\rprichard>cmd /c md .exe
A subdirectory or file .exe already exists.

Upstream winpty should use MSYS2's special path conversion somehow, but AFAIK, there's no public API for it exposed from MSYS-2.0.dll.  I suppose I should just copy what MSYS2-packages does and import the CC0-marked path_conv.cpp files.

Related to https://github.com/rprichard/winpty/issues/88.

Hello Richard,
what needs to be done to fix this? Do you need some help with this?

Might be related: rprichard/winpty#127

Any progress?

+1

As pointed by https://github.com/msys2/MSYS2-packages/issues/411#issuecomment-372585320 , I managed to fix this issue by not installing the package from the msys2 repository (i.e., pacman -S winpty), but downloading directly the binary from the winpty release page: https://github.com/rprichard/winpty/releases

pacman -R winpty
wget https://github.com/rprichard/winpty/releases/download/0.4.3/winpty-0.4.3-msys2-2.7.0-x64.tar.gz
tar -xvf winpty-0.4.3-msys2-2.7.0-x64.tar.gz
cd winpty-0.4.3-msys2-2.7.0-x64/bin
cp * /usr/bin

Now it correctly opens cmd.exe from bash with $ winpty cmd.exe.

authors: Noxware evandrocoan lanoxx niklasholm rprichard tarruda vipzen

repo: rprichard/winpty

license: mit

license_source: bigquery


text:
-C option won't work with a symlink inside WSL

After creating a new symlink inside WSL (e.g. ln -s /mnt/c/Users/winUser /home/wslUser/WinHome) I'm unable to open a new shell that automatically starts at that folder with a wslbridge.exe -C /home/wslUser/WinHome, all it does is to drop me back into my Windows home folder.
I'll be glad to provide any further info or help if needed.

Windows full version? Wslbridge version? Any extra permission? Which distro and it's version?

Windows full version? Win10 Pro 1803
Wslbridge version? Not sure about that, there is no --v option for it. It's the one bundled with ConEmu 180626, if that's of any help.
Any extra permission? No, as far as I know.
Which distro and it's version? Ubuntu 18.04 LTS (the one from Windows Store).

repo: rprichard/wslbridge


text:
🛑 dumb.lunar.icu is down

In 59cd128, dumb.lunar.icu (https://dumb.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dumb.lunar.icu is back up in c743776 after 12 minutes.

repo: rramiachraf/dumb-instances


text:
[documentation] how to properly listen to providers from other Notifiers?

import 'package:flutter_riverpod/flutter_riverpod.dart';
import 'package:zero_loss_compress/convertion_stats.dart';

final batchSizeProvider = NotifierProvider<BatchSizeNotifier, int>(() {
  return BatchSizeNotifier();
});

final progressProvider = NotifierProvider<ProgressNotifier, int>(() {
  return ProgressNotifier();
});

class BatchSizeNotifier extends Notifier<int> {
  @override
  int build() {
    return 0;
  }

  void setBatchSizeAndResetConversionState(int batchSize) {
    state = batchSize;
    ref.read(progressProvider.notifier).reset();
    ref.read(convertionStatsStateProvider.notifier).reset();
  }
}

class ProgressNotifier extends Notifier<int> {
  @override
  int build() {
    return 0;
  }

  void increment() {
    state = state + 1;
  }

  void reset() {
    state = 0;
  }
}

What is the proper way to modify ProgressNotifier to listen to batchSizeProvider and to reset itself when BatchSizeNotifier changes, rather than let BatchSizeNotifier call the reset function?
Is there any documentation about how to properly listen to providers from other Notifiers?
(it not maybe create one)

Are you looking for ref.watch?
class ProgressNotifier extends Notifier<int> {
  @override
  int build() {
    ref.watch(batchSizeProvider);
    return 0;
  }
}

I did try with ref.listen instead of ref.watch because I might want to call some other function instead of just resetting.
But I think ProgressNotifier is lazy build so the listen happens only if it has been evaluated first.
Can we force ProgressNotifier to build when batchSizeProvider is build so it can listen to it as soon as available ?

Let me guess: Your UI never listens to progressProvider
Providers rebuild only if they are in use.

@rrousselGit if I call BatchSizeNotifier.setBatchSizeAndResetConversionState(16) the listen/watch works.
Then, if I call BatchSizeNotifier.setBatchSizeAndResetConversionState(16) again, it doesn't work because state == 16. Is there any way to listen for state assignments rather than value change?

@rrousselGit also, if a provider listen to another provider and the info it carries is not shown on the screen, I don't think it's safe to assume that the provider no longer needed. showing it's value in a later stage would result in a wrong value.
Let's imagine a provider that tracks how many times a button is pressed and displays it on another screen. if you don't listen when you are not displayed, how are things supposed to work here?

authors: rrousselGit stephane-archer

repo: rrousselGit/riverpod


text:
RLP-1037: invoice minimum amount

This PR implements RLP-1037, which is about not allowing the generation of an invoice with more precision than a 1p BTC or its equivalent in ETH/token, as defined per BOLT #11.

@JONAF2103 @marcosmartinez7 @mauricioirace
please help me out in testing the API manually to make sure all scenarios are covered before moving this to QA (specifically: not allowing invalid amounts based on BOLT #11)
thanks :pray:

repo: rsksmart/lumino


text:
Use the latest Go release on Travis

I'm proposing to move to the latest Go release. Hopefully no one is against this change 🙌

It passed. Thanks!

authors: cristaloleg jjeffcaii

repo: rsocket/rsocket-go


text:
Possibility to support Chinese codecs?

Based on this Stack Overflow question I looked into support for Chinese character encodings.
The GB* series of codecs are, like UTF-8, a variable width encoding. The example in the question reads:
Ã¨Â¢â€¹Ã¨Â¢âdcx€¹Ã¤Â¸Å½Ã¦Å“â€¹Ã¥Ââ€¹Ã¤Â»Â¬Ã§â€ÂµÃ¥ÂÂÃ¥â€¢â€

which can be decoded using GB* encodings to varying degrees of success:
>>> print text.encode('windows-1252').decode('gb2312', 'replace')
猫垄�姑�⑩dcx�盲赂沤忙��姑ヂ�姑ぢ宦�р�得ヂ�氓�⑩�
>>> print text.encode('windows-1252').decode('gbk', 'replace')
猫垄鈥姑�⑩dcx�盲赂沤忙艙鈥姑ヂ鈥姑ぢ宦�р�得ヂ�氓鈥⑩�
>>> print text.encode('windows-1252').decode('gb18030', 'replace')
猫垄鈥姑⑩dcx�盲赂沤忙艙鈥姑ヂ鈥姑ぢ宦р�得ヂ氓鈥⑩�
>>> print text.encode('windows-1252').decode('big5', 'replace')
癡瞽�嘔阬Ｔdcx�瓣繡鬚疆��嘔氐�嘔刈鄞珍把�腕氐倦疇�Ｔ�

Unfortunately I do not know which one of these is closest to the original, but that doesn't matter all that much. What'd be needed is an analysis of how GB* encodings pushed through the CP1252 / Latin-1 sieve can be distinguished from UTF-8 Mojibakes and handled fix_one_step_and_explain().
Is supporting these codecs feasible?

I don't think it would be possible to support GB* without a huge loss in accuracy. The problem is that most sequences of bytes can be decoded as GB18030, for example, regardless of whether they're actually intended to be GB18030. (Are you sure the text in that example is meant to be Chinese at all?)
The thing that makes ftfy possible is that most sequences of bytes aren't valid UTF-8, so when you can decode something as UTF-8, it's a strong signal that it's the right thing to do.
At one point I looked into trying to support the Japanese encoding Shift-JIS. Even though it has fewer valid sequences than the GB* encodings, I was getting too many false positives on likely sequences of bytes.

Sure, I indeed did not look at what kind of byte sequences GB* codecs produce; if you say it's not feasible due to the false-positive rates, then it's not an option.
Yes, the text in question was meant to be Chinese; the problem was explicitly constrained to text that was either English or Chinese only.

This string is an interesting puzzle. I'm coming to the conclusion that it's not actually GB* - it seems to be Chinese in triple-UTF-8 with some bytes missing.

See, to me any Chinese character looks like any other Chinese character and I made the incorrect assumption that by using GB* on the sloppy-cp-1252 result I'd get something approaching valid..
The bytes missing are probably due to un-printable bytes not having been copied into the question; the OP didn't use repr() here after all.

��0$Í(eK>”ÇHÉÜbÆ{Â;fBo;¬UóÙC‹pÎ?Ÿ÷œ3·9BOƒ
æÏ�–—œ²ÆúCø|íÓ›C¼'Žÿ+´+¨$/í›Ùa½]íº3ÃÍì]B8Eí0d¤oIßˆY·	1qÍüV³èsÒ¾žÿð1¾€CI‹ÞÉáÈ•©—Ïÿ?Ñï-ÙŸKiäá¶•+¬Tä»eÀU{®§ÊEÅ3á!ÎMY¬®*k\qš¯yÏ$à¼æ÷þ	i@CZ¿R¯bäc0ü�¢ªÛ{níÎÜ}¤,¿” 3¬ì‡ýÒˆóÀr%Ôå†6Ë”Uœe<ÎAå"=Ù”[™n¯c_v>z3\†lJ¬TÍ8Mß3S˜0DÓÍï(ÓÍiHö©ü.�� $Í(eK>”ÇHÉÜbÆ{Z”7×Æ˜ë;¦l@©-8ýUu‘D¯l§µ7 ¢+ëžE$¿ÎÙãÑíË›©[»¸˜OþzL¢ÒGÞe°öð¦€c6„æŽh»êv#‡äHµà²ä+ŸÄÚwqá rÜQe7>›2HUä™šÆY¡æ1d,h¦ž×êöˆXHõ^
}ï˜Ú‘>†Vä ÉcWÛš,ÔI W³<=–Öh£"F±¶gëd¦ ä·\¨7	¿´{ËìE<aWµã×EÚ–|¿$!ú°¦<Ü¢$Öq�9Âˆ5J3ëz
Yag»°uÉñ’‡¡r'©ÈÙðo0’í‚3ÄÙÈ—k"w~Øül˜mS6“–@íûáw���p_Y…OÈänaþ+'dr„‡ˆ]=ì¢@QtæøÂéÚr.žà´Gm›L=î¬„«9D/3m‡ÜvOiäO§Î;Fâ¾¾œ£ÐL€)î–»È«~¶âXd|ÂiJ\µRË0'ÛªST€9šÕ'Çò†�� _Y…OÈänaþ+'dr„„Â®Á>!äó‡åÐpœšN‰ónÞo-{*ï{ë6ñ-„}NŸÉ «¾—O{fÀ¡(ÏiÖÙ¸ma·¨éÍ‘WuŠoÈ2XÎ.sf<Ï*º· 8‹xë0sa/ŠE 1'! SÈœæIwQÔbÄDŽiµWçØ^R/©y¯¯Ž¿.µ Eí²1žôõI Ð!^à£´ñòbeüÞY¥ï,Žc@9õF:ïx)5Û4˜ˆ¡bx3Ê8@2Ð¬}ÐˆA|w¾p?Í{Ê–°^s|0]{«¾©öË•×ci e¶íºðà7)C\;æúi0ýÉN¶^s1ïÇ_æŸY0Ìú)GØHß³éûÐÁ_YÉ!J���_Y…OÈänaþ+'dr„"YBDO(µÉÛ]Ã2æjÂ3„°k°–À¬<³%EÔpFø|ªt…)v¡bÇíŸ¼”ï-qê6ÚŸDìNìÃÛƒ’,2r×¦§ìÓä���_Y…OÈänaþ+'dr„P‰nði¢MQ÷ºp&…Or™Ó‚O]½•‡¦'þŒ"+µ€*xÃXóÚvðÃvi¬ÁJš¸äÞŒq"‹–BÃ8ß£š©7û|’¹9Z���€_Y…OÈänaþ+'dr„*VÛåF¢u&Ú]Ï‡,8ë�!í¯b|ž]k§!¸K2KŽ°!	íô©ÚïŒÙƒ¯ÀeZÉ=]F>N“u¤õÐ=}Iÿ48ÐV‹•lÓðµÈ†Ü˜Óa•Ûý³çÃ6ƒm¾í¶ê]g}\j:îu���_Y…OÈänaþ+'dr„SjK ·¦‡,8A¡bÌO»ª#, ¶Ÿ!dT0g‚ îªŒw{#d©wÆ±DsÂz(±s’ºÀ~®’|d'm3)*GŠ?_ÿ_ÈçÕsŒóy%���@_Y…OÈänaþ+'dr„l±)XÍf_cˆ¢Ü0¿)uä5¶QH€~žhXšöÍ÷²Ègq-ÀYŸU+�� _Y…OÈänaþ+'dr„£ò#"q°\µÚË$Uû^¡5½AQƒ§nÛàßÛä„ä\æ#Ð{³ÎI2‡”$¤iP$1˜—oó®uãPÎÿ—ÿÓ-~¼KU “¦pøPÏ|�B…ÄðÀš}q6aÈÀZ”¾Ê^Mfp/t#¹Èí1‹q_qPn\=À§Ï» <Ã°ªˆ¾ggpÕ–Fð½1/7~¶žI¶G3– ü)$‡ä‹—¥æVb	9zÁíÎ@ \¸ÿˆ ëé;ˆÂ°§±úÉO$ö=~íï}ê-ŽºSš;û—jT*k2F"º1©Z2ÐVXAV°fTîóHUqÙ²/¾bD¤/d/¡á‚¾���_Y…OÈänaþ+'dr„QP°D«L•¹Ñš; ^¤hÆµÒf¶J,ãž2 u*!AMÈ^Ì×ð%kzåxCò”“ÓžNNz‘µBÁIcãÔôí€ÿ˜BefÔ���€_Y…OÈänaþ+'dr„?'gfUZÇuÙårŸŠöp¦#’P«¯’äd_�ÞyÜ¹ÁäÅ˜‘ê&ûÒa6@m''Q³‰ñ}~Y°ábFêÊ{ÍkMƒ�S±¯b£Í5cKç;q¯¬CÌÑF§ÔðæÜ<7“yKìˆ¬nW®��0_Y…OÈänaþ+'dr„²WAí)ŸB	qu«3pÛ€ê~Ät;2Ñ¨e?Ö¨—%õI÷’V$.¹3fXG.ÃÃç31ØCX® +¯ý+=Ì«®Å-ÓëµOE¹èn5uPTU"ß<»·:‰òNõµ ™g'ß:vÝÆA]’ò¾û”ßÂÕ.
ã(×©ð6·vQ Ê}ìr\ß›êV”ýÁ¡bŸýI	»IãAÇªëâÚ]ÈÓ°j+!ê~HãAN´:·ñ5;ø÷‰Ž“ %FaLV9d…IÆ7³ZŸ0†£Ò¢ëòœþ]®ï}´.Ë|yÆ¬šŠâz¤# ïÆSAüöéZkŸŠwl•É|~Õch—ŠnüÙ1¬OÜÀý®#Ur+é���`Y…OÈänaþ+'dr„-f†Ýi
B4i^+þ”z¸%-9Å5Ï,~ktöY[ï>æ +ùj$L…kJRþÁccŽ|U×Çn²Y˜²#†³ÌEÿÍÁ���€_Y…OÈänaþ+'dr„%(ü.Ù7A0†5j'•0¶¦¡7DŸ°¾êA~ò•YðÎÆÌß¦úbŽ,½® DÊÖ€,><CæWÌÙî}²@ôãæ—†œ½Ð‚Öm©PÄ…HœÑäó)ëœC§l>÷÷¬ß}	z®'}��0_Y…OÈänaþ+'dr„°¯ðd(T4õ‡¹Ä‰{a^o%«ÿ‹µHž„ÆjÛÂ”á»ùá~Œ˜(5C{Ê
pÐÀ§wH7ÄÅ@Š6Q.xædWj_w¡@Á2è±²ccLf½¹æ’uL”ñ;ÝŒÈ~2ÿÕNí‚éâó¬ñ
¾‹¬‡¡e £k~U“˜&WÞÈÜy©fÔNÉ ÓtáPÍ³5ñ
ÜQ¥þv

authors: Memtiras mjpieters rspeer

repo: rspeer/python-ftfy


text:
Added support to return the 'me' profile along with the other contacts

Added support to return the 'me' profile along with the other contacts

what happens if a user omits the READ_PROFILE permission?

Good question.  I guess it won't work, but that's the same problem as if they don't accept the other permissions isn't it?  Or or there some guards in place?

It'd be great if it could return all contacts minus ME if the permission is not included.

I don't thin it's possible to switch off a permission in Android is it?  I think you either accept permissions when you down load the app, or you don't get to down load it.

true. I was thinking from the developer point of view. If I want to use react-native-contacts and only get contacts (not create contacts) the module works with just the android.permission.READ_CONTACTS permission. Will the code crash if a developer omits android.permission.READ_PROFILE and runs getAll()?

You mean if you manually change the manifest for what ever reason?

yeah as a developer wanting to use the least number of permissions. Too niche?

I think so, if you're going to edit the source feel free to do what ever you need.  I wouldn't let this prevent pushing to master.


text:
Multiple updates

Multiple updates:

Should fix issue with auto deleting of '>' and '/'.
Breakout code into more modular functions.
Fix issue with checkMissingCloseTag. Needed a <= 2 instead of < 2 for it work properly.

@rt320 This should fix most issues found in your PR to apache.

@rt320 I sent some update, give them a look over and see if everything functions how they should and let me know what you think.


text:
Can I use env var in SLACK_TITLE?

      - uses: actions/checkout@v2
      - name: Send Slack Notification
        uses: rtCamp/action-slack-notify@v2.0.2
        env:
          SLACK_WEBHOOK: 'https://xxxx'
          SLACK_TITLE: ':rocket:【Android】App Tester:rocket:\nバージョン: v${VERSION}(${BUILD_NUMBER})\nリリースノート:\n${RELEASE_NOTE}'

Please refer:

https://github.community/t/how-to-use-env-context/16975/2
https://github.community/t/env-vars-are-not-expanded-causing-dry-violations/16550/2

Thank you

repo: rtCamp/action-slack-notify


text:
Build fail error

Build failed without any reason
Every RTD projects worked ok and yesterday without any changes_what_can_provide_"fail" I got Build fail. A lot of time I try to fix text/config.... nothing helped, so I think: "ok, happend" and clone wittingly good code from
https://readthedocs.org/projects/edi-n/
to
https://readthedocs.org/projects/for-test/ and got Build failed
Reproducible Project
projects with errors:
https://readthedocs.org/projects/for-test/
&
https://readthedocs.org/projects/icona/
Error Logs/Results
https://readthedocs.org/projects/for-test/builds/8834547/
Expected Results
Build completed
Environment Info
* Python Version: 2.x

* Sphinx Version:

* RTD Theme Version:

Hi, the build that you mentioned here failed because there are some Unicode characters in the documentation and pdflatex fails because it's not well supported.
You may need to use another latex engine, like xelatex for example.
Check out this guide: https://docs.readthedocs.io/en/latest/guides/pdf-non-ascii-languages.html
Let me know if that helps.

Hi, sorry for long time respond: I add new settings ``latex_engine = 'xelatex'to **conf.py** file (https://github.com/EDI-N/Test/blob/rock/docs/source/conf.py) and nothing happend - got same error: https://readthedocs.org/projects/for-test/builds/8858534/ What should I do to fixpreloaded format=pdflatex```?

Hi @EDI-N! I enabled the feature flag mentioned in the guide I linked to your project and now it's building with xelatex. See the build at https://readthedocs.org/projects/for-test/builds/8859142/
You will need to adapt the font since it's not properly defined, though.
! Package polyglossia Error: The current roman font does not contain the Cyrill
ic script!
(polyglossia)                Please define \cyrillicfont with \newfontfamily.

I'm closing this issue. Let me know if you have any further question. Thanks!

authors: EDI-N humitos


text:
Prevent bots indexing promos

Mark the ads rel=nofollow
Add them to robots.txt
This was pretty much only a problem for Chinese search engine spiders (Yisou and Baidu)

I should mention in case any of our advertisers happen upon this ticket that this did not affect any paid ads.


text:
Mention elm-webpack-starter as an example

As proposed - closes #26.

+1 really helpful if you are just getting startet with webpack.

Thanks!

authors: dennisreimann eeue56 naltatis

repo: rtfeldman/elm-webpack-loader


text:
Make source browser-compatible

Browser doesn't contain process global variable which results in exception mentioned in #164

This would defeat the purpose of envify, which is the whole reason those are in there. It gets compiled out of the production build, which is what's supposed to be used in the browser instead of the source.
Does https://github.com/rtfeldman/seamless-immutable/pull/165 resolve this?

#165 resolves different issue I had with this tool.
Closing this in favor of discussion in #164

authors: nazar-pc rtfeldman

repo: rtfeldman/seamless-immutable


text:
Don't allow the compilers to perform strict aliasing optimizations

We type pun all over the place, which would cause undefined behaviour and bad code generation.

It's worth noting that this change is very likely to affect the overall performance negatively. The alternative is to completely re-write the affected portions of code (most of Reduce.cpp) to avoid aliasing.


text:
Convert old appimages to the new flatimage

I have tried extracting an old appimage which was made with a 32bit wineprefix and substituting it into the flatimage wineprefix directly but it complains of a kernal32 error. IS there anyway to convert these to flatimage format without having to reinstall the game again?
Also what is the process to extract a  flatimage?
WIth appimage all i had to do was run  --appimage-extract
and then run appimagetool  to create an appimage with any changes

Thanks Ruan. I'll try the fusermount option. Just be handy now and again. If I've extracted the contents of the flat image would I just need to replace the contents of the flat image with the contents of my game image build folder and re-run game image to pack it again?

No problem. It would not be that simple because the games are stored in compressed filesystems inside flatimage. The flatimage method of doing things does not require to extract everything to modify like it was with AppImage. Here are some examples, (make a backup before trying):
List the filesystems inside the image
$ ./tomb-raider-collection.flatimage fim-dwarfs-list
tomb-raider-anniversary
tomb-raider-legend
tomb-raider-underworld
usr
wine

Extract a game from the flatimage to the current directory (from the previous list):
./tomb-raider-collection.flatimage fim-exec cp /fim/dwarfs/tomb-raider-anniversary.dwarfs .

Extract a dwarfs file to a folder:
mkdir tomb-raider-anniversary
tomb-raider-collection.flatimage fim-exec dwarfsextract -i tomb-raider-anniversary.dwarfs -o tomb-raider-anniversary

Move the tomb-raider-anniversary directory and the tomb-raider-anniversary.dwarfs filesystem to the build directory of gameimage. On the creator, create click on '+', for adding a new game, type the same name of the directory/dwarfs file tomb-raider-anniversary and it should detect the folder and executables inside, without having to reinstall.

Update wine, with a new version downloaded from the gameimage-runners github. The name of the filesystem should be wine.dwarfs, the last argument is the mountpoint, games look for wine in this location.
./tomb-raider-collection.flatimage fim-dwarfs-add wine.dwarfs /fim/mount/wine

Note that I have not exposed this features yet because it is a bit experimental, if it is working I recommend to just leave it.

repo: ruanformigoni/gameimage


text:
网页快开遇到的bug

描述一下这个bug
网页快开无法使用搜索打开网页
复现方式
搜索框输入任意文本，
选择网页快开设置的搜索引擎，
不能弹出浏览器
预期行为
输入任意文本，选择搜索引擎，输入内容，回车进入浏览器搜索
截图
如果可以，请添加屏幕截图以帮助解释您的问题。

今天是2024/12/05还是打不开网页，我在utools上用这个插件也比较多

repo: rubickCenter/rubick


text:
Rails/WhereEquals add table/column split

With this change, the cops suggestions and autocorrect splits a namespaces column reference into
table: { column: value }.
Example:
Comment.joins(:post).where('posts.title = ?', 'Title')

turns into ->
Comment.joins(:post).where(posts: { title: 'Title' })

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Thanks!

authors: koic mobilutz

repo: rubocop-hq/rubocop-rails


text:
Partial autocorrection for Metrics/LineLength

This isn't quite an issue, but I didn't know where else to ask it. Sorry.
I want to make a PR to add partial support for autocorrecting Metrics/LineLength, just in the cases where the long line is a comment.
Before I make that PR, I have two questions about this:

Would something like this be approved?
Is it possible to write a “partial autocorrector” function?

I, for one, would absolutely love if this existed — in fact, I visited this repo on Github today just to check if this features was supported.

Would something like this be approved?

Very likely. It is possible that auto-correction might be disabled by default, but I don't see any reason why we couldn't put it in. 🙂

Is it possible to write a “partial autocorrector” function?

If you limit the scope, like you said, to long comment lines, I think it is very possible. 👍
I hope that answered your questions. I'm closing this issue as answered. Please go ahead and open a PR if you want to work on it. 🙂

authors: Drenmi dkniffin jackkinsella

repo: rubocop-hq/rubocop


text:
HTML formatter crashes on empty files

Create an empty file and then run RuboCop on it, with -f h.
It'll crash with the following backtrace:
index 0 outside of array bounds: 0...0
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/parser-3.0.0.0/lib/parser/source/buffer.rb:265:in `fetch'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/parser-3.0.0.0/lib/parser/source/buffer.rb:265:in `source_line'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/parser-3.0.0.0/lib/parser/source/range.rb:126:in `source_line'
(erb):246:in `block (2 levels) in binding'
(erb):239:in `each'
(erb):239:in `block in binding'
(erb):233:in `each'
(erb):233:in `binding'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/2.6.0/erb.rb:901:in `eval'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/2.6.0/erb.rb:901:in `result'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/html_formatter.rb:64:in `render_html'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/html_formatter.rb:49:in `finished'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/formatter_set.rb:34:in `public_send'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/formatter_set.rb:34:in `block (3 levels) in <class:FormatterSet>'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/formatter_set.rb:34:in `each'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/formatter/formatter_set.rb:34:in `block (2 levels) in <class:FormatterSet>'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/runner.rb:95:in `inspect_files'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/runner.rb:47:in `run'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/command/execute_runner.rb:26:in `block in execute_runner'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/command/execute_runner.rb:52:in `with_redirect'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/command/execute_runner.rb:25:in `execute_runner'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/command/execute_runner.rb:17:in `run'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/command.rb:11:in `run'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli/environment.rb:18:in `run'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli.rb:65:in `run_command'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli.rb:72:in `execute_runners'
/Users/daniel/RubymineProjects/rubocop/lib/rubocop/cli.rb:41:in `run'
/Users/daniel/RubymineProjects/rubocop/exe/rubocop:13:in `block in <top (required)>'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/2.6.0/benchmark.rb:308:in `realtime'
/Users/daniel/RubymineProjects/rubocop/exe/rubocop:12:in `<top (required)>'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/bin/rubocop:23:in `load'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/bin/rubocop:23:in `<top (required)>'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `load'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `kernel_load'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:28:in `run'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:476:in `exec'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:30:in `dispatch'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:24:in `start'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:46:in `block in <top (required)>'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors'
/Users/daniel/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:34:in `<top (required)>'
/Users/daniel/.rbenv/versions/2.6.6/bin/bundle:23:in `load'
/Users/daniel/.rbenv/versions/2.6.6/bin/bundle:23:in `<main>'

RuboCop version
master

Actually I can't duplicate this anymore... I wonder if it was a weird caching bug or something.

Actually I can't duplicate this anymore... I wonder if it was a weird caching bug or something.


text:
Remove mdx support as it appears bugged

Proposing we remove mdx support as it appears bugged re: the following issue.

https://github.com/rubocop/rubocop-md/issues/37

Makes sense, .mdx is not Markdown. Thanks!

authors: larouxn palkan

repo: rubocop/rubocop-md


text:
Add new Rails/PrivateTransactionOption cop

This PR adds a new cop called Rails/PrivateTransactionOption.
This cop checks whether ActiveRecord::Base.transaction(joinable: _) is used. The joinable option is a private API and is not intended to be called from outside Active Record core.

https://github.com/rails/rails/issues/39912#issuecomment-665483779 -
https://github.com/rails/rails/issues/46182#issuecomment-1265966330

Passing joinable: false may cause unexpected behavior such as the after_commit callback not firing at the appropriate time.
See also https://github.com/kufu/activerecord-bitemporal/pull/156
The motivation for wanting to add this is that even though the joinable is undocumented, it was recommended in some articles, so it may be inadvertently widely used. It is possible that it is being used incorrectly to simply enable requires_new implicitly without realizing that it affects the behavior of after_commit.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[x] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Can you first propose an addition to the Rails Style Guide?
https://github.com/rubocop/rails-style-guide
I'm not sure which articles have made incorrect references, but including a description in the Style Guide that RuboCop Rails follows would serve as one countermeasure to them.

Opened https://github.com/rubocop/rails-style-guide/pull/355.

I'm not sure which articles have made incorrect references

A quick Google search shows the following articles:

https://makandracards.com/makandra/42885-nested-activerecord-transaction-pitfalls
https://dev.to/gerardosandoval/understanding-activerecord-nested-transactions-3hee
https://zenn.dev/merda/articles/cbe2fdfd97ee75 (Japanese)
https://thinkami.hatenablog.com/entry/2021/06/30/014210 (Japanese)

Some articles mention unintended side effects, while others do not.

https://api.rubyonrails.org/v6.0/classes/ActiveRecord/ConnectionAdapters/DatabaseStatements.html#method-i-transaction documents joinable while not the recent. What happened?

https://github.com/rubocop/rubocop-rails/pull/414 Related

documents joinable while not the recent. What happened?

See https://github.com/rails/rails/pull/46186

Some more context https://github.com/rspec/rspec-rails/issues/2598#issuecomment-1109014190 - I withdraw my statement that adding joinable: false is a good practice. With requires_new: true and all explicit transactions (apart from implicit update/create/etc transactions), joinable: false is redundant. And considering the side effects (due to joinable? checks?) it’s plain bad.

Related cop suggestion https://github.com/rubocop/rubocop-rails/issues/400

Agreed with your opinion. I don't believe it's always right to require requires_new: true, but I do believe that using joinable: false is probably wrong most of the time.
In reality, there may be situations where you have to use joinable: false because the transactions used inside a third-party gem do not use requires_new: true, but considering the side effects, it should be a last resort. This Cop helps you understand that it must be used with caution and its behavior is not guaranteed by Rails core team.

Should it be possible to wrap a call to a gem that doesn’t require_new in a transaction to isolate it instead of a wrapping joinable: false?
It is worth mentioning that when reasoning about nested transactions and business logic, the error kernel design pattern comes handy.

As far as I know, there's no way around it. You need to fix the gem.
It might be useful to add some notes on how to fix such things, but I think that is outside the scope of this cop.

@koic @andyw8 @bbatsov WDYT?

🤔 Should this be part of a more general cop for avoiding private ActiveRecord APIs?

🤔 Should this be part of a more general cop for avoiding private ActiveRecord APIs?

This might be one option, but at this point, I'm not sure which other APIs should be included. Also, if we want to provide other options for each private API, it may be useful to have a Cop for each one.

Rails/PrivateTransactionOption cop

Can you consider naming the cop to suggest the risks associated with unexpected behavior in nested transactions, rather than focusing on the use of a private API?

repo: rubocop/rubocop-rails


text:
Style/FetchEnvVar check for if condition

Not sure that rubocop can check it or dynamic check is required for such checks, but I'll report it anyway
Steps to reproduce the problem

Create test.rb with content:

# frozen_string_literal: true

if ENV['foo']
  puts 'some code'
  puts ENV['foo']
  puts 'other code'
end

run rubocop -A check
result code will be:

# frozen_string_literal: true

if ENV['foo']
  puts 'some code'
  puts ENV.fetch('foo', nil)
  puts 'other code'
end

So fetch is literally useless in code like this
RuboCop version
$ [bundle exec] rubocop -V
1.28.1 (using Parser 3.1.2.0, rubocop-ast 1.17.0, running on ruby 3.1.2 x86_64-linux)
  - rubocop-performance 1.13.3

But in same time there may be code like this:
if ENV['foo']
  ENV.delete('foo)
  puts 'some code'
  puts ENV['foo']
  puts 'other code'
end

And fetch is required in this code

ENV['foo'], ENV.fetch('foo', nil) and ENV.dig('foo') are all functionally equivalent. All three return nil when ENV does not contain the matching key. Perhaps what this cop should state, when recommending ENV.fetch('foo', nil) as an alternative, is the explicitness of returning nil?
Ultimately, a developer/team/project is free to ignore or disable cops. We should not blindly use all of them. If we think the cop has no value or does not apply to our code base, we should disable them. I think that applies to this case.

repo: rubocop/rubocop


text:
[Fix #11998] Fix an error when inspecting blank heredoc delimiter

Fixes #11998.
This PR fixes an error when inspecting blank heredoc delimiter.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

We should have a lint cop for this!

Naming/HeredocDelimiterNaming might detect it by default instead of creating a new Lint cop. WDYT?
https://docs.rubocop.org/rubocop/cops_naming.html#namingheredocdelimiternaming

@koic Yeah, that's a good idea!

authors: bbatsov koic


text:
BigDecimal coercion

This PR attempts to fix coercion of params to BigDecimal as per https://github.com/ruby-grape/grape/issues/1969

Please, extend the STRICT_MAPPING constant which is used for checking types when custom coercers are given

Extending STRICT_MAPPING looks simple enough... I am concerned that no tests failed without the change being made already and I don't think understand enough of the internals of Grape to write an effective test for this.

Def want a test for that STRICT_MAPPING change. I’m ok merging without and opening an issue. Deferring to @dnesteryuk.

@dblock this bug is preventing some users from moving to Grape 1.3.0. Would you be able to release Grape 1.3.1 soon? Thanks!

@dblock this bug is preventing some users from moving to Grape 1.3.0. Would you be able to release Grape 1.3.1 soon? Thanks!

I opened https://github.com/ruby-grape/grape/issues/2008, add your +1.

authors: FlickStuart dblock tlconnor

repo: ruby-grape/grape


text:
Run git config manually

I don't know why this happens, but recently the tests have failed because of the following error:
Example
fatal: detected dubious ownership in repository at '/__w/gem_rbs_collection/gem_rbs_collection'
To add an exception for this directory, call:

	git config --global --add safe.directory /__w/gem_rbs_collection/gem_rbs_collection

Closing since #279 looks better fix of this problem.


text:
Update the README.md with what engine metadata does

Discussed in https://github.com/rubyatscale/stimpack/discussions/14

Originally posted by iMacTia July 21, 2022
The README says that you can make your package an engine, but it's unclear what difference that actually makes.
Could this be clarified and/or documented?
Task
Update README.md

@ngan Should we describe in a bit more detail what this does?

repo: rubyatscale/stimpack


text:
Removed location.reload when order cancelled

Removed location.reload when order cancelled

@Thedabest This is already being handled via websockets. Please have a look here
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_ui/my_orders.js.coffee#L28
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_data/member.js.coffee#L9
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_ui/my_orders.js.coffee#L6

@Thedabest This is already being handled via websockets. Please have a look here
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_ui/my_orders.js.coffee#L28
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_data/member.js.coffee#L9
https://github.com/rubykube/peatio-trading-ui/blob/1-9-stable/app/assets/javascripts/component_ui/my_orders.js.coffee#L6

event done, cancel not send to ranger

authors: Thedabest ritesh-skyach

repo: rubykube/peatio-trading-ui


text:
Order update event is not firing

We are using after_commit on create method for publishing trigger_pusher_event
this will only publish orders with wait state, orders with done, cancel will not be triggered

@advanceditsolutions We have fixed this issue in 1-9 https://github.com/rubykube/peatio/blob/master/app/models/order.rb#L36

@ysv Yes but it does not trigger trigger_pusher_event which is required for changing the orders state on peatio-trading-ui

Hey im talking about trigger_pusher_event which pushes events to pusher_member.
https://github.com/rubykube/peatio/blob/41bc0a3cdd7805440c583635b70fcb2d91dddc91/app/models/order.rb#L14
This triggers a event for new order
https://github.com/rubykube/peatio-trading-ui/blob/67f2e9d0133df852568c1c6a1b4193254ca4b615/app/assets/javascripts/component_ui/my_orders.js.coffee#L28
This listens to order states and process the front-end work like removing or updating orders.

@advanceditsolutions yes because this event is duplication of EventAPI call and we deprecate pusher so this call will be removed soon
Here is right eventing which you should use
https://github.com/rubykube/peatio/blob/master/app/models/order.rb#L30-L46

Some duplicated events should be removed as implemented (here)[https://github.com/rubykube/peatio/pull/1379/files]

authors: advanceditsolutions martianatwork ysv

repo: rubykube/peatio


text:
ValueError

Hi,
I am trying to use this AdaRank implementation which seems amazing.
However, when I try to train the model, I get a ValueError.
My code is:
 X, y, qid = load_svmlight_file(train_file, query_id=True)
 print('X shape:', X.shape)
 print('y shape:', y.shape)
 print('qid shape:', qid.shape)

 X_test, y_test, qid_test = load_svmlight_file(test_file, query_id=True)

 scorer = NDCGScorer(k=10)

 '''
 Run AdaRank for 100 iterations optimizing for NDCG@10.
 When no improvement is made within the previous 10 iterations,
 the algorithm will stop.
 '''
 model = AdaRank(max_iter=100, estop=10, scorer=scorer).fit(X, y, qid)

The shapes of my data are:
X shape: (140, 105)
y shape: (140,)
qid shape: (140,)

The error happens in line:
model = AdaRank(max_iter=100, estop=10, scorer=scorer).fit(X, y, qid)
The error is:
ValueError: shapes (3,) and (91,) not aligned: 3 (dim 0) != 91 (dim 0)
Specifically, the error is in this line of the library:
weighted_average = np.dot(weights, score)
When I try to debug in the library, I get these:
Number of queries: 3
Weights shape: (3,)
Number of weak ranker scores: 105

And inside  for fid, score in enumerate(weak_ranker_score)::
fid: 0
Score shape: (91,)

So it seems that there is a problem of sizes between weights and scores, but I don't know what's going on.
I have 3 different qid, 140 documents for training with 105 features each one.
Hope you can help me,
Thanks in advance

Hey @jmdu99, my best guess is that the qid's are scattered - usually for learning to rank the same qids are placed together to form contiguous blocks, and maybe your data wasn't formatted that way? Check if your qid is like: [0, 0, ..., 0, 1, 1, ..., 1, 2, 2, ..., 2].
Alternatively, you can also run this snippet to print out the number of query blocks:
print(len(list(utils.group_offsets(qid))))

If it doesn't match the number of queries, better check again and be sure the data is laid out in an expected order.

That seems to be the problem. There are 3 blocks before splitting.
But when applying train_test_split the number of blocks increases:
# Split documents, labels, and query_ids into training (70%) and testing (30%)
X_train, X_test, y_train, y_test, qid_train, qid_test= train_test_split(X, y, qid, test_size=0.3, random_state=1, shuffle=True, stratify=qid)

Is there any way of sorting the split by qid in order to have only 3 blocks or another way of splitting?
Thanks in advance

Thank you @rueycheng. That was the problem.
Now I have another problem in line pred = model.predict(X_test, qid_test)
I will open another issue if I don't manage to solve it

repo: rueycheng/AdaRank


text:
Action fails when sudo is missing

This action fails in an environment without sudo.
Common use-case is a blank docker container such as ubuntu:22.04, which runs as root by default and has no sudo installed.

In such container, isn't wget also missing?

True, but wget is commonly installed due to some requirements in the CI, whereas sudo isn't.


text:
AttributeError: 'Dimension' object has no attribute 'eval'

Im getting an AttributeError: 'Dimension' object has no attribute 'eval' when trying to train. Can someone assist me to solve this issue.
 File "train.py", line 107, in <module>
    model = create_model(args, overall_maxlen, vocab)
  File "/home/src/Unsupervised-Aspect-Extraction/code/model.py", line 43, in create_model
    W_regularizer=ortho_reg)(p_t)
  File "/home/.local/lib/python2.7/site-packages/keras/engine/topology.py", line 592, in __call__
    self.build(input_shapes[0])
  File "/home/src/Unsupervised-Aspect-Extraction/code/my_layers.py", line 127, in build
    constraint=self.W_constraint)
  File "/home/.local/lib/python2.7/site-packages/keras/legacy/interfaces.py", line 91, in wrapper
    return func(*args, **kwargs)
  File "/home/.local/lib/python2.7/site-packages/keras/engine/topology.py", line 418, in add_weight
    self.add_loss(regularizer(weight))
File "/home/src/Unsupervised-Aspect-Extraction/code/model.py", line 17, in ortho_reg
    reg = K.sum(K.square(K.dot(w_n, K.transpose(w_n)) - K.eye(w_n.shape[0].eval())))
AttributeError: 'Dimension' object has no attribute 'eval'

Can you follow the Dependencies section in README and check if the versions are correct?

What's the version of tensorflow

Were you able to solve the issue, i am getting same error.. i am using keras 2.2.4 and trying to update the code to work with this version.... Any help please ?

The same problem here.

Can you follow the Dependencies section in README and check if the versions are correct?

What;s the tensorflow version?

The code was developed using Keras 1.2.1 with theano 0.9.0 as the backend (not tensorflow).

For Windows users using Anaconda. Open the Anaconda Prompt and type:
set "KERAS_BACKEND=theano"

repo: ruidan/Unsupervised-Aspect-Extraction


text:
Unable to install playwright-crx through pnpm

When I run pnpm i playwright-crx, the installation failed and no file was found: playwright/packages/playwright/bundles/babel
This seems to be used because the local file: path is used in package.json

You're right, with pnpm it's not working. With npm it is working, that's why I never noticed that issue.
I'm using those local playwright bundles dependencies to avoid declaring all their transitive dependencies explicitly. Can you use npm instead to install it?

@ruifigueira use npm works and it is fine for testing, but do you have plan to make pnpm works? For production I (and people) usually use pnpm

8f06b95fa3527bf72ceaff6ad103d67e7f65fd53 should fix the issue. You can try it:
git clone git@github.com:ruifigueira/playwright-crx.git
npm ci
npm build
npm pack

This will generate a playwright-crx-0.6.0-next.tgz.
Then create a new temp folder, copy the playwright-crx-0.6.0-next.tgz. file there and run:
pnpm add playwright-crx-0.6.0-next.tgz

I released playwright-crx@0.6.0, it now works well with pnpm.

authors: ducan-ne molvqingtai ruifigueira

repo: ruifigueira/playwright-crx


text:
CORS is missing in the newly generated frontends

Issue
CORS seems to be missing when generating the NextJs frontend with a FastAPI backend.
Reproduction Steps

Create an app with the agentic RAG option (create-llama version 0.3.16)
Run frontend and backend and  send a message

Fix
Just need to add CORS back.
Would've created a PR to fix this, but am held up today, so just reporting the issue here for now :)

Hi @KenjiPcx, you can now directly access the chat UI using the backend address, like http://localhost:8000, so it should work without any CORS issues!

yes, @KenjiPcx we removed that on purpose, what's your use case for using CORS?

Oh I see I've been accessing the frontend through localhost:3000 and it was throwing errors

Did anything change with logging too? I can only see the logs of the backend starting and restarting but unable to view logs from anywhere else 😔

You need to set the NEXT_PUBLIC_CHAT_API env variable in the generated frontend to point to the URL of chat endpoint in your express backend.

authors: KenjiPcx leehuwuj marcusschiesser

repo: run-llama/create-llama


text:
Add Claude 3 Sonnet model to AWS Bedrock & update to support Messages API - Text Only, Not Multimodal

Description

Claude 3 Sonnet became available in AWS Bedrock on March 4th (link).  However, it could not be used with the same interface as the other foundation models since it was not included in the BEDROCK_FOUNDATION_LLMS dict.

Updated CHAT_ONLY_MODELS and STREAMING_MODELS to include its identifier.

Claude 3 introduced a new requested request and response schema known as Messages API.  The existing code was not compatible, so I updated it.  This is also backwards compatible with previous versions of Claude, so I consequently updated all the Anthropic logic to utilize it.

https://docs.anthropic.com/claude/reference/migrating-from-text-completions-to-messages
Anthropic has relabeled the previous Text Completions API as now deprecated/legacy.

Updated unit tests to reflect the changes to the request and response schema.

Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Some relevant discussions from the LangChain side:

https://github.com/langchain-ai/langchain/issues/18514
https://github.com/langchain-ai/langchain/pull/18548

Working for batch.

Claude 3 introduced a new requested request and response schema known as Messages API. The existing code was not compatible, so I updated it. This is also backwards compatible with previous versions of Claude, so I consequently updated all the Anthropic logic to utilize it.

Does this include provisioned throughput?

Claude 3 introduced a new requested request and response schema known as Messages API. The existing code was not compatible, so I updated it. This is also backwards compatible with previous versions of Claude, so I consequently updated all the Anthropic logic to utilize it.

Does this include provisioned throughput?

It doesn't explicitly alter that since a provisioned model has its own unique identifier unlike the on-demand foundation models.  So long as those go through the the same bedrock.utils.AnthropicProvider flow though, they benefit from the Anthropic Messages API schema update as well.

@brycecf is this ready to merge? I don't have access to bedrock to test, so I kind of need to put some faith in that it works :)

Could you add some testcases for the new format? Or maybe scope it to a different PR.

@sansmoraxz can you try in a query engine or chat engine? I suspect it will fail (my above comments would fix the issue though if it does fail)

Could you add some testcases for the new format? Or maybe scope it to a different PR.

@sansmoraxz Can you clarify what you mean by "new format"?  v3 specifically?  The Messages API works with all Claude versions now.

OK my bad, didn't parse the unit tests properly.

@sansmoraxz that makes sense. The normal llama-index-llms-anthropic package has handling for this case to avoid that error

OK I figured it out. Well AWS updated the docs for the new message api.
The system prompt is a not a part of the prompt itself but a separate parameter. You can technically pass it to older versions of Claude but it will just be ignored.

FWIW, it seems the Anthropic models are the only ones in Bedrock which support system prompts.

Well Anthropic models are the only ones takes json as input. Rest are still text based.

As system prompt capability was not present for Bedrock 2.1, I'm inclined to system prompt functionality being treated as a separate issue/PR just to make Cohere v3 available.  I personally do not have the time to continue working on that beyond this.

What @jc1518 seems to be working. There is not much difference between calling sonnet and haiku APIs.

Has this been already included in the release 0.10.20? I cannot seem to make it work with error: ValidationException: An error occurred (ValidationException) when calling the InvokeModel operation: "claude-3-sonnet-20240229" is not supported on this API. Please use the Messages API instead. :(
Also, is someone already working on adding the new Haiku model?

authors: brycecf dgallitelli logan-markewich sansmoraxz


text:
Add Alibaba cloud Bailian index intergration

Description
Alibaba cloud Bailian (Dashscope) is a platform for developing LLM based applications including RAG. We add a set of LlamaIndex intergrations including Parse, Node Parser, Index&Retriever for our platform.
Fixes # (issue)
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[x] Yes
[ ] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Can anyone review my PR? I've been waiting for 2 weeks. @logan-markewich @nerdai

Anyone can review my PR? Or tell me why my PR can't get reviewed. @logan-markewich @sourabhdesai @Disiok @EmanuelCampos

Its been one week, and its been busy to review such a large PR 😅

Just a few minor comments.
Also, up to you, but it's probably worth writing some unit tests? Some of these integrations are pretty complicated

Since the test need API key on DashScope Cloud, we are unable to put it in unit tests publicly. We test it locally before commit.

I added BUILD files to fix tailor failures.

authors: PhantomGrapes logan-markewich