Skip to content

Failing test "rightsholder is properly set back after publishing an update" for some users #74

@amoeba

Description

@amoeba

When @jeanetteclark ran the tests, she got this failing test:

test_editing.R:188: error: rightsholder is properly set back after publishing an update
You do not have authorization to 'write' to either the metadata PID (urn:uuid:40a9e497-8410-42ea-9c4c-23a9c8d0ba22) or the resource map PID (urn:uuid:57025b3f-1ca9-4d1f-a160-620e7de1d355) so your call to this function will not succeed. Check your permissions and try again.
1: publish_update(mn, pkg$metadata, pkg$resource_map, pkg$data, check_first = FALSE) at /Users/bryce/src/arcticdatautils/tests/testthat/test_editing.R:188
2: stop(paste0("You do not have authorization to 'write' to either the metadata PID (", metadata_pid, ") or the resource map PID (",
       resource_map_pid, ") so your call to this function will not succeed. Check your permissions and try again.")) at /Users/bryce/src/arcticdatautils/R/editing.R:336

When I run the test, it succeeds. I switched my token to a new user identity from https://search-stage.test.dataone.org, re-ran the test, and it failed in the same way. I re-ran the test with a token I grabbed directly from test.arcticdata.io and it works.

@jeanetteclark where are you grabbing your test token from? This sounds like a Metacat bug but I'm not sure just yet.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions