{"action":"created","issue":{"url":"https://api.github.com/repos/chapel-lang/chapel/issues/10342","repository_url":"https://api.github.com/repos/chapel-lang/chapel","labels_url":"https://api.github.com/repos/chapel-lang/chapel/issues/10342/labels{/name}","comments_url":"https://api.github.com/repos/chapel-lang/chapel/issues/10342/comments","events_url":"https://api.github.com/repos/chapel-lang/chapel/issues/10342/events","html_url":"https://github.com/chapel-lang/chapel/issues/10342","id":341265381,"node_id":"MDU6SXNzdWUzNDEyNjUzODE=","number":10342,"title":"Feature Request: Printing stack trace of tracked communications via CommDiagnostics","user":{"login":"LouisJenkinsCS","id":4269990,"node_id":"MDQ6VXNlcjQyNjk5OTA=","avatar_url":"https://avatars2.githubusercontent.com/u/4269990?v=4","gravatar_id":"","url":"https://api.github.com/users/LouisJenkinsCS","html_url":"https://github.com/LouisJenkinsCS","followers_url":"https://api.github.com/users/LouisJenkinsCS/followers","following_url":"https://api.github.com/users/LouisJenkinsCS/following{/other_user}","gists_url":"https://api.github.com/users/LouisJenkinsCS/gists{/gist_id}","starred_url":"https://api.github.com/users/LouisJenkinsCS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LouisJenkinsCS/subscriptions","organizations_url":"https://api.github.com/users/LouisJenkinsCS/orgs","repos_url":"https://api.github.com/users/LouisJenkinsCS/repos","events_url":"https://api.github.com/users/LouisJenkinsCS/events{/privacy}","received_events_url":"https://api.github.com/users/LouisJenkinsCS/received_events","type":"User","site_admin":false},"labels":[{"id":496591534,"node_id":"MDU6TGFiZWw0OTY1OTE1MzQ=","url":"https://api.github.com/repos/chapel-lang/chapel/labels/area:%20Modules","name":"area: Modules","color":"d4c5f9","default":false},{"id":520459015,"node_id":"MDU6TGFiZWw1MjA0NTkwMTU=","url":"https://api.github.com/repos/chapel-lang/chapel/labels/user%20issue","name":"user issue","color":"fef2c0","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-07-14T20:26:25Z","updated_at":"2018-07-18T21:15:24Z","closed_at":null,"author_association":"MEMBER","body":"From my experience using `CommDiagnostics`, it is an extremely helpful, even necessary tool, for profiling performance bottlenecks, but sometimes I wish for more verbosity. For example, if an internal module is racking up all of the communication, I want to know why and where it is being called and figure out whether or not I can eliminate that extra bit of communication. One thing that I would like to see is a small condensed stack-trace that shows just the fie name and line number of the calls leading up to that point. Maybe adding a new argument to `startVerboseComms`, like `startVerboseComms(printStackTrace=false)`? Maybe it could be a compile-time or runtime argument?"},"comment":{"url":"https://api.github.com/repos/chapel-lang/chapel/issues/comments/406076808","html_url":"https://github.com/chapel-lang/chapel/issues/10342#issuecomment-406076808","issue_url":"https://api.github.com/repos/chapel-lang/chapel/issues/10342","id":406076808,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNjA3NjgwOA==","user":{"login":"bradcray","id":7536222,"node_id":"MDQ6VXNlcjc1MzYyMjI=","avatar_url":"https://avatars0.githubusercontent.com/u/7536222?v=4","gravatar_id":"","url":"https://api.github.com/users/bradcray","html_url":"https://github.com/bradcray","followers_url":"https://api.github.com/users/bradcray/followers","following_url":"https://api.github.com/users/bradcray/following{/other_user}","gists_url":"https://api.github.com/users/bradcray/gists{/gist_id}","starred_url":"https://api.github.com/users/bradcray/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bradcray/subscriptions","organizations_url":"https://api.github.com/users/bradcray/orgs","repos_url":"https://api.github.com/users/bradcray/repos","events_url":"https://api.github.com/users/bradcray/events{/privacy}","received_events_url":"https://api.github.com/users/bradcray/received_events","type":"User","site_admin":false},"created_at":"2018-07-18T21:15:24Z","updated_at":"2018-07-18T21:15:24Z","author_association":"MEMBER","body":"I'm not all that familiar with the chplvis implementation, but my suspicion is that it doesn't have the ability to track callstacks at present."}}
{"actor":{"display_login":"bradcray"}}