| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This reverts commit d4e4511b19f4126d9271a6e3a8fa2eb716da7e85.
|
| |
|
|
|
|
| |
This reverts commit 1cf126f91eb533783409da95b117207d8c13d9aa.
|
| |
|
| |
|
|\
| |
| |
| | |
OTP-18422 (ERIERL-873)
|
| |\
| | |
| | |
| | | |
'bmk/snmp/agent/20230127/minimize_error_reporting_during_failed_init/ERIERL-873/OTP-18422' into maint
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
<This is a hack>
Tweaked the agent start sequence in order to minimize error
reporting during a failed start (due to net-if issues).
</This is a hack>
Also added a new net-if option in order to change what
otherwise will be an error reporet to an info report.
OTP-18422 (ERIERL-873)
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The <c>size/1</c> BIF is not optimized by the JIT, and its use can
result in worse types for Dialyzer.
When one knows that the value being tested must be a tuple,
<c>tuple_size/1</c> should always be preferred.
When one knows that the value being tested must be a binary,
<c>byte_size/1</c> should be preferred. However, <c>byte_size/1</c> also
accepts a bitstring (rounding up size to a whole number of bytes), so
one must make sure that the call to <c>byte_size/</c> is preceded by a
call to <c>is_binary/1</c> to ensure that bitstrings are rejected. Note
that the compiler removes redundant calls to <c>is_binary/1</c>, so if
one is not sure whether previous code had made sure that the argument is
a binary, it does not harm to add an <c>is_binary/1</c> test immediately
before the call to <c>byte_size/1</c>.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The <c>size/1</c> BIF is not optimized by the JIT, and its use can
result in worse types for Dialyzer.
When one knows that the value being tested must be a tuple,
<c>tuple_size/1</c> should always be preferred.
When one knows that the value being tested must be a binary,
<c>byte_size/1</c> should be preferred. However, <c>byte_size/1</c> also
accepts a bitstring (rounding up size to a whole number of bytes), so
one must make sure that the call to <c>byte_size/</c> is preceded by a
call to <c>is_binary/1</c> to ensure that bitstrings are rejected. Note
that the compiler removes redundant calls to <c>is_binary/1</c>, so if
one is not sure whether previous code had made sure that the argument is
a binary, it does not harm to add an <c>is_binary/1</c> test immediately
before the call to <c>byte_size/1</c>.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
kikofernandez/kiko/snmp/replace-size-by-xxx_size/GH-6681/OTP-18401
snmp: replace size/1 by XXX_size/1
OTP-18401
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
'bmk/snmp/20230103/single_thread_uncaught_crash/ERIERL-904/OTP-18379' into maint
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | |
| | |
| | |
| | | |
'bmk/snmp/20230103/single_thread_uncaught_crash/ERIERL-904/OTP-18379' into maint-25
* bmk/snmp/20230103/single_thread_uncaught_crash/ERIERL-904/OTP-18379:
[snmp] Single threaded agent handle request crash
[snmp] Handle failed vacm lookup
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we are processing a received request (pdu),
handle (catch) possible "crashes".
Previously, for a multi-threaded agent, the worker
(crashing) process was simply restarted (by the master-agent).
But for a single threaded agent, the master agent itself crashed.
OTP-18379
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Handle when we fail to lookup info (mask, type and status)
from the vacmViewTreeFamilyTable table. If this happens, we
will throw noSuchView (instead of crashing).
OTP-18379
|
| | |
|
|\ \
| | |
| | |
| | | |
OTP-18352
|
| | |
| | |
| | |
| | | |
OTP-18352
|
| |/
| |
| |
| | |
OTP-18352
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 'deterministic-build' of https://github.com/TD5/otp:
make: Allow OTP to be built deterministically
compiler: Make test_lib robust to +deterministic
compiler: Make compiler forward +determinsitic flag to epp
compiler: Make yecc respect +deterministic
compiler: Make leex respect +deterministic
compiler: Make asn1ct_gen respect +deterministic
compiler: Make EPP respect +deterministic
OTP-18165
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add a --enable-deterministic-build to the configure script,
which sets ERL_DETERMINISTIC=yes throughout the relevant
Makefiles, which then invoke the relevant build stages with the
+deterministic option.
This addresses absolute paths being included in generated .erl files
and compiled .beam files that resulted in builds from different source
directories generating different artefacts (which is a component of the
issue in erlang#4482).
I think it would make sense to make this the default at some stage, but
I've put the change behind a flag for now to decouple
making deterministic OTP builds possible from making them the default.
Having +deterministic set results in compiler options being
removed from the module info for modules where this options was used.
This may have other implications for users of OTP.
For tests themselves, +determinism is not set, since many test cases
depend on accessing the test module's compilation options, or other
features not available in deterministic mode, in order to configure
themselves. For tests of the determinism feature specifically,
+deterministic must be explicitly passed to the compiler within the
relevant test cases.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add configure option for (default) empty pdu size.
OTP-17115
|
| | |
| | |
| | |
| | |
| | |
| | | |
Define the empty_msg_size based on the empty_pdu_size...
OTP-17115
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Aloow for the 'empty-pdu-size' to be "pre-defined" (by the
compiler).
OTP-17115
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add some comments, mostly to add to the confusion, and test
and debug functions.
OTP-17115
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is an runtime check for how many varbinds can be
included in an get-bulk reponse. In this check an
'empty pdu size' constant is used. This constant
seemed to be too small (21). Increasing to 29 solved the
problem (for this user).
OTP-17115
|
|\ \
| |/
| |
| |
| |
| |
| | |
* maint:
Updated OTP version
Prepare release
Update copyright year
|
| | |
|
|\ \
| |/
| |
| | |
OTP-16559
|
| |
| |
| |
| |
| |
| |
| | |
The point of this is to ensure that it is possible to
use 'socket' sockets.
OTP-16559
|
| | |
|
|\ \
| |/
| |
| |
| | |
* maint:
Compile time no longer available
|
| |
| |
| |
| |
| |
| |
| |
| | |
A few functions still attempted to extract the "compile time"
of each module. This info used to be available when calling
Module:module_info but was removed "a long time ago". A first
removal was done in OTP-15330 and this removes some remaining
leftover cases.
|
|\ \
| | |
| | | |
Fix typos in lib/snmp
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| |/
| |
| |
| | |
* maint:
Update copyright year
|
| | |
|
|\ \
| |/
| |
| | |
OTP-17783
|
| |\
| | |
| | |
| | | |
OTP-17783
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add verbosity printouts at the error case(s).
OTP-17783
|
| | |
| | |
| | |
| | | |
OTP-17783
|
| | |
| | |
| | |
| | | |
OTP-17783
|