You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some CodingTracker sequences need to get post-processed to be parsed and replayed correctly. We store the fixed CodingTracker sequences in a Subversion repository different from our main data repository. If a user updates his or her original CodingTracker sequence, the fixed CodingTracker sequence becomes outdated, because it no longer contains the new changes. I suggest that we write a script to detect the fixed CodingTracker sequences that have become outdated.
The text was updated successfully, but these errors were encountered:
Some CodingTracker sequences need to get post-processed to be parsed and replayed correctly. We store the fixed CodingTracker sequences in a Subversion repository different from our main data repository. If a user updates his or her original CodingTracker sequence, the fixed CodingTracker sequence becomes outdated, because it no longer contains the new changes. I suggest that we write a script to detect the fixed CodingTracker sequences that have become outdated.
The text was updated successfully, but these errors were encountered: