THE COMMUNITY / FIND YOUR STACK
Explore 581 technologies, with eight spacious topic cards per page.
581 technologies · 8 on this page
Frameworks & web
Problem Statement After upgrading the htmx library, click interactions that previously relied on hx-boost no longer trigger requests. The page loads, but the console shows no network activity and the DOM does not update. Diagnostic Constraints • The application pins a specific htmx file via a CDN, using SRI where possible. • A prior build remains deployable;
Frameworks & web
I'm designing a libGDX game (assume 1.12.x, desktop and Android targets) that uses a single shared AssetManager across multiple Screen implementations: a loading screen, a menu screen, and several level screens. The loading screen polls update() and reads getProgress() to drive a progress bar, which works fine. The unresolved part is the boundary between the
Languages & runtimes
DBIx::Class::Migration::Version provides a structured way to manage schema evolution using up and down methods. While this framework tracks versioning via a metadata table, the actual execution of Data Definition Language (DDL) statements depends on the underlying database engine's capabilities. In environments using databases that do not support transaction
DevOps & observability
Goal is to surface only actionable build problems to notification channels while keeping normal build progress in logs. Packer controls verbosity via PACKER_LOG with levels debug, info, warn, error, and the -debug flag forces full trace output regardless of the environment variable. With PACKER_LOG at warn or error, informational step messages are suppressed
Developer tools
The objective is to migrate a single Chakra UI component from v2 to v3 while the remainder of the application continues to run on v2, ensuring no visual downtime, consistent theming across the boundary, and no unplanned bundle-size increase. Chakra UI v3 replaces the Emotion-based style engine with a recipe and slot-recipe system (defineConfig, defineRecipe)
Frameworks & web
Server-Side State Persistence Vaadin Flow maintains a server-side component tree that mirrors the browser DOM. In high-availability environments, this state is often offloaded to a distributed session store to allow for seamless failover across multiple server nodes. Interoperability Constraints When the Java server state is serialized and stored externally,
Developer tools
A pnpm workspace stores packages once in a content-addressable store and creates per-project node_modules via symlinks. Strict isolation preserves deterministic resolution and disk efficiency, but changes resolution paths compared to a flat layout. Selective hoisting via public hoist patterns and node linker options can expose specific packages at the worksp
Databases & messaging
Objective Determine whether point-in-time restore operations maintain data consistency when the source Cosmos DB account undergoes API version transitions within the 4-week backup retention window. Constraints Core SQL API accounts support continuous backup and PITR features. The restore creates a new container with copied data preserving schema but not iden
When using htmx's hx-retry attribute on a form that issues a POST request to create a resource, the goal is to prevent duplicate writes if the initial request succeeds but htmx retries due to a transient network error. htmx currently re‑issues the exact same request without any built‑in mechanism to detect that the server already processed the operation, so
Unannounced failure states in an hx-swap workflow I am designing a form workflow that uses hx-post with hx-target and hx-swap to update a results fragment in place. The documented behavior is that htmx, by default, does not swap response content for 4xx and 5xx status codes (with version-sensitive exceptions such as 422), which means a failed request can pro
The libgdx Disposable interface defines a void dispose() method, yet several implementations raise an IllegalStateException when dispose() is invoked more than once. Because the Javadoc is silent on whether repeated calls are permitted, developers encounter inconsistent outcomes: some libraries ignore the second call, others abort with an unchecked exception
Goal: ensure that a schema change made through libgdx’s gdx‑sql extension can be reliably rolled back to the previous version without requiring a full database backup. Constraint: SQLite versions prior to 3.35 commit DDL statements immediately, so wrapping ALTER TABLE in a transaction does not allow undo; developers must decide between maintaining incrementa
Perl’s reference‑counting memory manager reclaims objects when their count drops to zero, but circular references prevent this, requiring techniques such as weakening references with Scalar::Weak . To decide whether to adopt weak references in performance‑critical code, it is necessary to quantify the runtime cost of the extra bookkeeping they introduce. The
Goal: Establish a consistent policy for how DateTime::TimeZone resolves ambiguous local times that occur during daylight‑saving‑time fallback when no explicit disambiguation is supplied. Constraints: The module currently leaves the interpretation to the caller, which can lead to different results across systems or when using outdated tzdata. Additionally, Da
DNS Resolution Timing in Packer HCL2 Templates When configuring Packer templates with multiple network interfaces or custom DNS settings, there is an unresolved question about when DNS resolution occurs relative to template validation and builder initialization. The HCL2 syntax allows defining custom DNS servers through builder configurations like dns_server
Plugin version resolution at init time Packer 1.7+ uses a gRPC-based plugin protocol where the core negotiates a protocol major version at startup and rejects plugins advertising an incompatible major version. The packer init command resolves plugins declared in required_plugins blocks; when a version constraint uses a tilde ( ~> 1.2.3 ) or caret ( ^1.2.3
Goal: implement dark‑mode style values for a UI component in a Next.js 13+ App Router project that works correctly during server‑side rendering and updates instantly when the user toggles color mode, while keeping runtime cost low and avoiding hydration warnings. Constraint: the useColorModeValue hook provides live updates but can only be used in client comp
Goal Determine whether Chakra UI v2's internal state management and component lifecycle handling are fully compatible with React 18's concurrent rendering features, particularly startTransition and automatic batching. Constraints and Uncertainty Chakra UI v2 officially requires React 18, but the library's support for concurrent features remains partially exp
Context Vaadin 24 LTS tightened enforcement of @AnonymousAllowed so that navigation now requires explicit permission even when a mock user exists in the Spring Security test context. This change affects integration tests that rely on @SpringBootTest with @WithMockUser to exercise views without production credentials. Problem When the Spring Security filter c
When Vaadin Flow is configured with pushMode=AUTO , the framework attempts a WebSocket connection before falling back to long polling if the handshake fails. In environments behind strict proxies or utilizing self-signed certificates, the WebSocket handshake may time out silently without triggering an explicit client-side error in the browser console. While
Goal: deterministic rollback after lockfile schema transition pnpm uses a content‑addressable store that keeps each package version once in the global store, symlinking it into node_modules . The lockfile carries a lockfileVersion field that changed from 6.0 (pnpm 8) to 7.0 (pnpm 9) to support new features. When a project is checked out with a lockfile gener
Corporate networks that intercept TLS often require pnpm to trust a custom certificate authority while also disabling strict SSL validation. In these environments, pnpm install can fail with UNABLE_TO_VERIFY_LEAF_SIGNATURE even after both strict-ssl=false and a custom ca or cafile are configured. The uncertainty is that pnpm's fetcher appears to apply these
The goal is to understand whether Cosmos DB Change Feed guarantees exactly‑once processing of pre‑upgrade changes when a move to API v2.0.0 Full Fidelity mode fails and the account reverts to the legacy API. Constraints include the lack of automatic checkpoint migration during version changes, the possibility that a processor already switched to Full Fidelit
Automatic indexing in Azure Cosmos DB for NoSQL indexes every property on write, simplifying schema evolution but consuming request units per operation. When a custom indexing policy excludes specific paths, the default composite index interaction with remaining fields becomes a design consideration, particularly for range and equality queries. The policy ch
java
sqlite
nextjs