Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 10 of 774 for Errorfs (0.06 seconds)

  1. internal/config/errors-utils.go

    	// If this is already a Err, do nothing
    	if e, ok := err.(Err); ok {
    		return e
    	}
    
    	// Show a generic message for known golang errors
    	if errors.Is(err, syscall.EADDRINUSE) {
    		return ErrPortAlreadyInUse(err).Msg("Specified port is already in use")
    	} else if errors.Is(err, syscall.EACCES) || errors.Is(err, syscall.EPERM) {
    		if netErr, ok := err.(*net.OpError); ok {
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Aug 29 02:39:48 GMT 2025
    - 3.8K bytes
    - Click Count (0)
  2. docs/es/docs/tutorial/handling-errors.md

    Los códigos de estado en el rango de 400 significan que hubo un error por parte del cliente.
    
    ¿Recuerdas todos esos errores de **"404 Not Found"** (y chistes)?
    
    ## Usa `HTTPException` { #use-httpexception }
    
    Para devolver responses HTTP con errores al cliente, usa `HTTPException`.
    
    ### Importa `HTTPException` { #import-httpexception }
    
    {* ../../docs_src/handling_errors/tutorial001_py39.py hl[1] *}
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 9.7K bytes
    - Click Count (0)
  3. cmd/typed-errors.go

    package cmd
    
    import (
    	"errors"
    )
    
    // errInvalidArgument means that input argument is invalid.
    var errInvalidArgument = errors.New("Invalid arguments specified")
    
    // errMethodNotAllowed means that method is not allowed.
    var errMethodNotAllowed = errors.New("Method not allowed")
    
    // errSignatureMismatch means signature did not match.
    var errSignatureMismatch = errors.New("Signature does not match")
    
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Apr 16 07:34:24 GMT 2025
    - 5.9K bytes
    - Click Count (1)
  4. docs/en/docs/tutorial/handling-errors.md

    # Handling Errors { #handling-errors }
    
    There are many situations in which you need to notify an error to a client that is using your API.
    
    This client could be a browser with a frontend, a code from someone else, an IoT device, etc.
    
    You could need to tell the client that:
    
    * The client doesn't have enough privileges for that operation.
    * The client doesn't have access to that resource.
    * The item the client was trying to access doesn't exist.
    * etc.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 9K bytes
    - Click Count (0)
  5. cmd/api-errors.go

    }
    
    // toAPIErrorCode - Converts embedded errors. Convenience
    // function written to handle all cases where we have known types of
    // errors returned by underlying layers.
    func toAPIErrorCode(ctx context.Context, err error) (apiErr APIErrorCode) {
    	if err == nil {
    		return ErrNone
    	}
    
    	// Errors that are generated by net.Conn and any context errors must be handled here.
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Apr 16 07:34:24 GMT 2025
    - 93K bytes
    - Click Count (3)
  6. internal/config/errors.go

    //
    // You should have received a copy of the GNU Affero General Public License
    // along with this program.  If not, see <http://www.gnu.org/licenses/>.
    
    package config
    
    // UI errors
    var (
    	ErrInvalidXLValue = newErrFn(
    		"Invalid drive path",
    		"Please provide a fresh drive for single drive MinIO setup",
    		"MinIO only supports fresh drive paths",
    	)
    
    	ErrInvalidBrowserValue = newErrFn(
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 9.4K bytes
    - Click Count (0)
  7. docs/ru/docs/tutorial/handling-errors.md

    # Обработка ошибок { #handling-errors }
    
    Существует множество ситуаций, когда необходимо сообщить об ошибке клиенту, использующему ваш API.
    
    Таким клиентом может быть браузер с фронтендом, чужой код, IoT-устройство и т.д.
    
    Возможно, вам придется сообщить клиенту о следующем:
    
    * Клиент не имеет достаточных привилегий для выполнения данной операции.
    * Клиент не имеет доступа к данному ресурсу.
    * Элемент, к которому клиент пытался получить доступ, не существует.
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 14.1K bytes
    - Click Count (0)
  8. docs/de/docs/tutorial/handling-errors.md

    # Fehler behandeln { #handling-errors }
    
    Es gibt viele Situationen, in denen Sie einem Client, der Ihre API nutzt, einen Fehler mitteilen müssen.
    
    Dieser Client könnte ein Browser mit einem Frontend sein, ein Code von jemand anderem, ein IoT-Gerät usw.
    
    Sie könnten dem Client mitteilen müssen, dass:
    
    * Der Client nicht genügend Berechtigungen für diese Operation hat.
    * Der Client keinen Zugriff auf diese Ressource hat.
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 10.4K bytes
    - Click Count (0)
  9. docs/pt/docs/tutorial/handling-errors.md

    # Manipulação de erros { #handling-errors }
    
    Há diversas situações em que você precisa notificar um erro a um cliente que está utilizando a sua API.
    
    Esse cliente pode ser um browser com um frontend, o código de outra pessoa, um dispositivo IoT, etc.
    
    Pode ser que você precise comunicar ao cliente que:
    
    * O cliente não tem direitos para realizar aquela operação.
    * O cliente não tem acesso aquele recurso.
    * O item que o cliente está tentando acessar não existe.
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 10.2K bytes
    - Click Count (0)
  10. docs/uk/docs/tutorial/handling-errors.md

    Marcelo Trylesinski <******@****.***> 1760204929 +0100
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Sat Oct 11 17:48:49 GMT 2025
    - 13.9K bytes
    - Click Count (0)
Back to Top