ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Angular Proxy vs Spring Boot CORS In JHipster‑generated projects the Angular proxy (proxy.conf.json) forwards API calls to the Spring Boot backend during development. The backend typically registers a CORS filter that controls cross‑origin request handling. When both the proxy and filter are active, the forwarding of cookies and authorization headers is unce
The objective is to verify that a minimal PostCSS configuration can trigger a parsing error such as “Unexpected token” before any plugin that depends on production credentials is executed. Key constraints include the lack of standardized plugin execution order across PostCSS versions and the default disabling of source maps, which may obscure error locations
Goal Decide whether the production pipeline should enable Gradle's configuration cache, which serializes the task graph at configuration time for faster builds. Constraints Local runs often use a warm Gradle daemon and a populated ~/.gradle directory, while CI agents start cold with a clean GRADLE_USER_HOME . Plugins may perform unsupported work at execution
KrakenJS Alerts: Silence Duration Cannot Be Environment‑Specific The alerts package allows a silence setting that suppresses messages matching a regular expression for a fixed duration (default 10 minutes). The duration is hard‑coded in the library and cannot be overridden per deployment environment. Consequently, a single configuration file must be used acr
Goal Diagnose a firmware deployment failure that crashes with a segmentation fault, suspected to be caused by an out‑of‑bounds array access on a low‑memory target. Constraints Device flash is limited; log buffers are truncated early in the boot sequence. Only a few bytes of the crash context are captured in the serial log. The system runs an RTOS with a watc
GitBook SaaS enforces a 10‑minute hard timeout on each Git sync operation, and repositories that exceed this limit fail silently with a generic 'build failed' status in the dashboard. The legacy gitbook‑cli allowed unlimited local builds, but the modern platform runs builds in ephemeral containers with no user‑configurable timeout override, and partial sync
Context axios 1.x exposes a single timeout option that covers the entire request lifecycle—connection, response headers, and body download—with no built-in distinction between connection timeout and read timeout. The default value is 0 (infinite), which allows requests to hang indefinitely. Constraint In Node.js environments, the underlying http/https agents
I am trying to pin down the exact termination behavior of Lua's module search in package.path (assuming Lua 5.4). The manual documents that package.path holds semicolon-separated patterns with a ? placeholder replaced by the module name, and that require raises module 'foo' not found listing every attempted pattern. What it does not clearly state is whether
Goal Reduce operational cost for a low‑traffic Moleculer microservice by using the Local Transporter to avoid external broker fees while leveraging the built‑in cache mixin to cut downstream calls. Constraint / Uncertainty Increasing cache TTL improves hit rate and saves compute, but raises memory consumption; with the Local Transporter all services run in‑p
jhipster
postcss
gradle
krakenjs
embeddedc
gitbook
axios
lua
moleculer