- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Thu, Dec 12
In D17335#393946, @bytesofman wrote:In D17335#393945, @Fabien wrote:In D17335#393933, @bytesofman wrote:nice.
is this a greenfield lib or is it initializing a repo in the monorepo that exists somewhere else?
This is Tobias' client, the one we use for the explorer. @hazzarust is putting it into the monorepo then will add the failover proxy to it.
ok nice
in that case, not really a big deal about adding stuff like test comments, having this as a starting point is helpful
Wed, Dec 11
In D17335#393945, @Fabien wrote:In D17335#393933, @bytesofman wrote:nice.
is this a greenfield lib or is it initializing a repo in the monorepo that exists somewhere else?
This is Tobias' client, the one we use for the explorer. @hazzarust is putting it into the monorepo then will add the failover proxy to it.
In D17335#393933, @bytesofman wrote:nice.
is this a greenfield lib or is it initializing a repo in the monorepo that exists somewhere else?
is this a greenfield lib or is it initializing a repo in the monorepo that exists somewhere else?
improve cashtab test mock prep implementation
@bot build-explorer
The API is now very good imo
fixed indentation issue (timeout was indented in script, removed indentation)
rework the API, use a client object similar to ChronikClient, set a timeout for the socket so that we get an error if the server never replies (or never sends the final \n)
Make sure to run the test plan yourself
Better comments on classes in mock-chronik-client
improve organization of address.test.ts
ok after leaving this for a day or two then looking at it again, understand the constructor overloading comment. cleaned it up, updated tests.
make constructor private, stop supporting so many input types, no overloaded constructor, better test organization
Tue, Dec 10
@bot build-explorer
Fix a typo
- move lastfailure to top of build_dir
- ignore OSError exceptions on windows (didn't use contextlib.suppress because I don't think we should ignore it on Linux)
In D17330#393720, @PiRK wrote:Benchmark on my machine:
DEFAULT_JOBS = (multiprocessing.cpu_count() // 3) + 1 ALL | ✓ Passed | 1603 s (accumulated) Runtime: 179 s DEFAULT_JOBS = multiprocessing.cpu_count() ALL | ✓ Passed | 2187 s (accumulated) Runtime: 95 s DEFAULT_JOBS = 2 * multiprocessing.cpu_count() ALL | ✖ Failed | 2583 s (accumulated) Runtime: 68 sWith one port issue in the 2 * cpu_count attempt.
RuntimeError: Could not find available PortName.P2P port after 5 attempts.
Add input type validation, add test to confirm uint8array input is also supported
Benchmark on my machine: