THE COMMUNITY / FIND YOUR STACK
Explore 581 technologies, with eight spacious topic cards per page.
581 technologies · 8 on this page
Developer tools
TeX's Knuth–Plass paragraph builder retries breakpoint selection once with \emergencystretch after \pretolerance and \tolerance passes fail. The goal is to confirm whether that single emergencystretch attempt is the engine's final fallback when no acceptable breakpoints exist, or whether an additional automatic retry is available in any TeX engine. Documente
Mobile & games
A Framework7 view is expected to present 5,000–10,000 records on memory-constrained Android devices while keeping scrolling responsive. Assuming Framework7 v8 is the target major release, the unresolved design decision is between the documented Virtual List and Standard List components; the exact Virtual List options and defaults still need confirmation for
Mobile & games
A Framework7 view is expected to present 5,000–10,000 records on memory-constrained Android devices while keeping scrolling responsive. Assuming Framework7 v8 is the target major release, the unresolved design decision is between the documented Virtual List and Standard List components; the exact Virtual List options and defaults still need confirmation for
Frameworks & web
A major Ionic upgrade may also require a matching Capacitor native migration, but the web framework and native projects do not have identical change boundaries. The documented Capacitor update capability automates native configuration migration, while custom code added directly under android/ and ios/ is not managed by the Ionic CLI. The goal is to define wh
Frameworks & web
A major Ionic upgrade may also require a matching Capacitor native migration, but the web framework and native projects do not have identical change boundaries. The documented Capacitor update capability automates native configuration migration, while custom code added directly under android/ and ios/ is not managed by the Ionic CLI. The goal is to define wh
Developer tools
Goal Determine whether Drupal core's automatic database log pruning can remove messages from a failed deployment before an administrator reviews the Recent log entries report. Constraints and uncertainty The dblog module retains a configurable maximum number of entries and deletes older entries during cron. The default limit, administration path, and pruning
Frameworks & web
Livewire renders form inputs through Blade while Alpine.js manipulates the DOM, creating an integration boundary where focus is not automatically transferred after Alpine updates. Because Livewire’s @this directive can interfere with Alpine’s x‑data state and server‑side validation messages may appear after Alpine changes, developers lack a reliable method t
Developer tools
Goal Run distributed Erlang nodes across production hosts after local tests succeeded using short names and default ephemeral distribution ports. Constraint Production firewalls commonly allow EPMD on TCP 4369 but block the ephemeral TCP ports used for distribution data channels. Nodes started with -sname resolve on localhost but can fail across hosts when s
Portable restricted shell-escape allowlist A document that runs an external converter through \code{\write18} works on a local workstation but fails in production CI. The goal is to keep the same source compiling under both environments without weakening production security. pdfTeX, XeTeX, and LuaTeX read \code{shell_escape} from texmf.cnf: \code{f} disables
Goal: Configure the TeX engine so that a format file (.fmt) is automatically considered stale and rebuilt whenever any of its source .tex or .sty files are modified. Constraint: The current caching mechanism does not track file timestamps or content changes of the inputs, and there is no way to declare a set of directories that should trigger regeneration wi
Ensuring that a Xamarin.Android app's backup and restore cycle works correctly requires verifying that the backup archive captures all relevant app data, that the restore operation returns the device to the exact pre-backup state, and that no unintended side effects occur during the process. Validation must be feasible on both emulators and physical devices
The Android Navigation Component is designed to persist the navigation back‑stack across process death by storing NavBackStackEntry objects in a SavedStateHandle attached to the NavController . When the app is relaunched, the component rebuilds the NavGraph and re‑executes the navigation actions that led to the current destination. In practice, this restorat
When developing a Framework7‑Vue application I have added an admin section under the route /admin. I want to be certain that this section cannot be reached by unauthenticated users after the app is built and served publicly, but I am unsure how Framework7’s navigation guard mechanism behaves in production builds. The build process bundles the router configur
Integration Boundary Framework7's Router handles asynchronous route resolution through dynamic imports and template loading, while the Request Library ( f7.request ) manages XHR and fetch calls independently. The two subsystems operate without a shared cancellation protocol. Goal and Constraints The objective is to determine whether the framework provides an
Goal: Migrate a small Ionic Angular application to a newer version of Capacitor while using Ionic App Flow live updates to achieve zero‑downtime deployment. Constraints: The live update must keep the existing web bundle compatible with the native runtime and any Capacitor plugins that are being upgraded. Uncertainty exists around how to detect and resolve ve
Key/Value Persistence in Capacitor Apps The goal is to store small, frequently accessed key/value pairs in a Capacitor 5.x application while keeping the UI thread responsive and ensuring data security across iOS and Android. Two documented approaches are available: Capacitor Storage plugin – uses SQLite on iOS and SharedPreferences on Android, offers an asyn
Goal: Migrate a small Ionic Angular application to a newer version of Capacitor while using Ionic App Flow live updates to achieve zero‑downtime deployment. Constraints: The live update must keep the existing web bundle compatible with the native runtime and any Capacitor plugins that are being upgraded. Uncertainty exists around how to detect and resolve ve
Context Ionic 7+ applications using the default Vite builder load environment variables from .env files during both ionic serve and ionic build --prod . Vite's documented behavior requires a VITE_ prefix for variables to be exposed to the client bundle via import.meta.env . Observed discrepancy During development with ionic serve , Vite's dev server injects
I want to ensure that files placed in Drupal’s public file system are not unintentionally served to visitors when they contain sensitive information such as configuration exports or logs. The site uses the default public file path defined in admin/config/media/file-system, and I am unsure whether additional server‑level restrictions are required to block acc
Drupal Core Password Expiration and LDAP Authentication Goal: Determine whether Drupal core's expiring-passwords enforcement applies to accounts authenticated through an external provider such as LDAP or OAuth, and whether least-privilege role permissions can control password-reset access independently of external login. Drupal 8, 9, and 10 core include an o
When a FilamentPHP Livewire component initiates a long‑running operation, I need the UI to stay responsive, show a loading indicator, and allow the user to cancel the operation while also guaranteeing that the process does not exceed a predefined maximum execution time. The component must clean up any background workers or queued jobs when cancellation or ti
Trade-off: client-held locked IDs versus server-side re-fetching Livewire v3 components often need a stable resource identifier (for example, a post ID) to authorize mutations such as delete() or update() . Two documented patterns exist: Expose the ID as a public property marked #[Locked] so the client cannot tamper with it; Livewire's checksum validates int
When an Erlang release fails during deployment, the default error_logger output goes to the console and can be lost if the node terminates abruptly. To diagnose the failure later, I need to capture error_logger events in a file that survives node crashes and is available for offline inspection. Using error_logger:logfile/1 redirects logs to a file, but I am
In Erlang/OTP, using a `gen_server` to manage connection pools can lead to intermittent exhaustion when downstream dependencies experience latency. While the process remains active, the `gen_server` loop lacks a native timeout for individual message processing. If a request handler blocks on external I/O, the process cannot consume subsequent messages, causi
oauth