I'm seeing this warning:
(UndefinedFunctionError) function :ssl.cipher_suites/0 is undefined or private
My application is crashing with this warning.
I recently upgraded Elixir and Erlang using asdf. How do I start my application now?
This Erlang page says:
Functions Deprecated in OTP 21
ssl:cipher_suites/0 (use cipher_suites/2,3 instead)
ssl:cipher_suites/1 (use cipher_suites/2,3 instead)
At the time of writing, the
I got it to work by changing the function call to:
:ssl.cipher_suites(:all, :"tlsv1.3")
Reference: Erlang manual for cipher_suites/23
Related
constructor FBSDKPackage in class FBSDKPackage
cannot be applied to given types;
new FBSDKPackage(mCallbackManager),
^
required: no arguments
found: CallbackManager
reason: actual and formal argument lists differ in length
1 error
https://github.com/facebook/react-native-fbsdk/issues/429
have tried all solutions in the above link and still facing same issue
react-native: 0.59.9
If you use the latest version of react-native-fbsdk you will no longer to have pass the callbackManager to the constructor and the reason I strongly recommend you to upgrade it is that's the requirement of facebook to Upgrade to SDK v5.0 for new privacy features and the previous versions will stop working.
I have been trying to to generate a release version.
but I get this strange exception:
ReactNativeJS: Requiring unknown module "NativeModules"
and right after it I get :
Module AppRegistry is not a registered callable module (calling runApplication)
In my debug version everything works fine.
I have tried to checkout to the previous working commit.
and try to generate a version from it, but it fails with the same error.
maybe npm related issue ?
The problem was with a library Called rn-host-detect that reactotron-react-native was using ...
I have sent a message to the author of the and he fixed it.
removing my node_modules and npm install again solved the issue.
I'm on OS X 10.11.1 running the latest version of X Code. I installed Lua 5.3 today from source with no problem. Seems to work correctly. No errors installing luarocks and then using it to install moonscript. However, both moon and moonc give the following error when invoked from the command line:
$ moon
/usr/local/bin/lua: /usr/local/share/lua/5.3/alt_getopt.lua:24: attempt to call a nil value (global 'module')
stack traceback:
/usr/local/share/lua/5.3/alt_getopt.lua:24: in main chunk
[C]: in function 'require'
/usr/local/lib/luarocks/rocks/moonscript/0.4.0-1/bin/moon:2: in main chunk
[C]: in ?
Looking at alt_getopt.lua shows that it is indeed using the now-defunct 'module' keyword. The GitHub project for this module appears to be dead with no action in the past 3 years.
How should I proceed to get Moonscript working on my system?
Yes, as you noted, module has been deprecated for quite a while and was only working with earlier versions because of compatibility switches.
You can comment out the line 24 in alt-getopt and add the following line to the end of the alt-getopt.lua file: return {get_opts = get_opts, get_ordered_opts = get_ordered_opts}.
This should make this module Lua 5.2/5.3 compatible (I haven't checked if there are any other compatibility issues with using Lua 5.3 though).
Next compiles well
-module(cipher_id).
-export([a1/1]).
a1(I) ->
binary:encode_unsigned(I).
But then i try to call cipher_id:a1(I) it crashes with
** exception error: undefined function binary:encode_unsigned/1
The same happened if try to call function from binary module in erl shell. m() outputs lists in which no binary module present.
From the Erlang documentation of the binary module:
The module is implemented according to the EEP (Erlang Enhancement Proposal) 31.
From the proposal page:
Status: Final/R14A Proposal is implemented in OTP release R14A
You're using R13B03. My feeling is that you need to upgrade to a newer Erlang installation. Binaries for Ubuntu are available at:
http://www.erlang-solutions.com/section/132/erlang-otp-packages
I'm using the c++ crypto library called Botan, and at arbitrary times I am getting the following error at runtime. What does it mean?
terminate called after throwing an instance of 'Botan::PRNG_Unseeded'
what(): Botan: PRNG not seeded: X9.31(AES-256)
I ran into the same error message, which was caused by missing any entropy source.
You can try to enable a entropy source when building Botan library or generating single source file.
For windows platform, add win32_stats module into option --enable-modules. For linux, use dev_random.
e.g. configure.py --enable-modules=win32_stats,...
Well it looks to me like you forgot to seed the PRNG (pseudo random number generator). Having failed to do so, the Botan library threw the aforementioned exception which seems to have caused the terminate function to be called.
The most likely answer is that you are using v 1.8.2 which had problems with its autoseeding routines. Upgrading to 1.8.4 or 1.8.5 has fixed this for everyone who had reported this problem up to now.