I'm looking at trello and I see that you're working on automating dump imports into the cluser
cluster
is there anything I can take and push forward on this?
c1e0 has quit
ishaanshah[m]
iliekcomputers: Hi, are you there
iliekcomputers
ishaanshah[m]: hi
pristine__
iliekcomputers: I didn't get the chance to look at Trello but as of now I have enabled downloading and uploading dumps using spark_manage and from here I will be working for the release ( create recording dumps).
iliekcomputers
i've been testing the import PR
pristine__
If you find anything suitable from here to work on, go ahead :(
:) *
iliekcomputers
and it seems to have the incremental import feature, i might have commented a bit too fast.
ishaanshah[m]
It has the incremental feature, but I realized that there is a minor bug in it.
iliekcomputers
is it getting old pages instead of new ones?
ishaanshah[m]
Suppose the user closes the window mid import, then the latest time won't be updated
iliekcomputers
ishaanshah[m]: that's ok for now.
ishaanshah[m]: have you tested the incremental import thing ?
ishaanshah[m]
But if I set the latest import time after each page,
The incremental import would work correctly even if it was cut of mid import
> have you tested the incremental import thing ?
iliekcomputers
ishaanshah[m]: that seems a bit too much. That would mean thousands of extra API requests per full import
ishaanshah[m]
Yes I hav
have*
iliekcomputers
we could however send a request to `latest-import` when the close button is clicked.
however, that seems like a future pr
i would first like tests for this one.
ishaanshah[m]
Ohk, fine.
So should I start looking into writing tests
iliekcomputers
there's a few minor indentation problems in the jsx
if you fix that, i'll merge this.
and then let's follow up with tests for this.
ishaanshah[m]
I will look into it.
Also is the update message thing acceptable now?
iliekcomputers
I think so, I still don't like the fact that we have jsx in the importer.js file to be honest, but we can fix that later.
also
i'm a bit uncomfortable that we've removed a test that tests behaviour for user with non-ascii usernames
I think testing that imports work for those users still work might be a good idea too.
ishaanshah[m]
Good point.
I will look into it
iliekcomputers
thx!
MajorLurker has quit
MajorLurker joined the channel
MajorLurker has quit
shivam-kapila joined the channel
sumedh joined the channel
sumedh has quit
iliekcomputers has quit
iliekcomputers joined the channel
djinni` has quit
djinni` joined the channel
discopatrick has quit
discopatrick joined the channel
defaultxr has quit
prabal has quit
madmouser1 has quit
madmouser1 joined the channel
sumedh joined the channel
sumedh has quit
moufl joined the channel
shivam-kapila has quit
shivam-kapila joined the channel
rdswift
I knew that i18n is regarding internationalization, but I only now realized that it actually stands for 'i' + 18 characters + 'n'. Duh.
rdswift feels like a dummy for not understanding that sooner.