I am member of envs.net ecosystem (part of TILDE universe).

As you can see server has UTC timezone and everybody and users has their own TZ setup.

On server I have cloned repo https://nest.pijul.com/tankf33der/pil21 and latest pijul compiled :

$ cd pil21-pijul
$ ls -l README 
.rw-r--r-- 4.2k mpech envs  6 Dec 15:06 README
$ date
Sun 06 Dec 2020 05:13:23 PM EET
$ echo $TZ
Europe/Riga

You got the idea. OK.

Main part:

$ cksum README 
2797142561 4198 README
$ vim README                           # modify something
$ cksum README 
3170646386 4199 README
$ pijul diff
$

FYI, git and darcs can detect modification on this server and setup.

Hi! I am finally getting back to this, and I am still deeply puzzled by this. The modification time used to be read, but isn’t anymore, to check if files have changed. The reason is that this isn’t easy to do with the interactive editing of patches.

Is this still an issue? If you find a repository that has the issue, would you mind sending a tarball to pe@pijul.org? Thanks.

This is not the repository issue. This is issue for pijul diff to find what files modified.

Please, follow script:

$ rm mike
$ touch mike
$ ls mike
 ls -l mike 
.rw-r--r-- 0 mpech envs 11 Dec 19:25 mike

Remember time of created file –> 19:25.

When I run date on server it will be +3 from 19:25:

$ date
Fri 11 Dec 2020 21:25:19 PM EET
$ echo $TZ
Europe/Riga

and pijul diff will be confused inside any repo.

Ok, I don’t understand what is going on. Would you mind pasting the output of RUST_LOG="libpijul::record=debug" pijul diff? Thanks a lot.

http://ix.io/2HBD for pijul from crates (alpha.21)

Thanks! Can you confirm that the file you changed is README?

In 40mins.

Wait, my question was unclear. What were you expecting from pijul diff? What file was changed, that Pijul didn’t see?

$ pijul -V
pijul 1.0.0-alpha.21
$ pijul diff --short
$ cksum README
2797142561 4198 README
$ vim README
$ cksum README
3170646386 4199 README
$ RUST_LOG="libpijul::record=debug" pijul diff 2> ../diff-log.txt
# and post diff-log.txt file to:
`http://ix.io/2HBZ`

I could finally reproduce this on this very repository. This was actually a mistake in libpijul, fixed by #OQT5HBBWDPHQG7RILJIBPYWXI2LCBVDHN3Z4RRJFCGXTQOBLW3BQC.

This change is now going through the new CI system.

Did not helped. There is the new log: http://ix.io/2Ic6

This is strange. Can you send me the log of RUST_LOG="libpijul::record=debug,libpijul::diff=debug"? Thanks.

https://envs.sh/SU.xz

there is 70MB compressed debug log file, modified file is README in repo as always before.

Ok, I’m completely lost here. Can I bother you again, and ask you to send a tarball of the repo (with the modified, not-yet-recorded README) to pe@pijul.org? Thanks!

uploaded file is here https://envs.sh/Sk.tgz

$ cd pil21-pijul
$ pijul reset
$ cksum README
2797142561 4198 README
$ vim REAMD
$ cksum README 
3170646386 4199 README
$ pijul diff
<empty output>
$ cd ..
$ tar czf pil21.tgz pil21-pijul
$ cksum pil21.tgz 
3509003880 5658934 pil21.tgz
# upload file to site
# and download from site on normal linux (without time shift, see above)
$ tar zxf pil21.tgz
$ cd pil21-pijul
$ pijul diff
message = ''
timestamp = '2020-12-16T14:07:25.735373836Z'
authors = []

# Dependencies
[2] DFWL5M2V4G6Z5TYC33KTM7JDRRXL2CW72RN4LOG4Y25D2EA6WXHAC

# Changes

1. Edit in README:1 2.5294344
  up 2.5294344, new 0:1, down 2.5294345
+ 
$

Ok, I just tested, and I don’t get it, this looks like the expected behaviour:

$ cksum old_README
2797142561 4198 old_README
$ cksum new_README
3170646386 4199 new_README
$ diff old_README new_README
0a1
> 

And Pijul gives you the same new empty line, right?

I will send you screencast privately

I believe you should close this issue.

I have checked it again on the same Debian and now it works as should.

The issue was around byobu and pager and something else.

Thanks for testing again. I’ve been reading this thread many times in the last few days, trying to figure out how I was going to reproduce and fix it.

The pager issue is really subtle, I’m now testing the version of less on the machine before starting the pager, to know which options it supports ;-)