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
Hélène Polvèche ( CECS/I-Stem )
@helenepolveche
image.png
Nicolas CARPi
@NicolasCARPi
did you really try exactly what I suggested with the prune command?
maybe we're hitting a specific bug on 22.04 but I'd be surprised
what I don't get is that it is not clear what the issue is
normally it's easier to troubleshoot because we get a clear error message
Hélène Polvèche ( CECS/I-Stem )
@helenepolveche
I already did with the prune cmmand, but I can do it again :)
Nicolas CARPi
@NicolasCARPi
yeah, it's just to be sure (don't forget the -a)
Hélène Polvèche ( CECS/I-Stem )
@helenepolveche
i redo
Nicolas CARPi
@NicolasCARPi
if you still have the same issue it means the problem is reproducible
maybe I'll try an install in a vm
Hélène Polvèche ( CECS/I-Stem )
@helenepolveche
thank you !
Nicolas CARPi
@NicolasCARPi
sinon on peut faire un zoom pour debug aussi !
Hélène Polvèche ( CECS/I-Stem )
@helenepolveche
avec plaisir
Nicolas CARPi
@NicolasCARPi
voir mp
sur la gauche
Nicolas CARPi
@NicolasCARPi
for anyone reading this conversation, deleting the mysql folder on the host was key. After that it was seemingly working but we hit a timeout while connecting to mysql that needs further troubleshooting.
besselfunct
@besselfunct
I'm getting a certificate error on my server. It says that the certificate is expired, but CertBot is indicating that the certificate is not up for renewal until 2023. I ran certbot certonly --force-renew -d my.domain.edu which completed successfully, but I'm still getting an error
besselfunct
@besselfunct
I thought I set my certificates to autorenew, but apparently it didn't work?
alexander-haller
@alexander-haller

@besselfunct

`root@elabftw-dev:~# crontab -l

Ansible: elabctl backup

00 03 * /usr/local/bin/elabctl backup

Ansible: Certbot automatic renewal.

30 3 * certbot renew --quiet --no-self-upgrade --post-hook "docker exec elabftw nginx -s reload"`

did you reload your docker container after cert renew?
Nicolas CARPi
@NicolasCARPi
yeah that's probably the issue here
alexander-haller
@alexander-haller
tbh i stumbled over this one as well at one point ;-)
but live and (ideally learn) (and do not forget)
Nicolas CARPi
@NicolasCARPi
yeah, my renewal cronjob had an haproxy reload at the end ;)
jonasschwab
@jonasschwab
I have an issue with special characters in names when restoring an eLabFTW backup. Special characters like 'ß' are mit probely displayed in the fronted.
E.g. 'ß' is displayed as 'ß' or 'ć' is displayed as 'ć'. In the mysql shell they're displayed correcly, though.
Do you have an idea what might be the problem?
besselfunct
@besselfunct
I did not reload the docker container. That's definitely the issue
Thanks!
besselfunct
@besselfunct
@alexander-haller If I understand your crontab, you're trying to renew the Cert every day at 3:30 am?
3 replies
Nicolas CARPi
@NicolasCARPi
@jonasschwab welcome into UTF-8 hell!
Joshua Taillon
@jat255
Before making a feature request on Github, I wanted to check to see if I'm not missing something: is there a way to show "recursive" links in any sort of search query? i.e. if I have an experiment linked to "Item A", which has another link to "Item B", is there a way to display the whole link tree (or graph)?
or even just a list of "all" related items, no matter the depth
(not necessarily a graph)
Nicolas CARPi
@NicolasCARPi
nah
only with depth=1
Joshua Taillon
@jat255
hmm, okay, thanks. I did see the "Import links" button, which kind of helps, but then you lose the depth information
Nicolas CARPi
@NicolasCARPi
I guess by chaining api calls you can get what you want
"use the api" is the easy response to feature request for me :p
21 replies
thomasweiss
@thomasweiss:matrix.org
[m]
I think this chat room would benefit from using the (experimental but IMO good enough) thread functionality from Matrix :-)
10 replies
Nicolas CARPi
@NicolasCARPi
meh, then you have to click the threads to see the answers. I kinda like the flat structure à la irc
Joshua Taillon
@jat255
I'm having some trouble figuring out the correct syntax for a metakey/metavalue search using the elabapy library. Am I missing documentation somewhere about this? I've figured out that I can use the "search" parameter with manager.get_all_items() to searching using the category:Instrument title:"An Instrument" syntax, but cannot figure out the right syntax for searching in the "extra_fields" metadata like is possible from the search.php page
it looks like when searching with from search.php, those extra fields searches go through as metakey and metavalue query parameters, and I'm not sure if there's a mapping for those in elabapy
Nicolas CARPi
@NicolasCARPi
no, no mapping in elabapy, use the requests lib directly to add such parameters
13 replies
thomasweiss
@thomasweiss:matrix.org
[m]
thomasweiss
@thomasweiss:matrix.org
[m]
Oh I didn't put it in the thread. Sorry I created a bigger mess now :-D
jonasschwab
@jonasschwab

I have an issue with eLabFTW version 4.2.4, when resoring the dump from mysql 5.7 to mysql 8.0. The behaviour is the same when updating to later versions of eLabFTW: The special characters in names, e.g. "ß" don't get displayed correctly, but when accessing them through the console they seemed to be stored correctly.

I have eLabFTW 4.2.4 running with mysql 5.7. The database is dumped with

docker exec mysql bash -c 'mysqldump -u$MYSQL_USER -p$MYSQL_PASSWORD -r dump.sql --no-tablespaces --default-character-set=utf8 $MYSQL_DATABASE'

And on a fresh installation with eLabFTW 4.2.4 and mysql 8.0, I run on the mysql console:

drop database elabftw; create database elabftw character set utf8mb4 collate utf8mb4_0900_ai_ci;

And then

mysql --default-character-set=utf8 -u$MYSQL_USER -p$MYSQL_PASSWORD elabftw < dump.sql

When querying through the mysql console, the names seem to be stored correctly:

mysql> use elabftw; SELECT lastname FROM users WHERE userid = <some_userid>;
Database changed
+----------+
| lastname |
+----------+
| fooßbar  |
+----------+
1 row in set (0.00 sec)

While in the fronted this name is displayed as "fooßbar".

Changing the name to "fooßbar" in the fronted, translates to the mysql console as:

+----------+
| lastname |
+----------+
| foo�bar  |
+----------+

Do you have an idea what might be the issue? I've tried doing the migration with and without --default-character-set with the same results. Migrating from the existing version with mysql 5.7 to a fresh one with mysql 5.7 works fine.

1 reply
BeZie
@BeZie
Hey there, I am trying to delete an upload using the restapi v2 on current beta6 with pythons requests. Also patching the upload isnt working. Here is the snippet s.delete(f'{self.url}/items/{item_id}/uploads/{upload_id}', **{'headers': {'Authorization': self.token, 'accept': '*/*'}} )and I get the return 'code': 400, 'message': 'Bad Request', 'description': 'Incorrect content-type header.'
Thanks for any help :)
Nicolas CARPi
@NicolasCARPi
@BeZie use Content-Type: application/json headr
BeZie
@BeZie
@NicolasCARPi works like a charm. It is unfortunately not described in the doc. https://doc.elabftw.net/api/v2 . Again Thanks a lot for the quick answer
Nicolas CARPi
@NicolasCARPi
yes, I'll look into improving the docs with that header