~petersanchez

Los Angeles, CA

https://www.petersanchez.com

LA, CA USA - Managua, Nicaragua

Trackers

~petersanchez/gohome

Last active 1 year, 2 months ago

~petersanchez/tago

Last active 1 year, 2 months ago

~petersanchez/django-impersonate

Last active 1 year, 5 months ago

~petersanchez/honk

Last active 2 years ago

~petersanchez/migrate

Last active 2 years ago

~petersanchez/carrier

Last active 3 years ago

~petersanchez/djeploy

Last active 4 years ago

~petersanchez/djpubsubhubbub

Last active 4 years ago

#101 Change title length limit to > 150 characters 5 days ago

Comment by ~petersanchez on ~netlandish/links

Peter Sanchez referenced this ticket in commit 9ac75f7.

REPORTED RESOLVED IMPLEMENTED

#101 Change title length limit to > 150 characters 6 days ago

Ticket created by ~petersanchez on ~netlandish/links

Why we did a 150 character limit is beyond me. This needs to be updated to say 300 or maybe more.

#100 Add periodic task to process pending BaseURL instance 6 days ago

Comment by ~petersanchez on ~netlandish/links

REPORTED RESOLVED IMPLEMENTED

#100 Add periodic task to process pending BaseURL instance 6 days ago

task added by ~petersanchez on ~netlandish/links

#100 Add periodic task to process pending BaseURL instance 12 days ago

Ticket created by ~petersanchez on ~netlandish/links

It's possible that when attempting to fetch a saved bookmark that there is an error fetching the link metadata. Instead of trying to fetch it again right away we should create a process to automatically try again, periodically, and in bulk jobs.

My thinking is we have a job that runs every hour and processes say 1500 pending BaseURL's at a time. We will add 3 new fields to the base_url table.

  • error_count - the number of times we've had an error fetching the url
  • last_error_date - The last time we attempted to fetch the url
  • metadata - A JSONB array to store error messages and dates

We set a max limit to error count to say 3. The periodic task will look for entries that have public_ready=false, error count of greater than 0 and less than 3, and that the last error attempt happened 24+ hours ago. Then it will process it again and update the error date and error log if it fails again.

After 3 error attempts we just never process that link again as it's probably a bad link or just not worth the continued effort.

#99 Mattermost: Upgrade to mattermost v10 will (probably) require a rewrite of the integration 15 days ago

task added by ~petersanchez on ~netlandish/links

#98 Dep: minio v7.0.87 causes issues with mattermost-server 15 days ago

bug added by ~petersanchez on ~netlandish/links

#99 Mattermost: Upgrade to mattermost v10 will (probably) require a rewrite of the integration 15 days ago

Ticket created by ~petersanchez on ~netlandish/links

The module has moved from github.com/mattermost/mattermost-server to github.com/mattermost/mattermost/server

Also Mattermost apps have changed completely on the MM side.

Ref: https://forum.mattermost.com/t/transition-from-apps-framework-to-plugin-framework-in-mattermost-v10/19330

Ref: #98

#98 Dep: minio v7.0.87 causes issues with mattermost-server 15 days ago

Ticket created by ~petersanchez on ~netlandish/links

In gobwebs, upgrading minio module to v7.0.87 (current latest) causes the build in links to fail:

# github.com/mattermost/mattermost-server/v6/shared/filestore
../../src/go/pkg/mod/github.com/mattermost/mattermost-server/v6@v6.6.0/shared/filestore/s3store.go:109:27: cannot use customProvider{…} (value of type customProvider) as credentials.Provider value in argument to
credentials.New: customProvider does not implement credentials.Provider (missing method RetrieveWithCredContext)
make: *** [Makefile:16: links] Error 1

I don't see why as I can't see where minio client is updating anything with the mattermost-code which depends on the aws sdk.

Either way I think mattermost needs to be updated to v10. See #99 for reference.

#97 Import: large json files are failing during processing 15 days ago

Comment by ~petersanchez on ~netlandish/links

Peter Sanchez referenced this ticket in commit 63b52bd.

REPORTED RESOLVED FIXED