Fix twig environment

Fix #578
Credit to @RomainMazB

Well it's somewhat hacky, but I don't have any major concerns with it. @bennothommo any thoughts?

@mjauvin @RomainMazB is controller the only one needed? Would we need to support the other variables too, as per the Markup docs like this.page, this.layout, etc.?

@bennothommo, all the needed variables is mentioned here in the code: https://github.com/wintercms/winter/blob/b90b4fe869011f2ad8c33b3d0750bdb16db9fc17/modules/cms/classes/Controller.php#L309-L317
Kind of surprised that add variables as global is an acceptable fix, sounds to me like a regression compared to the work made by @LukeTowers in PR #455 but I'm no the guy in charge here ;)

I discussed with @mjauvin on Discord about a related issue he met with the plugin: vojtasvoboda /
DynamicPDF.
He discovered that this issue is not only under the macro scope as the issue appeared within this plugin without the use of macro.
The plugin uses the registered twig.environment Facade from the system module to parse templates into an html page and then render it as a PDF file.
The plugin parses templates without being in any controller context, which results to the same "undefined this issue".
I may investigate furthermore on how to solve these issues without adding global variables, but as of today, re-introducing a global scope may be the best affordable solution.
For the needed variables: to me, even if I only use the controller variable through the |page filter, I guess that all the variable I mentioned earlier may be needed by anyone else.
An example would be the access to a theme color config from a macro, or an url param using this.param.

Hmm, the global variables solution might not be enough then. With regards to the DynamicPDF plugin that's a separate issue, if someone wants to use the CMS twig environment to render a twig template then they need to refer to the correct namespace for it; we're not going to make the CMS features available in the system twig environment.
@RomainMazB What was the other solution that you proposed regarding overriding the processing of Macros in order to inject the correct context information into it? That sounds like that would be a better fix, especially when you consider a template itself might inject variables into the context that we might not have access to if we just go the global variable route.

This is still a breaking change @LukeTowers. If many plugins start breaking
for 1.2, this is not going to be a fun ride.
--
Marc
On Mon., Jul. 4, 2022, 17:10 Luke Towers, @.***> wrote:

Hmm, the global variables solution might not be enough then. With regards
to the DynamicPDF plugin that's a separate issue, if someone wants to use
the CMS twig environment to render a twig template then they need to refer
to the correct namespace for it; we're not going to make the CMS features
available in the system twig environment.
@RomainMazB https://github.com/RomainMazB What was the other solution
that you proposed regarding overriding the processing of Macros in order to
inject the correct context information into it? That sounds like that would
be a better fix, especially when you consider a template itself might
inject variables into the context that we might not have access to if we
just go the global variable route.
—
Reply to this email directly, view it on GitHub
https://github.com/wintercms/winter/pull/593#issuecomment-1174368974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPLTPQKRC7Z4P6JWAB4UKTVSNHMTANCNFSM52RNGFEQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@LukeTowers, I just finished to work on my day project, I'll try to make a draft PR to see if what I'd suggested would work and if it could be more appropriate.

@mjauvin I don't see how it is, the System twig environment was never meant to have CMS features in it and before the changes I made in my PR to separate everything there were all sorts of issues that would crop up if you were to initialize it before doing things like sending emails for example.
Could you clarify what the BC break is?

@mjauvin @RomainMazB would either of you be interested in making a unit test for both scenarios (the macro issue, and the issue from the Dynamic PDF plugin)? It would be worth it at least to ensure that any given solution we implement covers both scenarios.
Also, as for backwards compatibility - while it is one of our main goals, our major updates like with 1.2 does give us the leeway to make some backwards-incompatible changes if they are strongly justified. I am in agreement with Luke's rationale for the Twig changes in the first place, and reverting it back to fix these new issues is just going to bring back the issues that Luke's changes fixed.

I have a solution I made on my local machine, at least for the macro issue.
I was searching for any more convenient way before post it as a PR.
I'll post my code as a draft PR as soon as I am at home.
I didn't write tests for it atm.

@RomainMazB @mjauvin I have confirmed that you will need the other variables as mentioned here defined in the globals if you want to support this.theme or this.page within a macro.
For example, using {{ this.page.fileName }} outside a macro will work fine, and uses the vars from the block of code that @RomainMazB mentioned here, but using that inside a macro will come up blank.

@bennothommo I'm hoping that @RomainMazB's suggestion of overriding the macro handling to include the correct context will pan out and we don't need to define a bunch of globals, especially since some of those don't exist when we would typically be defining the globals.

I just tried to do that very thing. If Maz has worked that one out, he's a genius. 😜

I just tried to do that very thing. If Maz has worked that one out, he's a genius. :stuck_out_tongue_winking_eye:

Probably not a genius yet! I'm not fully convinced of the actual draft work: #598
It can be a starting point, at least it works.

Replaced by https://github.com/wintercms/winter/commit/5b8d189df4cd1f7fdf8e318f111543b85a0e2613


bug: dagstore recognizes empty EDS but cannot find file

Recently, @jcstein stumbled upon a bug where the dagstore knew about the empty EDS (it was in its index), but the shard file did not exist on disk. It needs to be investigated further how this happened, and if it involved swapping out node stores.
celestia full start --p2p.network blockspacerace --core.ip https://rpc-blockspacerace.pops.one --gateway --gateway.addr <IP_ADDRESS> --gateway.port 26659
2023-05-17T21:05:13.482Z	INFO	node	nodebuilder/module.go:22	Accessing keyring...
2023-05-17T21:05:13.548Z	INFO	module/state	state/keyring.go:40	constructed keyring signer	"backend": "test", "path": "/root/.celestia-full-blockspacerace-0/keys", "key name": "my_celes_key", "chain-id": "blockspacerace-0"}
2023-05-17T21:05:13.553Z	WARN	module/gateway	gateway/module.go:25	Gateway is enabled, however gateway endpoints are not authenticated. Use with caution!
2023-05-17T21:05:14.123Z	INFO	badger	v2@v2.2007.4/levels.go:183	All 28 tables opened in 479ms

2023-05-17T21:05:14.127Z	INFO	badger	v2@v2.2007.4/value.go:1158	Replaying file id: 20 at offset: 33280730

2023-05-17T21:05:14.127Z	INFO	badger	v2@v2.2007.4/value.go:1178	Replay took: 2.98µs

2023/05/17 21:05:14 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023-05-17T21:05:14.181Z	INFO	module/header	header/config.go:58	No trusted peers in config, initializing with default bootstrappers as trusted peers
2023-05-17T21:05:15.194Z	INFO	share/discovery	discovery/discovery.go:253	discovering peers	"want": 5}
2023-05-17T21:05:15.937Z	INFO	share/discovery	discovery/discovery.go:315	discovered wanted peers	{"amount": 5}
2023-05-17T21:05:15.957Z	INFO	share/discovery	discovery/discovery.go:315	discovered wanted peers	{"amount": 6}
2023-05-17T21:05:19.508Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "3503C58BA7A2AC72A797A01EA250110026CAEFBE0976915F21F9CFAEB52096A1", "error": "failed to acquire reader of mount so we can return the accessor: open /root/.celestia-full-blockspacerace-0/blocks/3503C58BA7A2AC72A797A01EA250110026CAEFBE0976915F21F9CFAEB52096A1: no such file or directory"}
2023-05-17T21:05:19.509Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "E5B09E7509FD65B254B9E7133B2F0F2AE9D05B5D11488D77D056A7CF877C53C7", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/E5B09E7509FD65B254B9E7133B2F0F2AE9D05B5D11488D77D056A7CF877C53C7: no such file or directory"}
2023-05-17T21:05:19.518Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "4D9026169ABF1746414AD601C5CC30A1402ED073A19F6369018546677395BBA1", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/4D9026169ABF1746414AD601C5CC30A1402ED073A19F6369018546677395BBA1: no such file or directory"}
2023-05-17T21:05:19.524Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "BA6B1BD30023126BCD64EEF92A9A73F4AEF69D9B8D99B81633E550D228401A21", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/BA6B1BD30023126BCD64EEF92A9A73F4AEF69D9B8D99B81633E550D228401A21: no such file or directory"}
2023-05-17T21:05:19.525Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "98532D51E06AC3980F3DD59834456820C3E38DEA07971251DD077CE05046DA6E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/98532D51E06AC3980F3DD59834456820C3E38DEA07971251DD077CE05046DA6E: no such file or directory"}
2023-05-17T21:05:19.526Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "31D80C9AEACBE2CEC222C942A4FD2DE296821E0AC75C661FB0B3E8B8F3D6951B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/31D80C9AEACBE2CEC222C942A4FD2DE296821E0AC75C661FB0B3E8B8F3D6951B: no such file or directory"}
2023-05-17T21:05:19.527Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "45C549E5D667D4D244AB328B5BA6F5FC94DF98BFC83BA0E976897A11357C3F8E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/45C549E5D667D4D244AB328B5BA6F5FC94DF98BFC83BA0E976897A11357C3F8E: no such file or directory"}
2023-05-17T21:05:19.528Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "38214880B98A1A8AB4E2E35B533DA68C65026DED126D4631DA583717E61A2D66", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/38214880B98A1A8AB4E2E35B533DA68C65026DED126D4631DA583717E61A2D66: no such file or directory"}
2023-05-17T21:05:19.528Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "A68FE0DE48F1B2AE40D7C48A490B178267C477D8C0F93FF6ED3446BE35DBF562", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/A68FE0DE48F1B2AE40D7C48A490B178267C477D8C0F93FF6ED3446BE35DBF562: no such file or directory"}
2023-05-17T21:05:19.528Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "6648AD46F51FFF9BC922A0EAD628B556B0BD9AEC10E879861F3F4E6B4D9EB309", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/6648AD46F51FFF9BC922A0EAD628B556B0BD9AEC10E879861F3F4E6B4D9EB309: no such file or directory"}
2023-05-17T21:05:19.529Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "B717ED6BB8FF05DE271F4A59F5E024B05C88D7174AA9F23D85E05C51F1F61A6E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/B717ED6BB8FF05DE271F4A59F5E024B05C88D7174AA9F23D85E05C51F1F61A6E: no such file or directory"}
2023-05-17T21:05:19.529Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "542B0B9CBF1DC386FE86B7AF11AEF5FC65193C790F49DF30C8E53EA2232886B3", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/542B0B9CBF1DC386FE86B7AF11AEF5FC65193C790F49DF30C8E53EA2232886B3: no such file or directory"}
2023-05-17T21:05:19.529Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "DBCE0B895BF6C9C7536F04D7AC25977F12226533239053435E4E56FE6C559B9B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/DBCE0B895BF6C9C7536F04D7AC25977F12226533239053435E4E56FE6C559B9B: no such file or directory"}
2023-05-17T21:05:19.529Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7406A8192705C0AC54A6CF1A9C496C0E2DF9A52D746484BB4AAEB79C48199EE2", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7406A8192705C0AC54A6CF1A9C496C0E2DF9A52D746484BB4AAEB79C48199EE2: no such file or directory"}
2023-05-17T21:05:19.530Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "85BDF9C1C7E6E3F8F2295F09E35E1FDBBA7A22328E54CF7B51E2DDB8158D0604", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/85BDF9C1C7E6E3F8F2295F09E35E1FDBBA7A22328E54CF7B51E2DDB8158D0604: no such file or directory"}
2023-05-17T21:05:19.530Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "613F0633F4038D9A01C10CDC6337C5694ECDD7B6519A6992CA3D1DEDEC77F819", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/613F0633F4038D9A01C10CDC6337C5694ECDD7B6519A6992CA3D1DEDEC77F819: no such file or directory"}
2023-05-17T21:05:19.530Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7E22E093AEE56F9428B25D0A246FDEEABD217E8C60C415C3372295D939928585", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7E22E093AEE56F9428B25D0A246FDEEABD217E8C60C415C3372295D939928585: no such file or directory"}
2023-05-17T21:05:19.530Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "10673CD31DCD6BF6F37EBFF0D2C0091EDF68E7BC64CDC09BC6168515692383D6", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/10673CD31DCD6BF6F37EBFF0D2C0091EDF68E7BC64CDC09BC6168515692383D6: no such file or directory"}
2023-05-17T21:05:19.530Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "54E1EE8658442FBEBA66243E150195CB05D8ECA421594956A92F7E939C358190", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/54E1EE8658442FBEBA66243E150195CB05D8ECA421594956A92F7E939C358190: no such file or directory"}
2023-05-17T21:05:19.531Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "4DA4678FA181BCFA5CDF4AF95586277B487D49975F26F2337EA356E846544681", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/4DA4678FA181BCFA5CDF4AF95586277B487D49975F26F2337EA356E846544681: no such file or directory"}
2023-05-17T21:05:19.531Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "97803446C78D5DE7907ABFE7355C19D272837D99CC423267AB633C9C9A5CC1E3", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/97803446C78D5DE7907ABFE7355C19D272837D99CC423267AB633C9C9A5CC1E3: no such file or directory"}
2023-05-17T21:05:19.531Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "CFA2FC26D199A920417B3F3F0B5FD08C8053930BED7CE134E1CE215B85BF5958", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/CFA2FC26D199A920417B3F3F0B5FD08C8053930BED7CE134E1CE215B85BF5958: no such file or directory"}
2023-05-17T21:05:19.531Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "AB99F6C63A7F0833F9BD0A02F97E56D4D0F65CA4596083981B70A26187F5C044", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/AB99F6C63A7F0833F9BD0A02F97E56D4D0F65CA4596083981B70A26187F5C044: no such file or directory"}
2023-05-17T21:05:19.532Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "37566D6A4A833AA25A6AEC962FE81EFF94E9658F11836359E640D00C799E66DC", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/37566D6A4A833AA25A6AEC962FE81EFF94E9658F11836359E640D00C799E66DC: no such file or directory"}
2023-05-17T21:05:19.533Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C4155522638C91B05BFCF258650AC4E53CE1167AD53C757B9E923B973F6341E0", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C4155522638C91B05BFCF258650AC4E53CE1167AD53C757B9E923B973F6341E0: no such file or directory"}
2023-05-17T21:05:19.533Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "EBFF8DA5536F01F8C499DCFB729EC1CCFCA903223D12106959F90EC1D7407B21", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/EBFF8DA5536F01F8C499DCFB729EC1CCFCA903223D12106959F90EC1D7407B21: no such file or directory"}
2023-05-17T21:05:19.533Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7FA1DA23255AA6CBD3659C57216E6B5281B11C50D812E4466EC6A87DBEF33FF8", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7FA1DA23255AA6CBD3659C57216E6B5281B11C50D812E4466EC6A87DBEF33FF8: no such file or directory"}
2023-05-17T21:05:19.534Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "DD538F26BE26E6B7DA611AFEB60C0480D7D5290D9B0D3B3B32B1838A9893EF7D", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/DD538F26BE26E6B7DA611AFEB60C0480D7D5290D9B0D3B3B32B1838A9893EF7D: no such file or directory"}
2023-05-17T21:05:19.534Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "1A4C6C7D2F87B14E4AC25B35E518FCAE6E735F582110B37A428EC7B52C52BEE3", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/1A4C6C7D2F87B14E4AC25B35E518FCAE6E735F582110B37A428EC7B52C52BEE3: no such file or directory"}
2023-05-17T21:05:19.535Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "87556F5EB6CE7B2D38FFDBFEAFD358C0D95CC852D0878B66EF95E2103275AE6B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/87556F5EB6CE7B2D38FFDBFEAFD358C0D95CC852D0878B66EF95E2103275AE6B: no such file or directory"}
2023-05-17T21:05:19.535Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "971EAD34C6C7E316E9FC7BE5E7FD2B1BD57DA56E03F1657A75B8136A09331835", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/971EAD34C6C7E316E9FC7BE5E7FD2B1BD57DA56E03F1657A75B8136A09331835: no such file or directory"}
2023-05-17T21:05:19.535Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "F7FDE75257560839D7432D19B39C6475A522AB6B68A340E191A456926E98EACC", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/F7FDE75257560839D7432D19B39C6475A522AB6B68A340E191A456926E98EACC: no such file or directory"}
2023-05-17T21:05:19.535Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "9A2A8AA7173EBF53024E7C85F96581A89E82ABBD4109A86AF84562A0A2B2C7EE", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/9A2A8AA7173EBF53024E7C85F96581A89E82ABBD4109A86AF84562A0A2B2C7EE: no such file or directory"}
2023-05-17T21:05:19.536Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "AB6CA4ECBE3B4E659E310084F696DD27D16102267C340B9A7BB10D0C670EBA39", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/AB6CA4ECBE3B4E659E310084F696DD27D16102267C340B9A7BB10D0C670EBA39: no such file or directory"}
2023-05-17T21:05:19.538Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "5736E185E5927D7D273419906F84126AE0D2052907BBB85E530BC54D83EBCAF1", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/5736E185E5927D7D273419906F84126AE0D2052907BBB85E530BC54D83EBCAF1: no such file or directory"}
2023-05-17T21:05:19.539Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "8ED2AA8E85CF6DE4D4B921D366BD926AFE35263601F8F2F4C16B91B0C59B1C01", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/8ED2AA8E85CF6DE4D4B921D366BD926AFE35263601F8F2F4C16B91B0C59B1C01: no such file or directory"}
2023-05-17T21:05:19.539Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "4F1F1DE3425ADCFF77F07300E62EF642979A925A59DC3BD2D0228C5E461A0B62", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/4F1F1DE3425ADCFF77F07300E62EF642979A925A59DC3BD2D0228C5E461A0B62: no such file or directory"}
2023-05-17T21:05:19.541Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "5CF39C034FEAE10452274C132D349325CBB4E3DE7404A9A53CE039D755D540A7", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/5CF39C034FEAE10452274C132D349325CBB4E3DE7404A9A53CE039D755D540A7: no such file or directory"}
2023-05-17T21:05:19.544Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "29870AAC41F9A13AC13573E426497CB22DA1B1F3B2782A087D42C41587E624D6", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/29870AAC41F9A13AC13573E426497CB22DA1B1F3B2782A087D42C41587E624D6: no such file or directory"}
2023-05-17T21:05:19.544Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "07DF1795D36A30434EB89058EE4F24DCBDB0467E7E0A7F64A0BA3953236E2140", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/07DF1795D36A30434EB89058EE4F24DCBDB0467E7E0A7F64A0BA3953236E2140: no such file or directory"}
2023-05-17T21:05:19.544Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7A0E48D9D4DBDF01305597A882F678BD4024B3058BD3A5CC30FC0CD673969175", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7A0E48D9D4DBDF01305597A882F678BD4024B3058BD3A5CC30FC0CD673969175: no such file or directory"}
2023-05-17T21:05:19.545Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C617C83D59DBAA5A663038B717B062CFFF4D1E781F361EE1CB13A716531093DA", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C617C83D59DBAA5A663038B717B062CFFF4D1E781F361EE1CB13A716531093DA: no such file or directory"}
2023-05-17T21:05:19.546Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0381EC81C061EDCE4CA8DA41692512E52F10F842FCC224DECFF3FD0CC78F8D6C", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0381EC81C061EDCE4CA8DA41692512E52F10F842FCC224DECFF3FD0CC78F8D6C: no such file or directory"}
2023-05-17T21:05:19.546Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "6CC9A56E8F3A354853ED04C98BA784716D47525EADBF94B5C80DD83B514AE390", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/6CC9A56E8F3A354853ED04C98BA784716D47525EADBF94B5C80DD83B514AE390: no such file or directory"}
2023-05-17T21:05:19.547Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "8A0912944ECC1C3F602A53C34CDACD90D0C19358598F40B87780EA0855E1CFD6", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/8A0912944ECC1C3F602A53C34CDACD90D0C19358598F40B87780EA0855E1CFD6: no such file or directory"}
2023-05-17T21:05:19.547Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "9AAF112395CC875F83359CA536FA45FED4BB570F2B3E6A6C88500E0AE2E487B8", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/9AAF112395CC875F83359CA536FA45FED4BB570F2B3E6A6C88500E0AE2E487B8: no such file or directory"}
2023-05-17T21:05:19.547Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "967BD2B122A3B9B41F80071906F33DE3078D7CD5C254E34350B419AF8C735144", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/967BD2B122A3B9B41F80071906F33DE3078D7CD5C254E34350B419AF8C735144: no such file or directory"}
2023-05-17T21:05:19.549Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "37BE9587F208878428C98ACD4299EE48F48DDFAB74FF61314EC81F9E6BA0C421", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/37BE9587F208878428C98ACD4299EE48F48DDFAB74FF61314EC81F9E6BA0C421: no such file or directory"}
2023-05-17T21:05:19.551Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "B527016BF609D5F2DA6CBF9BF1450389A8E4DB299A4DAFC013F5D7E7A14DCE55", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/B527016BF609D5F2DA6CBF9BF1450389A8E4DB299A4DAFC013F5D7E7A14DCE55: no such file or directory"}
2023-05-17T21:05:19.551Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "A819D3F4DFC18D604BC95DF0F8A88BDBA524EE0EEB127E6EAF264C47947F1E1D", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/A819D3F4DFC18D604BC95DF0F8A88BDBA524EE0EEB127E6EAF264C47947F1E1D: no such file or directory"}
2023-05-17T21:05:19.551Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C71B7A418522C1F1CBC3C63D8DA962A9B5C82928AD29D24310192BD050098B8D", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C71B7A418522C1F1CBC3C63D8DA962A9B5C82928AD29D24310192BD050098B8D: no such file or directory"}
2023-05-17T21:05:19.551Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "203314D6532CC45E53F8E8D0426BB5ED54AAD1E5487016C1E31A54046B9A1C68", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/203314D6532CC45E53F8E8D0426BB5ED54AAD1E5487016C1E31A54046B9A1C68: no such file or directory"}
2023-05-17T21:05:19.552Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "4531CA440A26B0B3A69B81BCA7427326B88822A06E9E3BBB3281E11AB94B5CBF", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/4531CA440A26B0B3A69B81BCA7427326B88822A06E9E3BBB3281E11AB94B5CBF: no such file or directory"}
2023-05-17T21:05:19.552Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "37E869B36D76D0E4A04859A25AFE66E8C52ABF9A39152971E5288D629DC545B5", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/37E869B36D76D0E4A04859A25AFE66E8C52ABF9A39152971E5288D629DC545B5: no such file or directory"}
2023-05-17T21:05:19.552Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "85851ACCEEF150BAE658DAB4D9F84BBD9210360EBD6DDE352405BBE0409E8B98", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/85851ACCEEF150BAE658DAB4D9F84BBD9210360EBD6DDE352405BBE0409E8B98: no such file or directory"}
2023-05-17T21:05:19.552Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "BEE3AF29760E4656F231385BDC3BFA4E9D5917B518C66FB13EC6E17731C54385", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/BEE3AF29760E4656F231385BDC3BFA4E9D5917B518C66FB13EC6E17731C54385: no such file or directory"}
2023-05-17T21:05:19.553Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0C171065002DE6FD5D5ACDFC1985FEAEB8331618F1FB7DD034A58AEB6AAC7FAD", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0C171065002DE6FD5D5ACDFC1985FEAEB8331618F1FB7DD034A58AEB6AAC7FAD: no such file or directory"}
2023-05-17T21:05:19.553Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "9628197B96CFBDCB7D65BF436888047AB627187FAA63A800FCD871FF57B7C773", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/9628197B96CFBDCB7D65BF436888047AB627187FAA63A800FCD871FF57B7C773: no such file or directory"}
2023-05-17T21:05:19.553Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "1C7ABF1525C0285EDD0D3CD3C2647D382AFC1FD3821A2A01363F36FD9C3F7CE9", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/1C7ABF1525C0285EDD0D3CD3C2647D382AFC1FD3821A2A01363F36FD9C3F7CE9: no such file or directory"}
2023-05-17T21:05:19.553Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "E0F3D989A3839D6EFE63AAC417F80E7BE5F069D913833DCCCD8FD233A2D76D10", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/E0F3D989A3839D6EFE63AAC417F80E7BE5F069D913833DCCCD8FD233A2D76D10: no such file or directory"}
2023-05-17T21:05:19.553Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "587F8AAFF78BF70155B5A0800555DD2C7A05B04040E416D70DDF62C9F0F79DF5", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/587F8AAFF78BF70155B5A0800555DD2C7A05B04040E416D70DDF62C9F0F79DF5: no such file or directory"}
2023-05-17T21:05:19.554Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "57136CB87227BE60F8E6FE018D281F4822F9FF8C42873490E6837B5ED8895F7B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/57136CB87227BE60F8E6FE018D281F4822F9FF8C42873490E6837B5ED8895F7B: no such file or directory"}
2023-05-17T21:05:19.554Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "17D002496D067318DD667DD0FD30F6DC885789D041D1A1B1145220B12A933CB2", "error": "failed to acquire reader of mount so we can return the accessor: open /root/.celestia-full-blockspacerace-0/blocks/17D002496D067318DD667DD0FD30F6DC885789D041D1A1B1145220B12A933CB2: no such file or directory"}
2023-05-17T21:05:19.554Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "2849C0A4A5AC7F5C55E9480F4F2D54D18089434A17681E0787FEFF3A6B9086CC", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/2849C0A4A5AC7F5C55E9480F4F2D54D18089434A17681E0787FEFF3A6B9086CC: no such file or directory"}
2023-05-17T21:05:19.555Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "DE2668BAAA1794BD910C4B379056CFA4E0BC8CC827480FCC1ACD49EE20A57C7B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/DE2668BAAA1794BD910C4B379056CFA4E0BC8CC827480FCC1ACD49EE20A57C7B: no such file or directory"}
2023-05-17T21:05:19.555Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "650065B99D87188F9B41B0E5555727E616EA89BE721DC2B4EF674B7BFC6723A4", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/650065B99D87188F9B41B0E5555727E616EA89BE721DC2B4EF674B7BFC6723A4: no such file or directory"}
2023-05-17T21:05:19.555Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "A16FD94D0637E4F8A15A23AB795D47FD04F089B0B5A512AB02616A17952D8604", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/A16FD94D0637E4F8A15A23AB795D47FD04F089B0B5A512AB02616A17952D8604: no such file or directory"}
2023-05-17T21:05:19.555Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "FED221951845D807FE300B95EA6E92D4B38372A4573864197550015A3B700712", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/FED221951845D807FE300B95EA6E92D4B38372A4573864197550015A3B700712: no such file or directory"}
2023-05-17T21:05:19.556Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "632E12F523CA9BFE002574FA6AD74A792D68107A72E82B9F4B7BE8FCCA69513E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/632E12F523CA9BFE002574FA6AD74A792D68107A72E82B9F4B7BE8FCCA69513E: no such file or directory"}
2023-05-17T21:05:19.556Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "E7FC5D7D7D3DA18A5532E8FC27E295E89B6729B7460C61273884C51C26B4187C", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/E7FC5D7D7D3DA18A5532E8FC27E295E89B6729B7460C61273884C51C26B4187C: no such file or directory"}
2023-05-17T21:05:19.557Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0AA751B5DFD778295A38D8B71E499CBDFC0C19EF9AAEB18581B4599E0028E447", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0AA751B5DFD778295A38D8B71E499CBDFC0C19EF9AAEB18581B4599E0028E447: no such file or directory"}
2023-05-17T21:05:19.557Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "B18F218D34644EC64C8F9D362ACEA90EAF312FA751D0D5DBF89F6DB3FF5BD4BA", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/B18F218D34644EC64C8F9D362ACEA90EAF312FA751D0D5DBF89F6DB3FF5BD4BA: no such file or directory"}
2023-05-17T21:05:19.557Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C70535FCC1E8D141C7988AA7405C2C79534C1751A2C8B6912AD6660FD123E8C5", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C70535FCC1E8D141C7988AA7405C2C79534C1751A2C8B6912AD6660FD123E8C5: no such file or directory"}
2023-05-17T21:05:19.557Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "805D88E91D4648DCECA8DB242F246D6EF03B9A2DEBA5D950BDAA614DFFAFDC00", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/805D88E91D4648DCECA8DB242F246D6EF03B9A2DEBA5D950BDAA614DFFAFDC00: no such file or directory"}
2023-05-17T21:05:19.557Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "14F6E73427EF121EAD288A77711CF8390B2FC04B9992EDF2B5FD762453CBE681", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/14F6E73427EF121EAD288A77711CF8390B2FC04B9992EDF2B5FD762453CBE681: no such file or directory"}
2023-05-17T21:05:19.558Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "46F5665C7583A9B082BF4772762CE7516639A22D54F2F06241A0AE2AAD6F8AE1", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/46F5665C7583A9B082BF4772762CE7516639A22D54F2F06241A0AE2AAD6F8AE1: no such file or directory"}
2023-05-17T21:05:19.558Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7D3A906E0BF3E12C8CF2A8C1734D34B898DFC783770BBE7C69C94456BCA4F0F2", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7D3A906E0BF3E12C8CF2A8C1734D34B898DFC783770BBE7C69C94456BCA4F0F2: no such file or directory"}
2023-05-17T21:05:19.558Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0FDF60066E64FE095192C6242209FCAA172B17CF1E660A5F6A5CF2317B8EA014", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0FDF60066E64FE095192C6242209FCAA172B17CF1E660A5F6A5CF2317B8EA014: no such file or directory"}
2023-05-17T21:05:19.558Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0267C545F066CD5B639732206C88E2256B3C575F5EDF6E7DCEC9CC64B832496E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0267C545F066CD5B639732206C88E2256B3C575F5EDF6E7DCEC9CC64B832496E: no such file or directory"}
2023-05-17T21:05:19.559Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "28149F9564EBCBF3E150A116DA25A75F36B07A2E1506E533443233B766C842C6", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/28149F9564EBCBF3E150A116DA25A75F36B07A2E1506E533443233B766C842C6: no such file or directory"}
2023-05-17T21:05:19.559Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "B12232994198544F0C654113AF8FD35146580D1976B93B15EB6AFB81DFF5203E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/B12232994198544F0C654113AF8FD35146580D1976B93B15EB6AFB81DFF5203E: no such file or directory"}
2023-05-17T21:05:19.559Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "4718C97A324E090ECE88C822B57680689F7C8CBDEA4F7F26AD6373D34560E4ED", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/4718C97A324E090ECE88C822B57680689F7C8CBDEA4F7F26AD6373D34560E4ED: no such file or directory"}
2023-05-17T21:05:19.560Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "94B6D0B3E1C00954D08A35E99195983733776CF0A6F17E74D30D9EC2F4E09147", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/94B6D0B3E1C00954D08A35E99195983733776CF0A6F17E74D30D9EC2F4E09147: no such file or directory"}
2023-05-17T21:05:19.560Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "95D652B7688E1A03CC3268343E987F20E17258A6CF4C7FD2F23FBF3DEAB1AD2F", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/95D652B7688E1A03CC3268343E987F20E17258A6CF4C7FD2F23FBF3DEAB1AD2F: no such file or directory"}
2023-05-17T21:05:19.561Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "96C52AA3FF2425A9F17DD856E7029EE23504745230389147AF473308A9134F6A", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/96C52AA3FF2425A9F17DD856E7029EE23504745230389147AF473308A9134F6A: no such file or directory"}
2023-05-17T21:05:19.561Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "1DCC62A0062CBC75D77464991F12F9CE58628F80C0E474A329C4AC4400F78A69", "error": "failed to acquire reader of mount so we can return the accessor: open /root/.celestia-full-blockspacerace-0/blocks/1DCC62A0062CBC75D77464991F12F9CE58628F80C0E474A329C4AC4400F78A69: no such file or directory"}
2023-05-17T21:05:19.561Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7B7EBBB22C6CE11A1420A788171F8D7EE2365354AA720ED9A4D6EBE0CE209A65", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7B7EBBB22C6CE11A1420A788171F8D7EE2365354AA720ED9A4D6EBE0CE209A65: no such file or directory"}
2023-05-17T21:05:19.562Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "98CE6A0C5401B98544B95A6B8D3929C493AC5914E2B431FC5445EACABABF7C97", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/98CE6A0C5401B98544B95A6B8D3929C493AC5914E2B431FC5445EACABABF7C97: no such file or directory"}
2023-05-17T21:05:19.562Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C52B71A0B69B1276E02A4042D5D355D3D712A4F613F9708A3F830B41D19D5822", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C52B71A0B69B1276E02A4042D5D355D3D712A4F613F9708A3F830B41D19D5822: no such file or directory"}
2023-05-17T21:05:19.563Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "011A58DC81BA7F9ED502E1FF29B4C692DBE6F594738F78F19AA2FCE4ADF5999B", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/011A58DC81BA7F9ED502E1FF29B4C692DBE6F594738F78F19AA2FCE4ADF5999B: no such file or directory"}
2023-05-17T21:05:19.563Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "5D15F9269B73FFCC944428474B0E40D114A1894EBACF878B621FA5E2C0AF3FFF", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/5D15F9269B73FFCC944428474B0E40D114A1894EBACF878B621FA5E2C0AF3FFF: no such file or directory"}
2023-05-17T21:05:19.564Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "517287ED383ECEB8EE90D37D3F1DF347B8BBA5BF0C281E82EAD5F8B81BB13B86", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/517287ED383ECEB8EE90D37D3F1DF347B8BBA5BF0C281E82EAD5F8B81BB13B86: no such file or directory"}
2023-05-17T21:05:19.564Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0E1433A7ABB5677235D18472D028CD7A01682D4785BF9F579F6C734518107E1C", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0E1433A7ABB5677235D18472D028CD7A01682D4785BF9F579F6C734518107E1C: no such file or directory"}
2023-05-17T21:05:19.564Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "A07548B9CC8E5BC211DC6226EEF3908E3352B99071A212C6460C9BF831AEAEBD", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/A07548B9CC8E5BC211DC6226EEF3908E3352B99071A212C6460C9BF831AEAEBD: no such file or directory"}
2023-05-17T21:05:19.565Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "CB84A3AD79B468197C52177010BF273971AC16D1406B65DFDE9CE4DA86FA20E7", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/CB84A3AD79B468197C52177010BF273971AC16D1406B65DFDE9CE4DA86FA20E7: no such file or directory"}
2023-05-17T21:05:19.565Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "5901F739BC81A4D72928EA6943765DB906CDB54797934B1772B44EEB6798972F", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/5901F739BC81A4D72928EA6943765DB906CDB54797934B1772B44EEB6798972F: no such file or directory"}
2023-05-17T21:05:19.565Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "DBDEBD718B72B784F1C0371ED0F476A661AF785388C9CFBB2928174C3EDEA224", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/DBDEBD718B72B784F1C0371ED0F476A661AF785388C9CFBB2928174C3EDEA224: no such file or directory"}
2023-05-17T21:05:19.566Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "2B84502AC68F94A3C13577E09EC8D62290B02335DFC42145331EC220A5A4EDD3", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/2B84502AC68F94A3C13577E09EC8D62290B02335DFC42145331EC220A5A4EDD3: no such file or directory"}
2023-05-17T21:05:19.566Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "E6B439738094169D8CBBA51F8859B8842573879A71BFAA06DF2644619DFD3A42", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/E6B439738094169D8CBBA51F8859B8842573879A71BFAA06DF2644619DFD3A42: no such file or directory"}
2023-05-17T21:05:19.566Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "12A0738A79B552449B001FAE2620940A9379AEAFAF0079AA07ED5C15AC9411F6", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/12A0738A79B552449B001FAE2620940A9379AEAFAF0079AA07ED5C15AC9411F6: no such file or directory"}
2023-05-17T21:05:19.567Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "DEA4E4E1AC00E6C8365973F61BFC05CABEB01B4A82BDBF2AF7F1004A61B87FC4", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/DEA4E4E1AC00E6C8365973F61BFC05CABEB01B4A82BDBF2AF7F1004A61B87FC4: no such file or directory"}
2023-05-17T21:05:19.567Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "16BAAB79D1D28F6D329FF470600256EAF0C2DDBB06058281D0BEA37537B410CC", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/16BAAB79D1D28F6D329FF470600256EAF0C2DDBB06058281D0BEA37537B410CC: no such file or directory"}
2023-05-17T21:05:19.567Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "0DC8D3912CCB6B6039B6C9962044DBBAA4135EDB05BE417878F0CDB54BE2A1FB", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/0DC8D3912CCB6B6039B6C9962044DBBAA4135EDB05BE417878F0CDB54BE2A1FB: no such file or directory"}
2023-05-17T21:05:19.567Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "26CCA64AE86FE4BFF3E17D2C483D67A27C2BCED47B16EFFCFB6E5D3DBD06B261", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/26CCA64AE86FE4BFF3E17D2C483D67A27C2BCED47B16EFFCFB6E5D3DBD06B261: no such file or directory"}
2023-05-17T21:05:19.568Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "B79CA00426610AF1B2F55C8A88EAA15B940AFDB571BAFCDA3004053AA1A04C04", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/B79CA00426610AF1B2F55C8A88EAA15B940AFDB571BAFCDA3004053AA1A04C04: no such file or directory"}
2023-05-17T21:05:19.568Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "9639BFF6A493A22120967B27F17311D130CB7CC5C974F1FEEAC8AB8AD5114CDC", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/9639BFF6A493A22120967B27F17311D130CB7CC5C974F1FEEAC8AB8AD5114CDC: no such file or directory"}
2023-05-17T21:05:19.568Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "76538B0D5F615F08CBE8150F530AA7DCD46AC7C8F200B7856629F84E4B8D2081", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/76538B0D5F615F08CBE8150F530AA7DCD46AC7C8F200B7856629F84E4B8D2081: no such file or directory"}
2023-05-17T21:05:19.568Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "835A5EA99129F27188FDB43A3EE5AC379844777D723E78CD1E3B2A0088CB1DCE", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/835A5EA99129F27188FDB43A3EE5AC379844777D723E78CD1E3B2A0088CB1DCE: no such file or directory"}
2023-05-17T21:05:19.569Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "C350A53A095C1D1CA8409328A2733E7857E17143967A8F86BD91A775BE4D394D", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/C350A53A095C1D1CA8409328A2733E7857E17143967A8F86BD91A775BE4D394D: no such file or directory"}
2023-05-17T21:05:19.569Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "6E30DDA207DEEE06CB1BC980ED0B3696720F8F86840B29A247D1C6879E1C67BE", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/6E30DDA207DEEE06CB1BC980ED0B3696720F8F86840B29A247D1C6879E1C67BE: no such file or directory"}
2023-05-17T21:05:19.569Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "3D6D8AA397EF1C8865D13973AC216FC64B32949DEFB6AF08647194513149ABEF", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/3D6D8AA397EF1C8865D13973AC216FC64B32949DEFB6AF08647194513149ABEF: no such file or directory"}
2023-05-17T21:05:19.570Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "25AEF60A07349407B875D8D334FE55A821D8A0CF4988BB8BF1E652A5875D7A58", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/25AEF60A07349407B875D8D334FE55A821D8A0CF4988BB8BF1E652A5875D7A58: no such file or directory"}
2023-05-17T21:05:19.570Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "7CA3E384AA264064395FE82D36BA1D22FF8D455BE5A9ADBB7A8708886E7B32FB", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/7CA3E384AA264064395FE82D36BA1D22FF8D455BE5A9ADBB7A8708886E7B32FB: no such file or directory"}
2023-05-17T21:05:19.571Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "5DE8E29399EF4FCD65C39C84386E5D01A347258245F735ADCD94D8FF25144B27", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/5DE8E29399EF4FCD65C39C84386E5D01A347258245F735ADCD94D8FF25144B27: no such file or directory"}
2023-05-17T21:05:19.571Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "F718A8D2FA902AA120A6CE6D10F5589681352DCFAB61C3507D8C02F240AF7BCA", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/F718A8D2FA902AA120A6CE6D10F5589681352DCFAB61C3507D8C02F240AF7BCA: no such file or directory"}
2023-05-17T21:05:19.572Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "6DDAA5884EEE35852C66C6D7059FFB0BFCEEACE932A8E8141BDE4587FFD5C17E", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/6DDAA5884EEE35852C66C6D7059FFB0BFCEEACE932A8E8141BDE4587FFD5C17E: no such file or directory"}
2023-05-17T21:05:19.572Z	INFO	dagstore	dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore.go:279	start: skipping recovery of shard in errored state	{"shard": "257760461993F8F197B421EC7435F3C36C3734923E3DA9A42DC73B05F07B3D08", "error": "failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/257760461993F8F197B421EC7435F3C36C3734923E3DA9A42DC73B05F07B3D08: no such file or directory"}
2023-05-17T21:05:19.576Z	INFO	basichost	basic/natmgr.go:93	DiscoverNAT error:no NAT found
Error: node: failed to start: failed to check if root already exists in index: failed to acquire reader of mount so we can return the accessor: open /home/celestia/.celestia-full-blockspacerace-0/blocks/257760461993F8F197B421EC7435F3C36C3734923E3DA9A42DC73B05F07B3D08: no such file or directory

This has not occurred since, assuming it occured from swapping node stores


Does ReplaceTagger works with  header?

Hi Pascal
I have question wheather ReplaceTagger can/should be used to extract data from text between
<content>....</content> using regexp? I was able to fetch data using XML commiter, however all important data i have are in  field. Thanks in advance for your support.

You mean the <content> tags in the files generated by the XML Committer?  If so, no you cannot, since the Committer is the "final" (crawled/parsed/modified/etc) destination for a document.  You need to perform your operations before it reaches the Committer.
What do you want to do with the data in the end?  Store it in a database, search engine, or else?
Can you give me a concrete example of a source document and the data/fields you want to extract?


[Compute] Fix #30565: az vm create: Fix creating VM with --patch-mode parameter

Related command

az vm create
Description

Close: #30565
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.


Model editor updates

[X] Add tests to cover ModelCommandAPI. See here

Done in #1231

[X] Make sure everything in ModelCommandAPI and on the Component inspector has units. See here

Done in #1231

[ ] Add View test. See here.
[ ] Add SDFEntityCreator test. See here.
[x] Add simulation runner test, see here.\

Done in #1231

[ ] Support custom noise units. See here.
[X] Use MAX_VALUE, see here.

Done in #1231

[ ] This changed the StateAware to allow all model spin boxes to be editable when running simulation. It should only allow the pose spin boxes for a model to be editable when running.
[ ] The component inspector will continue to show Entities that have been removed of recreated. See here.

The model editor work has been merged as a separate plugin, ComponentInspectorEditor, for expediency. We should port all the features from that plugin to ComponentInspector and then deprecate it so we have only one inspector.

PR porting some of the refactoring that organizes the C++ code into various files:

https://github.com/ignitionrobotics/ign-gazebo/pull/1400


Error installation: package dependency conflicts

Hi,
I tried to install OnClass, but has the dependency conflicts error for intervaltree.
When I have intervaltree==2.1.0, I got this error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
spyder 4.2.1 requires intervaltree>=3.0.2, but you have intervaltree 2.1.0 which is incompatible.

But when I have intervaltree==3.1.0, I got this error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
scanorama 1.7.1 requires intervaltree==2.1.0, but you have intervaltree 3.1.0 which is incompatible.

It seems scanorama 1.7.1 and spyder 4.2.1 requires different version of intervaltree.
Could you please let me know how to fix this issue?
Thanks!
Hurley

My intervaltree is 2.1.0. I don't seem to have spyder package.
Here is a conda yml file built by bschilder you can use to install OnClass https://github.com/bschilder/scKirby/blob/main/inst/conda/onclass.yml
Another solution is to just clone the github repo and run it without doing the pip install. You don't need to install scanorama if you only want to train on a single dataset.
I will look more into this intervaltree issue soon.


Video exited fullscreen

When we load the mejs player inside frame and zoom in/out the window. While entering into full-screen, it forcefully exited full-screen.

PR:https://github.com/mediaelement/mediaelement/pull/2920


adding small change for b2b cross cloud update

@sponnada : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ajburnle,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.

#sign-off

This PR is ready for merge.


New version: Appest.TickTick version <IP_ADDRESS>

Created by 🥟 Dumplings in workflow run #6504.

Log
Updated: <IP_ADDRESS> → <IP_ADDRESS>
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/issues/142854


Wrong handling of paths without params

Rewrite rules having no parameters, automatically applied to every path (even to the non-matching ones.)
The problem is in getTargetUrl function of util.js.
The toUrl is automatically set to the to parameter, and will be returned even if the path doesn't match. For non-matching paths the intact url parameter should be returned instead.
function getTargetUrl (from, to, url) {
  const { pathToRegexp } = require('path-to-regexp')
  const fromParams = []
  const re = pathToRegexp(from, fromParams)
  const fromMatches = re.exec(url)
  let toUrl = to // <--------- it should be 'url' if 'fromMatches' is undefined

  for (const [index, fromParam] of fromParams.entries()) {
    if (fromMatches && fromMatches[index + 1]) {
      fromParam.value = fromMatches[index + 1]
    }
  }

  /* replace named params */
  for (const fromParam of fromParams) {
    if (typeof fromParam.name === 'string') {
      if (fromParam.value) {
        toUrl = toUrl.replace(new RegExp(`:${fromParam.name}`, 'g'), fromParam.value)
      } else {
        toUrl = url
      }
    }
  }

  /* replace positional params */
  for (const fromParam of fromParams) {
    if (typeof fromParam.name !== 'string') {
      toUrl = url.replace(re, toUrl)
    }
  }

  return toUrl
}

Hi, could you post an example of a rewrite rule I can use to reproduce this bug please?

Let's consider the following rules:
rewrite: [
  {
    from: '/login/(.*)',
    to: 'dist/login/$1'
  },
  {
    from: '/login',
    to: 'dist/login/index.html'
  }
]

Here, I'd like to rewrite every path starting with /login/ to my dist folder path. This rule alone works, but as soon as I add the second one, everything will be redirected to 'dist/login/index.html'. The second rule doesn't have params to be replaced. getTargetUrl() will return the unmodified 'toUrl' which has been set to 'to' at the beginning of the function. (This 'to' variable holds 'dist/login/index.html'.)

Fixed and released in lws v3.1.1 - please upgrade.
Thanks, let me know if you find any more issues!

Thank you very much, that was really quick. :)


ANCM diagnostics strings review

We have a bunch of diagnostics error strings in ANCM. We need to do a spelling and grammar review for all these messages

@shirhatti do we need a meeting to go through these? Or will you be doing this offline?


[RELEASE-0.21] Rollback certificate algorithm changes

As per title. To fix FIPS related issues.

/hold
To determine if we want this.

/unhold


Benefit cap calculator pre autumn changes

Paired with @leenagupte
Trello Story: https://trello.com/c/IVrsJIfM/34-22-april-requires-fix-but-hold-deployment-benefit-cap-calculator-2016-2017-changes
Motivation
The benefit caps are going to change in the autumn as follows:

There will be higher cap for families inside London compared to those outside London.
Two benefits that currently affect the cap (Carer's Allowance and Guardian's Allowance) will be exempt.

To prepare the public for the coming changes, the benefit cap calculator needs to be updated to allow the public to check both i.e. what their cap is now and what it will be this autumn when the new caps are implemented to allow them to prepare for it.
A new question will be need to be added to the beginning of the benefit cap calculator to route users to the correct flow. If users choose to see the new caps, an extra question needs to be added to check their postcode.
Factcheck
Benefit Cap Calculator
Expected Changes
URL on GOV.UK

Add a first question to beginning of the flow to ask users which benefit cap they want to view.
Add Carer's Allowance and Guardians Allowance to the list of exempt benefits in the autumn 2016 flow
Remove Carer's Allowance and Guardians Allowance from the list of benefits to check in the autumn 2016 flow.

Before

After

Removing the future flow (Autumn 2016)
Sometime in autumn 2016, the new benefit caps will be implemented. At this point, the future flow will become the default flow and the old default flow will need to be removed.
We have (as much as possible) tried to implement these changes to make removing a flow as easy as possible. As it currently stands, these are the changes that will need to be made in Autumn 2016:

Remove the first question.
Remove the configuration for "default" from benefit_cap_data.yml
Rename "future" to "default in benefit_cap_data.yml
Remove all references to chosen_cap in the benefit-cap-calculator flow
Questions that have a _future version (i.e. is duplicated):

Remove the original, and rename _future to the same name as the original.
Consolidate the templates with the current versions.
Questions affected:

single_couple_lone_parent_future?
receiving_non_exemption_benefits_future?

Outcomes that have a _future version (i.e. is duplicated):

Consolidate the templates with the current versions.
Outcomes affected:

outcome_not_affected_future
outcome_not_affected_no_housing_benefit_future
outcome_not_affected_exemptions_future

Outcomes that have National and London future versions:

Outcomes affected:

outcome_not_affected_less_than_cap_future_london
outcome_not_affected_less_than_cap_future_national
outcome_affected_greater_than_cap_future_london
outcome_affected_greater_than_cap_future_national

Remove the default flow from the integration tests.
Rename the default flow to future flow in the integration tests.
Remove the first question from the integration tests.
Regenerate all test artefacts for the regression and integration tests.
Remove the version parameter from the functions in benefit_cap_calculator_configuration. There will only be one version (future renamed to default) of the configuration, so it's no longer needed.
Update benefit_cap_calculator_configuration_test

Tests affected by the changes:

test/regression/smart_answers_regression_test.rb
test/integration/smart_answer_flows/benefit_cap_calculator_test.rb
test/unit/smart_answer_flows/benefit_cap_calculator_flow_test.rb
test/unit/calculators/benefit_cap_calculator_configuration_test.rb

I'm slightly confused to see both the "Waiting on factcheck" and "Spike" labels on this. To me a "Spike" is something that I would expect to throw away - see this definition.

I think it might be better to use better names than default and future. I think something like @chrisroos's pre-2016 and post-2016 might be better. Or pre-autumn-2016 and post-autumn-2016 if those aren't specific enough. I just worry that when we get to autumn 2016, future might no longer be in the future!

Overall the final solution looks good. However, the sequence of commits is pretty hard to follow, especially as the code and tests are broken in one of the early commits and are not fixed until one of the last commits.
I think it would be better to structure the commits more like the following:

Introduce the new initial question, but still send the user to the same next node.
Duplicate the outcome_not_affected_no_housing_benefit outcome and in Q1 send the user to it if chosen_cap is future.
Make the relevant changes to the new future version of the outcome_not_affected_no_housing_benefit outcome template.
Duplicate the outcome_not_affected_exemptions outcome and in Q2 & Q3 send the user to it if chosen_cap is future.
Make the relevant changes to the new future version of the outcome_not_affected_exemptions outcome template.
Duplicate the receiving_non_exemption_benefits? question and in Q3 send the user to it if chosen_cap is future.
Make the relevant changes to the new future version of the receiving_non_exemption_benefits? question template.
Introduce support for multiple configuration types
Duplicate the default configuration to a future configuration
Change the future version of the receiving_non_exemption_benefits? question to use the future configuration.

... and so on. I hope that makes sense.
I think it would be relatively straightforward to ensure the flow was working and the tests were passing after each commit.
The regression tests for this flow don't take very long to run, so I think you could even keep them passing after each commit by making the relevant changes to the inputs and artefacts. That way you wouldn't end up with a giant commit at the end in which lots of the artefacts change.

The order of your last 6 commits is a bit odd. First there are two which make changes to the regression tests, then there are two which make changes, then there are two which make more changes to the regression tests. I think it would be better to have the two which change the integration tests first and then the four which change the regression tests.

Lastly I just want to point out that GitHub is indicating that this branch has conflicts with master and so you'll need to resolve those before merging.

My original understanding was that these changes were required urgently by the department and hence why we decided it was expedient to merge the pre-emptive refactoring in #2452 despite it not necessarily being ideal. However, it looks as if this follow-up PR has now been in "fact check" for nearly two weeks. Has anyone heard any news about it?

@floehopper We needed to have the changes ready for factcheck by April 22nd. We gave the department one week (April 29th) for factcheck. They have come back with a bug (that also exists in the current calculator) plus have hinted at other unnamed changes.
We are going to give them until stand up tomorrow to give us the outstanding changes, but in the mean time will work on the bug.
As it stands, the changes needed to be deployed to Production on May 9th (Monday).

@ikennaokpala: Thanks for the update.

I've added a Don't merge label, as the department got back to us this morning an pushed back the deployment date to May 24th. The trello card has been updated with the details.

Thank you @leenagupte.
What about creating a Milestone for the 24th May, and linking the card?

Regarding commit: https://github.com/alphagov/smart-answers/pull/2481#issuecomment-212973508
Future was picked as a name because it refers to something that hasn't happened yet. When the cap changes occur and the future becomes the present, Having two flows will no longer be valid. The "future" will become the default (current) and the future will no longer exist.

Regarding the ordering of commits. They reflect the our intention of starting at the model layer and finishing at the presentation layer, and then implementing the new questions.

I have moved to a new branch to resolve the merge conflicts with master to preserve the comment history: https://github.com/alphagov/smart-answers/pull/2542

Future was picked as a name because it refers to something that hasn't happened yet. When the cap changes occur and the future becomes the present, Having two flows will no longer be valid. The "future" will become the default (current) and the future will no longer exist.

@leenagupte: I understand the use of current and future but still think it'd be much clearer if it was something like pre-autumn-2016 and post-autumn-2016. Having terms that match the language used by the department makes it much easier to go from talking and thinking about the Smart Answer to working on the code for the Smart Answer.


HOTFIX: bug updating cache when loading group metadata

The bug causes only the first instance of group metadata in the topic to be written to the cache (because of the putIfNotExists in addGroup). Coordinator fail-over won't work properly unless the cache is loaded with the right metadata.

LGTM, maybe we can rename the function as updateGroup?

Also picked to 0.9.0 branch.


Feature Google Search

resubmitting my old pull request do to me messing up my forked repo.

I've updated this PR a bit for coding style, and have it in branch flarf/feature-googlesearch: https://github.com/JohnMaguire/Cardinal/tree/flarf/feature-googlesearch
I promise I'll get around to testing it before the end of the day. :) Thank you again.

Not a problem, glad I was able to contribute!


setting system-reserved/kube-reserved based on a % instead of a static value

Tell us about your request
currently kube-reserved and system-reserved is only configurable by a static value. i would like this to be more dynamic and take into account the instance-size. i would like to set a percentage like 10%.
cpu/memory/ephemeral-storage are all static values.
allowing to specify both a static or percentage similar to evictionHard which allows both 5% or 500Mi
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: default
spec:
  kubeletConfiguration:
    systemReserved:
      cpu: 1000m
  providerRef:
    name: default
  requirements:
    - key: karpenter.k8s.aws/instance-size
      operator: In
      values: ['4xlarge']

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
i want to specify a list of instance-sizes for example 2xlarge, 4xlarge, 9xlarge.
different workloads require different k8s settings. our main production workload requires more system-reserved cpu and i have set this at 1000m.
we would like to use more instance-sizes but if the machine was twice the size of another one, then there is no way to specify for it to have twice as much cpu reserved.
from what i have read, it is an anti-pattern to have multiple overlapping provisioners.
Are you currently working around this issue?
there are a couple of options available to work around this issue

fiddle with userdata to run and calculate the amount to reserve based on instance-size and use this value as a kubelet argument.
update all hpa's and lower the scaling target from 100% to 90%.
own ami.

Additional Context
No response
Attachments
No response
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What specific system overhead do you need to account for? If it's the container runtime, which scales w/ # of pods, you can consider using a runtime class https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/.

@ellistarn that is cool - don’t know how we missed that option.
we will try adding overhead to the pod spec tomorrow. Will have to figure out which of the 100s of micro services requires what overhead. But it looks like there are kube-state-metrics that we can use to identify which pods need it set and increase/decrease the overhead as needed.
thanks a lot for pointing this out - much appreciated.


Fix/broken tests

Proposed changes
fixing tests failing after changing BaseSkillTestCase.setup to BaseSkillTestCase.test_setup
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Codecov Report

Merging #302 (f5fffc3) into fix/BaseSkillTestCase.setup (7df6976) will increase coverage by 0.01%.
The diff coverage is n/a.

@@                       Coverage Diff                       @@
##           fix/BaseSkillTestCase.setup     #302      +/-   ##
===============================================================
+ Coverage                        93.95%   93.96%   +0.01%
===============================================================
  Files                              216      216
  Lines                            18619    18619
===============================================================
+ Hits                             17493    17495       +2
+ Misses                            1126     1124       -2

Flag
Coverage Δ

unittests
93.96% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aea/test_tools/test_skill.py
100.00% <0.00%> (+1.19%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


ERROR in LOG IN PLEASE HELP

i installed procurment latest version and have this error [Error] Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log , please help ?
pealse help

Please attach your DebugInfo.log file (which is in the same directory as Procurement.exe), as the error message requests, and provide more details on what you are doing when you are getting this error.  Have you successfully used Procurement before?

i have never used it before , although i added my correct alias and ID , and just pressed log in , though the log in button wasnt working untill i ran the program as administrator , and now after pressing log in multiple times because each time i press osmetimes says  or or more errors  but eventualy it works , and gives me this error for downloading stash .
DebugInfo.log

Ah, there is an out-of-date library in the latest release. Please follow
the link provided in the comment here --
https://github.com/Stickymaddness/Procurement/issues/1091#issuecomment-596160251
-- to download a patched version of Procurement with which you should be
able to log in.
On Wed, Apr 8, 2020, 2:42 AM ameen1998<EMAIL_ADDRESS>wrote:

i have never used it before , although i added my correct alias and ID ,
and just pressed log in , though the log in button wasnt working untill i
ran the program as administrator , and now after pressing log in multiple
times because each time i press osmetimes says or or more errors but
eventualy it works , and gives me this error for downloading stash .
DebugInfo.log
https://github.com/Stickymaddness/Procurement/files/4448640/DebugInfo.log
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Stickymaddness/Procurement/issues/1098#issuecomment-610780763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHNZOHXIKSGA5DJOZOLGLRLQMFTANCNFSM4MDVSVEQ
.

pfft, it now needs 1 time to press the log in button but it still have the error same one here is the new log .
DebugInfo.log

dont give up on me bro haha

You're getting 503 (Server Unavailable) and 404 (Not Found) errors when accessing the API.  The 503 errors suggest something is going wrong on GGG's end.  Please try to get a fresh SessionID from the browser (log out, then log in and use the guide here) and try to log in again.

again the next msj: Cloud flare clearance failed, please wait one minute and try again.
impossible to login
please help me

@ifkvothe , please see #1104. (You don't need to update multiple bugs when you have an issue.)

Procurement 1.29.0 has been released, which fixes this issue.


Improved existing test cases and added new ones

Works on my machine(TM)

One tiny nibble, LGTM otherwise, thanks!

fixed, thx!


solved issue #486

Changed the logo.png and removed the background from it.

Hi @arey-pranay
The Odigos logo that was talked about in #486 is this one:
https://github.com/keyval-dev/odigos/blob/6135601b942190180e56b33fb632eac4030666dd/frontend/webapp/utils/constants/config.tsx#L9C11-L9C57
and not the one that shown in the README.md


Updated description field of OLM metadata

/lgtm

Are the descriptions going to be the same for maistra and product? I mean, maistra's description is 'OpenShift Service Mesh'.

Not sure at this point, figured I'll sort out the servicemesh stuff first.

Added ticket number

@dmitri-d conflict, I think it's just the dates, but I'll leave that for you to take a look.

rebased


Arrow keys stop working after running dotnet or ssh

Platform Linux x86 (Fedora 36)
Terminal software GNOME Terminal
Hello from nushell/nushell! I've been looking into this Nu issue, and I've put together a minimal reproduction for Reedline v0.4.0. Here's a dumb little REPL that runs whatever command it's given:
use reedline::{DefaultPrompt, Reedline, Signal};
use std::{io, thread, time};

fn main() -> io::Result<()> {
    let mut line_editor = Reedline::create();
    let prompt = DefaultPrompt::default();

    loop {
        let sig = line_editor.read_line(&prompt)?;
        match sig {
            Signal::Success(buffer) => {
                println!("We received: {buffer}");
                let mut process = std::process::Command::new("sh");
                process.arg("-c").arg(&buffer);
                process.spawn().expect("process spawn error");

                // avoid writing prompt while external process is still running
                thread::sleep(time::Duration::from_millis(100));
            }
            _ => {
                println!("Abort!");
                break Ok(());
            }
        }
    }
}

Steps to reproduce

cargo run
Type "ls" then enter to run ls
Press up arrow then down arrow, observe that the history navigation works as expected :+1:
Type "dotnet --version" then enter (requires the .NET SDK)
Press the up arrow, observe that nothing happens :-1:

I was also able to reproduce the issue with SSH in Nu, but that's proving to be a little trickier in my minimal repro.
Next Steps
I'd be happy to investigate further, but I think I've reached the limit of my terminal debugging knowledge. If someone can point me in the right direction that would be much appreciated.
@elferherrera suggested that this might be a crossterm issue; I guess I could try building a similar REPL directly with crossterm but I'm hoping someone will have an easier idea.

Using scriptlike script -q -c 'dotnet --version' output.txt I was able to see the raw command output and investigate this further. It seems like Reedline doesn't like certain escape characters that dotnet outputs.
I can reproduce this by calling cat on either of these files in Nu: dotnet-version-raw-output.txt, minimal-repro.txt

It seems like that [?1h] control code sets a special "application mode" for arrow keys: https://www.vt100.net/docs/vt510-rm/DECCKM.html
So... I think the dotnet CLI is behaving badly here (related issues: 1, 2 ), but I don't understand why other shells handle it OK. And given that this happens with ssh too, I suspect this may still need a fix on Reedline or Crossterm's side :(

just to document a work-around ansi -e ?1l corrects the issue as does $"(ansi esc)c" or "\ec" but the last 2 also clear the screen.

Closing this; @fdncred was able to fix it in https://github.com/nushell/nushell/pull/5302 (thank you!).
To make a long story short, Nu can now tell the terminal to reset cursor key mode before each prompt. We think this is how other shells solve the problem.


Getting a failed to template error

TASK: [telusdigital.python | Install Packages | pip | {{ python_packages }}] ***
fatal: [localhost] => Failed to template {% if item is 'ansible' %}present{% else %}latest{% endif %}: template error while templating string: expected token 'name', got 'string'

FATAL: all hosts have already failed -- aborting

Just the way this was passed.
Resolved in master, correct way to write this is
"{% if item is ['ansible'] %}present{% else %}latest{% endif %}"


Add option to ignore comments in parse/accept functions

This PR adds an option ignore_comments to the parse and accept family that allows to ignore // and /* */ style comments.
PS: I still think there is a good reason JSON has no comment support. But it was by far the most popular request, and I understand that the lack of comments was a problem for a lot of folks that use JSON as configuration format. However, comments are still treated as parse error by default.
Closes #2061
Closes #1513
Closes #597
Closes #376
Closes #363
Closes #294
Related to #2090 #348 (comments only, no full JSON5 support).
Related to #311 (comments only, no JSON Schema support)

🔖 Release item
This issue/PR will be part of the next release of the library. This template helps preparing the release notes.
Type

[x] ✨ New Feature
[ ] 🐛 Bug Fix
[ ] ⚡ Improvement
[ ] 🔨 Further Change
[ ] 🔥 Deprecated function

Description

Add option to ignore comments in parse/accept functions. #294, #363, #376, #597, #1513, #2061, #2222


Delete sensor watcher queue

Closes: https://github.com/StackStorm/st2/issues/3628
TODO:

[x] Integration tests ** I had to enable rabbitmq_management in travis because https://stackoverflow.com/questions/4287941/how-can-i-list-or-discover-queues-on-a-rabbitmq-exchange-using-python **
[x] Document how to delete the queues that are left around. (https://github.com/StackStorm/st2/issues/3628#issuecomment-319801557)

OK, let's go ahead and merge this explicit delete for now.
We can always include durable and auto delete in a new PR if we confirm it works as it should and it's a good idea.


Refactor mod_manager.c a bit, break down some bigger functions

Additionally, I replaced a custom sort with a built-in sort. Lastly, I renamed some functions that are creating the mod_manager page for better clarity.

I see the diff is not very clear. Switching to unified diff helps.

Merging, thank you for the review.


build/bin/query error (cannot read background.slm LM)

The command
$MMT_HOME/build/bin/query --model $MMT_HOME/engine/$ENGINE/models/decoder/lm
fails when the background.slm is involved, for any ENGINE.
It works only when the --alm-only option is provided.
When the background.slm is involved, the command fails at LM loading time, reporting the following error:
terminate called after throwing an instance of 'lm::FormatLoadException'
  what():  ModernMT/src/decoder-phrasebased/src/native/interpolated-lm/kenlm/lm/binary_format.cc:133 in void lm::ngram::MatchCheck(lm::ngram::ModelType, unsigned int, const lm::ngram::Parameters&) threw FormatLoadException.
The binary file was built for trie with quantization and array-compressed pointers but the inference code is trying to load probing hash tables

fixed in commit 7c5f6b8


Reduce the number of blockchain nodes to 5 from 10

Change summary:

Reduce the number of blockchain nodes to 5 from 10 (ENABLE_JSON_RPC_API, ENABLE_REST_FUNCTION_CALL, ENABLE_EVENT_HANDLER, PEER_WHITELIST)
Add a sample keystore file for transfer tool

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/1173

Thanks for the review, now merging..


Problems with Jump to problem

Hi, been testing out this package and it looks very promising 😄
I've encountered a problem with the Jump to problem" feature
Could not open Whatever.elm in the editor.
The editor process exited with an error: spawn /Applications/WebStorm.app/Contents/MacOS/webstorm ENOENT.

Also as an additional question, is there a plan to add error messages to the console where the server is running or is it only supposed to be in the browser as an overlay?

Hi, @ericwern
I ran into this the other day with a friend. Does this solution work for you?
https://github.com/yyx990803/launch-editor/issues/4#issuecomment-359348189
If so, I think I will be able to improve the plugin to include this advice when an ENOENT occurs for users

Also as an additional question, is there a plan to add error messages to the console where the server is running or is it only supposed to be in the browser as an overlay?

Not at this time– but may add in as an option later. Thanks for bringing this up!


Remove trip advisor icon

Fixes an issue when using font_awesome_flutter 9.2.0 which removed tripadvisor icon as done in fontawesome.
https://fontawesome.com/v5/changelog/latest

duplicated with #78 😄

Oo I see. Why isn't it merged though?

@dengyin2000 any chance we merge those PRs soonish? I can't update the flutter dependencies properly because of this issue.

sorry guys, I have been busy recently. it was merged. thanks

Thank you @dengyin2000! How does it work now, do you need to create a new release to include this fix?


'Mark' is not defined

Here is an issue I am facing... using the plain javascript mark.js...
This sometimes throws an "'Mark' is not defined" error:
var instance = new Mark(document.body);
I say 'sometimes' because I am injecting the mark.js script into a webview control inside a UWP app.
The webview control is a web browser, and so I am using the mark.js script to perform page searches.  I do not control what page is showing.  I must mention that the page search does work most of the time, but not on every web page.  It fails for instance when I am injecting the script in https://wallethub.com/edu/most-fun-cities-in-the-us/23455/
Not being a javascript expert, I am hoping someone might know what I'm talking about...

Make sure that mark.js is loaded before you call it.

Closing due to inactivity.


Depth constructor fix - Issue #18

I added a default value of 0 depth to the constructor and removed some whitespace from the file.
See Issue #18 for reference.

Thank you very much!!


Setting tms to true

Using the directive, how can I set tms to true as described here:
http://leafletjs.com/reference.html#tilelayer-tms
This is what my obj looks like:
{
    url: '/api/tiles/' + a.id + '/{z}/{x}/{y}.png',
    defaults: {
        tileLayerOptions: {
            noWrap: true,
            tms: true
        },
        maxZoom: 6,
        minZoom: 0
    },
    noWrap: true,
    continuousWorld: false
};

Seems like tms is getting ignored

Hi, you don't need to pass the tms property in the defaults object, that's the default tiles object which only applies when the user doesn't define any layer. It's better to declare the custom layer properties it in the main layer "layerOptions". For example:
baselayers: {
    mylayer: {
        name: 'My Layer',
        url: 'http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png',
        type: 'xyz'
        layerOptions: {
            tms: true
        }
    }
}


Focused Color schemes not showing top border

Windows Terminal version
main d07c536
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce
select Color schemes and tab to focus drop-down options
Expected Behavior
focus border all around
Actual Behavior
top focus border not shown:

Yep, that's real, even on #12326. Linking to #11353


Expose tapped date on dayViewDidTapTimeline and dayViewDidTapTimeline

New Issue Checklist

[x] Use the latest version of CalendarKit
[x] I've read the Contribution Guidelines
[x] I've searched for existing GitHub issues

Issue Description
I need to create events on single tap, for that I need the tapped date.
Code I'm using with CalendarKit

func timelinePagerDidTap(timelinePager: TimelinePagerView)
func dayViewDidTapTimeline(dayView: DayView)

Result I am trying to achieve
func timelinePagerDidTap(timelinePager: TimelinePagerView, date: Date)
func dayViewDidTapTimeline(dayView: DayView, date: Date)

I can send a PR with these breaking changes.

Great idea. Please, refer to the didLongPressTimeline at date for the inspiration.
If there is some common code between those two methods, please extract it to the private methods inside respective classes.


Static link CRT for windows bin

Closes #419

After testing this out, it seems I used to wrong way to set the env. var to statically link CRT.

You can also just switch to bash instead of Powershell. This worked for me:
      - name: Create .exe file
        shell: bash
        run: cd myceliumd && RUSTFLAGS="-Ctarget-feature=+crt-static" cargo build --release && cd ..

You can also just switch to bash instead of Powershell. This worked for me:
      - name: Create .exe file
        shell: bash
        run: cd myceliumd && RUSTFLAGS="-Ctarget-feature=+crt-static" cargo build --release && cd ..

This indeed seems to work fine, thanks @scottyeager!


Menu title for Archives in CMS is not visible in german language

Since 4.8 I noticed that the menu title for the Archives in CMS is not visible, if I switch the user to german language. Only the icon is visible - see screenshot.

Parent issue

[ ] https://github.com/silverstripe/silverstripe-versioned-admin/pull/214

Weird ... the English title of that section changed in 4.8 which will have invalidated translation in other languages. However, it should still be showing the English string gather than nothing.

This should fix it https://github.com/silverstripe/silverstripe-versioned-admin/pull/214

Just tagged versioned-admin 1.8.1