-
Notifications
You must be signed in to change notification settings - Fork 886
chore: apply the 4mb max limit on drpc protocol message size #17771
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
14f3977
to
168fe3d
Compare
168fe3d
to
9ba91b6
Compare
98815ee
to
3783241
Compare
9ba91b6
to
073bedd
Compare
073bedd
to
c041459
Compare
I'm not sure I follow the logic. Aren't modules fetched dynamically at import time, which happens after the (up to) 10MB upload? There are no constraints on how big the modules could be during the import build which downloads them from a registry. |
You are right, modules will have to have a different solution. I thought a 10mb file could be uploaded as a template version, which would fail at the protobuf layer. Our We should still keep the config setting, as we check against 4mb limits here: coder/coderd/provisionerdserver/provisionerdserver.go Lines 710 to 713 in c041459
Edit: Reverted to 4mb, but still want the constant to set the settings |
Co-authored-by: Spike Curtis <spike@coder.com>
Respect the 4mb max limit on proto messages