Because, of course we do…
— Mike Jones (@mkdjns) July 31, 2017
via Twitter
It's a thing. Sometimes there's stuff.
Because, of course we do…
— Mike Jones (@mkdjns) July 31, 2017
via Twitter
Watched on Monday July 24, 2017.
— via Letterboxd
Not that there won't be a crapload of other male characters on the show…
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
Sandboxes have been around for a while. Tests pass in brand new sandbox, created today. All failures happen on same instance. maybe a bug!
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
No differences in profiles/roles that I can detect. We don't use roles, and the Profiles match across orgs.
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
Checked that. Failures started recently, with no changes to impacted code or profiles/sharing.
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
Have confirmed profile exists & code works when run "for real" in the orgs where tests fail. Profile Id is queried when test user is built.
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
Profile created in prod, sandboxes created after. Test creates and runs as user with profile, fails updating *real* user with same profile.
— Mike Jones (@mkdjns) July 21, 2017
via Twitter
Failure reason is 'INSUFFICIENT_ACCESS_OR_READONLY' or 'INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY' #askforce
— Mike Jones (@mkdjns) July 20, 2017
via Twitter
Unit test fails in two sandboxes, passes in third and production. Tested code updates User object. Any ideas on troubleshooting? #askforce
— Mike Jones (@mkdjns) July 20, 2017
via Twitter
Watched on Sunday July 16, 2017.
— via Letterboxd
Not so much, I guess…
— Mike Jones (@mkdjns) July 7, 2017
via Twitter
@evernotehelps I’m having trouble with Evernote points and an expired iTunes subscription. Can you help?
— Mike Jones (@mkdjns) July 6, 2017
via Twitter