More teaching team only logs #43
	
		Labels
		
	
	
	
	
		No Label
		
			
	
	
	bug
		
			component
executor
		
			component
framework
		
			component
parser
		
			component
UI
		
			duplicate
		
			enhancement
		
			help wanted
		
			invalid
		
			priority
p0
		
			priority
p1
		
			priority
p2
		
			priority
p3
		
			question
		
			wontfix
		
		
	
		No Milestone
		
			
		
	
	
		
		
		
			No project
			
				
			
		
	
	
	
	
	
		No Assignees
		
			
		
	
	
	
		2 Participants
		
	
	
		
		
			Notifications
			
				
			
		
	
	
		
		
	
	
	Due Date
	No due date set.
			
				Dependencies
				
				
		
	
	
	No dependencies set.
			Reference: JOJ/JOJ3#43
			
		
	
		Loading…
	
		Reference in New Issue
	
	Block a user
	
	No description provided.
		
		Delete Branch "%!s()"
	 
	Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If we only use output from gitea actions, we can only have tiny logs for TT and students for security reasons. TT should have access to more detailed logs. One approach would be writing the debug log to mounted
/home/tt/.cache/logs, while printing the info log to stdout.what would those logs be about? run logs (for debugging purpose) or more details on students' submission?
last year on a release (or grading keyword) an issue was opened in our joj/grading repo. so we didn't need to jump to the students repo to get the details of what went wrong.
depending on teh lgs content, opening an issue could be an other option?
I only think about the log for debugging purposes. But it would be great to log more details on students' submissions.
Currently, the debug log in joj3 logs almost every variable it uses. It could be helpful at the beginning stage of JOJ3 for faster debugging.
Also, I think the debug log in teapot is useful for debugging.