Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Binary release marked as unsafe in Chrome #1

Open
fmoessbauer opened this issue Mar 29, 2019 · 0 comments
Open

Binary release marked as unsafe in Chrome #1

fmoessbauer opened this issue Mar 29, 2019 · 0 comments
Labels
known-limitation This problem is known and will unlikely be fixed support related to build/release process

Comments

@fmoessbauer
Copy link
Member

Chrome warns the user that the drace binary release is a "unsafe" download. We should find a way to avoid this message if possible. Otherwise we should document it in the readme.

image

We further should make our build process fully transparent and repeatable which implies to generate a manifest with used VS version + compiler + OS version and checksums.
@fmoessbauer fmoessbauer added the support related to build/release process label Mar 29, 2019
fmoessbauer pushed a commit that referenced this issue Jul 10, 2019
@philip-harr
feat: added black/whitelisting, labeling of error boxes, SC box @ same
983ad0d 
height, file @ correct line, line highlighting, grey shading

feat: added black-/whitelisting functionality (issue #4)
feat: added object and function names in error boxes (issue #2)
feat: added source boxes are now at the same vertical position (issue #3)
feat: file is displayed at the correct source line (issue #1)
feat: affected source line is highlighted
feat: object without source file are grey shaded
refactor: minor design changes
@fmoessbauer fmoessbauer added the known-limitation This problem is known and will unlikely be fixed label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
known-limitation This problem is known and will unlikely be fixed support related to build/release process
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fmoessbauer