Skip to content

Conversation

@smacker
Copy link
Collaborator

@smacker smacker commented Dec 26, 2017

  • Use modtime 1 for go-bindata to avoid changes of assets.go
  • Don't copy node_modules inside docker container
  • Disable source map for production build to avoid assets differences
  • Updated react-scripts to 1.0.17
  • Validate assets.go as CI step

Signed-off-by: smacker max@smacker.ru

@smacker smacker requested a review from dpordomingo December 26, 2017 17:23
Copy link
Member

@dpordomingo dpordomingo left a comment

Choose a reason for hiding this comment

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

LGTM
But I'd require only one thing: to separate each feature in a dedicated commit. That way the changes will be easily tracked. Once you do it, you can auto merge :)

Makefile Outdated
# simple go get doesn't work for client go
install-client-go:
go get gopkg.in/bblfsh/client-go.v2
go get -d gopkg.in/bblfsh/client-go.v2
Copy link
Contributor

Choose a reason for hiding this comment

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

Also a "-v -u" will be helpfull

@smacker
Copy link
Collaborator Author

smacker commented Dec 27, 2017

@dpordomingo all features are related to each other. For CI step we need to keep assets unchanged for the same code, modtime doesn't help much without disabling source code mapping and we can't disable mapping without updating react-scripts.

So the point is there is no much profit in any of this changes without new CI step and this PR is about it.

Only .dockerignore doesn't belong here, but it's such a small change, I think we don't really need separate PR for it.

smacker and others added 2 commits April 3, 2018 15:21
- Use modtime 1 for go-bindata to avoid changes of assets.go
- Don't copy node_modules inside docker container
- Disable source map for production build to avoid assets differences
- Updated react-scripts to 1.0.17
- Validate assets.go as CI step

Signed-off-by: smacker <max@smacker.ru>
Signed-off-by: Maxim Sukharev <maxim@sourced.tech>
Copy link
Contributor

@bzz bzz left a comment

Choose a reason for hiding this comment

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

CI failure is not relevant to the changes and is tracked under https://github.com/bblfsh/client-go/issues/50

Is there anything left before merging this one?

@dpordomingo
Copy link
Member

Since @mcuadros comments were already addressed, there is two PR approvals and no rejections, I think @smacker can merge whenever he is ready.

@smacker
Copy link
Collaborator Author

smacker commented Apr 6, 2018

@bzz I don't think it's network failure. It compiles correctly locally on my machine (without cache), on Denis machine and in travis on client-go (I asked to rerun the job and it finished successfully). But it fails in travis of dashboard. I tried to investigate, but couldn't find the reason of the problem quickly. I'll try again later.

@dpordomingo
Copy link
Member

I spotted the problem. I'm taking care of it
@smacker @bzz @dennwc

@dpordomingo
Copy link
Member

This https://github.com/bblfsh/client-go/pull/51 should fix the issue with Travis

@bzz
Copy link
Contributor

bzz commented Apr 17, 2018

@dpordomingo thank you! Fix seems to be merged now, shall we update something here as part of this PR to benefit from it?

Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
@smacker
Copy link
Collaborator Author

smacker commented Apr 18, 2018

ci is green. I'm merging.

@smacker smacker merged commit c696e6f into bblfsh:master Apr 18, 2018
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.

4 participants