Home
last modified time | relevance | path

Searched refs:error (Results 26 – 50 of 59) sorted by relevance

123

/libuv/docs/src/
H A Dtcp.rst88 ``UV_ETIMEDOUT`` error passed to the corresponding callback.
109 error from :c:func:`uv_listen` or :c:func:`uv_tcp_connect` unless you specify
126 :returns: 0 on success, or an error code < 0 on failure.
133 this function will return an UV_ENOTSUP error.
158 connection error happened.
H A Dstream.rst39 `nread` is > 0 if there is data available or < 0 on error. When we've
45 `nread` might be 0, which does *not* indicate an error or EOF. This
48 The callee is responsible for stopping/closing the stream when an error happens
54 on error.
126 be initialized. < 0 return value indicates an error.
208 * < 0: negative error code (``UV_EAGAIN`` is returned if no data can be sent
H A Dpoll.rst26 active poll handle. This can cause the handle to report an error,
100 If an error happens while polling, `status` will be < 0 and corresponds
101 with one of the `UV_E*` error codes (see :ref:`errors`). The user should
103 anyway, the callback *may* be called reporting an error status, but this is
H A Dfs_poll.rst27 or the error reason changes).
64 by the user. Returns 0 on success or an error code < 0 in case of failure.
H A Dmigration_010_100.rst48 to fetch the error code, which was a positive number.
50 In 1.0, functions and status parameters contain the actual error code, which is 0 for success, or
51 a negative number in case of error.
H A Ddns.rst81 Returns 0 on success or an error code < 0 on failure. If successful, the
101 Returns 0 on success or an error code < 0 on failure. If successful, the
H A Dfs.rst193 Result of the request. < 0 means error, success otherwise. On requests such
381 support copy-on-write, or an error occurs while attempting to use
386 not support copy-on-write, or an error occurs while attempting to use
387 copy-on-write, then an error is returned.
390 If the destination path is created, but an error occurs while copying
400 .. versionchanged:: 1.33.0 If an error occurs while using
401 `UV_FS_COPYFILE_FICLONE_FORCE`, that error is returned. Previously,
506 Returns the platform specific error code - `GetLastError()` value on Windows
600 with the error `EBUSY`.
H A Dhandle.rst60 a ``UV_ENOBUFS`` error will be triggered in the :c:type:`uv_udp_recv_cb` or the
199 On success, zero is returned. On error, a negative result is
216 On success, zero is returned. On error, a negative result is
H A Dmisc.rst52 error. The `buf` pointer is the same pointer that was passed to
329 .. versionchanged:: 1.39.0 now returns an error if `uv_setup_args` is needed
344 .. versionchanged:: 1.39.0 now returns an error if `uv_setup_args` is needed
452 and :man:`inet_pton(3)`. On success they return 0. In case of error
469 terminator byte from `*size`. On error, a negative result is
830 zero on success, and a non-zero error value otherwise.
848 available, a non-zero error value is returned or passed to the callback.
869 :returns: 0 on success, or an error code < 0 on failure. The contents of
870 `buf` is undefined after an error.
H A Dpipe.rst82 flag is specified, in which case an ``UV_EINVAL`` error is returned.
112 flag is specified, in which case an ``UV_EINVAL`` error is returned.
H A Drequest.rst69 Returns 0 on success, or an error code < 0 on failure.
H A Dprocess.rst227 This is not supported on Windows, :c:func:`uv_spawn` will fail and set the error
261 negative error code corresponding to the reason it couldn't spawn is
/libuv/src/win/
H A Dreq-inl.h34 #define SET_REQ_ERROR(req, error) \ argument
35 SET_REQ_STATUS((req), NTSTATUS_FROM_WIN32((error)))
H A Dprocess.c555 goto error; in make_program_args()
562 goto error; in make_program_args()
593 error: in make_program_args()
/libuv/
H A DCMakeLists.txt200 src/win/error.c
544 test/test-error.c
590 test/test-pipe-bind-error.c
592 test/test-pipe-connect-error.c
631 test/test-tcp-bind-error.c
632 test/test-tcp-bind6-error.c
638 test/test-tcp-connect-error-after-write.c
639 test/test-tcp-connect-error.c
641 test/test-tcp-connect6-error.c
653 test/test-tcp-try-write-error.c
[all …]
/libuv/src/unix/
H A Dos390-syscalls.c60 goto error; in scandir()
66 goto error; in scandir()
82 error: in scandir()
H A Dcore.c1695 goto error; in uv_os_uname()
1700 goto error; in uv_os_uname()
1710 goto error; in uv_os_uname()
1715 goto error; in uv_os_uname()
1720 goto error; in uv_os_uname()
1729 goto error; in uv_os_uname()
1733 error: in uv_os_uname()
H A Dthread.c735 goto error; in uv_cond_init()
739 error: in uv_cond_init()
H A Dfs.c602 goto error; in uv__fs_opendir()
606 goto error; in uv__fs_opendir()
611 error: in uv__fs_opendir()
635 goto error; in uv__fs_readdir()
646 goto error; in uv__fs_readdir()
654 error: in uv__fs_readdir()
/libuv/docs/src/guide/
H A Dfilesystem.rst21 callback is null. The return value of functions is a :ref:`libuv error code
22 <libuv-error-handling>`. This is usually only useful for synchronous calls.
237 The read callback ``nread`` parameter is less than 0 on any error. This error
245 allocate memory. In this case, the read callback is invoked with error
334 #. ``int status`` - If ``status < 0``, there is an :ref:`libuv error<libuv-error-handling>`.
H A Dthreads.rst91 functions will return 0 on success, and an error code otherwise.
94 ``uv_mutex_lock()`` and ``uv_mutex_unlock()`` will ``abort()`` on error.
95 Similarly ``uv_mutex_trylock()`` will abort if the error is anything *other
101 The default BSD mutex implementation will raise an error if a thread which has
112 return an error in the second call to ``uv_mutex_lock()``.
H A Deventloops.rst39 there is an error, without having to ensure that all handlers are stopped one
H A Dutilities.rst54 old ``repeat`` value. If the timer hasn't been started it fails (error code
79 exit paths or error scenarios. Or you want the program to exit when all your
359 ``uv_lib_t`` pointer. It returns 0 on success, -1 on error. Use ``uv_dlerror``
360 to get the error message.
/libuv/.github/workflows/
H A Dsanitizer.yml56 # TSan exits with an error when it can't find the file.
/libuv/docs/
H A DMakefile14 $(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set t…

Completed in 94 milliseconds

123