reflex-dev/reflex

reflex

Performance History

Latest Results

hosting-cli(gcp): add --cpu, --memory, --min-instances flags (#6552) * hosting-cli(gcp): add --cpu, --memory, --min-instances flags Forward the new CPU / MEMORY / MIN_INSTANCES env vars to the deploy script so users can override the Cloud Run resource allocation. The restricted env in `_run_deploy_script` means callers couldn't override these from their shell — they have to come through the CLI flags. Defaults match the previously hard-coded values (1 / 1Gi / 1). Requires the matching backend change in flexgen (reflex-dev/flexgen#3735) so the deploy script honors the new env vars. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * review: rename env vars to CLOUD_RUN_* and validate --min-instances Per Greptile review on #6552: - Rename CPU / MEMORY / MIN_INSTANCES env vars to CLOUD_RUN_CPU / CLOUD_RUN_MEMORY / CLOUD_RUN_MIN_INSTANCES to avoid ambient shell-var shadowing (the bash `:=` expansion in the deploy script would pick up any ambient value with these short names). The flexgen-side script was renamed in the companion PR. - Validate --min-instances at the CLI via `click.IntRange(min=0)` so garbage input fails fast with a helpful error instead of bubbling up as an opaque gcloud error. Skipping format validation on --cpu and --memory: the set of valid Cloud Run values varies by execution-environment generation, so a client-side regex risks rejecting valid input. Let gcloud be the authority on what it accepts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ruff-format: collapse multi-line test signature Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: update reflex-docs dependency installation command to use --frozen --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

main

5 hours ago

test(compiler): match consolidated BaseContext error message The remaining "must be entered with 'with' or 'async with'" regex in test_compile_context_requires_attached_context didn't match the consolidated BaseContext's "must be entered before calling this method" message, so all 10 unit-tests jobs failed on CI. Loosen the regex to match the prefix shared by the new wording.

BABTUNA:issue-6514-consolidate-basecontext

5 hours ago

refactor(reflex-base): consolidate BaseContext into context.base (#6514) Removes the duplicate BaseContext defined in plugins/compiler.py and makes PageContext/CompileContext inherit from reflex_base.context.base. Converts BaseContext from a frozen dataclass to a plain class with __slots__ = () so frozen (RegistrationContext, EventContext) and non-frozen (PageContext, CompileContext) subclasses can both inherit. Ports the async __aenter__/__aexit__ helpers over from the removed copy, and pins identity equality on the base via object.__eq__ / object.__hash__. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

BABTUNA:issue-6514-consolidate-basecontext

6 hours ago

fix: update reflex-docs dependency installation command to use --frozen

simon/gcp-cloud-run-resources

6 hours ago

ruff-format: collapse multi-line test signature Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

simon/gcp-cloud-run-resources

6 hours ago

review: rename env vars to CLOUD_RUN_* and validate --min-instances Per Greptile review on #6552: - Rename CPU / MEMORY / MIN_INSTANCES env vars to CLOUD_RUN_CPU / CLOUD_RUN_MEMORY / CLOUD_RUN_MIN_INSTANCES to avoid ambient shell-var shadowing (the bash `:=` expansion in the deploy script would pick up any ambient value with these short names). The flexgen-side script was renamed in the companion PR. - Validate --min-instances at the CLI via `click.IntRange(min=0)` so garbage input fails fast with a helpful error instead of bubbling up as an opaque gcloud error. Skipping format validation on --cpu and --memory: the set of valid Cloud Run values varies by execution-environment generation, so a client-side regex risks rejecting valid input. Let gcloud be the authority on what it accepts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

simon/gcp-cloud-run-resources

6 hours ago

hosting-cli(gcp): add --cpu, --memory, --min-instances flags Forward the new CPU / MEMORY / MIN_INSTANCES env vars to the deploy script so users can override the Cloud Run resource allocation. The restricted env in `_run_deploy_script` means callers couldn't override these from their shell — they have to come through the CLI flags. Defaults match the previously hard-coded values (1 / 1Gi / 1). Requires the matching backend change in flexgen (reflex-dev/flexgen#3735) so the deploy script honors the new env vars. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

simon/gcp-cloud-run-resources

7 hours ago

refactor: make test proper

BABTUNA:fix-docs-breadcrumb-dead-filter

8 hours ago

Latest Branches

refactor(reflex-base): consolidate BaseContext into context.base (#6514)#6553

5 hours ago

94c05d2

BABTUNA:issue-6514-consolidate-basecontext

hosting-cli(gcp): add --cpu, --memory, --min-instances flags#6552

6 hours ago

894e1b0

simon/gcp-cloud-run-resources

fix(docs): remove dead docs breadcrumb segment filter#6427

8 hours ago

26c91ea

BABTUNA:fix-docs-breadcrumb-dead-filter

Home Terms Privacy Docs