This module is responsible for providing functionality that stores the text of source files during compilation for displaying the source code that caused an exception.

configuration

Configuration

There is configuration required to set up this functionality. The options include :enable_source_code_context, :root_source_code_paths, :context_lines, :source_code_exclude_patterns, and :source_code_path_pattern. The options must be set at compile-time.

• :enable_source_code_context - when true, enables reporting source code alongside exceptions.
• :root_source_code_paths - List of paths from which to start recursively reading files from. Should usually be set to [File.cwd!()]. For umbrella applications you should list all your applications paths in this list (e.g. ["/tmp/craft-hex-3BIUoh/apps/app_1", "/tmp/craft-hex-3BIUoh/apps/app_2"].
• :context_lines - The number of lines of source code before and after the line that caused the exception to be included. Defaults to 3.
• :source_code_exclude_patterns - a list of Regex expressions used to exclude file paths that should not be stored or referenced when reporting exceptions. Defaults to [~r"/_build/", ~r"/deps/", ~r"/priv/"].
• :source_code_path_pattern - a glob that is expanded to select files from the :root_source_code_paths. Defaults to "**/*.ex".

An example configuration:

config :sentry,
  dsn: "https://public:secret@app.getsentry.com/1",
  enable_source_code_context: true,
  root_source_code_paths: [File.cwd!()],
  context_lines: 5

source-code-storage

Source code storage

The file contents are saved when Sentry is compiled, which can cause some complications. If a file is changed, and Sentry is not recompiled, it will still report old source code.

The best way to ensure source code is up to date is to recompile Sentry itself via mix deps.compile sentry --force. It's possible to create a Mix Task alias in mix.exs to do this. The example below would allow one to run mix sentry_recompile && mix compile which will force recompilation of Sentry so it has the newest source and then compile the project. The second mix compile is required due to Mix only invoking the same task once in an alias.

defp aliases do
  [sentry_recompile: ["compile", "deps.compile sentry --force"]]
end

This is an important to note especially when building for production. If your build or deployment system caches prior builds, it may not recompile Sentry and could cause issues with reported source code being out of date.

Due to Sentry reading the file system and defaulting to a recursive search of directories, it is important to check your configuration and compilation environment to avoid a folder recursion issue. Problems may be seen when deploying to the root folder, so it is best to follow the practice of compiling your application in its own folder. Modifying the source_code_path_pattern configuration option from its default is also an avenue to avoid compile problems.