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

Incremental Compilation doesn't work on certain systems. Can't interpret a date #284

Closed
codec-abc opened this issue Feb 6, 2018 · 18 comments
Labels

Comments

@codec-abc
Copy link

Hi,

I try to follow the step described in the readme to get a something up and running. Here is what I did to create a project and try having it running. For more context, I used VSCode (thus the code . command) to modify the mix.exs file which is after the modification like this. Do you notice something wrong in my setup?

Also before that, I tried to get something working on Windows and I cannot even got something close to work. I could not even call elchemy from the command line. Is Windows supported at this point?

@wende
Copy link
Owner

wende commented Feb 6, 2018

Hi @codec-abc
Your setup seems fine to me. Can you print all of the versions according to troubleshooting doc here?
https://github.com/wende/elchemy/blob/master/roadmap/TROUBLESHOOTING.md

Regarding Windows, there was no attempts of running it on Windows what so ever.
Elchemy bash file uses many unix tools like find, symlinks etc.
I'm completely unaware what is the availability of these tools on Windows

@wende
Copy link
Owner

wende commented Feb 6, 2018

Oh! It seems that there is a problem here with incremental compilation feature.

Particularly here

find: I cannot figure out how to interpret ‘Mon Apr 10 00:00:00 CET 1995’ as a date or time

@wende
Copy link
Owner

wende commented Feb 6, 2018

What form is your output in when you use date command?
And what OS are you using?

@wende wende changed the title Cannot getting started Incremental Compilation doesn't work on certain systems. Can't interpret a date Feb 6, 2018
@wende wende added the bug label Feb 6, 2018
@codec-abc
Copy link
Author

I'm on A Ubuntu 16.04 LTS guest inside a Windows 10 host (through virtualbox). Typing date print mardi 6 février 2018, 18:44:14 (UTC+0100). About Windows, maybe a quick note in the Readme could be writem about it? Also do you plan to support it at some point (even far away in the future) ?

@wende
Copy link
Owner

wende commented Feb 6, 2018

I've never considered that it won't parse a date on non english locale. That's definitely an important bug 🐛
I'll fix that ASAP.

Regarding Windows I don't really have a platform to test it on. Plus I don't know how people use Windows for development (which terminal client for instance). I'd need help from somebody else on that.
But that definitely deserves a card created

@codec-abc
Copy link
Author

Thanks!

Concerning Windows support, it seems that it "only" boils down to using Unix tools in bash script and makefile since the underlying tools (Elixir and Elm) already support it. At first glance I don't notice something else that shouldn't work out of the box on Windows. Do you want me to open an issue to somehow track to start what won't work on Windows today?

@wende
Copy link
Owner

wende commented Feb 6, 2018

Created a card for that. I'd appreciate any reports and concerns if found. Thanks!

@OvermindDL1
Copy link

OvermindDL1 commented Feb 6, 2018

Why not use explicit date formatting syntax?

╰─➤  date +%Y%m%d 
20180206

It has a ton of formatting options to massage it into whatever format you want.

@wende
Copy link
Owner

wende commented Feb 6, 2018

Should be fixed in version 0.6.4
install using npm install -g [email protected]
And let me know 👍

@codec-abc
Copy link
Author

Still got the same error after update elchemy, elm and creating a new project.

hmird@hmird-VirtualBox:~/Dev/elchemy/a_project$ mix test
warning: redefining module ElchemyInit (current version defined in memory)
  elchemy.exs:1

==> elchemy
Compiling 6 files (.ex)

== Compilation error in file elm/Elchemy/Native/NativeDict.ex ==
** (CompileError) elm/Elchemy/Native/NativeDict.ex:2: module Elchemy.XBasics is not loaded and could not be found
    expanding macro: Elchemy.import_std/0
    elm/Elchemy/Native/NativeDict.ex:2: Native.Dict (module)
    expanding macro: Elchemy.__using__/1
    elm/Elchemy/Native/NativeDict.ex:2: Native.Dict (module)
could not compile dependency :elchemy, "mix compile" failed. You can recompile this dependency with "mix deps.compile elchemy", update it with "mix deps.update elchemy" or clean it with "mix deps.clean elchemy"

The good point is that the message about the unrecognized date thing has disappear.

@wende
Copy link
Owner

wende commented Feb 7, 2018

Did you elchemy clean before that?

@codec-abc
Copy link
Author

Since I delete the whole directory and create a new one, I didn't do it. Did I still need it to do it?

@wende
Copy link
Owner

wende commented Feb 7, 2018

Oh. Nope. Shouldn't change a thing then. Could you share a repo somewhere so I can look at it?

@codec-abc
Copy link
Author

Here is my project.

I hope it will be enough to diagnose the issue.

@wende wende reopened this Feb 7, 2018
@wende
Copy link
Owner

wende commented Feb 7, 2018

Downloaded.
Couldn't compile

elchemy clean
mix test

Fixed the issue for me

@wende
Copy link
Owner

wende commented Feb 7, 2018

If you're still seeing this problem tell me what outputs do you get from:

  • date +"%Y-%m-%d %H:%M:%S"
  • find . -newermt "1995-04-10 23:35:02"

@codec-abc
Copy link
Author

codec-abc commented Feb 7, 2018

I run elchemy clean and I got

rm: missing operand
Try 'rm --help' for more information.

Then I ran mix test and it worked, and now running elchemy clean again seems to work without complaining about a missing operand.

I am not really sure what happened there since I am quite sure I have done a rm -r over my old project and created a new one.

@wende
Copy link
Owner

wende commented Feb 7, 2018

Missing operand as far as I know would mean there was nothing to clean
So that would confirm your statement.

Can't really tell
Let me know if you see that again in future so we could reproduce the problem! 👍

Closing for now

@wende wende closed this as completed Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants