-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation use cases failing #541
Comments
Yeah I get some errors too after seeing some plots..
|
@apdavison : The problem is arising from checking of internet connection here: Made a minimal example here to reproduce the error: The problem only arises on the Collab, and running the same example locally runs fine (prints "B" via the except block) |
It looks as though google.com now resolves to some other IP address. I suggest replacing the
then
|
I can make that change, but I am curious as to why we see different behaviors locally and on the Collab. I see that the latter occurs as expected locally. For running this locally, I get:
whereas on the Collab, I get:
Why this difference? |
I don't know why this difference occurs, but it doesn't matter, a failure is a failure. All we are trying to discover is whether the machine is connected to the internet. |
Ok, will make those changes and deploy. It would be good to know why the Collab operates differently (would help setup better error handling if we understand). @alex4200 : let me know if you have any idea on this. |
I think the difference is coming from the remote server, it is treating the two cases differently, presumably based in differences in IP address or request headers. |
I am testing the new implementation here. It seems to work fine on the Collab (ip_address = "172.17.0.5"). Locally, on running the same code, I get my IP address as "127.0.1.1". But if we change it to (https://stackoverflow.com/a/30990617/7383605):
I get: Shall I go ahead with this? |
Both methods work for me, both at home and on the collab. But it seems the new approach is more reliable, so go for it. |
Made a new release of the Python client (0.5.28). @alex4200 : Can you test all the validation usecases again, and let me know if there are any more problems. |
Hi,
I tested the DEV versions of the notebook and all use cases seeem to work except the last one ( 'Basal Ganglia Population Morphology Validation'). I get the following error:
[cid:64ce2b9a-4dd9-43a1-966e-3d1edff765ce]
Can you check that please?
Thanks
Alex
…________________________________
From: appukuttan-shailesh <notifications@github.com>
Sent: Tuesday, April 28, 2020 10:26:46 AM
To: cnr-ibf-pa/hbp-bsp-issues
Cc: Dietz Alexander; Mention
Subject: Re: [cnr-ibf-pa/hbp-bsp-issues] Validation use cases failing (#541)
Made a new release of the Python client (0.5.28).
I have updated all the usecases to use this new version.
Also tested the Hippocampus usecase again, and it works fine.
@alex4200<https://github.com/alex4200> : Can you test all the validation usecases again, and let me know if there are any more problems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#541 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADBDXSY64OQHQVM7ZFA7WI3RO2HMNANCNFSM4MR6BFUQ>.
|
I was able to run the "Basal Ganglia Population Morphology Validation" usecase without any problems. I used the following input:
@alex4200 : Can you test again? @pedroernesto : Can you follow up on this particular use case with Alex (if required). Thanks. |
Sure, no problem |
Hi,
when I run the "Basal Ganglia Population Morphology Validation" usecase with my normal user it works.
However, when I use a different user (for the automated tests) I still get the same 403 error in the fourth code cell in section B1. Maybe there is a permission cause of the problem?
Cheers
Alex
…________________________________
From: pedroernesto <notifications@github.com>
Sent: Tuesday, April 28, 2020 4:23:30 PM
To: cnr-ibf-pa/hbp-bsp-issues
Cc: Dietz Alexander; Mention
Subject: Re: [cnr-ibf-pa/hbp-bsp-issues] Validation use cases failing (#541)
Sure, no problem
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#541 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADBDXS4DC23DVK3JZ5V4CULRO3RGDANCNFSM4MR6BFUQ>.
|
Curious.... do the other validation use cases work with this user account that you use for the automated tests? |
yes |
Ok, in that case it seems unlikely that it is a permissions issue (as all the validation use cases require similar privileges). It might be useful for @pedroernesto if you could share a snapshot of the error. Not sure he can reproduce it easily. |
Selected model: 1 Full error:
|
@apdavison : anything to do with permissions for adding new models/ instances on the KG? Also, @alex4200 : were you able to run this particular use case previously with this same user account? Also, do you run all the validation use cases to completion? Not skip any cells? |
|
Is the test user a member of the collab with which the model is associated? |
Ideally the use case should create the model with the running Collab as its host Collab. This ensures that the user is a member of the collab with which the model is associated. @pedroernesto can you confirm if this is true for this use case? To reproduce the situation, you can try to create a second HBP account for testing purposes. |
@apdavison I do not know what Collab you refer to. In the test, I simply navigate to the BSP (https://collab.humanbrainproject.eu/#/collab/8444/nav/65633), log in as alextestuser003, select the use case from the menu, create a new Collab and run the notebook in that Collab (for example: Collab TT_bdc14104-e55e-4b7f-a9ce-c6fac728fad8). |
@alex4200 This usecase has run successfully before, with me, Shailesh, Andrew, and even you as the right test-user. A problem happened only last time when you were using the wrong user. Are you sure this is not the case again? Do you remember which was missing in that kind of user and how you corrected it? |
I also see the use case "Validation Framework Demo" fail for the normal user. In the last cell before the section "7. Browse the result database", while running this notebook cell-for-cell without any change, I get the following error (done on 1.5.2020 10:50)
|
The above error is same as the original error reported in this ticket, and was fixed with release of v0.5.28 of the validation Python client. I have the feeling that the Jupyter notebook isn't being run entirely. Especially the initial cells dealing with package installations. The usecase was updated to use v0.5.28 and your above error log doesn't seem to reflect that. For example, Can you run the entire notebook manually with you regular user (and then if it works with the test user) and see if it runs to completion? |
Ah I see - you have updated your DEV notebook, but I am testing the PROD notebook. You have to let me know asap when you make a vital update to the DEV notebook, so I can test and move them to PROD! Testing DEV and then move them to prod. |
I actually did mention:
And since you mentioned afterwards that you had tested the DEV versions of the notebook, I presumed we were on the same page. |
Ah yes sorry for that. I got confused But the "Basal Ganglia Population Morphology Validation" use case still does not work, even on DEV. |
No worries. Yeah I am not sure about that particular use case. @pedroernesto might be better placed to comment on it as he owns that use case. My thougths on it are here. |
I think I was right about the source of the error: Only members of that Collab will be able to add model instances to this model, as required by cell #4 under "B.1 Instantiating the model; Running the validation tests". I believe this is the source of the problem. Alex's original user account (@adietz) is a member of this Collab, but I presume his "test_user" account is not. One solution could be to require users wishing to run this UseCase to request membership to this Collab, but I believe that makes it a bit restrictive. The other solutions might involve more changes wrt registering a new model itself (not simply a model instance) for each run. I recollect @apdavison suggesting previously that the validation UseCases should make use of existing models and not create new ones. I suppose the same holds true for model instances. But since this usecase being diffferent (population study), it potentially involves a different subset of models each time, not sure how to approach it. @pedroernesto maybe discuss this with @apdavison . |
Please can someone provide a link to an installed version of the use case in question? (in a collab I have access to), so I can quickly take a look? |
@apdavison I just shared a collab with you where I ran the use case again (and saved all the outputs): B1022 |
Thanks @alex4200 @pedroernesto I think the simplest solution would be to remove the part where the user creates a new model instance, and instead use a pre-existing model instance. For v2 of the VF, we can look into changing the permissions required in this scenario (see HumanBrainProject/hbp-validation-framework#262) |
Ok, I will do it. @alex4200 I will let you know as soon as it is ready and tested |
Hi, @pedroernesto, any update on this issue? |
I can connect to the Collab today, but it seems that problems with CSCS machines continue after the recent cyber-attack. I can not access the notebooks. I suspect that KG connection will be similarly running down. |
@pedroernesto The notebooks seem to be back running. |
With no changes and same choices, today the DEV notebook for this usecase (on 'Model validation suites' Collab) is running till the end (with my HBP account). Trying now the one on the BSP Collab. |
Same for the PROD notebook on the BSP collab (with my HBP account). Last time I even could not pass section 'A' about hard constraints, as a connection problem arose. |
@pedroernesto: I still get the 403 error when I use a non HBP test user. (DEV and PROD) When I use my normal user this use case works on PROD. But as far as I know this use case should also work for a test user. Is that correct? |
So to reproduce/test the problem, we need to use an account that is not a member of Collab #1771 (see Team list here). So the problem is more specific than the account being a non HBP test user. I hope that helps. |
@alex4200 I will add some modifications to the usecase, to make it work for other users, yes. As @apdavison suggested, I will eliminate the need to create a new model instance. |
@alex4200 it should work now. Can you try the latest DEV version, with other test users?
|
@pedroernesto Unable to test as the DEV version of this notebook seem to have vanished. Did you delete the notebook or the file and create a new one? You should not do that, as the reference ID in the usecases.json becomes invalid. What is the link to the current DEV notebook now? I will test the notebook and can fix the wrong ID in the usecases.json file... |
Oh, sorry for that. The latest DEV version is now available at https://collab.humanbrainproject.eu/#/collab/8123/nav/567961 |
@pedroernesto Thanks for the info. If you want to update something, only use THIS notebook: https://collab.humanbrainproject.eu/#/collab/8123/nav/567961 No need to recreate something, delete something etc. Just edit and save This notebook: https://collab.humanbrainproject.eu/#/collab/8123/nav/567961 Then I can easily select it in the BSP for testing! |
@appukuttan-shailesh does not recommend to work directly on the DEV versions. So, maybe the best way for me in the future, is to work in another Collab and when everything works, start editing the existing DEV version by copy+paste the new changes. |
@pedroernesto Thanks a lot, the notebook now seems to work finally! If that is the final version I will update the usecase.json tomorrow, and then implement it to the automated tests, and then merge it to PROD. |
Thanks for those good news @alex4200! "NOTE: Even if this notebook is not run inside a Collab, the following cell needs to be executed. It will identify if environment and manage accordingly. When not run inside a Collab, it will simply setup parameters required for the test, and not attempt to create new apps." I can imagine what @appukuttan-shailesh meant here, but I prefer to let him correct it. I guess this also escaped from our previous checks of that introduction in other use cases. After that, I agree to consider the resulting version as the final one. |
Corrected the typo now in all DEV notebooks. |
I believe this ticket can now be closed. Do let me know if anything is pending. |
None of the validation use cases seem to run.
Maybe there is a problem with a backend/a service
The text was updated successfully, but these errors were encountered: