 IMPORTANT: If opening a ticket, please include this information.

  - ID: dpapick
    SLS: sift.python-packages.dpapick
    Run#: 177
    Comment: Failed to install packages: dpapick. Error: Collecting dpapick

Downloading https://files.pythonhosted.org/packages/44/5a/066f5d9791d3799a0d2cd52b44cfe9caecefa7be14013ceb79953d13014b/dpapick-0.3-py2-none-any.whl
Collecting pyasn1>=0.1.7 (from dpapick)
Downloading https://files.pythonhosted.org/packages/7b/7c/c9386b82a25115cccf1903441bba3cbadcfae7b678a20167347fa8ded34c/pyasn1-0.4.5-py2.py3-none-any.whl (73kB)
Collecting M2Crypto>=0.21.1 (from dpapick)
Downloading https://files.pythonhosted.org/packages/52/e3/85f7ad64cd50b4c361b6533baeaa4d3919087993f24a93b34ae841a42628/M2Crypto-0.33.0.tar.gz (1.3MB)
Collecting CFPropertyList (from dpapick)
Downloading https://files.pythonhosted.org/packages/23/19/9b54460b5bc841a122672e7e25147f40b74320c683876a93b8c193d8b608/CFPropertyList-0.0.1.tar.gz
Collecting python-registry>=1.0.4 (from dpapick)
Downloading https://files.pythonhosted.org/packages/d6/19/a710a8509b4aa02b49cdf7bc992d0c03699b8a2d09b7dfee80005068b6df/python-registry-1.0.4.tar.gz
Collecting typing (from M2Crypto>=0.21.1->dpapick)
Downloading https://files.pythonhosted.org/packages/cc/3e/29f92b7aeda5b078c86d14f550bf85cff809042e3429ace7af6193c3bc9f/typing-3.6.6-py2-none-any.whl
Collecting enum34 (from python-registry>=1.0.4->dpapick)
Downloading https://files.pythonhosted.org/packages/c5/db/e56e6b4bbac7c4a06de1c50de6fe1ef3810018ae11732a50f15f62c7d050/enum34-1.1.6-py2-none-any.whl
Installing collected packages: pyasn1, typing, M2Crypto, CFPropertyList, enum34, python-registry, dpapick
Found existing installation: pyasn1 0.1.9
Not uninstalling pyasn1 at /usr/lib/python2.7/dist-packages, outside environment /usr
Running setup.py install for M2Crypto: started
Running setup.py install for M2Crypto: finished with status 'error'
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-bIiHgu/M2Crypto/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /tmp/pip-yGfxsu-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
copying M2Crypto/RSA.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/DSA.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/BN.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/httpslib.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/AuthCookie.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/m2crypto.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/DH.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/RC4.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/Rand.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/EC.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/six.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/ftpslib.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/Err.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/threading.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/m2urllib.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/m2.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/util.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/callback.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/m2urllib2.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/Engine.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/ASN1.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/SMIME.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/X509.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/BIO.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/EVP.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/init.py -> build/lib.linux-x86_64-2.7/M2Crypto
copying M2Crypto/m2xmlrpclib.py -> build/lib.linux-x86_64-2.7/M2Crypto
creating build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/Connection.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/Cipher.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/Context.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/timeout.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/ssl_dispatcher.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/Session.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/Checker.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/TwistedProtocolWrapper.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/SSLServer.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/cb.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
copying M2Crypto/SSL/init.py -> build/lib.linux-x86_64-2.7/M2Crypto/SSL
running build_ext
building 'M2Crypto._m2crypto' extension
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/SWIG
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -I/tmp/pip-build-bIiHgu/M2Crypto/SWIG -c SWIG/_m2crypto_wrap.c -o build/temp.linux-x86_64-2.7/SWIG/_m2crypto_wrap.o -Wno-deprecated-declarations -DTHREADING
SWIG/_m2crypto_wrap.c:4754:0: warning: "PyUnicode_FromString" redefined
#define PyUnicode_FromString(x) PyString_FromString(x)
^
In file included from /usr/include/python2.7/Python.h:85:0,
from SWIG/_m2crypto_wrap.c:151:
/usr/include/python2.7/unicodeobject.h:281:0: note: this is the location of the previous definition
# define PyUnicode_FromString PyUnicodeUCS4_FromString
^
SWIG/_m2crypto_wrap.c:4755:0: warning: "PyUnicode_Format" redefined
#define PyUnicode_Format(x, y) PyString_Format(x, y)
^
In file included from /usr/include/python2.7/Python.h:85:0,
from SWIG/_m2crypto_wrap.c:151:
/usr/include/python2.7/unicodeobject.h:275:0: note: this is the location of the previous definition
# define PyUnicode_Format PyUnicodeUCS4_Format
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_num':
SWIG/_m2crypto_wrap.c:9882:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9882:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9882:26: note: each undeclared identifier is reported only once for each function it appears in
SWIG/_m2crypto_wrap.c:9882:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9893:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:9894:17: warning: implicit declaration of function 'OPENSSL_sk_num' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_num((struct stack_st const *)arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_value':
SWIG/_m2crypto_wrap.c:9904:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9904:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9904:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9919:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:9925:20: warning: implicit declaration of function 'OPENSSL_sk_value' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_value((struct stack_st const *)arg1,arg2);
^
SWIG/_m2crypto_wrap.c:9925:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_value((struct stack_st const *)arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_set':
SWIG/_m2crypto_wrap.c:9935:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9935:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9935:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:9953:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:9963:20: warning: implicit declaration of function 'OPENSSL_sk_set' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_set(arg1,arg2,(void const *)arg3);
^
SWIG/_m2crypto_wrap.c:9963:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_set(arg1,arg2,(void const *)arg3);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_new':
SWIG/_m2crypto_wrap.c:9973:3: error: unknown type name 'OPENSSL_sk_compfunc'
OPENSSL_sk_compfunc arg1 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:9973:31: error: 'OPENSSL_sk_compfunc' undeclared (first use in this function)
OPENSSL_sk_compfunc arg1 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:9973:52: error: expected ',' or ';' before numeric constant
OPENSSL_sk_compfunc arg1 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:9975:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *result = 0 ;
^
SWIG/_m2crypto_wrap.c:9984:13: error: 'OPENSSL_STACK' undeclared (first use in this function)
result = (OPENSSL_STACK *)OPENSSL_sk_new(arg1);
^
SWIG/_m2crypto_wrap.c:9984:28: error: expected expression before ')' token
result = (OPENSSL_STACK *)OPENSSL_sk_new(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_new_null':
SWIG/_m2crypto_wrap.c:9994:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *result = 0 ;
^
SWIG/_m2crypto_wrap.c:9997:13: error: 'OPENSSL_STACK' undeclared (first use in this function)
result = (OPENSSL_STACK *)OPENSSL_sk_new_null();
^
SWIG/_m2crypto_wrap.c:9997:28: error: expected expression before ')' token
result = (OPENSSL_STACK *)OPENSSL_sk_new_null();
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_free':
SWIG/_m2crypto_wrap.c:10007:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10007:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10007:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10017:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10018:3: warning: implicit declaration of function 'OPENSSL_sk_free' [-Wimplicit-function-declaration]
OPENSSL_sk_free(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_pop_free':
SWIG/_m2crypto_wrap.c:10028:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10028:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10028:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10040:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10047:3: warning: implicit declaration of function 'OPENSSL_sk_pop_free' [-Wimplicit-function-declaration]
OPENSSL_sk_pop_free(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_deep_copy':
SWIG/_m2crypto_wrap.c:10057:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10057:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10057:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10058:3: error: unknown type name 'OPENSSL_sk_copyfunc'
OPENSSL_sk_copyfunc arg2 = (OPENSSL_sk_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10058:31: error: 'OPENSSL_sk_copyfunc' undeclared (first use in this function)
OPENSSL_sk_copyfunc arg2 = (OPENSSL_sk_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10058:52: error: expected ',' or ';' before numeric constant
OPENSSL_sk_copyfunc arg2 = (OPENSSL_sk_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10059:3: error: unknown type name 'OPENSSL_sk_freefunc'
OPENSSL_sk_freefunc arg3 = (OPENSSL_sk_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10059:31: error: 'OPENSSL_sk_freefunc' undeclared (first use in this function)
OPENSSL_sk_freefunc arg3 = (OPENSSL_sk_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10059:52: error: expected ',' or ';' before numeric constant
OPENSSL_sk_freefunc arg3 = (OPENSSL_sk_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10065:18: error: 'result' undeclared (first use in this function)
OPENSSL_STACK *result = 0 ;
^
SWIG/_m2crypto_wrap.c:10072:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10085:28: error: expected expression before ')' token
result = (OPENSSL_STACK *)OPENSSL_sk_deep_copy((struct stack_st const *)arg1,arg2,arg3);
^
SWIG/_m2crypto_wrap.c:10057:18: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_insert':
SWIG/_m2crypto_wrap.c:10095:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10095:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10095:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10113:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10123:17: warning: implicit declaration of function 'OPENSSL_sk_insert' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_insert(arg1,(void const *)arg2,arg3);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_delete':
SWIG/_m2crypto_wrap.c:10133:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10133:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10133:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10148:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10154:20: warning: implicit declaration of function 'OPENSSL_sk_delete' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_delete(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:10154:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_delete(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_delete_ptr':
SWIG/_m2crypto_wrap.c:10164:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10164:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10164:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10178:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10183:20: warning: implicit declaration of function 'OPENSSL_sk_delete_ptr' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_delete_ptr(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c:10183:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_delete_ptr(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_find':
SWIG/_m2crypto_wrap.c:10193:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10193:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10193:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10207:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10212:17: warning: implicit declaration of function 'OPENSSL_sk_find' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_find(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_find_ex':
SWIG/_m2crypto_wrap.c:10222:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10222:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10222:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10236:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10241:17: warning: implicit declaration of function 'OPENSSL_sk_find_ex' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_find_ex(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_push':
SWIG/_m2crypto_wrap.c:10251:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10251:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10251:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10265:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10270:17: warning: implicit declaration of function 'OPENSSL_sk_push' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_push(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_unshift':
SWIG/_m2crypto_wrap.c:10280:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10280:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10280:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10294:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10299:17: warning: implicit declaration of function 'OPENSSL_sk_unshift' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_unshift(arg1,(void const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_shift':
SWIG/_m2crypto_wrap.c:10309:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10309:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10309:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10320:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10321:20: warning: implicit declaration of function 'OPENSSL_sk_shift' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_shift(arg1);
^
SWIG/_m2crypto_wrap.c:10321:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_shift(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_pop':
SWIG/_m2crypto_wrap.c:10331:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10331:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10331:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10342:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10343:20: warning: implicit declaration of function 'OPENSSL_sk_pop' [-Wimplicit-function-declaration]
result = (void *)OPENSSL_sk_pop(arg1);
^
SWIG/_m2crypto_wrap.c:10343:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (void *)OPENSSL_sk_pop(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_zero':
SWIG/_m2crypto_wrap.c:10353:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10353:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10353:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10363:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10364:3: warning: implicit declaration of function 'OPENSSL_sk_zero' [-Wimplicit-function-declaration]
OPENSSL_sk_zero(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_set_cmp_func':
SWIG/_m2crypto_wrap.c:10374:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10374:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10374:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10375:3: error: unknown type name 'OPENSSL_sk_compfunc'
OPENSSL_sk_compfunc arg2 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10375:31: error: 'OPENSSL_sk_compfunc' undeclared (first use in this function)
OPENSSL_sk_compfunc arg2 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10375:52: error: expected ',' or ';' before numeric constant
OPENSSL_sk_compfunc arg2 = (OPENSSL_sk_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10380:23: error: expected ';' before 'result'
OPENSSL_sk_compfunc result;
^
SWIG/_m2crypto_wrap.c:10387:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10394:3: error: 'result' undeclared (first use in this function)
result = (OPENSSL_sk_compfunc)OPENSSL_sk_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:10394:33: error: expected ';' before 'OPENSSL_sk_set_cmp_func'
result = (OPENSSL_sk_compfunc)OPENSSL_sk_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:10374:18: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_dup':
SWIG/_m2crypto_wrap.c:10404:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10404:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10404:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10408:18: error: 'result' undeclared (first use in this function)
OPENSSL_STACK *result = 0 ;
^
SWIG/_m2crypto_wrap.c:10415:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10416:28: error: expected expression before ')' token
result = (OPENSSL_STACK *)OPENSSL_sk_dup((struct stack_st const *)arg1);
^
SWIG/_m2crypto_wrap.c:10404:18: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_sort':
SWIG/_m2crypto_wrap.c:10426:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10426:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10426:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10436:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10437:3: warning: implicit declaration of function 'OPENSSL_sk_sort' [-Wimplicit-function-declaration]
OPENSSL_sk_sort(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_OPENSSL_sk_is_sorted':
SWIG/_m2crypto_wrap.c:10447:3: error: unknown type name 'OPENSSL_STACK'
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10447:26: error: 'OPENSSL_STACK' undeclared (first use in this function)
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10447:41: error: expected expression before ')' token
OPENSSL_STACK *arg1 = (OPENSSL_STACK *) 0 ;
^
SWIG/_m2crypto_wrap.c:10458:26: error: expected expression before ')' token
arg1 = (OPENSSL_STACK *)(argp1);
^
SWIG/_m2crypto_wrap.c:10459:17: warning: implicit declaration of function 'OPENSSL_sk_is_sorted' [-Wimplicit-function-declaration]
result = (int)OPENSSL_sk_is_sorted((struct stack_st const *)arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_STRING_new':
SWIG/_m2crypto_wrap.c:10522:3: error: unknown type name 'sk_OPENSSL_STRING_compfunc'
sk_OPENSSL_STRING_compfunc arg1 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10522:38: error: 'sk_OPENSSL_STRING_compfunc' undeclared (first use in this function)
sk_OPENSSL_STRING_compfunc arg1 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10522:66: error: expected ',' or ';' before numeric constant
sk_OPENSSL_STRING_compfunc arg1 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_STRING_pop_free':
SWIG/_m2crypto_wrap.c:10776:3: error: unknown type name 'sk_OPENSSL_STRING_freefunc'
sk_OPENSSL_STRING_freefunc arg2 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10776:38: error: 'sk_OPENSSL_STRING_freefunc' undeclared (first use in this function)
sk_OPENSSL_STRING_freefunc arg2 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:10776:66: error: expected ',' or ';' before numeric constant
sk_OPENSSL_STRING_freefunc arg2 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
In file included from /usr/include/openssl/crypto.h:129:0,
from /usr/include/openssl/bio.h:69,
from /usr/include/openssl/err.h:124,
from SWIG/_m2crypto_wrap.c:3854:
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_STRING_find_ex':
SWIG/_m2crypto_wrap.c:10946:17: error: expected expression before 'struct'
result = (int)sk_OPENSSL_STRING_find_ex(arg1,arg2);
^
In file included from /usr/include/openssl/crypto.h:129:0,
from /usr/include/openssl/bio.h:69,
from /usr/include/openssl/err.h:124,
from SWIG/_m2crypto_wrap.c:3854:
SWIG/_m2crypto_wrap.c:10946:17: error: expected expression before 'char'
result = (int)sk_OPENSSL_STRING_find_ex(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:10925:9: warning: variable 'arg2' set but not used [-Wunused-but-set-variable]
char *arg2 = (char *) 0 ;
^
SWIG/_m2crypto_wrap.c:10924:35: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
struct stack_st_OPENSSL_STRING *arg1 = (struct stack_st_OPENSSL_STRING *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_STRING_deep_copy':
SWIG/_m2crypto_wrap.c:11024:3: error: unknown type name 'sk_OPENSSL_STRING_copyfunc'
sk_OPENSSL_STRING_copyfunc arg2 = (sk_OPENSSL_STRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11024:38: error: 'sk_OPENSSL_STRING_copyfunc' undeclared (first use in this function)
sk_OPENSSL_STRING_copyfunc arg2 = (sk_OPENSSL_STRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11024:66: error: expected ',' or ';' before numeric constant
sk_OPENSSL_STRING_copyfunc arg2 = (sk_OPENSSL_STRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11025:3: error: unknown type name 'sk_OPENSSL_STRING_freefunc'
sk_OPENSSL_STRING_freefunc arg3 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11025:38: error: 'sk_OPENSSL_STRING_freefunc' undeclared (first use in this function)
sk_OPENSSL_STRING_freefunc arg3 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11025:66: error: expected ',' or ';' before numeric constant
sk_OPENSSL_STRING_freefunc arg3 = (sk_OPENSSL_STRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_STRING_set_cmp_func':
SWIG/_m2crypto_wrap.c:11062:3: error: unknown type name 'sk_OPENSSL_STRING_compfunc'
sk_OPENSSL_STRING_compfunc arg2 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11062:38: error: 'sk_OPENSSL_STRING_compfunc' undeclared (first use in this function)
sk_OPENSSL_STRING_compfunc arg2 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11062:66: error: expected ',' or ';' before numeric constant
sk_OPENSSL_STRING_compfunc arg2 = (sk_OPENSSL_STRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11067:30: error: expected ';' before 'result'
sk_OPENSSL_STRING_compfunc result;
^
SWIG/_m2crypto_wrap.c:11081:3: error: 'result' undeclared (first use in this function)
result = (sk_OPENSSL_STRING_compfunc)sk_OPENSSL_STRING_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_num':
SWIG/_m2crypto_wrap.c:11103:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_num' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_num((struct stack_st_OPENSSL_CSTRING const *)arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_value':
SWIG/_m2crypto_wrap.c:11134:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_value' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_value((struct stack_st_OPENSSL_CSTRING const *)arg1,arg2);
^
SWIG/_m2crypto_wrap.c:11134:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_value((struct stack_st_OPENSSL_CSTRING const *)arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_new':
SWIG/_m2crypto_wrap.c:11144:3: error: unknown type name 'sk_OPENSSL_CSTRING_compfunc'
sk_OPENSSL_CSTRING_compfunc arg1 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11144:39: error: 'sk_OPENSSL_CSTRING_compfunc' undeclared (first use in this function)
sk_OPENSSL_CSTRING_compfunc arg1 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11144:68: error: expected ',' or ';' before numeric constant
sk_OPENSSL_CSTRING_compfunc arg1 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11155:47: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_new' [-Wimplicit-function-declaration]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_new(arg1);
^
SWIG/_m2crypto_wrap.c:11155:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_new(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_new_null':
SWIG/_m2crypto_wrap.c:11168:47: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_new_null' [-Wimplicit-function-declaration]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_new_null();
^
SWIG/_m2crypto_wrap.c:11168:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_new_null();
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_free':
SWIG/_m2crypto_wrap.c:11189:3: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_free' [-Wimplicit-function-declaration]
sk_OPENSSL_CSTRING_free(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_zero':
SWIG/_m2crypto_wrap.c:11210:3: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_zero' [-Wimplicit-function-declaration]
sk_OPENSSL_CSTRING_zero(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_delete':
SWIG/_m2crypto_wrap.c:11241:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_delete' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_delete(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:11241:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_delete(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_delete_ptr':
SWIG/_m2crypto_wrap.c:11273:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_delete_ptr' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_delete_ptr(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c:11273:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_delete_ptr(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_push':
SWIG/_m2crypto_wrap.c:11307:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_push' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_push(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_unshift':
SWIG/_m2crypto_wrap.c:11341:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_unshift' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_unshift(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_pop':
SWIG/_m2crypto_wrap.c:11365:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_pop' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_pop(arg1);
^
SWIG/_m2crypto_wrap.c:11365:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_pop(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_shift':
SWIG/_m2crypto_wrap.c:11387:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_shift' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_shift(arg1);
^
SWIG/_m2crypto_wrap.c:11387:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_shift(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_pop_free':
SWIG/_m2crypto_wrap.c:11398:3: error: unknown type name 'sk_OPENSSL_CSTRING_freefunc'
sk_OPENSSL_CSTRING_freefunc arg2 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11398:39: error: 'sk_OPENSSL_CSTRING_freefunc' undeclared (first use in this function)
sk_OPENSSL_CSTRING_freefunc arg2 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11398:68: error: expected ',' or ';' before numeric constant
sk_OPENSSL_CSTRING_freefunc arg2 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11416:3: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_pop_free' [-Wimplicit-function-declaration]
sk_OPENSSL_CSTRING_pop_free(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_insert':
SWIG/_m2crypto_wrap.c:11457:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_insert' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_insert(arg1,(char const *)arg2,arg3);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_set':
SWIG/_m2crypto_wrap.c:11500:20: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_set' [-Wimplicit-function-declaration]
result = (char *)sk_OPENSSL_CSTRING_set(arg1,arg2,(char const *)arg3);
^
SWIG/_m2crypto_wrap.c:11500:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (char *)sk_OPENSSL_CSTRING_set(arg1,arg2,(char const *)arg3);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_find':
SWIG/_m2crypto_wrap.c:11534:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_find' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_find(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_find_ex':
SWIG/_m2crypto_wrap.c:11568:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_find_ex' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_find_ex(arg1,(char const *)arg2);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_sort':
SWIG/_m2crypto_wrap.c:11591:3: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_sort' [-Wimplicit-function-declaration]
sk_OPENSSL_CSTRING_sort(arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_is_sorted':
SWIG/_m2crypto_wrap.c:11613:17: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_is_sorted' [-Wimplicit-function-declaration]
result = (int)sk_OPENSSL_CSTRING_is_sorted((struct stack_st_OPENSSL_CSTRING const *)arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_dup':
SWIG/_m2crypto_wrap.c:11635:47: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_dup' [-Wimplicit-function-declaration]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_dup((struct stack_st_OPENSSL_CSTRING const *)arg1);
^
SWIG/_m2crypto_wrap.c:11635:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_dup((struct stack_st_OPENSSL_CSTRING const *)arg1);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_deep_copy':
SWIG/_m2crypto_wrap.c:11646:3: error: unknown type name 'sk_OPENSSL_CSTRING_copyfunc'
sk_OPENSSL_CSTRING_copyfunc arg2 = (sk_OPENSSL_CSTRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11646:39: error: 'sk_OPENSSL_CSTRING_copyfunc' undeclared (first use in this function)
sk_OPENSSL_CSTRING_copyfunc arg2 = (sk_OPENSSL_CSTRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11646:68: error: expected ',' or ';' before numeric constant
sk_OPENSSL_CSTRING_copyfunc arg2 = (sk_OPENSSL_CSTRING_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11647:3: error: unknown type name 'sk_OPENSSL_CSTRING_freefunc'
sk_OPENSSL_CSTRING_freefunc arg3 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11647:39: error: 'sk_OPENSSL_CSTRING_freefunc' undeclared (first use in this function)
sk_OPENSSL_CSTRING_freefunc arg3 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11647:68: error: expected ',' or ';' before numeric constant
sk_OPENSSL_CSTRING_freefunc arg3 = (sk_OPENSSL_CSTRING_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11673:47: warning: implicit declaration of function 'sk_OPENSSL_CSTRING_deep_copy' [-Wimplicit-function-declaration]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_deep_copy((struct stack_st_OPENSSL_CSTRING const *)arg1,arg2,arg3);
^
SWIG/_m2crypto_wrap.c:11673:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
result = (struct stack_st_OPENSSL_CSTRING *)sk_OPENSSL_CSTRING_deep_copy((struct stack_st_OPENSSL_CSTRING const *)arg1,arg2,arg3);
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_CSTRING_set_cmp_func':
SWIG/_m2crypto_wrap.c:11684:3: error: unknown type name 'sk_OPENSSL_CSTRING_compfunc'
sk_OPENSSL_CSTRING_compfunc arg2 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11684:39: error: 'sk_OPENSSL_CSTRING_compfunc' undeclared (first use in this function)
sk_OPENSSL_CSTRING_compfunc arg2 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11684:68: error: expected ',' or ';' before numeric constant
sk_OPENSSL_CSTRING_compfunc arg2 = (sk_OPENSSL_CSTRING_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11689:31: error: expected ';' before 'result'
sk_OPENSSL_CSTRING_compfunc result;
^
SWIG/_m2crypto_wrap.c:11703:3: error: 'result' undeclared (first use in this function)
result = (sk_OPENSSL_CSTRING_compfunc)sk_OPENSSL_CSTRING_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:11703:41: error: expected ';' before 'sk_OPENSSL_CSTRING_set_cmp_func'
result = (sk_OPENSSL_CSTRING_compfunc)sk_OPENSSL_CSTRING_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:11683:36: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
struct stack_st_OPENSSL_CSTRING *arg1 = (struct stack_st_OPENSSL_CSTRING *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_BLOCK_new':
SWIG/_m2crypto_wrap.c:11766:3: error: unknown type name 'sk_OPENSSL_BLOCK_compfunc'
sk_OPENSSL_BLOCK_compfunc arg1 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11766:37: error: 'sk_OPENSSL_BLOCK_compfunc' undeclared (first use in this function)
sk_OPENSSL_BLOCK_compfunc arg1 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:11766:64: error: expected ',' or ';' before numeric constant
sk_OPENSSL_BLOCK_compfunc arg1 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_BLOCK_pop_free':
SWIG/_m2crypto_wrap.c:12005:3: error: unknown type name 'sk_OPENSSL_BLOCK_freefunc'
sk_OPENSSL_BLOCK_freefunc arg2 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12005:37: error: 'sk_OPENSSL_BLOCK_freefunc' undeclared (first use in this function)
sk_OPENSSL_BLOCK_freefunc arg2 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12005:64: error: expected ',' or ';' before numeric constant
sk_OPENSSL_BLOCK_freefunc arg2 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
In file included from /usr/include/openssl/crypto.h:129:0,
from /usr/include/openssl/bio.h:69,
from /usr/include/openssl/err.h:124,
from SWIG/_m2crypto_wrap.c:3854:
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_BLOCK_find_ex':
SWIG/_m2crypto_wrap.c:12157:17: error: expected expression before 'struct'
result = (int)sk_OPENSSL_BLOCK_find_ex(arg1,arg2);
^
In file included from /usr/include/openssl/crypto.h:129:0,
from /usr/include/openssl/bio.h:69,
from /usr/include/openssl/err.h:124,
from SWIG/_m2crypto_wrap.c:3854:
SWIG/_m2crypto_wrap.c:12157:17: error: expected expression before 'void'
result = (int)sk_OPENSSL_BLOCK_find_ex(arg1,arg2);
^
SWIG/_m2crypto_wrap.c:12138:34: warning: variable 'arg1' set but not used [-Wunused-but-set-variable]
struct stack_st_OPENSSL_BLOCK *arg1 = (struct stack_st_OPENSSL_BLOCK *) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_BLOCK_deep_copy':
SWIG/_m2crypto_wrap.c:12233:3: error: unknown type name 'sk_OPENSSL_BLOCK_copyfunc'
sk_OPENSSL_BLOCK_copyfunc arg2 = (sk_OPENSSL_BLOCK_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12233:37: error: 'sk_OPENSSL_BLOCK_copyfunc' undeclared (first use in this function)
sk_OPENSSL_BLOCK_copyfunc arg2 = (sk_OPENSSL_BLOCK_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12233:64: error: expected ',' or ';' before numeric constant
sk_OPENSSL_BLOCK_copyfunc arg2 = (sk_OPENSSL_BLOCK_copyfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12234:3: error: unknown type name 'sk_OPENSSL_BLOCK_freefunc'
sk_OPENSSL_BLOCK_freefunc arg3 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12234:37: error: 'sk_OPENSSL_BLOCK_freefunc' undeclared (first use in this function)
sk_OPENSSL_BLOCK_freefunc arg3 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12234:64: error: expected ',' or ';' before numeric constant
sk_OPENSSL_BLOCK_freefunc arg3 = (sk_OPENSSL_BLOCK_freefunc) 0 ;
^
SWIG/_m2crypto_wrap.c: In function '_wrap_sk_OPENSSL_BLOCK_set_cmp_func':
SWIG/_m2crypto_wrap.c:12271:3: error: unknown type name 'sk_OPENSSL_BLOCK_compfunc'
sk_OPENSSL_BLOCK_compfunc arg2 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12271:37: error: 'sk_OPENSSL_BLOCK_compfunc' undeclared (first use in this function)
sk_OPENSSL_BLOCK_compfunc arg2 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12271:64: error: expected ',' or ';' before numeric constant
sk_OPENSSL_BLOCK_compfunc arg2 = (sk_OPENSSL_BLOCK_compfunc) 0 ;
^
SWIG/_m2crypto_wrap.c:12276:29: error: expected ';' before 'result'
sk_OPENSSL_BLOCK_compfunc result;
^
SWIG/_m2crypto_wrap.c:12290:3: error: 'result' undeclared (first use in this function)
result = (sk_OPENSSL_BLOCK_compfunc)sk_OPENSSL_BLOCK_set_cmp_func(arg1,arg2);
^
SWIG/_m2crypto_wrap.c: At top level:
SWIG/_m2crypto_wrap.c:5671:1: warning: 'BIO_meth_free' defined but not used [-Wunused-function]
BIO_meth_free( BIO_METHOD *meth )
^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
---------------------------------------- The directory '/home/ssm-user/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

The directory '/home/ssm-user/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-bIiHgu/M2Crypto/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /tmp/pip-yGfxsu-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-bIiHgu/M2Crypto/
You are using pip version 8.1.1, however version 19.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
- ID: undefined
SLS: sift.packages.python-volatility
Run#: 188
Comment: One or more requisite failed: sift.python-packages.dpapick.dpapick
- ID: undefined
SLS: sift.packages
Run#: 257
Comment: One or more requisite failed: sift.packages.python-volatility.python-volatility-community-plugins
- ID: undefined
SLS: sift.pkgs
Run#: 284
Comment: One or more requisite failed: sift.packages.sift-packages

I ran into the same issue.
Solution: https://github.com/teamdfir/sift/issues/224
apt install python-m2crypto corrected the issue for me.

I think this will do it.
sudo pip uninstall m2crypto
sudo apt install python-m2crypto
sudo apt install python3-pip --reinstall
sudo pip install dpapick
sudo sift install - should then work, at least that's what I just did on a 2nd VM that was in a borked state.

@saltydog4n6
Thanks for the help.I tried integrating the above set of commands as a part of my script,everything went well.It is now able to install SIFT without any failures.


"Could not find elden ring process"

This is what im told every single time i try to start the game through Metis mod launcher.

Same. I can't get a single mod to work with Mod Engine or Metis.

Running the app as administrator fixed that issue for me


Receiving PHP error on map fields page for products in Feedme

Describe the bug
Receiving PHP error on map fields page for products in Feedme
PHP Fatal error:  Declaration of nystudio107\recipe\integrations\RecipeFeedMeField::getMappingTemplate() must be compatible with craft\feedme\base\FieldInterface::getMappingTemplate(): string in /home/site/craft/vendor/nystudio107/craft-recipe/src/integrations/RecipeFeedMeField.php on line 38
I don't need to map any recipe fields. Only a stock control feed
Versions

Plugin version: 4.0.7
Craft version: 4.5.14
Feedme Version: 5.3.0

@khalwat Any additional info you need let me know

I've installed dev-develop-v4 and it looks to have fixed the issue

Ah good reminder that I need to cut a release tho, so I'll re-open this issue

4.0.8 released -> https://github.com/nystudio107/craft-recipe/releases/tag/4.0.8


Disable limits notification

We introduce it in this PR and we have checked that we can't display the infobox each time a tile fails, without knowing the type of the problem. It could be any problem with the server, connectivity issue, limits,...
Place where the discussion started -> https://github.com/CartoDB/cartodb/pull/12890/files#diff-4c52b5000fde47e73c06414652d8ed45R43

I'll completely remove the error for now.
We could re-enable it and change the copy to something less worrying as long as limits are not active.
In any case, we need to improve our error strategy.

agree

🚢


fix winget for good

Type of Change

[ ] New feature
[x] Bug fix
[ ] Documentation update
[ ] Refactoring
[ ] Hotfix
[ ] Security patch
[ ] UI/UX improvement

Description
Attempt to resolve winget issues
Issue related to PR

Resolves #

Probably like 10 issues, but I'll track them down after more testing.
Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no errors/warnings/merge conflicts.

Have you tested this script
If no then please do


Can this be used as a means to speed up LLM inferencing?

Thanks for your work. I am interested in whether this can be used as a means to speed up LLM reasoning? I have the same idea as your work. I tried to divide up_proj,`` down_proj, gate_proj into 4 parts evenly on llama3-8b to form four experts, and added a gate net (dim, num_experts). I try to activate experts with top-2 sparsely, but I found that the reasoning speed will be slower (when not training) than dense model.
My code’s output is showed as below:
Once upon a time, in a small village nestled in the rolling hills of the countryside, there lived a young girl named Emily.  She loved to
Original model forward pass time: 1.6654 seconds
Perplexity: 5.239216327667236

Once upon a time(s gezocht inherited inherited inherited gezocht inherited inherited inherited inherited inherited inherited inherited inherited inherited inherited inherited(s inherited or inherited inheritedSFML inherited or(s inherited inherited inherited inherited or inherited inherited inherited inherited or inherited or inherited inherited inherited(s inherited inherited or inherited
Modified model (Sparse MoE) forward pass time: 2.2228 seconds
Perplexity:<PHONE_NUMBER>

This method can be used to speed up LLM inferencing with optimization on the hardware. Your observation that MoE lags the speed is also correct, as the MoE forwarding using nn.ModuleList is much slower than the dense model due to its dynamic property (e.g. extra cost for dispatching tokens and segmented forwarding). For optimized implementations you can refer to scattermoe and MegaBlocks, which can provide faster inference speed for the MoE.

Thanks for your answer! I find that if I split FFN into experts, the router's latency can not be ignored. It even exceeds the computation time of sparse experts. The most effective method i tested is random routing. But it just achieve a low speed increase. Thanks for the suggestion, I'll look into it.


fix: My Collection Additional Details form value bug

The type of this PR is: Bugfix

This PR resolves CX-2161
Description
This PR fixes a bug where the value of some inputs was not populated correctly depending on the "isEdition" field.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[x] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Fix "My Collection" Additional Details isEdition value bug - ole

iOS user-facing changes

Android user-facing changes

Dev changes

This PR contains the following changes:

Cross-platform user-facing changes (Fix "My Collection" Additional Details isEdition value bug - ole)

  Generated by :no_entry_sign: dangerJS against 22007ee2798079db85094dd710777371fb978fad


Fix django-guardian permission display

The django-guardian permissions are rendered in reverse.

Without unfold

Hey, thanks for report and the PR, it helped me a lot to debug the issue. In PR #793 I addressed your problem and additionaly I found one more issue with the template which is fixed there.
For the sake of shipping this fix as soon as possible, I merged my PR.

@gmargaritis I already made a release. You can update the version.

Thanks a lot for the quick response and release ✌

Yeah, no problem. If you find something else let me know.


Question about the training of BEVFormerV2

Hello, I've been trying to reproduce BEVFormerV2 recently, but according to the code, it seems that BEVFormerV2 doesn't support Batch Size > 1 during training, is this the case or do I have a misunderstanding. Because I think every sample within a batch needs to compute pre_bev features when batchsize > 1, but it's not in the code, it only uses the infos of img_meta[0].
https://github.com/fundamentalvision/BEVFormer/blob/32b65ffd2a85c35b5f74b753f23ef34f9a85a576/projects/mmdet3d_plugin/bevformer/detectors/bevformerV2.py#L195C9-L195C19

Yes, currently, the code only support training of batch size =1


Suggestion - Buycraft signs

I'd like to add signs in game that shows the current price on a package and sends you the purchase link if you press the sign. This would be very useful for my and other servers as we're often having sales & discounts.
https://gyazo.com/f7bf390793dbc102d9f859a8777352d3
https://gyazo.com/eb011a95c503ea2e0f5ed1f71e9bc616

This is already implemented. Just create a sign with " [buycraft_buy]"
as the first line and it'll let you select a package to put on the sign.
On 03/23/2016 05:16 PM, Johandrex wrote:

I'd like to add signs in game that shows the current price on a
package and sends you the purchase link if you press the sign. This
would be very useful for my and other servers as we're often having
sales & discounts.
https://gyazo.com/f7bf390793dbc102d9f859a8777352d3
https://gyazo.com/eb011a95c503ea2e0f5ed1f71e9bc616
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/BuycraftPlugin/BuycraftX/issues/28

Ah awesome, would be nice if we could change the layout on the sign though.


How to Implement

I'm not a Java dev but your library looks like what I need.
I need to load a .dae file into an Android app. I'm using Android Studio on a Mac.
How do I load this library into my existing project?
I get this following error after importing your library.
Exception in thread "main" java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
	at java.lang.Runtime.loadLibrary0(Runtime.java:870)
	at java.lang.System.loadLibrary(System.java:1122)
	at org.lwjgl.Sys$1.run(Sys.java:72)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.lwjgl.Sys.doLoadLibrary(Sys.java:65)
	at org.lwjgl.Sys.loadLibrary(Sys.java:81)
	at org.lwjgl.Sys.<clinit>(Sys.java:98)
	at org.lwjgl.opengl.Display.<clinit>(Display.java:132)
	at ColladaDemo.Window.<init>(Window.java:45)
	at ColladaDemo.ColladaDemo.<init>(ColladaDemo.java:20)
	at ColladaDemo.ColladaDemo.main(ColladaDemo.java:29)

From what I can tell it looks like you haven't included LWJGL into your project's library path. This repository doesn't actually use LWJGL so it may be a problem with your project setup.

Thanks for the fast reply. I'll try setting up what you have suggested and get back to you.


Project Page lacks filters

I'm pretty sure Adam Saleh story's are fascinating but regardless his storydrafts are not packaged in Fedora thus there needs to be means to filter such stuff out.  That said you will pretty fast exhaust all infra's resources if everything and everyone is allowed to use packit for anything so I recommend that packit is limited only to official teams/maintainers and their official maintained packages in the distribution. ( If packit takes off for real then you are talking about what 14k+ components that will be using it )

Hey Jóhann, these are filtered. Projects that have packit-service enabled (perhaps the user enabled it for all of their repos) but haven't ever touched packit at all are already hidden in the dashboard.
Some projects might have accidentally interacted with packit like the ones you pointed out, those are still visible.
As for the rest of what you suggested, someone from the Packit team will hopefully reply soon.

@IceWreck thank you for answering the filtering part. You are right.
It was originally requested by me in #63 and implemented by @IceWreck. Not sure if we can easily filter by a better rule than "at least one activity we have reacted on".
@johannbg Regarding the proposal about being strictly Fedora only, that's a different topic and much harder to answer, but thanks for creating the issue.

We do manual approval and require Fedora Project Contributor Agreement  for now. (We can make this step more strict if needed.) (For others, the onboarding has been discussed a bit in this issue: packit/packit-service#997)
For projects without proper Packit setup (=i.e. config file), we don't spend a lot of resources. (Really minimal comparing to regular workflows.)
We are still in a phase that we are happy for new users and trying to ease the onboarding as much as possible. (Yes, it can change and we need to be prepared before the state we can't handle all repositories.)
There is also some chance that by using Packit, some project will join the Fedora ecosystem.

@packit/the-packit-team can we discuss this tomorrow at our architecture meeting, please?

I think we can close this issue -- we already ignore projects without any activity and for special requests regarding searching/filtering, we can create a dedicated issue if needed (e.g. #61).


Segmentation fault with ICC/debug build

I built ospray v1.2.1 using ICC and the Debug build configuration and found that the resulting executable files terminated immediately after invocation due to a segfault. I tried with ICC and the Release configuration and both Release and Debug with GCC and did not observe the segfault (executable files ran as expected) with those configurations.
Here's the back trace from gdb:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff304fa7c in ospcommon::getCPUFeatures () at /home/jason/ospray/components/ospcommon/intrinsics.h:53
53	    asm volatile ("xchg{l}\t{%%}ebx, %1\n\t"
(gdb) bt
#0  0x00007ffff304fa7c in ospcommon::getCPUFeatures () at /home/jason/ospray/components/ospcommon/intrinsics.h:53
#1  0x00007ffff4fbb74d in ospray::api::Device::commit (this=0x6f0cf0) at /home/jason/ospray/ospray/api/Device.cpp:52
#2  0x00007ffff4fc7ae3 in ospray::api::LocalDevice::commit (this=0x6f0cf0) at /home/jason/ospray/ospray/api/LocalDevice.cpp:50
#3  0x00007ffff4f9e66e in ospInit (_ac=0x7fffffff9ce0, _av=0x7fffffffca18) at /home/jason/ospray/ospray/api/API.cpp:167
#4  0x000000000043d1e6 in main (argc=1, argv=0x7fffffffca18) at /home/jason/ospray/apps/volumeViewer/main.cpp:58

I used this cmake command to produce the problematic build:
CC=icc CXX=icpc cmake .. \
  -DISPC_EXECUTABLE=/opt/ispc-v1.9.1-linux/ispc \
  -DOSPRAY_MODULE_MPI=OFF \
  -DOSPRAY_TASKING_SYSTEM=TBB \
  -DOSPRAY_ENABLE_APPS=ON \
  -DOSPRAY_BUILD_ISA=AVX \
  -DCMAKE_BUILD_TYPE=Debug

Hi Jason,
thanks for reporting. A fix is available in the devel branch, or you could also cherry-pick 6f98e675.
Best regards,
Johannes


URL Host on Links

I'm trying to find a way to optionally automatically add the host to the links (self, related, etc...) in order provide a full url for my consumers as part of the response data.
Help is appreciated.
example:
 "data": [
    {
      "type": "categories",
      "id": "qORxXmZznVdmdyHcaBSH",
      "attributes": {
        "name": "My Name",
        "description": "My  Description"
      },
      "relationships": {
        "services": {
          "links": {
            "self": "http://localhost:8080/categories/qORxXmZznVdmdyHcaBSH/relationships/services",
            "related": "http://localhost:8080/categories/qORxXmZznVdmdyHcaBSH/services"
          },
          "data": [
            {
              "type": "services",
              "id": "5yEHz6mXHbIFSE/JMNbd"
            }
          ]
        }
      },
      "links": {
        "self": "http://localhost:8080/categories/qORxXmZznVdmdyHcaBSH"
      }

Hmm, it could be added as an option.

This is easy if the library stops enforcing / at the end of the prefix option :)

Thanks for the suggestion @amitassaraf
This has been committed as https://github.com/fortunejs/fortune-json-api/commit/f32541ddc11e96bb49204fcc45382c603ca500a2 and released.


Adds tags to releases

Closes https://github.com/thoughtbot/formulator/issues/38
What changed?
We have a bin/release script that will set the new release version and publish the package to hex.
We also want to create a tag and push it to GitHub so releases are easier to track. This commit adds a simple tag to the release script and pushes it to GitHub.

@drapergeek if you have a few mins, I'd love your thoughts on this. You opened the original issue, so I wanted to check if this is what you had in mind, or if it's at least a good first step.

Exactly what I had in mind @germsvel. Thanks! 🚢


Migrate from nsp to snyk

It looks like nsp was shut down so we should migrate to snyk.

Unnecessary, using npm audit will suffice.


Update History.md

Add info for 0.2.0—0.2.2

thanks for this @simison - sorry it took so long, I had notifications muted for a bit it seems


Null check operator used on a null value

@Doublelae
Can this be reproduce, so i can take a look
thanks


Allow Configurable Number of CPU Cores for Multi-Threading in DiceDB

Was going through the code of DiceDB, specifically this snippet:
	var numCores int
	if config.EnableMultiThreading {
		serverErrCh = make(chan error, 1)
		numCores = runtime.NumCPU()
		logr.Debug("The DiceDB server has started in multi-threaded mode.", slog.Int("number of cores", numCores))
	} else {
		serverErrCh = make(chan error, 2)
		logr.Debug("The DiceDB server has started in single-threaded mode.")
		numCores = 1
	}
	runtime.GOMAXPROCS(numCores)

Currently, DiceDB dynamically configures its threading model based on the EnableMultiThreading flag in the configuration, defaulting to the number of logical CPU cores available via runtime.NumCPU() when multi-threading is enabled. However, this approach can be problematic in containerized environments, such as Kubernetes, where resource constraints (e.g., CPU limits) are enforced per container.
In Kubernetes, a container can be allocated a specific number of CPU cores, and using runtime.NumCPU() may not reflect these limits accurately. For example, if the host machine has 16 cores but a container is only allocated 4 cores, DiceDB would still use all 16 cores unless GOMAXPROCS is manually set. This could lead to resource contention, poor performance, or overuse of allocated resources, resulting in throttling by the container orchestrator.
Issue Summary:

Current behavior: DiceDB defaults to using all available CPU cores on the host machine (runtime.NumCPU()).
Problem: In environments like Kubernetes, containers may have restricted CPU allocations, and the use of runtime.NumCPU() could exceed the allocated resources.
Proposed solution: Introduce a configuration option allowing the user to specify the number of cores to use dynamically, either through environment variables or a dedicated configuration field. This would ensure DiceDB respects the container's CPU allocation, preventing resource overuse and improving compatibility with cloud-native environments.

I can pick up these changes, can you assign this issue to me @lucifercr07 @JyotinderSingh @AshwinKul28 @arpitbbhayani

@dograprabhav I was thinking that workloads such as databases would run on dedicated nodes.
We are designing DiceDB to be running optimally on modern multi-core hardware extracting the max performance out of it.
However I agree, we need a more sophisticated logic to run DiceDB that allocating all cores to it blindly.
Irrespective this change may be helpful in test environments.
@arpitbbhayani @AshwinKul28 wdyt?

Adding it to icebox for now.

@lucifercr07 can I take this up?

optional config for num cpu sounds like a good idea
can I solve this?


Extract a couple of components from the event page

The [eventId].tsx file is on the large side; this extracts the DateList and EventStatus components as-is into separate files.
The specific motivation for this is that I've spotted a (small) bug in the DateList component: events will still appear as "Full" even after they're finished, for example tomorrow's event:

We're using isDayPast(endOfEvent) when I think we want isPast(endOfEvent).
This patch doesn't contain a fix for this bug, it just extracts the components into standalone files. I wanted them in the components folder so they'd be easier to test, but it's tricky to review any changes to the components at the same time as moving them. This patch leaves them as-is, and I'll do a separate patch for the bugfix.

np; would it be good to name it EventDateList since it is coded specifically for them?
Some pages are mega long and contain "components" that are only ever used within that one page. I used to work with a system that had a views folder alongside pages and components and they would contain folders for each page, with an index but also split off components. The pages/[file] itself would tend to be pretty simple, fetching the required data but then simply important the files from its view, very readable and functional. The display logic would lie withing views files.
I don't know if it's something we want (or if I'm being clear enough), I know our structure is already a tad complex, but wanted to put the thought out there.

I don't know if it's something we want (or if I'm being clear enough), I know our structure is already a tad complex, but wanted to put the thought out there.

Yeah, I definitely get what you mean. I think we have a couple of other bits of restructuring to get through first (combining content/catalogue, and moving to app-based routing), but after that it'd be a good one to revisit.


adding coverpoint defination for vm_sv39

Dear All,
)
This PR adds coverpoint definitions for the set of self-checking assembly tests for the architectural verification of MMU SV39, These coverpoints are hand-written and follows the test plan provided in the following testplan.
I have also submitted the  PR for the Virtual Memory Tests (ACTs) on the architecture test repository, PR#407
For a more comprehensive understanding of code coverage and verification results, please consult the generated report accessible through the provided  coverage report link
Best regards,

@Ammar-10xe these coverpoints will be rewritten according to the new translator, I am closing this PR to clear the backlog


java.lang.IllegalArgumentException: Cannot create a fluidstack from a null fluid

when i try to look up "tank" in nei http://paste.ee/p/tZO5D

This might be a Forge issue, as the same happens to me when I open the Railcraft coke oven GUI.

mods need to update but ccc has an update

Update EnderStorage


VHA3 - random fixes

🤷 WIP 👷
New feature:

add video notes to any video
allow searching through notes 👍
CSS to make notes look good 😓 kind-of-ok 🤷

Will close: #472

Thanks for the catch Cal!

I've left this PR unattended for too long -- I'd rather merge it and continue with cleanup in a separate PR 😕
The finalArrayNeedsSaving may be handled better in another way -- I'll see if maybe I don't need all the editFinalArrayStars and editFinalArrayTag and editFinalArrayYear emissions (.emit($event)) -- and I could just remove all of them and replace those and the "details changed" events with a single emit of finalArrayNeedsUpdating 👍


Fix entity reuse using dynamic create.

Using the length of generations is not a reliable source of the
next entity as it is out of date when using dynamic entity creation

@csherratt please clarify the cast that you found.

dynamic_create was the test that reproduced the issue.


Page indicator style is broken

Steps to reproduce

Launch app
Open any manga
See issue

Expected behavior
0.16.4:

Actual behavior
0.16.5

Crash logs
No response
Mihon version
0.16.5
Android version
Android 13
Device
Redmi Note 10 Pro (chopin)
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.5.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

It is not broken it is the new material design 3 elements from Google https://m3.material.io/components/sliders/overview
You'll have to live with it until they decide to change it again.
What is broken is the right to left reading slider being filled at page 1 though.

Actually, it actually does look broken.
The Material 3 slider has two sections, the active section, the inactive section, and a divider between the two. Meanwhile, Mihon has the active section, the divider, and... no inactive section. Furthermore, the slider looks overlayed on top of the dots representing the pages. My suggestion would be to completely get rid of the dots, and use the full slider. The steps would still be there, only the dots would disappear.

It's literally what I said. Check the left to right reading mode, it works as intended. The one that is broken is the right to left reading mode as that is now set by language

Shit, my bad. I misread your reply.

I wonder if this could be solved by reversing the colors? Like take this discrete slider and just reverse the colors on them? Or does that break the theming everywhere else?

I am not familiar with Material Design frameworks, but in this instance, the segment doesn’t appear at all in the slider. Reversing the colors would probably just make the slider grey.

Some themes were created with a colour palette that doesn't 100% match with what Material Design expects. Sometimes, attributes that are expected to be visually different have historically been set to the same value, causing these newer component designs to end up using the same colour twice.
M3 colours palettes are defined by a long list of attributes, like primary and primaryInverse (I believe there are about 30 or so different attributes).
"Fixing" these colour sets by making the attributes these components use actually distinct would mean going back and trying to recreate every theme with the modern palette definitions. While this is technically possible, it would be painstaking work and also end up with most themes appearing differently (because of the newly differing colours).
Some themes intentionally define different attributes as the same colour to preserve the aesthetic of the theme, and would end up appearing extremely different if they defined their colours exactly to spec.
This affects several of these progress components across the app, not just the chapter slider.

Some themes were created with a colour palette that doesn't 100% match with what Material Design expects. Sometimes, attributes that are expected to be visually different have historically been set to the same value, causing these newer component designs to end up using the same colour twice.
M3 colours palettes are defined by a long list of attributes, like primary and primaryInverse (I believe there are about 30 or so different attributes).
"Fixing" these colour sets by making the attributes these components use actually distinct would mean going back and trying to recreate every theme with the modern palette definitions. While this is technically possible, it would be painstaking work and also end up with most themes appearing differently (because of the newly differing colours).
Some themes intentionally define different attributes as the same colour to preserve the aesthetic of the theme, and would end up appearing extremely different if they defined their colours exactly to spec.
This affects several of these progress components across the app, not just the chapter slider.

So we basically have to pray that Google does something about this themselves.

Some themes were created with a colour palette that doesn't 100% match with what Material Design expects. Sometimes, attributes that are expected to be visually different have historically been set to the same value, causing these newer component designs to end up using the same colour twice.
M3 colours palettes are defined by a long list of attributes, like primary and primaryInverse (I believe there are about 30 or so different attributes).
"Fixing" these colour sets by making the attributes these components use actually distinct would mean going back and trying to recreate every theme with the modern palette definitions. While this is technically possible, it would be painstaking work and also end up with most themes appearing differently (because of the newly differing colours).
Some themes intentionally define different attributes as the same colour to preserve the aesthetic of the theme, and would end up appearing extremely different if they defined their colours exactly to spec.
This affects several of these progress components across the app, not just the chapter slider.

So we basically have to pray that Google does something about this themselves.

They won't. They're using the palette attributes they say should be visually different but some themes don't define them to be such. The sections not being different colours is a design issue with most of Mihon's themes.

Some themes were created with a colour palette that doesn't 100% match with what Material Design expects. Sometimes, attributes that are expected to be visually different have historically been set to the same value, causing these newer component designs to end up using the same colour twice.
M3 colours palettes are defined by a long list of attributes, like primary and primaryInverse (I believe there are about 30 or so different attributes).
"Fixing" these colour sets by making the attributes these components use actually distinct would mean going back and trying to recreate every theme with the modern palette definitions. While this is technically possible, it would be painstaking work and also end up with most themes appearing differently (because of the newly differing colours).
Some themes intentionally define different attributes as the same colour to preserve the aesthetic of the theme, and would end up appearing extremely different if they defined their colours exactly to spec.
This affects several of these progress components across the app, not just the chapter slider.

So we basically have to pray that Google does something about this themselves.

They won't. They're using the palette attributes they say should be visually different but some themes don't define them to be such. The sections not being different colours is a design issue with most of Mihon's themes.

Oh, okay-okay.

Even without RTL/LTR issues, the following issues are still present:

Progress bar does not exist until 1/6 through the manga
Dividing line is too thick for page count
Dividing line has big gaps on both sides, making some pages look like they don't fit in either "read" or "unread".

All of those issues are probably caused by the progress bar not being designed for 40 discrete stops. I think this just means this M3 Discrete progress bar is not fit for Mihon purposes.

All of those issues are probably caused by the progress bar not being designed for 40 discrete stops. I think this just means this M3 Discrete progress bar is not fit for Mihon purposes.

This is not the case.

works correctly with a small number of pages, so I don't think this is somehow Mihon's fault.

All of those issues are probably caused by the progress bar not being designed for 40 discrete stops. I think this just means this M3 Discrete progress bar is not fit for Mihon purposes.

This is not the case.

I'm not sure I understand what you mean by "This is not the case" here, to be honest.

All of those issues are probably caused by the progress bar not being designed for 40 discrete stops. I think this just means this M3 Discrete progress bar is not fit for Mihon purposes.

This is not the case.

I'm not sure I understand what you mean by "This is not the case" here, to be honest.

 I thought about it some more, and yeah, your point stands. It’s a mix of Mihon sometimes cramping too many dots inside the progress bar, and Google not having the spacing dynamically changing after a certain point threshold has been passed.

FWIW, I tried checking the M3 spec for these new "Sliders" as these are actually called, but the specs don't talk about a maximum number of steps, or about not colouring anything before 1/6.

FWIW, I tried checking the M3 spec for these new "Sliders" as these are actually called, but the specs don't talk about a maximum number of steps, or about not colouring anything before 1/6.

I see. And I agree, I would be surprised if this is how the new design functioned normally. I don't know what the cause of these issues is.

https://developer.android.com/jetpack/androidx/releases/compose-material3#1.3.0-alpha02

Fixed an issue with Slider and RangeSlider on RTL layout


Support for Jmeter plugins from Plugin Manager in DSL

Hi,
I am currently exploring this Dsl. Looks fantastic. But was wondering if dsl support the various plugins available in JMETER plugin manager like CustomFunctions? Also does it support Azure plugin or any feature to support Azure?

Hello,
I'm glad you like it :).
Regarding plugins, we add built in support for any particular plugins as users request for them and we identify in such requests a general need that would benefit the entire community. We encourage users and in general de community to ask for features and improvements, this way we can properly prioritize work, and make the community be more involved in the development (aside for being able to help with actual code, the community can help us identify improvements or prioritizing work).
In particular for custom functions: how do you use it? What custom functions are the ones you usually use?
As for azure plugin, you mean the Azure Backend Listener? What other kind of Azure support would you like/be interested? We do have some ideas to improve Azure usage experience, but would love to hear community ideas.
In general, some things you can do while we don't implement support for a particular plugin or jmeter feature:

First of all, let us know and ask for them in a GH issues, so the entire community can help prioritize, and can contribute.
You can implement some support, by extending the DSL either for internal purposes or for submiting a PR to contribute it to the community. Here are some guidelines for extension and contribution
You may use wrapper module as a way for easy/simple integration of existing elements without much coding required.

Regards

Hi,
Thanks for the detailed information. I was referring to the example
provided in the
https://abstracta.github.io/jmeter-java-dsl/guide/#custom-or-yet-not-supported-test-elements
section. But when I am trying the same in my IDE it throws an error
saying CustomSamplerGui cannot be resolved. An error is also present
in CustomSampler ret = new CustomSampler();
Where is this CustomSampler coming from?
Thanks & Regards,
Uddipan
On Tue, Mar 7, 2023 at 12:44 PM rabelenda @.***> wrote:

Hello,
I'm glad you like it :).
Regarding plugins, we add built in support for any particular plugins as
users request for them and we identify in such requests a general need that
would benefit the entire community. We encourage users and in general de
community to ask for features and improvements, this way we can properly
prioritize work, and make the community be more involved in the development
(aside for being able to help with actual code, the community can help us
identify improvements or prioritizing work).
In particular for custom functions: how do you use it? What custom
functions are the ones you usually use?
As for azure plugin, you mean the Azure Backend Listener? What other kind
of Azure support would you like/be interested? We do have some ideas to
improve Azure usage experience, but would love to hear community ideas.
In general, some things you can do while we don't implement support for a
particular plugin or jmeter feature:

First of all, let us know and ask for them in a GH issues, so the
entire community can help prioritize, and can contribute.
You can implement some support, by extending the DSL either for
internal purposes or for submiting a PR to contribute it to the community. Here
are some guidelines for extension and contribution
https://github.com/abstracta/jmeter-java-dsl/blob/master/CONTRIBUTING.md
You may use wrapper module
https://abstracta.github.io/jmeter-java-dsl/guide/#custom-or-yet-not-supported-test-elements
as a way for easy/simple integration of existing elements without much
coding required.

Regards
—
Reply to this email directly, view it on GitHub
https://github.com/abstracta/jmeter-java-dsl/issues/176#issuecomment-1458109286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW2XHGDO7UEU3L7AJSX45ALW24USXANCNFSM6AAAAAAVRYVYB4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello, CustomSampler and CustomSamplerGui are just "placeholders" to be replaced by the actual sampler or sampler gui (and more in general testElement and testElementGui) you want to use. The contribution guide goes in more detail (maybe too much in some cases) on what things to do to implement your own DSL test class.
One way to learn how to extend it is checking existing library source code. Eg: DummySampler is pretty simple and you might initially ignore CodeBuilder inner class. Here are some other simple examples:  InfluxdbBackendListener, CsvDataSet, ResponseAssertion, ResponseFileSaver, JsonExtractor.
Note: Implementing a DSL class, should be considered intermediate to high complexity. Using wrapper module is simple to intermediate level. Asking for particular support explaining need is simple (even though is subject to prioritization of work to be done) and may contribute to the entire community.

We have just released a new version which includes AzureEngine that should greatly simplify integration with Azure.
If you have other ideas to simplify Azure usage, please let us know!

I'm closing this issue for the time being. We can re open, or open a new one if any related topic needs further discussion or attention.


when to support webpack5?

As stated in the title

Hi @stxwd46,
there's a Draft PR for Webpack 5 at https://github.com/facebook/create-react-app/pull/7929
It will probably land at CRA 4.1. after we get an stable 4.0. out with Webpack 4.

thanks :)


Delay with touches being responded to after returning from detail view to master list

Short description of the problem:
I've got a very simple tab-based app with a list of items on the first tab which push across a detail view. So I tap on the list item and the detail view pushes on from the right as expected. I tap the Back button and then tap another item in the list. But nothing happens. In fact after returning to the list view, for about the next second, taps aren't responded to at all. Then once the delay has expired, the tap is recognised and detail view slides across as expected. BTW at the moment the detail view is a super simple template with one line of text and 2 properties which are passed from the list view, so I'm sure this is on the list side of things.
Which Ionic Version? 1.x or 2.x
2.0.0-beta.10
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 5.4.1
Gulp version:  CLI version 3.8.11
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.10
Ionic CLI Version: 2.0.0-beta.32
Ionic App Lib Version: 2.0.0-beta.18
ios-deploy version: 1.8.6
ios-sim version: 5.0.4
OS: Mac OS X El Capitan
Node Version: v5.11.1
Xcode version: Xcode 7.3.1 Build version 7D1014

Forgot to say that I'm seeing this issue when running on a device - iPhone 6s Plus - and not when running in Chrome.

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

I've narrowed this down now. It is connected with what element is set inside
The tabs template, has a button which works correctly.
<ion-list>
  <button ion-item *ngFor="let item of items" (click)="showItemDetail(item)">
    {{item.name}}
  </button>
</ion-list>

But if you use another element like a <div> or an <ion-item> as shown in the code examples in the docs for Lists, then the delay happens.
<ion-list>
  <div class="list-row-wrapper" ion-item *ngFor="let item of items" (click)="showItemDetail(item)">
    {{item.name}}
  </div>
</ion-list>

Example project (excludes "node_modules" contents so will need an npm install):
TapResponse.zip

Hello @martinjbaker would you mind adding the tappable attribute to your div and giving it another test?  Example
<div tappable>
</div>

Thanks Justin. Am pleased to confirm that fixes the problem (and shows the dimming when tapped).

Awesome, glad that fixed it for you! Thanks for using Ionic!