gphotosuploader | Unofficial Google Photos uploader and Go library | File Upload library

by simonedegiacomi Go Version: Current License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | gphotosuploader Summary

gphotosuploader is a Go library typically used in User Interface, File Upload applications. gphotosuploader has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Google Photos does not have a desktop uploader for Linux, ~~neither an API to upload a photo programmatically.~~ (now there is an Official Google Photos API). G Photos Uploader lets you upload photos from Linux (and, in theory, any OS for which you can compile a Go program) specifying the file name or watching a directory for changes. Furthermore, the project can also be used as a library that you can include in other Go programs.

Support

Quality

Security

License

Reuse

Support

gphotosuploader has a low active ecosystem.

It has 91 star(s) with 31 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

There are 8 open issues and 18 have been closed. On average issues are closed in 23 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of gphotosuploader is current.

Quality

gphotosuploader has 0 bugs and 0 code smells.

Security

gphotosuploader has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gphotosuploader code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gphotosuploader is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

gphotosuploader releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed gphotosuploader and discovered the below as its top functions. This is intended to give you an instant insight into gphotosuploader implemented functionality, and help decide if they suit your requirements.

CreateAlbum creates a new album
initAuthentication initializes the authentication cookie credentials .
Main entry point for image upload
EnqueueUpload enqueues a file at the specified path .
handleFileChange is called when a file change occurs .
StartWebDriverCredentialsWizard will start the web browser for the web browser
handleUploaderEvents handles uploader events .
Parse CLI arguments
instructUserAndWaitForLogin waits for the user to complete .
NewUpload creates a new Upload .

Get all kandi verified functions for this library.

gphotosuploader Key Features

No Key Features are available at this moment for gphotosuploader.

gphotosuploader Examples and Code Snippets

No Code Snippets are available at this moment for gphotosuploader.

Community Discussions

Trending Discussions on gphotosuploader

Race condition against Google Photos API

QUESTION

Race condition against Google Photos API

Asked 2020-Aug-07 at 07:47

I'm developing this CLI to upload images to Google Photos. The CLI creates several go routines to upload files in parallel 1. Once it's uploaded, the same routine adds it to an Album. These albums are created if they didn't exist before 2.

Due to the concurrency and the fact that Google Photos API allows the creation of two Albums with the same name, I'm having duplicated album names that I'd like to avoid.

The GetOrCreateAlbumByName() 3 doesn't ensure that the Album is unique. It basically ask if an album exists with the same name and if not, it will create a new one. But this function could be called in parallel so two Album with the same name could be created. Besides it's implementing a mutex, I'm observing duplicates.

How would yo recommend to deal with that?

Create a Worker (like a microservice) that deal with album creation. Each go routine will be blocked until the album is created. It will remove concurrency on the Album creation part.
Maintain an album cache and use it to check if the album has been already created. In that case, race condition could happen too, but with less probability.
Using 1 and 2 together.
Other, please specify.

I have concerns about 1, 2 and 3... that's why I would like to know how you would deal with that.

Thanks in advance

...

ANSWER

Answered 2020-Aug-07 at 07:47

You use Client.GetOrCreateAlbumByName() to get or create albums. This method is safe for concurrent use, and it uses a mutex internally to serialize calls, which ensures duplicates are not created.

However, you are creating and using multiple clients here, which means concurrent calls to all of them is not serialized, only concurrent calls to individual clients.

So the solution to either use a single client, then all calls will be serialized, or if that's not possible, you have to serialize calls to all clients, e.g. using a single mutex or other means.

An example how to serialize calls to all clients with a mutex:

Source https://stackoverflow.com/questions/63278929

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gphotosuploader

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: