false warnings about dynamic module calls
Closed this issue · 5 comments
Please see https://gist.github.com/sstrigler/34f72edb8d1134e9de5c
Using erlang.mk and elvis.mk as of
dep_elvis_mk = git https://github.com/inaka/elvis.mk.git c3bb3f5
Downloads elvis from:
--2016-01-26 15:54:33-- https://github.com/inaka/elvis/releases/download/0.2.5/elvis
Resolving github.com (github.com)... 192.30.252.130
Connecting to github.com (github.com)|192.30.252.130|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-cloud.s3.amazonaws.com/releases/21137327/8675a422-509c-11e5-814b-e82bc6d7ecec?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160126%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160126T155616Z&X-Amz-Expires=300&X-Amz-Signature=062e5b3877d32e5783aa9ace6b2a2e0732085f6954c15703f46c82d1dcb80904&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Delvis&response-content-type=application%2Foctet-stream [following]
--2016-01-26 15:54:33-- https://github-cloud.s3.amazonaws.com/releases/21137327/8675a422-509c-11e5-814b-e82bc6d7ecec?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160126%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160126T155616Z&X-Amz-Expires=300&X-Amz-Signature=062e5b3877d32e5783aa9ace6b2a2e0732085f6954c15703f46c82d1dcb80904&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Delvis&response-content-type=application%2Foctet-stream
Resolving github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)... 54.231.98.104
Connecting to github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)|54.231.98.104|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 419149 (409K) [application/octet-stream]
Saving to: ‘/home/stefan/src/llfm/elvis’
Erlang version used is 18.1
actually we're not using the ref from above since it's broken - see other issue
@sstrigler can you check if this behaviour is still observed in the current state (1.0.0) of the library?
Unfortunately I can't since I have neither access to the project/code nor the machine where this happened anymore.
12 apr. 2016 kl. 16:53 skrev Brujo Benavides notifications@github.com:
@sstrigler can you check if this behaviour is still observed in the current state (1.0.0) of the library?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
@sstrigler ok, then… I'll close this issue and if it happens again, I'm sure someone will reopen it. :)
👍
12 apr. 2016 kl. 17:25 skrev Brujo Benavides notifications@github.com:
@sstrigler ok, then… I'll close this issue and if it happens again, I'm sure someone will reopen it. :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub