advanced capstone 3.6

Community Support
1

Hi all, small issue when running ex 3.6, as you can see i have attached the failed tests below.

for the first fail, “fiauser cant run tables”, i think the reason this isnt working is because the tables havent been loaded in properly, i used the following solution for 3.1 but it doesnt seem to work, can you tell me how to adjust this loading statement?

however for the second fail i have no idea what the issue is. here is my .z.pg:

h".z.pg:{[query] api:.perm.users[.perm.users[user]?.z.u][api]; $[api~all;value query;$[api~.perm.parseQuery[query];value query;notAuthorised]]}"

it works perfectly for the other tests:

as we see here ^ there are no tables present as mentioned in my previous issue, but the appropriate access is granted.

 

all help appreciated, thank you in advance for your time 

 

kind regards

Conor

2

If you query a table you expect to have loaded in, what is returned?

Run a basic qSQL query. Is the error the table name?

Thanks, 

Leah

3

yes it is. thank you for getting back to me Leah

 

Conor

 

4

yes it is, thanks for getting back to me Leah!

Conor

 

5

Thanks Conor,

It’s looks like the load isn’t exactly erroneous, but rather might not be loading any tables.

It may be a case that the system load is happening on the current process which is then sending a null to the port. Instead, could be worth trying something like “system "l"”,getenv[…]

Just a thought! Welcome suggestions from others here too,

Leah

6

thank you Leah, tried that but unfortunately im getting an error now that just says 1.5.0 when i try that 

 

7

i got it using this command here ^, thanks for all your help leah!  

 

8

im still getting a fail on “fiauser cant run tables”;however all of the 3.6 exercises seem to be executing perfectly:

very unsure of the issue here.

 

Thanks in advance everyone,

Conor

 

 

 

9

EDIT: found the issue, i had notAuthorised rather than notAuthorized. Very silly mistake. Thank you all for your help.

10

Great spot!

s vs z  easy mistake to make.

Thanks for providing the update.