Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Tagged a scenario @user:admin and the run fails before a browser even opens:
✖ USER_POOL_EXHAUSTED: No users with role "admin" in dataset "users" (env staging).
hint: Roles present: standard, locked_out.There is definitely an admin in the CSV, I am looking at it. Roles in the file are standard, locked_out and admin. Where does "Roles present: standard, locked_out" come from? Those are two of my three.
Accepted answer
The hint lists the roles in the rows that were actually loaded, so it is telling you the file you are looking at is not the file that was read.
data/<env>/<name>.csv wins over data/common/<name>.csv, and they do not merge — the environment file replaces the common one wholesale. You almost certainly have a data/staging/users.csv with two rows in it, and the admin lives only in data/common/users.csv.
Add the admin row to the staging file, or delete the staging file if it was not doing anything the common one does not.
Two related things while you are in there:
admin has to be listed under tags.roles in the project yaml or lint rejects the tag before the run starts.@user:<role> leases before the browser context is created, which is why this fails ahead of the first step rather than inside it. That is deliberate: the scenario starts already logged in.The quickest way to see which file won is to preview both and compare:
sdods data preview projects/demo-shop/data/staging/users.csvWe got bitten by the same thing after somebody added a staging file to pin two accounts and quietly dropped the other four.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.