search

RoboTutorLLC / RoboTutor_2020

Other
3 stars 1 forks source link

2023 02 01 bhargav add stack trace #127

Closed bhargavmyadam closed 1 year ago

bhargavmyadam commented 1 year ago

1)Dumped stack trace in existing postError function previously just for stack-tracing CRASH. 2) Implemented error log creation similar to crash logs for each ERROR. All the ERROR_log.txt files are being stored in Robotutor_ERROR directory. --> don't want to have to change DriveSync FOLDER PAIRS on tablets. Options: a. Dump directly to same folder as crash_logs. b. Make robotutor_error folder under crash_logs. c. Make robotutor_error folder under tablet top-level RoboTutor folder where logs go and get uploaded. --> DO THIS

ERROR_LOG filepath and filename format: path: [device storage, e.g. /storage/emulated/0]/RoboTutor/RoboTutor_ERROR/ filename: ERROR_RoboTutor_version_device ID session sequence number session start timeerror time"sanitized" error message

"sanitize" = start...end or #hash

  java.lang.ClassCastException: cmu.xprize.robotutor.tutorengine.widgets.core.TStudentProfileModal cannot be cast to cmu.xprize.robotutor.tutorengine.ITutorObject

--------- Stack trace ---------

cmu.xprize.robotutor.tutorengine.CTutor.mapChildren(CTutor.java:740)
cmu.xprize.robotutor.tutorengine.CTutor.automateScene(CTutor.java:707)
cmu.xprize.robotutor.tutorengine.CTutor.instantiateScene(CTutor.java:682)
cmu.xprize.robotutor.tutorengine.CTutorGraph.gotoNextScene(CTutorGraph.java:448)
cmu.xprize.robotutor.tutorengine.CTutorGraph$Queue.run(CTutorGraph.java:203)
android.os.Handler.handleCallback(Handler.java:938)
android.os.Handler.dispatchMessage(Handler.java:99)
android.os.Looper.loop(Looper.java:223)
android.app.ActivityThread.main(ActivityThread.java:7656)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

--------- Cause ---------

JackMostow commented 1 year ago

@bhargavmyadam and everyone I cc'd in case this problem affected you:

The build failed before because travis started charging for builds for private repos, so I made robotutor_2020 public -- which required first making https://github.com/judithodili/RoboTutor_Help_Intervention and https://github.com/kevindeland/RoboTutor public.
The reason is that a repo can't be made public if it’s forked from a private repository. https://github.com/RoboTutorLLC/RoboTutor_2020 was forked from https://github.com/judithodili/RoboTutor_Help_Intervention, which was private and forked from https://github.com/kevindeland/RoboTutor, which was also private. (For details, see https://github.com/orgs/community/discussions/22624). Kevin and Judith kindly agreed to make those repos public.

In case you’re wondering why now, it’s because we build our apks using https://app.travis-ci.com/Builds, which just announced that “Builds have been temporarily disabled for private repositories due to a negative credit balance.” I hope that making our repo public solved the problem.

@bhargavmyadam - Please try the travis build again to confirm that it works now, and let us know either way. Thanks! - Jack

madeleinvillegas commented 1 year ago

@JackMostow Travis is still not working for the same reason (negative credit balance) even if the repo is already public. I think the credit limit is present regardless of whether he repo is public or private.

welcome[bot] commented 1 year ago

Congrats on merging your first pull request! 🎉 All the best for your amazing open source journey ahead 🚀.

JackMostow commented 1 year ago

Travis builds are working again; did a dummy commit to trigger this one.