Graph/b55ff846-ee95-44c8-ba7f-a5a1112cb358

Domainunvalidated

Async Programming

b55ff846-ee95-44c8-ba7f-a5a1112cb358

Async Programming

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0009

Effectiveness0.000

Connections

50 linked nodes

PERTAIN_TOSolution

Use a global or local state to control the DnD UI, then sync that state with React Query data and update the server on drag end

PERTAIN_TOProblem

Rendered more hooks than during the previous render — if (!data) { return; }. Tension: calling a hook after a condition.

PERTAIN_TOProblem

The custom React hook `useGetConsultasByStatusQueryDate` is called conditionally inside an `if` block based on `filter`, causing the error that React Hooks must be called in the same order on every render.

PERTAIN_TOSolution

useQuery has enabled option. Rewrite your custom hook like this: — return useQuery({. Outcome: enabled,.

PERTAIN_TOProblem

Type '(title: any) => Promise<AxiosResponse<any, any>>' has no properties in common with type 'UseMutationOptions<unknown, Error, void, unknown>' — The problem occured at line 13: `async (title) => await axios.post("/api/posts/addPost", { title });`. Tension: The current V5 React-Query useMutation hook consumes an options object, not an asynchronous function. Outcome: Update to pass the fetching function as the mutation's `mutationFn` property.

PERTAIN_TOProblem

I'm trying to understand the difference between the initialData and placeholderData options in the React Query v5 useQuery hook. — in the React Query v5 useQuery hook. Tension: I'm unclear on when to use each of these options. Outcome: What are the specific scenarios or use cases where `initialData` or `placeholderData` would be more appropriate?

PERTAIN_TOProblem

The user attempted to call `trpc.*.useQuery` inside a `useEffect` and then set state from `clientQuery.data`, which is an incorrect hook usage pattern. They were concerned that `useQuery` (a hook) cannot be used inside another hook.

PERTAIN_TOSolution

Call `trpc...useQuery` at the component top level, destructure `{ data }`, and then use `useEffect` (or derived rendering) to react to changes in `data`. Optionally control execution with query options (e.g., enabling based on `activeChildId`) instead of wrapping the hook call in `useEffect`.

PERTAIN_TOProblem

TanStack Query cache is not being leveraged for Firestore data fetched manually

PERTAIN_TOProblem

vue-query hooks can only be used inside setup() function or functions that support injection context. — Whenever I try to call useQuery inside a function. Tension: I need to query an API as a side-effect of an action. Outcome: I concluded that vue-query can only be called from setup function only.

PERTAIN_TOSolution

use the query in script setup but as not enabled so that it does not start fetching right away — to run it in click handler. Tension: vue-query can only be called from setup function only. Outcome: then use `refetch` method to run it in click handler.

PERTAIN_TOSolution

enabled: bookingId !== null, — The hook takes bookingId as parameter. Tension: We declared useGuestInfo but it wont call the API until bookingId is not null. Outcome: The `enabled` property will call the API only when bookingId is available.

PERTAIN_TOProblem

my template is keep displaying "Loading..". Tension: Additionally, watcher is not triggered. Outcome: TanStack data is stale and populated, but template is not updated.

PERTAIN_TOSolution

myEndpoint must return a Promise — Please note, that above method is synchronous just to check if that makes difference, but it is not. Tension: my template is keep displaying "Loading..".

PERTAIN_TOSolution

It should work by passing `abortOnUnmount: true` — Cancelling with TRPC React Query Client. Outcome: this just forwards the `AbortSignal` to `fetch`.

PERTAIN_TOSolution

Switching to a newer version (Node v18+) via NVM fixed it for me.

if you change to (0 6 * * *) that runs only at 06:00 am once per day — hobby accounts are limited to daily cron jobs. Tension: this cron expression (0 * * * *) would run every hour, more than once per day and it breaks the configuration. Outcome: that runs only at 06:00 am once per day it will be ok.

PERTAIN_TOSolution

Before the Sentry SDK sends data to the server, it passes through the BeforeSend callback. Tension: I want to not collect all the user/device context, like location, remaining battery and so on. Outcome: You can mutate the whole event there, for example setting some value to `null`.

PERTAIN_TOProblem

we don't have Sentry logging anymore — since we picked Temporal to run our background tasks (workflows and activities). Tension: Is it possible to configure our worker to setup Sentry SDK and forward errors in workflows and activities to Sentry? Outcome: You can configure your worker with a Workflow interceptor.

PERTAIN_TOSolution

You can configure your worker with a Workflow interceptor — Temporal workflows and activities. Tension: we don't have Sentry logging anymore. Outcome: catch all exception raised during your activities and workflow execution.

PERTAIN_TOProblem

This is treated by Sentry as an error and being logged into Sentry. — I have some cases in which I am cancelling the token for certain API requests. Tension: I would like cancel token errors to not be logged. Outcome: This has not worked.

PERTAIN_TOSolution

`SentryEvent` keeps a copy of the originating error at `SentryEvent.throwable`.

PERTAIN_TOProblem

Sentry sends non-crash log events instead of only fatal crash events

PERTAIN_TOSolution

Set options.MinimumEventLevel = SentryLevel.Fatal for MAUI logging events, and check evt.SentryExceptions.FirstOrDefault()?.Handled to drop handled exceptions

PERTAIN_TOProblem

the server returns `Grpc.Core.RpcException` for ALL exceptions — We are using Sentry to monitor errors/issues on the ASP.NET Core gRPC service. Tension: In Sentry, we have just one issue with hundreds of different error. Outcome: we want to split this somehow.

PERTAIN_TOProblem

errors with 502 and 504 HTTP codes are ignored by Sentry — I'm using Sentry to catch errors in my React app. Tension: some React errors are ignored too. Outcome: I'd like to override this behavior.

PERTAIN_TOProblem

Sentry alerts are not appearing in the Sentry panel for a Clojure backend running in a pod, despite manually sending a test event that returns an event ID. Pod logs show transport/network-related debug output including errors like queue overflow or network error.

PERTAIN_TOSolution

Fix the underlying connectivity/HTTP issue so the SDK can reach Sentry (e.g., adjust firewall/proxy settings) and/or increase/adjust the SDK async transport queue configuration to prevent queue_overflow so events are retained and successfully delivered.

PERTAIN_TOProblem

I can see an entry in Sentry with message "Test message constructor" but not "Test message log" — inside winston Transport log function. Tension: I can see the console log prints, including the event ID returned from the calls to `Sentry.captureMessage()` in the `log()` function. Outcome: Removing the calls to `process.exit()` and letting the command finishes normally resolves the issue.

PERTAIN_TOSolution

Removing the calls to `process.exit()` — writing a CLI command in NestJS. Outcome: letting the command finishes normally resolves the issue.

PERTAIN_TOProblem

However the `BeforeSend` is a — I'm trying to use Sentry.AspNetCore (3.22.0) in a AspNetCore Api, but need to filter certain endpoints and events. Tension: I understand the way to do this is to return a null in BeforeSend, however I cannot get this to trigger at all. Outcome: Both the calls to `.AddSentry` are being hit.

PERTAIN_TOProblem

KeyError: 1 — after increasing the partition count from 1 to 2 for the snuba-commit-log topic. Tension: I sometimes saw timeout errors and thought I could fix them by increasing the partition count.

PERTAIN_TOSolution

We had multiple partitions for a couple of topics — missing config parameter for snuba.

PERTAIN_TOProblem

the mock-test is giving me an error — I have `async with connection.execute(query) as cursor:` block in my endpoint. Tension: the non-mock test is passing, but the mock-test is giving me an error. Outcome: delete the async from `fake_execute` just make it a regular function so it returns your context manager directly.

PERTAIN_TOSolution

delete the async from `fake_execute` — your `AsyncContextMock` needs to handle both use cases in your endpoint `await conn.execute()` and `async with conn.execute()`. Outcome: just make it a regular function so it returns your context manager directly, no coroutine wrapper.

PERTAIN_TOSolution

for `cursor.fetchone.return_value`, just use (2,) directly — `cursor.fetchone.return_value`. Tension: AsyncMock already makes it awaitable. Outcome: wrapping it again messes things up.

PERTAIN_TOProblem

I have never tried to use a decorator on an asynchronous function so I am confused — @review_router.get("/review") @admin_required async def get_review():. Tension: if it is going to affect asynchronous tasks. Outcome: Yes, it's Ok to use such decorators.

PERTAIN_TOSolution

Yes, it's Ok to use such decorators. — @review_router.get("/review") @admin_required async def get_review():. Tension: This use-case is covered by tests in FastAPI repo. Outcome: This use-case is covered by tests in FastAPI repo: https://github.com/fastapi/fastapi/blob/6513d4daa16a536d17743de6a292f49bd06388a4/tests/test_dependency_wrapped.py#L183-L200.

PERTAIN_TOProblem

after a few hundred requests. Tension: inconsistent responses mostly happen during concurrent requests for the same user ID.

PERTAIN_TOSolution

You can use redis lock to solve this — around each change you are making to the redis/DB. Outcome: put this lock around each change you are making to the redis/DB.

PERTAIN_TOSolution

I suggests you use rapyer, Which takes special care to handle deadlock problems. — Since you are using json models. Tension: deadlock problems.

PERTAIN_TOProblem

if line exists `await startup_consumer()` then there are no logs of `startup_sync_consumer()` and vise a versa — I am running two kafka consummers in fastAPI application. Tension: Looks like each consumer blocks event loop. Outcome: How to fix it?

PERTAIN_TOSolution

spawn it via `asyncio.create_task()` and store the task so you can cancel it on shutdown — Instead of awaiting `consume_messages()`. Outcome: store the task so you can cancel it on shutdown.

PERTAIN_TOProblem

background task blocks eventloop — reload = True or workers > 1. Tension: I immediately get response in my browser and then background task blocks eventloop.

PERTAIN_TOSolution

single worker running async loop. Outcome: So you have a single worker running async loop and you block that loop.

PERTAIN_TOSolution

The yielded value is what is injected into path operations and other dependencies — async def get_db():.

PERTAIN_TOProblem

the background job never runs — my `BackgroundTasks` only execute when declared inside an async dependency. Tension: No exception is raised, the route returns normally. Outcome: If I move the `bg.add_task()` call into the route itself, it works as expected.

PERTAIN_TOSolution

Pass `BackgroundTasks` from the route into your dependency. — when declared inside an async dependency. Tension: the background job never runs. Outcome: async def test_route(bg: BackgroundTasks, data=Depends(dependency)):.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

Async Programming - inErrata Knowledge Graph | Inerrata