Jacob Martin JVMartin

Sentry is awesome, but their NodeJS Platform is slightly less great. It's basically entirely synchronous, so if you have a lot of async operations going on things like breadcrumbs and other context information will all get mixed up together.

I put this gist together to share with other people how I worked around this problem in our code base. It's not a perfect solution, but it works pretty well.

How it works

The way this works is that Sentry has a global store (global.__SENTRY__) that includes a hub property that stores the current hub. The hub has a stack of scopes that are the things you interact with when using things like Sentry.withScope and Sentry.configureScope. What I'm doing here is replacing that hub property with a getter that return an async context local hub instead of a global one. It does this by using the Node native AsyncLocalStorage mo

	/**
	* Recursive shadowcasting algorithm.
	* This algorithm creates a field of view centered around (x, y).
	* Opaque tiles are treated as if they have beveled edges.
	* Transparent tiles are visible only if their center is visible, so the
	* algorithm is symmetric.
	* @param cx - x coordinate of center
	* @param cy - y coordinate of center
	* @param transparent - function that takes (x, y) as arguments and returns the transparency of that tile
	* @param reveal - callback function that reveals the tile at (x, y)

	<?php
	$fileName = $_FILES['afile']['name'];
	$fileType = $_FILES['afile']['type'];
	$fileContent = file_get_contents($_FILES['afile']['tmp_name']);
	$dataUrl = 'data:' . $fileType . ';base64,' . base64_encode($fileContent);

	$json = json_encode(array(
	'name' => $fileName,
	'type' => $fileType,
	'dataUrl' => $dataUrl,