finally ! :)

YAY now can we have a update on the unscreened bug reports per category.

Even a please resubmit all old bug reports under this new system would work. Stating that the bug hunters work backwords new to old would also be enough to clear up peoples frustration with the bug reporting que. Full helpful bug reports beats incomplete bug reports everytime.

Unfortunately we have a quite long queue of unfiltered bug-reports at the moment. These unfiltered bug-reports often consist of "tricky cases", which are either difficult to verify or which lack needed information.

All new bug-reports are at least being checked within 1-2 days and many of them are also being forwarded to our internal defect system at this time or they are being sent back to the reporter for more information. At the moment we are giving bug-reports from Singularity a higher priority compared to old bug-reports or to bug-reports from TQ.

This new ingame bug reporting tool will hopefully also result in a higher quality of the bug-reports, as it includes information about the computer and some logs automatically. This should result in less bug-reports being sent back to the reporter for more information and hopefully this will also help us to reduce this long queue. You, as bug-reporter, can also help with this by making sure to write high-quality bug-reports: A clear title (makes it much easier to filter through bug-reports), a good description, and useful reproduction steps are of highest value. Check http://wiki.eveonline.com/en/wiki/Bug_reporting for more information on this (not yet updated for the new bug-reporting tool).

What about hiding something like this on TQ as well? Hide it behind an overly complex shortcut like the monitor window (ctrl-shift-alt-turn three times counter clockwise while chanting bloody marry-sacrifice a goat-M) so it doesn't end up being abused.

Actually that brings up another interesting question... what is the maximum capacity for the bug hunters? As in, how many reports can they handle before things start falling apart?

Running short on stuff to rant about?

Sweet Jesus. This is awesome.

Ninja edit: If we could be able to attach multiple screenshots, that would be superb.

Just added that last night.
Should be in the next sisi update, along with cropping and some other annotation tools.

What about my cant send a report bug
Do you have a twitter acount?

getting this error while stuck loading CQ UI responsive.

Exception #9

For the error on login, the logic is pretty simple and the only reason you should be getting that is if your username, password or character name don't match your Tranquility credentials (not necessarily the same as your Singularity ones).

There might be a bug in the bug data base with not being able to save a bug if you have never logged in to the data base before. will check that out once i bet back in to the situation i am trying to bug report.

Sending a bug report also puts the client into a unresposive state might want to add that as a warning in the bug reporting window. Sure takes a while

The other issue is the charcter i am sending the bug report from is not on TQ as it is a bug testing alt. The check might be checking the wrong data base. Will this get changed. Alot of the NPE testing is faster on testing alts.

The ~10sec stall when the client is negotiating with the SSL library is something that we're looking into.
The bug will need to be posted from a user/character that exists on Tranquility. The bugs website is not hooked into the Singularity database at all. You can still test using any character, but when you submit your bug report enter your TQ information in the dialog.

Server error in sending bug-report to the bug-reporting server. Response is



500 - Internal server error.

[FORUM POST CANNOT CONTAIN HTML TEXT]

Server Error




500 - Internal server error.


There is a problem with the resource you are looking for, and it cannot be displayed.

will this tool ever be avaible on TQ?

Many times during my play i ancouter some random bugs but im never bothered to post them, with tool ingame i might

Awesome screenshot tool. So cool - I can't help but want more :)

Proportional sizing buttons 50% - 100% - 200%
Useful for small crops that look bad when scaled to fit the window, and 200% will be popular with folks that want to place arrows precisely.

Arrows could be auto-numbered when placed, (as an option?) to help with notes in the bug.

I can't report any bug with this ingame tool, i write the TQ passwd, send the report and after the sending process i obtain always this error message:

An unknown error occurred when sending bug report.
Details:
[Errno 10054] Se ha forzado la interrupci+¦n de una conexi+¦n existente por el host remoto: 'recv operation failed'

Bug reporting tool without ability to attach the log server file???

Such a great tool and you make me use the old bug reporting method

Logs are attached automatically without needing to run logserver.

Now, Logserver does log more than is available in the in-memory logging (as we call it) but most of the time the latter is enough for bug reports.

For the error on login, the logic is pretty simple and the only reason you should be getting that is if your username, password or character name don't match your Tranquility credentials (not necessarily the same as your Singularity ones).

How about putting it into tranquility.

please check bug report 120905 for log files to "error 500 while uploading bug report through ingame bug reporting tool."

Thanks, it looks like the tool is uploading 8MB which the bugs website cannot handle and these bug reports are typically below 1MB. All I can think off is that your settings represent most of that data. I didn't realize people's settings could be so huge and I'll probably need to put a cap on the settings size that can be sent over.

I've responded to the bug report asking for more information to confirm that it is indeed your settings.

Thanks, it looks like the tool is uploading 8MB which the bugs website cannot handle and these bug reports are typically below 1MB. All I can think off is that your settings represent most of that data. I didn't realize people's settings could be so huge and I'll probably need to put a cap on the settings size that can be sent over.
I've responded to the bug report asking for more information to confirm that it is indeed your settings.

- why do you not just transfer the settings in binary form (but apparently in a serialized form)?
- why do you use jpg for IGBR and not lossless png?

to answer your questions:
- The settings are uploaded human-readable so that our bughunters can read the contents and spot 'false positive' issues that are due to settings configuration (this happens frequently).
- I haven't run into issues where the quality of the .jpg is insufficient. Is there something in particular that you're looking for with using a .png?