Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Json error format #230

Merged
merged 6 commits into from
Sep 27, 2016
Merged

Conversation

Vbif
Copy link
Contributor

@Vbif Vbif commented Aug 27, 2016

No description provided.

[Test]
public void FileNotFound()
{
const string output = "{\"message\":\"couldn't read \\\"main2.rs\\\": Не удается" +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that the test will fail when the system language is not Russian? That would be bad. Can you try to make this locale independent?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These test just check basic mapping between JSON and RustcMessageJson class. So it is not depend on language, but I definitely need translate error message

@Boddlnagg
Copy link
Contributor

Thanks! I added some comments inline. Apart from that, this looks great :)

@vosen: Are you still maintaining this project? Do you also want to have a look? And why is AppVeyor not set up to test PRs also?

@Boddlnagg
Copy link
Contributor

Boddlnagg commented Aug 30, 2016

I just tested this and found a few more problems:

  • The spans are incorrect: When you call LogError/LogWarning, you should use column_start/column_end instead of byte_start/byte_end for the columns.
  • The error aborting due to previous error should not be forwarded (it has no span and no code)
  • I think you have to add Newtonsoft.Json.dll as a component to the installer next to VisualRust.Build.dll. This is in VisualRust.Setup\VisualRust.wxs.

Besides that it seems to work 👍

@Vbif
Copy link
Contributor Author

Vbif commented Sep 4, 2016

I have a problem with building setup package.

Severity    Code    Description Project File    Line    Suppression State
Error       The "ResolveWixReferences" task could not be loaded from the assembly \WixTasks.dll. Could not load file or assembly 'file:///C:\WixTasks.dll' or one of its dependencies. Не удается найти указанный файл. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.    VisualRust.Setup    C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix2010.targets   735 

@Boddlnagg
Copy link
Contributor

@Vbif What version of WiX do you have installed? It works here with WiX 3.10.3

@Vbif
Copy link
Contributor Author

Vbif commented Sep 5, 2016

v3.10.3.2904

@Boddlnagg
Copy link
Contributor

Mine is v3.10.3.3007 .... and it looks like this issue was actually fixed there.

@Boddlnagg
Copy link
Contributor

Will you be able to finish this? Otherwise I'm going to do it.
One more thing: You're checking for a version ≥ 1.11, but --error-format=json is only stabilized in 1.12, so you should change the version check to check for ≥ 1.12.

@Boddlnagg Boddlnagg merged commit 17d0eac into PistonDevelopers:master Sep 27, 2016
@Boddlnagg
Copy link
Contributor

Thanks!

@Boddlnagg Boddlnagg mentioned this pull request Oct 16, 2016
@Vbif Vbif deleted the json_error_format_2 branch October 23, 2016 07:27
@vosen
Copy link
Member

vosen commented Oct 23, 2016

@Boddlnagg
yes, still interested in maintaining VR, just didn't have any free time lately. Conversely, are you? If so add youself to the README.
I disable AppVeyor on PR, because I've jave been commiting faster than AppVeyor could test my changes (It could take an hour to have a run) and with NCrunch my master-breaking changes were mostly isolated to WiX (which AppVeyor didn't catch anyway) so I settled on tests after merge.

@Boddlnagg
Copy link
Contributor

@vosen: I don't really have enough time to take over maintenance, either.
As far as CI tests for PRs are concerned: That sounds reasonable. It still would be useful to have them sometimes (like, on demand), but that's probably not possible?

@vosen
Copy link
Member

vosen commented Nov 7, 2016

Ill look into it

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

Successfully merging this pull request may close these issues.

3 participants