mirror of
https://github.com/stashapp/stash.git
synced 2025-12-06 08:26:00 +01:00
87709fd018
* Avoid redundant logging in migrations
Return the error and let the caller handle the logging of the error if
needed.
While here, defer m.Close() to the function boundary.
* Treat errors as values
Use %v rather than %s and pass the errors directly.
* Generate a wrapped error on stat-failure
* Log 3 unchecked errors
Rather than ignore errors, log them at
the WARNING log level.
The server has been functioning without these, so assume they are not at
the ERROR level.
* Propagate errors upward
Failure in path generation was ignored. Propagate the errors upward the
call stack, so it can be handled at the level of orchestration.
* Warn on errors
Log errors rather than quenching them.
Errors are logged at the Warn-level for now.
* Check error when creating test databases
Use the builtin log package and stop the program fatally on error.
* Add warnings to uncheck task errors
Focus on the task system in a single commit, logging unchecked
errors as warnings.
* Warn-on-error in API routes
Look through the API routes, and make sure errors are being logged if
they occur. Prefer the Warn-log-level because none of these has proven
to be fatal in the system up until now.
* Propagate error when adding Util API
* Propagate error on adding util API
* Return unhandled error
* JS log API: propagate and log errors
* JS Plugins: log GQL addition failures.
* Warn on failure to write to stdin
* Warn on failure to stop task
* Wrap viper.BindEnv
The current viper code only errors if no name is provided, so it should
never fail. Rewrite the code flow to factor through a panic-function.
This removes error warnings from this part of the code.
* Log errors in concurrency test
If we can't initialize the configuration, treat the test as a failure.
* Warn on errors in configuration code
* Plug an unchecked error in gallery zip walking
* Warn on screenshot serving failure
* Warn on encoder screenshot failure
* Warn on errors in path-handling code
* Undo the errcheck on configurations for now.
* Use one-line initializers where applicable
rather than using
err := f()
if err!= nil { ..
prefer the shorter
if err := f(); err != nil { ..
If f() isn't too long of a name, or wraps a function with a body.
55 lines
1,008 B
Go
55 lines
1,008 B
Go
package utils
|
|
|
|
import (
|
|
"crypto/md5"
|
|
"crypto/rand"
|
|
"fmt"
|
|
"hash/fnv"
|
|
"io"
|
|
"os"
|
|
|
|
"github.com/stashapp/stash/pkg/logger"
|
|
)
|
|
|
|
func MD5FromBytes(data []byte) string {
|
|
result := md5.Sum(data)
|
|
return fmt.Sprintf("%x", result)
|
|
}
|
|
|
|
func MD5FromString(str string) string {
|
|
data := []byte(str)
|
|
return MD5FromBytes(data)
|
|
}
|
|
|
|
func MD5FromFilePath(filePath string) (string, error) {
|
|
f, err := os.Open(filePath)
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
defer f.Close()
|
|
|
|
return MD5FromReader(f)
|
|
}
|
|
|
|
func MD5FromReader(src io.Reader) (string, error) {
|
|
h := md5.New()
|
|
if _, err := io.Copy(h, src); err != nil {
|
|
return "", err
|
|
}
|
|
checksum := h.Sum(nil)
|
|
return fmt.Sprintf("%x", checksum), nil
|
|
}
|
|
|
|
func GenerateRandomKey(l int) string {
|
|
b := make([]byte, l)
|
|
if n, err := rand.Read(b); err != nil {
|
|
logger.Warnf("failure generating random key: %v (only read %v bytes)", err, n)
|
|
}
|
|
return fmt.Sprintf("%x", b)
|
|
}
|
|
|
|
func IntFromString(str string) uint64 {
|
|
h := fnv.New64a()
|
|
h.Write([]byte(str))
|
|
return h.Sum64()
|
|
}
|