Skip to content
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

Add is_string column to market_deal_proposal model #1015

Merged
merged 6 commits into from
Jul 1, 2022

Conversation

frrist
Copy link
Member

@frrist frrist commented Jun 30, 2022

@codecov-commenter
Copy link

codecov-commenter commented Jun 30, 2022

Codecov Report

Merging #1015 (0b4ac92) into frrist/update-lotusv1.16.0-rc (1da0a11) will increase coverage by 1.9%.
The diff coverage is n/a.

@@                       Coverage Diff                       @@
##           frrist/update-lotusv1.16.0-rc   #1015     +/-   ##
===============================================================
+ Coverage                           35.5%   37.5%   +1.9%     
===============================================================
  Files                                 44      41      -3     
  Lines                               2884    2717    -167     
===============================================================
- Hits                                1025    1019      -6     
+ Misses                              1755    1595    -160     
+ Partials                             104     103      -1     

@frrist frrist changed the title Frrist/market proposal label Add is_string columnt to market_deal_proposal model Jun 30, 2022
@frrist frrist changed the title Add is_string columnt to market_deal_proposal model Add is_string column to market_deal_proposal model Jun 30, 2022
Copy link

@davidgasquez davidgasquez left a comment

Choose a reason for hiding this comment

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

Should we also update Lily data models with the new column, or that should be done at export time? Not sure how close these docs are to the real "live" schema.

return nil, fmt.Errorf("diffing deal states: %w", err)
}
isString = true
base64Label = base64.StdEncoding.EncodeToString([]byte(labelString))
Copy link
Contributor

Choose a reason for hiding this comment

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

If the label is a string, is it still necessary to sanitize the label?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think yes because the string may have utf stuff in it and make very ugly csvs (if not broken ones).

Copy link
Member Author

Choose a reason for hiding this comment

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

Is the ask to sanitize the label (using the currently removed SanitizeLabel method) before encoding it as base64?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes! And sorry for phrasing it as a question as I was not certain myself.

Copy link
Contributor

Choose a reason for hiding this comment

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

Moving my comment here from Slack for posterity:

My expectation is that if I decode a string from base64, it should already be cleaned of invalid characters, otherwise this falls into the realm of "surprising and unexpected" behavior.

@frrist frrist force-pushed the frrist/update-lotusv1.16.0-rc branch 3 times, most recently from 135e7bf to b9a137f Compare June 30, 2022 20:39
@frrist frrist force-pushed the frrist/market-proposal-label branch from 0b4ac92 to 59911fa Compare July 1, 2022 19:43
@frrist frrist merged this pull request into frrist/update-lotusv1.16.0-rc Jul 1, 2022
@frrist frrist deleted the frrist/market-proposal-label branch July 1, 2022 20:47
frrist added a commit that referenced this pull request Jul 4, 2022
* chore: add is_string column to market_deal_proposal model
frrist added a commit that referenced this pull request Jul 5, 2022
* deps: update to lotus v0.16.0

* refactor: remove unused actor gen code

* chore: update actor code generator for v8

* gen: init actor accessors

* gen: market actor accessors

* gen: multisig actor accessors

* gen: power actor accessors

* gen: reward actor accessors

* gen verifreg actor accessors

* gen: miner actor accessors

* chore: update miner state extractors

- required due to changes in miner actor gen accessors

* chore: update market actor extractors

- required for market actor gen accessors

* gen: builtin accessors

* refactor: remove unused map opts lookup

- actor accessors now return map opt values

* chore: update message test deps

- use v8 actor structs

* feat: add actor CID lookups

- replace with filecoin-project/lotus#8941 when lotus v1.17.0 is cut

* chore: update lens interface to match lotus api

- required due to lotus update v1.16.0

* refactor: register new actor code in processor

* fix: update parsed message extractor with new exitcode

* fix: only init VM for network version prior to 13

- ensures we can process message on FVM upgrade boundary

* Add is_string column to market_deal_proposal model (#1015)

* chore: add is_string column to market_deal_proposal model

* fix: many incorrect pointer equality comparisons (#1018)

* fix: many incorrect pointer equality comparisons
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.

5 participants