Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Number of scripts: 0 #729

Closed
jesus2099 opened this issue Sep 1, 2015 · 20 comments
Closed

Number of scripts: 0 #729

jesus2099 opened this issue Sep 1, 2015 · 20 comments
Labels
bug You've guessed it... this means a bug is reported.

Comments

@jesus2099
Copy link

All (my but not only) scripts seem to have recently vanish.
@jesus2099 jesus2099 changed the title Number of scripts 0 Number of scripts: 0 Sep 1, 2015
@Martii Martii added the bug You've guessed it... this means a bug is reported. label Sep 1, 2015
@Martii
Copy link
Member

Martii commented Sep 1, 2015

Give me a few to investigate this.

Site refs:

@Martii Martii added the expedite Immediate and on the front burner. label Sep 1, 2015
@Martii Martii mentioned this issue Sep 1, 2015
Closed
@Martii
Copy link
Member

Martii commented Sep 1, 2015

I've messaged @sizzlemctwizzle ... I rolled back the commit HEAD on production and it's still only showing minimal pages... he'll have to check out S3 storage which I don't have access to.

@Martii
Copy link
Member

Martii commented Sep 1, 2015

@sizzlemctwizzle
dev currently still has it's full compliment ...

at everyone else... still awaiting to hear back from him... this might take some time if he's not available. Sorry.

Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Sep 1, 2015
Downgrade the two of the three latest deps
6c74244 
* *sanitize-html* shouln't have anything to do with this so leaving as is
* Removing *node_modules* on VPS

May apply to OpenUserJS#729
@Martii Martii mentioned this issue Sep 1, 2015
Merged
@Martii
Copy link
Member

Martii commented Sep 1, 2015

@sizzlemctwizzle
Nada... downgrading the (affected) deps still isn't showing full compliment on local pro and actual production.

@Martii
Copy link
Member

Martii commented Sep 1, 2015

Arggh... so assigning to @sizzlemctwizzle ... I don't know how to fix this... sizzle mentioned that we might drop S3 and move it to production to avoid intermittent S3 issues.

@Martii Martii added the BLOCKING Concentrate on bug fixes primarily. label Sep 1, 2015
@Martii
Copy link
Member

Martii commented Sep 1, 2015

Added blocking since this is definitely blocking... may modify CONTRIBUTING.md to allow the Active Maintainer to add for ESR type situations.

@Martii
Copy link
Member

Martii commented Sep 2, 2015

OH NO!!!!!! :(

@sizzlemctwizzle

Ref: Automattic/mongoose#3326

Martii referenced this issue Sep 2, 2015
@Martii
Merge pull request #727 from Martii/someDepUpdates
1c2546d 
Some dep updates

Auto-merge
@Martii
Copy link
Member

Martii commented Sep 2, 2015

sizzle said that my Hello, World! Unit Test script is present on S3 (I republish that usually after every dep update) sooooooooooo... that probably means that we still have the source at least just no linkage to it yet... at least I hope the source is all there. crosses things

@sizzlemctwizzle
Copy link
Member

The source is still there but the DB is devastated. I have a backup that's about a month old. I forgot to turn on automatic backups. I won't make that mistake again.

@Martii
Copy link
Member

Martii commented Sep 2, 2015

Well a month ago is better than starting from scratch I think. I'd like to keep the published dates intact since that is in the _id currently for scripts. We'll lose the users_(/comments/discussions/script metas/page description changes/etc.)_ added since then as well... they can always resign up though... I'm feeling awful right now... I've added remove (delete) ops to my normal test routines as well.

We'll have to keep this blocking until I remigrate #285 on that DB ... and checkout an older HEAD from here.

@Martii Martii mentioned this issue Sep 2, 2015
Closed
@sizzlemctwizzle
Copy link
Member

It just makes me lose so much faith in mongoose. I mean, who in the hell
can get it that wrong? A method that is supposed to remove one document
from a collection removes ALL of the documents in that collection. It's
just ridiculous.

On Wed, Sep 2, 2015 at 12:07 AM, Marti Martz notifications@github.com
wrote:

Well a month ago is better than starting from scratch I think. I'd like to
keep the published dates intact since that is in the _id currently for
scripts. We'll lose the users added since then as well... they can always
resign up though... I'm feeling awful right now... I've added remove
(delete) ops to my normal test routines as well.

We'll have to keep this blocking until I remigrate #285
#285 on that DB ...
and checkout an older HEAD here.

—
Reply to this email directly or view it on GitHub
#729 (comment)
.

@chacham2
Copy link

chacham2 commented Sep 2, 2015

May i help with any SQL related issues?

I forgot to turn on automatic backups. I won't make that mistake again.

And don't forget to test them once in a while too. Those are 2 mistakes people don;t realize until after they needed them. :)

BTW, oujs is awesome. I hope you get this all cleaned up!

@jscher2000
Copy link

Would it be useful to post a list of scripts that don't have any metadata page, which makes them difficult to find? I haven't noticed that the site exposes any numeric index for simple spidering.

@Martii
Copy link
Member

Martii commented Sep 2, 2015

@chacham2

May i help with any SQL related issues?

Contributing is always welcome... I do have my own opinions on the direction as well as being the Active Maintainer... a lot of my thoughts on direction just changed with this issue too... some didn't.

One thing though is we don't use SQL... it's mongoose or MongoDB.

And don't forget to test them once in a while too.

That is sound advice. Thank you.

@jscher2000

Would it be useful to post a list of scripts that don't have any metadata page, which makes them difficult to find?

I presume these exist and those authors need to come forward and let me know what to look for. I can probably, eventually, be able to look it up... but I need their @name and their username to do this... without this they are orphaned on S3... this is what sizzle means by the "DB is devastated"... we lost all "linkage" due to that dependency deleting the entire collection instead of a single document (record). As I pointed out to @sizzlemctwizzle this could have been horrifically worse had we had a "delete user" option, as suggested in #359, and someone deleted themselves and poof all the users would have gone bye bye including myself. :\

I haven't noticed that the site exposes any numeric index for simple spidering.

SEO is handled differently than GreasyFork (GF) and we use username/scriptname in the route. I'm not real fond of looking at GF links as most of the time they are completely useless by not telling you anything until you visit that site. I'm open to improving SEO rankings but that would be another issue (and milestone at SEO) . I seriously doubt a plus vote will happen from me on changing this gently suggested routing url.

@sizzlemctwizzle
I still can't launch local pro possibly due to what you said at #712 (comment). Since the DB in use is 21ish days old it is pre this comment. I need this access to migrate the DB over the hump to get to 0.2.0 of our project and any manual look ups for those authors that may need their code from S3 slipped in somewhere (probably not the site itself)... so far no one has made any requests yet.

This user for example registered in the last 21ish days but didn't make any requests to be restored script source wise.

@chacham2
Copy link

chacham2 commented Sep 3, 2015

@Martii
I'm not that interested in taking a role, per se, at least not at this point. If SQL is ever required, desired, or seems like it might be nice, i'm willing to help this excellent site.

@Martii
Copy link
Member

Martii commented Sep 3, 2015

not at this point.

We'll be here when you are ready. It's okay to take part in issues as well... it is helpful to get a different perspective on what everyone wants versus what can be delivered. OUJS is, in part, about safer choices instead of closed source and/or forcing unreasonable .user.js engine features out of the way like some sites do.

If SQL is ever required

I'm open to examining this at the node level myself... mongoose is a different type of DB than I'm normally used to (I use "squeekel" myself for some applications ;)... if the benefits outweigh the effort, OUJS as a whole will surely consider it.

@Martii
Copy link
Member

Martii commented Sep 4, 2015

@sizzlemctwizzle
Please confirm we have a working back up of the re-migration later this weekend, unblock this issue, and close at your leisure. TIA

@sizzlemctwizzle
Copy link
Member

Will do.
On Sep 4, 2015 12:37 AM, "Marti Martz" notifications@github.com wrote:

@sizzlemctwizzle https://github.com/sizzlemctwizzle
Please confirm we have a working back up of the re-migration later this
weekend, unblock this issue, and close at your leisure. TIA

—
Reply to this email directly or view it on GitHub
#729 (comment)
.

@Martii Martii removed the expedite Immediate and on the front burner. label Sep 17, 2015
@sizzlemctwizzle sizzlemctwizzle removed the BLOCKING Concentrate on bug fixes primarily. label Oct 3, 2015
@sizzlemctwizzle
Copy link
Member

Confirmed that we have one backup (created at midnight UTC) per day for the last 7 days. It is fairly easy to restore from one of these backups.

@Martii
Copy link
Member

Martii commented Oct 3, 2015

Gratsi! :)

@OpenUserJS OpenUserJS locked as resolved and limited conversation to collaborators Apr 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug You've guessed it... this means a bug is reported.
Milestone
No milestone
Development

No branches or pull requests
5 participants
@sizzlemctwizzle @Martii @jesus2099 @jscher2000 @chacham2