Bizarre Loop: Not Storing Dispenser Tx

This is what it looks like to run counterparty these days... :/

fixed here https://github.com/CounterpartyXCP/counterparty-core/pull/1488

uh, what is this crazy logic? isn't the loop itself problematic??
now I'm getting this (just changed to debug)
[2024-03-11 16:41:30][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:30][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:30][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:30][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:31][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:32][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:33][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:34][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:35][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:36][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:37][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:38][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:39][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:40][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:41][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:42][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:43][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:44][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:45][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:46][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:47][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:48][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:49][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:50][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:51][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:52][WARNING] Not storing [mpma] tx [d4ab628d983fc707e66a51a5c1bb5d84d70cf2f6c29c32ce80e2d4471406cbae]: invalid: insufficient funds for asset BLAINEPEPE, address 173cE6ScUFCmBLCqZeG18ij6r9KHRPbAjC has no balance
[2024-03-11 16:41:52][WARNING] Not storing [mpma] tx [9807303b4d20043655028421dc380c0174d6520627267d8afd4d79a002c86a1d]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance
[2024-03-11 16:41:52][WARNING] Not storing [mpma] tx [8013c1da8fc6d61258387a1ab365f67d612822e494ca3e7a6b99c3bbb6eef2cf]: invalid: insufficient funds for asset A517301080302283367, address 1FueyNpiTJvFtxtPaop5wQVTJQuAEqieiZ has no balance

(see also https://github.com/CounterpartyXCP/counterparty-core/issues/1168)

this too:
[2024-03-11 23:31:29][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:31][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:32][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:33][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:34][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:35][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:36][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:37][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:39][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:40][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:41][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:42][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:43][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:44][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:45][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:46][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:48][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:49][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:50][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:51][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:53][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:54][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:55][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:56][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:57][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:31:58][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:00][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:01][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:02][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:03][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:04][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:05][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:06][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:08][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:09][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:10][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:11][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:12][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:14][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:15][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:16][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:17][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:18][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:19][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:20][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:22][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:23][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:24][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:25][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:26][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC
[2024-03-11 23:32:28][INFO] Dispenser: bc1qzzvqgzmn7t20tsq85g5ls8ggq8h8cxvlw6neze opened a dispenser for asset OXBT with<PHONE_NUMBER>0000 balance, giving 0.00080000 OXBT for each 0.00080000 BTC

By design transactions in the mempool are continually parsed and rollbacked..
Will be fixed with https://github.com/CounterpartyXCP/counterparty-core/issues/1440


Add build/install target to makefile

, which can then be a parent/dependency of make test and make style.

Close this out?

Closed by #54.


Audit feature branches and Pull Requests

Purge outdated code, and/or recover valuable ideas.

I've done about all I can for now until @halorgium especially has some time to go through his branches. Will come back to this when preparing the next release ( 0.18.0 ) after #545 is merged.


SAK-33651 SiteManage adding tools doesn't generate email notification

What is the magic line that fixes the reported issue?

look at line 11332, basically it bypasses the threaded version when using "Manage Tools".


ots module not available in rpcdaemon

Hello,
I have a running instance of erigon, and now I am trying to start otterscan.
I compiled the rpcdaemon from the provided repo ( https://github.com/wmitsuda/erigon )
but when running I get the following output:
EROR[06-09|09:19:37.299] Unavailable modules in HTTP API list     unavailable=[ots] available="[eth erigon web3 net txpool]"                                                INFO[06-09|09:19:37.300] HTTP endpoint opened                     url=localhost:8545 ws=false ws.compression=false grpc=true grpc.port=8547
I compiled rpcdaemon from the referenced repo at this commit:
git checkout 0929df8915936909278f4ce38a2e753630bb9dce
what I'm doing wrong?

did you enable the "ots" namespace when starting rpcdaemon?
see: https://github.com/wmitsuda/otterscan/blob/develop/docs/install.md#enable-otterscan-namespace-on-rpcdaemon

@wmitsuda Yesss I enabled like this:
./rpcdaemon-otter --grpc  --http.api=eth,ots,erigon,web3,net,txpool --datadir=bsc-mainnet
But when I start I get the above error

try to checkout the tag directly, like: git checkout v2022.06.02-otterscan

I guess you accidentally checked out a commit who is from upstream branch, so no "ots" support.

Since I'm running an old version of erigon, I had to use that commit to build rpcdaemon, bevause of client/server version mismatch.
Is there a way I can solve this issue?

Which erigon version are you running?

INFO[06-13|19:51:15.961] Build info                               git_branch=HEAD git_tag=v2022.06.02-otterscan git_commit=f03d08c5ce688352d3598f36d502a6a5cde7d3dc

that's strange, it doesn't match the commit hash for v2022.06.02-otterscan I have here, see:

Yess Im sorry here is my git log

Also its not clear if Its enough for me to use only rpcdaemon from your repository or also erigon compiled from your repo.

you can replace just rpcdaemon as long it is compatible with the original erigon version, as currently we don't have modifications at sync level (this will change in future).
I tried to checkout the commit you mentioned, I can't identify if it is contained in the devel or beta stream, I'm almost sure it is in devel, which is currently the alpha series. So, at that time we didn't have a compatible Otterscan version, can't guarantee if it'll even work, I suggest you first upgrade your erigon installation itself to recent alpha.

If you really want to feel adventurous, you can check and try it by yourself:

git checkout v2022.04.02-otterscan -> latest beta compatible tag
git checkout v2022.06.02-otterscan -> latest alpha compatible tag

compiling rpcdaemon from now on of these should work as long your erigon install is from one of these series, but can't guarantee everything will work.

@wmitsuda  thank you man, I'm going to try that and let you know asap

If you really want to feel adventurous, you can check and try it by yourself:

git checkout v2022.04.02-otterscan -> latest beta compatible tag
git checkout v2022.06.02-otterscan -> latest alpha compatible tag

compiling rpcdaemon from now on of these should work as long your erigon install is from one of these series, but can't guarantee everything will work.

@wmitsuda Hey man!!!! thank you very much, I compiled both erigon and rpcdaemon from git checkout v2022.06.02-otterscan and now they both seem to be working, will wait for the node to sync up and keep you updated!

Node is still syncing, but I get the following:

Is it expected?

I managed to open the rpc daemon on dockers private ip "<IP_ADDRESS>" and now I get this which seems okay, since node is still syncing

Made it work!!! I had some problems with CORS that were not solved with --http.corsdomain "*", so I had to run otterscan docker locally

glad you made it!
for running rpcdaemon not on localhost, be sure to follow the instructions on: https://github.com/wmitsuda/otterscan/blob/develop/docs/install.md#run-otterscan-docker-image-from-docker-hub, more specifically the ERIGON_URL variable.


[BUG]

Describe the bug
I have Installed Kasten in my AKS cluster to perform back ups of persistent volumes to test DR case.
After the installation I am able to access the k10 dashboard but getting the error like "One of the services (dashboardbff-svc) is slow to respond"
and also it is not showing applications inside the cluster, please find the screenshot attached.

To Reproduce
Steps to reproduce the behavior:

Go to http://<IP_ADDRESS>:8080/k10/#/dashboard

Expected behavior
I am expecting the k10 dashboard to be available with the applications which are deployed in the AKS cluster and able to take backups of PVs.
Environment
Kubernetes Version/Provider: 1.19.6
Storage Provider: Azure Blob storage
Cluster Size (#nodes):  4 nodes
Data Size: 5GB

Hey @Pranitha24 ,
This is not the good place to discuss about K10 issues. I would recommend you dropping a mail to k10 support at<EMAIL_ADDRESS>


Adding an English section to the README

I thought an English section in the readme would make things more friendly to everyone

Great!


Generic AppiumDriver

Hi guys! I want to propose changes that are similar as https://github.com/appium/java-client/pull/182 (java client, it is still waiting for the merging or rejection).
Major change:
AppiumDriver and its subclasses are generic now. This feature will allow to user the choice of IWebElement type those instances should be found and returned.
AppiumDriver<IWebElement> driver;
//some actions

IWebElement e = driver.FindElement(By.Id("id"));
List<IWebElement> l = driver.FindElements(By.id("id"));

User can choose the desired type. IWebElement, RemoteWebElement, AppiumWebElement or subclasses are allowed. So when they will choose something that differs from IWebElement then:
AppiumDriver<AppiumWebElement> driver;
//some actions

AppiumWebElement e = driver.FindElement(By.Id("id"));
IList<AppiumWebElement> l = driver.FindElements(By.Id("id"));

AppiumWebElement e1. = e.FindElement(By.Id("id2"));
IList<AppiumWebElement> l1 = e.findElements(By.Id("id2"));

AppiumWebElement and subclasses are not generic.  But their finders already return AppiumWebElement.
@Astro03 @Jonahss @bootstraponline What do you think about changes like that in C#?
I would like to merge them but release them later. There is scope of changes that I am going to implement and release as <IP_ADDRESS> version.

I'm okay with doing it that way if that's how the java guys do it.. I agree
that we need to be in line with how they do things as well.
On Sun, Apr 12, 2015 at 12:17 PM, Sergey Tikhomirov <
<EMAIL_ADDRESS>wrote:

Hi guys! I want to propose changes that are similar as
appium/java-client#182 https://github.com/appium/java-client/pull/182
(java client, it is still waiting for the merging or rejection).
Major change:
AppiumDriver and its subclasses are generic now. This feature will allow
to user the choice of IWebElement type those instances should be found and
returned.
AppiumDriver driver;//some actions
IWebElement e = driver.FindElement(By.Id("id"));
List l = driver.FindElements(By.id("id"));
User can choose the desired type. IWebElement, RemoteWebElement,
AppiumWebElement or subclasses are allowed. So when they will choose
something that differs from IWebElement then:
AppiumDriver driver;//some actions
AppiumWebElement e = driver.FindElement(By.Id("id"));
IList l = driver.FindElements(By.Id("id"));
AppiumWebElement e1. = e.FindElement(By.Id("id2"));
IList l1 = e.findElements(By.Id("id2"));
AppiumWebElement and subclasses are not generic. But they finders already
return AppiumWebElement.
@Astro03 https://github.com/Astro03 @Jonahss
https://github.com/Jonahss @bootstraponline
https://github.com/bootstraponline What are you think about changes
like that in C#?
I would like to merge them but release them later. There is scope of
changes that I am going to implement and release as <IP_ADDRESS> version.
You can view, comment on, or merge this pull request online at:
https://github.com/appium/appium-dotnet-driver/pull/84
Commit Summary

Generic AppiumDriver

File Changes

M appium-dotnet-driver/Appium/Android/AndroidDriver.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-0
(42)
M appium-dotnet-driver/Appium/Android/AndroidElement.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-1
(25)
M appium-dotnet-driver/Appium/AppiumDriver.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-2
(149)
M appium-dotnet-driver/Appium/AppiumWebElement.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-3
(134)
M appium-dotnet-driver/Appium/ByAccessibilityId.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-4
(24)
M appium-dotnet-driver/Appium/ByAndroidUIAutomator.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-5
(25)
M appium-dotnet-driver/Appium/ByIosUIAutomation.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-6
(25)
A appium-dotnet-driver/Appium/CollectionConverterUnility.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-7
(22)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByClassName.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-8
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByCssSelector.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-9
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsById.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-10
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByLinkText.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-11
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByName.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-12
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByPartialLinkText.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-13
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByTagName.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-14
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericFindsByXPath.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-15
(45)
A
appium-dotnet-driver/Appium/Interfaces/Generic/SearchContext/IGenericSearchContext.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-16
(47)
M appium-dotnet-driver/Appium/Interfaces/IContextAware.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-17
(6)
M appium-dotnet-driver/Appium/Interfaces/IFindByAccessibilityId.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-18
(6)
M
appium-dotnet-driver/Appium/Interfaces/IFindByAndroidUIAutomator.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-19
(6)
M appium-dotnet-driver/Appium/Interfaces/IFindByIosUIAutomation.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-20
(6)
M appium-dotnet-driver/Appium/MultiAction/MultiAction.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-21
(22)
M appium-dotnet-driver/Appium/MultiAction/TouchAction.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-22
(11)
M appium-dotnet-driver/Appium/iOS/IOSDriver.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-23
(33)
M appium-dotnet-driver/Appium/iOS/IOSElement.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-24
(25)
M appium-dotnet-driver/appium-dotnet-driver.csproj
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-25
(10)
M samples/AndroidComplexTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-26
(30)
M samples/AndroidConnectionTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-27
(12)
M samples/AndroidLocalServerTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-28
(4)
M samples/AndroidOrientationTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-29
(2)
M samples/AndroidSimpleTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-30
(25)
M samples/AndroidWebviewTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-31
(13)
M samples/IosActionsTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-32
(4)
M samples/IosComplexTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-33
(8)
M samples/IosLocalServerTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-34
(4)
M samples/IosOrientationTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-35
(2)
M samples/IosSimpleTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-36
(7)
M samples/IosWebviewTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-37
(4)
M samples/helpers/Actions.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-38
(4)
M samples/helpers/Filters.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-39
(76)
M test/specs/MJsonMethodTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-40
(472)
M test/specs/SelectorTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-41
(466)
M test/specs/SessionTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-42
(142)
M test/specs/TouchTest.cs
https://github.com/appium/appium-dotnet-driver/pull/84/files#diff-43
(466)

Patch Links:

https://github.com/appium/appium-dotnet-driver/pull/84.patch
https://github.com/appium/appium-dotnet-driver/pull/84.diff

—
Reply to this email directly or view it on GitHub
https://github.com/appium/appium-dotnet-driver/pull/84.

sorry.. didn't see this until now..


Problem With Scale Instance In <IP_ADDRESS>

ISSUE TYPE

Bug Report

COMPONENT NAME
Compute Offering
CLOUDSTACK VERSION
<IP_ADDRESS> Stable Latest Version
CONFIGURATION
KVM
Advance Networking
OS / ENVIRONMENT
Ubuntu 20.04
SUMMARY
I updated cloudstack to the latest version <IP_ADDRESS> From <IP_ADDRESS>. First, I create a disk offering and Map it to a Compute offering. When scaling the vm, I use that compute offering, but the amount of disk does not expand. While disk expansion happens through resize volume. What is the problem?
This Issue did not happen in the previous version
STEPS TO REPRODUCE
1- Crete Disk Offering
2- Create Compute Offering With Disk Offering Maped To it From Previous Step
3- Stop Instance
4- Hit Scale VM
EXPECTED RESULTS
Expand the disk
ACTUAL RESULTS
The disk size does not change in the  Detail Section Of Instance and Inside OS too.

@ahmadamirahmadi007
it should work if you change global setting "allow.diskoffering.change.during.scale.vm" to "true"

tnx. everything is ok

I have the same issue, nothing is changed, even if i changed the value to "true" for allow.diskoffering.change.during.scale.vm. The only difference is that I do not see anymore the warning in the log "Changing the disk offering of the root volume during the compute offering change operation is disabled. Please check the setting [allow.diskoffering.change.during.scale.vm]"
I executed this via cmk (api)
scale virtualmachine id=a2b9aca8-4e67-4cb4-8526-e2507b8d3898 serviceofferingid=08f5f8fa-88d7-44c7-8ed5-7f06a6031888 details[0].cpuNumber=1 details[0].memory=1024 details[0].rootdisksize=25
And the response is:
{
  "virtualmachine": {c API result
    "account": "emeaclient_16_49",
    "affinitygroup": [],
    "cpunumber": 1,
    "cpuspeed": 1600,
    "created": "2023-03-07T10:21:04+0000",
    "details": {
      "Message.ReservedCapacityFreed.Flag": "true",
      "cpuNumber": "1",
      "cpuOvercommitRatio": "3.0",
      "cpuSpeed": "1600",
      "dataDiskController": "osdefault",
      "keyboard": "us",
      "memory": "1024",
      "memoryOvercommitRatio": "2.0",
      "nicAdapter": "Vmxnet3",
      "rootDiskController": "scsi",
      "rootdisksize": "10"
    },
    "displayname": "Test-Scale-March-3",
    "displayvm": true,
    "domain": "cloud16",
    "domainid": "793d17f0-30d3-46c1-adbf-657c4659a624",
    "guestosid": "6428ffbd-1f58-11ec-b6e8-244bfeb8116f",
    "haenable": false,
    "hasannotations": false,
    "hypervisor": "VMware",
    "id": "a2b9aca8-4e67-4cb4-8526-e2507b8d3898",
    "instancename": "i-74-1443-VM",
    "isdynamicallyscalable": false,
    "jobid": "701a1122-0185-43a1-b110-bfbee380f4dd",
    "jobstatus": 0,
    "lastupdated": "2023-03-07T10:30:43+0000",
    "memory": 1024,
    "name": "VM-a2b9aca8-4e67-4cb4-8526-e2507b8d3898",
    "nic": [
      {
        "broadcasturi": "vlan://untagged",
        "deviceid": "0",
        "extradhcpoption": [],
        "gateway": "46.xxx.xxx.49",
        "id": "4e23f2be-ecc5-4793-8cbd-c3bc15920cd1",
        "ipaddress": "46.xxx.xxx.54",
        "isdefault": true,
        "isolationuri": "vlan://untagged",
        "macaddress": "1e:00:cf:00:00:87",
        "netmask": "<IP_ADDRESS>",
        "networkid": "3f5fbbe4-fe38-42ae-af2d-01709d7a2e9c",
        "networkname": "ShapeHost-Public-NL-01",
        "secondaryip": [],
        "traffictype": "Guest",
        "type": "Shared"
      }
    ],
    "osdisplayname": "Other Linux (64-bit)",
    "ostypeid": "6428ffbd-1f58-11ec-b6e8-244bfeb8116f",
    "passwordenabled": true,
    "pooltype": "VMFS",
    "receivedbytes": 0,
    "rootdeviceid": 0,
    "rootdevicetype": "ROOT",
    "securitygroup": [],
    "sentbytes": 0,
    "serviceofferingid": "08f5f8fa-88d7-44c7-8ed5-7f06a6031888",
    "serviceofferingname": "S-Packages",
    "state": "Stopped",
    "tags": [
      {
        "account": "emeaclient_16_49",
        "domain": "cloud16",
        "domainid": "793d17f0-30d3-46c1-adbf-657c4659a624",
        "key": "service_type",
        "resourceid": "a2b9aca8-4e67-4cb4-8526-e2507b8d3898",
        "resourcetype": "UserVm",
        "value": "S-2"
      },
      {
        "account": "emeaclient_16_49",
        "domain": "cloud16",
        "domainid": "793d17f0-30d3-46c1-adbf-657c4659a624",
        "key": "service_id",
        "resourceid": "a2b9aca8-4e67-4cb4-8526-e2507b8d3898",
        "resourcetype": "UserVm",
        "value": "450"
      }
    ],
    "templatedisplaytext": "RockyLinux-8",
    "templateid": "be405fbf-9ca9-4b90-bf97-9806ebf75b7b",
    "templatename": "RockyLinux-8",
    "userid": "df0acf1e-52a2-4c4f-b4e6-535546cf6b12",
    "username": "emeaclient_16_49",
    "zoneid": "55f0123b-285c-4a70-8b34-565d8454393d",
    "zonename": "EMEA-NL-01"
  }
}

This is tested is 4.17.2.
I'm doing something wrong?

@ccycv
Can you create an issue and provide more details ? For example, the details of disk offering and service offering

@ccycv
Can you create an issue and provide more details ? For example, the details of disk offering and service offering

Hi, just created at https://github.com/apache/cloudstack/issues/7325


Incompatible with Camera Overhaul

Description
Incompatible with Camera Overhaul
Minecraft version
1.20.1
Incompatible mod name
Camera Overhaul
Incompatible mod version
Camera Overhaul v1.4.0 / Shoulder Surfing 3.0.0
Game Logs
https://mclo.gs/3kMIkam

This is a known incompatiblity, hence the message on startup. Only the authors of CameraOverhaul can fix this problem. Once they fix it, I will remove the incompatiblity constraint.

@Exopandora Generally the creators of the Camera mod will probably never update the mod again, all their media is dead, so sadge :<


[ja] Update translations

Text changes:

h1: Accessibility Myths
Myth 6: Web accessibility is just a developer's responsibility
Myth 9: Accessibility can be fixed by the accessibility overlay
Myth 11: Accessibility is only for blind users
Myth 18: Accessibility is like a feature - you do it once and then you have it

Hi @yamanoku, I updated some text, would you find time to translate it?

@sergeicodes I translated it. Please review.


Speed issues in CMS

We used this module in a lot of our sites and noticed a major decrease in speed of the CMS. Especially if used in combination with more complex pages with many elemental blocks, the CMS can become unusable. Each time a page is opened in the CMS, the frontend is completely rendered (templates and image resizing). This takes up a lot of resources and slows everything down. Removing the module increased CMS speeds from 20 seconds to 2 seconds loading time on heavy pages.
It would be better if the module only calculates the scores on request and not always.

Hi remy,
Thanks for reporting,
I'll check this out and fix it.
Whats the number of blocks? Maybe i can repoduce problem by creating blocks
Best regards,
Bart

Van: Remy Vaartjes<EMAIL_ADDRESS>Verstuurd: donderdag 12 november 2020 09:25
Aan: hubertusanton/silverstripe-seo
Cc: Subscribed
Onderwerp: [hubertusanton/silverstripe-seo] Speed issues in CMS (#40)
We used this module in a lot of our sites and noticed a major decrease in speed of the CMS. Especially if used in combination with more complex pages with many elemental blocks, the CMS can become unusable. Each time a page is opened in the CMS, the frontend is completely rendered (templates and image resizing). This takes up a lot of resources and slows everything down. Removing the module increased CMS speeds from 20 seconds to 2 seconds loading time on heavy pages.
It would be better if the module only calculates the scores on request and not always.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/hubertusanton/silverstripe-seo/issues/40, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEOELHMFGWZNHUGRN7AQZTSPOLYRANCNFSM4TS7BFRA.

Hi Bart,
if you create a page with 10 blocks and another with only one block. You notice the speed difference between the two.
Also making Page.ss empty and reloading the page in the CMS, makes the difference clear.
In my case I have a page with multiple gallery blocks, a form and some basic content. Each block has approx. 6 large images.
Probably the larger the HTML source, the larger the images, the slower it gets.
Of course one could argue, to make the frontend faster, but this is not always easy.
Each time a user loads the page in the CMS the function getPageContent is called to render the entire HTML content and parse the DOM, but most of the time the module results are not needed, because user is only editing basic content:
public function getPageContent()
    {
        $response = Director::test($this->owner->Link());
        if (!$response->isError()) {
            return $response->getBody();
        }
        return '';
}

The server I use has 4 cores and 8GB memory. PHP memory_limit set to 512MB.
Regards,
Remy

Hi remy,
What about creating a setting to let a page type not reindex score always but do this reindexing score with a button/action in the cms?

In my testing, I've worked out that loading the edit page in the cms CMS causes the frontend page to render 7 times.
This is likely causing huge slowdowns considering that each call to getPageContent will also run any database queries invoked by the templates. Caching the return value of that function should speed up the score calculation.
I'll make a PR for this, but I'm going to target v2.2.1 first as that's what we're currently using and upgrading isn't an option for us at the moment.

In my tests just now, for a page with 2 blocks, caching the page content took load times from 23s to 5s.

I can't create a PR for 2.2.1 since there's no branch pointing to that version 😢.
Here's the code that I would have put in a PR
	public function getPageContent() {
		static $cache = [];

		if (!isset($cache[$this->owner->ID])) {
			Config::inst()->update('SSViewer', 'theme_enabled', true);
			$rendered_layout = $this->RenderLayout();
			Config::inst()->update('SSViewer', 'theme_enabled', false);

			$cache[$this->owner->ID] = $rendered_layout;
		}

		return $cache[$this->owner->ID];
	}

hi @OldStarchy
That's a great load time improvement! Why are you using 2.2.1?
I create tags (versions) from the master branch when i think it is 'releasable' as a version, not sure thats the way to go though. If you'd like I can create a branch for 2.2.1 if this helps? Or you can add this to master and then we create a new release/ tag from this ?

Why are you using 2.2.1?
Unfortunately upgrading to SS4 isn't an option for this project at the moment.

If you could create a 2 branch that would be great, I'll submit a PR for 2.2.2

not sure thats the way to go though
So long as it makes sense, its probably good enough

Or you can add this to master
I'll make 2 PRs, one for the 2 branch and one for master, which should get you a 2.2.2 tag as well as a 4.1.2 .

@OldStarchy Thanks a lot, i created the 2 branch! Hope this helps

During my testing on SS4 I've encountered an issue: https://github.com/silverstripe/silverstripe-framework/issues/10106


componentWillReceiveProps throws warning

WARN  Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://reactjs.org/link/unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state
Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 18.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: %s ActionButton
package.json
...
  "dependencies": {
    "react": "17.0.1",
    "react-native": "0.64.2",
    "react-native-action-button": "^2.8.5",

https://github.com/mastermoo/react-native-action-button/issues/365#issuecomment-797476260


protractor tests fail to click on Linux + Chrome 62

Bug report

Node Version: 6.10.2
Protractor Version: 5.2.0
Angular Version: 1.0
Browser(s): Chrome 62
Operating System and Version Ubuntu 14.04 (on CircleCI)

Sample test:
browser.get(homePageUrl)
  .then(() => $(emailSelector).click())
  .then(() => $(emailSelector).sendKeys(email))
  .then(() => $(passwordSelector).click())
  .then(() => $(passwordSelector).sendKeys(password))
  .then(() => $('#login_button').click());

The click to login used to work 100% and directs us to next page, now it fails 100%.  From the screenshot of the failure, it looks like it attempted to click but it doesn't go to the next page.
The only change was that chrome updated from 61 to 62.  This is happening for us on CircleCI where we install Chrome on the Ubuntu 14.04 container before running protractor.
We were able to work around this for now by downgrading back to Chrome 61 so it definitely seems like a regression caused by Chrome upgrading.  This does not repro on OSX

Hi @d3ming
On which version of ChromeDriver are you on? You should be on 2.33. Mostly this is an issue with a new version of Chrome and Chromedriver, not Protractor itself

Yeah I run webdriver-manager update before running protractor in CI, and it looks like it does update it to 2.33:
[localhost] local: ./node_modules/.bin/webdriver-manager update
[17:46:37] I/file_manager - creating folder /home/ubuntu/placelocal/node_modules/webdriver-manager/selenium
[17:46:38] I/update - chromedriver: unzipping chromedriver_2.33.zip
[17:46:38] I/update - chromedriver: setting permissions to 0755 for /home/ubuntu/placelocal/node_modules/webdriver-manager/selenium/chromedriver_2.33
[17:46:38] I/update - geckodriver: unzipping geckodriver-v0.19.0.tar.gz
[17:46:38] I/update - geckodriver: setting permissions to 0755 for /home/ubuntu/placelocal/node_modules/webdriver-manager/selenium/geckodriver-v0.19.0

So is this an issue that should get reported to https://github.com/SeleniumHQ/selenium/issues?

I tested it on my local machine and I don't have an issue with the clicks. This is my setup
Chrome: 62.0.3202.62
Chromedriver: 2.33
Node: v6.11.1
OS: 10.12.6
Protractor: 5.2.0

There are 144 scenario's with a lot of clicks and they all succeed.

@wswebcreation this issue only repros for me on Linux, specifically Ubuntu 14.04.  I also don't hit it on OSX 10.12.6

@d3ming
Sorry, I was focusing to much on the remark of @tricky21  and didn't read your last line. I would advice you to file a bug on the Chromedriver project with your config an an example script because it only happens with that specific config.
For now I'm going to close this issue.


Port Q.allSettled to $q

The allSettled method would function very similarly to all, but would additionally prevent reject or resolve from returning until all requests are completed.
See Q's documentation for details:
https://github.com/kriskowal/q#combination

Implemented this and added it to the bower registry: https://github.com/ohjames/angular-promise-extras


MiMC Hash Error

With the latest version: gnark v0.8.0 and gnark-crypto v0.10.0, the MiMC hash demo in the example directory cannot be successfully executed.
This is my mimc.go in mimchash folder:
package mimchash

import (
	"github.com/consensys/gnark/frontend"
	"github.com/consensys/gnark/std/hash/mimc"
)

// Circuit defines a pre-image knowledge proof
// mimc(secret preImage) = public hash
type Circuit struct {
	// struct tag on a variable is optional
	// default uses variable name and secret visibility.
	PreImage frontend.Variable
	Hash     frontend.Variable `gnark:",public"`
}

// Define declares the circuit's constraints
// Hash = mimc(PreImage)
func (circuit *Circuit) Define(api frontend.API) error {
	// hash function
	mc, _ := mimc.NewMiMC(api)

	// specify constraints
	// mc(preImage) == hash
	mc.Write(circuit.PreImage)
	api.AssertIsEqual(circuit.Hash, mc.Sum())

	return nil
}

And my mimc_test.go in mimchash folder:
package mimchash

import (
	"testing"

	"github.com/consensys/gnark-crypto/ecc"
	"github.com/consensys/gnark/test"
)

func TestPreimage(t *testing.T) {
	assert := test.NewAssert(t)

	var mimcCircuit Circuit

	assert.ProverFailed(&mimcCircuit, &Circuit{
		Hash:     42,
		PreImage: 42,
	})

	assert.ProverSucceeded(&mimcCircuit, &Circuit{
		PreImage: "16130099170765464552823636852555369511329944820189892919423002775646948828469",
		Hash:     "12886436712380113721405259596386800092738845035233065858332878701083870690753",
	}, test.WithCurves(ecc.BN254))

}

The error message:
# github.com/consensys/gnark/internal/backend/bls12-377/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bls12-381/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bw6-761/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bls24-317/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bls24-315/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bn254/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bw6-633/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bls12-377/groth16
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/groth16/prove.go:337:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/groth16/prove.go:338:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/groth16/prove.go:339:25: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-377/groth16/prove.go:357:32: cannot use true (untyped bool constant) as fft.Option value in argument to domain.FFTInverse
# github.com/consensys/gnark/internal/backend/bls12-381/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls12-381/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bls24-315/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-315/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bls24-317/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bls24-317/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bw6-761/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-761/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bn254/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bn254/plonkfri/setup.go:382:54: too many errors
# github.com/consensys/gnark/internal/backend/bw6-633/plonkfri
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/prove.go:490:41: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/prove.go:518:38: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFTInverse
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:212:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:213:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:214:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:215:65: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:352:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:353:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:354:55: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:382:54: cannot use true (untyped bool constant) as fft.Option value in argument to pk.Domain[1].FFT
../../../go/pkg/mod/github.com/consensys/gnark@v0.8.0/internal/backend/bw6-633/plonkfri/setup.go:382:54: too many errors

Compilation finished with exit code 1

And seems that the Hash of a secret and EdDSA signature examples in the gnark playground are also broken:

I encountered these issues when I was trying to build a signature proving scheme ten days ago. I hope the information can help address the problems if they exist.

these are 2 different issues, thanks for the detail report; the playground examples are broken because the witness doesn't match the underlying mimc impl (we will fix that).
The other issue with go dep, see #638

playground fixed 👍


Make  open if there is an #id in the URL

I'm probably not the best person to review the browser polyfill - but other than my query above, I think this is fine :)


no-proxy option closes prematurely

I expected -no-proxy to launch ggst patching it to request on <IP_ADDRESS>:21611 but it appears it only launch ggst vanilla

Ah, this is a race condition that I didn't catch when I was testing it. Thanks for the report. Will look into fixing this.


update .NET Framework to .NET in csharp/languagereferences where applicable

Summary
Updating mentions of .NET Framework to .NET only on csharp/language-reference where applicable. It turns out there are no applicable updates are necessary because many of the doc pages are already mentioning the .NET Framework specifics.
For example, as far as I know existing csharp/language-reference/langversion-compiler-option.md has mentions of .NET Framework but these .NET Framework mentions are correct. Because these mentions are explaining the historical of language features that comes originally from .NET Framework releases.
Also correct minor terms of .Net Framework to .NET and a minor grammar correction.
Fixes #18697 (partially)
@gewarren
Please review, and if you don't mind could you update the check mark in the issue description of #18697 for csharp/language-reference as completed?
CMIIW, there are no work left on the csharp/language-reference to update from .NET Framework to .NET.

@gewarren
Thanks for the review! I've updated as suggested.

@eriawan Thank you!


Unnecessary parentheses in element access expressions

Input:
var r = window[`${ "doc" }ument`];

Expected:
var r = window["doc" + "ument"];

Actual:
var r = window[("doc" + "ument")];

Seems fixed (tested with playground). I unknown what version/commit fixed it (maybe the referenced pull).


Security Risks for Existing Validators?

What are the main security risks for a validator to consider before implementing mev-boost on mainnet?
From my short time researching, it appears that with the current design of using a builder, relay, validator, the validator can be slashed from the relay trivially. Is that accurate or am I misunderstanding it only as a penalty offense such as a missed proposal instead of a full 16ETH slashing?

This is inaccurate -- slashing would only occur in the case of double-signing, which is not a risk that using the external builder network poses. See also https://www.bloxstaking.com/blog/ethereum-2-0/understanding-eth2-slashing-preventative-measures/ for more about slashing.

This is incorrect -- slashing would only occur in the case of double-signing, which is not a risk that using the external builder network poses. See also https://www.bloxstaking.com/blog/ethereum-2-0/understanding-eth2-slashing-preventative-measures/ for more about slashing.

Interesting answer. Its hard to believe MEV Boost does come without any risks. For every software module there are risks, known risks and unknown risks. I think there are some possibilities to get rekt by this implementation but time will tell. Would be great for more analysing what could go wrong. Slashing is not only in case of double-signing, there are some more circumstances to get slashed for misbehaviour in proposing (wrong) blocks.

@ChuckNorrison you can find the first audit of MEV-Boost here. I tried to add specifics of what the validators making use of MEV-Boost are assuming and what type of behavior could introduce risks to the validators.

Slashing is not only in case of double-signing, there are some more circumstances to get slashed for misbehavior in proposing (wrong) blocks.

In the current specification, relayers are the actors in charge of validating that blocks coming from builders are valid. Validator client implementations could also validate that the blocks received are valid before including them in the canonical change.

The reason I bring up this question is due to this topic discussion on ethresear.ch
https://ethresear.ch/t/mev-boost-merge-ready-flashbots-architecture/11177

What is the maximum damage that a malicious relayer could cause after a validator returns a signed header?

Slashing is not only in case of double-signing, there are some more circumstances to get slashed for misbehaviour in proposing (wrong) blocks.
@ChuckNorrison a proposer cannot be slashed for an invalid block, they can only be slashed if they sign two valid but otherwise different blocks

and for those reading the condition that you do not sign two conflicting blocks would (and should) be managed outside the mev-boost software

What is the maximum damage that a malicious relayer could cause after a validator returns a signed header?

the only thing they could do at this point to cause any damage is withhold the execution payload the proposer is committing to via the signing of the header