Skip to content

Pootle FS snaglist

Jump to bottom
Dwayne Bailey edited this page Jan 16, 2017 · 21 revisions

Another list of snags. Just throw it away when we're mostly fixed. Don't get yourself attached to the list.

New newer list

Language mappings

  • Adding a new mapping leave mappings stuck in cached state:
    • fetch, state
    • WARNING Could not import files for languages: es-ES, kab
    • Add mapping es<>es-ES
    • state
    • Does not show es-ES in the list
    • Only appears if you do add,sync,state
  • After the first warning there is no way to know what languages aren't mapped
    • YOu get WARNING Could not import files for languages: es-ES, kab after first state
    • But subsequently there is no warning
    • We should highlight missing languages always when we issue state, as its a state of the filesystem
  • Adding a missing locale code requires us adding this in admin then doing stuff in cli
    • Should we not have an option to create the language code?
    • That makes it pretty easy to import languages
    • But does require that we have access to language name or that users go and update language
    • Maybe better from a GUI

Adding files

  • When you first setup a project you cannot filter what gets added
    • fetch,state
    • add -P /af/
    • Lists that all files have been added, not just the ones you filtered down to
    • sync
    • Everything gets sync'd i.e. your filter has no impact
  • If you subsequently add a TP and issue the completely wrong path
    • Added fr to FS, fetch, state
    • fr listed
    • pootle fs add -P /es/small-lang/one.lang small-lang
    • All fr files are listed as added

Newer list

  • 'Filesystem backend' dropdown is not sorted alphabetically
  • Command order:
    • pootle fs state mozilla.org_pootle_fs, pootle fs fetch mozilla.org_pootle_fs -- would it not be better to do: pootle fs mozilla.org_pootle_fs fetch, pootle fs mozilla.org_pootle_fs state - much easier on the typing
    • The [options] part of the command can lead to unexpected outcomes. We maybe need to catch options specified in the wrong place to prevent unexpected additions of everything.
  • Adding missing language codes. Once you've selected the language code you can't press Tab to go to the FS code, you have to use the mouse.

Previous list

Haven't rechecked these

  • pootle fs state - should do nothing if you haven’t fetch’ed
  • pootle fs fetch isn’t implemented for localfs, should fail more elegantly
    • not sure about this - localfs has fetch (fka pull) but the base plugin does not
  • pootle fs
    • lists the available fs projects, we should document
    • Lots of warning noise with this command, should eliminate is possible
  • Cache doesn’t seem to expire after a pootle fs sync
    • not sure if this is a localfs thing - worth testing this again
  • Header
    • Meta info has not been updated, i.e. PO-Revision, etc
    • Includes X-Pootle-Path and X-Pootle-Revision which is noise only needed for download
  • When conflict becomes suggestion
    • It simply says “Added suggestion” in timeline and nothing in the actual suggestion, would be good to indicate why the suggestion was added because of a conflict created from Pootle FS
  • poodle fs rm - doesn’t seem to work
  • Looks like fetch subcommand still exists
    • this is now what was fka pull
  • Stats are wrong
    • Even after flushing cache
    • Added files, removed and moved and ended up wth just the one file
    • Stats are double
      • need some more context here - these should be correct
  • Probably want a pager on poodle fs state, or more compact representation of files
  • Sync takes ages on Pootle/locale//.po
  • No way to import langs that are missing in Pootle (well not easily from command line)
  • What happens if things happen while we’re busy
    • Should we prioritise conflict then add new files i.e. do most contentious quickly/frst
  • Adding new language
    • I added Aragonese (an) which wasn’t already there using web ui
    • It wasn’t added, reset cache doesn’t make it appear
      • It is shown on /projects/tutorial2 but its blank (stats) maybe?
    • poodle fs state - nada
    • Could be that my pootle rqworker never actually seems to answer any calls, its heard about an/tutorail2 but didn’t seem to make it happen
  • Can’t rm a file if nothing is in the state i.e. want to rm a language
    • pootle fs rm tutorial2 -p /af/tutorial2/pootle.po <- no work
  • A file is removed and you want to undo that remove
Clone this wiki locally