Skip to content

Commit

Permalink
Add troubleshooting info for #7585
Browse files Browse the repository at this point in the history
  • Loading branch information
mmmarcos committed Jun 17, 2024
1 parent 13a07cf commit 5deffd0
Show file tree
Hide file tree
Showing 2 changed files with 171 additions and 52 deletions.
182 changes: 141 additions & 41 deletions docs/locale/fr/LC_MESSAGES/userguide/troubleshooting.po
Original file line number Diff line number Diff line change
Expand Up @@ -7,80 +7,180 @@ msgid ""
msgstr ""
"Project-Id-Version: Parsec 2.16.0-a.0+dev\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-26 11:54+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: fr\n"
"POT-Creation-Date: 2024-06-17 12:28+0200\n"
"PO-Revision-Date: 2024-06-17 12:36+0200\n"
"Last-Translator: Marcos Medrano <[email protected]>\n"
"Language-Team: fr <[email protected]>\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.13.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"Generated-By: Babel 2.15.0\n"
"X-Generator: Poedit 3.4.4\n"

#: ../../userguide/troubleshooting.rst:6
msgid "Troubleshooting"
msgstr ""
msgstr "Résolution des problèmes"

#: ../../userguide/troubleshooting.rst:9
msgid "Excel/Word or another MS Office software says the file name is too long"
#: ../../userguide/troubleshooting.rst:10
msgid "MS Excel/Word or another MS Office software says the file name is too long"
msgstr ""
"MS Excel/Word ou un autre logiciel MS Office indique que le nom du fichier est "
"trop long"

#: ../../userguide/troubleshooting.rst:13
#: ../../userguide/troubleshooting.rst:14
msgid ""
"This error message occurs when you save or open a file if the path to the "
"file (including the file name) exceeds 218 characters. This limitation "
"includes three characters representing the drive, the characters in folder "
"names, the backslash character between folders, and the characters in the "
"file name."
"This error message occurs when you save or open a file if the path to the file "
"(including the file name) exceeds 218 characters. This limitation includes "
"three characters representing the drive, the characters in folder names, the "
"backslash character between folders, and the characters in the file name."
msgstr ""
"Ce message d'erreur apparaît lorsque vous enregistrez ou ouvrez un fichier si "
"le chemin d'accès au fichier (y compris le nom du fichier) dépasse 218 "
"caractères. Cette limite inclut les trois caractères représentant la lettre du "
"lecteur, les caractères des noms de dossiers, la barre oblique inverse entre "
"les dossiers et les caractères du nom du fichier."

#: ../../userguide/troubleshooting.rst:17
#: ../../userguide/troubleshooting.rst:18
msgid ""
"`Error message when you open or save a file in microsoft excel filename "
"<https://support.microsoft.com/en-us/help/213983/error-message-when-you-open-"
"or-save-a-file-in-microsoft-excel-filename>`_"
"<https://support.microsoft.com/en-us/help/213983/error-message-when-you-open-or-"
"save-a-file-in-microsoft-excel-filename>`_"
msgstr ""
"`Message d'erreur lors de l'ouverture ou de l'enregistrement d'un fichier dans "
"microsoft excel nom de fichier <https://support.microsoft.com/en-us/help/213983/"
"error-message-when-you-open-or-save-a-file-in-microsoft-excel-filename>`_"

#: ../../userguide/troubleshooting.rst:19
#: ../../userguide/troubleshooting.rst:20
msgid ""
"So this is a Microsoft issue, and there is nothing Parsec can do about it. "
"The only solution is to rename the file, or rename one or more folders that "
"contain the file in order to have shorter names."
"So this is a Microsoft issue, and there is nothing Parsec can do about it. The "
"only solution is to rename the file, or rename one or more folders that contain "
"the file in order to have shorter names."
msgstr ""
"Il s'agit donc d'un problème lié à Microsoft, et Parsec ne peut rien y faire. "
"La seule solution est de renommer le fichier, ou de renommer un ou plusieurs "
"dossiers qui contiennent le fichier afin d'avoir des noms plus courts."

#: ../../userguide/troubleshooting.rst:22
msgid "Too many old devices appear in the device selection dropdown"
msgstr ""

#: ../../userguide/troubleshooting.rst:24
msgid ""
"This usually occurs when a user has tried Parsec beta versions in which test "
"databases could be reset at any time, leaving old devices still registered "
"on their computer."
msgstr ""
#: ../../userguide/troubleshooting.rst:23
msgid "Specific to Parsec V2"
msgstr "Spécifique à Parsec V2"

#: ../../userguide/troubleshooting.rst:26
msgid "A user can still erase these devices manually though:"
msgid ""
"Copying files from Parsec V2 take some time / files are not accessible during "
"copy"
msgstr ""
"La copie des fichiers depuis Parsec V2 prend du temps / les fichiers ne sont "
"pas accessibles pendant la copie"

#: ../../userguide/troubleshooting.rst:28
msgid ""
"**On Windows**, in the explorer's address bar, go to ``%APPDATA%/parsec**`` "
"(or ``C:\\Users\\<YourUser>\\AppData\\Roaming``, AppData is a hidden "
"folder). **On Linux**, go to ``~/.config/parsec``."
"When copying files from a mounted workspace in Parsec V2 the operation may take "
"some time and the files may not be accessible to open them. After some time, "
"files are copied and can be open normally."
msgstr ""
"Lors de la copie de fichiers à partir d'un espace de travail monté dans Parsec "
"V2, l'opération peut prendre un certain temps et les fichiers peuvent ne pas "
"être accessibles pour les ouvrir. Après un certain temps, les fichiers sont "
"copiés et peuvent être ouverts normalement."

#: ../../userguide/troubleshooting.rst:31
msgid "Remove unwanted devices in config/devices"
#: ../../userguide/troubleshooting.rst:30
msgid ""
"This is most likely due to data is not being present locally in cache. Reading "
"data when is not in cache is much slower than reading data from from a regular "
"on-disk filesystem and performance is heavily dependent on your internet "
"connection speed."
msgstr ""
"Cela est probablement dû au fait que les données ne sont pas présentes "
"localement dans le cache. La lecture de données qui ne sont pas dans le cache "
"est beaucoup plus lente que la lecture de données à partir d'un système de "
"fichiers sur disque ordinaire et les performances dépendent fortement de la "
"vitesse de votre connexion internet."

#: ../../userguide/troubleshooting.rst:32
msgid "Remove unwanted devices in data"
msgid ""
"Moreover, while the file is under copy, its displayed size only grows when a "
"*flush* operation occurs. Flush are not explicitly issued by Parsec V2 and "
"happen automatically when data written since previous flush is bigger than the "
"blocksize of the file (i.e. 512KB)."
msgstr ""
"De plus, lorsque le fichier est en cours de copie, sa taille affichée "
"n'augmente que lorsqu'une opération de *flush* se produit. Cette opération "
"n'est pas explicitement lancée par Parsec V2 et se produit automatiquement "
"lorsque les données écrites depuis le flush précédent sont plus grandes que la "
"taille de bloc du fichier (c'est-à-dire 512 Ko)."

#: ../../userguide/troubleshooting.rst:34
msgid ""
"So this explain why the file can appear with a size of 0 for some time: data is "
"being downloaded into cache and then copied via occasional flush operations."
msgstr ""
"Cela explique pourquoi le fichier peut apparaître avec une taille de 0 pendant "
"un certain temps : les données sont téléchargées dans la mémoire cache, puis "
"copiées par des opérations de vidage occasionnelles."

#: ../../userguide/troubleshooting.rst:36
msgid ""
"Be very careful. Deleting a device virtually means deleting the data stored "
"in that device (since there's no way to decrypt them)."
"You could try enabling :ref:`off-line mode "
"<doc_userguide_workspace_offline_mode>` on workspaces before copying large "
"amount of files. In any case, you will need to wait for the copy to be fully "
"finished to be able to open files."
msgstr ""
"Vous pouvez essayer d'activer :ref:`off-line mode "
"<doc_userguide_workspace_offline_mode>` sur les espaces de travail avant de "
"copier une grande quantité de fichiers. Dans tous les cas, vous devrez attendre "
"que la copie soit complètement terminée pour pouvoir ouvrir les fichiers."

#: ../../userguide/troubleshooting.rst:39
msgid "How to remove old devices from the login page"
msgstr "Comment supprimer les anciens appareils de la page de connexion ?"

#: ../../userguide/troubleshooting.rst:41
msgid ""
"Old devices remain registered on the computer and are displayed in the login "
"page. This is usually the case after having tried multiple Parsec beta versions."
msgstr ""
"Les anciens appareils restent enregistrés sur l'ordinateur et sont affichés sur "
"la page de connexion. C'est généralement le cas après avoir essayé plusieurs "
"versions bêta de Parsec."

#: ../../userguide/troubleshooting.rst:43
msgid "You can still remove these devices manually:"
msgstr "Vous pouvez toujours supprimer ces appareils manuellement :"

#: ../../userguide/troubleshooting.rst:45
msgid "Go to Parsec configuration directory"
msgstr "Aller dans le répertoire de configuration de Parsec"

#: ../../userguide/troubleshooting.rst:46
msgid ""
"**On Windows**, open the file explorer and put ``%APPDATA%/parsec**`` in the "
"address bar (or go to ``C:\\Users\\<YourUser>\\AppData\\Roaming``, note that "
"AppData is a hidden folder)."
msgstr ""
"**Sous Windows**, ouvrez l'explorateur de fichiers et mettez ``%APPDATA%/"
"parsec**`` dans la barre d'adresse (ou allez dans ``C:"
"\\Users<VotreUtilisateur>\\AppData\\Roaming``, notez qu'AppData est un dossier "
"caché)."

#: ../../userguide/troubleshooting.rst:47
msgid "**On Linux**, open ``~/.config/parsec``."
msgstr "**Sous Linux**, ouvrez ``~/.config/parsec``."

#: ../../userguide/troubleshooting.rst:48
msgid "Remove unwanted devices in config/devices"
msgstr "Supprimer les appareils non désirés dans config/devices"

#: ../../userguide/troubleshooting.rst:49
msgid "Remove unwanted devices in data"
msgstr "Supprimer les appareils non désirés dans data"

#: ../../userguide/troubleshooting.rst:53
msgid ""
"Be very careful. Deleting a device means virtually deleting the data stored in "
"that device (since there's no way to decrypt it)."
msgstr ""
"Soyez très prudent. La suppression d'un appareil signifie virtuellement la "
"suppression des données qui y sont stockées (puisqu'il n'y a aucun moyen de les "
"décrypter)."
41 changes: 30 additions & 11 deletions docs/userguide/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,9 @@
Troubleshooting
===============

Excel/Word or another MS Office software says the file name is too long
-----------------------------------------------------------------------

MS Excel/Word or another MS Office software says the file name is too long
--------------------------------------------------------------------------

.. note::

Expand All @@ -18,19 +19,37 @@ Excel/Word or another MS Office software says the file name is too long

So this is a Microsoft issue, and there is nothing Parsec can do about it. The only solution is to rename the file, or rename one or more folders that contain the file in order to have shorter names.

Too many old devices appear in the device selection dropdown
------------------------------------------------------------
Specific to Parsec V2
---------------------

Copying files from Parsec V2 take some time / files are not accessible during copy
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

When copying files from a mounted workspace in Parsec V2 the operation may take some time and the files may not be accessible to open them. After some time, files are copied and can be open normally.

This is most likely due to data is not being present locally in cache. Reading data when is not in cache is much slower than reading data from from a regular on-disk filesystem and performance is heavily dependent on your internet connection speed.

Moreover, while the file is under copy, its displayed size only grows when a *flush* operation occurs. Flush are not explicitly issued by Parsec V2 and happen automatically when data written since previous flush is bigger than the blocksize of the file (i.e. 512KB).

So this explain why the file can appear with a size of 0 for some time: data is being downloaded into cache and then copied via occasional flush operations.

You could try enabling :ref:`off-line mode <doc_userguide_workspace_offline_mode>` on workspaces before copying large amount of files. In any case, you will need to wait for the copy to be fully finished to be able to open files.

How to remove old devices from the login page
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Old devices remain registered on the computer and are displayed in the login page. This is usually the case after having tried multiple Parsec beta versions.

This usually occurs when a user has tried Parsec beta versions in which test databases could be reset at any time, leaving old devices still registered on their computer.
You can still remove these devices manually:

A user can still erase these devices manually though:
1. Go to Parsec configuration directory

**On Windows**, in the explorer's address bar, go to ``%APPDATA%/parsec**`` (or ``C:\Users\<YourUser>\AppData\Roaming``, AppData is a hidden folder).
**On Linux**, go to ``~/.config/parsec``.
- **On Windows**, open the file explorer and put ``%APPDATA%/parsec**`` in the address bar (or go to ``C:\Users\<YourUser>\AppData\Roaming``, note that AppData is a hidden folder).
- **On Linux**, open ``~/.config/parsec``.

- Remove unwanted devices in config/devices
- Remove unwanted devices in data
2. Remove unwanted devices in config/devices
3. Remove unwanted devices in data

.. warning::

Be very careful. Deleting a device virtually means deleting the data stored in that device (since there's no way to decrypt them).
Be very careful. Deleting a device means virtually deleting the data stored in that device (since there's no way to decrypt it).

0 comments on commit 5deffd0

Please sign in to comment.