Jacob Fugal d9c6e2a0cd clarify Slug vs. UUID and fix event stream ... refs CNVS-13987 what was called CanvasUuid was *not* generating UUIDs. it was generating slugs. by default, its generate method only creates 4 character slugs. these should obviously not be used as UUIDs. the misnomer already caused a bug in EventStream where it used these slugs as UUIDs, causing collisions. to fix: (1) rename canvas_uuid gem to canvas_slug, and rename it's primary class CanvasUuid to CanvasSlug (2) create new canvas_uuid gem, with class CanvasUUID, extracted from lib/uuid_singleton for actual UUID generation (3) fix event stream use CanvasUUID, rather than following the rename of CanvasUuid to CanvasSlug test-plan: - have cassandra set up for audit logs - create an audit log entry (e.g. change a grade) - look at the generated audit log entry's id field; it should be a UUID value, not a 4 character slug Change-Id: I19758fff4433cd6cb2e21219217dced19ee05c5a Reviewed-on: https://gerrit.instructure.com/37506 Reviewed-by: Rob Orton <rob@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: August Thornton <august@instructure.com> QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Brian Palmer <brianp@instructure.com>		2014-07-11 16:58:42 +00:00
..
lib	clarify Slug vs. UUID and fix event stream	2014-07-11 16:58:42 +00:00
Gemfile	clarify Slug vs. UUID and fix event stream	2014-07-11 16:58:42 +00:00
Rakefile	clarify Slug vs. UUID and fix event stream	2014-07-11 16:58:42 +00:00
canvas_slug.gemspec	clarify Slug vs. UUID and fix event stream	2014-07-11 16:58:42 +00:00