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

Renames master to main in fixtures/flight webpack config file #21998

Merged
merged 1 commit into from
Aug 23, 2021

Conversation

junaidbinfarooq
Copy link
Contributor

Summary

Updates the reference to the main branch in the webpack config file of fixtures/flight package

Test Plan

No tests are required.

@facebook-github-bot
Copy link

Hi @junaidbinfarooq!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@bvaughn
Copy link
Contributor

bvaughn commented Aug 3, 2021

I'm not sure why the "sync_reconciler_forks" CI task is failing but I don't think we can land this PR while it is (or it would break the main branch).

@sizebot
Copy link

sizebot commented Aug 3, 2021

Comparing: 4df10c5...23d67be

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js = 127.58 kB 127.58 kB = 40.72 kB 40.72 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js = 130.40 kB 130.40 kB = 41.65 kB 41.65 kB
facebook-www/ReactDOM-prod.classic.js = 405.16 kB 405.16 kB = 75.04 kB 75.04 kB
facebook-www/ReactDOM-prod.modern.js = 393.72 kB 393.72 kB = 73.32 kB 73.32 kB
facebook-www/ReactDOMForked-prod.classic.js = 405.16 kB 405.16 kB = 75.04 kB 75.04 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 23d67be

@junaidbinfarooq
Copy link
Contributor Author

I'm not sure why the "sync_reconciler_forks" CI task is failing but I don't think we can land this PR while it is (or it would break the main branch).

It says this in CircleCI:
image

@bvaughn
Copy link
Contributor

bvaughn commented Aug 3, 2021

It says this in CircleCI

Right. I saw the text, but it doesn't make sense given the file (and the change) that was made.

@junaidbinfarooq
Copy link
Contributor Author

It says this in CircleCI

Right. I saw the text, but it doesn't make sense given the file (and the change) that was made.

Exactly, that is what I was thinking too.

@junaidbinfarooq
Copy link
Contributor Author

Running the suggested command applies changes to various files in the react-reconciler package like changing ReactFiberLane.old to ReactFiberLane.new.

@junaidbinfarooq
Copy link
Contributor Author

Is there any way to fix the said build issue?

@bvaughn
Copy link
Contributor

bvaughn commented Aug 16, 2021

Is there any way to fix the said build issue?

Sorry. I don't know or I would have suggested a fix. 😦

@junaidbinfarooq
Copy link
Contributor Author

Is there any way to fix the said build issue?

Sorry. I don't know or I would have suggested a fix.

Perhaps, creating a branch directly and subsequently a new pr on the said repo without a fork can prevent this issue?

@bvaughn
Copy link
Contributor

bvaughn commented Aug 22, 2021

This is definitely a problem with our yarn replace-fork script. It also impacts #22151 and can be reproduced by modifying any file in the fixtures folder and running yarn replace-fork, which updates a bunch of the .old.js files to import .new.js modules (which it should not do).

Edit: #22151 (comment)

@bvaughn
Copy link
Contributor

bvaughn commented Aug 22, 2021

Now that #22156 has landed, if you rebase on HEAD of main branch you'll see the underlying error here in CI (or when you run yarn replace-fork)

@bvaughn
Copy link
Contributor

bvaughn commented Aug 23, 2021

I guess it's probably fine to sync this, since linc only lints changed files in a branch.

@bvaughn bvaughn merged commit 0da5ad0 into facebook:main Aug 23, 2021
@junaidbinfarooq junaidbinfarooq deleted the patch-1 branch August 18, 2023 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants