[Hawkular-dev] strange chars in test output

John Mazzitelli mazz at redhat.com
Thu Oct 22 19:32:16 EDT 2015


Just ran a build and it looks like we are logging the contents of a zip file - which causes all kinds of bad things in the console:

FINE: Received over WebSocket: ExportJdrResponse={"fileName":"jdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3.zip","resourcePath":"/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;testing-worker-linux-docker-4d45e4b4-3236-linux-3/r;testing-worker-linux-docker-4d45e4b4-3236-linux-3~Local~~","destinationSessionId":"0I6Sw6bmxVggotD_2ti9F8WuY1R8-no6YDbDRJfn","status":"OK","message":"{\"start-time\" => \"Thu Oct 22 22:04:43 UTC 2015\",\"end-time\" => \"Thu Oct 22 22:05:46 UTC 2015\",\"report-location\" => \"/home/travis/build/hawkular/hawkular-agent/hawkular-agent-itest-parent/hawkular-agent-itest/target/hawkular-agent-itest-dist/hawkular-agent-itest-dist-0.12.0.Final-SNAPSHOT/standalone/tmp/jdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3.zip\"}"}PK��VGSjdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3/version.txt�r	�R(-ʳ�J�/.�J��M�rR����
���

It looks like we are trying to log the full JSON message that the WS receives, which is very bad because this could include a) sensitive data in the message (like passwords) and b) raw binary data

I'll look to see where this is coming from and fix it.



More information about the hawkular-dev mailing list