Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 01:40

    NicolasCARPi on hypernext

    bring out the permissions setti… (compare)

  • 01:01

    NicolasCARPi on ird

    make pdfs smaller by removing h… add doc link for @page add documentation link on api p… and 8 more (compare)

  • 00:17

    NicolasCARPi on hypernext

    make pdfs smaller by removing h… add doc link for @page add documentation link on api p… and 5 more (compare)

  • Nov 28 17:24
    NicolasCARPi labeled #3927
  • Nov 28 17:21
    NicolasCARPi commented #3927
  • Nov 28 16:00
    Proulx-S opened #3927
  • Nov 28 16:00
    Proulx-S labeled #3927
  • Nov 28 15:04

    NicolasCARPi on hypernext

    add comment on SITE_URL descrip… (compare)

  • Nov 28 14:49
    NicolasCARPi closed #3926
  • Nov 28 14:49
    NicolasCARPi commented #3926
  • Nov 28 14:47
    NicolasCARPi commented #3925
  • Nov 28 14:47
    NicolasCARPi closed #3925
  • Nov 28 12:11
    Ir33na labeled #3926
  • Nov 28 12:11
    Ir33na opened #3926
  • Nov 28 12:08
    Ir33na labeled #3925
  • Nov 28 12:08
    Ir33na opened #3925
  • Nov 26 13:19
    NicolasCARPi closed #3923
  • Nov 26 13:19
    NicolasCARPi commented #3923
  • Nov 26 12:20
    danielhatton commented #3923
  • Nov 26 11:51
    NicolasCARPi closed #3924
alexander-haller
@alexander-haller
the default data locations are on ext4 I assume?
besselfunct
@besselfunct
Yes
alexander-haller
@alexander-haller
well my guess is you hit the above bug with zfs - not 100% sure since I do have little experience with zfs myself
besselfunct
@besselfunct
Yeah, it looks like this is a ZFS issue.
I'm not certain how to proceed from here though. I like using ZFS because of the redundancy, and expanding a zpool is trivial
If I can't use ZFS, I'm going to have to figure out another file system, or hunt down a hardware raid solution
alexander-haller
@alexander-haller
there seems to be a bugfix:
because this is does affect mysql on zfs I would assume it will get pushed quickly for ubuntu
besselfunct
@besselfunct
Yeah, it looks like 2.1.5 will fix the issue and I'm running 2.1.4
alexander-haller
@alexander-haller
I'm off for today - if you have more infos note them here. It's always good for the community to have this feedback
besselfunct
@besselfunct
@alexander-haller Many many thanks for helping me nail down this issue. I'm familiar with *NIX systems, but docker and containerization technologies are a complete black box to me. I just need to get this working so I can finish my PhD thesis
Nicolas CARPi
@NicolasCARPi
I love it when community takes over support and I can just sit back and watch issues get resolved. Thanks @alexander-haller ;)
nmontua
@nmontua
Hi. I tried to update to the most current version, but I get an error about incorrect time format that is not covered by any Github issue etc. as far as I have found. The db:update command throws the following error: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0
000-00-00 00:00:00' for column 'datetime' at row 1
Is there a way to roll back to a previous version?
nmontua
@nmontua
I did that, thank you for the link, however not when I run docker exec -it elabftw bin/console db:update, I get a different error :(
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'elabftw.notifications' doesn't exist
nmontua
@nmontua
I have rolled back for now. Maybe I will have time to play around some more at a later date
Nicolas CARPi
@NicolasCARPi
the notifications table is created in schema70.sql, I don't see how it could have been skipped
also if you want support please open a proper github issue with all information so it's easier to debug
nmontua
@nmontua
Absolutely, if on my next attempt this occurs again, I will make a proper github issue. Thank you for your time.
nmontua
@nmontua
Okay, I tried again and this time everything worked fine. Again, I followed the instructions you linked, only this time I did not do "After, manually run the last lines of schema71:". Thats the only thing I did differently really. In any case, happy it worked and thank you for the troubleshooting guide.
Nicolas CARPi
@NicolasCARPi
ok cool
HClO4
@HClO4
I'm just trying to set up a elabftw instance on a Kubuntu VM to test the utf8 stuff prior to the update to 4.3.x. Did elabctl install and elabctl start but all I get is "ERROR: The Compose file '/etc/elabftw.yml' is invalid because:
services.web.depends_on contains an invalid type, it should be an array" with the last command. What is wrong?
Nicolas CARPi
@NicolasCARPi
@HClO4 you are asking what is wrong but you are not showing that part of your config file! So it's hard to say. Does it look exactly like this? https://github.com/elabftw/elabimg/blob/1338801d49fdd3c4ac8e71f58cc5b64b04799235/src/docker-compose.yml-EXAMPLE#L26-L28 If yes, upgrade your docker-compose version.
Nicolas CARPi
@NicolasCARPi
also note that it's perfectly fine to simply remove this part that is causing problem
taitlab
@taitlab
Hello! Silly question - how can I resize a picture in Markdown mode? I think I've done it before, but I forgot the syntax :)
Nicolas CARPi
@NicolasCARPi
You can't (AFAIK)
4 replies
plasmapper
@plasmapper
Hello everyone! I don't know if anyone here is using LabVIEW, but just in case I've made a LabVIEW client library for eLabFTW using API v1 documentation and testing it on https://demo.elabftw.net.
Nicolas CARPi
@NicolasCARPi
@plasmapper that's super cool! I'll add the link to the README once my tree is clean ;)
plasmapper
@plasmapper
@NicolasCARPi By the way. There is one thing that I couldn't do when I played with the API. When I try to set the experiment date using POST experiments/id with date=YYYYMMDD it always changes to current day. I tried other datetime formats with the same result. Changing body and title however works just fine. Do you know what the issue might be?
Nicolas CARPi
@NicolasCARPi
@plasmapper interestingly, this issue has been reported to me this morning and fix shortly after: elabftw/elabftw@8d778e5
it will be part of the next patch release
plasmapper
@plasmapper
Great! Thanks.
Nicolas CARPi
@NicolasCARPi
alexander-haller
@alexander-haller
I did the update to 4.3.9 but it still shows "Installed version: 4.3.8"
elabctl update said "Found latest release: 4.3.9" and pulled the images
in the logs I find "d41elabimg: info: eLabFTW version: 4.3.8"
any idea?
Nicolas CARPi
@NicolasCARPi
my bad, fault in the release process
alexander-haller
@alexander-haller
I suspected the branch in elabimg was strange - thanks for the quick fix @NicolasCARPi
Nicolas CARPi
@NicolasCARPi
FYI: it's this line that needs to be changed for a new version: https://github.com/elabftw/elabimg/blob/master/Dockerfile#L114
alexander-haller
@alexander-haller
and happy sysadminday to all of us ;-)
Nicolas CARPi
@NicolasCARPi
oh yeah it's today! :)
alexander-haller
@alexander-haller
we got ice cream - that's how I noticed
Nicolas CARPi
@NicolasCARPi
ahah