Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

2018-03-30 Thread Greg Trzeciak 
Continuation to this thread was happening 
at: https://groups.google.com/forum/#!topic/racket-users/xZCTFCBvzs0

The problem has been resolved by fixing how timestamps are read from 
filesystem.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

2018-03-28 Thread Greg Trzeciak 
Before I disappear for today - some additional observations + current hack 
if anyone has the same problem:
* folders have correct timestamps
* dependencies downloaded in the same run can have their timestamp even +2h 
into the future.
* install directly from git has the same problem -> "raco pkg install 
https://github.com/some-user/new-package.git; has timestamp +1h or +2h into 
the future
* current workaround (so that I can use Racket at all) is:
  - "raco pkg install new-package" -> edit all downloaded files to save 
with current timestamp OR simply wait 2h (possibly longer) -> run "raco 
setup new-package"

G.


On Thursday, March 29, 2018 at 12:59:12 AM UTC+2, Greg Trzeciak wrote:
>
> Thanks Philip for these ideas, I won't be able to test all the suggestions 
> today (due to time zone ;) but here is what I got so far:
> * My timezone is for Warsaw, Poland
> * When I create a file it is added with a correct timestamp but "raco pkg" 
> downloads it and saves with + 1 hour timestamp. When running raco make on 
> these files it brings the compile-zo error but when I wait 1 hour it 
> compiles them just fine.
>
> So it seems the problem is not during compilation (that was my first 
> thought) but with "raco pkg" which saves the files from git repos with a 
> future date! 
> Now the question is why, how and what to do to fix it?
>
> Thanks for getting me a bit closer to the answer!
>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

2018-03-28 Thread Greg Trzeciak 
Thanks Philip for these ideas, I won't be able to test all the suggestions 
today (due to time zone ;) but here is what I got so far:
* My timezone is for Warsaw, Poland
* When I create a file it is added with a correct timestamp but "raco pkg" 
downloads it and saves with + 1 hour timestamp. When running raco make on 
these files it brings the compile-zo error but when I wait 1 hour it 
compiles them just fine.

So it seems the problem is not during compilation (that was my first 
thought) but with "raco pkg" which saves the files from git repos with a 
future date! 
Now the question is why, how and what to do to fix it?

Thanks for getting me a bit closer to the answer!


On Thursday, March 29, 2018 at 12:18:51 AM UTC+2, Philip McGrath wrote:
>
> I don't really know, but a few thoughts:
>
>- I'm very suspicious about the daylight savings time possibility. 
>Would you be comfortable sharing your specific timezone?
>- It might be helpful to see the results of 
>file-or-directory-modify-seconds 
>
> 
>  
>for the source and .zo files.
>- Have you checked what your OS thinks about these modification times 
>compared to your system time? When you create other files, does it mark 
>them with the correct creation time?
>- What happens if you try to compile a module outside of a 
>package/collection, perhaps via raco make or the compiler/compiler 
>
>  
>library?
>- You could see if manually setting the source file's modification 
>time to something, say, a day in the past could trick it into working.
>
>
>
> -Philip
>
> On Wed, Mar 28, 2018 at 4:30 PM, Greg Trzeciak  > wrote:
>
>> I was too quick with the success update - although I was able to install 
>> some packages that were failing before, the problem is not resolved for 
>> other packages - I have just tested "syndicate" package - exactly the same 
>> error.
>>
>> In the offline conversation with Kieran Hardy we briefly discussed some 
>> edge-case possibility: I can't be certain it is the case but I don't recall 
>> having the problem before the Weekend and it was the Weekend with a Summer 
>> time switch in my time zone -> UTC+1 + 1 (Daylight Saving Time).
>>
>> From the time of the fresh install I only managed to install 2 packages 
>> that previously failed: pop-pl and pollen-count and test them + install 
>> syndicate that failed, no other Racket activity today.
>>
>> Any ideas?
>>
>> G.
>>
>>
>> On Wednesday, March 28, 2018 at 1:03:29 PM UTC+2, Greg Trzeciak wrote:
>>>
>>> Quick update - doing a fresh install of Racket solved the problem on my 
>>> machine, an interesting case nevertheless.
>>>
>>> On Wednesday, March 28, 2018 at 1:07:14 AM UTC+2, Greg Trzeciak wrote:

 Forgot to mention - my setup is: Racket 6.12 on Windows 10... could be 
 some recent Windows update?

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

2018-03-28 Thread Philip McGrath 
I don't really know, but a few thoughts:

   - I'm very suspicious about the daylight savings time possibility. Would
   you be comfortable sharing your specific timezone?
   - It might be helpful to see the results of
   file-or-directory-modify-seconds
   

   for the source and .zo files.
   - Have you checked what your OS thinks about these modification times
   compared to your system time? When you create other files, does it mark
   them with the correct creation time?
   - What happens if you try to compile a module outside of a
   package/collection, perhaps via raco make or the compiler/compiler
   
   library?
   - You could see if manually setting the source file's modification time
   to something, say, a day in the past could trick it into working.



-Philip

On Wed, Mar 28, 2018 at 4:30 PM, Greg Trzeciak  wrote:

> I was too quick with the success update - although I was able to install
> some packages that were failing before, the problem is not resolved for
> other packages - I have just tested "syndicate" package - exactly the same
> error.
>
> In the offline conversation with Kieran Hardy we briefly discussed some
> edge-case possibility: I can't be certain it is the case but I don't recall
> having the problem before the Weekend and it was the Weekend with a Summer
> time switch in my time zone -> UTC+1 + 1 (Daylight Saving Time).
>
> From the time of the fresh install I only managed to install 2 packages
> that previously failed: pop-pl and pollen-count and test them + install
> syndicate that failed, no other Racket activity today.
>
> Any ideas?
>
> G.
>
>
> On Wednesday, March 28, 2018 at 1:03:29 PM UTC+2, Greg Trzeciak wrote:
>>
>> Quick update - doing a fresh install of Racket solved the problem on my
>> machine, an interesting case nevertheless.
>>
>> On Wednesday, March 28, 2018 at 1:07:14 AM UTC+2, Greg Trzeciak wrote:
>>>
>>> Forgot to mention - my setup is: Racket 6.12 on Windows 10... could be
>>> some recent Windows update?
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.