ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DataSpell's DataFrame preview widget must display tabular data efficiently, stay read-only, and react to changes without compromising kernel stability. This architecture note outlines requirements, minimal design, trust boundaries, operational checks, and failure modes.
Goal: confirm whether the Storybook 8.x preview iframe renders a React Suspense fallback when a story component uses useQuery({ suspense: true }) while the initial query promise is pending. React Query supports suspending rendering until data resolves, and Storybook 8.x supports asynchronous play functions inside the preview. The unresolved interoperability
The Pulumi preview command acquires a read lock on the stack state when using a backend that supports locking (e.g., AWS S3 + DynamoDB). This allows multiple previews to run simultaneously but is intended to block concurrent update operations that require a write lock. The exact interaction between a running preview and an ongoing up operation is not fully d
Issue: Stale preview after Git rollback StackBlitz’s live preview rebuilds whenever files are saved, including configuration changes such as package.json updates. However, when a user performs a Git rollback to a previous commit, the file system is reverted but the preview iframe may still serve bundles cached from the prior build. This can result in a misma
Developers want `pulumi preview` to show an accurate drift detection without manually adding `--refresh` each time, so that the preview step remains reliable in a repeatable development workflow. The current behavior requires the explicit `--refresh` flag to synchronize state with remote resources, which guarantees correctness but can increase preview durati
Branch Deploy Preview Environment Variable Exposure Netlify branch deploys generate public preview URLs for each commit, and environment variables assigned to a branch deploy may be available to the preview build runtime. The goal is to keep sensitive credentials out of preview contexts while preserving non-secret variables required for builds. It is unclear
Goal: Allow Pulumi preview to complete when the configured provider lacks read‑only permissions, so users can run preview in least‑privilege environments without granting broad IAM rights. Constraint: Preview currently invokes the provider’s read APIs to enumerate existing resources; missing permissions cause an authorization error, and substituting a mock p
Memory retention during repeated preview invocations The Pulumi Automation API runs the engine in‑process and keeps the full resource state graph alive for the lifetime of a Workspace . When repeatedly creating a stack, previewing, and disposing the workspace, users observe a steady increase in resident memory that does not plateau, even after calling worksp
dataspell
pulumi
git
netlify