Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

getsentry / sentry-elixir Public

Notifications You must be signed in to change notification settings
Fork 189
Star 631

Code
Issues 9
Pull requests 8
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Continuous Integration

Remove --halt-exit-status option when running dialyzer on CI #817

Sign in to view logs

Sign in to view logs

Remove --halt-exit-status option when running dialyzer on CI

Remove --halt-exit-status option when running dialyzer on CI #817

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

2 warnings

62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

This job succeeded

Loading

Re-running jobs...

You can’t perform that action at this time.