profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/qy3u/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

qy3u/leetcode-rs 1

leetcode in rust.

qy3u/6.S081-xv6-riscv-fall19 0

Labs of 2019 MIT 6.S081 "Operating System Engineering". Each lab in its own branch. For code modified in each lab, refer to closed issues. This repo is a fork of https://github.com/mit-pdos/xv6-riscv-fall19

qy3u/bellperson 0

zk-SNARK library

qy3u/bitcoinbook 0

Mastering Bitcoin 2nd Edition - Programming the Open Blockchain

qy3u/bpftrace 0

High-level tracing language for Linux eBPF

qy3u/configs 0

My configuration files

qy3u/crossbeam 0

Tools for concurrent programming in Rust

qy3u/data-oriented-design 0

A curated list of data oriented design resources.

startedo1-labs/proof-systems

started time in 8 days

pull request commentfilecoin-project/neptune

remove unnecessary `to_vec`

Sure. @porcuquine . Force pushed.

qy3u

comment created time in 12 days

push eventqy3u/neptune

qy3u

commit sha bb4b2ea981691c8ebfa0d85a68d965412893344b

remove unnecessary `to_vec`

view details

push time in 12 days

PR opened filecoin-project/neptune

remove unnecessary `to_vec`

remove unnecessary to_vec to avoid one alloc and copy

+1 -1

0 comment

1 changed file

pr created time in 18 days

create barnchqy3u/neptune

branch : remove-to-vec

created branch time in 18 days

fork qy3u/neptune

Rust Poseidon implementation.

fork in 18 days

pull request commentfilecoin-project/rust-fil-proofs

Improve multicore SDR

It seems that https://github.com/filecoin-project/rust-fil-proofs/blob/9cc6444a78408a1fc19344a973d5ea8d91d63ad4/storage-proofs-porep/src/stacked/vanilla/create_label/multi.rs#L173-L176 makes that update the bitmask before increase consumer is thread safe. Otherwise, the current fill& getimplemention should not be thread safe too? 🤔

dignifiedquire

comment created time in 18 days

startedcmu-db/noisepage

started time in 24 days

startedcmu-db/bustub

started time in 24 days

issue openedfilecoin-project/rust-fil-proofs

The ParentCache doesn't seem to be generated correctly in circleci

Hi @cryptonemo @dignifiedquire . I just saw the CI test failure on my previous PR https://github.com/filecoin-project/rust-fil-proofs/pull/1477 .

After checking the detail of the failure in https://circleci.com/api/v1.1/project/github/filecoin-project/rust-fil-proofs/74927/output/106/0?file=true&allocation-id=611544a9648d5f76edbe1b19-0-build%2F7693C729 I found the error message: 'Error: corrupted cache: /var/tmp/filecoin-parents/v28-sdr-parent-3f0eef38bb48af1f48ad65e14eb85b4ebfc167cec18cd81764f6d998836c9899.cache, expected at least 3584, got 0 bytes'

According this error message, it seems that the test failed because the ParentCache file doesn't generated correctly in circleci. Besides,I have checkout to the commit that contains my PR and run the test locally, here is my command 'FIL_PROOFS_USE_MULTICORE_SDR=1 RUST_LOG=trace cargo test lifecycle_2kib --no-default-features --features gpu,blst --verbose --package filecoin-proofs --release -- --ignored --nocapture' . The test passed on my ubuntu machine.

I don't know a lot about circleci.I don't know in what environment it run these tests, but I saw it generate '/var/tmp/filecoin-parents/v28-sdr-parent-3f0eef38bb48af1f48ad65e14eb85b4ebfc167cec18cd81764f6d998836c9899.cache' and other cache multi times. In my sense, It's a little weired because while generating the cache, It use a exclusive file lock: https://github.com/filecoin-project/rust-fil-proofs/blob/9d6da0dc8ecbfe7e7b42dba44fcff1feafbbd2cc/storage-proofs-porep/src/stacked/vanilla/cache.rs#L298 According to the implemention of the LockFile, it use create_new not create, create_new will failed if the file exists.So, it makes me a little confused that how can these tests passed while multiple generating onto the same path exist (for example 'generating /var/tmp/filecoin-parents/v28-sdr-parent-b43672d2166d241418debd08d351335b3aa264f729125470f2eeb68f7a11fb20.cache' appear 3 times on the log above)? Looking forward to your opinion!

created time in a month

push eventqy3u/waitpool

qy3u

commit sha 205c4a543a77de13c6e0d6cecc76debddd01cbfb

initial commit

view details

push time in 2 months

create barnchqy3u/waitpool

branch : master

created branch time in 2 months

created repositoryqy3u/waitpool

created time in 2 months

fork qy3u/bpftrace

High-level tracing language for Linux eBPF

fork in 2 months

startediovisor/bpftrace

started time in 2 months

push eventqy3u/crossbeam

yuqing

commit sha a649cfc19ef4b0e669741afb5db2937a5c691364

remove unnecessary 'move' keyword

view details

bors[bot]

commit sha 311124c8336c80dfdce1b8f4b29f2a27f035725c

Merge #715 715: remove unnecessary 'move' keyword r=taiki-e a=qy3u The newer 'f' only captures a mut reference of the former 'f' to make itself becomes a FnMut.So, the 'move' keyword here seems unnecessary. Co-authored-by: yuqing <qy3u@outlook.com>

view details

push time in 2 months

push eventqy3u/rust-fil-proofs

qy3u

commit sha dbe251e0d0bf7381db26ec5618611af38d4f1f8c

set predecessor_index missing by api_version

view details

push time in 2 months

push eventqy3u/rust-fil-proofs

qy3u

commit sha b6af031a322b2f2203432f71f6039af211ff98a7

set predecessor_index missing by api_version

view details

push time in 3 months

push eventqy3u/rust-fil-proofs

push time in 3 months

push eventqy3u/rust-fil-proofs

nemo

commit sha 64a7c43abbb986bccb1d1e8532d711b269644994

feat: add a srs key loading bench (#1474) * feat: add a srs key loading bench * feat: separate aggregation benches from preprocessing * feat: add an aggregate proof encode/decode test * fix: separate aggregate proof test bytes from test * fix: improve tests by adding specific constants expected * doc: update comment and rename argument variable * feat: re-factor aggregation testing

view details

qy3u

commit sha 26865f5eb890e326b63be589713109d1635d6018

Merge branch 'master' into fix/unset_bitmask

view details

push time in 3 months

push eventqy3u/rust-fil-proofs

qy3u

commit sha 204358d6afd9c4056ac99f48a95d97f3d3ef8752

set predecessor_index missing by api_version

view details

push time in 3 months

push eventqy3u/rust-fil-proofs

qy3u

commit sha 469cc1fdeca055f1d47a46cf6660d30b1de551bd

set predecessor_index missing by api_version

view details

push time in 3 months

pull request commentfilecoin-project/rust-fil-proofs

Fix: correct usage of BitMask in multicore sdr

Hi @porcuquine. This PR has updated.Now,it stores the api_version in ParentCache and CacheReader, then it matchs the version stored to get corresponding indexs.

qy3u

comment created time in 3 months

push eventqy3u/rust-fil-proofs

qy3u

commit sha 309a8ad56e32d85252b263f1a33f4271a4708fdf

set predecessor_index missing by api_version

view details

push time in 3 months

PullRequestReviewEvent

Pull request review commentfilecoin-project/rust-fil-proofs

Fix: correct usage of BitMask in multicore sdr

 fn fill_buffer(     // Node 5 (prev node) will always be missing, and there tend to be     // frequent close references.     if cur_node > MIN_BASE_PARENT_NODE {-        // Mark base parent 5 as missing+        // Mark base parent 0 as missing         // base_parent_missing.set_all(0x20);-        base_parent_missing.set(5);+        base_parent_missing.set(0);

You are right! The current implemention doesn't has a good compatibility with different versions of the graph (which it should be).I'll try to improve this PR to solve this quesion.

qy3u

comment created time in 3 months

PR opened filecoin-project/rust-fil-proofs

Reviewers
Fix: correct usage of BitMask in multicore sdr

This PR contains two commits:

  1. The prev node is the first node of parents not the fiveth: https://github.com/filecoin-project/rust-fil-proofs/blob/00cb80440d14dd760805c14db597a306d4433fb2/storage-proofs-core/src/drgraph.rs#L168
  2. Unset the bpm after using it. The current implemention has never unsetted it so it will always read all base parents in the main hash loop.
+6 -4

0 comment

2 changed files

pr created time in 3 months

create barnchqy3u/rust-fil-proofs

branch : fix/unset_bitmask

created branch time in 3 months

push eventqy3u/rust-fil-proofs

nemo

commit sha 29bac1a25bd1663d06390bb9996fbddb0d2f4258

docs: update changelog for release

view details

nemo

commit sha 512de274fe43075018f63200ff89247aaf04aede

chore(filecoin-hashers): release 2.0.0

view details

nemo

commit sha 34136879052d7901e872009f3b9f7f8b033f3cdc

chore(storage-proofs-core): release 7.0.0

view details

nemo

commit sha 282af8c8c912cd98df75f60c56a09cb4a79b1537

chore(storage-proofs-porep): release 7.0.0

view details

nemo

commit sha 2893ece2a9dbc394e511e38ffda34ee0b5e792b3

chore(storage-proofs-post): release 7.0.0

view details

nemo

commit sha dba85626ddacf1c2ce63b7ba6fa32dae15364566

chore(filecoin-proofs): release 7.0.0

view details

nemo

commit sha fe6be2e4e60681733b684481ea690be61248066f

chore(fil-proofs-tooling): release 6.0.0

view details

nemo

commit sha f006700bec529dbf2dff3f55d2e8c1869fa3aec7

chore(fil-proofs-param): release 2.0.0

view details

nemo

commit sha 8c0fb8312391e47203506c0fe2aa06753890dae1

fix: update initial value for cache_count (#1454)

view details

nemo

commit sha 9eeccd17d99b978de225abbfe4f596049028f79b

docs: fix changelog errors (#1451)

view details

nemo

commit sha 22dada5504db2c381bdf47226812d0e4a4041b7a

fix: avoid unsupported sha256_intrinsics on aarch64 (regression) (#1455) * fix: avoid unsupported sha256_intrinsics on aarch64 (regression) * feat: add aarch64 CI jobs to ensure proper baseline support * feat: add required alignment in fr32 reader

view details

nemo

commit sha 7b35df3d0218573842fc053419ab8e519a59a461

fix: remove build warnings (#1456) * fix: remove build warnings * feat: upgrade nightly version used in CI * fix: bump rustup cache version * fix: update GPU CI runtime config

view details

nemo

commit sha 32eed31f92ed43f36956a0b8427d5689850b4622

feat: update sha2-asm dependency version (#1457) * feat: update sha2-asm dependency version * fix: update call based on updated version

view details

nemo

commit sha a38c9db40992f0e486885d5572328178a331ad5d

docs: update changelog for release

view details

nemo

commit sha da52915ae711a9c8a6f5b899613b77f8a76ec15c

chore(filecoin-hashers): release 2.0.1

view details

nemo

commit sha 5aa9bd651ae0a37e268d2ead07b4a29ef275f01c

chore(fr32): release 0.2.1

view details

nemo

commit sha c809248f88a35d2d887fad808fbcae61338690f8

chore(sha2raw): release 2.1.1

view details

nemo

commit sha c8205fbc254305158eaaad71d85a6cb7dc515ebe

chore(storage-proofs-core): release 7.0.1

view details

nemo

commit sha 5d6debb4fdacbaf11f6edf42ff2290bc9ad258a6

chore(storage-proofs-porep): release 7.0.1

view details

nemo

commit sha 09ade5278499ede5e4654659b0f26f64b5f63c58

chore(storage-proofs-post): release 7.0.1

view details

push time in 3 months