Skip to content
This repository has been archived by the owner on Jan 8, 2025. It is now read-only.

Failed to send feedback #383

Open
kirs opened this issue Jul 14, 2016 · 5 comments
Open

Failed to send feedback #383

kirs opened this issue Jul 14, 2016 · 5 comments

Comments

@kirs
Copy link

kirs commented Jul 14, 2016

Thank you so much for the Aalto-C summer course.

Here is the issue I get when trying to submit the feedback:

Submitting: Module_3-03_join
Test results: 1/1 tests passed
100%
All tests passed on server!
Points permanently awarded: [M3.03]
Send feedback for Module_3-03_join? [Y/n] y
Feedback question: How difficult was this exercise? (1: trivial -- 5: very difficult)
[0-5] 3
Feedback question: Did this exercise support your learning? (1: not at all -- 5: very much)
[0-5] 5
Command failed in tmc-core, check tmc-cli.log file for more info
Failed to send feedback.

Why does it fail and where can I find tmc-cli.log?

TMC-CLI version 0.7.1

@Salmela @jclc

@Salmela
Copy link
Contributor

Salmela commented Jul 15, 2016

In linux the log file is at /home/YOUR_USERNAME/.config/tmc-cli/logs/tmc-cli.log.
In windows it's apparently in Users\User\.config\logs

I would really appreciate if you could post the log file. If the file is really long you can paste it in http://pastebin.com/ and just post a link to it.

And thanks for trying tmc-cli.

@kirs
Copy link
Author

kirs commented Jul 15, 2016

Thank you for information about the log.
Maybe it's a good idea to print full log path instead of check tmc-cli.log.

2016-07-14 19:42:26 INFO  TmcCore:109 - Creating new SendFeedback command
2016-07-14 19:42:26 INFO  HttpRequestExecutor:157 - Received http response with non 2xx response code 500 with body "org.apache.http.entity.BufferedHttpEntity@431cd9b2"
2016-07-14 19:42:26 ERROR TmcUtil:209 - Command failed in tmc-core
fi.helsinki.cs.tmc.core.exceptions.FailedHttpResponseException: Response code: 500
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.handleResponse(HttpRequestExecutor.java:163)
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.executeRequest(HttpRequestExecutor.java:142)
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.call(HttpRequestExecutor.java:84)
        at fi.helsinki.cs.tmc.core.communication.http.HttpTasks$2.call(HttpTasks.java:94)
        at fi.helsinki.cs.tmc.core.communication.http.HttpTasks$2.call(HttpTasks.java:91)
        at fi.helsinki.cs.tmc.core.communication.TmcServerCommunicationTaskFactory$7.call(TmcServerCommunicationTaskFactory.java:293)
        at fi.helsinki.cs.tmc.core.communication.TmcServerCommunicationTaskFactory$7.call(TmcServerCommunicationTaskFactory.java:289)
        at fi.helsinki.cs.tmc.core.commands.SendFeedback.call(SendFeedback.java:44)
        at fi.helsinki.cs.tmc.core.commands.SendFeedback.call(SendFeedback.java:16)
        at fi.helsinki.cs.tmc.cli.tmcstuff.TmcUtil.sendFeedback(TmcUtil.java:181)
        at fi.helsinki.cs.tmc.cli.tmcstuff.FeedbackHandler.sendFeedback(FeedbackHandler.java:38)
        at fi.helsinki.cs.tmc.cli.command.SubmitCommand.run(SubmitCommand.java:139)
        at fi.helsinki.cs.tmc.cli.command.core.AbstractCommand.execute(AbstractCommand.java:63)
        at fi.helsinki.cs.tmc.cli.Application.runCommand(Application.java:67)
        at fi.helsinki.cs.tmc.cli.Application.run(Application.java:132)
        at fi.helsinki.cs.tmc.cli.Application.main(Application.java:141)
2016-07-14 19:42:26 ERROR TmcUtil:185 - Couldn't send feedback
fi.helsinki.cs.tmc.core.exceptions.FailedHttpResponseException: Response code: 500
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.handleResponse(HttpRequestExecutor.java:163)
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.executeRequest(HttpRequestExecutor.java:142)
        at fi.helsinki.cs.tmc.core.communication.http.HttpRequestExecutor.call(HttpRequestExecutor.java:84)
        at fi.helsinki.cs.tmc.core.communication.http.HttpTasks$2.call(HttpTasks.java:94)
        at fi.helsinki.cs.tmc.core.communication.http.HttpTasks$2.call(HttpTasks.java:91)
        at fi.helsinki.cs.tmc.core.communication.TmcServerCommunicationTaskFactory$7.call(TmcServerCommunicationTaskFactory.java:293)
        at fi.helsinki.cs.tmc.core.communication.TmcServerCommunicationTaskFactory$7.call(TmcServerCommunicationTaskFactory.java:289)
        at fi.helsinki.cs.tmc.core.commands.SendFeedback.call(SendFeedback.java:44)
        at fi.helsinki.cs.tmc.core.commands.SendFeedback.call(SendFeedback.java:16)
        at fi.helsinki.cs.tmc.cli.tmcstuff.TmcUtil.sendFeedback(TmcUtil.java:181)
        at fi.helsinki.cs.tmc.cli.tmcstuff.FeedbackHandler.sendFeedback(FeedbackHandler.java:38)
        at fi.helsinki.cs.tmc.cli.command.SubmitCommand.run(SubmitCommand.java:139)
        at fi.helsinki.cs.tmc.cli.command.core.AbstractCommand.execute(AbstractCommand.java:63)
        at fi.helsinki.cs.tmc.cli.Application.runCommand(Application.java:67)
        at fi.helsinki.cs.tmc.cli.Application.run(Application.java:132)
        at fi.helsinki.cs.tmc.cli.Application.main(Application.java:141)

@Salmela
Copy link
Contributor

Salmela commented Jul 16, 2016

I have never seen that error code and the problem doesn't seem to be in tmc-cli, but in tmc-server.

I made new issue about the log file path at #384.

@jamox will propably look at the server issue at some point.

@jamo
Copy link
Member

jamo commented Jul 16, 2016

Thanks for reporting this, I'll check the logs in a few days, whenever I have proper internet access...

@kirs
Copy link
Author

kirs commented Jul 16, 2016

Kiitos paljon!

On Jul 16, 2016 12:11 PM, "Jarmo Isotalo" [email protected] wrote:

Thanks for reporting this, I'll check the logs in a few days, whenever I
have proper internet access...


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#383 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf3q0g0A92UiCUJa29bjwwk5kks6f7Mks5qWQKfgaJpZM4JM9Gc
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants