@herbert24 Seems members couldn’t make it for the call except you and @jennifer…So on my side I have no blockers,dev environment is running, started working on a ticket… I hope others can give us an update aswell @jwnasambu @tendomart @sharif
1 Like
Well am also right way to get started work on tickets, my dev environment is running, sorry for missing the pm call tiday
1 Like
Sorry friends , am afraid cannot make it on Fridays .I thought we would have the sessions on thursday.
@tendomart point noted,you can go on and post your progress on this thread as @reagan did
@sharif and @reagan hope you guys before picking on the tickets you have done some good reading of the react.This will fasten our process
1 Like
Surely @herbert24…that is quite essential including testing.
1 Like
Yes @herbert24, since every thing is working very fine, then we wont hesitate, @reagan has also started some good work, Unfortunately or fortunately , @jwnasambu "s instance still seems to keep failing i dont know if she had been unblocked.@jwnasambu any progress so fur
It is still failing terribly and I am changing to a new OS tonight due to EOL of windows 7 which I suspect may be having backward compatibility issue on node.js.
2 Likes
Hi guys today since we have a few things to discuss,we shall not have the OCL call and let me just put them straight here:-
1)I have been trying to reach out to lincon on how far he has gone with writing the tests,he has not yet responded but i expect him to respond on this thread so as we get a way forward. 2) we need to get tickets to be worked upon as soon as lincon gets done with writing the tests for the new code base.We do have a gap in the process since we donot have the product owners currently available ie @ball and @jecihjoy.
Currently,we are only waiting for lincon to update us on how the testing has gone and as soon as that is done,we shall then be going in to create the tickets with help of the product owners.Incase of any questions kindly let me know on this thread!
@herbert24 @mozzy @jennifer @jecihjoy @jdick @kuang @whiscard @dkayiwa @darius @akanter @burke @jwnasambu @irenyak1 @tendomart @mseaton @mogoodrich @karuhanga @paynejd @ibacher
3 Likes
Thanks for the updates.
as we get ready for the Thursday’s on boarding session,i would like to hear from those under the on-boarding session,kindly drop here some information about your progress with the react tutorials. in case of any blockers,it is also important to drop them here.For the Thursday session,you are kindly requested to prepare some demo on the works that you have covered so that we have them presented during that day. thanks cc @jwnasambu @sharif @tendomart @irenyak1 @reagan @dkayiwa @paynejd @jennifer
@dkayiwa am still running in the same error and this is the error log https://pastebin.com/m9AFsjix
@jwnasambu is JULIE an admin account? Or some other type?
Its an admin account
Try delete the node_modules folder in C:\Users\JULIE\OpenMRS-Tickets\openmrs-ocl-client
Then run this command: npm cache clean --force
Finally run: npm install again.
I have followed the steps closely and this is the error log I have got https://pastebin.com/5UmJGuRH
Looks like a network connection problem. Can you try again?
You are right my network connection is not stable. I followed the same procedure and reproduced the same error log.
Can you share the new log?