ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Prisma 5.0 introduced the poolTimeout datasource parameter to control how long a query waits for an available connection before throwing ConnectionTimedOut. The default of 30000ms is documented, but no guidance exists for choosing values that suit applications with highly variable or bursty request patterns, especially in serverless environments where cold s
Automating bot deployments on Discloud requires balancing convenience with the principle of least privilege. The platform authenticates API and CLI operations through a personal access token tied to the user's account, meaning any token held by an automation script inherits the full permission set of that account rather than a scoped subset for individual ap
Cost‑efficient injection for low‑traffic Gatling scenarios The objective is to lower cloud instance‑hour expenses for Gatling tests that simulate a low‑traffic workload, such as one user generating requests at one per second. Constraints include using Gatling 3.10+ DSL helpers, accounting for JVM warm‑up and garbage‑collection pauses that may affect resource
I have a Scala 2.13 service where a function takes an expensive by-name parameter that builds a large in-memory index. The function body references that parameter several times, so the expression is re-evaluated on each access, which I understand is the documented semantics of by-name parameters (unlike by-name vals, which evaluate once at definition). My go
The goal is to schedule useful, user-visible alerts with Capacitor Local Notifications while avoiding audible noise and unnecessary interruption. Local Notifications supports controlling sound, vibration and presentation, but the effective behavior is platform specific. On Android, notification channel importance is determined at channel creation and control
A Nuxt 3 app needs to surface failures usefully without turning every problem into a full-screen interruption. The framework ships no notification system, so the nearest documented lever is error handling: showError or createError with fatal: true renders the app-wide error.vue page, while non-fatal errors are left for local handling, and useAsyncData and us
Graph API Token Lifecycle A repeatable local development environment relies on consistent access token behavior. Token Expiration Constraints Development-mode apps utilize short-lived user access tokens that must be exchanged for long-lived tokens. What is the precise mechanism to ensure token validity across environment restarts without manual re-authorizat
Goal Paginate a large Mattermost dataset through the public API while avoiding the performance degradation that offset-based queries can exhibit as page numbers increase. Constraint Mattermost REST API v4 list endpoints typically expose page and per_page parameters, but offset-based pagination scans and discards earlier rows as the offset grows. The GraphQL
A low-traffic application needs to reduce database connection costs without violating response-time expectations. SQLAlchemy’s default QueuePool maintains a fixed pool_size of connections plus overflow, which can keep idle sessions open on the database side during long idle periods. NullPool is a documented alternative that opens a connection on checkout and
prisma
gatling
scala
capacitor
nuxtjs
facebook
mattermost
sqlalchemy