Comments (2)
I wonder if this could be down to the usage of tmp_path.persist
here?
From the docs:
Note: Temporary files cannot be persisted across filesystems. Also neither the file contents nor the containing directory are synchronized, so the update may not yet have reached the disk when
persist
returns.
I haven't been able to replicate the error, but this would explain the test failure, where the test tries to read the file as soon as download_file
has returned Ok
.
It seems like there might be a couple of places in init_configs
where there's an assumption the downloaded file is immediately available for reading too, so possibly download_file
needs to be updated to fsync the folder somehow (not sure if that's viable) or persist
changed for a more manual approach where the renamed file gets synced right away.
from nearcore.
Hm, as far as modern operating systems are concerned, the "may not have yet reached the disk" usually means that the page data may still be in page caches or a writeback queue of some sort. But the OS will consult with these structures when the data is read back to provide a consistent and sequentially ordered view of the file system(s). I believe this may refer to situations where operating system stops executing at all, whether it be a result of a crash or a power loss or a similar such scenario.
from nearcore.
Related Issues (20)
- [EpochSync] Run a canary node on testnet and mainnet
- Reducing hard drive validator footprint HOT 5
- Insufficient resources: could not allocate code memory HOT 4
- Blockers and Wishlist for the 1.37 release HOT 3
- Test combination of resharding and high load in mocknet
- [BUG] By default, the first time you deploy a node localnet on gitpod, then execute with tools/restaked, and then an error occurred
- ใBUGใnear-olly opentelemetry conflicts with the standard library and has been contaminated HOT 3
- WARN jsonrpc: Timeout: tx_polling method.
- `Receipt` and `Action` validation is error prone and is missing compile-time checks
- Monthly issue metrics report
- 1.37 release timeline
- Implement transactions validation for Stateless Validation
- unmerge near-vm-runner from near-vm-logic HOT 2
- Run Stateless Validation code as part of mainnet
- Properly use source_receipt_proofs in ChunkStateWitness
- `yapf` test leaves a stray process that never quits
- Yield Execution (NEP 516 / NEP 519) HOT 6
- [State Sync] Create separate DB for State snapshots
- [State Sync] Upload headers to GCP to be able to work with stateless validation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nearcore.