Skip to content

Update api from election post to winning post and window post #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Apr 10, 2020

Conversation

dignifiedquire
Copy link
Contributor

@dignifiedquire dignifiedquire commented Apr 6, 2020

  • General API updates (rust)
  • Remove Election PoSt (rust)
  • Winning PoSt (rust)
  • Window PoSt (rust)
  • Add tests for new PoSt (rust)
  • Update Go generated code
  • Update Go wrapper code
  • Update specs-actors types in order to use them in the Go wrapper code
  • Update Go tests
  • Integrate Published Params

Depends on

@laser
Copy link
Contributor

laser commented Apr 6, 2020

@dignifiedquire - I've generated CGO bindings for you, which is part of the issue. PR for that can be found here.

@dignifiedquire dignifiedquire marked this pull request as ready for review April 6, 2020 21:23
@dignifiedquire dignifiedquire marked this pull request as ready for review April 6, 2020 21:23
@dignifiedquire dignifiedquire requested review from vmx and laser April 6, 2020 21:25
Copy link
Contributor

@laser laser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BLOCKING: The go.mod file points to a local (on your host, @dignifiedquire) version of specs-actors.

@magik6k magik6k mentioned this pull request Apr 7, 2020
14 tasks
* use latest specs-actors

* generate new CGO bindings

* delete now-dead types

* fix warnings from oddly-formed format string

* drop EligibleSectors field, which wasn't used / didn't exist

* circleci to use go-paramfetch to download (instead of paramcache to generate)

* linter said i had to delete you. sorry, toSectors

* clippy made me do it

* clippy says conversion wasn't necessary

* clippy says reading to end of file is naughty

* disable pesky gomodules for binary build

* so annoying
@dignifiedquire dignifiedquire changed the title [WIP] Update api from election post to winning post and window post Update api from election post to winning post and window post Apr 10, 2020
Copy link
Contributor

@laser laser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go go go

@laser laser merged commit 870251c into master Apr 10, 2020
@laser laser deleted the feat/new-post branch April 10, 2020 23:19
gracenoah pushed a commit to gracenoah/filecoin-ffi that referenced this pull request Dec 20, 2020
…in-project#69)

* update api from election post to winning post

* add winning post api

* generate new CGO bindings

* happy clippyg

* cleanup and add test for window post

* windWOW.bizgit add .

* basic adjustments to the go interface

* gofmt

* fix go tests

* fix constants conversions

* upate api

* update to latest version

* regenerate CGO bindings + drop unused struct which referenced non… (filecoin-project#73)

* use latest specs-actors

* generate new CGO bindings

* delete now-dead types

* fix warnings from oddly-formed format string

* drop EligibleSectors field, which wasn't used / didn't exist

* circleci to use go-paramfetch to download (instead of paramcache to generate)

* linter said i had to delete you. sorry, toSectors

* clippy made me do it

* clippy says conversion wasn't necessary

* clippy says reading to end of file is naughty

* disable pesky gomodules for binary build

* so annoying

* write a dumb property test for GenerateWinningPoStSectorChallenge to ensure i'm not crazy

* add failing property test

* copy values from one memory space to the other

Co-authored-by: laser <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants