-
Couldn't load subscription status.
- Fork 6.6k
Update folly, fix USE_FOLLY_LITE #14071
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
base: main
Are you sure you want to change the base?
Conversation
Summary: Resolving this folly upgrade required fixing the FOLLY_LITE build with header include from the 'fmt' library. I was close to timing out on fixing USE_FOLLY_LITE and removing it altogether - it could be considered obsolete and/or not worth the maintenance cost. Test Plan: CI
|
@pdillinger has imported this pull request. If you are a Meta employee, you can view this in D85268833. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing this!
Makefile
Outdated
| perl -pi -e 's/memcpy.&ptr/memcpy((void*)&ptr/' third-party/folly/folly/lang/Exception.cpp | ||
| @# const mismatch | ||
| perl -pi -e 's/: environ/: (const char**)(environ)/' third-party/folly/folly/Subprocess.cpp | ||
| @# NOTE: boost source will be needed for any build including `USE_FOLLY_LITE` builds as those depend on boost headers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we don't need to fetch fmt here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My local build apparently already had folly built from a full folly build.
And now I'm sure I would hit another CI failure if I just made the fix because of the new folly caching which does not hash the relevant makefile parts, so I'm going to arbitrarily change the folly git hash again :(
|
Well, that's concerning: |
|
@pdillinger oh wow. Should we file an issue for folly? |
It's more likely a rare race or UAF or something in our code, though I haven't been able to reproduce it. |
Summary: Resolving this folly upgrade required fixing the FOLLY_LITE build with header include from the 'fmt' library.
I was close to timing out on fixing USE_FOLLY_LITE and removing it altogether - it could be considered obsolete and/or not worth the maintenance cost.
Follow-up: make the folly build caching more friendly by hashing the relevant makefile parts. Not in this PR because then you wouldn't be able to see what changed in the folly build steps themselves.
Test Plan: CI